I have AT&T but I travel to Canada monthly. I have been flashing custom roms for a while now and have never had this issue until today. I flashed back to stock and my data remained disabled since I left the "data roaming" box unchecked. When I flashed FireFly 2.1, my phone does not realize that I am in Toronto, Ontario (roaming) and the data stays active.
For some reason my captivate is not recognizing that I am roaming.
Anyone know what to do?
arabcamel said:
I have AT&T but I travel to Canada monthly. I have been flashing custom roms for a while now and have never had this issue until today. I flashed back to stock and my data remained disabled since I left the "data roaming" box unchecked. When I flashed FireFly 2.1, my phone does not realize that I am in Toronto, Ontario (roaming) and the data stays active.
For some reason my captivate is not recognizing that I am roaming.
Anyone know what to do?
Click to expand...
Click to collapse
My only guess would be it has something to do with the rom being based off the rogers 2.2. Might be your best bet to get a widget to shut the data off
Sent from my SGH-I897 using XDA App
zelendel said:
My only guess would be it has something to do with the rom being based off the rogers 2.2. Might be your best bet to get a widget to shut the data off
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
That's what I thought, but when I flashed Phoenix 4.5 and also tried Supernova, the same thing happened. I don't think that those 2 roms are Rogers based.
It seems like this started when I first flashed FireFly. Is it possible that it changed something on my SIM card?
arabcamel said:
That's what I thought, but when I flashed Phoenix 4.5 and also tried Supernova, the same thing happened. I don't think that those 2 roms are Rogers based.
It seems like this started when I first flashed FireFly. Is it possible that it changed something on my SIM card?
Click to expand...
Click to collapse
I dont think it would have changed anything on the sim card. You are right if it did it with the other 2 as well. Did you do a master clear before flashing and after flashing FF? Might be something left over from the rom. I would return to stock flashing with the sim card removed, Master clear (yes I know it is a pita) and then reflash the rom
zelendel said:
I dont think it would have changed anything on the sim card. You are right if it did it with the other 2 as well. Did you do a master clear before flashing and after flashing FF? Might be something left over from the rom. I would return to stock flashing with the sim card removed, Master clear (yes I know it is a pita) and then reflash the rom
Click to expand...
Click to collapse
Here is the order that I did some troubleshooting:
1) I flashed and Master Cleared to Stock. - In stock, the data roaming feature works perfectly as I tested it while enabled and disabled.
2) I then installed Phoenix 4.5 - the data roaming feature was disabled by default, yet my data still was on while I am currently in Toronto.
I didn't bother continuing the tests into FireFly 2.1 since it even happened with Phoenix 4.5. So I think this rules out that the Rogers-based ROM is the issue.
I started with Cognition, then Darky's, then Phoenix, and now FireFly. Before today, I have only used the 1st three in Canada. The 1st three never had any issues with data roaming.
I used Phoenix in Canada before and the data roaming feature worked fine. I wonder why it all of the sudden stopped working.....
Any ideas?
arabcamel said:
Here is the order that I did some troubleshooting:
1) I flashed and Master Cleared to Stock. - In stock, the data roaming feature works perfectly as I tested it while enabled and disabled.
2) I then installed Phoenix 4.5 - the data roaming feature was disabled by default, yet my data still was on while I am currently in Toronto.
I didn't bother continuing the tests into FireFly 2.1 since it even happened with Phoenix 4.5. So I think this rules out that the Rogers-based ROM is the issue.
I started with Cognition, then Darky's, then Phoenix, and now FireFly. Before today, I have only used the 1st three in Canada. The 1st three never had any issues with data roaming.
I used Phoenix in Canada before and the data roaming feature worked fine. I wonder why it all of the sudden stopped working.....
Any ideas?
Click to expand...
Click to collapse
Your right that does remove the thoughts of it being Rogers based issue. To be honest I am not sure why it is happening all of a sudden.
zelendel said:
Your right that does remove the thoughts of it being Rogers based issue. To be honest I am not sure why it is happening all of a sudden.
Click to expand...
Click to collapse
I'm goingn to try a rom that I have never used before (Serendipity) just to see what happens.
Do you think there is any chance it is my sim card?
arabcamel said:
I'm goingn to try a rom that I have never used before (Serendipity) just to see what happens.
Do you think there is any chance it is my sim card?
Click to expand...
Click to collapse
To be honest I dont really think so but one never knows lol. There could be something that is causing the sim card to see that it is always in your home network. What rom did you use before that worked 100%? Do you still have it? If you do I would flash the older rom to see if it still works like it used to.
zelendel said:
To be honest I dont really think so but one never knows lol. There could be something that is causing the sim card to see that it is always in your home network. What rom did you use before that worked 100%? Do you still have it? If you do I would flash the older rom to see if it still works like it used to.
Click to expand...
Click to collapse
i'm going to try and install Cognition - the one I used in Canada before. I'll let you know what happens. Thanks for the suggestions, I'll be responding shortly...
One thing to point out... When I'm on stock, it says I am on "Rogers".
When I am having the data roaming feature issues, it says I am on "CAN Rogers Wireless Inc."
is that just the ROM being more specific and me being paranoid...or is that a hint to resolve the issue I"m having?
That sounds weird. The only other reason that could be it is because of your modem maybe? There are modems from Canadian Galaxy S models like JK4.. but then again I am not sure if modems make a difference. Agree with Zel, probably best to just get a widget and turn your data on and off manually.
arabcamel said:
I'm goingn to try a rom that I have never used before (Serendipity) just to see what happens.
Do you think there is any chance it is my sim card?
Click to expand...
Click to collapse
Serendipity did the same thing. still have the issue.
I installed AT&T Captivate 2.2 modem - UCJI6.
When I did that, there is a little "R" near my bars and a red triangle in the notification bar that says i am roaming. This being said, the data does not connect. So maybe the modem has been the issue all along....
arabcamel said:
Serendipity did the same thing. still have the issue.
I installed AT&T Captivate 2.2 modem - UCJI6.
When I did that, there is a little "R" near my bars and a red triangle in the notification bar that says i am roaming. This being said, the data does not connect. So maybe the modem has been the issue all along....
Click to expand...
Click to collapse
I'm going to flash back to stock, master clear, then flash firefly 2.1 back. I will add UCJI6 modem to see if that resolves the issue I was having on FireFly
arabcamel said:
I'm going to flash back to stock, master clear, then flash firefly 2.1 back. I will add UCJI6 modem to see if that resolves the issue I was having on FireFly
Click to expand...
Click to collapse
The modem was the issue I beleive. I am using FireFly 2.1 with znkp1 modem and there is a little "R" near my connection bars and data does NOT connect while roaming.
Thanks to the both of you that gave your input. With your help, I was able to figure out the issue. Apparently, the i9000 modems will not consider Canada roaming for an AT&T user.
arabcamel said:
The modem was the issue I beleive. I am using FireFly 2.1 with znkp1 modem and there is a little "R" near my connection bars and data does NOT connect while roaming.
Thanks to the both of you that gave your input. With your help, I was able to figure out the issue. Apparently, the i9000 modems will not consider Canada roaming for an AT&T user.
Click to expand...
Click to collapse
Glad you got everything set. Yeah it would make sense that it would not see you as roaming sense it is a Euro based modem.
zelendel said:
Glad you got everything set. Yeah it would make sense that it would not see you as roaming sense it is a Euro based modem.
Click to expand...
Click to collapse
Gonna close this up now.
Issue Solved thread closed
Related
Hey guys, I'm running remics 4.2.1 and I have had a lot of reception problems. Not sure why. The sim was out of a blackberry torch, we swapped it out at at&t for a new sim when this issue started but it has not been fixed. Does anyone have a clue as to why this would be happening? Any way to fix it?
coltlacey1 said:
Hey guys, I'm running remics 4.2.1 and I have had a lot of reception problems. Not sure why. The sim was out of a blackberry torch, we swapped it out at at&t for a new sim when this issue started but it has not been fixed. Does anyone have a clue as to why this would be happening? Any way to fix it?
Click to expand...
Click to collapse
Have you tried flashing different modem?
Is your IMEI fine?
Do you have the right carrier's APN?
BWolf56 said:
Have you tried flashing different modem?
Is your IMEI fine?
Do you have the right carrier's APN?
Click to expand...
Click to collapse
Havent tried flashing a new one yet, how do I know if my imei is fine? Also there are 5 different at&t apns....
coltlacey1 said:
Havent tried flashing a new one yet, how do I know if my imei is fine? Also there are 5 different at&t apns....
Click to expand...
Click to collapse
As long as your IMEI doesn't say unknown, it should be fine. As for your APN, just make sure you're on the right one outta the five (a little search will give you the one to use).
And if both of the above are fine, then go ahead a try flashing different modems.
BWolf56 said:
As long as your IMEI doesn't say unknown, it should be fine. As for your APN, just make sure you're on the right one outta the five (a little search will give you the one to use).
And if both of the above are fine, then go ahead a try flashing different modems.
Click to expand...
Click to collapse
k sounds good. as far as the apn, do you have to reboot for it to take effect when you switch?
Installed a new ROM, checked the APN settings on at&t its set for what its supposed to be but no luck I don't get it.
OK so after posting last I tried airplane mode. Turned it on then off then service????? What's the deal there?
Hello All,
Something changed in my phone and not really sure as to what has happened. All of a sudden my phone loses data connectivity and thinks that it is roaming. If I enable airplane mode and disable it, then the phone works for about 10-15 minutes and then loses connectivity again. Running the 12B baseband (been using it for months with no issue) and haven't changed the ROM in quite some time. This started happening on yesterday.
Any suggestions?
The 4G radio seems to have crapped out completely. Getting a replacement sent on tomorrow
Optimus124 said:
The 4G radio seems to have crapped out completely. Getting a replacement sent on tomorrow
Click to expand...
Click to collapse
Damnit. I am having the EXACT same problem, running CM11.
How did you come to that conclusion? I am thinking I'm going to have to restore to stock if I'm going to get Verizon to do anything about it.
EtherBoo said:
Damnit. I am having the EXACT same problem, running CM11.
How did you come to that conclusion? I am thinking I'm going to have to restore to stock if I'm going to get Verizon to do anything about it.
Click to expand...
Click to collapse
I reverted all the way back to 11A stock unrooted. The phone was in 4G for about 5 minutes (if that) and then remained in 3G mode.
Optimus124 said:
I reverted all the way back to 11A stock unrooted. The phone was in 4G for about 5 minutes (if that) and then remained in 3G mode.
Click to expand...
Click to collapse
I'm at the same point. Going to do an Asurion claim since I didn't buy my phone from VZW (Swappa).
I had this problem before when I tried other roms like cm rom and omni rom. I tried to do *228 to fix problem, but made it made it worse. I restored it back to stock and took it to the Verizon store. They put a new sim card in it for free and it fixed the problem. Now i am running stock with simple kernel.
Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great.
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
Alright, I'd be lying if this makes any sense to me, but the issue appears to be related strictly to the SIM card.
I had them swap the SIM, it fixed the issue, then it came back. I'm on a new phone now, and it appears to be working. The old SIM did not work on either phone, but the new one does. What makes no sense is the old SIM would work fine in my Galaxy Nexus, but would not work in the G2. Now the new SIM is working perfectly in the new G2 (haven't tried the old one).
I'm baffled.
I've never seen anything make so little sense. The guy at the store told me I would need to replace the SIM again in a few days. Whatever, if it happens again, I'll do just that.
I did the same with my gs3. What ROM are you running?
Sent from my VS980 4G using Tapatalk
The original phone was running CM 11 Nightlies.
I'm currently on stock - not sure if I'm going to stay with CM because the official thread indicates official development is DitW for the G2 .
That's actually strange... I'd expect roaming issues with an Intl ROM but not cm.
Sent from my Nexus 7 using Tapatalk
So Tmobile was having major issues on the east coast over the weekend, so I thought the problem was that. It turns out its on my end as well. I kept going from 4g lte to no service all the time. I tried a few diff roms and all done with a clean install and still had the same issue. I thought maybe it was some tweak I did after the rom install, but I was wrong. I just flashed my phone back to stock via odin and did the update from tmobile and my phone seems to be fine. Has anyone else had any similar issues after flashing their phone?
jrobinsky said:
So Tmobile was having major issues on the east coast over the weekend, so I thought the problem was that. It turns out its on my end as well. I kept going from 4g lte to no service all the time. I tried a few diff roms and all done with a clean install and still had the same issue. I thought maybe it was some tweak I did after the rom install, but I was wrong. I just flashed my phone back to stock via odin and did the update from tmobile and my phone seems to be fine. Has anyone else had any similar issues after flashing their phone?
Click to expand...
Click to collapse
No, I didn't experience any issue during last weekly. Did you try to call Tmobile to check out?
yoshinowasomy said:
No, I didn't experience any issue during last weekly. Did you try to call Tmobile to check out?
Click to expand...
Click to collapse
It was a none issue on the North East. My friends and fiance had the issues, but even after it was fixed I still had the issues. I have narrowed it down to flashing roms. Maybe i had a bad tmobile update idk, ill have to check and keep trying,
Today my Nexus will only get 3G and says "000000" in the settings instead of Verizon. What could be the problem?
TIA
Xirix12 said:
Today my Nexus will only get 3G and says "000000" in the settings instead of Verizon. What could be the problem?
TIA
Click to expand...
Click to collapse
I had the same issue trying blisspop, got a roaming notification, and could only get 3g after turning on data roaming. The only way to get LTE back was to flash a stock based rom, I used cleanrom, then I was able to go back to liquidsmooth. I tried going straight from blisspop to liquid while having the issue and same issue.
I did manage to try bliss one more time, and it worked..until I rebooted and same issue again. So back to cleanrom then to liquid..ugh
Thanks for the reply. Same thing. I just did what you mentioned. I had LTE working and on Blisspop. I then rebooted to install some navbar mods and bam lost LTE and got the "000000" instead of VZW.
Xirix12 said:
Thanks for the reply. Same thing. I just did what you mentioned. I had LTE working and on Blisspop. I then rebooted to install some navbar mods and bam lost LTE and got the "000000" instead of VZW.
Click to expand...
Click to collapse
Having weird issues where I am suddenly only able to get LTE on stock (cleanrom) based roms as well. Never had an issue on any rom previously. Weird.
Ok, so I just went from CleanROM to MeanPop rebooted and lost LTE and was only on 3G. Then from CleanROM to Chroma rebooted and lost signal entirely. I am not on Liquidsmooth from CleanROM and I have rebooted and still have LTE signal.
akellar said:
Having weird issues where I am suddenly only able to get LTE on stock (cleanrom) based roms as well. Never had an issue on any rom previously. Weird.
Click to expand...
Click to collapse
I am also having issues with Verizon as well, It started happening yesterday around 10am. I was on Puritan ROM, I switched to Chroma, Temasek, Euphoria and having the same issues where it's either 3G or the bar with an exclamation point. I flash Clean Rom and Sinless and I am able to get LTE again. Has anyone found a solution cause I would like to go back to Euphoria or other ROMS? Thanks
Can't even get LTE with Clean ROM anymore. After further testing, I put the phone on airplane mode for like 10 seconds and was able to get back LTE. This whole thing is just so weird
Yeah it's very odd, tried a few more times myself, and both times when I got LTE on bliss, a reboot would instantly kill it and it would go back to the data roaming 000000 issue, and 3g only. Tried the fastboot oem config carrier vzw command, flashing the zip, nothing had any effect.
I always have to go back to cleanrom to get LTE back. A couple times, when cleanrom was installed, it didn't give LTE right away, but I changed from global to LTE, toggled airplane mode and LTE was back. I tried going directly from Bliss to Liquid again, but it's like LTE must be working before it will work on liquid, even from a nandroid backup.
braxync said:
Yeah it's very odd, tried a few more times myself, and both times when I got LTE on bliss, a reboot would instantly kill it and it would go back to the data roaming 000000 issue, and 3g only. Tried the fastboot oem config carrier vzw command, flashing the zip, nothing had any effect.
I always have to go back to cleanrom to get LTE back. A couple times, when cleanrom was installed, it didn't give LTE right away, but I changed from global to LTE, toggled airplane mode and LTE was back. I tried going directly from Bliss to Liquid again, but it's like LTE must be working before it will work on liquid, even from a nandroid backup.
Click to expand...
Click to collapse
yup I was desperate too and tried the fast boot oem config carrier VZW command, flashing the zip, to no effect as well. Since I am under no contract I might as well go to Tmobile. Have you tried Sinless?
I haven't tried sinless, but maybe I'll check it out and see what happens... Hope someone figures it out soon as I'd like to try other roms, but need to keep LTE.
braxync said:
I haven't tried sinless, but maybe I'll check it out and see what happens... Hope someone figures it out soon as I'd like to try other roms, but need to keep LTE.
Click to expand...
Click to collapse
Well, if anything changes please keep me posted. Thanks for your input
this is a known issue for just about all roms except stock based.
the_rooter said:
this is a known issue for just about all roms except stock based.
Click to expand...
Click to collapse
I know, but everything was going well. In the past I had flashed DU, Tamasek, Chroma and purity without an issue. The LTE bar and signal was always consistent, but starting yesterday things went sour. I even tried flashing old versions of my previous ROMS and I am still seeing no LTE. It's so weird that out of the blue a few people just lost LTE on verizon. Clean ROM still an awesome ROM so no issues for me but it was nice to try other builds.
Damon13 said:
I know, but everything was going well. In the past I had flashed DU, Tamasek, Chroma and purity without an issue. The LTE bar and signal was always consistent, but starting yesterday things went sour. I even tried flashing old versions of my previous ROMS and I am still seeing no LTE. It's so weird that out of the blue a few people just lost LTE on verizon. Clean ROM still an awesome ROM so no issues for me but it was nice to try other builds.
Click to expand...
Click to collapse
i am on pureandroid made by the same developer of cleanrom
Works great with xposed
the_rooter said:
i am on pureandroid made by the same developer of cleanrom
Works great with xposed
Click to expand...
Click to collapse
Great! Will give it a try!
I had to switch to MeanPop to get LTE back. Does anyone know the technical reasons this stopped working?
fucheeno said:
I had to switch to MeanPop to get LTE back. Does anyone know the technical reasons this stopped working?
Click to expand...
Click to collapse
From my understanding a few ROMS used a certain commit that dealt with Verizons APN's setting and It didn't play nice with VZ. Chroma is up and running.
Made a thread about this about a month ago. It was a PIA. Verizon does not recognize this phone as a compatible phone with their network. I went from a working phone for 2.5 months to not being able to get service. Was on the phone over a couple days trying to go through with tech on making it work. I had intermittent 3G, ! in navigation bar, and many other problems. I finally spoke to a guy in tech and he told me that the phone kept being registered in Verizon's network as incompatible and consequently being stolen. He finally got it rolling again and haven't had too many problems, but he said that it could easily happen again and to have a back-up Verizon phone to switch the sim card into when calling tech support. Since then it has been fine, but I did have 3G for a day. I did reboots and backup restore, etc...None of it was an immediate fix. I just waited till the next day and when I looked at my phone LTE was back. d
ame29 said:
Made a thread about this about a month ago. It was a PIA. Verizon does not recognize this phone as a compatible phone with their network. I went from a working phone for 2.5 months to not being able to get service. Was on the phone over a couple days trying to go through with tech on making it work. I had intermittent 3G, ! in navigation bar, and many other problems. I finally spoke to a guy in tech and he told me that the phone kept being registered in Verizon's network as incompatible and consequently being stolen. He finally got it rolling again and haven't had too many problems, but he said that it could easily happen again and to have a back-up Verizon phone to switch the sim card into when calling tech support. Since then it has been fine, but I did have 3G for a day. I did reboots and backup restore, etc...None of it was an immediate fix. I just waited till the next day and when I looked at my phone LTE was back. d
Click to expand...
Click to collapse
Has nothing to do with this issue
Sent from my Nexus 6 using XDA Free mobile app
I'm beginning to think that this may be on Verizon's end because I can't get LTE back on any ROM. Mabey because if the official release of nexus 6 on their network.
Just to update everyone. I just went from Liquidsmooth to Chroma without going to Stock based ROM and was able to get LTE. The first time I rebooted it took some time, but I have rebooted twice and have not lost LTE. Hoping it stays that way. This is using Chroma's latest update 3.2.15 r2
So pretty simple I have a nexus 6 and it was originally from t mobile. It worked fine then it started saying emergency calls only it seems occur immediately after trying to make a call. Texts don't affect it but as soon as I receive a call or make one all service is lost. I'm using straight talk tmo sim and it has happened on pure nexus, 6 ROM and cr droid also du.. Straight talk shows I'm connected and only thing that fixes it is luck and wipes with reflashing a ROM. I assume its something on my device that doesn't get wiped but I'm not sure. Any tips or advice would be appreciated.
Ry4n83 said:
So pretty simple I have a nexus 6 and it was originally from t mobile. It worked fine then it started saying emergency calls only it seems occur immediately after trying to make a call. Texts don't affect it but as soon as I receive a call or make one all service is lost. I'm using straight talk tmo sim and it has happened on pure nexus, 6 ROM and cr droid also du.. Straight talk shows I'm connected and only thing that fixes it is luck and wipes with reflashing a ROM. I assume its something on my device that doesn't get wiped but I'm not sure. Any tips or advice would be appreciated.
Click to expand...
Click to collapse
Does it happen on stock?
How old is the device?
Do you have the simcard ejection tool? Have you tried reseating the simcard?
What radio are you running?
I've had it
rignfool said:
Does it happen on stock?
How old is the device?
Do you have the simcard ejection tool? Have you tried reseating the simcard?
What radio are you running?
Click to expand...
Click to collapse
I've had it two years. It was from T-Mobile site and yes and I believe its 44r I updated it back when I jumped to nougat. It does it on stock as well. I reflashed stock and it fixed it and then flashed a new ROM and it worked until I received a call. I played around a bit got it back and as soon as I called my voicemail and hung up I lost all service. I can't get it back again so I'm not sure what fixes it but I can say 100% a phone call in or out is what kills it.
Ry4n83 said:
I've had it two years. It was from T-Mobile site and yes and I believe its 44r I updated it back when I jumped to nougat. It does it on stock as well. I reflashed stock and it fixed it and then flashed a new ROM and it worked until I received a call. I played around a bit got it back and as soon as I called my voicemail and hung up I lost all service. I can't get it back again so I'm not sure what fixes it but I can say 100% a phone call in or out is what kills it.
Click to expand...
Click to collapse
In the development section there is a thread about radios...
Grab the baseband cache eraser... Or reflash your radio... I bet you have junk causing your issue in there...
And format your cache partition for poop and giggles when you do the radio thing
rignfool said:
In the development section there is a thread about radios...
Grab the baseband cache eraser... Or reflash your radio... I bet you have junk causing your issue in there...
And format your cache partition for poop and giggles when you do the radio thing
Click to expand...
Click to collapse
Just tried to no avail. If you have another theory maybe how straight talk switches from 4g to 2g or 3g for voice differently maybe its a build prop or some conflict. Otherwise I will just request a new sim maybe its an issue on there end.
Just wanted to update in case others struggle, I had a pack of 3 straight talk sims so I went online and transfered the number and service to my att sim and it fixed the problem either it was a sim issue or straight talk tmo problem or flashing a ROM or weekly jacks up something but either way I'd like to know because the Verizon sim never worked right it was the first one I tried hoping for more coverage in dead tmo spots. I will keep a look out in case someone has experienced this or has another idea. For now its working well with att sim
I didn't realize you had made a separate thread about this, as you mentioned your issues in the Pure Nexus thread. But now that I saw this thread I can utter those four immortal words no one likes to hear.
"I told you so."
In all seriousness, it's good to know that you got the issue resolved.