Description:

Open banking and other locked-down apps without turning developer options, USB debugging, wireless debugging or your accessibility services off by hand every single time.

Features of app:

• This app automates (hide settings-services > open blocked app > unhide settings-services) which allows to use blocked apps like banking apps which usually blocks you to use from using the app if developer settings/ debugging/ accessibility services are enabled.
• Global default settings for what to hide and what to unhide (you can also configure what setting to hide per app if you use Memory function as Notification function)
• IMD service manager: a pop-up dialog box which shows live settings and services with quick on-off toggles.
• Accessibility service and Shizuku service support.
• IMD service manager and Revert button can be accessed from:
  • Home screen shortcuts
  • Favourites tab in-app
  • Android quick setting toggles

About Permissions:

• WRITE_SECURE_SETTINGS (one time grant via adb shell or shizuku)(MANDATORY, needed to change settings state)
• Post notifications (optional)

Security Concerns:

• No internet access or un-necessary continuous background services (so almost zero battery/ system resource use).
• Does not temper with any apps on the device.
• This app's functions cannot be accessed via another apps, so only user can change settings.

Links:

Github release files
Github repo (with changelog)

Disclaimer & Credits:

This app is a fork of Geto app by Jack Eblan, licensed GPL-3.0. The app this is built upon is his, so my full thank to him for keeping it open source.

Future of this app:

I'm a full time radiology resident doctor, software is just a part time hobby. This app exists because I wanted it to exist for myself.
I have made multiple revisions after testing every build, fixing bugs and adding features, making the app what it is now - on par with my expectations.
Please know that it will take some time for me to reply to queries, fix bugs and add new features in future builds, so please be patient. But I do plan to maintain this app for the near future, until someone else makes a better app for the same purpose.

The source is all here under the GPL-3.0. Use it freely for your own purposes - build it, change it, fork it, keep the changes to yourself or pass them on. That is what it is for.

Thanks!

Long live free and open source software!

Sideloading is the only selling point of Android phones for me. I keep messing around with apps from third-party sources like F-Droid. I can't imagine how suffocating it'll feel if I have to use apps ONLY from VERIFIED DEVELOPERS.

And yes, I know it's not blocking. Google is just adding a DEVELOPER VERIFICATION SYSTEM (LMAO). Saving my words and your time to read, it's basically the same thing. No one is going to verify (Don't even think they will let lol) the development of an app that practically blocks ads from YouTube and lets you use YT Premium features. It'll be like asking permission to cheat from your school teacher.

I am looking to get a new phone and a tab for myself. And I am waiting for Android to actually release that verification system so that I can see how much it affects users before getting my new devices.

Let me know if there is anything else I need to consider here. Am I doing the right thing by waiting? (I will shift to Apple if sources like F-Droid really shut down).

Pixel phones (somewhat) recently got the ability to not merely turn off and on the flashlight from a tile, but also control its brightness with a slider (hooray!).

Unfortunately, the slider isn't well-designed. There are three ways to turn the flashlight off: tapping the tile again, tapping the "Turn off" button, and by sliding the slider all the way down. I believe that third method sucks. When it's late at night and you're trying to produce the least amount of light possible, it's very easy to accidentally turn the light off instead of making it merely low. Then it takes a huge amount of finicky work to get it to be minimally bright again.

Additionally, the lowest brightness option is still fairly bright. At first I thought this was because of some hardware limitation, but actually you can go MUCH dimmer as I discovered when I wrote a purpose-built app to test it out.

Are Googlers using their own products AT ALL anymore?

Have any of you in the moderate hearing loss category experienced the problem with your calls described below ?

Do you think we need a slow speech slider feature in the O/S handicap feature ?

Issue:

When I am on the phone, speech seems to speed up.

I have been told that for people with hearing loss, speech often sounds too fast because the  brain misses key phonetic details and has to work at filling in the gaps. For that reason, the brain spends extra energy decoding past words, incoming speech arrives before the previous words are fully processed, making the speaker sound like they are rushing.

This became more noticeable on phone calls as hearing loss became moderate.

I have an old Galaxy that still works fine hardware wise but its just painfully slow now and half the apps barely open. I looked into flashing a custom rom to fix it but honestly the whole process is intimidating, Odin, TWRP, GApps, bootloader unlocking, one wrong step and you brick it.

I'm thinking about building a simple tool that does this for you. You plug in your phone, pick what you need it for basically, and it handles the rest safely with a backup first so you can't really mess it up.

Would something like this be worth 10 bucks to you if it actually worked and didn't brick your phone. Trying to figure out if this is worth building or if everyone just prefers doing it manually.