Related
NOTICE: This is COMPATIBLE with ALL Vivid Rooted Stock and Custom ROMs
For frequency control use fauxclock from Google Play
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to hack this kernel. If you use my modified kernel source in parts or in its entirety, I kindly ask you mention its origins and to send me a github pull request or PM whenever you find bugs or think you can help improve my kernel hack further. This way the entire community will truly benefit from the spirit of open source. Thank you
Hi XDA members and fellow Vivid users:
This is my tenth kernel hack. I want to thank Erasmux, and several others I cannot recall for inspiring me to venture into this unfamiliar territory for me.
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
THIS KERNEL is BASED ON HTC Source Code. So it is COMPATIBLE ONLY WITH HTC ICS Vivid Builds.
Please DO NOT use any task killers, they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibilities (Forced Close).
CleanCache (via ZCache backend)
ZCACHE is a new technology I introduced to HTC Kernel. ZCACHE is a compressed cache similar to ZRAM but the similarity ends there. ZCache is meant to provide as many "cleancache" pages (non-dirty or untouched "virgin" memory) to apps that request for new memory. CleanCache is very easy to allocate and no additional penalty are required to hand them out, so having more CleanCache pages will improve performance. Under heavy memory pressure, often times the kernel will NOT have enough CleanCache pages, so the kernel has to do EXTRA work to reclaim dirty cache pages and clean them for the new apps that's requesting for them. The described process creates a performance hit for the kernel and the app, so the idea is to use compression to create more CleanCache pages available for use. Of course there's a penalty to pay for using compression, but the trade-off between compression penalty and the penalty for reclaiming dirty cache pages and allocating them after cleaning is smaller for compression, so in the end, CleanCache should add more performance.
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Joe's RCU (Optimized for Small SMP systems)
Joe Korty has created an RCU for small SMP systems (> 32 cores). His approach is to isolate all the Garbage Collection (GC, a slow time consuming but necessary processing) to a single core, thus allowing other cores to ONLY work on real required processing. This will allow the additional cores to complete their assigned tasks as fast as possible (not bogged down by GC) then immediately go back to a suspended state (saving battery).
Fast No Hz RCU (Optimized for SMP operations)
Fast NoHz is an optimized version of the traditional Tree RCU. Many new kernels are using the Tickless NoHz design. This RCU is tailored and designed to work with the new NoHz kernel system.
SmartAssV2 Governor (Balanced)
This governor has a built-in "profile" similar to SetCPU, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Interactive Governor (Performance)
This governor is designed to put more priority to User Interface (UI aka Apps) tasks, therefore appears more responsive then the traditional OnDemand governor. So if you want the smoothest UI interaction, this governor is for you...
Brain F*ck Scheduler - (BFS)
This scheduler is designed to be simple and speedy tailor specifically for user interface type systems such as desktop/smart phone devices where user interaction is MORE important than serving 1 million web requests (CFS, the default scheduler) at the same time (think of nimble desktop workstations vs large corporate servers).
SLQB - (SLAB allocator with Queue)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate). Not all kernels are using SLQB including CM7 main line...
Fair Budget Queue (BFQ I/O scheduler)
This I/O scheduler is an improvement on top of Completely Fair Queue (CFQ). CFQ is fair in terms of time but not in terms of throughput / bandwidth, so BFQ make sure that both time and throughput / bandwidth are balanced across all requests.
Kernel Files:
******* Ice Cream Sandwich (Android 4.0.x) ******* (Linux 3.0.33)
[ CFS ] (Ultimate Edition) *** S-ON ***
The File ==> Vivid Kernel 007 (1.73 GHz, GPU @ 320MHz, ZRAM) <==
[ CFS ] (Ultimate Edition) *** S-OFF ***
The File ==> Vivid Kernel 007 (1.73 GHz, GPU @ 320MHz, ZRAM) <==
[ Optional: ]
Files to DISABLE Sweep2Wake:
http://forum.xda-developers.com/showpost.php?p=25538084&postcount=6616
[ For Kernel Devlopers ONLY: ]
The File ==> My Global VDD_TABLE for under volt patch <==
The File ==> KGSL Ring Buffer Power Management Patch for Cordy and Ninja Jump <==
Optional Under voltage: Version 0.1.4+ ONLY
Code:
[ to over volt ALL frequencies by 25000 uv (microvolts) ]
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to under volt ALL frequencies by 25000 uv (microvolts) ]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to set a specific frequency (ie 1.18 GHz)
with a specific voltage (ie 1.0875 volts) ]
echo "1188000 1087500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
CPU Frequency Voltage Table Example
Code:
192000: 812500
310500: 812500
384000: 812500
432000: 812500
486000: 837500
540000: 850000
594000: 862500
648000: 875000
702000: 900000
756000: 925000
810000: 937500
864000: 962500
918000: 962500
972000: 962500
1026000: 975000
1080000: 987500
1134000: 1000000
1188000: 1012500
1242000: 1025000
1296000: 1050000
1350000: 1075000
1404000: 1100000
1458000: 1112500
1512000: 1125000
1566000: 1150000
Optional: Stock Clock Frequencies for Dual CPUs
Code:
su
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpu1/cpufreq/online
echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
Optional: ZRAM (Compressed RAM swap space )
Code:
su
mkswap /dev/block/zram0
swapon /dev/block/zram0
Low Voltage - Under Volt the processor, therefore uses Less Battery, but NOT ALL CHIPS can handle Under Volt.. If you experience instability, try the Stock Voltage Version.
Stock Voltage - Uses the voltage values from ORIGINAL HTC Kernel Source.
There are NO PERFORMANCE DIFFERENCE between the Under Volted and Stock Voltage versions!
Installation Instructions:
Here's a step by step instruction to install this kernel:
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
NEWS BULLETIN:
Ice Cream Sandwich Version 007 is out. More intelligent intellidemand! Completely free yourselves from mpdecision, thermald and now with intellidemand, complete CPU/Thermal Management by the kernel.
Please don't hesitate to talk among yourselves and help each other out... The XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
BUGS:
Not All CHIPS ARE CREATED EQUAL
TO DO:
version 1.x.x -- Haven't thought about it yet...
History:
[ Change Log ]
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My Github Complying with GPL and XDA rulez
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below
Awesome!! Can't wait to try it!
Sent from my HTC PH39100 using XDA
Thank you so much.. faux123~
Faux your a god.
Sweet....
Anyone install yet and have feedback to report?
Boot Loop
No go for me.
It gave me a reason to update to the new AT&T RUU.
May try again after clean install.
Going to flash stock rooted cwm then maybe this will report back.
ismoore said:
Anyone install yet and have feedback to report?
Click to expand...
Click to collapse
Well it's fast in quadrant scores. I got like a 3560 and in that test CPU scores are significantly higher. Antutu benchmark scores with no overclock are the same as stock. All else felt the same. I'm running this kernel with WC's 3.6 Vivid ROM. Still appreciate the contribution faux! I have run your kernels on other phones and they are always the best!
Now why would Window XP forget my android 1.0 drivers for hboot? can't flash anything in hboot now...
Great, thanks for the info. May try this tonight when I get home. Thanks for your efforts faux.
brwnohno said:
Well it's fast in quadrant scores. I got like a 3560 and in that test CPU scores are significantly higher. Antutu benchmark scores with no overclock are the same as stock. All else felt the same. I'm running this kernel with WC's 3.6 Vivid ROM. Still appreciate the contribution faux! I have run your kernels on other phones and they are always the best!
Click to expand...
Click to collapse
My wifi isn't working, it just says "turning on...". Other than that, it works great
**** mines bootlooping its get the att and loops what should i dooo? I got the latest cwm, and hboot, stock rooted rom. Is it because I let it try to boot right after I flashed the boot.img and didn't flash cwm strait after?
haloXgod117 said:
My wifi isn't working, it just says "turning on...". Other than that, it works great
Click to expand...
Click to collapse
Brand New said:
**** mines bootlooping its get the att and loops what should i dooo? I got the latest cwm, and hboot, stock rooted rom. Is it because I let it try to boot right after I flashed the boot.img and didn't flash cwm strait after?
Click to expand...
Click to collapse
You shouldn't be flashing via cwm. I've included a script for pc tethered flashing. Just run flash.bat on pc with USB cable connected to the phone. You may need to run it twice if it failed to load the modules.
Sent from my HTC Sensation 4G using Tapatalk
faux123 said:
You shouldn't be flashing via cwm. I've included a script for pc tethered flashing. Just run flash.bat on pc with USB cable connected to the phone. You may need to run it twice if it failed to load the modules.
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
So I could of flashed this on stock ICS? I didn't think you could OC with a non-rooted phone And I was bootlooping on the stock rooted rom not because of the your kernal I believe
iff this will help
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
D:\Documents and Settings\Noah>cd D:\Documents and Settings\Noah\Desktop\New Fol
der
D:\Documents and Settings\Noah\Desktop\New Folder>flash.bat
D:\Documents and Settings\Noah\Desktop\New Folder>adb kill-server
D:\Documents and Settings\Noah\Desktop\New Folder>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb push Modules/system /syste
m
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb shell mv /system/bin/mpdec
ision /system/bin/mpdecision_dis
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb shell mv /system/bin/therm
ald /system/bin/thermald_dis
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb reboot bootloader
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>fastboot flash boot Kernel-Her
e/boot.img
sending 'boot' (4348 KB)... OKAY [ 0.875s]
writing 'boot'... OKAY [ 4.984s]
finished. total time: 5.859s
D:\Documents and Settings\Noah\Desktop\New Folder>fastboot reboot
rebooting...
finished. total time: 0.188s
D:\Documents and Settings\Noah\Desktop\New Folder>pause
Press any key to continue . . .
D:\Documents and Settings\Noah\Desktop\New Folder>
can you make a aosp kernal
Nevermind Faux I figured it out! I just need to flash the boot.img that came with the stock rooted rom, then yours! I can't wait to test my battery now, games fly to!! Thanks for your support!!
SetCPU voltage tables are still nonfunctional, just like every other kernel I've tried.
come at me bro said:
can you make a aosp kernal
Click to expand...
Click to collapse
It would be easier to do so if we had a booting AOSP build right now, I think.
Having no issues here. Kernel is definitely smoother and faster than stock. Running fine on WC ROM. Hitting about 3350 on quadrant afer 5 consecutive runs. I haven't made and changes with setcpu, I'm assuming 1.5MHz from initial flash.
Sent from my HTC PH39100 using xda premium
Aus_Azn said:
SetCPU voltage tables are still nonfunctional, just like every other kernel I've tried.
It would be easier to do so if we had a booting AOSP build right now, I think.
Click to expand...
Click to collapse
thecubed's build boots but just barely and someone is working on a build right now I believe, so one day we might have working rom
Brand New said:
thecubed's build boots but just barely and someone is working on a build right now I believe, so one day we might have working rom
Click to expand...
Click to collapse
it boot loops with the proper builds , the one that boots is hacked up to hell
NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk
Damn this looks complicated as hell haha. Good job OP
Very nice job
Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me
I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?
Did you disable APK signature checking?
elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?
Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works
Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?
For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.
My rom is stock 4.4.4
I will try again with disabled optimization.
kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference
Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.
I tried again but this time booted upto lock screen and rebooted.
I tried with new build.
after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english
hennymcc:
Important notice:
- You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
- Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
- The image is only for S5 Mini SM-G800F (Exynos)
- The kernel is not tested well. It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an OTG device drains too much power)
- Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Side note: Tripping KNOX counter might break some Samsung applications even after a factory reset. This might be due to secure storage(which is fixable), but for now be cautious if you depend on these features! This image will likley damage the Qualcomm variant of the S5 Mini, do not flash if you have a G800H!
Hello! :laugh:
I've been working on a custom kernel for a while for personal use but I thought some of you might like it.
Current feature list:
Patched to Linux 3.4.113
Fading LED notification (default disabled)
Added row I/O Scheduler
Added zzmoove CPU Governor(with temperature export)
Added PIE network scheduler(supposed to reduce latency, default disabled)
DriveDroid support
Universal Control Interface[UCI] (use the Synapse app to configure)
USB OTG
Boeffla sound engine (Only configurable via Synapse! default disabled)
Powersuspend with LCD panel hooks
1.5GHZ clock speed on processors with revision 2 and above
Double Tap 2 Wake
Voltage Control
MDNIE Hijack
F2FS Support
Haptic Feedback for soft keys
Compiled with Self built Linaro 5.3 toolchain
This kernel is currently only designed to work with the corresponding TouchWiz ROM and likely won't be able to boot custom ROMs. KitKat/Lollipop TouchWiz is also not supported!
If you have any questions about the included features (how to enable, what they do) you may ask in the Q&A until I update the thread.
About 1.5GHZ clock speed
So, as it turns out, Samsung had already done the work to push the 3470 to 1.5GHZ. The frequency tables were already there and all that needed to be done was to remove a soft limit set on it and voila! 1.5GHZ! The catch is that these tables only applied to the second revision of the SoC and above.
Possible reasons why Samsung set the limit:
The S5 mini comes out with both the older and newer revisions of the 3470 and Samsung wanted to avoid getting in legal trouble for selling a higher clocked phone as the same product
The higher clock speeds legitimately can damage the phone
As I don't have multiple S5 Mini's at hand I can't prove the first point, but the second point is more likely true. If you don't feel comfortable with the higher clock speeds you may lower the maximum to 1.4GHZ via Synapse, but the default clock is always 1.5GHZ due to the way in which the frequency controller works.
Current status : BETA
Credits:
andip71(Boeffla sound), faux123(Powersuspend), FrozenCow(DriveDroid support), ZaneZam(zzmoove), Linux Foundation(kernel patches), AndreiLux(Voltage patches for INT and MIF bus), Yank(MDNIE hijack), Samsung(F2FS)
On-board BusyBox by meefik https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=en
The authors are not responsible for the way in which their features have been implemented in this kernel. Do not post bug reports to them!
Flashing procedure will be the same as with this kernel.
Download current image here:http://forum.xda-developers.com/devdb/project/?id=10241#downloads
Chaneglog:
Code:
1.0
-Initial Release
1.1
-ZZMoove Update to 1.0 Beta 8
- Linux Update to 3.4.108
- Toolchain update
- 1.5ghz unlock for higher revision SoC's
1.2
- Ramdisk update
- Double Tap 2 Wake!
- UCI update
- USB OTG now permanently enabled
1.3
- Voltage Control (CPU, GPU, bus)
- Fixes for DT2W
- Linux Update to 3.4.109
1.4
- Intelliactive Removed
- Linux Update to 3.4.110
- MDNIE Hijack
1.4_L
- Lollipop Variant Now Live
1.4_L2
- Second Lollipop release
- Fixed OTG
- System partition can be remounted again
- Removed Frandom (Does not work so well in Lollipop)
1.5
- KitKat support terminated
- Fix annoying bootloader warning ("KERNEL IS NOT SEANDROID ENFORCING")
- F2FS Drivers updated and F2FS support improved (/data and /cache)
- Patch to Linux 3.4.111
- UKSM removed due to stability concerns
- SELinux policy support update (Latest SuperSU betas might need this)
- Switch to self built linaro toolchain
1.6
- Update to Linux 3.4.112
- F2FS drivers updated
1.7
- F2FS drivers update
- NTFS support enabled (eg. for reading USB HDDs)
- Kernel side haptic feedback on soft keys added (see second post)
1.8
- patch to 3.4.113
1.9
- Switchable OTG
2.0
- Updated to MM
- No longer need to install BusyBox manually to use Synapse
XDA:DevDB Information
G800F Custom Kernel, Kernel for the Samsung Galaxy S5 Mini
Contributors
CurtisMJ
Source Code: https://github.com/CurtisMJ/g800f_custom_kernel
Kernel Special Features: Boeffla Sound, Fading LED, Linux 3.4.113, row I/O Scheduler, zzmoove CPU governor, PIE netsched, DriveDroid support, UCI, USB OTG, DT2W, Voltage Control, MDNIE Hijack, F2FS, Haptic feedback
YOU MAY NEED TO REFLASH SUPERSU AFTER FLASHING THE KERNEL!
Version Information
Status: Beta EOL
Current Beta Version: 2.0
Beta Release Date: 2017-03-07
Created 2015-06-08
Last Updated 2017-03-07
Reserved
OTG switching
Credit to tobigun for the original code (I actually attempted it at some point but failed miserably).
Execute the commands in a terminal:
Turn on OTG
Code:
su -c echo OTG > /sys/class/sec/switch/otg_cable_type
Turn off OTG
Code:
su -c echo USB > /sys/class/sec/switch/otg_cable_type
(Haven't touched Synapse in forever, cannot make sense of it anymore, so no Synapse switch soz)
Synapse Issues
I had some trouble with colour choosers crashing Synapse under specific conditions. If Synapse keeps crashing when picking colours for MDNIE, please try the custom build available in the downloads section of this project.
IF THE DEVICE IS CRASHING WHEN USING SYNAPSE, THEN YOU HAVE LIKELY SET UNSTABLE SETTINGS! SYNAPSE WILL NOT PREVENT THIS, SO PLEASE BE CAREFUL WHEN CHANGING SETTINGS!
There are two ways to recover:
- Use your recovery to delete Synapse's data folder
- Factory Reset your device (Only in extreme cases)
Using PIE netsched:(likely not working with Android at this point in time)
Run following in root terminal or as init.d script
Code:
tc qdisc replace dev wlan0 root pie
tc qdisc replace dev p2p0 root pie
tc qdisc replace dev rmnet0 root pie
ZZMoove and profiles:
The zzmoove governor is highly recommended. It can be set to various profiles to mimic the benefits of various other governors. It'll even ensure the device doesn't overheat!
The profile can be set by setting the "profile number" tunable in Synapse to one of the number values mentioned here. Setting it will change a bunch of other tunables. You'll need to restart Synapse after setting it and save the changes for future application.
Notes on DVFS
Samsung's DVFS feature in their TouchWiz ROMs seems to get a bit shouty when anything other than the "interactive" CPU governor is active. It could also be the cause of rare kernel panics relating to CPU frequency tables(frequency controller expects something from the governor, governor doesn't deliver, panic). Since it also seems to cause a couple other unrelated issues, I'd recommended simply disabling it altogether(the easiest way being via Xposed)
Double Tap 2 Wake
This feature allows you to wake the device by double tapping on the screen while it is off. NOTE:Deep sleep is near totally inhibited while this feature is active, this means extra battery may be consumed. On a tweaked ROM you'll get 2-3%/hr on full standby, on non tweaked you'll get about 4-5%/hr, please keep this in mind while using the feature! Android OS suspension should be unaffected. The feature disables itself when a Samsung branded flip cover is closed, including S-View covers(no double tapping on the window). The feature makes use of the light and proximity sensors in order to detect whether the device is in a dark enclosed place (eg. A pocket) and disables itself in these situations as well in order to prevent accidental wakes (though that may still happen...)
MDNIE Hijack Example
Profile based of iPhone 6+ screen:
R: FF 00 00 - G: 12 FC 12 - Bu: 00 00 FF - C: 12 FF FF
M: FF 00 FF - Y: FF FF 00 - W: FF FF FF - Bl: 00 00 00
Feel free to post any other nice looking profiles you find
Init.d in Lollipop
I did not add Init.d support when building the Lollipop variant's ramdisk. Instead, /su/su.d should be used to run boot scripts. The functionality is exactly the same as the old Init.d.
Haptic feedback on soft keys
In order to avoid conflict with ROM side solutions, haptic feedback is disabled by default. It can be enabled via the following command which can be run as a boot script (eg. in /su/su.d). Command must run as root.
Code:
echo 1 > /sys/class/misc/abov_touckey/vibrate
NOTE: Above "touchkey" was misspelled in code. It should be fixed in a future update. Sorry for any inconvenience
still not fixed lol
Extra Compatibility Notes:
[url]http://forum.xda-developers.com/showpost.php?p=62226500&postcount=2[/URL]
Awesome, thanks !
Installed it and testing now
After a few days of testing !!! All I can say is, Great Kernel :good:
Good performance, great battery life
No issues so far.:highfive:
Working fine on G800FXXU1AOE3
And works great on G800FXXU1AOG2 too.
Again big Thanks Curtis ! :angel:
kernel is damn good.
Games running very fast for me with the new updated kernel
The 1.5Ghz CPU overclock is .. awesome
For additional gaming performance you can lock the GPU Frequency like this:
Shell command:
cd sys/module/mali/parameters
echo 533 > mali_dvfs_control
thats it, gpu locked to 533 mhz. Thanks to hennymcc for this commands
for example:
GTA San Andreas running now with maximum resolution+visibility graphical settings
Solid 30+ FPS :cyclops:
Sorry for noob question - can someone show me the exact syntax to enter in Terminal (or procedure) to activate OTG ? I don't seem to figure it out .
seaman5705 said:
Sorry for noob question - can someone show me the exact syntax to enter in Terminal (or procedure) to activate OTG ? I don't seem to figure it out .
Click to expand...
Click to collapse
To turn on:
Code:
su -t echo 1 > /sys/devices/virtual/sec/switch/otg
And off:
Code:
su -t echo 0 > /sys/devices/virtual/sec/switch/otg
Will ask for root.
EDIT: Enter exact commands in terminal emulator or adb shell
Thanks Curtis , but something is wrong in my case . It doesn't work and I don't understand why . After running the script , I granted the root access
, everything seemed to be ok , but nothing happens when I connect and USB key which is recognized in my S4 phone .
seaman5705 said:
Thanks Curtis , but something is wrong in my case . It doesn't work and I don't understand why . After running the script , I granted the root access
, everything seemed to be ok , but nothing happens when I connect and USB key which is recognized in my S4 phone .
Click to expand...
Click to collapse
Does anything else work? OTG also gets reset on boot, maybe it needs to be in an init.d script. I'll admit, I don't have an OTG cable to test, perhaps I should get hold of one, but the code definitely creates the right behavior (exactly the same as the other OTG kernel around here actually). Maybe switchable isn't the right way to go about it and OTG must be enabled permanently. I'll have to look into this, but in the meantime could you perhaps test with the other OTG kernel and see if it works? Also, the stick maybe might not be automatically mounting. Run "mount" in a terminal and see if it pops up. Apologies for the inconvenience.
CurtisMJ said:
Does anything else work? OTG also gets reset on boot, maybe it needs to be in an init.d script. I'll admit, I don't have an OTG cable to test, perhaps I should get hold of one, but the code definitely creates the right behavior (exactly the same as the other OTG kernel around here actually). Maybe switchable isn't the right way to go about it and OTG must be enabled permanently. I'll have to look into this, but in the meantime could you perhaps test with the other OTG kernel and see if it works? Also, the stick maybe might not be automatically mounting. Run "mount" in a terminal and see if it pops up. Apologies for the inconvenience.
Click to expand...
Click to collapse
No, it will not mount . I tested and OTG works with henny's kernel . Otherwise you made a great kernel - thanks for your work and your advices !
seaman5705 said:
No, it will not mount . I tested and OTG works with henny's kernel . Otherwise you made a great kernel - thanks for your work and your advices !
Click to expand...
Click to collapse
Attached is a build of the kernel with OTG enabled on a permanent basis. If you would not mind, could you test to see if it works? If so it will be done this way in future release, if not I will have to have a good look at any related code...
(P.S, sorry for the wait, my dual-boot was giving me issues)
CurtisMJ said:
Attached is a build of the kernel with OTG enabled on a permanent basis. If you would not mind, could you test to see if it works? If so it will be done this way in future release, if not I will have to have a good look at any related code...
(P.S, sorry for the wait, my dual-boot was giving me issues)
Click to expand...
Click to collapse
Yes , OTG works with this kernel . Great !
Note that after flashing, another reboot is needed to have the usb key properly mounting and poping up the file explorer with the key's content on connection .
Thanks !
New Version!
New version of my custom kernel released. Now includes Double Tap 2 Wake.
Is it possible to add voltage control to your kernel ? thanks .
CPU Voltage control is now implemented. Will work on a Synapse interface and the int and mif buses later today.
New Version!
Voltage control, Linux patches and fixes for DT2W waking up the screen while a call is in progress(sorry 'bout that)
Working great - I achieved good undervolting . Thanks
Hope to see a modified kernel for Lollipop too .
Description
This module is my port of Crossbreeder, the old version was designed for Android 4.4 and below. So if you try use it on Android 5.0 and above, you will have some problems with it.
But now I have fixed that problem, and have changed some of the script; which was out-of-date. I have also added some new features of my own.
Details
For those who want to know what is this mod for, here are the details:
Random/Frandom tweak
Remove /dev/random as it's blocking . Link it to non-blocking /dev/urandom. Since /dev/random is blocking and designed to protect us from Quantum alien cryptographers with mathematical certainty and urandom is non blocking pseudo-random device that most apps and OSs are using anyway and with Haveged running, is as secure anyway as it's very difficult to empty the entropy pool faster than Havege can replenish it. Pre ICS devices have a lot to gain with this but ICS+ devices show visible gains too.
Haveged/Entropy tweak
Modulate OS entropy levels for lag reduction ala Seeder. The whole OS reads either /dev/random or /dev/urandom and both need entropy. However this mod uses a completely different, lightweight and efficient random number generator called Havege . This sharply reduces cpu consumption and corresponding battery life loss compared to Seeder. It also does a better job at keeping entropy levels high hence your device is more responsive. It doesn't run in a CPU intensive loop either. The extend queue functionality has also been added to CrossBreeder. See here for another rationale favouring Havege compared to Rngd - ( Look for the limitations)
Fix "Only position independent executables (PIE) are supported" problem on Android 5.0+ device
Here is how to fix it :
1. Install the Hex Editor.
2. Open the file in Hex Editor.
3. Find the 17th number, if the number is 02, change it to 03.
4. Save the file, that's it !
[Add-on 1] Dynamic Z-RAM/LMK
This tweak will automatic find how much ram do you have, how much ram do you left, then according to these value to set zram/lmk size.
[Add-on 1] Dynamic Power Saving
Here is the original post, I found this feature in Feradroid v0.24
A little translate:
DynBS can significantly reduce power consumption without shutting down the main functionality of the Android device (such as Wi-Fi, Bluetooth, mobile Internet, screen brightness, background processes) by reducing unnecessary high-frequency CPU when not needed.
Magisk Busybox Restorer
This module will let the busybox can be used externally at Magisk v15+
By linking the busybox in /data/adb/magisk to /sbin
Only support Magisk v15+
Trouble Shooting
1. Stuck at the boot stage
---> Reboot again ---> Not work? ---> Flash it again to uninstall it.
2. Application keep crashing after installed this module
---> Just disable Dynamic LMK.
3. CTS Profile miss match
---> Enable all the ways that you can hide the magisk, if its not work, then you can try Universal SafetyNet Fix
4. Any problem about CPU frequency, like your device become so slow, or become warmer, etc.
---> Disable DynBS can fix the problem
5. How to open the setting menu?
---> Open terminal, and type "cbconf" can open it.
6. The phone shows the message of rebooting/turning off but after 30 mins ,the process is not finished
---> Try to forced shutdown
7. Busybox-ndk failed because of install CrossBreeder
---> Try to use mine busybox
This module only test on my HTC One M7 running latest Slim 7.1.2 with Magisk 15.3
Not tested with Android 8.0+ yet.
If you want to install any add-on, you must install the main mod first.
Credit
1. Crossbreeder ( https://forum.xda-developers.com/showthread.php?t=2113150 ) - For most of files
2. FeraDroid Engine ( https://forum.xda-developers.com/an...beta-feradroid-engine-v0-19-ultimate-t3284421 ) - For the Governor Tweak
3. Dynamic Power Saving ( http://4pda.ru/forum/index.php?showtopic=620736&st=1120 )
Github Link
I'm on Lineage OS, OnePlus 3T, Radioactive Kernel, and for some reason whenever I enable this module, it breaks Root (MagiskSU). I'm not sure if this is a known problem, but if not, now you know. ;P
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
loocool2 said:
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
Click to expand...
Click to collapse
I messaged Rorsch about making a thread for their module a couple of days ago, so I assume the thought just didn't occur to them to make a thread. But now it's all good because there's a thread for it
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Rorsch_X1 said:
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Click to expand...
Click to collapse
Seems to be working! Although it's not 100% stable, it's better than having a totally broken Root.
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
nan0s7 said:
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
Click to expand...
Click to collapse
As tweaks, I've removed HEBF and LSpeed apps because I've had the same idea as you. As Magisk Modules, I've installed some camera and audio mods (Some very common mods for 5X: eis, 60fps libs, surround audio mod), Universal Deep Buffer remover, Selinux permissive script and Viper. The only one which modifies build.prop is EIS module. Does Crossbreeder modify build.prop too? Should I remove EIS in order to make this work?
As CPU governor, I'm using interactive (governor profile:Glasscannon)
Rorsch_X1 said:
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
Click to expand...
Click to collapse
That's strange because usually it's very very fast, it takes something like 3-4 seconds after the vibration. Eith this module installed, I've tried to wait even 10 minutes without any success.
Now I'll retry and send you Magisk log.
Sent from my Nexus 5X using XDA Labs
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Didgeridoohan said:
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Click to expand...
Click to collapse
I know that and I've tried it but it didn't work.
Edit: Now it is working. what
Thanks for your suggestion.
Sent from my Nexus 5X using XDA Labs
crayola555 said:
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Click to expand...
Click to collapse
I am a big fan of crossbreeder... However...
Iirc without frandom... You are not actually generating "random"
And according to what I have read (stop me if I'm wrong)... The less "lag" you are seeing is from that random number generation keeping your processor a little more ramped up... Equivalent to turning touchboost up a notch... Or raising your cpu min frequency...
Sent from my Nexus 6 using Tapatalk
This work on rooted s7 w/ Exynos CPU?
pan.droid said:
This work on rooted s7 w/ Exynos CPU?
Click to expand...
Click to collapse
Yes, it works on all ARM devices.
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Rorsch_X1 said:
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Click to expand...
Click to collapse
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
edoardotavecchio said:
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
Click to expand...
Click to collapse
Maybe the some script conflict with your system, try this version, you can enable/disable the tweak by yourself.
https://drive.google.com/open?id=0B1nFPsNMRIiiM2xocl9RTGt3OEk
After install this version, you need to go to /data/CrossBreeder, open the file with text editor then change the 0 to 1 to enable the tweak, I disable all in these config files.
P.S. Don't edit the CONF
Requirements :-
1. Rooted phone with Magisk installed.
2. Xposed framework (install 'busybox' module --reboot-- install 'riru core' module --reboot-- install 'riru edxposed sandhook' module --reboot--) & later install the 'edexposed manager' apk.
3. Magisk modules - 1. Debloter 2. Bromite Systemless Webview (optional but recommended)
4. Greenify app (full version i.e. donation package)
5. Swift Installer
Note - Please reboot after each magisk module is installed. If rebooting after multiple module installed at once phone may stuck on bootloop.
Steps -
Kernel Adiutor
1. Install FKM (Franko kernel manager) - go to the app ->
click on CPU tab ->
For 'Big Cores' set maximum frequency to 2169 Mhz ->
later set CPU governor to 'powersave' only for 'Big Cores -> toggle the option to 'on'.
Thats it, leave the 'little cores' as it is. -> REBOOT
2. Ater the FKM settings has been applied, install the 'Kernel Adiutor' app ->
click the 3 lines options from the top left screen ->
Click on 'CPU' tab -> For 'Big Cores' set maximum frequency to 2169 Mhz ->
set CPU governor to 'powersave' only for 'Big Cores ->
set CPU governor to 'schedutil' for 'little Cores'. turn on 'Apply on boot' option.
3. Now go to the 'GPU' tab from 3 lines menu -> set CPU governor to msm-adreno-tz' ->turn on 'Apply on boot' option.
4. Now go to the 'Low memory killer' tab from 3 lines menu -> click once on 'very light' -> turn on 'Apply on boot' option.
5. Uninstall the FKM app. REBOOT.
Debloat
Warning : For this please keep ready the LGUP tool and proper .kdz file for your device [i repeat do not ignore this]
Here are some of the apps that i debloted using 'debloat' magisk module->
1. Photos
2. Lens
3. Google Play Music
4. Calender (dont debloat if you want to sync it)
5. Chrome
6. Docs
7. Google text-to-speech engine
8. Gmail
9. Duo
10. Slides
11. Sheets
12. Gboard (Google keyboard)
13. Google Play movies
14. Google Maps
15. Google News
16. Facebook App Manager
17. Facebook App Installer
18. Youtube (If you debloat it, it wont run, it needs system access. Since i used Youtube Vanced i dont care)
Until this after rebooting all worked well.
But After debloating '19. Google' and rebooting my phone, it bootlooped. Thus, I have to LGUP and select the 'upgrade' option and flash the stock again and it worked fine and i successfully debloated the 'Google' app too. This is the main battery culprit. Or you you can just disable it. see if it works for you or not.
Note :- Debloat doesn't mean uninstalling, it means converting system apps to normal apps just opposite what the 'Sytemizer' magisk module does.
Greenify
1. install the greenify app (full version needed) -> then go to the Edxposed Manager -> click on 3 line menu -> click on module -> turn on 'greenify' -> REBOOT.
2. Open Greenify app -> Give it all the permissions needed -> now to go the setting from the 3 dots menu -> It should be showing working mode 'Root + Boost (Xposed)'.
3. Smart Hibernation = Enabled; Aggressive Doze = Enabled; Wake-up tracking and cut-off = Enabled; Automatic Hibernation = select it; Always ignore backgrounf free = select it.
4. Now click on Xposed-based features -> select each and every options.
5. Reboot the greenify app.
6. Now on the main screen of greenify, click on the 'zzz' icon and select the apps it recommends and most of the apps u dont care much about and click them for sleep just once and never again.
Swift Installer -
1. If you are using substratum please STOP. It drains a hell lot of battery.
2. Use swift installer instead for theming various apps you like.
3. And for system theming any good theme from PlayStore could work.
Major Note :- This isn-t the fool proof method of increasing battery life out of nowhere without losing some performance.
Sure it will, but you will even not notice it and will easily get you through it. Atleast it happens well with me
For Gamers : Just take away the root access from the Kernel Aduitor from Magisk Manager and reboot when you want to play system heavy games.
For All : if you notice any lag which annoys you, please start tweaking the 'Greenify' first rather than going directly after 'Kernel Aduitor'.
Please provide the precious feedback and other tweaks and tricks here to further improve the Battery and Performance of our beloved Phone LGv40.
I will be posting battery backup, SOT proofs stay tuned.
Using of Hotspot Still drains battery like water.
smartybro7788 said:
Requirements :-
1. Rooted phone with Magisk installed.
2. Xposed framework (install 'busybox' module --reboot-- install 'riru core' module --reboot-- install 'riru edxposed sandhook' module --reboot--) & later install the 'edexposed manager' apk.
3. Magisk modules - 1. Debloter 2. Bromite Systemless Webview (optional but recommended)
4. Greenify app (full version i.e. donation package)
5. Swift Installer
Click to expand...
Click to collapse
What system are you on? I'm on UA20a Pie! Will it matter?
smartybro7788 said:
Requirements :-
1. Rooted phone with Magisk installed.
2. Xposed framework (install 'busybox' module --reboot-- install 'riru core' module --reboot-- install 'riru edxposed sandhook' module --reboot--) & later install the 'edexposed manager' apk.
3. Magisk modules - 1. Debloter 2. Bromite Systemless Webview (optional but recommended)
4. Greenify app (full version i.e. donation package)
5. Swift Installer
Note - Please reboot after each magisk module is installed. If rebooting after multiple module installed at once phone may stuck on bootloop.
Steps -
Kernel Adiutor
1. Install FKM (Franko kernel manager) - go to the app ->
click on CPU tab ->
For 'Big Cores' set maximum frequency to 2169 Mhz ->
later set CPU governor to 'powersave' only for 'Big Cores -> toggle the option to 'on'.
Thats it, leave the 'little cores' as it is. -> REBOOT
2. Ater the FKM settings has been applied, install the 'Kernel Adiutor' app ->
click the 3 lines options from the top left screen ->
Click on 'CPU' tab -> For 'Big Cores' set maximum frequency to 2169 Mhz ->
set CPU governor to 'powersave' only for 'Big Cores ->
set CPU governor to 'schedutil' for 'little Cores'. turn on 'Apply on boot' option.
3. Now go to the 'GPU' tab from 3 lines menu -> set CPU governor to msm-adreno-tz' ->turn on 'Apply on boot' option.
4. Now go to the 'Low memory killer' tab from 3 lines menu -> click once on 'very light' -> turn on 'Apply on boot' option.
5. Uninstall the FKM app. REBOOT.
Debloat
Warning : For this please keep ready the LGUP tool and proper .kdz file for your device [i repeat do not ignore this]
Here are some of the apps that i debloted using 'debloat' magisk module->
1. Photos
2. Lens
3. Google Play Music
4. Calender (dont debloat if you want to sync it)
5. Chrome
6. Docs
7. Google text-to-speech engine
8. Gmail
9. Duo
10. Slides
11. Sheets
12. Gboard (Google keyboard)
13. Google Play movies
14. Google Maps
15. Google News
16. Facebook App Manager
17. Facebook App Installer
18. Youtube (If you debloat it, it wont run, it needs system access. Since i used Youtube Vanced i dont care)
Until this after rebooting all worked well.
But After debloating '19. Google' and rebooting my phone, it bootlooped. Thus, I have to LGUP and select the 'upgrade' option and flash the stock again and it worked fine and i successfully debloated the 'Google' app too. This is the main battery culprit. Or you you can just disable it. see if it works for you or not.
Note :- Debloat doesn't mean uninstalling, it means converting system apps to normal apps just opposite what the 'Sytemizer' magisk module does.
Greenify
1. install the greenify app (full version needed) -> then go to the Edxposed Manager -> click on 3 line menu -> click on module -> turn on 'greenify' -> REBOOT.
2. Open Greenify app -> Give it all the permissions needed -> now to go the setting from the 3 dots menu -> It should be showing working mode 'Root + Boost (Xposed)'.
3. Smart Hibernation = Enabled; Aggressive Doze = Enabled; Wake-up tracking and cut-off = Enabled; Automatic Hibernation = select it; Always ignore backgrounf free = select it.
4. Now click on Xposed-based features -> select each and every options.
5. Reboot the greenify app.
6. Now on the main screen of greenify, click on the 'zzz' icon and select the apps it recommends and most of the apps u dont care much about and click them for sleep just once and never again.
Swift Installer -
1. If you are using substratum please STOP. It drains a hell lot of battery.
2. Use swift installer instead for theming various apps you like.
3. And for system theming any good theme from PlayStore could work.
Major Note :- This isn-t the fool proof method of increasing battery life out of nowhere without losing some performance.
Sure it will, but you will even not notice it and will easily get you through it. Atleast it happens well with me
For Gamers : Just take away the root access from the Kernel Aduitor from Magisk Manager and reboot when you want to play system heavy games.
For All : if you notice any lag which annoys you, please start tweaking the 'Greenify' first rather than going directly after 'Kernel Aduitor'.
Please provide the precious feedback and other tweaks and tricks here to further improve the Battery and Performance of our beloved Phone LGv40.
I will be posting battery backup, SOT proofs stay tuned.
Click to expand...
Click to collapse
Hey all. To be honest this is the best battery saving guide among others after searching it for so long. I'm using LG V40 V409N with magisk root, of course. I would able to get close to 8 hours of SOT. Followed it to the letter. Two minor differences are my phone didn't boot loop after debloat Google and I'm using Franco Kernel app to substitute Kernel Adiutor. I'm satisfied with the result. I used to get only 3 to 4 hours of SOT. So increment of double the SOT is awesomely welcome.
I tried it with Oneplus Nord that my wife is currently using and can get 7 hours SOT with it. That is way better than 4 hours of SOT before. One thing is clear, this guide is working. Solute to smatybro7788 that make this guide. And thank you.
Battery has been my concern with this phone. Rom is not stable after root and crossflash i noticed that after a while you will start to see screen flickers here where battery consumption going crazy a factory reset will put things back to normal till screen flickers again.I am not an expert i know a little i discovered that if i go to maximum power saver phone go easy on battery magically (whyyyy) that's why this tutorial is aiming to address this issue thank you.