UPDATE 8/24! Please go to the site and download the latest version RC1b which corrects 2 small bugs people have reported. It now sets the proper permissions on batt-diag so it runs, and it changes the way the program tries to SU so that you can choose to not have the program attempt to run SU if your rom has trouble running su from terminal;
---Original Below---
I decided to create a new forum for the latest battery tweak as so much has changed since the initial versions.
To get things started, I'll just say that collin_ph battery tweak is a collection of scripts designed to make the hero (for now) last longer on battery, run faster, and run better. The tweak includes CPU management, Battery Management, Disk Performance Boost, Scheduler Boost, LED Fix, Audio Quality boost and other features to improve the usability of your Hero.
Instructions: Go to http://www.primoweb.com/froyo to download the latest version and get the documentation.
Boot into recovery and flash the zip file.
After reboot, you may run batt-cfg from shell or terminal (Note, that the scripts will all request root access, so there's no longer a need to su before running them).
to run batt-cfg
go to terminal in the phone or use adb shell from your PC
once there, type
batt-cfg
It will pull up a menu of choices. For further info, see http://www.primoweb.com/froyo
You can load a 691 mhz default (most Cyanogen kernels now only support up to 691 mhz anyway), or, if you have an uncapped kernel, you can choose a 768 mhz setting. Note: Both settings actually run at 691 when on battery and only run higher when plugged in.
The basics of how the battery is extended is that this tweak causes your phone to scale down (to lower frequencies) faster and to scale up slower. In stock configuration, the cpu scales up when only under 70% load -- while part of this tweak causes it not to scale until it's at 95% load, avoiding unnecessary scaling and battery drain. A second (and arguably more important) feature, is that as the battery drains, it lowers the maxumum CPU frequency. So when you have 1% battery left, you may be running at 468mhz instead of 691. Another plus is that the phone runs in a "higher performance" mode while charging via AC, and another mode to make sure the phone is actually charging when connected bia USB, in addition to the settings mentioned above when the phone is on battery.The best part is that almost every parameter in the system is adjustable through terminal or adb shell using a program called batt-cfg -- just run it and you'll be presented with a menu of options.
I'm constantly updating the documentation, so please check back often as I'll update this thread until there's a final 3.0 version. We're already working on a 4.0 which will be available on the market. We'll post more info there as it happens at www.tweaktool.com
COMPATIBILITY NOTES:
This tweak only works with clockable kernels. A lot of ROMS have reclockable or overclockable kernels which should work. I recommend Froyo roms, but I have heard of the tweak running with 2.1 releases. The main incompatibility seems to be with the service startup-- on some roms, the service doesn't automatically start up.
to verify if your rom is compatible and that the tweak is working, reboot.
Then go to terminal or adb shell and type:
pidof batt.sh
if it returns a number, then the service is running. If not, you'll have to start it manually every time the phone reboots by going to terminal or adb shell and typing
batt-cfg
then choose the option to save and exit. This will manually start or restart the service. Note: if your rom does not start the service automatically, you'll have to do the above batt-cfg procedure after EVERY boot or battery tweak will not run.
If you're a ROM developer, you'll can probably make your ROM compatible by adjusting your rom (ramdisk) to call (import) /system/etc/init.local.rc from init.rc -- assuming your ROM has an overclockable kernel like fresh, darch, or others.
ROMS based on unclockable kernels like Damage Control, won't work without a kernel upgrade and may still not start the service automatically upon reboot.
Thanks to Decad3nce for testing and improving several parts of the battery tweak.
So to flash this tweak and have it working on the latest Froyo nightly, do we need to flash overclockfix.zip ??
I had to flash this fix almost with ever nightly, coz the frequency list would not show up when i need to customize tweak settings.
I was reading the documentation and saw the CFS tweaks are disabled by default. Will this correct the GPS issue that was on beta 10?
Froyo Hero to the rescue
Thank you for all your work on this, got 12 hrs on 50% today with beta 10 and Decad3nse #8, 768 pre-set, most time I've ever gotten outa my Hero. Flashed your RC1 (with Darch's RC1) about 45mn ago and used custom settings to jack-up the max to 768 across the board, min.s and intervals stock. Thank you for explaining the 768 pre-set is really 691! Gonna sit on what I've got for a day and then try w/ Darch's "fix" kernel. Hope I can keep the max on batt @ 768 'cause it seems to make my Hero more responsive/less laggy.
I was not able to use the batt-diag in adb shell. I'll report back tomorrow how the tests go.
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
it made my hero laggy!!!
ToxicToastKatz said:
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
Click to expand...
Click to collapse
Follow the uninstall steps form the documentation
How do I uninstall it?
adb shell
batt-rm.sh
Follow the prompts and the tweak will be uninstalled.
Click to expand...
Click to collapse
Then flash the new version, this is how I have been doing it.
Excellent tweak! Used it through Beta and now enjoying the RC. Well done!
wow.. the way things are going i don't think i am going to jump into a evo... i am loving my hero so much.... thank you for all your hard work..
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
imb951 said:
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
Click to expand...
Click to collapse
Thanks for the notes on batt-diag. I'll look into it and release a fix this evening. Thanks.
Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
I'm getting the same root problem with 8/22 nightly.
Sent from my HERO200 using XDA App
Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
collin_ph said:
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
Click to expand...
Click to collapse
I'm using my red dawn rom with a modded ramdisk to allow for the battery tweak. The beta 10 worked and even the rc1 asked for su and I said allow the the whoami just kept going and going. I uninstalled via ur instructions on ur site and flashed again and same results
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
zachslavin said:
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
Click to expand...
Click to collapse
Were you doing the updates through ADB or terminal? When would it hard lock up.. during save changes?
CFS Tweaks and Decad3nce Kernel
I understand from reading the Kernel info, that the CFS on this tweak needs to be disabled first....did you make CFS tweaks on by default? Arent we supposed to flash the kernel first, then disable cfs tweaks and reboot? Im confused as to the order in which things are flashed. WIPE, ROM, GSHITZ, BLACKMOD, KERNEL#7, COLLINS RC1. Then go to term EMU and disable CFS, then save then go back into batt-cfg and choose option 1 768 and save and exit then reboot. Woudl that be correct?
Related
Warning Note: Overclocking may result in damage to your phone components, loss of life expectancy, or even frying them. Overclocking is done at your own risk and we take no responsibility for any damage you inflict upon your phone.
***This guide assumes you have rooted your Droid ***
Step 1: Download evilboot8.img here. (this is to overclock to 800mhz, on the web you can find files for 900mhz, 1.1 ghz and up to 1.3 ghz (tho not stable)
Step 2: Make sure you have/do all the following..
* Make sure you have sprecovery
* Make sure you have flash_image on your system, in /system/xbin/ or /system/bin
* Make sure you perform a nandroid backup first
* Make sure to enable USB debugging on phone
Step 3: Copy the respected evilboot file to the root of your SDCard (evilboot8.img)
Step 4: Now, reboot in sprecovery
Step 5: Select mount options
* mount /system
* mount /sdcard
Step 6: From your PC run the following…
* adb shell /system/xbin/flash_image boot /sdcard/evilboot8.img OR
* adb shell /system/bin/flash_image boot /sdcard/evilboot8.img
* (Where ever your flash image is on your phone xbin folder or bin folder)
Step 7: Now, unmount both system and sdcard using the following command
* unmount/system
* unmount/sdcard
Step 8: Now, reboot your device.
Click to expand...
Click to collapse
(this is not my work, just a mash up of guides from the net)
Is this for the milestone to?
Isn't this far more complicated than necessary?
As long as you have root, the free version of Rom Manager allows you to download any of bekit's or P3Droids kernels, low/normal/high voltages up to 1.2 or 1.3 ghz I believe. That coupled with setCPU (for on-demand scaling) eliminates any need to use the SDK really, doesn't it?
yes setcpu is much essier but i just thought i post here as a resource
Overclocking made easy
Just use this app (also available on the market).
This will allow you to set a predefined speed or custom speed/vsel (voltage selection).
Then use SetCPU and use option Autodetect speed. If you don't choose this option, you won't be able to set it to it's maximum speed.
I'm using SHOLS_U2_02.31.0 (2.1-update1) from this website and working perfect after applying root offcourse.
I do not know if this app is working for other versions then SHOLS_U2_02.31.0
Sort of related:
Is there a guide to the "best" configurations for stability and battery life using SetCPU or Overclock Widget on the Motorola Droid -- I've been trying to overclock my girlfriend's phone to save her battery life but neither SetCPU nor Overclock Widget work properly. SetCPU doesn't seem to run profiles correctly and is constantly spamming the highest clockspeed chosen, eating battery life like you wouldn't believe and Overclock Widget isn't properly recognizing clock speeds, displaying the wrong value...
So I was hoping that somewhere there was a guide to configuring these options once the phone was rooted and running a ROM which used a kernel that supported overclocking.
corrosivefrost said:
Sort of related:
Is there a guide to the "best" configurations for stability and battery life using SetCPU or Overclock Widget on the Motorola Droid -- I've been trying to overclock my girlfriend's phone to save her battery life but neither SetCPU nor Overclock Widget work properly. SetCPU doesn't seem to run profiles correctly and is constantly spamming the highest clockspeed chosen, eating battery life like you wouldn't believe and Overclock Widget isn't properly recognizing clock speeds, displaying the wrong value...
So I was hoping that somewhere there was a guide to configuring these options once the phone was rooted and running a ROM which used a kernel that supported overclocking.
Click to expand...
Click to collapse
What you want to do is UNDERclock her phone
but best for battery life would be to turn off widgets that update automatically or update less frequently so once every 30 min or 15 also display time out i find around 7 seconds is aways good and brightness of display down that will all help
I literally JUST picked up a Droid from a friend (used to have an Eris)
Rooted, flashed Cyan 6 and I'm up and running with Clockwork and ROM manager.
However, absolutely none of the OC kernels are working for me :/ Infinite splash screen!! doesn't even make it to the animation.
Any suggestions?
So far I have tried 1000, 1100 and 1200 mhz low voltage kernels and also 1100 and 1200 standard voltage.
First the kernel you use you must make sure it is compatible with your rom, I had many issues with kernel being compatible with bugless beast v0.4 but was able to find on from p3droid. I would recommended searching for a kernel specific to the rom. It should also say in the roms download forum which ones are compatible. There are roms still downloadable for previous version roms like 2.1 and etc. Just becareful, I had just switched to sapphire 0.8.4 which is from a new source build and I can tell you works great, I just followed spacific instructions on rom forum for overclocking, it mentions roms have scripts that make certain kernels work with them only if they were created for it or compatible. I should mention I also tried cm6 and I've found sapphire more stable and customizable as well as user friendly.
Sent from my Droid using XDA App
I didn't know where to post this, but I figured this was an appropriate thread because it dealt with overclocking.
http://www.greenecomputing.com/apps/linpack/linpack-top-10/
I was unable to get to the device specific listing, but it's clear that the Droid is ridiculous being on the list (once as the Milestone). I was wondering what it was these guys did to get so high? I understand flashing a stupid fast ROM, but are these phones similar to "dyno queens" in relation to cars? Just good for numbers but unstable for day-to-day use?
If so, what are the numbers for more "stable" ROMs in terms of MFLOPs?
Apparently the issues I was having were related to the recovery image not being properly flashed, therefore not flashing other zips correctly... after re-flashing the recovery a few times, I was able to boot up with Chevy's 1200mhz Low Voltage kernel and it runs perfectly on CM6.
11-24-2010 UPDATE
http://www.ziggy471.com/2010/11/24/ziggy471-kernels-incbravoevo-updated-24-nov/
11-14-2010 UPDATE
http://www.ziggy471.com/2010/11/14/ziggy471-kernels-incbravoevo-updated-14-nov/
11-13-2010 UPDATE
http://www.ziggy471.com/2010/11/13/ziggy471-kernels-incbravoevo-updated-13-nov/
11-05-2010 UPDATE - Sorry for the late update!
http://www.ziggy471.com/2010/11/05/ziggy471-evo-kernels-fps-fixed-updated-5-nov/
10-28-2010 UPDATE
http://www.ziggy471.com/2010/10/28/betaziggy471-evo-kernel-updated-28-oct/
10-26-2010 UPDATE!
ZIGGY updated the kernel. Here is the link. (It's the link that has evo in it)
http://www.ziggy471.com/2010/10/26/...credible-aospevobravo-kernels-updated-26-oct/
ZIGGY, thanks for visiting this thread and thanks for a great kernel.
10-25-2010
Hey Everyone, first of all I DO NOT take any credit for this kernel. I came across it in Myn's Rom thread and since it didn't have it's own thread, I just wanted to start one so people could find it easily. I also noticed it in VirusRom's thread. So whoever ziggy is, thanks a lot! I'm getting great battery life on this kernel and according to the threads, it looks like others are also. Here's the link to ziggy471 website with the download. Thanks again ziggy!
http://www.ziggy471.com/downloads/?did=31
source can be found here ~~~> https://github.com/ziggy471/linux-2.6.32.25/tree/evo
gotshores said:
Hey Everyone, first of all I DO NOT take any credit for this kernel. I came across it in Myn's Rom thread and since it didn't have it's own thread, I just wanted to start one so people could find it easily. I also noticed it in VirusRom's thread. So whoever ziggy is, thanks a lot! I'm getting great battery life on this kernel and according to the threads, it looks like others are also. Here's the link to ziggy471 website with the download. Thanks again ziggy!
http://www.ziggy471.com/downloads/?did=31
Click to expand...
Click to collapse
+1 on this bro! Found the kernel this morning while looking for bakes kernel lol. Awsome one got lil lags here n their but can b workable
Sent from my PC36100 using Tapatalk
ya man, i ran it the other day and had great battery, but i thought it had affected my 4g connection, so i flashed another kernel. i reflashed ziggy's today because i missed the battery effect and i haven't had any issues all day (4G connects just fine). I not too technical, so i don't know the in's and out's of this kernel, but i do notice my battery life at the end of the day.
you said that you came across it on Myn's ROM. Is that the ROM your currently running? Just want to see how it works on others
ya, i'm using myn's rom and have only used that so far. would be interesting to see how it run's on other roms
im using a htc evo 4g with ziggys Ziggy471Kernel-EVO-update_signed-10242010-1644
on the download page it says alot but doesnt really explain how to access anything.
http://www.ziggy471.com/2010/10/23/z...kernel-23-oct/
i cannot adb in, says device not found, but via terminal if i do lsmod i get this
bcm4329 210342 0 – live 0xbf000000
if i try init.d or /proc/undervolt i get permission denied.
i did enter SU before entering anything, i dont know whats going on.
if i do cat /proc/undervolt i get the list of undervolt values like shown a few pages ago...
can anyone help?
Ziggy471 HTC EVO Kernel 23 Oct
NOTICE: I am not responsible for anything that may or may not happen to your phone, except for maybe it running faster. You break it, you fix it.
23 Oct 2010:
Kernel version 2.6.32.24
Overclocked
1.28GHz, I don’t recommend this setting, it doesn’t appear to work on the newer Desire ports. I recommend 1.113 or 1.15.
BFS 357 CPU Scheduler
BFQ IO Scheduler
Swap enalbed
SLUB (Unqueued Allocator)
All CPU governors, Interactive is the default
CPU Undervolt control via /proc/undervolt – built in, not a module
http://forum.xda-developers.com/showthread.php?t=775997&highlight=voltage+module
Fix for slow SD card access
http://forum.xda-developers.com/showthread.php?t=815557
CIFS
EXT4
TUN
A few tweaks here and there.
etc…
Also included in the update:
1. For any ROM that has busybox’s run-parts enabled, I added a screen state frequency/governor switching script, located in /system/etc/init.d. This means you do not have to use setcpu to control the frequency or governor anymore. If you prefer not using this script, delete it
The defaults for the script:
AWAKE_GOVERNOR=”interactive”
AWAKE_GOVERNOR_FREQENCY_MAX=”1113600″
AWAKE_GOVERNOR_FREQENCY_MIN=”245000″
SLEEP_GOVERNOR=”powersave”
SLEEP_GOVERNOR_FREQENCY_MAX=”460800″
SLEEP_GOVERNOR_FREQENCY_MIN=”245000″
2. remount script that will be installed to /system/bin.
Valid input format:
remount [ro|rw|status]
ro = read only (default)
rw = read write (to make modifications)
status = current mount mode
3. hosts file that blocks most ads, if you find more, let me know
also new kernel released on the 24th...
http://virusrom.com/Kernels/Ziggy471/Ziggy471Kernel-EVO-update_signed-10242010-1644.zip
hmm might give this kernel a try...I'm willing to try anything to save battery life...
intheb0x said:
Ziggy471 HTC EVO Kernel 23 Oct
NOTICE: I am not responsible for anything that may or may not happen to your phone, except for maybe it running faster. You break it, you fix it.
23 Oct 2010:
Kernel version 2.6.32.24
Overclocked
1.28GHz, I don’t recommend this setting, it doesn’t appear to work on the newer Desire ports. I recommend 1.113 or 1.15.
BFS 357 CPU Scheduler
BFQ IO Scheduler
Swap enalbed
SLUB (Unqueued Allocator)
All CPU governors, Interactive is the default
CPU Undervolt control via /proc/undervolt – built in, not a module
http://forum.xda-developers.com/showthread.php?t=775997&highlight=voltage+module
Fix for slow SD card access
http://forum.xda-developers.com/showthread.php?t=815557
CIFS
EXT4
TUN
A few tweaks here and there.
etc…
Also included in the update:
1. For any ROM that has busybox’s run-parts enabled, I added a screen state frequency/governor switching script, located in /system/etc/init.d. This means you do not have to use setcpu to control the frequency or governor anymore. If you prefer not using this script, delete it
The defaults for the script:
AWAKE_GOVERNOR=”interactive”
AWAKE_GOVERNOR_FREQENCY_MAX=”1113600″
AWAKE_GOVERNOR_FREQENCY_MIN=”245000″
SLEEP_GOVERNOR=”powersave”
SLEEP_GOVERNOR_FREQENCY_MAX=”460800″
SLEEP_GOVERNOR_FREQENCY_MIN=”245000″
2. remount script that will be installed to /system/bin.
Valid input format:
remount [ro|rw|status]
ro = read only (default)
rw = read write (to make modifications)
status = current mount mode
3. hosts file that blocks most ads, if you find more, let me know
also new kernel released on the 24th...
http://virusrom.com/Kernels/Ziggy471/Ziggy471Kernel-EVO-update_signed-10242010-1644.zip
Click to expand...
Click to collapse
Is there a changelog for the latest?
Trying it now. I wonder why he left out 2 of the most popular frequencies 1119 and 1228. Goes from 1115 to 1280, thats a pretty big jump......
myn said on his thread that he can confirm that adb doesn't work on the kernel released on the 24th also. if ziggy gets adb to work, he's gonna recommend it. i don't use adb, i do use terminal emulator every now and then, but haven't check to see if that wouldn't work either.
phistyle said:
hmm might give this kernel a try...I'm willing to try anything to save battery life...
Click to expand...
Click to collapse
I just grabbed it and id say Im a heavy user and i took it off the charger at 4:30am and it just died on me at 11 something ... id say pretty good battery life... using Myn's Rom
Problem with the broken adb shell is that it's causing some users to have problems using Titanium Backup. I love the kernel, but won't use it as a daily driver until Ti works without issue.
gotshores said:
myn said on his thread that he can confirm that adb doesn't work on the kernel released on the 24th also. if ziggy gets adb to work, he's gonna recommend it. i don't use adb, i do use terminal emulator every now and then, but haven't check to see if that wouldn't work either.
Click to expand...
Click to collapse
Crazy, ADB works fine for me with the one from the 24th.
do i have to go into adb shell in order to change the clock speed?
sorry im a newb...
f10g44 said:
do i have to go into adb shell in order to change the clock speed?
sorry im a newb...
Click to expand...
Click to collapse
you can use setcpu or Overclock wideget
nugzo said:
Crazy, ADB works fine for me with the one from the 24th.
Click to expand...
Click to collapse
you lucky ****er lol,
i think your the ONLY one adb shell is working for!
ugh,
we need to get someone in here that knows how to run and tweak this kernel.
its got so much crap built in and its hard to access it all, i wish there was a write up for us evo owners...
someone get ziggy in here or someone that knows about this!
The kernel that was released on the 24th seems to be well put together, I'm oc to the fullest and stable as can be, will report back what the battery life is.
Funny thing my ADB has nvr been broken and the 24th works fine for me
Sent from my phone.. I think Tapatalk???
I used to randomly read certain cries for help about the calibration being WAY off after switching a rom or kernel making the Gtab unusable and me thinking poor souls... until it happened to me
I was happily using the Clemsyn Calkulin combo when I got a bit a greedy and flashed a clemsyn 1.5ghz OC kernel, but that made my battery life lower and the Gtab get too hot, so I decided to give Gharmony 2.3.4 a try since I was flashing stuff. I did the Gharmony after wiping everything as instructed, but I could no longer unlock the screen because my taps were registering all over the place.
tried flashing the 1.4ghz OC kernel from pershoot hoping that that would fix it, but it didn't
so here's what worked:
installed the updated android SDK
then found this nice little java script from incubus26jc:
http://forum.xda-developers.com/showthread.php?t=663390
that allowed me to control the tablet from the computer.
I tried to install Root Explorer so that I could do the empty calibration.ini file method (http://forum.xda-developers.com/showthread.php?p=12555275#post12555275) but Root Explorer kept force closing in GHarmony, so I had to go back and reflash my favorite (never to ever leave again) Clemsyn/Calkulin ROM
installed root explorer, got the calibration.ini file in, rebooted, and everything is great!
the calibration app from the other popular posting never worked for me (and not this time either).
So just thought I'd pass that along to others (the key point of my journey being that java script I found from incubus26jc!)
To calibrate the touchscreen the next time it gets out of whack, try this:
Code:
$ su
# echo -n 1 > /sys/devices/platform/tegra_touch/calibration
I'm pretty sure the echo command will also work. See this post for more.
Hello. The supercharger script by zep worked great on my galaxy ace. Now, has anyone been able to use it with the tab+? I think it would be a huge help to remove kauncher redraws and in improving the battery life. Do you guys think it would work on our tab? Our brothers from the gtab 10.1 were able to use it. http://forum.xda-developers.com/showthread.php?t=1256796&page=24
Click to expand...
Click to collapse
EDIT. 12/29/2011
Okay. Since no one bothered to reply, i took the risk and applied the script. To cut to the chase, IT WORKS. There are no launcher redraws and my tab sure feels a lot smoother. I also have 400 used RAM instead of 600 after a restart. Not to mention, i now have 6037 AnTuTu benchmark score as opposed to the 5700 that i got before supercharging.
------------------------------------------------------------------------
EDIT. 12/31/2011
------------------------------------------------------------------------
EDIT. 02/02/12
(I updated the versions to their latest in accordance with zepp's latest released scripts. supercharger 5.2 and KAK 3.1. The steps to be followed are still the same.)
If anyone wants to try, here are the steps that i followed.
BUT first things first.
CREDIT GOES TO zeppelinrox FOR HIS GREAT WORK ON THIS SCRIPT.
I ALSO WOULD LIKE TO THANK mroneeyedboh FOR THE STEPS HE PROVIDED OVER THE GTAB 10.1 FORUMS.
Original supercharger thread http://forum.xda-developers.com/showthread.php?t=991276
GTAB 10.1 supercharger guide http://forum.xda-developers.com/showthread.php?t=1256796
P6200 CWM and Root by garyd http://forum.xda-developers.com/showthread.php?t=1392348
***You MUST be rooted and have busybox 1.18.2 or upper (I have 1.19.3)***
So let's cut to the chase!
DOWNLOAD THE FOLLOWING.
v6 Supercharger script U9 RC5.2 http://forum.xda-developers.com/attachment.php?attachmentid=877591&d=1327834355
Script Manager https://market.android.com/details?id=os.tools.scriptmanager&feature=search_result
Zepp's original post with the log changes http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Save the supercharger script anywhere on your storage
Run Script Manager and press Browse as Root (the one under Install). When the SU dialog appears press allow.
While on Script Manager, browse to where you save the supercharger script click it
A new window would appear. Press the "Su" icon under the Run button at the upper left hand corner. Press Run.
A lot of codes would appear. Some sort of system check bla bla bla. Just a little patience...
"Press Return Key... and Come Get Some!!" would appear. DON'T PRESS THE RETURN KEY. Press anywhere and press any key and then press enter.
You would then see a lot of options 1-31. Please enter number 9.
It would now run the setting we chose. Like lowmemkiller values, OOM groupings, Kernel/Mem Tweaks, etc..
If an option to not use Build.prop appears, cause it might cause boot loops, then allow the creation of local.prop (i think. i can't remember). Just follow your heart. haha
Press the back soft key. "Script is running. What do you want?" Choose Kill.
Since we're all using stock ROMs (for the moment), press the back soft key until you reach the ROOT directory. Then open the Data folder and click on the 99Supercharger.sh
Then under the Run button, press the icon for Su and Boot. This would automate the supercharger script upon boot. Then press run and then kill the script.
Run the first script again (yup the one from Step 1). and now, choose option number 30. It would now super clean the system and restart.
DONE! Feel the difference!
If I missed anything, please inform me.
You could also install the Kick Ass Kernel Tweaks (KAK) from here http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021. Get the update 3 RC3.1
KAK Direct Download http://forum.xda-developers.com/attachment.php?attachmentid=877590&d=1327834355
IMPORTANT!!!!! Just follow the steps from above and be sure not to apply the IO Tweak as it is very unstable and might cause boot loop
Then using step number 11, navigate to 98KickAssKernelizer.sh and make it run upon boot.
Reboot your device and DONE!
Based on MY observations, here are the changes that I noticed.
Completely no launcer redraws (wherein the widgets disappear and appear. it's like refreshing in windows), I'm using the default Touchwiz UX.
There is no delay with the Task Switcher. (the third soft key) Before applying the script, I had like 1-1.5 second delay with it. Now it only has 0.5 or so.
The RAM usage is stable at 530-570. Compared to 660 before supercharging
The best part about this script is that multi-tasking has been easier. Jumping from one app to another is now a breeze. Applications start faster than before.
The thing is, our tablet is already blessed with great hardware which is why it is already fast and smooth to begin with. BUT, there is always room for improvements. FACT.
BR
That's impressive!
I have the P6210. Are you using the P6200 with the 3g?
Dan
Interesting find. Would you mind sharing the installation process. From the original post seems quite easy, but on the 10.1 tread it looks way more complicated.
P_
rp518dan said:
I have the P6210. Are you using the P6200 with the 3g?
Dan
Click to expand...
Click to collapse
Yes. i have the P6200 with 3G. I think the process and result would be the same with the P6210.
pakalrtb said:
Interesting find. Would you mind sharing the installation process. From the original post seems quite easy, but on the 10.1 tread it looks way more complicated.
P_
Click to expand...
Click to collapse
okay. i'll update it in a while.
just tried it, enabling the 99supercharger.sh and 98kickasskernel.sh at boot threw me into a boot loop. it said to make sure to enable at boot, so i did. will give it another try or just manually add custom lines to build.prop ..
chrisrotolo said:
just tried it, enabling the 99supercharger.sh and 98kickasskernel.sh at boot threw me into a boot loop. it said to make sure to enable at boot, so i did. will give it another try or just manually add custom lines to build.prop ..
Click to expand...
Click to collapse
really? I wonder why. I did not encounter any boot loop. Could you check my steps that i just posted and compare it with the steps that you did?
Also, what busybox version did you use?
I think it's with the KAK Tweak. Maybe you applied the IO scheduler?
as quoted from zeppelinrox
Updated August 1: Added Kick Ass Kernel Tweak Installer but without io scheduler tweaks. Use this new script if you try the regular Kick Ass Kernel Tweak Installer and get a boot loop! (My apologies to those that got the boot loops )
Click to expand...
Click to collapse
SOURCE: http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127
And you think that I would wait for tutorial or tester to try it out !?!?!
OK, I did the following :
1) downloaded the script and put it in the sd card ( not external sd ) root
2) downloaded and installed script manager
3) run the SM and selected the script
4) selected run as root and hit the RUN
5) selected 1 as scrolling speed
6) selected 9 ( MegaRam 2 )
7) selected 17 = Exit
8) broswed back to ../data and selected the 99supercharger.sh file
9) selected the run as root and run at boot option
10) Save and Exit the SM
11) Rebooted
All fine ( I mean no bootloop ) but to be quite honest NOTHING changed in terms of performance. I double checked that the script was run at boot and it did, since the values have been changed.
But the benchmarks are the same and the tab seems lagging as usual.
Also the amount of free RAM have not changed from previous stock configuration.
I fear that the main problem is GoLauncher, that seems to have slowed down the tab even more after the last update.
P_
---------- Post added at 12:01 PM ---------- Previous post was at 11:44 AM ----------
chrisrotolo said:
just tried it, enabling the 99supercharger.sh and 98kickasskernel.sh at boot threw me into a boot loop.
Click to expand...
Click to collapse
What do U mean by boot loop, and how did you get out of it ?
P_
pakalrtb said:
And you think that I would wait for tutorial or tester to try it out !?!?!
OK, I did the following :
1) downloaded the script and put it in the sd card ( not external sd ) root
2) downloaded and installed script manager
3) run the SM and selected the script
4) selected run as root and hit the RUN
5) selected 1 as scrolling speed
6) selected 9 ( MegaRam 2 )
7) selected 17 = Exit
8) broswed back to ../data and selected the 99supercharger.sh file
9) selected the run as root and run at boot option
10) Save and Exit the SM
11) Rebooted
All fine ( I mean no bootloop ) but to be quite honest NOTHING changed in terms of performance. I double checked that the script was run at boot and it did, since the values have been changed.
But the benchmarks are the same and the tab seems lagging as usual.
Also the amount of free RAM have not changed from previous stock configuration.
I fear that the main problem is GoLauncher, that seems to have slowed down the tab even more after the last update.
P_
Click to expand...
Click to collapse
Hmmm.. Maybe it's because we have different applications installed, settings, etc. With my experience, there are some very noticeable changes.
Completely no launcer redraws (wherein the widgets disappear and appear. it's like refreshing in windows), I'm using the default Touchwiz UX.
There is no delay with the Task Switcher. (the third soft key) Before applying the script, I had like 1-1.5 second delay with it. Now it only has 0.5 or so.
The RAM usage is stable at 530-570. Compared to 660 before supercharging
The best part about this script is that multi-tasking has been easier. Jumping from one app to another is now a breeze. Applications start faster than before.
I think it may hav had to do with changing the I/O tweaks from local.prop to build.prop, it said it was dangerous. after reboot about 20 sec or so SuperUser toast says script manager was granted root permissions, meaning the 98/99.sh scripts were loaded. I didnt run the v6script at boot. after about the 3rd reboot, I had time to go into app drawer and quickly drag uninstall and it stopped constant reboot.
tried the instructions in the OP and i can confirm this works on my P6200 and solved a lot of the lag I had.
Sent from my GT-P6200 using xda premium
Hmm, I had originally used the V8 version . I have uncharged, wiped the cache and recharged it with RC4 9V . But still the same. I do not see any difference from the original performances and the Antutu Benchmark gives pretty much the same results as before. I was hoping my tab would fly out of my hands after this hack ......... but not really
Curious to read about others, it looks like we have only 3 brave souls so far
P_
pakalrtb said:
Hmm, I had originally used the V8 version . I have uncharged, wiped the cache and recharged it with RC4 9V . But still the same. I do not see any difference from the original performances and the Antutu Benchmark gives pretty much the same results as before. I was hoping my tab would fly out of my hands after this hack ......... but not really
Curious to read about others, it looks like we have only 3 brave souls so far
P_
Click to expand...
Click to collapse
Haha yeah. And I am hoping that there would be more brave souls in the Development Section.
What score did you get in the Antutu Benchmark?
5648/5804/5727 three consecutive tests.
uncharged everything and got back to stock config : 5654/5841/5708
After uncharging I still got left a 1000HP Super-(6,12,200,220,240,275).sh file in ../data
P_
Bump.
No more testers?
P_
I am giving it another shot .
The only noticeable difference is that the amount of available RAM is always around 300 mb. BUT this also tend to decrease ( sometimes to 100 ) with extended use. With stock configuration I'd have 100/250 available, with the system bumping it up to about 300 when it was going lower than 100.
As for the quick access button, it's definitely snappier when you turn the device on, but it goes back to about 1 sec after a while.
I have a P6200 and applied the script, look smooth then before applied the script. Thanks for the instruction
Hey just wondering if anyone knows how to remove this script..Thanks!
Sent from my GT-P6200.
DevilBeyond said:
Hey just wondering if anyone knows how to remove this script..Thanks!
Sent from my GT-P6200.
Click to expand...
Click to collapse
It has an option to unsupercharge. It's listed in the menu with the different options of supercharging etc.
I'm currently suggesting that people do NOT use this script.
There are bugs in the GT-P62x0 kernel(s) that can (and do) cause kernel panics. Under normal circumstances, those panics would cause your tablet to simply reboot.
However, this "supercharger" script overrides a kernel parameter and prevents the kernel from rebooting on a panic, instead forcing it into an infinite loop. Instead of the bug rebooting your tablet, it causes your tablet to be frozen (if the screen is off, it appears to be a so-called sleep of death.)
To make matters worse, if this situation occurs when the tablet is running on battery power (not plugged in), then the infinite loop will completely deplete your tablet's battery (which can harm it.)
Take care
Gary
I have used supercharger on my phone without issue but after
reading what Gary discovered, I won't be using it again.
Thanks Gary
Hey guys and gals.
So I got myself a new/old HOXL and immediately flashed a Candy5 ROM on it with all lollipop and CM12 bells and whistles. To keep things even more interesting, I threw a nice package of google apps on top of it and enabled Google Now.
Guess what I found out immediately after my phone booted
My phone was sloooooooow. Like, it was fast for 1 hour or so after reboot and then it started to drag. After a day of moderate usage it became barely usable; sometimes I would miss a phone call because it wouldn't show me the bloody dialer and let me answer.
My phone was sucking battery like a thirsty camel in an oasis in the middle of Sahara desert... ok, ok, just don't throw that tomato at me. Anyway, I was losing 10-15% of my battery per hour.
So, I started messing around with the phone and found out several interesting things. I think it's worth sharing and discussing. In the next posts, I will share my findings with you. Please share yours.
My goal is pretty obvious: fast, smooth experience on CM12 and decent battery life. I was getting 2 full days of moderate usage on my good ol' HD2, so that's my current target with HOX. I also want Google Now working, at least to some extent. I especially like the feature when it shows me my parking location and things around me, so disabling locations altogether is not an option.
First step to smoothness: swap and OOM
DISCLAMER. The script below plays with your system settings. It might cause bootloops, brick your device or start nuclear war. Please use at your own risk.
So, first thing I noticed was that the phone was getting slow because it didn't have enough memory to run. I figure that CM12 and lollipop in general is probably optimized for 2GB RAM, whereas our device has only 1GB. So I tried to play with OOM values, but didn't get the desired results. So I went and enabled swap. Guess what? Works like a charm.
Here's how I did it:
1. install SuperSU from here .
2. open it and let it install its su module. this part might be tricky; for me, doing this via recovery didn't work and regular install didn't work either. i ended up having to open ADB terminal and setting SELinux to permissive manually, like so:
su
setenforce 0
and only after that did it succeed to push its su module to system/xbin.
3. go to SuperSU's settings and make sure you have checked the following:
a. Enable Superuser
b. Enable su during boot
c. Trust system user (this is not mandatory; however, if you don't check this, you will be flooded with requests to grant su to system apps)
4. after you have everything set up, reboot to recovery and install the attached zip like you would install a ROM.
5. reboot and enjoy your new silky smooth HOX
This script enables swap on data and cache. The files are pretty large, too: 250MB on data and 250MB on cache. I saw that even with this I still have plenty of room on data and cache to keep rolling. This gives me 0.5GB of swap, virtually enlarging my RAM to 1.5GB. This seems to be enough for all my needs.
The script also sets swappiness to 50, sets OOM to the values that work best for me at the moment and brings over several optimizations from my HD2 ROM. Feel free to edit the values and share.
EDIT: uninstalling script attached
EDIT2: scripts updated to reflect my latest changes.
EDIT3: reduced small (small_swap.zip) attached for those who want to use swap with ZRAM
Second step to smoothness: kernel
This step proved to be extremely important for smoothness. For some reason, stock CM12 kernel appears to be severely underoptimized... or the kernels that our devs generously made available for us are heavily overoptimized
To my best knowledge, currently there are only two kernels that work with LP and support swap: Torched Kernel v1.4 and Frosted Kernel.
IMPORTANT: if you are going to flash Torched kernel, be sure to flash LP version 1.3 or 1.4. Previous versions break swap, thus hurting speed and stability
IMPORTANT: if you are going to flash Bricked kernel, you ABSOLUTELY MUST flash the voltage table (see this post). First flash the kernel and then the voltage table. Not following this procedure can damage your phone.
I am currently using the Bricked kernel and the results are extremely impressive.
Third step to smoothness: Ext4 optimizations: disable journaling, enable dir_index
This step helps quite a bit if you decide to stay with ext4 for now. But even if you don't and want to switch to F2FS (see step 4), it's worth doing it on the /system partition.
WARNING. Journaling slows your system down quite a bit but it also adds stability. Please beware. You may lose your data or may even have to reflash your ROM in some extreme cases.
I never experienced any problems with non-journaling systems, but be aware that google enabled it for a reason.
Note: Your system might became unstable only if you forcefully shut the device down by long-pressing the power button or if you run out of battery. In case of normal work and normal shutdowns/restarts, everything will be fine.
1. Flash the attached zip (no_journal.zip).
2. Profit! Your cache, data and system partitions have no journaling now.
Fourth step to smoothness: F2FS
It took me some time to figure out this one, but it proved to be extremely helpful in terms of speed and general smoothness. Stability is yet to be tested, but I have it for ~24 hours now, and everything looks fine so far.
0. You need a F2FS-enabled TWRP. Luckily, we have jrior001 with us, who took care for that. Grab it from here (please thank jrior001 in his thread).
1. Install Torched kernel 1.4. (Bricked supports F2FS too, but for some reason, the performance is degraded and the stability is much worse than with Torched).
1a. If you had Bricked installed, remove undervolt script from /system/etc/init.d
2. Install attached zip (evita_F2FS_conversion_v2.0_pav.zip). This will enable you to work either with ext4 (with some extra optimizations) or with F2FS, so you can always go back without having to remove it. (note that you'll have to flash this zip each time you install a new kernel)
3. In TWRP, go to Backup, select data and cache and unselect system. I also disabled compression, just in case. Start the backup and wait for it to finish.
3a. STOP! Check that backup returned no errors. If there were errors during the backup, don't go any further or you'll lose your data!
4. Now connect your device to the PC. On PC, browse to Computer\One X\Internal Storage\TWRP\BACKUPS\<number of your device>\<latest backup>
5. You will see a bunch of files whose name contains ext4. For example, data.ext4.win.md5
6. Go ahead and change ext4 to f2fs for each file. The names should now look as follows: data.f2fs.win.md5
7. Back in TWRP, choose Restore -> your latest backup.
8. Sit back and relax while TWRP reformats your data and cache partitions as F2FS and restores all your data.
9. Reboot and enjoy!
10. If you'll ever want to go back to ext4, just go to TWRP, connect your device to the PC, on your PC, restore the original names of the backup files (rename f2fs to ext4), in TWRP choose restore and you're back to where you stated
First step to battery life: wakelocks
1. Go to Settings -> Privacy -> Privacy guard.
2. Scroll down till you reach the word Google.
3. Enable privacy for everything that starts with the word Google, including (!!!) Google Play Services.
4. Long-tap to enter each row and disable "keep awake" and "wake up" wherever applicable
Also, I use ServiceDisabler (from Play Store) to enter Google Play Services and disable Google Analytics
Second step to battery life: WIFI
Settings -> WI-FI -> three dots on top of the screen -> Advanced.
Disable "Keep WIFI on during sleep" (set to never) and "Scanning always available"
Third step to battery life: build.prop
Attached is my modified build.prop. It is derived from the stock build.prop, with some important tweaks that I brought over from my HD2 ROM. The measurements here are not that objective, but I felt that I could squeeze ~30% more juice from a single charge.
Of course, uninstall script is attached as well, just in case.
Fourth step to battery life: data usage
1. Head to Settings -> Data usage.
2. Scroll down till you see Google App.
3. Click on it and enable "Restrict app background data".
4. Go back and scroll further down till you find cLock.
5. Enable "Restrict app background data" as well.
for me
another one for me
last one for me
Cannot end a call by pressing the red button.. After unswap everything is normal again.. Can you please check it?
Nice work!!!!
How did u unswap ?
My phone was kinda cool.... Until I flashed this, my phone lagged the more.
Nice work BTW.
I want to unswap please!
Flash unswap.zip.. But i just notice that despite unswapping problem still persists.. Maybe it.s a cm12 bug.. I dont know
flashing unswap.zip should remove any traces of what swap.zip has done. if the problem persists after you flashed unswap, then the problem is elsewhere
I downgraded firmware from 2.18 to 2.15 and now i can terminate the calls.. I also install your swap file in latest cm12 02.19 nightly and seems to work fine..
I flashed Candy 5 and noticed that even after installing Torched kernel and overclocking, optimizing, etc, my phone would slow to a crawl by the end of the day and it definitely wasnt a memory problem as I had plenty free. What I found was that randomly my IO settings reset to 128Kb read-ahead and the scheduler resets to ROW. Changing back manually to 512Kb and FIOPS and suddenly the performance is back to what it was. This has happened twice in two days and I'm not sure if this is a Torched/CM/Candy/or Lollipop bug but at least I figured out what was causing it....
Hi thelonewolf_pav,
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work? I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now. I hope torched can figure out what the problem is. Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps. One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Thank You,
Hi harpin,
harpin14789 said:
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work?
Click to expand...
Click to collapse
nope. it starts alright, but it's never actually used
harpin14789 said:
I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now.
Click to expand...
Click to collapse
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
harpin14789 said:
Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps.
Click to expand...
Click to collapse
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
harpin14789 said:
One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Click to expand...
Click to collapse
very simple. run terminal from the phone or start ADB. then type:
free
Click to expand...
Click to collapse
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
thelonewolf_pav said:
Hi harpin,
nope. it starts alright, but it's never actually used
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
very simple. run terminal from the phone or start ADB. then type:
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
Click to expand...
Click to collapse
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
harpin14789 said:
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
Click to expand...
Click to collapse
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
harpin14789 said:
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
Click to expand...
Click to collapse
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
thelonewolf_pav said:
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
Click to expand...
Click to collapse
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
harpin14789 said:
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
Click to expand...
Click to collapse
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
thelonewolf_pav said:
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
Click to expand...
Click to collapse
ok, thanks