yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Johnston212:
Hey, I just wanted to check and see if anybody was noticing these bt problems as far back as 34. I've noticed a weird glitch with regards to music playback. When I powered down my s9 w/o pausing music and then connected my T9, music would playback through the speakers until I reset my phone. I just recently had to reboot because I powered down the s9 and then went to play music from the speakers and even at max volume it could barely be heard with the speaker right next to my ear. Again, problem resolved upon reboot.

I just want to know if this is something that others are experiencing. I may flash back to 32 or 33 tomorrow, just to be safe.
[Captivate Android Development] markdexter:
Anyone know how i can enable 3g only? I am on Rogers, and ive been saving battery by having phone on Edge network 2g,( so i can still receive email) but, I still sometimes would like to browse market or the internet, Edge is like Dial-up!!

To switch back to 3g or H, i have to go into settings turn off mobile data, turn off 2g only, turn on airplane mode, turn off airplane mode, then select mobile data again, it does work, just a pain in the ASS!!,

I know 3g wont be great on battery either, but better than Hspa.

By the way i have the JL2 modem, not that makes much difference.
[Captivate Android Development] pvr:
I believe you will have to flash a Samsung ROM and from there use the secret code to disable HSPA (D/U) and then flash back to CM7.

Again, this could be it but honestly I am not sure. Aside from little battery performance gain I guess it'd be helpful if your connection keeps failing because of HSPA or (in my case) even though I have HSPA/3G my connection is limited to 300K (seriously).
[Captivate Android Development] bdbsubscribe:
my phone has been doing this recently as well - ill get the 'complete action using dialogue' with either email or email for no reason whatsoever and i know its time to flash again. After that pops up the first time EVERYTHING starts force closing within a day or so

this usually occurs every 3 or 4 days.
[Captivate Android Development] kurrptsenate:
My black screen of death (knock on wood) seems to have sorted itself out after 2 days! YEA!

What app have people been using for their camera/video. The stock one with CM7 leaves a lot to be desired unfortunately.
[Captivate Android Development] jhernand1102:
Bluetooth Still Broken

Just a heads up, I flashed nightlie #38 and the bluetooth is still broken. Back to #33 for me.
[Captivate Android Development] Johnston212:
The MIUI camera apk that somebody posted about 4 - 5 pages back is actually pretty decent. Camera 360 is also a good option
[Captivate Android Development] aHecticLife:
Does anyone have the problem where their Captivate shuts off completely when they try to overclock it ?
[Captivate Android Development] veener79:
#38 I am able to get BT to turn on and stay on. On lunch going to see if it will work with the car.

I did have to reboot to get it to turn on and stay on.
[Captivate Android Development] Palmetto_X:
http://xdaforums.com/showpost.php?p=14965348&postcount=8788
[Captivate Android Development] shaolin95:
This thread is only for stock kernel. Ask in the one for the kernel you are using. You are either going beyond what your phone can do or perhaps too much UV.
[Captivate Android Development] Yaantra:
So is #38 a RC for our phones too as the change log suggests?

So far have had no issues with #38...
[Captivate Android Development] jhernand1102:
No it's not an RC, have you checked your bluetooth to see if you can connect to anything. It would not work for me, it would turn on but not connect so I flashed back to 33 and all is good.
[Captivate Android Development] bluestevo:
Nightly 38 and 37 the alarm sound doesn't work.
[Captivate Android Development] veener79:
Just got done playing will not connect. Only will turn on. :(
[Captivate Android Development] jhernand1102:
Yeah it looks like when the changed to the new pre-built kernel it broke the bluetooth. The thing is we can't report bugs on the nightlies so how it is ever going to get fixed if we can't report it. Oh well at least #33 has been working great for me and I can always keep trying the latest nightlies to see if it ever gets fixed.
[Captivate Android Development] techmik67:
It'll get fixed ... you know, they read this too, ..... an official bug report is hardly the only way things get fixed
[Captivate Android Development] OkNewMedia:
Bluetooth works great with the Glitch kernel.
[Captivate Android Development] Johnston212:
I had Glitch running on 37 and I still had some BT issues. I'm not sure about trying out 33 or 32, so I may stay at 31 for the time being.
[Captivate Android Development] bluestevo:
38 nightly I'm getting no ring tones or txt notifications sounds. Going back to 35
[Captivate Android Development] melbourne408:
Odd I've gotten plenty of email notifications and texts all morning without a problem, running #38 atm.
[Captivate Android Development] bluestevo:
im not sure what the deal is, ive checked all settings, but getting no sound at all :( the speaker phone dont even work :(
[Captivate Android Development] bentonhall:
I reverted back to #34 and can confirm Bluetooth works fine with the stock kernel.
[Captivate Android Development] aHecticLife:
I'm using the cyanogen kernel, and I heard several people were having the same problem too.

Btw, whats the limit for the Captivate ?
[Captivate Android Development] EnemyOfGlaDOS:
Limit :rolleyes::p.. not sure really. As long as your phone doesn't feel like it's gonna melt and your stability tests are passing without crashes or freezing.. then your pretty safe. :D But really, if your phone is staying cool..and your stable... then your good.

...btw, a couple of us have been able to hit and run @ 1.7GHz testing beta kernels ;)
[Captivate Android Development] Haloruler64:
Stock Cyanogen kernel has no OC though
[Captivate Android Development] skatcat31:
There is an app that allows you to OC stock kernels. It's in the market, and requires root. It was posted in the dev sections awhile ago, but got moved IIRC. To where IDK.
[Captivate Android Development] bluestevo:
okay im having some weird problems, idk if its my phone or CM7,

flashed 38, didnt have any external sound at all and the USB wouldnt connect so i cant connect to the computer.... so i reflashed, didnt help,

went back to 35, still didnt help, flashed back up to 38 and still no sound or USB.

BUMMER
[Captivate Android Development] skatcat31:
backup to dropbox through tibu, oneclick stock, factory reset, install CM7, factory reset, re partition, download your backups, restore, good to go.

yes it's involved, but the only 100% certain way to prevent ALL problems
[Captivate Android Development] bluestevo:
the usb isnt being detected. whenever i plug it up to the computer it just charges, doesnt state its connected USB :( so i cant
[Captivate Android Development] z28james:
It looks like they are suggesting you "one click" odin back to stock which is done in download mode. I'd personally suggest something like this:

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

This does not flash bootloaders.
[Captivate Android Development] bluestevo:
the problem with that is that it wont connect usb, it will connect using Debugging, but not normal USB.... any ideas?
[Captivate Android Development] z28james:
You are doing this while the phone is booted into the OS?
[Captivate Android Development] bluestevo:
ive went into download mode, pc wouldnt detect phone.... and while the phone is booted in the OS, my pc still doesnt detect the phone, all drivers are up to date.... before flashing the latest nightly i even moved files over from my phone so something with this update or something in between has messed up.

i restarted the computer and it seemed to work. idk whats going on... thanks for the help everyone flashing back to stock, then back to CM7
[Captivate Android Development] tarheelblueboy87:
So, does anybody else on build 37 have cpu governor problems on boot? Upon every boot, the governor acts like its set to performance, until I lock and unlock.
[Captivate Android Development] redeuxx:
Why do I get infinite reboots when trying to update to #38? It seems like it goes into CWM recovery to install something but then fails and reboots. I can't read the messages fast enough.

I can install back to #32, but would like to update.

Also, on #32, why does my phone not detect that I have root?

Much thanks!

Any help would be greatly appreciated.
[Captivate Android Development] esancakt:
which nightly so far did everyone think was the best on battery?
[Captivate Android Development] prayii:
If you go back into CWM and reflash #38 after it starts doing that it will boot up fine.

Also - just saw this in the changelog for those interested
[Captivate Android Development] veener79:
I am having this issue too. When I go to install a ROM from ROM Manger it reboots and after the ATT screen it goes into ROM manger and then there is a message that goes away too fast to read. Then it reboots to the ATT screen again. But it just goes back to a normal boot with out loading the new Rom.

To install the rom I need to reboot to recovery and select the zip and my phone updates.
[Captivate Android Development] CougarBroker:
Try a different USB ports.
[Captivate Android Development] hkk:
Thanks for the reply. Did try the factory reset, but doesn't seem to help.
[Captivate Android Development] tarheelblueboy87:
None of them have very good battery life right now, not sure when that will change. Changes are pretty incremental a lot of the time. Hope the battery issues go away soon tho, but

I feel like once you go CM, the performance boost over stock is worth the drain. I am confident that these amazing devs will fix things in the near future, I'm on for the ride now!
[Captivate Android Development] Haloruler64:
If you use that to go back to stock from CM7, I think it'll brick your phone. You need to use original one click, from what I've heard.
[Captivate Android Development] z28james:
Hmm..perhaps if you forget to check "re-partition"?
[Captivate Android Development] atinm:
That's right - original one-click does the repartition with correct pit file automatically. If you want to use standard Odin, you need to specify a pit file and check re-partition.
[Captivate Android Development] veener79:
After intalling 38 my phone gets stuck rebooting. After the install it goes into Rom manger. I see there is something about E but it goes away so fast I can not read it. I went back to 33 and my phone works fine again.
[Captivate Android Development] atinm:
Try just reinstalling #38 twice and let me know if it works.
[Captivate Android Development] markdexter:
once again we have a newer stock kernel with the latest nightly. Wolverine Kernel.

Anyone able to give any battery usage reports yet?
[Captivate Android Development] comdei:
Is #39 safe to flash? I'm on the build from 6-15 I dunno what number now I lost track
[Captivate Android Development] veener79:
That seamed to work. :)

Any idea why I can not install updates form Rom manger and I have to go into recovery to install all my downloaded roms. Last issue I have left.
[Captivate Android Development] comdei:
You need the premium version for that
[Captivate Android Development] parshantx:
haha yeah, i wasn't sure either! thanks for uor help guys! :D

i love this rom! buti have one question kinda.

when u hold home to bring the multitasker, in galasy s roms, there's a "end all" button. there isn't one in this rom, or the nexus s roms.

anyone have any better ideas to end all tasks? thankkks!
[Captivate Android Development] prayii:
So do the latest nightlies require double flashing for some and not others because of bad blocks we got during a previous flash?
[Captivate Android Development] Killemalll:
Flashed #39 through Rom Manager. All went smooth and everything is working so far. Including the BT. Which, by the way, was at least for me perfectly functioning on Nightly #38 as well.
[Captivate Android Development] peachpuff:
Any reason why this happens? Seems you also have to reinstall gapps after every nightly install.
[Captivate Android Development] Johnston212:
Just jumped from 31 to 39 and everything is looking good so far. Will be trying out BT and maybe even GPS in a few minutes. I also wanted to check and see if Glitch V10 was working with 39 or not.
[Captivate Android Development] sixstringsg:
Try paosting kernel questions in the kernel thread, on the glitch thread it has already been confirmed that 39 works just fine.
[Captivate Android Development] aHecticLife:
LOL, alright i'll try and get back to you :D
[Captivate Android Development] Jusrertiner:
On nightly 30 having constant force closes of everything. I reboot it have it happen again 10 mins later. I fix permissions many times n have cleared cache
[Captivate Android Development] veener79:
Same BT works for me and after installing market place again I am set and back up and going with #39 after doing the install twice with Rom Manager. Rom looks greats and feels smooth so far. I am noticing I am getting a extra bar and some times two at home with these last few buillds and my battery is better.
[Captivate Android Development] EsotericSYN:
For some reason I cannot flash between cm7 and miui anymore. Now the only way to get cm7 is going stock and starting fresh. Does anyone have a fix for this?

Sent from my I897
[Captivate Android Development] Johnston212:
Sorry, old habit, but thanks. I also want to report that BT is working fineish. Having a few glitches here and there, but nothing too bad. Also, GPS seems to be working good still compared to before. Not sure about battery life yet, haven't had a chance to calibrate.

Just out of curiosity, but does JK4 still have a reputation for bad battery life? It's been a while since I used it and just wanted to make sure about that detail now that I am using it again. Thanks.
[Captivate Android Development] CougarBroker:
Force Close

I am getting constant Google System Framework force closes, should I flash back to stock and start over? Any suggestions? I am on #39 btw.
[Captivate Android Development] tiuk:
Open a terminal, type df, see how much space there is in datadata. If it's full it will cause that. You can move your larger apps (like games) to sd to free up space.
[Captivate Android Development] CougarBroker:
it is only 49%, I have all apps that I can on the SD except gtasks and business cal. It happens a lot when I am in Facebook and Contacts.
[Captivate Android Development] sdconvoy:
I hope this isn't completely ignorant of me, but after flashing 39, some of my apps are missing, and my market doesn't work. the icon is there, but it opens up a white screen and immediately kicks me back to the homescreen.

am i missing something obvious here?
[Captivate Android Development] Haloruler64:
Reflash gapps, it happens.
[Captivate Android Development] sdconvoy:
I reflashed g apps, but no fix. One thing I noticed is that I don't have gmail under accounts any more
[Captivate Android Development] Haloruler64:
Do you have the absolute newest gapps? Download them from ROM Manager, the free version works. Maybe that'll help
[Captivate Android Development] bentonhall:
Download Cache Cleaner NG and give it a try.
[Captivate Android Development] aHecticLife:
I just restart my phone and its back to normal :)
[Captivate Android Development] sdconvoy:
tried that, no avail. reflashed rom, reflashed g apps... Nothing seems to work, even flashing to an older version
[Captivate Android Development] bluestevo:
i went back to stock from CM7

getting a replacement thru warranty.

is there anything else i need to do before i send it back to them so i wont have any trouble?

Thanks.
[Captivate Android Development] Haloruler64:
Wipe the internal SD!
[Captivate Android Development] TheTodFather:
I had a friend who didn't have recovery when he originally got his captivate so he had to do the 3 button combo fix. (uboot fix?) . He's been flashing nighlies with no problem till nightly 39. Unlike me i had it to boot loop from recovery to att screen over and over but i was lucky enough to get back into recovery, where as he can't. Download is not working as is recovery so it just bootloops. ADB recogizes it but then it boots back out into the endless loop , once again.... Any suggestions. I'm pretty sure it bricked. I guess we can go to radio shack and make a jtag. LIke I said any suggestions appreciated. Thanks

Did this somehow remove change the uboot/ 3 button fix/ bootloader whatever you call it. As far as i know nothing touches the bootloader. Hmmm,
[Captivate Android Development] EnemyOfGlaDOS:
Its not bricked.. if it was he would see NOTHING. However, a "jig" may help him to get into DL mode.
[Captivate Android Development] TheTodFather:
Technically yes till we get a jtag
[Captivate Android Development] littlewierdo:
Regarding CM and battery life, I think I have discovered (with the mention of it from several others) the source of the horrible battery life.

It isnt CM, its Google Maps (or at least appears to be that for me).

Last night before I went to bed, I used an app called Autostarts to disable all of the conditions that Google Maps starts under (so now it only launches when I click on the icon to launch it).

This morning, I unplugged from the charger and my battery life was only 'slightly' worse than Cognition 4.5.3 (instead of ending the day at 35% when I was on Cognition 4.5.3 with all of the conditions Maps auto starts under disabled, I ended around 25% on CM with all the conditions Maps auto starts under disabled using the latest CM #39 build).

Consider if you can live without it for a day, uninstalling Google Maps and see if that works, Id be curious to see if this is just a fluke or if there is a real problem with Maps.

Or, alternatively, if you have the money to buy Autostarts, try switching it to app view (hit the menu button when the app first launches and finishes loading and select App view) and scroll down to Maps and uncheck every option for maps. Dont worry, this will still allow Maps to load manually but will keep it from running in the background as long as you kill it after you are done using it.

I think the devs may not be hugely concerned about battery life because the battery life is acceptable if you are running CM with no apps installed - even google apps. My guess is, the hardware they are working with is a 'cleansed' device with nothing but CM and the apps it comes with (they probably arent even using anything included with Gapps).

And comparing CM with the most battery efficient rom out there for the Cappy (Cognition 4.5.3 - the Froyo based version), it seems to be plenty acceptable.
[Captivate Android Development] EnemyOfGlaDOS:
I could be wrong, but I think JTAG is for completely bricked phones..as in NO sign of life, black screen, natta. They phisically open the phone up take out motherboard to flash. A JIG will force the phone into DL mode from a powered off state. I think that is what you need.
[Captivate Android Development] Haloruler64:
JIG will save you. Saves anyone who has a phone without 3 button combo and can still power on their phone to some degree. Google it, they're either cheap or dead easy to make :)
[Captivate Android Development] EnemyOfGlaDOS:
Oh I know all about them..I have one. I was talking to thetodfather who thaught he needed JTAG.
[Captivate Android Development] Haloruler64:
Oh, I was clarifying and expanding on what you said, not for you but for the person you quoted. You're a pretty knowledgeable guy :)
[Captivate Android Development] markdexter:
I had the exact same Issue, had no 3-button combo, JIG was my only solution, i got the parts (3x100ohm resistors) from radioshack, put it together, and got into download mode, I then ordered one off Mobile Tech Videos, just for piece of mind!!!

Very easy to make though, actually check my Sig, the vid is in there.
[Captivate Android Development] EnemyOfGlaDOS:
Oh haha :) yeah a jig is a handy thing just to have around. I love mine ..and thanks btw :)
[Captivate Android Development] littlewierdo:
Just to clarify, the ONLY thing a jig will not save you from is mismatched bootloaders (and/or incorrect bootloaders).

In short, if your screen comes on, you are in luck, a simple 300 ohm resistor across pins 4 and 5 on a micro usb connection will put your phone right into download mode. If you cant get the screen to come on, you need to get a replacement phone or repair your existing phone by sending it to Samsung. JTag will also fix it (I ordered a JTag kit to fix one of my four cappies).

The easiest way to make a jig is to order a USB micro breakout board (this is basically a board that has holes for all five pins on a usb connection with a micro usb connector), order a 300 ohm resistor (or 3x100 ohm resistors and solder them all in one long circuit) and loop one end of the resistor into pin 4 and the other end into pin 5.
[Captivate Android Development] pvr:
I will test this today - Have to reflash my Cappy anyways so will keep Maps off of it but only because I've heard this story before about Maps being a huge battery drain as it starts some background stuff.

Will report back by the end of the day :)
[Captivate Android Development] rschenck:
CM7 Captivate Users!

In order to help us all keep track of CM7 Nightlies, a community wiki was started for the i9000 in order to share info about CM7 updates which are so frequent now that new ones seem to be appearing..well...ummm....nightly.

At the request of Atinm, the Nightly Wiki is now expanding to include CM7 Captivate users as well. You lucky dogs you.

The Nightly Wiki is there for all your Nightly Flashing questions, such as "What bugs does this one have?", or "What do I do if this Nightly bootloops?" or "Will flashing this Nightly make Peggy Ann realize that I am the only man for her and that Johnny is a no-good rat?"

The best thing about this Wiki is that all you have to do to add your own input to each Nightly report is ask to be a User. Therefore it is a one stop information source maintained by the entire community. What FUN! Thanks to everyone who have been pitching in thus far for the i9000, especially my co-admin zpon.

A new page has been prepared just waiting for Captivate users to rush in and begin filling in essential data on the most recent Captivate nightlies. All you need to do is either send me a PM asking for User access in order to edit the pages, or send a request directly from the Wiki.

Now, don't push and shove, there is plenty of room for all of you. Just aim your browsers at http://sgscm7nightlies.pbworks.com to get started. See you there!
[Captivate Android Development] atinm:
You're mostly right - we don't use many apps, but we do use our phones so we do have GApps working. It is more that we're usually hooked to the computer because we're debugging so we never have to worry about battery ;-).

But yes, background processes - especially ones that are hitting your wifi or radio are the biggest cause for battery drain (it is just radio in general really). If you can turn off your radio when you don't care - that'll save you serious battery. I actually keep my vibrant and captivate on airplane mode (as my SGS2 is my primary device now, and the other two don't have SIM cards anymore unless I'm testing them) and they last forever, leading me to blame radio.
[Captivate Android Development] atinm:
Get a jig - no need for jtag I think. Heck, even I finally went and got a jig and now I'm wondering why I didn't before (I wasn't going to go build one out of resistors and electrical tape - I like the little plugs I bought, much cleaner).
[Captivate Android Development] atinm:
Thanks!

Cappy users - please get on this, it is very nice for the devs to be able to see what the users are dealing with, without having to wade thru lots of very basic posts about "how do I?". I really love that the wiki has a section for each nightly, the problems that seem to be "general" with the nightly, and where I need to look.

Thanks.
[Captivate Android Development] Haloruler64:
If you switch off mobile data and wifi, your battery will last forever. Trust me. I turned on 3G for 5 minutes every 55 minutes, worked really well!