Related
Latest problem; it seems my phone isn't reading the simcard. I was having issues with bootlooping after installing safestrap but now I have no service but wifi. I repeatedly tried adding my APN info manually and tried APN manager. No luck. I tried to enable "simlock" and that is when i realized it wasn't reading the simcard. Card works fine in my Backflip and my g/f's month old simcard doesn't work in my phone.
A few weeks ago when I was out in the sticks, I had sketchy service but still usually a bar. Once in a while I would get "emergency service" only, I thought that was strange because I had a bar or two but got this status. Perhaps this was an early stage of the problem..
Anyone have their phone stop reading cards? I am thinking about sending it back for warranty service.
BTW, any suggestions on what to wipe before sending it back for service? I was going to remove root and get rid of safestrap.
Thanks again smart people.
A full SBF should remove everything and make it good as new and ready to be returned (I think..) If you need instructions on how to SBF your Droid 3, they are located... here! http://forum.xda-developers.com/showthread.php?t=1255198
Try your SIM cards after SBFing to see if it was perhaps faulty hardware...
(An SBF is basically a factory restore on steroids, kills and restores EVERYTHING including the system if i remember correctly!)
Thanks eh, unfortunately I am running the Canadian xt860 and I haven't found a Bell SBF file. There are some from other markets.
Oh, that's a curious issue than, are you still going to return the device?
(Try reflashing safestrap?)
Ya, I am going to send it in for service. I have spent so much time reading and trying different things with no luck. I have a couple more options but don't feel hopeful. At least all this reading has been a good way to learn things I wouldn't have otherwise.
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.
Hey, thanks for clicking my post. TL;DR Since updating from ARHD 40.3 to Viper One 6.2.0, my radio has been having major intermittent issues. I have a HTC One m7_ul unlocked outright from Optus here in Australia. It is as of right now running the latest firmware linked to by the Viper One/ARHD threads, the latest TWRP, is S-OFF and superCID, running Viper One 6.2.0.
Symptoms:
1) No signal most of the time.
2) Signal appears to return during periods of movement (e.g. driving).
3) Even at full signal, there is no mobile connection (no data, no text/calling).
4) Once every few hours, when it has signal, it will gain mobile connection for a short period of time, after which it will cut out again - repeat to 1).
Here's a short story about how this came to be:
For many many months now it has been running just fine on stock firmware, rooted with S-ON running ARHD 40.3 (since that version came out).
About a fortnight ago I started noticing issues with my contacts application. Something to do with 501 contact link suggestions and certain contacts having hundreds of Facebook profile entries. This would cause issues in the People app (people just wouldn't load) and the SMS app (message histories wouldn't load, including new texts).
After some troubleshooting attempts, I resolved to reinstall a ROM. I opted to install the latest Viper One (6.2.0) successfully. It resolved my issues. However, it introduced a new one. The next morning I woke up to 4 texts from my service provider informing me I'd missed calls. I had no notifications as such, so the calls never reached my phone. I put it down to tower signal flex in my area. I left and as I walked out the door I noticed I had no signal (no bars, x above the icon in statusbar). Driving around seemed to fix the issue though, it got back up to normal values quickly enough.
However, even though I had plenty of signal and mobile data was ostensibly turned on, I couldn't get internet. I tried sending a text to myself but it failed send. Calls out simply waited on signal and then timed out. Every single other function of the device is 100% AOK (wifi, bluetooth, nfc, etc). The entire ROM is fully functional, can't find any other issues with stability or otherwise.
I put up with it for the day and get home and start troubleshooting. Here's what I tried so far, in order:
1) Change from Viper One to latest ARHD (71.1). Installed with no issues. Booted phone, no dice - no signal.
2) Checked SIM by moving to old iPhone 4 - full signal, radios work. It's not a service issue.
3) Revert to last known working ROM - ARHD (40.3). Installed with no issues. Booted phone, no dice - no signal.
4) Research research research. Think it might be a problem with firmware perhaps. Tried revone, failed because I'm not on 4.2.
5) Flash MaximusHD (11.0.0) in order to make use of revone for S-OFF/superCID. Flashed latest firmware linked in Viper One/ARHD threads.
6) Reboot phone. Still no dice with latest firmware on MaximusHD (11.0.0).
7) Retry with latest ARHD. No dice.
8) Retry with latest Viper One. No dice.
In every single instance, all the ROMs are fully functional except for mobile signal - wifi, bluetooth, nfc, etc. radios function perfectly. No issues with ADB or fastboot during any step of these processes. All my device info shows what I expect to see. I've searched as much as I can, to no avail. I turn to first-time posting here as a last resort to maybe find out what the issue is.
I am slowly reaching the thought that the hardware itself might be the issue. I'd appreciate any insight into what could be causing this - be it software or hardware - as well as if there is any way to test or diagnose the radio physically. Even just a confirmation ("Yep, sounds like your radio's FUBAR"). In the meantime, I'll be using aforementioned iPhone 4 (ugh).
Thanks for reading.
Have you attempted to flash a different radio baseband?
Look up the radio version used in ARHD 41. If you find it, search for the radio within the forums and flash it. You can still keep the most current version of your preferred ROM. Search the threads for how to flash a radio baseband, there are plenty of them.
digitalism said:
Have you attempted to flash a different radio baseband?
Look up the radio version used in ARHD 41. If you find it, search for the radio within the forums and flash it. You can still keep the most current version of your preferred ROM. Search the threads for how to flash a radio baseband, there are plenty of them.
Click to expand...
Click to collapse
I found a forum for HTC One radios here, it's in the AT&T section but apparently work on all HTC Ones. I was unable to find out which radio ARHD 41 used, my understanding is that custom ROMs don't usually come with a radio baseband of their own and they don't appear to list any on their thread that I could see. I would inquire but I think there's an issue with new users posting in development sections. Do you think it's worth trying to look further into what radio was used, or should I start flashing radios from the aforementioned list? There's a couple that stand out as possible candidates (the earliest version, the newest version, etc) but I'm not sure I want to just start going crazy on that list until something works. Or do I?
edit: To clarify, and they say explicitly in the ARHD post FAQ, they do not include radio/hboot/firmware in their ROM. So I must assume that I was simply on the stock radio the device shipped with.
edit 2: Confirmed my current baseband matches one of the ones indicated as installed from firmware package. I'm not sure what it was before I updated to Viper One or even while I was using Viper One.
Flashed the earliest radio baseband available from the aforementioned thread. Put the SIM back in, signal achieved, able to send texts/make calls/USSD codes. I was unable to get it to transfer mobile data, however.
Can't believe I didn't think about radio baseband. Didn't even know that was a thing. I just thought it was part of the firmware package. There you go I guess. Thanks again for the tip.
Whitestrake said:
Thanks again for the tip.
Click to expand...
Click to collapse
No problem, just remember that if you're having issues with certain partitions on the device, each partition is technically flashable if you are S-Off and SuperCID.
digitalism said:
No problem, just remember that if you're having issues with certain partitions on the device, each partition is technically flashable if you are S-Off and SuperCID.
Click to expand...
Click to collapse
I've tried just about every radio in that forum. They all seemed to have the same issue for me - at first it seems to have no signal, then it gets normal signal, receives/sends any buffered texts, and then fails to work after that for any purpose regardless of signal. I think I'm back at square one; I don't suppose there are any other simple things to try?
Whitestrake said:
I've tried just about every radio in that forum. They all seemed to have the same issue for me - at first it seems to have no signal, then it gets normal signal, receives/sends any buffered texts, and then fails to work after that for any purpose regardless of signal. I think I'm back at square one; I don't suppose there are any other simple things to try?
Click to expand...
Click to collapse
If you are having issues still, the other alternative is to flash a different firmware version than what the ROM provides. Firmware and radios tend to "talk" to each other in certain ways, so maybe your firmware isn't using your radio the way you need it to. Also, make sure you are installing firmware particular to your device. For instance, do not install firmware originally meant for an AT&T phone if you use Verizon or another carrier. They tend to write the code particular to these things. I would do some research through the forums and see if you can find a good combination in your area that people have tried. Maybe even a Google search will help out if the forums seem daunting to dig through.
And don't forget, the iPhone has a Quad-Band receiver that's capable of receiving cellular signals much clearer. The HTC One, in my opinion, does not match hardware compared to the iPhone. The iPhone will always technically be superior, no matter what opinions people hold to both.
First, thanks again for your patience and assistance.
digitalism said:
Also, make sure you are installing firmware particular to your device. For instance, do not install firmware originally meant for an AT&T phone if you use Verizon or another carrier.
Click to expand...
Click to collapse
I was not aware of this restriction. I suspect I may have flashed firmware for a different region. I isolated the Optus firmware RUU numbers and got a firmware package matching, and the android-info.txt matches the device original CID and modelnum. I'll try it soon.
I'm still having trouble understanding, though, how it could have failed in the first place. My phone was S-ON when the radio stopped working; surely changes to firmware/radio couldn't have occurred anyway? None of the ROMs I've touched have firmware or radio included as far as I could tell.
Flashed the firmware appropriate to my region (4.20.980.1). Came with radio. Rebooted, put in SIM, no signal for 5 minutes. When I get signal, texts don't send and calling times out, USSD codes give connection problem errors. Same as before. How likely is it the actual hardware could be damaged? I did drop it on concrete, on the front of the device at the top, around the time this started happening - very shortly before I flashed Viper One to fix the contacts issue. There was no visible damage.
Whitestrake said:
Flashed the firmware appropriate to my region (4.20.980.1). Came with radio. Rebooted, put in SIM, no signal for 5 minutes. When I get signal, texts don't send and calling times out, USSD codes give connection problem errors. Same as before. How likely is it the actual hardware could be damaged? I did drop it on concrete, on the front of the device at the top, around the time this started happening - very shortly before I flashed Viper One to fix the contacts issue. There was no visible damage.
Click to expand...
Click to collapse
Quick question:
Are you installing your firmware and software without the SIM card in? If so, I would leave the SIM card in and have all the software installed during the process. Damage to the phone should not cause problems for connecting to the cellular network. Have you tried leaving the house, going outside, or getting into a different area to try your signal? Maybe your house is a deadzone and the phone is having a hard time picking it up. My room gets like this since I live in Florida where houses are built with cinder blocks to prevent hurricane damage. It really messes with my signal.
digitalism said:
Quick question:
Are you installing your firmware and software without the SIM card in? If so, I would leave the SIM card in and have all the software installed during the process. Damage to the phone should not cause problems for connecting to the cellular network. Have you tried leaving the house, going outside, or getting into a different area to try your signal? Maybe your house is a deadzone and the phone is having a hard time picking it up. My room gets like this since I live in Florida where houses are built with cinder blocks to prevent hurricane damage. It really messes with my signal.
Click to expand...
Click to collapse
Good ideas, but unfortunately not - every firmware and radio package I've flashed, I've done once with the SIM, once without, thinking along a similar line.
I'm in a known good cell location - coverage in my area is fantastic with my provider (Telstra, usually get 5 bar signal on 3G - I do not get LTE on my plan). I test in multiple places - next to my PC, outside the house, down the street, etc. The behaviour I've noticed is that I have no signal regardless of where I go, for about 5 minutes after booting the phone, after which it gets signal, sends/receives any buffered texts, and then fails to communicate successfully after that (i.e., I get the test text I sent myself, then I resend another test, and it fails to send). The iPhone 4 I've been moving my SIM to has been receiving full signal (as expected) at every place I've been testing the HTC One.
Hmm...
You might have to go into your APN settings to change some things in order to get it to work properly. Go to your Settings, then Mobile Data, then Access Point Names. From this menu click the current APN saved with the phone. After that, it will have you insert some information. Check this website for the specific APN information for your carrier. Make sure it's for your carrier as there is a large list of different ones on there.
http://ausdroid.net/apns/
Other than that, I honestly couldn't tell you what your issue is.
digitalism said:
Other than that, I honestly couldn't tell you what your issue is.
Click to expand...
Click to collapse
Tried the APN thing. There was indeed a few things different from the listed settings, but honestly, they were pre-populated with a bunch of Telstra data beforehand when the SIM was in. I made the changes and noticed no difference.
Thanks again for your help. As a last step I will return it fully to stock. After that I suspect my only recourse would be taking it back to Optus and asking if they'll quote me to fix it.
Unfortunately it does seem to be hardware issue from the history of what you have tried and posted.
Use nkk71's guide listed in my signature to go back to stock for warranty but substitute your local RUU/nandroid/etc.
SaHiLzZ said:
Unfortunately it does seem to be hardware issue from the history of what you have tried and posted.
Use nkk71's guide listed in my signature to go back to stock for warranty but substitute your local RUU/nandroid/etc.
Click to expand...
Click to collapse
Thanks for the link, that's actually one HTC One return-to-stock guide I haven't seen yet and it looks very concise. Cheers.
Whitestrake said:
Tried the APN thing. There was indeed a few things different from the listed settings, but honestly, they were pre-populated with a bunch of Telstra data beforehand when the SIM was in. I made the changes and noticed no difference.
Thanks again for your help. As a last step I will return it fully to stock. After that I suspect my only recourse would be taking it back to Optus and asking if they'll quote me to fix it.
Click to expand...
Click to collapse
Sorry about that, I know having a custom ROM is a lot of fun, but there can definitely be some cons along with it.
Good luck with your phone!
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
rmx36 said:
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
Click to expand...
Click to collapse
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first. EDIT: NOPE! Flashing the stock kernel from the ROM did not do it. Looks like total reformat/flash is next!
markwebb said:
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first.
Click to expand...
Click to collapse
I just got my Nexus 6 and I am also on Verizon and had the cell coverage drop too. I backed up my apps with titanium backup and did a factory reset and signal came back. I only had it for a day and went to Canada and on my way back to the US I noticed the cell bars were gone. I was just rooted and boot loader unlocked and otherwise stock. I read online that others had this issue when they got to places in the US that had little or no signal. I also noticed that under cellular network settings it loads up with Global under the preferred network type even though it has an option for "LTE (recommended)" and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected. With global selected it works perfectly with calls and LTE, so not sure what that means or if my selecting LTE made it drop the signal after going back from Canada.
Yep, total flash of factory image fixed it. Sigh. Early enough in the day for me to get everything set up again.
Same. About to do it too... I've done too many factory resets with this already. Kind of annoying.
I am in the same boat. Had no problems until I flashed bliss 1.5 then was stuck on 3g. Tried a clean flash of Slim and still stuck on 3g. I will try a stock rom but I am not very hopeful at this point. It's looking a like a reformat here as well :/
Ended up having to format everything and start from scratch again. I'm running a stock ROM now and in weary to try another cm ROM
Don't know if it'll help, but try LTE Discovery app in the Play Store. I use it from time to time to reset my data connection.
Having the same issue, running CM12 daily, have been for a week or so. Midday today it drops LTE, 3g data was working, then a few minutes later to no data. I didn't change anything, nothing new installed. I did reboot the phone at some point before this but that is all...
My only fix was to backup via trwp, restore stock rom, factory reset, reboot & let sim activate, then restore cm12 via twrp... it's a 20-30 min fix all said and done.... pita
Maybe its something Verizon is doing, because I didn't change anything and then next thing you know no data. I hope it's a simple fix for CM12 but I see this popping up more the last few days. Hopefully someone will figure it out. I like CM and prefer it over stock but I am not going to do this multiple times a day just to keep CM...
lohonda said:
...and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected.
Click to expand...
Click to collapse
I just checked and global is still an option for me. I've bounced back and forth, looking to see if anything changes..
Same thing has happened to me last night, lost connection to VZW cell and data. Looking at the field test menus, it seems like the SIM/device understand GSM but NOT CDMA anymore. So I believe the issue has something to do with that. Tried everything, but will nuke and repave most likely....also lost Global as well. and LTE Discovery shows GSM stuff nothing for CDMA
Tried the SIM in another device and it works so its not the SIM.
OK I tried a world of things to recover like some of you may have....its something in Userdata because if I flash everything but userdata it wont work. I am going to try and recover from the backup I had before this happened to see if that works....otherwise rebuild from scratch
will post back
UPDATE: So restoring a backup seems to be ok once you get the SIM back.
Having the same issue over here as well... After a month or AI of having the 6, now I randomly drop service where I would normally have full LTE. I almost NEVER get LTE now and am at most on H with a couple bars then it drops out again. Have also.noticed WiFi connection is very shakey.
Any one find a fix?
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
th3g0d said:
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
Click to expand...
Click to collapse
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
quidpro said:
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
Click to expand...
Click to collapse
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Edit: OK, just pinpointed MY issue. I have to wait for the "no service" text to change into "emergency calls only" before entering my pin or I don't have any service just the exclamation mark :/
th3g0d said:
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Click to expand...
Click to collapse
Thanks. I told her about it and she will give it a try, or just remove the pin altogether as a test. It is a weird issue. She is missing important calls from her elderly parents at night and it is rather frustrating. Turning wifi off also seems like a bad fix.
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.