yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Yea usually its just a script in /etc/init.d/ ...just remove the script and it will default 512 ...
[Captivate Android Development] markmunsch:
I am getting slightly better battery life, but I too am having WEIRD battery drains, phone acts fine and gets 12+hrs during battery calibration cycles, but after about 2-3 days my phone has these crazy drains, like 40-50% in an hour, no crazy processes running, nothing changed on the phone. I'm trying to test out if it's the modem (UGKC1) or if it's Onix. This only started after Onix 2.04, but was about the same time I started trying out the new modem. Hopefully I can get this figured out, testing today to see if it's the kernel. I like the speed of Onix but I need more than 12 hours of battery life out of my phone.
[Captivate Android Development] disellusional:
I get this also.

Please let me know of your results. I'm thinking of switching to speedmod/paragon kernel to see how it does
[Captivate Android Development] goodolsen:
I'm running KC1 and 2.0.5 without that problem. Check your battery usage and see if your cell standby has the 50% without signal issue.
[Captivate Android Development] markmunsch:
The 50% without signal bug isn't causing this. I have had that bug twice while running KC1, but the last 2 days it has not been the culprit causing this, either that or battery usage and spare parts are both lying to me.

EDIT: It's weird, I've checked spare parts and battery usage, GPS isn't running, Wifi sleep policy set to when screen is off, and nothing is running out of control. I haven't installed a new app in over a week, so it can't be anything different on the phone. My guesses are the modem or kernel, and I don't think the modem can cause the processor to freak out, because I too have had my phone sitting in my pocket on standby, and pull it out to find it 110+ degrees. And it doesn't do this for awhile, it has started after about 2-3 days of running Onix, after the battery is calibrate. Also, I've noticed some weird charge stats, my phone can be "dead" and cut itself off, I plug it into the charger for 5 minutes and it says it's at 51%. It's strange, I don't know what's going on...I may end up flashing back to stock and redoing everything.

And sorry existz, I'm not blaming you by any means, just posting to see if we can figure this out between the community since it seems it's not just me.
[Captivate Android Development] existz:
I know hardcore made a post awhile back about the battery percentage being off depending if charger is plugged in or not when powering on the phone... everytime I power on with charger connected it will throw my battery calibration off...causing higher battery drain...make sure this isn't the problem... I can get 30-40+ hours with moderate/heavy use with Onix..

http://xdaforums.com/showthread.php?t=908718
[Captivate Android Development] psloan:
I have observed this. make sure you unplug when rebooting too.
[Captivate Android Development] markmunsch:
Wow, maybe this is the issue, because my phone did die about 2-3 days ago and I plugged it in, let it charge for a few minutes and then i turned it on, while still plugged in. Never thought that could cause an issue, guess it's like the do not flash with USB plugged in thing. I'll test this, cause I like Onix for the features and speed, and will report back results. I guess that this issue would remain until a reboot or re-calibration?
[Captivate Android Development] johan8:
Sounds like you worry about the conflict.

Just del the script in /etc/init.d then it will goto default 512
[Captivate Android Development] shane87:
Hmm, I just noticed something odd. Nothing I am worried about, just odd. I opened vc ex and opened my states enabled tab to check time in states. I noticed that, even though it is disabled, my cpu is spending more time at 100mhz than any other state. I opened cpu spy to double check and saw the same thing, 100mhz having more time than any other state, besides deep sleep, and 100mhz NOT listed as an unused state. I checked my time in states file and it shows the same. So I checked my states enabled file, thinking maybe vc ex was broken and not disabling 100mhz even though it is not selected. According to states enabled file, 100mhz IS disabled. Is it impossible to disable this state?

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Android Development] cucumbersmell:
I experienced the same thing yesterday. Because of that, I ended up re-enabling 100mhz so I could at least UV it. Am still curious to know the answer though.
[Captivate Android Development] kodos96:
So I'm sure this question has already been asked and answered before, but there's too much thread history for me to read through it all....

What's the rationale for offering this kernel in 128hz and 1000hz versions? (as opposed to the 250 and 500hz versions of speedmod, which onix is based on). And is there a general consensus about how the two versions perform relative to each other?
[Captivate Android Development] H3llstorm:
Is "trying to avoid aggravation/re-flashing" the same thing as "worried"? No, hence I'm not worried, though I appreciate your worrying about my emotional well-being.

Good thing you clarified that. Some people seem easily confused. :cool:
[Captivate Android Development] ridethelight:
This doesnt work. I get "Usage: mount [-r] [-w] [-o options] [-t type] device directory" Funny how someone says it worked when if you actually test it, it yells at you

I'm having problems with /system/media being set to rw and not showing boot or shutdown animation, no matter what commands I throw at it it will not show them. Sorry if this is off topic, just dont like people throwing around false stuff
[Captivate Android Development] surfed.tk:
Just want to add that I am experiencing the same, 100 step can not be disabled.

Sent from my Samsung captivate.
[Captivate Android Development] topiratiko:
I want to add also that 800 cannot be disabled

Sent from Paragon Optimized
[Captivate Android Development] existz:
800 disables fine for me, verified with time in state ...haven't tried messing with 100 yet
[Captivate Android Development] Delicate Donut:
Also the cpu threshold doesn't stick in the voltage control app ex after boot. Can this be fixed?
[Captivate Android Development] harpo1:
Did you disable it in recovery first before you set it in Voltage Control EX?
[Captivate Android Development] Delicate Donut:
I hadn't even enabled it In recovery cause I know it doesn't work if is enabled
[Captivate Android Development] harpo1:
Did you apply it for now or for boot in Voltage control. No sure of the exact wording because I'm not running it anymore.
[Captivate Android Development] Delicate Donut:
Boot. If anything I'll just enable through clockwork
[Captivate Android Development] aalh:
dunno if this should be here or the VC EX thread, but I see shane here a lot so ....

I get sleepdeaths when I choose performance under threshold

Onix 2.0.5

It runs fine on battery saver

This is an FYI, it is not a problem for me since the phone seems to run great on battery saver for my uses,and the bat life is increasing
[Captivate Android Development] fractaline:
I was intrigued by shane 87's thoughts on waking faster without the 100 state....

Sure enough about 24 hours later 100 is the second most used state, after deep sleep.

Hmmmm.

Sent from my fire fly'n liberated captivate

{onix enhanced}
[Captivate Android Development] shane87:
What version of VC EX are you running? The 1.01b version has a bug in the way it saves cpu threshold settings for boot. It saves them as cpuT_.sh in /etc/init.d, but I found that for whatever reason the script is not run at boot. In VC EX 1.10b I added the settings to the S_volt_scheduler file, and it sticks fine for me.

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Android Development] shane87:
Hmm, I have not tested much on performance threshold settings, just enough to ensure they stick at boot. I run battery saver myself. And for future reference, it is easier for me to keep track of bugs if they are reported in the VC EX thread, :p. Although the cpu thresh settings apply equally to the kernel, so its all good.

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Android Development] GGXtreme:
About the battery drain being mentioned: I usually do power my phone on while it's plugged in, but that's because it's always on off the charger and I usually don't plug it in until it dies (well, only recently because it dies much faster than usual). I am using JL3 modem, but I haven't had the 50% cell standby problem ever since starting fresh with Serendipity.

Would you have any idea about what could cause a phone to overheat? It seems to be related to my issue: every time I turn my phone on and notice that a lot of battery has drained in a short time, the phone is very hot. As for the kernel panics, I'm not sure if it's related, but I used to get the 'POWER RESET or UNKNOWN UPLOAD MODE' screen a while back whenever I let my battery charge to full and left it on the charger, or unplugged it and got a sleep death while it was still full. I also remember the phone getting very warm whenever that happened.
[Captivate Android Development] VFO:
I am not sure what has happened but for some reason my VC settings are not saving. I hit the apply to boot settings button and it says it is saving to the file but when I exit out of VC and open it back up the settings are all set to default with no OC or UV. Would anyone have any suggestions?
[Captivate Android Development] topiratiko:
Apply for now and THEN save to boot

Sent from Paragon Optimized
[Captivate Android Development] VFO:
That worked! Thanks! I am suprised I never had that happened before now. Oh well now I know what to do.:o
[Captivate Android Development] 13_:
You could also try> uninstall VC, reboot to recovery, wipe cache, waipe dalvik, reboot, reinstall VC , set states and voltages. see if they stick. I had an issue with VC once, similar to this, after switching kernels and this fixed it.
[Captivate Android Development] topiratiko:
No problem man.

Sent from Paragon Optimized
[Captivate Android Development] rajendra82:
When a battery discharges, it always heats up. It heats up even more if it is used while charging. The phone itself is not causing the overheating. What is the build number of your phone? I have a build 1007, and back when I was on perception, at some random time my phone would lose all connection to the cell tower, and then the battery would drop like a rock, as the radio kept hunting for a signal. IIRC, I was on TLJL3 modem when this happened. Due to this reason, I moved away from i9000 based ROMs for a while, but am now back on Continuum, and have UGKC1 modem. I only lose connection if I charge the phone 100% while it is on. Otherwise the connection on both 850 and 1900 bands is rock solid, and battery has not ever dropped rapidly.
[Captivate Android Development] geokilla:
I can confirm that the following OC/UV states gave me Kernel Panic Mode problems: 100,200,400,600,900,1120

Currently OCing and UVing and I'm stable with everyday usage. Haven't tried stability tests yet. Here are the states I'm using: 100,200,400,600,800,1000,1200.

I think I should disable one, but not sure which to disable..
[Captivate Android Development] Delicate Donut:
Try disabling 600 that's how I have it 100,200,400,800,1000,1200 and it is stable and smooth. Then again every phone is different
[Captivate Android Development] GGXtreme:
Hmm, that makes sense. My phone is a build 1009. It's weird, because my battery info screen never shows a time without signal (and I never notice my signal dropping). In fact, JL3 is the only modem that doesn't constantly drop my signal. I've tried KC1, KP1, JK4, JK3, and JL2; I've always had to stick with JL3 on any ROM I've used, across all 3 Captivates I've owned (builds 1009 and 1010). I live in NYC if that makes a difference, and I've never had a dropped call or poor signal with JL3.

I am going to try to determine if these weird side-effects of charging while on or powering on while plugged in are occurring on my phone.

Also, I don't know if this has anything to do with the kernel or Voodoo Sound 7 specifically, but I've noticed two things:

1. My audio tends to skip/crackle/distort randomly when using headphones, using any music player, while the screen is off.

2. My volume control with Voodoo is very unresponsive compared to older versions of Voodoo Sound/kernels. It takes a few seconds for the volume to change sometimes and it will sometimes randomly change 1dB or up to 6dB with one press instead of the normal 2dB.

Edit: I disabled the CPU performance threshold tweak in recovery to see if it has any effect. I've noticed immediately that the phone seems much more sluggish. Scrolling through menus or the app drawer now takes forever =/
[Captivate Android Development] Shammyh:
Any word on the sleep-of-death issues?

I still get it every once in a while with Onix (though I didn't have it for most of the older Suckerpunch builds).

Anything in particular I can look for to try to narrow down the problem? I really like this kernel, but as I rely on my phone as an alarm clock, sleep of deaths are pretty much a deal-breaker for me. It seems to happen somewhat randomly, but of course, that's just because I can't tell what's causing it... :)

PS: I have a build 1007 phone, pretty stable overclocker and undervolter, but my problems occur even when I don't undervolt or overclock.
[Captivate Android Development] TRusselo:
ive only had the sleep death once. ever. a few builds ago..

also i would disable the 100 mhz step. a few times i have turned the screen on shortly after 2 am (around 2:10) when it does its TiBu backup @ 2 , and its taking 10 minutes to do, until i turn on the screen then zips right through. I find 100mhz is just to slow to be useful. im sure taking 10 minutes to do a 30 second job isnt saving much power . probably why samsung's minimum speed was 250mhz...
[Captivate Android Development] LNJ:
Try using Captivate Keep Alive from market for now till it gets resolved.

There has been no nightly build the past 2 days but the Github has been busy. I believe is is testing a 2.6.35 or something!
[Captivate Android Development] shane87:
I'm not sure, but I believe disabling the 100mhz state has no effect. I have had 100mhz disabled for some time now, and yet 100mhz is the state that my phone spends the most time in, besides deep sleep, of course. I reenabled my 100mhz band so I can uv it, since it gets used anyway.

ROM: Cognition v4.3

Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix

Modem: I9000 tljl3

HW Build Number: 1101
[Captivate Android Development] H3llstorm:
I was driving with my GPS on and my car charger plugged into my phone when suddenly my phone shut down. I guess this is "charge death"?
[Captivate Android Development] surfed.tk:
I wish this would be possible as I use my phone as an media player via bluetooth in my car and when data goes on or off or if the phone looses/gain reception i get audio glitches... if i could force the phone to stay in 200mhz or above i think things would be smoother...
[Captivate Android Development] jon.groves:
I was using google navigation yesterday with the phone plugged in, and I lost 10% in 40 minutes. That was with the phone plugged in! Any ideas?
[Captivate Android Development] surfed.tk:
Does not surprise me. Car chargers give of around 500mA and i am sure the phone uses more than that with the screen / gps / data and heavy cpu calculations for google nav all running at the same time. But i could be wrong....
[Captivate Android Development] TRusselo:
possibly i just noticed/ tried disabling 100 this morning.. and i am no expert on how the kernel works/ power states ect.
[Captivate Android Development] Shammyh:
Tried the same thing, and "time_in_states" shows that 100 MHz is still being used. It's definitely something in the modifications between Speedmod and Onix, but I'm not sure what... :confused:
[Captivate Android Development] eliminat:
With 128hz I've had no problems. Tried to switch to 1000hz and started getting lockups and charging deaths. Back to 128hz and the problems disappeared. No uv/oc.
[Captivate Android Development] Shammyh:
Hmm, I did switch back to 1000hz from the 100/128hz versions not too long ago. Perhaps that will help.

Thanks for the advice!
[Captivate Android Development] kdot25:
question

i want to use the kernal as stock.... is there any procedure or when i flash it set to default?
[Captivate Android Development] Sqb:
Just flash it straight over then. Its set up stock for battery I believe. No 6 & 9 cpu either. Go into tweaks for extras. A few are on already. Can't remember which. Its too deep into friday night. Sorry

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] sjavvaji:
ITS FASTER...(or at least tweaked so it runs faster by hardcore)
[Captivate Android Development] nosenuggets45:
I'm assuming it is an UV related issue, but after putting my phone on the charger at about 2%,, I woke up to the Kernel Panic Mode screen. Fixed it with a simple battery pull. My UV settings were -120, -100, -100, -75, -50, -25 (100mhz-1280mhz). Should I try giving it a bit more juice? I assume that's the issue.

Just tried charging up again to do the battery recalibration. Went from 95%-99% then went into Kernel Panic Mode again. I'm going to have to trying charging without any UV settings.
[Captivate Android Development] sf1120:
Woke up to a sleep death this morning.Phone was not plugged in.Uv settings -75,-75,-75,-100,-100,-100 cfq scheduler(1120-100).I'll up the voltage a bit to see if it still happens.
[Captivate Android Development] existz:
Which version?
[Captivate Android Development] capita:
Got my first incident of charge death this morning. 125, 100, 100, 100, 75, 50. Interestingly I had been running this kernel at these voltages since it came out with no issues up until I changed the scheduler from noop to cfq last night before bed. Could this issue of charge death be scheduler related?
[Captivate Android Development] LimaI896:
I didn't get a charge death this morning.

So far 1-1.
[Captivate Android Development] existz:
I've seen it happen on both noop and cfq schedulers
[Captivate Android Development] nosenuggets45:
I'm running the 1.28ghz 500mhz version. Also tried Voltage App 3.0 (instead of 3a) and still have the issue. For now I'm just going to to UV it until this gets sorted.
[Captivate Android Development] Auridran:
If anything you should be saying "for now I'm just going to OC until this gets sorted", because I'm pretty sure it is the undervolting causing the issue.

I've had a total of two sleep deaths and one charge death. Sleep death seems to cause crazy drain on the battery, too. I was at 84% battery after 9 and a half hours of heavy usage, and when I went to bed and woke up a few hours later after the sleep death had happened, I rebooted my phone and was at 40%.

I'm using #27 100Hz and am not overclocking.
[Captivate Android Development] sjavvaji:
yea...one of my sleep deaths just happened at the wrong time...first day of cfq...i have a scheduled backup on tibu...it ended up corrupting backups and installed apps...good thing i had a backup of stuff from yesterday...i did a fresh flash to make sure it didnt turn anything off...for now, im gonna leave the tibu schedule off...for clarification...i am only getting charge death (not sleep death) with build #27 1280 500hz using these settings (highest to lowest) 75, 125, 125, 125, 125, 125
[Captivate Android Development] sjavvaji:
any date/changelog for the next release u would like to share? :D
[Captivate Android Development] existz:
Ive been working on the charge death issue constantly, its about the only thing ive gotten done, ive been putting test builds out for some testers, once they report back that charge death is gone, ill open it up to more testers to verify... but after the charge death issue is fixed, im going to work on an all in one 1200/1280 version.
[Captivate Android Development] matt310:
Great kernel. However, like Speedmod, the brightness is just too low when it's set on auto. Was was the reason these settings started to be messed around with...were people complaining that the auto brightness settings of the stock rom were too bright?
[Captivate Android Development] LimaI896:
In a dark room on stock brightness its blinding lol as well too dim outside. Much better with the brightfix. It should still go to the right brightness based on the lighting in you are in.
[Captivate Android Development] tietherope:
However if you don't use automatic brightness and you used to manually set it to the lowest yourself, it is now a lot lower. I'm not even sure where to set it to match what it used to be.
[Captivate Android Development] sjavvaji:
would it be difficult to include higher overclocks such as 1.4ghz and 1.44ghz into that mix?
[Captivate Android Development] existz:
I might do an all in one but I don't know yet, since most phones can't handle 1400 iono if I will include it to not

My original intentions was just to make something with excellent battery life and the option to UV, something quick, stable and great battery right out of the box. Since most phones can't do 1400 and jumping the volts up to handle it will be cutting away from that. The 1280 version wasn't even intended on, so more than likley ill just do a 1200/1280 version together. Im not wanting to spend most of my time working on making this faster, as 1120 w/ 100hz to me is the perfect combo of battery/performance, and if its not, then there's the 1280 version. Im wanting to improve battery way more than what it already is, plus getting it 100% stable.
[Captivate Android Development] mkr14:
The stock settings are a bit excessive. The brightfix reigns this in and helps with battery life.
[Captivate Android Development] sjavvaji:
i see where you are coming from...yea...i use 1280 because i can still get way more than a day's battery life off of it while have it pretty damn fast...i don't intend to use 1400mhz unless it can comfortably get through a day...i would just toggle it for those times when im using a psx emulator or some heavy flash application...whenever you have some free time without another idea on how to make this kernel better...see if u can add it after all the charge death fixes, wifi fixes, voodoo sound v3+x's...thanks
[Captivate Android Development] existz:
I put the psx users into consideration when thinking about higher speeds, I know you guys can benefit from it. Who knows though, I may end up using raspdeeps v300 oc code, which is up to 1400mhz, I've been testing a few charge death fixes with no luck, I've pretty much redone the oc code, if that doesn't fix it I will try the v300 patch, which if it works then I killed 2 birds with 1 stone, higher oc and charge death. I wish GB would get back to me so I knew exactly what he done. But ill know by tomorrow if my fixes worked, if not ill try the v300
[Captivate Android Development] aalh:
I started having sleep death again. I disabled the read ahead tweak in cwm and they seem to have stopped.. They did not happen til I enabled it.

Sent from your Id using XDAPremium
[Captivate Android Development] tazman171:
Even with the car charger plugged in you have to consider how much power the phone is using for the screen, GPS, wifi (if use wifi networks is selected), bluetooth, etc.

My phone doesn't discharge but it doesn't charge neither. With wifi on (I never use it for GPS) my phone will discharge while plugged into the Samsung Car dock or the after market car charger I have. With it off it merely maintains a level. That's with bluetooth on, gps on, wifi and extra sensors off. :cool:
[Captivate Android Development] eliminat:
While it's slow, plugged into my car charger my phone actually does charge. over an hour it'll charge about 13%.