yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shaker2k:
Before you post to ask a question that you think might have been covered

If you are about to ask a question that you think might be covered: follow these simple steps

Log in

Click on "search this thread"

ask your question.

For me is was superuser not working. I typed in superuser in the search box and whammo I had about 20 + posts that answered my question. I only needed the first post.

The moderators have enough to do than continually answering already asked questions. So I hope this helps. :)
[Captivate Android Development] Thnikk:
1) It'll probably be fixed in the next build. If it bothers you enough, fix it yourself.

2) Pawitp already addressed this and it will be fixed in the next build.

3) Are you signed into your google account?
[Captivate Android Development] lothos:
I'm having some camera problems. Getting a force close when I try to change the resolution. When you reopen the app the resolution has been changed, though.
[Captivate Android Development] wash23:
This worked! Thanks!:)
[Captivate Android Development] JoshJ22:
This is a documented bug. Its in the list of known issues in the OP
[Captivate Android Development] APE992:
Flashed Build 14 and everything went fine until SMS Backup + restored all 6k or so text messages I have. Restored fine but when I went to load up a contact it'd choke and sit there doing nothing.

Guess I'll stick with CM7 or ditch my messages but the latter isn't such a pleasing thought. Anyone know of a workaround?
[Captivate Android Development] Joecascio2000:
Who keeps six thousand messages??
[Captivate Android Development] baghera1979:
He's waiting to get OVER 9000!!!!!!
[Captivate Android Development] Joecascio2000:
Haha oh man too funny.
[Captivate Android Development] RootTheMachine:
I've restored over 10,000. Give it some time, reboot, and more time. It will eventually work

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] pontonn:
Setting to change battery from text to icon appears to be broken. Anyway to accomplish this via ADB?
[Captivate Android Development] pizz0wn3d:
Read the OP Changelog and "Known Issues" section. It's not that difficult.

Herp derp Captivate XDA Premium.
[Captivate Android Development] pontonn:
Not trying to report a bug. Just wondering if it can be changed elsewhere?
[Captivate Android Development] pizz0wn3d:
Perkamod has a couple of different battery mods I believe, but you'll have to wait for him to update his mod. I also believe that the percentage battery was unintentional and will be reverted in the next update. Search the thread, the battery % has been discussed already.

Herp derp Captivate XDA Premium.
[Captivate Android Development] drawde40599:
rom

Had send in my galaxy nexus in for warranty so back to captivate, installed this cm9 from and I almost forgot I wasn't on my GN ( nice job!! ) I'm on att here in alaska flashed this from from 100% stock phone so I have the jl3 radio, what radio are most using now?? There just are two many radios for the is phone to actually test for myself . ( crazy how many radios out there for this phone )
[Captivate Android Development] jswclw:
First night to charge on build 15, charge death. Judging from the battery graph, out only got about 5% into the charge. Bummer!
[Captivate Android Development] dabels1961:
On 14 I had no sleep deaths, but now on 15 I have had 2. Stock kernal, one running on conservative performance setting and once on ondemamd setting.
[Captivate Android Development] alphahere:
Charge Death lives on with Build 15

Charge Death on build 15 every night.

Reverted back to nuskor's kernel and sleep death is gone. I have been trying to compile this kernel from source but the phone won't boot with my compile. Other kernels I compile run fine on the cappy, so it is not my setup. Does anyone know how to compile nuskor's kernel from source, or have a link (I did do the google thing before posting)? Sorry to post this in the thread about something that was not stock but I thought this might be helpful for others.

Anyone with charge death should give it a try. Make sure you run a script to clean out any left over modules or scripts before installing. Nuskor's kernel or playtypus kernel cannot install CM9. The big downside with nuskor's kernel is you must revert to stock kernel before updating your rom. :confused:

One other note with playtypus kernel charge death occurs about 10 minutes after connecting to the charger no matter how much charge the phone has.

Nuskor's Kernel

http://ics.darkirc.me/stable/
[Captivate Android Development] pawitp:
How to Report Charge Death on BUILD 15

- Did you have the problem on BUILD 14?

- Did you have the problem on BUILD 14 + test2/test3 kernel?

- Are you running Captivate GB bootloader? (If not, what bootloader are you running?)

Also report if build 15 fixes charge death for you (and mention your bootloader)

Note: It's not trivial to check what bootloader you are running, but it's the version of the latest ROM you've flashed via Odin which contained boot.bin and Sbl.bin.
[Captivate Android Development] aHecticLife:
Oh okaay thankss for the reply ! And for #3 yeah i was. (:

Probably just a bug, we'll wait and see :)
[Captivate Android Development] jswclw:
Had charge death on build 15, stock kernel. Also had them on 13 and 14. using i897 boot loaders. Test kennel 2 seemed to help, went from 7/7 charge deaths on stock to 1/5 charge deaths with test 2.
[Captivate Android Development] mcala:
Never ever had a charge or sleep death! I joined the bandwagon at build 13. Phone build date is 1012.

I897 G/B boot loaders, Stock default THS kernel!

What is not stock is my battery, it has been updated to an 1800MaH Epic 4g Touch's battery.
[Captivate Android Development] zmore:
Charge death datapoint

FWIW: I have NEVER had a charge death with any CynogenMod ROM, using either the USB or the higher-amp A/C charger. I've also never changed my bootloaders (still using the ones that came with Eclair) and am still using the original 1+ year-old battery.

I have only had the very rare sleep death, which is a separate issue. All the people having charging deaths are due to what? A finicky overheating battery and/or over/underclocking? Has anyone recently swapped battery variables to test?
[Captivate Android Development] singlebeam:
Not a bug. The rest of us connect to Google servers just fine.
[Captivate Android Development] cjpp78:
Never had charge death on build 13 or 14. Had charge death for first time last night on build 15. I've been on i9000 gingerbread bootloaders on all builds 13-15.
[Captivate Android Development] Abaddon:
I used KK4 via heimdall to flash gingerbread and it's bootloader then from there to build 14 and 15
[Captivate Android Development] nyciz:
Glad it did, hit the thanks button and the next person that reports the same issue, share the knowledge.

Peace
[Captivate Android Development] alphahere:
Charge death report.

Charge death report

Phone - build: Captivate - build 1010

- Did you have the problem on BUILD 14? Yes

- Did you have the problem on BUILD 14 + test2/test3 kernel? Yes

- Are you running Captivate GB bootloader? (If not, what bootloader are you running?) Captivate GB bootloader currently using UCKK4 and was using UCKF1 and had the same problem. Will try eclair again if this will do any good.

Also report if build 15 fixes charge death for you (and mention your bootloader). No build 15 did not fix the problem - Charge death lives on with build 15.
[Captivate Android Development] Rabidaries:
Hey guys, coming over from icssgs from to try things out and read the last 25 or so pages and didn't see anything regarding my issue, my main clock in the status bar is on 24 clock. When I go into settings and click on date/time I get "unfortunately %1$s has stopped working" any fix?
[Captivate Android Development] kublis:
None here to report. Had it charge over night. Everything stock with no changes. Came from could 14. Don't remember if I had sleep charge with 14.

Sent from my SGH-I897
[Captivate Android Development] Mauijpm:
Charge death report

Phone - build: Captivate - build 1007

- Did you have the problem on BUILD 14? No

- Did you have the problem on BUILD 14 + test2/test3 kernel? Did not flash because I had no reason to. Up until build 15, I have used six different builds without experiencing the charge death.

- Are you running Captivate GB bootloader? (If not, what bootloader are you running?) No. I am running the Galaxy S GT-i9000 GB bootloader, while everything else on the phone is stock.

Also report if build 15 fixes charge death for you (and mention your bootloader). No build 15 did not fix the problem. Build 15 actually brought on the problem. Bootloader is i9000 GB and it has not caused any issues previously with any of the prior builds.
[Captivate Android Development] kangi26:
Charge death report

Phone - build: Captivate - build 1008

- Did you have the problem on BUILD 14? ONLY when I flashed Glitch v14 ice

- Did you have the problem on BUILD 14 + test2/test3 kernel? No, but I didn't flash test 3

- Are you running Captivate GB bootloader? (If not, what bootloader are you running?) No, I ALWAYS come from JF6 stock

- Also report if build 15 fixes charge death for you (and mention your bootloader). I have not had any issues at all with Build 15 Stock. Again, came from JF6 stock.

As a side note, the ONLY time I have ever had charge death was when I ran GB, and it happened regardless of which GB ROM I ran
[Captivate Android Development] drawde40599:
Nobody has any comments on what radio there using?? Also calendar sync is not working I've tried few different ways I found on here, including the file from first page still can't get working, anyone have 100% way to fix this?? I also noticed the quick controls dont always work in landscape (browser labs setting )??
[Captivate Android Development] wash23:
Thanks button was hit. Made reply to notify next person that it worked.:D
[Captivate Android Development] apbthe3:
I have always come back to KP1, but have also had good luck with KG3 and JJJV5.

I believe the most common solution for calendar sync is to reboot into recovery, wipe cache/dalvik, then flash CM9 and then gapps without rebooting in between. Don't flash the fix unless you actually have issues (which you hopefully shouldn't).
[Captivate Android Development] codeblue315:
Charge death report:

Was not using Build 14, came straight to Build 15, sorry not able to answer both questions pertaining to that.

Came from the other ICS ROM, flashed to JF6 stock, installed Build 15 on top of that.

Had sleep death 2 nights ago, where the phone was unresponsive by using any buttons. Flashed latest Icy-Glitch kernel, phone ran perfect, charged overnight, then this morning it was charge death, and phone rebooted using the power button.

Hope this helps :)
[Captivate Android Development] Dr. aLkoo:
build 15 fix charge death with glitch v14 ice kernel ?
[Captivate Android Development] drawde40599:
Thanks, but for calendar fix that was very first thing I tried, didn't work . Strange there a flash fix that dose not work? I even try different gapps from other cm9 phones nexus s and Gn didntbwork so guess its the rom
[Captivate Android Development] mcnutty:
If you are running glitch, go to the glitch thread and ask whatever you want. Just keep your glitchy crap out of this thread. This has been mentioned over and over to the point that the devs had to ask people to stop asking questions if they aren't running the release the way they intended it.
[Captivate Android Development] singlebeam:
Just re-posting for those that don't read anything but the last page :D
[Captivate Android Development] raz123:
TV Out?

Is TV out working for anyone here?

Tried build 15 with default kernel, definitely broken for me.
[Captivate Android Development] b-eock:
This isn't the dedicated Q&A forum. Go HERE
[Captivate Android Development] sinichi21:
try reflashing the rom i got this before when i tried to flash a systemUI which is not made for the build or try to replace the systemui.apk that come from the rom give permission and see if it will be fix.
[Captivate Android Development] Clark Joseph Kent:
Seriously?!?........Maybe a scan back to page 1....and do lil reading...
[Captivate Android Development] nyciz:
Been on Build 15 for a weekend and would like to report other than losing my progression in a few games (&yea I used TiBu), ROM seems steady. I've never had a COD or SOD issue but I think its cuz how I load.

I always do the following (even though its more work up front but less false bug report later on):

-wipe all 3 (if u dont know what that means u havent read jack)

- data factory reset (backup all u want to keep b4 hand)

-flash to Stock (plenty of 1Clicks w/ BL & CWM inc, i use a GB that the Odin also has Master Clear)

-boot phone then click Master Clear (positive this is why I lost my game progressions but better to start fresh)

-reboot to recovery (aint u glad you used a 1Click that had CWM :D)

-wipe all 3 (c note above)

-flash THS ICS Build 15 and without rebooting flash gapps +gapps fixer+su fix

-reboot phone

Good Luck....when things start going wacko - reflash!
[Captivate Android Development] mcala:
Can you post a link please to the kk4 heimdall. Been looking but could not find it in the 1click sticky thread.
[Captivate Android Development] raz123:
I searched. Tried two TVs here, display was totally out of sync. Even just browsing the home screen.

Why so aggressive? Jeez, if you have the answer, provide it.
[Captivate Android Development] shaker2k:
I came from cyanogen 7 to build 14. did "WIPE (wipe data/factory reset + wipe cache partition)". had no problems with it except for the common ones like market and calander(fixed by flashing gapps 7.1) and the wifi acted up a few times.

I flashed to 15 without doing "WIPE (wipe data/factory reset + wipe cache partition)". the only thing I had to do was flash gapps 7.1(did this immediately after flashing 15 before resetting) and the superuser fix.

I have the i9000 bootloaders.

I think that the problem might be with the captivate bootloaders from what I have read.

I've had no charge deaths or sleep deaths. It runs like a dream! Everything is working great!

Good luck to you all and Teamhacksung rocks!

You had all better donate when this is finished or I will find you and bleed the donation out of you!!

P.S the search this thread button is your friend!!
[Captivate Android Development] Gromlakh:
Seriously, what's all this business with people suddenly Master Clearing left and right? Do people not realize that Master Clear is a complete waste of time, causes a ton of problems, and couldn't possibly fix/prevent any problems that just doing a quick wipe/flash wouldn't already solve?
[Captivate Android Development] kangi26:
I've been MC'ing since the very first custom ROM flash. If you're going to make statements this big/broad, please explain

WHY

it's a waste of time, and

HOW

it causes tons of problems, and couldn't possibly fix/prevent any problems that just doing a quick wipe/flash wouldn't already solve
[Captivate Android Development] zuN!:
Bug report:

Build 15

Stock and Glitch kernel

With DSP manager enabled for my headset, my music consistently stutters with my screen turned off. I've changed and disabled certain factors in the DSP manager for the headset but there are still frequent stutters. All stutters are gone if I leave my screen on or if there aren't any DSP manager settings enabled.

Can anyone else confirm this?

Sent from my SGH-I896 on Pre-CM9
[Captivate Android Development] kangi26:
What are you Enabling? Compression/Bass Boost/EQ?

I have the EQ enabled and I don't have any stuttering, screen off or on
[Captivate Android Development] zmore:
If you lost game progress, then you were probably only backing up new&updated apps. Always safer to do a full "forced redo" backup, or "redo for modified data" for all apps before a ROM install - that way the modified data for all also gets backed up.

(btw - I would like to think it was my email prodding that got the "backup for modified data" feature added a while back, but there were probably many others hounding them for that too. :) )
[Captivate Android Development] Gromlakh:
Master Clear wipes the SD card. Nothing on the SD card will cause ROM instability or any other problems with the actual operation of the OS itself. Assuming you have problems with things post-flash, it's not going to be because of something on the SD card, it's going to be because of a bad flash, corrupt data, etc. on the phone itself. Hence, waste of time.

It causes problems as listed above when you have games and other apps that store their information on the SD card. If you MC, you just needlessly wiped necessary files for those apps. If it's a game, you lose whatever progress/high scores you had saved. If it's an app, you lost all your preferences. If its' TiBu, you just lost all your backups. If it's CWM, you just lost all your working nandroid backups. Also, if you store a lot of music or pics on your SD card, also gone. Those would be problems.

I would assume that MOST people who have decided to use Master Clear for whatever reason are backing up the contents of their SD card before using it, or at least the parts they know are important. But, if you miss something you didn't realize was important, it's now gone. I have about 4 gigs of music and video on my SD card. Transfering that to/from my computer isn't immediate; it takes a long time. And all for something that doesn't affect the operation of your phone at all.

Flash to stock occassionally to force the installer to do a "full wipe"? Understandable if you're having problems that nothing else is resolving, since the CM installers are generally not "full wipe" installers.

Cache/dalvik wipe? Highly recommended, and even if it wasn't actually necessary your system just rebuilds them on the first reboot anyway so nothing's lost.

Doing the "wipe/wipe/wipe/stock/wipe/wipe/wipe/master clear/wipe/wipe/flash/wipe/wipe/wipe" dance that I've seen like 12 people post about in various threads over the last week or so? Seriously, there's so much redundancy and time wasting in there it makes my brain hurt. Unless you're selling your phone, there's never an occassion where a Master Clear should be the recommended course of action.
[Captivate Android Development] zuN!:
Compression, EQ, and virtual room effect. I forgot to disable virtual room effect during the whole testing so I'll report back when I have the chance

Sent from my SGH-I896 on Pre-CM9
[Captivate Android Development] aHecticLife:
Oh weird... Does the wifi and singal bars turn blue for you?
[Captivate Android Development] GRACO:
Same here, I disabled DSP and started to use voodoo sound....
[Captivate Android Development] aHecticLife:
Damnnn Team ICSSGS got everything working :| Transfer Speed, videos effects, Battery life, everything :O , i hope THS fixes this immediately ! (:
[Captivate Android Development] singlebeam:
Yes, everything works as intended. I've never had any kind of problem with Google server indication on CM9 Builds 1-15.
[Captivate Android Development] Gromlakh:
If your bars aren't turning blue, it's probably either a connection issue or (more likely) a gapps issue. You probably had a bad flash of the gapps package.
[Captivate Android Development] aHecticLife:
Oh okaay will try it out thanks :D

Hey do you know if theres going to be a transfer speed fix , video effects fix and etc on the next build ? Because Team ICSSGS got everything fixed and im jealous lol :(
[Captivate Android Development] singlebeam:
You have posted twice on the same page about something not constructive to this thread. There is a Q/A thread that welcomes questions of that sort.

Well said, sir. I constantly see people say they will "wipe data/factory reset" followed by formatting /data /datadata /cache. Do they not pay attention to the log when wiping?... it performs all of these things except formatting /system.
[Captivate Android Development] pawitp:
So it seems like everyone who started experiencing charge death on BUILD 15 are running I9000 bootloaders. BUILD 15 includes kernel changes which fixes stuff for Captivate users (with Captivate bootloaders), so I hereby declare that I9000 bootloaders are unsupported and unrecommended.
[Captivate Android Development] b-eock:
Thank you :D for finally saying what I have said :D
[Captivate Android Development] xxsxx:
Hmmm. Out of the three cappys at my house the two with i9000 bootloaders are fine, the one with kk4 bootloaders (mine unfortunately) gets charge death. It only started with this most recent build (all stock THS kernel, etc).
[Captivate Android Development] bentonhall:
Just wanted to report so far on build 15 I've had one reboot during a phone call. Last build with no reboot during calls was build 11. I've never had charge death or sleep death. Stock kernel, KK4 boot loaders from b-ock's heimdall one click. Phone is build 1006. For what's its worth on build 14 and icy glitch b1 I had no reboots.

I did however notice an improvement in battery life on build 15 with the stock kernel. I have 12 hours on battery with 3 hours of screen time and 1 hour of phone calls and have 8% left. Usually get around 6-8 hours with that usage.
[Captivate Android Development] iluretar:
I just got my 3rd charge death with build 15 , I'm using everything stock with jvt modem and stock jf6 boot loaders, I switched to cm7 when gb boot loaders were not supported and never felt the need to upgrade, maybe it's time to do so. Is this caused by my old bootloaders? Is there any log I can supply to check?
[Captivate Android Development] voldomart13:
I was checking it out the only thing that turns me off about this rom is I have to flash GB bootloaders. Ive lost 2 captivates to failed bootloader flashes. I think this rom will stay supreme because of the ability to flash without a specific bootloader.
[Captivate Android Development] shaker2k:


Ok I'm using the i9000 bootloaders and have had no problems. Should I switch to captivate bootloaders even though it's working fine on i9000?

If I switch to the captivate bootloader can I just flash them and go, or do I have to reflash the ROM add well?

I've read that changing bootloaders can be tricky.

This post is why I'm frankly scared of trying to change my bootloaders

http://xdaforums.com/showthread.php?t=1129821
[Captivate Android Development] galakanokis:
I have seemed to have lost the ability to send MMS messages. Worked fine on 14. Everything stock. Should I try a reflash or something else? APN looks fine.

Sent from I896 running ICS
[Captivate Android Development] ptesmoke:
is there anyway in knowing or checking which bootloaders one has? im pretty sure the last thing i flashed with bootloaders was a stock rogers gb rom. so i should be on captivate gb bootloaders right?
[Captivate Android Development] mcnutty:
Not sure what people think this build is missing, but holy battery life Batman! Not sure what you guys did with the kernel, but this is the best battery life i have ever gotten...

Edit: on froyo bls, never had a sleep death, run screen at minimum brightness usually to make it through the day

Sent from my SGH-I897
[Captivate Android Development] voldomart13:
What are your CPU settings? And which kernel are you using? stock or icy glitch
[Captivate Android Development] Nick0703:
Yeah, you have GB Bootloaders (I896 Version). You're good!
[Captivate Android Development] mcnutty:
Fully stock. No tweaking other than screen brightness set to minimum. On stock battery with an exchange and gmail account on push.

Sent from my SGH-I897