yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] the_boris:
Sim unlock

I have contacted AT&T and they gave me the sim unlock code for my IMEI. They also said that it is possible to enter the following USSD string: #7465625*638*<unlock code># and it should unlock the phone even with the AT&T sim-card still inside it. Now, it does not work with RC1. It says "Connection problem or wrong MMI code"

Are there different USSD codes on Cyanogen than on AT&T firmware? Do I need to flash 2.2 from AT&T again, unlock, flash back Cyanogen?
[Captivate Android Development] Smasher816:
Cyanogenmod is missing many MMI codes.

Flashing to 2.1, unlocking, and flashing back. Should keep the lock, so it is a possible solution.

Mind telling me how you got ATNT to give you that code? I just used one of the programs.
[Captivate Android Development] the_boris:
Just ask them. If you have your phone for 3+ months they will give you the code.
[Captivate Android Development] kinubic:
didnt work for me~ i called and they said sorry we cant coz this phone is only for at&t or somthing like that..
[Captivate Android Development] nkrick:
Try again. AT&T's official policy is that they will give you the SIM unlock code after you have had your (subsidized/under contract) phone for 3 months. If you purchase a new phone outright without a contract they may give you the unlock code immediately (if you talk to the right person).

edit: I can't find evidence of this now, but I have read it before. It may just depend on what AT&T rep you talk to. If you are persistent you can probably fine one who will give you the unlock code. There are certain phones (such as the iPhone) which AT&T will never unlock.
[Captivate Android Development] whyareyou:
They used to do this, but, after they revamped their international plans (new tieups etc.) they've stopped unlocking smartphones.
[Captivate Android Development] nkrick:
That's a shame. I guess that leaves us paying $15 to get an unlock code. Is is silly of AT&T to not provide unlock codes, even if they decide to charge for them. I'd likely pay AT&T $15 for the unlock code vs. a third party. If I get the code from AT&T and it doesn't work properly, I am a lot more confident that they can/will help me resolve the issue because they stand to lose more than an occasional customers $15 over the matter...
[Captivate Android Development] whyareyou:
I think there is a free program SGS Unlock that you can use while on a Samsung rom to unlock the phone to use any SIM you want.
[Captivate Android Development] michaelgaribaldi:
Just upgraded to CM7 last night, and I have to say, this ROM kicks butt!! The only issue I'm seeing is that I can't tether this with my computer. I run Linux and prior to this flash I was using Cognition 4 and tethering was easy. I had a wvdial.conference script that had the device name (dev / ttyACM0)

and the initialization string followed by the usual "test / test" combo for login. The initialization string is still correct ( I verified that after flashing) but I can't get my computer and phone to tether. (USB debug in on as is tether). Anyone else having this issue?

(Other than that and the fact that I actually prefer the stock launcher, this ROM kicks ass! )
[Captivate Android Development] prayii:
I use Linux and tethering works just like connecting to any other wireless router. Are you trying to tether through USB?
[Captivate Android Development] tiuk:
Yeah, works fine for me, use it all the time for work. Only thing I've noticed is sometimes the first time I try to enable it it just says"error"and turns itself off. If I then enable it again, it works fine.
[Captivate Android Development] Loremonger:
Interesting Annoyance

I have an interesting problem (other than the vampiric battery drain). I've been using this ROM since it first came out, and the one thing that really grates my nerves has to do with a combination of using Dolphin browser and Swype keyboard.

When I tap the URL bar in the Dolphin browser, instead of selecting the entire URL so that I can just hit backspace to erase it, the Swype (beta 3.6) keyboard kicks in with word suggestions and places the cursor in the middle of the URL. Then I have to long-press, select all, and then backspace. It's not a huge deal, but it is an annoyance. (See images below.)

It's a very unique problem. It doesn't happen in other ROMs, doesn't happen with other keyboards, and doesn't happen in other browsers. It has to be Cyanogenmod 7 RC1 + Swype + Dolphin.

Has anyone else experienced this? Does anyone know of a fix (other than just using a different keyboard/browser/ROM)?

Does this:

Instead of this:
[Captivate Android Development] michaelgaribaldi:
Yes I am. That's how I've been doing it all along. :)
[Captivate Android Development] jacorso:
I don't have an answer for you but I have this exact same problem with Mosaic + Swype + Dolphin and it drive me mad. I'm wondering if it's related to the Swype beta I can't recall how it behaved before that.
[Captivate Android Development] tiuk:
I've had this issue with swype pretty much since I started running gb. I think it's an issue of trying to be "helpful" and failing. just like when I deliberately tap in the middle of a word I want to correct only to have the cursor jump to either the beginning or end.

Honestly my biggest annoyance is the search box on google's own website. For some ridiculous reason it forces the beginning of the query to always be shown, so if it's a long one you can't see anything being typed on the far right. I don't know whose fault this is (I blame google because this its the only spot in all of android I've ever experienced this) but it's extremely annoying.
[Captivate Android Development] kangi26:
I think it's a issue with Swype. I wasn't having any think like that happen on the previous versions. Only started with the latest Beta upgrade, and does it for me on Mosaic's stock, Dolphin HD, and Firefox browsers
[Captivate Android Development] michaelgaribaldi:
CM7 - tethering part II

i did some further troubleshooting last night, and it's not the USB cable,

as I can access adb very easily in Linux. It looks like CM7 may be mounting the Captivate modem as a different device other than what my last mod (Cognition ) and the original AT&T rom did.

AT&T and Cognition (4 and 5 ) mounted that device as ttyACM0.

I saw that when I checked /Var/log/messages. I'll poke around some more after work.
[Captivate Android Development] Kaik541:
you mean like how the FAQ clearly states you should install Nexus S drivers if you're on Windows? >_>
[Captivate Android Development] michaelgaribaldi:
Kaik

Kaik,

I'm not using Windows ... I'm on Linux :). However, you raised a good point, IF my Samsung believes it's a Nexus S, then I'll need to defintely check which devices my LInux sees on boot up !
[Captivate Android Development] Kaik541:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04e8", MODE="0666"

putting this in my udev rules makes the captivate work in any settings. no need for product ID and all that user nonsense.
[Captivate Android Development] michaelgaribaldi:
Yup

Totally confirmed.... when I load this ROM and boot up Linux, (OpenSuse 11.4)

Linux sees the phone itself, but fails to detect the modem at all.

However, on Cognition 4.X or even the Stock Froyo, Linux sees both the phone and the modem.

I'll try out your fix later on tonight, Kaik541. Thanks !
[Captivate Android Development] EthanMG:
is there a reason this build of cm tells us to format the system partition before installing the rom, whereas the instructions on the nightlies only has us doing a factory reset (formats data, dbdata, and cahce) and then formatting the cache again? seems like a rather big discrepancy.
[Captivate Android Development] justlaxin13:
odd problem flashing this

Ok, so i tried this out, flashing it from recovery with clockwork recovery, but when I went to install zip from sdcard and selected this, i kept getting a lot of quick jumbled text and a "installation aborted" at the bottom where normally all the installing script goes on. If it matters, installing the google apps zip from sdcard worked just fine...whats going on? thanks
[Captivate Android Development] rcllcr:
Hey all,

Just curious how stable this RC has been because for everyone because I plan on flashing and using for everyday use.

Thanks for the help!
[Captivate Android Development] typ44q:
I am new to CM7 but I have been running Continuum v6.1 (2.3.4) with ClockworkMod Recovery v3.0.0.5

Can I just follow the instructions and do the install? Is this version ok or should I update it.

Thanks
[Captivate Android Development] atinm:
use the latest nightlies from

http://xdaforums.com/showthread.php?t=978150
[Captivate Android Development] Frodo56:
Hopefully not too stupid of a question, the file in the OP is named "update-cmxxxx". This is still a full version of the ROM, correct?
[Captivate Android Development] tkjeeper:
I'm a cm7 virgin also, trying to set up my email but keeps fcing on me, please help.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] Smasher816:
It should be... (but im not sure)

I believe its just cyanogegens naming convention. RC1 is really just a nightly that they renamed, to mark a milestone.

Like antimn said you should use the latest nightlies as they will have more fixes and features over this.
[Captivate Android Development] kinubic:
anyone recommend good modems for this? im in LA area :)
[Captivate Android Development] RockRatt:
Here are some I use in Orange County. I prefer the ones I have listed below but if you want to try out others look in the general section for captivate and the modems 60+ and I listed others. Also you MAY be able to find some of these listed on the gooinsideme links around for cm7 modems. All listed below I have used on my cm7 running the nightlies newer than rc1.

TUBJV6 http://db.tt/gsQAZXI

JK4 http://db.tt/yi74lK1

JVR http://db.tt/vZLHr1A

JJW2 http://db.tt/4VVVtXt

JJJV5 http://db.tt/OGKpbVB

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] vsboxerboy1:
I just put CM7 on my phone a few days ago and twice have have had the phone go to sleep and fail to wake up. I've had to pull the battery and restart it.

Anyone else have this issue or know how to solve it?
[Captivate Android Development] RockRatt:
Are you undervolting or overclocking aat all? ( You can't be if your on the rc1 with its stock kernel, but in case you are using another kernel with OC/UV "MAY" be the issue.

If no to the above then I would personally go and reflash rc1 or update to the newest nightlies. They are JUST AS or BETTER than the rc1 and basically built on top of the rc1. Clear cache and dalvich cache before reflashing the rc1 or nightly. If you still have a issue you MAY need to wipe data/factory reset, then flash rc1 or nightly. These are just the things I would try first off. But to answer your question I didn't have that issue on rc1 or any of the nightlies.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] vsboxerboy1:
No OC or UV - I installed by going all the way back to eclair so it should have been as clean of an install as you can get. I can try flashing it again but perhaps I'll wait until the next milestone build seeing as this is ~2 months old anyway.

Thanks for the reply though.
[Captivate Android Development] RockRatt:
You can flash any of the newest nightlies without problems. They are just as stable as the rc1 or more stable plus better battery life. They are the same kind of full rom.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] smeltn:
Only problem is themes aren't working with the newest nightlies right? So if you want say the Mattedblues theme you are "SOL"
[Captivate Android Development] EnemyOfGlaDOS:
Why not use the matted blues for theme Chooser? Those themes work fine and some of em even get updated. You can grab "Theme Chooser themes" from the market for more freaking themes than you can shake a stick at ;). Then after the apk is installed open theme Chooser and apply theme of your choice.

..btw, matted blues (theme Chooser version) works just fine with the latest nightlies. :)
[Captivate Android Development] RockRatt:
I use blue bionic or red something that I can't remember the name off the top of my head from the market and they work with no issues. Just look for Theme Chooser Themes in the market.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] melbourne408:
Bootloader wise yes but all in all, no.

Go back to stock with 1 click, make things a lot easier.

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] tysj:
Nevermind
[Captivate Android Development] sleither:
Just update from an earlier nightly. Looking good guys! Congrats on the milestone!
[Captivate Android Development] dangerdan:
Hows the battery life with this one?
[Captivate Android Development] markdexter:
seems a little better, once that issue is sorted out with the battery drain, this will be (currently is) there best ROM available for our phones, especially when the devs can start to use it as a base to build upon
[Captivate Android Development] haolc:
i tested nightly version . battery is very good but it become to very bad after i install google addon. i like CM7, so may be i have to reflash RC1 version tonight.
[Captivate Android Development] Enhanced:
Never thought I'd hear the team say this. :)

Hell of a progress from what it was in March. Congrats guys.
[Captivate Android Development] mortuus.x:
Unfortunately I needed to doubleflash and re-install gapps. That said, so far so good with the RC.

Stable, quick and battery seems decent. Not awesome, but decent. I worry I won't ever see amazing battery life due to having to use Touchdown for my email. It's a work phone and I wind up oncall so I absolutely need TD to work. It's second on the list of offenders right after the display.

That said I'm not quite getting what I did on some of the custom Froyo roms, but it's getting closer.

Keep up the good work guys. You're making a lot of people very happy Captivate owners.

Cheers!
[Captivate Android Development] phaedrusiszen:
It says "Registration Failed" when I try to register for updates. Expected?
[Captivate Android Development] serialtoon:
I unplugged my charger at about 9am, it is now 10:30 and dropped to 80% from 96%. So far the battery is attrocious. But the ROM is epic.
[Captivate Android Development] singlebeam:
Mine is acting similarly...it may need a few charge cycles for the rom to settle with the battery.
[Captivate Android Development] Kaik541:
Fails for me too, not sure why, possibly the back end is messed up or RC's don't count enough as a "stable release" to warrant such updates.

this pretty much sums it up:
[Captivate Android Development] CPeterson:
Now that it's RC1, is there a post/wiki anywhere that lists known issues and differences from the Samsung roms, for those of us who haven't been following the nightlies?
[Captivate Android Development] n0stalgia:
http://cm-nightlies.appspot.com/?device=captivatemtd
[Captivate Android Development] CPeterson:
That's the changelog. I'm more interested in an up-to-date issue tracker or at least a list of things that "everyone" already knows if they've been following development. What hardware doesn't work 100%, what audio/video codecs is it missing, what will it never support due to lack of open source drivers and framework changes?
[Captivate Android Development] morehush:
Flashed from Cognition 5 this morning. Using CM7 is worth going without the audience chip.

For anyone wondering, I flashed CM7 while on the GB I897 bootloaders and have not had any issues in CM7.
[Captivate Android Development] :
So glad to finally see a RC for the Captivate! Flashing this tonight! I dont know how I missed it last night when I flashed the latest nightly..?

Hopefully RC1 resolves this problem I am experiencing currently!
[Captivate Android Development] superdave69:
Would you mind elaborating a bit? I'm horribly tempted to try CyanogenMod, but I really don't know how it stands performance-wise against, let's say, a 2.3.4 custom Rom. Raw speed? App compatibility? GPS?

Also, what is the "audience chip"?
[Captivate Android Development] n0stalgia:
H.264 and DivX/XviD hardware acceleration doesn't work, making HD playback battery intensive and not very smooth. The mkv container format is not supported natively.

Audience chip is not supported, so calls will not have the microphone enhancements (still sounds great though).

The TouchWiz framework is removed, and thus the launcher, camera, calendar, dialer, contact apps are Android stock. I think some of the TouchWiz apps are more aesthetically pleasing and refined. Also, TouchWiz facebook integration is missing, which means no more facebook calendar sync. Facebook sync now requires the Facebook for Android app, which only supports contacts sync, and seems to take up more resources (cannot choose SNS interval, etc). Generally, TouchWiz makes for deeper social network integration (facebook, twitter).

Of course, Samsung and ATT apps are all gone and no longer supported (including swype and documents-to-go).

CM7 seems worse than Samsung ROMs at downloading large files. Downloads are often "unsuccessfully completed" despite a perfect connection. If you look at the internet dl/ul speeds, they are very erratic on CM7, which can compromise speed test results.

Battery life is still not as good as Samsung ROMs. The phone seems to get hotter when using CM7 than Samsung ROMs. There is still the recurring issue with Android OS eating up battery life. The Media Storage app (which indexes all media on the phone) gets "stuck" indexing, especially if you have large amounts of media on your SD cards, which prevents the phone from entering "deep sleep" and uses up lots of battery. If the Android OS/Media Storage problem affects your phone, expect a base discharge rate of 10-15%/hour without use. However, if the Android OS/Media Storage problem does not affect your phone, expect battery life only slightly less than the Samsung ROMs.

You can alleviate the Android OS/Media Storage battery drain by clearing the Media Storage app data each time you boot your phone or insert an SD card. However, this will render all music, photo, and video apps pretty useless as they won't be able to find your media.

Still, CM7 seems snappier than Samsung ROMs, and does not require Lagfixes or anything like that. App compatibility is the same. GPS is similar or better than Samsung ROMs.
[Captivate Android Development] morehush:
I'm not aware of any 2.3.4 roms for Captivate out there, but the performance would probably be around the same. The Audience chip is the little bit of hardware on the Captivate that's not on any other Galaxy S phones. It does the noise reduction in calls. None of the I9000 roms support it either, only roms based on samsung firmwares specifically for the captivate.

I do get higher benchmark scores on CM7 than on Cognition 5, but CM7 just has so many more options and UI tweaks to make the rom behave the way I prefer. I've heard that the 720p video recording isn't as good as on samsung roms, but I rarely record video on my phone. Using the camera for stills is as good or better than samsung roms, too. You can make it take a pic with the volume buttons or the search softkey.

It does seem to be draining the battery quicker, but as stated before, it just may take a few draining/charging cycles to get the battery stats right.
[Captivate Android Development] nkrick:
Actually, if you use TiBU to backup the AT&T wifi hotspots app and Mark this Spot (assuming you previously installed both apps), you can use TiBU to restore both these apps. (These are the only two AT&T apps that I find remotely useful, so they are the only ones I have tested and have installed).

Edit: Also, you can register for and use the swype beta app if you like swype (like me).
[Captivate Android Development] wvmstr:
Just flashed V7.1.0 RC1

On the phone was nightly 05212011

No errors reported.

Won't boot up. Stuck in boot loop. Never makes it to the screen that shows the arrow animation.

Restore my back I just made ==> No Service!

IMEI gone.
[Captivate Android Development] balishared:
flashed over miui

i was with miui now back with cm7 :)

format: system, cache and data

flashed the zip (over miui)

then factory reset

everything seem to be working fine, no issues to report, battery is better than miui
[Captivate Android Development] shotta35:
Well at least now we'll be able to report issues. There's definitely a few for sure but yes i know it's only RC so at least we are getting there. Hopefully we can get the audience chip thing going as well as fixing some radio stuff. I know atimn(?) said it's closed so not much they can do about it but i've tried every radio known and it always camps on 1900Mhz!

Still having some stuttering issues too - dunno if it's a RAM thing or what.

Oh and since Gingerbread includes RAM usage, is there any reason to still have the RAM info in About Phone?
[Captivate Android Development] serialtoon:
Does anyone else get random data connection loss? Ive had this issue with the 3 Nexus S' that i have owned so im hoping its just a software issue rather than a limitation with this phone.

One last question, im new to the captivate with CM7 scene so i just wanted to ask, has the battery always been a problem? Or is this a characteristic of CM 7 on the captivate?
[Captivate Android Development] pvr:
I do. Mine keeps the data connection alive but not activity. That is, the 3G/H icon is visible but it's greyed out and nothing opens on the browser.

And all of the sudden it goes to green with no explanation
[Captivate Android Development] melbourne408:
hmm did you make a backup of the efs folder?

Have you tried formatting system/data/cache, reinstalling 7.1, then wipe/factory reset and rebooting?

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] RockRatt:
Sometimes you just need to install it twice if you ha e the bootloop. About #25 or so I had to do that and started just downloading it via rom manager, finding the folder it downloads to, and flashing it via cwm twice. Just flash it and if it bootloops go back to recovery in cwm and flash again and it WILL come back up correctly. Since about #34-35 or so I have again been able to just use rom manager to flash the nightly+gapps with just clearing dalvich cache and have had no issues with bootloops at all. Seems some do sometimes and some don't.

Also I cannot remember when exactly but the radio partition changed so that could be your no service issue. Again just try to reflash. If that doesn't work then find the newer style radio and flash it via cwm and it should work. I found this out when it changed and when I went back had no service at all flashed forward then it worked again. I THINK that since you flash the newer nightly it changes the radio partition so when going back CM7 cannot find it. So either way just flash a radio like jk4 or anything from gooinsideme and see if that fixes it.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] melbourne408:
Ugh modem partition change, , if it helps you here is a link to JK4 after the change, from my dropbox.

http://db.tt/5WBxBPP

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] markdexter:
looks like Playpus has built a good Kernel, just been reading over in the I9000 thread, and the people that have used it are reporting good battery life:eek:

Hopefully we get to try it soon!
[Captivate Android Development] wvmstr:
Backup of efs folder and attempts to restore have proven to be futile efforts in the past.

Went ahead and flashed V7.1.0 twice, IMEI is back

Lost all google apps.

Flashed gapps again and everything works again.