{
"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.
Related
Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food
Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file
You sir are an absolute saint
Thanks so so much
5 STARS!
very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks
How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance
cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod
i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply
Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do
can't wait and i'll try it now
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it
cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...
cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks
thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..
PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.
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.
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
Code:
*** Disclamer ***
[U][COLOR="red"]NOTE: This is an experimental build with some bleeding edge features enabled.[/COLOR][/U]
I'm not responsible for anything that may happen to
your tablet as a result of installing custom roms and/or kernels.
You do so at your own risk and take the responsibility upon yourself.
CREDITS:
Ziyan , Sheffzor for setting up their Unlegacy Android project, which is the base of this experimental build.
If you can afford to support some of the developers, please donate to them instead of me.
Shout-out to:
AndDiSa, ParrotGeek, daniel_hk, and franciscofranco for their involvement in Nexus 7 kernel/ROM development.
Features:
The same as Unlegacy Android's kernel, with the addition of ZRAM & ZSMALLOC from upstream kernel 3.10 , and with the addition of SDCARDFS.
Installation:
0. MAKE A BACKUP
1. This kernel is compatible with Unleagcy Android's ROM only, and nothing else.
2. If you have the above mentioned ROM installed, boot in to bootloader mode and flash the boot.img with the following fastboot command:
Code:
fastboot flash boot boot.img
3. If you were previously rooted, don't forget to re-apply root to avoid any related boot loops.
4. Altough ZRAM is added as a feature you have to actually set a size to it in Kernel Adiutor (or some other similar kernel manager app)Download#1/Download#2 and tick "Apply on boot" and reboot your device to turn it on.
Or alternatively create an init.d script to enable it with your desired size at boot.
You can verify if your swap/zram device is working by typing "free" or "vmstat" into a terminal emulator.
If the size of the swap device is anything but 0, it will work.
{
"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"
}
Zram is set to LZ4 compression and 4 streams by default, swappiness is set to 50.
5. [Optional] SDCARDFS is enabled by default , you can verify that its working by typing the following commands into a terminal emulator:
Code:
su
df -t sdcardfs
If some lines shows up like on the picture below then SDCARDFS works just fine.
6. Various ramdisk scripts like re-mounting the drives and trimming are currently not added, to avoid any bug reports related to these additions. You can still use SSD Boost or FSTrimmer app to achieve these effects. If this build proves to be stable enough we can look in to adding the scripts to the ramdisk.
7. Have fun
Bugs:
Same as on the base 3.4, for example I rarely encounter a hang/freeze with some graphical glitches, but it's pretty much the same with the unmodified base version.
Due to the lack of a Tilapia device, I was only able test the kernel on a Grouper.
SDCARDFS is highly experimental, it caused some issues on other devices for some users (like space not freeing up after deleting some files), although it works fine for me, you should bear this in mind when you install this kernel.
As mentioned above, you have to either enable swap for zram via an init.d script or via a kernel manager app like Kernel Adiutor.
This is despite the fact that the block device is added to the fstab and swapon_all is added to the init.grouper.rc . Still have to figure out how to get around this, but currently i don't have the time to do so.
Downloads:
Check the downloads tab at the topic title, or
click here for the download link
Sources:
https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Changelog:
2017.06.26
Initial release
Added and enabled ZRAM & ZSMALLOC from upstream 3.10
Added and enabled SDCARDFS
Enabled F2FS for both Cache & Data
XDA:DevDB Information
[TEMPORARY HALT][ALPHA][3.4][ZRAM][SDCARDFS]Experimental Nexus 7 kernel build, Kernel for the Nexus 7
Contributors
namerke, Ziyan, Sheffzor
Source Code: https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Kernel Special Features: SDCARDFS, ZRAM, F2FS CACHE/DATA
Version Information
Status: No Longer Updated
Created 2017-06-26
Last Updated 2017-11-10
Reserved
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
Geko45 said:
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
Click to expand...
Click to collapse
Well, as said in the list of bugs, tilapia is not tested at all due to lack of device.
But if you didn't perform a clean install than it can take it's time to get through the bootloader screen, even on grouper. So make sure you wait there for a while.
On clean install I didn't encounter this issue.
Aside from the freezing issue, this is way smoother than stock.
My current config includes
200MB Zram (swappiness 100 - like Andisa's)
CPU quiet policy: runnable (experiment in reducing the freezes)
interactive perameter 'midrange_go_maxspeed_load' reduced to 90 from its default of 95.
Root Killing SystemUI when the screen is off (Again to try to prevent freezing/need for manual reboot)
SSD Boost
Running this command at startup :
Code:
service call SurfaceFlinger 1009 i32 1
(old habit - suggestion of parrotgeek's to speed up rendering of transparency)
Current result: freezing maybe eliminated, time will tell...
Current theory: Freezing may be due to excessive background cpu load, ie. the system trying to do too much at once. SystemUI may have nothing to do with it, but I still have my suspicions.
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
adstraylight said:
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
Click to expand...
Click to collapse
why the force gpu 2d rendering?
abhifx said:
why the force gpu 2d rendering?
Click to expand...
Click to collapse
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs ?
adstraylight said:
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs
Click to expand...
Click to collapse
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.
abhifx said:
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.
Click to expand...
Click to collapse
Amateurs of the world unite!?
It was something I remembered from trying to optimise MM on grouper that made a lot of difference at points.
So I've stopped killing the systemui, rebooted, and have had 19hrs of uptime since, so I think we can discount that as a cause.
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good ?
adstraylight said:
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good
Click to expand...
Click to collapse
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
abhifx said:
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
Click to expand...
Click to collapse
My guess is that they're already aware of what's been posted here, how are you finding it?
adstraylight said:
My guess is that they're already aware of what's been posted here, how are you finding it?
Click to expand...
Click to collapse
they are relying more on changes pushed to their gerrit rather than tracking all the thread. so i dont know posting in their thread is also a good idea.. but hey its better than nothing.
@namerke great to see someone build something off of the work the 3.4 guys achieved. This was the sort of thing we hoped for from the beginning and I really am surprised that you're the only one so far, years after the project started, to brave the source code and use it for a project.
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream? Cheers
I am running @adstraylight suggested tweaks and its running Rock Solid. The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy. After the initial start the tablet stops having any system ui, force close, or mtp reboot issues. Boot is much faster and functions more like a normal tablet. I would recommend these changes to be incorporated into grouper unlegacy because as of now, running stock unlegacy with updated builds still has freezing, random rebooting and general issues with slowdowns. Honestly I still don't know why F2FS got scrapped for data and cache. I get that they are working on adding support for a lot of devices but it's just not useable in its current form with stock Unlegacy, unless you are okay with systemui freezes and random reboots.
New version is up, please refer to the #1 post for the updated changelog.
adstraylight said:
My current config includes
200MB Zram (swappiness 100 - like Andisa's......
Click to expand...
Click to collapse
Hi @adstraylight , thanks for all the feedback, it's been helpful , really, since i don't have much time to pressure test our device.
New version is including some of your suggestions to the interactive governor + some adjustments to it from Unlegacy-Android gerrit.
Also, @AndDiSa uses 250MB of ZRAM with swappiness of 60 by default , therefore this is the way I have configured the latest version since it seems to work just fine on 3.1 .
Number of ZRAM streams have been reduced to 1, just like @AndDiSa 's config, again , to reduce CPU load.
HTCDreamOn said:
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream?
Click to expand...
Click to collapse
Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
chosin137 said:
The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy.
Click to expand...
Click to collapse
@chosin137 , thanks for the feedback. As it turns out, based on my experience F2FS on cache causes some instabilities on this version too, therefore I have removed the option to use in in fstab.grouper on the updated version.
Also, this way it will be closer to the base , which can help with merging if @Ziyan and @sheffzor decides to go that way.
Thank you all for the feedback, happy testing
Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
Click to expand...
Click to collapse
Makes sense, I've seen a lot of kernels using zram and similar from 3.10. That could be it, it doesn't look like zram is enabled at all in the default kernel but I find it odd that it would be missing the files. I only just flashed the recent version of the ROM a few days ago so it's running fine on the stock kernel, will give yours a go once I've bogged it down with some more apps though.
sadly my experience is on the negative side as i can easily completely freeze my tablet. only reboot is the solution. i guess i have seen this issue more in the stock 3.4x kernel too so i guess its more of a rom / memory leakage issue. However the tab does feels smother than other 3.1x kernel based rom. so the tweaks does seem to help more. i might try flat rom+kernel for while, if things are better then i can blame gapps and remove it altogether (although i do want maps for navigation purpose)
A11 & A11 - use v16
A13 - use v16
Hey Coral / Flame Gang!
First off, I'm glad to be here. I just came from Pixel 2 XL after my phone died from hardware issues and I needed to upgrade!
Anyway, here's a script that I put together for my own use, but still develop occasionally; tuned especially for our Coral / Flame devices.
Enjoy!
The Back-Story:
I helped some good guys out with developing the awesome Franco.Kernel tuning parameters "back in the day" (Franco's Dev Team - you can look us up, the great osm0sis still hosts the original file set - but they won't even run on Android Pie or later). What is still applicable to Android 12 is in this file; trimmed and consolidated into a single script, along with some other goodies I've come across since.
Philosophy:
- I don't write untested BS or questionable crap in my scripts. If a given tweak doesn't show an objective improvement in benchmarks or battery life or a subjective improvement in performance that can be turned on or off by running or not running the script in a blind test - it doesn't get added.
- If I do not believe a given tweak is safe to run on everyone's daily driver device, I also won't include it my script, regardless of the benefit.
- This script is biased toward increasing performance - but it takes advantage of battery saving opportunities that don't affect performance.
Notes:
- This script is lean and mean, but it's not rocket science.
- I didn't invent anything here. Feel free to use it (or not), distribute, alter, whatever; to your satisfaction, giving credit for redistribution only to "Franco's Dev Team", and maybe me if you're feeling generous.
- I have verified it works well on my personal Pixel 4 XL, and is compatible with all Android versions, Kernels, and Magisk versions applicable to the device.
- It won't make your phone run any worse, and it should make it feel a bit "snappier", but YMMV.
- Most benchmark scores improve marginally (1% - 4%) on my device with stock or EX kernel. Again, YMMV.
- I do not plan to do heavy maintenance on this, but I will keep it up to date so it at least safely runs on the Pixel 4 / 4 XL as long as I own one. I will post updates with a minimal change log (it's a script, you can read it!). If I stumble across something that helps the community, I'll share it!
Disclaimer:
I can't see how this could possibly cause irreparable harm to any Android device on which it is run.
However, I suppose untested configurations may (rarely) have slow-downs, reboots, or other effects.
REGARDLESS, it is offered as-is with no warranty, and you choose to run this at your own risk.
If you do encounter issues, let me know and stop using the script. I may ask you for further help with debugging.
Requirements:
Root
BusyBox installation (I recommend the Magisk module by osm0sis)
Knowledge of how to execute a linux script and/or where to place it and allow permissions to run on boot
Usage:
Download the linked file to your device
Copy it to /data/adb/service.d
Ensure permissions are correct (0755)
Reboot and wait a three minutes
NOTE: The script will generate a text file called "pksp4_script_result" in the base of your "external storage" directory (/storage/emulated/0). This file will state either "Success!" or "Failure..." indicating if the script completed at the last execution attempt (it will over-write each time the script is run - check the date/time stamp on the file properties) .
Credits:
Franco's Dev Team, esp. osm0sis
Others as noted in the script file header
94pksp4v16.sh
Shared with Dropbox
www.dropbox.com
94pksp4v17.sh
Shared with Dropbox
www.dropbox.com
Change Log
V17 (use for A13)
- Audited script against A13 to ensure compatibility
- Script timing edits to support successful execution on A13 with Magisk 24 (especially ZRAM)
V16 (use for A11 and A12):
Fixed V15!
- Delayed and slowed ZRAM change to enhance the reliability of it "taking" on each boot
- Made Adrenoboost and power-efficient work queues contingent on those modules actually existing in the user's kernel
- (Did the same with the wakelock blocker while I was at it)
- Fixed a script typo that was the likely root-cause of V15 not running to completion or outputting "failure" for some users.
V15:
Enabled power-efficient work queues by default (most kernels have this functionality built in)
Enabled GPU Adrenoboost module by default, set to low boost (many kernels have this available, on/low seems preferred for a slight / smooth gaming boost without battery life detriment)
Changed vm.vfs_cache_pressure to 50 (was 200, wrong-direction from 100, I now believe after more testing)
Changed vm.dirty_ratio to 10 (from 20; avoids latency when having to write-out data to disk asynchronously by halving the amount of data needing to be written; this could reduce occasional "hang-up's" you may have experienced on this device regardless of kernel or mod - including stock!)
V14:
Increased ZRAM capacity by 50% to 3 GB
Turned off TCP timestamps to reduce overhead
Adjusted VM settings for having more memory
Added a couple minor VM tweaks
Added a minor kernel scheduler tweak
Minor code clean-up and re-ordering
V12:
Small core schedutil up/down rate limit tweaks, making small cores more responsive to increasing frequency and maintaining higher frequencies a bit longer. This should keep more load on small cores / reduce offloading to big cores unless big core utilization is truly necessary. I noted a little less latency and a little better battery life in my testing.
V11:
REMOVED.
V10:
Welcome to 2021.
Minor update - now bbr2>bbr>westwood (depends on what your kernel offers) for TCP congestion control algorithm. As an aside, I reconfirmed txquelen of 512 is still optimal for modern wifi and lte networks.
V9:
Happy holidays!
Added some TCP and kernel cfs tweaks that reduce device latency.
V8:
Stable, slightly improved Android 11 release.
Minor CFQ tunable tweaks that very slightly improved IO in benchmark testing.
Now blocks a single wakelock: qcom_rx_wakelock (if your personal philosophy is to never block any wakelocks, feel free to comment that line out in the script).
Changed TCP congestion avoidance algorithm to BBR2 (if available in kernel) - else, Westwood; based on network speed testing (BBR2 > Westwood > BBR).
V7:
Removed mount tweaks - they no longer do anything useful
Increased DBR slightly
Modified write-out file to not list time/date (for some reason it was being written twice on R). Just look at the file properties in your file manager to see when it was last written, if needed.
V6 is deprecated: Use V7 for R, V5 for Q
V6:
- Updated for Android 11 B1, verified to run without outputting any errors and is 100% stable.
- Removed one schedutil tweak that is no longer available on A11.
- Reverted kernel entropy settings to stock; tweaked settings were no longer increasing entropy pool.
- Users on A10 may use v6 without any issues, but v5 will still provide very slightly better performance on A10.
V5:
- A minor kernel overhead reduction from scheduler statistics
- Force CFQ as scheduler (just in case non-stock kernel isn't already set that way)
- Two CFQ tweaks, one that eliminated backward seeking penalty (makes no sense on non-rotational storage) and one that my testing showed sped up throughput and in theory should also reduce latency (so a true win-win!).
V4:
- Reverted foreground app schedtune boost, swappiness, vfs_cache_pressure, and dirty_ratio to stock
- Reverted IO scheduler to CFQ
- Removed wakelock blocking - verified no / minimal effect on deep sleep (I got 0.12%/hr idle drain overnight)
(for all of the above, thanks to @Freak07 for the advice / education!)
- Re-verified tx_queue_len (512) and tcp_congestion_control (westwood+) are optimized for WiFi and LTE networks
V3:
- Remove fstrim commands for /data and /cache since device is F2FS and fstrim doesn't apply (thanks to @woundman for pointing this out to me)
- Changed to Deadline scheduler with Franco Dev Team tunables - I just verified still benchmarks better after all these years
- If your kernel does not have Deadline available (e.g. stock kernel), the script will still keep you on Noop, as before.
V2:
- Reduce schedutil downrate limit to increase battery life.
- Block some safe wakelocks to increase battery life.
- Oh yeah, and a magic trick to turn off vm dirty write back timer (it still happens, just memory based and not every 5 seconds), to also increase battery life.
V1:
- Initial Pixel-4/XL release.
ooh interesting! would this play nice with the blackened mod found in this forum?
pwnsicle said:
ooh interesting! would this play nice with the blackened mod found in this forum?
Click to expand...
Click to collapse
I wouldn't recommend you to mix stuff together because it can introduce values that conflicts with each other to some possible very random extent. Though it's your device - try it out and report back with accurate feedback on how it does perform.
:highfive:
I use this Script with fsociety Kernel 1.27 and it works fine.
Thx for it
Gesendet von meinem Pixel 4 XL mit Tapatalk
Welcome to the Pixel 4 XL community. Also coming from the Pixel 2 XL as well, looking forward to testing this out. ?
I'm on flame using this script and seems to work fine here.
It feels a bit snappier.
Thanks for your work.
Welcome brother... Nice to see another Taimen dev jump into the pool here!
I'm on p4 with kiri, so good so far, let's see how will this improve battery life, thanks
Running great on fsociety!)
Stock ROM only? Or will it work in pixeldust too.
pwnsicle said:
ooh interesting! would this play nice with the blackened mod found in this forum?
Click to expand...
Click to collapse
It should. My script runs after BlakenedMod, so you'll get most of xFirefly93's battery savings, with a little bit of the PK snappiness.
xFirefly93 said:
I wouldn't recommend you to mix stuff together because it can introduce values that conflicts with each other to some possible very random extent. Though it's your device - try it out and report back with accurate feedback on how it does perform.
:highfive:
Click to expand...
Click to collapse
See above. Should be fine to run both... might even be best for some users! Let us know if it doesn't work!
MarcoG: said:
I use this Script with fsociety Kernel 1.27 and it works fine.
Thx for it
Gesendet von meinem Pixel 4 XL mit Tapatalk
Click to expand...
Click to collapse
Glad to hear it!
Curiousn00b said:
Welcome to the Pixel 4 XL community. Also coming from the Pixel 2 XL as well, looking forward to testing this out.
Click to expand...
Click to collapse
Thanks. Hope you like it!
2WildFirE said:
I'm on flame using this script and seems to work fine here.
It feels a bit snappier.
Thanks for your work.
Click to expand...
Click to collapse
Glad to hear it - it should...
CyberpodS2 said:
Welcome brother... Nice to see another Taimen dev jump into the pool here!
Click to expand...
Click to collapse
Thanks! Great to see you again, too. Athouth, technically, I'm not a Dev
bl4dy_pt said:
I'm on p4 with kiri, so good so far, let's see how will this improve battery life, thanks
Click to expand...
Click to collapse
Probably won't help much, but I'm working on some improvements for V2 (probably tomorrow or the day after!)
FlatOutRU said:
Running great on fsociety!)
Click to expand...
Click to collapse
Thanks for letting me know!
chopt51 said:
Stock ROM only? Or will it work in pixeldust too.
Click to expand...
Click to collapse
Any ROM!
New Version - V2
A little Sunday night treat!
V2 available in OP, change log in 2nd post.
Better battery life as I tune this in for Pixel 4/XL...
Any testing with kirisakura's kernel? You said not to mix things
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
tlxxxsracer said:
Any testing with kirisakura's kernel? You said not to mix things
Click to expand...
Click to collapse
It should work on any kernel... I've used on on stock and EX on Pixel 4, but I used it on kirisakura on my previous Pixel 2 XL device. If there are any issues, let me know.
woundman said:
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
Click to expand...
Click to collapse
Thanks for the heads-up. Running the fstrim command doesn't return any errors, so the script is "safe" to use, but if it's not actually doing anything on the device, I'll remove it in a future release.
woundman said:
I see your script runs Fstrim. I thought Fstrim doesn't work on F2FS system partitions. Figured I'd mention it.
Click to expand...
Click to collapse
AFAIK - only the /data partition is using the "newer" f2fs filesystem on the three latest Pixel line-ups..
xFirefly93 said:
AFAIK - only the /data partition is using the "newer" f2fs filesystem on the three latest Pixel line-ups..
Click to expand...
Click to collapse
Looks like you're right.
That said, I stopped trimming /System to be safe once Android went SAR, and /Cache is sym-linked to another partition anyway. So, I don't think the commands are actually doing anything anymore - at least not anything useful since /cache isn't really used for much on newer Android versions.
I'll be removing the fstrim commands starting with the next version. In the meantime, it's not really hurting anything.
Thanks for the mod. How can one confirm if this is actually running?
sharpz811 said:
Thanks for the mod. How can one confirm if this is actually running?
Click to expand...
Click to collapse
Look for the log as in the pic. Then view it with your text viewer. It should say script successful :good: