yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] thresherhorn:
Just wanted to report, since it's release on April 8th, I received my first SD since it's update (received several on 2.0.3/0.4).

3 tweaks enabled:

IOSCHED

KERNELVM

MEMTIMING

OC/UV fairly heavily:

1300.... -25

1200.... -50

1000.... -100

800..... -100

600..... -100

400..... -100

200.... -125

100..... -150

Sporadic use nets a battery life anywhere from 16- 38 hours during testing.

Average % drained per hour= ~1.89%

Had these settings the whole time.

Just another case report.

--Side question (FIXED): Wanted to try out speedmod's new-ish K13E, tried to instal via Onix Recovery and received error message:

"Can't open /mnt/..../speedmod.zip

(bad)

Installation aborted"

Just wondered if a) this was due to trying to install a different kernel on top of Onix Recovery or b) just a bad download (will be testing this with a re-download shortly).

Short Answer....

B. Bad Download, everything worked fine after a redownload

That is all, have a nice day.
[Captivate Android Development] aalh:
you answered your own question

I dont UV anymore, it gives my phone fits

I have the same OC as you (no 600)

when I UV (even a little bit) I get SD

I am in the proccess of checking each CWM tweak to see what else causes SD for me (I take about 24hrs per tweak to check for SD's)
[Captivate Android Development] RichMD:
kernel panic on 2 different phones

I loaded Continuum 4 with Onix v2.0.5 on my and my wife's I897. We have never seen a kernel panic on either phone previously and now see if often (always when charging). I OC'd my phone to 1.2Ghz and left my wife's with no OC - 1G max. I have UC'd both however, but with conservative settings below. I read that possibly this is caused by the 600 (which I did use on both) or the 900hz settings. After disabling the 600hz, I ran stability test for 1 hour and 50 minutes on my wife's phone - no problems. However, she saw a kernel panic this morning - it had been charging all night. Any ideas? I don't want to go back to speedmod if I can fix this.

My wife's settings with the latest kernel panic:

100 Mhz: -100 > 850mv

200: -100 > 850mv

400: -75 > 975mv

800: -75 > 1125mv

1000: -75 > 1200mv

I just changed the 100 and 200 to (-75) in case that helps avoid it. Any other ideas? I searched the continuum thread for "kernel panic" and couldn't find a hit.
[Captivate Android Development] neubauej:
This looks like too much UV to me...

Try backing it down to -50 or so across the board, and see if that helps.
[Captivate Android Development] topiratiko:
Im no pro....but im running WAY more uv and have never had kernel panic. All phones behave different i know but im not so sure its your uv settings. You can try another rom if you wanna flash one and see if it continues. Also, ive had charge death on this kernel but wiped battery stats 3 days ago and ive yet to have one since. Not saying its the answer, but worth a shot?

Sent from Paragon Optimized
[Captivate Android Development] RichMD:
Thanks to both of you. I'm wondering if there is any consistent result when you OC too much or UV too much. I've seen the phone lock up solid when either of those happen and holding power and vol. up reboots it. The kernel panic is new so I wondered if that only happens when something else is wrong such as not having full support for 600Mhz or something with tweaks,etc. The result is just very different than anything I saw before.
[Captivate Android Development] TRusselo:
no kernel panics for me no SD

100 - 125

200 - 100

600 - 100

800 - 100

1000 - 100

Running PERFECT, Stable, all settings thouroughly tested with stability test and neocore, using the mini overclocking guide

at each speed step

.
[Captivate Android Development] RichMD:
Thanks,

You obviously wanted to make a point of "at each speed step" but can you explain? Do you mean that you run the stability test and neocore after you undervolt at 100 (leaving everything else at zero) and then change 200 and run them again, etc? I've never read up on it but I have "assumed" that stability test only tests the high CPU (overclocking) - is that incorrect? I've never been too sure what settings would work best at the low speeds (100, 200, etc) but maybe I need to review the mini overclocking guide again.
[Captivate Android Development] shane87:
Yeah, if you read the mini overclocking guide, it explains how to do it. What you do is, you select the highest speed you want to use, for example I run a max of 1400mhz, so I select 1400mhz in the Max CPU Limit dropbox, and go to the States tab and unselect all states except 1400mhz. Then I set a moderate uv, maybe -50, for 1400mhz, and run stability tests. If it is stable, then I up the uv to -75 and test again, until I find the uv that causes stability problems. When I find stability problems, I go back one step in uv, for example from -100mv to -75mv, and repeat the process for each voltage. Of course, this kind of testing takes quite some time, especially on the lower frequencies because they move so slow. Anyway, I hope this explains it in a way you can understand it.
[Captivate Android Development] TRusselo:
well thats what the guide tells you to do...

I took it a step farther..

I did that at EACH max clock limit.

for 600 800 1000 1200 and 1300. however i dont overclock unless N64oid emulating

i did that whole guide over and over for each step

(except the really low ones)

to make sure and verrify i have stability at each step,

the tests crank you up to 100% and test there, this will make sure your in-between steps are stable.

for all normal use i leave the clock max at 1000, so i only posted those voltages, overclocking is dangerous!
[Captivate Android Development] RichMD:
Thanks to both of you. I should have thought of setting the max clock lower and run the stability test if I wanted to check UV at a certain frequency. :o
[Captivate Android Development] shane87:
Yeah. I guess I wasn't clear in my post. I also lower the max clock setting for each step. When I test 1400mhz, I set max clock to 1400, for 1200 I set max clock to 1200, etc. I try to keep my max clock at the highest(or only)frequency I have selected. I have found that setting max clock different from the highest enabled state may cause issues, at least for me. For example, leaving max clock at 1400 but only selecting 1000mhz, 800mhz, 600mhz, 400mhz, and 200mhz caused several glitches/crashes that cleared up after setting max clock to the highest enabled state. I am thinking about adding some code to Voltage Control EX that will change the max clock string to the highest selected state when the States drawer is closed. I haven't decided yet.
[Captivate Android Development] TRusselo:
hey shane, i always leave my max at 1000

but always have 1120 and 1300 selected,

no problems at all. when i go to game with n64 i set max clock up to 1300, apply for now and game! when im done just back to 1000,

only 1 sleep death ever, on onix 2.0.3, no glitches no problems at all

thats why i would flip your idea and have max clock only show enabled states....
[Captivate Android Development] shane87:
I see what you are saying. I may set it up so that it only shows enabled states, and when you exit the states drawer, it will default to the highest enabled state, but then you can still change it of course. So for example, if you go in and enable 1400 in the states drawer, it will select 1400 in the max clock, and if you want to limit to 1000, or any other enabled state, you would just open the max state drop down and select it. The only reason I mention defaulting it to the highest selected state is that sometimes I forget to change my max clock when I disable the higher states, and then I will realize it about the time I apply or save as boot settings, and then have to change it, and re apply or save again. Its just an idea though, haven't had much time to work on it in a couple days, hopefuly I will get some time tomorrow, but no promises.

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] leetnoobie:
lol damn

can someone please help? im trying to flash this kernel using CWM but it's just stuck at 0%

edit: nvm i just reflashed the continuum rom that contained it
[Captivate Android Development] existz:
For those waiting on a gingerbread version, me and ytt3r have made some progress... working UV, few upstream fixes..etc etc...changes can be found here https://github.com/existz/linux_gt-i9000-gb/commits/gingerbread-dev ... ytt3r is currently working on adding 1200 oc, I have a few things I want to do also (smartass/interactive governors, SLQB, color fix..etc)... still dont have a working cwm ..but hopefully we can get it fixed soon, and hopefully a release.. If anyone decides to build from my repo, you will need to use Hardcores initramfs from his gingerbread speedmod, im having issues building with Xcals, you can grab Hardcores from his sources in i9000 forum.
[Captivate Android Development] aalh:
SD's are back with a vengeance

I have had 4 since I got up this morning and found it off

I have NO tweaks enabled

NO mem-timing,cputhresh, or SVolt scripts

I have neither VC nor VC-EX installed

I have never used SetCPU, ever

the only thing different than when I went almost a week without SD's is I installed a themed market from 00.ante

I have used his markets for a long time, went 2months with no SD, a themed market could cause this?
[Captivate Android Development] H3llstorm:
Reverted to Onix 2.0.3 last weekend. 1200 enabled, 600 & 900 disabled, no U/V. No freezes, lock-ups or "deaths" either. :cool:
[Captivate Android Development] shane87:
Dang, sorry to hear that the sleep deaths are back. By any chance, was you phone bought before November 18th, 2010? I read on the Cognition thread that Captivates purchased before that date had a hardware error that may attribute to sleep deaths. Not sure about that, though, as I purchased mine in Febuary of this year, and I have never had a sleep death issue.

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] aalh:
I got it this year

I bought my first one 12/20/2010 (build 1012)

I exchanged it 12days later because it shutdown all the time

I got the one I have now (1007) and it started shutting down too

after a couple rom flashes it quit having SD's for a while and I thought they were gone, till Onix was released and I started having them again

I wonder if anyone that has sent their phone off to be fixed due to SD still has SD's once they get their phone back
[Captivate Android Development] FocuseD83:
Great job exists! Keep up the good work. Can't wait for your JVB kernel to drop! Already getting the best battery life by far on Continuum, and its only a beta! It's a daily driver beta, lol... I can't imagine where my battery will be if I can UV, and how good my N64 Emulator will be with an OC! -boner-
[Captivate Android Development] johan8:
I am using Onix-2011-04-13 till now,

no SD COD at all.

Mine is batch 1008.
[Captivate Android Development] TRusselo:
i have only had 1 sleep death onix 2.0.3... ever

2.0.5 is running great still
[Captivate Android Development] nelsonw:
Hi i'm totally new to this... sorry for dumb question:

What means

Onix-2.x.x-OC.zip =CWM flashable,OC/UV,Kernel HZ=128 <-- this

Onix-2.x.x-OC-1000hz.zip = CWM flashable,OC/UV,Kernel HZ=1000 <-- and this means NO OC? or what?

Thanks a lot!
[Captivate Android Development] TRusselo:
its the kernel hz not the processor speed. processor speed is in mhz.

the 1000 hz is more "snappier" feeling but will use more power.

both come stock 1000 mhz speed, OverclockABLE with Voltage Control EX

they both say OC/UV (over clock under volt ABLE)
[Captivate Android Development] aalh:
What TRusselo said, for more detail read post #2

the kernel is well documented, that is a common question
[Captivate Android Development] sixstringsg:
A better explanation than above is in the second post of the thread.

Sent from my CM7 powered captivate

Edit: Looks like someone beat me to it. Oh well.
[Captivate Android Development] TRusselo:
yeah there it is...

by the way also check out the onix idiot guide in my sig~
[Captivate Android Development] nelsonw:
Wich tweak? Thanks!

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] H3llstorm:
Hey existz, anything interesting in Voodoo sound v8?

http://xdaforums.com/showthread.php?t=806195&page=216

Just wonderin' :cool:
[Captivate Android Development] aalh:
the read ahead tweak in CWM (recovery)

but

I started having SD's again with it disabled

I am relocating the source of my SD's.....I hope
[Captivate Android Development] TRusselo:
have you considered a hardware problem?
[Captivate Android Development] aalh:
Yes, since the day I bought it:p

but I have yet to be convinced that living without a phone for weeks is worth it to try and stop this, so I have yet to pursue wnty repair

I want to know that NO ONE has had a recurrence of problems ever, after getting the cappy back from Samsung

I havent said it out loud, but I have started thinking of my phone as a CRAPtivate.....poor thing
[Captivate Android Development] bclark:
Hey existz, I don't know if it helps at all but ficeto from the darky team has a working voodoo kernel for the cappy, cwm and all.

http://www.darkyrom.com/community/index.php?threads/kernel-dark-core-2-x-ginger-kernel.2072/

Edit: BTW it is very smooth but needs xcals home button fix to work perfectly.
[Captivate Android Development] TRusselo:
well if you return to ATT you will get a refurb, the inside board SHOULD be newer than the date under the battery,

with samsung warranty you have a BETTER chance of getting a new phone,

EITHER way, there is no guarantee, some people had random shutdown issues, (which may be what you are getting) , got a new phone, then the GPS sucked! other people had Crappy GPS, then got better GPS with worse battery life.

Refurbs are a gamble.

wait the extra time and go through Samsung if you can.

and if it is a harware problem, maybe you shouldnt be asking so much of the software Devs....
[Captivate Android Development] shane87:
Hmm, I have been watching the sleep death issue closely, and it seems to me that those who are having sleep death/charge death issues seem to have hardware build numbers that fall in the 1006 to 1010 range. I have seen reports of a few people with builds outside this range, but most fall into this range. If I am not mistaken, you are running 1007, right? I have never had any sleep death/charge death issues, and I have build 1101. I don't know if there is that big of a difference between the hardware build numbers, but it is worth looking into.

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] kickmys:
the kernel is working very stable, awesome, the best OC kernel i tried. However there is one little problem, my back key turned into home key, doesn't anyone has the same problem and do know how to fix that? thanks!
[Captivate Android Development] existz:
There was missing files in xcals initramfs, got that fixed and now have working cwm ...its finally getting there

Sent from my i897
[Captivate Android Development] kickmys:
Ops, i just found another issue on my i9000. i turned the screen off and it couldn't on again, the screen just stay black and i can only pull out the battery, how can i fix this? i have wipe cache and dalvik cache, what can i do? i am using it with darky 9.5. thanks
[Captivate Android Development] existz:
This is a captivate kernel :P

Sent from my i897
[Captivate Android Development] M1nur:
Is anyone else having issues with the video camera?

When I try to use it, it say "camera failed".

Using onix 2.0.5 with precision v4.0
[Captivate Android Development] TRusselo:
im build 10.11

as stated before only one sd ever
[Captivate Android Development] goodolsen:
Mine is 1008 and I've only had one SD as well. It seems more phone specific than build specific.

Right now I'm UC'd and UV'd and have no issues with SD or CD.
[Captivate Android Development] stinkynoon:
I have build 1101, and haven't had any SDs or CDs, though I've only been running this kernel for a few days. My previous Captivate was build 1012, and it had none either with DG's 4.3 Cog kernel or eXistZ's (version 7).
[Captivate Android Development] aalh:
chill dude

who is asking anything, I am reporting feedback

being a good user and supporting the community with information
[Captivate Android Development] aalh:
I had a 1012 to start with and it had SD's for me

now on a 1007:rolleyes:
[Captivate Android Development] TRusselo:
i didnt mean anything bad, i just have been reading the past few days, (very busy days for the devs) and i was just saying maybe its time to give up on thinking its software related.
[Captivate Android Development] meadhros:
Have a 1007 cappy. No SDs or CDs. Ever. Been running it since Aug. 2010. And none of the crazy haptic. Been using existz kernels since december. Some of these issues people have are random and may never be solvable. At least they are not I-??&$&s.
[Captivate Android Development] fractaline:
I have a 1008 and a 1006 both running onix for a month our two now , both oc/uv 1.2.

I had one sd with my daily driver, the 1008, from, I believe, too much uv..... None on the 1006, even when I let it sit in idle for 9 days! !

I regularly charge them over night and also keep plugged in while using mobile ap ...

Seems that if there is a tendency for certain builds to have these issues, not all will.

Like it or not , our phones are individuals......

Thanks existz for your tireless support.......

Sent from me to you.

Firefly + onix = :)
[Captivate Android Development] WirelessMike:
I agree. AT&T released a statement in which they identify the models that MAY experience this issue, but that doesn't mean they all definitely will, and it certainly doesn't mean that sleep death is always hardware-related.

I had a 1007 that definitely had the sd issue. I traded it in under warranty for a 1011 and have only had the issue twice. It occurred once after I flashed the onix 2.0.1 kernel, and again after I flashed the onix 2.0.3 kernel.

Now in the time I've had this phone, I've used cognition and firefly. Can't remember what kernel I had with Cognition 3, but I started on speedmod with firefly, then tried onix, had the sd's, then went back to speedmod several weeks ago and haven't had an sd since.

You'd have a hard time convincing me that the issue (in my case, anyway) is hardware related, but as you so aptly put it, "our phones are individuals..."

That said, I have yet to try 2.0.5, but I'm looking forward to flashing it later this weeks, perhaps. I do have it on the sd card.
[Captivate Android Development] aalh:
48hrs SD free

I have VC-EX installed again (1.3)

no tweaks enabled

Cleared bat stats

I think my SD's are caused by a combination of settings.

I say this because I can do something like enable read ahead and get SD's, but simply disabling that tweak does not end the SD's.

But I got rid of the SD's once I disable all tweaks, uninstall VC and/or VC-EX, and clear cache(s) and stats.With plenty of reboots sprinkled in.

No Single change stops the SD's for me, but it incorrectly seemed one thing was causing it so that is what I looked for to end them. And why I was unsuccessful

I will update when I have more data on this, it will take a while to cover the permutations
[Captivate Android Development] topiratiko:
Your efforts r appreciated

Sent from Paragon Optimized
[Captivate Android Development] neubauej:
I had frequent fc's and cd's when i ran this kernel at 1.3, tested stable. Very. It would even sorta run at 1.4, But was very choppy, would hang often, just didnt feel smooth. This was with most tweaks enabled, and uv -50 at most.

Now, i switched to 1.2, and all problems are gone. Butter smooth and no issues.

Excellent battery life too strangely.

In both cases i had 200, 400, 600, 800, 1000 enabled at -50 for all but 1000 which was at -25.

1200 or 1300 only enabled additionally at -50.

Is the code for 1300 funky?

Thanks for your hard work!
[Captivate Android Development] Jep56:
I had a 1006, and it took about 4 months before it developed sd on a daily basis, up until then, maybe once a week, then it became 3 or 4 times per day, by the end. I traded it for a refurb model in January and received a 1007 build. No problems with this one!
[Captivate Android Development] thresherhorn:
So I'm coming back to you Onix,

Was getting horrible battery life with Speemod for some odd reason.

--- 10 minutes of use netted me -15% battery life.

--- "Over-night" test where I just let her sit there was 3x the battery loss compared to Onix... all this after plenty of cycles to ensure the battery was set.

... Granted, speedmod was solid as a rock.

Want my ability to oc/uv back (dunno why, it's not like I use something that requires extra juice... just makes my warm and fuzzies feel warm and fuzzy)... incidentally, fired up voltage control and set my UVs to HALF of what I did prior and instantly received a "welcome back" reboot :P still trying to figure that one out.

Went into Onix Recovery and disabled BLN (tho I love this little function, I want to see how much it's affecting my battery life... if it's not night and day I'll likely re-enable it)

But I tell ya, it feels good to be back :P
[Captivate Android Development] TRusselo:
i just got off a 60 hour use on my extended battery, bln on, wifi on....
[Captivate Android Development] aalh:
both cpuspy and VCEX show no time spent in Deep Sleep after hours of the phone sitting with the screen off and no calls

This is making the battery life less yjan optimal

I see no odd apps or services running

any ideas?

how would I find what is keeping my phone from sleeping?
[Captivate Android Development] shane87:
Hmm, that's very odd. It almost seems as though you have something similar to captivate keepalive running. I mean, the good news is, you can't experience sleep death if the phone never goes into sleep, but at the same time, it is killing your battery. I can't think of anything that would keep your phone from going into deep sleep, unless your wifi policy is set to never sleep? I am not sure if that would even cause it. I am pretty sure that bln will not cause the cpu to stay active, although I have not really paid a whole lot of attention to my time in states info recently. I mainly use tis to pick what states are seeing the most use, so I can make sure to have optimal states enabled. Now that my phone is running smoothly, I have no reason to check tis, other than after an update to vcex to make sure evrything is showing up. I may look into this over the next few nights, since I am working on my gb control freak app and I don't want to flash gb just yet, want to make sure that all of the kinks are ironed out of vcex first!! Or as best as I can 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] TRusselo:
my wifi policy is set to never and also use bln, goes to sleep just fine.

@aalh

when was the last time you tried flashing back to stock and only reinstalling the bare essentials manually to see if it still happens? as you said last page it may be hardware problems. and the clock is ticking on your 1 year warranty.
[Captivate Android Development] shane87:
On a side note, aalh, I do remember seeing something mentioned by the android resources saying that the function I use to poll real time since startup can be reset at anytime. Since both vcex and cpuspy calculate deep sleep time by subtracting the time cpu has been active from the real time since last boot, having the real time reset would cause both to show 0 seconds deep sleep. I am not 100% if that would cause it, but it may be the case. I never thought much about the real time reset, since there isn't much I could do about it anyway, that is handled by acore, the android core, I do believe.

ROM: Cognition v4.3

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

Modem: I9000 tljl3

HW Build Number: 1101