Accessibility Permissions Manager​
Hi Everyone,
I would like to share with you my app which you will only need if you want to use apps which needs Accessibility Permissions to work.
This app reduces the hassle to enter the commands to set those apps up and is created to be used on FireTV Devices.
Instructions:
Enable ADB Debugging on your FireTV.
Open Accessibility Manager.
If you are on FireOS 6 or 7 then you will see a prompt to Allow ADB Debugging, Click ALLOW
if app shows Connection Failed Disable then Re-enable ADB Debugging.
Sometimes reboot is required, and if you are still getting Connection Failed, there will be System Update ready to install
Install that update and reopen Accessibility Manager.
If everything goes fine, you will reach the Main Screen where you can Allow and Deny other Apps.
After that you can Disable ADB Debugging to be on safe side, you will not be needing that anymore.
If you are on FireOS 5, follow the on screen Instructions,
you will need a PC with ADB on it, or you can use Remote ADB Shell on other Smartphone.
after following the Instruction reopen Accessibility Manager and you are good to go.
NOTE: APP WORKS ON OLDER VERSION OF FIREOS ONLY.
XDA:DevDB Information
Accessibility Manager, Device Specific App for the Amazon Fire TV
Changelog
Version 1.8
Optimized Code
Version 1.7
Bug Fixes
Version 1.6
Fixed Scrolling Issue
Contributors
SweenWolf
Version Information
Status: Beta
Current Beta Version: 1.8
Beta Release Date: 2020-12-06
Created 2020-08-07
Last Updated 2020-12-06
Reserved
fireos 6.2.7.2
Fire Tv Setting - accessibility service is still OFF in Fire TV Settings after installing
Accessibility Manager_1.6.apk
On/Off Sleep mode auto starts Wolf Launcher, but hard-reset brings original amazon home screen. & pressing home button on remote still brings me to OG home screen (amazon) launcher.
Please anyone tell LaunchX method in OP is still working as of 16 Aug or not..
Because after doing everything for me it's not working.. Amazon launcher keep coming back after pressing home button on remote!!
Profzack said:
Please anyone tell LaunchX method in OP is still working as of 16 Aug or not..
Because after doing everything for me it's not working.. Amazon launcher keep coming back after pressing home button on remote!!
Click to expand...
Click to collapse
Seems like the latest Amazon Update broke it again. we have to wait for the developers
Yes, mine also FTV4k did an update last night going from 6.2.7.1 to 6.2.7.3
Now Accessibility Services: Stopped.
Home screen button back to default UI
Yup same here, just got the same update last night. So Accessibility workaround to enable a custom bootable application [like launchers] stopped working.
Hopefully @SweenWolf can work some magic and get us another workaround.
No longer working on fire TV is 6.2.7.3 any idea Wolf?
I used to use an app that enables another apps accessibility just by opening it. But I can't seem to get it to work for techdoctoruk's firetv settings.
https://github.com/oathzed/BMsettings/blob/master/bmsettings (1).rar
Even though I put this in the main activity :
const-string v3, "enabled_accessibility_services"
const-string v4, "com.wolf.firetvsettings/com.wolf.firetvsettings.HomeService
Is that not where accessibility service is located?
OathYvne said:
No longer working on fire TV is 6.2.7.3 any idea Wolf?
I used to use an app that enables another apps accessibility just by opening it. But I can't seem to get it to work for techdoctoruk's firetv settings.
https://github.com/oathzed/BMsettings/blob/master/bmsettings (1).rar
Even though I put this in the main activity :
const-string v3, "enabled_accessibility_services"
const-string v4, "com.wolf.firetvsettings/com.wolf.firetvsettings.HomeService
Is that not where accessibility service is located?
Click to expand...
Click to collapse
Amazon hasn't released 6.2.7.3 from what I can tell. My Fire TV is currently on 6.2.7.1 according from the Check For Updates page. Has Amazon recently pushed out 6.2.7.3 yet?
Skel40 said:
Amazon hasn't released 6.2.7.3 from what I can tell. My Fire TV is currently on 6.2.7.1 according from the Check For Updates page. Has Amazon recently pushed out 6.2.7.3 yet?
Click to expand...
Click to collapse
I am on 6.2.7.3. might be a slow regional roll out.
Skel40 said:
Amazon hasn't released 6.2.7.3 from what I can tell. My Fire TV is currently on 6.2.7.1 according from the Check For Updates page. Has Amazon recently pushed out 6.2.7.3 yet?
Click to expand...
Click to collapse
I know many have received the update and it broke the apps, but I too am waiting for the update, without looking it myself i cannot say anything.
Amazon pushed out 6.2.7.3 on August 17th for the FireStick4k. It's a slow rollout though. I have it in Canada.
Same here, in Canada. I have 5 Firestick 4K. Two of them have updated to 6.2.7.3 (and broke the Home button of the Wolf launcher) and the other 3 are still on 6.2.7.1 and when I click to check for updates on those 3, it says that they are up to date. So I'm not sure it's a regional thing as opposed to maybe which have been registered first or some other order of operation... I ended up rooting the two at 6.2.7.3 and was able to figure out how to make work in a "round about way". You can check out my post here: https://forum.xda-developers.com/fire-tv/development/ive-rooted-fire-os-6-2-7-3-firestick-4k-t4150143
Skel40 said:
Amazon hasn't released 6.2.7.3 from what I can tell. My Fire TV is currently on 6.2.7.1 according from the Check For Updates page. Has Amazon recently pushed out 6.2.7.3 yet?
Click to expand...
Click to collapse
SweenWolf said:
I know many have received the update and it broke the apps, but I too am waiting for the update, without looking it myself i cannot say anything.
Click to expand...
Click to collapse
Did you get the update yet? XD
OathYvne said:
Did you get the update yet? XD
Click to expand...
Click to collapse
No i haven't.
SweenWolf said:
No i haven't.
Click to expand...
Click to collapse
Dang, hopefully soon you'll be able to debug, or if you need me to help debug anything Im hear.
Any hope on a fix Sween? Looks like accessibility doesn't fully seem to be the issue. I cant get my button mappers to find any key codes.
OathYvne said:
Any hope on a fix Sween? Looks like accessibility doesn't fully seem to be the issue. I cant get my button mappers to find any key codes.
Click to expand...
Click to collapse
you do know that Accessibility service is the services which gives back the "key codes".
And yeah, I cannot bind my service to the system, the only problem, there isn't any other problem.
In short Accessibility Service is doomed for FireOS. Unless it isn't because VoiceView still works.
I had no time to fully understand the issue, i was held up, i will look into it tomorrow, Night.
SweenWolf said:
you do know that Accessibility service is the services which gives back the "key codes".
And yeah, I cannot bind my service to the system, the only problem, there isn't any other problem.
In short Accessibility Service is doomed for FireOS. Unless it isn't because VoiceView still works.
I had no time to fully understand the issue, i was held up, i will look into it tomorrow, Night.
Click to expand...
Click to collapse
I have accessibility enabled on the button mapper though. I'm not getting thrown any error saying i need to enable accessibility. On my other keymapper it also says accessibility "enabled".
Well that sucks. hopefully you can figure something out tomorrow. cheers man.
OathYvne said:
I have accessibility enabled on the button mapper though. I'm not getting thrown any error saying i need to enable accessibility. On my other keymapper it also says accessibility "enabled".
Well that sucks. hopefully you can figure something out tomorrow. cheers man.
Click to expand...
Click to collapse
It doesn't matter what the keymapper is saying, the Methods aren't returning.
Related
Someone on the Amazon forums has reported getting a software update to 6.3.
I have droidwall blocking a lot of stuff in hopes of avoiding the automatic update. We shall see...
Someone reported it on The Verge too. Nothing on Amazon's site about the software update, though.
6.3 was pushed out to my Kindle today as well.
there's now a parental controls on/off toggle option in the 'more' menu, not sure what it might control yet (would be nice if it protects from purchasing apps w/o a password). *update*: parental control restricts wifi use (going online requires the parental control set 4+ character password). however, there's no options to lock the wifi immediately after screen lock, or a certain timeout, etc. appears you need to manually disable the wifi after you use it to re-enable parental control.. also doesn't require password for downloading/purchasing from amazon app store (would've be nice).
Also seeing that the screen can now be dimmed lower (i noticed that first, since i keep the brightness at lowest setting, after the update it stayed at lowest setting, but was noticably dimmer. I also compared it visually w/another kindle i have that's still at 6.2.2 while both are at their lowest brightness setting)
I'm noticing pulse reader has been updated as well (from 2.4.3 to 2.7.6).
6.3_user_4019920 got pushed to my device a short while ago and I lost access to root. There is a little information on the Kindle Fire site from Amazon that says 6.3 is coming and lists some of the new features. I was in the middle of something and all the sudden my fire restarted and I lost my root.
Direct link for anyone who's interested:
http://kindle-fire-updates.s3.amazonaws.com/update-kindle-6.3_D01E_4019920.bin
Still nothing on the Amazon site about it, though. I just figured out the link.
Amazon says that is is coming soon and lists some details on a update. It is on the fire update page under 6.2. Sorry I can not post a link to it.
Thanks for the link - each new version's download has been about a meg bigger than the last one, but this one is an 11 meg jump - wonder what's grown so much!
Please excuse my ignorance on the issue, I haven't used stock rom since I pulled my first Kindle Fire out of the box...But, is there a way to disable automatic updates? Isn't forcing updates on someone pushing the boundaries of what's actually legal?
Isn't that why Microsoft was having so many issues with forcing their "Legit Check" on people?
Sent from my Kindle Fire using xda premium
It is my first update..hope it will not destroy my current settings.
I also got this update today. Now I lost root and Kindle Fire Utility 0.9.3 is not working anymore.
6.3 Update
No more root even here in the other side of atlantic.
Now the solution is wait for the wonderful people of XDA.
Got 6.3 update preloaded into my KF already when I got it. Anyway to download 6.2 on it without root? D;
jdock said:
Someone on the Amazon forums has reported getting a software update to 6.3.
I have droidwall blocking a lot of stuff in hopes of avoiding the automatic update. We shall see...
Click to expand...
Click to collapse
I just installed droidwall to avoid having my root removed. Thanks for the advise
Just a quick thought did any of you that lost your root capability install Voodoo OTA? Because this app supposedly allows you to keep root even after over the air updates. It's also the primary app I use for watch amazon prime. No 6.3 yet for me, but waiting to see what happens. Also does anyone have a link on how to disable the OTA updates in case future updates break recovery options?
Jspex said:
I just installed droidwall to avoid having my root removed. Thanks for the advise
Click to expand...
Click to collapse
Thank you. What application do you black list to stop the OTA?
Here we have it: http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6land_software2?nodeId=200790620
It says coming soon, but the bomb has landed for some users. I still don't have it yet though.
Laquox said:
Just a quick thought did any of you that lost your root capability install Voodoo OTA? Because this app supposedly allows you to keep root even after over the air updates. It's also the primary app I use for watch amazon prime. No 6.3 yet for me, but waiting to see what happens. Also does anyone have a link on how to disable the OTA updates in case future updates break recovery options?
Thank you. What application do you black list to stop the OTA?
Click to expand...
Click to collapse
Yes, I had Voodoo OTA installed. I still have access to google services (gmail, calendar, google play, and more) after the 6.3 update but if I go into a program like Titanium Backup it say there is no root to the system. I can click on restore root in voodoo and there is a pop up that "root su restored" but nothing happens. So there is no root access anymore.
pwissing said:
Yes, I had Voodoo OTA installed. I can click on restore root in voodoo and there is a pop up that "root su restored" but nothing happens. So there is no root access anymore.
Click to expand...
Click to collapse
This displeases me. Well DroidWall it is then. Thanks for the update. I will let it come through once I know there is a custom recovery (root) solution. Until then I blocked most of Amazon's services.
I will be updating with a new exploit within the week. I have had a second one in the waiting for a while, I just need to package it properly.
jcase said:
I will be updating with a new exploit within the week. I have had a second one in the waiting for a while, I just need to package it properly.
Click to expand...
Click to collapse
If I had the money right now I would be buying you a pint! Awesome news!
jcase said:
I will be updating with a new exploit within the week. I have had a second one in the waiting for a while, I just need to package it properly.
Click to expand...
Click to collapse
Just sent you a pm sir.
Sent from my ADR6425LVW using xda premium
The source code for the next software updates for the Fire TV and Fire TV Stick have been posted to Amazon's US source code page. I've already seen word of people receiving these updates, so they've begun rolling out.
If you install the update, let us know if you notice any changes.
Fire TV update version is: 51.1.4.3_user_514020320
Fire TV update download URL is: http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.4.3_user_514020320-signed.bin
Fire TV Stick update version is: 54.1.0.3_user_103020320
Fire TV Stick update download URL is: http://amzdigitaldownloads.edgesuit...ed89a/montoya-ota-54.1.0.3_user_103020320.bin
UPDATE:
After comparing this new update to the previous version on both a Fire TV and Fire TV Stick, I've been unable to find any visible changes. Amazon has also now updated their software page and listed "Bug Fixes" as the only change.
AFTVnews.com said:
The source code for the next software updates for the Fire TV and Fire TV Stick have been posted to Amazon's US source code page. I've already seen word of people receiving these updates, so they've begun rolling out.
If you install the update, let us know if you notice any changes.
Fire TV: 51.1.4.3_user_514020320
Fire TV Stick: 54.1.0.3_user_103020320
Click to expand...
Click to collapse
what are the changes? Im still on 5.1.1.0.1
cpugeeker said:
what are the changes? Im still on 5.1.1.0.1
Click to expand...
Click to collapse
Once I receive the update I'll post a full overview of the changes, as I always do.
Hmm. I wonder if this is the cause of the new problem I've encountered. I have got two AFTV's both of which can't get any Amazon content since this weekend. I get the "Unable to contact our servers" error for the Home, TV, and Movies sections. They both can still get apps and they will download apps that aren't on the boxes. Netflix works fine. And of course Kodi works fine.
If they were supposed to get this update, and Amazon knows they are not updated, could this be the cause of this problem for me? I am in the US so I am not using any VPN to circumvent any geo content restrictions. I'm not even blocking DNS. I wonder if this wouldn't be a problem if I were blocking DNS.
AFTVnews.com said:
The source code for the next software updates for the Fire TV and Fire TV Stick have been posted to Amazon's US source code page. I've already seen word of people receiving these updates, so they've begun rolling out.
If you install the update, let us know if you notice any changes.
Fire TV: 51.1.4.3_user_514020320
Fire TV Stick: 54.1.0.3_user_103020320
Click to expand...
Click to collapse
kraqh3d said:
Hmm. I wonder if this is the cause of the new problem I've encountered. I have got two AFTV's both of which can't get any Amazon content since this weekend. I get the "Unable to contact our servers" error for the Home, TV, and Movies sections. They both can still get apps and they will download apps that aren't on the boxes. Netflix works fine. And of course Kodi works fine.
If they were supposed to get this update, and Amazon knows they are not updated, could this be the cause of this problem for me? I am in the US so I am not using any VPN to circumvent any geo content restrictions. I'm not even blocking DNS. I wonder if this wouldn't be a problem if I were blocking DNS.
Click to expand...
Click to collapse
It's unlikely that your issue is related to this update. If Amazon were truly going to require this update in order to view content, then they wouldn't have flipped the switch yet. The vast majority of Fire TVs have not received this update yet.
I hope this fixes the bluetooth remote and the high cpu usage running kodi
kraqh3d said:
Hmm. I wonder if this is the cause of the new problem I've encountered. I have got two AFTV's both of which can't get any Amazon content since this weekend. I get the "Unable to contact our servers" error for the Home, TV, and Movies sections. They both can still get apps and they will download apps that aren't on the boxes. Netflix works fine. And of course Kodi works fine.
If they were supposed to get this update, and Amazon knows they are not updated, could this be the cause of this problem for me? I am in the US so I am not using any VPN to circumvent any geo content restrictions. I'm not even blocking DNS. I wonder if this wouldn't be a problem if I were blocking DNS.
Click to expand...
Click to collapse
I get the same problem about twice per week. Unplugging and plugging back in solves the problem I don't know if it is the AFTV or XBMC use causing it.
Download URL for the Fire TV 51.1.4.3_user_514020320 update is: http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.4.3_user_514020320-signed.bin
( Attention @rbox )
I don't know about the changes yet because I haven't installed it yet. As usual, it's one of my rooted Fire TVs that tried to update first. Once my sacrificial Fire TV updates, I'll be able to see what has changed. My Fire TV Sticks have also not updated yet.
AFTVnews.com said:
Download URL for the Fire TV 51.1.4.3_user_514020320 update is: http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.4.3_user_514020320-signed.bin
( Attention @rbox )
I don't know about the changes yet because I haven't installed it yet. As usual, it's one of my rooted Fire TVs that tried to update first. Once my sacrificial Fire TV updates, I'll be able to see what has changed. My Fire TV Sticks have also not updated yet.
Click to expand...
Click to collapse
I'm not at home, but my wife is reporting that the Fire TV Stick (unrooted) won't work because of internet problems. The Internet is fine. I still was blocking the update servers through OpenDNS. I removed the block and I'm waiting for openDNS to allow the connections. I think Amazon is forcing the update on the stick. My other two rooted Fire TVs are off, so I'll have to test when I get home. I disabled the update service on those.
Got the update on the fire tv i don't see any difference what so ever
gonna keep digging
radiohead7778580 said:
Got the update on the fire tv i don't see any difference what so ever
gonna keep digging
Click to expand...
Click to collapse
Would you happen to have a Windows 8.1 machine to check if Miracast works?
Resnoid said:
Would you happen to have a Windows 8.1 machine to check if Miracast works?
Click to expand...
Click to collapse
i have a macbook with bootcamp running windows 8.1 i can check it out!!
I really wish they would fix this issue that i posted on kodi forums its something with the amazon firmware and kodi on both fire tv and stick take a look and let me know what you think
http://forum.kodi.tv/showthread.php?tid=216525
radiohead7778580 said:
I hope this fixes the bluetooth remote and the high cpu usage running kodi
Click to expand...
Click to collapse
I haven't noticed high CPU usage running Kodi on my AFTV. It runs super smooth.
I use this to launch my Kodi: https://play.google.com/store/apps/details?id=se.blunden.xbmclauncher
Neo3D said:
I haven't noticed high CPU usage running Kodi on my AFTV. It runs super smooth.
I use this to launch my Kodi: https://play.google.com/store/apps/details?id=se.blunden.xbmclauncher
Click to expand...
Click to collapse
Its only happens when you launch it from the settings, manage all user installed apps its seems like its no shutting down some services
radiohead7778580 said:
Its only happens when you launch it from the settings, manage all user installed apps its seems like its no shutting down some services
Click to expand...
Click to collapse
Give this a try. It frees things up well for me on all my android devices including the FTV.
https://play.google.com/store/apps/details?id=com.greatbytes.fastreboot&hl=en
xm41907 said:
Give this a try. It frees things up well for me on all my android devices including the FTV.
https://play.google.com/store/apps/details?id=com.greatbytes.fastreboot&hl=en
Click to expand...
Click to collapse
I will try it for sure... but you guys give int a try loading from the settings menu then click on the cpu usage then launch it from a 3rd party launcher or llama classic tv or ikono tv icon you will see there is something wrong
AFTVnews.com said:
It's unlikely that your issue is related to this update. If Amazon were truly going to require this update in order to view content, then they wouldn't have flipped the switch yet. The vast majority of Fire TVs have not received this update yet.
Click to expand...
Click to collapse
mychaelp said:
I get the same problem about twice per week. Unplugging and plugging back in solves the problem I don't know if it is the AFTV or XBMC use causing it.
Click to expand...
Click to collapse
Thanks. It was unrelated. It seems to have resolved itself without any reboot sometime between my post and this weekend when I went to look at it again. My AFTV's are always running Kodi so I really have no idea how frequently this might occur. I'll keep an eye on it and see if this happens regularly.
also, you dont have to power cycle to reboot. hold the play/pause and select button for a few seconds to reboot.
psycon said:
also, you dont have to power cycle to reboot. hold the play/pause and select button for a few seconds to reboot.
Click to expand...
Click to collapse
Never knew that. Nice tip!
I've received both updates now (Fire TV & Fire TV Stick) and had a chance to compare them to the previous version. I haven't been able to find any visible changes. Also, Amazon has updated their software pages and officially listed these updates as "Bug Fixes".
OnBootKodi
OnBootKodi starts Kodi when you start up your device! Also, has the option to start Kodi after a screen timeout period [user set] (If you turn on/off the timeout service, one reboot is required for changes to take effect)
Requirements
-Kodi installed
Changelog
Added timeout support
Source:
Bitbucket
Donations
Donations are not required, but if you like my work they certainly are appreciated!
Donate!
Download
GDrive
XDA:DevDB Information
OnBootKodi, Device Specific App for the Amazon Fire TV
Contributors
Xtraordinair, Xtraordinair
Source Code: https://bitbucket.org/Xtraordinair/onbootkodi/overview
Version Information
Status: Beta
Created 2017-05-18
Last Updated 2017-05-18
Thanks. Haven't tried this yet. What happens if I press the Home button on the Fire remote? Do I go back to the Amazon or Kodi screen?
fido14dido said:
Thanks. Haven't tried this yet. What happens if I press the Home button on the Fire remote? Do I go back to the Amazon or Kodi screen?
Click to expand...
Click to collapse
Goes to the Amazon home screen, so far only supports loading Kodi on boot and after screen timeout.
I have tested your App. Not working on my 5.2.4.1 Fire TV. But keep up the goodwork though.
Working with issue
Xtraordinair said:
Goes to the Amazon home screen, so far only supports loading Kodi on boot and after screen timeout.
Click to expand...
Click to collapse
Thank you working on my first gen ftv stick with new menu update. However could not interact with it via either the remote or the amazon iOS remote app. Had to uninstall and reboot to stop it booting kodi. Thanx BB
justjones said:
Thank you working on my first gen ftv stick with new menu update. However could not interact with it via either the remote or the amazon iOS remote app. Had to uninstall and reboot to stop it booting kodi. Thanx BB
Click to expand...
Click to collapse
Fire os 5.2.4.1 Home ver. 5.7.3-17
Worked for me on both a Fire TV 1 and Fire TV 2. Both on latest 5.2.4.1 version. But I could not get the timeout option to work. Not sure about the units used, so I tried 1, 1000, and 1000000 but it always just launched immediately after boot each time.
Looks like the Time out function is to start kodi after the fire tv has gone to sleep for X amount of time.
AFTVnews.com said:
Worked for me on both a Fire TV 1 and Fire TV 2. Both on latest 5.2.4.1 version. But I could not get the timeout option to work. Not sure about the units used, so I tried 1, 1000, and 1000000 but it always just launched immediately after boot each time.
Click to expand...
Click to collapse
Doesn't work for SPMC
OnBootKodi has been blacklisted by Amazon. This means you can only use it if your device is rooted and you've disabled the blacklist.
You can modify Kodi to run as a launcher. Then use Launcher Hijack v3 to make it act as the default launcher. It works WITHOUT root.
nyln said:
You can modify Kodi to run as a launcher. Then use Launcher Hijack v3 to make it act as the default launcher. It works WITHOUT root.
Click to expand...
Click to collapse
How do you turn Kodi into a launcher? And once you have, would pressing the home button on the FireTV remote open Kodi or will it continue to load the Amazon dashboard?
Patrick_445 said:
How do you turn Kodi into a launcher? And once you have, would pressing the home button on the FireTV remote open Kodi or will it continue to load the Amazon dashboard?
Click to expand...
Click to collapse
I am not 100% sure, but I think you can edit the manifest.xml file and add a launcher behavior. Not my specialty. If not you could edit Launcher Hijacks open source code to work with kodi, In the meantime just press home when it turns on and it will load your launcher of choice .
Patrick_445 said:
How do you turn Kodi into a launcher? And once you have, would pressing the home button on the FireTV remote open Kodi or will it continue to load the Amazon dashboard?
Click to expand...
Click to collapse
nyln said:
I am not 100% sure, but I think you can edit the manifest.xml file and add a launcher behavior. Not my specialty. If not you could edit Launcher Hijacks open source code to work with kodi, In the meantime just press home when it turns on and it will load your launcher of choice .
Click to expand...
Click to collapse
Would recommend SPMC with Launcher build in. Might be best option:
https://github.com/koying/SPMC/releases/tag/16.7.1-spmc
Haven't had time to test this option. Post your experience.
Unfortunately OnBootKodi is being blacklisted via Amazon.
I tried to hide Amazon blacklist Service, but it didnt help
pm hide com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService
OnBootKodi is being shown as disabled package after a FireTV reboot which cant be re-enabled due to non-root privileges.
edit1: also deinstalling tv settgins wont help
pm uninstall -k --user 0 com.amazon.tv.settings
TV33 said:
Unfortunately OnBootKodi is being blacklisted via Amazon.
I tried to hide Amazon blacklist Service, but it didnt help
pm hide com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService
OnBootKodi is being shown as disabled package after a FireTV reboot which cant be re-enabled due to non-root privileges.
edit1: also deinstalling tv settgins wont help
pm uninstall -k --user 0 com.amazon.tv.settings
Click to expand...
Click to collapse
I mentioned this in another thread some time ago but it never gained any traction. It appears Amazon is currently blocking these apps by package name alone. Why don't any of these developers just change the package name to something already in use on the app store that way Amazon can't block it without also blocking the real app?
As of November 16th 2017, Amazon tablets had a new firmware that improves performance, notifications on status bar, and much more! But, the bad thing is, is that the install button to get apk files that aren't from the appstore is greyed out and cannot be installed! But there is a solution and thanks to a YouTube video I found by "liliputing", I am able to get unknown apk's installed successfully. Here are three ways to do it:
First method is to put the device into sleep mode and unlock it, go to the apk you wanted to download, and BOOM!
Second way, switch app and switch back to the app you're using to get an apk installed.
Finally, go to settings, go to security, and turn unknown sources off and back on.
If you don't understand what I am saying, watch this video I made:
https://youtu.be/HLXjpRERIKs
Hope you all get your apk!
ChompDroid126 said:
As of November 16th 2017, Amazon tablets had a new firmware that improves performance, notifications on status bar, and much more! But, the bad thing is, is that the install button to get apk files that aren't from the appstore is greyed out and cannot be installed! But there is a solution and thanks to a YouTube video I found by "liliputing", I am able to get unknown apk's installed successfully. Here are three ways to do it:
First method is to put the device into sleep mode and unlock it, go to the apk you wanted to download, and BOOM!
Second way, switch app and switch back to the app you're using to get an apk installed.
Finally, go to settings, go to security, and turn unknown sources off and back on.
If you don't understand what I am saying, watch this video I made:
Hope you all get your apk!
Click to expand...
Click to collapse
While these techniques were previously surfaced they are sure to receive more attention due to the appropriately titled thread. Thanks!
Thank you, I hope you managed to get the apk's you wanted!
It seems this APK sideloading bug is a AOSP bug specific to 5.1 Lollipop caused by the October security patches - https://issuetracker.google.com/issues/67884224
Hopefully it'll get fixed in a future update at some point.
Fire Kids Edition
Is it possible to do this in the freetime child Profile? It does Not work there because Apps are stopped Ehen Lockung the Tablet and the switch Button does Not exist within freetime. Please help my Boy needs YoutubeKids in his profile.
oppa9999 said:
Is it possible to do this in the freetime child Profile? It does Not work there because Apps are stopped Ehen Lockung the Tablet and the switch Button does Not exist within freetime. Please help my Boy needs YoutubeKids in his profile.
Click to expand...
Click to collapse
Track down a Bluetooth or USB OTG keyboard. Once attached you should be able to navigate to the install button via tab key. Once highlighted it should activate via enter/return key.
Also make sure Blue Shade is disabled in child profile as screen filters can disrupt installation of 3rd party apps (Android security feature).
ChompDroid126 said:
As of November 16th 2017, Amazon tablets had a new firmware that improves performance, notifications on status bar, and much more! But, the bad thing is, is that the install button to get apk files that aren't from the appstore is greyed out and cannot be installed! But there is a solution and thanks to a YouTube video I found by "liliputing", I am able to get unknown apk's installed successfully. Here are three ways to do it:
First method is to put the device into sleep mode and unlock it, go to the apk you wanted to download, and BOOM!
Second way, switch app and switch back to the app you're using to get an apk installed.
Finally, go to settings, go to security, and turn unknown sources off and back on.
If you don't understand what I am saying, watch this video I made:
https://youtu.be/HLXjpRERIKs
Hope you all get your apk!
Click to expand...
Click to collapse
Thanks, this worked for me. Using MI TV Box 3S (16AB). It also enabled just after pressing the voice command button and latest back button. No idea why it's happening, but found a solution.
I woke up today to find my tablet on the table with the screen on and a weird new lockscreen with some spam about hints on how to use Alexa. I guess my tablet had updated a few minutes before I got up and so the screen was on.
Because my tablet was previously rooted and I disabled the stock launcher and was using Nova, I was unable to get out of the lock screen. Pressing home did nothing nor did swiping from any direction. Funny enough too, the lockscreen was saying how to use Alexa but on my device purchased in Japan, Alexa i completely missing even from a stock install which is just insult to injury.
Anyway, I am looking for a way to remedy this hopefully without a reinstall. My initial thought was to re-root and re-disable the stock launcher giving Nova control again, if possible. However, I am unsure if the usual rooting method works on this version. I can't even re-enable the stock launcher without root (I think) so I guess if I lost root I will have to do a reinstall to get back to stock?
Does yours have your home buttons/top bar? Mine disappeared with the update and now the only way to get back to my home screen is to reboot my fire entirely!
taiyoko said:
Does yours have your home buttons/top bar?
Click to expand...
Click to collapse
Yes. I was still able to use the device with those functions but it's incredibly inconvenient. Would a reboot help with anything?
I was looking at another thread in the help section, and apparently my nav/notification bars being missing is some sort of compatibility problem with 5.6.2.0 and Nova Launcher.
uninstall nova via adb
I think I figured it out but this won't work for everyone. After opening settings using the pull down notification menu, this reenabled the recent apps which allowed me to open Nova launcher. I rerooted using the offline method here https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-offline-rooting-t3734860 which thankfully still works. After that I was able to use Titanium backup to freeze the new "Launcher 1.0........".
Everything is now running like before the update.
yoflo said:
I think I figured it out but this won't work for everyone. After opening settings using the pull down notification menu, this reenabled the recent apps which allowed me to open Nova launcher. I rerooted using the offline method here https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-offline-rooting-t3734860 which thankfully still works. After that I was able to use Titanium backup to freeze the new "Launcher 1.0........".
Everything is now running like before the update.
Click to expand...
Click to collapse
Not able to disable the stock launcher with the old method, pm disable, once you have root?
EDIT: Was finally able to try some stuff on my tablet. I was able to get root due to your method you linked, which BIG thank you by the way as that method is way less fishy than Kingroot nonsense, and was able to disable the launcher with the "pm disable com.amazon.paladin" command. Seems like they gave their new launcher the name Paladin.
And I'm back to Nova launcher! Thanks so much.
REMOVED
I'm just hoping the new version doesn't make it even harder to root the 8. It's already seeming hopeless. I had updates blocked at the router level. It updated at work.
Sent from my SAMSUNG-SM-G935A using Tapatalk
stew1411 said:
I'm just hoping the new version doesn't make it even harder to root the 8. It's already seeming hopeless. I had updates blocked at the router level. It updated at work.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
DeviceSoftwareOTA.apk will update the tablet even if blocked at that level. Amazon uses several IPs which change often. You have to disable that apk or completely removed it. You can try NetGuard firewall. You have to buy the features, but it allows you to block individual IPs. On my HD 8, before I posted a guide on how to disable system apps on 5.4.0.0, at one point I had a dozen or more IPs blocked through NetGuard. It will take time to tinker with all it's features, but I don't regret buying them.
Ugh, me too!
No notification bar.
I'm unclear as to what I can do to remedy this.
I have Nova Launcher running and I am a novice.
Can someone please tell me what to do?
---------- Post added at 03:48 PM ---------- Previous post was at 03:07 PM ----------
OK, update...
So, I restarted a couple of times, and like the third time I restarted, another update applied and a video about "Show Mode" displayed. I sped to the end of it.
I also (previously) turned off "Show Mode" on the lockscreen.
Then, I backed-up my Nova and shared it via Gmail.
Suddenly, the navigation buttons on the bottom appeared and the notification bar showed.
Does that mean it got fixed (somehow) with that orange-screened update that showed upon restarting?
Also, how can I halt any further updates?
When I received the 5.6.2.0 update, I had the same problem of no pull-down menu and no navigation buttons. I had previously installed Google Play, Nova and LauncherHijack. I did not have root. I called Amazon tech support and the guy connected with their MayDay remote assistance program, so I'm sure he could see I was running Google and Nova. We went thru several reboots and checked settings, but he was still stumped. Finally we did a factory reset and reapplied the 5.6.2.0. update and it started working. I have since reinstall Google Play, Nova and LauncherHijack and everything is running fine. My suspicion is that LauncherHijack is blocking the complete install. I read another post that exactly described this issue. In that case the user uninstalled Nova and LauncherHijack and powered off and back on. The installation then continued and when completed, the Show Mode video ran. I contacted the author of LauncherHijack and he said he would check it when he got the update.
Bottom line--if your tablet updates to 5.6.2.0 but the Show Mode video does not appear, the installation has failed/hung before it completed (even if it says the update completed). If you have LauncherHijack installed, try uninstalling it, cycle power and see if that fixes the problem.
I know this won't work for everyone but I was lucky enough to manage to access the Play Store when I noticed this happened on my HD10 and saw that the last app updated was amazon alexa under "Recently Updated" in the "My Apps and Games" section. I hit uninstall and rebooted. Show mode setup then came up normally after reboot and after the setup process for that everything worked normally again. Re-updated alexa and everything is working perfectly now. This worked for me so it's worth a shot but I might have just gotten lucky.
I got the orange screen, rebooted, still had it, tried several times locking and unlocking and kinda fiddling around, from the lock screen pulled the little "tag" icon (swipe for offers I think?)
At some point I was able to get into my email client (type mail) but only had a back button, no home or task buttons. Restarted again, same kind of fiddling around, and somehow it ended up playing the video. Skipped to the end, disabled Alexa when prompted and ended up on my normal home screen with all three nav buttons. Everything seems to be back to normal now. FYI, I'm running Nova, launcher hijack, all the standard Google apps including play store, and I didn't have to uninstall anything. I wish I knew the exact sequence that got it to work, but I'm really not sure... Maybe it wasn't even anything I did? Maybe it was just taking time downloading that obnoxious video?
It is nerve-wracking when something like this comes up knowing that they could push an update that messes everything up and there's basically nothing we can do about it.
I really really hope we can get root on this device
NFSP G35 said:
I really really hope we can get root on this device
Click to expand...
Click to collapse
You can just re-root it.
autobulb said:
You can just re-root it.
Click to expand...
Click to collapse
I thought there wasn't any root on the HD 8? Did I miss something???
NFSP G35 said:
I thought there wasn't any root on the HD 8? Did I miss something???
Click to expand...
Click to collapse
Ah sorry, my device is the HD10. You're right, HD8 doesn't have root.
autobulb said:
Ah sorry, my device is the HD10. You're right, HD8 doesn't have root.
Click to expand...
Click to collapse
Why are these devices lumped together when they are clearly very different?
n3wt said:
Why are these devices lumped together when they are clearly very different?
Click to expand...
Click to collapse
That's just the way the XDA forum was set up unfortunately. Sometimes similar devices are put together in the same forum and the users are expected to be clear about which device they are talking about.
A Solution - At Least For Me!
autobulb said:
I woke up today to find my tablet on the table with the screen on and a weird new lockscreen with some spam about hints on how to use Alexa. I guess my tablet had updated a few minutes before I got up and so the screen was on.
Because my tablet was previously rooted and I disabled the stock launcher and was using Nova, I was unable to get out of the lock screen. Pressing home did nothing nor did swiping from any direction. Funny enough too, the lockscreen was saying how to use Alexa but on my device purchased in Japan, Alexa i completely missing even from a stock install which is just insult to injury.
Anyway, I am looking for a way to remedy this hopefully without a reinstall. My initial thought was to re-root and re-disable the stock launcher giving Nova control again, if possible. However, I am unsure if the usual rooting method works on this version. I can't even re-enable the stock launcher without root (I think) so I guess if I lost root I will have to do a reinstall to get back to stock?
Click to expand...
Click to collapse
I found a simple way around it - if rooted.
I had to re-root, but that wasn't too difficult using existing resources.
Through some trial and error I figured out "com.amazon.paladin" is linked to the Alexa/Show Launcher (that's what I'm calling it at this point).
You can disable it with the following via ADB. It should revert back to your default launcher.
I also had Nova Launcher installed, so I disabled the stock launcher (the second pm line below).
Code:
adb shell
$ su
# pm disable com.amazon.paladin
# pm disable com.amazon.firelauncher