yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zacharias.maladroit:
I'm sorry if that sounded condescending - it wasn't :o

don't take things personally or too seriously here

the biggest part of the users here are not experienced in any way ("noob" how they call themselves - all of us were one at one point and still are in several areas of our lifes)

and oftentimes almost kill their device due to 1:1 copy & paste

therefore I had assumed that you'd adapted the command from the post before you & not actually knowing what you're doing

just wanted to help :)
[Captivate Android Development] ninjuh:
I've spent daaaaays running this rom going back and forth between different roms, here are my results with the green/white signal bars.

I ALWAYS have a Google account associated with and inputted into my phone.

I NEVER use auto sync

At the beginning of writing this my bars were white, now they're green again.

I conclude it is SUPPOSED to work the way you guys claim, however this is a BUG.

End of story I win kthx

MOD EDIT: Don't use foul language
[Captivate Android Development] techmik67:
reported for language, kthnx
[Captivate Android Development] Kaik541:
so I guess the fact that it works fine for absolutely everyone else is just a fluke? it isn't a bug as it works on every device running gingerbread. go ahead and start the ROM from stock and never sync a google account (do it for an hour at most) and see how it will never turn green. there is no bug as it works the way it is intended, your issues are unique and you have no logs or proof, therefore it doesn't exist and you are wrong.

also, reported (and edited quote) for language.
[Captivate Android Development] born_fisherman:
Am I missing something or is the option to use battery percentage gone from cm settings?
[Captivate Android Development] born_fisherman:
Has anyone been able to get matted blues theme to work?
[Captivate Android Development] skoNuff:
On the 4/11 Nightly and option is still there for me under CM Settings/Interface/Status bar tweaks
[Captivate Android Development] smeltn:
There is a Matted Blues specifically for CM7 for us and is updated to the most recent nightlies.
[Captivate Android Development] born_fisherman:
Lol. I'm 100% sure I went into every sub menu and did not see that :) I even went into the power widget controls and made changes.. I need some sleep
[Captivate Android Development] born_fisherman:
I see it now.. must have overlooked this. Thanks.

The evo version wasn't working too well ;) it did make my market blue however! Other than that just a nice boot animation and continuous boot loops
[Captivate Android Development] tysj:
I know I've read about this before but never read about the answer since I didn't check this thread that often then (wasn't running CM7, was just checking out of curiosity). Is it a common problem that the signal bars in the notification bar get "stuck"? There are times when I know I am in a terrible area for reception (manufacturing lab) and it shows on other roms on the same modem, has slow data speeds in real use and speedtest. A reboot seems to fix it, was just wondering if it was common or it was just me.
[Captivate Android Development] Smasher816:
Quick quesrion, How would I go about doing a full charge to wipe my battery stats while in cm7, seeing as you can't charge with the phone off. My battery stats are jacked. Thaks for your help.
[Captivate Android Development] EnemyOfGlaDOS:
I believe you can wipe your battery stats in recovery. I've noticed after a couple days of empty to full charges, my battery behaves quite nicely. (After installing CM7)
[Captivate Android Development] Rikusaki:
Amazing work, CMSGS Team.

This rom is just amazing. The difference in performance and fluidity is so great that it's like a completely different phone.

My only issue is with the camera. Slow, buggy and no 720p@30fps.

Amazing work, CMSGS Team. :cool:
[Captivate Android Development] oxlong27:
i also have this problem. never found a fix. is your cappy a build number 1007 by any chance? reboot does not fix mine however. also had this with miui. it bums me out its kinda a deal breaker for me cuz i have bad signal at my house and cant get an accurate signal reading would love to be able to run this rom i love it but i cant til i find a fix. if anyone knows the problem or how to fix it please pm me thanks
[Captivate Android Development] bazald:
Sorry about the delay. Do you still want me to do this?

Edit: /sdcard/bmlovermtd.log didn't seem to be present for me either, IIRC.

Edit2: Does the sdcard have to be unmounted to make the logfile accessible?
[Captivate Android Development] contentryder:
Does CM7 have automatic call recording feature or can it be installed?
[Captivate Android Development] soypoi:
I used to wonder what the big deal was about CM, what made it special. After using it for a couple of days, I can see why it's so popular. Excellent work!!
[Captivate Android Development] tysj:
Yeah it's a 1007.
[Captivate Android Development] atinm:
No, I think I made a mistake - the file is not being created. But some other issue happened that is screwing with installs. Hopefully 04/11/2011 update fixed your issues.
[Captivate Android Development] alkiter:
Holy crap! 10.7 Mbps down, 2Mbps up on wireless!

Any way to assign individual ringtones on contacts?
[Captivate Android Development] waffle418:
In contacts... under options... Ringtone... ;)
[Captivate Android Development] skoNuff:
On 4/11, I noticed that the Notification bar stutters on pull down. Once your finger is lifted from the screen.. the bar jumps, then continues down. It's nothing major, but I never experienced this problem prior.

Also, I had reported that my green bars would fluctuate to white constantly on 4/11.. however, when I went back to 4/2.. it was happening on that build as well. Possibly a problem on Goog's end?? I went back to 4/11 now.. if the devs would like a log cat of anything.. please let me know.
[Captivate Android Development] ctleng76:
I say just ignore those who complain and aren't willing to help. Don't let it get to you. It's funny how so many people in these forums on XDA think that the developers owe them when things don't go well. Remember everyone, these guys are doing this work FOR FREE! They are volunteers, and generous ones at that. I for one can't wait to see the final result of all the work from this team. We should be grateful that someone has decided to take ownership of Cyanogen for the Captivate!
[Captivate Android Development] zas0006:
Had an odd issue with blacklist again. Phone just starts ringing and wont stop till I either cycle through all of the ringer options in the notification bar or reboot.

Logcat after the link:

http://db.tt/kOek6sB.
[Captivate Android Development] inneyeseakay:
I had this issue on earlier build... was written off as non-issue because I couldn't replicate it and didn't get a logcat. Glad to hear it wasn't just me.
[Captivate Android Development] rabi347:
I am using CM7 with the latest update, I flashed the trident kernel.

After I use the phone over the bluetooth in my car, a weird thing happens. As soon as I end the call, the music player comes on and starts to flash but does not play music.

Nothing is usable after that. I either have to turn off BT or restart the phone. After that, the phone starts working properly again. Can somebody please tell me what's going on with my phone.
[Captivate Android Development] shaolin95:
Does it happen with the stock kernel too?
[Captivate Android Development] rabi347:
I actually don't think I tried with the stock kernel ! but I am going to try the stock kernel and see what happens.
[Captivate Android Development] zas0006:
Well hopefully now it can be looked at. If anyone needs more input to figure this out just pm me and I will provide any info I can to help y'all fix this.
[Captivate Android Development] APE992:
I'm getting this now myself. Seems after over a week this bug has yet to be fixed.

Back to stock, I can't deal with a phone that continually reboots into recovery even after doing every "fix" mentioned here.

If "no misc partition" isn't an error, don't have it pop up saying there is a problem then eh?
[Captivate Android Development] RockRatt:
No miscellaneous partition is the norm with this rom. I believe it was put in for future use or something along those lines. It still comes up whenever flashing even for those NOT having any issues with booting or anything else.

Not booting is either bad boot blocks (happens to me with one of my phones) or it could have been a bad download/bad flash possibly. I am not sure what FIXES you already tried but if you didn't re-download I would try that. Either download straight to your phone or to a PC and paste it into your phone. If you have tried that and it doesn't work it is possible the bad boot blocks is what is causing it.

On my bad boot block phone I can run the initial kernel, initial rom and have everything working. BUT if I try to change a kernel or run an update zip it seems like it goes through and then I use the reboot system now from cwm. The att screen comes up and it is stuck there. If this sounds like what is going on with your phone then most likely it is bad boot blocks. Hope this gives you two an idea of what may be going on.

Sent from My KickAss Captivated CM7 OC'd 1.4Ghz/Undervolted
[Captivate Android Development] shaolin95:
First you are one of the few I have seen with the "issue" second if you cant deal with a beta ROM then dont install it eh? :rolleyes:

Nobody is going to miss a complainer with 14 posts and demanding support for something he pretty much is the only one getting....gotta love it.
[Captivate Android Development] APE992:
I just reverted to eclair stock, dropped Rom Manager back on (which didn't install properly the first time but did the second) and reflashed my daily driver which is booting up just fine right now. Not quite finished but it looks fine.

Regardless CM7 was booting into recovery each and every time. If it didn't write correctly I'd like to know where I can get a copy of Clockworkmod recovery that bothers to check to make sure what it writes actually gets written out.

Yeh so I don't post here often, big deal. So XDA approves of more senior members crapping on junior members for any reason they see fit?

FYI, I'm not "demanding" support for anything. If you bothered to read my post you'd notice I'm not asking for support at all, more a disgruntled bug report. But don't let that get in the way of your crapping on me.

Something constructive:

The only clue I had was when I went to do a factory wipe and this popped up:

format_volume:make_ext4fs failed on /dev/block/mmcblk1p2

Which sounds vaguely familiar as part of a lagfix done a while ago.
[Captivate Android Development] techmik67:
1 - your post *does* have attitude ...... "...seems after a week this bug hasnt been fixed..." tons of attitude.... "...if it's not an error, then dont have it pop up..." so now your a developer and know better than them how it should be done, huh?

2 - If you'd bother reading, you'd see that it's only the latest update that has that issue of not booting. try either 4-10 nightly or the one right before that one..... no "bug" of the misc partition notification, and it works fine, no booting only into recovery issues.
[Captivate Android Development] techmik67:
nothing to do with a lagfix..... mmcblk1p2 is ext-sdcard....
[Captivate Android Development] tjsooley:
do we still have these bugs?

* Polling problem on RIL (works after lock and unlock)

* 2G/3G toggle (works if no data connection is active)

* Compass (works not at 100%)

* TV-Out

I did try to search on both this forum and the cm forum to find answer but nothing thus far.
[Captivate Android Development] APE992:
It might but that doesn't seem reason enough for someone to crap on another user for having a low post count as if it means something beyond how many entries you have in a database somewhere. As a developer I do find it really annoying when someone tells me "oh ignore that it isn't a real error". "Just ignore that check engine light it got set off by*KABOOM*"

Clearly in this case your phone won't explode.

2) I'll 4-10 a try and see what happens. Thank you for being helpful.
[Captivate Android Development] shaolin95:
Of course you are not demanding support...sure....like anyone can see what you are doing mate. And no is not a senior member crapping on a junior member...dont act the victim now...is about not allowing someone demanding fixes and acting all offended because you cannot fix that issue that pretty much only you have. So like I said, you can act like the victim all you want but the rules are simple, it is beta , it may have issues, almost nobody else has yours...sorry, dont like it ...move along.

Regards
[Captivate Android Development] APE992:
That's nice.

4-10 didn't fix it either. Just boots straight into recovery. Guess there is something wrong with the phone itself.

Though I did find an answer for the misc error:

"E: no misc partition found

Don't care about. We've simply no misc partition."
[Captivate Android Development] bugity:
My phone also at one point kept booting to recovery only.. I used one click odin to stock the reflashed a clean copy of cm7 and i have not had an issue since. But there was an issue my buddy had with his epic that it only had a non working clockwork recovery and nothing else , all flashes failed even backups. Not even a jig worked it like mystically lost all usb info in device and after 2 weeks of trying things we sent it back to samsung. that is the ONLY time i hav ever heard of something being stuck permanently at recovery.
[Captivate Android Development] joeybear23:
When in Recovery, Choose "mounts & storage" and format /system, /data, and /cache

Next, apply the newest zip
[Captivate Android Development] nkrick:
I see the same thing. I am not sure anything in a logcat will help, but I will provide one if requested.
[Captivate Android Development] nkrick:
The bug list is current. Most of these bugs are non-issues or easily worked around so don't let the list prevent you from trying CM7 unless one of these items is critical for you.
[Captivate Android Development] NiXXeD:
I had the same issue with the no booting. All I can say is follow the install instructions. I missed a step on my friends phone and it did that.

Pretty sure it had to do with having a correct kernel to run the efsbackup under.
[Captivate Android Development] mwiz123:
How the heck do u install it

HOW DO U INSTALL IT THIS IS MY THIRD DAY AND

[YOUTUBE]http://www.youtube.com/watch?v=mLNv_-sEng4[/YOUTUBE] IS NO HELP WHERE DO U GET ALL THESE KERNELS HES TALKING ABOUT:mad::mad::mad::mad::mad:
[Captivate Android Development] Kaik541:
if you can't follow the instructions listed in the post, then this ROM isn't for you. we aren't going to help you through the process of learning to read.
[Captivate Android Development] joeybear23:
INSTRUCTIONS - FIRST TIME FLASHING CM7 TO YOUR SAMSUNG GALAXY S SERIES PHONE:

01. Make sure your phone is fully charged! Update process will take some time.

02. Make sure there's enough free space at your internal sdcard (200MB)

03. Make sure you've not disabled HSPA by using the dialer code *#301279#

04. Download following files from sourceforge: Captivate | Galaxy S | Galaxy S B | Vibrant

- DEVICE-efsbackup.zip

- cm7-DEVICE-initial-kernel.tar

- cm7-DEVICE-initial-XXXXXXXX.zip

05. Copy following files to your internal sdcard

- DEVICE-efsbackup.zip

- cm7-DEVICE-initial-XXXXXXXX.zip

06. Use the attached Update.zip to get CWM

07. Reboot into recovery using 3-button-combo and apply DEVICE-efsbackup.zip.

- Don't use "reboot recovery" command or other shiny things to do this!

08. Flash cm7-DEVICE-initial-kernel.tar as pda using odin without auto-reboot and without re-partition

09. Reboot into recovery using 3-button-combo

10. Choose "mounts & storage" and format system, data, cache

11. Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip

12. Do a factory reset / data wipe!

13. Reboot

14. OPTIONAL: Copy Gapps to your internal sdcard and flash it at recovery.
[Captivate Android Development] Thegodfather156:
We are getting updates like crazy!!
[Captivate Android Development] joeybear23:
???

Just a teaser??
[Captivate Android Development] Rikusaki:
If you can't read, this rom isn't for you. ;)
[Captivate Android Development] mwiz123:
its Beautiful :)

i could use the epic style lockscreen
[Captivate Android Development] photosbynick:
What theme is that fr your home screen? That looks dope
[Captivate Android Development] tjsooley:
is anyone having problems playing videos I get audio but no video on mp4's.
[Captivate Android Development] Rikusaki:
Not a theme. :)

Just LauncherPro with the SiMi Clock Widget, the LG Weather/Clock Widget and this wallpaper:
[Captivate Android Development] Thegodfather156:
I'm a tease
[Captivate Android Development] bsi007:
Originally Posted by Rikusaki

If you can't read, this rom isn't for you.

-------

Don't be a jackwagon! We were all newbies at some point...idiot
[Captivate Android Development] techmik67:
he's 100% correct.... if you cant even read the OP and install, this is NOT the rom for you.....
[Captivate Android Development] r.iqbal87:
Are audio/music skipping bugs most likely kernel related? I posted about this recently, reporting skipping issues with my audio files. Since then, I did a full flash to stock along with a master clear and reuploaded all my tracks. Sadly to no avail, because its still happening. I only use the FLAC format, because my ears are unfortunately spoiled by being used to high fidelity audio, through my kick ass etymoitic er-4p's. Since these headphones are extremely accurate I cannot bare to listen to my music in mp3 format. The reason I mention all this is because I'm starting to think the higher bit rate of FLAC is using too many resources and causing the tracks to skip. I hope this is not the case because other than FLAC the only other option is apple lossless, which only works on ipods, and I can't be seen with an apple product, I mean I have a reputation you know? Lol. I didn't experience this with froyo, and I dunno how many people actually use this audio format, so if its something that's not used so often, if there is something wrong it may go unnoticed. I have made sure that the tracks themselves aren't the issue, by listening to them on my computer. It is only on my phone where the skipping occurs. Help?
[Captivate Android Development] skeepon:
After the last nightly, my camera no longer works
[Captivate Android Development] rain175:
With over 4000 posts I couldn't find an answer for my question.... so....

I installed the latest update from 4/11 and now my market app is missing. I tried flashing/installing the gapps again to get it back but its still missing. I even cleared the market cache like the cm7 wiki page suggested... anyone have any ideas on how to get it back?

I'm sorry if I'm posting this in the wrong area... there are so many possible places to put this :)
[Captivate Android Development] Kaik541:
backup apps with TiBu, factory reset/data wipe and cache wipe, install gapps, reinstall backups
[Captivate Android Development] r.iqbal87:
Do you have root explorer? If so I suggest you check the permissions on the vending apk in the system/apps folder, or alternatively you could select to fix permissions via recovery.
[Captivate Android Development] johnyhoffman:
Anyway to fix browser force closes? Can't open it at all without a force close. Have to use apps to do anything web related, like this post.
[Captivate Android Development] jack_slapped:
I'm having this issue too, I'm using v0 mp3. My problem is there will be split second pauses occasionally in songs. They will still play all the way through, but I understand your plight of wanting to enjoy high quality sound. with that said I doubt it's the bit rate of flac that is causing the problem since I'm having the same issue with v0 mp3's. Of course I can't really say what the problem could be attributed too. *shrugs* Just putting this out there CM7 is A-mazing.
[Captivate Android Development] Kaik541:
no logcat? didn't happen.
[Captivate Android Development] atinm:
I don't know where the problem is yet - but this is something I'd like to get time to work on as I want good audio as well. I am getting tired of crappy sound . . . right now there are enough issues in the kernel that could be the cause that I cannot narrow down yet. I'll start testing with FLAC soon though but in the meantime, if music is your main beef, you would be better off with a 2.2 ROM because all the source is available from Samsung and so many of the weird issues are fixed there.
[Captivate Android Development] tjsooley:
My audio issue is mp3's would not play on the aosp music player till I installed winamp then they played on winamp and the aosp music player
[Captivate Android Development] bokaboka:
Personally I find the audio quality on the captivate is by far not worth using FLAC with (at least not without a portable amp), whether it be stock, voodoo, or other random market apps/mods... I'd subjectively say it doesn't really render much detail above the 160kbps MP3 ballpark, and the bass range is almost entirely missing.
[Captivate Android Development] know8677:
I tried this ROM a few weeks ago and it was not ready for primetime.

I've been waiting for it to become stable enough and I thought with the release this week that had likely happened. But when I come to this thread, there still seem to be a lot of bugs that people are having.

Still waiting for it to become stable enough to use....
[Captivate Android Development] shaolin95:
Not sure what you consider prime time but I have been running it for a while now at 1.5Ghz no less and is super stable for me so to each its own I guess....
[Captivate Android Development] XGX5309:
It's been quite stable for me. I'm using The Escapists kernel and I haven't had any trouble at all. Smooth as glass, and I've got mine underclocked to 800MHz and I get pretty decent battery life.

It is more than capable as a daily driver ROM.
[Captivate Android Development] tjsooley:
I love cm good work.

Does anyone have problems with video playback?

I play a compatible mp4 and all I get is audio.
[Captivate Android Development] joeybear23:
For anyone that is running into the issue with it boot-looping into recovery, I have been able to reproduce it under certain circumstances, and I think I know what the problem is.

When you load a kernel that will allow you to run efsbackup.zip, make sure that you fully boot up with that kernel first, then shutdown completely and use the 3-button combo to get into recovery, run the efsbackup.zip, then fully boot up again. (steps 6.a and 6.b and 7.a below)

Full steps:

INSTRUCTIONS - FIRST TIME FLASHING CM7 TO YOUR SAMSUNG GALAXY S SERIES PHONE:

01. Make sure your phone is fully charged! Update process will take some time.

02. Make sure there's enough free space at your internal sdcard (200MB)

03. Make sure you've not disabled HSPA by using the dialer code *#301279#

04. Download following files from sourceforge: Captivate | Galaxy S | Galaxy S B | Vibrant

- DEVICE-efsbackup.zip

- cm7-DEVICE-initial-kernel.tar

- cm7-DEVICE-initial-XXXXXXXX.zip

05. Copy following files to your internal sdcard

- DEVICE-efsbackup.zip

- cm7-DEVICE-initial-XXXXXXXX.zip

06. Flash a kernel which comes with clockworkmod-recovery

06.a. Boot the phone up completely with the new kernel

06.b. Shut the phone down completely, no "reboot recovery"

07. Reboot into recovery using 3-button-combo and apply DEVICE-efsbackup.zip.

- Don't use "reboot recovery" command or other shiny things to do this!

07.a. Boot the phone up completely

08. Flash cm7-DEVICE-initial-kernel.tar as pda using odin without auto-reboot and without re-partition

09. Reboot into recovery using 3-button-combo

10. Choose "mounts & storage" and format system, data, cache

11. Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip

12. Do a factory reset / data wipe!

13. Reboot

14. OPTIONAL: Copy Gapps to your internal sdcard and flash it at recovery.