Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for latest Fire OS restriction on changing settings via adb (Proof of concept) #53

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wilkovatch
Copy link

Note: This is just a proof of concept, it could break something if done like this.

This fixes the restriction introduced by the latest FireOS version (at least on Fire TVs): the setting enabled_accessibility_services cannot be changed anymore via adb, however it can still be changed via application. Hence the solution: change it via LauncherHijack itself. This way, instead of setting the accessibility variables manually, the users just need to grant LauncherHijack the required system permission:

adb shell pm grant com.baronkiko.launcherhijack android.permission.WRITE_SECURE_SETTINGS

@RedcatPhoenix
Copy link

heck no, use this https://www.mediafire.com/file/kqa89yndk468itf/Launcher.Hijack.v.4.0.3.b.43.Clone.apk

@wilkovatch
Copy link
Author

@oathzed Here it is: SettingsTest.zip

@oathzed
Copy link

oathzed commented Aug 25, 2019

@wilkovatch you're the best man, thank you

@pychopaul
Copy link

Thank You!! i almost sent my 4k stick back, but your way works. also, if you dont already know, you can use shizuku app to enable icebox app, which can then be used to freeze amazon updates on the stick. i believe this is the only working way to block them now. although it is unclear on the xda page, once you freeze apps, they do stay frozen through reboots. https://forum.xda-developers.com/fire-tv/general/suprise-root-pc-adb-fire-stick-to-t3918668

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants