yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] antonyvijai:
Thanks for the onix file. I flashed ut after clearing cache and dalvik cache. The boot took longer than usual. Way too longer for me :-) I was losing it but glad that I was patient. It updated well in the end and I checked it using cat /proc/version on terminal emulator as well. Thanks a lot buddy.

Edit: I went to the phone browser to click the "thank you" button but I forgot that I already used my 5. ...sorry
[Captivate Android Development] AReynante:
Lol, glad it worked :) and don't sweat the thanks button. It's all good :)

Also, anyone on this kernel playing cordy from the market? Mine won't run, trying to find the problem
[Captivate Android Development] ryude:
HUEHUEHUEHUE

THAT WAS ONIX-PECTED!11LO!
[Captivate Android Development] jon.groves:
I didn't notice any instability with the script, but my battery life flew away very quickly. I started using 12% every hour. I removed the script and it stored happening.
[Captivate Android Development] jde984:
I've been using this script for a couple days now. I'm UV but not OC. To be honest I haven't really notice much difference in battery, although my usage is so sporadic it's hard for me to get a good feel for that kind of thing. I haven't noticed any issues or affect on performance however.
[Captivate Android Development] xThe Enforcer:
Installing right now on FF 2.7. Heard a lot of good things about this Kernel and can't wait to use it!
[Captivate Android Development] Johnny Paranoid:
Cordy is running just fine for me. OC'd to 1.2Ghz, UV -75mv each step.
[Captivate Android Development] dmshaefe:
I had a charge death last night. Running serendipity 6.03 and the newest 1000 hz kernel of this. Have it overclocked to 1300 and uv to -50 across the board. Hope that helps
[Captivate Android Development] topiratiko:
I have no overclock or uv and had charge and sleep death. My phone is one of the bad batch of imeis but too lazy to flash for warranty etc...now checking app called soft locker to prevent fone from full sleep therefore preventing sleep death....checking batt consumption will post results

Sent from Paragon Blue
[Captivate Android Development] existz:
Im not directing this to anyone special, but to all the lurkers out there ...I've seen this in alot of different threads, if you have issues, please post them here, I usually don't keep up with all the other threads, so if you don't post it here or my irc channel, I wont know about it ...and if I don't know about it, I can't fix it ...simple as that .. and please post more than "it didnt work for me" . Post when it happened, how it happened, if it happened in a previous build or if it just started ...etc..etc.. useful information ..there's tons of people using this kernel without issue, so it might just be something simple causing the problem ..there's over 1000+ downloads per release in this thread alone, not counting the people using it cooked in roms, so with that amount of users and no one posting any issues, I have to assume there is none ..(except for the few that is posted here)
[Captivate Android Development] Johnny Paranoid:
Hear, hear!

Also: So far using the CPU frequency tweaks script I haven't had any problems. OC'd to 1.2Ghz, UV -75mV each step, Optimized memory timings tweak

is

enabled, CPU Performance Threshold tweak

is not

enabled. Other recommended tweaks are enabled. Battery seems to be better as it seems my phone goes into sleep mode quicker and stays there longer, therefore not draining the battery hardly at all while idle. While in use, however, it seems about the same. Also, the new memory management/low memory killer in v2.0.3 seems to be working great! I haven't noticed kswapd0 getting hung up at all! Will test further and report if there is any noticeable change in performance.
[Captivate Android Development] aalh:
well on that note.....

I have been getting sleep death and charge death, I havent posted anything because I wanted to eliminate what causes I could. I havent had SD or COD for a while and it started again last week. I had to reinstall Captivate Keep Alive, which hasnt been on my phone since Jan.

I cant say if it started with the pre-release onix test kernel or one of the later releases, but that is the only change that remains.

I also went through the JK3>KP1>JQ1 route to get 850 enabled on JQ1 last week (it still is on 1900 most of the time but will go to 850 as needed now, guess it's mostly 1900 towers around me)

I am using the regular PU, not PUSE

Settings:

sio

1300,1200,1000,900,800,600,400,200,100

no UC

phone spends almost all it's time in under 600mhz

I did not notice it having a sleepdeath until after I saw it shutdown while charging from usb. Then it started dying every time the screen was off, just like after I got it. Something stopped it for a long time, but now it's back

Any ideas?

**

I just unchecked 900, I remembered reading that having adjacent clocks (800-900 or 900-1000) would give issues, dont know if this applies to 100-200 step as well

we shall see
[Captivate Android Development] topiratiko:
Verdict. Normal usage for me is 2-3% per hour with no use. Using soft lock app, its 3-4% Its a slight increase, but theres no sleep death AND you dont have to deal with the HIDEOUS keep alive status bar icon

Sent from Paragon Blue
[Captivate Android Development] nappent:
When is the last time you have flashed to stock and then to a custom rom/kernel?

I hadn't flashed to stock for about 2+ month because I keep using the same rom (Darky's) and this Onix/suckerpunch kernel. For me it seems like ever time their was a rom or kernel update flashed to my phone it just kept getting slower, and more unstable with random lock-up and restarts. And to note every time I did a flash I would always clear both caches. This week I re-flash to stock and re-flashed the latest rom and Onix kernel 2.0.2. All I can say now is that my phone is working 100% better, battery is lasting a good 25% longer, and no stability issues. I think after a point of rom and kernel updates we likely need to wipe the phone and start fresh. Keep in mind 6-8 months ago that is what we used to do every time their was a update. It might be a good practice to start up again, but maybe on a 1-2 month cycle.

Just a theory of mine and I really have no hard evidence other than my own experience.
[Captivate Android Development] WirelessMike:
I'm sorry, existz, I am one of those who have posted issues in another forum but not this one.

I know you said it's not directed at anyone in particular, just thought I'd own up as one of the guilty (I'm sure there are more). I can certainly understand your frustration. There can't be much you can do or say to address issues if the issues aren't brought to your attention.

That said, I was hesitant to describe my issue here, as I thought with the many complimentary remarks that it was probably just my phone or my failure to try all the general fixes I've read about on these forums.

My issue began with 2.0.2, when I experienced my first "charge death" with this phone. I upgraded the day after you posted the update, and I had let the battery completely drain (didn't meant to go under 5%, it just happened) the following evening, and in the morning, I pulled it off the charger with "100% full" showing on my batt displays (which is a little weird, it typically says 97% to 98%). The display froze, so I pressed power a couple more times and the next thing I know, there's the boot screen.

I figure it's just a one-time thing, so the next day and evening, I charge overnight again (but not fully drained as before), and all's well in the morning, but I have to manually toggle the wifi. I use wifi buddy (a beta app), so I didn't think too much of it.

Fast forward another day to the release of 2.0.3, which I installed. Now, by the way, I'm getting PHENOMENAL battery uptime (ok, maybe not "phenomenal" but pretty darn good by anyone's standard). That evening, I charge overnight. The next morning, all's well and I take it off with 97%, but since I know it will go to 100% full (have done it many times) if I just bump it a little, I put it back on the charger. Now when I go to take it off, there's just the black screen with the home buttons lit. I take it off and after a couple presses of the power, it boots.

After booting, I again had to manually turn on wifi (but this might really just be wifi buddy not playing well with a new kernel-- perhaps if I wipe its cache...).

I figure for now, I'll just sit on speedmod (even though I LOVE the extended uptime your kernel gives me, and I like your version of cwm better, as well as your custom boot screen-- kudos on all these cool features) until another update of onix comes out. I intend to troll the forum regularly to see if my issues, which appear to be shared by a few here, start disappearing so I can come back to what I think is an exceptional kernel you've designed.

Oh, btw--

I've been using your 100hz kernel with default settings (no oc/uv).
[Captivate Android Development] LNJ:
existz...the experimental battery saver script that's placed in etc/inid.d slows down the phone a little.

I'm not talking about calls or sms but the UI and launching apps in general.

I don't talk kon the phone much but am constantly on it to the point that it needs to be re-charged by around 6pm so I'm certain of it.

Once the script is removed, everything is back to normal.

It's also probably because I'm running 1.4Ghz all day long so I notice the slow down a little more.

It's not majorly slow...probably 1/2 a sec to 1 sec slower launching stuff!
[Captivate Android Development] H3llstorm:
I'm pretty sure he said that the battery-saver script would impact performance. I'm just too lazy to search the thread. :cool:
[Captivate Android Development] Soccer_Dad:
If you want issues, I'll give you issues!

Well, not really. It's not like I'll ever run the phone this way in "user mode". I was fooling around with single state activity in Voltage control 3, seeing how the phone reacts at 100Mhz alone (slow, but actually usable for the most part), and I went to 200Mhz, but was called away in the middle of testing. When I came back the phone had gone to sleep, and with no 100Mhz to fall back to, it was dead. Nothing would bring it back - no key press, no power hold, no 3 button, etc. After a battery pull, everything was all hunky-dory (since I never changed the boot settings).

Just posting this as a data point. It's not like it needs to be fixed. I am interested in why this sleep death requires a battery pull instead of a simple power-button restart.
[Captivate Android Development] LNJ:
I'm pretty sure he also said to report any observations. And since everyone using it is only saying how it helped on battery life, nobody seems to be noticing the slowdown like I have.

It's feedback and not a complaint.
[Captivate Android Development] Soccer_Dad:
That script changes the rate the processor gets up to speed by a factor of 50. Instead of ramping up to top speed in one-tenth of a second, it takes five seconds, roughly. So if you are tend to go from quiet to active states often, it will take a while for it to get going with the new setting. If you tend to be either asleep or playing CPU intensive games, the new setting will work better.
[Captivate Android Development] aalh:
I did it this flash to Phoenix Ultimate (not SE)

I dont usually either, but I decided it was time to clear it out.

besides, the problem did not start when I flashed PU, I ran that fine with SP#55-59

I also do not restore system data other than wifi networks

and the app data I restore is very selective
[Captivate Android Development] existz:
See if it happends at stock voltages/frequencies, also if your using the cpu performance threshold tweak in recovery, disable it during testing... Heres probably whats going on...

With SP59, the threshold values were the same as the default now, which keeps the cpu at lower speeds, it doesnt scale up as fast..but it will scale down quicker.. (so your higher frequencies, 1200-1300, didnt have to be as stable)..so if your using the performance threshold tweak, it will keep it at higher frequencies more often, it will scale higher quicker, but wont scale down as quick..spending more time at higher steps...so your higher frequencies didnt need to be as stable as before...so try setting everything to 0mV in VC and enable only stock frequencies (100,200,400,800, 1000) then see if it happends..setting everything to stock frequencies/voltages will be the easiest way to pinpoint whats causing it..
[Captivate Android Development] pizz0wn3d:
Just copied over the cpu freq script to test it out. Going to run it with stock oc/uv for a couple of days and see how it goes. I'll post results.

On another note, I turned off the "autokiller memory optimizer" App and flashed 2.0.3 yesterday, and since then the kswapd0 process has been behaving quite well. Idk if it's the kernel fix or turning off the app, but something is working really well do I'm just going to uninstall the autokiller app and let the kernel do it's magic without anything else interfering.

Herp derp Captivate XDA app.
[Captivate Android Development] aalh:
DONE:

as well as disabling the tweak in recovery

I will let you know as soon as it is at a full charge

I have removed the no-sleep apps I had tried, just to be sure and give this a clean shake
[Captivate Android Development] gibson3659:
I read somewhere that the cappy wakes up at 800, so it makes sense that it would not wake up if 800 is disabled. Also try holding pwr and vol-up instead of pulling the battery.
[Captivate Android Development] ninjuh:
I'm having one small problem with this kernel, something that happens with any rom I apply it to.

When I unlock my screen it feels laggy, but once I open something to get it going its smooth until I lock the screen again.

Anyone?
[Captivate Android Development] existz:
Try enabling the cpu performance threshold tweak in recovery, I use battery saving settings by default and it could be from the default threshold values I use.. With default, the cpu has to be on average of 90% load before it scales up ..so when its idel with screen off, it could cause it to lag when turning the screen on .. Also make sure you don't have too many states enabled. ..if there's alot of states the cpu has to scale, it will cause lag also ..keep it close to a step every 200mhz...

Also try to do a level 2 clear after boot to kill apps that's not used..don't do it alot or it will hurt battery life, as the apps in use or used will start right back up..I usually do it just once every boot...or use a program that let's you select what's ran on boot..alot of things get started that you might never use..it will free up some ram and might help with speed/battery also..but doing it often can hurt it
[Captivate Android Development] harpo1:
What is the kswapd0 process and how do I check it?
[Captivate Android Development] existz:
Linux uses kswapd for virtual memory management such that pages (processes) that have been recently accessed are kept in memory and less active pages are paged out to disk.
[Captivate Android Development] Delicate Donut:
This kernal has been nothing but awesome for me excellent work existz! Only issue I have is the kswapd0 issue but then again I'm still on 2.0.1. I shall update to the newest version tonight! Also when I apply the cpu threshold tweak from the cwm the framerate seems to go down is this normal?
[Captivate Android Development] harpo1:
So is this the 0 bar I see under networks usage in battery history? If so it's always blue all the way across.
[Captivate Android Development] halfsoul:
I disagree. I did my voltage testing with only one state enabled from 100 to 1200, one at a time, with reboots in between to make the state changes effective.

Also, using temp+cpuv2 widget clock is always at 1000 after unlock (I'm back on speedmod currently).
[Captivate Android Development] LNJ:
I think 800mhz is right. Cause 100, 800 and 1400 are 85% of the frequencies used.
[Captivate Android Development] aalh:
Hey existz,

your advice stopped the sleep death so far

I set clock and volt to stock

removed threshhold tweak in recovery

and it hasnt shut down since, a couple hours now

one strange thing, after changing the threshold setting and rebooting, I let it sit at the lock screen on the charger to finish charging

it shut off while connected to ac and the battery was about 85%, according to juiceplotter.

I let it charge to full while off then turned it on and it has been fine, we shall see if it sleeps too deep tonight

********************

It made it till midnight and 58% then it shut off (about 6-7hrs)

what now?
[Captivate Android Development] abee_13:
So just making sure. I can use the cpu performance tweak from recovery and the script?

Sent from my cappy UC'd 900mhz and UV'd running di11is rom/ Onix kernel
[Captivate Android Development] fractaline:
I had to ask that one too, few pages back.....

Yes you can. I ended up disabling the tweak before applying the script so I can't comment on how they mix.

But I think it's a valid experiment . Think I'll try soon.

I'm curious how your uc is treating you?

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] dajeoo:
How do you Oc, i installed the kernel but i don't see any options in recovery to OC. Do i need an app or something? Thanks guys...
[Captivate Android Development] harpo1:
Get a program called voltage control from the market.
[Captivate Android Development] johan8:
You better read existz #1 post, and also the links inside his post.........

Whatever OC/UV capability kernel you are using, OC is NOT tune inside recovery.

Use VoltageControl app, set the clock speed and UnderVoltage value.

In fact, that app is already in his #1 post.

How can't you see it !??
[Captivate Android Development] dajeoo:
Thanks guys
[Captivate Android Development] nappent:
existz,

Can we really control what clock speed the phone boots up in? I thought I read that it boots at 1000Mhz with no UV to prevent problems. Then when the phone is up the Voltage Control boot settings are applied.

Is this correct or completely wrong?
[Captivate Android Development] dajeoo:
I found it...
[Captivate Android Development] crusecontrl:
kernel Panic

So my battery dropped below 10% and when I looked at my phone I had a crazy Kernel Panic upload mode screen. Is that caused by my UV/OC settings or something else?
[Captivate Android Development] existz:
Alot of different things can cause it ...an unstable oc/uv being one of them, try lowering your oc/uv some.. best thing to do is put your oc/uv settings back to stock and if it doesnt do it then, then adjust your settings accordingly
[Captivate Android Development] crusecontrl:
Yeah I had just bumped them up after running for two days solid and stable....I will bump them back to where I had them and see if that fixes it.....Thanks for the quick answer existz
[Captivate Android Development] Dino.:
First, I really want to thank existz for his AWESOME kernel tweaks! Seriously I don't want to go to 2.3.# because you haven't made a rom for it yet!! lol!

Seriously, keep up the good work!

So of stock is at 20000, is it possible for me to test possibly 60000? can I manually edit the .sh file to do so? And if so which number do I change, the one in quotes, or the one after the #? Thanks again!
[Captivate Android Development] johan8:
Try lower the UV, or just move/delete your /etc/init.d/S_volt_scheduler and test it.

For me, previously my lowest UV was -125mV in 100~400Mhz when using SP#59.

However I have COD and phone freeze / reboot problem when keep it in Onix.

So now I lower it to -100mV, it seems ok now.

Try back to stock value, means that no uv/oc, then tune and find your working value.
[Captivate Android Development] k2ham:
First of all, thanks for all the work on this kernel. It is very nice.

I am having issues with the wifi though similar to the others. I have to manually toggle it on more times than not and I have also had to restore my wifi settings several times with tibu. For some reason they just disappear.

I'm running the stock 100mhz kernel on FireFly 2.7.

Thanks
[Captivate Android Development] abee_13:
Uc is doing pretty well, no lag or anything that Ive noticed.

Sent from my cappy UC'd 900mhz and UV'd running di11is rom/ Onix kernel
[Captivate Android Development] fractaline:
Cool, might just give it a whirl...

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] aalh:
all stock clock and sleep death still

I first mentioned this here

http://xdaforums.com/showpost.php?p=12508138&postcount=3423

it shut off over night, still shows 51% battery

I put it on charger now to see if it COD's
[Captivate Android Development] bclark:
Exists I had a sleep death last night. Wasn't UV as I have been stable with my settings for 2 days or so and have done overnight charging. I did just check though and I had accidentally checked CPU threshold tweak rather than memory timing.
[Captivate Android Development] existz:
That's probably why, with the tweak off the cpu will not scale up as quick and scale down faster, spending more time at lower frequencies, so higher frequencies are not stressed as much (meaning higher frequencies don't have to be as stable) ..with the cpu threshold tweak on, it scales higher quicker and doesn't scale down as quick, spending more time at higher frequencies ..so your higher steps will probably need adjusted...either disable the tweak, or readjust your oc/uv settings
[Captivate Android Development] disellusional:
exist do you know why the wifi bug still exists (pressing wifi on doesn't always turn on, have to manually go to settings to do so)
[Captivate Android Development] goodolsen:
What kernel and ROM are you using? Wifi worked fine for me from SP #58- Onix 2.0.3.
[Captivate Android Development] nappent:
Which modem are you using?
[Captivate Android Development] Sqb:
Hey existz just wanted to say thanks. After a little tweaking to my u/v settings everything seems to be real stable. My son even played cordy for over 45 min until I made him give it back. Thanks for all the hard work and I'm sure most problems people are having are o/c u/v related. Sorry to hear people are hating on other threads. at least you know you are on to something that is making noise across the board. Great job!

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] disellusional:
i've tried jpg jq and now on jvk

i believe it happened on SP too but i dont remember.
[Captivate Android Development] aalh:
I had a COD in the car this morning

that makes a COD on USB, AC, and AUTO

and a sleepdeath during the day

sleepdeath does not seem as frequent with the threshold tweak off, but it still happens

stock clock & V

BLN off

noatime on

VM tweak on

mem tweak on

no voodoo screen tweaks on

ext4+ext4nj no loops

what next Existz???
[Captivate Android Development] sthodupunuri:
does this have voodoo color?
[Captivate Android Development] topiratiko:
QUESTION. I have soft locker installed on my phone which prevents full sleep which in turns prevents sleep death. Question is can i undervolt ONLY 100 mhz too -100 mv or is that too much of a voltage jump when scaling up mhz??? I figure itll save battery since cpu WILL be "humming" along @ 100 mhz when screen off. Waddayathink?

Sent from Paragon Blue
[Captivate Android Development] existz:
It just depends if your phone can handle it.. I currently have 100 set to -150mv..and I dont use any apps to keep it from sleeping, never had a problem with charge/sleep death.. but it all just depends how your phone handles it, try it and see...if it causes instability then set it back up...

heres my current oc/uv settings, these are perfectly stable for me, no sleep/charge death...but I doubt these will work for most ppl, so test accordingly ..might cause instability for you..

100 (-150mV)

200 (-125mV)

400 (-125mV)

600 (-100mV)

800 (-100mV)

900 (-100mV)

1000 (-100mV)
[Captivate Android Development] topiratiko:
Thanks existz. Ill try and see.

Sent from Paragon Blue