yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ninjuh:
Clear cache, dalvik, wipe permissions, cleanup your SD, get rid of old app folders & clean up as much as u can(makes it easier to isolate the issue). Then go through ALL of your settings, 1..by..1. Check EVERYTHING including wifi settings, display, sound, accounts and sync, etc,. Finally reboot your phone & see what happens. If you're still experiencing issues, I can guarantee its a bad flash, or a bad app. Good luck.

Try turning off all location based settings such as GPS also... Get rid of grooveip unless you really need it too...Hope this helps.
[Captivate Android Development] voldomart13:
How did they devs fix the android OS bug here in the cappy builds. I still have mine running CM9 and android OS runs at around 6-8%, but on my new I777 running CM9 android OS can run from 50-70%. I know I'm on the I777 now but Id'e just like to know how it got fixed here.
[Captivate Android Development] johnnyrichter:
Will try all that.

This is a wifi-only phone that utilizes GrooveIP for incoming/outgoing calls at home so I don't burn up my minutes on my main phone. I also use it for FB and GMail when away from home and in wifi hotspots.
[Captivate Android Development] CheesyNutz:
What random shut downs smooth as butter where

From apple to android I've been there
[Captivate Android Development] account4me2:
No luck. Still got a sleep death. It was a good idea though, thanks. Think overvolting any more would do the trick?

Also I overvolted both the ARM and the INT voltages - is that a problem?

Keep us updated. :)

Also, if it's compatible with your life, it would be cool if you did a full wipe, reflashed a *nightly and gapps, installed virtually no apps and changed no settings, and ran the phone for a few days to definitively prove whether it's a ROM problem or not.
[Captivate Android Development] azunino:
It's not a ROM problem. I've been updating cm9 since April almost every day and I've wiped just once (the first time I installed). I also tried several kernels, and so far no problems. Besides, I've been running cm9 with /data on the external sd, which is not the standard way by any means. I have approx 80 apps /games installed and >10 themes (and downloading more right now).
[Captivate Android Development] johnnyrichter:
Haven't suffered any shut-offs since uninstalling titanium pro and that pool game.

Just to be safe I removed the GO task manager, although I did like it because it doesn't kill system processes. It only kills user processes and side processes started by apps that like to stay open after the app is closed. The cool thing about it was that I could lock certain user processes so hitting the sweep button didn't kill them.

I know for sure that I'm not running the latest gapps so I'll get the newest one on the internalSD when I get around to moving over the latest nightly.

I always do a stock flash-back > easyroot to 7.0a > wipe data//wipe caches before doing a new ROM install, except if I'm updating from one nightly to the next. So leftover data shouldn't be an issue otherwise it'd be an issue for many others.

I'll give it a few days and if there's no problems I'll go back to Icy Glitch and my 200/1200MHz overclock.

---------- Post added at 11:38 PM ---------- Previous post was at 10:49 PM ----------

Anyone else having a problem with Android Commander not connecting with CM9 installed? I made sure to enable debugging and that extra option that allows data/adb via debug(an option I've never seen editable on any other ROM) and no matter what I choose AC just won't see the phone. I have some important db files I need to put back on the phone.
[Captivate Android Development] Katze Pavilion:
Recently, I've not followed the thread frequently. I've just updated from 10/7 build to 16/7 build and missing Gapps, but all Gapps icons still display in the menu, so I touch on the icon but can't access the apps. I have to install Gapps again. :D
[Captivate Android Development] johnnyrichter:
Both Android Commander and Droid Explorer fail to see my phone. It seems as if USB debugging in CM9 doesn't work for me. The phone says it's in debug mode but I don't think it actually is. This worked fine on KK4 and Legend5.
[Captivate Android Development] ThreeofNine:
Did you pull the notifications drawer down and touch the "USB connected" then in the next window "Turn on USB storage" ? Just asking since usb connection isn't automatic.
[Captivate Android Development] shane87:
Usb debugging is automatic, as long as usb debugging is enabled. To the person having problems with Android Commander, does it require root access through usb debugging? I have never used Android Commander, but if it requires root access through usb debugging, that could be your problem. By default, usb debugging does NOT have root access. To enable root access for usb, go to settings > developer settings > root access and select apps and adb.
[Captivate Android Development] nkrick:
Something else to check, did you install the Nexus S drivers? For various reasons, when you use CM on a Galaxy S 1 device (i9000, i897, etc), you need to use the Nexus S driver instead of the Samsung drive for your device.
[Captivate Android Development] johnnyrichter:
I did make sure that USB debugging was enabled and that root access was applied to apps and adb, rather than just apps which is the default setting. KK4 and L5 ROM worked fine, just had to enable USB debugging.

I did not know about this Nexus driver thing. With the Captivate driver my phone charges via USB and USB mass storage works fine. Does that mean I didn't/don't need that Nexus driver or is it still necessary for root adb access?
[Captivate Android Development] azunino:
This applies to all SGS phones:

http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Frequently_Asked_Questions

Besides, this thread contains lots of q&a about cm9 that may help you solve the problems you've been experiencing with cm9: http://xdaforums.com/showthread.php?t=1367586
[Captivate Android Development] johnnyrichter:
I checked that first link and there's a Q&A about not being able to adb in to the phone and they mention needing the Nexus driver, but the link they supply is 404ing. Any current legit/safe place to get that from?
[Captivate Android Development] azunino:
The same link minus "%7C":

http://developer.android.com/sdk/win-usb.html
[Captivate Android Development] johnnyrichter:
That seems to have worked, although both ADB programs are finitely more sluggish than they were before on my last ROM. The app folder I had to restore to my phone also didn't seem to work, when I try to run the app I get an error that it can't find data even though the folder is exactly where it belongs. I've done this folder restore before and it worked fine all those other times. May need to go back to L5 ROM or stock since basic USB debugging/adb access doesn't seem to work right. :\
[Captivate Android Development] shane87:
Well, as far as them being sluggish, slow usb transfers is a known issue for cm9. As far as the app folder you restored, it may be looking for the data in the wrong place, since cm9 uses a separate partition, /datadata, instead of /data/data. I know that I use sqlite explorer, and if I open sqlite explorer and click on an app name to view databases, it says "no databases found," even though I can open root explorer, navigate to /datadata/<appname>/database/ and click on the db file, and sqlite explorer opens it properly.
[Captivate Android Development] rocketcuse:
I am now seeing random sleep deaths since 7/16. I have saw a couple post pointing to a Titanium backup update. I believe this might be the issue. I removed TB last night and so far no sleep deaths. Obviously need to test a few more days.

If you have TB, try removing, see what happens.
[Captivate Android Development] Snorchblapp:
I have TB and have not had a single sleep death. Been flashing CM9 since 05/24.
[Captivate Android Development] Primus76:
Anyone have a copy of gapps kicking around? Mine is corrupt on my sd card and looks like goo.im is under too heavy of a load to get it from there. Latest flash impacted my google apps and the /datadata move script was causing horrible lag. Apparently the only way to revert the /datadata move is to wipe/reset so no time like the present since nothing was really working. Had the latest CM and my old GAPPS but that is showing bad :(.

Thanks
[Captivate Android Development] johnnyrichter:
I removed it yesterday and the phone didn't turn off last night while I was asleep, first time for that. I did have my alarm set, though, which I've never used before. I'll see how it goes tonight just to be sure.

http://goo.im/gapps looks to be working for me. If it's not working for you then try using a different browser to access the page.
[Captivate Android Development] Primus76:
I can get to the page now but when I try to download 0429 it says the server is too busy, tried from chrome, firefox on system and 2 different phones.

I checked the back up I had made on my home server and the gapps i had there was listed as 0 bytes so looks like mine has been corrupted for a bit.
[Captivate Android Development] ThreeofNine:
Here's the one from 2012-04-29 https://dl.dropbox.com/u/26095738/CM9/gapps-ics-20120429-signed.zip
[Captivate Android Development] nkrick:
I can't be sure since your sleep death may be caused by something different than the problems people have had in the past, but, past reports of sleep death have included people upset that their phone alarm did not wake them up. Using that as anecdotal evidence, it is unlikely that having the alarm set made any difference unless your problem is different than past problems.

Also, consider thanking the people who helped you get ADB working.
[Captivate Android Development] Primus76:
Thank you Thank you!
[Captivate Android Development] johnnyrichter:
After removing Titanium and two games the phone seems to be fine. I switched to Glitch and had a few sleep-deaths, switched back and it hasn't shut off since. So it looks like Titanium and Glitch both cause that problem.

I thought I thanked them yesterday but I'll check again to be sure.
[Captivate Android Development] nkrick:
I don't know why Titanium would cause issues, but sleep deaths can definitely be kernel related.

If you do some research on old threads, you'll find that AT&T/Samsung had an internal document back in ~October of 2010 instructing AT&T stores to replace Captivates with "sleep death" problems due to a hardware problem. Then, in ~December of 2010 a firmware update was released that resolved this issue. Several people (myself included) have interpreted this to mean that in certain Captivates there is a hardware problem (likely too low of voltage for the specific CPU in that device) that was fixed by a workaround (probably an increase in the default voltage which can be done in the kernel). This is why the two common recommendations to resolve sleep death problems are to increase the minimum clockspeed to 200 Mhz and to increase the voltage by 50mv. In most cases I have seen reported, using 1 or both of these techniques works to "fix" the sleep death issue.

Sleep death also tends to be a much rarer problem on Samsung based ROMs because most of them use repackaged Samsung kernels, or kernels compiled directly from Samsung sources (with a few tweaks/additions). These kernels would include whatever workarounds Samsung put in the Dec 2010 Firmware update that "fixed" the problem.
[Captivate Android Development] johnnyrichter:
Thanks for the info, I had no idea about that issue being known by Samsung and ATT. All I know about this phone is that it's a Rev.02 and that it was completely up to date before I first rooted/ROM'd it a few weeks ago. Never had sleep-deaths until CM9 and only TB/Glitch seem to cause it. When I get a chance I'll try out Glitch again and see about doing that voltage bump...do I need to bump voltages across the board, min freq only, max only, or min+max? I'd much rather use Glitch and that voltage bump may be what I need.
[Captivate Android Development] nkrick:
You can experiment with different settings, but the sleep death seems to happen only when idle, so only the idle clockspeeds/voltages need to be adjusted. Most people first try making the minimum clock speed 200 Mhz, and if that works, they stop. If that does not work, I have seen some people try bumping the voltage at 200 Mhz and I have seen other people try setting the min clock speed to 400 Mhz. Personally, I'd try bumping the voltage at the low clock speeds before increasing to 400 Mhz.

I am lucky, I have a 1007 REV0.4 (July 2010 mfg date) that does not have any sleep death problems. Some people have assumed that only phones manufactured before ~Nov 2010 have the sleep death problem, but I don't know there is any evidence to support that. While yields on the Hummingbird processor may have increased causing less CPU's to be impacted by low voltage issues, Samsung's workaround in the firmware fix likely would have made it such that new phones are less likely to be impacted because they shipped with the newer firmware.
[Captivate Android Development] anshoo:
Hi all

I need your help. Cappy is my little ones phone that I am running cm on.

Since the last day, whenever I lock the phone, the screen stays off no matter what I do. I have disabled lock screen also but it didn't help. The screen is on after reboot but as soon as it gets locked, the display fails to come back up.

Please help me..
[Captivate Android Development] shane87:
Sounds like you have the same problem I do: a stuck power button. Go to settings > display and at the very bottom there is a check box that says "wake with volume rockers." Check that box and use the volume keys to wake the phone instead of the power key. You can also add a "go to sleep" button to the notification pull down: settings > system > notification drawer, make sure the checkbox for "show power widget" is checked, then click "widget buttons" and add a checkmark beside "go to sleep." Now you can wake the phone using the volume keys, and pull down the notification bar and press the "go to sleep" button to turn the screen off.
[Captivate Android Development] CptTwinkie:
Do you have daily backups scheduled in titanium? I'm kind of thinking it may be related to the backup starting while the phone is idle. If you can somehow confirm this it may be information that the developer can use to fix the problem.

Sent from my Galaxy S3 [AT&T][CM9]
[Captivate Android Development] Ajfink:
I don't suppose anyone is working on this anymore to resolve WPA/WPA2 PSK Wifi authentication issues....

Besides that, the nightlies for a long time have been absolutely superb. Here's hoping once the Nexus S source drops it will help expedite any sticking issues.
[Captivate Android Development] johnnyrichter:
No daily backups.

In fact, at one point yesterday the sleep deaths returned. I tried setting the idle MHz to 400 but that didn't help. I also couldn't change the voltage with the baked-in kernel so I switched to glitch and upped the idle voltage by 25. No more shut-offs yet.
[Captivate Android Development] nkrick:
Looks like CM9 RC2 is coming up soon :fingers-crossed: : https://github.com/CyanogenMod/android_vendor_cm/commit/a1c18a5b2907e7b66dcdce1c02b4567f24482e93

---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------

Hopefully adjusting the voltage makes it stable for you. Most recommendations I have seen call for increasing the voltage by 50, so if 25 is not enough, try a little more.
[Captivate Android Development] wavemaster00:
How to get CWM on Captivate with 2.3.5 and root

Allright, I am dumbfounded by the last step of these simple instructions:

First time flashing ICS to your Captivate (or coming from another ROM)?

Root your device and install ClockworkMod Recovery.

How do I get CWM on a Captivate that is rooted and has the latest Kies update 2.3.5

Any suggestions please?

TIA

Robert
[Captivate Android Development] nkrick:
The top stickied thread has links to download kernels with CWM recovery. The easiest thing to do is download any 1-click that contains CWM. If you have odin and are familiar with now to use it, you can also download any of the non 1-click packages and use it to install a CWM enabled kernel. It is always safest to use a package that does not contain bootloaders (without bootloaders). Here is a link to the thread: http://xdaforums.com/showthread.php?t=1300843

Edit: Try the "full update guide" from the Cyanogenmod wiki, it has a lot more information and step by step instructions: http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
[Captivate Android Development] johnnyrichter:
Bumping the voltage up 25 on idle seems to have worked.
[Captivate Android Development] account4me2:
I'd just like to reinforce in the minds of readers that this means: Titanium Backup is not related to the sleep deaths (as you would expect), despite johnnyrichter's previous posts. He was on the THS kernel.

As far as my own experience, I think that raising the minimum clock speed to 200mHz is useful, as is raising the 200mHz voltage by 50mV. During the 3-4 days that I had those both done simultaneously, I only had 1 sleep death, and it's possible I'm actually just imagining that one. Thank you to those who suggested these settings! :)

After a few days of stability with the above settings, I noticed slightly worsened battery life (as you'd expect), and so I experimented with lowering the min clock speed to 100mHz but raising the 100mHz voltages (by 50mV), and soon noticed a sleep death (although strangely and perhaps notably it wasn't the normal kind where all I have to do to power the phone back on is push the power button - I actually had to hold up, down, *and* power for 10 seconds, i.e. the typical reboot sequence).
[Captivate Android Development] igorgomez:
wifi issue on nightly 17-07-2012

Hello everybody!

After updating to the nightly 17 I had for the first time since the first installation of ICS, problems with wifi on and off. This morning my phone, which was 60% at 2:30 am (hours that I slept), dawned stuck (6:00 am), with the lockscreen turned on and connected to my wifi network, but without responding to commands. I removed the battery, put back, but he did not turn on. I thought I could have bricked my device, but when plug in the notebook it began to load from zero, showing me the battery was 60% to 0% in 3.5 hours. I dont know if it has some correlation, but I use the Power Master Go to automate the 3G connections (on/off when screen is activated) and time of entry into airplane mode (00:00 to 7:00). Anyone experienced this problem?

PS: sorry for some google translate errors!
[Captivate Android Development] CheesyNutz:
http://get.cm/get/jenkins/4619/cm-9.0.0-RC2-captivatemtd.zip

RC2 released for the Cappy
[Captivate Android Development] lordxentris:
Hehe, Nice :)
[Captivate Android Development] ThreeofNine:
NICE! Now I can wait for the CM10 whenever or if it becomes available for the cappy!:cool:
[Captivate Android Development] vinay427:
I thought it would be better to make a new thread for the RC2 as it wasn't a nightly, as described in the title of this thread.

http://xdaforums.com/showthread.php?t=1783122

EDIT: This caused me some issues in the i9000 forum. If anyone here doesn't want me making a new thread, please let me know.
[Captivate Android Development] nkrick:
Great to hear that increasing the voltage helped both of you. Each CPU is unique. Depending on where the CPU was in the wafer and yields, it is likely to have different characteristics for required voltage and maximum clock speed. Anyone with sleep death problems will have to do their own testing and tweaking to find what is required to keep their phone "alive."

Most large CPU manufacturers (like Intel) use different CPU's off the same wafer and "bin" them to become different CPUs (1 might be a 2.4 GHz part and another could be 2.8 GHz; 1 might be a "regular" voltage part, another might be an ULV part to be used in an ultrabook). For the Samsung Hummingbird CPU's, they were all intended to run at 1.0 GHz with the same voltage. This means that as long as they meet a "minimum spec" everything is good. However, for some reason yields must not have been as good as Samsung though and some of the CPU's that went into production devices could not meet the original specs, specifically, at very low clock speeds, the supplied voltage was not enough. Luckily, modern smartphones are so programmable that a firmware update is able to increase the voltage supplied at low clock speeds, or increase the lowest clock speed from 100 MHz to 200 MHz.
[Captivate Android Development] skyxliner:
is it just me or rc2 doesn't work well?
[Captivate Android Development] azunino:
Working fine here. However my 2 cappys never have problems...
[Captivate Android Development] CheesyNutz:
just you smooth sailing here
[Captivate Android Development] johnnyrichter:
I wasn't sure if it was Titanium Backup causing it, another poster told me to try uninstalling to see what happens but the sleep deaths still occurred. I guess other people fixed their sleep deaths by uninstalling that from what he was saying. The sleep deaths also occurred with Icy Glitch.

So far the only way I have been able to reduce the amount of sleep-deaths was to increase my idle clock from 100mhz to 200mhz and increase the idle clock voltage from 950mv to 975mv or 1000mv. This has reduced my sleep-deaths from 4+ times a day to 1-2 a day and sometimes down to only 1 every other day. It's very random but there is a definite drop in amount/consistency.

My brother's phone started suffering sleep deaths yesterday after a week or two of running like a champ with Icy Glitch. I adjusted his idle voltage up by 25mV and as far as I know the problem has gone away almost completely.

Based on the above, and the fact that a LOT of other people have been experiencing the same problem and were saved by the same solution, I hope to see this voltage bump implemented in future releases or at least give end-users the ability to do it themselves on the baked-in kernel.
[Captivate Android Development] whipps:
Adding apks to zip file

I want to add some apks to the nightly zip file before I install it on my phone.

Will doing that mess up anything?
[Captivate Android Development] ap1618:
I haz question... if i do a factory reset, do I need to reflash google apps?
[Captivate Android Development] shane87:
If all you do is a factory reset, no. Factory reset just wipes data, datadata, cache, /sdcard/.androidsecure, and, if you have an external sd formatted for apps2sd it wipes sd_ext. Gapps are stored in /system, so factory reset won't touch them. However, you will loose all of your gapps data, such as any synced contacts, any synced gmail messages, etc. And it will remove your gmail account from the phone. After you add your gmail account back in, though, you can resync everything that got erased from gapps.
[Captivate Android Development] sansaman:
Yo. Cm9 Rc2 for captivate is damn fast. Add to that the data fix zip from here, this phone is super slick. I might get separation anxiety if I get another phone now.
[Captivate Android Development] carlosgardel:
For factory reset don't have to flash Gapps but if flashing CM9 yes you have to flash Gapps.
[Captivate Android Development] ThreeofNine:
May I suggest to re-boot and wait about 5-10 minutes? Longer if your apps start updating. Sometimes a new flash takes the cappy a while to 'settle' in and become stable.

RC2 works great here! I think I'll stay with it until the stable shows up.
[Captivate Android Development] Primus76:
have been floating around the CM website looking for any particular steps to flashing RC2, especially coming from nightlies. Wondering any of you did anything special or just -> recovery, install zip? Does this need cache wipe/dalvik or does the install do it like the nightlies?

Thanks
[Captivate Android Development] Madtowndave:
Do you have the link for the data fix zip? I assume this would be the /datadata low storage fix...

I looked at a couple threads on this issue, but got confused. Would be great to find just the zip file to flash to resolve this.

TIA