AT&T / HSPA from downgrade - Nexus 6P Q&A, Help & Troubleshooting

OK so a few weeks ago I downgraded from Nougat preview 5 back to 6.0.1. When I did this, suddenly I was having issues with only being able to get HSPA instead of LTE. I called AT&T and they pushed information to my phone for what I am assuming was a SIM card config. After that, LTE came back till last night. Again it started acting up so I called and was basically told your on a unlocked phone, go fish. So after that I continued to research and aligned my APN settings to what was in article published by AT&T for setting up the APN on non AT&T devices. LTE came back and since then I have had no issues getting LTE (knock on wood). The two items I changed in the APN was removing the fota from APN type and setting APN protocol to IPv4 only. Previously it was the combined setting for IPv4 and IPv6. I also in the last few days upgraded to the final version of Nougat.
However what really still bugs me is what happened during the downgrade to start all of this..... Prior to this I had this Nexus 6P for 7 months and never had a LTE connection issue. Any thoughts? I am going to be traveling to Canada and Mexico, anyone see any issues with my config for International travel? I posted screenshots of my settings.
Thanks in advance!

downgrades are notorious for messing things up. my advice, under apn options, reset to default, and then delete everything except att nextgenphone, reboot, go to back up and reset settings and do a network settings reset. should sort you out.
oh, and wait to connect to wifi until it actually connects to LTE first

murtezahu said:
downgrades are notorious for messing things up. my advice, under apn options, reset to default, and then delete everything except att nextgenphone, reboot, go to back up and reset settings and do a network settings reset. should sort you out.
oh, and wait to connect to wifi until it actually connects to LTE first
Click to expand...
Click to collapse
Question on the last part under network settings, if I do that reset does it wipe the configuration on the SIM card. The wording gives me a 50/50 perspective on it doing that.

roaddaw9 said:
Question on the last part under network settings, if I do that reset does it wipe the configuration on the SIM card. The wording gives me a 50/50 perspective on it doing that.
Click to expand...
Click to collapse
Can't be 100% sure
From experience, android doesn't mess with the SIM card on its own. Usually the carrier has to push changes. The fact that it worked before and stopped working after downgrade seems to point to the fact that their was never and issue with the SIM. It was an os issue... But do what you're comfortable with, if it ain't broke...
Keep these instructions for if it ever screws up again

murtezahu said:
Can't be 100% sure
From experience, android doesn't mess with the SIM card on its own. Usually the carrier has to push changes. The fact that it worked before and stopped working after downgrade seems to point to the fact that their was never and issue with the SIM. It was an os issue... But do what you're comfortable with, if it ain't broke...
Keep these instructions for if it ever screws up again
Click to expand...
Click to collapse
Thanks for your help and input

Related

[Q] No service after trying LTE

Hi
I was playing around with my phone and tried the old hack through the settings screen, *#*#4636#*#*.
Switched it to LTE and set up a new APN for Rogers LTE.
It Didn't work. After more reading I discovered this wouldn't work for me anyway. I have Android 4.4.2 and I don't think my SIM is LTE enabled.
I rebooted thinking it would just go back to the original settings.
It seems to have gone back but now I have No signal at all.
I am with Rogers. I tried going back to the original APN settings and selecting Rogers.
The phone is finding the correct networks for my area.
I tried the Reset to default in the APN settings. This sets the APNs to Rogers LTE and chatr, not the original Rogers APN that I started with.
The phone is rooted but running stock Android 4.4.2.
The baseband seems correct.
What have I done and how do I fix it?
Have I done something to the Rogers SIM?
Thanks
Angus_xda said:
Hi
I was playing around with my phone and tried the old hack through the settings screen, *#*#4636#*#*.
Switched it to LTE and set up a new APN for Rogers LTE.
It Didn't work. After more reading I discovered this wouldn't work for me anyway. I have Android 4.4.2 and I don't think my SIM is LTE enabled.
I rebooted thinking it would just go back to the original settings.
It seems to have gone back but now I have No signal at all.
I am with Rogers. I tried going back to the original APN settings and selecting Rogers.
The phone is finding the correct networks for my area.
I tried the Reset to default in the APN settings. This sets the APNs to Rogers LTE and chatr, not the original Rogers APN that I started with.
The phone is rooted but running stock Android 4.4.2.
The baseband seems correct.
What have I done and how do I fix it?
Have I done something to the Rogers SIM?
Thanks
Click to expand...
Click to collapse
Did you flash a LTE Hybrid?
Sent with my Nexus® 10 minus 3
Berrydroidcafe said:
Did you flash a LTE Hybrid?
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
I didn't flash anything.
Angus_xda said:
I didn't flash anything.
Click to expand...
Click to collapse
Had to assume that because I've never seen someone try LTE without doing so.
What you can try is find the stock radio, which might still be the same as you are using, then flash it. Maybe that will reset things back to normal.
Sent with my Nexus® 10 minus 3
Berrydroidcafe said:
Had to assume that because I've never seen someone try LTE without doing so.
What you can try is find the stock radio, which might still be the same as you are using, then flash it. Maybe that will reset things back to normal.
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
No luck.
I tried flashing the stock radio then flashed everything using efrant's instructions. Still no go.
The thing I find strange is when I select Reset to default in the APN settings it sets the APN to Rogers LTE not the default 3G setting.
Delete the Rogers LTE apn and make a new one with this info:
Name: Rogers
APN: rogers-core-appl1.apn
MMSC: http ://mms.gprs.rogers.com
MMS Proxy: 10.128.1.69
MMS Port: 80
MCC: 302
MNC: 720
APN Type: mms
You can also try this one:
APN: internet.com
Username: wapuser1
Password: wap
Go to phone info *#*#4636#*#*, and change network type to WCDMA Preferred. Reboot, and see if that does it.
I've done that several times.
Still won't connect.
The error is; No service. Selected network (ROGERS) unavailable.
When I search networks Telus, Bell and Rogers all show up.
I've tried selecting Rogers and selecting automatically. When I select automatically it selects Rogers but comes back with the same error.
Try reflash Radio
alexcheveau said:
Try reflash Radio
Click to expand...
Click to collapse
That was already suggested.
I have tried wiping everything out and flashing a complete stock 4.4.2.
I've also tried another Rogers SIM.
This is getting ridiculous.
All I did was change a setting from "WCDMA Preferred" to "LTE/GSM auto (PRL)" and back again and that killed a phone?
Angus_xda said:
That was already suggested.
I have tried wiping everything out and flashing a complete stock 4.4.2.
I've also tried another Rogers SIM.
This is getting ridiculous.
All I did was change a setting from "WCDMA Preferred" to "LTE/GSM auto (PRL)" and back again and that killed a phone?
Click to expand...
Click to collapse
I find this very strange. I use the secret menu on two phones but have never heard of this happening. My N4 will only lose signal for a few moments before switching to gsm autoprl, after switching from LTE/GSM.
Sent from backpack
Mystery solved.
I don't know why it happened at exactly the time when I tried LTE but...
The phone has been reported lost or stolen.
I bought it over two weeks ago. I checked the IMEI on the Government web site, that is supposed to protect us from this kind of thing, and it came back clean. I checked again last night and it's blacklisted.
I would say the girl that I bought it from got it on a $0 contract. Sold it then reported it lost or stolen. She's still on the hook for the contract but, so what, she'll never really have to pay it. Either that or it takes 2-3 weeks for a phone to show up on the blacklist.
Either way, the Government initiative to blacklist stolen or lost phones sounded like a good idea but in reality it's not protecting anyone.
So, now I have a small tablet and learned a lesson. Don't buy used cell phones and if you do, don't trust the protectyourdata.ca web site to protect you.
The site boasts;
"Purchasing a pre-owned device?
Check the IMEI number here to ensure the device has not been reported lost or stolen in Canada."
Thanks for trying to help folks. I did learn more about Android through this.
Angus_xda said:
Mystery solved.
I don't know why it happened at exactly the time when I tried LTE but...
The phone has been reported lost or stolen.
I bought it over two weeks ago. I checked the IMEI on the Government web site, that is supposed to protect us from this kind of thing, and it came back clean. I checked again last night and it's blacklisted.
I would say the girl that I bought it from got it on a $0 contract. Sold it then reported it lost or stolen. She's still on the hook for the contract but, so what, she'll never really have to pay it. Either that or it takes 2-3 weeks for a phone to show up on the blacklist.
Either way, the Government initiative to blacklist stolen or lost phones sounded like a good idea but in reality it's not protecting anyone.
So, now I have a small tablet and learned a lesson. Don't buy used cell phones and if you do, don't trust the protectyourdata.ca web site to protect you.
The site boasts;
"Purchasing a pre-owned device?
Check the IMEI number here to ensure the device has not been reported lost or stolen in Canada."
Thanks for trying to help folks. I did learn more about Android through this.
Click to expand...
Click to collapse
That really sucks
But thanks for letting us know.
Sent by carrier pigeon
klvnhng said:
That really sucks
But thanks for letting us know.
Sent by carrier pigeon
Click to expand...
Click to collapse
I've seen about 2 or 3 threads on Android Central with the same symptoms that seemed to never get resolved.
I suspect they had the same problem and either didn't know how to check or were to embarrassed to say.
I was upset but I want others to be able to find this answer.
Through buying and selling different phones working my way up to the Nexus 4 I'm really only $110 out of pocket.
A 16GB Android media player with WiFi must be worth $110.
So, is there a way to eliminate the wireless radio and leave WiFi?
I guess I should start another thread on that.
Angus_xda said:
I've seen about 2 or 3 threads on Android Central with the same symptoms that seemed to never get resolved.
I suspect they had the same problem and either didn't know how to check or were to embarrassed to say.
I was upset but I want others to be able to find this answer.
Through buying and selling different phones working my way up to the Nexus 4 I'm really only $110 out of pocket.
A 16GB Android media player with WiFi must be worth $110.
So, is there a way to eliminate the wireless radio and leave WiFi?
I guess I should start another thread on that.
Click to expand...
Click to collapse
I guess the simplest way would be to just have airplane mode on?
Sent by carrier pigeon
klvnhng said:
I guess the simplest way would be to just have airplane mode on?
Sent by carrier pigeon
Click to expand...
Click to collapse
Airplane mode also turns of the WiFi.
I just pulled the SIM, deleted all APNs, turned off Mobile Data and left WiFi on.
The warning that I had no data connection is gone and I still have the ability to make a 911 call if necessary.
Unlocked, rooted and flashed a USB-OTG enabled kernel. This is great fun...
Angus_xda said:
Airplane mode also turns of the WiFi.
I just pulled the SIM, deleted all APNs, turned off Mobile Data and left WiFi on.
The warning that I had no data connection is gone and I still have the ability to make a 911 call if necessary.
Unlocked, rooted and flashed a USB-OTG enabled kernel. This is great fun...
Click to expand...
Click to collapse
You can turn wifi on with airplane mode on as well. Just do it after airplane mode is already on.
But that works too, I guess
Sent by carrier pigeon
klvnhng said:
You can turn wifi on with airplane mode on as well. Just do it after airplane mode is already on.
But that works too, I guess
Sent by carrier pigeon
Click to expand...
Click to collapse
Yep, just figured that out.
Did you make a police report? You might not be able to recoup anything, but you should still make the seller be responsible for their actions
Sent from my Nexus 4 using xda app-developers app

WARNING! Do not update to 8.1 if your phone is CDMA

HTC 8X/8S
HUAWEI W1
Confirmed brick after 8.1 developer update with CDMA network.
Lumia 822 Verizon
Confirmed no problem if you use GSM/WCDMA.
If you have already bricked your phone, try this:
1.Power down phone by pressing Power button.
2.Press Power button and Volume +/- button at the same time, phone will go to flash mode.
3.Press Camera button for 5 seconds to power off your phone.
4.insert a GSM/WCDMA SIM card in your phone and turn on phone.
It seems that 8.1 not compatible with CDMA SIM card.
reker said:
HTC 8X/8S
HUAWEI W1
Confirmed brick after 8.1 developer update with CDMA network.
Lumia 822 Verizon
Confirmed no problem if you use GSM/WCDMA.
If you have already bricked your phone, try this:
1.Power down phone by pressing Power button.
2.Press Power button and Volume +/- button at the same time, phone will go to flash mode.
3.Press Camera button for 5 seconds to power off your phone.
4.insert a GSM/WCDMA SIM card in your phone and turn on phone.
It seems that 8.1 not compatible with CDMA SIM card.
Click to expand...
Click to collapse
I have it on my htc 8xt and its working fine. Well I am having lockscreen issues but the network is working fine for me on sprint.
starsoccer9 said:
I have it on my htc 8xt and its working fine. Well I am having lockscreen issues but the network is working fine for me on sprint.
Click to expand...
Click to collapse
the problem with me no wifi
no mobile data
That is so far from something you could call a "brick" it's not funny. "Brick" means un-recoverable. If you can "un-brick" something without diassembling it or at least using hardware a normal user couldn't have access to, it's not a brick!
Also, has anybody else actually had this problem? A few people seem to indicate that they have *not*...
No problems what-so-ever updating and running on my Odyssey...other than taking forever to download and install.
Working fine in my Lumia Icon from Verizon.
No cellular data after hard reset
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
GoodDayToDie said:
That is so far from something you could call a "brick" it's not funny. "Brick" means un-recoverable. If you can "un-brick" something without diassembling it or at least using hardware a normal user couldn't have access to, it's not a brick!
Also, has anybody else actually had this problem? A few people seem to indicate that they have *not*...
Click to expand...
Click to collapse
HTC confirmed this yesterday, they awared the problem and contacting with MS. Announcement by HTC China
The problem covered both HTC 8s(A620D) and 8x(C620d)
8X/8S have similar but more serious problem with gdr1 - gdr2 upgrade last year, even can't boot into SPL.
By the way, to normal users, if their phone turn into black screen and can't boot, it's a brick. No one will care about if it's a real brick, what they know is: I can't use my phone, it's not working, just like a brick.
fgr said:
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
Click to expand...
Click to collapse
i got the same issue with my ativ s.
everything works except mobile data.
is there some settings i can try since i didnt do a hard reset but the normal reset from the phones "about" menu.
my network is WIND greece.
fgr said:
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
Click to expand...
Click to collapse
No need to apologize for the novel! I did the SAME exact thing as you (except I hard resetted via settings > about > more info > reset your phone). Luckily I know my MSL, and have my MSID handy. I wiped my settings by doing ##72786# and selecting ok twice. I rebooted my phone manually and then went to the 'activate my device' app in settings. It did what looked like a profile update and it said my phone was successfully activated with my phone number listed.
I can browse the web on Sprint's network, make/receive calls and send/receive texts. The only thing I can't figure out to fix is MMS. I can't get or send picture mail, group texts or any kind of MMS at all.
I've managed to get my coworkers settings from his ATIV S Neo but I can't figure out how to edit them on my phone. Going into ##3282# doesn't let me edit things that deeply.
From what I've heard on other forums is that we're basically SOL unless Sprint releases their firmware updates and their release of 8.1 soon (which they have confirmed they will do this summer).
I figured from the get go when this started yesterday that this 8.1 release doesn't seem to properly support CDMA and judging by how many people have this issue, I was correct. Microsoft really needs to work better on the CDMA side of things.
fgr said:
I by no means have a brick, but I do now have an issue. Here’s what happened.
I have a Sprint ATIV S Neo, GDR3, Interop-unlock, the whole deal.
Installed the 8.1 update yesterday, and everything was working. I have been playing with all kinds of “stuff” in the registry and such, so I decided that since I had just installed 8.1 I would start fresh and do a hard reset. I don’t really care about keeping interop-unlock at this point. Even with it, so much is still locked down. I’m sure in the future someone will get this cracked and we can really have fun, but until then, just being developer unlocked is good enough.
So, when I got home I reset the phone (power+volume down, exclamation point, then the remaining sequence).
Phone boots back up, and I connect to my WiFi and set everything back up. I think life is wonderful at this point. Then decide to test my 4G download speed so I turn off wifi.
Oops, no cellular data, phone calls and text are fine (didn’t try mms, but probably doesn’t work, blank url in the provisioning). Tried all the usual tricks (##72786# and such). I have my msl, so I go into the provisioning, and things look messed up. My MDN and MSID are 000003872. That makes no sense, so I set them back to the correct values and still no go.
Called Sprint. They ran me through all the usual things that I had already done (hour on the phone with them).
Long story short: The activation program seems to be missing from my phone. Hands free activation never tries to start, in fact, after hard resetting again and watching closely, during setup it says “Activate your device can’t be opened”. And the network settings are missing from the settings menu.
So after work I’m going to take it to Sprint and hopefully they have a factory image they can flash (hopefully an older version so I can update things myself).
My thinking is that the 8.1 update is basically the new rom, but during install doesn't delete the existing carrier programs. When I hard reset, all that got re-installed was the strictly Microsoft stuff, not the carrier specific items i.e. hands free activation.
PS Sorry about the novel...
Click to expand...
Click to collapse
I saw your reply to my thread for the same issue. I did some research on WP Central and found another thread where someone was having the same issue with an Ativ S and the solution was to manually enter the APN information. I don't know what the APN info is for Sprint, but when I checked it on my phone it was blank. It seems like a safe bet that updating that info would fix the issue.
---------- Post added at 04:01 PM ---------- Previous post was at 03:40 PM ----------
iknowsingh said:
No need to apologize for the novel! I did the SAME exact thing as you (except I hard resetted via settings > about > more info > reset your phone). Luckily I know my MSL, and have my MSID handy. I wiped my settings by doing ##72786# and selecting ok twice. I rebooted my phone manually and then went to the 'activate my device' app in settings. It did what looked like a profile update and it said my phone was successfully activated with my phone number listed.
I can browse the web on Sprint's network, make/receive calls and send/receive texts. The only thing I can't figure out to fix is MMS. I can't get or send picture mail, group texts or any kind of MMS at all.
I've managed to get my coworkers settings from his ATIV S Neo but I can't figure out how to edit them on my phone. Going into ##3282# doesn't let me edit things that deeply.
From what I've heard on other forums is that we're basically SOL unless Sprint releases their firmware updates and their release of 8.1 soon (which they have confirmed they will do this summer).
I figured from the get go when this started yesterday that this 8.1 release doesn't seem to properly support CDMA and judging by how many people have this issue, I was correct. Microsoft really needs to work better on the CDMA side of things.
Click to expand...
Click to collapse
Would you be willing to post the settings? I am guessing that the issue may be partially related to APN settings being missing under Settings, Cellular+SIM, SIM settings. I read a post by someone on another forum who had the same data issues but fixed them by entering the APN information for his carrier. I've tried a couple of different APN settings that I've found out on the web for Sprint, but I'm not sure they are accurate. All I know is that they were missing when I checked them on my phone.
i have fixed my issue with some internet research.
adding manually the APN of the provider in the APN settings solved the issue for me.
hope i helped.
Would you be willing to post the settings? I am guessing that the issue may be partially related to APN settings being missing under Settings, Cellular+SIM, SIM settings. I read a post by someone on another forum who had the same data issues but fixed them by entering the APN information for his carrier. I've tried a couple of different APN settings that I've found out on the web for Sprint, but I'm not sure they are accurate. All I know is that they were missing when I checked them on my phone.
Click to expand...
Click to collapse
I would not mind at all! I went into ##3282# on his phone, selected 'view' then 'others' then 'MMSC URL' . The two pictures are attached, the order of the settings begins with the picture that says '[email protected]'. The second pic is literally a continuation as it starts right where the first picture ends (I scrolled neatly!)
I've been trying to find the correct Sprint APN settings around the web, and a lot of sites have similar settings as options but either Windows Phone doesn't have enough fields for the settings, and the fact that in the APN settings on 8.1, it doesn't let me change the authentication type.
I noted on my coworker's ATIV S Neo that in his 'cellular+SIM' section, he doesn't have options to input APN like I do... the hard reset must've kicked the CDMA stuff in our phones to the curb.
fatdata said:
i have fixed my issue with some internet research.
adding manually the APN of the provider in the APN settings solved the issue for me.
hope i helped.
Click to expand...
Click to collapse
Would you mind posting the APN settings you used? That would be appreciated... I've tried going to various sites but wasn't sure what was the correct ones.
iknowsingh said:
Would you mind posting the APN settings you used? That would be appreciated... I've tried going to various sites but wasn't sure what was the correct ones.
Click to expand...
Click to collapse
they are for greek providrs though... I think you need to find the ones for your provider.
note: i just used the GPRS APN address for wind (my provider) and it worked the rest seemed to not make any diference
VODAFONE
GPRS APN: - internet.vodafone.gr ή webonly.vodafone.gr
Username: - {κενό}
Password: - {κενό}
MCC=202
MNC=05
APN type=default
DNS: - 213.249.17.10, 213.249.17.11
WIND
GPRS APN: - gnet.b-online.gr ή gint.b-online.gr
Username: - {κενό}
Password: - {κενό}
MCC=202
MNC=10
APN type=default
DNS: - 212.152.79.19, 212.152.79.20
fatdata said:
they are for greek providrs though... I think you need to find the ones for your provider.
note: i just used the GPRS APN address and it worked the rest seemed to not make any diference
Click to expand...
Click to collapse
Ahhhh, Vodafone... I assumed you were a Sprint brethren... I appreciate your post nonetheless! Thank you, sir. Now to continue the hunt for correct Sprint settings -_-
Just got back from two Sprint stores and a Best Buy with Samsung reps on hand. None of them had access to any means of reflashing to stock, and really had no useful information. I was surprised by how little they knew about any Windows phones.
I do have TEP though, and they ordered me a new phone. I should have it in a few days. Costing me nothing
Wish I had something useful to tell you folks...
fgr said:
Just got back from two Sprint stores and a Best Buy with Samsung reps on hand. None of them had access to any means of reflashing to stock, and really had no useful information. I was surprised by how little they knew about any Windows phones.
I do have TEP though, and they ordered me a new phone. I should have it in a few days. Costing me nothing
Wish I had something useful to tell you folks...
Click to expand...
Click to collapse
I actually work for a Sprint store (non service/repair location) and I don't have TEP. I actually DO have an upgrade available since I bought the ATIV S Neo off-contract. I wouldn't mind using my upgrade on another ATIV S Neo... and whatever Windows Phones Sprint gets in the future, I'll have to buy off contract (which is nothing new to me lol).
I could technically add TEP to my line and wait a few days then do an advanced exchange at a local repair center but I'll most likely get a refurb as most of them are. I'd rather a brand new device
So I'm currently debating using my upgrade...
fgr said:
Just got back from two Sprint stores and a Best Buy with Samsung reps on hand. None of them had access to any means of reflashing to stock, and really had no useful information. I was surprised by how little they knew about any Windows phones.
I do have TEP though, and they ordered me a new phone. I should have it in a few days. Costing me nothing
Wish I had something useful to tell you folks...
Click to expand...
Click to collapse
Did you mention the update to 8.1 or did you just play dumb? I am thinking I am going to have to do the same thing as you but I don't want to walk in there and tell them that I did the update and have them tell me I'm SOL.
ZogJones said:
Did you mention the update to 8.1 or did you just play dumb? I am thinking I am going to have to do the same thing as you but I don't want to walk in there and tell them that I did the update and have them tell me I'm SOL.
Click to expand...
Click to collapse
I was completely honest, gave them the whole story from start to finish. Even pointed out some of the cool features of 8.1 :laugh:
If this was the new Galaxy they might have given me a hard time, who knows.

I cannot get LTE to any APN work right with any custom ROM on the Moto G4 Play. :(

I have the Moto G4 Play (XT1607) (Harpia) and I have decided to flash LineageOS (lineage-14.1-20170131-nightly-harpia-signed.zip) on it using TWRP v3.0.2 r5. After getting it installed I noticed that it was not connecting to my 4g LTE Internet (I have Ting). So I figured I needed to make some changes to the APN settings. So I go to Settings>... More> Cellular Networks and the moment I click on "Cellular networks" I get an error message saying "com.android.phone has stopped". After reflashing and trying again a few times with the same result, I tried using a completely different ROM. AOKP. (aokp_harpia_nougat_nightly_2017-01-31.zip) and I ran into the same exact problem I was having with LineageOS.
I then tried to see if I could force my way into the APN configuration using an app called "Change APN". This worked, but now I see the message "Access Point Name settings are not available for this user". I decided to ignore this and click on the + to create a new APN. After filling the correct info out for Ting APN, I click on "Save"... and it doesn't save at all.
I decided to revert to the stock rom, and everything works perfectly fine with the stock rom. 4G LTE on Ting works fine. Whenever I try using a custom ROM of any kind, I run into the problem I described above. I don't know if I am forgetting to do something, or completely doing something wrong. I could use some help with this guys.
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
Yes. Ting is a Sprint service. Well either way LTE isn't working and the 3G keeps randomly turning on and off whenever I use a custom ROM. However, when I use Stock firmware, everything works perfectly fine. I am unsure what is causing the issue.
It seems nearly all custom ROMs at this point are having data connectivity issues. I'm trying to find a nandroid of the original xt1607 rom so I can just go back until its all sorted out.
mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.
n76 said:
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.
Click to expand...
Click to collapse
I haven't noticed any issue with my GSM ting service on lineage. I get LTE and the WiFi/LTE handoff seems to work. I don't install many apps and don't let them run in the background, so perhaps there's a conflict between them that's shutting down LTE service. This is just a guess.
Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
I looked around in the file system and in /data/data/com.android.phone/ there is no files, no .db files or anything. I don't know of there's supposed to be either. But like OP stated, stock rom is flawless.
Would I be and to copy com.android.phone from stock and restore after flashing? I don't know what to do but this is with every single custom ROM out right now on every release. Data and everything works fine as far as I can tell but just no way to configure the settings. Any help would be greatly appreciated!!!
[email protected] said:
Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
Click to expand...
Click to collapse
Just out of curiosity, have you tried the *22XXX thing yet?
EDIT: Just so we're clear, with you all who have CDMA phones, when you go into "IMEI Information," it does show both an IMEI and an ICCID, right? Because if not, I think I figured out why your LTE isn't working.
I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?
[email protected] said:
I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?
Click to expand...
Click to collapse
It depends on the carrier and the model of the phone. For most Tracfones, it's *22890. For US Cellular, I've seen it as *228 and *22894. You may have to call your carrier and ask what their phone programming code is.
Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)
[email protected] said:
Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)
Click to expand...
Click to collapse
After I posted that, I went back to try and see if Lineage was able to pick up my phone's MEID (even though I use a GSM SIM, the MEID is still tied to the phone hardware). For some reason, Lineage is not reading it, and I think all of your problems are being attributed to that fact.
The way CDMA phones work (and god, do I hate this), is your 2G/3G network is tied to the phone MEID, while the LTE SIM is data only. The OS needs to read both the 14-digit MEID (sometimes shows as a 15 digit IMEI where last digit is 0) as well as the 20 digit ICCID (SIM Number). A phone may also use the SIM number itself as an IMEI (BYOP SIMs do this) by dropping the first five digits of the 20 digit SIM number.
If you phone is showing only one 15 digit number in the system settings, then it's either the MEID OR the SIM, not both. So either you have calling and no LTE, or LTE and no calling. You can't program APN settings because the phone has no idea what ID number to tie APN settings to. This is actually a rather serious conundrum.
Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!
[email protected] said:
Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!
Click to expand...
Click to collapse
I think you just answered your own question. As stated in PCMag back in 2015, "Nobody makes a Dual-Sim phone compatible with Sprint or Verizon." It legitimately believes your MEID is a GSM-based IMEI, and is attempting to cross the streams, so to speak. And the only way your friend's StraightTalk SIM would work is if it was piggybacking off ATT or TMo's networks (the MEID would have been paired to the other phone causing a mismatch).
If you look at the stock ROM for this phone, you will see a BUNCH of system apps for programming Sprint and Verizon network information. They never made it into the custom ROMs we're using. FWIW, here's my thoughts on the matter. Someone needs to go back and make a single-SIM variant of these ROMs, as well as a flashable ZIP containing the necessary APKs for Android to detect the necessary information correctly. And if that doesn't happen, then everyone who bought an XT-1607 has to ditch their carrier and move to a GSM carrier.
That makes complete and total sense! Because I wasn't thinking this while time of it but I was in Oklahoma at the time where the main towers are AT&T, matter of fact Sprint and U.S. Cellular lose almost all signal right when you hit the county line where I was at. Verizon only gets signal because it's Verizon, lol. Reason I say that is because I was wondering why this whole time I has full signal with LTE coverage and completely list everything when I went hone, because where I live is complete opposite, there is hardly any GSM coverage, we don't even have an AT&T store, just Verizon, Sprint, USC.
So, with that being figured out, my laptop just recently kicked the bucket on me so I'm out for the most part, I do have a trick to swap files in and out of a compressed archive without extracting it in any way! But, it takes a while, not too much longer I guess but nowvi just remembered everything is pretty much .dat files so nevermind that.
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.
[email protected] said:
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.
Click to expand...
Click to collapse
IIRC, there is a Verizon thread with 80ish replies, but I think a developer like Squid might need to be made aware of this, so I might copy this into the Lineage thread.
A bit of good news. While reflashing all the time that were force closing when opening cellular networks, I looked in /data/data/com.android.phone/ and was looking, now remember to go back to that directory after I say all this, I found that directory was empty, on all of the Roms. Was curious so I flashed back to stock. Went to the same directory, BOOM! com.android.phone was not empty, in that folder I found 2 folders that were now populated with in:
1: (/files/ )I now had a file named carrierconfig-com.android.carrierconfig- (and after the dash was my ICCID number) so for this directory I need /data/data/com.android.phone/files/carrierconfig-com.android.carrierconfig**ICCID** (replace **ICCID** my ICCID number)
2: then there was this /data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
and
phone/shared_prefs/com.android.phone_preferences.xml
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.
[email protected] said:
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.
Click to expand...
Click to collapse
That is definitely a major find! My only concern is even if you do that, there might be further missing components that would cause Dialer to crash on startup or some other wacky side effect. However, if you can make it work, then it's possible the proper APN settings will load by default and you'll no longer need to change them.
If you can, go into the System Apps on the stock ROM and look for any APKs branded by/with Sprint, VZW or USCellular, or anything CDMA related. They might be necessary for reading the SIM's ICCID.
That's what I was thinking too, and sadly for me I don't really know EVERYTHING to look for so it'll be mostly out of trial and error for me to figure it out. I wish they didn't compress Roms into .dat so I could use a root explorer to swap between tabs rather than copy, flash the rom, paste files and then if that didn't work start all over on restoring stock, so on and so forth. I miss my laptop. =(
Updates?
Has anyone looked into this further? I'm experiencing the same problem with the latest LineageOS nightly. US Cellular Prepaid with an XT1607.
I noticed that in my case i had to skip the Insert Sim thing on 1st boot. It never did whatever it wanted to there. (Maybe because I have no signal or weak roaming where I live?)
I'm seriously considering trying it from an area that I have good service in..

Galaxy S5/Galaxy Note 3 Sprint help thread

The point of this thread is to have a general place for Sprint folks to help each other out.
I started it because I saw a lot of the same information getting repeated in the S5 thread.
I'll be keeping a list of a few tips and tricks to help get your Sprint S5/Note 3 working as best as it possibly can, and hopefully explain it in a straightforward matter.
If anyone has other suggestions of what should go here, please let me know.
Common problems:
1. LTE isn't working
Possible solutions:
1. Your network provisioning got weird somehow. Flash stock, update your PRL, update your Profile, and then flash Lineage again
2. Your sim card is very old, and we no longer have hacks to support it. Get a new one off eBay, and follow steps in solution 1 for provisioning. See list of working SIM cards below
2. Other network service isn't working
Possible solutions:
1. Your network provisioning got weird somehow. Flash stock, update your PRL, update your Profile, and then flash Lineage again
3. Phone is bouncing between network types
Possible solutions:
1. Try making a standard voice call, to force it to CDMA or EvDO, to help stabilize the connection
4. Voicemail notifications don't show
Disclaimer: Known bug, will not be fixed. This is because sometimes voicemail read signals don't get cleared properly in Sprint's system, so they show forever.
Possible workarounds:
1. Manually call voicemail whenever you get a missed call
2. Use Google Voice and forward calls and texts to a dummy number on your phone instead, or use Sprint's Google Voice integration
General Tips:
1. Don't mess with preferred network settings, I set them specifically to work properly on Sprint
Known working SIM cards:
SIMOLW216R
Known not working SIM cards:
SIMGLW206R
I have a G900P with Virgin Mobile. I wanted to provide some info on the bouncing between GSM-CDMA issue. Today I wiped three times and flashed three builds (LineageOS 10/25, 11/1, and crDroid 10/26 based on LOS 10/25). In all three times, after wiping and flashing roms, I would see the phone bouncing CDMA-GSM when switching between preferred network types. Then I would dirty flash the same ROM (only the rom, nothing else), it seemed like this issue goes away and the phone is VERY stable. I will wipe again to see if I can keep replicating this phenomenon. You guys can try to dirty flash to see if it also fixes the LTE connection issue (nothing to lose). I saw it a few times but I couldn't see a pattern, and now that I have been switching preferred network types several times over the last few hours, I have not seen it anymore. I will keep testing.
The G900P radio issue has been going on forever. its almost as bad as the timezone bug we have had forever.
install rand g900p cyanogenmond/lineage rom.... go through install..... deal with phone trying to escape into wrong carrier or frequency... pray it remains stable for work.... post logcat hoping for fix..... repeat for several years with no avail......
eurohunter said:
I have a G900P with Virgin Mobile. I wanted to provide some info on the bouncing between GSM-CDMA issue. Today I wiped three times and flashed three builds (LineageOS 10/25, 11/1, and crDroid 10/26 based on LOS 10/25). In all three times, after wiping and flashing roms, I would see the phone bouncing CDMA-GSM when switching between preferred network types. Then I would dirty flash the same ROM (only the rom, nothing else), it seemed like this issue goes away and the phone is VERY stable. I will wipe again to see if I can keep replicating this phenomenon. You guys can try to dirty flash to see if it also fixes the LTE connection issue (nothing to lose). I saw it a few times but I couldn't see a pattern, and now that I have been switching preferred network types several times over the last few hours, I have not seen it anymore. I will keep testing.
Click to expand...
Click to collapse
I'll add the suggestion to not mess with preferred network types, I set the default to what is ideal for Sprint. Did you dirty flash the ROMs over themselves? or over an older version?
TomNeverwinter said:
The G900P radio issue has been going on forever. its almost as bad as the timezone bug we have had forever.
install rand g900p cyanogenmond/lineage rom.... go through install..... deal with phone trying to escape into wrong carrier or frequency... pray it remains stable for work.... post logcat hoping for fix..... repeat for several years with no avail......
Click to expand...
Click to collapse
I aim to improve that, at least a little bit. The stability has improved, from the feedback I've been getting. The timezone bug was fixed a long time ago as well, in May iirc (and it wasn't just Sprint, T-Mobile US and AT&T had it too)
The network for sprint devices using; lineage-14.1-20171108-nightly-kltedv-signed is definitely better so far.
Sounds like you guys on sprint have some issues still ... I am running my g900p on att .... Works great i dont think i get full 4glte but i still average2-3 megs a second so its definitely not bad ... Fair trade off i guess.
pinheaD420 said:
Sounds like you guys on sprint have some issues still ... I am running my g900p on att .... Works great i dont think i get full 4glte but i still average2-3 megs a second so its definitely not bad ... Fair trade off i guess.
Click to expand...
Click to collapse
I would imagine the LTE bands AT&T uses don't line up with Sprint's. I have similar issues on my G900F on T-Mobile, I frequently see H+/3G/E when I should have LTE.
As for Sprint issues, yeah, but it's a lot more manageable now. Most of the weird bugs/quirks are now just fixed by getting provisioning on stock, or a new sim card.
I always heard about what a PITA sprint was, and imagine it worked like crap then, but it's not too bad now. I still prefer T-Mobile, for various minor reasons,
but my hltespr on Tello (Sprint MVNO) makes a perfectly usable backup phone if anything goes wrong with my T-Mobile sim, and it wouldn't
really bother me to use it. That's pretty much my main goal: Make Sprint as usable as possible, so the user doesn't need to notice they're on Sprint.
javelinanddart said:
I would imagine the LTE bands AT&T uses don't line up with Sprint's. I have similar issues on my G900F on T-Mobile, I frequently see H+/3G/E when I should have LTE.
As for Sprint issues, yeah, but it's a lot more manageable now. Most of the weird bugs/quirks are now just fixed by getting provisioning on stock, or a new sim card.
I always heard about what a PITA sprint was, and imagine it worked like crap then, but it's not too bad now. I still prefer T-Mobile, for various minor reasons,
but my hltespr on Tello (Sprint MVNO) makes a perfectly usable backup phone if anything goes wrong with my T-Mobile sim, and it wouldn't
really bother me to use it. That's pretty much my main goal: Make Sprint as usable as possible, so the user doesn't need to notice they're on Sprint.
Click to expand...
Click to collapse
Totally appreciate the efforts and this thread.
For me, you called it, by the way. Old-ass SIM card.
meatfest1974 said:
Totally appreciate the efforts and this thread.
For me, you called it, by the way. Old-ass SIM card.
Click to expand...
Click to collapse
Just to update, everything worked out well!
Upon replacing the old SIM with a new one, I still couldn't get past 3G. I flashed to stock CQD1 in Odin, updated the PRL and profile, ##72786# to reset, and still nothing.
After a few Google searches, a few forums suggested to call into Virgin Mobile to update the SIM's ICCID number, because this is the reason I couldn't get LTE; the ICCID didn't match the SIM card they had on file. Once done and after a final reboot back into stock, LTE success!
Flashed TWRP in Odin and restored a recent lineageOS backup, and LTE success!
Again, this board was very helpful, thanks!
Just ordered a new SIM card from Sprint. The old one showed as incompatible according to OP. I could only get 3G if I changed to CDMA/EVDO.. Hopefully the new one will allow me to run LOS 14.1 with access to LTE on TING. Thanks for the info.
@javelinanddart Hi, would you mind taking a look at this radio log from 15.1? I can't get LTE working under any circumstances. I have the latest baseband for G900P and a good SIM card, and everything was working in 14.1. Log shows switching from "CDMA/EvDo" to "CDMA/EvDo + LTE" then setting the APN to FreedomPop LTE.
javelinanddart said:
General Tips:
1. Don't mess with preferred network settings, I set them specifically to work properly on Sprint
Click to expand...
Click to collapse
hmmm
where are your files ?
don't say
https://github.com/javelinanddart/
because i just spent 15 min looking at everything there and could find nothing specific to G900P
a1yet said:
G900P
Click to expand...
Click to collapse
I imagine its buried deep, around about here:- https://review.lineageos.org/#/q/status:merged+project:LineageOS/android_device_samsung_klte-common+branch:cm-14.1+topic:klte-oss-ril
fitittome said:
I imagine its buried deep, around about here
Click to expand...
Click to collapse
thank you very much
Ohhh good Joke LOL .. had me going there, I really thought you were trying to help.. till I spent another 5-10 min looking around at gibberish
thanks a lot
PS: i'm not mad .. i can appreciate a good joke
i think i'll wait tile the OP tells me where i can download his ROM
OR
find one in the S5 sprint thread on this site
a1yet said:
i think i'll wait tile the OP tells me where i can download his ROM
Click to expand...
Click to collapse
It's the official LineageOS kltedv.
fitittome said:
It's the official
Click to expand...
Click to collapse
then i thank you again
i see the files now that i failed to find on my own
thank you
Couchy said:
@javelinanddart Hi, would you mind taking a look at this radio log from 15.1? I can't get LTE working under any circumstances. I have the latest baseband for G900P and a good SIM card, and everything was working in 14.1. Log shows switching from "CDMA/EvDo" to "CDMA/EvDo + LTE" then setting the APN to FreedomPop LTE.
Click to expand...
Click to collapse
Well, If you come back to this, let me know if you need more logs. I'm going back to 14.1 for now, as the signal is really bad (Keeps switching between 1X and 3G).
Edit: 14.1 is now borked as well... Some relatively recent change must have killed it.
And here's a log from when 3G/EvDo craps out...
Sorry for the multi-post, but I just found my problem: The default APN settings for FreedomPop, the MVNO I use, are somehow wrong. So I deleted that APN and redid it with the following settings and was able to get LTE.
Name: FreedomPop LTE
APN: n.f6.ispsn
MMSC: http://mms.sprintpcs.com
MMS proxy: 68.28.31.7
MMS port: 80
MCC: 310
MNC: 120
APN type: default,mms,supl,hipri,fota,ims,cbs
APN (roaming) protocol: IPv4/IPv6
Bearer: Unspecified
MVNO type: None
Couchy said:
Sorry for the multi-post, but I just found my problem: The default APN settings for FreedomPop, the MVNO I use, are somehow wrong. So I deleted that APN and redid it with the following settings and was able to get LTE.
Name: FreedomPop LTE
APN: n.f6.ispsn
MMSC: http://mms.sprintpcs.com
MMS proxy: 68.28.31.7
MMS port: 80
MCC: 310
MNC: 120
APN type: default,mms,supl,hipri,fota,ims,cbs
APN (roaming) protocol: IPv4/IPv6
Bearer: Unspecified
MVNO type: None
Click to expand...
Click to collapse
Sorry for the delay, I've been busy working on another device. I had the same issue (even though it worked fine before) on my hltespr. After a wipe, my LTE started working again too, which was really weird. I don't really want to investigate this, since it's working now.

Verizon Essential stuck in 3G after the upgrade

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.

Categories

Resources