yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] EnemyOfGlaDOS:
Only flash twice if you have to. Flash and reboot.. if you get stuck in a bootloop, you can flash again.. but that bug should be fixed.
[Captivate Android Development] jhernand1102:
I flash the RC1 with ROM manager with no issues. Didn't have to do it twice or reinstall google. I think they have fixed the issues it used to have.
[Captivate Android Development] PhoneTay11:
AT&T CyanogenMod 7 #43

I couldn't add new contact (new number )and unable to disable call forward ( network error ) .I couldn't find somes downloaded games .sound is too small (max volume).
[Captivate Android Development] EnemyOfGlaDOS:
Nice, good to know :)
[Captivate Android Development] littlewierdo:
FYI re Nightly #44

Its going to do some wonky things on initial boot, mainly, the Cyanogen logo will restart multiple times (I counted 3 or 4) and some minor screen flicker between each animation. Just let it sit and after the third or fourth animation restart, CM will boot the phone up just fine.

After the initial reboot, I restarted the phone for good measure without any problems.

I was preparing to have to redo my phone, boy am I glad I dont have to do that tonight, am really tired and dont feel like tinkering with my phone.
[Captivate Android Development] lanisan:
So I'm about to go on a lengthy roadtrip today and before I do considering the latest nightly.. I have RC1 CM7 on my cappy and I guess I didn't realize there's a difference? So.. what's the difference between RC1 and the latest nightly?
[Captivate Android Development] Enhanced:
http://cm-nightlies.appspot.com/?device=captivatemtd

The difference is everything after the RC1 and before the nightly you want to install.
[Captivate Android Development] EnemyOfGlaDOS:
Not much.. but you can always look at the changelog. Like has been said, nightlies are untested builds that will roll out in between RC releases. If there is something in the changelog that your interested in having, than flash the latest.. or wait till the next one..
[Captivate Android Development] lanisan:
Ahh I see so rc1 is pre ... say build 24 (or 41 which I believe is the latest)
[Captivate Android Development] EnemyOfGlaDOS:
RC1 came out I think around #40 or 41.
[Captivate Android Development] Yaantra:
RC1 came between 40 and 41. All nightlies after RC1 are built on the RC but may not be as stable as the RC release as they have more experimental / development stuff built into them... If the stability continues with more experimental refinements we will soon see another RC being released... just think of it as a whole number with fractions inbetween...
[Captivate Android Development] tjsooley:
have a 1007 on cm7.1 newest nightley.

I have had problems with what I think is sleep death.

After about 1-2h of the phone being in my pocket I take it out and hit the power button to wake it up and all that happens is the soft buttons come on but the screen does not.

I am not using a custome kernel or anything. I have reset to stock and same issue I have wiped data and same issue.

I am using jp6 modem. any ideas?
[Captivate Android Development] skatcat31:
stock on click, format, factory reset, CM nightly, format, factory reset. Happened to me a couple dozen nightlies ago and this fixed it.
[Captivate Android Development] scottlinux:
How is 720p video recording, recently? That is unfortunately a deal breaker for me.
[Captivate Android Development] EnemyOfGlaDOS:
she's workin like a beaut! :D
[Captivate Android Development] Haas360:
Is BT back up and working for any of you?
[Captivate Android Development] EnemyOfGlaDOS:
Bluetooth was noted FIXED in nightly #39. Should be working :). Works for me, but I'm using a custom kernel.
[Captivate Android Development] bubbad58:
I am on nightly 41 and BT is working great
[Captivate Android Development] kurrptsenate:
I'm still having an issue when making calls, but at least I've learned more about the issue. If i make a call and I'm the first to hang up, there's no issue. But, if someone calls me and hangs up before I do the screen will remain black until i either reset the phone or hook the phone up to a computer.

I've tried every nightly since 32 hoping the issue will eventually get resolved but to no avail.

As far as the video recording goes, it will record at what it says is "HD", but compared to the stock app, its nowhere near as good. I have replaced the stock camera app with vignette, which is a very good replacement. The phone doesn't actually zoom like the stock one does (which allows you to view the picture zoomed in) but after capturing the picture it gives you the same effect. I'm still trying to find an apk that is comparable to the stock video recorder.
[Captivate Android Development] solarpenguin:
Depends on what version you are flashing from. Starting around 30-something that bug was fixed and only required one flash from that point forward.

I like cwm as I can wipe cache and then flash from SD...guess it just gives me a little more control.
[Captivate Android Development] Yaantra:
Reposting from RC1 thread...
[Captivate Android Development] jhernand1102:
I answered in the RC1 thread. there is no way to do it.
[Captivate Android Development] aHecticLife:
Any update for the 720p ? Because my video recording keeps on frame skipping. :(

Edit: Wait, so if I update to nightly #43, 720p would work? :D
[Captivate Android Development] Smasher816:
I think i found an answer and posted it in the RC1 thread.
[Captivate Android Development] aHecticLife:
I have a problem after the nightly update where I can only change live wallpapers and not non-live wallpapers :(
[Captivate Android Development] musicalmindz:
Im upgrading from Nightly #24 haha so I have a feeling I should just do it from CWM to be safe. I'm just gonna go to RC1 and see how the battery life is on that and then maybe get back to the nightlies.
[Captivate Android Development] zmore:
Why would you think that? Nothing in the changelog since RC1 says anything about it, and nothing is to be expected either. If you really want smooth 720p encodes, use Cognition instead, or another ROM that uses Samsung's special sauce. The jerky 720p is a small tradeoff for all the other pluses of CM7.
[Captivate Android Development] PhoneTay11:
how to use custom ringtones on CM 7 samsung captivate

please give me idea how to load custom ringtones to CM7 Captivate and set it as phone ringtone. Thanksss
[Captivate Android Development] EnemyOfGlaDOS:
Same as any other ROM. Use an app to find or get whatever ringtone your looking for. Then in settings> sound> ringtone notification ...that's where you set it as ringtone. Or if you open and edit a contact you should be able to assign custom ringtones to a contact.

I've always liked zedge ringtones and wallpapers.
[Captivate Android Development] hernan078:
Hi im having a problem it seems like my date is messed up, I reset my phone, factory reset, cleared cache and everything but my date and time continues to be messed up. The twitter app says that a tweet was sent July 2 but where I live the time is still 11:56 please help because I think that by having a wrong time I can't useny favorite twitter client (twicca) thanks in advance
[Captivate Android Development] aHecticLife:
Does GPS work for any of you guys!?
[Captivate Android Development] Jusrertiner:
On nightly 42 the camera doesn't work properly
[Captivate Android Development] Johnnie5000:
Try todays nightly (#46).
[Captivate Android Development] cotr:
why are they adding droid2 and 1080p Tegra recording capabilities to the captivate nightlies?
[Captivate Android Development] peachpuff:
That log shows changes for all devices, not just for the captivate. Click on the other devices and you'll see that the log is identical, the only thing that changes is the link to download the nightly.
[Captivate Android Development] PhoneTay11:
When I edit a contact I can't be able to assign a custom ringtone to a contact.

What kind of APP Do you use to find ringtone ?Where do you get zedge ringtones & wallpapers ? I want to try. Thankss
[Captivate Android Development] EnemyOfGlaDOS:
Your right.. I tried to assign a ringtone to a contact and had trouble myself. Download Zedge from market. Find a ringtone (zedge even has a search bar) download it, then select ringtone in settings>sound. Not sure about the contacts though.. I thought it would be easy .. ill mess around and see if I can figure it out :p

*update* ahh.. got it. Just select a contact and then press the menu button.. then options> and you'll see ringtone is set to default. Select it to change.
[Captivate Android Development] RCACO:
I've been a bit out of the loop over the last ten builds. I hopped onto 46 this morning and now cannot connect to google's servers. I'm using the JL3 radio if that's worth anything.

Please advise.
[Captivate Android Development] tiuk:
You need to flash gapps, rom manager is the easiest way.
[Captivate Android Development] RCACO:
Should I do a nerd-load and rebuild everything? I cleared dalvik and user cache before loading. Do I need to review the changelog to get some answers? Will flashing gapps over my system cause issues with existing Google installs?
[Captivate Android Development] PhoneTay11:
I have tested Videos on Captivate CM7 #43 (GRJ22) .Volume was too small and even MAX (mpg4) without headset.Any advice How to fix it ,please?Thanks
[Captivate Android Development] melbourne408:
No never an issue, besides the immediate notification of green bars to only white, the gapps will still be there. Another quick way to know you need to reinstall them, as it happens to me is simple, click gmail for example and if it pops up very briefly and disappears then its an automatic sign of having to do just that.

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] n0stalgia:
Next nightly looks MEGA. Hopefully the work on media scanning fixes the AndroidOS battery drain issue.
[Captivate Android Development] dabels1961:
Man, everyone and their obsession with battery life :) don't see how that one would lead to better battery life.
[Captivate Android Development] aHecticLife:
I cant seem to find the Lbstestmode for the Cyanogen Nightly.

Any workarounds ?
[Captivate Android Development] hernan078:
my google apps keeps forceclosing me, the framework fails and then all my apps force close, im in need of help i cant have a working phone for more than a couple of hours, and apparently something is wrong with time because the hours in the app dont match with the hour of the cellphone

edit: apparently if i add a day to my date my cellphone works great, but i dont really like that i will use it like this for a while but i want to be able to fix this thanks
[Captivate Android Development] musicalmindz:
Well that worked smoothly, didn't even manually go into CWM, just downloaded RC1 from Rom Manager, checked Google Apps, wiped Dalvik Cache, backed up current rom and let it do its thing.

RC1 installed flawlessly! No double flashing needed, BT is working well, camera/video is good (as can be expected for CM7), and I guess we'll see if battery life has improved since nightly #24 haha.
[Captivate Android Development] CougarBroker:
backup, install a nightly, wipe data and cache, restore apps and data.
[Captivate Android Development] melbourne408:
Hmm, maybe I got a bad download will try again. Just had to go with an old backup trying nightly #47, just bootloops, I'll check

.md5 and attempt again, report back.

(Edit-sleep deprivation had me forget summfin but it's all gravy now, nice work!)

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] EsotericSYN:
Flash it twice and it wont bootloop =)

Sent from my SGH-I897
[Captivate Android Development] solarpenguin:
Great!

Batt life is always a challenge when left to its own devices. I've been using juice defender (and then bought juice defender pro because I liked it so much) for nearly a year. It helps manage battery life with great results. I've had a few annoyances with it, but nothing major and certainly better than running out of juice! Check out the free product and see if it helps you out.
[Captivate Android Development] melbourne408:
Wasn't the case this time :) , I think I just had something left in there from voltages and glitches kernel somehow , oddly first time to format/wipe for a long long time, looks good haha. No sleep or coffee hmmm. :D

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] MZeora:
The jig did the trick, everything else had me doing the reboot and such. So to anyone reading this who doesn't own a jig - go get one (got mine for 7 usd), it might save your life.

Sent via XDA on CM7 Captivate
[Captivate Android Development] hernan078:
I have done that the problem is the time I have to use my phone with a extra day, I haven't had any problem, what I need to fix is the time of my phone, for example I use twicca as my twitter client, if I put the correct date on my phone twicca will not work, it would not search for tweets, thank for your help.
[Captivate Android Development] melbourne408:
You've told me you can and know how to change your time, being it a day ahead for your tweets to remain accessible, twitter seems to be chirping in just fine here on my end. Are you using the 6/13 gapps? Here I'm trying to help you out yet again, just not keen to the arrogance pushed on my side. :)
[Captivate Android Development] musicalmindz:
Actually there must have been something wrong with build #24, I used to leave my phone unplugged at night to test battery life and it would be close to dead by the morning but since getting RC1 it went from 91% -> 71% over night with no charge. Woohoo! Back to being usable.

I usually have charge most of the day so I'm not asking for miracles or even stock level battery usage :)
[Captivate Android Development] flucks:
This may not be the best place to discuss this, but I think I have found a bug.

When I put my phone in the official dock and set the phone to stay away while charging, the phone refuses to stay on. I am not sure what the problem is or if it is a phone deal or what. Thank you so much for all the work you have done on this rom. This is by far my favorite rom.
[Captivate Android Development] impulser91:
You need to install the home dock from the samsung apps, or in application settings/ development turn on Always on while plugged in
[Captivate Android Development] flucks:
Yeah, I have done that. It still won't stay on in the dock. Any other way I charge it, it stays on. I am really not sure if it's the rom or the dock. :/
[Captivate Android Development] rwells813:
47 feeling pretty good, can't find a problem that isn't already known.
[Captivate Android Development] singlebeam:
Running great for me as well but it broke the Email.apk w/o exchange security that I got from here

I've been able to use that Email.apk with every release previous to 47.

**EDIT** I updated to 48 and it works just fine now. I flashed back to stock for this update and the problem went away. I'm guessing it was an issue with a previous update flash and not CM.
[Captivate Android Development] Jusrertiner:
Does deleting data delete internal sd card. I like forgot.
[Captivate Android Development] melbourne408:
Formatting data will delete all texts and info like stuff saved into the phone, won't wipe the sd card
[Captivate Android Development] Jusrertiner:
Thanks
[Captivate Android Development] darcjrt:
I just got a bricked I think cappy from my friend. Apparently he installed cyanogen on a cappy that does not support button combo. Now it goes into boot loop on cyanogen boot screen. How can I recover this cel? It wont go into download mode plugin the phone to the usb port with odin. it wont go into recovery mode. It just boot loops. I guess they tried to flash a rom over cyanogen without using odin?? What can I do pls help!!
[Captivate Android Development] Haloruler64:
It's bricked. Useless. Send it to me, I need parts.

Seriously, research JIGs. Buy one on eBay or make one yourself! It'll send your phone into Download mode even if you don't have the button combo.
[Captivate Android Development] darcjrt:
I have one I ordered on the internet. When I plug it the phone just turns on and go into boot loop. It might be broken the jig?
[Captivate Android Development] melbourne408:
Agree, sad to say :(

You could try this, stumbled in it yesterday :D

http://xdaforums.com/showthread.php?t=1153310
[Captivate Android Development] Haloruler64:
I donno. Maybe it's a bootloader issue, if a JIG doesn't work. I say wait for others opinions... i don't know what to do.
[Captivate Android Development] darcjrt:
GOT IT WORKING!!!!!!!! Thanks guys!!! The jig is broken. Just moved the resistor a bit and it worked!!! Thanks a lot!!
[Captivate Android Development] melbourne408:
Dope, hadn't got the chance to test it on one of my ungrateful friends cappys haha, glad to know it did the trick, happy fourth! :D
[Captivate Android Development] dpmurphy81:
Build #47

This is the best build so far for me, Battery life with moderate usage lasted 21 hrs. unplugged so yea I thinks this build says it all. but I'm sure some of the heavy users will have a great deal less but not to bad for moderate phone usage. and it is also super smooth.
[Captivate Android Development] atinm:
Only on supported devices. SGS phones are not supported yet.
[Captivate Android Development] kurrptsenate:
I've figured out the problem with the "black screen of death" and the causes of it (proximity sensor) but I have yet to find a reliable fix for it.

Basically, my phone is great until a make a phone call. At this point, as soon as the phone detects something close to the sensor, it causes the screen to go black. The problem lies in the fact that if the object is then taken away from close proximity of the sensor, the sensor is too dumb to notice the difference. I've tried a few apps to fix this problem but instead already proved to me what it was actually doing.

Now that I know what is causing the problem I believe I'm half way there to finding a solution. I need to either turn the proximity sensor off completely during a call or find some way to change the settings of the sensor to show its always unblocked.

Does anyone have any ideas how I could do this? I've tried 'proximityscreenoff' and a few others that were supposed to wake the phone up. As of now, I have to shine a bright light at the sensor, or what I normally do is light my lighter really close to the sensor to get the screen to kick back on.
[Captivate Android Development] base88baller:
how are builds 48 or 49 treating everyone?
[Captivate Android Development] EnemyOfGlaDOS:
I hear 48 is working like a charm...
[Captivate Android Development] kurrptsenate:
I'm on 49 and haven't ran into anything yet (minus BSoD)
[Captivate Android Development] atinm:
I need a dmesg from this to see what is happening. As no one else seems to have this issue, I think it might be your sensor's sensitivity.
[Captivate Android Development] shotta35:
I figured it must be his phone because even the other issue of first call after boot up was fix a few nightlies ago with a kernel update it seems.

I don't have any of those issues he mentioned - running 49 now but can't say much yet as i just installed it. Will be testing it out today :)
[Captivate Android Development] kurrptsenate:
I'm a bit of a layman when it comes to certain terminology... Does that mean debug message?

How would I go about sending this to you? The phone is only 1.5 months old by the way. Not ruling out the possibility mind you, just giving more information on the subject.
[Captivate Android Development] base88baller:
i installed 48 this morning and so far so good. just had to flash twice to get out of a boot loop. performance and battery life seem great.

what happened to the LED notifications option in cm settings?
[Captivate Android Development] kurrptsenate:
I did a little research and learned what a dmesg is and how to create one to send along to figure out where the is caused. The problem with adb is that my computer has not yet been able to detect my captivate since I switched to CM7. I've updated sdk as many times as I could and tried to manually install the drivers through my manager, but to no avail.

Is there any way to get this dmesg file straight from my phone and post it to the SD card? I am able to mount the card and transfer files in that manner but right now I'm having zero luck with adb detecting my phone.
[Captivate Android Development] cotr:
Increase Headset Sound

Is there any way to increase the sound output from the 3.5mm jack?
[Captivate Android Development] jhernand1102:
Download Voodoo Control from the market.
[Captivate Android Development] Jemack:
Voodoo control app.
[Captivate Android Development] cotr:
awesome. "thanked"
[Captivate Android Development] kurrptsenate:
I figured out how to get this dmesg you were asking about. I had to use terminal emulator, figure out how to copy the output to a text file, then use root explorer to put it on the "root" of the SD to be able to copy.

I should have the link for you shortly. Thanks for the help. :D

http://www.megaupload.com/?d=TPOQTK96

If there's anything else I could do to aid you in helping me solve this I'd be more than happy to oblige.
[Captivate Android Development] EnemyOfGlaDOS:
It was taken out a bunch of builds back. You can grab the cmparts.apk from an older build though and slap it in your next update ;)
[Captivate Android Development] XsceneXhippieX:
multi-rom browser FC

NOTE: exclude nightlys 48+ from this post, i only tested up to #47

i am going to be posting this in the cm7 and the miui threads because im experiencing the exact same problem with the browser on both roms and was wondering if anybody could shed light on this:

the browser will force close, A LOT, like google loads and then i go to xda and FC, i go to www.theberrics.com/dailyops it FC's, basically i cant browse the internet for more than 30 seconds to 2 minutes without getting a FC. this goes for EVERY browser (ie stock, opera mini/mobile, skyfire, miren, dolphin...) i am experiencing this on cm7 nightlys, cm7.1-rc1, and miui 1.7.1 and getting better results with miui now that ive uninstalled auto-killer memory optimizer for some reason.

what i find extremely weird is on any cm7, and with miui until a few hours ago, i keep getting FC's of google.framework.services, gmail, the market wont download things or gives me the "not enough space" error with 1.4gb of free space internally, the amazon app store FC's at the same time as all the others and it gets better then worse, ive cleared google services framework's data, the market's data, reinstalled gapps, installed the gapps for 2.3.3, fixed permissions over and over, reflashed the OS, nothing has worked to stop this error im getting, stock and glitch kernels both act the same.

MIUI 1.7.1 has had none of said FC issues today, so the browser problem is what im more worried about. nothing has FC'd except for the browser today not even once, and i didnt do anything different, just charged the phone overnight like usual and deleted autokiller like i said before which i believe is the culprit.

but i would really like to be able to switch between cm7 and miui without experiencing the issues i am speaking of on either and i have seen a few similar reports but nothing quite like this, i followed the standard procedure for flashing the rom every time (ie wipe data/dalvik/cache before and gapps after, then another wipe of the cache/dalvik before booting) because i have a backup of a working market (finally) and no service whatever FC's i am going to attempt to get a logcat of the browser FC'ing tonight for reference if i have any time, but yeah anybody have a clue as to why every browser i install FC's on cm7 AND MIUI even though they are completely different? i figure the gapps errors are due to a corrupt gapps .zip, but i can fix that, i cant figure whats wrong with the broswer but i just got this captivate and it sucks not being able to simply browse the net on any of my roms >.<

sorry for the looong post