Database Info

[Kernel] CM6-Snapv7.6 Turbo! Splash Screens, Papersv4, Widgetv5

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Join us on irc.freenode.com #cm6-snap​
Snap F.A.Q.
(maintained by shift_)​
Click to expand...
Click to collapse
Daily Drivers
The best options for daily drivers are:
Downloads:
cm6-snap-v7.5-havs925 Download md5 bcdb177c62b51542e450ce2e620fea45
cm6-snap-v7.01 Download md5 80cfe44a7043a4a6d06cd0eefca88bb4
cm6-snap-v7.11 Download md5 9ed1236e28a82766f46c5eea994eac5e
Read the rest of the OP and ask questions in the thread for additional information.
Click to expand...
Click to collapse
Snap kernels are built to work only on CM6 based ROMs
You assume all responsibility for the use of this software.​
Version 7.6 [cfs/bfs]/nhavs925/qs2
Before I start, I want to give a special thanks to the usual suspects: spiicytuna for his work on SNAPturbo, and shift for his outstanding graphics work. We also had a very helpful beta testing team open their phones up to some fairly wild experimentation and some late nights: drmacinyasha, jabbawalkee, i[e, gerald410, swatspyder, nicholaaaas, mrkmrk, and jsseidel1. (Deepest apologies if I missed anybody, please let me know and I'll update the list)
Initially there are two releases of v7.6: CFS and BFS. Try both and use the one that works best for you. v7.6 is built from the CM6 2.6.32.15 source. It includes the first release of SNAPturbo, SNAPpapers, SNAPwidget, overclocking to 1.19ghz, netarchy's modified HAVS [nHAVS], and my modified conservative governor. You do not have to utilize SNAPturbo: It is an optional feature. Instructions for use are below.
The BFS version of v7.6 uses BFS Scheduler-v318 of BFS because this version currently provides the best results on CM6. All other features of the BFS release are identical to the CFS release.
SNAPturbo
SNAPturbo is a proprietary application designed to enhance system performance with no additional overclocking or battery penalty. SNAPturbo is not derived from the kernel source, is not subject to GPL, and the source code will not be shared, so please do not ask. SNAPturbo may not be distributed without prior written consent from jmxp69 and spiicytuna. SNAPturbo will only activate on a snap kernel.
Once you've successfully activated Turbo, you never have to do it again as long as you stick with a v7.6 kernel. You can safely flash v7.6 directly on top of CM6 nightlies in the same recovery session.
Before using SNAPturbo, please follow these instructions:
Perform a nandroid backup. Really, you should be doing this anytime you flash customized software.
Optional but recommended: Use Titanium Backup or My Backup Pro (available in Market) to backup your data and applications.
Enable Airplane Mode
Run the SNAPturbo application
Give SNAPturbo SU permissions
Do not touch any controls or the screen until after the phone reboots.
Note: You will probably see force closes while running SNAPturbo. This is normal and expected. Just let SNAPturbo run and it will reboot your phone when it finishes.
Known Issues
Important: During beta testing, some members of the beta team reported they stopped receiving SMS messages. We were unable to directly correlate this to anything happening with the kernel. In other words, it was not repeatable and the majority of testers never saw the issue. In one case, a re-flash of CM6 restored inbound SMS, and in another, it took a re-flash back to Stock Sense (with root). In each case after flashing either CM6 or a Sense ROM, the testers were able to re-flash v7.6 and never encountered the issue again.
Occasionally after activating SNAPturbo, one or two applications may repeatedly FC after rebooting. If this happens, try clearing data in application manager or just re-install the app. This has cleared the problem 100%.
SNAPturbo may look like it's destroying your phone when it runs. You may see force closes and maybe even smoke coming from the battery compartment. This is NORMAL. Let it run, leave it alone, and it should reboot on its own. After reboot, your phone should run normally. (Actually, I'm kidding about the smoke, but it does look ugly at first. Just let it ride…)
If for whatever reason SNAPturbo does not reboot your phone and return you to normal operating conditions (boot loops/odd behavior):
Do not attempt to re-activate.
Use the failsafe installation method listed below.
The only current method of disabling SNAPturbo is to wipe. v2 of SNAPturbo will provide a disable function.
Screen Tearing - v7.6 sets Nova panels T2 to 380. Previous testing indicates this is the best option for most phones. If you encounter any tearing, find Assasainslament's Novafreq and try 371.
After enabling turbo, if SetCPU FC's, uninstall and reinstall. That fixes it.
Failsafe Install
As much testing as went into SNAPturbo, the possibility exists you may run into problems. If you do, the following method is known to work 100%.
Backup apps with Titanium or My Backup Pro
Wipe Everything
Flash CM6
Flash v7.6
Reboot-DO NOT sign-in to Google
Turn Airplane Mode On
Activate Turbo
Sign-In to Google (Open Market)
Restore Apps
Resume normal use
Flashing Nightlies
If you flash a new nightly, make sure you flash v7.6 immediately afterwards. I recommend flashing in the same recovery session. If you do not flash v7.6 after flashing a nightly, you will bootloop.
If you forget to flash v7.6 after a nightly and you start to bootloop, just go back into recovery (hold Volume down while powering phone on) and flash v7.6. You will work fine afterwards.
v7.6 Changelog
Kernel now includes SNAPturbo application only. All other applications have been removed
Set the maximum CPU freq to 1.19. Many people were able to run 1.22g, but there is no practical benefit to doing it, so 1.19 is the new max across all revisions.
Minimum UV is 925. I've found this value to be the most stable and best for my battery.
Added Koush's AnyKernel Updater. Wiping Dalvik should now be a thing of the past.
BFS Version: Revert to BFS v0.318
Set interactive as default governor
Legacy snap tweaks to filesystem, network, vm, etc..
Tweaked conservative governor timings
Downloads
Click to expand...
Click to collapse
SNAP Extras - Here are a few extra user installable goodies to round-out SNAP on your CM6 installation.
SNAPsplash
For even greater Snapification of your phone, check out the graphics madness from Shift available now via SNAP Themed Splash Screens. Shift posted screenshots and detailed instructions here.
Update: SNAP Turbo Splash Screens now available in the Extras folder. See this post for screenshots.
Downloads
Click to expand...
Click to collapse
SNAPpapers
SNAPpapers is for those who want to sport their love and support for SNAP. Application credit goes to spiicytuna with wallpapers by Shift. It will work on any version of CM6, even if you don't have a SNAP kernel installed.
You install SNAPpapers just like any other .apk and use it by long press on the home screen, selecting wallpapers, and clicking SNAPpapers. For those unsure on how to install SNAPpapers: download a versions below and simply do an "adb install c:\path\to\snappapers.apk" or download an installer from the Market and install the SNAPpapers.apk from your sdcard.
v0.0.5 Changelog
New Snap Graphix themed wallpapers
Includes everyone's favorite Timeless Classic wallpapers (a la Lady in Red & Grunges)
Known Issues
Link to SNAP thread is not clickable as of yet
Planned Updates
Clickable link(s) to SNAP thread
Live wallpapers
v0.0.3 Changelog
Some wallpapers from v1 & v2 modified as per request
More wallpapers, including pics graciously provided by kpoz
known issues
Link to SNAP thread is not clickable as of yet
Planned Updates
Clickable link(s) to SNAP thread
More requested wallpapers
Live wallpapers
???
Downloads
Click to expand...
Click to collapse
SNAPwidget
The SNAPwidget is a widget created by our own spiicytuna for use with snap kernels that utilize H/AVS. It will not work on non-snap h/avs kernels. You install this just like any other .apk and
use it just like any other widget--ie. long press on the home screen. For those unsure on how to install SNAPwidget: download a version below and simply do an "adb install c:\path\to\Widget.apk" or download an installer from the Market and install the SNAPwidget.apk from your sdcard.
The goal of SNAPwidget is to provide easy access to H/AVS adjusted voltage at any given CPU frequency. The widget also displays the current battery draw in mA; red for discharging, and green for charging. Testing has shown no noticeable loss of battery with SNAPwidget when using update intervals of greater than 15 seconds; even with logging enabled.
**Please note that the frequency and temperatures displayed may not match setCPU. Rest assured that SNAPwidget has been triple checked and it's information is exactly the same as what the kernel/EVO is providing.
v0.0.5 Changelog
FIXED: bug that widget showed o[email protected]
Planned Updates
Additional skins/colors (post suggestions to thread)
Downloads
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Version 7.5 BFS/UV/OC/nHAVS
v7.5 is built from the CM6 2.6.32.15 source. It incorporates the latest BFS Scheduler-v0.330, overclocking to 1.19g, netarchy's modified HAVS [nHAVS], and my modified conservative governor.
There have been some mixed results with v8.x kernels. Some people have charging issues, some don't. Some people have screen tearing issues, some don't. While 2.6.34 issues continue to be sorted out, I decided to release a known stable version with the latest BFS/nHAVS implementation.
Known Issues
Testing revealed a down threshold of approximately 40 for the conservative governor to yield the best screen interaction. You can set this value in the advanced tab in SetCPU.
Since the introduction of AVS, some users see bootloops after installing. The known fix is to wipe dalvik. Since moving away from the ultra-undervolt kernels, I have yet to see a bootloop on my device. YMMV--if you encounter a bootloop, wipe dalvik.
This kernel is not as fast as v8.x. It's not because anything is wrong, it's because it is an older kernel revision. Please do not fill up the thread complaining about quadrant scores. For reference, I saw [email protected] vs [email protected] on v8.x
v7.5 Changelog
Set the maximum CPU freq to 1.19. Many people were able to run 1.22g, but there is no practical benefit to doing it, so 1.19 is the new max across all revisions.
Minimum UV is 925. I've found this value to be the most stable and best for my battery.
Added BFS v0.330
Built with CM-6.0.0 ramdisk. Works great on the first official CM6.
Legacy snap tweaks to filesystem, network, vm, etc..
Tweaked conservative governor timings
Downloads:
cm6-snap-v7.5-havs925 Download md5 bcdb177c62b51542e450ce2e620fea45
Click to expand...
Click to collapse
Version 8.2/BFS/U-UV/OC/nHAVS
v8.2 is built from Toastcfh's 2.6.34 source. It incorporates the BFS Scheduler, Overclocking to 1.19g, and netarchy's modified HAVS [nHAVS].
With BFS enabled, we're seeing quadrant scores approaching 2000 @ 1.19g. Stock frequencies (998mhz) routinely achieve 1500-1600.
Known Issues
Some phones have demonstrated difficulty charging via AC. So far, I've been unable to replicate the issue. I'll keep an eye out for updates and apply anything that looks relevant.
In-line headset buttons don't work. I patched 8.2 with the latest HTC Headset driver, but I don't believe this fixed the problem.
Led Flashlight - Toast commented that Torch didn't light the led flashlight on github. I have not experienced this problem. Two tools I've used (torch and switchpro widget) both light the camera leds just fine on my phone.
Conservative CPU governor is the default in v8.1 and it does not appear to log the correct minimum CPUFreq in kmsg so the snap widget will continually report 384mhz. You can check the actual frequency with:
Code:
adb shell s.getfreq
This should show you 245mhz if your phone is idle. If this really bothers you, switch to interactive as your default.
v8.2 Changelog
IPv6 added (Google Goggles fix)
Set the maximum CPU freq to 1.19. Many people were able to run 1.22g, but there is no practical benefit to doing it, so 1.19 is the new max across all revisions.
Added BFS
Regulator patch from toast's github
Built with CM-6.0.0 ramdisk. Works great on the first official CM6.
Fixed 802.11n - works again
Legacy snap tweaks to filesystem, network, vm, etc..
Tweaked conservative governor timings
Downloads:
cm6-snap-v8.2-havs800 Download md5 45a9428cf556d4d44d16dbb295b41d23
cm6-snap-v8.2-havs825 Download md5 5f207d52e44878b8fdae78fc541e8db9
cm6-snap-v8.2-havs850 Download md5 668f0eb6115c68e980b37a0867c867c9
cm6-snap-v8.2-havs875 Download md5 618b4c4c2dbff49ce5bf7816b054af3e
cm6-snap-v8.2-havs900 Download md5 7fd5a621592f4775ed971ce19ec71057
cm6-snap-v8.2-havs925 Download md5 262c5a836e75ac0643f7115fd7d5f853
Click to expand...
Click to collapse
Version 8.1/U-UV/OC/nHAVS
v8.1 is built from Toastcfh's 2.6.34 source. It incorporates netarchy's modified HAVS [nHAVS] introducing the ability to specify the maximum and minimum voltage range at every frequency step. This differs from the original implementation of HAVS which only permitted specifying the maximum voltage at a given step. By incorporating a minimum we still benefit from voltage scaling, but it provides a little human intervention to prevent AVS from trying to undervolt too far.
This first v8.1 release uses an 850mv floor. With the more stable implementation of HAVS, I have high hopes that it addresses some of finicky behavior we've seen with previous revisions. My preference is to start reducing the number of versions in each release which is why this first version is U-UV or UltraUnderVolt.
This is a significantly faster kernel out of the box than .32.
Known Issues
Led Flashlight - Toast commented that Torch didn't light the led flashlight on github. I have not experienced this problem. Two tools I've used (torch and switchpro widget) both light the camera leds just fine on my phone.
Conservative CPU governor is the default in v8.1 and it does not appear to log the correct minimum CPUFreq in kmsg so the snap widget will continually report 384mhz. You can check the actual frequency with:
Code:
adb shell s.getfreq
This should show you 245mhz if your phone is idle. If this really bothers you, switch to interactive as your default.
I will closely monitor toast's github for updates to address this and other remaining minor issues.
v8.1 Changelog
Added Static version of Snap 8.1. This build eliminates nHAVS and uses stock frequency/voltage scaling. For those of you unable to find a stable nHAVS implementation, this one is for you.
Removed 1.22g in havs825. We've gone back and forth with 1.22 in various revisions of snap, but I've come to the conclusion that downside outweighs upside. So 1.19g will be the new max in snap going forward.
Fixed 802.11n and Wifi AP.
Merged netarchy's HAVS from .32 enabling specification of min/max AVS voltages at each frequency step.
Built with CM-6.0.0 ramdisk. Works great on the first official CM6.
Fixed 802.11n - works again
Fixed 1.22g - confirmed working
Legacy snap tweaks to filesystem, network, vm, etc..
Removed - Added OC up to 1.22
Tweaked conservative governor timings
Downloads:
cm6-snapv8.1-static.zip/OC Download md5 30485362938e2c586d6abc4b67479487
cm6-snap-v8.1-havs825/OC Download md5 5b4949ab11c81ffb30e107a3dcbce0b0
cm6-snap-v8.1-havs850/OC Download md5 99955f8d1a6eaeb98ffa7d578717cb73
cm6-snap-v8.1-havs900/OC Download md5 8fc3b56f0a50d1dfae4e80715a9abc5d
Click to expand...
Click to collapse
Version 7.4 HAVS/OC/UV
The 7.4-havs kernel incorporates BFQ and AVS. After spending some quality time discussing HAVS with intersectRAVEN, this release should work on most phones. If it doesn't work for your phone, let me know in the thread and we'll try to sort it out. v7.4 is a minor update from v7.3 below focused on enabling stable Hybrid AVS. BFQ from v7.3 is also included, but I took it out of the kernel name because it's also now a standard feature in CM6.
About AVS
Code:
Adaptive Voltage Scaling (AVS) for ARCH_MSM_SCORPION
The AVS driver adjusts the CPU voltage based on hardware feedback. Using
hardware feedback AVS is able to achieve lower voltages than the equivalent
static voltage scaling (SVS) voltage.
The Scorpion architecture includes three ring oscillators for AVS. The
ring oscillators provide real time feedback about the voltage requirements
for the current operating conditions. The hardware can sense when the voltage
can be lowered and needs to be raised.
The AVS software keeps track of the current operating conditions. Periodically
AVS queries the hardware. Every query AVS updates a table of required voltage
indexed by operating conditions, CPU frequency and temperature.
This first release uses 975mv as the floor voltage based on intersectRaven's test results from his work on the N1. The current release plan for 7.4 includes:
UV - 975 - Available now
UV - 875 - Available now
UV - 825 - Available now
Version 7.4-havs Changelog
Modified conservative CPU governor set as default. Modifications designed to reduce scaling lag.
HAVS implemented with min voltages set to 975mv in -havs975 and 875mv in -havs875
Known Issues
Do not reboot your phone with adb reboot. Use the power button and reboot/power off from within the phone. Using adb reboot causes HAVS minimum voltages to stay at the maximum specified in the AVS voltage table. This will cause battery drain equivalent to stock kernels.
If you get a bootloop after installing one of the v7.4 kernels, reboot into recovery and wipe dalvik/cache. That generally fixes things.
Downloads:
cm6-snap-v7.4-havs975/OC/UV Download md5 d121ee63c9f147dcadd91ebd1626fa83
cm6-snap-v7.4-havs875/OC/UV Download md5 cb4ff35841eadc47651e19d24c7f64cf
Avoid this one unless you know what you're doing.
cm6-snap-v7.4-havs825/OC/UV Download md5 d138071715a7d5137622c57867f56271
A big thanks to intersectRaven for discussing AVS with me and clearing up some nagging problems!
Click to expand...
Click to collapse
Version 7.3-avs
The 7.3-avs kernel will be the only 7.3 option. I've decided against making a 7.3-noavs version because BFQ is not enough of a performance enhancement to warrant a new revision beyond 7.x1. So if you can't run AVS, I suggest you stick with 7.01 or 7.11. Version 7.3-avs incorporates BFQ and AVS (see codebox below).
** Note: The version numbers are known to be off in the betas.
Click to expand...
Click to collapse
Experimental zImages
Experimental zImages are provided only for those interested pushing their devices for even more performance. They are not intended as daily drivers, although some may find them perfectly acceptable as a daily driver.
I will not provide update.zips for experimental zImages so please don't ask. These zImages are intended for seasoned users who are comfortable restoring their phones and using fastboot.
Please see the readme in each download section for further information.
CFS Releases
v7.6cfs-havs800
v7.6cfs-havs825
v7.6cfs-havs850
v7.6cfs-havs875
BFS Releases
v7.6bfs-havs875
This zImage is identical to the production release of v7.6 except the undervolt floor has been dropped to 800/825/850/875 for 128 and 245mhz.
Download
Click to expand...
Click to collapse
Click to expand...
Click to collapse
EOL Revisions
cm6-snapv7.3beta1 (900mv) Download
cm6-snapv7.3beta3 (875mv) Download
cm6-snap-v7.3 AVS Final (875mv/tweaked conservative governor) Download
cm6-snap-v7.3-avs825 Download
cm6-snap-v7.3-avs850 Download
cm6-snap-v7.3-avs875 Download
cm6-snap-v7.3-avs925 Download
cm6-snap-v7.3-avs950 Download
cm6-snap-v7.01 Download
cm6-snap-v7.11 Download cm6-snap-v5.01 Download
cm6-snap-v5.11 Download
cm6-snap-v5.0 Download
cm6-snap-v5.1 Download cm6-snap-v4.0-cc Download
cm6-snap-v4.1-cc Download
cm6-snap-v4.0 Download
cm6-snap-v4.1 Download cm6-snap-v3 Download
Click to expand...
Click to collapse
Before proceeding, please run a nand backup!​
Download and Install
You do not need to wipe. Just flash over your CM6 nightly builds.
If you are flashing nightly CM6 builds, you'll need to flash this kernel again after each nightly. Just flash your nightly build, reboot and make sure everything is working, then reflash your favorite snap kernel.
Click to expand...
Click to collapse
v8: Thanks to toastcfh for his tireless efforts getting .34 working on CM6 and to netarchy for a great job modifying HAVS for stability.
I need to thank netarchy, assassinslament, joeykrim, sentenced, ffolkes, spiicytuna, and of course toastcfh for helping me along the way. Special thanks to ffolkes and netarchy for their work on the 2.1 kernels which has made its way to CM6. They are an incredibly helpful and patient group, and this community is lucky to have them working for all of us. Thanks to Cyanogen for providing crucial tips during the development of snap, and the entire CyanogenMod crew for a wicked 2.2 ROM. Thanks to intersectRaven for the AVS code.
GPL Compliance and Credits
My github
Koush for this exceptionally clever AnyKernel Updater template.
v8.x is built from toastcfh's source.
v8.1 nHAVS merged from netarchy's HAVS source.
spiicytuna for SNAPwidget, SNAPpapers, and the upcoming SNAPturbo.
shift for the incredible graphics work.
v7.x and below snap kernels are built from the CM6 git source.
v7 and below AVS code imported from intersectRaven git source.
Click to expand...
Click to collapse
Donate!
Ok, I've been asked multiple times how to donate for my work on snap, so I added a button to my sig.

Great job. Just installed it and working fine so far.
Will update more later after I put all my apps back on.
Thank you for the tweaks.

will this help improve battery or drop it quicker lol sorry

What the hell,Ill give it a shot.

Sporkman said:
will this help improve battery or drop it quicker lol sorry
Click to expand...
Click to collapse
Try it and tell me. It certainly will not *improve* the battery life, but I don't expect the penalty to be material.

E: No signature (11 files)
E:Verification failed
Installation aborted.
Any advice? Does this need to be run off Clockwork?

Fps2d before was roughly 49 fps with a stdev in the high 7s
now its 53 fps avg with stdev=5.26
gears is chilling at 53-54 fps
quadrant is 1279.
This is all without setcpu.

TheMike1 said:
E: No signature (11 files)
E:Verification failed
Installation aborted.
Any advice? Does this need to be run off Clockwork?
Click to expand...
Click to collapse
Yes, I'm sorry, I should have mentioned it's unsigned. I'll update the OP.
J

Just flashed, novatek 003 -- getting fps2d 51 with StDev of 9 after several runs, which is actually a slight downgrade. My Long Bench in SetCPU is in the 600's vs the 300's as before.
LinPack is very strange. I get my usual 39-43 but every once in a while it seems to lag and I get 2MFLOPS - 6MFLOPS, not 20, literally 2.
I have a feeling something must not be right, is there anyway to debug what is going on?

Didn't change anything, just sat around and did a bunch of LinPacks, then noticed they were pretty consistent so went into SetCPU and started doing a bunch of Long Bench, and actually started to get into the low 400s consistently, high 300s. Back to fps2d and now I am getting 54 avg with a 5.5StdDev consistently.
Strange, I cannot figure out what changed, any idea?
edit: Just ran a 1571 Quadrant too
My SetCPU Current profile btw is 1152max, 245min performance

It helps to let the phone settle for a while before testing. When you first boot, it's pretty busy.

This kernal just put me back to 29 fps. With or without setcpu. ?? Mflops was 46 tops though
Sent from my PC36100 using XDA App

TheMike: How does that quandrant score compare to your stock ROM?

jmxp69 said:
TheMike: How does that quandrant score compare to your stock ROM?
Click to expand...
Click to collapse
I am getting 1575+ Consistently now, vs 1400-1530 with CM6 stock kernel.
My stock ROM was like a 500 quadrant or something
This is Awesome!!
HAHAH! I just got a 1620 Quadrant with your Kernel, my first time breaking 1600
Awesome Kernel man, thank you very much

Attempted to flash this kernel on top of baked pastries beta 2 with the 2.2 update and just got a boot loop. The nexus boot logo animated fast then slower then screen for a blank and starts all over again.
Sent from my PC36100 using XDA App

rmriggin said:
Attempted to flash this kernel on top of baked pastries beta 2 with the 2.2 update and just got a boot loop. The nexus boot logo animated fast then slower then screen for a blank and starts all over again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This is based on CM6 rmriggin. Kernel update.zips contain ramdisks with rom specific information. So you can't do it that way. I could make the zImage, and modules available to you if you want to flash it with fastboot and manually copy the modules over. That would likely work.
J

If you want to experiment, this kernel may work on a non-CM6 or maybe even a 2.1 ROM with the following steps. I have no idea. Proceed at your own risk.
**Warning** Don't try this without a backup! You'll need to nandroid restore to undo this.
1) Download this and unzip on your PC (do not try to flash it).
adb shell reboot bootloader
fastboot boot zImage <-----this will let you test to see if it works. If it does, proceed with the following to survive reboot. If it doesn't work, just reboot your phone and you'll be back to normal. No other action required.
2) Move to a different directory from where you unzipped donotflash.zip and do the following:
adb pull /system/lib/modules/bcm4329.ko
adb pull /system/lib/modules/sequans_sdio.ko
Save these somewhere safe.
3) From the location you unzipped donotflash.zip:
adb remount
adb push bcm4329.ko /system/lib/modules/
adb push sequans_sdio.ko /system/lib/modules/
adb shell reboot bootloader
fastboot flash zimage zImage ** pay attention to the caps!
fastboot reboot
If you try this, I'd be interested in hearing about your results.

Thank you so much for this kernel, I ran my FPS2d app on the HTC EVO 4g running under the latest Cyanogen ROM and I get 54 AVG with 5.45 stdev...
It's a lot faster and I'll check about battery usage when I get a full charge overnight.
Thanks again!

Quick question.. I've flashed latest nightly today and I'm capped at 28~30 fps now.. and I flashed this kernel and still stuck at 30 fps.. can anyone tell me what might be causing this? Any help will be greatly appreciated.
Sent from my PC36100 using XDA App

mizerab1e said:
Quick question.. I've flashed latest nightly today and I'm capped at 28~30 fps now.. and I flashed this kernel and still stuck at 30 fps.. can anyone tell me what might be causing this? Any help will be greatly appreciated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you have setCPU installed? If so, uninstall it, reboot, and see what happens.

[MOD] IncrediControl - Easy GUI Undervolting

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

[KERNEL][A510/A700][07/30] Z-Kernel Beta

Welcome to Z-Kernel's thread!​
Features
- Base kernel fully updated to linux-tegra-nv-3.1 (bug fixes & performance improvements)
- Simplified board codes
- Cleaned up Acer specific code
Click to expand...
Click to collapse
Changelog
r2:
- Restarted kernel development (r1's features not implemented yet)
- Base kernel fully updated to linux-tegra-nv-3.1 (bug fixes & performance improvements)
- Simplified board codes
r1:
- CPU OC to 1.6 ghz by default (should be stable)
- GPU OC support up to 700MHz (default is 520 mhz)
- Overclocked LP core from 500 to 620 mhz
- Custom user voltage control for CPU and Core components such as EMC, GPU, and LP (faux123)
- Dynamic FSYNC
- Optimized KSM
- Optimized ZRAM
- Compiled using latest Linaro toolchain with optimized compiler flags
- Optimized SLUB and use SLUB by default instead of SLAB
- Glibc memcpy and memmove
- Deadline improvements for solid state drives
- Proportional Rate Reduction for TCP
- Tegra 3 variant display (faux123)
- Optimized swahb32 byteswap helper
- Asynchronous I/O latency improved through removal of plug in do_io_submit()
- allow use of an I/O controller's native max block size
- Optimized ARM RWSEM algorithm
- timer: optimize apply_slack()
- Optimized crypto algorithms
- Optimized AES and SHA1 routines
- LowMemoryKiller fixes and improvements
- Lock performance governor to all 4 cores
- Many scheduler improvements and optimizations
- updated bcmdhd driver (wifi)
- over 450 changes committed, so the above list isn't complete
Click to expand...
Click to collapse
Complete list of changes can be found in the commit log: https://github.com/Ziyann/android_kernel_acer_t30
I'm not responsible if anything bad happens with your device!
This build has been tested on CM11 only, so if you run into something with other ROMs, report it and I will see what I need to change to cooperate with it.
XDA:DevDB Information
Z-Kernel, Kernel for the Acer Iconia A700 and A510
Contributors
Ziyan
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R2
Stable Release Date: 2014-07-30
Created 2014-09-23
Last Updated 2014-09-23

Nice, if it's working fine, I hope you will also support the A510/A511

Shreps said:
Nice, if it's working fine, I hope you will also support the A510/A511
Click to expand...
Click to collapse
Of course, I'll see what can I do when I get everything (OC, UV, ...) working here waiting for a tester...

it is indeed slow. even when completely debloated plus stripped of "essential" system components that I personally do not use. I will try this right away. will report back within an hour in this post.
@Ziyan
it boots, runs, everything seems standard. not seeing any performance increases though. same ol' 10 to 15 fps is there anything more you wish for me to test with it? I replaced this tab a while ago with galaxy note pro 12.2 so I can't really use it enough to check for random reboots

Sterist said:
@Ziyan
it boots, runs, everything seems standard. not seeing any performance increases though. same ol' 10 to 15 fps is there anything more you wish for me to test with it? I replaced this tab a while ago with galaxy note pro 12.2 so I can't really use it enough to check for random reboots
Click to expand...
Click to collapse
Thanks, that's good, it means I can continue improving it. I need to check the kernel periodically after a big bunch of commits, because if something gets broken, it can be hard to find what causes it if from a thousand things I'll push a new version and changelog later today or tomorrow.

sounds good. quote this post when it's uploaded, it'll send me am email notification and I can get right on it.

Sterist said:
sounds good. quote this post when it's uploaded, it'll send me am email notification and I can get right on it.
Click to expand...
Click to collapse
Here's a new version. Before testing it, please make some benchmarks with the previous version (mainly 3D), because - if everything works as it should -, the GPU is now working at 520 mhz instead of 416. It should also have CPU overclocking and voltage control support, so please install Trickster Mod, or something like that from Play Store to see if it works (screenshots are welcome). If it works (i'd be a bit surprised lol it was too easy), please run some benchmarks again to see if there's a noticeable difference. I've got 12 pages of commits waiting to be merged, so yeah, if something got broken, I better fix it now :silly:

Ziyan said:
Here's a new version. Before testing it, please make some benchmarks with the previous version (mainly 3D), because - if everything works as it should -, the GPU is now working at 520 mhz instead of 416. It should also have CPU overclocking and voltage control support, so please install Trickster Mod, or something like that from Play Store to see if it works (screenshots are welcome). If it works (i'd be a bit surprised lol it was too easy), please run some benchmarks again to see if there's a noticeable difference. I've got 12 pages of commits waiting to be merged, so yeah, if something got broken, I better fix it now :silly:
Click to expand...
Click to collapse
just woke up and leaving for work in 20 minutes. when I get there and settle in (about an hour and 20min from this post) I'll test it
which benchmark though, antutu?

Sterist said:
just woke up and leaving for work in 20 minutes. when I get there and settle in (about an hour and 20min from this post) I'll test it
which benchmark though, antutu?
Click to expand...
Click to collapse
Yeah, antutu will do, just note the invidual points

Ziyan said:
Yeah, antutu will do, just note the invidual points
Click to expand...
Click to collapse
woah woah... I just went to download the second version and the tab was dead from 77% last night, still warm.
there's a wake problem, screen will turn on one time after booting up but only that one time
and a sleep problem, after manually turning the screen off it will not turn back on (and kills battery very quickly!)

Sterist said:
woah woah... I just went to download the second version and the tab was dead from 77% last night, still warm.
there's a wake problem, screen will turn on one time after booting up but only that one time
and a sleep problem, after manually turning the screen off it will not turn back on (and kills battery very quickly!)
Click to expand...
Click to collapse
Thanks for the report, I'll investigate the problem tomorrow (it's 01:30 AM here :silly. If you could take a dmesg (while turning the screen off, then trying to turn it back on), or last_kmsg, that would be great help! If you don't know how, refer to section 2 and 3: http://forum.xda-developers.com/showthread.php?t=1520508

Ziyan said:
Thanks for the report, I'll investigate the problem tomorrow (it's 01:30 AM here :silly. If you could take a dmesg (while turning the screen off, then trying to turn it back on), or last_kmsg, that would be great help! If you don't know how, refer to section 2 and 3: http://forum.xda-developers.com/showthread.php?t=1520508
Click to expand...
Click to collapse
higher score / lower 3D performance is v1
lower score / higher 3D is v0
recent apps cleared and CPU set to 1400 performance and ROW
no app gives OC/UV options with v1
I don't have access to a pc at work so can't run dmesg properly for this, and I'm having trouble reproducing the sleep crash now
this is probably all exactly what you did not want me to say lol
edit: so, I got it to crash again (yay!) but can't get klast to work (read only fs) I tried mounting various directories as RW but honestly I have no idea which to do... and here's dmesg which may or may not contain what you need.
I know it might be a little early to ask but any chance you could implement Frandom?

Sterist said:
(cut)
edit: so, I got it to crash again (yay!) but can't get klast to work (read only fs) I tried mounting various directories as RW but honestly I have no idea which to do... and here's dmesg which may or may not contain what you need.
I know it might be a little early to ask but any chance you could implement Frandom?
Click to expand...
Click to collapse
Thanks for the detailed report, I think I revert Franco's hotplugging driver for now, seems like it's on a rampage. May try again in the future.
As for the last_kmsg, your first command was correct, it's just that it doesn't always get created.
We'll see about Frandom when we get things working nice
Here's a build with the stock hotplugging driver, report back if it still crashes.

Ziyan said:
Thanks for the detailed report, I think I revert Franco's hotplugging driver for now, seems like it's on a rampage. May try again in the future.
As for the last_kmsg, your first command was correct, it's just that it doesn't always get created.
We'll see about Frandom when we get things working nice
Here's a build with the stock hotplugging driver, report back if it still crashes.
Click to expand...
Click to collapse
ok I let it idle for about 30 minutes (that was enough to crash every time I left it alone at work) and so good so far.
still no OC/UV though
edit... idle 2 more hours and no problems

Sterist said:
ok I let it idle for about 30 minutes (that was enough to crash every time I left it alone at work) and so good so far.
still no OC/UV though
edit... idle 2 more hours and no problems
Click to expand...
Click to collapse
Great, let's see if CPU OC/UV works with this one. If it does, don't forget to run a benchmark, as GPU OC didn't work till now

Ziyan said:
Great, let's see if CPU OC/UV works with this one. If it does, don't forget to run a benchmark, as GPU OC didn't work till now
Click to expand...
Click to collapse
still no CPU OC/UV. also, that 52mhz step has never worked on any ROM or kernel I've tried, that may extend battery life

Sterist said:
still no CPU OC/UV. also, that 52mhz step has never worked on any ROM or kernel I've tried, that may extend battery life
Click to expand...
Click to collapse
Ok, it must work now.
About 52 mhz, it's so low that any small background work would ramp up the CPU to hispeed_freq, so in the end, it would shorten battery life. The same thing happens with Galaxy Nexus if we go down to 180 mhz, which is a lot, compared to 52 mhz
I've added about 200 commits since your last try (this is a great daily activity :silly, the kernel is getting to be on pair with a Nexus 7 kernel soon if we get OC/UV and some more extra things working :highfive:

Ziyan said:
Ok, it must work now.
About 52 mhz, it's so low that any small background work would ramp up the CPU to hispeed_freq, so in the end, it would shorten battery life. The same thing happens with Galaxy Nexus if we go down to 180 mhz, which is a lot, compared to 52 mhz
I've added about 200 commits since your last try (this is a great daily activity :silly, the kernel is getting to be on pair with a Nexus 7 kernel soon if we get OC/UV and some more extra things working :highfive:
Click to expand...
Click to collapse
ok so UV menu now loads but doesn't look to work quite right - not usable. this is the menu I was looking for that did not load before
OC still does not work though
about 52 (51 actually) every time it is selected, after I leave the screen and come back 102 becomes the selected minimum automatically, even if lock frequency at 51
need benchmark? and ty ty your time!

Sterist said:
ok so UV menu now loads but doesn't look to work quite right - not usable. this is the menu I was looking for that did not load before
OC still does not work though
about 52 (51 actually) every time it is selected, after I leave the screen and come back 102 becomes the selected minimum automatically, even if lock frequency at 51
need benchmark? and ty ty your time!
Click to expand...
Click to collapse
At least we're making progress :good: try this one, and also try trickster mod (specific and general menu).
Benchmarks are welcome, those 200 commits should improve performance a bit, though I think most of them can only be seen in real usage (low memory killer, zram, ...)

Ziyan said:
At least we're making progress :good: try this one, and also try trickster mod (specific and general menu).
Benchmarks are welcome, those 200 commits should improve performance a bit, though I think most of them can only be seen in real usage (low memory killer, zram, ...)
Click to expand...
Click to collapse
bootloop, won't get past Acer logo
benchmark is from the last kernel

[Kernel][Ville S4][LP] - Mrak Kernel by mikronac.ns 2015-10-12

Disclaimer:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* blah blah blah you get the point.
*/
I am presenting to you StockLike kernel. My idea is to keep kernel simple, close to stock functions. For beggining, I just undervolted frequencies to achive better battery life. Additional functionality like S2W, d2tw, etc will not be implemented.
Changelog:
Feb 23
Enable S2W, S2W, DT2W
Feb 22
-Compiled with Linaro GCC 4.9.3-2015.02 Toolchains
-Set Multi Core Power Saving Mode to 2
-New name, Mrak kernel
Feb 21
- GCC 4.9 Used
- Linux 3.4.106
- Some Updates From CM 12
- F2FS ready
- Voltage Control
- CPU and GPU OC
- TCP Congestion Controls
- Optimized Algorithms
- Fast Charge
- Export Krait Variant
- Simple GPU Governor
- BFQ, FIOPS, SIO I/O Schedulers
- Intellidemand, Intelliactive, Intellimm, and ElementalX Governors
- FRANDOM Support
- exFAT Support
- Asynchronous Fsync
- BLN (report if (not) works)
-Add -Stockie-Kernel to the Kernel Version
Jan 15
-GCC 4.8 Used
-Base Updated to 3.4.105
-Overclocked L2 Cache
Click to expand...
Click to collapse
Download: LINK
Kernel Souce
XDA:DevDB Information
[Kernel][Ville S4][AOSP][KK && LP] - Mrak Kernel by mikronac.ns, Kernel for the HTC One S
Contributors
mikronac.ns, javelinanddart
Kernel Special Features:
Version Information
Status: Stable
Created 2014-10-02
Last Updated 2015-10-16

Mine...

Will this kernel have some of the Bubba features? Also it'll be based on the 3.4.82 kernel or it'll be in sync with CAF like bubba was (I think it has reached 3.5.x something already or it is 3.4.100+ since latest Bubba was 3.4.99)?
Will you also include additional governors (like the intellidemand, intelliactive and so on), GPU govs/OC, BLN ..?
Thank you

Rapier said:
Will this kernel have some of the Bubba features? Also it'll be based on the 3.4.82 kernel or it'll be in sync with CAF like bubba was (I think it has reached 3.5.x something already or it is 3.4.100+ since latest Bubba was 3.4.99)?
Will you also include additional governors (like the intellidemand, intelliactive and so on), GPU govs/OC, BLN ..?
Thank you
Click to expand...
Click to collapse
Please, write me which Bubba features?
It will be based on stock 3.4.82. I have plan to add additional governors, IO schedulers and BLN...
Maybe some optimization algorithms but without OC (for now)...

mikronac.ns said:
Please, write me which Bubba features?
It will be based on stock 3.4.82. I have plan to add additional governors, IO schedulers and BLN...
Maybe some optimization algorithms but without OC...
Click to expand...
Click to collapse
Mainly it is that "sleepy-plug" that rmbq used instead of the mpdecision algorithm to increase battery life. It was a brilliant idea and was working great, I would love to see that feature again not being "dead". Then comes the GPU new govs and ability to OC the GPU (not the CPU).... And the sync with CAF sources, eg. keeping the kernel updated to the last base. I'll add more if I remember more.
Sent from nowhere over the air...

Rapier said:
Mainly it is that "sleepy-plug" that rmbq used instead of the mpdecision algorithm to increase battery life. It was a brilliant idea and was working great, I would love to see that feature again not being "dead". Then comes the GPU new govs and ability to OC the GPU (not the CPU).... And the sync with CAF sources, eg. keeping the kernel updated to the last base. I'll add more if I remember more.
Sent from nowhere over the air...
Click to expand...
Click to collapse
yeah but it is better to compile Bubba kernel with newest WiFi base. Here I want to be close to stock kernel...
Maybe I will have time today after work to compile and test Bubba... I dont know what is happening with @rmbq?

mikronac.ns said:
yeah but it is better to compile Bubba kernel with newest WiFi base. Here I want to be close to stock kernel...
Maybe I will have time today after work to compile and test Bubba... I dont know what is happening with @rmbq?
Click to expand...
Click to collapse
Thank you, I've already send a PM to you regarding this since I didn't want to clutter the thread with discussions about other kernels. Take your time.
Nothing is wrong with rmbq I guess, he said he'll move to another device/projects so that's why he stopped bubba
Sent from nowhere over the air...

Primary devhost link don't have DL links, DB mirror is ok.
Can't play with phone until evening, so will test it then but just a quick question - Qualcomm iris fm supported?
Update: FM radio is working. WiFi is not, but I'm on oneplus one cm11 so it's my side. What has suprised me was that after flashing kernel, i was on 13.08. Ice, battery dropped from 64% to 21% in a flash. I remember that it was on 66% when switch to recovery, 64% after boot and several sec later it was on 21%. Than reboots started, reboots with data loss. Traffic counter was reseted, all zeroes, whatsapp was like data was cleared, no recents pics or docs, root explorer was back to fabric state. So i had to quickly return to Ice cause i had no charger in vicinity. OFC soon phone turned off

Loreane Van Daal said:
Primary devhost link don't have DL links, DB mirror is ok.
Can't play with phone until evening, so will test it then but just a quick question - Qualcomm iris fm supported?
Update: FM radio is working. WiFi is not, but I'm on oneplus one cm11 so it's my side. What has suprised me was that after flashing kernel, i was on 13.08. Ice, battery dropped from 64% to 21% in a flash. I remember that it was on 66% when switch to recovery, 64% after boot and several sec later it was on 21%. Than reboots started, reboots with data loss. Traffic counter was reseted, all zeroes, whatsapp was like data was cleared, no recents pics or docs, root explorer was back to fabric state. So i had to quickly return to Ice cause i had no charger in vicinity. OFC soon phone turned off
Click to expand...
Click to collapse
It happens to me on Bubba every time I flashed it... Stock kernel haven't that behavior... About FM: Which FM App are you using? I guess that is 1+1 Native app? Can you share it?

mikronac.ns said:
It happens to me on Bubba every time I flashed it... Stock kernel haven't that behavior... About FM: Which FM App are you using? I guess that is 1+1 Native app? Can you share it?
Click to expand...
Click to collapse
Do you know what is a reason for such behavior? I also had strange reboots on bubba. Think it's because of lower voltage on slower krait. But, with lowered voltage on @AKToronto 's IceCold phone is rock solid. So it beats me up.
Using Spirit fm. Both 1 and 2 r working.
1+1 don't have FM radio, although it does have qualcomm combo wifi/bt/fm chipset.

Loreane Van Daal said:
Do you know what is a reason for such behavior? I also had strange reboots on bubba. Think it's because of lower voltage on slower krait. But, with lowered voltage on @AKToronto 's IceCold phone is rock solid. So it beats me up.
Using Spirit fm. Both 1 and 2 r working.
1+1 don't have FM radio, although it does have qualcomm combo wifi/bt/fm chipset.
Click to expand...
Click to collapse
Hm, sure that reboots can be voltage related but I don't think that we have that case here. Something is wrong with governors. I have reboots with almost all governors but with interactive everything is fine... When i switch on ondemand gov, I have reboot in next 5 mins... Spirit1 have poor signal reception here in Novi Sad (with stock I have every single one station) and spirit2 doesn't work for me... HTC buzz still stays my fm device
Sent from my One S using XDA Premium 4 mobile app

Delete

mikronac.ns said:
Hm, sure that reboots can be voltage related but I don't think that we have that case here. Something is wrong with governors. I have reboots with almost all governors but with interactive everything is fine... When i switch on ondemand gov, I have reboot in next 5 mins... Spirit1 have poor signal reception here in Novi Sad (with stock I have every single one station) and spirit2 doesn't work for me... HTC buzz still stays my fm device
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was on interactive, set it via trickster, but there were reboots.
Spirit2 is working with me with no aditional settings, just changed to EU+ from US. Tuner knob is not tunning but i use "arrows". Spirit1 has a good reception in Belgrade and also down the "south railway"

https://www.androidfilehost.com/?fid=95897840722643297
This is basically stock kernel with undervolted table.
And, it is based on 3.4.105, not on 3.4.82.
Nothing less, nothing more.
It is only for KitKat, when I switch to LP, there will be LP version.

mikronac.ns said:
https://www.androidfilehost.com/?fid=95897840722643297
This is basically stock kernel with undervolted table.
And, it is based on 3.4.105, not on 3.4.82.
Nothing less, nothing more.
It is only for KitKat, when I switch to LP, there will be LP version.
Click to expand...
Click to collapse
Switching to LP won't be hard:
Code:
git remote add cm https://github.com/CyanogenMod/android_kernel_htc_msm8960
git fetch cm
git checkout -b cm-12.0
git reset --hard 594eaa187a86da35487f59b9f2913e0f28fc5826
git merge cm/cm-12.0
git push -u origin cm-12.0
curl https://raw.githubusercontent.com/mikronac/android_kernel_htc_msm8960/cm-11.0/arch/arm/mach-msm/acpuclock-8960.c > arch/arm/mach-msm/acpuclock-8960.c
git commit -asm "Undervolting & L2 Cache OC"
curl https://raw.githubusercontent.com/mikronac/android_kernel_htc_msm8960/cm-11.0/drivers/cpufreq/cpu-boost.c > drivers/cpufreq/cpu-boost.c
git commit -asm "Fix cpu-boost.c"
git push
Also you might want to take a look at this commit:
https://github.com/javelinanddart/a...mmit/53b9168f745d100be8841b3d89eb04c122ac3924
It's GCC 4.9.x Fixups for future-proofing or to start using GCC 4.9

I knew this but thanks. I don't want to make it until I switch to LP.
Sent from my One S using XDA Free mobile app

mikronac.ns said:
I knew this but thanks. I don't want to make it until I switch to LP.
Sent from my One S using XDA Free mobile app
Click to expand...
Click to collapse
Just letting you know.
I'm with you though. I haven't switched to LP and it's still a long way in the works.
What features are you planning on adding?

@mikronac.ns You should check out my Linux 3.10 Kernel porting project. I added you as a collaborator
Here's the development thread
http://forum.xda-developers.com/htc-one-s/development/kernel-t3003992#post58205030

javelinanddart said:
@mikronac.ns You should check out my Linux 3.10 Kernel porting project. I added you as a collaborator
Here's the development thread
http://forum.xda-developers.com/htc-one-s/development/kernel-t3003992#post58205030
Click to expand...
Click to collapse
Thanks man... I will take a look these days, maybe even tomorrow...

mikronac.ns said:
Hm, sure that reboots can be voltage related but I don't think that we have that case here. Something is wrong with governors. I have reboots with almost all governors but with interactive everything is fine... When i switch on ondemand gov, I have reboot in next 5 mins... Spirit1 have poor signal reception here in Novi Sad (with stock I have every single one station) and spirit2 doesn't work for me... HTC buzz still stays my fm device
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Spirit2 Requires the Radio Iris and Radio Iris Transport Drivers in the Kernel. @rmbq and @AKToronto included that a long time ago. In Bubba/Void the Voltages are lowered further than IceCode so it randomly rebooted. About the Governors, IDK why that's happening for you, that's really strange.

[KERNEL] RebelKernel by RebelLion

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.