You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m sorry to open the thread, today I’m done the steps to install the own launcher but it don’t work’s. It seems Amazon has change something since the OS Version 6.2.7.3.
The Following steps are working fine it the past, but now i configure a new 4k Stick with the Fire OS Version 6.2.7.3 and it it doesn't works:
Ok, here is a quick and dirty solution:
Edit: before doing this first uninstall LauncherHijack if you have it still installed.
First install the cloned LauncherHijack apk from here
Then install the apk inside this zip
(don't pay attention to its UI if it shows, it's just a template, the important part is that when it opens it configures the accessibility variables as needed)
Then grant it the required permission by running:
adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
__
Have anyone a new solution?
The text was updated successfully, but these errors were encountered:
I’m sorry to open the thread, today I’m done the steps to install the own launcher but it don’t work’s. It seems Amazon has change something since the OS Version 6.2.7.3.
The Following steps are working fine it the past, but now i configure a new 4k Stick with the Fire OS Version 6.2.7.3 and it it doesn't works:
Ok, here is a quick and dirty solution:
Edit: before doing this first uninstall LauncherHijack if you have it still installed.
First install the cloned LauncherHijack apk from here
Then install the apk inside this zip
(don't pay attention to its UI if it shows, it's just a template, the important part is that when it opens it configures the accessibility variables as needed)
Then grant it the required permission by running:
adb shell pm grant com.example.settest.settingstest android.permission.WRITE_SECURE_SETTINGS
__
Have anyone a new solution?
The text was updated successfully, but these errors were encountered: