I guess just don't by one of these "certified Android devices". Might become a selling point. Other option would be to run SailfishOS (buy a Jolla phone) or install Ubuntu Touch / Mobian and use Anbox.
install them with adb. its a crucial feature for developers, so they won't easily get rid of it.
How do you get updates when installing via adb?
Install them via adb, probably
Is this manageable for the non-dev by chance? I can get by on a tutorial or too but if enough things break I'm feeling a dumbphone alt may be the only viable path
Yes it is.
It will probably be something similar to ios altstore. You would have an app which has a list of your non-playstore apps and repo for their releases and would notify you for upgrades that you would manually have to install (for example I suppose obtainium will implement adb), the setup will be annoying but far far less cumbersome than apple where you have to reboot your device multiple times self sign ipas and refresh once a week otherwise the apps don't load at all. This iOS experience is awful but still doable and non-dev. Android will have a better experience for sure.
There is also Shizuku that might be utilized in der Future to install apps (Im just speculating here)
Depends on your comfort with CLI tools. Here's the process (assumes Windows):
set PATH=%PATH%;C:\your\path\here\ <- Temporary, just for the current sessionsetx /M path "%path%;C:\your\path\here\" <- PermanentOn your device, go to Settings -> About and look for Build Number it can sometimes be buried in Software Information
Tap Build Number repeatedly until a message appears You are now a developer
You should now have a new Developer options menu item somewhere in your settings. Sometimes it's top level, sometimes it's buried under Additional Settings or Advanced Settings or the like
Make sure USB Debugging is turned on
Connect the device over USB
Back on WIndows type:
adb devicesadb devices again. You should see your device listedadb install C:/path/to/app.apk <- if adb devices only returns one deviceadb -s <device_id> install C:/path/to/app.apk <- specific deviceYou can install updates the same way, just download the updated APK and add the -r flag
adb install -r C:/path/to/app.apk
So no
Most of that stuff is automatable - except the bit about activating Developer mode and USB Debugging on the device (steps 3 to 6) which only needs to be done once per device - so I expect we will soon see several nice GUI tools that automate the rest and eventually we might even just see stuff that talks directly to the phone over USB via libusb and using the same protocol as ADB, so installing the Android Platform Tools won't at all be needed.
But yeah, at this point it requires people to at the very least be familiar with using the command line.
Someone suggested elsewhere (I can't remember where) that Shizuku could be messed around with to allow installation without any computer's involvement at all, to emulate adb on the phone itself. Would you know anything about this workaround?
A quick look through its documentation shows that it instructs the user how to go through a subset of the instructions the original user provided (or an alternative set of instructions if using Android 11+ as there it can use a different mechanism) plus a few more, in order to run a Shizuku service as user "adb".
From then on, that Shizuku service can then be used by other apps to do everything the "adb" user can, including installing and updating applications.
So I guess it could be used by something like F-Droid to go around Google's new mechanism to close down app installs.
For Android < 11 it's is no more non-expert friendly than the instructions already provided by the original user, though it's better in Android 11+ as there it's all interacting with menus on the Android side (see here under Start Shizuku)
I feel embarassed to say this as someone who is fairly techy, but I'm a little confused by the whole brouhaha.
Is Google making changes to Android, or to AOSP?
If Google is making changes to the Android fork they put on their own phones, then fuck 'em. Use Graphene. Use e/OS/, use Lineage...use something that forks their own branch of AOSP and Google can pound sand because those forks are in no way obligated to make the same changes as Google. AOSP is open source for that very reason.
If Google is making those changes to AOSP itself, which means that anyone who uses AOSP as a base have those changes by default, then isn't Google obligated to keep those changes as Open Source, in which case anyone else who uses AOSP can just remove them from their own fork?
Someone explain like I'm a particularly dim five-year-old, please.
If you want to keep using google playstore and services, you no longer will be able to use f-droid, whether google or any aosp rom. grapheneOS claims it won't be affected given their sandboxed google play and services. Though I'm not sure if eventually google would come up with a counter measure or it won't ever care. They want to enforce that if anyone uses their proprietary stuff the apps interacting with it must be from register developers, which automatically exclude any libre/free app storage on which developers don't want to register to google. GrepheneOS being the exception.
If you use microG with any custom rom, I guess that might work through fake registrations, but can't be sure. But any custom rom without google play and services is supposed to be ok with f-droid. The thing is that google knows most if not all users need one app that depends on their stuff, perhaps bank apps, payment apps, and so on...
I've also been confused about this, but this is my take on it.
You're correct that they are making these changes to Android and not AOSP. This means that an OS like Graphene or e/OS/ will still be able to use sideloaded apps and other appstores like F-Droid.
I think the reason everyone is freaking out about this, is that it hurts appstores like F-Droid. It has a chilling effect on apps that are released to alternative app stores and may cause those stores to fail over time, thus killing FOSS apps at the point of distribution.
That said, this is also over my head technically, so I would love if someone more knowledgable could weigh in.
I've been using GrapheneOS for a while, which should minimise disruptions, but I'm also hoping the Linux phone ecosystem improves before Google locks down Android completely.
GrapheneOS
I've started donating to PostmarketOS this month, so hopefully I'll be able to buy a device with decent support once my current phone needs replacing.
I already run LineageOS on my phone with microG instead of Gapps, so not much is going to change for me. There'll also be an update to Android 16 for me soon, LineageOS just announced that last weekend.
TL&DR; PinePhone. Longer explanation below
I'll prepare for sacrifices. I should not blame the Open-Source alternatives that they're not on par with Android yet. It was Android's decision to become more closed, and I'll keep remembering it.
I'll start using my PinePhone that I already own anyway. I've used it for a while, but there was less push for me to use back then. Without F-Droid, I'll press myself hard to adapt to PinePhone and will just stay there until it improves. I have 1-2 decades of experience of using non-mainstream software and see it improve with time. I'll learn. I'll adapt.
Get a pocket pc, probably. And only use the phone for what strictly requires it.
It'll likely end up being more comfortable from a usability standpoint than it is now anyway.
Slowly switch to Linux devices, or dumb phone, and learning to adapt happily living without some features, but also without control and censorship :)
I'm gonna get a linux phone. I used a flip phone and windows phone for a long time. I don't actually need any of this bullshit.
I would love to go all in on one of the newer Linux distros made for phones. Haven't tried any yet.
I'm not very good with technology, so I don't understand most of what you're saying. Could you explain it simply, as if I were five years old, how we protect the FOSS community and stop Google to pressuring us.
I'll happily continue using my GrapheneOS Pixel since nothing will change for 3d-party ROMs :)
Until it does. Google is already closing development, so the GrapheneOS devs will have a more difficult time rebasing their changes to AOSP each snapshot.
Not exactly. GrapheneOS has an OEM partner and has early access to AOSP changes that aren't public. A huge downside to that is that security preview releases can't be open source until after Google makes the code public.
Well, that's not a huge downside. They still provide those security updates in their binary builds.
Fair enough. I said "huge" because I guess some people care a lot. I personally don't and have been on security preview releases since they started releasing them.
I don't have to do anything. I use GrapheneOS btw.
The problem for all these things is proprietary firmware.
What problem? Firmware for my phone works fine.
I hope there will be a good Linux phone in a few years that I can switch to. Would be great with it was compatible with the latest Fairphone by then, for a true FOSS and ethical phone.
From what I've been researching, Fairphones pretty much work after a year or two on at least Ubuntu Touch. It uses Halium though for that. It seems like the older ones mostly work after a couple years on postmarketOS, but crucial stuff like audio from the speakers is still broken or whatever. Security is pretty obviously gonna be worse than an Android phone no matter what you use though.
Man this is depressing. I'm hoping the EU will put a stop to this.
brute force it with root
you literally cannot prevent root from doing anything.
What happens wen they prevent rꝏting tho ? Samsung already doing it
Nothing.
My daily driver is an iPhone. We've always had the problem of limiting sideloading (to be nonexistent for most people) and it's never been a problem for me.
I also have a Galaxy S10, but all my apps on that come from the Play Store.
This won't affect 99% of users, just like it doesn't on iPhone.
I just hope now that they're taking sideloading, and they've already taken memory card slots, headphone jacks... and they're still taking a cut off the back end by selling your personal information... maybe the cost will come down. But I doubt it. Android makes sense when it's cheaper than iPhone. I mean, iPhone makes sense to be expensive. It's a pocket Mac, it's made by a computer company. Sure, they have telemetry but it's not an ad company like Google. So for a phone that's less powerful and still has the same restrictions, and I'm paying with my personal data? I expect the phones to be cheaper. They really should be cheaper.
But I'm gonna let you in on a secret. Smartphone performance plateaued a long time ago. All these new phones are kind of a scam. Okay, so the Pixel 10 has the benchmark performance of an iPhone 11. The Galaxy S25 is like 40% faster than the iPhone 16 Pro until it hits load (like the top 1% of games, maybe) then the iPhone is like 10% faster... Who Cares? My 2019 Galaxy S10 is still a viable daily driver in 2025. So, I think I'm done chasing the latest model for a while. If Apple Health comes to iPad (I'm not sure if it's there or not), I'd even consider replacing my Android phone with a newer phone next, like a gently used Galaxy S24 or S25 (I mean in a few years). These new phones talk about performance numbers, but for most people, they don't really mean shit. Phones don't slow down like they used to. They got a lot better and it wasn't even that recently.
The thing is an iphone wont let me do anything. It's useless. No custom connection to my server, no seperate maps, no music, no ssh, no RDP. No adblock, no firefox.
Iphones are kind of nice but you can't do anything worthwhile with them.
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Community icon from opensource.org, but we are not affiliated with them.