Database Develop

Atrix HD - Having intermittent signal loss using Straight Talk.

The wife and I have Atrix HD phones that we bought used but in great condition a couple months ago. We purchased the Straight Talk at&t compatible micro sim kits from walmart.com and set up our service. We previously had Samsung Captivates also on Straight Talk and they worked flawlessly. I put in my APN settings and I get data and MMS perfectly but occasionally I get a red triangle where my signal bars should be and my phone says "Emergency Calls Only" and I will wait 30 seconds or so and my signal returns. There is no steady decline in signal that leads up to this. It goes from like 4 bars to a red triangle with a cross inside it.
I live in a fair sized town and have always had 3 or more bars of at&t service with phones in the past so I do not think its an issue with poor coverage. I am attaching pictures of my APN settings.
Any help would be appreciated.

Applehater87 said:
The wife and I have Atrix HD phones that we bought used but in great condition a couple months ago. We purchased the Straight Talk at&t compatible micro sim kits from walmart.com and set up our service. We previously had Samsung Captivates also on Straight Talk and they worked flawlessly. I put in my APN settings and I get data and MMS perfectly but occasionally I get a red triangle where my signal bars should be and my phone says "Emergency Calls Only" and I will wait 30 seconds or so and my signal returns. There is no steady decline in signal that leads up to this. It goes from like 4 bars to a red triangle with a cross inside it.
I live in a fair sized town and have always had 3 or more bars of at&t service with phones in the past so I do not think its an issue with poor coverage. I am attaching pictures of my APN settings.
Any help would be appreciated.
Click to expand...
Click to collapse
I'm having the exact same issue since switching to to the 4G LTE micro sim. It only seems to happen on mine when I'm connected to Wifi though. I get the red triangle intermittently. This never happened to me until I went from the old sim to the new one. Can't find anything on it yet.

same thing
The same thing is happening to me here as well but using a Net10 LTE sim card (same as straight talk basically). I notice it the most after I complete a phone call. It takes a minute or two to regain service again. This is really annoying. Would like to see a solution to this problem.

So I worked with Straight Talk support for about 5 days, back and forth, bounced to several reps throughout and nothing substantial has come of it. It seems a little better after they made "adjustments" to my account as they put it, but I still get disconnected from mobile data when on wifi.
Don't get me wrong, their support people were very responsive and seemed to genuinely want to help me, but in the end they said "your ticket has been open for more than 24 hours so it has been closed. If you continue to have issues please open a new ticket." Anyone else have any luck on this?

I also was having this problem found that if you edit existing att apn (phone needs to be rooted)with sqlite editor it seems to work fine.
tether also works fine this way.I am still not able to get lte to work with straight talk even with new sim.

Just to follow up. As usual, it seems with ST support, one rep tells me they have some things they can try once I call back on another line and then I get a new rep who says nothing can be done until 10 people complain about the exact same issue I'm having. I'm assured this is an isolated incident...
I went ahead and purchased a new SIM card (looks different than the first LTE card I had) in case I had a faulty SIM. Worked flawlessly for a day and now it's back to the same issue of cutting out completely throughout the day.

same problem here on wifi get red triangle (especially after phone call).
More since i switched from 4g sim card to lte sim noticed that data disconnect from time to time like make impossible to watch video flawlessly...
with old 4g was yes only 4g but never loss a bite....could watch anything also streaming tv.....now it is impossible.....
the end of the month going to switch to old sim and see if the problem is in the new sim cards they tried may be to limit access or is in the new service doesn't matter what sim card you possess..
we'll see...

htchd2fix said:
same problem here on wifi get red triangle (especially after phone call).
More since i switched from 4g sim card to lte sim noticed that data disconnect from time to time like make impossible to watch video flawlessly...
with old 4g was yes only 4g but never loss a bite....could watch anything also streaming tv.....now it is impossible.....
the end of the month going to switch to old sim and see if the problem is in the new sim cards they tried may be to limit access or is in the new service doesn't matter what sim card you possess..
we'll see...
Click to expand...
Click to collapse
Switching to my old sim was my first thought to. However when I tried it didn't work. I called ST and they informed me that once you switch sims, the old one can never be reactivated. On top of that they don't offer the non LTE sims anymore. Such a pain. Hope you have better luck though.

pentjaksilat8 said:
Switching to my old sim was my first thought to. However when I tried it didn't work. I called ST and they informed me that once you switch sims, the old one can never be reactivated. On top of that they don't offer the non LTE sims anymore. Such a pain. Hope you have better luck though.
Click to expand...
Click to collapse
Some one could correct me if I'm wrong here but I'm pretty sure this is a result of ROMS using a 4.4 rom. Modem crashes. If you want to test it run a Stock ROM... If you are already using a completely stock ROM then Idk what to tell you. But same thing happens to me using any version besides stock. And yes only when on WiFi

metalmike6 said:
Some one could correct me if I'm wrong here but I'm pretty sure this is a result of ROMS using a 4.4 rom. Modem crashes. If you want to test it run a Stock ROM... If you are already using a completely stock ROM then Idk what to tell you. But same thing happens to me using any version besides stock. And yes only when on WiFi
Click to expand...
Click to collapse
I'm on a 100% stock ROM, I haven't unlocked my boot loader, just rooted.

pentjaksilat8 said:
I'm on a 100% stock ROM, I haven't unlocked my boot loader, just rooted.
Click to expand...
Click to collapse
Then unlock your bootloader and try flashing different radios from the different stock fastboots we have. Depending on the fastboot I can have next to none or almost full in my bedroom. For me, ATT JB is in the middle, JB Mex Retail is the best, Bell ICS is the worst. ATT ICS was about the same as ATT JB.

skeevydude said:
Then unlock your bootloader and try flashing different radios from the different stock fastboots we have. Depending on the fastboot I can have next to none or almost full in my bedroom. For me, ATT JB is in the middle, JB Mex Retail is the best, Bell ICS is the worst. ATT ICS was about the same as ATT JB.
Click to expand...
Click to collapse
For the time being, I just switched to Aio and so far so good with LTE coverage and no disconnecting issues. If they return I'll try different radios as you suggested.

So I've been with Aio for about a week now and everything is working great (knock on wood). I've had 2 mobile data drops at work with Wifi turned on, but they only lasted for a second and I do have really bad reception here inside the building. Outside of that no issues at all so far. I'll update if anything changes.

[Q] Phone Roams All The Time

My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.

EtherBoo said:
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
Click to expand...
Click to collapse
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.

dr_w said:
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
Click to expand...
Click to collapse
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.

EtherBoo said:
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
Click to expand...
Click to collapse
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"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.

dr_w said:
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"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.
Click to expand...
Click to collapse
Alright, so, I have some interesting news.
I got a replacement device from Asurion - not just a replacement, a brand new device out of the box. I pulled it out of the box, swapped the SIM, same exact issue .
I went to Verizon and *****ed up a storm. They basically said "you bought it on eBay, not our problem" (I actually did Swappa - but they don't know Swappa and they do know eBay).
So I got the guy in the store to do some digging, and apparently Verizon has a point opened up with LG as they're seeing this on more and more devices - especially since KK came out. So I figured I could try an older radio. The device was on 12B when it arrived. I just flashed stock to 10B and it's the same issue. I don't know what's going on at this point - nothing makes sense but its apparently a known issue that's been appearing since the KK update.
I'm going to call Asurion and request a new device again since this one is doing the same thing, we'll see what happens. I'm still leaning towards hardware and thinking there was a slew of bad radios that went out.
Just for giggles - and I have no reason whatsoever to think this will work. I'm going to swap out the new SIM that came with the phone. Originally, I just put in my old SIM since the new one was taking too long to activate. I'm having the exact same issue I had previously. With that, I'm going to leave the new SIM in and see if it has the same dropping issue. The guy in the store had mentioned he could swap out the SIM but after a few days it will crap out again... which makes zero ****ing sense. Because of that, I might as well see what happens if I pop a new SIM in. While again, this makes 0 sense, I'm wondering if maybe the phone is frying the SIM somehow?
Again, it makes no sense at all, but I have nothing else left to try other than getting Asurion to repeatedly send me phones until I find one that works or they replace for another type of phone (which I REALLY don't want). I'll drop an edit in an hour or so if what I try makes a difference.
Quick Edit:
I COULD just keep going to the VZW store and have them repeatedly swap out SIMs since it will fix it for a few days .
EDIT:
Got the new SIM installed and it's working. The guy in the VZW store told me that we can keep swapping SIMs and the same issue will happen, which again, makes no sense to me. I'm at a bit of a loss to be honest. I wonder if it's possible that my old device was frying the SIMs (again, makes no sense) and that maybe the new SIM not going in my old device will fix the issue.

What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk

dr_w said:
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The only ROM I've ever run was CM11.
Same thing happened on stock though after flashing through the LG Flash Tool. Then, with the new phone from Asurion, used old SIM - 3G only. Used new SIM - 4G sticks.

[Q] Sprint Stock stuck on activating

I am happily using liquid smooth but wanted to test a few things on stock. when i deploy stock i get stuck on the activating the connection part. I let it sit for about 15 minutes and still nothing. i can restore my nandroid and connect again just fine.
I am new to sprint so i don't really know the ins and outs.
Thoughts?

Also I can only get 3g when I had 4g with this room earlier. Do I need to call sprint?

JustusIV said:
Also I can only get 3g when I had 4g with this room earlier. Do I need to call sprint?
Click to expand...
Click to collapse
Have you used the Sprint fix zip for custom Roms? If not, search around for it. That might help. As far as stock hanging up, I've had that happen too. I usually just cancel and retry and it goes through. You can find the data reset dialer code here:
http://forum.xda-developers.com/showthread.php?t=2949996
That might help too.

Funny... I'm having a similar problem. I switched to CM Nightlies for about three days. I experienced some instability today, so I decided to go back to stock for a while.
I flashed the newest factory image and re-locked my bootloader. It hangs on "Waiting for activation" or something like that. Nothing I do in settings resolves this.
Going to give it a little time and pray it fixes itself. I really loathe having to call customer service.

I skipped and went to more/cell networks/carrier setting/update Prl/update config and it went through. On stock.

Just an update. I moved my phone to Verizon and got instant 4G.
I just couldn't handle the crap service anymore.
Moved from one evil to one super evil.

Verizon Network Only 3G

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

Lost mobile data with an exclamation mark, I can still make calls.

Edit: added details.
I have had my Nexus 6 for 3 days and first installed my Straight Talk SIM yesterday. Everything worked fine for less than a day then I started getting MMS picture messages failing. Now I get no mobile data. I swapped my SIM with my wifes, also on straight talk and mine with hers and I get the same issue and mine works fine in her phone.
I have rebooted many times, I have checked my APN settings and even have tried alternatives.
I have done a few searches and see other have this or very similar issues but I have not found anything that fixes my issue.
I am running Pure Nexus with the stock kernel.

tjlmbklr said:
Edit: added details.
I have had my Nexus 6 for 3 days and first installed my Straight Talk SIM yesterday. Everything worked fine for less than a day then I started getting MMS picture messages failing. Now I get no mobile data. I swapped my SIM with my wifes, also on straight talk and mine with hers and I get the same issue and mine works fine in her phone.
I have rebooted many times, I have checked my APN settings and even have tried alternatives.
I have done a few searches and see other have this or very similar issues but I have not found anything that fixes my issue.
I am running Pure Nexus with the stock kernel.
Click to expand...
Click to collapse
Need few more details. Who is your carrier? What ROM is on working phone?
I would clean flash latest factory image and see if that helps.
https://developers.google.com/android/nexus/images#shamu

Witek_M said:
Need few more details. Who is your carrier? What ROM is on working phone?
I would clean flash latest factory image and see if that helps.
https://developers.google.com/android/nexus/images#shamu
Click to expand...
Click to collapse
Straight Talk.
Pure Nexus ROM
I did a back up and tried flashing another ROM last night, CyanogenMod but I did something wrong and I ended up flashing Pure Nexus again and it restored everything from my backup (still learning I guess). But it is working fine, now that is, it was working fine before. The only thing that I thought may have caused an issues was I had Macrodroid setup to disable wifi radio when out of my homes cell tower's range. I used this all the time with my old phone and it helped a lot to save battery. But it didn't seem to work for some reason. So I turned Macrodroid off and it did help with my data issues then I even uninstalled it completely.
So bottom line, it's working now, but like I said in my original post, it was working for about 24 hours then I started having issues.

tjlmbklr said:
Straight Talk.
Pure Nexus ROM
Click to expand...
Click to collapse
Straight Talk is not a carrier. They are reseller of services provided by Big Four.

Witek_M said:
Straight Talk is not a carrier. They are reseller of services provided by Big Four.
Click to expand...
Click to collapse
I think all know this detail by now. The APN however is unique straight talk even though it is technically AT&T or (T-mobile)

I can't believe this is still an issue, totally unacceptable IMO

I've had this twice today. 100% stock, no root. Latest T-Mobile 5.1.1 with T-Mobile service. I'll take my phone out of my pocket and have a "!" next to the signal bar.
This even happens when in use. I had Spotify streaming music in my car when it cut out. When I got home, I checked the phone and again, "!" next to the signal bar.
I just did a clean flash and factory reset yesterday and set the phone up as a new device (no apps auto downloaded from previous setup) and I'm still getting this error whenever I leave the phone to sleep too long.

Same here !
Bought a N6 as my first Google phone, I thought I'd get the benefits of an always up to date phone, but instead I have to deal with that kind of issue
Hopefully that's a software issue and Google will provide us with a fix quickly... that's why I bought a Nexus !
(Orange 4G - France)

I had the same thing happen to me today. I left my phone in the car to go to a meeting, went to check it had no signal. Just turned on airplane mode for a few seconds then off, everything came back. I'm using the phone on ATT GoPhone network. I'm also using the nextgenphone apn instead of the phone apn. Maybe that's causing it.
Sent from my Nexus 6 using Tapatalk