yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] opteron88:
Is this compatible for 4th Gen HDX 8.9 (late 2014 launch)? Thanks.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
No - don't even have root for that device (4th gen HDX). Nor is it likely IMO.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] qingtest:
Thank you. Working pretty good. Firstly seems not able to use Titanium Backup (sdcard failure something), later now recheck its all fine!

I was not able to pair my bluetooth speaker with the lateset CM12 ROM & SlimLP ROM. After I refreshed this CM13, there was a failure at first time but then a 2nd time was working.

Great work!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
i am extremely interested since my fire hdx seems to have some problems in the system partition

so if i wanna repartition my device without any oversize that what would i do?

how do u start parted and mke2fs? i can boot into bootloader and recovery
[Kindle Fire HDX 7" & 8.9" Original Android Develop] CrashThump:
These tools are included and can be used through ADB under TWRP, also we have a e2fsck.

You better have to know what you're doing to not to brick your device by removing a sensitive partitions.

I doubt that your device really needs a repartitioning.

Since this task is topic-unrelated, please post your question including the simptoms by creating another thread and post me in PM.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cocoon4u:
Hi!

If I download something with the web browser I get FC. Downloading the same via app ES Explorer works well.

This happend to me since version 2015-12-16. Does someone else has the same problem?

Edit: Problem has gone after last update 2015-12-23. thx ggow
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
New Build is Up

- Dated 23 Dec 2015

- Change log on Post #2
[Kindle Fire HDX 7" & 8.9" Original Android Develop] itsmeinarizona:
Dec.23.2015 build looks good. Youtube starts but doesn't connect .... says "Retry an error occurred".

But overall .... very nice!!! Thank you.

---------- Post added at 07:42 AM ---------- Previous post was at 07:20 AM ----------

Google Play video app does work.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- that's strange

- I tested YouTube and Netflix again with the latest build and it seems to be working fine here

- I did not however test Google play video
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Common issues with all custom ROMs for this device (most Amazon tabs) due to non-standard hardware and/or interfaces. Comments/workarounds:

- AFAIK no cover art solution for Amazon Instant Video; everything else works

- Several Xposed modules effectively deal with rouge rotations; I use (paid) 'ownorientation' on Lollipop+; there's a free alternative (sans UI) from same author

---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------

Do a thread search; several workarounds posted with variable results. Seems multiband APs are a contributing factor. Be sure bootloader is at v3.2.3.2; see Android Development thread for patch.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
WiFi issues are being looked at in Android 7.1 prior to any Alpha releases. Specifically the connect / disconnect issue as well as a hard time joining networks.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] norritt:
Thanks, I am searching for this path. Regarding the HDX Bootloader: I have TWRP 3.0.2.0 - how can I find out the boot loader version? Can I flash 3.2.3.2 even though I have a higher version?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Bootloader and recovery are different things. Follow the instructions in this thread to insure bootloader is on version 3.2.3.2. I would not flash it w/TWRP. Unfortunately, there is no way to query the bootloader version (directly or indirectly).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] norritt:
Hi,

Thanks I did that and then also added a static IP instead of DHCP. Now wifi drops not every second but like once every 40-60 seconds. Still not perfect, especially when streaming video. Are there other real solutions to this issue that you can direrct me to? I could not find any solution via search for our tablet.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
In addition to setting a static IP have you tested for and/or taken action to further isolate the problem:

- presence of a dual band AP; move to a location (eg: coffee shop) with only 2.4Ghz WiFi

- uninstall SuperSU (CM will default to native privacy/root manager)

If still no joy consider flashing CM 12.1 that does not share the WiFi issue. Adding Nova, Xposed, GravityBox, Greenify and (optionally) a few other well regarded modules yields a device that emulates CM 13 in appearance and functionality. Fire Nexus (MM build) is another option.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] p-4:
Thanks to all the people who are developing this rom.

How much time do you need to convert the stock android cyanogen rom to the Fire HDX?

I am interested in learning how to build a rom. What is the best way to start?

Till now I never developed something for android, but i am familiar with Java.

Thanks a lot

p-4
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cyablo:
Anyone tried the 4.12. Build? Is the boot Problem fixed here?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jore011:
against only boot logo :(
[Kindle Fire HDX 7" & 8.9" Original Android Develop] MrPuddington:
Bugs?

First of all I think it is great that we a have a CM ROM - it just provides so much more especially in terms of apps than the obsolete Kindle firmware.

That being said, I do have a number of problems, and I wonder whether they are something that other people experience, too.

1. I tried an update from 20160929 to 20161118, and it would not boot. It seems that is a common problem? Any idea which ROMs are good and which ones to avoid?

2. The GMail does not work for me. It checks my email, notifies me of new email, but when I start it, it is stuck at the setup screen. I reinstalled GMail, and that did not fix the problem. Is it gapps related?

3. As observed by others, 3G is not working.

4. I also get very high battery drain - 24h of idle seem to drain the battery, and even turned off the tablet still seems to drain. I guess that could be a driver issue, but I have no idea how to investigate it further.

Still: yeah for finally breaking out of the walled garden!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
- avoid CM 13.0 for now; as you observed nightly builds are problematic

- CM 12.1, Fire Nexus 6.x and AICP are all fine

- 3G only supported by KitKat roms (FireOS, CM 11 or HDX Fire Nexus)

- high battery drain is atypical and symptomatic of ROM misconfiguration

- most Google apps, including GMail, work fine with proper GAaps package

Some of the symptoms reported suggest Safestrap v4 may be in play. Just to confirm, bootloader is unlocked and you are flashing ROMs from TWRP.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] blade22:
i flashed the 04-12 (latest) build today and its stuck on CM boot animation (blue CM head logo)

whats the problem ?

I am using unlocked bootloader
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Do you search the thread or simply look back a few posts? Nightlies are broken and have been for several weeks.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] MrPuddington:
Thanks for the replies. Yes, it is unlocked, and all installed with TWRP. I had some difficulties with the gapps package, so maybe I should revisit that step to get GMail working. And I will check whether I can figure out the battery drain - it is always possible that it is caused by certain apps.

KitKat is an option to consider: all my apps are fine with it, and if it gets me working 4G, that may be worth it.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] blade22:
Thank you, coming after days :eek: missed the posts
[Kindle Fire HDX 7" & 8.9" Original Android Develop] impact79:
Hey guys,

how long does the first boot into android take after flashing CM13? I can see the CM boot animation pulsing but nothing goes forward ?

Please help

(Device is unlocked, did a factory reset before flashing)

---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------

Ok, understood that nighlys are broken.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
- suggest Nexus 6 (MM) or CM 12.1 (LP) as alternatives

- a 'factory reset' in TWRP does not wipe all important system partition

- in general should always wipe system partition when switching roms

- data partition can be left intact for 'dirty' updates to current rom

- did I mention wiping the system partition ... :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Another update:

Sorry for the delay on the nightlies fix. The previously posted fix is too difficult to implement in cm-13.0. Which is effectively in stable release mode at this point.

I was busy this last week with work travel, so I'm back to finding a suitable fix this week.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] MahmudS:
Last working CM13 builds

Apollo: https://www.dropbox.com/s/x42vd1och6wq59u/cm-13.0-20161108-NIGHTLY-apollo.zip?dl=0

Thor: https://www.dropbox.com/s/d2fx3u9mc7pemsa/cm-13.0-20161107-NIGHTLY-thor.zip?dl=0
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Anyone know of a decent hosting site nowdays? I cant seem to get Android File Host to create the Fire HDX 7 device.

I have a build of cm-14.1 for Thor that I've been testing for the last week. Just not sure where I should upload it.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] KevinX8:
I upload all my files on Google Drive, mega is also quite suitable
[Kindle Fire HDX 7" & 8.9" Original Android Develop] blade22:
a new nightly build 12-12-2016 is available in https://download.cyanogenmod.org/?device=thor

is the boot issue fixed ?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] KevinX8:
It's a build bot making them, if you don't see any announcements here then it's not fixed
[Kindle Fire HDX 7" & 8.9" Original Android Develop] thomas.magnum:
Nope, tried it - doesn't work.

And obviously, updating from 2016-11-07 to any later update does not work either...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stangri:
Not sure how different the devices are in terms of CM implementation, but if you have a cm-14.1 build for apollo, I'm willing to be a guinea pig.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
It's up - check CM 14.1 thread.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] thomas.magnum:
I have two HDX 7" used by my kids, primarily as eBook-Reader, but there are as well some apps assigned to the kids' profiles. Under FireOS I was able to setup restricted profiles, which I assumed was a native Android feature.

After hours of rooting and bootloader-patching I recently was able to move from FireOS (4.5.5.1) to CM. I started with CM 12 and was surprised, that setting up profiles is possible, but there seems to be no way to setup restricted profiles. Same applies to CM 13.0, so finally I had to go back to use a Kitkat based system. After some research story seems to be, that starting from Android 5.0 restricted profiles are only available for tablet and NOT for smartphones.

Finally my question: Is there a way to enable restricted profiles in CM12 or CM13 out of the box? If not, are there any plans to support restricted profiles in CM for the Kindles (which for me are rather tablets than smartphones) in future?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
With the recent release of CM 14.1 for HDX prior builds (CM 11/12.1/13) will likely see few (if any) changes beyond security updates. At some point those may stop too. Development resources are simply spread too thin.

I too have noticed most/all custom ROMs for this device sometimes take on (report) phone vs. tablet characteristics regardless of values set in various build.prop entries. This is most noticeable in display characteristics such as the number of columns used for settings. Appears it may impact restricted profiles as well.

Suggest trying CM 14.1 to see if the behavior persists. If so report findings in that thread for possible consideration by the developers/maintainers.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
It's been a long time since I used FireOS to any extent. When you say restricted profiles are you referring to a user mode where they cant make modifications to the device? vs. normal profiles which control sounds, etc.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] thomas.magnum:
Well, long time ago since I set this up on FireOS. The feature is quite similar to Android 4.4 / Kitkat. Main feature is, that you can directly assign apps from the "main" profile to the restricted one. No need to give the restricted user access to the app store (no clue if that would work anyway).

For the currently available 12.1 and 13.0 builds for the HDX 7" restricted profiles are not available. You can setup a new user profile, but you would need to

login to the app store

download all app required

disconnect the app store

remove all standard apps (like browser) from the profile to disable internet access

Restricted profiles are the (almost) perfect solution if someone wants to make the tablet available to younger children i.e. as an ebook reader or remote control on the music library (Sonos).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] thomas.magnum:
Fully understood. My question was more in the direction, if there might be a switch to enable this feature deep down in the configuration files of CM.

I'm a rookie in this topic, but do I understand you right, the the devices themselves decide, whether they are smartphone or table once CM is installed? Isn't there a way to override this? As I understood in an other discussion, the "regular" Fire (non HDX) does support restricted profiles under CM, so isn't there an easy way to enable this for the HDX by a simple configuration change?

I'll will do that, but as the device is heavily used by my kids, I'm pretty reluctant to move to this quite early release...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Elaborating on my earlier response there are various build.prop entries (eg: ro.build.characteristics) that are used to distinguish device type. However, Google APIs often ignore those entries and make a determination of device and/or characteristics using unknown means. Not sure custom ROMs can overcome this behavior without extensive tweaks. I invested a fair bit of time looking for solutions w/o reward. Even resorted to quietly whispering to my HDX as it slept ("you're a tablet darling...not a phone"). Still exhibits schizophrenic identification behaviors. Most of the time tablet dominates but the recessive phone side surfaces with some regularity. Has become one of unique characteristics of this device that distinguish it from run of the mill Android gizmos. :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Weicheng_Gao:
Can you add download link to the latest available (no bootloop) build in the OP? It can not be found in cyanogenmod download page.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Changes coming shortly (next 24-48 hours). For now you can grab the last working builds from here: http://xdaforums.com/kindle-fire-hd...3-kindle-hdx-2015-11-29-t3259732/post70039742
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Final builds are Up

- CM-13.0 is now considered legacy because we now have CM-14.1 as official :)

- Final working builds are now linked in the OP from this post

- Also changed the OP title to reflect

- Enjoy CM-14.1
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Zathor:
I did a full wipe in TWRP (incl. system) and installed the latest apollo nightly (cm-13.0-20161108-NIGHTLY-apollo). Afterwards I tried in several ways to install "Play Games" but I always get an error -505. In the CM 14 thread I saw that modification of the OpenGapps package may help. However this failed :( Any help is welcome!

What I tried:

- open_gapps-arm-6.0-full-20161217: insufficient disk space (was expected, but worth a try)

- open_gapps-arm-6.0-mini-20161217 + installation from "Play Games" within CM: -505

- open_gapps-arm-6.0-mini-20161217 incl. playgames-arm.tar.lz + "playgames" to the mini section of installer.sh: not installed in CM, try to install it within the store ==> -505

I have to search for the logs. As I asued sideload they may not be available. Maybe time to flash it from sdcard.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
What happens when you attempt install (sideload) Google Play Games from APKMirror or another trusted apk download site? This is the standard workaround for Play Store -505 errors.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Zathor:
My bad! I did not thought about that option before and my google searches did not reveal that (wrong buzz words likely) :(

Yes, it indeed works. Thank you very much again for your continuous support for the community!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
CM13 is now half dead (no more security patches for Marshmallow), but I'd still like to ask if the previous bootloop problem for 11/07+ nightlies can be resolved in a way. I need Xposed and CM Theme Engine so I have to stay on this for some time, and I build CM/Lineage for my own devices on a monthly basis, so applying patches isn't a problem.

[MENTION=4243514]Hashcode[/MENTION] previously posted this (https://review.cyanogenmod.org/#/c/174077/), but from the review it looks somewhat WIP and I can't determine whether it's ready to be applied... It doesn't hurt to try though, and I will try picking it, making a build and report back.

Sent from Google Nexus 6P @ CM13
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Appears I'm missing something. Static builds linked in OP (20161107) are known to work; no bootloops. Are you having trouble with one of those?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
Not on your end - as a flashaholic, I just want to keep the underlying CM features up-to-date and also take any security patches that comes monthly (as of now we're missing Nov and Dec patch sets).

In other news, the build process is going smoothly so far and is coming to an end as we speak. I'll see if it results in a booting build, and if it does, I'd share it on my AFH.

EDIT: No it doesn't. 3 hours gone to waste :/

Sent from Google Nexus 6P @ CM13
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
The common developers/maintainers have indicated their intention to focus limited resources to CM 14.1. Understand your rational for remain on CM 13; I'm sticking with CM 12.1 for similar reasons. Neither legacy rom will receive much (if any) love going forward. At some point we will all be on LineageOS.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Lineage 13.0 is Resurrected

- Dated 16 Jun 2017

- Upstream LineageOS tree

- Device tree will be updated at some point this week

- Kernel updated will be incoming as time permits

- Maybe an ideal way for anyone wanting to run Xposed.

- I have placed the downloads in the same buckets as Lineage-14.1
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Woohoo - a fresh Marshmallow build for us Xposed junkies! Popped this in about an hour ago on a fully wiped Thor. Initial findings (some really good news here):

- installation (ROM, GAaps, Xposed Frameworks) and initial boot/setup were smooth and error free

- soft reboots (bypassing bootloader) occur in <15 seconds ... fast!

- wifi connects quickly and has remained stable in my 2.4 GHz only environment; will test 5 GHz later

- rotation functions reliably (0, 90, 180, 360) recognizing native landscape is 180 'off' on ALL HDX devices

- bluetooth works!! Successfully connected to keyboard (required pin), speaker, and wireless buds

- camera works!! Native camera app wouldn't connect but Open Camera does; images were plenty bright - even in a low light

Google Play Store is throwing up faux app compatibility barriers; have to fiddle with build.prop tweaks to get around that (already tried changing 'ro.product.model' to KFHDX; no luck). This is not a big deal as I can easily sideload.

I am looking forward to playing with this exciting build. Got a busy week coming up so updates may be a bit slow in coming. Thank you, [MENTION=5749760]ggow[/MENTION] for resurecting this wonderful addition to the HDX ROM barn.

Side note

: Unfortunately (for me), the debilitating 'Select SIM Card' bug from CM 13.0 carried over to Lineage 13.0 (not present on 14.1) when using certain messaging apps. Obviously no SIM option on WiFi only devices. This glitch first popped up in CM 12.1 and was quickly corrected. As CyanogenMod began to unravel in 2016 the branch owner declared the regression would not be addressed without further explanation. Admittedly there are not a lot of WiFi only devices in the marketplace but it also hammers mobile devices that do not have a SIM installed for whatever reason. Without a resolution means this ROM can not become my daily driver although I hope to get good use out of the device sans messaging client.

Edit

: Most of the CyanogenMod forums are now dead; however I found the following which suggest there may be some hope if these newer builds got ported to Lineage:

Source: https://www.tapatalk.com/topic/4119...card-message-in-hangouts-with-newer-nightlies

Just a quick update on this item in case anyone else has the issue. I have now updated to the 13.0-20161031 nightly and I am now able to send SMS from Hangouts - Google Voice without a SIM card installed. I will post back if this changes but as of now it seems to be working again in the newest nightlies
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I'll look into the the Select SIM Card bug for the next release. Can you give me the name of a messaging app that shows the behaviour?

EDIT: Will try hangouts app

EDIT2: Tried hangouts, wasn't able to reproduce the issue. CM-13.0 + Latest OpenMiniGapps which includes hangouts app
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Sorry for delayed response. I use a carrier specific client (Verizon Messages+) but the 'Select SIM Card' pop-up behavior can easily be observed with the Android Messages app by Google. After installation simply compose a SMS message to a phone number or anyone in your contact list. The SIM pop-up will appear immediately after the cursor moves into the message input field.

I've tried numerous build.prop tweaks to no avail. The code appears to be baked deep into CM/LinOS 13.x core and is beyond the reach of Xposed and other standard SIM selection mitigations.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Curious if the select SIM pop-up is reproducible? It is on a pair of thors in my HDX inventory; I assume the same thing would happen on any WiFi only HDX.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Yes it's reproducible here too.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Thanks. Seem like a tough nugget to crack as I was not able to identify any workarounds from others who ran into this obstacle on CM13.

Wonder if ACIP would make a better base for those seeking Xposed compatibility. I'll try to flash over the next few days to verify proper behavior on WiFi only devices. So far no complaints from users of this ROM.

Guessing the effort to resurrect Nexus exceeds potential benefits (kernel testing for LinOS 14.1) and available resources.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
New Build is Up

- Dated 17 July 2017

- Upstream Lineage Updates
[Kindle Fire HDX 7" & 8.9" Original Android Develop] schr01:
I flashed the New Build, but after the the reboot it hung in the boot animation logo.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Albert Poon:
Bootloop.

TWRP 3.1.1-1, Cache/Data/Dalvik wiped, MD5 checked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Can you send me a logcat of bootup?

Is this Apollo or Thor?