[2020-01-27] ®FDE.AI - Ultimate Android Optimizer

Code:

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!

Intro:​

• ARMv7 (armeabi-v7a) (32bit)
• ARMv8 (arm64-v8a) (64bit)
• x64bit (x86_64)

• 4.1 and higher

See compacted list of most included features HERE.

Artificial Intelligence:

• Make a backup just in case something goes wrong.
• Download latest version of FDE and install it via custom recovery OR add zip in modules list if you are using Magisk systemless root.
• After OS boot, you will get vibration and a log file /sdcard/Android/fde.txt will be created if FDE worked OK.

• It will work on any device which runs Android OS.

• NO. Don't use any other All-in-One tweakers or things may get much worse!

• Yes, why not? It will work even better on custom kernel.

• No configurations. This is "flash & forget" optimizer. It will configure your system depending on you hardware/software automatically & individually. Log is available in /sdcard/Android/fde.txt

• Yes, sure. FDE not only gives performance, but also increases power-saving.

• The difference is only in installer - zip provided here is universal, while one in Magisk repo is for Magisk root only.

• You may try to install FDE via Flashfire app.

• Try to emulate init.d support with app like Universal_Init.d_Support or similar.

• Try to reboot device. Wait for a minute or two more. Maybe it will work, but a little later than expected. Also check for /sdcard/Android/fde.txt file. If still no luck, try to update your ROOT method (Magisk preferred). If you do have log and it says "all good" - then don't worry at all. Some rare devices doesn't support vibrations triggered by script. If still not working, read THIS post.

• No, FDE has a built-in one already. But if you already have one - they will not conflict.

• YES.

• This is not an Android apk and it has no interface yet.

• NO. Boot ROM first, then install FDE.

• You may try to install another custom kernel. Those features are kernel dependent.

• FDE.AI is under active development. Please attach any useful information such as log/screenshot, name of your device, ROM/recovery version. I am developer of FDE and I will help you to figure out the problem.

• Real AI with machine learning, CPU & GPU turbo boost, custom GPU throttling engine & more..
• Board clock gate activatation
• Board clock scaling activation
• CPU sleep mode activation
• CPU power-saving idle mode activation
• Touch boost optimization
• Device wakeup boost activation
• CPU synchronisations optimization
• Power-key input boost activation
• Schedulers input boost optimization
• Input boost optimization
• Fingerprint boost activation
• CPU core hotplug boost optimization
• EAS dynamic boost optimization
• LCD power consumption reduce
• Simple GPU mode activation
• Multi-core CPU optimization
• Kernel wakelocks optimization
• Touch-screen sensivity optimization
• Vivante GPU frequencies optimization
• Adreno GPU frequencies optimization
• Adreno GPU I/O optimization
• Adreno Idler optimization
• Mali GPU optimization
• Mali GPU debugging dectivated
• Mali GPU thermal limit deactivation
• Mali GPU touch boost optimization
• Frame buffer optimization
• Misc unneeded logs deactivation
• Forced file sync deactivation
• Dynamic file sync activation
• Disabling various kernel debugging
• Network buffers optimization
• Kernel network stack optimization
• TCP congrestion controller optimization
• WiFi packets throughput optimization
• Disabling Doze settings reset
• Doze and Light Doze parameters optimization
• System animations optimization
• Cache partition trash cleaning
• User partition trash cleaning
• Internal memory trash cleaning
• Apps cache cleaning when low free memory
• MMC NAND memory optimization
• Automatic I/O scheduler setup
• R/W speed optimization for all partitions
• I/O optimization for all partitions
• File system optimization for all partitions
• Kernel schedulers optimization
• ARCH power-saving activation
• Kernel tracing deactivation
• Entropy generator optimization
• File system cache optimization
• Kernel RAM allocation optimized
• Kernel OOM killer deactivation
• VM cache optimization
• VM panic deactivation
• VM dumps deactivation
• VM read/write speed optimized
• VM memory compaction activation & optimization
• Task dumps deactivation
• VM memory regions optimization
• File system kernel parameters optimization
• Kernel hung-task check deactivation
• Kernel panic deactivation
• Kernel watchdog deactivation
• EAS optimization
• Sched parameters scaling deactivation
• Power aware kernel scheduling activation
• Multi-core CPU scheduling optimization
• HMP scheduler optimization
• ARM SWP feature activation
• CPU dynamic bus frequency scaling activation
• RAM dumps deactivation
• ANY CPU governor optimization
• Cgroups parameters optimization
• Power efficient CPU queues activation
• CPU bandwidth optimization
• LMK debugging deactivation
• LMK agressiveness optimization
• LMK fast run logic deactivation
• ALMK deactivation
• LMK OOM reaper logic activation
• UKSM/KSM activation & optimization
• zRAM optimization
• NO-zRAM kernel parameters optimization
• Process reclaim logic activation
• OS boot process optimization
• DalvikVM optimization
• DalvikVM memory allocation optimization
• Checking errors on all partitions
• Multitasking optimization
• System services fixes
• Patching SafetyNET
• Refreshing file system on all partitions (fstrim)
• System processes optimization
• SElinux fixes
• Launcher redraw deactivation
• RIL dumps deactivation
• App-manager power-saving optimization
• WiFi misc debugging deactivation
• Sqlite (database) optimizations
• Image compression level increase
• Media codecs log deactivation
• HW powersaving video playback activatation
• ART optimizations
• DalvikVM multi-threading optimization
• DalvikVM JIT compiler optimizations
• Activation of 4K-video support in YouTube app
• Audio buffer optimization
• Wireless display streaming optimization
• Protection against net vulnerability CVE-2016-5696
• Protection against Stagefright vulnerabilities
• ANR/Dropbox debugging deactivation
• GPRS/EDGE net speed optimization
• App switching delay deactivation
• HW UI rendering activation if needed
• Project-butter activatation
• Tripple-buffering activatation
• Frames draw latency reduction
• Dynamic FPS support activatation
• A LOT of various debugging deactivation
• misc..

dope77 said:

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)

Click to expand...

Click to collapse

FeraVolt said:

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.

Click to expand...

Click to collapse

1. "But FDE.AI also overrides the manufacturer’s values." - I am OK with that. They provide those tunables for tuning. So why not.

Click to expand...

Click to collapse

2. Thanks for "smb135x" wakelock info - I will fix this asap.

Click to expand...

Click to collapse

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.

Click to expand...

Click to collapse

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.

Click to expand...

Click to collapse

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.

Click to expand...

Click to collapse

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.

Click to expand...

Click to collapse

6.2 That's true - I mixed this up with f2fs fsync_mode=nobarrier.

Click to expand...

Click to collapse

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)

Click to expand...

Click to collapse