Related
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
Hi,
Good job, just one thing, i use Eviollet kernel (svs) and there's a step at 128 mhz.
The apps doesn't show these step.
It Would be great if you can implement it.
Otherwise i found no bug.
Thx in advance.
sffmandrake said:
Hi,
Good job, just one thing, i use Eviollet kernel (svs) and there's a step at 128 mhz.
The apps doesn't show these step.
It Would be great if you can implement it.
Otherwise i found no bug.
Thx in advance.
Click to expand...
Click to collapse
The app skips the first frequency because on a lot of phones its a.useless frequency like 19mhz. Thanks for letting me know though. I will add an exception and upload a new version later.
Sent from my ADR6300 using XDA App
7/31/11 - Preview 5-4
Minor change to no longer skip the first frequency. On many phones the first frequency is a useless frequency like 19mhz so the app was set up to skip that frequency. This is only a temporary fix until I change it to display only the available frequencies instead of all of them.
Sounds interesting, will have a go
Hi,
Thx chad0989, now it works at 128 mhz
sffmandrake said:
Hi,
Thx chad0989, now it works at 128 mhz
Click to expand...
Click to collapse
Great. I just sent you a PM.
Works great thanks!
IncrediControl v1.0!
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
Good job. Works on cm7 nightly with manU kernel 2.1.1.
chad0989 said:
The app skips the first frequency because on a lot of phones its a.useless frequency like 19mhz.
Click to expand...
Click to collapse
The eviollet Kernel implements AXI @ 128Mhz, which drops the bus down to 19Mhz which potentially could save more battery
rootSU said:
The eviollet Kernel implements AXI @ 128Mhz, which drops the bus down to 19Mhz which potentially could save more battery
Click to expand...
Click to collapse
But the actual cpu speed still never drops below 128mhz if I'm not mistaken (at least thats how it is on the inc, its possible to enable the use 19mhz cpu speed, but the phone is unusable). So the cpu voltage for 19mhz would never be used. I have changed the app now though to show all cpu frequencies available for use, so if you did enable the use of 19mhz cpu speed (you have to comment out a line in the acpuclock file), it would show up.
Hopefully that clears up confusion.
IncrediControl v1.3
Major changes include:
Ad Free has now been turned into a key that removes the ads from the free version. This allows donors who have downloaded the ad free version from the site to update through the market.
HAVS voltage checking. Minimum voltages can no longer be set higher than maximum voltages.
Boot voltages are now stored in the application’s data directory. Boot settings will now persist if you update your ROM or restore the application and data from a backup.
IncrediControl v1.4:
This is mostly a bug fix release but I have also added:
Automatic detection of the minimum and maximum voltages supported by your kernel
Unless any more bugs arise, the next release will have some new goodies to play with...
http://www.incredikernel.com or from the market.
I'm making an enquiry for a friend who uses his HTC desire with RCMix S v2.0 Evolutionary Sense using SNQ v05 kernel. Does this Rom / kernel meet the InvrediControl system requirements?
One other question, in other utils I've used in the past they also supply a "reset" zip which can be used to revert the settings back to default in the event if instability/freeze (requires flash from recovery). Do you see value in creating a similar zip for over agressive UV?
Thanks again for a wonderful utility. Can't wait to try it.
Sent from my Desire HD using XDA App
fidoedidoe said:
I'm making an enquiry for a friend who uses his HTC desire with RCMix S v2.0 Evolutionary Sense using SNQ v05 kernel. Does this Rom / kernel meet the InvrediControl system requirements?
One other question, in other utils I've used in the past they also supply a "reset" zip which can be used to revert the settings back to default in the event if instability/freeze (requires flash from recovery). Do you see value in creating a similar zip for over agressive UV?
Thanks again for a wonderful utility. Can't wait to try it.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I don't believe that kernel has the sysfs interface for adjusting voltages. You can still give it a shot though. The app will let you know if the kernel doesn't have the correct interface.
I also have a reset zip. It's on the site and there is a link in the OP.
SNQ anyone?
Ahhhw...no love for the wildly popular SNQ Kernal?!
SilverHawk2 said:
Ahhhw...no love for the wildly popular SNQ Kernal?!
Click to expand...
Click to collapse
The kernel dev has to implement the interface in order to use the app. Since I don't believe that the source for the GB kernel has been released yet for the desire, the dev won't be able to implement the interface until it is.
chad0989 said:
The kernel dev has to implement the interface in order to use the app. Since I don't believe that the source for the GB kernel has been released yet for the desire, the dev won't be able to implement the interface until it is.
Click to expand...
Click to collapse
Thanks for the heads up. Next time I have access to the phone I will install and see what unfolds. But from what you said I'm not expecting much with SNQ.
Maybe time to suggest to my friend a new Rom
Title says everything.
Sorry if it is a repost, I've tried finding some answers but no luck.
Bump
184 views, not one reply.
But thank you, trying to learn this myself at the moment.
No luck on info here but will try to find some!
Err, I just read from the official post. O /C normally can set sleep and wake speed. Bypass will make it run at same speed.
Sent from my HTC Sensation Z710e using XDA App
I know nothing technical about it but I'm going by common knowledge and sense here:
O/C Daemon function uses O/C Daemon values and also O/C Daemon method of switching profiles (favourable because it switches with virtually no lag).
Bypass function essentially bypasses the O/C Daemon method of switching frequencies and targets the CPU frequency directly.
This all started a couple weeks ago when I posted on a thread about ICS Kernels that if you wanted a different ICS kernel, you should compile your own. Well, just to make sure I wasn't being too far out of line, I did. The last two weeks has given me confidence that it is stable, at least as I use my phone, and hopefully will take some of the pressure off Bryan and the others working on a 3.x kernel for ICS and beyond.
With the way I've tuned the Smartassv2 governor, I find this kernel to be gentle on the battery and snappy in responding, even in situations like an incoming call bringing the phone out of sleep.
I have tested this kernel with AOKP. It should also work with CM9 or any of the various spin-offs of the TeamAcid codebase.
Team Acid has incorporated this work into their mainline kernel. The current CM9/AOKP builds effectively supply v0.8.1 or later
See the second post in this thread for Hefe Kernel of Darkness if you are also looking to turn off the touchkey backlights.
Please keep questions to the Q&A Thread
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM 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 point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
Features:
Overclock (OC) (can set through AOKP ROM Control)
Undervolt (UV) (System Tuner and Voltage Control now working)
Advanced governor options
SmartassV2
OndemandX
Intellidemand
Lulzactive
Kernel optimization
Known Issues:
AOKP ROM Control can't read or set UV levels
Minimum CPU speed permitted "randomly" changes between 100 and 200 MHz
VCO may false lock on OC speeds (just as AntonX's GB kernel will)
Intellidemand and Lulzactive drivers were felt by AntonX to be too unreliable for daily use
Not a drop-and-go install if your non-TeamAcid ROM isn't using the bcm4329 driver
Most anything that is a known issue with the TeamAcid ICS kernel
ROM/App Issues:
Recovery may not "flash" the WiFi driver, especially when flashing ROM, gapps, and kernel in one "session." Re-flashing seems to resolve this.
On cMIUI, it has been reported that using NSTools to set smartassv2 governor causes boot loops.
Thanks
TeamAcid, for bringing ICS and AOKP to the phone at all
TeamAcid, for actually posting their sources, in full
AntonX, for taking the time to add OC/UV functionality to the GB kernel
Teamhacksung, for various drivers and bits
TeamAcid, for hopefully not complaining that I didn't replace their boot logos
Bhundven, for pulling everything together and his ongoing work on a 3.x kernel
Change List
v0.8.1 -- 2012/06/19 -- MD5: 1ae5bba6dbacb8cbef5b739075818300 hefe-kernel-v0.8.1.zip
UV can now be set using System Tuner or Voltage Control
v0.8.0 -- 2012/06/16 -- MD5: 4e99cc054f6902af2447f0bdc91e39c4 hefe-v0.8.0.zip
Initial release
Installing
Download the zip and copy to your phone's microSD
Reboot to recovery
Flash
Reboot
If WiFi does not work after flashing, you might want to flash again. See Rom/App Issues, above.
Suggested Configuration
Governors
If you don't know much about governors, you can start here. I've been using the smartassV2 governor. Either that or the ondemandX governor probably should be your first choice. They can be selected in the AOKP ROM Control app, under Performance.
I have tuned the smartassv2 governor differently than AntonX did. It is set to drive to significantly lower CPU speeds in "idle" than the GB equivalents. This should help battery life. Please let me know in the Q&A thread if you are seeing unexpected sluggishness.
Undervolting (UV)
Default settings are 25 mV less than the "stock" kernel supplies.
Voltages can now (v0.8.1) be easily set using System Tuner or Voltage Control (and probably a few others)
I'm aware of the issues with AOKP ROM Control not being able to write and read the voltages. It's on my list to resolve.
Overclocking (OC)
If you aren't willing to kill your phone prematurely, do not overclock. If your phone already runs hot, do not overclock. If you run Quadrant tests all the time and have your governor set to "performance" all the time, do not overclock.
WIth a conservative governor, such as smartassv2, with the kernel defaults, the phone shouldn't be spending much time above 1000 MHz. If you used the AntonX kernels under GB, you probably have a feeling what your phone can reliably handle. I personally wouldn't push things past 1200 MHz.
Future Plans
Perhaps not in this order
Rework clock timings to prevent false locks
Resolve app AOKP ROM Control access to UV tables
Add Badass governor
Add additional schedulers
Source code on Github, hefe-kernel branch. Compile with TeamAcid's AOKP build environment on a supported platform.
Hefe Kernel Of Darkness
This is a hack, a pretty ugly one at that.
This is a "quick build" to provide a kernel that comes close to disabling the touchkey backlights "completely." (They do turn on while you are touching the key.)
BLN may or may not work. I have not tested it. At least one user has reported that it is working.
Known issues beyond those in the standard Team Acid CM9/AOKP kernels:
Long-press of touchkeys does not work (b2) -- resolved in b3
This is equivalent to the current TeamAcid CM9 kernel with the exception of the changes to the touchkey driver to:
Turn off the backlights on every touch
Remove the turn-on of the backlights at driver resume
Have the sysfs entry that controls the backlight turn it off even if asked to turn it on
This won't "fix" auto-brightness on your ROM. Auto-brightness requires not only kernel changes, but some libraries and changes to the Android Framework.
It should work with TeamAcid's current CM9 and AOKP builds.
Hefe-KOD-b3a.zip uses a new installer that should resolve some of the issues related to the WiFi module not being installed.
This is not a TeamAcid-supported kernel.
Change List:
Code:
79ec09ecc7d9b544d66d8d1f6ece1f8e Hefe-KOD-b3a.zip
* Same kernel and WiFi module as Hefe-KOD-b3.zip
* New installer to hopefully resolve the module not being installed
ff14d7f2237bc7462b357e8bb33e6573 Hefe-KOD-b3.zip
* Resolves issue with long-press actions not being recognized
69361b72a441ffda6e11f3ad52b9812f Hefe-KOD-b2.zip
* Initial release - has problems with long-press actions
Source on github, hefe-kernel-of-darkenss branch. Build using Team Acid AOSP-based build environment (CM9/AOKP).
(ibid)
Good work bro seems your OP has stuff written twice?
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
Hey jeff, You can add this frequencies to your kernel I have thorougly tested this for a long time and they are very stable and reliable ones.
1.5 OC
Core Voltage: 1400 mV
Internal Voltage: 1175mV
1.6 OC
Core Voltage: 1435 mV
Internal Voltage: 1195mV
1.6 is very stable and I normally use it when the phone is slow, but I would recommend it running it in times where you really need it like in bench marking or apps.For games this frequency doesn't do much but for them i would use 1.5 since it doesn't put way too much heat on the phone. This frequency is special because it actually boosts your cell download speed by about 35%~40% because it process data much faster.
Oi what's a thus? A new kernel with full sources posted . Good work, you're going to make a lot of people happy
tichs said:
Hey jeff, You can add this frequencies to your kernel I have thorougly tested this for a long time and they are very stable and reliable ones.
1.5 OC
Core Voltage: 1400 mV
Internal Voltage: 1175mV
1.6 OC
Core Voltage: 1435 mV
Internal Voltage: 1195mV
1.6 is very stable and I normally use it when the phone is slow, but I would recommend it running it in times where you really need it like in bench marking or apps.For games this frequency doesn't do much but for them i would use 1.5 since it doesn't put way too much heat on the phone. This frequency is special because it actually boosts your cell download speed by about 35%~40% because it process data much faster.
Click to expand...
Click to collapse
It's impossible to say that those OC's would work on every SGS4G. I for one know that my phone will not handle an OC above 1.4ghz. The 1.2ghz threshold that OP mentioned is a safe number that every SGS4G should be able to handle.
Personally I think anything above 1.3ghz is superfluous.
Tested this out and the only issue I have come across is WiFi does not work.
Code:
D/dalvikvm( 969): GC_CONCURRENT freed 574K, 36% free 2616K/4035K, paused 1ms+2ms
D/LocalBluetoothProfileManager( 2508): Adding local A2DP profile
D/LocalBluetoothProfileManager( 2508): Adding local HEADSET profile
D/LocalBluetoothProfileManager( 2508): Adding local OPP profile
E/WifiStateMachine( 226): Failed to load driver!
D/LocalBluetoothProfileManager( 2508): LocalBluetoothProfileManager construction complete
E/WifiStateMachine( 226): DriverFailedState
I am going to try reinstalling the kernel to see if it was just a fluke, but just in case also attached is a logcat report from aLogcat.
A great start, thanks Jeff!
EDIT Disregard a reflash of the kernel + dalvik wipe did the trick. Great job!
They have worked in my phone for a very long time many moths. The phone is totally capable of this
Sent from my SGH-T959V using xda app-developers app
crackpot said:
Tested this out and the only issue I have come across is WiFi does not work.
Code:
D/dalvikvm( 969): GC_CONCURRENT freed 574K, 36% free 2616K/4035K, paused 1ms+2ms
D/LocalBluetoothProfileManager( 2508): Adding local A2DP profile
D/LocalBluetoothProfileManager( 2508): Adding local HEADSET profile
D/LocalBluetoothProfileManager( 2508): Adding local OPP profile
E/WifiStateMachine( 226): Failed to load driver!
D/LocalBluetoothProfileManager( 2508): LocalBluetoothProfileManager construction complete
E/WifiStateMachine( 226): DriverFailedState
I am going to try reinstalling the kernel to see if it was just a fluke, but just in case also attached is a logcat report from aLogcat.
A great start, thanks Jeff!
EDIT Disregard a reflash of the kernel + dalvik wipe did the trick. Great job!
Click to expand...
Click to collapse
When reporting issues, please also specify the ROM you installed the kernel with. Usually the "Failed to load driver" issue, is because the /system/etc/wifi/wifi.conf is trying to load the wrong driver.
Not a kernel issue, but a rom issue.
tichs said:
They have worked in my phone for a very long time many moths. The phone is totally capable of this
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
My phone will no o/c over 1.4 with this kernel, the phone may be capable but for some reason not every sgs4g will go as high as others. Same can be said for many phone models.
Sent from my SGH-T959V using xda premium
jeffsf on ics slim v2 the bcm4329.ko module is not being replaced. Not sure if the install script isnt working or another issue. This was early this morning so anything is possible.
bhundven said:
When reporting issues, please also specify the ROM you installed the kernel with. Usually the "Failed to load driver" issue, is because the /system/etc/wifi/wifi.conf is trying to load the wrong driver.
Not a kernel issue, but a rom issue.
Click to expand...
Click to collapse
It started after flashing the kernel package with TWRP, so I figured it was kernel related. A simple reflash and dalvik clear fixed any issues. Not that it matters at this point but i'm on AOKP M6B4.
Twrp doesn't seem to mount system properly. I had smooth sailing on cm9.
And I love the kernel.
Sent from my SGH-T959V using xda premium
This kernel fixes Voodoo Sound! Tested on both MIUI roms and Slim ICS and Voodoo is finally working without having to reboot. Thank you so much. All other features work as OP states.
Sent from my SGH-T959V using xda app-developers app
htaak said:
This kernel fixes Voodoo Sound! Tested on both MIUI roms and Slim ICS and Voodoo is finally working without having to reboot. Thank you so much. All other features work as OP states.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Voodoo sound is confirmed working here as well on beam..
Sent from my SGH-T959V using xda premium
Thank u for this kernel. Any help you need i am available. Looking forward to updates. Going to try this on gummy...
Sent from my SGH-T959V using XDA Premium HD app
Works on gummy. I tried with setcpu. Allows up to 1.4, i like 1.2. Voodoo sound works. I think im gonna switch yo aokp and try this kernel as gummy isnt really being supported anymore, drains battery too much. Love the rom tho. Thanks
eollie said:
jeffsf on ics slim v2 the bcm4329.ko module is not being replaced. Not sure if the install script isnt working or another issue. This was early this morning so anything is possible.
Click to expand...
Click to collapse
Thanks for the report. Please let me know if this happens again. I tried it today and was successful in flashing Slim and then Hefe and connecting to WiFi. It did remind me how much I prefer TWRP over CWM.
man, you worked it out!!! Thaaaanks a ton!!!! You rock!
On my attempts, when I flashed AOKP and Hefe on the same recovery-boot, wifi ended up broken. Rebooting to recovery and flashing Hefe again fixed it.
Guessing that the 'broken' flashes happen when it's flashed without actually booting the ROM in the interim. Since I don't remember that happening when I flashed it onto CM9 earlier.
Whenever my tablet is updating apps it begins to lag tremendously. I'm running cm11 but this problem has been occurring since I was on the stock ROM. I've even flashed a kernel which overclocks to 1.7 ghz and with the interactive governor running it will still lag while updating apps. I tried to create a tasker profile which would initiate the performance governor whenever the play store app is open, but it doesn't help. Any ideas?
ChiefIlliniwek5 said:
Whenever my tablet is updating apps it begins to lag tremendously. I'm running cm11 but this problem has been occurring since I was on the stock ROM. I've even flashed a kernel which overclocks to 1.7 ghz and with the interactive governor running it will still lag while updating apps. I tried to create a tasker profile which would initiate the performance governor whenever the play store app is open, but it doesn't help. Any ideas?
Click to expand...
Click to collapse
Yep I've always got that. Someone said that it is a problem with the tablets hardware I/O, theres not much you can do about it.
ChiefIlliniwek5 said:
Whenever my tablet is updating apps it begins to lag tremendously. I'm running cm11 but this problem has been occurring since I was on the stock ROM. I've even flashed a kernel which overclocks to 1.7 ghz and with the interactive governor running it will still lag while updating apps. I tried to create a tasker profile which would initiate the performance governor whenever the play store app is open, but it doesn't help. Any ideas?
Click to expand...
Click to collapse
Try using the ROW I/O scheduler that should be optionally available in most kernels.
It favours read operations over the slow write operations in the background.
Sent from my TF300T using Tapatalk
You should really change your I/O scheduler and run TRIM and maybe change your Entropy so when I/O lag does come, its not as bad.
Sent from my One X using xda app-developers app
Introducing RebelKernel for all variants of the Moto E4 'perry' device. Upstreamed to the latest linux-stable 3.18 tag and loaded with features and optimizations. The aim of this kernel is to make the User Experience as smooth and efficient as possible, while also bringing in features like DoubleTap2Wake (DT2W), KCAL (advanced color control processing), and USB OTG that help bring this budget phone on par with mid-end devices.
A lot of testing has been done to get this kernel stable, however there is always a chance that flashing this kernel could leave something not working correctly. Please take logs (dmesg and ramoops) in this event and send them to me.
Features:
* Linux-stable: 3.18.63 -> 3.18.134
* F2FS Loopback Bug patched
* LZ4 Compression
* CPU Input Boost driver
* KCAL color control driver
* DT2W driver
* Boeffla Wakelock Blocker driver
* Wireguard Support
* XPad Rumble and LED support
* USB OTG Native support
* USB HID Keyboard support
* Cmdline flags removed to pass SafetyNet
* Toolchain: GCC 4.9.4 --> Linaro 7.4.1
* I/O Schedulers: Zen, Maple
* Governors: Electron, Zzmoove, Lionfish
* Hotplugs: Alucard
* GPU: Adreno Idler, Adreno Boost
* TCP: Westwood
* FSync On/Off
* Swappiness: 15
* VFS Cache Pressure: 10
* Drastically reduced logging overhead and spam
* Migrated many workqueues to Power Efficient WQs
Installation:
1) BACKUP. Always have a recent system backup when flashing anything.
2) Download the zip from the link below and flash from TWRP.
3) If you get bootloops or issues, please take kernel logs and logcats (if booted) and report back so I can address the issue.
Please give feedback. A lot of work is being put into this kernel so I hope it improves your experience.
Download:
Version: 2.0
https://mega.nz/#!M6J2ESiZ!xUpI5yQvhpta3TSWr_MQQYmi-xFhiEEJa_JnGBIfdww
Source:
* Branch 'rebel'
https://github.com/RebelLion420/kernel_perry
Credits:
@squid2
@facuarmo
@jasonmerc
*** While donating is not required to use my work, it is certainly appreciated. Thanks in advance!
https://paypal.me/rebelliouslion
Note:
I posted this on XDA to bring attention to my project, but I will not be regularly updating this thread. You can find the active thread on Android Forums
androidguy99 said:
Why? I had nothing to do with this
Click to expand...
Click to collapse
I removed the mention, I just felt that you contributed to the project as a whole. Also, I was stumped until you posted trees for us and then I got building again since I broke my last repo lol. But as you wish
Damn, with all those features you almost made me wish I still had my e4
Almost
Very nice work @RebelLion_
This kernel is extremely fluid and responsive. The baked in KCAL works great with Kernel Adiutor-Mod in customizing the display contrast & vibrance with the presets included in the app. No noticeable lags or instabilities. Wonderful work. Thank you for your contributions and hard work.
AeonFlux1603 said:
Very nice work @RebelLion_
This kernel is extremely fluid and responsive. The baked in KCAL works great with Kernel Adiutor-Mod in customizing the display contrast & vibrance with the presets included in the app. No noticeable lags or instabilities. Wonderful work. Thank you for your contributions and hard work.
Click to expand...
Click to collapse
I'm glad you like it, it was a lot of hard work lol. Don't forget to turn on DT2W in Kernel Adiutor 'Gestures' as well, and look through all the settings to see everything that's included. I know CPU Input Boost is disabled by default and requires a little tuning to get right. I have it set to boost to 1094 for 250 ms, which might not be as big of an improvement I hoped for since there are only 4 clock frequencies for the cpu to cycle through. But I'm working on fixing that too if it's possible for this device
jasonmerc said:
Damn, with all those features you almost made me wish I still had my e4
Almost
Click to expand...
Click to collapse
Almost is good enough lol
RebelLion_ said:
I'm glad you like it, it was a lot of hard work lol. Don't forget to turn on DT2W in Kernel Adiutor 'Gestures' as well, and look through all the settings to see everything that's included. I know CPU Input Boost is disabled by default and requires a little tuning to get right. I have it set to boost to 1094 for 250 ms, which might not be as big of an improvement I hoped for since there are only 4 clock frequencies for the cpu to cycle through. But I'm working on fixing that too if it's possible for this device
Click to expand...
Click to collapse
1094 MHz for 250ms appears to give a nice little boost when the load gets heavy. If you can improve upon that, you are a beast indeed. I have also set DT2W in Kernel Adiutor as you advised. And the Gesture settings....Wow!!
Don't cut yourself short with this nice piece of work. If you never added another mod, I would continue using this kernel over bone stock any day. I'm with zeal to see such a dedicated and skilled dev on this device. My many thanks are most sincere.
Out of curiosity, is this kernel compiled using the latest upstream sources?
Wow! I'm glad you finally got it working. Thanks for giving me some credits (although I'm more or less just a cherry-pick machine lel), I'll get an eye on this thing, probably even grab some patches for the msm8916 repo and maybe I'll send a PR at some point .
Been using this kernel since it's beta releases and it's amazing. I love the work put into this!
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
Yes it is. As far as I know
AeonFlux1603 said:
1094 MHz for 250ms appears to give a nice little boost when the load gets heavy. If you can improve upon that, you are a beast indeed. I have also set DT2W in Kernel Adiutor as you advised. And the Gesture settings....Wow!!
Don't cut yourself short with this nice piece of work. If you never added another mod, I would continue using this kernel over bone stock any day. I'm with zeal to see such a dedicated and skilled dev on this device. My many thanks are most sincere.
Out of curiosity, is this kernel compiled using the latest upstream sources?
Click to expand...
Click to collapse
Yes it is
Your kernel fixed my sd card storage access problem! After unlocking/no-verity'ing, some apps couldn't access sdcard storage (Google Maps and Here Maps were a few). Your kernel allows them to finally access sd card storage perfectly! What did you do? Thank you!
---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------
Follow up question: this new kernel eliminates the need for dm-no-verity, correct?
@RebelLion_, I wanted to let you know also that the Lionfish CPU governor is absolutely amazing. Handles heavy loads with ease.
zahna said:
Your kernel fixed my sd card storage access problem! After unlocking/no-verity'ing, some apps couldn't access sdcard storage (Google Maps and Here Maps were a few). Your kernel allows them to finally access sd card storage perfectly! What did you do? Thank you!
---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------
Follow up question: this new kernel eliminates the need for dm-no-verity, correct?
Click to expand...
Click to collapse
I would think @RebelLion_ removed dmverity in his kernel.
If he has, definitely list that in your features dude. If not, that's a great (fairly straightforward) feature to add.
Noice work bro
madbat99 said:
I would think @RebelLion_ removed dmverity in his kernel.
If he has, definitely list that in your features dude. If not, that's a great (fairly straightforward) feature to add.
Noice work bro
Click to expand...
Click to collapse
@madbat99, I decompiled this kernel with an image kitchen; the ramdisk appears to have AVB/dm-verity set to disabled. Also, force encryption seems to be set to opt-encrypt. And, to note, I am using this kernel on my CDMA xt1766 "SPerry," and I've experienced no adverse issues or problems.
Very nice. An updated kernel with f2fs loopback bug patched is great news for this device. Magisk with no extra junk. (F2fs loopback bug workaround)
madbat99 said:
Very nice. An updated kernel with f2fs loopback bug patched is great news for this device. Magisk with no extra junk. (F2fs loopback bug workaround)
Click to expand...
Click to collapse
Amen @madbat99. Nice to use a root file explorer without kernel panic/dead lock. The Alucard hotplug on this kernel is solid as well. Man, this is just an all around badass piece of work. Excellent. Hey @madbat99, do you know if there are any CPU/SoC differences between the SPerry & the Perry?
madbat99 said:
Very nice. An updated kernel with f2fs loopback bug patched is great news for this device. Magisk with no extra junk. (F2fs loopback bug workaround)
Click to expand...
Click to collapse
OP fixed the F2FS bug as well?!? I didn't even think to check on that! IMO, his kernel has saved the Moto E4.
Now I'm wondering if this kernel has also fixed the echo cancellation problem with 3rd party ROMs...
AeonFlux1603 said:
Amen @madbat99. Nice to use a root file explorer without kernel panic/dead lock. The Alucard hotplug on this kernel is solid as well. Man, this is just an all around badass piece of work. Excellent. Hey @madbat99, do you know if there are any CPU/SoC differences between the SPerry & the Perry?
Click to expand...
Click to collapse
Small difference. Snapdragon 425 and Snapdragon 427
madbat99 said:
Small difference. Snapdragon 425 and Snapdragon 427
Click to expand...
Click to collapse
Ahh. I see. Makes sense then that the custom kernel works for both chipsets. Thank you.
Awesome kernel @Rebellion. Definitely appreciate your work on this. Just wondering though, is safetyNET supposed to pass by default with this kernel installed or do I need to do any additional steps to make it pass?
[email protected]@bl3s said:
Awesome kernel @Rebellion. Definitely appreciate your work on this. Just wondering though, is safetyNET supposed to pass by default with this kernel installed or do I need to do any additional steps to make it pass?
Click to expand...
Click to collapse
I know you directed this question to OP, but on my device (xt1766 Boost Mobile), running latest stock Android 7.1.1 Nougat (NCQS26.69-64-11)with OP's kernel, SafetyNet passes ctsProfile & basicIntegrity on Stable Magisk v18.1 -- by default and without any additional patches, mods or tweaks.
---------- Post added at 11:01 PM ---------- Previous post was at 10:15 PM ----------
@RebelLion_,I know you're probably tired of hearing my two cents, but I just wanted to inform you that I've tested all aspects of your kernel, and I have encountered no bugs or instabilities. I'm running debloated & Magisk rooted stock from this thread (NCQS26.69-64-11) with your kernel, with no additional Magisk Modules or mods. I'm using the Lionfish CPU governor with 960 MHz minimum and 1401 MHz maximum clocks; the Alucard Hotplug, I/O Busy, 65% Sampling Rate, 4 maximum cores online, GPU Adreno Idler, 20 Down Differential, 15 Idle Wait, 7 Workload, Vomer BrightBalance Color Profile w/ KCAL, DT2W Halfscreen, SoC Sound Drivers High Performance Mode, I/O Scheduler Maple 512kb Read Ahead for Internal Storage, Add Random enabled, I/O Stats enabled, RQ Affinity 2, Low Memory Killer set to Very Aggressive, Virtual Memory Dirty Ratio 20%, Dirty Background 5%, Dirty Expire Centisecs 200cs, Dirty Writeback Centisecs 5200cs, Overcommit Ratio 50%, Swappiness 100%, VFS Cache Pressure 9, Laptop Mode enabled, 2500kb Min Free, 10,800kb Extra Free, 510 MB Z-RAM Disksize, Entropy 64 Read, 128 Write; SELinux set Permissive, Westwood TCP Congestion Algorithm, FSync & Android Logging enabled.
Under normal to light use, my CPU averages around a 7% workload, whereas extremely heavy to heavy use (gaming, multitasking) will never average more than about 53% workload consumption.
Compared to unmodified stock, this kernel definitely improves upon responsiveness and overall performance on both normal and heavy usage. I'm seeing a 2 - 3 hour increase in battery life on the settings I referenced in comparison to the pure stock kernel. Also, during normal use, I'm seeing around 750 - 800 MB free RAM on average.