Related
I have a Rogers/Fido/Telus Nexus S. I tried a bunch of ROM's, CM7, ASOP, NSColab, Honycomb port. And then I realized that my 3G stopped working. I'm only getting Edge. My baseband version says "NO DGSXXXKB1", in the bootloader, carrier info says ATT. Any ideas?
do I need to re-flash the GRI40 radio again?
Same problem here. Initially all was working fine, then I tried to play with 2G/3G settings in Power Widget (CM7) since then, I am only able to get Edge connection.
I reset, changed firmwares, went back to my original Nandroid backup, no help.
I was also getting the Roaming Icon indicator on Fido's network, even though I purchased the Fido branded Nexus-S...
Tried changing Radio, KB1 and KB3, still no go.
I have owned Nexus One, Desire, Desire HD, Samsung Galaxy-S and Nexus-S
Never had issues except with Samsung phones!
Anyway, relocked NAND and this phone is going back.
Same. I was ASOP and the 2G was enable by default. I changed it to 3G and never saw 3G again. I thought swapping radios would do it, apparently not. Really weird. I guess I'm returning mine as well. Hopefully Future Shop will not snoop around too much.
Do you think odin would work?
nakadm said:
Same problem here. Initially all was working fine, then I tried to play with 2G/3G settings in Power Widget (CM7) since then, I am only able to get Edge connection.
I reset, changed firmwares, went back to my original Nandroid backup, no help.
I was also getting the Roaming Icon indicator on Fido's network, even though I purchased the Fido branded Nexus-S...
Tried changing Radio, KB1 and KB3, still no go.
I have owned Nexus One, Desire, Desire HD, Samsung Galaxy-S and Nexus-S
Never had issues except with Samsung phones!
Anyway, relocked NAND and this phone is going back.
Click to expand...
Click to collapse
The version of the phone changed to GRI40 which if I'm not mistaken is the T-mobile one. Which would explain everything. I hope one of the devs could help us out.
APN missing?
I have the same problem guys. After flashing CM7, I can only get edge connection. Whenever I turn on 3G from the toggle, a "H" sign will appear,but no internet at all! Wtf. Hope there is a solution for this. Back on stock nexus s (slcd i9023) for now
Sent from my Nexus S using XDA Premium App
Tony_M said:
APN missing?
Click to expand...
Click to collapse
Nope. It's there.
smoothfreeze said:
I have the same problem guys. After flashing CM7, I can only get edge connection. Whenever I turn on 3G from the toggle, a "H" sign will appear,but no internet at all! Wtf. Hope there is a solution for this. Back on stock nexus s (slcd i9023) for now
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Are you getting 3G on stock?
i.mac said:
Are you getting 3G on stock?
Click to expand...
Click to collapse
Yes. On 3G right now. I wonder whats the problem
Sent from my Nexus S using XDA Premium App
i just read somewhere else that after flashing the wcdma setting in *#*#4636#*#* got set to the wrong option. so type that and go change it back to wcdma preferred, or your preference.
nakadm said:
Same problem here. Initially all was working fine, then I tried to play with 2G/3G settings in Power Widget (CM7) since then, I am only able to get Edge connection.
I reset, changed firmwares, went back to my original Nandroid backup, no help.
I was also getting the Roaming Icon indicator on Fido's network, even though I purchased the Fido branded Nexus-S...
Tried changing Radio, KB1 and KB3, still no go.
I have owned Nexus One, Desire, Desire HD, Samsung Galaxy-S and Nexus-S
Never had issues except with Samsung phones!
Anyway, relocked NAND and this phone is going back.
Click to expand...
Click to collapse
Never hit the 2G/3G button. Its broken, been broken and doesnt work as of yet. Just dont hit it.
Had the same problem. For some reason it was on the wrong band (if that's possible). in the *#*#4636#*#*, phone information, menu, select radio-band, USA, and fixed!
Still getting no 3G/H on my CM7. I even tried the *#*#4636 method, still no go. However I can surf the browser to sites like google, facebook etc. But whenever I want to sync my google acc, I will get a network error. Wtf? One thing that I noticed is that, my signal bars won't "light up" (but I can surf the net). Another thing, after flashing to CM7, my build number changed to GRI40 instead of GRI54 in the settings on stock. Maybe that is the problem?
smoothfreeze said:
Still getting no 3G/H on my CM7. I even tried the *#*#4636 method, still no go. However I can surf the browser to sites like google, facebook etc. But whenever I want to sync my google acc, I will get a network error. Wtf? One thing that I noticed is that, my signal bars won't "light up" (but I can surf the net). Another thing, after flashing to CM7, my build number changed to GRI40 instead of GRI54 in the settings on stock. Maybe that is the problem?
Click to expand...
Click to collapse
I tried changing it to CDMA preferred and it changes itself back.
Sent from my Nexus S using Tapatalk
Put this into your dial pad: *#*#4636#*#*
Then hit Phone Information
Then hit the menu button and select radio band, the select corresponding Country.
USA will fix our issues.
I found a dirty workaround for this problem. Turn on airplane mode, then turn it off. Worked for me.
Same issue for me on the Nexus One. 3G icon is there when phone is idle. As soon as I try to do anything data-related (ie. browser) it switched to an H.
Tried setting to USA, no dice. APN is internet.com
crap I guess no root for my nexus S until this canadian carrier thing is resolved...
I thought i would throw in my experiance
I bought a Nexus S from Telus, and i am using it with a Sasktel Sim on Bell/Sasktel network (live in sask but have a national account from Bell) and on stock, i could never get H.....only the 3g would show up. But that was short lived because i flashed CM7 on it and the H now appears and works perfectly fine
So i dunno if its a Rogers frequency thing/problem, but the phone works great on HSPA on Bell/Sasktel
Cheers
I've never had this happen before, I can't get my phone to connect to Google services. Some Google apps are still working and sync is working. The only app I ran across that doesn't seem to work is Talk. It also seems my data is slow to respond to me accessing something on the internet, it will just sit at the 3G signal and do nothing for a while.
When I first flash everything runs great until I reboot then the connection issue starts. Anyone got any ideas?
Running AOKP nightlies, and I've tried several different versions.
Latest Faux kernel.
xsnipuhx said:
I've never had this happen before, I can't get my phone to connect to Google services. Some Google apps are still working and sync is working. The only app I ran across that doesn't seem to work is Talk. It also seems my data is slow to respond to me accessing something on the internet, it will just sit at the 3G signal and do nothing for a while.
When I first flash everything runs great until I reboot then the connection issue starts. Anyone got any ideas?
Running AOKP nightlies, and I've tried several different versions.
Latest Faux kernel.
Click to expand...
Click to collapse
I always used to have issues with GTalk when restoring from TB after flashing a new ROM. I suggest to never back up GAPPS when flashing ROM's. If that's what you did... wipe everything again and start over but do not restore GTalk. Hope that works for you.
What carrier are you on?
Double check your APN settings (Settings > Wireless & networks > Mobile networks > Access Point Names)
If it's WiFi, it's probably a ROM-thing. Reflash or use another one
asawoszc said:
I always used to have issues with GTalk when restoring from TB after flashing a new ROM. I suggest to never back up GAPPS when flashing ROM's. If that's what you did... wipe everything again and start over but do not restore GTalk. Hope that works for you.
Click to expand...
Click to collapse
Alright, so I tried this and it didn't work. Only thing I restored was battle net authenticator.
309041291a said:
What carrier are you on?
Double check your APN settings (Settings > Wireless & networks > Mobile networks > Access Point Names)
If it's WiFi, it's probably a ROM-thing. Reflash or use another one
Click to expand...
Click to collapse
T-Mobile. I didn't get too check the APNs before I restored from a previous version. It looks like a AOKP build from Dec 24 and its got Faux working on it perfectly. I'll try another build at a later date unless someone has any advice that I can try.
Bumping for hopeful solution to this. I've tried running JellyBro, JellyBeer, newer AOKP and even an older Gapps. I can't seem to solve this problem. ANY info would be appreciated.
Edit: So taking out my sim card and letting the N4 sit on wifi does the trick but as soon as I put the sim card back in it continues to have problems. This leads me to believe its the sim card so i put it into my Gnex and it works just fine...
Bumping again for anyone who has any ideas on how to fix this. Haven't been able to even use my Nexus yet since I've gotten it because of this.
xsnipuhx said:
Bumping again for anyone who has any ideas on how to fix this. Haven't been able to even use my Nexus yet since I've gotten it because of this.
Click to expand...
Click to collapse
Someone please help, I'm having the same problem, if I solve it, I'll let you know...
The details:
So I recently acquired my Nexus 4 on the T-Mobile $30 plan, coming from it's brother the Optimus G on Sprint.
It is rooted and running CM11 and I have been using Spare Phone and GrooveIP for VoIP calls with no problems whatsoever. I finally decided to pull the trigger and use the Play Store app to add LTE support since my area supports it. Got that working too so I'm feeling good, but I realized shortly after that I cannot make a VoIP call over data now. WiFi still works perfectly, but on data it will ring and connect but there is no audio sent or received from either party.
I reverted back to my working backup with no luck so I did the adb/fastboot method of returning the phone to the stock image and then rerooting, reinstalling the rom and then testing VoIP over data and still no luck. I then proceeded to reinable LTE and it works again.
So in short, I tried to revert to stock modem and APN settings with no luck, but I am currently on the .98/.33 hybrid modem with the fast.t-mobile apn settings again. Also not sure if something in the *#*#INFO#*#* menu could have messed it up, but that's why I reverted to stock...
The question:
Is there any other reason all of my VoIP apps would stop working over mobile data, but still work on WiFi?
highnoteuser said:
The details:
So I recently acquired my Nexus 4 on the T-Mobile $30 plan, coming from it's brother the Optimus G on Sprint.
It is rooted and running CM11 and I have been using Spare Phone and GrooveIP for VoIP calls with no problems whatsoever. I finally decided to pull the trigger and use the Play Store app to add LTE support since my area supports it. Got that working too so I'm feeling good, but I realized shortly after that I cannot make a VoIP call over data now. WiFi still works perfectly, but on data it will ring and connect but there is no audio sent or received from either party.
I reverted back to my working backup with no luck so I did the adb/fastboot method of returning the phone to the stock image and then rerooting, reinstalling the rom and then testing VoIP over data and still no luck. I then proceeded to reinable LTE and it works again.
So in short, I tried to revert to stock modem and APN settings with no luck, but I am currently on the .98/.33 hybrid modem with the fast.t-mobile apn settings again. Also not sure if something in the *#*#INFO#*#* menu could have messed it up, but that's why I reverted to stock...
The question:
Is there any other reason all of my VoIP apps would stop working over mobile data, but still work on WiFi?
Click to expand...
Click to collapse
A few people including myself have been discussing this issue in the thread I linked below. We haven't really found much out, though it seems that it is T-Mobile at fault when you consider all of the variables. Here is an argument by user Ztone:
"What helped me was arguing that I know five other users who's issue started happening exactly at the same time and only on T Mobile's network. There are only 4 components to this: the phone, groove IP, Google and T Mobile. It cannot be the phone or groove IP if many others are experiencing the same thing at the same time (not to mention the fact that I had wipe the phone and reinstalled everything clean). It can't be Google because then it wouldn't work on wifi. This leaves T Mobile. My Tech troubleshooter from t-mobile had me delete the data from Google IP and restart the phone. While I had the phone off she did something on her end to refresh something on T Mobile's network regarding data coming to my phone, then after I restarted the phone. It still didn't work, then she asked me to try on wifi and then it worked perfectly. That seemed to be the tipping point, when she escalated it to engineering. Whatever that means. But I was told to give it 72 hours. Yeah, I think we need to make some noise to T Mobile."
http://forum.xda-developers.com/nex...30-prepaid-plan-users-thread-t2001290/page322
So did you say when you re-enabled LTE the calls worked again? If so that would be a good temporary fix.
jjflemin said:
A few people including myself have been discussing this issue in the thread I linked below. We haven't really found much out, though it seems that it is T-Mobile at fault when you consider all of the variables. Here is an argument by user Ztone:
"What helped me was arguing that I know five other users who's issue started happening exactly at the same time and only on T Mobile's network. There are only 4 components to this: the phone, groove IP, Google and T Mobile. It cannot be the phone or groove IP if many others are experiencing the same thing at the same time (not to mention the fact that I had wipe the phone and reinstalled everything clean). It can't be Google because then it wouldn't work on wifi. This leaves T Mobile. My Tech troubleshooter from t-mobile had me delete the data from Google IP and restart the phone. While I had the phone off she did something on her end to refresh something on T Mobile's network regarding data coming to my phone, then after I restarted the phone. It still didn't work, then she asked me to try on wifi and then it worked perfectly. That seemed to be the tipping point, when she escalated it to engineering. Whatever that means. But I was told to give it 72 hours. Yeah, I think we need to make some noise to T Mobile."
http://forum.xda-developers.com/nex...30-prepaid-plan-users-thread-t2001290/page322
So did you say when you re-enabled LTE the calls worked again? If so that would be a good temporary fix.
Click to expand...
Click to collapse
Thanks for pointing me to that thread, I'll read up shortly. This all started for me between Saturday night and Sunday morning.
Re-enabling LTE does not fix it. I actually thought that broke it at first, but since reverting to factory settings didn't fix it I figured I might as well continue to enjoy LTE even if VoIP is broken.
highnoteuser said:
Thanks for pointing me to that thread, I'll read up shortly. This all started for me between Saturday night and Sunday morning.
Re-enabling LTE does not fix it. I actually thought that broke it at first, but since reverting to factory settings didn't fix it I figured I might as well continue to enjoy LTE even if VoIP is broken.
Click to expand...
Click to collapse
Yeah, unfortunately we have no solution yet. I'm in the same boat as you. I'm just glad it works over WiFi.
jjflemin said:
Yeah, unfortunately we have no solution yet. I'm in the same boat as you. I'm just glad it works over WiFi.
Click to expand...
Click to collapse
Tonight I'll test Spare Phone on my wife's (my old) Optimus on Sprint. I expect it will work normally and will report back to rule out the app itself since I will be using my same Google account.
highnoteuser said:
Tonight I'll test Spare Phone on my wife's (my old) Optimus on Sprint. I expect it will work normally and will report back to rule out the app itself since I will be using my same Google account.
Click to expand...
Click to collapse
Confirmed that VoIP on data works with Spare Phone and GrooveIP on other networks.
It appears that I am back in business with no change on my part...
Help. I bought my note 3 the day it came out. I have been running Alliance build 1 since it came out. A couple of days ago I noticed my phone wouldn't connect to data unless I was on WiFi. The 4g icon stays grayed out. I could still send text messages though. But if I opened the my Verizon app, the 4G icon would brighten and it would connect to Verizon. But no other app can access data, even when the 4G icon was highlighted. So I hoped upgrading to build 2 would solve the problem. BUT NO LUCK. Now I can't send text messages or connect to data. Any body have a clue?
update
So I spent an hour on the phone with Verizon. They said they couldn't find any problems on their end, and we troubleshot my phone and nothing helped. So it is something going on with my phone for sure and not the network. Should I try another Sim card? Should I Odin another modem? Should I Odin back to stock and see if I can connect then to data?
Update
Well, I've tried several different modems. None of them worked. What I don't understand is why the modem will connect when I open the My Verizon app, but nothing else. Leads me to believe there is something software wise that won't let it connect. But it stopped working when I was on Alliance build 1 and that problem carried to build 2. HELP
turtletodd23 said:
Well, I've tried several different modems. None of them worked. What I don't understand is why the modem will connect when I open the My Verizon app, but nothing else. Leads me to believe there is something software wise that won't let it connect. But it stopped working when I was on Alliance build 1 and that problem carried to build 2. HELP
Click to expand...
Click to collapse
Odin back to stock and see if still persists. If it does then it's hardware. If not then starting fresh and rooting/flashing the rom should fix.
Sent from my SM-N900V using Tapatalk
Please any ideas?
So I Odined back to MJE. Still doesn't work. Odined back NC4 and the modem still won't connect. But the modem/data works. The My Verizon app will turn the data on and connect like normal. There has to be something keeping other programs from accessing the modem/data. Otherwise My Verizon wouldn't connect. Please can anybody help.....
Update...HELP....SOS
So it isn't hardware related. I just turned my Hotspot on. Guess what, the Hotspot works. My wife was able to connect to my Hotspot and use my data. BUT I still can't use it on my phone. Even when she was connected to my Hotspot using my data, I couldn't use data. How weird is that!? Please, help....
Did you actually Odin back to stock firmware or did you just Odin the radio?
Sent from my SM-N900V using Tapatalk
turtletodd23 said:
So it isn't hardware related. I just turned my Hotspot on. Guess what, the Hotspot works. My wife was able to connect to my Hotspot and use my data. BUT I still can't use it on my phone. Even when she was connected to my Hotspot using my data, I couldn't use data. How weird is that!? Please, help....
Click to expand...
Click to collapse
Did you by and chance turn off Mobile Data in Settings->More Networks-> Mobile Networks
Sent from my Note 3 via Tapatalk
I am stumped.
I Odined just the MJE modem at first, didn't help. Then I Odined back to stock Nc4 firmware, did factory reset, didn't work. I've spent hours pouring through every menu I could find to see if there was something not turned on, then I did it again. I haven't gone into service mode yet. I've toggled data/airplane mode/global-ltecdma/anything else I could find hoping it would help. Still no dice. But the Verizon app still connects add well as my Hotspot so other devices can use my data.
Did you try your APN settings? With all that flashing you have done maybe lost your APN settings.
If I helped Hit the Thanks Button Like This?
S2_brickmaker said:
Did you try your APN settings? With all that flashing you have done maybe lost your APN settings.
Click to expand...
Click to collapse
Yeah, I checked them against the settings I have found on the Internet. I couldn't create my own for some reason though. The option is grayed out on my phone...
Update
To add to the confusion, data decided to start working again today. Looked down and noticed it was back on.
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.