yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] dc41:
Same thing here. Google Voice has been acting a strange with the last few nightlies. It will sometimes take forever to send a message, and then no messages will arrive for several hours only to be followed by 10 messages instantaneously all with different timestamps. I wonder if the Voice service itself is having problems.
[Captivate Android Development] nkrick:
It looks like you might be right. Way back in post 66, Atinm said that as long as you start from a kernel with properly working CWM 2.x or 3.x, there is no need for an initial kernel flash.
[Captivate Android Development] TheEscapist:
Only the speedmod flash though. You do need to flash the initial-kernel tar, though.
[Captivate Android Development] nathanjones:
Hey atinm, a few pages back (I can't for the life of me find the post...sigh), you had asked us to turn on error reporting, I'm more than happy to do that... I would do just about anything to help you guys out given how much I couldn't live without CM... but I'm also (for shame!) using the Voodoo Kernel linked in the first page... just because I do use the phone for music a lot, so I sorta need that. Given that I'm using a custom, non-supported kernel, do you still want error reporting turned on? Or does it become useless at that point?

Also, if I can ask a kind-of-non-CM7 related question, I have a bunch of custom notifications and ringtones. I normally copy these to /system/audio/media so that they're accessible even when I'm in mass-storage mode listening to music. When I do an upgrade, obviously it blows these away. Is there somewhere I can put them, not on the internal/external SD card that would _not_ get blown away (outside of a factory reset of course). Otherwise, not a huge deal since I have a script to copy them back after a flash... but I thought I'd ask.

Thanks again for all your (and the others on the development team) hard work.
[Captivate Android Development] RockRatt:
Not sure if this is what you are asking but I made a folder in /emmc/media/audio/notifications and /emmc/media/audio/ringtones and now even if when I flash anything I do not lose all my ringtones and notification sounds and they are accessible when setting up personalized ringtones and notification sounds.

Sent from My KickAss Captivated CM7 OC'd 1.4Ghz/Undervolted
[Captivate Android Development] ACDYZG:
Can someone help me out here? i just installed cm7 and flashed the latest nightly and whenever i enable auto-rotation it goes into landscape and does not return to portrait unless i disable it, its really pissing me off.
[Captivate Android Development] Kaik541:
did you perhaps install the galaxy s version?
[Captivate Android Development] EnemyOfGlaDOS:
I originally posted this in the Q's & A's yesterday but have not had any replies, and it seems the questions in this thread get answered more frequently so I'll try again;)

I'm trying to install the nexus s drivers so i can use adb. I've followed the directions for installing them: : Download and install the Android SDK here then download "Google USB Driver package, revision 4"

Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you isntalled the SDK.

I get to "update driver software" and when i search for drivers i get "windows could not find drivers for your device"

when i try to update again and choose "browse my computer for driver software", the best place I know to look is in where I have SDK tools.. so i choose android sdk windows folder and then i have platform tools and all those.. but now im way past the point that the directions end at. I've tried just selecting the c drive and i still get "cannot find drivers".

**the one thing I can get is if I choose "browse from my comp", then choose "let me pick from a list of drivers on my computer" ... if I go in there and choose "ADB interface" it actually scans and I get 2 devices both the same; SAMSUNG Android Composite ADB interface. If i choose one i get warnings saying if my driver is not compatable my hardware will not work correctly and my computer might become unstable or stop working completely:eek: .. so im guessing that's not the one to click on. Its the only one that actually renders options for drivers

Any help would be greatly appreciated.. :)
[Captivate Android Development] ACDYZG:
all of the files i got were from the captivate directory, could my version of odin have something to do with it?
[Captivate Android Development] RockRatt:
Even in the Captivate directory IF you grab the one listed at the very top that says something like get newest update link it can be wrong many times more than not. Make sure you got it from down below where the other links are provided. Just make sure the name on it is captivate update

Sent from My KickAss Captivated CM7 OC'd 1.4Ghz/Undervolted
[Captivate Android Development] glos7777:
same here. I have a battery problem for nighlty 05/04.. I was flashed it then charged full about 05:00 am then go to sleep and wake up about 15:00 pm battery status was %15 without any usage :S
[Captivate Android Development] ACDYZG:
all files say captivate, i flashed back to stock and the sensor orientation is still broken, so i dont think it has anything to do with cm7, sorry for the useless posts lol
[Captivate Android Development] techmik67:
you were so close...... right next to platform-tools in the sdk folder is "google usb driver".....

=))
[Captivate Android Development] Evilspawn:
Any idea what's up with the battery problem? I thought it was fixed in the revised nightly..I'm going to have to go to another rom in the meantime.
[Captivate Android Development] EnemyOfGlaDOS:
Thanks mike for the reply.. arrgh:(.. i don't have google usb drivers in my android-sdk-windows folder. I got all of the above; add ons, extras, platforms, platform-tools, temp, and tools.. no google usb driver. I feel like I'm close, but yet so far away:eek:
[Captivate Android Development] Houka420:
Check the extras folder. Thats where I found mine.
[Captivate Android Development] tiuk:
Google usb drivers are a selectable option in the android repo listing. Sorry, I don't have it in front of me so I can't give you more detail than that, but I know if you run the main android sdk setup tool it's in there somewhere. Failing that, you could always try googling "nexus s usb drivers" or something.
[Captivate Android Development] EnemyOfGlaDOS:
I did, in that folder is a google folder but all it has is market_billing and market_licensing. ..thanks though:)
[Captivate Android Development] EnemyOfGlaDOS:
right.. thats where I downloaded it from. I followed the directions in the OP for qs and a's. But after that the directions say: Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you isntalled the SDK.

I am unable to update driver software because i cannot find the drivers on my computer.. I think thats where Im at:rolleyes:

*EDIT* maybe I should add that I've been x'ing out all of the other options in the list of DL's when i select google usb drivers 4 or whatever. There is 1 file at the top of the list that i need to have checked as well in order to confirm install. But everything else is x'd out. Does this matter or do i leave EVERYTHING checked and just add the google usb driver?
[Captivate Android Development] jhernand1102:
Unzip this and put it in your extra folder in your android sdk directory. I copied these from my computer, maybe you can get it to work with this. I am running Win7 32 bit. I don't know if that matters...

https://rapidshare.com/files/460835622/google.rar
[Captivate Android Development] matt310:
Just go back to the 4/28 nightly...that's where I'm camped out till these new issues get ironed out; namely:

-Losing text messaging center number

-Losing ability to MMS

-Losing Wifi connectivity

-Boots taking substantially longer than they should

-Battery performance inconsistencies

-Google Apps not working properly or going completely missing

Even with the bugs (hey, it's pre-beta after all), it still wipes the floor with *any* other ROM for the captivate. So here I sit, happy as a clam.

...And apparently a little drunk from those cadillac margaritas at happy hour.
[Captivate Android Development] EnemyOfGlaDOS:
I'll give it a shot, thanks :)

*EDIT* ..ok this is really confusing me. I see an extras folder when I try to go through with the driver install. But when I pull it up on my desktop and try to put this in my android sdk directory- there isn't an extras folder :confused:
[Captivate Android Development] Evilspawn:
haha nice i will do the same....:)
[Captivate Android Development] jhernand1102:
When it ask for the drivers just try just to point to it where ever it is I don't think it has to be in the android sdk folders.
[Captivate Android Development] EnemyOfGlaDOS:
:) i was just trying that.. it works, but in that google folder and in usb driver there is i386 and amd64.. umm:confused:
[Captivate Android Development] jhernand1102:
Just drill down to the usb driver folder and click next. It will pick the correct one for you pc...
[Captivate Android Development] EnemyOfGlaDOS:
muchos gracias senior:D ..it installed without any scary warning pop-ups.. thank you again sir!:D:D
[Captivate Android Development] lpfansether:
I just wanted to add (I know you're probably already going to 4/28) that I don't have any battery problems with 5/4. Also my battery life is the best it has been ever on cm7 for captivate. I have been wiping cache dalvikcache and data with each update except 5/4. I don't know if that makes a difference or not.
[Captivate Android Development] tifxalex:
seriously me too...8 hours at 68 percent

...

Straight up!
[Captivate Android Development] LOSTLOGIC89:
Lucky u lol
[Captivate Android Development] torontomark:
05042011 update

Hi all,

First post - two things I have noticed that has not been posted here - never been a problem until now.

Display brightness - after update, the next morning, got into the daylight and the screen would not get off dim state - it usually would operate "normally" but not now

GPS - up till the latest revision, has always operated correctly, now, for instance, the program called "car home" has no speed display (always shows NA) and MAPS - always shows "searching for GPS"

Is there something I am doing wrong? Hopefully, I don't get flogged in public :)

Otherwise, its been the best release to date - in particular, as some others have mentioned, the battery life is the BEST so far.

Many, many thanks to the TEAM for their work. For all of us who understand the difference between iOS and anything else, it is amazing. The last phone that I owned and had this much attention was the T-Mobile DASH - and I loved that phone after they made it sing!
[Captivate Android Development] Vik_92_Sandhu:
Yeah its working after a reflash, must of screwed up the first time. I'm having a problem rendering flash videos from the browser, the videos will stream sometimes and then black out. Is this a known issue as it did not occur with my last rom cog. Im currently running one of the late april builds.

Edit: now my youtube app is not working either but was working yesterday.
[Captivate Android Development] RKight:
I flashed the latest update but flashed back because of the horrible boot time, but then I started having the media process crash constantly, which prevented me from using my gallery. I ended up having to wipe my phone and reflash. :-\
[Captivate Android Development] Vik_92_Sandhu:
Yeah just flashed latest update aswell and youtube video does not stream, audio works however.
[Captivate Android Development] pmpntl:
battery still won't charge past 94%... is this still an issue others are seeing. i'm on the 5/04 build.

what do i do to get it past 94%? i've cleared batt stats... and cleared dalvik cache....
[Captivate Android Development] Vik_92_Sandhu:
Html5 videos on web browser are only streaming audio aswell, no video. I dont think this rom likes me very much.
[Captivate Android Development] NiXXeD:
Pretty sure this is answered multiple times, that the readout is displaying actual charge. So your battery Max is 94. Batteries don't last forever.
[Captivate Android Development] sixstringsg:
Mine only took forever the first time. After that it was reasonable.

Sent from my CM7 powered captivate
[Captivate Android Development] Auridran:
From what I've read (and experienced), the reason you don't hit 100% is to protect the battery and prevent overcharging.
[Captivate Android Development] TheEscapist:
This. Samsung kernels just lie and report that as 100% (for the reason that people would complain about tthe battery not charging properly, when it actually is).
[Captivate Android Development] jaysix79:
When I flash back to 4-28 my phone get lots of error is that normal
[Captivate Android Development] atinm:
Boots are going to take longer from now on because our boot is a lot more complicated now.

Google Apps has to be installed by you. There are links all over where you can get them.
[Captivate Android Development] techmik67:
New builds going up with good changes.... rejoice, all!!
[Captivate Android Development] skoNuff:
atinm,

Just to touch on the google apps issue. Is there a reason why the new nightly's, specifically 5/3 and 5/4 remove Google Talk? I installed the 2.3.4 gapps version that was posted on your Twitter to get the new GTalk.apk and each time I flash a new update, it removes Google Talk. Is this something you guys are aware of, because gapps never disappeared on prior updates.
[Captivate Android Development] atinm:
We don't mess with gapps, but it is possible that it is getting installed incorrectly from the zips. Have not looked at it. You can just flash the gapps again and get it back so not worth our time given everything else we could be focusing on.
[Captivate Android Development] comdei:
excited for new build :) was spying on your github
[Captivate Android Development] TheEscapist:
The new camera drivers seem better, in my uneducated (camera-wise) eyes. It starts up instantly now.
[Captivate Android Development] skoNuff:
Indeed, which is what I have been doing.. Just pointing it out to you guys in the off chance someone wants to take a look at why its happening. Anyway, thank you for taking the time to answer my question. :)
[Captivate Android Development] zerojay:
I can confirm that the updates removed a few things like Gtalk. Also ended up having a problem where I was just using my phone as always and suddenly got a ton of FCs just out of the blue, then everything would always FC. It's strange, seems to have problems that only end up popping up after a few days.
[Captivate Android Development] TheTodFather:
I figured put the problem with drain and crap signal. ..horrible data speeds and ping times. Its the radio...at least for me i switched the cwm zipprd jk4 modem and now ping time is 115ms and great speeds up and down. Try jk4 modem. This fixed the problem for me and now battery is sipping once again
[Captivate Android Development] Roof King:
Any updates on the merge? Its amazing how far you guys have come with this project.
[Captivate Android Development] comdei:
SO EXCITED FOR AFTERWORK!

:D

good job once again. all these fixes :D
[Captivate Android Development] atinm:
Uploaded new 20110506 update. Notice that initial install is different and much easier now as well. Changelog in first post.
[Captivate Android Development] TheTodFather:
I definatetly recommend that jk4 modem. At least for me it kills the stock cm7 current radio jesus it been a looong while since my speed test have been awesome. 3mbs down 1.5 up ping was 108ms. Ping is the most important for me because i use the hotspot to tether to the xbox playing COD. Give it a wirl...

Atinm just want to say thanks bro for the hard work bern rockin this since the day posted cm7 up...thanks
[Captivate Android Development] NiXXeD:
Install process looks much better. Very good work. I'm flashing now to test the MMS.
[Captivate Android Development] zuN!:
I know atinm uploaded new gapps for 04/30 but from the provided link should we use gapps-gb-20110503-signed.zip which is the most recent?

BTW H shows once in a while now for me (Canadian issue).
[Captivate Android Development] shaolin95:
Thats news to me...I am still on the original since I have not flashed from scratch in a while...just do the normal market upgrades...hope I am doing right, lol
[Captivate Android Development] atinm:
We will never merge. Ever. Until someone tells us why end users care besides being able to get nightlies from CyanogenMod nightlies as opposed to what we upload. At the moment we're still making too many changes such that automatic nightlies aren't really what anyone wants.
[Captivate Android Development] TheTodFather:
Atimn so then do you build from the most current builds when you build your captivate specific builds? I am assuming you do but just wanted to make sure.
[Captivate Android Development] NiXXeD:
MMS still giving me the same symptom from non-CM7 user (I can send between mine and my wife).

Checked the # in my phone info settings and it looks correct. Went back to an MMS from a day ago, still shows download button. When I click, it gave me the message: "Download of message (no subject) from <person> was unsuccessful." I had him send me a new fresh text just to be sure. I didn't get a text message noise, and it showed up with the download button again, and gives me the same error.

Attached logcat to this post.

Edit: Eww, even worse. I can't send any SMS now either. Odd. I was able to at least get one out to tell my friend to send me an MMS.

Edit again: I just re-tested and my wife's phone (CM7 5/1 build) can still send me MMS and it works fine. My friend that I tested with has an iPhone 4 (not sure if it matters).
[Captivate Android Development] atinm:
Just so everyone is clear, if it says "initial" in the file name, don't touch it if you are already running CM7. Just flash the nightly. Initial is for Initial flash to CM7 from anything Samsung.
[Captivate Android Development] nkrick:
I looked at the new initial instructions. Since the initial no longer includes using odin to flash a kernel with CWM recovery in it, you may want to mention that CWM recovery is required. Obviously it says to use CWM in the install steps, but if you don't at least point to someone else's instructions on how to install CWM, people will be asking questions.
[Captivate Android Development] atinm:
Yes. Given that I am one of the main developers on all devices, if I don't have it, it's not there. And yes, we sync to upstream as well.
[Captivate Android Development] TheTodFather:
Oh and is no one else having problems with the current radio? My friend and i both have had problems we usually 95 percent of the time on 850 band but I swear my base band had been jk4 till recently but i may of just imagined it. Again just to say now my battery is sipping again after replacing the stock radio and voice and data a great
[Captivate Android Development] atinm:
You can do it from 2e recovery - just need to rename the kernel-cm-7-INITIAL-Device-signed.zip to update.zip and then "update packages" or whatever that recovery does. Then flash the update initial zip after the reboot from cwm as now you will have cwm.
[Captivate Android Development] comdei:
Mainly rom manager support
[Captivate Android Development] atinm:
Merge is not needed for that. Koush will have it working in a couple of days. We have finally done all the pieces as of this update.
[Captivate Android Development] comdei:
You guys are the best

:) just saying
[Captivate Android Development] nkrick:
Thanks. I see that you updated the instructions to mention "Stock 2e." Perhaps you can also mention that if you use Stock 2e you need to rename "kernel-cm-INITIAL-DEVICE-signed.zip" to "update.zip." Just trying to save the same questions being asked over and over in the future.
[Captivate Android Development] nkrick:
LOL, been awhile since that...I like how it is still a tag on the thread ;)
[Captivate Android Development] ls377:
You mean...like he did? ;)

" just need to rename the kernel-cm-7-INITIAL-Device-signed.zip to update.zip "
[Captivate Android Development] nkrick:
Maybe I am still seeing a cached page... perhaps you can point out where it is in the instructions: http://forum.cyanogenmod.com/topic/...7-for-samsung-galaxy-s-phones-build-20110303/
[Captivate Android Development] ls377:
Ah, I thought you were talking about his post that you quoted. My bad :p
[Captivate Android Development] nkrick:
NP. Atinm asked for people to check out the new instructions. So I did and was giving some feedback on an area where some people may get confused.
[Captivate Android Development] nkrick:
I have a picky 1007 revision, so when I got JL3 (the included modem) working I just left it. After seeing so many people saying that JK4 is better for battery life, I finally switched. While it is far to early to say anything about battery life, I did want to give information for other revision 1007 owners.

When I first flashed the JK4 modem, after reboot the cell took a long time to connect. Once it did connect, it kept dropping its connection constantly. I went back into CWM again and re-flashed JK4. After reboot, it did take a little longer to get connected than with JL3, but since picking up the connection, I have not had the connection drop yet.

I have seen people report similar things in the past about constantly dropped connections. I have also read about 1007 revision captivates needing to be flashed twice to use i9000 modems, and that is how I got JL3 to work originally. So, for anyone experiencing a lot of dropped connections, try flashing the same modem a second time, especially if you have a 1007 revision.
[Captivate Android Development] nkrick:
Did something happen to the Ambient light sensor in the 0506 build? I am back to 6, 5000, 9000, 15000 again like the previous builds. Brightness is at 100% almost all the time again....

edit: the CM settings do show the "correct" range up to 15000, so I modified the settings so that at 5000-9000 lux the screen is not so bright. But in the previous build the sensors reported many more (and lower) values.
[Captivate Android Development] Auridran:
Yeah, I noticed this too. I really liked having more values there.
[Captivate Android Development] techniq35:
Stuck at AT&T boot screen

I've been having update issues for the past few releases (and intermittently before). I tried to update from 05042011 to 05062011 and on reboot, my phone hung at the AT&T boot screen (gave it close to an hour, phone was hot, but never got to the Galaxy S/Gynogen boot or the CM7 boot screen). I also couldn't boot into recovery in this state (but was able to get into download mode).

I had to grab a Odin flashable kernel (http://touristinparadise.blogspot.com/2010/12/at-captivate-download-speedmod-kernel.html), and just flashed the kernel-cm-7-INITIAL-Captivate-signed.zip. Currently sitting at the Galaxy S / Cyanogen screen, waiting for the CM7 (has been about 5 minutes so far). Going to give it 10-15, then try to boot into recovery (which I figure I can since I'm getting past the AT&T boot screen). I plan to clear the 2 caches (dalvik and cache partition) and attempt a boot again.

This is probably the 5th time I've had an issue trying to apply an update-cm-7-DDMMYYYY-NIGHTLY-Captivate-signed.zip update, and alot of times have to start back over with the initial.

Am I missing something when doing an update (should I always clear the 2 caches, is there something else I'm missing)?

Thanks.
[Captivate Android Development] beryxil:
Hi, is anyone having issues with the camera? I just flashed following the new instructions and the camera opens but the screen is black. It can still take pictures though. I reflashed the nightly and no effect.

Any ideas?

Thanks.
[Captivate Android Development] phaedrusiszen:
I've never had a problem just applying the update, and I never clear the two caches. I would only do that (or a factory reset) if I had problems.
[Captivate Android Development] cgugino:
Goddamnit, you guys are magical. Thank you for being magical.