yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] calvinpreston:
i don't have any problem with the sleep of death issue. the only problem i have is the battery life. 5% every 30 minutes on standby. i reconditioned my battery too. someone know how to fix this?
[Vibrant Android Development] jzero88:
Exactly. Very suprised at the battery life. Anyone able to get the full battery life to work with these kernels? And what is the cause of such a drain.
[Vibrant Android Development] JeremyNT:
Are you sure it's specific to these kernels, or froyo in general? I know that regardless of kernel wifi calling saps my battery quickly, even when it's not enabled.
[Vibrant Android Development] sader2202:
Why is my kernel keeps on panicing. Every 2 hours is on a panic PLEASEEEEE HELLLPPPPP!!!!
[Vibrant Android Development] Kubernetes:
Well, all I know is that the stock JK2 kernel has awesome battery life, something like 1-2% draw per hour on standby. That's a lot compared to some Eclair builds, but way better than any i9000-based tweaked Froyo kernel.

Eugene, I believe you when you say the tweak works on your phone, but unless the voltage readings are way off, I'm seeing the phone the phone die at the same threshold as before.
[Vibrant Android Development] t1h5ta3:
-- just a heads up --

li-io batts dont technicly get a memory, but the protection circuitry does get out of wack after alot of partial discharge cycles. the way to corect it is to manualy discharge the battery. personaly i use an old #194 automotive bulb. you are going to need a multi meter to watch the voltage so you dont go to low and brick the battery.

let the battery go below 2.5v and your buying a new one.... you have been warned
[Vibrant Android Development] calvinpreston:
i think it's the kernel because when i was in A4, my battery life is normal. my rom which is Macnut R12 in both kernel.
[Vibrant Android Development] jzero88:
Really even better than stock JI6? What Rom would you suggest or are you using?
[Vibrant Android Development] Kubernetes:
No, I don't think it's better than JI6 (well, some of the tweaked UV JI6 kernels), but it's not that much worse. On some of TW's UV/OC Core kernels I was getting less than 1%/hr drain. Froyo stock JK2 is draining about 1-2%/hr for me.

I'm currently on Obsidian v5 with stock JK2 kernel. Kinda thinking about flashing Anderdroid's AOSPish Froyo this afternoon just to play with it. Maybe Axura after that?
[Vibrant Android Development] jzero88:
I am on AOSPish right now woth a13 kernel. Not sure if its the kernel the rom also have wifi calling deleted and still am getting crappy batteru. Stock JI6 has been the best for me against any rom kernel combo. Wish there was a JK2 rom worth using. Maybe eugene can cook something up to where we can get a stock JK2 kernel with the mod that gives you dead battery at 3volts
[Vibrant Android Development] Whitehawkx:
Just wanted to share this with everyone. http://xdaforums.com/showthread.php?t=848471

It seems that the 0.3 ULF kernel has a bug in it that causes corruption to /system. Apparently this can cause things like a soft brick when you flash from ULF back to say stock kernel. Supercurio discovered it and was kind enough to share his findings. This bug can be corrected though and from what I understand its a very minor fix. Hopefully Eugene can implement this fix into his future ULF kernel releases.
[Vibrant Android Development] eugene373:
A_OVERKILL Kernel Now Posted.... So Far is Fast & Stable on my Phone...

100% ( Deleted Batterystats.bin & Rebooted )

Called Barak & got 24 minutes + on 10% battery....

Please Read OP before asking Questions regarding this Kernel..

~Eugene
[Vibrant Android Development] xspeed9190:
Sounds great lets give it a shot.

Eugene. when we delete battery stats then the battery dies. and gets to around 10~ or below will we see the mV go below 3500
[Vibrant Android Development] rsfaze:
Just flashed a_overkill. My phone was sitting at 100% from your stock kernel running Macnut 12 flawless for the past week.

Just unplugged will report some battery life in a few hours.

ty sir for your dedicated work, need to send some Pepsi funds to you and Barakin.

edit, converting to jfs looks with a backup and restore, looks frozen on libysshared.so :(
[Vibrant Android Development] hanbaoquan15:
Has the sleep issue been fixed?

Thank you Eugene for your hard workl
[Vibrant Android Development] ludachez:
i would guess in the overkill kernel yes, since clocks are high and the UV app is not supported, so no UV. If the battery is lasting well i could care less about UV (although that app is really cool) i am excited to try this before i head out to work. Eugene is amazing, pumping out updates and new things to try. i can only imagine the progress that will be made in a month from now.
[Vibrant Android Development] ilaf0106:
How do you delete battery stats.bin?
[Vibrant Android Development] jzero88:
Dont want to hog up the post but why wouldnt i be getting a huge battery life increase with a13 kernel?
[Vibrant Android Development] hanbaoquan15:
Because the kernel has some bugs.
[Vibrant Android Development] frankencat:
I would like to try this latest kernel but I can't download from the site in the OP. Can someone attach or host it somewhere else? Thanks.
[Vibrant Android Development] t1h5ta3:
quick tutorial for those who still get shutdown before 3.0v

http://xdaforums.com/showthread.php?p=9382853#post9382853
[Vibrant Android Development] ludachez:
Installed AOverkill and 5 minutes into it got the sleep of death. FROZE the UV app, setcpu working at 1.3/100, tried to put it to "on demand" but phone immediately froze, went back to conservative. sleep of death.........
[Vibrant Android Development] eugene373:
Remove the mtpx file in system/bin

If you Read the OP you would have known not to use UV App with kernel
[Vibrant Android Development] m00nshake:
Thanks for your efforts, Eugene. I tried to apply the Overkill lagfix and then Setcpu to 1.2 ghz, on demand, but it had the sleep of death issue almost immediately. Just Odin'ed back to unofficial Froyo, and am going to try OC with this kernel and Axura 2.0.5 without any lagfix. Setcpu should work right, and is it better to set 'on demand' or 'conservative'?
[Vibrant Android Development] m00nshake:
Ok I just read on your forums Eugene not to use SetCpu. This may be a dumb question but how do I set OC and the scaling without it?
[Vibrant Android Development] jcc332006:
Eugene MTPX OR MTPD? I went in system bin and did not have mtpx only mtpd. By the way the overkill kernel is awesome. 2500 quadrant with overkill jfs enabled and all tweaks. Also is there a way to delete the voltage app? thanks and great work as usual.
[Vibrant Android Development] eugene373:
Well, I can't say it will work on all Phone's for Starters...

I can say I found the reason for Battery Life Issue's & ondemand should not be used. Stick with conservative, and don't down clocking past 1.2Ghz with SetCPU, as it messes with the Scaling at that Point & will Cause Lock-Ups & Freezes when Going to Sleep.

There's still a Few issue's, but stick with Stock Default Settings of the Kernel you should be fine..

If you Flash the Overkill Kernel,

Remove ( adb shell, rm -r /system/bin/mtpx ) if it has One..

Reset after a Full Charge of Battery Left ( If Using ) & Batterystat.bin

( mtpx, NOT mtpd ).

To remove the UV App, just adb shell & type rm -r /system/app/VoltageControl_1.98b.apk or use Root Explorer and find /system/app/VoltageControl_1.98b.apk and long press & delete.

OC and the scaling is Auto, no need to Touch it... Either the Kernel will Run, or it wont on your Phone.
[Vibrant Android Development] daenigma:
remove mtpx file (it is a file from an older rom and limits the CPU to 1ghz thus causing lockups):

adb shell

rm -r /system/bin/mtpx

Also the Kernel auto adjusts to custom OC/Scaling without external apps...
[Vibrant Android Development] sader2202:
I flash the new kernel and got to a boot loop with lots of can't mount issues. So i had to

odin back to stock.

P.s. im was using axura with a11 kernel and overkill ext4 lagfix
[Vibrant Android Development] rsfaze:
I just had to odin back to jfd after trying to convert to jfs and restore the restore froze.

Fun times :)
[Vibrant Android Development] ilaf0106:
What is battery stat bin?
[Vibrant Android Development] xspeed9190:
Having sleep of death issues at,100mhz...have to clock it to 800 so its stable
[Vibrant Android Development] jzero88:
Wow thats great thanks! Sucks that thays the only way but i do have a meter and will get a bulb.
[Vibrant Android Development] jcc332006:
I'm using this overkill kernel on Axura 2.04 and it's blazing fast. When I first installed Screen froze up, but once I pulled the battery I have had no other issues. Noticing that the battery is alot better with this kernel. I currently have set cpu at 1300_100 conservative and havent had no sleep off death. Getting quadrant of 2500 to 2600. This kernel is wicked!:D
[Vibrant Android Development] eugene373:
That will be Fine... setting on 800 wont Drain the Battery.. I already Addressed this before release as I knew a few can run at 100 Mhz

Read more: http://eb-productions.proboards.com...ction=display&thread=28&page=18#ixzz1697FwfTT
[Vibrant Android Development] firefly6240:
well...

I'm on the new A_OVERKILL Kernel. (I came from A14)

I was hoping to rid myself of the sleep death...

but this one is actually slightly worse for me with that issue.

I got rid of the mtpx file.

and rebooted, without using setcpu, I ran a benchmark to see that it would clock up to 1.3 ghz by itself. (it did very nicely :)

but the second it went to sleep it would'nt come back. (A14 seemed to come back the first couple times)

I tried this a couple of times, with the same result. (sleep death immediately)

so I tried set cpu...

all settings under conservative resulted in sleep death (and of course on demand freezes the phone but we knew that)

so, I'm back to using the same fix as i was using for A14: use set cpu on performance clocked constantly as high as the kernel allows. (in A14: 1.2 ghz, in A_OVERKILL Kernel: 1.3 ghz)

well my phone runs beautifully again :)

no sleep death, and its nice and snappy.

unfortunately I'm stuck on 1.3 ghz now rather than 1.2 lol

maybe I should go back to the kernel that came with Macnut so my CPU doesn't spontaneously combust or something.

although I do have to say, it really does not get any hotter than usual.

it does eat battery, but that's to be expected.

edit: never mind, I just tried 800 - 1300 on set CPU using conservative and its stable so far, maybe it was just a fluke that it was not working before.

awesome :)

edit: sleep death is back... back to super overclock.
[Vibrant Android Development] JeremyNT:
Eugene, is this just because the hardware can't handle less than stock voltage at 1.3GHz? If I were to lower scaling_max_freq to 1GHz would you expect UV to work OK, or is there some other issue?

FWIW I was successfully running with a 25 25 25 25 25 25 UV_mV_table with 1GHz max with this kernel for a while without stability issues. Not sure whether I was just lucky though.
[Vibrant Android Development] bbm21:
Dude this is awsome i love you thank you so much
[Vibrant Android Development] calvinpreston:
i'm having sleep of death all the time with the A_overkill kernel. i removed the voltage control and no setCPU. i don't know what's happening. A14 is better for me. i tried A_overkill because I was hoping i could have better battery life.
[Vibrant Android Development] shortyhp256:
Eugene thank you so much for your work! but there is seriously a problem with the sleep of death. Battery life seemed much improved on this, as it frankly sucked on A14. PLEASE if you could post a quick revision to A14 with the battery life fix from overkill and nothing else as i loved everything from a14 other than the battery life.

THANKS!
[Vibrant Android Development] krntehknik303:
I just ended up disabling the lagfix from A14.. my phone decided to shut itself off and refused to turn on unless I put the charger on the phone and force it into clockwork recovery.. **** was scary!!
[Vibrant Android Development] calvinpreston:
second that motion. thanks.
[Vibrant Android Development] henreeg:
Been there done that. Had to Odin back to stock. Lol thanks though eugene! Still getting the sleep issue on the new kernel. Going to remove the app and mtpx.
[Vibrant Android Development] TunedFish:
Was running Axura 2.0.4 with kernel #66, OCLF and it's Aggressive task killer setting and Strict scheduler. Disabled Lagfix and flashed A_Overkill: everything was running smoothly. Then I tried the OCLF and I got the "sleep of death." So, the question is to those getting the "sleep of death": what, if any, lagfix are you using?
[Vibrant Android Development] henreeg:
A_overkill was running really good. I was stuck at 17% for about 5 hours. Awesome batter life! but took a nap, and had my gf yelling "WHY DON'T YOU PICK UP YOUR PHONE?!?!" lol

the phone was off.

no lag fix... running Axura as well.

What a shame!!! i thought it would work for me. oh well... tested it, loved it, not for me. thanks anyway eugene!
[Vibrant Android Development] JeremyNT:
Well I disabled UV/1GHz cap and now I just got the sleep of death again :(

I'm going to re-enable the clock speed cap from the Voltage Control init script. That seems to be the only way I'm stable with any of these kernels.
[Vibrant Android Development] Jerzeeloon:
It was probably the 100mhz min giving you the sleep death,100Mhz min always made my phone freeze.i wish this kernal had 200mhz min.Ive always been good with that.unfortunatly Im,now stuck at 800mhz min 1.3ghz max.eugene if your reading this please make a 200mhz min version.as I know many people get freeze issues with 100nhz min.
[Vibrant Android Development] NikolaiT:
On the A_OVERKILL kernel, 1.12GHz, is this a mistake, or is it actually 1.12GHz not 1.120GHz (the zero is commonly omitted, examples 1.2GHz=1.20GHz 1.6GHz=1.60GHz, etc.

#apologiesforgrammarnazism
[Vibrant Android Development] eugene373:
That will be Fine... setting on 800 wont Drain the Battery.. I already Addressed this before release as I knew a few can't run at 100 Mhz

No Mistake
[Vibrant Android Development] hnrclothing:
Sorry if this has been said in a ealier post or on a different forum but how do you install the new kernels? I have been looking around the forum for a little and cant figure it out. I am on (ROM)[ODIN] Unofficial TMO 2.2 Froyo ODIN Ready Image * Updated & Final *

Have not really played with any other roms just yet.

Thanks for the help!
[Vibrant Android Development] cashyftw:
How exactly do I oc, I set it too 1.3 in setcpu, and everything works, but when I click home, it freezes...
[Vibrant Android Development] qreffie:
I'm trying your fix now to see if it'll stop the freezing issue for now.

I'm sort of in the same boat as you. I even contemplated going back to A12 which ran beautifully for me except for the boot issue, but I decided to just come back to A_Overkill.

Edit: Froze right away. Looks like my phone wasn't meant to have this kernel.
[Vibrant Android Development] qreffie:
OK, still a bit determined to get A_overkill to work on my phone so I'm going to try reflashing R12 to get the mtpx file back, then reflashing A_overkill and editing the min clock of the mtpx file. And if that doesn't work, then I'm gonna call it quits of the kernel.
[Vibrant Android Development] bbm21:
download the rom and put it onto your sdcard, then download rom manager (free or the paid) and click flash clockworkmod recovery. then click on install rom from sd and chose the zip that you downloaded and put onto your phone
[Vibrant Android Development] firefly6240:
yeah I had it set to 800 min but I have a sneaking suspicion that it hits 100 randomly anyways. it does last longer at 800 min but I still eventually get sleep death.
[Vibrant Android Development] firefly6240:
try it on A13/14 if you want, your phone may handle 1.2 better than 1.3 :)

but if your flashing kernels anyways you might just go back to A12, I might do that myself.
[Vibrant Android Development] JeremyNT:
So using voltage control and capping at 1ghz does the trick. I guess my phone just can't handle the oc.
[Vibrant Android Development] firefly6240:
LOL!! the tags on the bottoms of these threads are Hilarius :-D

mmmm tasty?
[Vibrant Android Development] xspeed9190:
same here man i noticed the exact same thing.. worked with 800 for a few mins then no matter what as soon as it goes to sleep ..never comes back out
[Vibrant Android Development] qreffie:
Ditto for me. On second thought, I'm just going to run something stable for the next few days. I've been flashing and Odining a bit too much the past few days.
[Vibrant Android Development] m00nshake:
I tried all of the tips and tricks that I could find here, various lag fixes, different roms, etc. etc., and still the phone was freezing. I ended up Odin flashing back to stock Froyo then flashing Axura 2.0.5, then A12 kernel, Overkill lagfix with OC, and it is running stable thus far. I'm not going to mess with anything else for a while, leave things as they are.

That being said, I do thank Eugene for all of his hard work and I look forward to any and all of his future releases.

~m00n
[Vibrant Android Development] xspeed9190:
thats my plan right now ..axura is great.. im sure Eugene will figure out why it doesnt work on alot of devices. he also stated a few times he found an area of heavy battery drainage that he is working on so here hoping.
[Vibrant Android Development] :
So far I've been able to to avoid the freezing by using SetCPU. All I did was set the minimum freq to 800 MHZ. It's probably not the best for battery, and is probably not supported by the kernel, but the phone doesn't freeze.

EDIT: Just read all the other posts that addressed this. Please disregard.
[Vibrant Android Development] TunedFish:
LOL! Running a minimum of 800mhz stopped the sleep wake dilema but on the othet end of the spectrum, asphalt 5 freezes at 1300mhz (1200mhz is fine).
[Vibrant Android Development] nanim0n:
wth even setcpu min. at 800mhz i still get the sleep of death
[Vibrant Android Development] FitzMichael:
1.3 mhz and Quadrant only scored 1750 and it went to sleep,going back to 4.2:)
[Vibrant Android Development] takato23:
i'm having a lot of sleep of death too with A14 and Overkill kernels.. i don't know why =(. It can be the 1.2ghz? because i set the processor on 1ghz and freezes too
[Vibrant Android Development] hnrclothing:
Did you mean download the kernel to the sd card? Then follow the steps? I did that and it seemed to unpack the kernel. In the "about phone" "Kernel" what would it show if i loaded the a-overkill correctly?
[Vibrant Android Development] firefly6240:
it wont show different in the about phone, just run a cpu benchmark or see if you have the option of 1300 in set cpu
[Vibrant Android Development] }{Alienz}{:
No-wake freeze EVERY time phone goes to sleep with Overkill Kernel. Sigh. Was worth a shot. Excellent otherwise.
[Vibrant Android Development] takato23:
what are the tweaks on recovery?
[Vibrant Android Development] hnrclothing:
Ok I see. I installed set cpu and had it autodetect speeds, it only showed 1000.
[Vibrant Android Development] hurrpancakes:
What type of lagfixes are supported on the overkill rom?
[Vibrant Android Development] calvinpreston:
trying to flash a_overkill again. how can i know if i'm running 1.3ghz?
[Vibrant Android Development] ludachez:
So im reading a lot of stuff here and get 2 different things, sleep of death, no sleep of death. Is there a way to get rid of it now? thanks so anyone who helps. All the searching ive done is people says yes and no, and different ways to stop it. i tried a lot of things, i didnt give OVERKILL much a chance cause i got the sleep of death quickly but didnt get rid of the UV app and didnt set it at 800/1300. any feedback GREATLY appreciated:)
[Vibrant Android Development] theclarkman:
you might need to make a user profile in setcpu so when it goes to sleep the freq doesnt drop below 200 / try that out
[Vibrant Android Development] cashyftw:
I went back to stock, installed Axura 2.0.5, then the Overkill kernel, didn't install any lagfixes and it seems to be running fine so far, I also have setcpu to 800/1.3ghz i'll try 100/1.3ghz next

Edit: Just set it to 100/1.3ghz and everything is fine, I would advise to go back to stock, then re try :D
[Vibrant Android Development] hanbaoquan15:
Do we have to have SetCPU on this to make it stable?
[Vibrant Android Development] cashyftw:
Not sure, from what I read, it's a YES, and a NO, I'm using it, and everything seems to be fine.
[Vibrant Android Development] aloxotls:
Eugene suggested over on his webpage to remove the mtpx file and not to use setcpu. I would make sure you back the file up first if you want to go back to a different kernel

adb shell

rm -r /system/bin/mtpx

From what I understood is that the kernel does its own scaling and that setcpu and the mtpx file are telling the phone to run, for example, 1.0GHz while the kernel thinks it should be running at 1.3 GHz and then that causes the phone to lock.

Saying all that I tried it on my phone and it stilled locked up but I did use a lot longer before I had a lock up. I have a weak cpu in my phone and it was expected. Maybe for others it may just be the little extra they need to make it stable.
[Vibrant Android Development] hanbaoquan15:
How's the battery life?
[Vibrant Android Development] JeremyNT:
What's extra annoying is that I can't seem to catch the sleep of death when running logcat (although I assume it wouldn't reveal anything anyway since this looks like a hardware lockup).

Disabling the oc with the voltage widget is still working for me though.
[Vibrant Android Development] hnrclothing:
Alright. I tried getting the kernel to work but still cant get it. Benchmark is still at 9xx..

I put the Overkill.pdf on the SD, downloaded rom manager, downloaded flash colockworkmod recovery, booted into recovery, went to reinstall packages, picked Overkill (I had to rename it update.zip to recognize), it seemed to unpack it, then it goes to clockworkmod recovery, then I apply sdcard:update.zip, then I pick it in one of the slots to confirm install, it looks like it unpacks it, then I reboot system.

I guess I am a noob at this way of installing kernels. I used to do it through odin. Can someone tell me something I am doing wrong? Thanks!
[Vibrant Android Development] eugene373:
Stock Kernel Coming in a Few hours at Most, will Need Testers To test Battery Life.. Made a Few Adjustments & Tweaks, but should see great Battery Life COMBO with ULF
[Vibrant Android Development] shep211:
Has the system corruption with ULF code been fixed in A_OVERKILL Kernel?

http://xdaforums.com/showthread.php?t=848471
[Vibrant Android Development] m00nshake:
Can't wait to test it, Eugene. I have faith that you will get this worked out and I and many others greatly appreciate your hard work and dedication. On Thanksgiving day I'm donating to you.

Cheers,

m00n
[Vibrant Android Development] hnrclothing:
I also tried on the OC widget to see if I can get to 1.3 and it will only show upto 1267, but it will never go past 1000, so shows the widger. I try to "set it" to the 1267 then see its still at 1000 on the widget, so I go into the widget again and it is set to 1000 again by itself. This repeats.

Any help why its not loading the kernel? Do I need a different ROM?
[Vibrant Android Development] }{Alienz}{:
Well. To prevent lockups I had to set the Overkill Kernel at 1.0Ghz min and 1.3 Max which KILLS battery like nothing I've ever seen. Left phone at 80% before going to bed...woke up 7 hours later and battery was completely dead from being in standby. I really hope the stock Kernel does not freeze. That would be epic.