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
Related
The purpose of this thread is to diagnose, and possibly fix, the dropped network connection issue when using i9000 based ROMs on the Captivate.
If you don't know what I'm talking about, then you probably can ignore this thread.
But if, like myself, your connection to your provider's network is hit and miss after installing an i9000 ROM then I want to hear from you.
Why go through all this trouble?
Because most i9000 ROMs run circles around the current Captivate ROMs in terms of speed as well as function.
Bluetooth is a prime example since voice dialing with a BT headset works on i9000 but does not on Cappy ROMs.
It will help if you provide the following:
1. Carrier (mine is AT&T).
2. Approximate date you bought your phone (got mine launch day back in August).
3. Current ROM and/or ROM you experienced the issue with (I've used just about every i9000 ROM out there but currently I'm using Axura 2.3).
4. Your ideas/theories as to why the problem occurs.
5. Any "fixes" you may have tried that improved or solved the issue.
One theory I have as to why this is happening is that my carrier (AT&T) may be intentionally "kicking" me off the network when it sees that I'm using a phone that is configured for another network. mad: bastards!)
If that's the case, then maybe there is a way to spoof and make AT&T think the phone is still pure Captivate.
Or, maybe an app can be developed that will monitor connection status and automatically reboot the phone when connection is lost for more than a couple of minutes.
I'm pretty sure we can figure this thing out if we put our heads together.
Thanks in advance for any assistance given.
Seems like modem would be an important thing to track IMO.
AT&T wouldn't boot you off. Because if they did, they would have been booting me off daily with my Nexus One.
I was having problems with a rom. When I lost connection (say at my UNI, since they have poor service in the lecture halls) it would reconnect, but data wouldn't ever work again. I would have to reboot my phone to get it to work.
I since reinstalled an updated ROM, but haven't been back to UNI to test it out, since the semester is over.
I just assumed it's a bug in the modem that was being used in my rom.
Carrier - AT&T
Purchased - Launch Day
ROMs Tried - All the i9000 modems lost service and the i9000 kernels paired with captivate modems wouldn't give me call sounds.
Currently on a JJ4 Kernel+Voodoo 5 / JJ4 Modem slow upload speeds but d/l~3.2mbps and definitely seems the most stable as of now
Fix - no earthly idea
hellishhorses said:
Carrier - AT&T
Purchased - Launch Day
ROMs Tried - All the i9000 modems lost service and the i9000 kernels paired with captivate modems wouldn't give me call sounds.
Currently on a JJ4 Kernel+Voodoo 5 / JJ4 Modem slow upload speeds but d/l~3.2mbps and definitely seems the most stable as of now
Fix - no earthly idea
Click to expand...
Click to collapse
Have you tried the new JK3, JK4, or JL3 modems? I had similar issues with the old JG8 modem, but with the new 2.2 modems out there I no longer have these issues.
Jay120171 said:
Seems like modem would be an important thing to track IMO.
Click to expand...
Click to collapse
so yea , the jl3 gives me roaming issues ,..
the jk3 rarely does ( and I say like it happened twice)
so I say its the modem ..
btw I m on fido / rogers ..
doctahjeph said:
Have you tried the new JK3, JK4, or JL3 modems? I had similar issues with the old JG8 modem, but with the new 2.2 modems out there I no longer have these issues.
Click to expand...
Click to collapse
Yes all three modems tried with JJ4 Kernel- Didn't have in-call sounds (ringing, dialing, other person talking, other person hearing me). Data speeds were great, but I can't live without the phone part of my phone.
AND when I tried pairing the JK4 modem with i9000 kernel it was super fast but kept getting "no service"
hellishhorses said:
Carrier - AT&T
ROMs Tried - All the i9000 modems lost service and the i9000 kernels paired with captivate modems wouldn't give me call sounds.
Click to expand...
Click to collapse
Not trying to derail this thread and I realize I am new here but are you saying you were running an i9000 kernel on your Captivate? If you run an i9000 ROM you must use a reorientated kernel like xcaliburinhand's.
For reference: I am running Darkyy's 5.5 JPU ROM, xcalibur's reorient kernel 2.2.1 and the JPU modem on my Captivate. I have been running a JPU modem and Darkyy's JPU ROM (5.2-5.5) for a few days now and I haven't had any issues with data.
Jay120171 said:
Not trying to derail this thread and I realize I am new here but are you saying you were running an i9000 kernel on your Captivate? If you run an i9000 ROM you must use a reorientated kernel like xcaliburinhand's.
For reference: I am running Darkyy's 5.5 JPU ROM, xcalibur's reorient kernel 2.2.1 and the JPU modem on my Captivate. I have been running a JPU modem and Darkyy's JPU ROM (5.2-5.5) for a few days now and I haven't had any issues with data.
Click to expand...
Click to collapse
Yes these were all reoriented i9000 kernels for the captivate
I'm seeing that the phones purchased after the launch date aren't having these issues
I am not sure if i have the same issue...Although my data speeds are very crapy lately...Does this have anything to do with what you are talking about
hellishhorses said:
Yes these were all reoriented i9000 kernels for the captivate
I'm seeing that the phones purchased after the launch date aren't having these issues
Click to expand...
Click to collapse
So do you think that if I exchange my phone for a more recent one the issue may go away?
doctahjeph said:
Have you tried the new JK3, JK4, or JL3 modems? I had similar issues with the old JG8 modem, but with the new 2.2 modems out there I no longer have these issues.
Click to expand...
Click to collapse
All of those modems dropped service for me.
I'm currently running the JL3 and my service just dropped about an hour ago and I had to reboot to get it back.
That's why I don't think the modem is the issue...it's either in the kernel or the network is rejecting the phone.
I have been having problems since I flashed Axura 2.2 on my captivate. I do not receive any phone calls or texts, of course my carrier is ATT
ozone777 said:
So do you think that if I exchange my phone for a more recent one the issue may go away?
Click to expand...
Click to collapse
That's certainly a possibility. The reason I haven't done this yet is that the inconvenience of having to "stock" my phone then trick AT&T into thinking there's something wrong with my phone even though it's just their lousy service and them retarding the phone so it doesn't beat their almighty iPhone far outweighs the benefits of getting a slightly faster phone. Plus, I'm waiting on a fix for this one, cause I've kinda grown attached to her.
Is there anyone that has this issue and is NOT on the AT&T network?
Or is it isolated to just AT&T phones?
i have been having this issue too mainly cm6.1 betas, tried different modems all do the same thing, wondering if its a combo of firmwares
You're missing the two most important pieces of information, kernel and modem version.
There after known modem kernel incompatibilities. I've been on an i9000 modem & kernel since we got the first ones back in the end of september or beginning of october, and I've never had an issue with anything.
Build date (underneath the battery) would probably be more helpful than purchase date if it's actually a hardware issue.
Sent from my brain using Thumbs 2.0.
glitterballs said:
You're missing the two most important pieces of information, kernel and modem version.
There after known modem kernel incompatibilities. I've been on an i9000 modem & kernel since we got the first ones back in the end of september or beginning of october, and I've never had an issue with anything.
Build date (underneath the battery) would probably be more helpful than purchase date if it's actually a hardware issue.
Sent from my brain using Thumbs 2.0.
Click to expand...
Click to collapse
Who is your carrier and what is the build date of your phone?
Which number is the build date by the way?
there have been a few threads on this. they were also moved because some more than "helpful" people decided it didnt belong in the development forum (i, obviously, dont agree there).
however, we have made some headway. please see the following 2 threads:
http://forum.xda-developers.com/showthread.php?t=865846
http://forum.xda-developers.com/showthread.php?t=864903
you can continue chatting here or take up over there.
tl;dr - we have been working on this. it seems like launch captivates are the hardest hit, and it seems like i9000 based roms AND modems cause the issue. running a captivate based rom (the most important part) and modem seems to get you back in action. - easiest move: flash cog2.3b6 (dont have a DL link right now and DG took it off his repository) which is captivate based. for performance, toss the latest voodoo kernel in there.
keep us posted on your findings otherwise.
Batch #1006 (assuming that means June 2010, if it's anything like the printed control boards I warranty for work)
Rev. 0.4
I've got a JJ4 modem paired with a JJ4+Voodoo kernel right now and very stable and no "No Network" issues. But it is a fair bit slower than the Perceptions and other i9000 based ROMs. Something I'll just have to deal with I assume.
http://twitter.com/#!/SamsungFUSNews/statuses/38172937131401217
Model: SCH-I500 | Code: USC | Version: SCH-I500USEB16/SCH-I500USEB16 | Date: 17.02.2011 14:09 | Size: 202,38 MB | ID: 1324135920
If someone could get firmware out from FUS server....
correct me if im wrong but isnt the us cellular mesmorize also the i500? and the code listed on twitter saying USC seems to indicate its not for us
(as someone who works on themes i dont think i can deal with porting to another tw build )
Yes, US Cellular (Code: USC) is the Mesmerize, and is also a SCH-I500. It isn't directly compatible with the Fascinate. They do list another I500, but with a code of XAR. I think this might be the Cellular South Showcase. I also believe it is like the Mesmerize in that it's not directly compatible with the Fascinate.
The code for Verizon is VZW.
Zerg The Bear said:
Yes, US Cellular (Code: USC) is the Mesmerize, and is also a SCH-I500. It isn't directly compatible with the Fascinate. They do list another I500, but with a code of XAR. I think this might be the Cellular South Showcase. I also believe it is like the Mesmerize in that it's not directly compatible with the Fascinate.
The code for Verizon is VZW.
Click to expand...
Click to collapse
I still personally believe they are all interchangable...just a matter of gettimg the settings right.My phone is running a verizon modem on a different carrier...
All of the mesmerize roms I've flashed booted just fine; its essentially the same hardware. The problems begin to arise when a different modem is used. In that sense its about as functional as a fascinate rom w/o phone or web capability.
In my case I found it to be a valuable tool in recovering from a brick. I always keep a stock mesmerize rom handy. It was the one thing that would flash and boot into recovery. From there odin could successfully flash a stock vzw i500 file and my phone worked again.
Lesson learned: don't touch the phone button in odin and read up every last bit of information available before taking similar risks.
That about sums up my experience with mesmerize roms.
Sent from my SCH-I500 using Tapatalk
sneakysolidbake said:
All of the mesmerize roms I've flashed booted just fine; its essentially the same hardware. The problems begin to arise when a different modem is used. In that sense its about as functional as a fascinate rom w/o phone or web capability.
In my case I found it to be a valuable tool in recovering from a brick. I always keep a stock mesmerize rom handy. It was the one thing that would flash and boot into recovery. From there odin could successfully flash a stock vzw i500 file and my phone worked again.
Lesson learned: don't touch the phone button in odin and read up every last bit of information available before taking similar risks.
That about sums up my experience with mesmerize roms.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
But I think, regardless of the modem, it can be done. It's just a matter of using the correct configuration setup in qpst. For example, I'm using a Verizon modem on a completely different CDMA carrier. I just had to adjust the um and am in ppp config along with mob + simple bx in qpst and it works like a charm. So long as you have a functioning prl, it's just a matter of finding a tunnel for 3g. In other words, you would be using a flashed phone on US Cellular. I've used sprint phones on verizon, both sprint and verizon on cricket ect. It's just a matter of finding the right settings.
I was not aware this was possible. Interesting. Are there any advantages besides the obvious one of carrier choice?
jenisiz said:
But I think, regardless of the modem, it can be done. It's just a matter of using the correct configuration setup in qpst. For example, I'm using a Verizon modem on a completely different CDMA carrier. I just had to adjust the um and am in ppp config along with mob + simple bx in qpst and it works like a charm. So long as you have a functioning prl, it's just a matter of finding a tunnel for 3g. In other words, you would be using a flashed phone on US Cellular. I've used sprint phones on verizon, both sprint and verizon on cricket ect. It's just a matter of finding the right settings.
Click to expand...
Click to collapse
Sent from my SCH-I500 using Tapatalk
sneakysolidbake said:
I was not aware this was possible. Interesting. Are there any advantages besides the obvious one of carrier choice?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I feel bad for US and Southwest Cellular users b/c of their lack of development capabilities so I was willing to look into it for them. As far as advantages, I've found ironically that some radios do enhance call quality, but having the correct prl is key. Our phones share identical hardware...only difference is the modem software. It's funny though no one has noticed it though, but often ppl will flash dl09 or eb01 modems and still get partial use, either data or call/text. It's obvious it's working, however since you're no longer on that previous radio, the settings would have to be adjusted. Honestly, if anyone is willing to try...I don't mind helping.
jenisiz said:
I still personally believe they are all interchangable...just a matter of gettimg the settings right.My phone is running a verizon modem on a different carrier...
Click to expand...
Click to collapse
and i have did what he said to get mine successfully flashed to another carrier (cricket) also
akaine2001 said:
and i have did what he said to get mine successfully flashed to another carrier (cricket) also
Click to expand...
Click to collapse
Hey there...enjoying it still? All the same services for 1/3 the cost
sneakysolidbake said:
I was not aware this was possible. Interesting. Are there any advantages besides the obvious one of carrier choice?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Verizon f'd up with me bigtime talkin about 197 a month for two fascinates ?! wtf ... and thats not even unlimited minutes, I have unlimited everything on both phones for 55$ a piece. with 3.13$ of tax, not 25$, the 3g is negligibly different from verizons, at a fraction of the cost. Voice and text actually come through more often for me, i wasn't getting calls etc when using verizon.
Two fascinates, Android plan, $113.13. My oldest daughter is born on 12/13/05 so the 13 doesn't bother me, it was actually a good sign, especially with a new baby on the way next month. Until I get this job, and can afford a 200$ phone bill (alone until she goes back to work) i'm going to stick with cricket. Good thing is, I can always go back to vzw, purchase a phone outright as an upgrade, and then flash that one back to cricket also now that I know how to
akaine2001 said:
Verizon f'd up with me bigtime talkin about 197 a month for two fascinates ?! wtf ... and thats not even unlimited minutes, I have unlimited everything on both phones for 55$ a piece. with 3.13$ of tax, not 25$, the 3g is negligibly different from verizons, at a fraction of the cost. Voice and text actually come through more often for me, i wasn't getting calls etc when using verizon.
Two fascinates, Android plan, $113.13. My oldest daughter is born on 12/13/05 so the 13 doesn't bother me, it was actually a good sign, especially with a new baby on the way next month. Until I get this job, and can afford a 200$ phone bill (alone until she goes back to work) i'm going to stick with cricket. Good thing is, I can always go back to vzw, purchase a phone outright as an upgrade, and then flash that one back to cricket also now that I know how to
Click to expand...
Click to collapse
I actually really enjoy cricket. PRL hacking is easy with them, and they share towers with sprint anyways. The best part though is you're not limited to any specific phone or carrier. I can use any CDMA android I want.
sneakysolidbake said:
All of the mesmerize roms I've flashed booted just fine; its essentially the same hardware. The problems begin to arise when a different modem is used. In that sense its about as functional as a fascinate rom w/o phone or web capability.
In my case I found it to be a valuable tool in recovering from a brick. I always keep a stock mesmerize rom handy. It was the one thing that would flash and boot into recovery. From there odin could successfully flash a stock vzw i500 file and my phone worked again.
Lesson learned: don't touch the phone button in odin and read up every last bit of information available before taking similar risks.
That about sums up my experience with mesmerize roms.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Wait, are you saying that you fixed your phone after flashing with Phone in Odin?
GoogleAndroid said:
Wait, are you saying that you fixed your phone after flashing with Phone in Odin?
Click to expand...
Click to collapse
That's correct. At least I think I did. I tried many bizarre combinations of tar files in just about every button in odin. I didn't know any better.
If it really is IMPOSSIBLE to recover from a phone flash then I don't know what to think anymore.
Sent from my SCH-I500 using Tapatalk
It's definitely possible to recover from that. Before we had modems to flash, it wasn't.
Sent from my SCH-I500 using XDA App
To summarize: every CDMA Galaxy S ROM will work as long as I do one of the following:
1) Install a Verizon I500 modem
-or-
2) Use the correct settings with the existing modem.
I wanted to install AOSP 2.2, and then replace the parts that didn't work from another ROM, but I was worried about this part. This information helps. Thank you.
Sent from my SCH-I500 using XDA App
dangerismymiddlename.com said:
To summarize: every CDMA Galaxy S ROM will work as long as I do one of the following:
1) Install a Verizon I500 modem
-or-
2) Use the correct settings with the existing modem.
I wanted to install AOSP 2.2, and then replace the parts that didn't work from another ROM, but I was worried about this part. This information helps. Thank you.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I'd still save back ups incase you run into problems. But as long as you use a modem that is for an i500 it's a matter of finding the right settings. I'm trying to find one I can teenker with for the non verizon users.
Anyone want the files? I have the generic and the USC version...Please let me know via PM Developers only please!
jenisiz said:
I'd still save back ups incase you run into problems. But as long as you use a modem that is for an i500 it's a matter of finding the right settings. I'm trying to find one I can teenker with for the non verizon users.
Click to expand...
Click to collapse
i'm a showcase user and I flashed the EB16... the modem works Perfect? I guess you can say... last night i was getting very slow speeds using speedtest app, but today i've gotten the fastest speeds ever... So i think it may be just the fact that Cell South's network is so finicky.. I've always gotten different speed test even when i was stock, from 1 test to the next will be drastically different..
However the problems i've having with the ROM are:
GPS button will not turn on....
When you reboot you have to re log in to gmail/twitter/facebok
for some reason Exchange email stays logged in..
ADB won't give SU access because it says it's a production build..
It won't let me access the market..
I think it's the same problems for the mesmerize, and more than likely will be the case for the Fascinate..
But if we could all figure this out, then we could possibly have 1 ROM for all 3 phones making it simple to port themes/mods/etc...
I really wish some DEVS would help us out with this..
elijahblake said:
i'm a showcase user and I flashed the EB16... the modem works Perfect? I guess you can say... last night i was getting very slow speeds using speedtest app, but today i've gotten the fastest speeds ever... So i think it may be just the fact that Cell South's network is so finicky.. I've always gotten different speed test even when i was stock, from 1 test to the next will be drastically different..
However the problems i've having with the ROM are:
GPS button will not turn on....
When you reboot you have to re log in to gmail/twitter/facebok
for some reason Exchange email stays logged in..
ADB won't give SU access because it says it's a production build..
It won't let me access the market..
I think it's the same problems for the mesmerize, and more than likely will be the case for the Fascinate..
But if we could all figure this out, then we could possibly have 1 ROM for all 3 phones making it simple to port themes/mods/etc...
I really wish some DEVS would help us out with this..
Click to expand...
Click to collapse
I believe it's def. doable. It's just a matter of trying to figure out a way for the roms to have universal settings. All I500's store their values for their network in the same location, hence the reason why qpst will register the phones as the same phone. The only thing I've noticed different is the modem and the way the rom reacts to the modem and those settings. For example, I am in the process of using kaos v5 and it has reset my connections. No 3g but talk and text. If I can figure out how the values are being pulled I can adjust the settings and we may be a step closer to having gingerbread on all three devices.
I had this problem since SC roms but now I have Evil froyo rom and having alot more missing calls. My friend told me that he called me three times but didnt get any....i really dont care about the multimedia but phone calls!!!! phone should functioned as it should be but its not...so anybody knows how to solve this problem...?? I tried to do *228 thingy but still doing this...
What radio/modem are you using? Try using ED04, if you're not already on it. I had your problem before and ED04 seemed to help.
Sent from my SCH-I500 using XDA App
Go back to eclair with ea28 radio. There is no froyo rom/radio free of this issue currently available. I have tested all radios available right now and had missed calls on all of them. ED04 made it even worse actually.
I've tried numerous radios, roms, and kernels and am currently on stock ED04 with the same issues. I think ED04 is actually worse on my phone as well. I've read about quite a few people having the same problem and the overall consensus is that it's a hardware issue.
For ****s and giggles, Odin the EC09 radio. I personally use it and find it to be pretty nice, much faster data speeds, and it MAY fix your issue.
It's not a FroYo deal, it's a network issue. My wife's Fascinate is still on DL09 and she has missed calls too. A lot of people believe it is an issue with LTE affecting 3G, since the problems started popping up around the same time LTE was flipped on
Call and complain... They know it's a known issue, but they are not fixing fast enough. It's pretty sad. I miss calls from the wife and boss... You may even get the droid charge...
RacerXFD said:
Call and complain... They know it's a known issue, but they are not fixing fast enough. It's pretty sad. I miss calls from the wife and boss... You may even get the droid charge...
Click to expand...
Click to collapse
Yeah I did call and they offered me another Fascinate, Droid X or D1 so nothing that I could accept. The only upgrade that makes sense available right now would be Charge but had no luck convincing them. Right now I'm testing EC09 leak modem and so far all calls came through (as far as I know) but it was just 2 days so it's too soon to know if it helps or not.
They won't offer me jack... Am I saying something wrong? Hahaha
This freakin issues is pissing me off since i got this VZN fascinate imported here in India ,
and its not NETWORK its just bloody FROYO and FASCINATE , somehow all froyo ROMS have got this crap issue.
i have started inumerable threads about so many ROMs and setups but this issue always keeps coming back.
I am keeping my fingers crossed that the GB roms wont have this bug..
Just to keep myself connected i have yesterday flashed back to dl09 debloated and using ed04 ( i know its full of crap this modem is , but i am giving it a shot with dl09 and so far in last 24 hours havent missed a single call.
I'm on hold with VZ tech support right now, I can't stand this bug anymore.. I'm trying to find a new job so I can't afford to be missing calls
edit: they're sending me a new fascinate.. might just have to buy another phone and use my fascinate as an mp3 player
Trying out the EC09 (gingerbread) radio.. I may not know anything for a few days.
I have been having this problem every since I started using froyo
if I switch back to eclair it is gone
It is not in the radio
It has to do with the phone going in a deep sleep it will not wake up
The deep sleep is causing other issues with sms, mms, alarm not working when set all because it will not wake up
Alot of problems Same cause
The only way I have found to stop this is go to Eclair
wardcst said:
I have been having this problem every since I started using froyo
if I switch back to eclair it is gone
It is not in the radio
It has to do with the phone going in a deep sleep it will not wake up
The deep sleep is causing other issues with sms, mms, alarm not working when set all because it will not wake up
Alot of problems Same cause
The only way I have found to stop this is go to Eclair
Click to expand...
Click to collapse
Yes indeed, ECLAiR is the only answer for this issue.
if anyone wants to install debloated rooted version of dl09 then simply ODIN this > http://forum.xda-developers.com/showthread.php?t=911677
after that boot it up
store latest SU file in sd card and this debloated ROM (only ROM and nothing else ) from adryn >>
http://adrynalyne.us/files/roms/DL09_2.zip
and then again shutdown and ODIN CWM and without booting install SU first via recovery
boot up
shutdown
reboot into recoveryand flash the alreday stored adreyn's debloated version.
My wife has always been on DL09 and still experiences it... Which is why I keep saying it isn't a froyo issue
Sent from my SCH-I500 using XDA App
You are probly right
It just got way worse with froyo
Is it doing this on the GB Leak
JaeKar99 said:
Trying out the EC09 (gingerbread) radio.. I may not know anything for a few days.
Click to expand...
Click to collapse
Been using it for couple days. Nothing new to report, went back to ED03. If we could just get the stability of GB 3G signal I would be a very happy camper.
+1 for the EA28 modem, at least for my phone in a VZW marginal reception area where 1x reigns supreme. Easy to get the missed calls, by attempting calls during bootup, sleep-wake, busy with GPS/aGPS, etc.
In my particular case, ED04 made things worse. EC09 was much much better. EA28 had the least missed calls as far as I can tell (n=1). YMMV.
Link to jazzyjames discussion:
"Interesting GPS find"
http://forum.xda-developers.com/showthread.php?t=1106868
Link to Comradesven's thread:
"[MODEM][ODIN][CWM]DL09, EA28, ED01, ED03, ED04 modems without ridiculous 100MB OTAs"
http://forum.xda-developers.com/show....php?t=1097355
Link to JPTech7's thread:
"[EC09][MODEM][ODIN] EC09 Radio/Modem for Odin"
http://forum.xda-developers.com/show....php?t=1132236
Deep Sleep Missed Calls
Download softlocker from market. Keeps the phone from going into deep sleep and helps out with the missed calls issue. It is mostly for tablets but will also work for android phones.
Just saw this over on Google+ and didn't see it posted on here.
We are no longer supporting the Vibrant due to the inability to dial 911. We consider the issues related to this unresolvable without source code from Samsung related to the Radio interface layer and its interactions with the Audio layers and have taken the decision to no longer support this. We apologize for the inconvenience and strongly suggest that Vibrant users use a Samsung ROM due to the 911 issues with any ROMs based on open source code.
-SGS Team/Team Hacksung/Teamdouche​
https://plus.google.com/115559452692492479251/posts/cebZUe4E7wM
Old news
Sent from my T959 using XDA App
Bad news...
bfranklin1986 said:
Old news
Sent from my T959 using XDA App
Click to expand...
Click to collapse
The 911 issue is old news, but the decision to stop support for the phone specifically stating the reason to be said 911 issue is new.
Sent from my HTC Sensation 4G
I wonder why there hasn't been a fix for it yet. Why not just let us set a location during the initial setup. Seems like an easy fix to me
geoffcorey said:
The 911 issue is old news, but the decision to stop support for the phone specifically stating the reason to be said 911 issue is new.
Sent from my HTC Sensation 4G
Click to expand...
Click to collapse
It's old news that they were going to stop support....
ferhanmm said:
I wonder why there hasn't been a fix for it yet. Why not just let us set a location during the initial setup. Seems like an easy fix to me
Click to expand...
Click to collapse
Did you even read the link? They explained why in both the CM7 nightly thread and at the g+ link.
Sent from my HTC Sensation 4G
This is just ****ty news. I wish the was a disclaimer when you download that you have to agree to rather then this...
Sent from my SGH-T989 using XDA App
its the nice way of saying we are dropping support, they really dont have a good reason considering all that they really need to do is fix button mapping and release it, but since gps doesnt work 100% of the time they basically just said F*** it, thats my take, I'm sure that there will be kernels that are cm9 compatible and then we will just flash an I9000 version of the rom with a button mapped fix.
the best way to do it would be to create an update.zip that has a button fix in it so then we can just flash I9000 roms and then the button mapping fix but we'll see
So the 911 issue is specific to CM7 ROMs and not gingerbread ROMs for Vibrant in general? Do the new ICS ROMs have this problem?
bearsfan85 said:
its the nice way of saying we are dropping support, they really dont have a good reason considering all that they really need to do is fix button mapping and release it, but since gps doesnt work 100% of the time they basically just said F*** it, thats my take, I'm sure that there will be kernels that are cm9 compatible and then we will just flash an I9000 version of the rom with a button mapped fix.
the best way to do it would be to create an update.zip that has a button fix in it so then we can just flash I9000 roms and then the button mapping fix but we'll see
Click to expand...
Click to collapse
I am sorry no - it isn't that simple. 911 calls, audio callbacks (and related GPS callbacks) aren't working correctly specifically on the Vibrant due to missing code in the Radio Interface layer and audio stacks. We don't have this code, we are unlikely to ever get this code. This was something we've been trying to fix for a while, and have finally given up. As a lot of other ROMs use our code, we'd rather not have CyanogenMod distributing a ROM that cannot do 911 calls correctly, even with disclaimers. The disclaimers will mean squat if someone actually has to call 911 and we strongly encourage you to stick with Samsung ROMs. Until we can fix this, this is off our supported device list and we are sorry about this.
This came to a head last evening after some unrelated threats, but an actual 911 operator who has been working with us to fix 911 calling made it clear to us just how dangerous this really is if Vibrant cannot do 911 calls, and we made the decision to stop support and remove the device from our supported list.
Yes, others can still build it - but it will not be CyanogenMod that does it. We're sorry about this.
atinm said:
I am sorry no - it isn't that simple. 911 calls, audio callbacks (and related GPS callbacks) aren't working correctly specifically on the Vibrant due to missing code in the Radio Interface layer and audio stacks. We don't have this code, we are unlikely to ever get this code. This was something we've been trying to fix for a while, and have finally given up. As a lot of other ROMs use our code, we'd rather not have CyanogenMod distributing a ROM that cannot do 911 calls correctly, even with disclaimers. The disclaimers will mean squat if someone actually has to call 911 and we strongly encourage you to stick with Samsung ROMs. Until we can fix this, this is off our supported device list and we are sorry about this.
This came to a head last evening after some unrelated threats, but an actual 911 operator who has been working with us to fix 911 calling made it clear to us just how dangerous this really is if Vibrant cannot do 911 calls, and we made the decision to stop support and remove the device from our supported list.
Yes, others can still build it - but it will not be CyanogenMod that does it. We're sorry about this.
Click to expand...
Click to collapse
Atinm you guys did the right thing. I appreciate everything you and everyone else working to bring CM on Vibrant did. However, no rom is worth risking someones life. I applaud you guys for making the right decision. I hope Samsung releases the source needed and we can get CM back on the Vibrant with working 911/GPS.
It may suck for us but its the right thing to do what if someone dies do to this then they could be sued and possibly mental stress on someone who is doing something for fun/free
Sent from my SGH-T959 using XDA App
Sounds like we all gotta put our heads together and fix the 911 bug
Sent from my SGH-T989 using xda premium
That's a pretty weak excuse to give up on development. People can add local emergency service numbers to their phone contacts
lilroach said:
That's a pretty weak excuse to give up on development. People can add local emergency service numbers to their phone contacts
Click to expand...
Click to collapse
But they don't want to put out product that would put peoples life at risk an vibrant has no source so that makes it even harder so y waste a head ache
Sent from my SGH-T959 using XDA App
I was just thinking today that it may be time for a new phone... I guess this further suggests that the Vibrant is surely fading away.
lilroach said:
That's a pretty weak excuse to give up on development. People can add local emergency service numbers to their phone contacts
Click to expand...
Click to collapse
I disagree. Local numbers don't do jack when you are out of town. To many what-ifs to worry about.
These guys supported our phones LONG after Samsung abandoned us. Credit where credit is due I say.
lilroach said:
That's a pretty weak excuse to give up on development. People can add local emergency service numbers to their phone contacts
Click to expand...
Click to collapse
Another point to add is what if you didn't have cell reception? And you were lost in the woods? The only number you can contact is the emergency number which happens to be 911. So if you didn't have the option to call this # you are screwed big time.
I've been trying to research this 911 issue from a user's perspective for the past few days now, but I still have some questions unanswered. If anyone can answer them or point me in the right direction/thread I'd appreciate it.
First of all to reiterate something I learned, the issue isn't that you can't actually dial and connect to a 911 operator. The problem is that they won't be able to hear you and they wouldn't be able to get a GPS lock on your phone. Although I've also heard 911 calling does work for some people in some states.
Anyway, so my question is which specific ROMs actually support 911 calling? Is it JUST the offical stock ROMs? What about Froyo custom ROMs like Bioinix 1.3.1? I read from one Bioinix user that 911 does work, but I'm not sure if they're just guessing. Do these custom Froyo ROMs have this missing Samsung code (I'm guessing all GB ROMs don't)? Thanks!
Being a relative newcomer to the Android and Smart Phone world, I wanted to comment on my experiences with my first step into this community.
The phone that I have is a Samsung Galaxy SCH-S950C that I purchased from Straight Talk about a year ago. While it is not necessarily common knowledge... this phone is identical to the Samsung Galaxy Fascinate SCH-I500. This particular model was made specifically for Straight Talk and is a CDMA phone running on the Verizon Towers.
For all practical purposes, when it comes to modifying this phone, you can simply treat it as a Verizon Fascinate and simply follow any existing guide for flashing custom ROM's. The only real difference is that if you ever wanted to go back to Stock for whatever reason.... there is an additional Stock Image for Straight Talk which I can point you towards if anyone needs it.
Since getting this phone, I have tried pretty much every modification you can think of because.... well to put it simply... playing with these things and testing their limits is a lot of fun
I have become "Flash Happy" and change ROM's on this phone every couple of days. Thanks to the Developers on this Forum.. I have had a nearly constant supply of new and interesting ROM's to play with. They all have their advantages and disadvantages. Some are more stable than others. A few are good for daily drivers and a few are a little too unstable for anything but experimentation with special features.
I have experienced every issue you can think of.... I have had my phone stuck in Boot Loops, been unable to flash anything due to Status 7 Errors, I have had the battery overheat, the Radio stop working, lockups, random reboots, and even pretty much bricked the phone.
Thanks to all the great people on this Forum.... I have always been able to find a way to recover from any issue and get my phone back to stock and start all over again.
So THANK YOU to all the members of this Forum and to all of the Developers that are still producing great work for this phone... such as HHP_211, Unjustified Dev, BBrad, Bdogg718, Notta, DerTeufel1980 and of course jt1134, you have provided me with an unending supply of fun things to do with this phone. And I thank you for all that you guys do for this community.
So which ROM do you find most enjoyable/stable ?
Sent from my SCH-I500 using xda app-developers app
icemanwbs said:
So which ROM do you find most enjoyable/stable ?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Most enjoyable..... I'd have to go with Domination simply because it has all the bells and whistles.... ton's of features to play with
Most Stable...... HellyBean. Never had any issues at all with it and it has quite a few bells and whistles as well.... I tend to keep going back to it as my daily driver because I keep running into glitches with all the others I've tried out...
Do you have any suggestions on where I can start to find a proper mod for this phone? I find the stock rom extremely unreliable.....crashing programs etc pretty often....and i am pretty new to fooling with them, but have a basic grasp of what i'm gonna be doing.
Well.... this forum is the place to start.... take a look through all of the ROMs listed in here and play around with a few of them. They all have their strengths. What works for one person may not work for another.... it all depends on what you like.
4.3 ROMs are a lot of fun to play with since they are the newest version of Android... however Data is really flaky on 4.3 so far. It is an issue that is being worked on so soon I think it will be stable... but it isn't really suitable for a daily driver quite yet unless 3G data is not important to you.
A lot of people say that 4.2.2 ROMs are too much for this phone to handle and are slow and buggy... however my experience tells me that they work just fine. I am a personal fan of HellyBean.... I have never had an issue with it... everything works the way that it should.... and at least for me... it runs very fast. But my best suggestion is to try a few out for yourself and pick the one you like.
CGSemperParatus said:
A lot of people say that 4.2.2 ROMs are too much for this phone to handle and are slow and buggy... however my experience tells me that they work just fine. I am a personal fan of HellyBean.... I have never had an issue with it... everything works the way that it should.... and at least for me... it runs very fast. But my best suggestion is to try a few out for yourself and pick the one you like.
Click to expand...
Click to collapse
I agree. I actually went back and tried Gummy ICS (had a bad experience with that after trying to change the boot animation. wouldn't boot up at one point at all). Since I have a VZW fascinate, i tried the EH03 Verizon build and oh god it's awful. eh03 is like ten times better than the eclair and froyo builds, but it's still really bad due to bloatware and Touchwiz. so i tried CM7 and wifi was actually really finicky. i was using glitch kernel but it was still strange. ICS and JB could hold a connection, even EH03 could, but not CM7 for some reason.
I have since moved to Hellybean and haven't looked back.
---------- Post added at 03:57 PM ---------- Previous post was at 03:57 PM ----------
also, out of curiosity, what version of Android is stock on the Straight Talk Showcase?
skepticmisfit said:
[/COLOR]also, out of curiosity, what version of Android is stock on the Straight Talk Showcase?
Click to expand...
Click to collapse
The Showcase came with Gingerbread 2.3.4.... In order to go back to stock... I actually Odin the Verizon EH03 package and then Odin a Straight Talk Image over that. Basically the same as the Verizon Fascinate Image but with some of the Bloatware removed and changes the Boot Animation to Straight Talk logo instead of Verizon.