tsume

I've had IPv6 over Sprint LTE for a while now on my M9. Might have even been there since release, but I've definitely had it for at least a month. http://i.imgur.com/CEM081b.png http://i.imgur.com/1qB11IG.png

If I wanted to take an extra 1-2 hours to get to Pittsburgh, I would be passing through Harrisonburg. The fastest route is to go through WV.

Driving up to Pittsburgh, PA from Johnson City, TN this weekend. Looks like 85%+ of this drive is going to be in nTelos land... wish me luck :/ Last time I was up in SWVA the service was insanely bad.

davidtm, it's probably something specific to the M9. I have the same problem on my M9 and M8. Going up I-81 leaving nTelos for Shentel, everything is fine. On the way back I had to reboot to get my data to work. There are other places where it does weird things. Going from TN to NC over I-26 for example, my phone will get stuck roaming on Verizon's 1X and will not connect to the Sprint towers in NC until I reboot. It is always fine on the way back. I think it's just something weird with HTCs radios on the Sprint version of the device.

I was able to find the AT&T HTC One M9 on Industry Canada's site by searching 0PJA110, but I was not able to find the Sprint variant 0PJA200. I don't think it's on there. This is the site I used to look for it (not sure if it's where I should be looking): https://sms-sgs.ic.gc.ca/equipmentSearch/searchRadioEquipments?execution=e1s1

If you call drudging through my posts from a year ago with the aim of publicly harassing me "well informed with research" then so be it. I am not going to argue with you on that, as that is your closely-held opinion. Attacking me directly and personally does not benefit me nor does it benefit you. There's no rational reason for it. Discussion closed on that matter, as I've nothing else to say to you regarding that. The FCC ID of the phone is NM80PJA200. There does not appear to be any Industry Canada information on the phone or in the settings menu of the phone, unfortunately. I looked over the box and the included manual and did not see anything there either except the FCC ID.

What a difference a year makes, right? Yes, I do travel to Canada. I appreciate you keeping your opinions on how I spend my money to yourself, as they were not solicited nor are they relevant. Stereotyping people from Tennessee and assuming they do not travel internationally is telling of your prejudices. Let's keep this on topic, please. If the M9 can't roam in Canada, it is a clear regression - your opinion does not change that. I have not been to Canada with my M9. I have been there with my M8 and with my M7, both of which did roam in the Vancouver area.

People can talk about Wi-Fi all they want, but Wi-Fi is not everywhere. I don't care what Sprint's excuse is, purposely hamstringing a flagship device just because other carriers are jerks is not acceptable. If the Sprint M10 can't roam in Canada, I might have to switch to T-Maybe. Good thing I only have a 1 year lease. mrrogers1: If you select an old device (like the EVO 4G LTE) it will give you a message saying that some services are not available internationally. It shows you can only roam on Telus' CDMA network: http://i.imgur.com/mcN7fWc.png If you select the M9, you get no warning message and the site implies you can roam on Rogers, Bell, and Telus' GSM networks: http://i.imgur.com/HFsR5sJ.png

So what you are saying is that Sprint released a 2015 flagship phone that does not work in what is one of the most popular international roaming destinations for Americans, and the CSRs don't even know that it doesn't work there. If that's the case... nice going, Sprint. Way to shaft your customers. I wonder how many times devices are going to get replaced because Sprint techs just can't figure out why the phone won't work in Canada and conclude that it "must be a defective device". I am sure that even the Sprint techs could not imagine the possibility of Sprint being dumb enough to release a "worldwide" phone that doesn't work in Canada, one of the only two international roaming destinations that has a land border with the US.

There was only one place where I could not place a call. Calls worked fine everywhere else. The main problem I had was with data, so a severed fiber optic link would make sense as the cause. Just interesting that it did not affect any other cell provider. I'm guessing that Sprint uses someone else for backhaul there. Hopefully it's fixed soon. I know if I lived there, I'd be pissed if it were still as bad as it was on Friday and Saturday.

Both phones had more than sufficient signal strength to place a call or use data. This wasn't a device or signal issue. It would sit there for a good 20 seconds and then say "call failed" without it even ringing at the cool springs mall food court. There was definitely something going on with the network there this weekend, as while that was the only place I couldn't place a call, data was not usable or so sporadic it was basically not usable all weekend at multiple places in Nashville. I had two different devices and both worked fine when I left Nashville and before I got there. The only time I've ever experienced data this bad was when I was in Atlanta for a convention, so I'm pretty sure it was congestion.

I was just in Nashville this weekend and the Sprint service was useless. At Cool Springs mall I saw my phone switching between b25, b26, and b41 and the data barely worked on any band, frequently failing to load anything at all... on two different devices. I could not even make a phone call. In the Woodbine area things were even worse with data, with data failing to work on LTE (b25/26) and 3G whatsoever, but at least I could make calls. Similar situation at Opry Mills mall; even on b41 the data was useless. Phones started working fine as soon as I left Nashville, and had great data all the way back on the 5 hour drive to the Tri Cities. I of course have the profile updated and PRL updated on both. Why is Sprint so terrible in Nashville? It was not like this 6 months ago.

My M9 seems to perform about the same as my M8 now that the weird LTE loading issues are fixed. I get LTE in the same places and 3G in the same places. b41 is just as rare as it was on the M8. And I still have the same problem where after driving across the mountains on I-26 from TN to NC, my phone gets stuck on roaming until I reboot it (airplane mode toggle doesn't fix). Weird that it never happens on the way back but always on the way there. Wonder if it has something to do with going from an Ericsson market to a Alcatel market with roaming in between.

My impression of the signal on the edge is that it performs very similar to the M8 in terms of where it gets LTE and where it stays on 3G. I'm a bit miffed that Samsung won't come out and say if the rotation thing is a software or hardware problem, considering the volume of complaints on the issue. Both times I talked to them their reps seemed totally clueless that this is affecting multiple people. My thoughts on possibly going with the M9 instead weren't really regarding device reliability since I'm sure it has it's own issues, but more regarding my better experiences with their support. Samsung support so far has been a bit of a joke I'm sad to say. It's a shame because the edge is a really nice piece of hardware.

I bought it online on the advantage club store online. You cannot return it at any Sprint store unless it is a corporate store on a SWAC account. It is a huge pain to return a defective device on SWAC accounts. I think I'm going to go HTC M9 this time because there are people saying they're on their 3rd edge with the same problem and Samsung still has no clue.