Agreed. The choppiness gets more and more noticeable as battery discharges. I'm using S7 Edge, LightRom with Moro 7.0 kernel.Updating with practical experience.
Phone goes awkwardly sluggish once it is below low battery threshold and despite plugging it in for recharge, the unbearable lags do not vanish. Uninstalled FDE.AI and problem solved.
NoI have grernify installed. Do I have to remove it for the fde.ai to work?
As the second post clearly states....no it doesnt
*** v4.06 ***
— Whole code revised & optimized
— Built with latest CLANG toolchain with max optimizations
— Bulletproof (no code stuck) FDE execution
— Removed some unstable tweaks
— Better Android Pie support
— Disabled forcing fast charge mode
— Removed network packet queues optimization
— Updated sqlite tweaks
— DalvikVM multithreading optimization
— Updated network tweaks
— Updated device information methods
— Updated I/O tweaks
— Tuned kernel tweaks
— Updated & fixed CPU tweaks
— AI modules logic improvements
— AI support custom thermal engines
— misc.
> NF - Thing Called Love
> Kotovsky '86 - Space Traveller
> Lazerpunk - Black Lambo (Quixotic Remix)
> Gorillaz - Stylo
Yes. Just think about it, you have one mod telling your system to do one thing and the other mod telling it to do the opposite your system will crash or just not boot at all.
Complete stupidity. Why would you do that? Cant say you weren't warned
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
What's worst than this is that he was making fun of the module author on xda discord. He said "Imagine being this guy, lol" after posting a photo of feravolt's comment (where he said he's depressed)
First of all, I don't even know him personally, he never contacted me or my friends, advising or pointing on mistakes or whatever. And so I don't understand why he publically offends me & my work.
This is what you should know about his personality first. This type of behavior kinda reminds me YaroST.
1. "But FDE.AI also overrides the manufacturer’s values." - I am OK with that. They provide those tunables for tuning. So why not.
3. https://github.com/feravolt/FDE-sc/blob/master/fde.c#L1124 > this code is valid for only for 2.6.x kernels (very old devices), and it realy does improve UX a lot since I personally tested that on my 2011's device. For rest kernels this is simply not applied. I might just add kernel version check.
5.1 "dumbest choices for tuning your I/O device" + https://github.com/feravolt/FDE-sc/blob/master/fde.c#L1217 > This code should fix rare deep-sleep issues on older kernels and as per my tests (I do own 2 UFS & 2 MMC devices), does not impact performance. I might add kernel version check before apply here too and/ro simply remove this string.
5.2 Will change that to single hit merge and/or check for storage type, because on slow MMCs this helps a lot in write speed.
5.3 I did researched about this and know what this option do. With my value it showed a better result in benchmarks which may fooled me up. Will research about this more.
6.2 That's true - I mixed this up with f2fs fsync_mode=nobarrier.
arter97@arter97-x1:/tmp/FeraDroid-Engine$ git log -1 @
commit f05275e7ed01827d34cd8d7947aa17f71796b1a4 (HEAD)
Author: FeraVolt <fera.volt@gmail.com>
Date: Sat Jul 22 17:49:07 2017 +0600
Merge to v.1.1-rel
arter97@arter97-x1:/tmp/FeraDroid-Engine$ git grep nobarrier
system/engine/feradroid.sh: $B mount -o remount,noatime,nodiratime,nobarrier,discard "${x}";
system/engine/gears/io.sh: $B mount -o remount,noatime,nodiratime,nobarrier,discard "${x}";
Also nobarrier (in rare cases) could corrupt FS, not physically destroy block. I believe that none of existing FS mount flags can actually physically destroy a block. (Don't mix up with file system corruption)