[ROM][6.0][jem] CM redux

[monster1612]

I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.

READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:

• doesn't work as a result of flashing this;
• initiates a nuclear meltdown, or;
• doesn't permit your alarm clock to function normally.

By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.

Downloads:

• click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
• OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
• SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)

Features:

• [*]Compiled with UBERTC 4.9
  • UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
• based on CM13
• more to come!

Known issues in post #2
Changelog in post #3

Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.

Credit where credit is due

• @Hashcode, because we wouldn't have CM on our kindles at all without him.
• @BuQQzz for some mentoring & advice
• @transi1 for porting CM13 and providing some useful fixes for build errors

XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD

Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod

Version Information
Status: Alpha

Created 2016-03-29
Last Updated 2016-08-07

 

[monster1612]

Known issues

Bugs affecting all CM13-based ROMs on the kindle

• Screen artifacts when playing video from Snapchat, Vine, etc.
• Audio chops in and out often
• Other bugs currently afflicting the other CM13 ROMs for this device
• Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
  • Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
• Play Store & Setup Wizard FCs
  • CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)

 

[monster1612]

Changelog

• 08/07/2016
  • experimental backtracking to kernel 3.0.84+
  • July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
• 07/01/2016
  • doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
  • June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
  • reverting from UBERTC toolchains to native CM/AOSP one
• 05/20/2016
  • defecting to BlissRoms-Devices GH for newest device config files
  • 05/2016 security patches from AOSP, et al.
• 04/27/2016
  • refreshing CM sources & obtaining latest sources from transi1
• 04/09/2016
  • revert the 4/4 kernel reversion; back to 3.0.101(+)
  • carry in latest edits from transi1 to try to fix the camera
• 04/04/2016
  • revert to kernel 3.0.72+
  • first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
• 03/29/2016
  • initial build!

 

[monster1612]

Roadmap

The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.

• Layers/RRO theming support
• Custom boot animation (or at least one scaled to the kindle's screen size)
• Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
• Publication of a custom .gapps-config file for use with opengapps packages

 

[monster1612]

I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.

 

[monster1612]

So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.

 

[monster1612]

Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.

 

[monster1612]

Some updates...

• I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
• I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.

 

[monster1612]

More updates...

It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:

• I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
• My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
• That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.

Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.

Finally, some planned changes:

• I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
• Obvious name change in the ROM, mentioned earlier.
• Replacing CM's theme engine with RRO(?)
• CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.

 

[wizard_mini]

Good version,thanks. But it often wifi reconnect , can it fix?

 

[monster1612]

Good version,thanks. But it often wifi reconnect , can it fix?

I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?

 

[wizard_mini]

I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?

It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time

 

[wizard_mini]

Android system cost battery drain more than screen, is it normal?

 

[monster1612]

Android system cost battery drain more than screen, is it normal?

That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.

 

[wizard_mini]

I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?

 

[sirp0p0]

I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?

I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.

Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033

That's not the one I used, but I used a similar version from here somewhere.

 

[wizard_mini]

I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.

Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033

That's not the one I used, but I used a similar version from here somewhere.

It's a good solution,, I fix it, thanks

 

[wizard_mini]

That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.

I use 4hours screen on and 7hours screen off cost 92% battery.

 

[monster1612]

I use 4hours screen on and 7hours screen off cost 92% battery.

I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.

 

[wizard_mini]

I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.

Thanks. I am expecting it!