Related
My 3 month old galaxy nexus lost the ability to connect to the cell network, wifi and bluetooth are fine but when i scan for an apn it errors out, and i can not add an apn manually. i followed the thread to bring the phone back to factory defaults and re locked it like it was going back for warranty and that did not help, so it has the factory radio, bootloader, recovery and os 4.0.2 on it now.
do i have a $600 paper weight now? has anyone ever heard of this happening?
More than likely a SIM error if you've restored to stock and it still happens. Do you have another device or SIM to swap and test?
the sim is now in my blackberry torch that i have as a back up phone and working, even with out a sim in it there is no notice on the screen that says please insert sim card, but i am not sure if thats normal or not.
looking at the *#*#4636#*#* screen the radio keeps going from emergency calls only to radio off and back again.
edit: it does say no sim inserted, but its only on the lock screen so i missed it.
so looks like i am screwed with this phone, the store i bought it off the guy is freaking out saying why did you root it, (he keeps calling it jailbreaking) why didn't you just leave it alone, my response is why did you put those rims on your car, why did you change your desktop wallpaper, what can i say, i love AOKP rom.
but this is a hardware related problem, i put the stock radio and everything back to stock so what else could it be but hardware?
has no one ever heard of this problem with a gsm galaxy nexus?
The only time I saw this issue someone flashed the AOKP tablet rom.
El Daddy said:
The only time I saw this issue someone flashed the AOKP tablet rom.
Click to expand...
Click to collapse
i had been using the aokp rom for a few days before this started, and i just checked that is was the gsm nexus rom.
what fixed it on the one you heard about?
grinmaul said:
My 3 month old galaxy nexus lost the ability to connect to the cell network, wifi and bluetooth are fine but when i scan for an apn it errors out, and i can not add an apn manually. i followed the thread to bring the phone back to factory defaults and re locked it like it was going back for warranty and that did not help, so it has the factory radio, bootloader, recovery and os 4.0.2 on it now.
do i have a $600 paper weight now? has anyone ever heard of this happening?
Click to expand...
Click to collapse
You are not the only one buddy. I am just south of Chicago and mine hasn't worked for over a week. I have full signal bars, but 7/8 of the time it reads that I'm not connected to the mobile network (as in my signal bars hardly ever turn blue). Even if it looks as if I have a connection EVERYTHING just times out. I haven't had the nerve to send it back to Singapore for a repair. The only reason I even own this phone is due to my drug abusing postal carrier inputting they delivered my GS2 and then simply didn't. Without signature verification its just a he said/ she said.
Hi everyone, I received the Galaxy Nexus last night from Google Play. Out of the box, I was able to connect to the network (make calls, send texts, etc.). I was charging my phone at night and then I realized that I was no longer connected to the T-Mobile network. The triangle is empty now and I can't do anything on the network anymore. I ran the Jelly Bean 4.1 OS upgrade as soon as we took the phone out of the box. I checked the APN settings and I noticed that it was completely blank but I was unable to successfully add a new one. I can try to create a new one and input all the settings but it doesn't seem like it was saved.
I just took it up with T-Mobile and told them to update my line to this phone, and they assured me that it would work in 2 hours, but I won't be holding my breath. At the same time, I contacted Google and they unfortunately said that they cannot do anything in this case and I would have to take it up with Samsung... I don't really want to do that and I hope that I don't have a faulty device..
Also, I never rooted it and everything is completely stock.
ANY HELP??
No internet connection gsm galaxy nexus
mapheg2 said:
hi everyone, i received the galaxy nexus last night from google play. Out of the box, i was able to connect to the network (make calls, send texts, etc.). I was charging my phone at night and then i realized that i was no longer connected to the t-mobile network. The triangle is empty now and i can't do anything on the network anymore. I ran the jelly bean 4.1 os upgrade as soon as we took the phone out of the box. I checked the apn settings and i noticed that it was completely blank but i was unable to successfully add a new one. I can try to create a new one and input all the settings but it doesn't seem like it was saved.
I just took it up with t-mobile and told them to update my line to this phone, and they assured me that it would work in 2 hours, but i won't be holding my breath. At the same time, i contacted google and they unfortunately said that they cannot do anything in this case and i would have to take it up with samsung... I don't really want to do that and i hope that i don't have a faulty device..
Also, i never rooted it and everything is completely stock.
Any help??
Click to expand...
Click to collapse
hi,
im in the exact same situation phone is perfect on stock rom and all but has an empty triangle with no internet connection being displayed on the notifications bar, i need my phone to work and would love to figure this out please someone help would greatly apprecitae it.
I have the same issue on my international one. It has been decided it has a hardware failure. I have no warranty though. I might buy one with a broken screen and swap. You have a warranty use it.
Sent from my Galaxy Nexus using xda premium
Same issue here. I had the phone for months (stock ROMs) and was perfectly happy. Few days back, connection dropped at random and the only way to fix it was through a reboot. Then, after 2 or 3 days, no connection whatsoever, it doesn't even "find" the sim card, so it seems as it's no longer asking for my sim pin code.
Tried about everything, even wiping and reflashing every stock ROM and radio I could get my hands on (including 4.2.1, 4.1.2 and 4.0.4), to no avail. I'm about to give up and return it to Samsung for repair. We're not the only ones, that for sure...
Let me start off first by saying that I am S-Off through Sunshine.
I have an AT&T branded HTC One M8, which I recently converted the the Developer's Edition M8 by changing the CID and flashing the DE Recovery and Nandroid Backup.
I did this for two reasons: Tired of waiting on AT&T to release updates (Was still on 4.4.2 when I converted), and to get rid of bloatware while also having the ability to get OTAs.
Now my issue at the moment, which seemed to arise(although cant say for sure it was because of this) when I updated to DE 4.4.4. As far as I can tell right now, two apps - Snapchat, and Google Play, will not connect or send or receive data when LTE is active. Chrome, Instagram and a few other apps have no problem loading and sending and receiving data. If I go into Mobile Data settings, and switch from "GSM/WCDMA/LTE auto" to "GSM/WCMDA auto" everything will work fine. So the problem is solely with LTE. If any other information needs to be provided to troubleshoot feel free to ask.
Also, this happens with full bars, and with the LTE up and down arrows lighting up.
If you figure this out please let me know. I am experiencing the same issue. I called At&t and they were at a loss too. My browser works fine. My reddit app, my bank's app, and just about everything else doesn't work at all. And, the issue is only on LTE. So, we have the exact same problem. I really would appreciate help on this. I use my phone to find houses on emergency calls. If I don't have internet it makes it difficult.
The crazy part is the LTE works. I just doesn't work with apps.
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
I'm wondering if after doing the RUU my radio or something isn't at a proper level. Attached is a screenshot of my current bootloader. Anyone see something out of the ordinary that needs updating?
Yeah, I would go ahead and check with ATT if there are any bars on your account. Sounds like more of a network issue than a phone issue.
downbringer said:
Yeah, I would go ahead and check with ATT if there are any bars on your account. Sounds like more of a network issue than a phone issue.
Click to expand...
Click to collapse
Thanks for the reply! What would lead you to believe it's a network issue? I can make calls just fine and if I'm on the phone and someone calls me it works as if it normally would. Only issue is when someone calls me and I'm NOT on the phone.
Try turning off LTE, and see if you can get calls.
Some folks have been having issues with "international" based Sense ROMs not playing well with AT&T's LTE network upgrades (in preparation for Voice Over LTE). Not sure if this affects AOSP ROMs, but I have a feeling this is the problem.
redpoint73 said:
Try turning off LTE, and see if you can get calls.
Some folks have been having issues with "international" based Sense ROMs not playing well with AT&T's LTE network upgrades (in preparation for Voice Over LTE). Not sure if this affects AOSP ROMs, but I have a feeling this is the problem.
Click to expand...
Click to collapse
Wow......You, you're good you lol. @redpoint73
Sooooo yeah, changing my mobile data to 3G all of a sudden allows calls to come through. What exactly is at play here and how do I fix it?
italynstylion said:
What exactly is at play here and how do I fix it?
Click to expand...
Click to collapse
As I already described, AT&T is upgrading their LTE network for Voice Over LTE (they call it "HD Voice") and something in that upgrade doesn't seem to be playing well for some people on international based custom ROMs. In addition to voice call problems, you will probably also find SMS messages won't work on LTE.
Curiously, the problem seems to be very location specific. I've been running Skydragon Sense and LeeDroid for a few months, and on AT&T network. And everything has been working fine for me at my home location, as well as a few other locations around the country (I travel pretty occasionally for work). These are some of the ROM that others have had AT&T LTE issues with; and at one point even in the same city as another user that was suffering this issue (Chicago area). But for me, everything seemed to work fine.
The only real fix is to go back to stock AT&T based ROM. Folks have tried to flash various radios, and other things with no luck. Team Venom (Viper ROM) also said they would look into it a few months ago; but I don't think anything ever came of that.
An ingenious workaround posted by another user (if you want to stay on an international ROM): call AT&T and ask them to turn off HD Voice for your account. So you can still use LTE for data, but the call bug won't occur.
Of course, the downside for this is that you won't be able to utilize HD Voice. But that is probably the lesser of evils, if you want to stay on the current ROM.
redpoint73 said:
As I already described, AT&T is upgrading their LTE network for Voice Over LTE (they call it "HD Voice") and something in that upgrade doesn't seem to be playing well for some people on international based custom ROMs.
The only real fix is to go back to stock AT&T based ROM. Folks have tried to flash various radios, and other things with no luck.
An ingenious workaround posted by another user (if you want to stay on an international ROM): call AT&T and ask them to turn off HD Voice for your account. So you can still use LTE for data, but the call bug won't occur.
Of course, the downside for this is that you won't be able to utilize HD Voice. But that is probably the lesser of evils, if you want to stay on the current ROM.
Click to expand...
Click to collapse
This is brilliant. I'll give it a shot. Thanks for your help!
italynstylion said:
This is brilliant. I'll give it a shot. Thanks for your help!
Click to expand...
Click to collapse
I agree, its a good workaround. Especially since HD Voice requires users on both ends of the call to have a phone that supports the feature; and few phones for the time being have it. So having HD Voice turned off on your account (even if its deployed in your area) is probably mostly irrelevant.
You're quite welcome. And if you have a chance, please click the "Thanks" button for any posts you found helpful!
redpoint73 said:
I agree, its a good workaround. Especially since HD Voice requires users on both ends of the call to have a phone that supports the feature; and few phones for the time being have it. So having HD Voice turned off on your account (even if its deployed in your area) is probably mostly irrelevant.
You're quite welcome. And if you have a chance, please click the "Thanks" button for any posts you found helpful!
Click to expand...
Click to collapse
Just got off the phone with AT&T and everything is just peachy again. I updated the first post with the solution/fix. Thanks so much for your help!
italynstylion said:
Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues.
Click to expand...
Click to collapse
Interesting. I wonder if HD Voice hasn't been activated on my account yet; and that is why I haven't had this issue while others have?
redpoint73 said:
Interesting. I wonder if HD Voice hasn't been activated on my account yet; and that is why I haven't had this issue while others have?
Click to expand...
Click to collapse
It's certainly possible. I live in Dallas which is a fairly large area. It wouldn't surprise me if we were one of the areas that got it first. Sucks being a guinea pig but I've left a trail of breadcrumbs for everyone else to follow.
italynstylion said:
It's certainly possible. I live in Dallas which is a fairly large area. It wouldn't surprise me if we were one of the areas that got it first. Sucks being a guinea pig but I've left a trail of breadcrumbs for everyone else to follow.
Click to expand...
Click to collapse
I'm in Boston area, and according to the AT&T maps, HD Voice is working here.
Although, I got the M8 long before it supported the feature (they added it with the 4.4.4 OTA). So I don't know how they decide when to activate it on your account; but if its device related, I can see how it might not be on mine yet.
italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
Thanks for the post this helped me with my issue!!!
Have any of you tried to disable enhanced 4G LTE Mode in network settings instead of slowing you down to 3g?
goo.gl/photos/BX9N2b37Z2Wb1UeQA
[/QUOTE]
italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
phgojiya said:
Have any of you tried to disable enhanced 4G LTE Mode in network settings instead of slowing you down to 3g?
goo.gl/photos/BX9N2b37Z2Wb1UeQA
Click to expand...
Click to collapse
[/QUOTE]
What ROM are you on? I dont have that option to turn off enhanced LTE on my network settings page
grafik2 said:
What ROM are you on? I dont have that option to turn off enhanced LTE on my network settings page
Click to expand...
Click to collapse
If you are on AT&T and suffering this problem, my advice would be to call AT&T and ask them to turn off HD Voice on your account. The enhanced LTE setting on the phone does nothing to help this problem.
redpoint73 said:
If you are on AT&T and suffering this problem, my advice would be to call AT&T and ask them to turn off HD Voice on your account. The enhanced LTE setting on the phone does nothing to help this problem.
Click to expand...
Click to collapse
Gotcha.
i had this happen to me once months ago maybe even a year ago and i called and they turned HD voice off and it worked. it started happening again last week I wonder if ATT reapplied the HD voice setting for some reason
italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
Thank you so much! I've been looking everywhere for a solution after I installed the Resurrection Remix Rom 5.7.4 on a replacement HTC M8 that I bought new. Love these now 3+ year old phones but not recieving phone calls was crazy. I thought I would be forced to go back to stock.
Hi everyone,
I have a Sprint HTC 10 that I've sim unlocked. I'm running Mint Sim (a T-Mobile MVNO). This has been working perfectly for 2 months now. Yesterday I was told several times that my phone sent incoming calls directly to voicemail. I tried calling myself with my work phone and it goes to voicemail right after the first ring. I popped out my sim and put it in my Nexus 4 which rang immediately with an incoming call.
I tried several roms, PureFusion, Lineage, and Viper, same with all of them. I'm able to receive texts, send texts and mms, and make calls, but incoming calls go to voicemail. I just ran a RUU to the latest image for the Sprint device. Does anyone have any suggestions as to why this may be happening and what I can do to fix it?
I'm currently S-On, so no ability to downgrade firmware.
thunder2132 said:
Hi everyone,
I have a Sprint HTC 10 that I've sim unlocked. I'm running Mint Sim (a T-Mobile MVNO). This has been working perfectly for 2 months now. Yesterday I was told several times that my phone sent incoming calls directly to voicemail. I tried calling myself with my work phone and it goes to voicemail right after the first ring. I popped out my sim and put it in my Nexus 4 which rang immediately with an incoming call.
I tried several roms, PureFusion, Lineage, and Viper, same with all of them. I'm able to receive texts, send texts and mms, and make calls, but incoming calls go to voicemail. I just ran a RUU to the latest image for the Sprint device. Does anyone have any suggestions as to why this may be happening and what I can do to fix it?
I'm currently S-On, so no ability to downgrade firmware.
Click to expand...
Click to collapse
Since you say the sim worked on a nexus 4, the problem is definitely within your sprint phone. Just from a bit of googling it seems CID or some form of editing your radio would have been necesary to make it work. Idk what the problem is but the radio settings is where you want to look.
drago10029 said:
Since you say the sim worked on a nexus 4, the problem is definitely within your sprint phone. Just from a bit of googling it seems CID or some form of editing your radio would have been necesary to make it work. Idk what the problem is but the radio settings is where you want to look.
Click to expand...
Click to collapse
That was my first thought, but it didn't make sense that I'd lose my ability to receive calls after 2 months of it working well. I went S-off, downgraded, reran the latest ruu, wiped modemst1 and 2, re-unlocked the Sim, and still having the issue.
I then tried the sim in two more phones, both gsm unlocked, and had the same problem in them. I tried it again in the Nexus 4 and could make and receive calls, but no data anymore. Trying an AT&T sim in my phone I could receive calls just fine.
I pressured Mint and they're going to send me a replacement sim for free, so hopefully that'll fix the issue.
thunder2132 said:
That was my first thought, but it didn't make sense that I'd lose my ability to receive calls after 2 months of it working well. I went S-off, downgraded, reran the latest ruu, wiped modemst1 and 2, re-unlocked the Sim, and still having the issue.
I then tried the sim in two more phones, both gsm unlocked, and had the same problem in them. I tried it again in the Nexus 4 and could make and receive calls, but no data anymore. Trying an AT&T sim in my phone I could receive calls just fine.
I pressured Mint and they're going to send me a replacement sim for free, so hopefully that'll fix the issue.
Click to expand...
Click to collapse
nice! i've had bad or outdated sims before lol didn't think that was much of an issue anymore, but no that you say that I'm sure it'll fix it. last thing i would've said if APN changed but sounds like that might not be it either.
drago10029 said:
nice! i've had bad or outdated sims before lol didn't think that was much of an issue anymore, but no that you say that I'm sure it'll fix it. last thing i would've said if APN changed but sounds like that might not be it either.
Click to expand...
Click to collapse
Weirder still, I went into town today (I live in the boonies but get 3-4 bars, LTE data, and I max out the Mint throttle) and my phone rang. Now that I'm back home it's working again. Maybe the tower just didn't like me and now that I've checked in on another one it'll work.
Edit
And now 20 minutes later it's going directly to voicemail again.