Accessiblility, developer mode hide option doesnt seems to work

[istiakahmed0190]

Issue Checklist

• I confirm that this issue is not a duplicate and hasn't been reported before.
• I agree to follow the project's code of conduct.
• I have checked and verified that I am using the latest version of Geto from GitHub or F-Droid.

Additional terms

• I understand that providing incomplete or inaccurate information may result in the issue being closed.
• I agree to provide all requested details promptly for a comprehensive bug report.

Issue explanation

Nexus pay app developer mode enabled popup show even after enabling all the 4 options in geto. This option stops first time if i manually stop shizuku. But then detects accessibility service enable hhis type popup show. And after that again developer mode enabled show. (Although all this time developer mode wasnt really enabled , but shizuku was running)
This are the accessibility apps running (they are using shizuku)
<img width="1080" height="2208" alt="Image" src="https://github.com/user-attachments/assets/8190cacf-1dae-4f20-bdf5-d19bdc3b308a" />

Expected behavior

..

Version name

1.17.1 and its immediate previous version. Also from fdroid

Download source

GitHub

Relevant log output

[T31n]

It could be that it has different Setting key?

Yes I have confirmed it. The templates gave wrong value. Please add it on your own.

Read it here. The Setting type is Secure
https://developer.android.com/reference/kotlin/android/provider/Settings.Secure#accessibility_enabled

[istiakahmed0190]

Thanks for the reply. But still same. With shizuku shows developer mode enabled, without shizuku detects accessibility.

[T31n]

Thanks for the reply. But still same. With shizuku shows developer mode enabled, without shizuku detects accessibility.

Do you click the Launch? The arrow at the bottom right?

[istiakahmed0190]

-_- obviously. Even cleared cache,data,reinstalled geto.

[defurious]

-_- obviously. Even cleared cache,data,reinstalled geto.

try using enabled_accessibility_services as the setting key not accessibility_enabled. you need to type that in btw. thats what works for me. if you see the Setting Value on Revert field populate with package names then you'll know thats the right one. I also used null in Setting Value on Launch.

[istiakahmed0190]

-_- obviously. Even cleared cache,data,reinstalled geto.

try using enabled_accessibility_services as the setting key not accessibility_enabled. you need to type that in btw. thats what works for me. if you see the Setting Value on Revert field populate with package names then you'll know thats the right one. I also used null in Setting Value on Launch.

Thanks. Now it doesn't detect Accessibility Enabled because Geto successfully disables the accessibility services. However, after testing, I found these issues on my device:

1. False Developer Mode detection
   The "Developer Mode Enabled" warning seems to be triggered by Shizuku, not actual Developer Options. My Developer Options are OFF, but NexusPay detects them whenever Shizuku is running. Once Shizuku is completely stopped, the warning disappears. Maybe NexusPay is detecting Shizuku but showing the generic "Developer Mode Enabled" popup.

Note: so after some more i found shizuku needs usb debug enabled(adb mode) so this is what causing that developer mode enabled popup.

2. enabled_accessibility_services key detection
   If I manually type enabled_accessibility_services, the Revert field does not auto-populate. If I select the same key from the dropdown, it immediately fills with the current accessibility service package names. It looks like manually entered keys and dropdown-selected keys are handled differently.

3. Accessibility revert not working
   Setting enabled_accessibility_services = null successfully disables accessibility services, and the previous value is correctly backed up in the Revert field. However, after closing NexusPay (even after removing it from Recents), the original accessibility services are never restored. The backup works, but the revert action does not (maybe because Shizuku is stopped before).

4. Lock Me Out compatibility
   Using enabled_accessibility_services = null disables all accessibility services, including Lock Me Out. Since Lock Me Out enforces its accessibility service, it immediately shows the "Enable Accessibility" prompt. This is likely a compatibility issue rather than a Geto bug, but it prevents this workaround from being used with Lock Me Out enabled.

[istiakahmed0190]

Do you click the Launch? The arrow at the bottom right?

Sorry for the confusion earlier - it turned out I had disabled Geto's notification, so I completely missed the manual Revert action. 😅
After further checking , I have two feature requests that would make Geto even more useful:

1. Stop/Restart Shizuku:
   Since Shizuku requires USB debugging to be enabled, many banking apps detect it. It would be great if Geto could optionally stop the Shizuku server on app launch and restart it on revert.
2. Control "Display over other apps" :
   Disabling enabled_accessibility_services stops accessibility services successfully but some apps like Lock Me Out which uses Display over other apps permission still allows them to show a popup asking to re-enable accessibility (like every 5 sec, which is a pain). It would be very useful if Geto could temporarily disable/restore this permission on launch/revert.

I found that the following ADB commands achieve exactly what I need, although I guess Geto can't execute them directly at the moment:
Launch: cmd appops set com.teqtic.lockmeout SYSTEM_ALERT_WINDOW ignore
Revert: cmd appops set com.teqtic.lockmeout SYSTEM_ALERT_WINDOW allow
Thanks again for the great app!

[MirazMac]

1. Stop/Restart Shizuku:
   Since Shizuku requires USB debugging to be enabled, many banking apps detect it. It would be great if Geto could optionally stop the Shizuku server on app launch and restart it on revert.

I second this. Happening the same thing on my device too. If I disable Shizuku's Watchdog, NexusPay won't detect Developer Options anymore. So either it's disable first then use Geto or keep Watchdog turned off and start Shizuku afterwards.

It'd be nice if Geto could stop/start Shizuku via the auth token or something. Don't know if that'd be possible.

[shajal0190]

It'd be nice if Geto could stop/start Shizuku via the auth token or something. Don't know if that'd be possible.

I made a taskar (now using macrodroid) widget to stop and start shizuku (using the auth token). So current workflow is stop shizuku, use geto, revert ,start shizuku.
Maybe i can do all this things just by using macrodroid/ taskar w/o using geto at all (someone on reddit said to do that sort of thing) but i am too lazy.

[shajal0190]

In case anyone is interested , I am using shizuku fork Version 13.7.0-thedjchi