yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Android Development] vasolini:
As far as a Marshmallow rom for Tate, these are it, but they are all pretty much in the testing stage right now. If you want something stable for now, there are a couple of good Lollipop roms, but I don't know which are still being updated. I personally use the ResurrectionRemix Lollipop rom. It's great on battery and very responsive.
[7" Kindle Fire HD Android Development] mikeataol:
just a few things I have seen , comparing this to the RR remix version to test.

there's definitely something going on when this rom goes through a reboot.

on a unit with cache and data formatted f2fs it boots to the CM boot animation, then back to the KindleFire boot screens, and then reboots properly

Ive wiped and installed more than once and have seen this behavior consistently

I had no luck trying to get any gapps installed , I think the known issues with gapps permissions havent made it to this build yet, so not sweating it.

(by that I mean: gapps installs fine but FC's on reboot dont seem to be correctable. I tried several opengapps versions and BanksDynamic gapps as well. Also tried a userinit.sh to add proper permissions to gapps.)

Wifi Is not as stable as the RRremix version. This rom will not reconnect to wifi on reboot, unless you go into settings for wifi, also consistent.

It's not terrible, but the other RRRemix ROM is closer to "done" IMO.

Thanks transi1 for all the effort .
[7" Kindle Fire HD Android Development] :
As discussed a few posts ago, this was caused by an upstream issue in CM and has been fixed for builds dated 3-29 and on. I tried the userinit.sh fix as well with the same lack of a result.

[MENTION=6751354]transi1[/MENTION] If you have time, is it possible to upload a new build that includes this gapps fix?

I experienced the same strange reboot behavior after initial flashing as well, but after the startup app upgrading prompt and device setup, it reboots normally as expected. As for wifi, I haven't been able to reproduce any issues that have been mentioned. The only thing that seems strange is that wifi turns off completely during deep sleep but this also happened in CM12 so I assumed it was to save battery life. Wifi always starts up immediately when I wake the device so it never bothered me much.

The biggest advantage to plain CM over RR is its simplicity. For greater customization RR is the easy choice, but not always the best for all use cases, so having the option of both is great.
[7" Kindle Fire HD Android Development] transi1:
build 20160404 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/a3lbccheuv9t4ab/cm-13.0-20160403-UNOFFICIAL-tate.zip

ps kernel 3.0.101+, HDMI-test, tested gapps: https://github.com/opengapps/arm/releases/download/20160315/open_gapps-arm-6.0-pico-20160315.zip
[7" Kindle Fire HD Android Development] mikeataol:
[MENTION=6751354]transi1[/MENTION] Thanks a lot for this . It has now supplanted the RR remix as the better of the two choices in my opinion.

Just as an FYI , I always load "No Frills CPU control" , and these run fine on 1500MHz as opposed to the default 1200MHz

I also load "Speaker Boost" (Omega Centauri Software) on these and the Nook Tablets. Not so necessary on the Kindle HD 7", but an ad-free volume booster that works fine.

------------ just a re-cap of what I know are outstanding issues, but it's still an awesome ROM :D

- initial setup got a little confused during adding Google account but skip through it after adding one and all Gapps seems fine.

- the default landscape orientation is opposite what it should be

- I don't believe any camera modules are loaded at all. can't interface any camera app

- the underlying OMAP drivers I believe still need work, not really expecting any further developments on that, but it would help this and the Nook tablet. ( I deduce this from seeing some chromecast enabled apps fail, and GoogleCast and native screen casting not working)

These are awesome devices with this rom , a binge watchers dream! as you can see is my intent below - :highfive:

Your work is appreciated, I see you juggling ROMS for a load of different devices, and I am grateful this is available.

M
[7" Kindle Fire HD Android Development] mikeataol:
regarding double booting - what I've seen consistently

If you are connected to a PC with working ADB, a reboot is abnormal.

it goes from the splash screens, CM boot animation , then back to the Kindle Fire splash screens, and then reboots...
[7" Kindle Fire HD Android Development] tatefan:
Boot time and wifi

I had installed this rom over cm11 on the tate. I had wiped caches and system.

I did not wipe data, surprisingly all went well and the rom works well, all apps remain intact

and working.I know the initial boot does take a bit(about 8 minutes in my case).

However, subsequent reboots take about 4 minutes, compared to about 1 1/2 minutes

in cm11. Could this be b/c I didnt wipe data? Anyone else experiencing this? I suspect

something is happening behind the scenes making the boot take so long.

Also, wifi still not working on reboot, have to toggle it on every boot.

I am using the 4/3 version. Still, great work on the rom so far Transi!
[7" Kindle Fire HD Android Development] Droidriven:
Read the ROM threads, they'll discuss issues and stability of each ROM. There may be discussion of which get updates also.

Ink'd from my KrAkEn'd S3
[7" Kindle Fire HD Android Development] :
All gapps packages should be working again, tested successfully with 3 April stock package. HDMI is working well again. Third party camera apps seem to be broken now as others have mentioned but I haven't tested it much, possibly due to newer kernel?

The 'double boot' does not occur after the first boot and initial install. The lengthened boot I've just now noticed and not sure if its new in this build since I always leave the tablet running and boot time isn't critical for me.
[7" Kindle Fire HD Android Development] mikeataol:
I'm seeing the double boot even after the first install, and I had one other totally borked boot, screen went totally static. Had to power down and restart.
[7" Kindle Fire HD Android Development] Droidriven:
I'm trying to flash LP and MM ROMs on my kfhd7 but no matter what wipes I use I keep getting this error:

Failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system

I'm assuming there is some kind of formatting or partitioning that needs to be done? I haven't used this thing in over a year so I don't know if there as any things I missed in development from then to now.
[7" Kindle Fire HD Android Development] skalnas:
I believe I had seen those errors in twrp 3.0 when I flashed cm13, however the ROM still flashed. Did u give it a few minutes to flash or would it refuse to flash? Also make sure if your on twrp to be using at least version 2.7. If u are u can try to mount system in twrp.
[7" Kindle Fire HD Android Development] Droidriven:
I saw a post about an hour ago in the CM12.1 thread that said it gives a mount failure but if you let it sit it'll flash.

I gave AICP a try with TWRP 3.0.0-0, let it sit for 10-20 minutes and when I checked it had flashed, just booted it, doing setup wiz as I type this.

Never had that issue before on any of my devices. I don't assume anything when flashing, when I get errors, I check them out thoroughly before trying anything else. I've only soft bricked one device one time, I've avoided bricks ever since then. I take my time and step carefully when flashing anything on anything.

Ink'd from my KrAkEn'd S3
[7" Kindle Fire HD Android Development] Droidriven:
Somehow this flash lost root.

I have root access set to apps and adb in developer settings, I've flashed SuperSU in TWRP and su binaries are in xbin but when I try to turn on root explorer in ES file explorer it prompts for permission, I grant access, I get the toast confirming the app has root permission but then right after that I get a toast saying this feature cannot run on your device.

I have SuperSU in system settings but when I first flashed SuperSU in TWRP and rebooted, SuperSU was in app drawer but after trying to grant superuser to ES file explorer the app disappeared from app drawer. When I open SuperSU it shows that ES file explorer has permanent permission but it still won't allow me to enable root explorer.

Ink'd from my KrAkEn'd S3
[7" Kindle Fire HD Android Development] tatefan:
I have read in the forums not to flash supersu for cm13, due to bootloops, however if you flash this supersu you should not bootloop:

http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[7" Kindle Fire HD Android Development] who444444:
thanks to those that figure all this out so someone like me can make it work. here is what I did. I was already on cm11 on my kindle hd 7 and using twrp 2.8.7.0

I used the files from post 94 of this thread. booted to recovery and backed up. then did a restore of the back up to make sure twrp was working for me.

next normal wipe in twrp and then install cm13. then boot into recovery (not system ) and then install open gapps. Then wipe dalvik cache then boot system.

I'm not saying this is the way to do it but this did work for me the first try. First boot did go from yellow fire logo to blue then yellow again and then long wait.....

then cyanogen boot started. (yes!) log on to google did act up so I skipped it at first. I had no problem signing on after first setting up the rest of the options of a first boot. Remembered to tap many times on build number (about tablet in settings)to allow developer options in settings menu. then in developer options is where you will find root setting with about four choices. Mine was already selected allow root for apps and adb. Did not do anything related to any su or superuser. when installing apps that need root the normal permission choice would come up as it always does the first time an app asks for root

Like mentioned no camera app seems to work but that is all that I have noticed so far. No problem with you tube ( i do use an older version 100506130apk ) or pandora18 apk, also an older version. wifi good, all and all great rom. Almost forgot, power on boot does seem to take about 4 minutes for me but most of the time I leave it powered up.

Thanks again to all the developers for all your work allowing me to make a 30 dollar e-bay kindle into a marshmallow tablet. (sorry about any bad spelling and grammar)

Now I have to practice my soldering so I can fix the loose usb port.:fingers-crossed:
[7" Kindle Fire HD Android Development] skalnas:
Pretty much what I did but didn't wipe data, boot is also 4 minutes vs 1.5 for cm11. Other than the long boot loving the rom
[7" Kindle Fire HD Android Development] ZeeJM:
Strange gmail problem

I'm having a strange problem with gmail on this build. Specifically, gmail doesn't appear to recognize any Google accounts configured on my device. I receive new email notifications and sync completes successfully, but I every time I try to open an email message I'm prompted to add an email account to gmail. I've added secondary gmail accounts but still can't get to my inbox. I'm able to use the gmail client with non-Google email accounts (such as outlook.com), and I'm not experiencing any other gapps problems on my device.

I've tried wiping my device completely and using different gapps packages (pico and nano) and different gapps releases (315 and 408).

Is anybody else seeing this behavior?
[7" Kindle Fire HD Android Development] mikeataol:
This worked for me just now

(probably not what fixed it because it acted exactly the same after doing these and a reboot)

removed my google account

cleared cache and data for

Google Play Services

Google Framework

GMAIL

reboot

and it was still broken

then

added my default gmail account back in to google play

tried gmail, still broken

after getting the "add at least one email account" on the "take me to gmail" screen

I added a second non important gmail account, and then the screen populated (strangely) only with the first one.

I removed the second non important one from "settings/account" , and it seems to work normally now.

went through a reboot and it still seems to have stuck.

edit : OH, and I went in to apps/settings/permissions for gmail and made sure the 3 that were turned off were all turned on....
[7" Kindle Fire HD Android Development] ipdev:
After trying a few different things. I got Gmail to work on my jem. (Haven't tried on my tate yet.)

It looks like just turning on "Contacts" under App permissions is all that was needed for me. (Wish I would have tried that an hour ago.?)

[Running ResurrectionRemix-M-v5.6.7-20160409-jem]

Note on my tate :

Only had to turn on "Contacts" - No other screwing around.

cm-13.0-20160403-UNOFFICIAL-tate & open_gapps-arm-6.0-pico-20160402

Installed Gmail from playstore, turned on Contracts under App permissions. Works fine.
[7" Kindle Fire HD Android Development] ZeeJM:
Thanks, mikeataol and ipdev. Turning on "contacts" permission resolved the issue for me.
[7" Kindle Fire HD Android Development] Maromi:
Micro gapps also will fix the issue but hate using it

---------- Post added at 03:50 PM ---------- Previous post was at 02:57 PM ----------

Performance wise f2fs isn't ART friendly. KitKat you could run art to use /data and/or /cache(ext4 is better) for dalvik-cache but if you used f2fs on the same partition as dalvik-cache performance was not great and reduced usuable space for /cache by about 120 MB.

Lollipop and above uses /data for dalvik-cache, while f2fs performs great on that partition with exception of dalvik-cache. Which leaves a pretty much empty 650 MB /cache partition in ext4 and 530 MB in f2fs.

Using /cache for dalvik-cache would restrict you on how many apps to install and performance would improve with ext4 but a way to get more apps to install would be running ART in interpreter mode.

If running f2fs on data partition with dalvik-cache best performance is ART in interpreter mode
[7" Kindle Fire HD Android Development] NewportShortie:
Please Help :/

So, I soft/hardbricked my kindle :/

What happened was I successfully got cm13.0 on my device but without root of course and needed root. So I followed this reply from r3t3ch:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.

Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:

Code:

echo SYSTEMLESS=false>>/data/.supersu

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Now... It LOOKED like there is a space in between the / and the . before supersu but there isn't as it came to my attention after the fact... because after I installed SuperSU from twrp and rebooted, my kindle is now in a bootloop.

I tried for 2 hours to reboot into twrp (doing the combo while the kindle is off) to restore to one of my backups but I cannot access twrp. The kindle fire logo pops up, stays on for about 6 seconds give or take, then goes to a black screen, then goes right back to the kindle fire logo again. I can't access TWRP and ADB does not work and does not see my device in windows. I am pretty sure I messed up my boot.img? Because the blue kindle fire logo does not come up anymore, just the orange one.

I am pretty sure my last chance now is to buy a fastboot cable and reboot into recovery that way? I am semi lost with all this and would love a response.

Thank you, and any help would be amazing
[7" Kindle Fire HD Android Development] ipdev:
Fastboot cable was the best $9 I ever spent on amazon. That said, disconnect the battery (or let drain). After a day or so reconnect the battery (or charge). Then you should be able to get into amazon stock recovery. - At least that worked for me.

( I would highly recommended any tate owner to buy a fastboot cable. - I thought it was mandatory.)

(Matter of a fact, I didn't realize you could get this far without one. Things must have changed in the last few years. )
[7" Kindle Fire HD Android Development] :
You're fine. As you said, soft brick from boot image being broken by supersu patching it. Easily recoverable with fastboot cable following steps I mentioned here. If you're not too impatient, the cheapest one from china I've found that I can confirm works is <$4 (ships via epacket so not actually too long a wait).

That command in twrp just creates a config file in the data partition for supersu with the line that gets echoed to it. To confirm it got created correctly, just do "cat /data/.supersu" in the terminal afterwards and it will display its contents. Also pay attention to the output from flashing supersu in the twrp console log where it says either "systemless mode" or "system mode". As long as you don't reboot yet you can always reflash a working boot.

He mentioned he has twrp which I think completely replaces amazon's stock recovery so I'm not sure how this would work. Draining the battery sounds like a bad idea since I don't think he'd be able to charge it again while it's still bootlooping.
[7" Kindle Fire HD Android Development] ipdev:
Where did I mention twrp?

Besides the point, twrp 2.?.? was installed. I ordered another tate, and while I was waiting for it, I reconnected the battery in my boot looping one to see what would happen. When I plugged it into a charger I got an amazon recovery screen. (Surprised me too ! Buy the way I have an extra tate that has been untouched since I got it. I charge it up every week.)
[7" Kindle Fire HD Android Development] Maromi:
If you want to use SuperSU instead of built in su

You can flash a SuperSU build that doesn't use systemless root for marshmallow

Then reboot

Download the SuperSU app from playstore and update thru the app

Or enable su from developer mode and use supersu app from playstore to update
[7" Kindle Fire HD Android Development] Sid.G:
Can multi-users be enabled in this cm13 tate build ?

Can multi-users be enabled in this cm13 tate build ?

I tried the Xposed module - link - androiding (dot) how/enable-multi-users-lollipop-marshmallow/

and manually editing the build.prop

In both the cases the 'settings' app crashes when I select add a new user.

Anyone else had any success with this?
[7" Kindle Fire HD Android Development] monster1612:
I tried the same xposed mod on RR 5.6.5 for jem - also got your issue.
[7" Kindle Fire HD Android Development] NewportShortie:
Thank you for the reply :) Will buy a fastboot cable and let you know what happens.

---------- Post added at 01:03 AM ---------- Previous post was at 12:57 AM ----------

Also, is this http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 the correct supersu I need to flash when I get everything back and running again? I just don't want this to happen again. Thank you for your replies :)
[7" Kindle Fire HD Android Development] :
Not sure if the OP is still updating that thread, but the stable build is up to date and it'll work without pre-configuring anything. You can flash any of the official supersu builds as well as long as you've made a config file that includes the systemless false line.
[7" Kindle Fire HD Android Development] NewportShortie:
I Just bought the fastboot cable that you recommended in the last posts, and it should be here by May 10th. I will reply when the cable gets here. And are you sure? After I get everything back up and running, I just flash the stable System Mode SuperSU and I should be fine with root access?
[7" Kindle Fire HD Android Development] :
Yes, system mode supersu has been confirmed working with this rom by multiple users already. Once you're back in twrp, you can extract the boot.img from the rom zip and just flash that alone to fix your current install.
[7" Kindle Fire HD Android Development] syrinxxx:
Boot up speed

Hi,

flash worked all fine for me for my fire HD (7).

Just to compare how about the boot up speed.

Feels very long, isn't it?

Cheers
[7" Kindle Fire HD Android Development] skalnas:
Yes about 4 min for me, love the ROM otherwise
[7" Kindle Fire HD Android Development] syrinxxx:
Thanks sharing this experience with me!

Cheers,

syrinxxx
[7" Kindle Fire HD Android Development] transi1:
r43 on https://www.mediafire.com/folder/5a97vbv93k24n/tate
[7" Kindle Fire HD Android Development] :
Thanks for the update. It boots, camera still not working. I crash now if I change max cpu freq to 1500MHz in kernel adiutor with heavy load such as updating several apps from play store. Can't seem to get any crash logs as last_kmsg never gets written and I don't think the logcat has anything useful either.

Edit: Now I'm not so sure if it was the cpu tweak that influenced the play store crashes. I've run several cpu stress tests at the higher clock speed without any instability. Everything seems more stable now, though when rebooting, it does tend to crash as soon as the boot logo appears before being able to boot successfully.
[7" Kindle Fire HD Android Development] transi1:
try old playstore, i use 15.03.2016 pico version and not trouble.

camera still debugging
[7" Kindle Fire HD Android Development] electrikjesus:
Have you pushed all your changes to your github? When I try to build from your sources, I keep getting errors related to omap4-common/sepolicy/file_contents for both Camera and video. And when I am able to get past that error, I keep running into this one: http://hastebin.com/erotananin.vhdl Please share what you are doing to get past that on your setup. I tried to PM you, but have not gotten a response yet. Feel free to PM me if you would like to share.
[7" Kindle Fire HD Android Development] monster1612:
I PM'd him about it a while ago, and he said to:

remove the "options = common.OPTIONS" line and everything below it in build/tools/releasetools/make_recovery_patch.py

comment out or remove the "RECOVERY_PATCH_INSTALL :=" line in build/core/Makefile

I was trying to build for jem when I got those errors, but both the 7" and the 8.9" share the majority of the device-specific code, so this fix should work either way. Also, I'd try building from the blisspop repos, but my build machine's down and I need to wait to have it fixed...
[7" Kindle Fire HD Android Development] electrikjesus:
I'll give you a heads up if I get it all up and running. Been pulling my hair out for a week on this :D
[7" Kindle Fire HD Android Development] NewportShortie:
I'm sorry for asking so much but can you please explain all the steps I need to take? The fastboot screen on the kindle is up but in cmd fastboot and adb devices are showing up with no decices. Am I missing something? And also once I get these driver issues done, can you please give me the commands I will need to flash the boot.img? Thank you so much.
[7" Kindle Fire HD Android Development] :
1) When in fastboot mode, use "fastboot -i 0x1949 devices" to check if the kindle is connected. You should already have adb/fastboot and the kindle drivers installed. If fastboot shows no device, check windows device manager and do this.

2) Once you see the kindle under fastboot devices, use "fastboot -i 0x1949 reboot oem recovery". You might have to unplug the fastboot cable shortly after issuing the command or it'll go back into fastboot again. This will get you to back to recovery/twrp.

3) Download the rom zip you last flashed and open it in windows. Extract the boot.img file from the zip. Copy it to sdcard of kindle using usb cable and MTP mount in twrp. Select install menu in twrp like you are flashing a zip, select image mode in bottom right corner, look for boot.img and flash it as boot partition then reboot.
[7" Kindle Fire HD Android Development] NewportShortie:
I figured it out, my kindle is up and running again, Thank you so much. Now on to flashing SuperSU in system mode. :)

Okay so I'm in another bootloop. Nothing serious, as i'm restoring my backup as we speak. But I flashed SuperSU as system mode and in the the twrp log it said system mode. Maybe flash the stable one? as I flashed 2.71 which is the beta.