[Q] Need Help: Using In Japan - Nexus One Q&A, Help & Troubleshooting

Hello. I posted this yesterday in the Nexus S forum (I have an S, not a One) but no one seems to know the answer so I was wondering if perhaps someone here could help out, as the Nexus One has been out for some time now.
In a nutshell, I would like to know how in the world I can get my unlocked Nexus S to work in Japan with respect to data transmission.
Early this year I developed an interest in foreign smartphones as all we had here in Japan was the (IMHO) horrid Xperia X10 and the wonderful HTC Desire. I have purchased a number of phones from overseas (either Hong Kong or the UK) including:
HTC Mini (HK)
HTC Desire (HK)
Xperia X2 (UK)
Galaxy S (UK)
Galaxy Tab (UK)
Nexus S (USA)
Now here's the thing: ALL of these phones were unlocked yet NONE of them allowed any data transmission except the HTC Mini. To this day I fail to understand why.
When I got the HTC Mini, I was using the Mopera U APN/service. I put my Docomo SIM card into the Mini and without doing anything at all, it had data connectivity from the start. To this day I question if it was something related to Windows Mobile, as all of the other phones I listed above are Android (except for the X2).
I had Mopera U with all of these other phones and yet NONE of them work, even after I have tried multiple APN services and have manually typed in the APN settings (i.e. mpr2.bizho.net, spmode.ne.jp, mopera.flat.foma.ne.jp, etc).
Just yesterday I received my unlocked Nexus S from the USA and while it hardly came as a surprise, I am nonetheless infuriated once again that the phone refuses to connect to the wireless network.
It should be noted however that the very first time I attempted to connect the Nexus S to the mpr2.bizho.net APN, for a scant one second, the 3G data transmission icon appeared in the taskbar at the top of the screen, but then immediately disappeared. Since that initial setting, it has never reappeared when I toggle the APN.
Can anyone please offer some advice here? I fail to believe that there is absolutely no way to use this phone in Japan. With all the different network bands and whatnot supported by this phone, surely it has to work. I am still at a loss as to why the Galaxy S and Galaxy Tab failed to connect to the network here when both are in fact, available for purchase domestically. Are the manufacturers actually creating modified band phones for each country despite making the same exact product?
Docomo is absolutely no help whatsoever, claiming that the ONLY band supported here is "3G" and denying any understanding of the other band spectrums (i.e. Quad Band GSM, Tri-Band HSPA, etc).
Some of the IT-related people I know have suggested that my phone is in fact, NOT unlocked and thus the problem stems from that, however considering that the phone will instantly register the NTT DOCOMO network and I can make calls and receive SMS messages, I fail to believe the phone is locked.
I will bring up a point that a friend passed onto me: They suggested that perhaps my problem is that the phone won't work because the previous carrier settings are still on it. The seller on eBay however stated that this was a factory unlocked phone and thus I don't think this applies, though I was a bit confused as to why there was a T-Mobile SIM card inside the Nexus S box, which led me to believe that perhaps the phone is unlocked but it is "defaulted" to T-Mobile network values?
Anyway if anyone could be of some assistance here I would greatly appreciate it.

You seem to know your stuff -- so I'm baffled as to why this isn't working for you.
You're armed with the Docomo APN and authentication, as well as compatible hardware. NTT Docomo (as well as SoftBank) operate 3G/UMTS/HSDPA on 2100Mhz, which your Nexus S supports.
Each year I visit family, I get a rental SIM, get the spiel that loaner SIMs aren't allowed to be used in smartphones (might have changed now). So they give me a phone instead, which I just rip the SIM out of and place in my phone.
I doubt your previous carriers' info would be interfering, since I'm guessing the only entry you have under operators is Docomo (and removed every other carrier), and you have your FOMA SIM inserted.
The only thing I can think of are: your HTC Mini's passing some authentication type handshake (or maybe it's a parameter or setting its' flipping), or the network has some strange blanket ban on IMEI numbers.
Both scenarios are pretty unlikely -- which brings me back to me being baffled. I was able to rip out a SIM and use in a Nokia E51 and an HP iPaq 910 (a handset not sold in Japan). I just entered in some APN settings and it was happy as pigs in ****.
I'm sorry I don't have anything more to offer -- but from what you said, and you are correct -- this should work.
This might sound obvious : Sometimes, Android will have a database built in with APN settings and will use those. Sometimes, It'll read the settings off of the SIM, and use those. Some cases, the auto-selected values might be incorrect if the carrier changed something on their end. Or sometimes, it might not do anything at all. You might have already tried this -- find a working handset (HTC Mini, friend, demo unit in a store, etc), write the settings down and enter them in by hand on your Nexus S. If you've already tried this, I apologize.

Related

[Q] Why is my Gear S not able to register on TMobile's network anymore?

My wife bought me the international version of the Samsung Gear S (SM-R750W). She said that she researched and from her understanding it should work on the T mobile network. From what I've found though the consensus seemed to be it would not work, or if it did it would be spotty at best depending on the specific towers/area you were in because Tmobile utilizes different network types in different areas.
I decide to give it a shot anyway and went to the T-Mobile store where I signed up for the wearable plan and got a new nano sim card. I was crossing my fingers but as soon as they put the sim card in the watch it came to life. It looked to be working fine but as I left the store I received a text from T-Mobile stating " the SIM for your wearable devices is in an ineligible device. Services to the SIM are locked until it returned to your eligible wearable device".
I pessimistically started thinking well great, there goes that idea. But as I got into my vehicle I shut my phone down and tried to see if the watch can work on its own as a phone when unencumbered from my Note 4 bluetooth/WiFi data connections. It worked perfectly-I started calling my friends and they couldn't believe I was talking on a watch phone. Several I actually felt the call sound quality was better on the watch speaker phone compared to normally speaking on the Note 4. I called customer service but they told me they couldn't see anything and if it was working fine not to worry about it.
For the next eight or 9 hours it worked perfectly and I was using it a lot. I drove around large swaths of town and neither data nor call experienced even the slightest issue - for once I was happy to be wrong.
Eventually, as I am oft to do, I fell asleep. When I awoke this morning the watch was no longer connected to the network. It gave me a message saying it was unable to connect and did I want to scan for additional networks. I selected yes and it was able to find the T-Mobile and ATT networks. T-Mobile was selected and a "registering" notification was displayed. It took awhile but eventually said it was unable to register with the network.
I call T-Mobile and they said pretty much exactly what I expected them to say -that because it was not a T mobile device they could not ensure proper operation. But he said (and he characterized this as "good news", "light at the end of a tunnel" and "viable solution” Seriously said all 3 things.) I could either forget all about the cellular connection and just use this as a companion device OR go and buy a new Gear S from T Mobile if I really wanted that feature.
I’m truly and utterly baffled that he believed his suggestions merited the positive sayings from above. Never in my lifetime has my head been closer to exploding.
After I was finally able to speak again, I explained that it seemed unlikely to be an issue with the watch. If my Gear S was working perfectly yesterday and can still detect Tmobile & ATT networks, then something on your end seems to be preventing registration. He agree to file a ticket with the engineering team and tomorrow I should hear from them hopefully. He also told me to go and try another nano-SIM, gratis, at the Tmobile store. So today I went and as soon as I put the new card in all systems were go. I assumed that I somehow had received a bad card because here again now, data and voice are connected.
This time I didn’t even make it out of the parking lot before it notified me that that it was again unable to register with the network. There is conflicting information regarding the radio frequencies and bands that the different Gear S models have and I didn’t have high hopes. But then it actually did work, WELL, so any ideas as to what is going wrong?
I don't know how I put this in the wrong forum, could one of the mods please delete it? It's already been reposted in the correct forum.

Anyone else on Sprint? No APN settings?

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.

Anyone tested Verizon support for this phone

I know the XZ2 Compact supports verizon, I just wanna know if you pop verizon sim in xperia xz2, if it will have signal or volte?
Trying to figure that out myself. Specs are the same so I don't see why it won't other than a couple folks saying it won't.
Sent from my [device_name] using XDA-Developers Legacy app
Ended up picking up the compact today and popped the sim in from the Essential. Verizon service works fine on it with volte working perfectly. No full size in stock, don't think they even ordered any. Best Buy.
jerrygenius said:
I know the XZ2 Compact supports verizon, I just wanna know if you pop verizon sim in xperia xz2, if it will have signal or volte?
Click to expand...
Click to collapse
I tried it with a H8296, first, second (both with working T-Mobile sim), and only sim. No go.
Put the Verizon sim back in my pixel 2, and fired right back up on Verizon.
Has anyone tried this after installing the Android P beta on the XZ2? Curious to see if that magically lets Verizon work. (So irritating that it doesn't regardless...)
Message from a Verizon rep:
Please note that the Sony Xperia XZ2 Compact model certified for Verizon is model H8314. The dual SIM version H8324 is not compatible.
alexj714 said:
Message from a Verizon rep:
Please note that the Sony Xperia XZ2 Compact model certified for Verizon is model H8314. The dual SIM version H8324 is not compatible.
Click to expand...
Click to collapse
You rock!!
Honestly it should work fine if you have Volte enabled on your account. For example, the Mi Mix 2 works perfect on Verizon and is not Certified on the network. It just has the appropriate band support (as well as CDMA in this case). However, I had no problems getting Volte working on the Mix 2 despite it not being "certified". I'm going to purchase the XZ2 Premium and try, but it would be great to hear some success here as well.
About what the rep said though, most normal Verizon reps know very little about getting phones on the network. I'd recommend at least getting transfered to an upper tier troubleshooting agent.
You may have to call Verizon to get support on it, but it should just recognize the bands just by popping the already activated Sim in. Maybe toggle the network settings in the options to "Global" or LTE preferred. Volte will be the only obstacle really being that it has all of the LTE bands.
Which is the US variant with support for Verizon LTE bands, H8216 or H8296 or H8266??
Ok guys so I purchased a xz2c (H8314) from Best Buy and it won’t commect to Verizon service for me. It connects briefly when I start phone and when I turn on/off airplane mode. Then it goes back to network service or emergency calls only. I’ve tried several times with tier 1, tier 2 Verizon reps, when to store, went back to bestbuy and spoke with Sony and nothing Is getting my phone to connect. Please help.
TPlatt said:
Ok guys so I purchased a xz2c (H8314) from Best Buy and it won’t commect to Verizon service for me. It connects briefly when I start phone and when I turn on/off airplane mode. Then it goes back to network service or emergency calls only. I’ve tried several times with tier 1, tier 2 Verizon reps, when to store, went back to bestbuy and spoke with Sony and nothing Is getting my phone to connect. Please help.
Click to expand...
Click to collapse
Hello TPlatt, I've been trying to follow your posts on a variety of threads. Before you potentially flash another country's firmware on your device, could you review/answer/do some of the following?
Pre-1) This question is probably better served on the sony xperia xz2 compact xda forum rather than the xz2 forum as this issue is mostly resolved for the compact. Search for "HD Voice" in the xz2 compact forum.
1) Did you ever get your phone working on verizon before you started playing around with it i.e. rooting/flashing other other firmware?
-I don't know if this has anything to do with your issues, just curious.
2) Do you have a data only sim or a line+data sim?
-Again, I don't know if this has anything to do with your particular situation, but the general solution of enabling HD voice either through Verizon support or your account through the Verizon website might depend on this. If you have a data only sim, I suggest you find someone with a full Verizon sim and have them finish the activation for you (HD Voice enabling) so the device can be properly show up on and be configured on the Verizon network, before switching back to your data only account.
3) When you were talking with the verizon techs, what transpired?
-I'm assuming you gave them your imei or meid number (I don't remember which one was necessary) so they can whitelist the device and assign it to your account.
Best of luck? If you believe you cannot get your phone to work because of flashing you did, maybe get a swap from BestBuy? I also got my xz2c from there, working on verizon, and waiting for the bugs to work themselves out before rooting my phone.
Magchild said:
Hello TPlatt, I've been trying to follow your posts on a variety of threads. Before you potentially flash another country's firmware on your device, could you review/answer/do some of the following?
Pre-1) This question is probably better served on the sony xperia xz2 compact xda forum rather than the xz2 forum as this issue is mostly resolved for the compact. Search for "HD Voice" in the xz2 compact forum.
1) Did you ever get your phone working on verizon before you started playing around with it i.e. rooting/flashing other other firmware?
-I don't know if this has anything to do with your issues, just curious.
2) Do you have a data only sim or a line+data sim?
-Again, I don't know if this has anything to do with your particular situation, but the general solution of enabling HD voice either through Verizon support or your account through the Verizon website might depend on this. If you have a data only sim, I suggest you find someone with a full Verizon sim and have them finish the activation for you (HD Voice enabling) so the device can be properly show up on and be configured on the Verizon network, before switching back to your data only account.
3) When you were talking with the verizon techs, what transpired?
-I'm assuming you gave them your imei or meid number (I don't remember which one was necessary) so they can whitelist the device and assign it to your account.
Best of luck? If you believe you cannot get your phone to work because of flashing you did, maybe get a swap from BestBuy? I also got my xz2c from there, working on verizon, and waiting for the bugs to work themselves out before rooting my phone.
Click to expand...
Click to collapse
Wow so sorry didn’t realize I was in xz2 and not the compact. Guess that’s what I get from using small phone to research
So my mother was in a no LTE zone with the US variant of the XZ2 compact. Earlier she had data and phone service, but once she got back to the same place with data and service the phone wasn't connect. She had to restart her phone to get it working again. Is this common or is there something wrong with the service?

N9600 on AT&T, NO network/signal

I'm still using my N9600 device on AT&T (since the last year) and woke up today to realize the device is NOT registering on AT&T's network. I spoke to customer service & they're NOT sure what happened...
After speaking with the "advanced technical team" at 866-344-6217, guy mentioned it is the end of the road & the device cannot be re-activated on the network. Anyone else facing this issue?
Although I didn't swap/remove the SIM from this device, the customer representative said AT&T's system kicked the device OUT & replacing the SIM won't resolve this issue. Is AT&T trying to force people to move onto a 5G device deliberately?
I popped the (same) SIM into an A71 (T-Mobile version) that I had, everything started working... FYI
They started doing this months ago. And you can't whitelist imei either.
Just Google Phones that will work on At&t network. They have a list of devices they support
So its pretty much if its International devices and model number ends in F or G they will suspend your account if you put sim in phone and you have to call to have it activated again. You can't just put it back in device and your sim provisions...trust me I spent $400 on a Note 10 lite had it for 2months and this happened. Still have several International phones that no longer work. Most United States carriers will probably do this in the future
Sucks that they're doing this since a few months, sounds like I got lucky for more time than others have.
Is there any dual-sim 5G phone (Note-20 Ultra N9860 perhaps?) that is still expected to work with AT&T? I need to maintain 2 phone numbers (1 international number) due to work/business & hate carrying 2 different devices to accomplish this, this was the whole reason behind holding on to my N9600 for such a long time... Don't like iPhones, have been using Samsung for almost a decade now.
Any suggestions? Help appreciated...
Thanks

SM-N910T on T-Mobile USA in 2023?

I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".
This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.
Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?
Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?
If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?
I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?
Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.
https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.
Seeing this forum has so little activity, on 1/21 I ended up getting a used Moto E6 (XT-2005-3 is a tmobile aka carrier unlocked MetroPCS version). While overall this is not as nice a device and has fewer features than Note 4, it does cover what for me are the essentials - removable battery, SD card slot, support for 5.8GHz wifi. Best of all, it supports B71 which will be helpful for, well, making phone calls!
I still ponder someday getting one of these as a hobby device, but that would be second place to the E6 for use as a phone, and won't be for a couple more months yet (too many expensive household issues are taking their toll on my "toy" budget right now).
ForestCat said:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice.
Click to expand...
Click to collapse
Thank you, this was the part I needed to find out. With that in place, the only thing missing would be the B71 coverage but the E6 is already in place for that.
Re your Verizon adventures, I have no experience with any of that. What I read about T-Mobile dropping support for the verizon version in the last network update is all I know, and I don't have the skills to dispute what they say there. The best I could do is offer some links to threads on this forum but on double checking them it seems you've already been there and got no answers.
The only thing I see that might help you with that is if you could update just the t-mobile modem without disturbing the verizon bootloader. I see you tried that but it didn't stick when using Odin. I don't know if it would be any different using SmartSwitch that seemed to work for MarineWonder as he posted at https://forum.xda-developers.com/t/...pgrade-on-jan-29th-2021.4224237/post-87464609 ?
Then again he may have been putting it on a t-mobile phone rather than mixing with the verizon bootloader so who knows?
My guess since it has been so problematic for you on the verizon phone is that you may need to only use a tmobile phone since that may be the only way to get the last t-mobile modem update. Bummer that the one you bought has a dead usb port. How are you charging it? Is there any chance you could return it to the seller since it came pre-broken? Then put the refund money toward another, hopefully working, tmobile phone? And would that MODestROM work on a non-verizon phone?
The only other thought I had is there are apps to connect to ADB over wifi. Sadly most of these need root. The ones that don't, seem to need at least once using a usb connection to do the "adb tcpip 5555" command to set it all up. . . . how annoying that it is all so circular!
There is also https://telnetd.en.aptoide.com/app?store_name=apps&app_id=59202144 , maybe a telnet connection could do the "adb tcpip 5555" command instead of using the USB connection? Sadly the documentation (at https://waxrain.com/docs/010.html ) appears to be written in Chinese, and I never had much luck with google translate.
The N910T still supports VoLte.. It is still compatible with cellular networks.

Categories

Resources