yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] TomMelee:
For about a week or so I was having terribad battery issues, was running Glitch latest + and nightly...I dunno...60-ish. Yesterday I went to the 8/5/11 nightly and allowed it to wipe cache/data/dalvik and did NOT add gapps to the dl list. (It still asks when it comes back, so...why bother?)

Anyway, when it came back I realized I'd forgotten to run a recent TiBu backup, but whatever, no biggie, and ADW didn't feel like recovering anything but again, whatever. First step I did in the CM7 settings section was go to PERFORMANCE and set Governor to CONSERVATIVE and not change clock settings at ALL.

I then reinstalled everything I use regularly and went on about my day. It's possible that something I had installed but didn't use was eating battery, but neither the phone's battery stats nor SpareParts had anything to tell me about where it was going, so w/e.

Anyway, I'm happy to report that my battery life is GREAT right now. No joke, in like 8 hours yesterday I dropped I think 18% and that was with some calls and texts, although admittedly not much use. Today with more use I'm still over 50% remaining and it's now been unplugged for 13 hours.

Also, in regards to flashing to stock---I was on Continuuim with "official" gingerbread bootloaders before I came to CM7. The only Odin package I could easily find put me back to 2.2, not 2.1 (Froyo, not Eclair.) I found a buried thread somewhere that even though the CM7 FAQ says you MUST be on 2.1 that 2.2 works fine.

It does. If you're running non-CM7 gingerbread bootloaders, I strongly suggest that you use one of the Odin 1-clicks and go back to original Eclair or Froyo BL's---it takes 10 minutes, why not?

I'm also sticking with the KC1 modem, before and after this most recent reflash.
[Captivate Android Development] tiuk:
Honestly I've been flashing pretty much every nightly since cm7 for sgs went public without any factory resets/back to stock/etc, just moving apps to sd when datadata gets full (mostly moved games). Using glitch's kernel (with oc/uv) and managing my apps properly I use practically no battery in standby even with background data (I work 10+ hours a day and use touchdown because this is also my work phone). I really think anyone who has battery issues just has a bad setup. Battery life for me is leaps and bounds better than any samsung based rom I ever ran, which was all the popular froyo ones from october til late january/early feb.
[Captivate Android Development] wizurdofawwz:
Forgive my possible stupidity but I tried flashing to the KC1 modem and now all I get is "Baseband Unknown." Any ideas?
[Captivate Android Development] sixstringsg:
You didn't flash the CM7 version.
[Captivate Android Development] wizurdofawwz:
Where can I find it?
[Captivate Android Development] wizurdofawwz:
I found them.

Here's a link if anyone else is looking.

http://goo-inside.me/galaxys/radios
[Captivate Android Development] melbourne408:
I wonder if it's possible to flash the bootloaders while on CM7?

My brain is fried from all these dam pythons bootlooping in my head but it would be an interesting note to jot down.

Maybe I might give it a try, ward off others if the direction bears an irreparable outcome.

I'll see what's up as the night transpires, college back in session on the 29th dreading it somewhat.

Hope your cappy's are doing well RockRatt and sad to hear :(

Cheer up droog brotha :D
[Captivate Android Development] everest.deth:
Anybody checked this? :(
[Captivate Android Development] kurrptsenate:
I was having terrible problems with my phones service on a recent update (Friday's I believe). People would try to contact me and couldn't for whatever reason. I know the updates of 2.3.5 have all been terrible for my battery life. Last nights update seem to fix all these problems almost simultaneously.

I plan on sticking with this nightly for quite some time.
[Captivate Android Development] insaneturbo13:
Did you do a permissions fix from rom manager?
[Captivate Android Development] nimper:
No, this is wrong. We don't have galaxys, we have captivate.

http://goo-inside.me/captivate/radios
[Captivate Android Development] malbolgias:
Uhmmm...

So?

Both phones have the same chip used for the modem so you can safely use i9000 modems on captivates. I personally do.
[Captivate Android Development] sixstringsg:
I'm sure he's aware he has a captivate, but I9000 modems work just fine on the Captivate. Even better than captivate modems often.
[Captivate Android Development] everest.deth:
I've tried that, tried reflashing, tried different SIM cards, and even tried a full wipe + reflash + fix p and no go :(
[Captivate Android Development] melbourne408:
Alright so its all working fine on my end here. Ended up with a fun situation last night, lets just say yea it is possible to flash the bootloaders while still on CM7, but I wouldn't advise it if you don't know how to get around a lot of walls, but ill exclude that, it does work. Ill cut out the "fun" I had and let you know how it worked for me. Step one, flash to stock 2.3.3 with Odin 1.8-not a one click.

Two, once booted up and in need of root I flashed a nice fix again from Odin, DG had put it up as a workaround.

That gave me root access, while powering the phone back on I encountered no errors.

Chose my recovery in Rom Manager then once done booted the phone off....again.

Three, phone off and back again to download mode, use Odin and flash the speedmod kernel.

From there I installed the nightly on my SD card and gapps, it was all history from there :D

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] nkrick:
Thanks for the information, I am sure it will help many people who want to try out the "official" i897 gingerbread bootloaders. I might try it if I want a "fresh start" at some point. Otherwise I will probably wait for team hacksung to come up with an "official" method, because when they do, it will probably be a single ROM Manager/ClockworkMod Recovery Flash or Odin flash.
[Captivate Android Development] melbourne408:
Do you ever show any heart?

Every post you've flopped my way comes off way tooo demeaning.

Best of luck in life you obviously own this turf hard core.

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] CVuPlay100:
Is CM7 connecting to my AT&T Microcell?

I'm apologizing ahead of time if this topic has already been covered but my searches don't seem to think so.

I have an AT&T Microcell and since using CM7, my connection only displays "AT&T" and not "AT&T Microcell". My signal strength fluctuates wildly no matter where I am from the Microcell. My call quality is also bad and it makes me question whether CM7 is actually routing calls through the Microcell. This is compared to when I was running stock Froyo - the Captivate displayed AT&T Microcell and my phone reception was noticeably better - call quality worked well and the signal bars stayed high.

Can anyone else that has a Microcell share their experiences with me? Is there something I could be doing differently?

I haven't dabbled with changing radios and would appreciate someone pointing me to a thread that gives good information on which radios work best for which regions. My baseband information shows T959TLJL3 so I'm assuming that I'm running JL3?

Right now I'm running on build #69 of the nightlies.
[Captivate Android Development] lowlymarine:
I haven't had any experience with the Microcell myself, but if I had to take a random stab at the problem, perhaps only AT&T radios will connect to it. You could try using UCKB1, the only captivate radio with a CM7 version (that I know of):

http://goo-inside.me/captivate/radios/radio-cm-7-Captivate-KB1-signed.zip

For reference the other Captivate-compatible radio packages can be found here:

http://goo-inside.me/captivate/radios

Hopefully somebody who has some experience can shed some light on this problem.
[Captivate Android Development] nimper:
Apologies, I wasn't aware they were interoperable due to the frequency differences.
[Captivate Android Development] mnjm9b:
Not sure when it changed... it used to display fine.But now it only shows ATT.

However, I know for a fact that it is connected to the microcell because I would have only one bar without it and I am always showing full signal.

It is just a display issue. Not sure how it got broke but it doesn't seem to matter.
[Captivate Android Development] nkrick:
I don't have a Microcell, but my understanding is that the network name that displays comes from the network or device you connect to. Based on mnjm9b's post which indicates that he must be connecting through the Microcell or would have no signal at all, the cause of the difference is likely the Microcell itself. Since the Microcells are linked to AT&T's network, AT&T can probably push firmware upgrades to the devices similar to how they upgrade firmware on a cell phone. A couple things you can check:

Unplug the Microcell and see if it causes a difference in your signal strength.

Test with a different phone running AT&T software (or flash to stock) to see if the network says AT&T or AT&T Microcell in order to eliminate CM as a cause.

Call AT&T and ask if they have made any changes to your Microcell.
[Captivate Android Development] nkrick:
Not all i9000 modems support the 850 Mhz band. The modems sticky in the Captivate Android Development forum is a good place to cross reference the modems to see if they will work on both 1900 and 850. However, do not download and try to use the modems from the stickied thread as they may not work in CM. I believe that some are labeled for use with CM, but they may be from the old partition layout. The best place to download modems for CM is from http://goo-inside.me
[Captivate Android Development] RockRatt:
Or make your own, it is VERY EASY. Take ANY modem you want to try and download it to the phone. Also download AT LEAST one modem from the the link just posted. Now go to root explorer and long press on the NEW modem you want to use. PICK extract. Now do the SAME with ANY CM7 modem file. Go to extracted folder in /sdcard/extracted. Go to the NEW modem file name and open it. Hold down on the modem.bin file and the select copy. Now go to the CM7 modem also in the extracted folder and open it. DELETE the modem.bin file from the CM7 modem file and the hit PASTE. This will put the NEW modem inside the file. Hit the BACK BUTTON and go to the CM7 modem file and long press again and the choose RENAME and name it with whatever the name of the NEW modem you pasted inside is. Hit the back button again and again LONG PRESS on the CM7 modem file you just created and choose zip this file. Then choose GO TO ZIP FILE. Now long press the CM7 modem file zip and press copy. Then hit the back button until you go to the /sdcard and the hit PASTE. NOW hold down the power button and choose reboot. Then choose recovery. Then when cwm opens choose install zip, then install zip from sdcard. Scroll down to the NEW modem file you created and click on it. Choose YES to install. Then reboot and your done.

I have made about 10+ modem files this way. Good luck.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] mnjm9b:
It's definitely cm7...

My wife is on stock and it still displays microcell.

Very minor issue if you ask me.

I don't care what it says as long as it works.
[Captivate Android Development] halfsoul:
My phone also stopped displaying AT&T Microcell when I went from Serendipity to CM7. My wife's iPhone still says ATT M-cell, so it's definitely CM7. I also suspect cosmetic display only, but it'd still be nice...
[Captivate Android Development] xtsuname:
I thought that it affected the strength but I realized that it doesn't matter both on stock and CM7 there is still some problems with calling using the microcell. I think the only reason why the call quality is better on stock is due to the active audience chip.
[Captivate Android Development] Kaik541:
what I've actually noticed (as I pass through an AT&T microcell entering a friend's home often) is that if you catch it *right* as it connects, it actually does briefly say "AT&T Microcell", but only for about a second or two. Once it establishes the connection, it switches over to "AT&T". I have no idea why it does this, but it does make the immediate realization it's connecting through a microcell. I'm guessing because the APN still identifies from both the SIM card and actual network connection as being the same as the "AT&T" APN, it renames it (just like Rogers users up in Canada seem to only see the numeric value of their carrier http://forum.cyanogenmod.com/topic/27964-cant-find-network-bell-mobility/ -- for us would be 310410 if I'm remembering right).
[Captivate Android Development] littlewierdo:
Sorry, don't mean to derail but when exactly did the Cappy get 'official' GB bootloaders?

To my knowledge, there are three bootloaders that 'can' be used with the Cappy (altho not all three are designed for the Cappy).

1. What are known as the 'i897 Eclair/Froyo bootloaders' that come installed with the phone (which usually has Froyo installed nowadays). These bootloaders are identical to the 2.1 Odin 1-click packages used for doing a stock restore of the phone.

2. What 'should' be referred to as the 'i9000 Gingerbread bootloaders'. These are bootloaders that were extracted from Gingerbread roms either officially released or leaked for the i9000 series phone. The key here is, this bootloader is NOT designed for use with the Captivate, it is designed for use with the international i9000 series Galaxy phones (NOT the Captivate, which is an i897).

3. The 'leaked i897 Captivate Gingerbread bootloaders' that were stripped from 'leaked' beta build roms of Gingerbread. The key here is, they are not officially released to the public yet as they came from beta builds of a rom (again, not yet released).

I should mention, there is some debate that #2 and #3 are identical. However, (although this doesnt mean anything directly), a bit comparison will show they are different from each other.

I am really quite confused as to why people are so anxious to flash to these different bootloaders. There is no performance gain and no official upgrade path (that I am aware of) from Samsung.

It seems to me, just hang out on Eclair/Froyo bootloaders... Why risk hard bricking your phone... unless... there is... some... benefit I don't know of?????
[Captivate Android Development] lowlymarine:
You must use the new bootloaders in order to use Samsung Gingerbread ROMs, and you can use them with Samsung FroYo/Eclair ROMs as well. Therefore you only need to switch back to the old bootloaders for CM7, which is irritating for those who wish to try out both.

The issue of an "official upgrade path" is irrelevant because it's not like you can't just flash any new bootloader they come out with with Odin/Heimdall as you did with the current ones. You're only flashing bootloaders if you're flashing custom ROMs anyways, so what are the chances you're going to care about an official ROM release until the devs get their hands on it?
[Captivate Android Development] littlewierdo:
Well, fair enough. It isnt worth the risk to me, especially considering I am VERY happy with Cyanogen (now that it is being treated as a serious development project), its getting plenty of updates (assuming the nightly bot is working), has more features than any other rom I know of for the Cappy, I really cant see a reason to run another rom... to each his/her own tho...

With respect to an official upgrade path, the reason this is important is, it would set a standard and finally clear up the confusion regarding bootloaders for the Cappy. I am very picky with how / what we call things, it creates alot of confusion when someone says 'GB bootloaders' with regards to the Cappy because there are two different bootloaders based on GB and they both are different. They are also very dangerous to be flashing willy-nilly.
[Captivate Android Development] CVuPlay100:
CM7 is connecting to my AT&T Microcell - but just not showing it

So after a little bit of messing around and troubleshooting (taking some of the advice offered in this thread - thank you), here's what I'm seeing.

I had turned on the setting to only use 2G networks in order to save battery since these days, I mainly use the phone where I can use WiFi. That puts the phone in EDGE mode. After unplugging the Microcell, I did notice that my signal will go to crap. It goes from -85dBm to around -115dBm - which is from 3-4 signal bars to 0.

In the next test, I turned 3G mode back on but kept the Microcell unplugged. As expected, my signal was still crappy - hovering around -110dBm.

Last test, I turned the Microcell back on. I did not notice that the phone would quickly display AT&T Microcell like one of the other posters. What I did notice is my signal strength skyrocketed up! It was now around -75dBm and showing full 4 bars.

Here's the final confirmation that I am indeed connected to the Microcell... If I go to About phone -> Status, the Mobile network type display "UMTS". Without the Microcell, this would display HSDPA instead.

All in all, I guess it's not a big deal that I don't see "AT&T Microcell" displayed on the phone as long as it's working. It would just be nicer to confirm that my Microcell was working.

CM7 rocks! Keep up the great work guys.
[Captivate Android Development] Pralix:
I have had various issues with bluetooth and CM7 (nightly & RC). Here is a list of issues:

Can't stream music over Wi-Fi annd listen over BT for any length of time. The BT connection drops and music starts playing out of the speakers (embarrasing). I can stream via 3G and listen over BT just fine. I am using the Sirius App for streaming but I don't think that is the issue here.

Can't make or accept calls while I am listening to music over BT. A call will come in, I press the button on the headset to answer it but nothing happens. THe call is answered but the phone audio is not transferred over BT. The BT button on the call screen shows that it is on. I press the BT button on the call screen so that I can hear the caller and it transfers fine over the phone speaker. The BT connection to the phone is dropped. I have to go into BT settings and reconnect to my headphones.

I have used other custom ROMs as well as stock and none of this occurs. My headset is a Dell BH-200. I really like CM7 as it has been the most stable custom ROM that I have tried so far.
[Captivate Android Development] Haloruler64:
I used CM7 for the longest time with i897 Gingerbread bootloaders. You do not HAVE to switch back for CM7. i9000 bootloaders will not work, no. Some stuff is messed up with CM7. But everything works with i897 GB bootloaders. Yes, it isn't "supported" by the CM time as far as I know, but a lot of people are running CM7 on them. So if you upgrade to GB booloaders, you can run CM7, GB Samsung ROMs, and Froyo/Eclair ROMs too. It's compatible with everything.
[Captivate Android Development] Kaik541:
i9000 GB bootloaders would work as well now, but it isn't recommended because you shouldn't flash a bootloader for another device onto your phone. external sd card is still accessible on froyo OR GB bootloaders (both captivate and i9000)
[Captivate Android Development] Dzmitry:
I am using CM with i9000 gb bootloaders for 2 days now. Everything is working flawlessly. I cant find any issues.

For those who want to know about battery life: i have 18h of life with 3h of display and Exchange, Twitter, Facebook sync enabled. I think it's a decent battery life.
[Captivate Android Development] Belaflek:
dialer is omnomnoming my battery for some reason. build 81 glitch 11 1.6oc
[Captivate Android Development] Kaik541:
custom kernel, just invalidated everything you said. we don't care about any issues people have unless you're running stock.
[Captivate Android Development] Haloruler64:
Oh thanks. Either way I think the best ones to run are i897 gingerbread bootloaders. It's compatible with every ROM available.
[Captivate Android Development] Belaflek:
gotcha thanks
[Captivate Android Development] 105437:
Call quality issues

I just flashed nightly #81 with stock kernel and radio and people are complaining about the call quality. I have tried several calls from different locations and it's the same. Any suggestions to try for scratchy, static calls?
[Captivate Android Development] nimper:
Flash a new modem in recovery. The stock CM7 modem is JL3.

http://goo-inside.me/captivate/radios
[Captivate Android Development] rivera151:
I can't turn on my bluetooth. No matter where I try to start it from (power control on status bar or settings menu), it will not turn on, thus I can't use BT.
[Captivate Android Development] 105437:
I just re-flashed the JL3 radio and call quality is much improved. Thanks!

So is there any merit in flashing a non-stock radio? Are others more capable with the same call quality?
[Captivate Android Development] RockRatt:
Jl3 is what originally came with CM7. So basically you just reflashed it. Other modems may give you better speeds and or signal. It IS worth it to try them all. Just make sure to use a CM7 compatible modem.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Thesandlord:
Some people say modem affects GPS performance but I'm not sure (doesn't make sense to me). Personally, I have been running jk4 since forever (idk why) and decided to try kc1 because people were saying it was good. Signal stayed the same but battery life was 10x worse. Quickly went back.
[Captivate Android Development] skatcat31:
Gps aids works really well (it was raining and I had a solid lock for a five hour drive). The new version works even better.

Sent from something from somewhere
[Captivate Android Development] Dzmitry:
After flashing Captivate GB bootloaders instead of i9000 gb bootloaders i have screen artifacts on every boot - power off. Is it expected?

Managed to fix this.
[Captivate Android Development] FireRaider:
I had the same issue. Acted like it was turning on but never did.

I fixed mine by doing a factory reset/wipe from recovery then reflashing whichever nightly. Several people reported this starting back around nightly #69 or #70. It works great on mine now after I did this.
[Captivate Android Development] 105437:
Upon further review... people are telling me my phone sounds better but worse than it used to before I flashed a different radio. Apparently the JL3 re-flash improved upon that but call quality still remains worse than it was.

Has anyone found a radio that delivers good call quality other than JL3? I'd like to try it and see if it helps.
[Captivate Android Development] cbasse:
Before I do something stupid and change a setting I shouldn't (warning, there be dragons ahead!) ...can anyone tell me what affect changing the governor to the other settings will have on the performance/stability of my phone? Put another way, can someone describe what the differences are between the "conservative", "userspace", "powersave", "ondemand" and "performance" settings?

Thanks in advance!

(wish there were a users' guide for CM7!! )
[Captivate Android Development] littlewierdo:
I just want to draw attention to this, I have had a very similar problem with Bluetooth calls.

When I hit the button to answer a call on my BT unit, nothing happens. I can pick up the phone and swipe to answer but the call does not go thru the bluetooth, it is only thru the handset. If I remember correctly, the bluetooth button in the phone app is greyed out (the screen that has a picture (if available) of the person you are talking to with 6 buttons underneath - things like speaker, mute, end call, etc).

Actually, now that I think about it, I cant remember exactly whether the Bluetooth button is greyed out or whether it shows it is connected (and I dont have my phone atm to check on this).

I know my phone is still connected via BT because, as soon as the call drops, my phone will resume playing audio thru the BT headset (if any was playing when I answered the call).