Has anyone else installed the Tmobile Windows 6.5 upgrade on their device? I'm not able to use GPS - it's not in the Settings tab at all and Google Maps has the option disabled in the menu.
I am running the TMOUS ROM and my GPS works great!
AT&T
Thought this might be of interest to AT&T subscribers:
"AT&T needs to spend $5 Billion to catch up
by Dave Freeman on January 20, 2010
With all the crap that’s gone on (and still going on) between AT&T and Verizon, it’s safe to say that this is the last thing AT&T wanted to come out. According to a study that just came out, AT&T would have to spend approximately $5 billion US to get their network to the same level as Verizon and Sprint.
This probably doesn’t come as a surprise to anyone who actually owns an AT&T phone, given the almost constant problems with dropped calls, spotty service, and slow data speeds. The study also admits that AT&T has started to upgrade their infrastructure, particularly in the Bay Area, with positive results. This makes sense give the nature of their agreement with Apple."
[Via PCWorld]
I guess this explains a lot of the probelms that I've been having with connections and data speed.
soulthief said:
Has anyone else installed the Tmobile Windows 6.5 upgrade on their device? I'm not able to use GPS - it's not in the Settings tab at all and Google Maps has the option disabled in the menu.
Click to expand...
Click to collapse
That's strange... which radio are you using? There is a radio upgrade as part of the 6.5 updgrade. I tested the upgrade a few days ago and everything was working fine (except for all the stock stuff being there).
Hi,
I just received an unlocked International Galaxy Note II in the US. Ordered from Handtec in the UK, and the phone appears to be the French model. I have observed what I think is a problem when trying to use the phone on T-Mobile USA.
I put my T-Mobile USA SIM card in the phone, and the phone thinks I am roaming. Uhhhh no. It's a T-Mobile USA SIM card on the T-Mobile USA network. It is NOT roaming. Now, it probably doesn't have any impact beyond the "R" notifier, and a "Roaming" page which shows up on TouchWiz, but it DOES make me feel very uneasy. I have to enable "Data use while roaming" to be able to use data while on my home network!! It's crazy!
To those who will point out, yes, I know that T-Mobile USA has their 3G currently on the AWS 1700/2100 band, which the Note II does not support. I am therefore using EDGE with this phone. (Yes the data speeds suck, but T-Mobile's refarming will make this problem go away in the next few months). Even though I am on EDGE, I am not "roaming" unless the Note II's definition of roaming is different from mine. I am still on the home network, regardless of whether I am on 2G or 3G.
Has anyone else seen a problem like this?
If I can't figure this out in the next day or two, I may return the Note II and just wait another month or so for the T-Mobile US version. (Probably that's what I should do anyway, but I figured the GT-N7100 would get more developer support).
Hope someone can help!
Thanks!
Edit: I forgot to add - I also have and unlocked international Note 1 GT-N7000 and an unlocked iPhone 4. Neither possess the T-Mobile USA 3G band, and neither of which show roaming when I'm using T-Mobile USA. So, either T-Mobile did some funky network work today which changed something, or there is something different (and possibly a bug) about how the Galaxy Note II determines if it's roaming.
Unfortunately I cannot be of any assistance to your issue, just wanted to comment however. I find it very odd that ALL Note II's don't work on every frequency. Bear with me, I'm under the impression that they are identical hardware wise, every version. So, maybe it's a simple matter of flashing a different radio.img? Not that there are any available currently, but there will be shortly. I hope (think) it will be similar to the ATT Note on Tmo. Hopefully it works out better though. We still don't know if the Tmo Note II will be HSPA+42 or not, but it will support next years Tmo LTE.
So, as of now, this is a little bit of a disappointment for Tmo customers looking for the N7100. Hope you can find a workaround for at least HSPA+21 soon :good:
ccampbell1 said:
Hi,
I just received an unlocked International Galaxy Note II in the US. Ordered from Handtec in the UK, and the phone appears to be the French model. I have observed what I think is a problem when trying to use the phone on T-Mobile USA.
I put my T-Mobile USA SIM card in the phone, and the phone thinks I am roaming. Uhhhh no. It's a T-Mobile USA SIM card on the T-Mobile USA network. It is NOT roaming. Now, it probably doesn't have any impact beyond the "R" notifier, and a "Roaming" page which shows up on TouchWiz, but it DOES make me feel very uneasy. I have to enable "Data use while roaming" to be able to use data while on my home network!! It's crazy!
To those who will point out, yes, I know that T-Mobile USA has their 3G currently on the AWS 1700/2100 band, which the Note II does not support. I am therefore using EDGE with this phone. (Yes the data speeds suck, but T-Mobile's refarming will make this problem go away in the next few months). Even though I am on EDGE, I am not "roaming" unless the Note II's definition of roaming is different from mine. I am still on the home network, regardless of whether I am on 2G or 3G.
Has anyone else seen a problem like this?
If I can't figure this out in the next day or two, I may return the Note II and just wait another month or so for the T-Mobile US version. (Probably that's what I should do anyway, but I figured the GT-N7100 would get more developer support).
Hope someone can help!
Thanks!
Edit: I forgot to add - I also have and unlocked international Note 1 GT-N7000 and an unlocked iPhone 4. Neither possess the T-Mobile USA 3G band, and neither of which show roaming when I'm using T-Mobile USA. So, either T-Mobile did some funky network work today which changed something, or there is something different (and possibly a bug) about how the Galaxy Note II determines if it's roaming.
Click to expand...
Click to collapse
That happened to me as well using my International Galaxy S3, I dug into it for about a month and trust me, it's something with the phone detecting that it can't connect to the HSPA+ bands it supports, and when it "defaults" down to EDGE it considers it "Roaming". Stop digging for answers, I was at it for weeks, this is the reason.
You wont get charged for roaming or anything though, so use EDGE until T-Mobile's refarming finally happens; I waited for 2 months and nothing, so I jumped ship and got Straight Talk. I use over 15 GB of data a month, no throttling, $45 bucks. :good:
Hope this helps, because NO ONE gave me a straight answer, Dont even bother calling T-Mobile, they're of absolutely no help. I flashed all sorts of custom ROMs, Kernels, Network Tools, Diagnostics, etc. trying to figure it out. It's just the way these Samsung phones (GT-I9300 and N7100 by the looks of it) work when their 3G/HSPA+ bands are not supported.
Cheers!
farfromovin said:
Unfortunately I cannot be of any assistance to your issue, just wanted to comment however. I find it very odd that ALL Note II's don't work on every frequency. Bear with me, I'm under the impression that they are identical hardware wise, every version. So, maybe it's a simple matter of flashing a different radio.img? Not that there are any available currently, but there will be shortly. I hope (think) it will be similar to the ATT Note on Tmo. Hopefully it works out better though. We still don't know if the Tmo Note II will be HSPA+42 or not, but it will support next years Tmo LTE.
So, as of now, this is a little bit of a disappointment for Tmo customers looking for the N7100. Hope you can find a workaround for at least HSPA+21 soon :good:
Click to expand...
Click to collapse
farfromovin,
I agree it's a complete pain why one model can't work worldwide - or even between carriers in one country, the US!! I'm not sure that all the revisions are the exact same hardware though. Certainly the different revisions will support different LTE bands from one another, different 3G bands (ie T-Mobile USA) and even different technologies (VZW, Sprint, US Cellular CDMA). Whether there is one uber radio chip that's the same in all versions, with different bits enabled here and there, I don't know. I would doubt that a chip currently exists to support all GSM, UMTS, LTE and CDMA bands in the one, but you never know.
I really cannot wait (getting super sick of it) until T-Mobile's 1900MHz refarming, and finally all UMTS/HSPA phones will work on pretty much any UMTS/HSPA network worldwide. But just as we finally get 3G harmony, LTE comes along with a zillion different bands, and we're back to where we were at the start of GSM, and the start of UMTS - all over again.
As far as getting the GT-N7100 to work on T-Mobile AWS bands - unless the radio supports that band somewhere, and can be enabled by some hacky flashing, I don't think there's much chance. I followed a thread for a while which was trying to do that for the original GT-N7000 and it ended up nowhere unfortunately.
I'd be very, very surprised if the T-Mobile US official Note II did not support DC-HSPA +42. Given how TMO pushes that, I don't think they'd sell a phone without it these days. I'm kind of surprised the GT-N7100 doesn't have it, to be honest, but I guess it's not yet that widespread, and most carriers will bypass it to go to LTE.
Cheers!
Ars-Hexis said:
That happened to me as well using my International Galaxy S3, I dug into it for about a month and trust me, it's something with the phone detecting that it can't connect to the HSPA+ bands it supports, and when it "defaults" down to EDGE it considers it "Roaming". Stop digging for answers, I was at it for weeks, this is the reason.
You wont get charged for roaming or anything though, so use EDGE until T-Mobile's refarming finally happens; I waited for 2 months and nothing, so I jumped ship and got Straight Talk. I use over 15 GB of data a month, no throttling, $45 bucks. :good:
Hope this helps, because NO ONE gave me a straight answer, Dont even bother calling T-Mobile, they're of absolutely no help. I flashed all sorts of custom ROMs, Kernels, Network Tools, Diagnostics, etc. trying to figure it out. It's just the way these Samsung phones (GT-I9300 and N7100 by the looks of it) work when their 3G/HSPA+ bands are not supported.
Cheers!
Click to expand...
Click to collapse
Hey Ars-Hexis,
Thanks so much for the reply. I googled about the same issue on the i9300 as you mentioned - and sure enough a couple of threads on androidcentral, and tmobile support - and all with pretty much a bunch of people going "what?" I think you're right, and this is either some crazy change which Samsung has made to the "S3" generation of phones, or it's an unintended bug which was introduced. I contacted Samsung support on twitter but I'm sure they'll tell me to go away since this is an international model and not sold or supported in the US.
I would love to have this properly reported to Samsung though because it is NOT correct behaviour, and I'm sure it does not meet the 3GPP standard behaviour. These phones' definition of "roaming" is frankly wrong. It's possible they know about the bug but don't care about it too much, because it only affects the minority of importers or travelers, and then only on the very few networks which use AWS band for 3G.
The phone and data works fine of course, so it's really a cosmetic annoyance. However, if I was actually outside TMO's network without knowing it (maybe camping on to some network on the Canadian border or something) then I'd never know if I was actually roaming or not. So the phone's roaming indicator, by being permanently false, is useless in the times when I'm actually roaming. Since this is not a likely scenario for me to be on the Canadian border and roaming onto an AWS-only network any time soon, I'll not worry too much about it.
Yes, I'm really sick waiting on this refarming. It's a huge undertaking of course, so I understand why. I do have a Straight Talk AT&T SIM which I got for my Galaxy Note 1, however I don't use it often for several reasons: haven't ported my number to it, am wary about data throttling or cut-off, and I find the data hit or miss on Straight Talk anyway. I heard stories about people being warned or cut off after 100MB in any day, but if you're saying 15GB and no throttling, it may be something I want to put to the test!
Thanks a lot for your reply! It's nice to know I'm not crazy!
Cheers!
ccampbell1 said:
Hey Ars-Hexis,
Thanks so much for the reply. I googled about the same issue on the i9300 as you mentioned - and sure enough a couple of threads on androidcentral, and tmobile support - and all with pretty much a bunch of people going "what?" I think you're right, and this is either some crazy change which Samsung has made to the "S3" generation of phones, or it's an unintended bug which was introduced. I contacted Samsung support on twitter but I'm sure they'll tell me to go away since this is an international model and not sold or supported in the US.
I would love to have this properly reported to Samsung though because it is NOT correct behaviour, and I'm sure it does not meet the 3GPP standard behaviour. These phones' definition of "roaming" is frankly wrong. It's possible they know about the bug but don't care about it too much, because it only affects the minority of importers or travelers, and then only on the very few networks which use AWS band for 3G.
The phone and data works fine of course, so it's really a cosmetic annoyance. However, if I was actually outside TMO's network without knowing it (maybe camping on to some network on the Canadian border or something) then I'd never know if I was actually roaming or not. So the phone's roaming indicator, by being permanently false, is useless in the times when I'm actually roaming. Since this is not a likely scenario for me to be on the Canadian border and roaming onto an AWS-only network any time soon, I'll not worry too much about it.
Yes, I'm really sick waiting on this refarming. It's a huge undertaking of course, so I understand why. I do have a Straight Talk AT&T SIM which I got for my Galaxy Note 1, however I don't use it often for several reasons: haven't ported my number to it, am wary about data throttling or cut-off, and I find the data hit or miss on Straight Talk anyway. I heard stories about people being warned or cut off after 100MB in any day, but if you're saying 15GB and no throttling, it may be something I want to put to the test!
Thanks a lot for your reply! It's nice to know I'm not crazy!
Cheers!
Click to expand...
Click to collapse
Hey there! Sorry I hadn't answered in such a long time. We'll actually I've found that the S3 (sold it) and the Note 2 (own it) some how cannot be tracked for data usage correctly by straight talk. It's quite interesting... I ported my number over from T-Mobile, so if you have an S3 with a T-mobile prepaid sim... I think you have nothing to lose! I'm in Dallas and regularly get around 3-4Mbits/S during high usage hours and 6-7Mbits/S after 7 pm when network usage goes down.
There have been 2 occasions over the past 2 months where I'm throttled for like an hour and suddenly it gets uncapped on its own (?!?!?) lol. Last month I used about 25 GB... It's insane. Btw, if you if get throttled for real (happened to me once), you can just call them and say your "Internets is slow" (act technologically challenged) and they'll reset it.
Ah 1 last thing: I got the at&T ST sim card when I switched.
Cheers!
Sent from my GT-N7100 using XDA Premium HD app
I just got my International Note 2 today, and I am using it on the T-Mobile network also. I am seeing that I am roaming but my data is off and I am just using wifi. I have turned off my phone and back on again and its still showing. But after reading this whole thread I am getting that is a bug or something along those lines is that correct? Thanks.
I really need to know
Sent from my Nexus 4 using Tapatalk 2
roaming
I am on prepaid tmobile and I have Roaming sign only in areas where I used to loose signal with my old phone . Basically when I go in Garage underground my signal starts getting weaker and weaker and then roaming kiks in and signal is up all the way . T-mobile does not charges for local roaming . If you use USA tmobile and you are in usa you are fine . My texts and voice are still the same rate for me . When I had Chinese rom it was showing all the time , now I flashed German t-mobile and R shows only sometime , but it does not bother me .
Hope this helps .
I too have a Note II (GT-N7100) I purchased in Thailand in December. I use it on the T-Mobile network and have the same issues with the "R" symbol. I am located in Tampa Bay area, Florida.
T-Mobile was indicating to me in January that this was an issue in weaker signal areas for their data network as they prepare to refarm it. Don't know if this explanation is entirely accurate, but I find in my local area that the R symbol goes away in certain areas and it behaves "normally". This includes the area where my T-Mobile office is located. It seems to be somewhat of a patchwork network, and for some reasons certain areas cause it to go into the Roaming mode.
I was just on a trip with stops in Los Amgeles, San Francisco, and Philadelphia and noted the same behavior in some of those cities: Getting normal signal indications in some places, and Roaming in others.
Sup all?
Not much info on here for what I'm about to ask. So here we go..
I'd like to upgrade to the S4 from my beloved S3 for the faster data speeds, for online gaming. I was going to do the $0 down deal on tmobile.com yesterday but read about an LTE-Advanced capable s4 that was released in S.Korea not too long ago.
From what I've read, tmobile plans to roll out lte-a technology into their LTE-ready towers by year end. So if this is true, wouldn't it make sense that this lte-a version of the s4 would come to T-Mobile?
When I bought my current s3 (t999) at release, a short time later, the lte version comes out (t999L). When I bought my Samsung vibrant 2 years ago, a short time afterwards the "4g" version comes out as well. Samsung/tmobile seems to like playing this little game.
So I'm just curious on you guys thoughts on this. Buy the current s4 now or wait till the possible lte-a version comes to U.S. carriers?
Source 1: http://www.androidpolice.com/2013/0...4-lte-a-for-sk-telecoms-lte-advanced-network/
Source 2: http://bgr.com/2013/06/26/t-mobile-lte-advanced-features/
T-Mobile S3 / Hyperdrive RLS14
From what your second link says; it looks like LTE-A won't be a big priority and will probably be in a "testing" phase for awhile just like LTE was when they made that move. They'll put it in one specific city or area and test to see how well it does (it's what they've done in the past as well). More than likely they won't bring the S4 LTE-A over and just wait till more and more phones corporations start using it. They aren't going to focus solely on upgrading something they are still in the process of upgrading just for one phone...it's a stupid illogical move. Also who's to say that chipsets used in phones here will be able to support LTE-A (same reason the first S3 didn't have LTE).
You could jump in on the the $0 down now and get in on the JUMP! program so later you can just upgrade to the new phone if they do bring it.
T-mobile Just turned on LTE this summer i doubt that well see LTE-A in 2 years...
Hey All
Current Verizon M8 (rooted to GPE) user and I'm considering jumping to T-Mobile. I've loved the M8 and would intend on going with that device again if we make the switch. Planning on doing a Test Drive to get a feel of the network coverage in my area (Morris County, NJ).
Should all go well with that test, anything I should take into consideration with the T-Mobile version of the M8? Anything to be concerned with (rooting again, network radio capabilities, features, etc.)? Any past experiences of others switching to make note of?
Edit: Also, any success with using a Verizon M8 on the T-Mobile network? I'm savvy enough to make root-based mods if necessary. Wouldn't mind buying out the rest of my Verizon EDGE value on the phone to keep what I have.
Thanks for any input!
I also made the switch to t mobile from verizon. My first and only phone I have owned is the HTC Oe m8. The phone staright from TMobile came full of bloatware. 10+ apps of non sense. Coming from ios i had never rooted or unlocked a bootloader. I have to say it was super easy. TMobile does take awhile to realease updates but converting over to developer edition can take care of all that.
SiK TL said:
I also made the switch to t mobile from verizon. My first and only phone I have owned is the HTC Oe m8. The phone staright from TMobile came full of bloatware. 10+ apps of non sense. Coming from ios i had never rooted or unlocked a bootloader. I have to say it was super easy. TMobile does take awhile to realease updates but converting over to developer edition can take care of all that.
Click to expand...
Click to collapse
Tmobile updates faster than Version and att.[emoji1]
HTC One M8 from T-Mobile here. I switched from Verizon to T-Mobile a while back and was disappointed at first but T-Mobile is definitely upping their game and recently I haven't even looked back. The benefits to T-Mobile over Verizon? Much faster updates. Most devices are less locked down. Uses GSM version of the M8 (I don't believe the Verizon version is compatible but T-Mobile has a neat little monthly payment program that makes getting new phones feel easier) Did I mention the GSM M8 has a LOT more roms and support than the Verizon version? Oh, and you can get truly unlimited data without losing your ability to upgrade. And they don't throttle your data speeds like Verizon seems to do. In many areas T-Mobile has much faster 4G LTE speeds than Verizon.
But that's just everything I can tell you off the top of my head. For many devices, T-Mobile is the first to update their carrier branded devices and, in my opinion, the bloatware was never a big deal. Even found myself using most of what was provided.
At this point, I'd probably wait till the m9 if possible. If you can't, as much as I love my One, the G3 or Moto X would probably get my money on t-mobile. the M8 not having band 2 lte is a major annoyance for me.
TriBeard said:
At this point, I'd probably wait till the m9 if possible. If you can't, as much as I love my One, the G3 or Moto X would probably get my money on t-mobile. the M8 not having band 2 lte is a major annoyance for me.
Click to expand...
Click to collapse
Yeah, might as well wait. I like Hima plus 5.5". I just hope when we get lollipop update will have volte.
I would only switch if you live near a major city. Since your Verizon phone will only work on Verizon bands. T-mobile has different bands. I have a Verizon m8 and am on T-Mobile. Luckily I live within 5miles of Philadelphia,PA. I also enabled bands that are locked that can be found out how to do in the Verizon forum. I have excellent reception, lte data, and WiFi calling. But I can say from past users on forums, that the reception can be dreadful if you don't live near a major city due to the band frequencies.
We have lollipop, bad thing is no volte, @at&t probably get their updates next year.lol!!!
Hello fellas. . Long time that I hadn't been active in this forums.
Long story short. I bought the marvelous note 7 and I felt in love within minutes, a week later had to returned it. After that I tried the S7 edge, V20 and iPhone 7plus with no luck bc my note 7 left the bar way up there. So I downgraded to note 5
Bought one from Verizon and it was unlocked, it works once a changed the apn setting, same speed and all the goodies also. I have the unlimited plan from att and they forbid the hotspot with this plan. Is no way around it. But with the note 5 from Verizon I have unlimited hotspot just so u guys know. . The only one drama that I'm experiencing its that when I get an incoming call my data drops. . Can't get around the problem I had been playing w setting but just can't.
Any help or advice it's much appreciated it
Have a good day one guys and thanks
I have same issues I have a n920a on straight talk I constantly get Internet connection not active or something like that
I do know one of the differences between the two versions is that the Verizon phone lacks LTE band 17, AT&T's primary LTE band. I don't know if this is the core of your issue, but is a difference between the two.