Since F-Droid (i.e., the repositories, not the app) builds all apps, a practical solution would be for the repositories (i.e., their signing keys) to be recognized by El Goog. Whether and how much help / obstacle the "maybe we do evil" company puts up for / against this is a different question.
It seems to me this is a blocker to use if google can restrict sideloading like this. Its not going to end with just get people requiring to register their app with an identity. Wont they be able to put presser on f-droid devs to lock out software they consider a threat to some business model?
That newspeak term should just disappeared. It only contributes to the image that downloading and installing an app is something that is outside the "happy path". Installing software of your choice on a device you own shouldn't be demonised
If the issue Google has with sideloading is really just the rampant app piracy (and the malware that comes with cracked apps) that might be something F-Droid can accomodate.
The Emacs version for Android makes uses of something like this IIRC by signing a version of Termux with the same key and distributing it in the same SourceForge repo such that Emacs on Android can access CLI tooling like git for example.
It looks exactly the same as now. You will have to do Google's 24 hour flow thing, but it's not like that's going to stop anyone who appreciates what F-droid brings to the table.
It seems google is going to allow an "advanced flow" that is scam resistant by requiring the user to wait 24 hours before they can start installing their own apps. It sucks, but assuming they don't change the plan again, F-Droid should be able to continue working.
Currently, switching to GrapheneOS means giving Google money. Next year's Motorola-based alternative is also likely going to be several price classes above the Pixels you can currently put GrapheneOS on.
Then buy a Pixel second-hand or when they hit rock-bottom prices, which usually happens after 6 months or so. At some point Google is probably not making a lot of profit from the devices anymore and they want to sell it to you for tracking and to sell Google One subscriptions, which are mostly irrelevant if you use GrapheneOS.
The current lockdown plan is that you'll need to wait 24 hours before installing the first unauthorized app, right? So probably exactly the same as it is now except setting up a phone will take 24 hours longer.
Updates on this have been slowly trickling out and the best I can discern is you will be able to still install apps from stores like F-Droid, but you have to go through a manual "advanced flow" which will most likely make you wait 24 hours before installing it and make you go through other hoops.
In short, google has referred to this as "increased user friction" to try and deter people from doing this. Essentially not making it impossible; just really frustrating for users so they get sick of the process and just install verified apps through them.
The only way I know around this is to install a custom rom like GrapheneOS or Lineage OS since this change targets Because the policy targets the Google Mobile Services (GMS) framework rather than the foundational Android Open Source Project (AOSP).
There is an entire world of Android phones not controlled by Google, including GrapheneOS, LineageOS, and countless variations in China and other places where Google is effectively banned.
Isn't it possible, however complicated, for users to undo the lockdown to install an app? The required 9 steps are noted at https://keepandroidopen.org/ for devices that use Google Play Services.
Irrespective, people should probably be migrating to a GrapheneOS or similar OS asap once the OS ships with a device.
Honestly not as bad as I feared it would be. Still not great and it's moving us farther from the idea that people who paid for the device should be allowed to install what they want on it, but as it stands it's a workable process. We'll see how quickly it takes Google to make it worse
Since F-Droid (i.e., the repositories, not the app) builds all apps, a practical solution would be for the repositories (i.e., their signing keys) to be recognized by El Goog. Whether and how much help / obstacle the "maybe we do evil" company puts up for / against this is a different question.
It seems to me this is a blocker to use if google can restrict sideloading like this. Its not going to end with just get people requiring to register their app with an identity. Wont they be able to put presser on f-droid devs to lock out software they consider a threat to some business model?
> sideloading
That newspeak term should just disappeared. It only contributes to the image that downloading and installing an app is something that is outside the "happy path". Installing software of your choice on a device you own shouldn't be demonised
30 replies →
If the issue Google has with sideloading is really just the rampant app piracy (and the malware that comes with cracked apps) that might be something F-Droid can accomodate.
3 replies →
They have to use one key per app, otherwise independent app could end up sharing some permissions (IIRC).
The Emacs version for Android makes uses of something like this IIRC by signing a version of Termux with the same key and distributing it in the same SourceForge repo such that Emacs on Android can access CLI tooling like git for example.
It looks exactly the same as now. You will have to do Google's 24 hour flow thing, but it's not like that's going to stop anyone who appreciates what F-droid brings to the table.
It seems google is going to allow an "advanced flow" that is scam resistant by requiring the user to wait 24 hours before they can start installing their own apps. It sucks, but assuming they don't change the plan again, F-Droid should be able to continue working.
> assuming they don't change the plan again
Knowing Google, that's a big assumption
Alternative app stores are mandated atleast here in the EU I believe?
Yes but the process to enforce it is intentionally so difficult that nobody can do it.
Yes, but the ability to install any software isn't. goggle can still decide to allow only "official" apps in """3rd party""" stores.
Switch to GrapheneOS or HarmonyOS
Currently, switching to GrapheneOS means giving Google money. Next year's Motorola-based alternative is also likely going to be several price classes above the Pixels you can currently put GrapheneOS on.
Then buy a Pixel second-hand or when they hit rock-bottom prices, which usually happens after 6 months or so. At some point Google is probably not making a lot of profit from the devices anymore and they want to sell it to you for tracking and to sell Google One subscriptions, which are mostly irrelevant if you use GrapheneOS.
6 replies →
There's zero reason to buy a last year phone.
The current lockdown plan is that you'll need to wait 24 hours before installing the first unauthorized app, right? So probably exactly the same as it is now except setting up a phone will take 24 hours longer.
Updates on this have been slowly trickling out and the best I can discern is you will be able to still install apps from stores like F-Droid, but you have to go through a manual "advanced flow" which will most likely make you wait 24 hours before installing it and make you go through other hoops.
In short, google has referred to this as "increased user friction" to try and deter people from doing this. Essentially not making it impossible; just really frustrating for users so they get sick of the process and just install verified apps through them.
The only way I know around this is to install a custom rom like GrapheneOS or Lineage OS since this change targets Because the policy targets the Google Mobile Services (GMS) framework rather than the foundational Android Open Source Project (AOSP).
Wait, it's not 24 hours per app though, is it? Isn't it 24 hours before the "allow installing apps from .apks" setting turns on once and for all?
Yes, you toggle it once and that's it. It also moves with backups so new devices don't need that step.
If I'm a developer I also need to wait 24hrs to test my app?
So you will think really hard about what you're doing instead of just hoping :D
There is an entire world of Android phones not controlled by Google, including GrapheneOS, LineageOS, and countless variations in China and other places where Google is effectively banned.
Isn't it possible, however complicated, for users to undo the lockdown to install an app? The required 9 steps are noted at https://keepandroidopen.org/ for devices that use Google Play Services.
Irrespective, people should probably be migrating to a GrapheneOS or similar OS asap once the OS ships with a device.
Ah this is good to know. Awful it's required, but glad there is a work around.
Honestly not as bad as I feared it would be. Still not great and it's moving us farther from the idea that people who paid for the device should be allowed to install what they want on it, but as it stands it's a workable process. We'll see how quickly it takes Google to make it worse
no root on graphene, non starter