| ▲ | binyu 5 hours ago | ||||||||||||||||
> This is ignoring the fact that the main reason retired phones are e-waste is proprietary firmware blobs and locked-down systems Couldn't Google somehow fix this? Since they control the substrate (Android) and they would be doing it for their convenience | |||||||||||||||||
| ▲ | Elfener 4 hours ago | parent | next [-] | ||||||||||||||||
They're literally doing the opposite, right now you can't install a custom operating system, but in the near future you won't be able to install custom apps either: https://keepandroidopen.org/ | |||||||||||||||||
| |||||||||||||||||
| ▲ | redleader55 5 hours ago | parent | prev | next [-] | ||||||||||||||||
Unfortunately it is a bit more complicated than that. All these phones run firmware, bootloaders, libraries under license from SoC providers, who package components from other vendors under a license themselves. Opening up the bootloader can be done, but two things have to happen: either the phone is crippled of various functionalities or the manufacturer is in breach of license because all the binary blobs become open and can be reverse engineered. No one wants to go through all of this for a few hundred people who are interested in running their home assistant on an exotic device. | |||||||||||||||||
| |||||||||||||||||
| ▲ | ajsnigrutin 5 hours ago | parent | prev [-] | ||||||||||||||||
Why would they? They're actively working on closing the ecosystem even more (no more sideloading), DRM features, etc. Maybe they'd do it for themselves, but they clearly don't want you, the customer, to do whatever you want with the device you bought and paid for. | |||||||||||||||||