yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
For awareness this option is only available for devices rocking an older bootloader (5.0.x) that allows booting a custom recovery from Fastboot. Others will need to reload FireOS from the stock recovery menu.
[Fire Original Android Development] Marsu42:
Good idea since the current zip files names don't include the bootloader version and it's still possible to confuse them after download. But thanks for continuing to support both versions, I guess a lot of people will keep using the latest cm 12.1 with the 5.2.0 base.

Questions: The link says pegasusq has hotplugging integrated, so I'm not to chose any other 3rd partyhotplugging module supplied, correct? And Thunderplug is optimized for hexa-core, but the Fire7 is a quad-core?

Last not least: According to this link, you're still missing a couple of modules :-p
[Fire Original Android Development] BeeWall:
Thuderplug does work, it just was meant originally for something else. I don't think this was intended to offer all modules, just some. Also, it's 5.3.2.0, not 5.2.0.
[Fire Original Android Development] theophile2:
The PegasusQ governor does not appear to be doing hotplugging on this device, although it does aggressively scale unused cores to the lowest frequency. I'll look and see if I can figure out why that is, but fixing it might be beyond my skill set at this point. The separate hotplugging drivers seem to work together with the PegasusQ governor though.

The Thunderplug driver says its optimized for octa-core, but I don't think that means it will work any less effectively on quad-core. That said, it does appear to be creating a 100% load on one of the cores at the moment, so something is clearly amiss somewhere.
[Fire Original Android Development] RoroTiti:
1 million thanks to you [MENTION=2748225]theophile2[/MENTION] :D !!! Your work is just amazing, we have now an Amazon Fire, unleashed :D !!! Keep up your good work bro ;) !!!

Config used : Latest Nexus ROM + PegasusQ CPU Settings + ZEN IO Scheduler + Kernel Adiutor + LMK set to light + ZRAM set to 300Mo = multi task that I was never able to do in the past (Clash Of Clans + Facebook Messenger + Spotify...) WoW :D !!!
[Fire Original Android Development] ms372591:
I've tried several time and I can't get the Zen IO or the ZRAM to take. Kernel Adiutor crashes most of the time, but even when it doesn't I reboot and the settings go back to cfq. Any ideas?
[Fire Original Android Development] DB126:
Kernel Adiutor crashing is symptomatic of a larger problem with your device. Also explains why settings do not stick as kernel defaults are restored when device reboots. Kernel Adiutor (or a similar tool, eg: EX Kernel Manager) is responsible for reapplying your preferences shortly after the device starts. If KA is improperly configured or crashing at boot settings will not be applied.
[Fire Original Android Development] Marsu42:
Right... but Kernel Awhateveritscalled has an "Endurance Level" option for ThunderPlug, including "Quad-Core mode" - I take it this is meant for octa-core cpus and the option that does make sense on the fire would be "Dual-Core mode"?

I dunno, for me everything's totally peachy including boot settings, what doesn't work is the zen scheduler which keeps switching back to whatever was set before. Zram settings crashes, too (using latest cm12.1).
[Fire Original Android Development] RoroTiti:
I confirm the bug... I applied my settings this morning... I've just restarted my Fire, and ZRAM, Scheduler and LMK settings are now resetted to default... Seems to be a small problem when trying to set ZEN as Scheduler... Weird...

EDIT: Retried the same settings, but with BFQ Scheduler instead of ZEN, not any setting is resetted : LMK, ZRAM and Scheduler still saved after reboot... SO, ZEN is the problem ;) !!!

EDIT2: BFQ seems to works as good as ZEN, so, I will keep BFQ for now ;) !!!

So, my final settings : PegasusQ Governor + Light LMK Preset + ZRAM 512MB + TripNDroid Scheduler still active after each reboot, seems to be unbeatable :D !!! For non Kernel Adiutor users : LMK preset is : 17,26,34,43,52,60
[Fire Original Android Development] BeeWall:
From what I've read, tripndroid is based on the same schedulers as Zen is. It might work well.
[Fire Original Android Development] RoroTiti:
Yeah, you're right ;) !!! I will have a try :D !!!
[Fire Original Android Development] jaladhjin:
I always thought kernel mods were for boot loader unlocked devices only..

Is that not accurate..

A thing of the past..

Or did something new emerge for Kindle Fire ?
[Fire Original Android Development] BeeWall:
I think that it modifies the kernel files in /sys to accomplish this. That's why it needs to run a script on boot, to get the modules ready.
[Fire Original Android Development] ttcontributor:
Thank you for your work. Now we can get more from our little Fire!

---------- Post added at 05:29 AM ---------- Previous post was at 04:55 AM ----------

ZRAM keeps returning to 440MB?!

P.S: After setting and using this KERNEL and restarting, in my 3rd day use now it seems to cure the brightness bug in Fire Nexus rom which happens once the cpu got heavy use and needed a restart to be able to adjust the brightness again.
[Fire Original Android Development] RoroTiti:
You're right, that's why I don't use anymore Kernel Adiutor, I use EX Kernel Manager since I've found that also ;) !!!
[Fire Original Android Development] DB126:
Sadly I also experienced irregularities with Kernel Adiutor (multiple devices) and have since switched to EX Kernel Manager. I prefer the former but have struggled through several head scratchers traceable to KA - both interactive and restoring preferences on boot.
[Fire Original Android Development] BeeWall:
Kernel Adiutor Mod has worked well for me, and has nice features like toggling ADB over wifi at boot.
[Fire Original Android Development] DB126:
KA mod is a nice alternative but still exhibits some of KA's inherent issues the last time I checked. May be worth another look.
[Fire Original Android Development] BeeWall:
For some reason, whenever I try to enable alucard hotplug or zen I/o, it restarts my device, and does not change either. Anyone else have this problem?
[Fire Original Android Development] DB126:
Underlying kernel needs to support features called by governor/hotplug/scheduler. These mods are simply a layer on top. You'll note the same thing happens with the interactive governor on 'stock' kernel. Not saying it's unsolvable ... but also not unexpected.
[Fire Original Android Development] nirogu325:
I faced a restart with ZEN but not when trying the Alucard hotplug. For reference, I am not using the latest Fire Nexus, but the previous 2/2 version, and likewise with these kernel modules (using the previous version).
[Fire Original Android Development] crazyates:
Just wanted to say thanks for this! I installed it to the 2/8/17 Nexus Fire ROM, and it's working great! Running PegasusQ & Tripndroid, and it feels a lot snappier!

Side note: I also noticed that Alucard hotplug immediately crashes the tablet, and does not stick. I'm OK with not using it, tho, as the other improvements are great!
[Fire Original Android Development] nirogu325:
So it crashes with the 2/8 ROM build but not the 2/2 one I have? Interesting.
[Fire Original Android Development] DB126:
Note a different build is required for the 2/2 and 2/8 Nexus releases per OP. Figure you know that; just a quick reminder.
[Fire Original Android Development] nirogu325:
I did figure. It was a kind of sarcastic post but it is kind of interesting because that Alucard thing works in both of my tablets which has the 2/2 build of FN ROM and no, both are actually running the previous version modules and not the 2/12 ones.
[Fire Original Android Development] DB126:
I will be building out a Fire with 5.0.1 kernel and the latest Nexus ROM along with the corresponding build of this package. Hadn't planned on messing with hotplugs but might give it a whirl and report back if this discrepancy/issue/whatever remains unresolved.
[Fire Original Android Development] DB126:
ROM: Nexus build 20170208; fresh install; only EX Kernel Manager added

Kernel 'bonus' modules from this thread: 5.1.4 package (UPDATE-Amazon-Ford-bonus-modules.20170212.zip)

Used EX Kernel Manager to set PegasusQ & Tripndroid per [MENTION=8097242]crazyates[/MENTION] post. All good. Set hotplug to Alucard. Instant crash.

Have some upcoming travel so won't be experimenting further. At least for a few days. :)
[Fire Original Android Development] nirogu325:
I did not move to the 2/8 FN ROM because the changelog didn't have anything useful for me. I stayed with the 2/2 build and the modules that were released before 2/12. Again, everything is working except ZEN scheduler which I don't really care that much. Pictures for reference.
[Fire Original Android Development] trulyparis1:
Tried to download file for Nexus 0802217 and uninstaller but files not available via download links
[Fire Original Android Development] DB126:
Confirmed; none of the files are available.
[Fire Original Android Development] theophile2:
Sorry guys, Dropbox turned off the "Public" folder for sharing purposes. OP has been updated with working links. Also sorry I haven't updated the packages in a while. Things have been busy lately.
[Fire Original Android Development] DB126:
Wait...who said you could have a life outside XDA! :)

Kidding aside, I appreciate the significant contribution you made to this device along with ongoing support. I run your kernel enhancements with the latest Nexus build and have yet to experience the frustrating brightness bug. That in itself is a huge win. Nice job.
[Fire Original Android Development] iSonik:
Nice Kernel. Works well so far.

If only overclocking would be possible :( ...( I know that darn locked bootloader)
[Fire Original Android Development] akz1x1:
I ran into a bootloop after messing up with some init.d scripts, anyone mind help to recover ?

---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------

Is there any chances of getting a recovery and thus to perform a clean ROM install ?

If not how can I get back to stock amazon os ( I don't rememver which version I was from)

Any help is greatly appreciated. Thank you
[Fire Original Android Development] DB126:
Unfortunately, 3rd party recovery environments can not be booted except with very early 5th gen Fires that came with bootloader version 5.0.x You'll need to launch Amazon's stock recovery (<power>+<vol-up>), reload FireOS (same version as was previously on device) and start from scratch. If you are unsure which version of FireOS was previously loaded go with 5.3.1 which is the highest rootable build as of the date of this post.
[Fire Original Android Development] akz1x1:
Thanks for the help davey, I've tried a data wipe from stock recovery and luckyly for me phone booted just fine after that :))
[Fire Original Android Development] DB126:
Interesting solution; hadn't thought of that (data wipe w/custom ROM from stock recovery). One to keep in mind as there is no downside given the alternative.
[Fire Original Android Development] akz1x1:
I lost everything I had in internal . Still it's better than going through all the troubles of flashing stock, rooting it and commin back to firenexus.

Wish someone could find a way to unlock the bootloader and enable us to flash twrp newer rom versions and all the good stuffs.

I remember reading you were gonna build a rom, How'd it go?bitd be great to have a rom from an active user like you.
[Fire Original Android Development] DB126:
Yep - understand.

As for spinning up a custom ROM you likely have me confused with another contributor. While I likely have the technical background (ya don't know what you don't know until you know it) there would be no personal or community benefit given the excellent work by [MENTION=5749760]ggow[/MENTION] and others. My bucket list is full of other goodies with precious little time to pick off the ripe cherries.
[Fire Original Android Development] jd45321:
Loaded this mainly because I heard it fixes the brightness bug. Seems better, but after my son plays games on it, has brightness issue (darker, brightness slider does nothing) again. A reboot corrects. Just want to know if I need to set anything special to get brightness bug fixed (I'm a noob, only been doing this since Fri when my Fire arrived, was able to root, install the ASOP Nexus ROM, get this mod loaded (I think) add Kernel Adiutor mod). But not sure which options to set exactly to eliminate brightness bug.

Thanks
[Fire Original Android Development] DB126:
No knobs - kernel mod itself seemed to quell the brightness bug for many. But I'm not a gamer and rarely stress my Fire 7 beyond brief periods. Best known mitigation is to minimize memory load which is obviously hard in a gaming situation.
[Fire Original Android Development] jd45321:
The brightness bug is starting to bother me. Are there any other ROMS that can be put on this tablet? If so, do they have any negatives?
[Fire Original Android Development] DB126:
There are at least four other custom ROMs for this device. None are being maintained at present; some have significant installation, stability and/or compatibility issues. All suffer the brightness glitch to varying degrees as problem is rooted in the kernel. How quickly is manifests seems to be dependent on the ROMs memory management algorithms and/or tuning.
[Fire Original Android Development] jd45321:
Ugg, thanks. Other than the brightness glitch, this ROM is really nice! So, I guess there is no real fix then and it probably will not be fixed in his rom either?. If I load Amazon OS back on this, would the brightness glitch go away or is that still part of the kernel? If this is an option, is there anyway to get Google Playstore loaded on the Amazon ROM? Thanks
[Fire Original Android Development] DB126:
For whatever reason FireOS does not appear to suffer from this glitch. Perhaps it uses a different binary/mechanism to adjust brightness. You can get Google Play Services/Store to work with FireOS but the experience is not as refined; some apps will still need to be side loaded. You'll also loose the UX niceties of Nexus and (arguably) gain a few from FireOS. Choose your poison wisely.
[Fire Original Android Development] crazyates:
I used FireOS with Google Play and Nova Launcher for several weeks before wiping it and loading Fire Nexus. It ran SOOO much faster on the Fire Nexus than on FireOS.

I think it's because there are a ton of Amazon programs and services running in the background, and since this only has 1GB of RAM, it runs out very quickly. Also, it's not the beefiest CPU, so anything you can do to limit the number of programs and limit the CPU usage will result in better performance.

With FireOS, you gain little tweaks like the brightness working 100% of the time, but when it does stop working on the Nexus Fire, a quick reboot fixes it just fine. It happens maybe once a week? Considering I use it almost every day, it's worth it.
[Fire Original Android Development] DB126:
If you have Xposed framework installed might try brightness controls in Edge when a 'freeze' occurs. More than likely will not be effective (especially if problem resides in kernel) but easy enough to test. Edge itself is a wonderful addition to Nexus. Hard to understate the flexibility offered through this module for those who enjoy fully personalizing the operation of their device. Tasker like control without the learning curve.
[Fire Original Android Development] crazyates:
I'll give it a try, but I'm not expecting much. It seems to be a kernel issue, but I've been wrong before. Also, I wish there was a way to decrease the minimum brightness. At night, in a pitch black room, it's still too bright for my tastes.
[Fire Original Android Development] DB126:
I use a blue light filter app to deal with the excess min brightness issue. No power savings of course but keeps me retinas from being burned into the back of me eyeballs in a dark room. :)
[Fire Original Android Development] crazyates:
Which version should we use for the new 7/22 Fire Nexus ROM? Still 5.3.2.0? It's great to see this device still being supported, and these kernel tweaks are fantastic!
[Fire Original Android Development] crazyates:
Nevermind. I used the one for the 5.1.4 boot img, and it seems to be working fine. Thanks!
[Fire Original Android Development] t3chwizard:
[MENTION=5488402]Davey126[/MENTION], I searched this thread and found nothing about it but I'm wondering if you had any success with these modules on the Lineage ROM by [MENTION=5749760]ggow[/MENTION]? If not do you think it would be possible for one of the versions to work?

I have an original Amazon Fire (5th Gen) with the 5.0.1 bootloader (got it when Best Buy and all the stores were having those black Friday sales 2 years back). Additionally, I apologize if I have asked this in the wrong place but I am very uninformed and wondering if this would somehow improve the performance on my tablet using the new Lineage ROM.
[Fire Original Android Development] DB126:
I tried these in the past. Perfectly stable, interesting to play with but in the end brought no significant usability or performance enhancements; I no longer use them. The stock hotplug governor is a good choice for the modest hardware. I switched the scheduler to 'on demand' as it is a better match for my workflow. Both are further tuned to my liking.

I see no reason why these wouldn't work with the Lineage 12.1 build for this device.
[Fire Original Android Development] ggow:
The version labelled "Package for ROMs Based on 5.1.4 Boot Image" should work fine.

[MENTION=2748225]theophile2[/MENTION] - The current version of Lineage-12.1 uses FireOS 5.1.4 blobs (Same as Fire Nexus ROM). I don't envisage that this will change.
[Fire Original Android Development] t3chwizard:
Got it. Thanks!!
[Fire Original Android Development] theophile2:
If there is anyone running a ROM based on the 5.3.2.0 boot image, could you please post me the output of 'uname -a' ?

I'm trying to build a unified installer package that detects the boot image version and installs the correct set of modules, but I'm not sure how to reliably detect the boot image version other than to match the exact kernel version string.
[Fire Original Android Development] theophile2:
Or if no one is using 5.3.2.0-based ROMs anymore, maybe I can drop support for that?

I've been doing some more work on the 5.1.4-based branch and now have the IntelliPlug hotplug driver working, and it actually works very well! I don't know if it's just me, but the Alucard hotplug driver causes a kernel panic on 5.1.4 so I may remove it until I can sort that out. I'm also working on fixing Smartmax and perhaps adding a couple more things to play with.
[Fire Original Android Development] DB126:
Few builds were based on 5.3.2.0 bootloader/kernel; all have updated alternatives that feature 5.1.4 equivalents. IMO it would be safe to drop 5.3.2.0 support.
[Fire Original Android Development] melvinaury:
Just to confirm I'm using Lineage 12.1 August 2 version. What package I need to download?
[Fire Original Android Development] nirogu325:
Please try reading the OP again OR try reading some posts before yours, answer was discussed.
[Fire Original Android Development] melvinaury:
Ok, no problem I already download the modules and the revert files. Thanks..
[Fire Original Android Development] ms372591:
ggow has moved both the Nexus and Lineage roms to 5.4.0.0 will there be a kernel released to use on these or is it best to stick with what the rom has loaded?
[Fire Original Android Development] theophile2:
It looks like Amazon hasn't released source code under the GPL for 5.4.0.0 yet. Once they do, I should be able to build a package for it.
[Fire Original Android Development] Marsu42:
Any progress? I just revived my old Fire with the latest rom, but without the pegasusq govenor I'd rather use an older rom again :-\
[Fire Original Android Development] theophile2:
Sadly, no. It has been a very long time since Amazon has released any source code as required by the GPL.
[Fire Original Android Development] Marsu42:
Has a complaint been given to Amazon or some 3rd party like the fsf - or has this been discussed on some mailing list where gpl pople are involved?

If you know what Amazon used to do, and now has stopped doing even thought they are under gpl obligation, it would be nice if you would write a short mail to license-violation@gnu.org

https://www.fsf.org/licensing/
[General Questions and Answers] xda2014:
I sometimes need to rotate jpg images on my Android mobile. To avoid image quality degradation what I do now is to copy the image and then use "rotate image" using Gallery (or other) app on the copied image. I later transfer the original to my PC where there are many image viewers to perform lossless rotation.

Is there any Android app that can perform lossless rotation?

If not, can one of the talented developers here create a app to do the same?
[LG K10 Questions & Answers] Mulukou:
So, i unlocked bootloader, tried to install TWRP 3.0.0 by berkantkz but it didn't work, so i used the gottlasz guide, after going to recovery i installed the cm 13 unnofficial rom by pvineeth97, after this the phone just bricked I can enter recovery mode (which is not TWRP) but it doesn't change anything, I can enter download mode, but after entering the usb connects and disconnects, making it impossible to use the LGUP. Is there any hope or I can't recover my phone at all?
[LG K10 Questions & Answers] gottlasz:
In case the usb connection doesnt stick it means you have exchange mother board... i`ve been in the same shoes bro. Tried everything.. no luck.
[LG K10 Questions & Answers] pvineeth97:
I don't understand what do you mean by "USB" connects and disconnects? What do you see on screen after entering download mode?
[LG K10 Questions & Answers] Mulukou:
After entering download mode, windows detects the phone, but after 1 sec it loses connection to the phone, in the K10 appears the normal download mode screen (after a little time, the phone reboots)
[LG K10 Questions & Answers] ArcherEmiya:
did you use the original USB cable of k10? try to use LGbridge instead since LGUP doesnt work perfectly with K10 because it so hard to find its DLL file. If you are using LGUP to flash use it with Uppecut Software to bypass its incompatibility issue search it in google and you will find it xda.
[LG K10 Questions & Answers] Mulukou:
I used the original cable and tried LGBridge, didn't work.
[LG K10 Questions & Answers] Professor Woland:
First you don't install twrp you just boot it from fastboot.

Other thing is that if you read any post in that thread you would see that everyone who tried to install that rom got their phone bricked, some of them succeeded to bring phone back to life, and some killed their devices for good..

So if you can't have stable connection via usb then I have bad news for you..
[LG K10 Questions & Answers] Mulukou:
Yep I knew the risks, just wanted some hope i guess...
[LG K10 Questions & Answers] pvineeth97:
I don't understand why did'nt you read the forums before flashing it and moreover the ROM was just for testing purposes for advanced developers and it was clearly written at top of the page.
[Sony Xperia M] Malgotra:
i need help. may be my device hard bricked. i just switch off my phone to remove sim but after i turn it on i can't pass the sony bootlogo. then i open twrp and it shows everything 0mb (internal,external memory both). i attached the screen shot. i also tried flashtool(install drivers) but it can't connect my device. always shows disconnected. please if their is any solution guide me.
[Sony Xperia M] olibub:
can you format ext partition ? :) "sdcard"
[Sony Xperia M] MiyamuraNEET:
Me too ;--;
[Sony Xperia M] Malgotra:
Nope:(
[Sony Xperia M] olibub:
..this format option is in advanced, partition SD card, but if you can't, so try to format SD CARD with SD CARD READER in pc and install twrp 2.8.6.0..:)..

but try flash again kernel or flash kernel via TWRP--> 2.8.6.0 :)
[Sony Xperia M] extremetek:
Go back to CWM or TWRP older that 3.0.0-0 and wipe system/cache/data. If you can't wipe, the phone is doomed.