yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kaik541:
xda loads fine for me, both over 3G and wifi.

same with market

as for voodoo sound complaints, you're free to make a kernel with voodoo sound implemented. the team isn't integrating voodoo sound as it cannot be merged upstream. simply merge voodoo sound related patches and release sources (as required by GPL)
[Captivate Android Development] cupps:
D'oh!

I've spent the last couple nights trying to compile CM7 per the instructions on their website. Had some issues with github, and finally the repo sync'd tonight. Everything else went smoothly, and I got it running about an hour ago.

Then I see here I just missed a (presumably) much easier release. Oi.

I'm still catching up on the thread, but is there any real benefit to re-flash using the zip in this thread, or am I okay to stick with what I compiled earlier tonight?

PS - Still early in using it, but hat's off. It appears to be everything I was expecting an more (first-time CM user here). Thanks for all the hard work, guys.
[Captivate Android Development] bay_wolf:
Benchmarks:

Linpack = 14~

Neocore = 55.1 fps

Smartbench 2010 =

Productivity Index - 960

Games Index - 1510

Quadrant = 1609

Ran all of them three times and posted the averages.
[Captivate Android Development] whitesox311:
I'm build 1007, btw

neocore: 55.5 (on 2.2 w/ speedmod i was getting 54-55)

smartbench: 774/1138

and i simply refuse to run linpack on a hummingbird, sorry.
[Captivate Android Development] TheEscapist:
I'm having no problems with xda, nor market.

As for sound complaints, there's problems with the sound driver, and voodoo can't be merged officially, cause it wouldn't work on other devices.

Galaxy tuner provably checks model numbers, in which case, its a simple fix (and may have already been implemented, I'm not sure).
[Captivate Android Development] demonte21:
Anyone else having the screen "keep on" when on a phone call?

Is there a way to change this in the settings?

Or is this a sensor proximity issue ?
[Captivate Android Development] MisterAnthonyxD:
By wipe, do you mean like a ODIN master clear? Or a factory wipe?
[Captivate Android Development] coderunner:
I think this is going to be my daily driver now. The only problem I am having poor battery life. But I charge my phone every night anyways. It would be hard to go back to froyo though. Even though there are some little bugs. There are more things that are working better than ever. Like downloading from market even with the market fix on froyo I could just hit update and all my apps update with out me have to restart a few. But it works now. GPS works great. and more I forgot to mention but overall I love it.
[Captivate Android Development] coderunner:
Factory Reset in Clockworkmod recovery
[Captivate Android Development] Roof King:
My wife and I are having a good laugh after refreshing our memories with some you tube clips of Man from Atlantis. We're giving our age away here.
[Captivate Android Development] shaolin95:
Would you believe I learned about those those watching a History Channel special? :D

Sorry for going Off topic to the other readers :o
[Captivate Android Development] loraque:
You can buy an external BT GPS receiver for $40. That is the only fix for Galaxy S GPS issues that reliably works. Otherwise, it seems totally random which combo of whatever makes it work better. The first time I flashed CM7, I had great GPS without my BT receiver. Then I had to flash Cog back for a vacation where I needed the camera and wifi reliability... and when I returned and flashed CM back, GPS is the typical crap I usually get.

For me, the $40 to not have the headache was worth it. The interesting side effect is that now the GPS is accurate enough for me to see which lane of traffic I am in without having to look out of the windshield :). Not recommended.
[Captivate Android Development] shawn.ferris:
My results are hit our miss to.. Sometimes works without an error at all.. Other timess it's useless. Usually it's good enough though.

I wondered the same.. And that's when I truly understood the difference between this rom and the other cappy roms. I pulled those fixes apart, browsed through this rom and there is nothing usable in those fixes. If you flash those fixes, you'll be making a mess out of this beautiful rom. Don't do it 8D

The only thing I haven't done much of is try to understand the configuration of the gps stuff on this rom, to see if some of those same techniques can be applied. (configuration wise.. the daemons almost certainly won't.. And I wouldn't use them if they did) I'm personally holding out for the compass fixes as I would think that would at least help the situation.

Hope I didn't say anything blatantly wrong.. Someone will surely correct me.. But take this with a grain of salt regardless
[Captivate Android Development] Johnston212:
It could also be your area. I know that some areas of Georgia don't have good GPS signal reach either. However, I have found that the assistance data that GPS Status (& Tools I think) is very helpful
[Captivate Android Development] Johnston212:
I know that on normal Captivate ROMs you could actually go in and delete the GPS data in LbTest mode. Overall, I haven't had that much of a negative experience with the Captivate GPS, but CM7 has been one of the better ROMs for GPS and HSPA+ that I have used yet.
[Captivate Android Development] EnemyOfGlaDOS:
Sorry I wasn't trying to come off sarcastic. I was on the go and knew that this had been discussed many times and should be an easy find. Aldo didn't realize the search functionality was down.
[Captivate Android Development] matt310:
I guess I jumped the gun too - I could have waited till the morning to post my question. XDA is a great resource, and I have donated to it and to the developers, but the back-end needs some juice. The search functionality on a site like this is paramount and the fact that it's been down a lot lately is a likely contributor to asked-and-answered questions appearing multiple times.

That said - the reason I asked about the dialer codes is because I'm in West LA between an 850 and 1900 tower that constantly hand-off registration which contributes to battery drain. In previous ROMs using the now-described-as Samsung dialer codes, I could force the phone to stay on one band and not the other. I have yet to come across a setting in the awesomely comprehensive list of CM7 menus where this is an option - and as such it will continue to drain my battery more than other roms. This is not a deal breaker to me, but if losing the functionality to force the modem to stay on a certain band is of greater importance to others, it's worth mentioning, right?
[Captivate Android Development] Uncle Irish:
dude... really?

It's people like you that will piss the team off and they will stop their work on the Captivate.
[Captivate Android Development] stuff:
I'm doing nothing but supporting them in all ways possible. I note down an occurrence, and I get bashed for it. I didn't post something that was already posted. I was somewhat vague, but how easy is it to say "you are too vague."

Instead he is sarcastic and insults me.

My apologies to the long rant post. I just get annoyed when I witness people being completely rude to new captivate owners. I understand that it gets annoying seeing the same questions over and over, but I am sure a lot of people are overwhelmed with the large amount of information available, that they overlook what they are seeking for.

In the OP, in this thread the link to http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/list should be bolded, or perhaps a few sizes bigger in font. So it's more easily seen.

That way when users view this page, they see such link and go to it.
[Captivate Android Development] spiritssight:
Kernel

Hello Folks,

PLEASE excuse me if I have missed something, I had read the direction and again same. I have watch the how-to and read the Q&A, I have download three files from sourcefrog that directions told me.

Now my LAST issue and concern because I don't want to DL wrong kernel could someone PLEASE send a direct link to a so called supported kernel. I thank you very much for your assistance.

I am SORRY if I am asking a stupid or already answered question.

One last question, is there a kernel that I can do through CWM as I am using linux (Ubuntu) system and I really don't know how to use heidall.

God Bless,

Christopher
[Captivate Android Development] techmik67:
both the initial rom and any updates have kernels built in. you only need to download a "different" kernel if you want the features offered by those kernels, such as voodoo sound, oc/uv, etc...... otherwise, after you flash the update or nightly, you are done =)
[Captivate Android Development] spiritssight:
Thank You for your quick and helpful post. I ask this question because in the direction it says something about downlording a kernel so that what was confusing me.

God Bless,

Christopher
[Captivate Android Development] stuff:
There are a few kernels that are developed by other people not apart of the CM7 team.

Here are two different ones, with OC(overclock) and UV(undervolt) capabilities. If you don't know what that is... well you have some reading ahead of you lol.

ytt3r's kernel

http://xdaforums.com/showthread.php?t=1009962

The Escapist's kernel

http://xdaforums.com/showthread.php?t=982337
[Captivate Android Development] spiritssight:
Hello Folks,

Thanks you for assistance, I have now done the whole process twice, I don't believe I missed any thing in what I did. My phone has the initial-kernel and boots into the CMW fine, I then formated as directed the data, cache, and system, then I applyed the cm7 zip file then did a factory reset / wipe after that I told it reboot system and it gave blank screen with button lights on. so I hit power less then sec and it shows the att screen then the cm boot screen then it goes into the cmw again. what went wrong?

I thank you very much for your assistance in this matter

God Bless,

Christopher
[Captivate Android Development] techmik67:
are you sure you are using the captivate files? ignore the file that shows up on top as "latest"..... go into captivate and use the files there.
[Captivate Android Development] RockRatt:
I have had that on occasion and just held down the up/down volume buttons and power button until the att screen came up then I let go. When the cwm screen comes up I hit reboot system and it has rebooted fine. Another thing to try is going into the CM7 cwm screen and clear cache. This has also seemed to help. Third option is flash the most current nightly again then reboot.

Sent from My KickAss Captivated CM7 OC'd 1.3Ghz
[Captivate Android Development] Kaik541:
my point is there is honestly no reason to post ANYTHING to this thread about a bug you find unless you have info to back it up. this ROM is pre-beta, there are bound to be bugs and crashes... so just dropping by to say "this thing dun broked" is completely worthless to the team, and it was the quickest way to convey that point.

your logic of "I should share it in case it happens to someone else" is a little silly, as you've provided them no more information than what they already know (mms crashed, lost messages)... you have provided no hints of what might have caused it, how to prevent it, or how to repair it; there is literally zero contribution made by posting that "something has broken." if you'd like to leave a note for yourself to remind yourself to logcat it next time (which you don't need a computer for either, might I add)... then carry around a pad of sticky notes.
[Captivate Android Development] zelendel:
Do I really need to post the rules in big bright letters in every other post?:rolleyes:

There is no swearing in the forums. One and only warning.

As for the issues, it is a simple rule. Either post a logcat or it didnt happen. If you dont know how to run a logcat from your phone then you most likely should not be flashing this rom to begin with as it is not a NOOB friendly rom. (no offence to the team.) Now I let the team handle this thread but i will not allow swearing or posting of BS that is of no help.

As stated "Posting this doesnt work" is almost of no use with out helping to find out why this doesnt work. Please Help the team to help you. Learn a few basic Trouble shooting tools so you can help them find the bug and fix it. (if it can be fixed)
[Captivate Android Development] stuff:
Well the error occurred again but I am doing too much to literally stop what I am doing and grab a logcat.

Plus I'm not familiar with the process.

How do I do it within the terminal emulator without just creating a large wall of text that continuously updates with each message added to the log?

I read the original post, and I cannot figure it out. It just displays a constant updating logcat.
[Captivate Android Development] Kaik541:
"logcat > /sdcard/log.out"

adb pull /sdcard/log.out
[Captivate Android Development] techmik67:
su

logcat > /sdcard/log.txt

(count to, let's say 5)

back your way out of terminal emulator and log.txt will be on your sdcard
[Captivate Android Development] kant5t1km3:
In the market I go to my downloads and it says "the market is not compatible with your phone."

I tried wiping data, cache, installing updates. Help plz
[Captivate Android Development] techmik67:
I'm pretty sure you forgot to back up your efs. Check your imei (settings>about phone>status). I f I am correct, flash back to stock and start over, making sure not to skip the efs-backup step

=)

i forget if its that or the modem thats screwed. if its the modem, you will have unknown as your baseband
[Captivate Android Development] stuff:
Posted the logcat on the developer page.
[Captivate Android Development] kant5t1km3:
No this just happened today. I've been using the market daily since I flashed.i powered my phone on since the shutdown.this morning
[Captivate Android Development] spiritssight:
Flashing CM7 issue

Hello Techmik67 & Folks,

Yes I am using captivate files as all them have the name in the files them selfs.

OK this is what I have done so far; I have updated to the latest and greatest nighly build, I have rebooted and it goes right into CMW, I select reboot system in there and it reboots and goes back into CMW, I have reflashed kernel two or three times I extract zImage and used heidall as I don't have windows system, as much as I can tell the kernel was successful as its allowing me to go into CMW and also mount to PC as storage able to format, etc and read from the internal SD card and exterinal card.

Some how now I have a cicule on screen with a hat and its not doing anything else, I don't know how that even got there as I was in CMW. I am also getting error in CMW of no misc partition and this error three times at bottom of the screen, OK I think the Hat pick is a screen type saver in CMW???

Any help would be greatly. I followed the direction to the T except installing outside kernel.

God Bless,

Christopher
[Captivate Android Development] Kaik541:
did you flash initial first? you *MUST* flash initial zip package and then boot once into the OS before you can apply an update zip.

edit: what do you mean "except installing outside kernel"? that first step for efs_backup is required and will cause major headaches if you don't... on top of that, if you used commands like "adb reboot recovery" or "adb reboot download" during the install process, you'll run into even more headaches.
[Captivate Android Development] spiritssight:
Yes I did the kernel first using Heidall, then went right into CMW. After that I did the initial-xxxx file then I told it to reboot system thats when it went right back into CMW then I toke battery off and back on and hit power botton and it went right into CMW.

OK, I did this order for installing CM7:

I flashed back to stock 2.1

mounted SD card internal to PC and moved efs zip & initial-xxxxx zip to internal SD Card

I used cmw update.zip file to run the efs zip to get the backup

then I flashed kernel initial using heidall

I then went straight into CMW by holding three bottons (NOTE: I did not use any shinny thing to do this)

I then used CMW to format data, system and cache

after that I applyed the initial-xxxxx zip using install from zip in cmw

after taht was finish I told it to do a factory reset / data wipe

after that I did reboot system from the menu in cwm

at this point it to blank screen and the four led buttons was on, I hit the power button no more then a sec and it showed the att screen then the cm boot screen that is in the kernel I believe then it went into cmw again. after this I tryed to boot again by remove battery and put it in again and press power and then it did the att and kernel boot screen and then into smw it went

OK, I don't know what I am doing wrong, please assistance, thanks very much ahead of time.

God Bless,

Christopher
[Captivate Android Development] bay_wolf:
You need to be on a kernel with CWM built in like speedmod or something similar. I'd just flash a custom ROM like Serendipity or another one (if you already have it downloaded) and then start following the CM7 instructions.
[Captivate Android Development] techmik67:
i see the problem.... you skipped an important step.....

you say you flashed initial kernel and efs backup both from 2.1 stock...... you need 1 more step before that.....

you need to flash speedmod kernel after you flash 2.1 stock. The 2.1 stock kernel is not suitable to start from.

so, copy the zips to your sdcard from 2.1, thats fine.... *then* flash speedmod kernel..... you will *not* be able to boot from speedmod........ when done with flash, pull battery and 3 button boot to recovery..... from *there* you efsbackup, then continue...... initial.tar...... format system, data and cache, install initial zip..... boot up..... shut down....... 3 button to recovery..... install gapps...... boot...... shutdown......... 3 button recovery....... install nightly update.....

=)
[Captivate Android Development] ckelvin87:
Hi is CM7 still considered beta? Because I remember seeing a Beta Tag on the title before but now it seems to be gone. So I guess most bugs like the wifi drain have been fixed already?
[Captivate Android Development] Enhanced:
Definitely still beta.
[Captivate Android Development] TheEscapist:
Pre-beta, to be exact.
[Captivate Android Development] ckelvin87:
O i see, Thanks. I guess ill wait for the stable build then. Not very fond of flashing a lot hehe
[Captivate Android Development] c0ldburn3r:
But that's half the fun! Its my daily driver. Works great.
[Captivate Android Development] spiritssight:
Thanks & G-Apps

Hello Folks,

I need to say thank you to the person that pointed out the missing step, to me it was not clear that you should start from a rom with kernel that was at less 2.2 kernel with cmw to start, once I got that every thing seem to go much better so thank you for the information :-)

OK for my next question as I just searched and did not find a link that point to the dl of gapps I look in the first post and I may of missed it so please excuse me if I did. could you please either provide the link to the most up-to-date gapps or point me to the area that I may find them. I thank you all again for the help and wonderful build :-)

God Bless,

Christopher
[Captivate Android Development] HaiKaiDo:
http://xdaforums.com/showthread.php?t=982776

fifth down in the FAQ on the first post. :]
[Captivate Android Development] spiritssight:
Thank you very much, wow thats where I saw it and couldn't find it again :-) thanks for the reminder :-) now my phone is great again :-)

God bless,

Christopher
[Captivate Android Development] ClaPik:
Hi my captivate doesn't seem to recognize my external sd card? Is there a way to fix this problem?
[Captivate Android Development] techmik67:
(sigh)

are you that lazy that you cant read the known issues? or search?

it cannot be mounted usb to your computer...... it is available in the phone browsers as /mnt/emmc
[Captivate Android Development] hernan078:
someone here is changing their lcd density? i cant get a signal if i reduce my density to 200.
[Captivate Android Development] shaolin95:
I use 185 with no issues.
[Captivate Android Development] EnemyOfGlaDOS:
I get a signal.. but it takes longer.. at least it seems that way, and that's with a density of 200.
[Captivate Android Development] skynet11:
Do you have an SD card adapter? In case you don’t know what that is, it's a full-size SD card that you insert your MicroSD card into so your PC's card reader can read it (if you bought that external card yourself it should come with one). Perhaps you can use this method to transfer files between your card and your PC until a fix is provided.

Released from Captivate-y by my XDA app...
[Captivate Android Development] Kaik541:
how on earth do you think these two things are related? =/
[Captivate Android Development] EnemyOfGlaDOS:
Never said they were related, I was just replying to someone who asked about LCD density at 200 not getting a signal. And all I said was I thought it might take a little longer but I'm not sure. I was letting them know that I use LCD density at 200 also. That's all..please don't reply with a sarcastic attitude and put me down. I was trying to help.
[Captivate Android Development] Kaik541:
I have personally used the LCD density changes and there is no difference... if you are taking longer to get a signal (or no signal at all), it is unrelated and another issue entirely is all I'm saying.

a single line change in build.prop not related to RIL will not affect signal.
[Captivate Android Development] EnemyOfGlaDOS:
That's good to know. I've always had signal but really wasn't sure if it was taking longer or if it was just me. Honestly I assumed it was just me until I saw that post..that's when I thought I would share that "maybe" it takes longer. But you certainly cleared that up.. thanks for the info.
[Captivate Android Development] ClaPik:
Oh well I did look for it though but I thought there was a function somewhere I don't know that "activates" the emmc

Next time I'll try my best to look for the answer first :)

Thanks a lot by the way!

Sadly I don't...I'll just copy the file into the internal sd card and use the browser to move it to the external one
[Captivate Android Development] techmik67:
for future reference, even if xda's search function is down, you can use google to search and if you use enough proper keywords it finds the xda forums anyway...... and even if that doesnt work, i understand most people wont read this whole thread, but its almost *required* that you read, say, 5 pages at the beginning, then a few here and there in the middle, then maybe the current 5...... you'd be amazed how much info you'll find in just browsing.... =)
[Captivate Android Development] skynet11:
You can get an SD card adapter by getting, say, a 2GB microSD card for $8 at Best Buy... it comes with an adapter.

Another post released from Captivate-y by my XDA app...
[Captivate Android Development] skatcat31:
So I've been using this for a few days now, and I love it, but the battery life is terrible. I get at most 16 hours. That's with data turned off and screen set to auto. I use wifi sparingly and only when needed. But I do have one issue with the lockscreen and power widget, so off to the bug tracker.
[Captivate Android Development] Disgustipated:
I'm having the same problem as well. It started with the April 2nd nightly.
[Captivate Android Development] ksimilie:
after flashing the latest nightly i have been getting many FC's. Any suggestions?
[Captivate Android Development] phoenix2217:
clear dalvik cache, cache and you may need to do a factory reset/wipe.
[Captivate Android Development] shaolin95:
Same here and I have tried flashing 5 times already. I am going back to the previous nightly I think for now.
[Captivate Android Development] ksimilie:
Actually i forgot to mention i can't boot, animation stuck in loop. Caches are clear. Guess ill factory reset (which sucks)

EDIT:After factory reset, nothing has yet to FC but i can't get signal. Kinda don't know what to do now.

EDIT2: After putting the phone in airplane mode and off airplane mode, signal began working again and so did data.