Database Users

Epic GPS FTW!

Originally posted by: kngyn19
Looks like the Epic's GPS is indeed working correctly! Confirmed by Samsung and Engadget!
Linky:
http://www.engadget.com/2010/08/18/samsung-says-gps-is-tested-and-validated-on-epic-4g-our-testi/

I wonder if they use the same gps hardware as the GSM counterparts ?

I would guess their firmware is different enough that they fixed it before releasing the Epic. Someone mentioned that may be the reason for the supposed delay.

The EPIC and Fascinate are CDMA devices. It might take a littler longer to reconfigure stuff versus GSM.

My own reaction to this news, posted in a sister forum, is more cautious optimism.
And if Sprint management did delay the release of the Epic to incorporate a fix to the GPS, good for them. If that is true, it would seem advantageous for them to make some statement to that effect. If they keep quiet on the matter, I have to wonder why.

boomerbubba said:
My own reaction to this news, posted in a sister forum, is more cautious optimism.
And if Sprint management did delay the release of the Epic to incorporate a fix to the GPS, good for them. If that is true, it would seem advantageous for them to make some statement to that effect. If they keep quiet on the matter, I have to wonder why.
Click to expand...
Click to collapse
Maybe they want those worried about the GPS issue to rest assured but don't want to start a discussion about it where average consumers won't buy the Vibrant and Captivate variants after hearing there is a GPS issue..

gTen said:
Maybe they want those worried about the GPS issue to rest assured but don't want to start a discussion about it where average consumers won't buy the Vibrant and Captivate variants after hearing there is a GPS issue..
Click to expand...
Click to collapse
The average consumers that have the vibrant or captivate don't even know it had issues.. and some don't. We here on xda are the exception..
Most sprint customers don't even know its the same phone.. let alone know about a gps issue...
Sprint really don't need to say anything to anyone.. us here at xda are a small margin of their sales..

I honestly don't care as long as the GPS is working. For the $400 bucks i'm going to be paying for this phone (Sprint wants a $150 deposit before I can get the phone), I expect the GPS TO BE WORKING.
Im happy they are saying the GPS works but i wont believe it until I see it. I am out and about on a daily basis and use GPS just as much.

boomerbubba said:
My own reaction to this news, posted in a sister forum, is more cautious optimism.
And if Sprint management did delay the release of the Epic to incorporate a fix to the GPS, good for them. If that is true, it would seem advantageous for them to make some statement to that effect. If they keep quiet on the matter, I have to wonder why.
Click to expand...
Click to collapse
Yes.. imagine how that would go "Buy the best phone Sprint has to offer... GPS doesn't work but we'll work on it AFTER you buy the phone!" or maybe "This phone is great, GPS doesn't work but we'll fix it before you buy it!!!" ... either way it doesn't look good for the company, so keep it hush, delay it and people will get it when it comes out. The only ones *****ing about the delay are the ones on these forums which is 0.000003 of their sales.

DirtyShroomz said:
Yes.. imagine how that would go "Buy the best phone Sprint has to offer... GPS doesn't work but we'll work on it AFTER you buy the phone!" or maybe "This phone is great, GPS doesn't work but we'll fix it before you buy it!!!" ... either way it doesn't look good for the company, so keep it hush, delay it and people will get it when it comes out. The only ones *****ing about the delay are the ones on these forums which is 0.000003 of their sales.
Click to expand...
Click to collapse
That's the kind of spin Sprint would have to make if it released the phone with the GPS defect, and without fixing it first.
I was talking about a more positive statement in light of this news from Samsung. Sprint could affirm that there are no GPS issues on the Epic. And if there were issues in prerelease, but they held off to fix them first, that is a very positive thing to brag about. (And, by implication, a swipe at the two U.S. competitors who released defective products and are still awaiting new firmware in September.)

I hope this is true. I dont understand it though. I have read in many deferent places that they are working on a new driver to fix gps issues in all the other galaxy s phones. How did the fix the issue with out the new driver? If this is true then this makes me worried they will never really fix the captivates gps since the epic is fixed with the same gps driver.

I have asked multiple people who have the Epic for review purposes, and all of them state that there is no GPS problems. Things are looking good!

shep211 said:
I hope this is true. I dont understand it though. I have read in many deferent places that they are working on a new driver to fix gps issues in all the other galaxy s phones. How did the fix the issue with out the new driver? If this is true then this makes me worried they will never really fix the captivates gps since the epic is fixed with the same gps driver.
Click to expand...
Click to collapse
My guess is they did fix it..but probably want to fix all the other issues at the same time before mass pushing the update..like say the lag fix and etc..or maybe they will just include the gps fix and froyo together....either way if they release it we may be able to extract the driver and use it on the others..

gTen said:
My guess is they did fix it..but probably want to fix all the other issues at the same time before mass pushing the update..like say the lag fix and etc..or maybe they will just include the gps fix and froyo together...
Click to expand...
Click to collapse
Huh? In the wake of Samsung's public announcement that the GPS works on the Epic while the other brands are still awaiting new firmware, you think Sprint would secretly be planning to omit that fix and launch with the same defect they have? That is just crazy.
The implication of Samsung's statement is that the Epic firmware is already tested and installed on the units about to be sold and shipped. There would not need to be any pushing of a GPS update for Sprint phones.
If that is ambiguous to people, that is all the more reason for Sprint to make a statement about this.

gTen said:
My guess is they did fix it..but probably want to fix all the other issues at the same time before mass pushing the update..like say the lag fix and etc..or maybe they will just include the gps fix and froyo together....either way if they release it we may be able to extract the driver and use it on the others..
Click to expand...
Click to collapse
Yes you are right. If they do have the gps fix we should be able to port it over to the captivate. I wil have to return my captivate before the 30 days then get the epic and see what happens. If they fix the captivate I may go back to it since I love the slim look and design.

boomerbubba said:
That's the kind of spin Sprint would have to make if it released the phone with the GPS defect, and without fixing it first.
I was talking about a more positive statement in light of this news from Samsung. Sprint could affirm that there are no GPS issues on the Epic. And if there were issues in prerelease, but they held off to fix them first, that is a very positive thing to brag about. (And, by implication, a swipe at the two U.S. competitors who released defective products and are still awaiting new firmware in September.)
Click to expand...
Click to collapse
Now that would be great. Sprint launching a commercial attack on AT&T and Tmo... Go with them, you'll have phones that can't make calls and can't guide you to your destination! Not so smart for a smart phone huh?

I would lol so hard if they did a commercial like that. It is nice to see a company think of the end user and not about the $. I am testing the gps fix from the epic dump. So far it looks good. It locks the sats fast and shows me with 5m of my location(Use to never go below 30). I will test the gps when I go to lunch and see if it tracks me correctly.
Edit: I used my gps at lunch and it worked a lot better. It didnt jump from street to street and change route over and over. Its usable now but its still not as good as n1\evo. It will lag pretty bad then jump to your location. If the epic radio does not have updated code for gps that fixs lag issue then I would say gps is not really fixed just improved. I think we will have to wait till September to see if it gets fully fixed.

shep211 said:
... I am testing the gps fix from the epic dump. So far it looks good. It locks the sats fast and shows me with 5m of my location(Use to never go below 30). I will test the gps when I go to lunch and see if it tracks me correctly.
Edit: I used my gps at lunch and it worked a lot better. It didnt jump from street to street and change route over and over. Its usable now but its still not as good as n1\evo. It will lag pretty bad then jump to your location. If the epic radio does not have updated code for gps that fixs lag issue then I would say gps is not really fixed just improved. I think we will have to wait till September to see if it gets fully fixed.
Click to expand...
Click to collapse
Exactly what are you "testing" here? I gather you don't have an Epic. So you are you somehow running some hacked form of what you believe the "GPS fix" is -- drawn from the Epic dump -- on the hardware of some other Samsung S variant such as a Captivate. Right? Can you please describe the steps you used to set up this test environment. What is it about the Epic dump that you are calling "the GPS fix," and how did you apply it on the other hardware? Did you flash a ROM, change config files, or what?

boomerbubba said:
Exactly what are you "testing" here? I gather you don't have an Epic. So you are you somehow running some hacked form of what you believe the "GPS fix" is -- drawn from the Epic dump -- on the hardware of some other Samsung S variant such as a Captivate. Right? Can you please describe the steps you used to set up this test environment. What is it about the Epic dump that you are calling "the GPS fix," and how did you apply it on the other hardware? Did you flash a ROM, change config files, or what?
Click to expand...
Click to collapse
He is talking about this:
http://forum.xda-developers.com/showthread.php?t=759976

gTen said:
He is talking about this:
http://forum.xda-developers.com/showthread.php?t=759976
Click to expand...
Click to collapse
Thanks. What I see there are three hacked "experimental" versions of a "fix," none of which even purport to replicate the Epic environment completely. [Edit: I gather it was the "fix" supposed to be drawn from the Epic that was tested.] (For example, shep211 himself questioned how this can be a fix without new drivers. I agree with that criticism. But how do we even know what drivers this environment has?)
So it is not valid to run this test, which showed a less-than-successful GPS performance, and declare on the basis of that test that the Epic fix is incomplete as shipped.
The Epic fix may or may not be complete. We don't know that. We can't know it until a real Epic is tested rigorously.

Bell Canada finally admit the GPS bug!!!

I bought a Galaxy S from Bell Canada in august. Made the update to JH2 trough kies. Had the GPS bug (locked fine, but was sometimes way off (1-3 streets off)).
I told Bell. They said they didn't know any GPS problem affecting their device.
I tried many differents things, but I still had the problem so I recorded tracks with both my Hero and my Galaxy S to prove that the Galaxy S has a bug.
I called Samsung. I told them that I had a bug with the GPS. They said that they were not aware of any GPS bug affecting the GT-i9000M (the canadian version).
I went to Bell and asked for a repair. Seems like I was the first in Canada to report the problem because they told me again that there was no report on such problem, so it must be a specific problem with my device. They give me a Samsung Omnia II for the time of the repair. Worst touch screen ever, almost useless compared to a Galaxy S.
My device came back "repaired" (what they did was a factory reset and allegedly a ROM update, but it was JH2 before and after the repair, so this is bull****). In short they did nothing but loose my time.
Of course, I still have the exact same bug, the repair guy probably didn't even test it.
I call Bell again. Shock! Horror! They admit that there is a problem with ALL Galaxy S. Finally! Not that I told them since August... And it's not only in Canada, according to the tech support agent, it affects devices from all around the world. And that I shouldn't worry because the update to 2.2 will be released everywhere in the world in November and will fix that. Great!
Oh wait. The update to 2.2 is already released in some parts of Europe. I am not even sure that it fixes the GPS. At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.

+1
Two thumbs up for your effort. Hopefully canadian sgs froyo update comes on November like the rest of the world....
Sent from my GT-I9000M using XDA App

Great job on the audio recording too, nice move

Good job. Please keep us posted when froyo released.
Sent from my GT-I9000M Ver. UGJH2 using XDA App on Bell Mobility Network

sorry to say but some tech reps are more informed than others because they take time to do their own independant research. One tech i talked to barley knew a thing about the galaxy S, while another rep was fascinated by it and couldnt wait to get their own. Mine is in repair for faulty internal SD, lets hope froyo will fix the gps, as i didnt send it in for that issue.

Those who know something about the Galaxy S (and other smartphones) are the so-called "data" support.
1-877-328-2123 (choose language and then select the first option in the menu)

I agree data support are the only ones that know anything. I called customer service like 5 times before they gave me someone that knew anything, ala data support.
Sent from my GT-I9000M using XDA App

Well, I think that of course the response is "we haven't heard about any bugs". It's business -- they aren't allowed to admit to anything unless an order comes from the top to announce that a certain bug .. or a few bugs have been found. I haven't seen any admittals from Samsung that SGS is slow, laggy and the 2.2 update is crap. Or that there are any bugs at all. That would crash sales.

Same here
I got pretty much the same info. been through the same ordeal. I don't think I can last til the end of november for a maybe fix that might not fix anything or might get pushed back to january or even february or??? At least now with them endorsing the issue it should not be as hard to fight for an exchange, maybe get a Z.....

root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!

sbcmp3 said:
root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!
Click to expand...
Click to collapse
Well that's not the GPS bug I am talking about. My GPS locks just fine (as already said). The problem is that it is not always precise. But anyways xtra1.gpsonextra.net seems farther aways (mesured by ping times) than north-america.pool.ntp.org, so it should not fix anything.
And north-america.pool.ntp.org works just fine on my HTC Hero.

thurtig said:
Well, I think that of course the response is "we haven't heard about any bugs". It's business -- they aren't allowed to admit to anything unless an order comes from the top to announce that a certain bug .. or a few bugs have been found. I haven't seen any admittals from Samsung that SGS is slow, laggy and the 2.2 update is crap. Or that there are any bugs at all. That would crash sales.
Click to expand...
Click to collapse
Well the thing is, when you know that there is a bug and you hide it to increase your sales, you do not deserve any customers.

zorxd said:
At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.
Click to expand...
Click to collapse
I am very curious as to what software you used to record that call?
You didn't use a Korean Galaxy S (SHW-M110S) by any chance, did you? Because its firmware has a native call recorder function that I would die to get my hands on, but unfortunately Samsung doesn't allow international Galaxy S users to flash to the Korean firmware Send me a PM if you know how to force flash it!

dillovic said:
I am very curious as to what software you used to record that call?
You didn't use a Korean Galaxy S (SHW-M110S) by any chance, did you? Because its firmware has a native call recorder function that I would die to get my hands on, but unfortunately Samsung doesn't allow international Galaxy S users to flash to the Korean firmware Send me a PM if you know how to force flash it!
Click to expand...
Click to collapse
I am a proud user of the Asterisk PBX, which I installed on my OpenWRT router . I used that to record, not my cell phone.

zorxd said:
Well the thing is, when you know that there is a bug and you hide it to increase your sales, you do not deserve any customers.
Click to expand...
Click to collapse
All companies do that. Focusing on all the bugs takes the attention from the good to the bad. Basic stuff. All the companies that made you any of the things you own operate on the same principle. This is business. This is life.
But this does not mean they are not working hard on fixing the issues -- believe me, they are. Our comments and complaints are very important in bringing these things out. Stuff that gets discussed here on XDA dev is _vital_.

sbcmp3 said:
root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!
Click to expand...
Click to collapse
Interesting- this is one fix I hadn't seen before. Where did you read about it?

zorxd said:
Oh wait. The update to 2.2 is already released in some parts of Europe. I am not even sure that it fixes the GPS. At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.
Click to expand...
Click to collapse
thats rite live in the uk and upgraded ma android to 2.2 using kies reg mod and guess what it made the GPS worst. it wont go two streets without losing gps signal. theres no hope i heard it may even be a hardware fault.

we need newest (newer than dk28) modem.bin

to fix problem with modem(radio) issue relating to CDMA RADIO, signal bars, gps, voice audio, multimedia, 2g and 3g firmware and some power management issues with s5pc110( hummingbird) and modem (radio hardware)
if you have a odin flashable tar, PM me..
noobnl ( cyanogenmod epic team)

Newer than dk28?
Sent from my SPH-D700 using XDA App

Is there a modem newer than dk28 that anyone has? I thougt the source for the leaks didn't want to risk it again.
Sent from my SPH-D700 using XDA App

Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.

riceknight said:
Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.
Click to expand...
Click to collapse
10-char!!!

n00b,
I love your work. You're an amazing developer, you're a nice guy, and you contribute a lot to these forums. Everyone likes you and you're somewhat of a legend around here.
However, to have someone to leak you unpublished work from a huge corporation is incredibly risky. The NDA's that people sign are pretty iron clad that if they leak information, they won't be able to have a job anymore. Their trust is completely lost if they get caught and they'll have trouble finding work elsewhere. They might even face jail time and fees. That's how serious this stuff is.
I'm as anxious as the next guy in order to get the new modem, froyo, and other mods. However, if you're REALLY interested in developing... why not join the machine? AKA try to get a job with Sprint, Samsung, Motorola, HTC, etc.? You can use all of us for references! Seriously, why not turn your hobby into real money with a career with them? To program for Android in the Bay Area would net you atleast over $100K a year!

DangerZone1223 said:
I'm as anxious as the next guy in order to get the new modem, froyo, and other mods. However, if you're REALLY interested in developing... why not join the machine? AKA try to get a job with Sprint, Samsung, Motorola, HTC, etc.? You can use all of us for references! Seriously, why not turn your hobby into real money with a career with them? To program for Android in the Bay Area would net you atleast over $100K a year!
Click to expand...
Click to collapse
As someone who works for a large corporation, I can tell you that the companies in question probably have people just as good as n00b employed with them (not to take anything away from n00b since his work around here has been awesome). The problem in these large companies isn't talent (IMO) as much as it is the RED TAPE. Some of the red tape is needed, but probably like 5% of it.

riceknight said:
Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.
Click to expand...
Click to collapse
Last time noobnl tried to keep a lid on things, it kinda blew up in his face. There was a whole lot of drama about it. I do hope someone can help him out on this, though. It would be nice to see some more progress from our community. We've kind of stalled out while waiting on Samsung and Sprint.

riceknight said:
Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.
Click to expand...
Click to collapse
I would think that any reliable source that cared would have given it to him a long time ago. If they are willing to leak a new modem then why not just leak the kernel sources while they're at it..
Sent from my SPH-D700 using XDA App

DK28 was not leaked to devs. Our devs got their hands on it because someone with hardware version .4 got an OTA and worked with them to dump it to a useful format. The update.zip was also temporarily available on Google's servers.

leatherneck6017 said:
DK28 was not leaked to devs. Our devs got their hands on it because someone with hardware version .4 got an OTA and worked with them to dump it to a useful format. The update.zip was also temporarily available on Google's servers.
Click to expand...
Click to collapse
it was a tar leak.. and a ota leak too

Noob talk talk to me! I know you are a sly dog what's going on? You always have the inside track so I take it this is a hint. I hope ll is well.
Sent from my SPH-D700 using Tapatalk

You know, you could probably just edit the CDMA parameters and be done with it... I know that my radio problem is that it picks up towers that are too weak into the "active set" and that it is a recent common Samsung problem on several models. They tweak it so that it will utilize too low a signal level in order to decrease the number of "out of service" states as well as decreasing its apparent time to ready.
I just don't know how to do this on the Epic, and am waiting to see if the official 2.2 update fixes this. I know it started with the DI18 update, and persists with DK28, and disappears when flashed back to DI07. My brother's Epic which for some reason has never updated from DG17 (and he doesn't care to do it manually) and does not display this behavior.
On the A900 years ago it was easy with QPST. Actually, come to think of it, my Sanyo 8500 did it too, and I fixed that one as well.

... bump....

Do u know if the newest modem was leaked and know who would get it? Sorry i cant help i was just asking if it was leaked somewhere?

davidrules7778 said:
Do u know if the newest modem was leaked and know who would get it? Sorry i cant help i was just asking if it was leaked somewhere?
Click to expand...
Click to collapse
Obviously not or this this thread wouldn't be here.

Poryhack said:
Obviously not or this this thread wouldn't be here.
Click to expand...
Click to collapse
well he must kno something we dont know, maybe somepne got a leak and thats y hes asking?

Sources would be 10000x harder to leak than a phones zimage, modem, and /data/. Soure is held in a source control mechanism (git) internally usually, and unless the leaker is a dev, they probably don't know what to get. And if the leaker is a dev, they probably only have access to their piece of the project. Places I've worked in the past have been so anal bout what parts of source I see/have access to that I couldn't even tell what other features other devs were working on.
Sent from my SPH-D700 using XDA App

There's a January leak in somebody's hands, he knows it. I do too.

He wasn't asking for a source. He asked for the new modem which is out
Sent from my SPH-D700 using Tapatalk

No 911 in AOSP ROMS

I just want to make sure everyone knows that 911 does no work on roms that are based off the AOSP, and it NEVER HAS WORKED. You can read a better description on this post:
http://forum.xda-developers.com/showthread.php?t=1385613&page=7#68
The only ROMs that 911 has worked on are ROMs based off of official releases from Samsung. I would suggest for your safety flashing back to a Samsung based ROM.

Went back to Bionix 1.3.1, at least GPS works now. (Yeah I know why it did not work in CM7, just saying that is not too bad going back to a Samsung ROM :/)

E911 doesn't work. 911 works, different.
E911 is if you have no sim card or have no service and can make emergency calls only.
I lived a long, long time before 911 existed and I can't remember the last time I had no service to t-mobile and had to rely on att towers for an emergency call.
I'll take my chances, thank you.

Ohh now I get it I thought it did not work completely now I get it now I understand how having no source code would effect that!
Sent from my SGH-T959 using XDA App

Does 911 calling work on MIUI?
Sent from my Vibrant

Kind of scary that some people are barely now finding out that their custom flashed Vibrant doesn't make 911 calls. I wonder how many other people who don't frequent the forums often still have no clue their phone doesn't make 911 calls.
It still blows my mind why a disclaimer wasn't posted in large bold font in the CM thread when the stable was released.
Anyway I still think they did the right thing to stop support. Maybe Samsung will surprise us with source or a leak soon and we can get support back.

Tynen said:
I just want to make sure everyone knows that 911 does no work on roms that are based off the AOSP, and it NEVER HAS WORKED. You can read a better description on this post:
http://forum.xda-developers.com/showthread.php?t=1385613&page=7#68
The only ROMs that 911 has worked on are ROMs based off of official releases from Samsung. I would suggest for your safety flashing back to a Samsung based ROM.
Click to expand...
Click to collapse
according to your link:
"The same emergency call callback handling that is present on Galaxy S and Captivate doesn't work on Vibrant, and the differences are enough to make E911 fail"
What makes you think it is working on all the I9000 ports to the Vibrant and not just Official Samsung Vibrant Roms if the above statement is true? back to KB5 I guess.
I'm not saying E911 works, but why would it work on a I9000 rom with I9000 framework running on a Vibrant if it's a incompatible framework issue?

Nabeel10 said:
Does 911 calling work on MIUI?
Sent from my Vibrant
Click to expand...
Click to collapse
As long as I have been on MIUI, I have had to call 911 a few times. Each time, it would not even connect. Luckily I had my wife's phone handy.

My best combo.
Well when I found out that 911 doesn't work on CM/MiUi I switched back to 2.2.
I have been back on 2.2 for a while now and my phone is actually fast without the frequent crashes and problems that came with CM/MiUi.
If you want a fast lag free experience with working 911 I suggest the following semi-stock combo.
(before any of these steps always good idea to backup your nv_data.bin so that you don't lose your imei ever)
1) Flash stock deodexed/rooted KB5, found in the development section
2) Flash the stock KB5 kernel with voodoo lagfix included in the kernel. Also in development section. Make sure you go into recovery and enable Lagfix after you flash the Kernel. Also make sure you disable Lagfix anytime you want to flash something new.
3) Touchwiz is very laggy, so use LauncherPro instead. LauncherPro found in Market.
The above combo has been fast and lag free. 911 works and the GPS works also as best as it can.

+1 on this. I have had same experiences but with different set up. KB5 and Voodoo and am completely happy with performance, speed and stability. On Toxic D9 RC3 Bali X kernel. GPS lock 9 birds down to 10 feet.

bobshute said:
E911 doesn't work. 911 works, different.
E911 is if you have no sim card or have no service and can make emergency calls only.
I lived a long, long time before 911 existed and I can't remember the last time I had no service to t-mobile and had to rely on att towers for an emergency call.
I'll take my chances, thank you.
Click to expand...
Click to collapse
Actually, 911 doesn't really work either - you will get no audio during the call and will have to wait for a call back if your phone doesn't actually freeze when your call fails (which also happens sometimes during the 911 call on the Vibrant when using any code derived from our source). E911 is just an extreme case of the same issue. Our advice, go back to a Samsung derived framework for the Vibrant on the Vibrant.

bobshute said:
according to your link:
"The same emergency call callback handling that is present on Galaxy S and Captivate doesn't work on Vibrant, and the differences are enough to make E911 fail"
What makes you think it is working on all the I9000 ports to the Vibrant and not just Official Samsung Vibrant Roms if the above statement is true? back to KB5 I guess.
I'm not saying E911 works, but why would it work on a I9000 rom with I9000 framework running on a Vibrant if it's a incompatible framework issue?
Click to expand...
Click to collapse
The framework is incompatible with tmo - it works fine on Galaxy S and Captivate, which is one reason it took longer to find out because we didn't actually have Vibrants to test on. I don't know of any AOSP builds that didn't start with our code (CyanogenMod), and therefore it would be safe to assume that all AOSP builds for Vibrant cannot do (E)911 calls correctly. Our suggestion is to go back to a Samsung or Samsung derived ROM that is using Samsung's framework for the Vibrant on the Vibrant.

Thank you atinm. I have appreciated all your work to make our Vibrant phones better. This 911 issue has people spooked. But outside of the CM team (you and coolya). Its not understood very well. I'm dumb sometimes but I can't figure out how this would not affect non vibrant stock rooms as much as aosp roms.
Sent from my SGH-T959 using XDA App

Sorry, I'm slow...still confused. Can someone please answer yes or no if 911 and e911 will work on any i9000 Samsung Gingerbread ROMs ported to the Vibrant? Not sure if the Simply Honey (2.3.4 JVR) ROM falls into this category but I read in that post that 911 was not working -- at least in the August and September time frame.
I'm just trying to find out if there are any Gingerbread ROMs (non AOSP) I can use that will have this functionality because I'm ditching my land line and this will be my primary phone soon. If not, back to Froyo.

claucXC said:
Sorry, I'm slow...still confused. Can someone please answer yes or no if 911 and e911 will work on any i9000 Samsung Gingerbread ROMs ported to the Vibrant? Not sure if the Simply Honey (2.3.4 JVR) ROM falls into this category but I read in that post that 911 was not working -- at least in the August and September time frame.
I'm just trying to find out if there are any Gingerbread ROMs (non AOSP) I can use that will have this functionality because I'm ditching my land line and this will be my primary phone soon. If not, back to Froyo.
Click to expand...
Click to collapse
why don't you call 911 yourself ?
If your call doesn't goes thru for any reason they will try to call you back, if that's the case then just answer the phone and tell them that you bought a used phone and you were testing 911 calling.
Simple as that, I did it myself and my result varied between asop roms from phone crashing and only solution was a battery pull to connecting but not audio plus new years force close party.

claucXC said:
Sorry, I'm slow...still confused. Can someone please answer yes or no if 911 and e911 will work on any i9000 Samsung Gingerbread ROMs ported to the Vibrant? Not sure if the Simply Honey (2.3.4 JVR) ROM falls into this category but I read in that post that 911 was not working -- at least in the August and September time frame.
I'm just trying to find out if there are any Gingerbread ROMs (non AOSP) I can use that will have this functionality because I'm ditching my land line and this will be my primary phone soon. If not, back to Froyo.
Click to expand...
Click to collapse
If 911 doesn't work in CM and MiUi do you think it would work in ported i900 Gingerbread roms? I'm not 100 percent certain but I would think NO.

SamsungVibrant said:
If 911 doesn't work in CM and MiUi do you think it would work in ported i900 Gingerbread roms? I'm not 100 percent certain but I would think NO.
Click to expand...
Click to collapse
CM7 and MIUI are AOSP and i9000 Gingerbread is international Samsung if I'm not mistaken. Hence my question.

If you are like me, Cyanogen,of works great as media player for Vibrant.... happy with it, never use it as a phone anyways.
Sent from my Xoom

old news.. this has been pretty common knowledge for almost a year now. But good job compiling all the info together i suppose?
luckily in the 12 years i've cellular devices i've ha to dial 911 twice.
and even then you can call non emergency and get forwarded to local enforcement based on your Cell tower triangulation.
---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------
claucXC said:
CM7 and MIUI are AOSP and i9000 Gingerbread is international Samsung if I'm not mistaken. Hence my question.
Click to expand...
Click to collapse
Most i9000 roms "are" samsung. However if you read the OP of the rom itself you are looking to flash the Dev will usually tell you what source the rom is built off of.

For those interested...a little info on 911.
E911 stands for enhanced 911. E911 differs from 911 in that location information is transmitted to the 911 call center. This is for landline phones attached to a physical address. For wireless call, there are two types of data transmitted. The old standard (and still in use on older cell phones and with some of the newer carriers) was call Phase 1 Wireless Data (WPH1). It was simply the location of the Cell Phone tower the cell phone radio attached itself to. The current standard is called Phase 2 wireless Data (WPH2). This provides GPS location data to the call center. Depending upon the carrier, it can be actual GPS data from the cell phone chip or GPS data triangulated via cell phone towers.
Further more, none of the AOSP ROMS (miui or CM based) that I've tested work with 911. The Cyanogenmod team did the right thing pulling their work. Genesis3 (props to Genesis3!!!!) continues to dig into the problem and I'm his canary. I have personnaly verified that Simply Honey Gingerbread 2.3.4 JVR + Modem JVS works as well as NeoBuddies ICS V7. Other than that, it's a waiting game for source or a fix.
Ken

So why us Sprint detecting I'm in mikfroyo 4.62

Anyone know why when I tried to open a network support ticket they are detecting I'm on a mikfroyo rom. I changed Roms so many times the past 6months.. so what the hell is up with that:
They even said you have to be on a official Rom.. man how they detect this info is pretty funny. And how wrong it is.
But any way to fix that issue
Sent from my PC36100 using XDA App

Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...

I don't need support. I do wish to inform them of their network problem here... If so I have 8 other people with Sprint who are official.. who can report the network problem aswell ... Why would I need support if my phone is perfectly fine. And besides the fact I'm not running the Rom they are indicating I am...
Sent from my PC36100 using XDA App

Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.

nemoid said:
Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...
Click to expand...
Click to collapse
You only voided your warranty with HTC, not sprint. I've taken my rooted/S-OFF device many times and have talked to the store reps and they have no policy against rooted devices. There is stores that will give you a hassle just to be lazy, meanwhile other stores will ask you to simply flash back to stock to help narrow down issues caused by software or hardware.

Oh so a version from stock that just has apps removed that ate considered bloated. So that can be a phone error. Dude I've flashed many roms kernels and radios and its the network. I'm not after phone support. I don't need a warranty on my Damn phone but I pay them for service via their towers if they have issues with it then they should fix their network problems. I will pay insurion if I have phone issues its why I have them.
Sent from my PC36100 using XDA App

The guy just said to install a stock Rom and give him info. The guy was like okay 3rd party. You need to install stock . But he did agree there is probably a problem in the area.
Sent from my PC36100 using XDA App

ANyways the guy said I should keep stock until testing is done well. Im on a modified stock rom etc (testing this rom out). Anyways is there a way to show them my software/build number as stock or whatever to fool them when i re provision it to update their system?

nemoid said:
Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.
Click to expand...
Click to collapse
no they are not wasting their time providing CUSTOMER support to a paying CUSTOMER

How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App

culua said:
How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I used to Run Mikfroyo but the thing is I don't know how they know I was on a custom rom. Maybe when provision your phone it sends that data. Now I'm On a different rom but i was unaware how he knew. The guy *PinkElmo* basically just said to go back to stock ROM for the duration of the testing (sounds like he not only not has a problem with it but sounds like he uses custom as wellXD).
I'm still puzzled as to how they found out...

I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App

culua said:
I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I had to provision a few months back though... But It Got me wondering. I have been downloading a stock rom at 199mb it should take roughly 2-8 hours on the Sprints NOW DialUp Network

Sprint has a program called OMA-DM. This program has all the information from the status section of your device. When I worked for sprint we would have customers update their data profile, this would send the information to the tool. The rep can then see what rom you are on. However this did not work on AOSP roms since they do not update the profile.
If you want to fool sprint update your profile under a stock unmodified rom, then flash to AOSP, the info for the sense rom would be still in the system.
Furthermore they can see if you have updated the profile, so if you tell them that you did they will be able to see if you actually did or not.. They are also able to view all the transactions with dates and times between your phone and the tool.
My advise to you is to suck it up and run the official rom until the testing is over, usually about a week.
Also sprint has no control over a custom rom, so they automatically have you update profile and firmware to the current version to ensure that the phone is working to their standards and things that they have control over.
TL;DR - Quit complaining and use a stock rom so sprint can do their testing.

The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...

Pao23 said:
The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...
Click to expand...
Click to collapse
is your favorite "Tom" a "Tom Collins"? hahaha, sorry. i had to.

Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App

I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics

cmsjr123 said:
Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes the one under the updates.
scottspa74 said:
I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics
Click to expand...
Click to collapse
They used an application call LogMeIn Rescue. It gives them the ability to remotely view/control a pc, windows or blackberry phone. Its actually a lot easier to do it for a customer more often then trying to walk them through it.
Yes the information displayed in the about phone section is stored in the build.prop.
As for the software; software plays a factor in how the device operates and communicates with the network. Sprint has designed the stock software on their devices to their standards. They know their software and how it works. Now take a custom rom, one that has be frankenstined together. How do you expect a company to properly troubleshoot and diagnose a problem that could very well be related to the customer software?
I totally agree with the laziness part on the Tech Reps, after working with the company for several years, Id have to say most of the reps were less educated or technically minded about the device that they were working with. I could not tell you how many times I would hear customers complain about the Tech Reps.
Going to a hardware issue, Custom software would not break the screen, blow a speaker, or otherwise cause physical damage to the device (with the exception of a battery). So these should have no effect on hardware warranty's or exchanges.