yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Fallingwater:
I have a Thor with its cramped screen on which I just installed CM13. It seems to work perfectly fine (I don't care about the selfie camera that's the only one the Thor has), but is there anything I can use that'll work like full!screen? It worked fine in Nexus/JB but it misbehaves on CM13 and ends up crashing the touch interface. It really is an absolute must for me, I can't stand the soft button band at the bottom and used the tablet in fullscreen mode 99% of the time.

Edit: I've discovered the expanded desktop feature which removes the system bars; however, when it's active there seems to be no way of using the buttons without deactivating it, whereas full!screen placed them on the corners for easy access.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] MahmudS:
but Amazon has Saturn (8.9 4th generation) with FireOS 5, and, as I see by motherboard, same cameras
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Maybe, but they are built for a different soc (processor) and not interchangeable. I have already tried to use the binaries in different combinations from the Saturn ROM.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Try sliding up from bottom to momentarily expose soft buttons and status bar. If this proves unsatisfactory there are a handful of Xposed modules offering different interpretations of "immersive mode". Start with Gravitybox and move out from there. I believe CM 13 also offers some immersive customizations via the settings panel and/or under developer options (don't have a CM 13 device available at the moment to check). Bottom line is this is not a HDX build issue IMO, just CM being CM.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Fallingwater:
Sliding from bottom gave me exactly what I needed, I don't think I'll need further customization. Thanks and yeah, I get the hint, I'll stop polluting this thread with non-HDX related requests.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Fallingwater:
Problem (relevant this time): it's not connecting to my Jam Classic bluetooth speaker - in fact, it can't even see it in the available devices. I've tried with another, much older speaker I have (generic Chinese "BBQ" speaker) and it doesn't see that either. I didn't expect this since the progress table in the first post specifically mentions bluetooth speakers should work.

I've tested bluetooth connectivity and it connects flawlessly to my cheapo brandless keyboard, but it doesn't want to know about bluetooth audio any way I spin it.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Nice catch. See OP for proper reporting/tracking of potential bugs.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Soulreaver1993:
Hi, will you create an Android 7 for the Hdx7?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
CM 13 (Marshmallow) just became available. Nougat in time...perhaps. Not even generally available yet. Plus need an Amazon device with A7 for a binary starting point.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] n1cklan:
Snapdragon 800 doesn't support Vulcan, so Android 7 makes no sense
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Android 7 will be coming to Apollo and Thor. The vulkan API is an optional element.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] therealisttruest:
CM 13 and Play Store

Hi,

This my first post here but I wanted to say a couple things and ask a couple almost newbie questions. I am pretty technical though as an analyst and developer, just not yet so much with ROMs yet. So here goes. Firstly THANKS for the work you've done with CM 12.1, Fire Nexus, CM 13, and the new bootloader unlock method. The new bootloader unlock is the original reason I created an account here, just to simply say thanks because that allowed me to finally stop using Safestrap and try these CM ROMs. Yay! I just got this Apollo tablet a few weeks ago and wasn't trying to get used to the Amazon ecosystem, which led me here to get an Android ROM. I'm definitely looking forward to seeing a Nougat ROM come out at some point too. In the meantime, I have a couple issues with CM 13 on Apollo that may or may not be part of the ROM. Just let me know if this isn't the place for the following questions and I'll kindly pursue other fixes elsewhere.

1. Using this CM 13 ROM, the Play Store tells me "Your device isn't compatible with this version". I'm not totally sure, but it seems to be related to location functionality. A few examples (I'm also a weather geek) - WeatherBomb, Weather Underground, Storm, and Starbucks. These are all available with CM 12.1 and were also with the Nexus version. I've tried adjusting build.prop, tried adding files from those other ROMs to /system/etc/permissions and still am having no luck. Also, I have an S7 with M on it and do have those same apps installed without issue so it's not a version issue. Any ideas or fixes coming soon?

2. SuperSU seems to cause my wifi to get really flaky. It tries to reconnect but fails consistently to get an IP. If I just flashed the ROM and GAPPS, then I never have any issues connecting. It's only after I've flashed SuperSU. This is probably a SuperSU caused issue, so feel free to tell me that I should go that way to look for an answer to this question. But I think I saw somewhere that people with dual band routers might have issues with the ROM. I do have a dual band router but there are no issues with this ROM unless I've flashed SuperSU. I can also then 'uninstall' it in Marshmallow and make the issue then go away but it's odd.

Anyways, thank you, thank you, thank you again!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] therealisttruest:
Well it looks like I was on the right track so I now have one less issue and am even happier with the CM13 ROM at this point. I'm okay without SuperSU for now. For the above issue, I copied these two files into internal storage from the 12.1 image I had in /system/etc/permissions:

android.hardware.location.gps.xml

android.hardware.compass.xml ( I probably didn't need this one but oh well)

Then in TWRP Recovery, did a little command line magic after also mounting /system like this:

cd /sdcard

cp android.hardware.* /system/etc/permissions

cd /system/etc/permissions

The next part I hadn't previously done before but is essential apparently:

chmod 644 android.hardware.location.gps.xml

chmod 644 android.hardware.compass.xml

Now my location based apps that I could not download in the store are downloadable and working. Woohoo! Hope this helps someone else if they've come across this. Might want to add gps.xml to the nightly if possible.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sergtot:
Could you please upload here your gps.xml file?

I want to try that solution too.

File from Nexus 5 AICP CAF didn't solve the issue. I need original one.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] WW3:
Yah, could you post those 2 files here, I'm having same issue downloading some apps.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] therealisttruest:
Again, these came from the CM 12.1 ROM I had previously flashed so I'm not sure they're original or what but they are attached. I tried copying them before and it never worked until I also changed permissions to match the other .xml files. And, to reiterate, the apps I was missing all had Location functionality so logically it seemed like the gps file was the missing one. I really don't think compass should fix the location based apps, but it might have an affect on apps that need compass functionality. There are other differences between the CM 12.1, ggow's Nexus HDX ROM, and CM 13 so perhaps copying other .xml files would help.... or cause other issues. Just make sure the permissions are correct, otherwise it won't help and might break everything as it did for me a few times. I must've flashed between CM 12.1 and 13 a dozen times in the last few days before I tried adjusting permissions also. Anyway, I'm no ROM developer so use at your own risk, make sure you have a back up first, and good luck!

Edit: Also make sure you delete cached data for the Google Play app. I did this before rebooting into TWRP, then copy files, then booting and trying again.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] wuith:
Thank you very much for this rom! Now that I was able to unlock the bootloader of my Thor I moved to this Rom!

I decided to use the built-in superuser. Any reason why it is suggested to use SuperSU in the installation procedure?

For people having problems with amazon apps for me changing the following values in the build.prop did the trick. Then the device is recognize as a Nexus 7!

ro.product.model=Nexus 7

ro.product.brand=Google

ro.product.name=nakasi

ro.product.device=grouper

ro.product.manufacturer=Asus
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
No liabilities and arguably some advantages to using the integrated (and proprietary) CM root manager. In contrast, SuperSU works across a broad portfolio of devices/roms and it serves as a familiar thread for both developers and users. I use both depending on device and intended usage.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] murso74:
Can I not install Instagram from the store because it's seeing it as a tablet or for another reason?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Håvi:
Anyone lese having the problem that after you take a picture, you get a notification that says, cannot connect to camera? Using Apollo device.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jeryll:
Yes, my problem too, Apollo 32gb - tried several nightlies, same result, cannot connect to camera ...

Still, this is for me THE best modern ROM for HDX so far, battery friendly, so thanks [MENTION=4243514]Hashcode[/MENTION], [MENTION=5749760]ggow[/MENTION] for your hard work...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] hgthanh:
Hi Guys! :o

I just flash CM13 on kindle fire HDX7 only wifi.

Every thing great, but camera front error. It notification " Can't connect the camera"

Please tell me how to fix?

Thanks guys.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] n1cklan:
When will be stable version of this CM13?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
What if we say "never"? Have you ever seen a CM build marked "stable" since the days of CM11?

Sent from Google Nexus 6P @ CM13
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Developers will work on issues as time permits. Might be tomorrow, might be never. Pestering for timelines doesn't help. Read the OP to report bugs.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] preisl:
Hi,

I can confirm, that copying these 2 files to /etc/permissions will enable more apps in Play Store. I just used Termux to re-mount system r/w, copied the files to /etc/permissions, changed owner to root.root and set 644 perms. After re-flashing the latest snapshot (cyanogenmod recovery doesn't have a dedicated wipe cache/dalvik entry) and clearing play cache I was able to install Google Inbox :)

Also testing the Wifi instability fix (have this one as well) by removing SuperSU and using CM builtin root, but it might take a while to get some results ...

BR,

Martin
[Kindle Fire HDX 7" & 8.9" Original Android Develop] therealisttruest:
Ahh, Termux, that's a good tip too. For some reason terminal did not occur to me. I guess I just felt more comfortable running terminal from TWRP figuring if I broke something there I could undo it in a hurry. On another note, I ended up using Wifi Manager from the store as a sort of workaround for the wifi issue. It still drops from time to time but WiFi Manager still shows my access point (unlike the default wifi management) so I can instantly just pop back on. It might only drop once or twice a day so I'm perfectly fine working around things as necessary. Overall this ROM is pretty solid, not flawless, but solid. No spontaneous reboots, no garbled graphics, everything important to me anyways works. That said, if something annoys me enough and I find a solution I'll continue to contribute as I"m able. But I don't think I have any new issues that aren't already known issues so the OP is a good reference point of known issues.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
+1. Long time user of WiFi Manager on several devices. Streamlines AP switching when moving around various properties circumventing 'sticky' receivers that cling on to marginal signals that can slow web pages and buffer video. This tool is actually a side show to the developer's primary app, AquaMail, which is hands-down the best Android email app for those who need a full featured product that interfaces with virtually any service/server. Great support too as evidenced by the active user forums dedicated to this product. Sorry for the shameless promo; author deserves an occasional plug (ok...I'm done).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
hey in the latest nightly, The screen rotation does not work. How can I fix this?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Works fine here. 20160928-nightly-thor
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
iam on apollo, now i will test it on thor :)

edit: today i flashed apollo and thor

apollo from 3.x and thor from 4.x

installed cm with latest twrp => on thor screen rotation is working fine, on apollo doesnt work... seems like cm related or?

seems like none of my sensors are working light screen etc... when i debug senors it shows none ^^ wtf

do u need a logcat?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Fire Nexus -> CM 13

FWIW - My primary HDX was still running Fire Nexus with plenty of customizations (apps/kernel/settings/system/Xposed/etc) that had evolved over time. I was dreading a clean install but knew my KitKat days were numbered. On a whim I dirty flashed CM13+GAaps (nano) with minimal difficulty following a brief set of sensible preparations. Booted on the first go-around and immediately had a usable system. Took about an hour to adjust for various app/settings/Xposed and AOSP->CM differences but ALL of my apps and personal settings remained intact. Not a journey I would recommend for most (clean install is much safer) but shows it can be done.

---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------

Thanks for reporting. I'm not the developer/maintainer so can do little to help. Suggest reading OP and then post a formal bug report as suggested. I believe there are others using this ROM on Apollo so could be a nightly glitch or (less likely) something peculiar with your hardware. In the past Apollo has experienced more rotation issues; obviously something different with the sensors and/or reporting mechanisms.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
thanks i tryd all nightlys for apollo with no success,

thor works fine and snappy

do you know how can i install stock amazon os? revert all my changes? wanna test sensors at original firmware ;)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Thoughts:

- on Apollo try flashing 3.2.3 bootloader update which addresses some display glitches (typically not rotation). Most easily done via fastboot or Flashify

- wipe system/data/dalvik/cache and flash a modified FireOS v4 image from here to return to stock; bootloader will remain unlocked
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
haha now i bricked my device

damn i stuck at amazon boot logo

i cant goto twrp with volume+ and power

saw my device in adb as offline

now i will try a script in linux or do u have any sugestions for me?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Yikes! Take a peek at these posts/threads:

http://xdaforums.com/showpost.php?p=64452651&postcount=1

http://xdaforums.com/showpost.php?p=68742099&postcount=1

Objective is to get TWRP reinstalled so you can rebuild device. There's a way to do it via fastboot but the details are beyond my pay scale. Perhaps [MENTION=5594063]ONYXis[/MENTION] or [MENTION=5828306]draxie[/MENTION] can help.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
thanks for your help found these threads before

do u recommend twrp 2.8.5 or 3.x?

thank good for my fastboot cable i used it serveral times and it helps me out of the **** haha

now i will flash stock rom and try it again

thank you Davey126 for your fast help and support

the screen rotation is bootloader relatet...

after i recovered my device i made a test installed 3.0 => root cm etc doesnt work

installed latest breakable bootloader 3.2.3 works fine!!

i think you should add this to the required stuff for this rom! ;)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
At present I am recommending TWRP 2.8.7.x as there is a problem with the posted 3.0.2.0 build (error 7 when flashing some roms). 3.0.0.1 and 3.0.1.0 also work fine but are not immediately available for download. Go with 2.8.5.x for now and upgrade to the successor to 3.0.2.0 when it becomes available.

Interesting your cable worked for recovery. Factory/fastboot cables are almost totally useless on HDX devices with locked bootloaders. Something to keep in mind; I may have to adjust my guidance regarding such cables. Thank you!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
ok i read the whole thread but i cant found play store error 505 i looks like permission error or device isnt compatible do you know something about?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Error 505 is common with custom ROMs on Amazon devices and is most frequently seen attempting to install Google Play Games and associated titles. Best option is to sideload GPG from here and address individual titles on a case-by-case basis. There is guidance on tweaking device properties in build.prop a few posts back which has not proven especially successful on other ROMs but may work better with CM 13/Marshmallow. On my list of things to try ...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I have posted links to the 3.0.0.1 version until I get time to look into this.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] preisl:
Best way to work around small system partition?

Hi,

while switching to CM13 I tried to find a good work around for the small system partition issue, so I tried:

Flashed micro gapps instead of stock. That wasn't really the best idea, as some google apps fail to install from play store (like Google Play Games) and some don't work properly (like Maps or Keep).

Resized the system partition. That was a rather straight forward thing to do, however, whenever I flash CM (or any updated version), it "virtually" resizes the system partition to 1.2GB. So the partition itself was still 3 GB, but "df" showed 1.2GB again. The resize partition option in TWRP fixed that, but doing that after every update is a bit cumbersome. Why does installing a new snapshot change that visible disk space?

Flashed stock apps and excluded apps I don't need - that is for now the most easiest way. It was just a bit challenging to find the (for me) correct list of apps to exclude

so my personal preference would be to resize the system partition, but it seems, that the current flashing "workflow" is not designed for that.

Cheers,

Martin

P.S. btw. wlan is now perfectly stable after removing SuperSU - so thanks again for that hint.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Thanks for the details. With CM13 and nano GAaps I still have 455MB free. All Google apps obtained from the Play Store work fine including Keep and Maps. I found flashing GAaps seperate from CM12 can lead to issues; might extend to CM13 too. I wouldn't want to see the system partition enlarged unless the space was taken from cache which is ridiculously large (1GB) and typically 95% unused. Respecting existing partition sizes would be nice rather than "virtually" resizing back to 1.2GB.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] preisl:
Actually I had that 505 (or was it -501?) error when trying to install Google Play Games - installing it as system app with OpenGapps worked just fine. With Keep and Maps the application itself started, but it asked me to configure / select a Google account, when I chose the account used on the device, the apps crashed. Again, the OpenGapps flashed version didn't show that behaviour.

I just removed the latest 2 partitions (I think 22 is system and 23 data) and shrinked data. I have the 32gig version, so I didn't care to loose 2GB from the data partition.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Yep - 505 errors are pretty common with Google Play Games across a variety of devices w/custom roms. Typical solution involves sideloading GPG from apkmirror when flashing a larger GAaps package is not an option. The Maps/Keep behavior you observed is strange; never had that happen to me but I dirty flashed CM 13 on this device so possibly would have been bitten on a clean install. Didn't happen with clean installs of Nexus or CM 12.1 on this device.

Looks like you are all set. Think the best long term solution is for the installer to respect existing partition sizes offering flexibility to those who have desire/skills to tweak layout detail.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] matt_2_27:
I just flashed twrp using the 1 click unlock method and wiped my hdx thor that was running cm11 and flashed cm13 and opengapps. Everything is working great except for my GPS. GPS worked fine in CM 11. I tried therealisttruest's idea in post #610, didn't work. Help?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Not surprised; LTE is shown as 'not working' in the OP feature matrix along with some other detail around location packages. LTE and GPS hardware reside on the same SOC. Based on scattered user reports (dating back several years) when one isn't working usually the other isn't either. The matix shows GPS works but I strongly suspect that is the 'fused' location offered by Google Location Services. If hardware GPS and LTE are not working then that consists only of an approximation based on what Google knows about nearby APs.

I believe CM 11 and FireOS are the that fully support hardware GPS/LTE on this platform.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Anyone know of a solution to the "Select SIM Card" pop-up that spams some hybrid messaging apps like hangouts/gv and vzw messages+? Obviously irrelevant on a WiFi only device but a complete show stopper as there is no selection to make. Have to FC foreground app to regain control of device. Seems to have popped up in the July CM 13 nighties with no official resolution in sight (branch maintainer says he doesn't have time to fix it).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Nice device (Z2)! Your presence in this forum will be missed [MENTION=3370844]jeryll[/MENTION]. You were quick to help when I was new to Android (and in a deep hole) and later kept me honest when I said something stupid. Those early experiences were a significant influence in choosing to 'give back' to (some might say misguide) a small corner of the XDA community. It was pretty amazing getting meaningful assistance from a complete stranger.

No experience with nightly 20161005 but I did update to 20161001 via auto-update a few days ago w/o incident (Thor).

Take care,

Davey
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sergtot:
Thor nightly 20161005 was successfully flashed by the way.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sergtot:
I want to ask - does AudioFX somehow affect sound? I don't feel any difference applying any preset or tuning frequencies.

Thor, CM 13 20161005 and all previous builds.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Can not speak to AudioFX on this device (works on others) as I typically flash a Dolby ATMOS package on HDXs. Makes a significant difference although some don't like the exaggerated effects which can be easily tamed avoiding presets. A simple search will lead you to downloadable packages. Be sure to pick one that has an uninstaller.