yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] rwells813:
Do it manually, DL gapps from RM, hold your power button, reboot recovery, install zip from sd

Clockworkmod, goo-insideme gapps. Profit

Sent from SGS Captivate CM7 or MIUI with Escapist orTKGlitch using XDA premium app.
[Captivate Android Development] skeepon:
i saw this in the changelog and wanted to know what it meant:

Added Samsung Galaxy S phones

anyone know?
[Captivate Android Development] Palmetto_X:
I use the MIUI camera it works pretty goodhttp://db.tt/E86ARc5

First time sharing from dropbox directly, let me know if that link works.
[Captivate Android Development] matt310:
^Thanks for posting the camera apk. It definitely works better than the stock CM7 app.
[Captivate Android Development] Kaik541:
you know that you can simply click the text which will take you to the gerrit review? which then has all the affected files and what their impact is.
[Captivate Android Development] musicalmindz:
Is there any way to do this double installing from Rom Manager? I still on like #22 and I've been afraid to upgrade with all of the root issues, sd not mounting, double installing stuff, etc. I don't have Odin or the 3 click stuff so I'm a little worried about installing any of the new ones for fear ill get stuck and have to factory reset or something hah.

Any ideas when or if it is safe to upgrade to latest nightlies from Rom Manager?
[Captivate Android Development] Smasher816:
Um. In terminal or adb you can use "reboot recovery" to send you to recovery to manually do it. It is probably not the smartest thing if your 3 button combos aren't working though.
[Captivate Android Development] pvr:
how about spelling for us poor corporate-IE6 bastards to whom the ajax-developed changelog page simply does not work? :)
[Captivate Android Development] z28james:
Thanks for the suggestion. This camera works well.
[Captivate Android Development] z28james:
I had jumped to the leaked 2.3.3 for a bit and while I had done that, things got a little crazy here. I jumped back in at #34 and I had zero issues. I popped the zip onto my sdcard and installed through clockwork recovery. I had no issues. I'm on today's newest nightly and everything is still fine.

i am not sure what rom manager does different other than just automating the reboot into recovery and installing the package but I had luck installing manually.
[Captivate Android Development] esancakt:
anyone having issues with bluetooth not starting? i did an upgrade not a wipe.
[Captivate Android Development] markdexter:
the latest nightly #36 has a new rebuilt kernel. apparently for the vid cam record. Hopefully it improves battery life too!!!!
[Captivate Android Development] imb951:
edit: New kernel has already been reported.

Hope to see the Escapist build his OC/UV kernel off this new one included in the 6/22 nightly
[Captivate Android Development] hkk:
Bluetooth doesn't work for me too. Initially, and it turned on, and but wouldn't connect to the headset. Now, it wouldn't even turn on.
[Captivate Android Development] hayslett4:
Bluetooth isn't turning on for my either. Also, my phone only charges when it's plugged into the computer instead of allowing me to use it as a USB drive. I'm on #35. I wiped the dalvik cache, re-flashed, powered down, removed the battery, rebooted... realized gapps needed reinstalled again. Reinstalled gapps, but still no Bluetooth or USB drive capability. Hopefully #36 or #37 will bring back some functionality.

Edit:

Flashed #36. Bluetooth still will not come on. The phone is recognized by the computer and can be used as a USB drive (seeing both the internal and external SD cards) Didn't have to reinstall gapps this time. :)
[Captivate Android Development] markdexter:
radios wont flash with latest nightly, tried to flash jv6 for cwm3 once loaded I still had stock modem
[Captivate Android Development] parshantx:
hey peeps, had one quick question. i see there's MANY updates of this rom.

so if i install the rom, and install an update, will it erase everything on my phone? or can i just leave everything as is, and update?

thanks!
[Captivate Android Development] rwells813:
Wont erase the SD, Follow OP instructions, install, update. Good to go

Sent from SGS Captivate CM7 or MIUI with Escapist orTKGlitch using XDA premium app.
[Captivate Android Development] Haloruler64:
The updates only reflash kernel (and modem but I'm not sure about this one), it'll keep your apps and everything. So flash the update, then flash your modem and kernel of choice again.
[Captivate Android Development] hayslett4:
Need to have the latest version of gapps on your SD card ready to flash after the update. I've lost them a few times during updates.

wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
[Captivate Android Development] prayii:
They reflash kernel but not the modem. At least none of the updates I've ever done have changed my modem from what I set it and I've flashed nearly every update even before the nightlies.
[Captivate Android Development] Tweakrr:
Bluetooth won't turn on for me with N36. So far everything else is working as well as it was on N35 though.
[Captivate Android Development] Haloruler64:
Thanks, I wasn't sure :)

Or download gapps from ROM Manager, you only need the free version. IF you happen to lose gapps or Superuser, get both from ROM Manager!
[Captivate Android Development] jhernand1102:
I'm on 36 and it turns on fine for me.
[Captivate Android Development] bentonhall:
I'm on 35 and Bluetooth turns on but doesn't connect.
[Captivate Android Development] switters1:
Any update on battery life improvements?

I'm more or less happy with nightly 22, but I'll upgrade to anything that can promise a battery boost!
[Captivate Android Development] lowlymarine:
@bay_wolf: How are you getting so much better battery life? I'm having "Android system" eat over 20% of my battery life, putting me down ro about 20% in less time.
[Captivate Android Development] E_man5112:
Is anyone else having these issues? My home and search buttons don't work. The rom is rather slow. I cannot select a home launcher, even on boot. Are these common, or a possibly bad flash?
[Captivate Android Development] lethoncbon:
Kimda same here : search and back button don't do anything. Home acts as back.
[Captivate Android Development] Kaik541:
sounds like some people didn't format cache/do a factory reset after installing
[Captivate Android Development] thatguysteve:
Hey if anyone wants to use the themed markets, just replace the vending apk in the gapps zip and flash.
[Captivate Android Development] lethoncbon:
Reflashed, did a factory reset and a format cache.

Still headphone issue.

Back and search not working.

By default, screen is in landscape, have to uncheck autorotate to have it in portrait.
[Captivate Android Development] BTTNext:
You downloaded the wrong files. If you have a Captivate and you download and flash the Captivate files, it will work just fine.
[Captivate Android Development] lowlymarine:
It sounds like you flashed the Galaxy S kernel rather than the Captivate one.
[Captivate Android Development] h0ckey10:
does anyone else have a problem where your phone doesnt see any contacts from your sim card?
[Captivate Android Development] flucks:
All I can say is that after following instructions to the T, imagine that, this rom is running flawlessly on my captivate. Thank you so, so much.
[Captivate Android Development] PuffinNugz:
Yeah, known bug. But you can still import them from sim.
[Captivate Android Development] flashman2002:
I had the home button not working when I flashed yesterday and so I rebooted and was fine.
[Captivate Android Development] Kaik541:
reversed headphone logic... not registering virtual buttons... 90 degree orientation... sounds like your real problem is you flashed the i9000 build! start over and try again please (this time with Captivate files)
[Captivate Android Development] bay_wolf:
I don't really know haha. I think the first time I flashed this I had that issue (or it was the first hour or two I had it installed this time) but it has just seemed to go away. After I charged it fully last night into the morning, I've just done my normal routine for a day. I just have WiFi turned off and am using the JK4 Modem.
[Captivate Android Development] lethoncbon:
Shame on me, you're right, I flashed with Galaxy S files, not captivate specific ... going back to flashing ....
[Captivate Android Development] h0ckey10:
Thanks got it to work
[Captivate Android Development] h0ckey10:
can someone explain to me once more how to get the market back. i installed gapps and im on the screen to select what i want after i sign in but their is no market option. what do i do?
[Captivate Android Development] PuffinNugz:
don't worry about. market will be installed automatically.
[Captivate Android Development] mcord11758:
Choose what you want market will be there
[Captivate Android Development] nyciz:
+1 Loving -CM7-06182011 but the battery life is hard to deal with... not knocking just asking....been search since Ive flashed and dont want to OC/UV but looks like I'll have to try to get better juice life.
[Captivate Android Development] acmcelwee:
No Bluetooth on #36 for me either.
[Captivate Android Development] jaxf250:
On 35 too and BT is same - turns on but doesn't connect.
[Captivate Android Development] veener79:
Same for me. :(
[Captivate Android Development] godzulu:
I'm on 36 and by is working fine here.
[Captivate Android Development] aHecticLife:
?

Why is it that on my Nightly 33, after a couple of hours everything (my apps) such as browser, messages, music, mostly anything that's a stock app on cyanogen starts to crash, and also Google Frameworks starts to crash too ? :(

Any solutions?
[Captivate Android Development] r3ferrei:
I've gotten that too. What I did was clear out some space by moving Apps to the sd card and clearing the browser cache. Check the exception you get when reporting the error and see if it's an io error.
[Captivate Android Development] Killemalll:
BT is sketchy on #35 for me as well.
[Captivate Android Development] ccrowe3:
I am on #36 and it is the first nightly since #29 that didn't require me to flash twice. I love how CM7 has progressed over the last couple of months.
[Captivate Android Development] aHecticLife:
Hey I actually tried what you said but by using Cache Cleaner NG from the market and waited a few hours for the crash but it never crashed! :D

Thank you so much :)
[Captivate Android Development] Johnston212:
I know that #31 (I think. It's the 6/17 nightly) is pretty good. I've got decent battery life and a significant improvement to GPS as well.

I'm also flashing back to 34 as we speak. I was on 35 and had horrible battery and lots of lag issues. I did not experience the BT problem at all, I live off that stuff.

Hopefully a few of these new issues will be cleared up by #37, but if 34 works fine I will stay there for now, otherwise its back to 6/17.
[Captivate Android Development] Haas360:
I can get it to start but nothing else
[Captivate Android Development] contentryder:
cyanogenmod doesn't have driving mode in voice input & output settings =(
[Captivate Android Development] contentryder:
I have a problem, voice search and in call mic is very low. How can I resolve this? Thanks!
[Captivate Android Development] tjsooley:
on 37 and no bluetooth just like 36
[Captivate Android Development] ronii1123:
So I searched around and haven't found much of an answer, but does anyone know how to solve the issue with Battery Use showing Android OS as the main battery consumer? I had this issue before but not sure how it came back or how to get rid of it, my battery life is horrible now. Currently on #36 moving to #37 in a bit, should I flash to stock and flash #37?
[Captivate Android Development] bubbad58:
I DL 36 yesterday and blutooth worked fine. I powwered off for the night and turn on my phone and now bluetooth does not work.
[Captivate Android Development] shotta35:
Yeah, no bluetooth here also. It didn't try 36, did a clean install - wipe everything then flashed and it just turns on but doesn't scan for my headset.
[Captivate Android Development] veener79:
Same :(
[Captivate Android Development] Palmetto_X:
Anyone having BT problems on 36?

JK
[Captivate Android Development] nkrick:
At least read the last few pages before you post. There are several posts reporting Bluetooth problems on 35, 36, & 37.
[Captivate Android Development] CougarBroker:
I think that is what the JK was for, JUST KIDDING.
[Captivate Android Development] Johnston212:
Are you sure? I would have sworn I had seen it before. If not, you could always get safe reader through vlingo, it's a decent option.
[Captivate Android Development] jhernand1102:
Has anyone submitted a bug report for this issue?
[Captivate Android Development] EnemyOfGlaDOS:
You can check the bug list. I believe there is a link in the OP or at least in the Q&A OP.
[Captivate Android Development] Johnston212:
Quick question, but is anyone having any issues with downloading updates (or anything in general) from the Market? I've tried downloading updates about 3 or 4 times, both on data and wifi, and they are all unsuccessful.

On a side note, I finally got a JP9 modem made. I think I know what the issue may be between the 7.1 modems and the goo-inside modems. The goo-inside modems have more files visible once you open it compared to the 7.1 ones. I could be wrong, but this could be related.

However, while my latest attempt did flash, it also was the WORST JP9 version and WORST modem I have ever flashed. I've used JP9 before on CM7 and it was actually good on data, unlike what I just flashed. This is the first time I modified a modem myself, so I don't know if I did something wrong. I wish I could just figure out how to fix this glitch that prevents me from using some of these modems.
[Captivate Android Development] KohjiNagata:
Ok so I did a little test and maybe someone can tell me if I've done something wrong. I spent a few days using the stock kernel (build 32), then a few days on escapist, then a few on Glitch. I used the latest Voltage Control to admin both escapist and Glitch. I had escapist set to noop with the conservative gov. Didn't OC and had my UV settings as such:

1000 MHz - 100mv

800 MHz -100mv

600 MHz -125mv

400 MHz -75mv

200 MHz -75mv

100 MHz -100mv

On Glitch I used smartass with the same settings. This is what I found. Both escapist and the stock Cyanogen kernal gave me the same battery life with roughly the same use over 2 days each. It ended up being about 10% batter loss per hour. With Glitch I slightly worse battery life. About 12 - 13% loss an hour. (Now I know this was due to my use of Smartass over Conservative). My ultimate goal is to squeeze as much battery out of this thing as possible and this is by NO MEANS a comment on the custom kernels. I'm just wondering what else I can do to get this thing to last me through the day.
[Captivate Android Development] jhernand1102:
Copied from the first post:

What are Nightly builds? Auto compiled build of the latest CyanogenMod source from github. This version changes each night and aren't officially supported.

If you find bugs/issues you can/must discuss here (do not submit nightlies bugs on CyanogenMod issue tracker).

So I guess on the nightlies if we find and issue we just flash back to one that was working for us.
[Captivate Android Development] EnemyOfGlaDOS:
Yeah my bad.. I forgot things had changed since the nightlies .. but that makes since as there are bound to be broken things. I used #35 with another kernel and Bluetooth was working. Ill check again in a bit when I get home just to be sure. Its hard to keep track when you flash your phone a few times a day :p
[Captivate Android Development] jhernand1102:
Yeah I think it's something in the new pre-built kernel that is causing the issue.
[Captivate Android Development] smeltn:
Which Glitch kernel do I need to use for build 35+ ? I used Glitch on MIUI and loved it, would like to give a try on CM7
[Captivate Android Development] EnemyOfGlaDOS:
v10C will work. Haven't updated past #35. Also camera is working with glitch's kernel as well ;)

*update* just checked bluetooth and its working with this kernel.
[Captivate Android Development] z28james:
Im back on #34 as well. I also noticed that zipthemer stopped being able to modify things from #35 on....
[Captivate Android Development] kurrptsenate:
Does anyone know why I keep having this problem? It's not exactly killing the experience for me but it is very annoying.

If I go to make a call the screen goes black. I try waking it up with every method possible and its just SOOOooo slow to respond. Swiping the light sensor rarely works, if at all. :-(
[Captivate Android Development] matt310:
Have you played with the settings in:

Settings-->Call Settings (specifically the Keep Screen Awake option)
[Captivate Android Development] Haloruler64:
It should only happen once after a reboot. If you make a second call, it'll work fine. Known bug, as far as I remember.
[Captivate Android Development] kurrptsenate:
I turned that option on (keep screen awake longer) and tried it out. It did in fact keep the screen on for a good 6 seconds which made me pretty optimistic, but then reverted right back to normal. Do you think its my stock boot loaders doing this?

If it just happened once after a reboot it wouldn't bother me. The only fail-proof method I've found for resurrecting the screen has been to wait for the call to end, allow the screen ample time to "power off", then plug a usb cable to a power supply (computer works best for me)

It's gingerbread roms in general to my understanding but it appears my experience has been worse than most. Lucky perhaps lol
[Captivate Android Development] Tweakrr:
Bluetooth isn't fixed for me with N37 either. My bluetooth stopped turning on with N36 and I was hoping it would be fixed in N37 but that is not the case. I went back to N34 and everything is working good again.
[Captivate Android Development] Tinyboss:
When I notice that, I reboot the phone, and it stops being a problem, usually for at least the rest of the day. I don't know how to keep it from coming back, though.

I think this is the only battery life problem I have--when I notice the battery dropping more than my usage should justify, I always see Android OS with an abnormally large amount of CPU time.
[Captivate Android Development] z28james:
If you have a corrupt file on your SD card somewhere, "Media storage" will keep the phone awake and will sometimes peg the CPU. Clearing application data for that application fixes it until the next time your phone scans the SD card for new files.

Also, I noticed that if you switch from cell data to wifi while a google app is trying to sync, the gapps service keeps the phone from sleeping (this happens to me when I go home for instance and my phone automatically attaches to my wifi AP). At that point, ill kill the market, kill gmail, etc as its not usually obvious which one is the problem exactly.I have a system monitor app which shows each process and its cpu usage, so its a bit easier for me to spot the offending processes/services but these are usually the ones that give me problems.
[Captivate Android Development] markdexter:
noticed this coming up for the next nightly cm: Bump versions for 7.1.0-RC1

This mean where one step closer to a stable?
[Captivate Android Development] markdexter:
Good info, thanks mate
[Captivate Android Development] jhernand1102:
If you click on that line it will send you to the page and you can scroll down and see the devices it is for. Not for us yet.
[Captivate Android Development] nyciz:
+1 BT works for headset speakerphone on WM7 laptop but music and Audio fails

I'm on #36

Edit: removed and paired phone with pc, driver software says ready to use but then at the very end I see Driver Software Installation and it shows:

BT AV Source Ready to use

BT AV Remote Control Target Ready to use

BT Peripheral Device No Driver found

BT Peripheral Device No Driver found

BT Headset AG Ready to use

BT OPP Ready to use
[Captivate Android Development] ls377:
I think it just wasn't added in that part. There was another commit for adding Galaxy S to the changelog, so it might still be for us.

Sent from my Captivate
[Captivate Android Development] RockRatt:
Sorry. Double post
[Captivate Android Development] RockRatt:
Yep same here, I noticed that and thought maybe I actually didn't apply the zip themer in cwm. Bummer. Maybe I will go back a ways then too.

EDIT: It might be kernel related unless I just broke/lost some functionality that I am not seeing yet. I installed The Escapist Kernel#4 on top then applied the zip themer addon that I had just created and now zip themer is working and applied correctly. I have been on the stock kernel lately and had no issues and I am sure I am losing something from the newest updates since. But it still shows that I am on the current nightly from today but with the Escapist Kernel. Oh well see how everything else functions.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] arcardinal:
Zipthemer doesn't seem to work, but you can use Metamorph. That's what I've been doing.
[Captivate Android Development] smeltn:
works fine here. Tell ya the easiest way.. is to set up web connect in ROM Manager

http://www.koushikdutta.com/2010/09/new-rom-manager-feature-web-connect.html

Then click on the rom manager link on the side and it will auto download through rom manager and install it for you..

http://goo-inside.me/captivate/radios
[Captivate Android Development] z28james:
No problems that I can see.
[Captivate Android Development] Johnston212:
How is that going for you? I'm on 34 for the first time, downgrading from 35 and I'm not 100% sure about the battery. It doesn't seem to be draining as quickly as 35, but not quite as good as 31 or 32. Just wanted to get your opinion on it.
[Captivate Android Development] hkk:
Force Close Problem

Hey guys,

I have been on CM for a while, and has been working great. Since the last several weeks, I am running into a problem. The phone would report any one of the applications as Force Closing, and next thing, every app is force closing, and the phone becomes unusable. I tried going into recovery mode, and doing 'Fix Permissions' (based on some search results in the post). Sometimes it'd help, sometimes not. I would go back to stock using Odin, flash CM. Things would work fine for a few days, and again back to Force closes.

A few days ago, I decided to clean out the phone completely, and start fresh. So I backed up all my data to my pc, wiped internal sd card clean, went to stock, and flashed CM7. Made sure the internal SD card had several GB of free space. In about 3 days, I am back to the same problem - force closes.

I tried to capture logcat, but couldn't find the instructions to do that, and I was in a hurry to get the phone to a working state.

What are the possible reasons for this issue? Is it software, space, hardware, something else?

Any help would be appreciated.
[Captivate Android Development] EnemyOfGlaDOS:
I had that problem a long time ago.. long before the merge. I did exactly what you did besides fix permissions. Although it sounds like you got it worse than me. Try a factory reset. Last time it happened to me i did a factory reset and haven't been to stock since or had that problem since. Not sure if it's the solution, but it's worth shot if you've got nothing to lose:rolleyes:
[Captivate Android Development] Smasher816:
Force closes can also be caused by a full datadata

See if you can find its usage with the "df" command in terminal/adb

For logcat its the logcat command to store it type "logcat > /sdcard/logcat.txt"