yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Phateless:
Craigslist is your friend.
[Vibrant Android Development] Jasonhunterx:
Yes...yes it is saw galaxy s phones for 200$ value going down might bye another one :D
[Vibrant Android Development] Dougfresh:
Is anyone having issues with Bluetooth.?My dad is on #85 and his coworkers were complaining about echoes and breakups ..
[Vibrant Android Development] cwalker29:
That's exactly what did GUY! No kernel gave me sixteen hrs on 2.3 and up. It wasn't a complaint. More so a question.
[Vibrant Android Development] gamikzone:
try the latest version of neo im sure u will get alot better battery :) ive been running my phone for 12 hours with light use and got 60% left
[Vibrant Android Development] compuguy1088:
Or.... For xda'ers who are still are using a vibrant as a daily driver, it's a good time to unload their phone. Before/around the Samsung presser.
[Vibrant Android Development] Ch4m3l30n:
Calling 911 still does not work

911 still doesn't work on builds 85, 86 or 87.

:eek:

The automated message relayed is:

"Your call cannot be completed as dialed. Please check the number and dial again, or dial 611 for customer assistance. Message WA-911-51"

I realize this is a beta, but not being able to place a call to 911 could potentially cost lives if a thusly afflicted phone were the only method of communication.

This seriously needs to be fixed sooner than later please.

I had to use my wife's stock Vibrant to call after coming home last night to find our apartment broken into, a friend's laptop, wife's iPod, her car key & fob and motorcycle key & garage door opener all stolen. I still can't sleep because of this!

Thank God the vehicles are still there (for now). I have disabled the car and changed the code on the garage door opener, which I hope is enough. :(
[Vibrant Android Development] ginzberg:
911 needs to get fixed.

That said, you're using 911 wrong. That was not an emergency. You call the police in that situation, not 911 Emergency.
[Vibrant Android Development] nedlog:
Just tried the 911 test and sure enough it doesn't work.
[Vibrant Android Development] javacody:
Wow, the 911 thing is bad. I hope that gets fixed shortly!!!

A note on battery life. I added this line to build.prop:

ro.ril.disable.power.collapse=1

Now, keep in mind that my data is always off (looked at data usage on my TMobile bill, and I couldn't stomach the large data transfers happening at night when I was sleeping!) except when I specifically need it or when I'm at home hooked up to Wifi.

I charged my phone to 100% yesterday at 10:00 AM. It is now 8:15 AM and I have 45% battery left! I used the phone for about an hours worth of calls and as my alarm clock.

Before, without this line, I would have had to put the phone on the charger last night before bed.

Is there anyway we can petition to get this line added to the cm7 build.prop?
[Vibrant Android Development] fraserwAstro:
Won't adding that line to the build.prop disable sleep data access for everyone? Maybe it better to add an option in CM7 settings?
[Vibrant Android Development] ChristoA1:
FWIW in some areas that's acceptable use of 911. And yes I agree that even for nightlies, 911 calling is a requirement... however it may be difficult to figure out as it's the network denying the calls for whatever reason... it may be hard to figure out why...

Sent from my AOSP MyTouch 4G
[Vibrant Android Development] zmattmanz:
For the life of me I cannot stop getting Force Closes. I have:

ODIN back to JDF

ODIN to KB5

ODIN to KB5 with Recovery

Wipe Data/Partition and Cache

Flash Build #84

Flash Gapps

I initially thought it was restoring from TB that was causing it but I didn't this time and it is still now Force Closing like crazy. Used the Gapps from 6/13. Can anyone tell me what I'm doing wrong?
[Vibrant Android Development] droidfan77:
Here is one more request to make fixing the 911 glitch a priority. I have been using CM7 since nightly #3 and understand that it's a beta and will have it's issues, but if I can't rely on my phone being able to contact 911 when I'm in an emergency situation then this is a HUGE problem and I won't be able to remain on this ROM. Devs I appreciate all of the hard work you have done, but this 911 issue is far more important than any other bug you are trying to fix.
[Vibrant Android Development] dgsmith90:
What exactly does this line force the phone to do? I use Google Voice and if it does anything with the data connection, I wouldn't want it.
[Vibrant Android Development] javacody:
I don't know enough about it to say.

But, if we could add it as an option in the CM settings menu, that would be very cool. :D

And Google Voice can send you text transcripts via sms. I really prefer that option. Not that it transcribes that well, but I can usually get the gist of the message.
[Vibrant Android Development] ipnekgs:
What I do is:

Odin back to JFD

Boot device

Connect phone to computer

Format SD card

Place update.zip and CM7Nightly.zip on SD card

Shutdown phone

Get in plain recovery

Do wipe data and wipe cache

Get in cwm recovery

Do wipe data, wipe cache, wipe dalvik

Install CM7Nightly.zip

Reboot

Been doing this since always, with every single rom I install. Never had issues.
[Vibrant Android Development] bigtom624:
I always go to mounts and storage in cm recovery and format system, data, cache, wipe data, flash rom then wipe Davlik and fix permissions. I never had a problem doing that way either. Good luck man.
[Vibrant Android Development] db3:
i had lots of FC problems and corrupt data with #84. not sure why, but i had to go back to 81. Tried 85 and it's working great -- very odd since there's no real difference between 84 and 85 for vibrant users (that i understand). md5sums checked out so i suspect 84 was a bad build or upload or something.

Try #85 or or something more recent... Good luck!
[Vibrant Android Development] vinnydakid:
Bumping 911 issue as this seems to be incredibly important. The first thing we have to do is check if MIUI has this bug and then find out if the other Galaxy S variants have this issue. If they do then this should become a pretty large priority.
[Vibrant Android Development] zmattmanz:
Dammit! I literally just ODIN back to stock and used 84. I'm downloading 87... think I'll just try to flash over. This difference this time is that I'm going directly from JFD to CM7 instead of the added KB5 part. Thanks ipnekgs and bigtom.
[Vibrant Android Development] Locksmith81:
Puts your phone into deep sleep mode after the screen is off for a while. That's it.

from the amazing Jets Bread
[Vibrant Android Development] ironlood:
I used to get an unhealthy level of FC's, made my phone completely unusable. Apparently there were sync errors with all the Gapps (To see if this is the issue go in to settings and then accounts and sync... if its a sync error the spinning arrows next to your Google account will be red meaning sync error, if not click on your Google account and see if there are any errors in the account, it might say on the bottom that "Sync is experiencing issues at the moment and will return shortly" if that's the case then there is a sync error). in order to fix the problem i used ODIN to go to 2.2 then reflashed the nightly i was using (Manually in CWM not using Rom Manager) then prior to reboot i wiped Dalvik and flashed flashed the 6-13, then repeated the process with a Dalvik wipe and reflash gapps.

It might work for you it worked for me
[Vibrant Android Development] strictlyrude27:
I haven't needed to call 911 - when people say "calling 911 doesn't work", what exactly do they mean? Does the call never connect? Does the number come up as invalid?
[Vibrant Android Development] gamikzone:
it never really connects
[Vibrant Android Development] dgsmith90:
Correct. I just thought it was my phone acting up when I tried and was on the earlier builds. I haven't had to since. It was a legit reason to call though. I witnessed a monte carlo get t boned by a car doing 60.
[Vibrant Android Development] GreenDroidX:
How do u set the voltage and CPU on this new kernel?
[Vibrant Android Development] ChristoA1:
To clarify, it connects to the network and dials [something] but you get a carrier error.

Sent from my AOSP MyTouch 4G
[Vibrant Android Development] swa2k4:
fail

911 doesnt work?!!?!?! This is a basic requirement for all phones, if you say that calling works then 911 should work. I am saddened by the person who used version 74 and could not call 911 in an actual emergency. Please let me know which version works with 911 and I will advise all my friends on CM7 Vibrant to go back to that for the sake of their life.
[Vibrant Android Development] es7241:
Yes I have the same question, what it the latest version that has 911 working?
[Vibrant Android Development] ChristoA1:
I know 911 calling is pretty major, but some of these responses make me lawlz...

Sent from my AOSP MyTouch 4G
[Vibrant Android Development] gamikzone:
none of them do :p
[Vibrant Android Development] es7241:
lol, so your saying that 911 doesn't work on any nightly?
[Vibrant Android Development] nedlog:
I just tried it today out of curiosity, so I don't know if it ever worked and I've been flashing regularly since around nightly #8 but never had to call 911, thankfully.
[Vibrant Android Development] compuguy1088:
Did you try formatting datadata? The galaxy s phones have a partition dedicated to datadata that has the max size of 170 megabytes.
[Vibrant Android Development] Phateless:
Only thing to add is do another wipe data after you flash gapps. AND LET IT SIT ON FIRST BOOT.
[Vibrant Android Development] ericdude:
It's probably more major than you think. I work for the second largest 911 infrastructure provider in the country, and not many people realize that some people need 911 a lot more than others. The elderly and people with general medical issues are much more proactive about their 911 service being available than you would think, to the point of scheduling regular test calls through us to ensure that they can reach the nearest 911 PSAP in an emergency.

This was an issue on previous builds of Bionix and was quickly fixed after it was found to be an issue with the device phone number not being entered into the Build of bionix...doesn't seem to be the case with CM, but there must be something lacking in the code that the network doesn't like.

This really should be prioritized. I can only imagine the negative response when this news reaches sources outside of XDA and it suddenly hits all of the blogs and tech sites that have often praised CM and it's devs.

My two cents.
[Vibrant Android Development] ChristoA1:
Don't worry, I completely understand the priority; I also did 911 communication. I'm just commenting on the word usage of some of the commentary around here :D

Sent from my AOSP MyTouch 4G
[Vibrant Android Development] stevedrz:
Can anyone try 112 ? That is the international variant for 911, may work. I've seen locked phones respond to it as an emergency number ... that or 999

Just a thought....

http://en.m.wikipedia.org/wiki/Emergency_telephone_number
[Vibrant Android Development] ericdude:
Good idea, but no, I just tried it and received the same message. "the subscriber you have dialed is not in service."

I don't know enough about the coding that goes into these phones to say what the problem is, but my next guess beyond the phone number not being available in the settings->about phone->status in the build would be something to do with the IMEI possibly not being available to the network/wireless provider.

Something is lacking in this rom that either the cell towers need to route the call or that something on the actual network needs in order to route the call to the nearest PSAP.
[Vibrant Android Development] Ch4m3l30n:
Thanks, but it was after business hours at the cop shop, so they wouldn't have answered anyway. 911 was appropriate in this case.

I did call the police station's main number today during business hours wanting to discuss the case with an on-duty officer since the one who came out to take my report was off duty at the time... They transferred me to 911 dispatch.
[Vibrant Android Development] Kaik541:
This thread is now about 911 calls and the definition of an "emergency"
[Vibrant Android Development] mdkxtreme:
Hey, when you guys update, what do you guys wipe? You don't wipe data, correct? Cause with these nightlies, I can't see myself restoring from Titanium Backup every time there's a nightly update.

Is it alright to wipe cache partition and dalvik, then update?
[Vibrant Android Development] Demetris:
*Bug* report:

Latest nightly, take a screenshot enter gallery and when you click on the picture when moves to be shown gets pixelated/flickers until it shows. you have to pay attention to see it.
[Vibrant Android Development] javacody:
While I agree it's a big flaw, this is a nightly. When you flash it, you and you alone are responsible for any ill effects. No matter what.

Re-read the OP.
[Vibrant Android Development] jad3675:
The 911 bug is not going to get fixed by posting repeatedly in this thread that it's broken. Someone who is having the issue needs to do a logcat of the issue and submit a bug report here:

http://code.google.com/p/cyanogenmod/issues/list'

I'm not on T-Mobile (Cincinnati Bell) and 911 works for me. FWIW, I'm on nightly #87.

John
[Vibrant Android Development] javacody:
Actually, we are not supposed to submit bug reports for nightlies. Isn't that also in the OP?
[Vibrant Android Development] jad3675:
Yes, but the bug also exists in the latest RC - you can submit bug reports for that. Someone needs to flash RC1, logcat and dial 911.

John
[Vibrant Android Development] javacody:
I wonder if this is for all phones? All T Mobile phones? All Galaxy S phones? Or just Vibrants? That would be interesting to know...
[Vibrant Android Development] INeFFeCTiVE:
I really don't know why the USB not working bug keeps getting blown off as a hardware issue... I have it now after flashing from #73. It went from device not recognized to not being seen at all, but it can still charge the dam thing. It seems that flashing the later builds is causing the issue. Another thing leading me to believe that this is a software issue and not a hardware issue is the fact that i have never had any problems rebooting into download mode until now, and the fact that after issuing the 'reboot download' command just reboots the phone which has never failed before is now failing. There is more to this, perhaps a bad flash on my part but i cant fix it now... Is there any way to tell if there is something wrong in the latest nightlys or am I just screwed... I have ways around flashing things to my device via dropbox but it would be nice if some one at least looked at the code just to see if there was a problem.

Thanks

CM7 Still rocks...
[Vibrant Android Development] Phateless:
Everything about usb works for me except adb reboot download. I think that's a known bug and the same reason it isn't in the power menu.
[Vibrant Android Development] heyarnold007:
Samsung GPSRestore

Have any of you been able to use samsung's GpsRestore app?

I tried running it on CM7 nightly 88, and it lists the model as "soju". It wont restore the GPS settings.

I know this has been discussed ad nauseum here, but after 3 different vibrants is there any hope of gps working at all?

(i tried the gpsd file a while ago, and it didn't help at all)
[Vibrant Android Development] strictlyrude27:
Samsung GPSRestore is for Samsung-TouchWiz based ROMs, so that's probably why it doesn't work..

Have you tried the software GPS fix for CM7? See my sig. It replaces your gpsd to a known good variant (nightly #54), injects long-term orbit data, and has a couple gps.conf tweaks. A lot of positive feedback - I am able to keep and maintain a 25ft lock, although I'm still tweaking..
[Vibrant Android Development] ChristoA1:
I haven't tried, so forgive me for being uninformed, but would this problem even show in the logcat? The problem itself isn't happening at the phone level, so it wouldn't be an error per se... again I'm not horribly familiar with logcat so go easy on me ;)

Sent from my AOSP MyTouch 4G
[Vibrant Android Development] jad3675:
It may not show, but they won't even look at a ticket without a log.

John
[Vibrant Android Development] disgustip8ted:
sooo technically you answered your own question?

hehe sorry i couldnt resist

to add some actual content to this post, i did just run a logcat for a regular call and there were some things logged that appeared that it might make more sense to someone more intimate with how the phone app operates than i.
[Vibrant Android Development] ironlood:
I found out about this a while ago ... in regards to needing 911.

Most areas have a 10 digit emergency phone number. This is because sometimes cell phones cannot provide a reliable connection or location. When I calk 911 with my cellphone it routes my call to the nearest highway patrol services, I need to relay my information and emergency to them and then after I give my address they transfer me to proper dispatch then I'm required to give the same information again, hindering the response time. What I found is that rather then calling 911 you can call your closest emergency dispatch with a number that a direct connection. If you call your areas police non emergency number they should have it listed for you.

Sent from the depths of Norwegian black metal
[Vibrant Android Development] imitebewrong:
Well I just called 911, and in my area, it works no problem. 112 also worked.

I got right through to a 911 operator.
[Vibrant Android Development] vinnydakid:
Where do you live and what modem are you on?
[Vibrant Android Development] bdubs4200:
Isnt it illegally or highly frowned upon to call 911 sans emergency?? Or did you just explain to her that your bug testing? ;-)

Im using the xda premium app on my cm_vibrantmtd_full
[Vibrant Android Development] jakemg:
I was having this problem and couldn't figure it out. Then I thought back about when everything started force closing on me in two separate flashes. As soon as I set up and started using profiles, everything went nuts. Flashed the nightly from two days ago and haven't touched profiles and haven't had any problems so far...

I read somewhere for another device that this was happening when profiles are used, so I guess it's happening on our ROM, too.
[Vibrant Android Development] jakemg:
Dammit, I meant to reply to you with my previous reply about profiles causing force closes.
[Vibrant Android Development] treyvaporizer:
Every screenshot that I've taken (with the cm7 feature or any screenshot app) has done that. Not a bug, just don't know why it does that

Sent from SGH-T959 (CM7)
[Vibrant Android Development] Demetris:
That comment was funny sort of a way.

You got my attention, thanks
[Vibrant Android Development] nedlog:
If I had gotten through I would have stated I was testing my phone because of issues I was having. For some reason I'm starting to think it's T-Mobile's network in my area but I haven't tried my wife's phone yet (she has a Blackberry though).
[Vibrant Android Development] Se7eN43:
It IS a software issue. This happend when 2.2.1 kernel source was released. Warrentied phone thinking hardware issue. USB on new phone worked for some time then stopped. Flashed cm7 initial, usb worked for some time then stopped. BUT i must point out, phone IS recognized when connected to my samsung tv. i dont have a way of testing it on a mac or linux system, which might work since the OS used on the tv is linux based. Would be nice to look into to avoid having to warrenty the phone on a regular basis.
[Vibrant Android Development] INeFFeCTiVE:
Let me test it on a linux box... i got one here at work.
[Vibrant Android Development] nedlog:
Without knowing your history just be sure you have the Nexus Drivers from Google SDK tools; and ensure you download and run/install SDK tools as Administrator on your computer. Once I installed CM7 my phone's drivers changed from Samsung to Nexus and yes you cannot run the reboot recovery command from adb anymore, that's normal.
[Vibrant Android Development] bellrb19:
If it works on 2.2 then you have no warranty claim. You state you believe it is a software issue when the working then stopping to work sounds like hardware. If your phone can't handle 2.3 go back to froyo.
[Vibrant Android Development] Se7eN43:
I would like to odin back to froyo and see what the outcome is but no usb recognition. I can warrenty the phone if i have to without the complaint being usb. The phone does handle cm7 just fine til around the #40-50's nightlies. Odd thing, flashing back or restoring back did not resolve issue. Same thing happend when testing eugene's 2.2.1 dead horse kernel source, flash back and restored back with no success. If ineffective confirmes whether or not it works on a linux system, then it narrows down to software.
[Vibrant Android Development] Se7eN43:
Yes nexus drivers r installed from latest sdk

Vibrant drivers installed as well from kies

Cables been swapped

Different usb port

Different pc

Rebooting with usb connected to pc

Flashed back to roms and kernels in which usb worked

Warrentied phone

rooted, recovery new phone. Flashed rom (team whiskey) without flashing a custom kernel. Later flashed dead horse kernel after usb mounting issue was discovered and fixed. Worked fine after a while then stopped. Figured cm7 would fix it, flashed cm7 initial, usb worked but was a little buggy (connecting usb right after disconnecting the cord, was not recognized). Somewhere between nightlies 40-50 it stopped. BUT like i said, samsung tv recognizes phone and CAN mount sd and browse.
[Vibrant Android Development] derek210:
On the last few nightlies my battery is way off. I don't ever know what it actually is. Is there a fix for this?
[Vibrant Android Development] gamikzone:
did u wipe your battery stats?
[Vibrant Android Development] strictlyrude27:
I'm in the CM7 IRC room right now alerting people to the 911 issue. Hopefully people can help.
[Vibrant Android Development] strictlyrude27:
Can someone who has *confirmed* that their 911 calling does not work please attempt to call 911, then open a terminal and get the results of:

adb logcat -b radio

Then also get a logcat of a normal call. (The -b flag denotes what type of log to get - radio log is in a different location than main log, so naively doing 'adb logcat' won't help.)

Also, a full logcat wouldn't hurt either.

Please only attempt if you know you can't get through to 911. I don't want people calling 911 and getting through successfully when it's a non-emergency (although if you do, you should also get a logcat against the radio please!)

Post the result here, then I'll take it back to the IRC channel and/or try to find someone to look at the issue ASAP.
[Vibrant Android Development] derek210:
Yeah, I will try again
[Vibrant Android Development] t1h5ta3:
change log:

cm_vibrantmtd_full-87.zip (2011-08-18 10:13:11)

Improve battery calculations (android_device_samsung_vibrantmtd)

Modified MFC setting to match stock Samsung (android_device_samsung_aries-common)
[Vibrant Android Development] Ch4m3l30n:
Done; thank you!

Performed using build #88.