Mishaal Rahman3d ago

📣Important clarifications on the new advanced flow for sideloading on Android!

1) It is a one-time process. Once you go through it, you can choose to allow installing unregistered apps indefinitely.

2) ADB installs are not affected. The waiting period does not apply to app installs via ADB.

3) It's my understanding that you don't have to keep developer options enabled after you enable the advanced flow. Once you make the change on your device, it's enabled...

Show threadMishaal Rahman3d ago
...If you turn off developer options, then to turn off the advanced flow, you would first have to turn developer options back on.
Show threadaryan3d ago
@MishaalRahman Haha i'm not going to tirn that off, and if i get a new device, it will probably be the first thing i enable lol.
Show threadYaksh Bariya3d ago

@Aryan Wait till they make this option available to "trusted" apps on play store via a API and they force you to turn this off becoz sEcuRiTty

I am honestly already annoyed by a lot of bank apps doing this, to the point that I have got rid of all of those crap and now I do most of my banking via my browser

Show threadaryan3d ago
@CodingThunder Urm, can this even be an Api?
Show threadYaksh Bariya3d ago

@Aryan Might be not sure, I haven't looked into it. But there are bank apps that refuse to open if certain apps are installed. I am not getting the link to the Reddit thread someone posted about it a few months ago. But Google already allows apps to query for installed apps, as well as look for developer options flag for apps, so won't be surprised if they allowed apps to also query if sideloading is enabled.

(Take this as a mountain of salt)

Show threadYaksh Bariya3d ago
@Aryan Also AOSP code isn't now maintained publicaly or else could have confirmed before it hit the release channels
Show threadaryan
@CodingThunder yeah, but we do still sea the code updated once in a while still?
Mar 19 at 6:44pmWeb
Show threadYaksh Bariya3d ago

@Aryan Yep they release the code once in a while after Android releases, the AOSP code is always lagging behind though. GrapheneOS devs were complaining about it last year or something. Also, I don't have to look at AOSP that much.

Mostly I do look at bionic (the cursed child made by forced mating of FreeBSD libc and glibc, aka the libc used in Android), and so I don't care much about the unreleased versions, and just the stable releases that actually ships on devices

Show threadaryan3d ago
@CodingThunder + on top of that brands like realme and oppo do their own fuckery, like makeing termux crash or whatever.
Show threadaryan3d ago
@CodingThunder Also, not to mention completely break the stoc android accessibility stac and try to implement their own which breaks the experience for users who are blind and just want to use their screenreader normaly.
Show threadYaksh Bariya3d ago

@Aryan Software accessibility is a difficult topic. Requires quite a bit of planning and engineering to ensure that things are accessible.

But yeah even as someone with eyes, I absolutely hate these brands trying to redo the UI just to make it look like a cheap Apple iOS clone while performing like shit.

Show threadYaksh Bariya3d ago
@Aryan Even Samsung's OneUI is something which my brain can't get around because of weird "swipe down from left" is notifications and "swipe down from right" is the control panel. I can do nothing but wonder how hard it is for folks with limited/no vision.
Show threadaryan3d ago
@CodingThunder That shit e can do using the gestures, But samsung uses its own version of talkback which makes samsung users miss out on nice features that google talkback gets.
Show threadaryan3d ago
@CodingThunder Yeah, it definitely does. But when your userbase is complaining for the last 2 years and you don't listen, then its definitly your negligence.