I’m pretty sure that custom roms will remove that 24hr wait period from their binaries. Android is still open source and removing a check isn’t going to be very hard for them.
The tech ecosystem is as open as you can. Use linux. Use SearxNG. Use graphene or other custom roms. There’s options out there, you just have to start adopting them instead of just complaining online about having no choice.
This whole APK dicussion is important, but Google is taking steps to lock down the bloody internet if you aren’t on a verified iOS or Android device. This will be far reaching going way beyond the APK changes.
If your country forces you on a locked down OS for ID requirements, something is wrong entirely. You should absolutely make some noise against that and urge them to allow custom OS. That’s a political issue, not a technical.
Shit country tbh. You might be able to get a cheap stock android device for your ID and your “actual” device keeps living the good life on a custom rom. Idk how feasible that is for your lifestyle tho.
I guess one solution to that is to have a second used or ultra low cost phone just for your personal ID and banking stuff. But then it’s no longer really mobile lol.
I might have misunderstood that all those years, but custom roms like graphene or lineage all use the AOSP source to build “their” stuff on top. Android itself is all the proprietary shit google adds and probably bunch of proprietary firmware drivers, which isn’t relevant in the slightest if you switch to a supported device.
AOSP is an open source OS based on a Linux kernel. Importantly, it is not a linux distro. GrapheneOS and LineageOS are downstream, open source derivatives of AOSP. Android is the same, but is proprietary.
Android isn’t just what is added on top of AOSP, just like Ubuntu isn’t just things added on top of Debian, but a complete OS.
Yeah, that’s roughly what I thought, in which case switching to graphene (or any other custom rom) would completely “release” you from the proprietary grasp of google and their genius ideas. Because even if they add this 24hr lockdown in the AOSP-Project, graphene could rather easiely revert that change in their fork.
I’m pretty sure that custom roms will remove that 24hr wait period from their binaries. Android is still open source and removing a check isn’t going to be very hard for them.
The tech ecosystem is as open as you can. Use linux. Use SearxNG. Use graphene or other custom roms. There’s options out there, you just have to start adopting them instead of just complaining online about having no choice.
Google reCaptcha enters the chat.
This whole APK dicussion is important, but Google is taking steps to lock down the bloody internet if you aren’t on a verified iOS or Android device. This will be far reaching going way beyond the APK changes.
related article
Not everybody has a choice. I’m currently on grapheneos, but it looks like I may be forced back to android due to national ID requirements.
If your country forces you on a locked down OS for ID requirements, something is wrong entirely. You should absolutely make some noise against that and urge them to allow custom OS. That’s a political issue, not a technical.
It’s not going to go anywhere in my country, unfortunately. Not even a blip on the radar.
Shit country tbh. You might be able to get a cheap stock android device for your ID and your “actual” device keeps living the good life on a custom rom. Idk how feasible that is for your lifestyle tho.
I guess one solution to that is to have a second used or ultra low cost phone just for your personal ID and banking stuff. But then it’s no longer really mobile lol.
AOSP is open source, android isn’t
I might have misunderstood that all those years, but custom roms like graphene or lineage all use the AOSP source to build “their” stuff on top. Android itself is all the proprietary shit google adds and probably bunch of proprietary firmware drivers, which isn’t relevant in the slightest if you switch to a supported device.
Not quite, but I would accept that.
AOSP is an open source OS based on a Linux kernel. Importantly, it is not a linux distro. GrapheneOS and LineageOS are downstream, open source derivatives of AOSP. Android is the same, but is proprietary.
Android isn’t just what is added on top of AOSP, just like Ubuntu isn’t just things added on top of Debian, but a complete OS.
Hope that helps
Yeah, that’s roughly what I thought, in which case switching to graphene (or any other custom rom) would completely “release” you from the proprietary grasp of google and their genius ideas. Because even if they add this 24hr lockdown in the AOSP-Project, graphene could rather easiely revert that change in their fork.
Yes. Most of those AOSP forks still use elements of android (google play services) for compatibility reasons.
Graphene doesn’t, they got their own sandboxed google play services compatibility layer. Other OS - no idea tbh.
It’s actually the opposite. GOS GPS are real GPS, most other AOSP distros use MicroG, which is reimplementation of GPS.
It’s real GPS, but within a sandbox without additional permissions. https://grapheneos.org/usage#sandboxed-google-play