yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] flipper2006:
This has the best DND mode. If the stupid Phone.Android message didnt keep coming up, i would try this. people woulnt be able to get ahold of me for a day.. what a great excuse:eek:
[Vibrant Android Development] flipper2006:
On a serious note, can we load different modems with this yet or do we need to stick with the default? I had better luck with different modems.
[Vibrant Android Development] cpittman:
MODEMS again
[Vibrant Android Development] flipper2006:
That was a JOKE! you guys are way too freakin serious...:cool:
[Vibrant Android Development] cpittman:
sorry, anymore i'm on auto pilot in this thread. i'm almost like a bot who answers dumb questions and cracks jokes here and there.
[Vibrant Android Development] flipper2006:
This time im not joking, i reloaded build 8 because after loading #11 I got no service and "the process android.phone has stopped" and i figured it was a bad build and i was going to go back to 8 and im getting the same thing i got on #11 where it says "no service" but i keep getting "the process com.android.phone has stopped" and keeps repeating.

Crap.. not sure what to do , i dont have a nandroid backup since Saturday (i know but i did lots of on phone since then). Should i just try another build? Never had this issue before.
[Vibrant Android Development] droidfan77:
I ran in to this problem as well and found that reflashing Build 6 solved the problem for me.
[Vibrant Android Development] apollo15rover:
Ditto.. went to Build 6 as well and that resolved no end of problems I was having.. guess newer's not always better ..just newer...
[Vibrant Android Development] VeryCoolAlan:
So is it the kernel that doesnt work in call audio or the build?
[Vibrant Android Development] apollo15rover:
Good question..

Zach, who makes the Platypus Kernel claimed he had found a fix within the latest generation of his Kernel but I still had the same problems. I don't know if anyone else has tried. To me that would indicate something in the build, but will defer to people that actually know something about this..
[Vibrant Android Development] VeryCoolAlan:
Tried with build #11 and the newest platypus kernel, no luck

Then flashed the script fixes? no luck either.

Have you tried the newest kernel on build #6?
[Vibrant Android Development] flipper2006:
Trying it now, not sure what changed from 10 to 11 that screwed it up. I guess one of the major data structures changed that hosed it. NOPE didnt work.

still no service and FC on phone.android

Unless this is isolated, everyone need to be careful wtih #11

After looking around, it seems it's stuck in airplane mode and it cant be toggled off.. hmmmmm
[Vibrant Android Development] sad2903:
Whenever i flash another kernel ( Platypus and Kang ) it deleted my EFS folder even though i backed it up with EFS backup, plz reply, thankyou !
[Vibrant Android Development] Jackdog89:
Are you asking a question or making a statement?
[Vibrant Android Development] masr1979:
... so are you odin-ing back? I was having issues with FC, and did a full wipe, and I formatted "system" from within CWM recovery before flashing v8 and gapps. Have been running ok so far.
[Vibrant Android Development] CTown:
There already is!

Except for stable builds of Cyanogenmod (and the Gapps), one needs Rom Manager Premium in order to download the Cyanogenmod nightlies and other custom ROMs. Since, no Galaxy S device has a stable CM build, Rom Manager will not display anything under Cyanogenmod in the downloads section.
[Vibrant Android Development] jonathanhuerta4:
I think he wants someone to give their take on that matter. It has already been discussed in the Platypus kernel thread, it is an issue with the RIL fixes that are in build 9 and 10. Zach, has made a kernel specific for those builds, called Revolution NEO, but still suffers from audio call issues.
[Vibrant Android Development] Jasonhunterx:
Wow another bad release but besides the no service battery for me was awesome got 7 hrs with heavy use I played a ton of games so I'm staying on 11 service don't matter phone cut off for now :P can't wait for 12 >.<
[Vibrant Android Development] flipper2006:
How did you use #11, didnt you get FC's every couple of seconds over and over?
[Vibrant Android Development] iceman1251:
No eta
[Vibrant Android Development] cal4877:
until the official one is release lol.
[Vibrant Android Development] cpittman:
seriously guys these aren't releases. they are nightly builds built by a bot. please don't treat them as releases or expect for them to be at the level of a release. you can do that when they become rc or stable. until then enjoy the preview of what's to come and expect issues.
[Vibrant Android Development] atinm:
We still haven't got to the bottom of the audio issues with phone calls, but have narrowed it down to some specific things in the Samsung RIL.

We basically went to the Samsung RIL in an effort to solve many of the problems related to GPS, mute/unmute etc but it is quite a hack and so will take a little time to resolve all the issues. It is essentially all new code rather than bug fixing of working code as we completely replaced the open source RIL code that we were using to go to the closed source Samsung RIL binary that doesn't follow the specification laid out by Google. Very painful work . . .
[Vibrant Android Development] wizern23:
well keep up the good work atinm
[Vibrant Android Development] movieaddict:
ty for ur devotion and hard work, much appreciated.
[Vibrant Android Development] VeryCoolAlan:
Will stay on build 6 then
[Vibrant Android Development] jashlock001:
Should I disable voodoo before I download and flash right now im on stock 2.2 with kb5 stock voodoo kernal? Someone please help want to flash this soon...
[Vibrant Android Development] parmijo11:
I would disable it, you won't need it here.

Sent from my Vibrant with CM7...
[Vibrant Android Development] :
atinm and all devs thank you for the hard work.
[Vibrant Android Development] djluis48:
Glad to know. Thanks for the hard work guys!
[Vibrant Android Development] jashlock001:
Thanks for the help!
[Vibrant Android Development] inrelief:
Nothing like blackboxed binaries without documentation... :P

Thanks for fighting the good fight!
[Vibrant Android Development] Jasonhunterx:
Nope everything work except service even GPS work jk don't flame me >.< but great rom better than froyo so customizeable thanks for all hard work
[Vibrant Android Development] mrxela:
Thank you for all the hard work fellas.
[Vibrant Android Development] enzomtrx:
Can't live without cyanogen. I cringe when using anything else.
[Vibrant Android Development] phantomsniper773:
thanks for all the hard work you guys put into this ROM. I still remember trying it out back when wifi sleeping would cause reboots, and it's come a long way since then. I also wanted to point out that in the OP, coolya's twitter link is wrong. It should be http://twitter.com/#!/dumdidum
[Vibrant Android Development] ChristoA1:
Atinm,

Is there any reason that other device-specific changelogs reference the Samsung RIL change? I tend to stay on the nightlies for the G2/Vision, and noticed that it also mentioned said RIL on the latest build in spite of being an HTC device...

I know this is kinda only-semi-related/off-topic, which is why I'm asking it here: If you happen to see it and reply, great, but I don't want to waste your time otherwise... Just curious :D
[Vibrant Android Development] Kaik541:
it required a modification to RIL.java which affects *every* device. but it basically goes "if samsungRIL then continue from new RIL file". the people working on the LG G2x/O2x said they're going to use a similar implementation for their RIL since it's equally as messed up in different ways.
[Vibrant Android Development] movieaddict:
anyone else having trouble getting onto cm nightlie on rom manager? I keep getting error?
[Vibrant Android Development] OPTheory:
It seems like tons are having the no audio problem when making call. I have never had this problem, not even once. Anybody else in the same boat?
[Vibrant Android Development] hitman818:
What version are you on?
[Vibrant Android Development] Moped_Ryder:
If you are #9, #10, or #11 you are about to be flamed for not reading first. :rolleyes:
[Vibrant Android Development] Moped_Ryder:
Only in the nightly section - not the others. Prob updating or doing something with it.

[Correction]

After I updated the app from the market it worked fine - showing up to #11
[Vibrant Android Development] exploit777:
FC after 35 mins 720p video rec

've tried many time, same result
[Vibrant Android Development] atinm:
When a change is in the framework, that is used for every phone - you'll see the change in all the phones. RIL stuff was done as a hack in framework (because Samsung replaced a piece of what is supposed to be common code with a custom non-conforming binary blob), and so other phones are seeing it as well. It shouldn't affect them.
[Vibrant Android Development] Moped_Ryder:
Honest question -

If the code is good, and its works properly then why would Samsung change it? Is this another reason why it takes so long for them to update (IE: 2.1 > 2.2)?
[Vibrant Android Development] atinm:
Good question. We have no idea - we assume it is because Samsung was late to the Android party, and they hacked their code in to get it out. They did a lot of things in non-standard ways, that's why it takes us longer to get rid of dependencies on non-standard things so that we can get CyanogenMod working cleanly. Their code is generally very hacky, if you look at commit logs, you'll see Google actually removing and changing the Samsung code for the Nexus S. Code that Samsung put right back in JVB for Galaxy S . . .
[Vibrant Android Development] cal4877:
How do heck do I flash a different modem and kernel and the new update if I can't get into recovery mode
[Vibrant Android Development] Nowaysout:
come on brooo. read. search! haha. you have to use the three button recovery for all up until the latest update. turn off your phone. hold down both volume keys and the power button, then after it shows samsung vibrant, let go. it'll take you to recovery
[Vibrant Android Development] atinm:
The initials do it for you. But can't hurt to do it yourself too if it gives you peace of mind.
[Vibrant Android Development] gopheer:
Not really, consistently get about 3 bars and use task killer frequently. I have the same setup on Simply Honey 2.3.3 and it lasts hours more, just saying.
[Vibrant Android Development] robkonz:
Google Video Talk

Ive been using this for a couple of days now and flashed todays update. Is Google Video Talk working in this version? I cant seem to find how to get it going.
[Vibrant Android Development] jonathanhuerta4:
Ok this may or may not be a silly question but, has the mute/unmute problem ever been fixed in the latest nightlies?. Just asking since its late and I don't get calls until morning.
[Vibrant Android Development] cal4877:
Lol I know that man however for some reason it doesn't take me to cwm it just reboots and back to normal any other ideas I tried already thru rom manager and no luck
[Vibrant Android Development] cal4877:
Nvm Its the down volume button key plus the home key and the power button key I guess my phone is not a vibrant anymore on boot logo it says gt i9000 and for this is a different combo keys
[Vibrant Android Development] skater4690:
So hows battery life on this now been off my vibrant for a lil bit experimenting with a hd2 and I thinks its time to come.back to the vibrant cause the screen is well lack of better words so vibrantly captivating lol but if the battery isn't too great ill have to stay with cm7 on the hd2...:-\
[Vibrant Android Development] Jasonhunterx:
It all depends on usage constant use I get like 5 he's I would say a little bit better then stock
[Vibrant Android Development] chev:
Thanks for that!
[Vibrant Android Development] skater4690:
Sounds good cause the screen on the hd2 is bigger but sucks and battery lasts all day and way better compared to the vibrant but the vibrants screen is amazing along with sound quality its louder and clearer
[Vibrant Android Development] atinm:
Uploaded 20110506-lightsensor update.

Changelog:

- fixes light sensor
[Vibrant Android Development] Jasonhunterx:
Y is battery life so bad for cm7 on vibrant when cm7 is notorious for amazing battery life?
[Vibrant Android Development] hitman818:
Delete
[Vibrant Android Development] d33dvb:
Are we waiting on a leak before we can get gps drivers working?
[Vibrant Android Development] hitman818:
After the 3/04 initial, the 103 mb initial needs to flashed then the light sensor update, right?
[Vibrant Android Development] gehzumteufel:
You are correct in that you are SOL if your EFS gets corrupted or borked in some way. Been there, done that. It blows.

Power management issues. It's typical when things aren't documented well.

If you are already on CM7, ONLY flash update. If you are coming from NON-CM7 rom, then flash the latest initial, and then the latest update. The new initial does NOT require ODIN/Heimdall anymore.
[Vibrant Android Development] Jasonhunterx:
Two deal breakers on this rom for me is that can't charge to 100 an can't charge phone when off will this be fixed or changed?
[Vibrant Android Development] hitman818:
Nm. So we just flash the initial kernel.zip, initial.zip then update.
[Vibrant Android Development] numberoneoppa:
Funny Samsung. Having worked as a programmer in Korea, none of this actually surprises me at all. Ok, maybe a little. I can't see why they'd ignore the changes Google made on the Nexus and revert to their odd stuff for the Galaxy.
[Vibrant Android Development] jzero88:
"atinm @TheEscapist_xda GPS, no more modem crashes (hopefully), etc."

Whaaaaaa?
[Vibrant Android Development] kimbo1986:
The updated Platypus kernel is updated for the kernel changes made from build 9 on I believe. This has nothing to do with the no audio on calls that started at build 9. This is a problem is the rom build that started also in build 9, something broke and the nightly builds where automaticly compiled before they can fix it. From what I have seen they are working on it very hard and I'm sure soon enough a new build will be compiled with a fix.
[Vibrant Android Development] psychedelicx:
First of all, thanks for all the hard work that has gone into this.

I am tied to ROM's that allow WiFi calling which is why I haven't moved away from Bionix ... is there anyway to include this feature in CM7 similar to how this was done for the Nexus One (http://unforgivendevelopment.com/20...-wifi-calling-for-cyanogenmod-7-on-nexus-one/)?

Thanks
[Vibrant Android Development] defconoi:
Yea wifi calling would be a nice addition down the road
[Vibrant Android Development] numberoneoppa:
I agree. Signal is often very poor where I am at. Low priority, though, of course, compared to getting all the basic functionality proper.

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] themoose:
Is it just me? Radio issues....

Been running Nightly-8 with KB5 modem/radio and it's been brilliant! Been getting 20+ hours with normal usage and that's with half the day in an office with crappy at best signal. However, whenever I've tried to update to the latest nightly starting with 9 and trying with 10 and 11 it loses the radio image for some reason. Even if I flash the KB5 package again after the update! But, if I flash back to 8 it magically reappears. What gives? Do I really need to do a full wipe with each nightly?!
[Vibrant Android Development] romitkin:
No, This issue has started since build 9 and is not fixed yet. atinm said they are close to find a solution for this problem.
[Vibrant Android Development] lunatikv:
How are so many people getting 20+ hours on their phones??? Do you have the higher capacity battery or something? My phone usually last, on a good day, 6 hours! And I am not constantly on it either, normal usage. I recently switched over the KB5 modem and it really has increased the battery life, I am currently at 37% and before I would be at 8% lol. Crazy battery I tell yeah.
[Vibrant Android Development] djluis48:
Same here, i would LOVE to know how to get 20hrs of batery live wuth average use...hell, i would be happy with 12hrs.

Sent fron my Vibrant!!
[Vibrant Android Development] g1flasher:
Not really sure what to tell ya about batt life.. I've got stock 1500mah batt, and get avg of 24-26hrs using k1 or kb5 sync facebook, twitter, weather widgets, the whole 9 yards. I even played games and watched netflix pretty much all day yesterday and still got 12hrs with my phone hardly ever being put down.

Ever sense the nightlys have been rolling out my batt life has gone as follows.

#1= 18-20ish

#4= 20-22ish

#6,7,8= 22-26ish.

Your milage may very..
[Vibrant Android Development] lunatikv:
I was just venting, the battery has been an issue for me even on Stock that came with the phone since day one, before I started to flash roms on this thing. You are one lucky person I tell you lol. Thanks for the reply. I had actually gotten the very first Vibrant at the T-mobile store by my job and I had to go back the very next day and get a new one because it just kept dying within 2-3 hours with barely any use, it was odd.

Anyway, paitently waiting for the next nightly. Keep up the good work guys!
[Vibrant Android Development] Sdobron:
Poor signal? That's the only thing I can think of.
[Vibrant Android Development] jzero88:
Ya regarding battery life it is vital to use kb1 or kb5 modems with this build. It really makes a difference. I would try both because kb1 works better for me than kb5 but some say kb5 is better for them.
[Vibrant Android Development] lunatikv:
Thank you for the recommendation. I have noticed that KB5 has really improved the battery life, but not by 20 hours! I wish lol. I will try KB1 next to see if it helps it even more.

@Sdobron I dont know about the poor signal thing. The bars are full, maybe the searching between 3G and H is draining the battery.
[Vibrant Android Development] masr1979:
I agree. I seem to remember that when I had a MyTouch I set it to only connect to 3G, and the battery lasted longer than when it was 2G/3G... only drawback was that I had/have crappy 3G coverage in my area.
[Vibrant Android Development] jonathanhuerta4:
If you don't mind me asking, how would I make the Vibrant only connect to 3G?. :)
[Vibrant Android Development] iwasblown:
i'm getting everything to work except speaker routing, any suggestions?
[Vibrant Android Development] neobuddy89:
Switch to build 8
[Vibrant Android Development] parmijo11:
Thought there was a option for 3G only but I don't see it, sorry. Only options for 2G only.

Sent from my Vibrant with CM7...
[Vibrant Android Development] ugokind:
again

thinking of a basin.. and you pull out the stopper.. and you open the tap to fill water.. ok this is the idea of what is the battery in cm8

because if I surf the net.. obviously with 3g up (wifi is better) I see the batt percentage that goes down EVEN if I have usb charger connected.

so this tell more than tecnicism and words.. I like this rom.. but CM8 is not perfect for audio calling... I hear very well but people on the other side have recorded the call.. ahhh the noise is .. compressed.

for the other component of the phone.. is great!

and.. with data switched off.. I see 3..4% batt down in 30 min

here are my tests
[Vibrant Android Development] cal4877:
So have anyone find a way to fix the no signal issue?
[Vibrant Android Development] MStrawder:
Grab SystemPanel off the Market and set it to monitor the device. Let it run in the background and do what you do on any given day. You can go back later and find out what's running in the background and eating CPU cycles and network traffic. I had several apps I didn't realize were set to sync so frequently and they were waking the phone up every hour or two. Since I changed those settings and froze a few apps I rarely use, but insist on running in the background, my battery life has improved dramatically.
[Vibrant Android Development] Abu-7abash:
I've been running 8 for about a week now and sound issues are zero for me and the other side of the call, excluding the mute/unmute issue this rom has been perfect for me. Sure battery life can be better but it's certainly is 40% better than any other GB rom out there for Vibrant and Im speaking from experience here.
[Vibrant Android Development] Abu-7abash:
On side note, I haven't followed anything here for about 24 hours now, so please don't kill me for asking this but It's almost impossible to know that anywhere but here. Is nightly 11 suffering from the same old call issue and by that I mean no signal/no way to hear the caller and vise versa?
[Vibrant Android Development] jimmyhawk:
Yes

cm7 latest, le kernel @ 1400 and kb5 modem....awesome
[Vibrant Android Development] ugokind:
good for U

tried to reflash from scratch.. but no improvements.. it's strange.. so I believe you!
[Vibrant Android Development] Trev420:
nightly 7 has been working great for me. just saying. i dont think i gave 8 a try. i checked and saw 9(one of the nightlies with the voice issues) so thats the one i downloaded.

sure, i have to mute/unmute when someone calls, but no big deal. i give 7 my vote for most stable that ive tried.

is there somethin in the OP that says what version is the most stable? it might be a good idea to put it in there.
[Vibrant Android Development] droidfan77:
Unfortunately it looks like which build is "most" stable is phone dependent. With my phone I have problems with random reboots and dropping wifi every 20 seconds with builds 7 and 8, so I have been rocking build 6 for the last week and it has been running wonderfully for me.
[Vibrant Android Development] jzero88:
So when is 12 expected? I thought these builds were automatic. We should have had it out by now?
[Vibrant Android Development] dcpetterson:
ONLY rule of CM: Don't ask for ETA'S!
[Vibrant Android Development] jzero88:
Didn't think I had to, thought it was automatic.
[Vibrant Android Development] masr1979:
Hmmm, I think you'd have to use a rom based on a samsung one... you'd need to do it through one of the engineering codes and I just tried SGS Tools to verify and they don't work on CM7. There's probably some way to do it, but I'm at a loss.

Well people were complaining that along the lines of

and similar, so this just means they haven't worked out the problem yet, patience is a virtue grasshopper... that said, I'm also waiting, but I can manage without it for now.

*EDIT* Some further reading and I found the code I used for the MyTouch works on the CM7 Vibrant builds... but I can only choose "GSM/CDMA auto (PRL)" or "Unknown" no other options stick. *EDIT*
[Vibrant Android Development] numberoneoppa:
http://cmsgs.com/mediawiki/index.php?title=List_of_Secret_Codes
[Vibrant Android Development] sjohnjuan:
hey.. I put the KB1 modem on my phone.. but when i go to "about Phone" it still says i have KA7 in the menu, is this normal?
[Vibrant Android Development] Jackdog89:
It should update the phone info. Where did you get the modem?

The link to the modems is in my signature. You'll have to look closely though, my sig isn't as loud as yours. ;)
[Vibrant Android Development] numberoneoppa:
Nope. Mine reads T959UVKB1.
[Vibrant Android Development] junglerumble:
First time running cyanogen. Which version should I try? Hearing bad things about the latest
[Vibrant Android Development] Abu-7abash:
I recommend 8. Great battery life and no serious issues.
[Vibrant Android Development] numberoneoppa:
Apparently "great" is subjective. :P (yes, go with 8)
[Vibrant Android Development] Abu-7abash:
Well as I've always said, I've been experiencing the best battery life on a vibrant gingerbread rom on this. That's what I meant there :)
[Vibrant Android Development] parmijo11:
Build 6 & 8 are both good in my opinion. Running 8 now.

Sent from my Vibrant with CM7...