yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] dank8885:
Man sounds like you have bad luck! Glad that modem worked out and hopefully it exceeds your standards since you had such a hard time getting it installed.
[Captivate Android Development] airtower:
Oh by virtue of the installation pains alone it already has!
[Captivate Android Development] theytalkalot:
Just installed test three for the sleep deaths....well let you know..but question...if it is the battery problem, if I got a new battery would that solve my sleep death problems?
[Captivate Android Development] Fear of Oneself:
Not sure if that is a bug in teamhacksung's version of ics, or ice in general. Because I tried the AOSP version, and have the same issue as you.

However I'm on Fido (basically rogers) in Toronto and the roaming symbol came up. (Fixed the problem by re-flashing with the sim out)
[Captivate Android Development] energyracing:
I just flashed Build 14 last night and I love it, but today I've had a few sleep deaths. Very rapidly, back to back to back.

I was running the stock kernel that came with Build 14. I turned the phone back on, let it boot, set it down, and less than 5 minutes later, dead. (All of these sleep deaths happened once the battery went below 50% charge, if that's relevant)

So I flashed Glitch v14 B1, and when I went into CPU Master to bump the CPU up to 1152mhz, as soon as I hit "Apply", the phone locks and reboots, but it keeps the 1152mhz on reboot. I tried Voltage Control, same exact deal.

Any suggestions on the sleep deaths and/or phone locks?
[Captivate Android Development] Razzman:
Sounds more like a bad flash than anything else. I would clear all and re-flash the rom. As for sleep deaths, add that subject to the search bar in this forum thread and you'll find dozens and dozens of posts about it with no clear solution yet.
[Captivate Android Development] JoshJ22:
For the first issue, try increase ur min CPU frequency to 200mhz

For the phone rebooting issue, it sounds like a stability issue. Try going back to the stock glitch settings and see if it reboots when u change the max CPU frequency back to 1000mhz, if it doesn't then I would keep it there and not try to OC ( also, u might want to use NSTools).

For future references post in the glitch thread if ur using their kernel
[Captivate Android Development] energyracing:
Yea, wasn't holding out much hope on the sleep death solution.

As for the flash, I ODIN'd back to 2.2, rooted, wiped date/cleared cache, Flashed Build 14 (twice), and booted. Everything has worked fine (except the sleep deaths), until after I flashed Glitch kernel and adjusted the CPU. That's the only thing that's wrong.
[Captivate Android Development] b-eock:
Or use the recommended OC APP.

NSToolS
[Captivate Android Development] Silencer96:
Is anyone else getting force closes when using the search function in the music app?
[Captivate Android Development] oldskooldawgz:
I did all of that before the flash. It was a freak occurance that happened after using build 13 for a while i just thought it was weird and worth sharing. It never got warmer than usual. I powered it off and put it in my book bag for during my classes. It had never happened before that or since then(a couple of of weeks. I typically try to completely drain it a couple of time a week and let it get fully charged.
[Captivate Android Development] Fear of Oneself:
Yup

ICS build 13

Glitch V14

1.4Ghz OC
[Captivate Android Development] bentonhall:
I haven't had any charge or sleep deaths on the stock kernel but I have had reboots during phone calls. However I installed glitch v14 beta and have not had any reboots during phone calls in two days. I did have one random reboot while updating apps on glitch though.
[Captivate Android Development] Gromlakh:
With all the talk of charge/sleep deaths, just thought I'd chime in quickly to say everything's running 100% smoothly for me after 4 days on Build 14. Battery life is much improved over my previous setup, which was Glitch + one of makelegs' kangs. The last few flashes were particularly bad on the battery, but ICS has been fantastic so far. A few issues with gapps early on, but once I did a cache/dalvik wipe and re-flashed gapps + the fixer everything is fine.

Zero charge/sleep deaths this way. I also do not get FCs when searching in the music app.
[Captivate Android Development] gstern:
Just had another sleep death (at least so it seemed), went out for a cigarette, pulled the phone from my pocket (it was sitting idle for about an hour), tried to turn it on- no response (oh great:mad:....). as always, first thing i tried is long pressing the power button to turn it on and SURPRISE:eek:- a screenshot sound! apparently i was also pressing the vol down button at the time!

so- not a sleep death after all!! screen just won't turn on but the cappy is still running!

cigarette out, run to pc, plug the phone in via cable, cmd window, adb- S**T:mad:- no devices connected! forgot to re-enable usb debugging after last reboot!!! can't pull logcat, kmsg or anything....

so, if any of you stumble upon a sleep death issue, double check to see if it's just a screen wake up issue.

on b14 test kernel 2.

will post again with logs if this happens again.
[Captivate Android Development] Silencer96:
For anyone who's still deciding whether to install this or not, here's my brief review of the rom. The final score is in the description.

[YOUTUBE]CYE8U-KN_6c[/YOUTUBE]

Hope that helps :)
[Captivate Android Development] pawitp:
It's simply how Google chose to do it in ICS. Maybe file a bug with Google? (or find a friend with a Galaxy Nexus to report it for his phone to Google)
[Captivate Android Development] k2ham:
Running b14 and loving it. After increasing min voltage to 200 I haven't had any sleep deaths with original kernel or icy glitch. About the only issue I'm having, which is minor, is that after rebooting the phone I have to re-enable JuiceDefender and SwiftkeyX. Keep up the great work! We really appreciate it!
[Captivate Android Development] drwx:
wrong time on lockscreen

Has anyone else had the issue of having the wrong time show up on the lockscreen? I'm on build 14 and didn't notice the problem in any other versions. I usually just use my phone instead of a watch, so just looking at the lockscreen for the time has become a habit. Last night, I checked the lockscreen and it was 45 minutes behind. A few minutes later i checked it again and it was right. I had the same thing happen again this morning.
[Captivate Android Development] owe2003:
How do you get the volume + power to take screenshots? No matter what I do, it doesn't work. I can only take one using the power menu.
[Captivate Android Development] Dr. aLkoo:
I'm usually using media player. I use headset. But now music player force closed every run.
[Captivate Android Development] The Communicator:
yep 10char
[Captivate Android Development] alphahere:
question did you add 200 to the minimum voltage? Could you explain better please.

Thanks
[Captivate Android Development] mbc663:
Whats that SQUARE shiny thing in the background of the video from the screen shot? ;p
[Captivate Android Development] airtower:
looks like some sort of black glass sphere enclosed in a plastic housing. Looks like it's from the future! :D
[Captivate Android Development] voldomart13:
I just noticed something, the phone was giving me a low storage space message so i started looking around and I found that the app data that is in /datadata is also in /data/data. Is this right? Ide like to be able to use all my internal app storage space instead of like 300 megs. I already tried clearing my cache, I had to move my apps to get it to disappear.
[Captivate Android Development] theyurtingyeti:
The data is linked between the two folders: there isn't a duplicate of all the files. I replied to something like this a few pages ago, here's the link: http://xdaforums.com/showpost.php?p=21744795&postcount=4524

It may not match exactly what you are seeing, but it may fix it regardless.
[Captivate Android Development] voldomart13:
I saw this a couple hundred pages back some people said that it fixed there low data isues

http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list

I'm afraid because I havnt seen anyone flash this to build 14

forgot OP

http://xdaforums.com/showthread.php?p=21259132&highlight=low+storage+space#post21259132

One person said this about it

It gets rid of the symlink in between /data and /data/data. One of the devs (iirc) said that this would fix the issue, but make things a bit slower.

Either way, its fine to flash on this rom, if you want. It just runs a script, doesn't replace any files or anything.!
[Captivate Android Development] gstern:
Just press power + volume down at the same time and hold for a sec or two.
[Captivate Android Development] nyciz:
Strange but on my phone its Volume - (thats volume down) + power for 2 seconds and you should her the camera shutter plus see the pic for a few seconds.

You should also get a Screen Capture notification, that takes you to the screenshot. I think it saves it on the internal SDcard in a folder called ScreenCapture
[Captivate Android Development] ScottyNuttz:
I think that's what he meant: Power AND Volume DOWN (-). I knew what he meant when I read it, but I also knew it was the worst possible way to phrase it.
[Captivate Android Development] Kaik541:
or a much easier, and less hackish way is to create a file in /datadata called ".nodatadata" and reboot.

adb shell touch /datadata/.nodatadata
[Captivate Android Development] owe2003:
Yes, that is what I meant. Volume down + power button. I just forgot to put the "down." My bad. Anyway, I finally got it to work. I just had bad timing with the way I pressed it. All it would do was bring my volume down, or bring up the power menu (again because of timing).
[Captivate Android Development] nyciz:
LOL...gstern & ScottyNuttz, when I read it I saw Volume Up. Wow think I better get the reading glasses out. Hmmm wonder what else I could do to improve my eyesight...I wonder....:confused:
[Captivate Android Development] voldomart13:
OK i did that and it made that file within datadata. It was also made in /data is this correct?
[Captivate Android Development] tsuda:
I also have this problem. If the screen turns off during a call on skype/fring over wifi, the call is cut off. If the call is over 3G, no problem.

So the wifi always on option is not working.
[Captivate Android Development] shane87:
On build 14, I have not seen my wifi turn off when the screen is off. Granted, I don't run anything that relies on a constant data connection, so I haven't seen any problems like you mentioned, however, if I go into battery stats, it shows that my wifi is always on, regardless of whether or not my phone is awake.
[Captivate Android Development] tsuda:
On mine it also shows in battery stats that wifi is always on, but it gets turned off when screen is turned off.

It's very easy to test. Just start a Fring test call, turn off the screen, and the call gets dropped.

Edit: interestingly, Skype kept the connection but Fring gets dropped when the screen is turned off.

Edit 2: just tested the same on onecosmic's ics, for the same results. Will try on stock and report back. Still not sure if it's a ROM issue or App issue
[Captivate Android Development] malbolgias:
WiFi also dies when the screen turns off and USB tethering is active. Rendering it useless.
[Captivate Android Development] pizz0wn3d:
There's an option in the settings to keep the screen from timing out when it's charging.

Herp derp Captivate XDA Premium.
[Captivate Android Development] baghera1979:
You should be able to switch the wifi sleep option when screen off to never sleep.
[Captivate Android Development] RaptorOne3:
Confirmed. WiFi does not shut off when "Keep WiFi on during sleep" policy is set to "Only when plugged in" or "Never" and the screen is shut off. WiFi remains active.

You can test this by first setting your WiFi policy to "Only when plugged in" or "Never", then restricting background data. Then turn WiFi on, start a download and shut the screen off. The download should pause or cancel as WiFi should shut off. However, the download will continue and finish the entire time the screen is off...
[Captivate Android Development] Joecascio2000:
To save battery just keep it set to never and use an app called Auto Wifi Toggle or Auto Wifi On/Off. They work great. Wifi stays on when your using it and turns off when your away from a wifi that is not in your saved list.
[Captivate Android Development] singlebeam:
insightful post...im in the same boat

Sent from teamhacksung SGH-i897
[Captivate Android Development] Abaddon:
been using the ROM for weeks now. one small issue is with any kernel I try I get SoD.

Sent from my Cappy
[Captivate Android Development] Lollipop_Lawlipop:
Sleep and charge death victims... Are any of you using SetCPU? If so, uninstall it and see if that makes a difference. SetCPU will freeze your phone after sleep for some reason.
[Captivate Android Development] Abaddon:
apparently most of us arent using setcpu. NSTOOLS is the app we use

Sent from my Cappy
[Captivate Android Development] ScottyNuttz:
What if you uninstall that? I've been on build 14 for a week (from Illuminance) and not had a 'death' of any kind. I don't mess with over clocking at all or experimental kernels at all.
[Captivate Android Development] Abaddon:
ok let's see. I'll clear it's data and test for a couple of days. tried this before but with the different kernel. lets see

Sent from my Cappy
[Captivate Android Development] Razzman:
Neither have I. No deaths, freezing or reboots at all. All stock out of the box, no oc. Been on 14 for over a week now.
[Captivate Android Development] alphahere:
Charge Death Update

Phone - Captivate Build 1010 with GB Bootloader.

I once had a problem with the first CM7 builds with charge death when undervolting but this was quickly resolved by using the default voltages.

I have always had charge death problem with the following kernel rom combinations.

1) teamhacksungs ics with stock and test kernels

2) Glitch kernel with teamhacksungs ics caused charge death and had to pull battery to restart phone.

3) icssgs rom with Platypus Kernel

I then tried nushor's kernel + teamhacksungs ics build 14

http://ics.darkirc.me/stable/ICS_Captivate_20120108_r3189v_BIGMEM_update.zip

It has been 12 hours on the charger and no charge death at all. I was having charge death events every night with all previous kernels.

This looks promising. Will keep testing and will post if charge death returns.
[Captivate Android Development] jerkysh:
yay, just flashed the CM9 ALPHA build 15, and i would like to say it is pretty AWESOME!

will continue testing and looking for bugs, but the build is great :)
[Captivate Android Development] speedy_11:
Came form stock 14: no custom kernel

After installing build 15 i'm getting constant Trebuchet force closing.

Fixed by using drop down and acessing setting> apps> trebuchet> clear data

Battery is showing percent instead of icon from first boot. Changing it in the setting doesn't work (its probably just a place holder for now)

Edit: Wondering why cant apps like dsp manager, dev tools and such be disable in app info? I checked the permissions are the same as other apps that an be disabled.
[Captivate Android Development] airtower:
Only getting percentage battery as well. You can use TiBu to remove DSP manager and probably devtools, although I never tried.

Build 15 is really great otherwise. Love the new CMsettings integration, brings back a lot of what I missed having in CM7
[Captivate Android Development] speedy_11:
I use a file manager to delete them from systems apps, after every update. Just wondering why they don't let you disable them. Its not a big issues thought.
[Captivate Android Development] anishz:
Hey airtower, your sig says you use the volume rocker wake, my power button is also broken, so wanted to know what are you using for the rocker wake, same build 14 zip from thinkk or another app, for build 15.
[Captivate Android Development] chasesavestheday:
Quick question, why at times in recovery it'll say the back button is disabled and I cannot enter any menus. Sometimes the home button with then work, others it wont?
[Captivate Android Development] airtower:
Actually my power button started working the day after it failed, but it's EXTREMELY sensitive. It works like a soft button, with no tactical feedback. Very annoying since I'm constantly hitting it when using the phone. Getting a new phone on insurance next week.

but to answer your question, I'm not using a rocker wake at the moment so I can't say if it works with build 15.
[Captivate Android Development] anishz:
Thanks, good it started working at least, mine stopped working for no reason, never dropped it or damaged it, it's almost 17 mths old so no warranty.
[Captivate Android Development] kmakiki:
Man, build 15 is amazing so far. Really starting to feel like CyanogenMod again, can't wait for all those place holders to be filled! Thanks guys!
[Captivate Android Development] GRACO:
:( Is there a way to show icon instead percent ? I try settings and as you said, doesn't work...
[Captivate Android Development] Chuckd610:
Unable to open Superuser.....anyone else?....Wondering if I can download the same or another version.

Edit: I hold in my hand an old, musty, spoiled dead fish. After reading the "known issues" section in the OP, I slapped myself accross the face several times. Please, anyone who wishes to slap me as well, feel free!
[Captivate Android Development] ScottyNuttz:
Please read the first post. This is a documented bug.
[Captivate Android Development] mbc663:
hit volume up, then volume down back and forth a few times, itll say enabled again.
[Captivate Android Development] Thnikk:
the build 14 package works fine on build 15
[Captivate Android Development] airtower:
Same here. It worked. Set it on the coffee table for a few minutes and that was it. If I end up getting another captivate next week, it will be for sale in late February.
[Captivate Android Development] zmore:
RC0

Loving the first of many CM9 RCs.

I did notice the new numerical battery percentage default, and I like it, but, it's almost always stuck at 99% with periodic blinks to 100% while charging. It would be nice if it rounded up to 100%, and, optionally, to save space, the battery icon replaces the wide text when at "~100%".

; ceil(99 + 0.01)

100

Also, anyone happen to know how often the CM stats are updated? Daily I assume? I'll make a note to check it out again tomorrow to see where stats for 9.0.0-RC0 stand (shows "1" now)
[Captivate Android Development] chasesavestheday:
Any way to turn up vibrate intensity. Cant tell when I receive messages.
[Captivate Android Development] airtower:
Reboot..mine fell into a weak vibrate state earlier but it's good now.
[Captivate Android Development] Chuckd610:
I had already edited my original post to reflect what you posted. thanks
[Captivate Android Development] TheSoaresan:
Look for my vibrator mod. I just attached my girlfriends vibrator to the back of the phone and it increases the vibrations x10! Now I always know when I get messages. Also it makes for a great phone handle too.

Just kidding budd.
[Captivate Android Development] Razzman:
Not sure what's going on but since flashing 27 minutes ago i'm down to 66% battery from 100%! :confused: Cleared all before flashing.
[Captivate Android Development] zmore:
Hmm. I didn't notice until now that there's no "Vibration intensity" system setting anymore. Perhaps it was set to max and the setting removed in Android 4.0 to simplify?
[Captivate Android Development] pizz0wn3d:
Does that plug into the micro usb port or the headphone jack?

Herp derp Captivate XDA Premium.
[Captivate Android Development] macropp:
Build 15 - displays only battery percentage, it can't be changed. maybe it's the matter of glitch 14 preview 5.. also network display( in dbs) doesn't work.
[Captivate Android Development] TheSoaresan:
Battery/solar powered with vibration motion detection
[Captivate Android Development] chasesavestheday:
Hahah awesome! Thanks guys!
[Captivate Android Development] pintek:
with the stock keyboard an swift key when i type into google search,maps,navigation,browser it will stay up for a few moment then go back to the launcher which gets kinda annoying for trying to look up stuff x.x
[Captivate Android Development] richsale:
So far Build 15 is flawless for me. Like the battery % mod but wish it had the same color as time.
[Captivate Android Development] Holmes108:
Agreed, I like it too, but needs to be blue.
[Captivate Android Development] johnhazelwood:
I installed build 15, then installed nushor's kernel but lost home button functionality. How do I get back to stock kernel? I tried installing 15 over itself, but I got a buildprop error.
[Captivate Android Development] :
format everything except sdcard in the mounts and storage menu in recovery and try flashing Build 15 again or alternatively flash from stock. Why were you using Nushor's kernel again????
[Captivate Android Development] johnhazelwood:
Thanks, I'll give that a shot. I had placed everything in a folder for flashing (build plus sufix plus gapps...that kernel was in there too...over ambitious flashing).
[Captivate Android Development] RaptorOne3:
I'm not even going to explain why this is a bad idea again... I went into plenty of detail as to why it's a bad idea to flash old kernels on new builds and also posted the solutions to this...

Not to mention, the developers do not like these types of discussions because it has nothing to do with them, the new build, nor the topic of this thread... Check yourself!
[Captivate Android Development] ThreeofNine:
I perfer the battery % too! Blue would be nice, but that little 'touch-up' can wait. No problems so far with Build 15 installed over 14 and I'm staying stock kernel, modem, etc until I see problems with them.

This 'almost CM9' rom is making my ol' Captivate work like a Nexus!
[Captivate Android Development] jswclw:
Running Test Kernel #3 right now for build 14 to tackle the charge death problem. 2 out of 2 nights without charge death on #3. Had 4 of 5 night without charge death on #2.

Curious: If I go to build 15 and start experiencing charge deaths again, are those test kernels going to work?
[Captivate Android Development] nok6100:
Just installed build 15 over build 14, which was installed over build 13, LOL, and everything went very well, no force closes on anything, just wanted to chime in and give a update.

Very exited to see how far this has come, this version of ICS has worked better than any other, been using it since build 3 and will report any bugs as needed.

Thanks guys! :D
[Captivate Android Development] Razzman:
I too prefer the percentage and blue would be good as well, but as you said can wait. So far so good without any issues other than a strange battery drain after first flashing? oh well it's good now.
[Captivate Android Development] RaptorOne3:
The kernel/s will function, however you will lose any kernel-related changes that were made on Build15.

It's not recommended to use them unless pawitp has certified their use with a specific build.

As always, flash at your own risk!

Personally, I would try to address the issues in a different manner.

I recommend -

Back up all your personal files (copy them to your computer via USB transfer). Wipe data/factory reset, Wipe Dalvik cache, wipe battery stats, wipe cache partition. Then flash back to stock GB with Odin3. This will help make sure you have a nice clean device to start with.

Place Build 15, Gapps_fixer and Gapps7.1 on your internal SD card.

Flash any SGH-i897 kernel with CWM in it through Odin3. The kernel absolutely MUST be an SGH-i897 specific kernel. Alternatively you can try using ROM Manager to obtain CWM...

Then flash Build 15, Gapps_fixer and then Gapps7.1.

Reboot.

I have not experienced any "charge death" or "sleep death" that people are referring to. The first time I flashed Teamhacksung's ICS ROM, I did the above steps and ever since then I've simply flashed each new build along with Gapps fixer and Gapps7.1, right over the old build. No problems here at all. Everything is fully functional.