yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Android Development] blaacksheep:
What I fear happened is that when you reset your tablet, OTA updates was activated once again, and being unable to access the tablet with Toolbox, your tablet updated itself with the latest update. This wouldn't happen if you never turned on wifi, but it seems you have because of the "sync in progress" notification.

You'll probably need to revoke all ADB permissions on your tablet, unplug it from your computer, re-attach it, and run Toolbox again. Then watch your tablet for the request to authorize this device (the computer), check the "always trust this device", and then authorize it.

Welcome to the new world of v7.3.2.4. :confused: You are now unable to shut off OTA updates, it takes a little doing to get rid of lockscreen ads, and your launcher replacement now has a few bugs in it (the home button becomes invisible on light screens).

Let us know how you do getting Toolbox to recognize your tablet, and if you got the update that I fear you now have.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I don't know what dependencies Skype has, but it may be that one of them was disabled when you debloated your tablet (especially if you used one of the presets). I've never used the presets myself, so I can't say for sure. Take a look through Manage Amazon Apps > Manual tab > Simple (Recommended) > Restore Apps tab. Check for anything that might be needed for Skype to communicate or authorize. (I know. Who knows, right?) The other thing that comes to mind is that many apps don't notify properly on Fire tablets because there some things are not in FireOS that are in regular Android. Because Skype is in Amazon's appstore, I would think that at least that version would work properly in an unmodified tablet, which is why I suspect something was disabled that is needed. If all else fails, you could re-enable all the Amazon apps to see if it works, and if so, disable the ones you don't need manually until it stops working. Then you could tell us which app removal caused the failure so we can help others.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
I've had the update for a while. But it never stopped me from using Toolbox.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
OK. Well, try revoking ADB authorizations. You may need to open a command prompt on your computer after you close Toolbox and type in

adb kill-server

That will shut down ADB completely. Make sure your tablet is disconnected from your computer. Then under Developer options on your tablet, revoke USB debugging authorizations, and turn off USB debugging. Now turn USB debugging back on once again and reconnect your tablet to the computer. Make sure it's awake (screen on) and launch Toolbox again. You should now see a request for authorization on your tablet. Tick the box at the bottom that says "Always trust this device" and accept the request to connect.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
Didn't work. It's ok. I only really want to get rid of the bloatware. I'll just have to live with it. What sucks is that I can't use my SD Card for internal storage like I once was able to.

When I try to format as internal storage, the whole tablet freezes at 20%
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I just looked at my tablet and the option to format as internal storage is greyed out while connected to computer. Try disconnecting from the computer and opening Storage under settings. Maybe it will now be available.

Another thing I thought of for connecting to ADB is that maybe the connection type needs to be changed. Plug in your tablet then swipe down and tap the "System - Connected as xxxxx". Change it to PTP (camera). Maybe then you can authorize the ADB connection for Toolbox.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
I think one of the "features" of FireOS is to turn on "Battery Background Restrictions" by default to conserve battery life. One of the consequences is that "push" notifications are not received unless a specific app is active in the foreground. This is the situation with Skype where call notifications are active when Skype is open, but inactive when Skype is closed.

"Stock" Android and most other mfg custom ROM have a "Background Restrictions" settings in "Battery" to select which apps can run in the background ... FireOS doesn't (of course).

Some apps have a "persistent notification" setting (like the weather apps) but I don't think Skype has.

Also I think there is also the situation of Amazon Messaging Services (which pushes Amazon notifications) not "co-operating" with Google Play Services in pushing notifications for apps like Gmail.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
I can get to format as internal storage. But the whole Kindle freezes after 20%
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Amazon has an option to turn off background restrictions, too. It's just not under battery. It's under Apps and notifications > Skype > Battery. Turn off battery optimization. :)
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I remember having to reset my tablet a couple of times to get my 512 GB SD card to format as internal storage. It finally succeeded and then I ran Toolbox. I don't remember if my card was formatted on Windows (using Rufus) first. That may make a difference too.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
Should I keep trying until (hopefully) it works?
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
I was able to sideload Google services and Play. I grouped all the Amazon apps in a folder so it doesn't bother me as much. Everything is good. I can live without the toolbox. But not having more internal memory still sucks. I wish I never factory reset it in the first place. Oh well.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
You're right! Even though battery optimization in FireOS on turned on by default, it can be tuned off an an app-by-app basis, but it's buried pretty deep in the settings ... learning something new about FireOS every day!

To clarify (may differ for FireOS variant):

Open Settings > Apps & Notification > See all apps > Skype > Battery > Battery Optimization > select "All apps" from drop-down menu > Skype > select "Don't optimize" > "Done"

This should keep Skype in the foreground and keep call notification active. Probably works for all other apps requiring active app notification on Amazon tablets ?

ADDENDUM : per Amazon dev support, Goggle "push" notifications are not supported by Fire devices. Firebase Cloud Messaging (Google "push" services) is tied to Google Play Services which explains why Google-branded apps (Gmail et al) cannot automatically display persistent end-user app notifications. Devs must use Amazon Device Messaging to be Fire device compliant.

Part of the ongoing FireOS/GPS conundrum.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Had similar situations with microSD cards on other Android devices.

1. Could be "dirty" card contacts. Try cleaning with contact cleaner/deoxidizer

2. Could be "dirty" Fire tablet contacts.

3. Try reformatting SDcard on PC as FAT32. May be more "robust" than Android in determining condition of SDcard and whether it can be formatted properly. Can reformat as internal storage on Fire tablet later.

3. Potentially a "weak" or "bad" memory sector on SD card. May be able to "repiar"or block bad sector using a memory analyszer on PC. Probably best to replace SDcard to avoid future lost data.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
The tablet reads the SD card, so it isn't the connections. I can also format it no problem. Just not as internal storage on the tablet. I formatted it for portable on the tablet, and formatted it on my laptop. It worked, but it can only be used as portable storage.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
You could. It may eventually work. In my case it was a brand new name brand SD card (Samsung or Sandisk, I don't remember), and it was verified as good with FakeFlashTest.exe. It does make a difference which brand cards you get. You want a fast class 10 card, preferably with at least A1, and U3 ratings for use as internal storage. Otherwise your whole system is slowed down by a slow card. Fire tablets are partial to certain brands of cards too. Stick with the slightly more expensive name brands and they'll be more likely to work.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
I have a class 10 U3 Kindle SanDisk SD card. It's literally made for Kindle. It's a grey SanDisk card. It worked as internal storage perfectly fine before I factory reset my device. I got it in March and had no problem until now.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I remember having some difficulties doing this with my tablet, too. I've since disabled the lockscreen altogether so it doesn't matter to me anymore.

The option is there to set separate wallpapers for home screen and lockscreen. It's under Lockscreen Management > Change Lockscreen Wallpaper. There you have the option to set wallpapers for both your lockscreen and home screen. Last time I tried it, it did indeed work.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
It's up to you if you want to brute force it to work by resetting. It may or may not work.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
At this point, I am just going to use it as portable storage. Easier, less stressful. I added the apps I use onto the 32GB internal drive and I still have about 10 or 11 GB left.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
@blaacksheep Thank you for the help. I hope there's another update of Fire Toolbox that supports my device. *Fingers crossed*
[Fire HD 8 and HD 10 Android Development] blaacksheep:
It's not a matter of Toolbox supporting your device - it already does. It's a matter of getting ADB authorized on your tablet so that Toolbox will see it.

ADB recognizes your device as unauthorized, so it sees it. Now you have to get your tablet to communicate with ADB enough to prompt you for authorization. Once that is done, you'll be good. Sometimes you need to revoke all authorizations, turn off USB debugging, reboot the tablet and computer, turn on USB debugging again, and run Toolbox again just to "start from scratch". My tablet on the later firmware (I have 2) requires the tablet to be in PTP (camera) mode in order for ADB to work. My earlier tablet doesn't care what mode it's in. You'll just need to play around with it and make sure your tablet stays awake when you try to connect so you'll see the authorization prompt on the tablet.
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
I'll try that! Thanks!
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
HOLY S**T!!! IT WORKED!!! Thank you @blaacksheep !!!
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Persistence is a powerful tool!!(y)
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
For some reason I can't get rid of Washington Post
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Firmware update woes! They made about 6 things I used to turn off into "protected apps" that can't be disabled any longer after v7.3.2.1 :cautious:
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
OMG I GOT IT TO USE MY SD CARD AS INTERNAL STORAGE!!!
[Fire HD 8 and HD 10 Android Development] blizzardblaise:
Is there any way to make the lockscreen wallpaper and home screen wallpapers different? I was never able to do that with my Fire 10. It worked on my Fire 7 though.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Persistence once again!! Woot! :cool:
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I don't know. I had difficulties trying to use that tool, but Datastream33 either walked me through it or modified Toolbox and then it worked. I can't remember if it uses Automate, but it might. I've since disabled the lockscreen altogether on both my HD10 and HD8 so I haven't even tried using it in over 6 months. (It was my 10 that I had it working on.)
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Jeff Bezos owns the Washington Post, of course
[Fire HD 8 and HD 10 Android Development] Aymon_star:
Hi everyone have you managed a workaround for the playstore and if so please tell me 😁 fire tablet 7 12gen OS 8.3
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Not yet from what I've read. FireOS 8 still appears to be a problem with the Play Store. There's always Aurora.

Here's an article about Aurora Store on XDA.
[Fire HD 8 and HD 10 Android Development] drovan:
I only installed 3 out of 4 of the google apk's in order to sideload chrome and get gboard voice typing to work (which both perform great), and then erased those google services. Then I merely sideloaded all the apps I need. This is a trick I've been using since 2018 to get google apps working on fire tablets without having google services running in the background hogging ram. Based on what I've heard, the issue arises when you have the services constantly running in the background. I'd recommend the Lenovo tab M7 gen3 if you want a nice 7" android tablet, I have one as well and it's great.

I'm planning to explore this issue more thoroughly soon. I'm convinced getting google play to function properly on the new 7 is just a matter of time. Stay positive lol.
[Fire HD 8 and HD 10 Android Development] rockinmax:
Hi guys. My Fire HD10 (11th) 7.3.2.4 doesn't seem to be recognized by Fire Toolbox. I turned on Developer Options. It worked before but doesn't seem to work now.
[Fire HD 8 and HD 10 Android Development] Gone2Maui:
Has anyone got Aurora to install in the Fire 7 2022? If so, how?
[Fire HD 8 and HD 10 Android Development] Gone2Maui:
Can you give a little more detail on how you got this to work?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I don't have FireOS 8. My most recent tablet is FireOS 7. An HD8 (2020), running firmware v7.3.2.3. What problem does the installer give you? Where did you download the apk file from? The second link I posted has an article with a direct link to the most current stable release. It installs fine on FireOS 7. Please give details about the problem.

Oh, and welcome to XDA! :)
[Fire HD 8 and HD 10 Android Development] manuelruso:
pagsrfectpo
[Fire HD 8 and HD 10 Android Development] hmoobguy:
Failing to download google services on Fire HD 8 2020.

I did a factory reset and reattmpted to install Fire Toolbox but this time it's failing. I don't recall the last version I had but it's been at least half a year.

Anyways, there's a problem with it not being able to perform Google Services install. Is that still an oustanding issue?

I'm running 7.3.1.8, I have never updated this version since the last time I did the Fire Toolbox. And it's under the 73.2.2.

"If your tablet is running FireOS 7.3.2.2 or above please note that some functions of the Toolbox may not work due to new restrictions in the new firmware. The following tools either do not work or have limited functionality:"

There are other issues, sometimes it doesn't recnogize the tablet.

Any help would be appreciated.
[Fire HD 8 and HD 10 Android Development] ChrisMili:
I've tried using the Fire Toolbox to install Google Play Services on Fire 7 12th generation I bought the other day, and when I try to open the google play store app it just crashes. I don't get any information it just kicks me back to the home screen. I've tried factory resetting a couple of times but still got the same result. I don't know if I'm doing something wrong or if the tablet came with an issue but I would appreciate it if someone could help me and maybe tell me what the problem might be.
[Fire HD 8 and HD 10 Android Development] hmoobguy:
It it just me or is build V29.0 worse than V28.0 it won't even connect now.

I'm not running 7.3.2.2 (I'm running 7.3.1.8,) click no and it says conneciton lost.

Also, I'm getting Unhancled Exception. failed to dispose object.

I've restarted my computer (windows 11 x64), factory reset the device, booted and did the entire "SKIP NOW" with developer USB debugging on.

EDIT: I just reinstalled v29 on my laptop Windows 10. It worked. Perhaps this is not compatible with Win11? Not sure but Win 10 is working so far.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Greetings!

It appears the Toolbox is failing to read the Android version, and as a result, the Toolbox can't set the appropriate download links.

Could you please run the following command in an ADB Shell and provide the output:

getprop ro.build.version.release

In the meantime, I'm going to take a look at the code and see if something's wrong there.

On a sidenote, is W11 running on your PC by chance?
[Fire HD 8 and HD 10 Android Development] Datastream33:
Greetings!

I believe 12th gen has been having some problems with Play Services. If I remember right (could be entirely wrong here) it had something to do with a component of the Play Services already being baked into FireOS somewhere causing play services to fail to install. That happens with the Android 11 variant, so the Toolbox is installing the Android 10 versions. Apparently, Android 10's versions don't play well with the tablets either. I'd recommend installing Aurora Store right now in the meantime. So sorry, my friend :(
[Fire HD 8 and HD 10 Android Development] redkaku:
Does this mean custom launcher and lockscreen still works since it is not mentioned?
[Fire HD 8 and HD 10 Android Development] Datastream33:
Greetings and great question my friend!

Lockscreen ads can once again be removed on tablets running 7.3.2.2+ (as of last nights update). As for Custom Launchers, they should still work via the Custom Navbar Key method.

;)
[Fire HD 8 and HD 10 Android Development] Datastream33:
The download links in the OP have been updated to point to a new build of V29.0. Try uninstalling the V29.0 you already have and install the new one from the OP. Let me know if the still issue persists with the new build. Thank you! :D
[Fire HD 8 and HD 10 Android Development] redkaku:
thank you for taking the time to reply. I am gonna try them later
[Fire HD 8 and HD 10 Android Development] ChrisMili:
It's fine. Although I would like to know if 12th gen Google Play Services support is coming in the future.
[Fire HD 8 and HD 10 Android Development] Willrodg:
I cannot change the launcher. Everything else works (Google, Bloatware, etc)

Someone mentioned the navmenu method but I cannot find it.

Help?
[Fire HD 8 and HD 10 Android Development] codingisveryinportant@123:
hi,

can anyone help me for uninstalling(not hiding) the in-built apps in amazon fire tab 10
[Fire HD 8 and HD 10 Android Development] blaacksheep:
It's under Custom Launcher in Tooolbox. Select your launcher of choice to install (Nova works well and is a popular choice). Under Launcher Activation Method, Custom Navbar Key should be pre-selected for firmware versions above v7.3.2.1.

That is the method to which you were referring. Only 2 methods are possible on the newer firmware. The other (Re-route Homekey), will only function for the current session and must be done again every time you reboot.

Follow the instructions from Toolbox carefully to make sure that Automate is installed, it gets turned on at each boot, and it is granted all the permissions that it needs.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Hi and welcome to XDA!

Since none of us has Amazon's encryption key to digitally sign any apps, and a method to acquire root privileges has not been found, none of the built-in Amazon apps can be removed. We can only disable most of them, but they are trying to prevent even that by making them "protected" system apps. It would have been posted already if we could remove them altogether. Just be sure to disable OTA Updates if you have FireOS v7.3.2.1 or earlier. You'll want to keep that firmware because later firmware is much more restrictive.
[Fire HD 8 and HD 10 Android Development] ooonimrodooo:
Hi There. Thanks for this tool. It has been a huge help. However, with the automate app for using custom launcher. It does not seem to work while watching a video in any media app. I apologize if this has been address. I did search, but I did not find anything. Is there a permission that needs to be granted or setting I need to enable? Or is this just a limitation I have to deal with?
[Fire HD 8 and HD 10 Android Development] Willrodg:
My fire wasn't updating. It works great now! Thanks!!!!!!
[Fire HD 8 and HD 10 Android Development] ParadoxGBB:
Hello,

I'm a lucky one with a 7 inch 8th generation frozen on 7.3.1.9. I love this tool, things work great. But there's a few apps that really need the upgrade.

So I just have a few questions:

1) For a smooth experience do you recommend upgrading and configuring and running the tool prior to enabling OTA updates and upgrading? Or do you recommend removing things like the play store first?

2) Can anyone comment how performance is on older tablets with FireOS8?

3) Or should I hold off upgrading? Say, until there's a way to disable OTA again? I'm hoping I can continue to avoid some of the problems folks experienced here when OS8 dropped.

4) I take it from this thread the issues around getting the Play Store to install correctly on OS8 have been resolved?

Thanks in advance!
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Pl

Short answer : DO NOT enable OTA.

Sorry tlo be blunt, but enabling OTA will only update your Fire tablet to the current Fire OS 7 f/w which may "ruin" your existing FTB setup.

From previous history, Amazon will NOT be upgrading exiting Fire tablets with FireOS 7 to FireOS 8 ... which is probably a good thing.

Major incompatibility/instability of FireOS 8 on 12th gen Fire tablets with Google Play infrastructure persists and may be getting worse ... latest FireOS 8 update even crashes Google Play Store. No resolution in sight yet.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I believe the problem is not that Automate stops working during media playback, but the button mapping itself. I had a similar problem with audio playback and the home button not functioning. I had a chat with @Datastream33 and he made a couple changes that corrected the problem. I believe he mapped the button differently because the button mapping was taken from Automate by the media app while using it. I don't know the exact issue, but it's close to that. I tagged Datastream here because you'll need to talk with him about the issue you're having. He's been in here frequently the past few days so he'll probably see this soon. (y)