yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Jasonhunterx:
No it depends on kernel if its stock Neo it's orange others that sexy blue
[Vibrant Android Development] gamikzone:
i think it was blue on bali and i have orange now im on neo
[Vibrant Android Development] gamikzone:
the stock kernel is orange it depends what kernel u have

all of them :p
[Vibrant Android Development] MaddBlazed:
So what is decent battery life? Froyo? Lol. On gb I average 8-10 hours. And I bought this phone to use it. GPS, wifi, videos, twitter, emails, synching...oh and phone calls. why are people so hung up on battery life? Get a dumb phone. Battery will go for days. If you want performance use cm.
[Vibrant Android Development] hitman818:
Also do the other modems not work with these new cm7 roms? I dont get any service when I flash the kb5 modem. Also I thought the kernel version will be .13 and not .12.
[Vibrant Android Development] Nabeel10:
You have tto flash the radios that are specifically made for CM 7.1, you can't use regular ones, I would give a link to the forum but I'm on my phone
[Vibrant Android Development] hitman818:
Thanks. Forgot about that.
[Vibrant Android Development] Jasonhunterx:
Trying out 84# I must say battery is excellent makes me feel like I'm on Froyo oc
[Vibrant Android Development] automatek:
I've been on CM7 since #76 and before, and everything worked great, but battery life would drain like crazy because it wouldn't go into deep sleep sometimes. I Odin'd back to stock today and flashed #84 and I have gotten 17 hours out of moderate use today. I also didn't use Titanium Backup like I used to, so that might be something. Regardless, I'm loving the speed and if my great battery life keeps up I don't have anything more to want out of my favorite ROM. :D
[Vibrant Android Development] Locksmith81:
Its perfect. Just need voodoo color lol

from the amazing Jets Bread
[Vibrant Android Development] KWKSLVR:
Weird, because I started fresh from Odin. #79 refused to sleep with the stock kernel but slept fine with Neo. #84 is the same way. My phone has been off the charger for 1.5 hours. I'm at 71%.
[Vibrant Android Development] KWKSLVR:
kswapd0 is currently running like mad taking up 10% of my CPU over the past 2 hours. Normally that process if under half a percent with normal use. Typing this is laggy as hell and screen on burns 1% in under a minute. Every fourth or fifth word causes the system to freeze and hang for several seconds. Something isn't right about the stock kernel. I've been running #84 for 12 hours so it needs more time, but still...

This is more than just an old battery in my phone. I'm starting to think that people on unmodified nightlies claiming eleventy billion hours of battery life are either full of it or have extended batteries! ;)

LAGGY!
[Vibrant Android Development] bosox86:
Cyanogen works for Samsung now

I don't know if this has been posted yet, but here you go:

http://gizmodo.com/5831176/steve-kondike-cyanogen-of-cyanogenmod-fame-joins-samsung-mobile
[Vibrant Android Development] Mannymal:
go into clockwork and wipe cache and dalvik. worked for me a few times.
[Vibrant Android Development] atinm:
My thanks to Jay for sending me his extra vibrant that he cracked and had replaced. The slight crack on the screen doesn't bother me because it runs just fine and it will be my development device anyway. This will make things much easier for not just Vibrant but for everything else as well because it can stay on test builds all the time without worrying about missing calls etc that I have to worry about on my Captivate. Someone else said they could send me an extra FFC, so I can test that too whenever I have it.
[Vibrant Android Development] atinm:
Are the ones that don't work iPhones? We know there is an issue with iPhone MMS to 2.3.4 - but haven't isolated it to whether it is common to all 2.3.4 or just SGS itself. No time to work on it yet beyond seeing that our phones complain about the format of the MMS not following the WAP WSP specification.
[Vibrant Android Development] archie53:
Awesome news, thanks to Jay.

Sent from my CM7 Powered Vibrant
[Vibrant Android Development] numberoneoppa:
Yes. Have only had this issue from an iphone. Good catch!

Will the FFC source make a differnce on the ROM end? (I.e. from sgs4g, i9000).

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] thethirdeye:
no it hasnt just been iphones, but i think i figured it out, thanks guys.

one other question, is there anyway to save contacts to the SIM card instead of just phone and export to SD card
[Vibrant Android Development] CappyQ:
This is fantastic news. Keep up the excellent work! I've been an avid fan of CyanogenMod since my G1. And thanks to Jay!!
[Vibrant Android Development] blahbl4hblah:
Which kernel is everyone using for cm7? The one I downloaded with 1.5ghz made my phone semi brick
[Vibrant Android Development] atinm:
What did you figure out? Give!
[Vibrant Android Development] atinm:
Most people are staying with stock. We'd prefer if ppl stayed with stock because it helps us test. If people are using other kernels, then reports need to go to that thread and it basically dilutes the testing pool. You all do realize that you're testing these for us until we are ready to merge and get to release, right?
[Vibrant Android Development] numberoneoppa:
I do realize and I'm pretty psyched!

Also, stock kernel ftw!
[Vibrant Android Development] thethirdeye:
i tried a different kernel just to see how it worked, and somehow it screwed up my MMS, i flashed the "stock" kernel that you guys use and it fixed everything that was wrong, now if only we could get GPS working i would be a completely happy camper :D
[Vibrant Android Development] numberoneoppa:
I'm on stock and always have been. Still have issues receiving MMS from iPhones.
[Vibrant Android Development] thethirdeye:
well like i said, i wasnt getting them from certain people, and none of them had Iphones, it just wouldnt let me get them, and now it is working just fine
[Vibrant Android Development] apollo15rover:
This is why I don't really report bugs but I do have my anonymous reporting activated in CM settings.

I only use custom kernels for Voodoo Color - the improvement is very significant and hard for me to live without. I don't really care about monkeying around with OC or UV.. fix the color and I'll never move from stock!
[Vibrant Android Development] Mannymal:
I use the stock kernel. It produces faster 3D and doesnt break the camera for me like the others do.
[Vibrant Android Development] barribow:
Have a question: Does CM7 support Arabic language?

If not and we want to add that support what should we do?
[Vibrant Android Development] atinm:
I think this is a CyanogenMod question (and I think it does support it). It isn't specific to SGS phones.
[Vibrant Android Development] Tynen:
Figured out what was wrong. I needed to flash bionix before cm.
[Vibrant Android Development] cojonesx:
I don't have a color problem on the stock kernel
[Vibrant Android Development] Demetris:
Actually my battery is a fake chinese one at $3 and i have a great battery life on CM7.1 with radio JVR, so no dice on your comment.
[Vibrant Android Development] lifehijack:
Downloading build # 85. :)

Edit: Smoothly updated.
[Vibrant Android Development] T.C.P:
What he said :p

Sent from a phone with android 1.6
[Vibrant Android Development] Droidicus:
That's awesome when good things happen to good people. :)
[Vibrant Android Development] pelmenept:
Just was wondering. Since we are already on Nightly 85, are there any plans to move nightly to testing ? or Beta ? any time soon ?
[Vibrant Android Development] KWKSLVR:
4.5 hours of unplugged time, 1hr 40 minutes of screen on time, 14% left. Out of the minutes that the screen has been off, there's been zero sleep time. The lag doesn't concern me. It'll work itself out in a few cycles. The battery life does.

Everyone says they get "great" battery life, but few are posting solid numbers on what they're doing with their phones. It's hard to determine where everyone else is really at. I suppose battery life is in the eye of the beholder. I'm used to going 16-20 hours with a couple of hours of screen on time, and 2 days on Edge with little to no use (which for me is a few sms's, etc, roughly 20 minutes of screen on time).

Don't get me wrong, it's an improvement. When I first flashed CM7 I got 3-4 hours of battery life with the phone in standby. :p It's just hard to pinpoint what exactly it is when System Panel is showing my apps behaving.
[Vibrant Android Development] jzero88:
Its starts to get old seeing seeing everyone complain about this rom. All the problems they have are from everything else except what they did not do right. Start over my friend.....
[Vibrant Android Development] jzero88:
O

My suggestion would be to Odin back to stock, reflash the #84, do not use any other kernel except stock, and DO NOT install any apps except gapps. Then see how everything is. Also let it sit without touching it at all after the nightly flash for five or ten minutes. Then reboot twice.
[Vibrant Android Development] Phateless:
Wow, that's wild! I'm expecting much better cm support for Samsung phones from now on.
[Vibrant Android Development] KWKSLVR:
For the record, I'm far from a complainer. Search my posts. In fact, I think this is the first time I ever have. I'm normally on the other end of scope wondering why others are having issues. I'm far from complaining about the ROM, I love the ROM, I'm just trying to methodically figure out what the heck my set up is doing or what I may be doing wrong.

Also, for the record, I've done that...3 times now (which is actually a huge source of frustration). Every ROM I flash I let sit for 15-20 minutes, then reboot, wait another 5 minutes, reboot again, see how it is, then restore apps. For arguments sake (in other words, lack-of argument) I'll give it another whirl in a day or two the next time I have some down time because I'll be the first to admit that maybe there's something I've done unintentionally out of force of habit that has done some screwy stuff.

I just take EVERYTHING I read on XDA with a grain of salt. There is a ton of awesome information and work here, but there's also a lot of BS. There's a reason why I post screen shots...I don't want people to think I'm one of the BSers! :D
[Vibrant Android Development] agosine:
I have read everything I can find and am still not sure why my battery drains so quick. I lose approximately 5% every 25 minutes even if the phone is just sitting idle with the screen off.

I just ODINed back to stock (2.1) and charged the battery to 100% (checked with Battery Calibration) before flashing nightly 85. Same problem.

I have nothing installed beyond what comes with CM7. Am I missing something?

Thanks.
[Vibrant Android Development] lifehijack:
I've got the orange CWM (4.x.x.x) and its running fine.
[Vibrant Android Development] cyberpyr8:
I agree with you that there are some people claiming an insane amount of uptime on stock batteries that are better than anything I have ever seen on my extended life battery.

I ran my wife's stock battery the other day and gave her mine. On CM7 with the stock battery I was able to get about 8 hours with 17% left. On my extended battery I get 15 hours with 25% left but I use my phone more heavily. I will surf the web at night, play Field Runner for an hour and normal email, FB and Twitter. So if I used my extended battery like I do the stock one I could probably get 30+ hours of use from it. Either way the stock battery seems to last me only 8-10 hours max but that is limiting my use of it. BTW, my wife was getting 12 hours from my extended battery but she was using the phone for texting and calling all day long on a 2.2.1 ROM.

I have to think that anyone saying they get more than that are leaving the phone on standby with nothing updating and the screen off. If that is the case then they really aren't getting any benefit from having a smartphone IMO.
[Vibrant Android Development] Demetris:
Here is a solid number for you on a fake chinese battery after unplugged wifi usage on market 4-5 games downloaded go launcher update etc also tap fish which needs wifi to work for half an hour and also played paradise island for 1 hour see screenshot attached ah! and also a few calls made.

Something is very wrong with your battery or something else dont know
[Vibrant Android Development] droidfan77:
I have been using CM7 on my Vibrant since Nightly #3 and didn't suffer from any of the odd draining issues until I installed nightly #76. Ever since I installed #76 my phone won't enter deep sleep and usually stays at around 800mhz. I odined back to stock last night and installed #84. It all worked beautifully and my phone would enter deep sleep again, at least it did until I turned on my wifi. After turning on wifi my phone went back to no longer entering deep sleep and hanging out at 800mhz. Even after turning off wifi and rebooting after wiping cache and dalvik didn't solve my problem. I tried reflashing #84 and the problem persisted, so I made sure my wifi was off and flashed back to #83. Everything was working fine again, so I flashed #84 and my phone goes in to deep sleep again. I noticed that when I turned wifi on, all of a sudden my kswap and suspend processes started using a lot more of my cpu. Here is a screen grab I took of the suspend process about an hour after I turned the wifi back on. You can see that it was barely using my cpu all day and then when I turned my wifi on at around 5:30pm it spikes.

Other than not using my wifi I don't know how to fix this. I hope at least the info I'm providing will help the devs solve this issue since it looks like I'm no longer the only one suffering from it. Keep in mind this is not a complaint, but intended to be a report of what I have found to be happening with my phone lately.
[Vibrant Android Development] defconoi:
At 22 hours with 30% battery left on nightly 84 after turning off to charge and wiping battery stats before first boot
[Vibrant Android Development] defconoi:
This new kernel is the best and OC/UV needs to stay :)
[Vibrant Android Development] jzero88:
No worries mate. I know how things don't work sometimes and how it can get very frustrating. I initially was having problems with CM7, about the same problems as you are, around builds 20ish. I went back to stock for some time and tried again with the 60s. The battery life increased dramatically, but still wasn't the greatest. Now it is so much better. I noticed after about 3 to 4 days is when the battery finally got stable and gave me better battery life. It seems after every nightly I don't get the best battery life till after about that many days. Now with UV/OC support in the stock kernel, it seems even better. I don't use OC, but UV it about -50 on all freqs up to 1000.

OH, also try flashing KB1 modem specifically made for CM. The stock modem kills my phone, but KB1 is what works for me.
[Vibrant Android Development] gamikzone:
i remember i had drains back then and for a while but i just made sure my phone was charged lol
[Vibrant Android Development] atinm:
Don't. Not much is going to change - he can't release source to us that isn't released already, he's a Samsung employee now. The longer-term could be better if he gets to clean up the framework so that it is easier to port.
[Vibrant Android Development] eservant:
I found that "on my phone" build 85 would not deep sleep, as it was with a few other previous builds (and I truly mean just a few). I edited the build.prop and added this line ro.ril.disable.power.collapse=1. The instructions are in the link. When the screen is off the phone deep sleeps. Maybe that can help save some battery.
[Vibrant Android Development] charkey:
Is it just me it is anyone having camera problems with the latest 85 build?
[Vibrant Android Development] Locksmith81:
Works perfectly

from the amazing Jets Bread
[Vibrant Android Development] gamikzone:
there is probably an app keeping your phone from sleeping
[Vibrant Android Development] ironlood:
Would it be possible for devs to create drivers for the phone with out source... like reverse engineer what we do have?

Sent from the depths of Norwegian black metal
[Vibrant Android Development] notverycreative:
Most of the drivers we have are from the Galaxy S, modified to work with our phone. They were mostly black-boxed binaries, so their usage had to be figured out because Samsung didn't stick to the Android guidelines like HTC did. As far as I know, the only drivers that had to be worked on heavily to get them to work properly were the video drivers (I believe they were originally the Nexus S ones, but have since been replaced with Galaxy S ones) and the GPS (which still doesn't really work all that well).

Someone please correct me if I'm wrong!
[Vibrant Android Development] here.david:
News for me on #85...Has anyone else seen that their battery now charges when you power-off, whereas previously it would just reboot back into running. Kind of cool
[Vibrant Android Development] FReQ Z:
The GPS drivers are Samsung-signed and not able to be modded or incorporated. Probably due to a non-disclosure agreement between Samsung and the GPS chip manufacturer. This sucks for us, because Cyanogen and the other ROM developers can't access/use/include the Samsung-based drivers for our phone.
[Vibrant Android Development] Phateless:
Not legally.
[Vibrant Android Development] Se7eN43:
this is true
[Vibrant Android Development] krackers:
I am running #79 build and I would like to know why the video chat in gtalk is not working. -Thnx

(and also... the battery seems to be charging awfully fast, but I am geting 24+ hours of battery life... is that normal?)
[Vibrant Android Development] Droidicus:
I just have to laugh at the whole "we're not getting source because of NDAs between samsung and the gps chip manufacturer." Although it's likely true I have to wonder wth they are not supposed to disclose? How pathetically crappy the gps chips are? I mean, if the chips were super awesome or something, sure... Ah. Good times. Good times. :)
[Vibrant Android Development] stevedrz:
Agreed! Who would want to use the "secrets of GPS" they uncover when they get to play with this junky chip's closed source driver?
[Vibrant Android Development] Jasonhunterx:
GPS is not that bad an I think that its mostly software an for some people hardware
[Vibrant Android Development] iynfynity:
How's the latest release?
[Vibrant Android Development] gamikzone:
pretty good i heard u can charge ur phone while its off now :D another accomplishment in the world of cm7
[Vibrant Android Development] gamikzone:
i just looked through my cm7 nightly database and noticed that in 2 days it will be cm7 nightlies 4 month anniversary for vibrant :D
[Vibrant Android Development] notverycreative:
I would pop the champagne, but unfortunately, I am but 17.
[Vibrant Android Development] gamikzone:
lol me too but correction 3-month :D
[Vibrant Android Development] Jasonhunterx:
Been a great 3 months been on it 4 that long went back to 2.2 once a while looks like its apple cider for u guys
[Vibrant Android Development] gamikzone:
lol by the time its my birthday nightlies would probably be around build 200 :P
[Vibrant Android Development] Jasonhunterx:
CM8 is gonna be out before we hit 200 then were all gonna abandon cm7 lol :P
[Vibrant Android Development] gamikzone:
true but u never know :P
[Vibrant Android Development] charkey:
Just to follow up that clearing the data for the camera resolved the issue.
[Vibrant Android Development] Jasonhunterx:
I hope I do know so I'm hyped for ics so I hope we get it soon but not half baked like honeycomb
[Vibrant Android Development] ironlood:
Sam Firm Ware

This says that samsung is rolling out 2.3.4 to the galaxy s, and was posted by Samsung on August 17, 2011 at 1:50 AM.

Most of the ones listed on the SamKies twitter are a bunch of I-9000 varients for different areas. No clue if this is for any of the U.S. varients (Not likely but im hoping)
[Vibrant Android Development] gamikzone:
i highly doubt it but who knows maybe samsung realized how important we are :D
[Vibrant Android Development] gamikzone:
True but don't forget honeycomb was made for tablets
[Vibrant Android Development] t1h5ta3:
have you tryed pulling the battery out. use a multi meter and a #194 light bulb to manualy discharge the battery to 3.0v?

i do it every 3-6 months and allways see an immediate improvement in battery life.

remember 100% is just over 4.2v, 0% is kernel dependent 3.2-3.7v

our battery's technically arnt dead till 2.8v
[Vibrant Android Development] Phateless:
Hahaha, burn.... But they deserve it.
[Vibrant Android Development] cwalker29:
I just wondering how people be getting 24 hrs of battery life with cm7? Is that with the phone sitting still? I am a heavy user so I get maybe and do mean maybe 4hrs of life before charging. I like the rom but damn! If and when Samsung do drop the source code I will be on another phone. If it wasn't for these great developers on xda I might have switch os. I might have to go back to 2.2 Just because of battery life and t.v out. What a shame
[Vibrant Android Development] gamikzone:
If u need maximum battery go for froyo I'm a moderate user I got about 16 hours today, which kernel r u using?
[Vibrant Android Development] t1h5ta3:
im by no means a " heavy user" by my definition, but i do manage to make it thru a 10 hour shift with 30-50% left, and thats listening to slacker the entire time, FB, txt etc on lunch and durring breaks etc...
[Vibrant Android Development] lifehijack:
Where can I find the changelog for each new version of CM? I mean I want to know what was new from build #85 to #86. Please help.
[Vibrant Android Development] ericdude:
http://cm-nightlies.appspot.com/?device=vibrantmtd

There you go
[Vibrant Android Development] DAKIDD236:
Hey guys, for the past 5 or 6 cm builds I have flashed I never get the notification that I have received text messages. Notifications are on through the messaging app, I've even turned sync on. The only way I recieve my messages is if I click on the messaging app which is a pain, because somedays I forget to click it and I see messages from early in the morning. Is anyone else having this problem or does one know of a solution? Thanks
[Vibrant Android Development] lifehijack:
Thanks mate. :D
[Vibrant Android Development] stevedrz:
No new changelog notes for #86 yet :(
[Vibrant Android Development] konthewicked:
Does anyone know why any build with the mute/unmute fix breaks wired headset functionality? That is the only thing keeping me off of the new builds
[Vibrant Android Development] nedlog:
The buttons on the wired headsets have never worked and might never work. I assume that's what you're referring too.
[Vibrant Android Development] fraserwAstro:
Wait a minute... hasn't something like this already been announced? Didn't we also get an announcement from Tmo saying that the 2.3.x won't be very vibrant? <confused>
[Vibrant Android Development] Phateless:
Check the cm settings and turn on lock messaging in memory. Are you on tmobile us? Try a full wipe and reflash and don't use titanium to restore anything, you bring issues with you when you do.
[Vibrant Android Development] cyberpyr8:
Lol, no I haven't tried that.
[Vibrant Android Development] konthewicked:
Great try lol but no for some reason people claim they can't hear me when im using a wired headset. I tried muting and unmuting the call but that did not fix it.
[Vibrant Android Development] DAKIDD236:


Thanks for the reply! I'll try this now
[Vibrant Android Development] roffee:
what is low power mode?
[Vibrant Android Development] krntehknik303:
Allows phone to be charged while its off? I think that's what it is.. Lol from what I know.
[Vibrant Android Development] :
You mean "people who bought phones a year ago and are almost definitely locked into a contract for another year?" Yes, I think Samsung knows exactly how important we are.
[Vibrant Android Development] gamikzone:
I'm not locked into this phone but most of the phones better then the vibrant r way too expensive like the t mobile sensation is fot around 600 D:
[Vibrant Android Development] Jasonhunterx:
Any good ram scripts that work on cm7?