Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: !android@lemdro.id
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
Sloppy use of terms in the article. Locked down bootloaders should be illegal.
All new phones come with a locked bootloader, but unlocking codes are delivered on (a few) maker's website by IMEI. Then the user unlocks it, installs a new OS, some of which can re-lock the bootloader with a new signature, re-enabling verified boot = secure boot, which stops malware from making itself reboot-resistant, and blocks evil maid attacks through the USB port.
The problem with the codes being on the website is that it gives the company control over who can unlock the bootloader
Eh. It's a bit more complicated than that. Most of the carrier phones are locked because they are given to customers on a financed plan. Unless and until the phone is paid off and all other contract terms are satisfied, then the customer doesn't actually "own" the device. It sucks, but it does make sense in the context. If you don't like it, then don't enter into such agreement. Either buy your device outright or use alternative means of financing which do not impose such restrictions.
My point is that those restrictions exist on a non-financed plan. Also, computers get sold financed all the time with an unlocked bootloader and it's not a big problem, I don't really see how the existence of financed plans justifies the practice.
Seriously? Are you serious? Perhaps for the same reason you are required to carry comprehensive insurance on a car you are still paying the note for. Or why you can't remortgage your hose to turn it into an amusement park. Or why a company owned laptop may not give you admin access. Because you don't have full ownership of the underlying assets. You don't have to like it, but claiming not to understand it is just being juvenile and intentionally obtuse. JFC.
I said that the existence of plans with locked bootloader doesn't justify the practice of locked (with key on website) bootloaders on non-leased smartphones, no need to be rude.
Your comparisons are flawed because all of those things are required to reduce or offload risk, whereas locking the bootloader on a phone doesn't really reduce the risk, since phones are so easy to lose or damage. They could just presume the phone lost if the bootloader is unlocked, and require full payment anyways, so I will change my position to be that it should be unlocked regardless.
Like are you really having trouble understanding this?
You literally typed out the correct understanding in your last response and then just blew right past it.
If I gave you a $1,200+ device on credit, I would want to reduce my risk by limiting what you can do with it while you still owe me money for it. Like not being able to run arbitrary software on it, as an example. I would need a method to enforce this while still allowing you full control once you've paid me my money.
Which is exactly why most phone plans also require you to carry device damage and theft insurance on financed devices.
Planning to need to recover losses is never a smart idea. Not to mention this would likely bite hardest on exactly the demographic which is most difficult to recover monies from.
As a side note. Usually the answer to a question (or prescription) of the form, "Why don't [they, we] just ..." is because the thing suggested is likely critically flawed in some way that may not be immediately apparent.
If you aren't happy with that you don't have to do business with that company, or use them to finance a device. Phones purchased outright from retailers or manufacturers come unlocked. I don't understand why a perfectly practical and understandable businesses practice is making you so irate.
If you want to be outraged at something, be outraged at a company trying to, through aggressive business and software practices, control what you do with a device that you own outright. You know, like what is claimed is happening between Google and GrapheneOS in the article you are posting comments on.
Just to be clear. I'm not arguing with you. I am trying to help you understand how the world works because you seem to be having trouble. And I've done the best I can. Possibly I could have been nicer about it, but I think I've still been fair. In any case this will be my last response to you. I wish you the best in all your future endeavors.
I understand the world very well, in the future if you want to help people understand things try being less condescending, hope this helps :)