yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Bluetooth does work but making the initial connection can be challenging. This a problem with ALL custom ROMs for this device based on Android 5 and above. Please search the thread for more info and tips on pairing.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jukiba101:
Bluetooth does work but making the initial connection can be challenging, I CANT CONNECTION TO GAMEPAD OF SOUND DEVICES, BUT I CAN CONNECT TO ANDROID PHONE , EX : XIAOMI , SAM SUNG , BUT I CANT CONNECT TO GAME PAD OF SOUND DEVICES, I USES TO PARIS , BACKUP DATA BLUETOOL TO OTHER CUSTOM ROM , LATER ,I FLASH TO TWRP ROM AOSPEXTENDED , I BACKUP DATA ON PARIS , BUT , BLUETOOL DON'T WORK FOR MY DEVICES, I SO SAD :D , BUT I BELIEVE YOU FIX TO ROM FUTURE , THANK YOU VERY MUCH

---------- Post added at 01:51 PM ---------- Previous post was at 01:46 PM ----------

i cant connection to gamepad of sound devices, but i can connect to android phone , ex : Xiaomi , sam sung , but i cant connect to game pad of sound devices, i uses to paris , backup data bluetool to other custom rom , later ,i flash to twrp rom aospextended , i backup data on paris , but , bluetool don't work for my devices, i so sad :d , but i believe you fix to rom future , thank you very much

---------- Post added at 01:52 PM ---------- Previous post was at 01:51 PM ----------

i cant connection to gamepad of sound devices, but i can connect to android phone , ex : Xiaomi , sam sung , but i cant connect to game pad of sound devices, i uses to paris , backup data bluetool to other custom rom , later ,i flash to twrp rom aospextended , i backup data on paris , but , bluetool don't work for my devices, i so sad :d , but i believe you fix to rom future , thank you very much
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
It won't be fixed because it is not a correctable ROM issue. If you need reliable Bluetooth on this device go back to stock or use one of the two custom ROMs based on Android 4.4.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jukiba101:
is it possible to fix it in the future, kitkat 4.4 is quite boring, i used to use nougat rom, it is quite friendly to me, i still do not understand why it is not a problem chrome 5.1, you can explain why
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Kernel issue; further customization/tweaking not possible. Amazon hardware is unique. Amazing developers (really just one) are able to get custom ROMs working at all. Be happy for what you have. Consider another device If BT is a priority.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] droiduzr2:
BT does work.

You have to try about 10-20 times for the first device.

My headphones would not pair so I tried with my keyboard and it finally worked.

I tried 5 times after with my headphones then I tried to turn off/on BT then airplane mode...still was not connecting.

So I rebooted and then tried the headphones again and it paired the first time.

Once you get the first device to pair (sometimes try switching airplane mode on/off) then reboot to connect the other device.

Sometimes you can try turning BT on/off for a few seconds to see if it pairs.

I paired other devices with no issues.

When I was onn LOS14 my wifi and bt would resume after sleep for me but I notice in this rom I have to toggle airplane mode for them to reconnect. No big deal, just add widget on homescreen. I think they said LOS has the same issue but for me I did not have that issue.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] droiduzr2:
[MENTION=5749760]ggow[/MENTION] Is it possible to add a shortcut for airplane mode to the lock screen shortcuts. I don't see it.

This will allow us to toggle airplane mode to turn on wifi and Bluetooth after coming out of sleep mode.

I tried replacing the dialer shortcut but did not see airplane mode shortcut.

Thx
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
This can be easily accomplished via the quick settings pulldown which is available on the lock screen. Alternatively, Xposed framework and select modules such as Gravity Box or Xposed Edge can get the job done.

Not a fan of adding 'stuff' to any AOSP ROM.

As an aside I rarely experience WiFi issues on my HDX which sleeps like a baby. Be sure the radio remains engaged during sleep under advanced settings. Also consider changing AP to a non DFS channel if spontaneous disconnects are a problem.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] droiduzr2:
1. instead of pulling down the option would be there as soon as I turn screen on

2. nothing to add since there are lots of options from system settings than can be used e.g. bluetooth

3. I personally don't want to add xposed or other apps I don't need/use (for now).

I did turn on the option for wifi to run off during sleep (save battery?) OR does this not matter?

My suggestions is based on the the fact we HAVE to turn the screen on with the power button and then we have to swipe to unlock (at the least). If there is a shortcut we can toggle airplane mode...unlock and by that time the tablet is ready to go and connected to the wifi.

It's just an idea to make it easier since we have to live with this "glitch".

As mentioned...if it's an easy change to display airplane mode as an option in the lockscreen ui settings would be great.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
- look through the many dozens of 'activities' that can be assigned via the native AEX interface

- Xposed Edge can do everything you suggest with a single action of your choosing; no programming required

- mucking with the feature set of an off-the-shelf ROM is just asking for a downstream maintenance headache

- the "glitch" is manageable via other means

My idle (screen-off) drain rate is 0.2%/hr with all radios on, full push mail and no special actions beyond normal doze and hibernating a few 'bad actors' (apps I prefer to keep despite their inconsiderate idle behaviors) with Greenify. Drain rate does not decrease significantly with radios off...perhaps 0.15%/hr on a good day.

As an aside, I use a case with a magnetic switch that powers the device when opened and turns it off when closed. I could also auto unlock but I prefer leaving that as a manual task. If connected to my home network the device unlocks with a swipe; otherwise the normal pw/pin challenge is displayed. Convenience and security wrapped in a single bundle. Best part - works with any ROM without having to bother the dev with 'special' feature requests.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] xmfahrer:
Is there any way to switch the UI to Tablet-Mode ? (Dock and NAV-Bar at the bottom in landscape-Mode) ? :confused:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
That's the default behavior; dock/navbar on bottom regardless of orientation.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Locklear308:
Pardon me, but is this rom still supported? I actually just bought an 8.9 and will most likely be loading this one. I've read that it is the best one :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Still supported although updates come relatively infrequently. That's not necessarily a bad thing for those who value stability.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Locklear308:
Oh wow I didn't realize you were the dev Davey!

I totally value stability :D
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Ha - [MENTION=5749760]ggow[/MENTION] is the dev supporting AEX and most of the other excellent ROMs for this device. There is a fair bit of working involved spinning up images for this temperamental gizmo. Be sure to give a shout out to [MENTION=5749760]ggow[/MENTION] via 'thanks' button or other means as appropriate.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Locklear308:
I did just that!

So great to finally have a custom rom'd tablet again.

I do have some questions though... while she runs great I noticed that sometimes she makes strange little pop sounds and that locking the screen sometimes makes her stutter. Is this normal?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
- locking sound toggle: settings->sounds->other sounds

- lock screen stutter likely a consequence of a lean ROM; purely cosmetic :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Locklear308:
Oh sorry, not the lock screen sounds. It's like, so I plug in headphones to listen to some ASMR and while video is playing everything's fine. But when there's no audio, there's a strange occasional pops and clicks, I mean it's not not a huge deal I just want to make sure that this is normal and that there's not something wrong with mine.. lol

Other than that, the rom runs great! I got about 7 hours of screen on time my first run, I'm sure it'll get a little better over time.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Occasional clicks/pops are a characteristic of this device when running any custom ROM. Flashing a Dolby mod will usually reduce but not eliminate the spurious sounds. Most just live with it.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Locklear308:
Okay cool, I just wanted to make sure my device didn't have a problem. I will look up this Dolby mod.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] therealisttruest:
Hardware Failure?

I'm just wondering if anyone has seen this issue with this ROM or any others on Apollo. The other day when the battery was under 15%, I plugged it in to charge and left it setting on the desk nearby. A little later I looked over and noticed that the screen had gone from the usual standby mode in darkness to a very notable all blue screen. I tried to get the device to respond at that point but it didn't so I held down the power button for a bit to shut it all the way down. Then restarting it I got the Kindle Fire screen that's normally before the AEX boot screen but it did not proceed further. Then shut it down once more and was going to go into recovery mode but it fully stopped responding at that point. I then plugged it in and let it set for hours and tried again to boot it up but now it's basically a brick., no screen coming on, buttons don't seem to do anything, and plugging it in via USB to another device does not seem to recognize that it's there either. Any ideas or has this thing finally bit the dust?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Sounds like an eMMC failure which is not terribly uncommon on this device. Sorry for your loss.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] therealisttruest:
Argh! Thanks for letting me know anyway. I suspected as such but was hoping since it happened with no real warning that there might have still been some wizardry to perform. Any chance of possibly getting one on eBay and parting is out for the drive, or is that a nonstarter? Probably not worthwhile even if possible, I suspect.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Probably best to unlock/reconfigure eBay acquisition retaining current unit for spare parts if needed.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] bobcat131:
Any status on lineage 15-1 ?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Why are you asking in this thread? See: https://xdaforums.com/kindle-fire-hdx/orig-development/rom-cm-14-1-thor-t3517481/post76573527
[Kindle Fire HDX 7" & 8.9" Original Android Develop] bobcat131:
Sorry, I meant AospExtended :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
[MENTION=5749760]ggow[/MENTION] stated work on Lineage 15.x will come first and, if successful, *may* result in other Android 8.x variants for this device. Last update suggests hurdles remain getting a working/stable Oreo ROM on this device and the developers time is very limited.

I'm pretty happy with AEX 7.1. Nothing in Oreo serves as a 'pull'. Nice to have - yes. Fundamental - no. AEX and other Nougat variants will serve it well during its golden years.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
New Build is Up

- Dated 10 June 2018

- Security updates up to May 2018

- Upstream updates
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sublimeace:
Thanks for the continues development of our beloved device!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] kisirong2501:
I flashed this rom yesterday but internal storage only have around 9.5gb available and system storage occupied around 6gb. Can anyone please tell me that is normal or any issue?

Thanks
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Not sure what you are asking. HDX system partition is 1.2 GB with ~350 MB free after flashing AEX and GApps nano. Data partition is 11.7 GB with remaining free space largely dependent on your personal app portfolio.

---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------

FWIW - flawless update via TWRP following the (my) usual best practice:

- backed up boot/data/system partitions

- wiped same partitions; left data partition untouched

- flashed latest Lineage, GApps (nano), SuperSu (2.82 SR5) and Xposed Framework zips

- reboot and profit
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jukiba101:
howto change icon to rom ?

---------- Post added at 12:15 PM ---------- Previous post was at 11:29 AM ----------

how i can change icon pack
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Snail Wang:
Got problem when rooting this Rom

I got a problem then rooting this Rom. My device is Apollo, and the twrp version is 3.1.1-1.

If I just flash the latest Rom and OpenGapps, everything works fine.

But if I flash Magisk 16.0 or SuperSU v2.82, the device will freeze at the kindle fire boot logo when booting.

I had checked the replies in this post, and it seemed that nobody else meets this case. So any suggestions will be appreciated.

By the way, same problem occurred when rooting the latest LineageOS for MicroG Rom in this post https://xdaforums.com/kindle-fire-hdx/orig-development/lineageos-microg-6-13-18-t3803805
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Need to unlock the bootloader (mandatory for root).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Snail Wang:
I tried to unlock following the guide in this post https://xdaforums.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 but failed.

I did receive a "unlock code is correct" message, but when I tried to flash a recovery with fastboot I get a message like "failed... locked hw". It's confusing for me.

So, do I need to roll back to a stock version Rom to unlock the bootloader? I'm in Slim 7 now.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steamport:
You flashed the aboot via QHUSB_BULK, right?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Snail Wang:
No. I use the terminal in TWRP 3.1.1-1 with dd command.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You do not; installed ROM is irrelevant. Sounds like a faux success message. Make sure the vulnerable aboot appropriate to your device type has been flashed. Might need to redo entire procedure after dumping device into 'bulk mode' - including erasing current aboot.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Snail Wang:
I followed guide from here, but it seemed bulk mode do not work too.

"unlock code is correct" message did received, but flashing a recovery via fastboot still returns a "failed... locked hw" and still freezing at the "kindle fire" boot logo after flashing a root zip.

Do you have any other idea?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Exact details please!

Could perform these steps (need to enter 'fastboot mode' first):

fastboot -i 0x1949 flash unlock YOUR_UNLOCK_CODE_FILE
fastboot -i 0x1949 flash recovery YOUR_RECOVERY_IMAGE_FILE

and post a screenshot of your terminal/cmd window showing

the steps and their output?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Snail Wang:
Terminal:

Kindle:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Mysterious

Umm... That's paradoxical... (^;

Is there any chance that you may have flashed the wrong aboot?

Granted, I have no idea if that could actually cause such behavior,

but I don't quite see what else (other then a HW issue) might...

Could you also run these commands?

fastboot -i 0x1949 getvar product
fastboot -i 0x1949 oem idme \?

(Or post the info pane on the left in the 1-Click web-UI,

if you managed to get your device connected/assessed.)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Snail Wang:
Here are the command results:

[IMG="Commands results"]http://wx2.sinaimg.cn/mw690/b9b454f8ly1fsnmg439ljj20ej03w74k.jpg[/IMG]

I tried to unlock with 1-Click, but failed.

First, I got this:

[IMG="Step 1"]http://wx1.sinaimg.cn/large/b9b454f8ly1fsnmg4mfsrj21hc0u07dk.jpg[/IMG]

Then I clicked the check mark. It keeps running until this:

[IMG="Step 2"]http://wx3.sinaimg.cn/large/b9b454f8ly1fsnmg4ls1aj21hc0u0k13.jpg[/IMG]

You can see the log from the left that the script keeps echoing the same message. I tried to wait for a long time, but nothing changed. So I closed the cmd and ran the script again, but no help. Finally I found I needed to reboot my computer then ran the script again, then I came to next step:

[IMG="Step 3"]http://wx3.sinaimg.cn/large/b9b454f8ly1fsnmg4mevtj21hc0u0k0h.jpg[/IMG]

I clicked the check mark, and it works. A notification pannel popped out, and I followed the guide on it. Then I got this:

[IMG="Step 4"]http://wx2.sinaimg.cn/large/b9b454f8ly1fsnmg4netxj21hc0u0k0h.jpg[/IMG]

What's strange that it ended without unlocking my device. No message echoed from the devices.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Wow.... Personally, I think there's a lot more that's strange than failing to unlock....

First and foremost, that 'unlock code correct' message is absolutely weird,

considering that your bootloader is locked...

Next, the first assessment from 1-Click shows that you have AEX installed

in the system partition. How did that happen with a locked bootloader? (-;

BTW, the device enumerates with a Google vendorID, which seems to confirm

a successful AEX installation. Chances are this has been unlocked before you

started, and somehow you managed to relock it. (Again, I suspect you may

have flashed the wrong aboot; i.e. 13 for Thor instead of 14 for Apollo.)

Possibly even more strangely, the serial number reported on the first two

tries is different than that on the next two. Your device obviously reports

the same all the time (as evidenced by the logs), but -in bulk mode- 1-Click

tries to read the serial number and EMMCid from the diagnostic partition,

and the serial number there differs!!! BTW, unless I'm mistaken, Thor serial

numbers tend to start with D and Apollo with B; so, I'm thinking that the

serial number on the diagnostic partition is the one that is actually correct.

(Again, could this be due to the wrong bootloader having been flashed?)

Finally, the last three logs show weird errors I've never seen before,

and I have no idea where they might come from (except, perhaps, adbd),

since my code doesn't ever use sqlite, or connection factories of any kind.

May I ask where/how you got this device?

Did you install AEX, or was it like that when you got it?

It's just all weird.

I'll PM you for troubleshooting with 1-Click.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
On this point only ... AEX and several other HDX custom ROMs can be flashed on locked hardware following the installation of a vulnerable aboot. However, root can not be obtained via any method (SuperSu, PPH, Magisk) until the bootloader is unlocked. As mentioned in an earlier post me thinks the wrong aboot is installed; I suspect it was never unlocked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Snail Wang:
I bought this device from a E-commerce Vendor. The device was in Lineage 14 when I got it.

I just use TWRP to install the twrp-3.1.1-1.img to upgrade it and flash Slim 7 with OpenGapps. In fact, I can flash any Android 7 Rom in this forum with OpenGapps and the devices works well. But the device will freeze at the "kindle fire" boot logo If I flash any root zip, such as SuperSU or Magisk. So the AEX was installed by me in TWRP.

By the way, I do notice the serial number problem and now I am doubting if I get the correct aboot file. I just download aboot-14-apollo.zip from this post, and the md5sum of the .msn file is 4a2be8e374c8d1fce8e6743ac2d09bb0.

Can you PM me a aboot file for apollo? Then I will try to unlock again. Or, How to reflash the bootloader?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Of course...

That's right. I forgot that the new ROMs have their boot images fake-signed.

The latest crop of system-less root managers on the other hand implant themselves

in the boot image, which changes the binary; so, any signature check will fail...

This suggests a potential work-around: grab the modified boot image (TWRP should do,

but bulk mode certainly works), fake-sign, and put back that version. I'd still recommend to unlock instead, but in a situation where the bootloader remains locked despite the coveted 'unlock code is correct' message, this might be easier than finding the root cause....

(Although I'm in violent agreement with the expectation that this is likely due to the wrong

bootloader/aboot version having gotten flashed.)

---------- Post added at 19:31 ---------- Previous post was at 19:26 ----------

Thanks for the background info!

Your hash matches; so, you should be fine.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
BT pairing timeout bug?

I'm having the exact same issue as [MENTION=8595854]urigg[/MENTION] with keyboard pairing timing out *way*

before having a chance to enter a 6-digit PIN, but -honestly- I don't buy the power

management ideas. Not for a split second. This looks/feels like a simple timing bug,

such as simply using/assuming the wrong units (e.g. micro instead of milliseconds)

for a timeout value... Also, given that -once paired- devices appear to work flawlessly,

the obvious place look for discrepancies would be the pairing code...

If you need a rationale why I presume a bug, the pairing times out *very quickly*

claiming to have received the wrong code even if I don't ever touch the keyboard.

I have serious doubt about this happening due to _very quickly_ entering/resuming

deep sleep...

[MENTION=5749760]ggow[/MENTION]: Can you give me a hint where to look to check if this may be the case?

Would this be in the kernel driver or (more likely?) controlled from external settings?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
I hope you are right. That said, the scenario you are experiencing is only one of several that occur during failed pairing attempts. On most of my troublesome devices the timeout occurs after a much longer period of time, if at all. In most cases the pairing just fails forcing a reboot before making further attempts.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I think you're right, it's a bug. It should be possible to get it fully working. The kernel driver is here and more specifically the power control:

https://github.com/ggow/kernel_phoenix_hdx-common/blob/or-8.1/drivers/bluetooth/bluetooth-power.c
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Workaround

Thanks, but as I said, I seriously doubt it has to do with power control.

What makes you think it does??

In any case, I got lucky. (-;

I kept trying until I got a 6-digit code with enough repetitions;

so, that I could read, comprehend, and enter all 6 digits before

the timeout kicked in. That got my keyboard connected.

Once the keyboard was connected, I tried pairing my speakers

without much luck, UNTIL I kept pressing keys on the freshly

paired keyboard during the pairing procedure (which I assume

kept the BT stack busy enough to miss the timeout); and, then,

lo and behold, the speakers got connected as well.

So, I'm good for now. This is _really_ fiddly, but _can_ be

gotten to work.