yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] dillonc:
I just tried the color tuning thing, it kinda helped but the screen just doesnt look right. I know that sounds picky but the captivate really has a great screen and it would be a shame not to take advantage of it! I tried formating all of those things and it still isnt working for me. However I just tried it on my girlfriends captivate and it worked flawlessly! (Frustrating) Would you suggest completely wiping EVERYTHING and starting fresh? How would I go about formatting the internal SD...?
[Captivate Android Development] gredberd:
Maybe it is too soon to ask, but how is battery life on build 13? (especially comparing to build 12) I am running build 12 am happy but would like the comera updates so I want to flash build 13 if it has great battery life like build 12. Thanks.
[Captivate Android Development] pixbuf:
I very much doubt it for 2 reasons:

Once the phone is booted, the bootloaders don't have anything to do with anything

I and many other have been using GB bootloaders for a long time (8 months for me) and have never had this problem.

The only way the bootloaders could affect anything is by not loading something properly when the phone boots, but that's not likely.
[Captivate Android Development] attsw:
My first recollections of Sleep Death were from back when the devs starting building custom kernels with OC in the 2.2 days so I doublt the GB bootloaders are the culprit.
[Captivate Android Development] know50:
I would Odin back to stock and start from there. I doubt you need to format the SD card but you can if you think you need to, just save what you want to keep on your computer first and format SD in recovery. You should be able to find everything pretty easy with Google. I personally use a 2.3.3 Odin package but I have gb bootloaders so if you go with a 2.3 Odin package just make sure it has bootloader included or Odin to stock 2.2 then flash to cm7 then ics. Make sure you follow the directions for anything Odin extremely well:-)
[Captivate Android Development] dillonc:
I really appreciate your input on this and I hate to sound too much like a noob but I haven't formatted my SD card before...when you say "You should be able to find everything pretty easy with Google", do you mean instructions on how to do it or do you mean the necessary files that i might delete when doing this?

I tried going back to stock 2.2 and coming back so that is why I believe i should clear the sd card.
[Captivate Android Development] daskanda:
http://xdaforums.com/showthread.php?t=731989

you can use this to master clear your internel storage

just boot phone phone normally open odin hook up the phone and click master clear... do NOT put the phone in download mode
[Captivate Android Development] know50:
I could be wrong but I think I remember reading something like if you're on a rom that you have overclocked you have to go back to stock voltages before you wipe and flash because those settings could stick sometimes somehow. I can't remember where I read it but it was something like that. I never changed my overclock before I wiped and moved to something else and I never had a problem with it. Also I would think that when you wipe and format everything that the CPU settings would be wiped too but I'm sure I read that somewhere. Still though I haven't seen any sleep death while at stock speeds so I'm kinda lost on this one. I've also been using gb bootloaders for months with no issues. Sorry I couldn't help more.
[Captivate Android Development] SkitchBeatz:
FWIW my battery life on build 13 has been about 30% better than all previous 12. Small sample size though as I've only had it for about 24 hours I think
[Captivate Android Development] know50:
Still the red screen after you odined to stock? That would have me thinking that either you need a different Odin package or it is hardware related. And if I'm not mistaken your girlfriends phone had the red tint to it also? It seems strange that both of your devices had the red tint issue. That really makes me scratch my head. I wish I could replicate this just to see what's going on. I wish I had more for you but I'm kinda lost on this one. But yeah if you're on 2.2 and you want to wipe internal SD I think you can just go into settings then storage and format SD there or in recovery or even the master clear with Odin then run the 2.2 package. Oh yeah and by find everything with Google I just meant all of the packages and instructions you would need for Odin
[Captivate Android Development] wildnux:
I am having two problems with these builds:

1) auto brightness does not work. If i set it to auto, it will not change the brightness unless i turn the screen off an turn back again. So basically the auto change of brightness only works after wake of phone. This has been after the hue fix of the auto brightness.

2) the notification ringtone plays right after i unlock the screen. Say i got a message, i can feel my phone vibrate. I do not hear the notification at that moment. It will play the sound right after i unlock the screen. Even if i unlock my phone hours later after receiving the message.

FC's have been greatly reduced(above 90% for me) i used to get fc's on some apps every time i launch the app, and had to launch them again for them to work but its been a smooth sailing on that matter since build 12.

Edit: just want to add that i tried reflashing build 12 as well as build 13 (both twice) and formatted all partitions except for sdcard and emmc before flashing the rom.

Sent from my magical wand!
[Captivate Android Development] dillonc:
No actually my girlfriend's phone did NOT have the red screen tint, which frustrates the hell out of me! The funny thing is that she probably doesn't appreciate the ROM like i would, and of course hers is the one that works just fine! lol And I normally would think this would be hardware related but, (I may have not made this clear earlier) the red screen tint goes away when I flash back to build 11.

I will try the master clear and report back with my results!

Thanks everybody!
[Captivate Android Development] know50:
OK I think then you may have gotten a bad download. Redownload and wipe everything and flash again

Did you use the same download on both phones would be my next question. Lastly if 11 worked for you then I would reflash 11 and gapps, fix permissions, boot up, then boot back into recovery wipe cache and dalvik and flash 12 and gapps(with the new downloads), fix permissions and boot up and see what it looks like. If its good then wipe cache and davik flash 13 and gapps, fix permissions etc. If all of this fails then I would stick to 11 until 14 comes out if 11 is good enough for you. I know its agrevating, you should have seen all of the crap I had to go through with the old optimus s for my girl lol! I ended up fixing it for her but then bought her a new phone cause I never wanted to look at it again lol
[Captivate Android Development] saobang3886:
I don't have any problem with build 13 until now :) try reflash maybe fix it for you!
[Captivate Android Development] know50:
Yeah that's a bunch of craziness there. I would definitely wipe all and reflash
[Captivate Android Development] alphahere:
For folks with Sleep death when charging and a custom kernel. Try increasing the voltage for the following:

200mhz - 1000 mV

100mhz - 1000 mv

I had the same problem with gingerbread and custom kernels. This was the solution for gingerbread and this worked great in ics. My captivate needs more power. Probably not good for battery life but it runs great now and no more waking up in the morning and my phone is off.

I have never had Death sleep with the stock kernel.

It is not the GB bootloader at least for me. Captivate Build number is 1011.
[Captivate Android Development] theytalkalot:
What program are you using to change the voltage, volt control or ??

I'll give it a try, I have been waking up to a dead phone for a while now....
[Captivate Android Development] jerkysh:
if using the v14 Glitch kernel, NSTools is the app :)
[Captivate Android Development] theyurtingyeti:
Latent data solved!!

Special thanks to kangi26! I was able to solve my problem by following his advice:

flashed to stock

master clear

started from scratch

I'm now on build13 and the system data in /datadata is 3MB -- WOOT!
[Captivate Android Development] kant5t1km3:
Can I use glitch kernel with b13? Also any way to change the font to walkway sans?
[Captivate Android Development] baghera1979:
its working for me but dont expect support from teamhacksung while on it.
[Captivate Android Development] tiuk:
That's really high for those clocks. If it solves your problem that's good, but you may be able to bring it down a bit for the sake of battery.

Sent from Captivate, teamhacksung ICS.
[Captivate Android Development] uzbeque:
Noob question: When I flashed back into stock rom with one-click heimdall, it flashed my bootloader too. Now how can I install ICS bootloader?

(sorry if the question was composed wrong:))
[Captivate Android Development] b-eock:
ICS doesn't have it's own BL! But flash to GB BL and then to ICS from there...

And please ask question's in the dedicated Q&A thread.
[Captivate Android Development] ls377:
You don't need GB bootloaders, go ahead and install ICS.

Sent from my Captivate
[Captivate Android Development] b-eock:
It is preferred to have GB BL though. I have done my research dude, I promise you that my knowledge tops yours...
[Captivate Android Development] ls377:
Alright, show me where it says GB bootloaders are preferred.

Sent from my Captivate
[Captivate Android Development] b-eock:
That way people don't flash the 3 button fix and brick their phone. It is know over the whole Captivate community to keep GB BL's! So there you go! :D fun being wrong right?
[Captivate Android Development] ls377:
You mean the 3-button fix that is made for the eclair bootloaders? The one that will definitely brick your phone if you flash it on GB bootloaders?

Also, I said SHOW me where it says that. I'd appreciate it if you would at least back up your info before you insult me.

Sent from my Captivate
[Captivate Android Development] Kaik541:
we at teamhacksung have never promoted one bootloader or another. we don't care which you use. some users claim they receive better battery life on gingerbread ones, some say they receive better battery simply with i9000 bootloaders.

to be quite frank, I have tried them all and have encountered absolutely zero difference. I am currently on KK4 bootloaders and they aren't any better than JF6 in terms of battery life.

the only difference the bootloaders changed was a bug with external sd card mounting in regards to powersaving features (which we have accounted for and aren't truly life-altering in terms of day-to-day usage).
[Captivate Android Development] b-eock:
Exactly with the GB BL's there is no need for the 3 button fix. But because people are so dumb and don't read, then brick their phone. I am not going to keep on arguing with you, i'm not the only one that says you should stick to GB BL's. So do it your way, IDC!
[Captivate Android Development] ls377:
So if you don't need 3-button fix on GB bootloaders, why would someone try to flash it in the first place? I'm not arguing with you just to be right, I take issues with telling someone to unnecessarily flash bootloaders, which CAN brick your phone (trust me, I've done it. Way before unbrickable mod). It's an extra step that simply isn't worth the risk when using mtd ROMs.

Sent from my Captivate
[Captivate Android Development] b-eock:
So people flashed it because they used it before, so they were like "hey i used it before, what could it hurt?" BAM "My phone is bricked :*(" That is why AIO toolbox was taken away from this forum! They didn't read, because I know it was posted to not do that!
[Captivate Android Development] ls377:
So what exactly is the advantage of installing GB bootloaders if you don't have them? That situation only comes up if you have them installed.

Sent from my Captivate
[Captivate Android Development] b-eock:
GB BL's fix the button combo problems if people have them. If you have GB BL's installed there is never a need to flash BL's again PERIOD
[Captivate Android Development] ls377:
So how do people who don't read figure this out? You'd think if they didn't know not to flash 3-button fix, they would do it next time they needed to go back to stock.

This is getting way off topic, you're welcome to PM me if you want to continue this.

Sent from my Captivate
[Captivate Android Development] RockRatt:
To add onto what b-eock said also besides making it so you DONT LOSE your three button combo from flashing back to eclair bootloaders. With GB bootloaders you can flash ICS as of right now it doesnt matter, ANY GB rom, ANY FROYO rom, and ANY ECLAIR rom. If you are on eclair/frouo bootloaders you will have some issues when running GB roms with weird bootup/shutdown colorations on screen.

Once you flash GB bootloaders you will NOT ever have to flash back to any of the eclair stock roms that jnclude bootloaders. Since it IS very easy to brick it flashing bootloaders at any time. While on my cappy back in eclair and froyo days I probably flashed back to stock eclair with bootloaders to fix a issue with a rom i had tried about 60+ times. Finally on one of those occasions I hard bricked the cappy and had to send it for jtag. I had him flash tbe ginger bootloaders and I have never had to mess with them again.

Yes with CM7 you do not necessarily need to flash ANY bootloaders since it will NOW work with them all. Plus it is basically the same with TeamHacksungs ICS not really NEEDING to flash a bootloader. BUT what I am saying is IF you are gonna flash something with a bootloader you might as well flash a i897 GB bootloader and be done with bootloaders for good. Then IF you need to flash to stock you can use any of the Gingerbread odins that do not contain bootloaders to get off of cm7/cm9ICS or any other rom.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] ls377:
I agree with you, if you have GB bootloaders, there's no need to go back. However, if you're on Froyo bootloaders, there's no need to flash GB bootloaders unless you're flashing a Samsung GB ROM (I've honestly never been to crazy about flashing them then. Maybe it's just because Odin hates me :p). I imagine that most people that flash this at this point won't go back to a Samsung ROM (unless we get some magical ICS leak), so bootloaders won't matter in the long run.

Or I could just be paranoid.

Sent from my Captivate
[Captivate Android Development] m.e.:
OK, thanks for help!

But should the light really stay on if this setting is enabled? I would expect it to "pulse" couple times, and turn off.
[Captivate Android Development] spritetth:
I'll try now! dowloading....

this build 13 has played the game 3D?
[Captivate Android Development] voldomart13:
I've noticed that the app beautiful Widgets the clock doesn't sync with system time any help there?
[Captivate Android Development] TheEscapist:
It would flash on and off ( or "pulse" ) if we had a real led. The way led notifications is written means that you can only have them turn on and off. (Technically, you can write code to make them flash, but it kills the battery because the code constantly has to run).
[Captivate Android Development] k2ham:
I had that same problem. Try going into manage apps, clear the data and the cache for the app, and reboot the phone. That took care of it for me. I haven't had the problem since then.
[Captivate Android Development] dnk.:
Hi.

I'm having a strange behaviour , screen does rotate in camera app, but does not rotate in browser, gallery.

Androsensors shows data from g-sensor. G-sensor games like jetcarstunts work fine.

And also I've noticed that when I flash stock Eclair rom I also do not have any rotation. In 2.3.* roms everything works fine.

Tried to flash Onecosmic's rc2.1, same there :(
[Captivate Android Development] theyurtingyeti:
[Q] Bug or Market Issue?

Flashed build 13 yesterday and everything seemed to be going great. I also flashed gapps 7.1 and gapps fixer.

I had some 101 errors with the market but was able to fix it by removing my google account and then adding it back on.

This morning I continued putting stuff back on my phone and I'm running into error 406 through the market. I have taken the following steps but none have worked yet.

1)Rebooted

2)Recovery and re-flashed gapps 7.1

2)Recovery and re-flashed gapps fixer

3)Removed 2nd google acct (I have to loaded)

4)Removed primary google acct

5)Added primary account back in

6)Rebooted

After each step I tried to download Root Explorer from the market. To see if it wasn't just Root Explorer I then tried to download Angry Birds and got the same error.

What is this error, and how do I fix it? I can probably restore some of these apps from TB, but if there's a bug that affects the market, I wanted you guys to know about it!
[Captivate Android Development] slayp00n:
Updated to 13 this morning. Camera is not working?
[Captivate Android Development] kangi26:
Camera world great for me

Sent from a autonomous device
[Captivate Android Development] theyurtingyeti:
The camera appears to be working well for me also.
[Captivate Android Development] know50:
Yes 3d games play fine on build 13 for me

---------- Post added at 11:41 AM ---------- Previous post was at 11:28 AM ----------

Market is working fine for me so far. Have you tried going into manage applications and clearing cache and wiping data for market? Also don't flash the gapps fixer unless you're sure you need it. I didn't need it and I flashed it anyway and I had some issues so I had to wipe and reflash without the gapps fixer and all is well now.
[Captivate Android Development] ThreeofNine:
On Build 12 the camera zoom didn't work, but on build 13 the camera zoom works great! ICS is getting very, very close to PrimeTime as CM9!!! My Captivate is sooooo good now I just may wait way past my upgrade date (sept) before upgrading to some phone worthy of replacing it. Maybe get one of the special Christmas priced deals that were out there last month!
[Captivate Android Development] airtower:
Reboot Recovery doesn't work for me in the extended power menu on V13. Three button still works. Not sure if ROM or kernel related, as I'm running Glitch V14.

All worked well in V12 and prior.
[Captivate Android Development] Ikonomi:
Reboot recovery is working for me on the stock kernel, so it may be Glitch related.

And I just want to tell the team that I am getting the best battery life under heavy use that I have ever had on this phone. It's pretty awesome right now.
[Captivate Android Development] know50:
Its glitch kernel related as glitch comes with its own recovery.
[Captivate Android Development] caleb4992:
So I'm having sleep death when not charging and also when I am. It only turns off after really long periods of time like overnight. Any way that I can stop this? I have No custom kernel, no mods, flashed from cm7, i897 BL, b13
[Captivate Android Development] J0ESK0:
Actually I'm on the stock kernel and I too can not get into recovery via extended power menu in Build 13. Was working on Build 12 however.
[Captivate Android Development] nimper:
Works for me on stock kernel. Eclair bootloaders for what it's worth.
[Captivate Android Development] kangi26:
Just checked, I am having no problems getting into recovery from the power menu (stock kernel)

Sent from a autonomous device
[Captivate Android Development] theytalkalot:
Same with the sleep of death...tried increasing the volts.no go...and when I turn it on goes straight in to recovery mode.....should I just start all over?
[Captivate Android Development] J0ESK0:
Hmm not sure, I just tested again to be positive.. Can you guys answer me this. Since I believe Build 10.. I've lost the CyanogenMod kernel screen and instead get the white at&t world phone boot screen twice. Does that happen to you as well? I'm beginning to think something messed up between flashes.
[Captivate Android Development] theyurtingyeti:
I flashed the gapps fixer 'because I needed it when I flashed build12... but I should have held off on doing it for buiod13 until i knew I needed it.

I cleared data/cache for the Market and it didn't work... so I cleared them again, rebooted and I'm still getting the 406 error.

Just to eliminate the question I cleared data/cache for gapps and then flashed gapps 7.1 again (not the fixer).... still got the 406 error.

---------- Post added at 01:41 PM ---------- Previous post was at 01:20 PM ----------

I'll have to keep my eye open for the snooze issue. I also noticed that using calendar snooze may have a similar issue. I'll 'edit' the calendar from the app, but the calendar never gets officially updated and the reminder just pops up again in like 5 min.
[Captivate Android Development] 60hzrumble:
I was having the same problem. I disabled the Calendar sync from the accounts menu, then flashed the gapps_fixer, then reenabled. Worked for me.
[Captivate Android Development] johnhazelwood:
Same Issue here this morning. I got it while on a call. The call ended and phone shut off (it's plugged into car cigarette adapter). When I booted up via power button I went right into recovery. I selected reboot and it booted up normally. I've been on build 13 for 4-5 days now, this is the first time I've had the phone shut down, and it's only happened while on a call (never while charging at home).
[Captivate Android Development] iluretar:
same thing happens to me and since build 10 too
[Captivate Android Development] theyurtingyeti:
I did that... it didn't help with the 406 error, but I'll have to wait and see if it helps with the calendar snooze issue :)

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

On a whim, I disabled Wifi while trying to download... it worked!

Only a little confused though as I've downloaded apps through this wifi connection in the past. Either way, CM9 seems not to blame :)

Thanks
[Captivate Android Development] RootTheMachine:
Pretty sure the kernel screen is supposed to be that way, otherwise it would be an isolated issue.

However, I have been getting infrequent sleep death since build 13. I had no problems on 12 for a whole week. I'm sure they will fix it

Sent from my ICS i897 Captivate
[Captivate Android Development] know50:
My bad. I mis-read your problem. I thought you meant you couldn't boot from the boot option in recovery. Sorry about that. My extended power menu works fine though
[Captivate Android Development] theyurtingyeti:
Note about titanium backup

With my super clean install of build 13 from stock, I ran a little test with the above issue.

I manually restored 5 apps from TB (free) keeping track after each one for /data, /datadata, and /datadata/system data. After those 5 apps, NO system data was added to the /datadata folder (in fact, there is none there at all)

I then batch restored 5 apps and checked the data again. System data was at 2.73 MB.

What this says to me is that something about how TB does it's restore that adds 'system data' to the /datadata partition. Based on my previous experience, this 'system data' is VERY difficult to get rid of -- I had to go back to stock.

This seems to be a TB issue, not an ICS issue, but as much of a pain as it is, I'm probably going to do individual installs/restores for my apps. Note that I did not try to install apps individually and then batch restore data. If I do, I'll post an update.
[Captivate Android Development] know50:
I actually had the issue with it booting only into recovery when I tried to power on. I ended up having to wipe all and start all over to get it fixed. I was on the glitch kernel when it happened. Still not seeing any sleep death issues though but there are so many people reporting it that I'm sure its a bug. Hopefully it will be worked out by the next build
[Captivate Android Development] airtower:
the glitch team said new builds were in the works to address the recovery problem, so that leads me to believe it's related to that kernel. Perhaps they will find that it is not.

I am on GB loaders by the way, but was on build 12 as well.