Related
I've got the Moto X GSM developers edition with Kitkat 4.4 unlocked and rooted. I am on H2O wireless (AT&T MVNO). I've had this setup for about a month.
At least several times a day, I'll hear a quick beep in my bluetooth headset alerting me to the fact that I have no mobile signal. I look at the phone and I have zero bars for maybe 30 seconds and then it goes back to (usually) 4 bars. This happens at home, where I always seem to have 4 bars except for these incidents, so it is not like I am in a marginal signal area and it is going between 1 and 0 bars. It also happens when driving around Portland OR on the major freeways. It doesn't happen in the same spots, so I don't think I am driving through a weak signal area. If I'm driving around it happens more often than when I am at home - maybe 10 or more times on a two hour trip.
At least four times I have been driving and the phone kept dropping signal and getting it back maybe 8 or 10 times until it finally lost the signal for good. I powered off and on and then the signal was fine. Once I left the phone on after the signal had dropped out completely until I stopped driving and was in an area that I know that I have had good signal strength before. I left the phone on for at least 10 minutes and the signal would not come back until I power cycled the phone.
Searching here and with google, I couldn't find reports of signal problems like this with the Moto X. So I'm guessing that this isn't some problem endemic to the Moto X. I can't believe that this is normal behavior for a phone on the AT&T network (I just ported from Page Plus on Verizon towers when I got the Moto X and I never got signal dropouts). Could there be something faulty in my phone? Should I try to get a warranty exchange from Motorola? Or is there anything else I can do to debug/fix the problem? Thanks.
There's a reflash toolkit around here. Use it. It fixed a similar issue I was having
MotoX Developer Edition
When you say you ported from page plus, do you mean you are using a verizon moto x on H2O?
If so that could be part of your problem. However, i was having an issue where my Verizon moto x wouldn't connect to 3G on Verizon. It would go from LTE to 1x. I factory reset and it didn't fix it.
Ultimately before I returned it to moto I tried a sbf to 4.2.2 and then accept the ota for 4.4. and that fixed my problems.
All the files for flashing back to 4.2.2 are in the Dev section. Just be sure to backup anything that is important to you. All data will be deleted.
Sent from my XT1060 using Tapatalk
mawells787 said:
When you say you ported from page plus, do you mean you are using a verizon moto x on H2O?
If so that could be part of your problem. However, i was having an issue where my Verizon moto x wouldn't connect to 3G on Verizon. It would go from LTE to 1x. I factory reset and it didn't fix it.
Ultimately before I returned it to moto I tried a sbf to 4.2.2 and then accept the ota for 4.4. and that fixed my problems.
All the files for flashing back to 4.2.2 are in the Dev section. Just be sure to backup anything that is important to you. All data will be deleted.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
No, I don't have the Verizon Moto X, as I said, I have a GSM developers edition Moto X. I was just mentioning Page Plus as my previous experience with never seeing any dropped service. I don't have any previous experience with AT&T towers, so I don't know what might be normal for them. I know coverage is not as good as Verizon in my area, but I can't believe what I am seeing is normal.
I think you are talking about data service, am I right? I am not talking about data, I am talking about problems with voice/text service. I could try going back to 4.2.2 and then taking the OTA, but that is basically the path I took to get where I am now, so I'm not too hopeful that it would change anything.
Same problem here /:
Just wanted to add some info here, experiencing the same issue unfortunately.
GSM Unlocked Moto X 16GB, running off MVNO Straight Talk AT&T LTE.
I'll have several instances where I won't be able to send texts. Every time it bounces back with a "Failure to send SMS" error, and I'll notice that the signal strength will fluctuate rapidly from 0-3 bars. Data works fine, but texts don't send
Had it happen at school, AT&T service is great there. Gonna try it with my Optimus G tomorrow and report back to confirm if it's a device issue.
UPDATE: Moto X issue. Going to call them for a moto maker replacement.
Carbon Trooper said:
UPDATE: Moto X issue. Going to call them for a moto maker replacement.
Click to expand...
Click to collapse
What issue did they say it was? Had this happen twice randomly in 2 weeks, but no sure if it's the phone or the network - otherwise signal has been great.
Ckryt said:
What issue did they say it was? Had this happen twice randomly in 2 weeks, but no sure if it's the phone or the network - otherwise signal has been great.
Click to expand...
Click to collapse
They didn't give me any details I just got to order a new one for free, and they'll take a look at the old Moto X when they get it. Hopefully the new one doesn't do this crazy stuff.
If any issues come up, i'll just return it. Don't see a bright future for Motorola anyways...
johninor said:
I've got the Moto X GSM developers edition with Kitkat 4.4 unlocked and rooted. I am on H2O wireless (AT&T MVNO). I've had this setup for about a month.
At least several times a day, I'll hear a quick beep in my bluetooth headset alerting me to the fact that I have no mobile signal. I look at the phone and I have zero bars for maybe 30 seconds and then it goes back to (usually) 4 bars. This happens at home, where I always seem to have 4 bars except for these incidents, so it is not like I am in a marginal signal area and it is going between 1 and 0 bars. It also happens when driving around Portland OR on the major freeways. It doesn't happen in the same spots, so I don't think I am driving through a weak signal area. If I'm driving around it happens more often than when I am at home - maybe 10 or more times on a two hour trip.
At least four times I have been driving and the phone kept dropping signal and getting it back maybe 8 or 10 times until it finally lost the signal for good. I powered off and on and then the signal was fine. Once I left the phone on after the signal had dropped out completely until I stopped driving and was in an area that I know that I have had good signal strength before. I left the phone on for at least 10 minutes and the signal would not come back until I power cycled the phone.
Searching here and with google, I couldn't find reports of signal problems like this with the Moto X. So I'm guessing that this isn't some problem endemic to the Moto X. I can't believe that this is normal behavior for a phone on the AT&T network (I just ported from Page Plus on Verizon towers when I got the Moto X and I never got signal dropouts). Could there be something faulty in my phone? Should I try to get a warranty exchange from Motorola? Or is there anything else I can do to debug/fix the problem? Thanks.
Click to expand...
Click to collapse
Carbon Trooper said:
Just wanted to add some info here, experiencing the same issue unfortunately.
GSM Unlocked Moto X 16GB, running off MVNO Straight Talk AT&T LTE.
I'll have several instances where I won't be able to send texts. Every time it bounces back with a "Failure to send SMS" error, and I'll notice that the signal strength will fluctuate rapidly from 0-3 bars. Data works fine, but texts don't send
Had it happen at school, AT&T service is great there. Gonna try it with my Optimus G tomorrow and report back to confirm if it's a device issue.
Click to expand...
Click to collapse
Ckryt said:
What issue did they say it was? Had this happen twice randomly in 2 weeks, but no sure if it's the phone or the network - otherwise signal has been great.
Click to expand...
Click to collapse
Just mentioning I have the XT 1053 and have replaced it 2 times. All had the issue mentioned. Some worse than others. I never rooted or done anything to my phone I'm currently testing 4.2.2 since 4.4 and 4.4.2 have been giving me the problem. I'll update if I notice anything.
Also a whole thread here of people are having the same issue:
http://forums.androidcentral.com/moto-x/348535-i-love-my-moto-x-but.html
Someone should reach out to the Motorola engineers on G+ they usually respond pretty fast!
drago10029 said:
Just mentioning I have the XT 1053 and have replaced it 2 times. All had the issue mentioned. Some worse than others. I never rooted or done anything to my phone I'm currently testing 4.2.2 since 4.4 and 4.4.2 have been giving me the problem. I'll update if I notice anything.
Also a whole thread here of people are having the same issue:
http://forums.androidcentral.com/moto-x/348535-i-love-my-moto-x-but.html
Someone should reach out to the Motorola engineers on G+ they usually respond pretty fast!
Click to expand...
Click to collapse
Thanks for the link - I didn't find that thread when I was searching around to see if other people were having the problem.
I am still having the problem. How often it happens each day varies a lot. Some days it hardly happens at all and others it will happen dozens of times. I just installed 4.4.2 a few days ago, so it hasn't been long enough to tell if it has improved with the update. It has happened only a few times since I updated.
This happened to me a few times....only when I was leaving lte and going to 3g. The phone seemed to hang a bit switching over from lte to h+.
I'm thinking if I lived in an area where it switched back and forth a lot, I'd have a real problem. Probably unless a better fix comes along....forcing 3g only would solve it. Though that would be pretty crappy.
Thats what I noticed in my case anyway.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
The x is a msm8960 too. http://forum.xda-developers.com/showpost.php?p=43152766&postcount=1
aviwdoowks said:
The x is a msm8960 too. http://forum.xda-developers.com/showpost.php?p=43152766&postcount=1
Click to expand...
Click to collapse
the link you posted was in russian and google wouldn't translate it.
drago10029 said:
the link you posted was in russian and google wouldn't translate it.
Click to expand...
Click to collapse
It only confirms my claims in my op.
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
If a Rsd restore solves your moto x 4g problems then we have more confirmation.
aviwdoowks said:
It only confirms my claims in my op.
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
If a Rsd restore solves your moto x 4g problems then we have more confirmation.
Click to expand...
Click to collapse
*#*#4636#*#* OR the Play apps: Phone Info will break the radio IF you select the 3 dots and mess with the band!!
RSD flash or Matts utility is the only fix. Flash of a new radio did not work.
Click to expand...
Click to collapse
Also if you're referring to the above as a fix, I never messed with "phone info' settings and the problem was always apparent even fresh from the factory! :/
drago10029 said:
Also if you're referring to the above as a fix, I never messed with "phone info' settings and the problem was always apparent even fresh from the factory! :/
Click to expand...
Click to collapse
Obviously it is likely to be HW then. Yet Rsd restore may fix it.
aviwdoowks said:
Obviously it is likely to be HW then. Yet Rsd restore may fix it.
Click to expand...
Click to collapse
If it did fix it, then it sure wouldn't be hardware related, but that would be interesting. And it is suspect that only some people are having this issue and others aren't unless other people just aren't reporting it. So many thoughts lol
My wife's phone was having this issue. Would just drop cellular connection. You could make it happen by running a speedtest, as soon as it hit the upload part of the test it would drop all connectivity and a few seconds later it would reconnect. I waited for 4.4.2 to be pushed and that didn't fix it so I waited for the .sbf to flash it clean to 4.4.2 which didn't help either. I swapped her SIM in to my Moto X and it worked without issue.....putting it back in her Moto X and constant drops of cellular connectivity.
I finally had Motorola issue me an RMA to send it back for repairs. They were going to swap it out for new but when they realized it was a Developer Edition they said it had to be repaired. It's been with Motorola for two weeks so far with no info from them on what's going on. Very disappointed in their service so far. Apparently Motomaker versions get handled much faster than Developer Editions.
tcrews said:
My wife's phone was having this issue. Would just drop cellular connection. You could make it happen by running a speedtest, as soon as it hit the upload part of the test it would drop all connectivity and a few seconds later it would reconnect. I waited for 4.4.2 to be pushed and that didn't fix it so I waited for the .sbf to flash it clean to 4.4.2 which didn't help either. I swapped her SIM in to my Moto X and it worked without issue.....putting it back in her Moto X and constant drops of cellular connectivity.
I finally had Motorola issue me an RMA to send it back for repairs. They were going to swap it out for new but when they realized it was a Developer Edition they said it had to be repaired. It's been with Motorola for two weeks so far with no info from them on what's going on. Very disappointed in their service so far. Apparently Motomaker versions get handled much faster than Developer Editions.
Click to expand...
Click to collapse
Yeah it's true Moto maker phone's just get replaced! no questions asked. You ask me their warranty needs work! Also I've tried 4.2.2 and 4.4. Using wifi on and off and nothing has fixed the issue for me. I told them about the issue and got my refund. This is a problem and should be fixed.
This phone would be great if it didn't have camera issues and the MMS and LOS bug I hope you get it fixed. otherwise, let Moto know, be aggressive in your point, speak to a supervisor and get your money back! Best of luck to you.
It's a known 4.4.2 issue that's supposed to be fixed with the 4.4.3 update, among other things. Some of the fixes are Nexus 5 specific, while others are shared issues. I'm currently experiencing the data drop outs frequently, tried everything without luck.
LINK
Hey folks,
I'm wondering with all the recent monthly builds that Google has been releasing, what build # my Verizon Nexus 6 should be on. Currently, it's on LMY48M but it's been acting really strange. Text messages won't always go through, sometimes half of my wallpaper disappears, and the phone's settings don't always work.
By phone settings, I mean I'll be in a setting page like accounts, trying to change the sync settings for my accounts and it won't let me choose a specific account to manage the sync settings. It's weird.
I'm not sure what's happening, or if it's just the build # that's wrong. I'm also rooted and unlocked, but using stock kernel and stock build.
My Nexus 6 is unlocked and rooted using WugFresh Toolkit, and I bought the device straight from Google about a year ago.
Thanks!
P.S. If anyone knows what I can do, Enhanced 4G LTE does not work on my phone at all. People cannot hear me, and calls are dropped all the time. I've had to turn that off. Any suggestions on how to get that working would be greatly appreciated too! I'm not sure if this is related to my radios or not.
Many thanks folks.
NexusReach said:
Hey folks,
I'm wondering with all the recent monthly builds that Google has been releasing, what build # my Verizon Nexus 6 should be on. Currently, it's on LMY48M but it's been acting really strange. Text messages won't always go through, sometimes half of my wallpaper disappears, and the phone's settings don't always work.
By phone settings, I mean I'll be in a setting page like accounts, trying to change the sync settings for my accounts and it won't let me choose a specific account to manage the sync settings. It's weird.
I'm not sure what's happening, or if it's just the build # that's wrong. I'm also rooted and unlocked, but using stock kernel and stock build.
My Nexus 6 is unlocked and rooted using WugFresh Toolkit, and I bought the device straight from Google about a year ago.
Thanks!
P.S. If anyone knows what I can do, Enhanced 4G LTE does not work on my phone at all. People cannot hear me, and calls are dropped all the time. I've had to turn that off. Any suggestions on how to get that working would be greatly appreciated too! I'm not sure if this is related to my radios or not.
Many thanks folks.
Click to expand...
Click to collapse
first off, what build you are on has absolutely nothing to do with your issues, nothing at all. your issues are caused by your use of the phone(most likely). by your use i mean what apps you install and use, what mods you make to your device, etc. and you need to turn on enhanced lte in your phone and in your verizon settings, its called Volte(voice over lte). personally, id factory reset and start all over again. oh, and do some research about your nexus 6. itll be beneficial to you. i know you didnt do research about your device(at least not enough) because of your use of the toolkit. you should never use a toolkit the first time you root a nexus because you will learn nothing. doing it the right way, takes 3-5 minutes once you learn, and you get to learn stuff about your device. afyer doing it right the first time, next time you can use toolkits.
simms22 said:
first off, what build you are on has absolutely nothing to do with your issues, nothing at all. your issues are caused by your use of the phone(most likely). by your use i mean what apps you install and use, what mods you make to your device, etc. and you need to turn on enhanced lte in your phone and in your verizon settings, its called Volte(voice over lte). personally, id factory reset and start all over again. oh, and do some research about your nexus 6. itll be beneficial to you. i know you didnt do research about your device(at least not enough) because of your use of the toolkit. you should never use a toolkit the first time you root a nexus because you will learn nothing. doing it the right way, takes 3-5 minutes once you learn, and you get to learn stuff about your device. afyer doing it right the first time, next time you can use toolkits.
Click to expand...
Click to collapse
Thanks for the advice. I've been a long time flasher with my Galaxy Nexus which I had for 3 years. Flashed a ton of different ROMs, radios, kernels, the whole shebang. I could learn more about my device, so I'll certainly take that into consideration. I asked about which build I should be on because I've read that the build # you need for your Nexus 6 depends entirely on your carrier. Some build #'s are designed for T-Mobile, some are designed for AT&T, and some are designed for Verizon or Project Fi. It get's really, really confusing trying to keep track of which build goes with which carrier, which is why I'm asking if I got it right or not.
I know how to turn on enhanced LTE, but when I do, nothing works. No one can hear me, calls are dropped, and it just doesn't work. When I turn it off, everything is fine. It's very possible it could be my one little area where I'm at (in Salt Lake City), but wanted to know if I was having issues because of flashing the wrong radio or something. I used the toolkit for that as well.
Perhaps all my issues come from using the toolkit, and I'll definitely take responsibility for that. I've never had issues using it though and I've been doing this for years without any problems.
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
HueyT said:
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I'm already unlocked, rooted, TWRP'd and using the PureNexus that came out end of april (I haven't flashed the one in may yet). I believe I'm also currently using the latest radio and latest bootloader.
Edit - I actually was not on the most recent radio, but I did flash that, no change.
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
In others countries we don't get the same bands management, then I can't say anything about LTE.
But I'm on PureNexus 7.1.1 and I get the same "issue" about network droppin when calling. When the call starts, my phone turns into don't disturb-mode and recover the network only when the phone call ends.. It doesn't really cut my network connection, but it looks like. It may be rom settings.
However I don't care as long as everything works good, it's just an icon. (how a phone call can be done while network is shutted off ^^)
When I was on the stock ROM, this autumn, 7.1 version of Android did the same thing, loosing data connection while being still connected to the network (but at anytime not just phonecalls). Finding it back some minutes later. That was fixed with 7.1.1. Stock.
Hope that might help you (looks not ) if it's the same problem. May be give an eye to the Rom settings..
Have you tried if your device do the same thing with an another Rom ? (stock for example)
Larzzzz82 said:
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Click to expand...
Click to collapse
I knew something looked like it was missing. I don't have any enhanced 4g LTE settings in that section. Normally there's a tick box to turn it on there. It's missing. Is that due to them not having it turned on in my account?
Also for everyone else, this problem only started when I tried the whole at&t switch. I was on this rom when I switched and it worked fine before then. I didn't factory reset since then though, wondering if I need to try that.
zelendel said:
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Click to expand...
Click to collapse
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
BlockOfDynamite said:
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
Click to expand...
Click to collapse
I think i'm going to reflash my rom today. I did the modem, twrp is up to date, bootloader is fine. I did the reset network settings (I was sure that was going to fix it, no dice). So I'm going to reflash the rom today and see if that fixes it. After that I have no idea what is left to try other than reverting to stock, which I'd like to avoid.
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Larzzzz82 said:
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Click to expand...
Click to collapse
How do you enter the hidden menu on the n6? I thought I found it but it wasn't working.
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Larzzzz82 said:
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Click to expand...
Click to collapse
I got in, VoLTE was not ticked. I ticked it. I got the setting for it then in settings. But making a phone call gave me an error. I rebooted, and it's not ticked now. So does that mean I need to call Verizon to have them flag my account?
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Larzzzz82 said:
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Click to expand...
Click to collapse
That did the trick. All fixed. Thank you! That was driving me nuts. I never considered the idea that the setting would be turned off . But since I did leave and come back...
Thanks again!
Glad you're all set. ?
Anyone else running the G5S+ on Sprint? It's working fairly well for me other than a couple of IPv6/IPv4 connection issues. However, is it normal for Cellular network settings to not include any kind of APN settings/options? We have six different devices on our family Sprint account -- Nexus 6, Samsung Galaxy S5 Active, Samsung Galaxy S3, iPhone 7, iPhone 6+, and now the G5S+. All of the other devices have a way to edit the APN settings, even when running the stock, unrooted ROM. I'm waiting to root my G5S+ until after an official Oreo update. Is this a limitation of the stock ROM?
My concern is mostly for when I travel out of the country. I know from past experience I'll need to be able to select the proper APN to get the best connectivity, but I've also needed to select the correct APN locally sometimes like when my phone(s) freak out and only connect to the CDMA_0 APN so I'm stuck on 3G.
internetpilot said:
Anyone else running the G5S+ on Sprint? It's working fairly well for me other than a couple of IPv6/IPv4 connection issues. However, is it normal for Cellular network settings to not include any kind of APN settings/options? We have six different devices on our family Sprint account -- Nexus 6, Samsung Galaxy S5 Active, Samsung Galaxy S3, iPhone 7, iPhone 6+, and now the G5S+. All of the other devices have a way to edit the APN settings, even when running the stock, unrooted ROM. I'm waiting to root my G5S+ until after an official Oreo update. Is this a limitation of the stock ROM?
My concern is mostly for when I travel out of the country. I know from past experience I'll need to be able to select the proper APN to get the best connectivity, but I've also needed to select the correct APN locally sometimes like when my phone(s) freak out and only connect to the CDMA_0 APN so I'm stuck on 3G.
Click to expand...
Click to collapse
There should be, even on stock. Might be a problem with the sim - contact Sprint for help
Phazmos said:
There should be, even on stock. Might be a problem with the sim - contact Sprint for help
Click to expand...
Click to collapse
Oh, I already have contacted Sprint several times, and had the SIM switched out 3x now. This is a different type of Sprint SIM than I had in my Nexus 6. I think it's probably going to require root and modifying the build.prop or even a custom ROM, which I don't really want to do until the Oreo OTA comes out or at least a much more stable custom ROM than what we have now for this phone.
The Sprint network has gotten a little weird. First this new 3-in-one SIM, which seems to have locked-down APN settings, and then this phone also only has an IPv6 IP#, which is causing a couple problems with monitoring my IP security cameras at both my homes (neither of my ISP's are fully on IPv6 yet), but also even Google Weather and the Android Wear Play Store won't connect on my Asus ZenWatch 3 paired through this phone and only using mobile data. If I connect the phone to wifi (anywhere -- home, public, etc.), the IP cameras, Google Weather, and Wear Play Store all work fine. It's just bizarre that Sprint isn't running a dual stack IPv4/IPv6 network until everything is IPv6. Most things work fine on my phone -- regular Play Store, Netflix, all social media, and even TeamViewer and Plex, which both are hosted the same IPv4 networks that have the IPv4 security cameras . I guess it's because all these other services are running some kind of dual stack configuration at their end, but I'm very surprised that Google Weather and the Wear Play Store apparently is not.
I've yet to find anyone else who is using this phone on Sprint to confirm that they're encountering the same thing I am.
internetpilot said:
Oh, I already have contacted Sprint several times, and had the SIM switched out 3x now. This is a different type of Sprint SIM than I had in my Nexus 6. I think it's probably going to require root and modifying the build.prop or even a custom ROM, which I don't really want to do until the Oreo OTA comes out or at least a much more stable custom ROM than what we have now for this phone.
The Sprint network has gotten a little weird. First this new 3-in-one SIM, which seems to have locked-down APN settings, and then this phone also only has an IPv6 IP#, which is causing a couple problems with monitoring my IP security cameras at both my homes (neither of my ISP's are fully on IPv6 yet), but also even Google Weather and the Android Wear Play Store won't connect on my Asus ZenWatch 3 paired through this phone and only using mobile data. If I connect the phone to wifi (anywhere -- home, public, etc.), the IP cameras, Google Weather, and Wear Play Store all work fine. It's just bizarre that Sprint isn't running a dual stack IPv4/IPv6 network until everything is IPv6. Most things work fine on my phone -- regular Play Store, Netflix, all social media, and even TeamViewer and Plex, which both are hosted the same IPv4 networks that have the IPv4 security cameras . I guess it's because all these other services are running some kind of dual stack configuration at their end, but I'm very surprised that Google Weather and the Wear Play Store apparently is not.
I've yet to find anyone else who is using this phone on Sprint to confirm that they're encountering the same thing I am.
Click to expand...
Click to collapse
I'm glad I never used Sprint, mainly cuz I've heard of so many problems with them over the years, and where I am it's basically att or Verizon if ya want any kind of coverage (rural + mountains = shirty cell coverage). Did you get the phone from Sprint? I'm wondering if it's locked down for Sprint - last time I used a locked down device was about 6 years ago. I always thought apns were handled by the os, but if it's locked down, it could be handled by the sim. Now I'm curious - what would happen if you popped in a sim from one of those other devices that do work?
Unlock, root and roms - not many available right now (new devices always take a while - especially if uptake is slow), but what's out there now are pretty much stable enough for daily use. This device is supposed to get Oreo, but probably not till sometime next year (I'm not running it yet but only cuz the features I want aren't there yet). Ipv6 implementation - lol - I've worked with a few network engineers over the years and when the talk of ipv6 started up, they went crazy. Implementing it, even on a small scale isn't an easy thing, imagine on a nation wide, or world wide scale. It started about 5 years ago, and it'll probably take another 5+ before everything is compatible. Anyway, I ramble - good luck , I do hope it gets sorted out for ya!
Phazmos said:
I'm glad I never used Sprint, mainly cuz I've heard of so many problems with them over the years, and where I am it's basically att or Verizon if ya want any kind of coverage (rural + mountains = shirty cell coverage). Did you get the phone from Sprint? I'm wondering if it's locked down for Sprint - last time I used a locked down device was about 6 years ago. I always thought apns were handled by the os, but if it's locked down, it could be handled by the sim. Now I'm curious - what would happen if you popped in a sim from one of those other devices that do work?
Unlock, root and roms - not many available right now (new devices always take a while - especially if uptake is slow), but what's out there now are pretty much stable enough for daily use. This device is supposed to get Oreo, but probably not till sometime next year (I'm not running it yet but only cuz the features I want aren't there yet). Ipv6 implementation - lol - I've worked with a few network engineers over the years and when the talk of ipv6 started up, they went crazy. Implementing it, even on a small scale isn't an easy thing, imagine on a nation wide, or world wide scale. It started about 5 years ago, and it'll probably take another 5+ before everything is compatible. Anyway, I ramble - good luck , I do hope it gets sorted out for ya!
Click to expand...
Click to collapse
No, it's a carrier independent unlocked phone that I bought from BestBuy.com (because they offered the best price for the 64gb version through a Cyber Monday sale). Except for the iPhone (and maybe the newer Samsung models), Sprint phones don't have removable SIMs -- they're built-in to the phone making them a special Sprint-only phone. That's the way my Samsung Galaxy Note 2 was. After my Note 2, I bought an unlocked Google (Motorola) Nexus 6 and used a SIM to use it on Sprint (and had access to APN setting as soon as I activated the phone), but that SIM isn't compatible with the G5S+ even though they're both Motorola phones, have the same radios, etc. I'm pretty sure my current problem is the SIM, but I don't think it's unsolvable. I just think I'll need to root and mod or ROM the device to get access to those settings. I know this is one of Sprint's newest SIMs (they have like 22 different SIMs), so I'm sure this is just another attempt by Sprint to lock down unlocked carrier independent phones on their network to help reduce excessive roaming (on Verizon towers) which costs Sprint money.
I've been on Sprint for like 15 years. The only reason I stayed on them is because the others aren't really any better, and Sprint is the only one who truly offers unlimited everything (which is really good to have for a family of six). Starting like 3 years ago (when Sprint and Samsung abruptly abandoned the Samsung Galaxy Note 2 rather early), I refused to buy Sprint locked-down phones because they require to sign another 2 year contract commitment. Whereas right now if Sprint ticks me off (like they did a couple of years ago when they sent me a $500 bill for "free" international roaming), I can just immediately drop them and move on with no penalty and even take my phone with me.
This is the first Android phone I've owned that I haven't immediately rooted. I even rooted all my family's locked Sprint phones. There just isn't much support for this phone from 3rd-party devs (yet or maybe ever since it's just a "special edition" upgrade?), so I really want that OTA Oreo update in place before I root it. I came pretty close to immediately rooting this phone, but then decided not to when saw some people had problems getting it back to stock enough to take the OTAs from Moto. I actually like the Moto Android (along with a heavily themed Nova launcher) experience enough to not feel the overwhelming need for a custom ROM, so about the only thing I really want root for is to get a better camera app (preferably Google Camera), wifi tethering, and Titanium Backup. I'm even getting used to the stock Moto camera app, so I'm not really feeling the pressing need for the Google Camera as much. I wouldn't mind getting LineageOS 15 on here, but there isn't an official version and it doesn't seem very stable yet on any device. I tend to keep my phones for a while (three years for my Nexus 6 and Note 2), so I tend to outlast most 3rd-party dev ROM support, which is why I tend to just go with LineageOS (and before that CyanogenMod) which doesn't just vanish one day like individual dev ROMs do. We'll see what happens. Hopefully this phone will start seeing more developer activity. I was originally going to get the Moto G5+, which does have a lot more dev support, but considering how long I tend to keep phones, it didn't make sense not to buy the latest/greatest version.
I'm sure it will all eventually work out. Worst case scenario is that during a European vacation next Summer I won't be able to take full advantage of Sprint's free low speed international data roaming and texting, but even then I can always just grab a local PAYG SIM and use it.
internetpilot said:
No, it's a carrier independent unlocked phone that I bought from BestBuy.com (because they offered the best price for the 64gb version through a Cyber Monday sale). Except for the iPhone (and maybe the newer Samsung models), Sprint phones don't have removable SIMs -- they're built-in to the phone making them a special Sprint-only phone. That's the way my Samsung Galaxy Note 2 was. After my Note 2, I bought an unlocked Google (Motorola) Nexus 6 and used a SIM to use it on Sprint (and had access to APN setting as soon as I activated the phone), but that SIM isn't compatible with the G5S+ even though they're both Motorola phones, have the same radios, etc. I'm pretty sure my current problem is the SIM, but I don't think it's unsolvable. I just think I'll need to root and mod or ROM the device to get access to those settings. I know this is one of Sprint's newest SIMs (they have like 22 different SIMs), so I'm sure this is just another attempt by Sprint to lock down unlocked carrier independent phones on their network to help reduce excessive roaming (on Verizon towers) which costs Sprint money.
I've been on Sprint for like 15 years. The only reason I stayed on them is because the others aren't really any better, and Sprint is the only one who truly offers unlimited everything (which is really good to have for a family of six). Starting like 3 years ago (when Sprint and Samsung abruptly abandoned the Samsung Galaxy Note 2 rather early), I refused to buy Sprint locked-down phones because they require to sign another 2 year contract commitment. Whereas right now if Sprint ticks me off (like they did a couple of years ago when they sent me a $500 bill for "free" international roaming), I can just immediately drop them and move on with no penalty and even take my phone with me.
This is the first Android phone I've owned that I haven't immediately rooted. I even rooted all my family's locked Sprint phones. There just isn't much support for this phone from 3rd-party devs (yet or maybe ever since it's just a "special edition" upgrade?), so I really want that OTA Oreo update in place before I root it. I came pretty close to immediately rooting this phone, but then decided not to when saw some people had problems getting it back to stock enough to take the OTAs from Moto. I actually like the Moto Android (along with a heavily themed Nova launcher) experience enough to not feel the overwhelming need for a custom ROM, so about the only thing I really want root for is to get a better camera app (preferably Google Camera), wifi tethering, and Titanium Backup. I'm even getting used to the stock Moto camera app, so I'm not really feeling the pressing need for the Google Camera as much. I wouldn't mind getting LineageOS 15 on here, but there isn't an official version and it doesn't seem very stable yet on any device. I tend to keep my phones for a while (three years for my Nexus 6 and Note 2), so I tend to outlast most 3rd-party dev ROM support, which is why I tend to just go with LineageOS (and before that CyanogenMod) which doesn't just vanish one day like individual dev ROMs do. We'll see what happens. Hopefully this phone will start seeing more developer activity. I was originally going to get the Moto G5+, which does have a lot more dev support, but considering how long I tend to keep phones, it didn't make sense not to buy the latest/greatest version.
I'm sure it will all eventually work out. Worst case scenario is that during a European vacation next Summer I won't be able to take full advantage of Sprint's free low speed international data roaming and texting, but even then I can always just grab a local PAYG SIM and use it.
Click to expand...
Click to collapse
I've been following the few thread there are on this phone since I got it (about a month now), and others have had the same (no apn settings or can't change them) issue, but I just figured it was noob issues as I've always modified the apn and never had a problem, on stock or any of the roms available now, and I've tried them all. I'm an old tech guy (in age and computer experience - took my first computer class in 77) and at this point it's in my blood and I'm to old to change my ways! Still curious though - what do ya mean by the by sim wasn't compatible? Granted I'm on straight talk, but been using the same SIM - starting with the n5, then 6p, now g5s plus - I just cut it down to size when it went to the micro format. I to hope to see more work for this thing. Almost makes me want to get back into building again (been like 6+ years since I built a rom) but I just don't want to spend the time, which I don't really have anyway. I thought about the g5+, but I can't go back to a smaller screen. Yeah it wasn't much smaller, and has same cpu, and probably a better camera, but this pig will do. And with finger print actions and expanded desktop, screen is the same size as my 6p (which I was extremely happy with till the big cores shirt the bed - still running though). Wish the camera was as good, but if I really want to take a good picture, I have my nikon d5100 (hacked of course)!
Again, good luck, I'm sure you'll get it fingered out eventually!
Phazmos said:
I've been following the few thread there are on this phone since I got it (about a month now), and others have had the same (no apn settings or can't change them) issue, but I just figured it was noob issues as I've always modified the apn and never had a problem, on stock or any of the roms available now, and I've tried them all. I'm an old tech guy (in age and computer experience - took my first computer class in 77) and at this point it's in my blood and I'm to old to change my ways! Still curious though - what do ya mean by the by sim wasn't compatible? Granted I'm on straight talk, but been using the same SIM - starting with the n5, then 6p, now g5s plus - I just cut it down to size when it went to the micro format. I to hope to see more work for this thing. Almost makes me want to get back into building again (been like 6+ years since I built a rom) but I just don't want to spend the time, which I don't really have anyway. I thought about the g5+, but I can't go back to a smaller screen. Yeah it wasn't much smaller, and has same cpu, and probably a better camera, but this pig will do. And with finger print actions and expanded desktop, screen is the same size as my 6p (which I was extremely happy with till the big cores shirt the bed - still running though). Wish the camera was as good, but if I really want to take a good picture, I have my nikon d5100 (hacked of course)!
Again, good luck, I'm sure you'll get it fingered out eventually!
Click to expand...
Click to collapse
25-year career network engineer here myself -- I was on the internet since before it was called the internet (I guess "world wide web" didn't sound as kewl ). At this point in my life, I don't find technology as "fascinating" as I used to, and I pretty much just want it to work for me right out of the box. I know, I know...pipe dream. What's annoying for me is that I know this is a Sprint SIM/network issue (especially the IPv6 part), but to actually communicate with someone who even understands my questions is impossible because they're not working the help desk chat lines. Oh, well...I could go on and on with all kinds of funny stories, but the short of it is that I usually just fix my issues myself.
By the SIM being incompatible I mean just that. I took the SIM out of my Nexus 6 (which I loved, especially the camera -- broke my heart when it started randomly rebooting after 3 years of faithful service) and popped it in the G5S+ and it said "Incompatible SIM" and wouldn't register on the Sprint network. So, I took it to a corporate Sprint store (where I got the SIM for the Nexus 6) and thankfully a very knowledgeable employee was there, who said, "Yep, the G5S+ takes a specific model number of nano SIM." He popped that specific SIM in the G5S+, and it pretty much came right up on the Sprint network without an issue except for the APN thing and the IPv6 thing (which I discovered later). I have spoken with a mid-level Sprint network tech who told me that the whole IPv6 isn't my SIM as much as it's when I added that SIM and phone to the Sprint network. He said all new phones after a certain date are only getting IPv6. They supposedly were going to do something to my account that forced me back on IPv4, but it didn't actually work. They also said that it would only be for a few months anyway, because they're planning on converting everyone over very soon.
This phone is 1/2" smaller than my Nexus 6, but I actually like that. I feel like I'm on a tiny phone again...haha. Anyone I tell that to quickly points out that my G5S+ is a huge phone. I didn't think I'd like the fingerprint scanner, but I really do. I also thought I'd miss the dual front speakers on the Nexus 6, but I don't really even notice it since this speaker is so loud. I do miss the Nexus 6 camera which was superb, but I'm actually getting the hang of the G5S+ camera. I'm finding myself using the "professional" (manual) mode feature a lot, but I only change the ISO to 200 and leave everything else automatic and the pictures are vastly improved. If Moto would just provide an update that would allow post-processing to be turned off, it might actually be a very good camera. I too have a couple of really nice dedicate digital cameras that can take care of anything I really need in higher end photography or video. I've always only used my phone camera because I always have it with me. For tourist stuff, family events, etc., I always bring my real camera(s) anyway.
I've created my own custom ROMs and kernels before, but it's always just been modifying or adding to someone else's work, so I just used it myself and never released it here on XDA or anything. Depending on how things go for others, I might try doing my own LineageOS builds, but I'd much rather see an official build get going for this phone and just use that. But I said, I really don't mind that stock Moto ROM that much. It's pretty much vanilla Android, and once I root it a lot of the little customizations that go into most ROMs could probably be applied to the stock ROM in the form of a mod. We'll see.
Thanks again for the replies and commiserations!
internetpilot said:
25-year career network engineer here myself -- I was on the internet since before it was called the internet (I guess "world wide web" didn't sound as kewl ). At this point in my life, I don't find technology as "fascinating" as I used to, and I pretty much just want it to work for me right out of the box. I know, I know...pipe dream. What's annoying for me is that I know this is a Sprint SIM/network issue (especially the IPv6 part), but to actually communicate with someone who even understands my questions is impossible because they're not working the help desk chat lines. Oh, well...I could go on and on with all kinds of funny stories, but the short of it is that I usually just fix my issues myself.
By the SIM being incompatible I mean just that. I took the SIM out of my Nexus 6 (which I loved, especially the camera -- broke my heart when it started randomly rebooting after 3 years of faithful service) and popped it in the G5S+ and it said "Incompatible SIM" and wouldn't register on the Sprint network. So, I took it to a corporate Sprint store (where I got the SIM for the Nexus 6) and thankfully a very knowledgeable employee was there, who said, "Yep, the G5S+ takes a specific model number of nano SIM." He popped that specific SIM in the G5S+, and it pretty much came right up on the Sprint network without an issue except for the APN thing and the IPv6 thing (which I discovered later). I have spoken with a mid-level Sprint network tech who told me that the whole IPv6 isn't my SIM as much as it's when I added that SIM and phone to the Sprint network. He said all new phones after a certain date are only getting IPv6. They supposedly were going to do something to my account that forced me back on IPv4, but it didn't actually work. They also said that it would only be for a few months anyway, because they're planning on converting everyone over very soon.
This phone is 1/2" smaller than my Nexus 6, but I actually like that. I feel like I'm on a tiny phone again...haha. Anyone I tell that to quickly points out that my G5S+ is a huge phone. I didn't think I'd like the fingerprint scanner, but I really do. I also thought I'd miss the dual front speakers on the Nexus 6, but I don't really even notice it since this speaker is so loud. I do miss the Nexus 6 camera which was superb, but I'm actually getting the hang of the G5S+ camera. I'm finding myself using the "professional" (manual) mode feature a lot, but I only change the ISO to 200 and leave everything else automatic and the pictures are vastly improved. If Moto would just provide an update that would allow post-processing to be turned off, it might actually be a very good camera. I too have a couple of really nice dedicate digital cameras that can take care of anything I really need in higher end photography or video. I've always only used my phone camera because I always have it with me. For tourist stuff, family events, etc., I always bring my real camera(s) anyway.
I've created my own custom ROMs and kernels before, but it's always just been modifying or adding to someone else's work, so I just used it myself and never released it here on XDA or anything. Depending on how things go for others, I might try doing my own LineageOS builds, but I'd much rather see an official build get going for this phone and just use that. But I said, I really don't mind that stock Moto ROM that much. It's pretty much vanilla Android, and once I root it a lot of the little customizations that go into most ROMs could probably be applied to the stock ROM in the form of a mod. We'll see.
Thanks again for the replies and commiserations!
Click to expand...
Click to collapse
Lmfao - I know exactly how ya feel! I "retired" about 5 years ago, but people ask what did for a living and I say computers - then the questions start coming. I don't mind really, but I'm more thrilled by hitting a good golf shot than talking computers again. Now when they ask what I do I say , play golf! And leave it at that. Still, I just can't help myself when it comes to noobs - I still help folks out when I can, although my patience is much shorter than it used to be. It still amazes me how people do things without knowing their arse from a hole in the wall (xda has become pretty much a source of amusement for me nowadays). I did the same with roms, never went public with any - mostly cuz I didn't have the patience for stupid questions about things I've explained clearly. Some just don't appreciate the humor in giving a stupid answer to a stupid question! Oh well! Really most roms out there have more bloat than a stock rom - way too many "features" I'll never use - all I need is date in status bar (why this isn't a stock feature is beyond me), status bar brightness (auto brightness is always either to bright or to dim) and keyboard cursor control - anything more is useless and if I don't use it, I don't want it. I like things lean and mean. Really the main reason I root is to load a custom hosts file, I've been ad free for too long to start seeing them now. I thought about the n6 when it came out, but I only had the n5 for a year and wasn't ready to upgrade and 6 in did sound big (shamu was a perfect name for it). Of course I did jump on the 6p when it came out, and loved it, now I can't do anything smaller than 5.5 (that may be more a comment on eyes that are almost 60 yrs old though). At this stage, bigger is definitely better! And look at that, I ramble again (nothing on the golf channel so I run on). Anyway, pleasure chatting - and best of luck with the issue - sounds like it'll be short lived. And may be with the trouble - it is a decent device, plenty of power for most uses (only slowness I see is working big spreads in open office) and with my usage 10+ hrs of screen on time is easy to hit and have something like 20% battery left. A good deal for the $$ spent. Enjoy!
Okay, after looking into it more, here's what I think is happening/going to happen. I found a dial code that got me to a really good phone information screen (*#*#4636#*#*). I also found a site that stated country by country the compatibility of the US version of this phone when used internationally. It can pretty much get 4G in just about every country, so the Sprint international roaming feature should at least get me 2G, which is all they advertise anyway. Through the above dial code, I can choose from a lot longer list of Preferred Network Types, including GSM only, GSM/WCDMA, TD-SCDMA, etc. When I select these, it tries unsuccessfully to connect to that network type, and when it can't it just reverts back to LTE/CDMA (the Sprint default). I think that the APN option won't show up on the menu until I successfully connect to a network other than Sprint's. I'll find out next Summer as we're planning on going to Europe. At least I now know for sure that this phone can operated internationally just fine, so I can always go the PAYG SIM route. I looked into it on previous trips with my Nexus 6, and there are travel websites that tell you exactly the best SIM service to get for each country.
Otherwise, like I said, it seems to be working fine on Sprint. On my Nexus 6 I would have problems with it switching APNs on me from the Sprint LTE APN to the one of the 3G CDMA APNs so I'd lose 4G LTE service until I switched it back. I haven't had that problem with my G5S+ so far, so I haven't "needed" the APN option in the menus yet. Hopefully I won't. I'm about to go from Virginia to Florida for the Christmas holidays, so it will be interesting to see how things work in a different location. Sprint service at my Florida house isn't exactly stellar (none of the providers are), so it should be a good test of this phone and the lack of access to APN settings.
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
internetpilot said:
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
Click to expand...
Click to collapse
Ok yes I'm on Sprint. So I can get to those apn settings but I can't add an apn.. exactly how do you do that.. Yes I can edit the only existing one just can't add any.
edit APN settings for IPV4
also posted here: https://forum.xda-developers.com/mo...ing-ipv4-address-sprint-t3747256#post76243857
First please forgive this post if it is not helpful, I didn't see a solution and came up with something that worked for me, so hope it will help others.
Problem: On my Moto XT1806 GS5+ I was getting no IPV4 connectivity only IPV6 (tested with app: Ping & Net by Ulf Dittmer from the play store).
The main issue this caused was that I couldn't view my security cameras via Sprint's network., It would only show cameras on my home WIFI.
To verify I used Ping & Net to try to ping google.com. The app gives you the option to use IPV4 or IPV6, as you can guess IPV6 succeeded and IPV4 gave no results at all.
With some guesswork I did the following to fix this:
Solution:
open dialer and typed *#*#DATA#*#* or *#*#3282#*#* selected apn settings then internet.
at the top right tap the 3 dots and select edit this prompted me to enter a passcode which after several guesses ended up being 6 zeros "000000". (maybe this is in the instructions somewhere? Don't know didn't look, kinda figured it would be posted already if it was).
then I was able to change the APN NI from x.ispsn to n.ispsn.
Waited a few seconds, turned on airplane mode and then turned it back off and then I was on 3G with IPV4. It would be even better if it was LTE with IPV4, I will continue to experiment, or maybe someone can step in and save me the trouble. maybe cinet.spcs?
Anyway it works for now as a workaround and I can look at my security cameras away from home again, hooray.
gravityecho said:
also posted here: https://forum.xda-developers.com/mo...ing-ipv4-address-sprint-t3747256#post76243857
First please forgive this post if it is not helpful, I didn't see a solution and came up with something that worked for me, so hope it will help others.
Problem: On my Moto XT1806 GS5+ I was getting no IPV4 connectivity only IPV6 (tested with app: Ping & Net by Ulf Dittmer from the play store).
The main issue this caused was that I couldn't view my security cameras via Sprint's network., It would only show cameras on my home WIFI.
To verify I used Ping & Net to try to ping google.com. The app gives you the option to use IPV4 or IPV6, as you can guess IPV6 succeeded and IPV4 gave no results at all.
With some guesswork I did the following to fix this:
Solution:
open dialer and typed *#*#DATA#*#* or *#*#3282#*#* selected apn settings then internet.
at the top right tap the 3 dots and select edit this prompted me to enter a passcode which after several guesses ended up being 6 zeros "000000". (maybe this is in the instructions somewhere? Don't know didn't look, kinda figured it would be posted already if it was).
then I was able to change the APN NI from x.ispsn to n.ispsn.
Waited a few seconds, turned on airplane mode and then turned it back off and then I was on 3G with IPV4. It would be even better if it was LTE with IPV4, I will continue to experiment, or maybe someone can step in and save me the trouble. maybe cinet.spcs?
Anyway it works for now as a workaround and I can look at my security cameras away from home again, hooray.
Click to expand...
Click to collapse
Just found easier/better way to get/test IPV4: dial *#*#4636#*#* select phone info, from this screen you can run ping test to see if IPV6 and/or IPV4 is working. In my case, changing network type from "LTE/CDMA auto (PRL)" to "CDMA only" gave me a pass ping on IPV4.
This seems like a much easier/faster/better method than previous post and is now my preferred workaround method.
gravityecho said:
Just found easier/better way to get/test IPV4: dial *#*#4636#*#* select phone info, from this screen you can run ping test to see if IPV6 and/or IPV4 is working. In my case, changing network type from "LTE/CDMA auto (PRL)" to "CDMA only" gave me a pass ping on IPV4.
This seems like a much easier/faster/better method than previous post and is now my preferred workaround method.
Click to expand...
Click to collapse
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
internetpilot said:
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
Click to expand...
Click to collapse
Yeah after talking to support at my ISP (Cox who doesn't support IPv6 yet at least in my area), Sprint (who would love to sell me another phone), Motorola (who suggested I reset app preferences and restart) and Best buy (who didn't have a clue but again would love to sell me another phone), yesterday I had enough and returned it. It's staggering how many people in tech support fields have no idea what IPv4, IPv6, and APNs are. One support person at sprint thought IPv4 meant Iphone 4... Back to my trusty Note 4 with it's emmc problem and cinet.spcs.
internetpilot said:
Updating this thread for any other poor sap with a G5S+ on Sprint (haha). Actually, it's all working out fine.
The IPv6 issues really are app related issues. I've definitely researched any of my own problem apps, but even looked into some other reported problem apps that I don't use (Pokemon Go, WeChat, etc.) and every single one of the apps or their respective servers are simply not IPv6 compliant. There are some things that Moto and Sprint could have done to make these IPv6 app issues never rear their ugly head, but that's not really Sprint's or Moto's problem to solve. All these developers need to do is make their app IPv6 compliant like the vast majority of all other apps are (actually, all iPhone App Store apps were mandated to be IPv6 compliant by June 2016).
As for the APN settings issues (lack thereof), I figured out how to get access to the APN settings by way of (believe it or not) my youngest son's iPhone 7. It's apparently common knowledge for more techie iPhone users (believe it or not, there are some techie iPhone users) to use the *#*#Data#*#* dial code to get a much more extensive mobile data settings menu, which does include APN settings. This is a very good thing since the day after I came down to my Florida house for Christmas vacation, my G5S+ kept getting stuck on 3G, and wouldn't ever get a LTE signal even though there is one here (relatively weak, but it's still here). So I used that dial code to get access to the APN settings, and immediately noticed it was using some CDMA/ehrpd APN instead of the usual n.ispn LTE APN. So, I changed it back to n.ispn and the phone immediately latched on to a LTE signal and tends to keep it fairly well throughout my Florida house, actually better than my previous few phones did.
So, I'd have to say all's well that ends well on this whole thing. Hope this helps anyone else using this phone on Sprint (although it looks like I may be the only one on XDA).
Click to expand...
Click to collapse
I just recently bought a G5S Plus to replace my G5 Plus, because the screen on my G5 is cracked and I was going to fix the screen, but then I've found that the Micro USB port on the bottom is also growing "lose" (I HATE!!!! Micro USB because they always wear out on my phones).
Anyway, I went to "activate" my new G5S+ on the Sprint web page and it just said sorry they can't help w/that, I have to "Speak to someone for assistance" (but they didn't show me what phone number to call).
Glad to see the phone will actually work on Sprint! (Since I already bought it, it would be a big deal for me if it did not!).
I have not rooted mine yet, but plan to soon. I am just not sure what ROM to use yet because it seems like these days there is no such thing as a custom ROM without problems. I sure miss the days of my Samsung Galaxy S3 when most ROMs I tried seemed to be basically flawless and better than Stock, or, at least as good, in every way.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
internetpilot said:
Unfortunately, the 4636 dial code doesn't work on most (all?) of the current 3rd-party ROMs, and all of the current 3rd-party ROMs (to date) do not allow for Sprint users to change any of the carrier settings. It defaults to Global, and if you try to switch it to LTE (which is what is recommended), you'll lose your mobile signal and won't get it back until you reset the network settings, which defaults you back to Global.
It's very frustrating. Doesn't seem like any of these 3rd-party ROMs support Sprint at all.
Click to expand...
Click to collapse
Damn, wow, that really sucks. I have this phone, it's too late to return it, and I've got about 6 months left of my "unlimited everything" from sprint for approximately $3 per month.
critofur said:
I just recently bought a G5S Plus to replace my G5 Plus, because the screen on my G5 is cracked and I was going to fix the screen, but then I've found that the Micro USB port on the bottom is also growing "lose" (I HATE!!!! Micro USB because they always wear out on my phones).
Anyway, I went to "activate" my new G5S+ on the Sprint web page and it just said sorry they can't help w/that, I have to "Speak to someone for assistance" (but they didn't show me what phone number to call).
Glad to see the phone will actually work on Sprint! (Since I already bought it, it would be a big deal for me if it did not!).
I have not rooted mine yet, but plan to soon. I am just not sure what ROM to use yet because it seems like these days there is no such thing as a custom ROM without problems. I sure miss the days of my Samsung Galaxy S3 when most ROMs I tried seemed to be basically flawless and better than Stock, or, at least as good, in every way.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
Damn, wow, that really sucks. I have this phone, it's too late to return it, and I've got about 6 months left of my "unlimited everything" from sprint for approximately $3 per month.
Click to expand...
Click to collapse
Yep, welcome to my world! I think we're the only two people on the Moto G5S Plus on Sprint here! I was a little surprised when the SIM from my Motorola Nexus 6 didn't work in the Moto G5S Plus, but that's probably the reason you have to talk to someone or go to a Sprint store to activate it because this phone does require a rather specific SIM that's different from the previous Moto G and E models. At least Sprint finally solved the IPv6 issues that were going on when I first got this phone. That was pretty bad. It got better when my home internet providers (Comcast and Verizon at two different houses) finally upgraded to IPv6, but Sprint really shouldn't have pulled the trigger on implementing IPv6 so early. To this day only like 25% of the entire internet is on IPv6 and in the world only like 50 countries have more than 5% of IPv6 implemented.
I've literally tried every ROM posted here and even the unofficial versions of very popular ROMs (that have always worked for me on my Android phones with Sprint) like Dirty Unicorns, Resurrection Remix, LineageOS, etc., all do the same thing. They all seem to be using the same proprietary blobs or base or whatever (I'm not a developer), and they just simply don't work (or are at least VERY sketchy) on Sprint. I've been rooting/ROMing Android since my first phone almost a decade ago (HTC EVO 4G), and never had these problems on Sprint before this phone. My immediate previous phone was also a Motorola (Google Nexus 6), and I never had any problem with Sprint and custom ROMs on that phone.
I actually just recently flashed everything back to unrooted stock Nougat, took the Oreo update and all the security updates, and didn't even bother to re-root it. Sprint put a free 50GB/month wifi hotpot on every phone on my account, and the Camera2 API is activated in the stock Oreo ROM, so other than flashing a custom ROM, those were my two main reasons for rooting and they're no longer needed. So, I'm currently happily running stock unrooted Oreo with Nova Launcher.
Hello,
Does anyone know if there are versions of the Google Pixel 5 that have locked bootloaders? For example on the Galaxy S10e Snapdragon model you can't enable OEM unlocking with a certain bootloader version, however on the Exynos version this isn't as much of an issue. Are there specific updates on the Google Pixel that may prevent you from using GrapheneOS? If I get a Google Pixel I want to ensure it will be compatible with GrapheneOS.
Thanks!
Verizon is locked. Keep away from Verizon variants for basically any device if you want it to have bootloader unlocking. AT&T also I believe. Unlocked variant is usually the way to go.
andybones said:
Verizon is locked. Keep away from Verizon variants for basically any device if you want it to have bootloader unlocking. AT&T also I believe. Unlocked variant is usually the way to go.
Click to expand...
Click to collapse
I'm assuming you're American? I don't live in the USA so that shouldn't be a problem. If I go to a carrier in my country I'll see if they will let me handle the phone before buying it. I'd check to see if the OEM can be unlocked. Is there anything I should test or look at on the phone to determine compatibility?
Skyty said:
I'm assuming you're American? I don't live in the USA so that shouldn't be a problem. If I go to a carrier in my country I'll see if they will let me handle the phone before buying it. I'd check to see if the OEM can be unlocked. Is there anything I should test or look at on the phone to determine compatibility?
Click to expand...
Click to collapse
I am, sadly.
May I ask why not just buy the unlocked variant? I use it here in the US, and it seems to not be hardware specific. When I bought the Pixel 5 I was on Verizon, and switched recently to AT&T, and all it took was swapping of the sim card and all is working fine.
Are other carriers cheaper?
And If I am understanding correctly, as long as you can get into those dev settings and verify "OEM unlocking" is there and working, you are set. But, don't fall back on just my limited knowledge, as I don't really know outside the US, and as far as Pixels are concerned, once its bootloader is unlocked, nothing will be locking it down, like on Samsung. Sans strange cases like paying to unlock the bootloader of a locked down carrier variant, which I haven't come across on the Pixel 5.
andybones said:
I am, sadly.
May I ask why not just buy the unlocked variant? I use it here in the US, and it seems to not be hardware specific. When I bought the Pixel 5 I was on Verizon, and switched recently to AT&T, and all it took was swapping of the sim card and all is working fine.
Are other carriers cheaper?
And If I am understanding correctly, as long as you can get into those dev settings and verify "OEM unlocking" is there and working, you are set. But, don't fall back on just my limited knowledge, as I don't really know outside the US, and as far as Pixels are concerned, once its bootloader is unlocked, nothing will be locking it down, like on Samsung. Sans strange cases like paying to unlock the bootloader of a locked down carrier variant, which I haven't come across on the Pixel 5.
Click to expand...
Click to collapse
And here we come full circle once again. The problem is that unlocked does not mean bootloader unlockable which I know you know but others might not. GrapheneOS needs to have an unlocked bootloader or it will not install. I don't know how a buyer can get a business to boot into the OS in order to see if the OEM switch is active. But as you state that is really the only way to tell. @Skyty which carrier are you using? I don't know how you will get that guarantee that you can unlock the bootloader but that is really what you need to do if you can't handle the phone.
In the case of Pixels, the unlocked version has the added bonus of having an unlockable bootloader, Google doesn't seem to play the games that Samsung does. They're both carrier unlocked and don't have the bootloader super locked down.
andybones said:
Verizon is locked. Keep away from Verizon variants for basically any device if you want it to have bootloader unlocking. AT&T also I believe. Unlocked variant is usually the way to go.
Click to expand...
Click to collapse
People that say "don't buy the Verizon model" never tell you that the unlocked Google version of the pixels brought to the Verizon network will NOT be VoLTE and preferred/default wifi calling options. There is NO root solution to this limitation that works.
Schroeder09 said:
People that say "don't buy the Verizon model" never tell you that the unlocked Google version of the pixels brought to the Verizon network will NOT be VoLTE and preferred/default wifi calling options. There is NO root solution to this limitation that works.
Click to expand...
Click to collapse
Correct me if I'm wrong but in my post I did say "usually" the way to go.
And, just to state, I had no issues with VoLTE on my rooted, unlocked variant P5 on Verizon, nor At&T, VoWIFI works also.. what am I doing special? Just curious. Here I am on a call using VoLTE.
Also, if they are creating VoLTE Magisk modules for China and more. This is the first complaint I've read about this issue. My HTC 10 was also an unlocked variant on Verizon with VoLTE, Wi-Fi Calling and preferred options were the same as my brother stock un-rooted Verizon variant. So, I'm lost. Sorry.
Schroeder09 said:
People that say "don't buy the Verizon model" never tell you that the unlocked Google version of the pixels brought to the Verizon network will NOT be VoLTE and preferred/default wifi calling options. There is NO root solution to this limitation that works.
Click to expand...
Click to collapse
Can you please explain this statement? I don't use wifi calling but I'm willing to test out your theories. I have an unlocked Google P5 and I'm on the Verizon network.
bobby janow said:
Can you please explain this statement? I don't use wifi calling but I'm willing to test out your theories. I have an unlocked Google P5 and I'm on the Verizon network.
Click to expand...
Click to collapse
When you buy the Google bootloader unlocked phones and being them to Verizon they do NOT have all the locked down Verizon version phone capabilities. On a pixel with a locked bootloader purchased from vzw you will have options in your settings to enable VoLTE services AND to enable Wi-Fi calling by default meaning whenever you're on wifi the phone will default to making calls over wifi as opposed to a network. This is useful of you have poor reception in your house or place of work.
Without it the phone will only use wifi to make calls when the network is very, very poor, and it still will only use wifi sporadically. It will switch to the wifi network AFTER the call starts sometimes. This will cause momentary dead air where you miss words and may think you dropped the call. It's a total PITA. There are supposed fixes and options you can toggle in the phone app by dialing some crazy number which is actually a code to access options and settings in the phone app. None of these options work. There are 3 guys in the world who have had success with these options and work arounds, and I'm sure they'll chime in here to encourage you to spend $1200 on a p6 or $600+ on a p5 because you'll **probably** be able to get these functions working. If you need or greatly prefer VoLTE and/or wifi calling know that you probably will NOT be the 4th guy in history to have success with these work arounds.
I do not care about VoLTE at all. I have never had it, but I guess it's super clear voice AND it's only available in a (growing) list of big cities. Who cares about SUPER clear voice? How often do you even actually use your phone anyway? I DO care about preferred wifi calling as this has a definable, useful function, and I was and still am (4 years later) ticked about not having the ability to have my phone preferably select a wifi network regardless of the signal coming from the cell network.
Schroeder09 said:
When you buy the Google bootloader unlocked phones and being them to Verizon they do NOT have all the locked down Verizon version phone capabilities. On a pixel with a locked bootloader purchased from vzw you will have options in your settings to enable VoLTE services AND to enable Wi-Fi calling by default meaning whenever you're on wifi the phone will default to making calls over wifi as opposed to a network. This is useful of you have poor reception in your house or place of work.
Without it the phone will only use wifi to make calls when the network is very, very poor, and it still will only use wifi sporadically. It will switch to the wifi network AFTER the call starts sometimes. This will cause momentary dead air where you miss words and may think you dropped the call. It's a total PITA. There are supposed fixes and options you can toggle in the phone app by dialing some crazy number which is actually a code to access options and settings in the phone app. None of these options work. There are 3 guys in the world who have had success with these options and work arounds, and I'm sure they'll chime in here to encourage you to spend $1200 on a p6 or $600+ on a p5 because you'll **probably** be able to get these functions working. If you need or greatly prefer VoLTE and/or wifi calling know that you probably will NOT be the 4th guy in history to have success with these work arounds.
I do not care about VoLTE at all. I have never had it, but I guess it's super clear voice AND it's only available in a (growing) list of big cities. Who cares about SUPER clear voice? How often do you even actually use your phone anyway? I DO care about preferred wifi calling as this has a definable, useful function, and I was and still am (4 years later) ticked about not having the ability to have my phone preferably select a wifi network regardless of the signal coming from the cell network.
Click to expand...
Click to collapse
I've read this about 5 times already and I still have no idea what you are talking about. I don't really use wifi calling but I'd be willing to test your theory. Walk me through the steps and tell me what I'm looking for. Wait maybe the 6th time is the charm. So if I turn on wifi calling on my phone now in a very good network setting you are saying that it will not use wifi until the network drops out right? How can I test that?
bobby janow said:
I've read this about 5 times already and I still have no idea what you are talking about. I don't really use wifi calling but I'd be willing to test your theory. Walk me through the steps and tell me what I'm looking for. Wait maybe the 6th time is the charm. So if I turn on wifi calling on my phone now in a very good network setting you are saying that it will not use wifi until the network drops out right? How can I test that?
Click to expand...
Click to collapse
Don't bother man, I give ample proof.
The "dialing some crazy number which is actually a code to access options and settings in the phone app" is *#*#4636#*#* FWIW. That's where my 3-4 pictures come from.
He doesn't even use his phone as a phone, but is upset about WIFI calling, so once again, I'm lost, but I won't be replying to anything he has to say. and let's just leave it alone because I don't make fake posts, and don't want to keep going off-topic, for IMO, no reason.
Schroeder09 said:
When you buy the Google bootloader unlocked phones and being them to Verizon they do NOT have all the locked down Verizon version phone capabilities. On a pixel with a locked bootloader purchased from vzw you will have options in your settings to enable VoLTE services AND to enable Wi-Fi calling by default meaning whenever you're on wifi the phone will default to making calls over wifi as opposed to a network. This is useful of you have poor reception in your house or place of work.
Without it the phone will only use wifi to make calls when the network is very, very poor, and it still will only use wifi sporadically. It will switch to the wifi network AFTER the call starts sometimes. This will cause momentary dead air where you miss words and may think you dropped the call. It's a total PITA. There are supposed fixes and options you can toggle in the phone app by dialing some crazy number which is actually a code to access options and settings in the phone app. None of these options work. There are 3 guys in the world who have had success with these options and work arounds, and I'm sure they'll chime in here to encourage you to spend $1200 on a p6 or $600+ on a p5 because you'll **probably** be able to get these functions working. If you need or greatly prefer VoLTE and/or wifi calling know that you probably will NOT be the 4th guy in history to have success with these work arounds.
I do not care about VoLTE at all. I have never had it, but I guess it's super clear voice AND it's only available in a (growing) list of big cities. Who cares about SUPER clear voice? How often do you even actually use your phone anyway? I DO care about preferred wifi calling as this has a definable, useful function, and I was and still am (4 years later) ticked about not having the ability to have my phone preferably select a wifi network regardless of the signal coming from the cell network.
Click to expand...
Click to collapse
I don't know about you, but I USE my phone primarily as a phone., this is why own a tablet and a small 13" laptop.
And just because I do use my phone and you don't doesn't mean anything, as far as what others use theirs for, you're not to say and neither am I.
I'm up here in the boondocks with hardly ANY service on the weekends, and get crystal clear calling when I am connected to and with Wi-Fi Calling on.
No work-arounds for me, just an unlocked variant P5, rooted and on the stock ROM, now on AT&T, switched the other week.. And all I had to do was swap the SIM cards..
The only thing I suppose I can't fully check (that I'm aware of) is the "SUPER clear voice" preferred calling as IDK if it has a setting to turn on/off such as VoLTE/VoWIFI.
And even so, it's subjective to the person using and listening to the phone.
And I've been using an unlocked variant device on Verizon with "IMS, advanced calling, Wi-Fi calling and all other Verizon features" since the HTC 10!
So, just saying, this isn't exactly new. And I'm certainly not telling anyone to go out and buy anything just because I get these features.
And Bravo to these "3" people. IF they have it working and you don't, it is what it is, I guess, I don't know what to say, other than they aren't breaking any rules by posting about it.
Also, anyone who spends $600-1200 based off someone's single post.. That's on them, bro. You can't control how people spend their $$
And I'm certainly not making this post to try and shill anyone to buy an unlocked variant. Like you don't care about VoLTE, I don't care what phone someone buys.
I think these screenshots speak for themselves.
andybones said:
Don't bother man, I give ample proof.
The "dialing some crazy number which is actually a code to access options and settings in the phone app" is *#*#4636#*#* FWIW. That's where my 3-4 pictures come from.
He doesn't even use his phone as a phone, but is upset about WIFI calling, so once again, I'm lost, but I won't be replying to anything he has to say. and let's just leave it alone because I don't make fake posts, and don't want to keep going off-topic, for IMO, no reason.
I don't know about you, but I USE my phone primarily as a phone., this is why own a tablet and a small 13" laptop.
And just because I do use my phone and you don't doesn't mean anything, as far as what others use theirs for, you're not to say and neither am I.
I'm up here in the boondocks with hardly ANY service on the weekends, and get crystal clear calling when I am connected to and with Wi-Fi Calling on.
No work-arounds for me, just an unlocked variant P5, rooted and on the stock ROM, now on AT&T, switched the other week.. And all I had to do was swap the SIM cards..
The only thing I suppose I can't fully check (that I'm aware of) is the "SUPER clear voice" preferred calling as IDK if it has a setting to turn on/off such as VoLTE/VoWIFI.
And even so, it's subjective to the person using and listening to the phone.
And I've been using an unlocked variant device on Verizon with "IMS, advanced calling, Wi-Fi calling and all other Verizon features" since the HTC 10!
So, just saying, this isn't exactly new. And I'm certainly not telling anyone to go out and buy anything just because I get these features.
And Bravo to these "3" people. IF they have it working and you don't, it is what it is, I guess, I don't know what to say, other than they aren't breaking any rules by posting about it.
Also, anyone who spends $600-1200 based off someone's single post.. That's on them, bro. You can't control how people spend their $$
And I'm certainly not making this post to try and shill anyone to buy an unlocked variant. Like you don't care about VoLTE, I don't care what phone someone buys.
I think these screenshots speak for themselves.
Click to expand...
Click to collapse
^^^ one of the 3 people who gets this stuff to work.
My point to the question was that this stuff seldom works. No one knows why. It worked for you. Cool. You got lucky. There are plenty of us who never get it work with alllll the root options and magisk modules put there.
Schroeder09 said:
^^^ one of the 3 people who gets this stuff to work.
My point to the question was that this stuff seldom works. No one knows why. It worked for you. Cool. You got lucky. There are plenty of us who never get it work with alllll the root options and magisk modules put there.
Click to expand...
Click to collapse
No, I'm not that lucky, believe you me.
And I've let this go on long enough.
Anymore OT on this subject gets deleted.
Thank you.
I sell pixel devices basically for a living that have Graphene/Calyx on them. If its a carrier device and sitll locked to that carrier, the bootloader OEM Unlock option will be forever grayed out until the device is SIM Unlocked.
The Pixel 5 can be Unlocked, Verizon or ATT. ATT and VZW will be locked until sim unlocked
KaptinBoxxi said:
I sell pixel devices basically for a living that have Graphene/Calyx on them. If its a carrier device and sitll locked to that carrier, the bootloader OEM Unlock option will be forever grayed out until the device is SIM Unlocked.
The Pixel 5 can be Unlocked, Verizon or ATT. ATT and VZW will be locked until sim unlocked
Click to expand...
Click to collapse
I saw those phones being sold for double the list price of a P5. Is that true? So basically charging a few hundred dollars to install a rom / os that anyone with a semblance of knowledge can do themselves. I'm not sure I have the details correctly so let me know if I'm wrong.
As for the second part of your statement, the VZW P5 cannot be bl unlocked no matter what you do, sim lock or not. I'm not sure about ATT.
bobby janow said:
I saw those phones being sold for double the list price of a P5. Is that true? So basically charging a few hundred dollars to install a rom / os that anyone with a semblance of knowledge can do themselves. I'm not sure I have the details correctly so let me know if I'm wrong.
As for the second part of your statement, the VZW P5 cannot be bl unlocked no matter what you do, sim lock or not. I'm not sure about ATT.
Click to expand...
Click to collapse
I usually add +40 to +75, unless I have original boxes and accessories. They really do sell for more, and people pay it.
As for the VZW P5, I have a few in my shop office right now that cannot be unlocked and their IMEI reads back as a Verizon phone, double checked by inserting another SIM and comes up locked. VZW Statement on unlocking is "if the phone was paid off (6 months of payments), it will auto unlock" .. so you probably have one that's paid off.
No, I bought the Google version. Even paid up you can't unlock the Verizon version. It's just the way they operate.
Seems like a fair price. This is the article I was talking about. https://9to5google.com/2021/09/05/n...-focused-grapheneos-that-costs-twice-as-much/