Related
I had a unique problem that is now solved and I wanted to share my experience in case anyone else can benefit from it. I was unable to access any Google services over 3G cellular internet, but over WiFi it worked just fine.
I was also able to browse the web over cellular. My EVO is NAND unlocked and been running Fresh's ROM and also CyanogenMod.
Since I first noticed this with Android Market I tried clearing data for it and that didn't work. I also noticed Google Voice couldn't send/receive messages, so tried that as well and could not reinstall as AM wasn't working.
I restored a backup I had made days earlier and had the same results. I tried clearing cache/dalvik cache/etc. still no joy. I tried installing fresh after clearing data/cache/etc. etc. and it still did not change anything.
Finally I called Sprint and they instructed me to do the following:
Enter ##3282## into the phone keypad, select Edit.
Enter a password the tech gave me.
Go to Data -> Press Menu -> Press "Restore". Allow the phone to reboot.
It will go through a lot of different things -- ie: PRL update, firmware update, resetting your "profile" (in settings/update), etc.
It did not work after all of these things so he said he would reset all the "stuff on their end" and after he was finished it worked. I asked and he assured me it had nothing to do with any configuration on my phone. When I asked him to describe what it was he did to fix it, he said he "switched the provider/internet signature" which is on their end. This finally resolved the issue.
So, if you have these same exact symptoms -- you may benefit calling Sprint FIRST before wasting your time trying all those things that I did.
The problem that I am having is GTalk will hang at trying to connect for a very lengthy time. It works over WiFi just fine but over 3G or 4G it's sporadic. And when GTalk isn't connecting the market won't be able to complete a download either.
If it persists I'll give Sprint a call.
mytouchglast said:
The problem that I am having is GTalk will hang at trying to connect for a very lengthy time. It works over WiFi just fine but over 3G or 4G it's sporadic. And when GTalk isn't connecting the market won't be able to complete a download either.
If it persists I'll give Sprint a call.
Click to expand...
Click to collapse
Well... you can certainly try and troubleshoot via your phone. Steps I tried with mine:
- Restarting the phone (lol)
- Clearing specific app data (settings -> applications)
- Reinstalling apps (couldn't do this because related to Market and did not have APKs)
- Clearing Dalvik cache/cache
- Clearing app data
- Restoring a previous backup
- Wiping and reinstalling the ROM
- Trying a different ROM or ROM version
I'm sure there's another one or two but a Sprint call doesn't typically cause you to lose any data on your phone. Hope you get your issue resolved.
I've been having this issue sporadically ever since I switched from the Hero to the Evo about two weeks ago, and it's very frustrating! After trying to sign in to google talk (or cancelling and redownloading an app download) 10-20 times... it usually starts to work. Connecting to a wifi network always resolves the issue immediately.
I called sprint, and after trying most of the steps you have posted, the best they could do is ask me to call google at 650-253-0000, which I will try later.
I mentioned the "switch the provider/internet signature" idea to the initial rep that I spoke to as well as the "escalation rep" I was transferred to, and they had no idea what I was talking about
aikeru , have you experienced the problem again since Sprint's "fix" was applied?
xellus said:
I've been having this issue sporadically ever since I switched from the Hero to the Evo about two weeks ago, and it's very frustrating! After trying to sign in to google talk (or cancelling and redownloading an app download) 10-20 times... it usually starts to work. Connecting to a wifi network always resolves the issue immediately.
I called sprint, and after trying most of the steps you have posted, the best they could do is ask me to call google at 650-253-0000, which I will try later.
I mentioned the "switch the provider/internet signature" idea to the initial rep that I spoke to as well as the "escalation rep" I was transferred to, and they had no idea what I was talking about
aikeru , have you experienced the problem again since Sprint's "fix" was applied?
Click to expand...
Click to collapse
Hmmmm... I haven't experienced the problem anymore. That does sound frustrating. I got the rep to clarify more than once that it was a fix on their end and not on my phone. It's odd, but it's specifically Google services that I had problems with (ie: market, voice, talk, etc.) and not internet and they worked fine over WiFi.
You may just have to keep trying with someone else who is a little "smarter" or follow through the script until they get to that point. I wish I knew more technical details but that is all I recall them saying, really.
I'm having the exact same issue as the first poster. I can't connect to Google services when using 3g. WiFi and 4g works fine. This started after I did a nandroid restore yesterday. I did another nandroid restore of an older know good backup and it did the same thing. I called Sprint and they said they did a reset on my phone and still the same thing. The tech also said she had another caller just before me with the same issue that they were not able to fix.
I'm am still using the stock HTC Rom (3.29) with it rooted with Unrevoked.
So, from your description I've been having the same very problem. Like a couple of people, I had to call sprint a couple of time until they got me to a "senior" tech support. Until, then, they kept on telling me: go to google, call google, email the app developers.... bs bs bs... So, While on the phone with one of their "senior level tech support" (silly that they will insist for a half an hour on the phone with you before they pass you on to these senior techs... even sillier that there is such a division... if they are techs, they all should be trained to deal with these problems.. but anyway).
So the Senior Tech guy told me that they were aware of the problem, that it was indeed on their end and that they they were working on it....
(the first tech to answer the phone should know something like that as opposed to spending 30 mins of my time (each time I call) with "go to the app developers.... all 20 of them, it's their problem").
So, now, I'm supposed to wait until it's working again. Nothing I can do until they have it fixed on their network.
The apps that are not working for me are Market (on and off), Talk, google voice, news rob, Places Directory, Madison Bus, and a few others that use some kind of google service in part or in full, except google maps.
I'm on an Epic 4G, stock rom, up to date, and rooted. And this problem has persisted for 3 days now, in the Madison, WI area (3G/ no 4G).
Hope this clarifies a bit.
Great Read....
Augie754 said:
I'm having the exact same issue as the first poster. I can't connect to Google services when using 3g. WiFi and 4g works fine. This started after I did a nandroid restore yesterday. I did another nandroid restore of an older know good backup and it did the same thing. I called Sprint and they said they did a reset on my phone and still the same thing. The tech also said she had another caller just before me with the same issue that they were not able to fix.
I'm am still using the stock HTC Rom (3.29) with it rooted with Unrevoked.
Click to expand...
Click to collapse
Sprint had a 3G problem yesterday and today: http://forum.xda-developers.com/showthread.php?t=832866&page=1
I fulfilled my quest to get a data only plan on the Atrix by buying an AT&T mifi and just putting the SIM card in my atrix. This required creating a new APN for isp.cingular, and for about 4 months this worked great with a pure voip setup.
A few days ago something happened. My Atrix seems to be stuck on EDGE. It will no longer connect to HSPA in the same locations that it used to be H+ 24 hours a day.
The basics have been covered: power cycling, airplane mode cycling. No use. The SIM itself seems okay since I tried putting it back in the mifi unit, and it got 3G like normal. That also rules out a tower problem.
Anyone have any ideas? I feel like an ass now since I bought the mifi on contract.
You can call At&t and switch it to a voice plan with an hspa data plan so you can use your atrix.
Kind of admitting defeat though.
Sent from my MB860 using xda premium
Perhaps try flashing a different radio on the atrix. It could be an Incompatibility issue ? Worth a shot I would say
Sent from my MB860 using xda premium
So, I tried flashing different radios. No luck. After that I thought maybe some fresh ROMs might do it some good. No luck on Alien, and then I installed CM7 and noticed something interesting. The "Use only 2g networks" setting is stuck on. I turn it off, go back, and soon as I look again it's on. Is there something special you have to do to save it, or could this be pointing to an underlying problem?
nalorite said:
So, I tried flashing different radios. No luck. After that I thought maybe some fresh ROMs might do it some good. No luck on Alien, and then I installed CM7 and noticed something interesting. The "Use only 2g networks" setting is stuck on. I turn it off, go back, and soon as I look again it's on. Is there something special you have to do to save it, or could this be pointing to an underlying problem?
Click to expand...
Click to collapse
Nothing special is needed to save it. It could be throttling by AT&T do to your imei being that of an Atrix vs a mifi.
Sent from my MB860 using Tapatalk
try another at&t sim on your Atrix
cesierra said:
try another at&t sim on your Atrix
Click to expand...
Click to collapse
I suspect att has caught you with imei check and you should try with other sim card.
but i suspect it may not work.
why not use it with MiFi only?
drpratik said:
I suspect att has caught you with imei check and you should try with other sim card.
but i suspect it may not work.
why not use it with MiFi only?
Click to expand...
Click to collapse
The problem with the mifi is its terrible battery life. It only gets 4 hours in hotspot mode. If it could last as long as my phone, I wouldn't even mind carrying around two devices, but it doesn't.
Anyway, great news. After listening to everyone's suggestions I took the SIM out of my phone and noticed that I was then able to properly disable "Use only 2G networks". So, I ordered a new AT&T SIM online, called and had it activated, and now 3G and H are working properly again. And along the way I fell in love with CyanogenMod.
I expect I'll probably have to repeat this process every few months if they continue to slap down my SIM cards, but I consider it worth it for not having to pay for a voice/text plan. I am still on contract, but to anyone who is considering doing something like me, T-mobile recently started offering a $30 a month plan that gets you 5 GB of data, 100 minutes, and unlimited text, and it's for phones! The only hitch is that it's a month by month thing (no contract) and it's promotional, so who knows when they'll decide to cut it. But personally, I'm hoping it's a sign that carriers are finally moving in the right direction.
nalorite said:
The problem with the mifi is its terrible battery life. It only gets 4 hours in hotspot mode. If it could last as long as my phone, I wouldn't even mind carrying around two devices, but it doesn't.
Anyway, great news. After listening to everyone's suggestions I took the SIM out of my phone and noticed that I was then able to properly disable "Use only 2G networks". So, I ordered a new AT&T SIM online, called and had it activated, and now 3G and H are working properly again. And along the way I fell in love with CyanogenMod.
I expect I'll probably have to repeat this process every few months if they continue to slap down my SIM cards, but I consider it worth it for not having to pay for a voice/text plan. I am still on contract, but to anyone who is considering doing something like me, T-mobile recently started offering a $30 a month plan that gets you 5 GB of data, 100 minutes, and unlimited text, and it's for phones! The only hitch is that it's a month by month thing (no contract) and it's promotional, so who knows when they'll decide to cut it. But personally, I'm hoping it's a sign that carriers are finally moving in the right direction.
Click to expand...
Click to collapse
what do you use for voip?
xxgmon3yxx said:
what do you use for voip?
Click to expand...
Click to collapse
I setup a google voice enabled PBX with pbxes.org, back when they let you make them for free. I know for a while they stopped doing that; not sure what the current policy is.
Basically the pbx pretends to be a google talk client, so when someone calls my google voice number it goes to the pbx. Then I have an extension on the pbx that I register on my phone with the native android SIP client, which on CM7 works like a dream. Seriously far smoother and more reliable than sipdroid or csipsimple.
Oh and this does work for outgoing too, but if you're using a solution that doesn't (like google voice -> sipgate/ipkall -> pbxes.org), you can get around it with an app called Google Voice Callback. And it's still all free.
nalorite said:
I setup a google voice enabled PBX with pbxes.org, back when they let you make them for free. I know for a while they stopped doing that; not sure what the current policy is.
Basically the pbx pretends to be a google talk client, so when someone calls my google voice number it goes to the pbx. Then I have an extension on the pbx that I register on my phone with the native android SIP client, which on CM7 works like a dream. Seriously far smoother and more reliable than sipdroid or csipsimple.
Oh and this does work for outgoing too, but if you're using a solution that doesn't (like google voice -> sipgate/ipkall -> pbxes.org), you can get around it with an app called Google Voice Callback. And it's still all free.
Click to expand...
Click to collapse
What is the native android SIP client? May I know the app?
Sent from my MB860 using Tapatalk
anupash said:
What is the native android SIP client? May I know the app?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
In 2.3 they added SIP calling to the android OS. It's not an app. Of course, in stock android it only works on wifi. Cyanogen unlocks its true potential by letting you use it on cellular too.
In my experience, on stock ROM SIP is an epic fail, both native and via apps (tried acrobits, sipdroid, csipsimple, sipagent). There is something funny about moto's audio routing stack, its not a network or settings issue.
Same settings and SIP providers - yes I tried two lol - , same apps, same network i.e. home Wifi, 100% perfect with nexus one. So I'm sure its Atrix specific. This happened on both stock 2.2 and 2.3 AT&T.
Custom ROM fixes this, CM7 native SIP works perfectly.
Can't remember for other ROMs, but they seemed to get apps working if not native SIP.
YMMV
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
im betting that is what my issue is, can you give me the settings so I can make this apn?
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 leak and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
BarryH_GEG said:
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
Click to expand...
Click to collapse
Yes. This is what started me on his quest lol. My s voice has been working and then quit which rendered the watch pointless. So I have been trying to fix it for a few days now
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
raiu said:
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
Click to expand...
Click to collapse
It's an odd problem and not easy to isolate. When S Voice first died I thought it was related to the S Voice app itself. I tried the SGS5 update in your link right before the problem started and thought that was it. So I cleared data in the app via Settings and went back to the factory version and the N3-specific S Voice update that came out a few months ago. Didn't solve the problem - S Voice was fine over Wi-Fi but borked on AT&T data.
I remembered I was in a VoLTE market and tried the nxtgenphone APN and that solved the problem. All three versions of S Voice worked; original, N3 update, and SGS5 update. Everything was fine until I had to use the "phone" APN in a non-VoLTE market. S Voice worked fine until I got home to my VoLTE market and it stopped working again. This time, the nxtgenphone APN didn't help. I cleared data on S Voice again and tried all three versions and S Voice still wouldn't work.
Thinking it might be Gear related I deleted the Gear from BT settings, uninstalled Gear Manager from my phone, hard reset my Gear by long pressing the power button and using recovery, and rebuilding it via reset rather than using "restore" to reinstall my previous apps/settings. For some reason, the original and N3 update of S Voice wouldn't work. The SGS5 version did. At some point in the second "S Voice is broken" repair S Voice started to work on my phone but not the Gear.
So some combination of playing with the APN's, installing different versions of S Voice, and resetting the Gear, S Voice is working reliably again. What a pain in the ass. I'm guessing it's AT&T network related because its the only common denominator in both times S Voice started to fail and using the nxtgenphone APN fixed it the first time.
Same issue here (Samsung Note 3), ATT & Samsung are clueless
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Avi-J said:
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Click to expand...
Click to collapse
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
raiu said:
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
Click to expand...
Click to collapse
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
BarryH_GEG said:
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
Click to expand...
Click to collapse
mine works with the s5 svoice app update
raiu said:
mine works with the s5 svoice app update
Click to expand...
Click to collapse
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
BarryH_GEG said:
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
Click to expand...
Click to collapse
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
raiu said:
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
Click to expand...
Click to collapse
Thanks for that. I saw the security update yesterday but didn't think it would solve the problem so didn't play with S Voice after I installed it. AT&T must have done something security permissions wise on their network otherwise all carriers would have had S Voice issues which we know isn't the case. The S Voice app in Galaxy Apps is the one and only update the N3 received in January so that's not what fixed the problem.
So, when I woke up this morning I noticed my cell signal strength icon was one I haven't seen before. I tried rebooting and toggling airplane mode. I also verified that my sim is working in another device. I attached a screen cap with the icon.
Noticed something similar with mine. I had to turn wifi off, restart to get LTE data (verizon) then turn wifi back on. If restarting with wifi on the LTE data doesn't register.
that didnt work for me
update: had to factory reset, looks like verizon doesnt like that essential ph1 wont take all their bloatware, etc. might have to return the phone if this keeps up
My data connection has also become very erratic - and I've lost voice+data (VoLTE connectivity) wholly yesterday. Worked fine with the activated SIM from my HTC 10 from the 31st to yesterday.. Now, not at all, I've not been able to restore it since.
Really don't want to return it, as I really like the phone, but this has nexus 5x issues written all over it for long term use...
Hoping essential can get a certification and an agreement with Verizon before my return window is over (or at all)..
Pretty disappointed in Verizon here.
Sent from my PH-1 using XDA Labs
Same here, another issue is that essential shipped my phone and within a day i had an email from essential saying that verizon certification is still in progress. verizon will probably not certify it with their system unless essential lets them install their monitoring crap all over the phone.
j1999t said:
Same here, another issue is that essential shipped my phone and within a day i had an email from essential saying that verizon certification is still in progress. verizon will probably not certify it with their system unless essential lets them install their monitoring crap all over the phone.
Click to expand...
Click to collapse
The Nexus 6P didn't have the bloat and worked fine.
My PH-1 works fine including Enhanced 4G LTE Mode.
What do you have selected for network type?
I have the first one selected because that's the only one that includes the various CDMA protocols, EVDO and LTE.
I see the same connectivity that I had with my Nexus 6P.
i have global selected, as it covers everything the phone can connect to. i had the first one selected but it wouldnt show the lte+, just regular lte. i also have Enhanced 4g lte mode on. it just happened to lose service earlier today. if it does it again, ill probably return it after a visit to vzw
tech_head said:
The Nexus 6P didn't have the bloat and worked fine.
My PH-1 works fine including Enhanced 4G LTE Mode.
What do you have selected for network type?
I have the first one selected because that's the only one that includes the various CDMA protocols, EVDO and LTE.
I see the same connectivity that I had with my Nexus 6P.
Click to expand...
Click to collapse
I have the same settings as you, I had functional "enhanced 4G LTE" for the first 4 days as well... That ended yesterday morning abruptly, and I'm not able to bring it back.. There's more happening here.. How long has your device been on the Verizon network? Only a hunch - in a few days you won't have "enhanced 4G LTE" either, even though it'll still be checked, and provisioned for it.
Sent from my PH-1 using XDA Labs
Cellular network is not available
After 7 days my phone won’t make calls I can only use data I’m on sprint and it was working fine until today I call sprint they had no answers at all I email essential no answer now I can only use WiFi calling while home and axx out at work
So, upon further digging I found a place to look at some more in-depth stuff relating to signal stuff. I did some fooling around and switched it from unknown to lte/cdma/umts auto (prl) and it seemed to work after a few moments of time. Though it seems have gone back to t he unknown state again but is working normally for me now, so maybe it was changing states and then a reboot?
How I got to this screen was by punching *#*#4636#*#* into the dialer, and went to phone info
I'm having a similar issue. I often lose my signal. I will have the full triangle/bars but no label of the signal(LTE+/LTE/3G/1x/etc....) and no cellular data at all.
The only way I can get it to return is to restart the device. Happens a few times a day, can't be 100% sure why, but it often appears to be when switching from WiFi -> Cellular only.
I have Verizon, I have had a Nexus 6 and then a Pixel XL for the past 3 years, never once had this issue.
I had constant disconnects and lost of service with my Tmo sim. Tried my Xfinity (VZW) sim and it was great until this morning. Complete lost of service. Airplaned mode on and off, connected to old school RTT 1x.... lol This phone's cellular just plain suck for a lot of us regardless of carrier. Not sure if we just have bad phones because apparently there are those who claim they have great service and connection.
I'm having this problem with Verizon. Seems like if I'm on wifi for a long period it only connects to 1x and putting in airplane mode and stuff won't get it to re-connect to to LTE. Only a reboot seems to fix the problem.
fade79 said:
I'm having this problem with Verizon. Seems like if I'm on wifi for a long period it only connects to 1x and putting in airplane mode and stuff won't get it to re-connect to to LTE. Only a reboot seems to fix the problem.
Click to expand...
Click to collapse
Necro post here but chiming in that I have the same problem with Verizon LTE. Happens when I'm moving long distances in car too. Suddenly just drops LTE and only a reboot will bring it back.
defTwitch said:
Necro post here but chiming in that I have the same problem with Verizon LTE. Happens when I'm moving long distances in car too. Suddenly just drops LTE and only a reboot will bring it back.
Click to expand...
Click to collapse
You might check out my post from the Oreo Beta thread... I was having some goofy signal issues early on which I've pretty much cleared up by doing what I mentioned here. Someone touched on it briefly earlier but only mentioned monkeying around with the settings, said nothing about picking up a new PRL.
I state this in that post too, but just in case: I offer this with no express intent of warranty, if you screw up your device, it's on you.
https://forum.xda-developers.com/es...-oreo-beta-program-live-t3705133/post74920423
I just changed it from global to LTE/WCDMA and I got LTE back almost immediately. Was weird and global had been working for me for awhile now so not sure what happened in the past few days...
wolfhelm said:
You might check out my post from the Oreo Beta thread... I was having some goofy signal issues early on which I've pretty much cleared up by doing what I mentioned here. Someone touched on it briefly earlier but only mentioned monkeying around with the settings, said nothing about picking up a new PRL.
I state this in that post too, but just in case: I offer this with no express intent of warranty, if you screw up your device, it's on you.
https://forum.xda-developers.com/es...-oreo-beta-program-live-t3705133/post74920423
Click to expand...
Click to collapse
I had, right after writing this, tried *#*#4636#*#*
I set it to global as instructed in another post. The next time I drive a distance in the car I'll have to see if I have the same issue that only a reboot would fix again.
Thanks
I had the same issue and I resolved it a little differently than the previous posters. I turned on adb debugging and logged into adb shell and user-disabled com.redbend.app. This stops the Sprint oma-dm service from running. After doing this I no longer have the issue of my device not reinitializing lte after sleep or 3g.
I have essential on vzw but my only issue is my device won't connect to 4G. If I change network to LTE I get full 4G service but I'm unable to make phone calls. Went into vzw store and they told me you didn't get the phone from us so we cant help you. Day 14 fml
On Xfinity mobile, I had similar issues. Great LTE but sometimes calls just don't work at all. I mess with various settings and it'll work for a bit then so again. Gave up and ported over to Sprint for the free unlimited year which is still probably not worth it. Should've kept with Xfinity Mobile. Lol
Before I updated via OTA to 8.1 the Essential was connecting to LTE without issue. Since 8,1 I have to connect to CDMA and 3g in order to user my Dialer, otherwise Server Error is generated. No calls in or out.
I wanted to downgrade Yes rebooted, factory reset, etc.
I searched google up and down with no real answers that work. How do I get Sideload working again? It has to be a simple configuration or driver problem I will assume.
Thanks
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Exxeviant said:
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
wolfu11 said:
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
Click to expand...
Click to collapse
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Bigdny said:
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Click to expand...
Click to collapse
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
wolfu11 said:
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
Click to expand...
Click to collapse
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
wolfhelm said:
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
Click to expand...
Click to collapse
Yeah I've screwed with this phone so much I don't know what I did LOL but now it shows wifi calling even in dialer. I'm not sure if it really works cuz I have a good signal so it never switches. My e911 address is set up from my Moto z and I do have a wear24 watch tied to this phone not sure if that's what triggered it. ? I did get a new SIM card on Monday as well because I was fighting with the vzw crap so I don't know exactly what triggered the WiFi calling.
wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?
wolfhelm said:
Are you on 8.0 or 8.1?
Click to expand...
Click to collapse
I upgraded to 8.1 via OTA. No root, no rom.
Bigdny said:
I upgraded to 8.1 via OTA. No root, no rom.
Click to expand...
Click to collapse
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
wolfhelm said:
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
Click to expand...
Click to collapse
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
tech_head said:
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
Click to expand...
Click to collapse
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
wolfhelm said:
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
Click to expand...
Click to collapse
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
That's a good point, I have reported as well.
tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
Doing the same right now. Just glad Im not the only one having the problem.
Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Try turning off Enchanted 4G LTE Mode. It's possible going to 8.1 just reset this setting to on. This should only be on if you have HD Voice enabled on your line on Verizon (you'll have to call Verizon to enable it, it's a free feature).
This should fix server error on 4G, randomly connecting to Sprint is a separate issue.
UPDATE Now working
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Bigdny said:
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Click to expand...
Click to collapse
Just wanted to second this post that a new sim card is the key to solving this issue. In my case, I was using Red Pocket CDMA (VZW network), and I ran into the same problem. Red Pocket rep explained to me that my sim got provisioned to 3g only and that I needed a new sim to connect to LTE. As soon as we switched to a new sim, I got LTE. I hope this helps others.