Replies (23)
WTF. Well, this absolutely does suck, but at least there's still the ability to side load apps, which iOS doesn't allow at all. But Jesus. What bullshit.
And restart your device.
I suppose the good news is:
"with the option to allow installs for seven days or indefinitely. Even within that seven-day time frame, once sideloading is enabled you can install as many different APKs from as many different unverified developers as you like"
It's a one-time 24-hour wait for the setting update, not a 24-hour wait every time a side load happens, to be clear.
what the hell is this crap??? we dont hate big tech enough.
We gotta protect GrapheneOS at all cost
The user has to say they aren't being coached. So if I'm walking a friend through installing on of my apps, I have to ask them to lie to get the first step done?
That we have to do anyways but these rules on normal Androids are not changing anything for you and me do they?!
They don't but if we lose GOS we are fucked
LMFAO. Android users love to brag that they have full control over their device, only recently learning that they never really had any control at all.
I hear this all the time, their logic is,”I paid for the device, I should be able to with it as I please, and you can. It’s the software that it is running that you don’t own and graphene is no different.
I own a car, does that mean I can drive it however I chose?
I own a gun, does that mean I can shoot it however I please?
Starting to understand why that logic is moronic?
It will affect them as well.
You think Google is gonna let them get away with it? Let me know how that works out.🤣
It will be interesting what will happen with AOSP
See, that’s the thing, Google
maintains AOSP. Graphene is still using their code, they are just forking and hardening it for their use. They didn’t magically create their own version of Android out of nothing and therefore are also subject to rules that Google lays down.
I got tired of having to flash custom software so that the device I paid a significant amount for, runs the way it should have out of the box. Every Android device is like this, ironically, even the devices from the company maintaining the code.
Eventually I just said fuck it and joined #teamapple. Sure there are drawbacks, but the benefits of being able to just use my device without constantly playing cat and mouse with Google/safetynet or having to flash something else custom because the OEM version is horrible or the custom version I was using is no longer being maintained, are immeasurable. For me, I’ll just stick to one ecosystem because Apple does it better than anyone else.
@npub1c9d9...sqfm could you confirm #GrapheneOS will remove the sideloading restrictions set in AOSP?
Insane. I might finally switch to Graphene.
You do relize only 12% of all Android phones can even be developer unlocked? 88% cannot be unlocked, like at all, from step one.
You do relize only 12% of all Android phones can even be developer unlocked? 88% cannot be unlocked, like at all, from step one.
Curious how this will work for developers themselves. 24 hours to install your own new code? Guess I'm disabling updates on my pixel 10 (OEM locked or it'd be graphene already).
Don't get cocky itoddler 👶 forks are a great thing 🍾 and new code 💾 that does this is easily removable 🧽 from a fork.
We're yet to see this implemented in AOSP. We won't be adding sideloading restrictions.
It’s humorous that people think graphene is somehow immune to this. Google maintains the code that graphene forks. Sure, maybe graphene could get around the code, until Google finds out and just says fuck it, no more unlocked devices or modified Os’, the end.
If that’s not clear enough, the only reason you can flash graphene, use a custom AVB key and relock your bootloader, is because Google allows it.
And it’s not just the device, some carriers don’t allow it either, so it wouldn’t matter if you bought a pixel.
When things change, we will find a way.
What's important is not becoming a cucked doomer.