yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Android Development] Datastream33:
You need to ensure the navbar is setup correctly, and the "tb_custom_launcher" key is set (determines what activity Automate needs to launch, so if it's not set correctly, Automate won't be able to find the activity - as seen in your screenshot).

Before we do anything, let's put the home button image (will be used on the navbar) in the right place. On your tablet, make a new folder on the root of the SDCard, call it NavIcons0, and put the home.png (attached to this post) file inside that folder (Should look like this: sdcard/NavIcons0/home.png).

Next, we need to run some ADB commands to set up the navigation bar layout and Launcher Invoker.

Try running these commands one at a time in an ADB Shell (double-check the commands are inputted exactly as they appear below before executing!):

settings put secure tb_custom_launcher com.teslacoilsw.launcher

settings put secure sysui_nav_bar 'left[1WC],;back[1WC],key(130:file:///storage/emulated/0/NavIcons0/home.png)[1WC],recent[1WC];right[1WC]'

Once each command is executed (the commands shouldn't return anything), start the Launcher Invoker flow, and try tapping the home key to pull up your custom launcher. Let us know how it goes. Best of luck!
[Fire HD 8 and HD 10 Android Development] jhford:
I'll do this first thing tomorrow and report back to you.
[Fire HD 8 and HD 10 Android Development] Datastream33:
OK, sounds good. Have a great night! :D
[Fire HD 8 and HD 10 Android Development] jhford:
The second command returned the following.

Alias file was missing, so it has been created.

> "cd /storage/emulated/0/;settings put secure tb_custom_launcher com.teslacoilsw.launcher"

I'm using One Button Navigation. So, where is the Home Key, the yellow One Button Navigation dot?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
There's your problem! One Button navigation replaces the navbar. We're trying to fix the standard navbar to work with your launcher, but you've replaceds it with One Button Navigation so this won't work.

You're 2 choices are to scrap the Custom Navbar Key method and configure One Button Navigation to do what you want.

The other choice would be to disable/uninstall One Button Navigation and use the Custom Navbar Button method of replacing the middle button.

Both methods will do what you want, just differently. The choice is completely up to you, but they can't be run simultaneously and still work.

If you want to use Custom Navbar Key, just uninstall/disable One Button Navigation and follow the steps I gave earlier about resetting the navbar in ADB Shell and going through the Custom Launcher subtool.

If you wish to use One Button Navigation, similarly reset the navbar key in ADB Shell, install Nova Launcher, and One Button Navigation. Finally, you must configure One Button Navigation to launch your launcher on button press.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Ah, that makes sense. Yeah, @blaacksheep is correct... you need to make a choice as to which method you'd like to use. Running the commands from my last post should of successfully setup your navbar so all you need to do is unhide the navbar and run Launcher Invoker. Or, if you do prefer using One Button then you don't need to do anything else except setup One Button to work to your satisfaction.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
The main drawback to One Button Navigation is that it doesn't transition to landscape mode and remains on the short side of the screen in landscape. If that doesn't bother you and you like it that's fine. :)
[Fire HD 8 and HD 10 Android Development] jhford:
The Commands and the output:

Alias file was missing, so it has been created.

> "cd /storage/emulated/0/;settings put secure tb_custom_launcher com.teslacoilsw.launcher"

> "cd /storage/emulated/0/;settings put secure sysui_nav_bar 'left[1WC],;back[1WC],key(130:fiile:///storage/emulated/0/Navicons0/home.png)[1WC],recent[1WC];right[1WC]'"

I'm now running the Custom Launcher in FTB. Do I click "Re-route home key" and "Custom Navbar Key"?

[EDIT] I guess so, because I clicked them and am now inspecting OUR (mostly YOUR) work.
[Fire HD 8 and HD 10 Android Development] jhford:
I don't see a Home Key. I can't navigate in Nova. The dropdown notification says that Automate is running 2 fibers. Is that normal?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
You would just choose one of those. I assumed you were going to run Custom Navbar Key, not Re-route home Key. Re-route Home Key is nice, but it doesn't survive a reboot of the tablet if I remember. It needs to be done each time you boot the tablet.

Custom Navbar Key / Automate / Key definition DOES survive reboots and only needs to be done once. It's the better choice IMO.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Firstly, if you followed those commands, then you need to have the Home icon file where it's supposed to be, otherwise it cant draw a home button. See this post by @Datastream33 for the file and where to put it.

The running fibers all have flowers next to them when you open Automate. If you have more than one Launcher Invoker fiber running, stop one of them. You could also have a fiber running for the quicklaunch icon rearrangement if you chose to do that too. It is needed to make the order permanent. Otherwise, it goes back to standard on reboot.

Edit: You may have an "invisible" home button. You can test this by pressing where it's supposed to be. ;)

Edit 2: I had a look at my tablet with 2 flows running - Launcher Invoker, and Custom Quicksetting Tiles. It has 4 fibers running so I guess that's normal.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Hmm, it should be running 3 fibers. If you don't mind me asking, where did the Launcher Invoker flow come come? Did it come from an older version of the Toolbox?
[Fire HD 8 and HD 10 Android Development] jhford:
My man @blaacksheep. https://xdaforums.com/t/windows-linux-tool-fire-toolbox-v33-1.3889604/ BTW, what does the Home Key look like? I've been using OBN too long. BTW, before ran FTB Custom Launcher a few minutes ago, I tried to access the SD card with Windows Explore which I could do yesterday, Now it's no longer available in Explorer. :unsure:

Also, should I download another version of Automate from the Google Play Store?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
It's just a dot or a circle. It's white but looks like OBN button.

The tablet won't transfer files in camera mode, and it usually won't do ADB in file mode. You have to switch modes to access files in Windows Explorer.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Here's the home button from Datastream33's post. link
[Fire HD 8 and HD 10 Android Development] jhford:
But I can't navigate in Nova. I use File Manager + from the Play Store to do the file stuff. OMG, I think I misspelled the name of the directory on the SD Card where home.png is stored. [EDIT] I just renamed the directory even though it seemed to be spelled correctly, and home.png is there. Now what?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
You can do it all automatically by restting the navbar in ADB Shell, and re-installing the custom launcher in Toolbox. It should offer to re-install whatever is needed.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Be sure the folder is named "NavIcons0". It's very sensitive.

Once the home.png file is placed, re-execute the navbar command:

settings put secure sysui_nav_bar 'left[1WC],;back[1WC],key(130:file:///storage/emulated/0/NavIcons0/home.png)[1WC],recent[1WC];right[1WC]'
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I'll shut up here so we don't get things confused any worse.
[Fire HD 8 and HD 10 Android Development] jhford:
Alias file was missing, so it has been created.

> "cd /storage/emulated/0/;settings put secure sysui_nav_bar 'left[1WC],;back[1WC],key(130:file:///storage/emulated/0/NavIcons0/home.png)[1WC],recent[1WC];right[1WC]'"

Why did it add extra apostrophes at the end??

I don't see home.png displayed and still can't navigate, and still can't setup my Nova Widgets.
[Fire HD 8 and HD 10 Android Development] Datastream33:
It just appends a quote to the beginning and end of the command to show what's been executed exactly. Could you take a screenshot of your current setup?
[Fire HD 8 and HD 10 Android Development] jhford:
Which screen would you like? What am I saying? I can't navigate.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Could you take a screenshot of the Launcher Invoker flow?

Open automate, tap the Launcher Invoker, tap the pencil icon at the bottom right, and then tap this button:

Then pinch the screen and zoom out so we can see the full flow. Thank you!
[Fire HD 8 and HD 10 Android Development] jhford:
I hope that worked.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Yep, everything here looks good.

Ok, what does your navbar look like?
[Fire HD 8 and HD 10 Android Development] jhford:
I don't have one. Also, there are only 2 flows.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Ah, we need to get your navbar working again, then. Do you still want to go down the Custom Navbar Key route?
[Fire HD 8 and HD 10 Android Development] jhford:
I'm no expert, but I guess so. @blaacksheep prefers it to OBN.

BTW, something to think about. Isn't there some way to backup the whole damn thing like Nandroid? Maybe just clone the disk or something similar. I would sure save you guys a lot of grief.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
The only reason I prefer it is that it follows landscape mode. OBN doesn't, so when you turn it sideways, the navbar stays on the side with OBN.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Just out of curiosity, is this the One Button Navigation app you're using?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
That's the one I was using. It's in the Play Store, too.
[Fire HD 8 and HD 10 Android Development] Datastream33:
It appears it has an option to start Nova on tap instead of just pressing the home key. Perhaps @jhford could just set it to launch Nova instead of messing with Automate and the navbar?
[Fire HD 8 and HD 10 Android Development] Datastream33:
Turning off the service in One Navigation should restore the navbar. After it's turned off, run this command and see if that restores the navbar (if it isn't already):

wm overscan 0,0,0,0

If that doesn't work, try this:

settings put global policy_control null*
[Fire HD 8 and HD 10 Android Development] bibikalka:
So there was DNSMASQ upgrade for my router due to a vulnerability. Updated the router, tried to turn on private dns again via [put global private_dns_mode hostname], and immediately back to the same issue as before! So I had to revert to "private_dns_mode off" to ensure things are working.

I am not sure if there is a good way to reset the local private dns stuff on the tablet without doing a factory reset ...
[Fire HD 8 and HD 10 Android Development] C0RLoCK:
Hello all, I am having an issue where the toolbox (33.1) keeps "Dropping" the connection to my Fire HD 10 (2017) after the ADB stays active for a few seconds. The Fire has been factory reset and the wifi connect has been skipped. Can anyone help me figure it out?

PS: I'm running the latest version of Windows 10
[Fire HD 8 and HD 10 Android Development] blaacksheep:
The first thing I would do is try to rule out a faulty cable or USB port on the computer. Try a different port and try a different cable. Many times, it's that simple. :)

Edit: BTW, Welcome to XDA!
[Fire HD 8 and HD 10 Android Development] C0RLoCK:
Will do, I'll let you know how that turns out. Thanks much!
[Fire HD 8 and HD 10 Android Development] C0RLoCK:
I've tried 4 different cables and all of my ports, and still no luck. I HAVE noticed something which might be causing an issue. I seem to have an emulator that keeps popping up and disappearing even while the fire isn't plugged in, and I do have the Android function enabled in my BIOS that allows me to play and use android Apps & Games on my PC via Noxplayer, could that be causing the issue?

Also, the ADB command isn't recognized in my CMD prompt, if that means anything.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
That was the next thing I was going to say - an Android emulator would cause problems because ADB can only connect to one Android device at a time.

You could try temporarily disabling the Android emulation in your BIOS to see if that fixes things. Also, a Roku, a smart TV, or other Android TV box will also disrupt the ADB connection (Wired or WiFi). They must be disconnected for Toolbox to work.

The ADB command is probably not launching because it isn't in your system's path. If you want to launch it via command line, right-click on your Toolbox icon and select "open file location". Double-click the ADB folder. I can't remember if it's just another right-click or if it's shift+right click or ctrl+right click in that folder that brings up "open command window here". Shift+right click in that folder and select "Open command window here". ADB will work in that command window. (y)
[Fire HD 8 and HD 10 Android Development] jhford:
wm overscan 0,0,0,0 worked. The 3 nav buttons are at the bottom, but on reboot the device is the Amazon Launcher and I have no widget control. Should I run the second command?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Great. I hope you understand that I don't want to confuse things by offering different advice than @Datastream33 . I don't think he gets in here till later on. Please wait for him to help you out. :)
[Fire HD 8 and HD 10 Android Development] C0RLoCK:
SOLVED:

It turns out NTKDaemon, which is a Sub-Process of Native Instruments & Native Access software was the culprit. It was continuously popping up in the ADB as emulator-5562, and I fixed it by simply ENDING the NTKDaemon PROCESS in TASK MGR. I now have a stable ADB with my Fire.

Thanks again for the assist!
[Fire HD 8 and HD 10 Android Development] blaacksheep:
You're the second person in recent memory with a problem like that. I'm glad you were able to find it without too much difficulty. I hope you enjoy Toolbox and with your tablet being a 2017 model, probably can block most of the Amazon things like Launcher and OTA updates that require workarounds to block on later tablets. Good luck and have fun. :)
[Fire HD 8 and HD 10 Android Development] C0RLoCK:
Sry, I seem to have another issue, can anyone link me to the "Google App" APK that will work on HD10 7th gen? The toolbox can't download it, crashes, and going through the play store directly only shows that the app isn't compatible. The reason for the request is that Google Assistant needs it.

I am unsure if the suggested "Google GO" within the store would work as an alternative.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I'm not sure about this, but searching XDA for "google App fireOS" lead me to this app from apkmirror.com. It's a very early version of the google app which should update itself to whatever version is applicable now. Try installing it and leaving your tablet online for 10 minutes or so before trying google assistant. You may need to force a manual update from google by tapping your avatar in the upper-right of Play Store, then tap manage apps and device. Look under Updates to see if it wants to update anything. Make sure you remove any previous version of google app before you install it. Later versions of the app come in multiple versions with multiple signatures and I don't know which signature you need, hence letting it update itself from an early version that is known to work on Fire tablets.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Over the last while, Google has been upgrading the level of Android OS support required for the Google-branded apps.

To recap, your Fire HD10 (Gen 7, 2017) is running FireOS 5 (based on Android 5).

Cuuent version of Google app now only supports Android 9 (and later) . Same for Google Go app. Google Assistant still supports Android 5.

Sideloading an older versions affected apps from a trusted source might work. More recent older Google app versions supported at least Android 6, so you have to find a much older version. Older app compatability with current Google Play infrasttucure is uncertain, as Google is upgrading the checking/verification of app versions in line with their current more stringent app security coding requirements.

Check the current level of Android support of specific apps by expanding "About this app" from the app's entry on Google Play Store.

Disable auto-updating of apps to avoid unwanted app upgrades.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
The app I linked was written to support Android 5, so it might work. 🤷
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Yes, that's an older version Google app for Android 5, but I'm uncertain of the compatabilty with current Google Play infrastructure. Google has been "encouraging" app devs to upgrade their coding to be compliant with recent stricter security guidelines, which will be more strictly enforced by mid-2024. Seems a lot of devs may be dropping coding for older Android versions to simplify compliance with the new Google guidelines.

#Edit

I haven't seen any complaints from exiting FireOS 5 users, so older Android 5 apps should should still work for the mean time. I'm not an Android dev (.. not even close ) but I recall that app support for unsupported Android versions (ie depreciated versions) is optional. FireOS 5 (and even FireOS 7) must be considered "geriatric" in an Android 14 world.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
You're absolutely right. I have no knowledge that the app actually works. I just offered it as a suggested trial. I'm pretty sure if it doesn't work, or won't update, that it can simply be uninstalled like most other apps. Then it's up to @C0RLoCK to decide if he wants to try either a different version, or some other method of making Google Assistant work.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Awesome! No need to run the second command as we now have the navbar present. Could you now please take a screenshot and share it with us?
[Fire HD 8 and HD 10 Android Development] jhford:
A screenshot of any particular screen? Remember, I kind of stuck in Amazon Launcher hell.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Yeah, any screen will do. Just need to see the navbar.
[Fire HD 8 and HD 10 Android Development] jhford:
Here you go.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I see a small home button. Looks like the Custom button to me. (I hope I'm right!) :)
[Fire HD 8 and HD 10 Android Development] Datastream33:
As far as I could tell, the Google GO app doesn't have assistant baked on like the regular Google app does. Here's an APKMirror link to the Google App that should run on your tablet. You'll also need the "GAssist.apk" file, and that can be downloaded from here. It's supposed to be included with the Toolbox, but for some reason I forgot to include it. Place it in the "\bin\Google Services" folder for your Toolbox installation (right click the Toolbox desktop shotcut and then click "open file location" to open the Toolbox's root directory in File Explorer). Now execute the Google Assistant tool and the Toolbox should set everything up.

Let us know how it goes, and best of luck! :D
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Sounds like a much better idea than my stab at trying to give you an app to try. (y)

Edit: Well, at least I gave you an earlier version of Google app for Android 5 ARM-v7a. I had no idea about the GAssist app, though. :/
[Fire HD 8 and HD 10 Android Development] Datastream33:
Thank you for the screenshot. The navbar looks correct. Is the Launcher Invoker flow started in Automate?
[Fire HD 8 and HD 10 Android Development] jhford:
It is now with 3 threads if that's what they're called. I took the liberty of restarting it - sorry to step on your toes. But it still can't setup my widgets and I'm still stuck in Amazon Launcher hell.
[Fire HD 8 and HD 10 Android Development] Datastream33:
Ah, dang.

Staying on that screen, what does the log look like when you press the home button?
[Fire HD 8 and HD 10 Android Development] Datastream33:
Let try a different approach to the appbind for widgets. Try this:

In an ADB Shell (one at a time and make sure to type the commands exactly):

1.

cp /system/bin/appwidget /sdcard/appwidget.sh

This command should return nothing.

2.

sh /sdcard/appwidget.sh

This command should return the following:

3.

appwidget grantbind --package com.teslacoilsw.launcher --user 0

This command should return nothing.

Now try adding a widget.
[Fire HD 8 and HD 10 Android Development] jhford:
Output 2, I think - I sort of lost track, but you'll understand.

Alias file was missing, so it has been created.

> "cd /storage/emulated/0/;cp /system/bin/appwidget /sdcard/appwidget.sh"

Output 3, same caveat.

> "cd /storage/emulated/0/;sh /sdcard/appwidget.sh"

usage: adb shell appwidget [subcommand] [options]

usage: adb shell appwidget grantbind --package <PACKAGE> [--user <USER_ID> | current]

<PACKAGE> an Android package name.

<USER_ID> The user id under which the package is installed.

Example:

# Grant the "foo.bar.baz" package to bind app widgets for the current user.

adb shell grantbind --package foo.bar.baz --user current

usage: adb shell appwidget revokebind --package <PACKAGE> [--user <USER_ID> | current]

<PACKAGE> an Android package name.

<USER_ID> The user id under which the package is installed.

Example:

# Revoke the permisison to bind app widgets from the "foo.bar.baz" package.

adb shell revokebind --package foo.bar.baz --user current

[ERROR] Unsupported operation: null

I rebooted to test the widgets. It's not really working. Is the home key the white dot in the center flanked by the left pointing arrow on the left and running apps square icon on the right?
[Fire HD 8 and HD 10 Android Development] jhford:
I really appreciate you're help, but can we pick this up tomorrow. My wife just came home
[Fire HD 8 and HD 10 Android Development] jhford:
I just woke up to pee (hypertension & diuretic meds) and checked the Internet with my HD 7. I noticed that both the Nav Bar and ONB are installed and active which I guess I took for granted. See attached screenshot.
[Fire HD 8 and HD 10 Android Development] Datastream33:
@jhford, could you open Automate, tap on the Launcher Invoker, and on the screen with the log could you please press the home button and let me know what the log says?
[Fire HD 8 and HD 10 Android Development] jhford:
@Datastream33. I hope you didn't give up on me. "if you'll be my bodyguard, I can be your long lost pal."
[Fire HD 8 and HD 10 Android Development] Datastream33:
Haven't given up yet. Just got some housework to do. Be with you soon. ;)
[Fire HD 8 and HD 10 Android Development] golfgirl8350:
I have a new HD 10 (2023). I ran all the usual FTB modifications (I've been using toolbox for years--so love it.) Anyway, besides the launcher being a little glitchy, I have one other problem I'm hoping someone can help with. In Google Calendar, the drag and drop feature to move posts around doesn't work. I've scoured the web for answers and none really apply to fire tablets (turn off select-to-speak and turn off screenshots). Drag & drop works flawlessly on both of my HD8+ tablets, and moving a calendar post on my phone or on one of the HD8+ tablets will update the HD10 when it syncs. Is there something I can do to make this work?
[Fire HD 8 and HD 10 Android Development] DB126:
Interesting - calendar app crashes after intro screens on my Fire 11 (8.3.2.2). Most other Google apps run fine. I'll try installing on my 2023 HD 10 later; not accessible ATM.

Make sure all scaling options are set to default (even if not your preference) and try again. Might help identify source of issue.
[Fire HD 8 and HD 10 Android Development] Datastream33:
So when you tap the home button, Nova doesn't start, right?

I don't get it. Everything is set up properly. The Navbar looks right, and it looks like the settings database value is also set up correctly.