yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RockRatt:
Corey I sold one of my captivates just before launch of the SGS2 also and paid for my SGS2. I kept one cappy just as a backup or test phone but I have hardly picked it up since getting the GS2. It is more of just keeping it up to date and sometimes using it while I am messing with stuff on the GS2 like checking xda constantly. So far I ahev only kept it so WHEN the unbrickable mod with Nexus S firmware working I will port it to that for some ice cream. BUT with how reliable it has been flashing the GS2 and how long the battery life last I am not sure if I want to keep the cappy. Well have been seeing you on the other side before you got the GS2 so continued good luck with it.

Sent from My KickAss CM7 Galaxy S2
[Captivate Android Development] ou812bkewl:
Does anyone know what's going on with nightly 151 and the errors in ROM Manager when attempting to download it?
[Captivate Android Development] n0stalgia:
SamsungServiceMode on the changelog, I am very excited. We can finally get to see what bands our radios are on! (and perhaps the coveted power savings as well??)

Thanks CM7 team!
[Captivate Android Development] airtower:
151 isn't available (yet) on the CM site, not sure why ROM manager thinks it is. Sometimes nightlies get skipped even though there are pending changes. I'm not smart enough to know why that happens.
[Captivate Android Development] tjsooley:
152 is now up but cant download on rom manager or from http://download.cyanogenmod.com/?type=nightly&device=captivatemtd

get a 403 error
[Captivate Android Development] ou812bkewl:
Downloaded #152 with ROM Manager and flashed. I got service mode by pushing *#*#0011#*#* and hit the back button to access parent menus and am now locked into "850mhz only" mode. Awesome. :-)

Edit: Just confirmed that band settings changed in service mode will persist through reboot! My mobile data runs like a scalded ape now! Woo hoo! Huge differences in latency and speed, at least in my area in southeast texas.

1900mhz = 220ping 1500d/800up

850mhz = 120ping 3200d/1200up
[Captivate Android Development] airtower:
Still having issues with incorrect lables appearing, has been happening since #150

this comes up whenever i longpress text:

and also the lockscreen battery widget is different. It should say "Battery" between the icon and the percentage. Also, when charg

ing

it just says "Charged" and when charged it says " Please connect your charger (%s)".
[Captivate Android Development] ou812bkewl:
First, what kind of theme is that you are running? If that keyboard is Swype, what version is it?

To start, I would use Titanium Backup to backup all my apps, flash back to stock, apply a kernel with CWM, and then reflash back to nightly 152 and see if that corrects your problem. Then you can bring everything back with TiBu. I do this anyway about every 10 or 15 nightlies. Just remember to use care if flashing boot-loaders.
[Captivate Android Development] XsceneXhippieX:
or, be extra careful, backup only user apps with TiBu, wipe data/factory reset via cwm, reflash the latest nightly, restore using TiBu, and get identical results with 1/10000th the risk of a brick :)
[Captivate Android Development] ou812bkewl:
Or that too... :-)
[Captivate Android Development] airtower:
Theme is MattedBlues. It's in the market. The wallpaper and lockscreen zips are in a thread here on XDA. Swype is the latest beta, not themed or anything.

I just did the back to stock dance the other night, and if I flash back to #149 everything is correct. I figured I'd see if there was a quicker solution before I went through with going back to stock (i'm lazy! )
[Captivate Android Development] airtower:
Here is another screenshot. The battery is low (and usually says such). There is definitely a SIM in the phone.
[Captivate Android Development] Time_Zone:
I'm on 149. I think I am just going to set still for now and watch where this goes.
[Captivate Android Development] n0stalgia:
Possible bug: Manual entry of values is not possible on the debug menu. When you click on where you enter a value, the keyboard doesn't pop up, with a "?" showing where the value should be.

Anyone else?

(also, why does my modem keep to 1900 so much?)
[Captivate Android Development] ou812bkewl:
Yes, the popup doesn't appear so you can't make selections that require numbered input. For the band adjustments, you can just tap the line you want to select, but on some other menus, tapping can't work. Hopefully its fixed in a future update.

I even tried setting my keyboard as the long press action on the menu button and it even came up as a numbered pad automatically, but the numbers pressed wouldn't be seen by the menus.
[Captivate Android Development] nkrick:
Are you able to get the menu to pop-up to exit service mode? All I can do to "get out of" service mode is hit the home button.

At this point I am guessing there may still be some pieces missing since we only have part 1/4 and 3/4 (unless part 2 & 4 are for other devices maybe?).
[Captivate Android Development] ou812bkewl:
I just hit the back button.
[Captivate Android Development] nkrick:
Strange. I can hit back as far as the main menu. When I hit back from the main menu, service mode completely locks up and I have to restart the phone in order to do anything in it again...
[Captivate Android Development] RichMD:
Yes, they are for other devices - 2/4 and 4/4 are for GalaxyS and Vibrant as shown below. The fix for the "use internal storage had an "aries-common" and a captivate specific piece as well.

http://review.cyanogenmod.com/#q,status:merged,n,z
[Captivate Android Development] squishy5:
is there even the slightest of chances that cm7 will be bumbed up to android 4.0
[Captivate Android Development] sixstringsg:
Well it will be CM9 first of all...
[Captivate Android Development] goulet:
Just flashed nightly 152. Having an issue with the capactive buttons staying lit up when i receive a text. The buttons will remain lit until i answer the message. Is there a setting to change this? Or should I just reflash?
[Captivate Android Development] Lollipop_Lawlipop:
That's called LED notification, a useful way to remind you you have a notification waiting.

If you don't want it (and seriously, why don't you want it?), you can either set quiet hours or turn them off individually. Both are under cyanogen settings.
[Captivate Android Development] squishy5:
lets hope 4.0 bump can just come with a normal daily quick update

and that 4.0 doesnt take that long to work on to change

i love android
[Captivate Android Development] Smasher816:
Watched the Google nexus (Nexus prime sounds better) release.

Can't wait to see ICS rolling out (SDK alright out + Emulator).

Hopefully cm(9) gets updated and onto out devices sometime soon.

I can't wait, it looks pretty sweet.
[Captivate Android Development] goulet:
Thanks for the quick reply.

Would rather conserve battery I suppose than have the lights on all the time.
[Captivate Android Development] EnemyOfGlaDOS:
.. hardly any juice is used for LED notifications if you were concerned about battery drain :)
[Captivate Android Development] Smasher816:
Think about it like this. If the phone had an actual LED you wouldn't think about it, and the battery drain it doesn't cause...
[Captivate Android Development] rbrown13:
So the capacitive touch buttons stay lit all the time? My cap buttons stay on as soon as my screen shuts off and don't go off until I wake the phone back up..
[Captivate Android Development] Javs2010:
My battery has lasted forever today!

Sent from my CM7 Captivate
[Captivate Android Development] Thunder22:
Any chance the USB host support works on the captivate??? Saw it in the past changelog.
[Captivate Android Development] gstern:
Just updated to #152 from #147, was a little nervous as some apps fc's and I took a peek are mnt\sdcard, where's my data?

A quick look at cm settings resolved the issue.

Note to self: read the f***ing changelog...
[Captivate Android Development] fatalexception87:
Soo... Im sure you devs are gettin tired of me popping in here every month or two and asking the same question, but I still cant find a definitive answer by searching, and there is no way in hell I can ready all 1175 pages of posts withing ending myself...

With a few versions of Gingerbread leaked for the cappy, has CM7 integrated any of the Audience noise chip's drivers yet?

I use this phone in noisy backgrounds too much not to have that little sucker activated, as evidenced by the shear number of complaints I had from people on the other end of the line the last time I tried this ROM.

Any news? Thanks in advance everyone, and keep up the good work!
[Captivate Android Development] goob1284:
Quick question, I haven't been on cm7 in a while, but have they ever added the text pop up like in miui? That's the only reason why I'm still with it. I know of the app text pop up but it didn't work last time. Thanks.
[Captivate Android Development] ou812bkewl:
Does anyone know if there is a way to make folders for the bookmarks in the browser? Thanks.
[Captivate Android Development] sixstringsg:
Audience chip drivers require source code we don't have. So no, it doesn't work yet.
[Captivate Android Development] fatalexception87:
Maybe im confused... if there is a leaked Gingerbread ROM, does that not mean that there is source code? or is the source code different than a leaked ROM?
[Captivate Android Development] sixstringsg:
Completely different. The leaked part isn't the source code. Think of it like a car, we got the whole car, whereas the source code is how they built the car. Not a perfect analogy, but it will do. We have what is capable of running on phones, the binaries and such, but not the files/configs necessary to build those. They are required to post source code only after an official release, and Samsung actually does that part really well.
[Captivate Android Development] airtower:
I tried this method, but no longer have any connectivity to the google mothership. Signal bars stay white, can't download anything from the market (but can search just fine). Trying a fix permissions run now, but if that doesn't work, it's back to stock and I'll start over.

I've been out of the stock game for awhile...is there a one-click that will safely put me back to stock with GB bootloaders? I'm still on froyo and might as well use this as an opportunity to upgrade.

edit: fixed permissions and cleared user data again. works now. Thanks for your help!

edit2: i'm an idiot. The problem was fixed but came back as I was setting the phone backup. The problem: a zip themer zip I was applying that I hadn't "redone" in several weeks. Something with the framework was changed and my zip theme is no longer compitable.
[Captivate Android Development] fatalexception87:
Ahhh... alright, I get it. Thanks for the help man, i never knew that.

I suppose I'll just sit tight and wait for an official release of gingerbread from Samsung... which will probably be a while, eh?
[Captivate Android Development] ou812bkewl:
Ok, first what I would do is check your IMEI number and make sure your number matches the number under the battery of your phone. If it starts with 0's, then you have another big problem.

You can find most of what you'll need here: http://xdaforums.com/showthread.php?t=1300843

What I do to get back to stock GB is I first do a reboot of my computer and allow it to boot back up completely. I make sure that all my programs are closed and bring up DG's Odin One Click JF6. I then plug in my phone while holding both volume buttons while powered off to bring up DL mode. Once Odin sees my phone on a com port, I wait about ten seconds to see if windows throws out a taskbar notification about driver issues. If no notifications are displayed, I click the button to start the process. Once that is complete, I unplug my phone, and allow it to boot completely and reconfirm my IMEI. Then, I flash Cezar's KF1 "Bootloaders-Only" Odin One Click. (You will need to search for this thread, its not in the thread linked above.) Once that is complete, the phone will boot up normally. Then you have stock froyo with KF1 bootloaders (which work fine with froyo btw). From there, you can use the thread linked above to download non-bootloader Odin One Click installers for any stock Captivate ROM if your curious. I used the non-bootloader Odin one click for KJ3 and it flashed without a problem. Then download Boog's KJ3 kernel 3 and flash it. (I used Odin 1.83 with the .tar file in the PDA slot.) Then download CM7 nightly 152 and flash it with CWM. (ROM manager won't work to download CM7 from within KJ3, so you'll have to use the links in the OP.)

That should put you at bone stock CM7 with KF1 booties. I'm sure there is an easier/faster way, but this is how I do it and it has never failed me.

Edit: Link for the bootloader thread: http://xdaforums.com/showthread.php?t=1129821
[Captivate Android Development] RichMD:
Try the factory reset and then the market before you restore anything. If it works, then restore and off course only user apps.

Edit: I now see your edits and that you are set.
[Captivate Android Development] RichMD:
I NEVER flash anything with bootloaders anymore. The KF1 BLs let you run anything - CM7, Samsung ROMs, etc. There is a 1 click I KH3 with Boog's kernel (so CWM) integrated and no BLs.	This virtually eliminates the risk of a hard brick.
[Captivate Android Development] ou812bkewl:
I agree, once you're on Captivate GB bootloaders, there is no need to ever flash them again unless you want to go back to pure JF6 stock to plug in and see what Kies mini will give you. I always restore my /EFS folder from backup in between flashes too, but I'm a bit obsessive. :-)
[Captivate Android Development] cbasse:
How do you restore the /EFS folder? Does this have something to do with why Kies Mini does not recognize my phone (or, rather, says device unregistered)?
[Captivate Android Development] techmik67:
you are confused..... if we were talking about Windows, the rom would equal the .exe ......... the source code is what is BUILT FROM to CREATE the exe.....
[Captivate Android Development] Yaantra:
Re-posting from RC thread...

Cannot save signature :

The signature field in e-mail app does not stick... i mean once you type in the signature and navigate back to email (or elsewhere) it gets deleted... the signature feild is blank.

Is there a workaround?

Thanks...
[Captivate Android Development] RichMD:
OK, if you flash KH3 with no restore and there is STILL a problem, then go back to JF6? My guess is that almost always it would be a HW problem at that point...

As long as CM7 is a different FS and therefore repartitions on install (if RFS is in use) then I don't think there is any difference between flashing stock KH3 or JF6 first.
[Captivate Android Development] littlewierdo:
Very quickly, using CWM to do a factory reset is NOT the same thing as restoring to stock.

A couple months ago, my phone was extremely quiet and garbly during phone calls. I originally was on the stock kernel and modem that comes with cwm.

I tried flashing different kernels and modems, no such luck. A factory reset BOTH via the settings and via the recovery menu did not fix anything (just an fyi, I did not restore any apps with Tibu after either restore so my apps were not a factor).

I did a restore to stock / master clear and reflashed CM and voila, phone calls were great.

I am currently in a situation where I have two cappies, one where the alarm force closes every time it goes off (and yes, clearing data for the clock did not fix anything) and another cappy that I cant transfer phone calls to the bluetooth device in my car (yet it streams mp3s just fine) - a factory reset from within CM and the recovery menu did NOT fix either issue.

So this weekend, I am going to have to try a stock restore...
[Captivate Android Development] RichMD:
I actually posted a ? specifically on the difference between factory reset and flashing stock. There was no reply but my "assumption" is the following:

Flashing Stock: Everything you did/modified outside the SD cards (internal and external) will be wiped since the RFS filesystem is installed and the CM7 install will repartion/wipe everything. This has the effect of also causing any custom kernel or modem selection to be wiped so you get defaults with the ROM. Sometimes that might be the actual problem.

Master clear will even wipe settings/files on the internal. Some apps, etc will store configs, etc there so formatting the internal SD is the same as Master clear I "think".

Factory Reset (when on CM7): This will wipe all your data/settings. This will NOT wipe the kernel (custom, etc) and modem you chose.

IF you haven't modified the base ROM files AND your problem isn't kernel/modem related then the end result will be the same.

When you had the "garbled" problem, I think there was some problem with the kernel/modem combination. That is what can happen with an I9000 kernel and an I897 modem, etc. I don't know why flashing another modem didn't fix it but did you have a custom kernel possibly that had a bug?

As far as the FC issue, I would be curious if you could fix it by booting to CWM, factory reset, and then format system (wiping any base ROM updates) as well, and then reinstall the ROM.

I "think" the only difference with the wipe data and system method and stock is to replace your kernel and modem - other than directories such as EFS, etc that rarely are a problem. The stock flash wipes system and you have to reinstall CM7 so maybe that is what is really fixing the problem...?

As you can tell by my " marks above, I am not saying this is necessarily true - just my somewhat educated guess
[Captivate Android Development] cesierra:
I have been waiting for this feature forever. Thanks to the devs.

Question: Isn't this a Samsung only feature that wouldnt work on CM?
[Captivate Android Development] Gromlakh:
That's pretty much it. With any of the options from CWM (factory reset/master clear/etc.), you're basically just taking an eraser to various non-critical parts of your phone. You will lose personal things like installed apps, user data, cache files, and things on the SD card (at least with Master Clear). None of them will make any alterations to your core system files, such as the kernel/modem. CWM would have to have access to the original kernel/modem/system apps to change them, which it doesn't if you're "clearing/wiping" and not flashing a zip file.

When you're using Heimdall (or, if you're lame, Odin) to flash in download mode, you are straight up overwriting whatever parts of your phone's file structure you tell the program to. The "flash to stock" option will completely repartition your phone, create an entirely new file system, and rewrite all new stock files. So, this is "eraser + ink pen."

Oh, and never flash bootloaders unless something is wrong with your current bootloaders. 99% of the time when someone tells you "flash to stock", they mean the horrible Odin 1-click method that includes flashing bootloaders. Don't do that. You're much better off using the Heimdall stock KH3 package that includes Boog's custom KH3 kernel with CWM injected, but no bootloaders.
[Captivate Android Development] CptTwinkie:
The answer seems a little obvious since it does work.

The way I understand it is that there are additional setting in the Samsung hardware and this update adds the menus for those settings to the captivate build of cm

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] rbrown13:
came over from pinnacle rom which had some issues but seemed to have really good battery life with CM I only get about 8-10 hours with light use any suggestions.
[Captivate Android Development] 105437:
So where do we find info on how to use this new ability?
[Captivate Android Development] Captain_Nero:
Give the Glitch Kernel a try.

I am not amused with your phones performance
[Captivate Android Development] ou812bkewl:
I think most of what they're doing to make stuff work with CM7 is alot of trial and error between the opensouceness of google's core android software and samsung's array of closed-source proprietary drivers and software. Its a miracle that they get it to work at all.
[Captivate Android Development] cwgannon:
Dial *#*#0011#*#*

The service mode will open; hit the back button. Go to phone control, network control, band selection. Make your choices here; they take effect immediately. The star in the brackets,

[*], indicates a particular band is active.
[Captivate Android Development] goabunny:
I accessed.service mode and selected GSM 850 and stuck with Edge speeds. I cannot get H symbol on my phone.

Am I doing something wring?
[Captivate Android Development] XsceneXhippieX:
gsm=edge wcdma=3-3.5g for at&t afaik 850mhz being the most used/faster of the 2 frequencies for an oversimplified explanation to my knowledge, thats how i have it setup (on top of 3gsupercharger or something from the v6 supercharger thread that changes the build.prop for faster 3.5g speeds or something like that)
[Captivate Android Development] ou812bkewl:
Nightly 154 has broken service mode. It cannot be accessed now with the *#*#0011#*#* code. Still trying alternate methods. Servicemode was moved to a different file path according to the changelog.
[Captivate Android Development] nkrick:
Not all AT&T service areas have 850 Mhz available. You may live in one of the 1900 MHz only areas (like me, unfortunately). AT&T is supposed to be deploying additional network capacity and network "overlays" (AT&T's term for supporting both 1900 Mhz and 850 Mhz for HSPA) in many major markets this year, including the market I live in, but I tested yesterday and 850 is still not an option for me.

---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------

154? The latest I see in the changelog is 152 (http://cm-nightlies.appspot.com/?device=captivatemtd).

I noticed the change to move service mode to packages/apps. I was hoping this meant they were creating an app that would show up in the application drawer... :confused: If this is not the case, is there any way to create such an app or shortcut? I know that it was possible to create an shortcut to the GPS configuration on the TW ROMs.
[Captivate Android Development] Tuftylb:
Message Access Profile (MAP)

I've been searching around but cant seem to find an answer to this question: Is there anyway to get Message Access Profile (MAP) working on the Cappy with CM7 or other means...? TIA :)
[Captivate Android Development] nkrick:
It looks like MAP is not a part of CM, nor is it a part of stock Android. There have been two feature requests for MAP, but it does not appear that any work as been done. A developer may need to buy a car with Ford Sync before there is any priority to do this.

Please refer to these two links:

http://code.google.com/p/cyanogenmod/issues/detail?id=2056

http://code.google.com/p/cyanogenmod/issues/detail?id=3857
[Captivate Android Development] XsceneXhippieX:
okay, i understand the wrong thread/iron fist thing going on but its ENTIRELY relevant to the past few change logs of CM7 nightlies for the cappy for me to ask this:

should i see if 1900 bands are faster than 850 bands in my area? or is 850 faster regardless if it is actually available to your area, because when set to 850 bands only, i only get 1.6mbps on speedtest.net's app, whereas others are reporting 3.2mbps on the same settings.... thus my confusion, captivates are "capable" of 6.7mbps, i want to get the UTMOST out of that piece of hardware, is "850 only" the way to go? or trial and error the 1900 band and combined band mode the more intelligent option? my past speedtest results state that ive somehow recieved a 4.6mbps download speed sometime in march running a cm7 nightly though 0.o i think that was a mistake because my 1.6mbps is the 2nd highest mobile data speed recorded
[Captivate Android Development] alkoholic:
154 shows up now...

Looks like there is another change that needs to be merged before an app shows up in the app drawer.

http://review.cyanogenmod.com/#change,9173

This is why nightlies can be more dangerous than "stable" builds. If the auto-build happens between two related merges, there can be broken functionality.