Related
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.
It's my understanding that these features (advanced calling, like WiFi calling and VoLTE) Doo not work on unbranded devices like Pixel and others. This was the case with my unbranded SM935F or Galaxy S7 Edge until we got some files, an appropriate CSC, and also had AT&T switch our account to an IMEI of an AT&T branded device that had working WiFi Calling (others have apparently just called AT&T and had them provision WiFi Calling)
Note: for me, I have a business account so I could just go into my business portal and put in an IMEI that I got from an S7 Edge model in an AT&T store
I am attaching the files that we needed to add to our system to get WiFi calling to work on AT&T. I think I remember all I had to do was to add them and make sure permissions were correct
Here is an IMEI that I saw on another post that may work ..... But I do know that the AT&T system needs to recognize your phone IMEI as an att branded device that has working WiFi calling. So if you aren't business customers it will require a call to customer support.
Possible working IMEI:
Mod edit: Removed
Any Pixel AT&T users that could try this and report back would be greatly appreciated!
Btw, I'm not completely sure which files are needed in the Pixel as compared to the S7 Edge .... I would have a backup available
Here's link
https://drive.google.com/file/d/0B4qgtyu0rDEbU3dGNnhLZ0FXTWM/view?usp=drivesdk
File too late to upload here
You don't need any of that for WiFi calling or VoLTE. That all works fine on custom roms
spaceman860 said:
You don't need any of that for WiFi calling or VoLTE. That all works fine on custom roms
Click to expand...
Click to collapse
I obviously could be wrong ...... But I'm 99% sure that what you are saying is not true for AT&T and maybe even other USA carriers!
I KNOW that I'm right for S7 phones and ROMs .... And the problem is so pervasive that they have even been able to get unbranded S8's to obtain WiFi Calling on AT&T or other USA carriers (even though WiFi calling works great on branded S8 phones)
AT&T users a different mechanism to provision WiFi calling than other carriers
jcrompton said:
I obviously could be wrong ...... But I'm 99% sure that what you are saying is not true for AT&T and maybe even other USA carriers!
I KNOW that I'm right for S7 phones and ROMs .... And the problem is so pervasive that they have even been able to get unbranded S8's to obtain WiFi Calling on AT&T or other USA carriers (even though WiFi calling works great on branded S8 phones)
AT&T users a different mechanism to provision WiFi calling than other carriers
Click to expand...
Click to collapse
You are correct that AT&T does not allow unbranded phones to use those features. It's all BS too. I have great LTE coverage but many times I will go to make a call and have crap service because they have canabalized a lot of the hsdpa towers for LTE. Then the switch back to LTE can take forever. And I don't care what they or anyone says AT&T's hspa+ is no where near as fast
None of this works, as AT&T blocks access to VoLTE on Pixel phones. Denies me the use of Numbersync for my tablet and android wear 2.0 watches. AT&T service techs keep promising to fix it and try to force it to work, but still blocked. It is simply a situation for Google to get the Pixel certified for the AT&T network, which is problematic, as AT&T uses a non-standard protocol for HD Voice that is unique to their network. So, as best I can tell, AT&T has to release the source code, for a price, I presume, to Google to add to the phones and then pay for the certification process with the FCC. Seems a stand-off as long as Google has an "exclusive" arrangement with Verizon. So for me, I'm pissed not to have numbersync for my devices, but unwilling to give up all the advantages of the Pixel phone.
That's why I switched to T-Mobile.
So there is no way to get VoLTE on the Pixel XL with AT&T then?
Sent from my Pixel XL using Tapatalk
chipstien said:
So there is no way to get VoLTE on the Pixel XL with AT&T then?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Not currently
If AT&T carries the upcoming Pixel 2, is it possible Numbersync would start working on Pixel 1 devices?
jkimrey said:
If AT&T carries the upcoming Pixel 2, is it possible Numbersync would start working on Pixel 1 devices?
Click to expand...
Click to collapse
I doubt it. They only support advanced features on devices sold by them so it's not as if older Pixels will suddenly be grandfathered in just because they start carrying newer ones.
This annoys me to no end... If I buy a phone from att, do they have to give me an unlock code when the phone is paid off? I really need WiFi calling for a trip I make multiple times a year
Sent from my Pixel XL using Tapatalk
murso74 said:
This annoys me to no end... If I buy a phone from att, do they have to give me an unlock code when the phone is paid off? I really need WiFi calling for a trip I make multiple times a year
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I was able to get the code the same day or next for the att Note 8 that was bought from Samsung. The device is paid off.
muzzy996 said:
I doubt it. They only support advanced features on devices sold by them so it's not as if older Pixels will suddenly be grandfathered in just because they start carrying newer ones.
Click to expand...
Click to collapse
Yeah according to a rep I spoke with, the pixel 2 will support Numbersync even though att isn't selling them. There are, however, no plans to change the restriction on the original pixels.
I'm in the same boat but I'm genuinely curious - if I don't need wifi calling - is it really a big deal not having VoLTE? I'm taking in terms of better signal or faster LTE internet speed. Or does VoLTE is just having clearer phone calls? I guess what I'm asking is what other benefits are we losing (on a technical standpoint)
keplenk said:
I'm in the same boat but I'm genuinely curious - if I don't need wifi calling - is it really a big deal not having VoLTE? I'm taking in terms of better signal or faster LTE internet speed. Or does VoLTE is just having clearer phone calls? I guess what I'm asking is what other benefits are we losing (on a technical standpoint)
Click to expand...
Click to collapse
Late response but as far as AT&T goes besides VoLTE what I experienced on my Pixel XL was random issues with group text (MMS) reception from certain individuals from other carriers.
In particular it seemed as though if senders of MMS texts to a group chat that I was participating in sent a text from a carrier like T-Mobile and they were using Samsung devices with VoLTE and enhanced LTE stuff enabled on their end I'd not receive the text. I would instead receive texts from others in the conversation. I could freely text any of the same individuals in a separate standard SMS conversation just fine, and they could send me an MMS text like a photo, but as soon as we were in group MMS I'd lose the ability to receive their texts and no amount of APN changes or combinations of texting apps would fix it.
I can't tell you how many times over the course of the first 5 months of owning my Pixel XL with an AT&T SIM in it I missed out on half the conversation in group MMS. Doing nothing to my phone other than porting number to T-Mobile and putting in my new T-Mobile SIM all of my group MMS issues went away (replaced with ****ty signal LOL but that's a different story). I'm now on Verizon with my XL and am a happy camper, albeit poorer having wasted money jumping around.
Needing help, I have had the Galaxy Note 8 since it was released and I love the phone, but we switched to Total Wireless because it was half of the price of Verizon and now we cant get our VoLTE to work. Working with support on this is like asking my 6 year old niece to help, so this is the only place I know to go to.
I have done a software update with Samsung Smart Switch on my computer and the Build Number is N950USQS7DSK6
I have used the 4G LTE/3G Network Secret Setting app to check the provisioning settings on the phone and I have enabled the VoLTE after the software update.
I'm still not getting VoLTE when I make a phone call. Total Wireless says that my phone isn't compatible but that's ridiculous because they run off of Verizon's network and I am using a Verizon phone. I asked them to contact Verizon about the provisioning and they said they can't do that. I know that is a lie because I used to work Advanced Tech Support for T-Mobile and worked with Tracfone daily changing provisioning settings and providing support. My sister in law has a Verizon Samsung Galaxy S8 and her VoLTE works just fine. I know its a different model, but the phone is from the same year and has all of the same features. I know Total Wireless sells a Galaxy Note 8 that works with VoLTE so I wonder if I could flash that rom to my phone? I have done this with an ATT Note 2 once to get it to work with Wifi Calling on T-Mobile, so I dont see why it wouldnt work here. Unless anyone has a custom rom that will enable the VoLTE for me. I know the phone is two years old but I would have to upgrade 4 cell phones and that seems ridiculous to me when these phones are working perfectly fine.
Anyway, my biggest concern is that Verizon will be removing the 3G and below networks so my phone will be useless. If anyone has any help with this, please reply!
I made a call and got a message that my phone would no longer work on their network since they are upgrading things. This phone isn't that old. I wonder if their system doesn't recognize it. The lady said their system was showing it was a 2g phone so I told her it handles 4g. She said on Cricket it's only able to use 3g. Does anyone know if this is true. I don't trust some operator in another country reading off a script. It sounded like they want everyone to buy phones from their website. I can't imagine a relatively new phone not having the right band. Maybe there is a setting I need to tweak or flash onto my phone if I'm only using 3g on Cricket. I'm sure I've seen my antenna say LTE. Or maybe Cricket is screening out non Cricket phones.
Check it's specs.
If it supports the needed 4G bands it may need to be reconfigured. I haven't a clue how to do that.
Maybe Access point names but it may go deeper than that.
I'm going to google and see exactly what specs Cricket will require. I think you're right and maybe something to reconfigure. I can't imagine Cricket shutting off tons of new ish phones just because they aren't bought from Cricket. Ran a speed test now and got 2.77mbps download and 8.49mbps upload. I am showing LTE now which means I'm not on 3g as she was saying now. I bet it's a sales gimmick to scare less savy folks. What mean loose phone signal in Feb hehehe.
Edit: I was on wifi when I got the message so maybe when I phone is on wifi and not using their LTE network it doesn't detect anything which is why they told me I have a 2g phone. When I shut off wifi LTE popped right up so it's probably a glitch in their way of informing us.
Edit2: Spoke to a tech at Cricket and he said my phone currently isn't compatible with them aaahahahhaha dumb. I told him I'm currently using it on LTE just fine no issues. He didn't have anything to say when I asked him since I'm not using 3g then it shouldn't affect me. He just said he wants me to have great service so buy another phone from Cricket. BS
Only HD1905 works
bhaliyo said:
Only HD1905 works
Click to expand...
Click to collapse
I have HD1907 and it's currently working on LTE. Are you referring to not working in the future or currently working?
jeffrimerman said:
I have HD1907 and it's currently working on LTE. Are you referring to not working in the future or currently working?
Click to expand...
Click to collapse
Not working in the future. Here is the list of devices can work after Feb 2022.
bhaliyo said:
Not working in the future. Here is the list of devices can work after Feb 2022.
Click to expand...
Click to collapse
That link keeps rerouting to an ATT samsung S21 advertisment. I'll try to google the list
jeffrimerman said:
That link keeps rerouting to an ATT samsung S21 advertisment. I'll try to google the list
Click to expand...
Click to collapse
See the attachment above
Yes I
bhaliyo said:
See the attachment above
Click to expand...
Click to collapse
Yes I was able to download that list when I googled. Judging by what it said these are phones that are tested and will work, not so much that other phones won't work. My phone was originally branded for Tmobile so I'm sure they wouldn't have tested it but it would have only had a different OS with Tmobile bloatware which I took off. The cricket people said their LTE isn't changing so I shouldn't have an issue but it will be interesting to find out. They must have just been looking at this list which is why they said my phone currently isn't compatible.
Funny this was asked but no answer given from ATT. I'll keep googling
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
I read a discussion here from 2019 someone else asked and the different variants are by region as they usually are for the different LTE frequencies. 1905 is North American, 1907 is Tmobile in North America so I would imagine my LTE frequency is still going to be fine. Those that bought Chinese phones etc probably not.
This is weird. The current ad for it on Amazon says it's currently not compatible with ATT and Cricket. I wonder if me flashing another OS for North America or USA I forget is why it works fine? Maybe I'm screwed hehe
*** NOTE: Due to changes with AT&T and Cricket, this phone currently cannot be used on AT&T/Cricket. Compatible with T-Mobile and all GSM Networks along with their compatible MVNO networks such as Red Pocket GSM, Ultra Mobile, Mint Mobile, Ting GSM, Google FI and many others. This phone is NOT compatible with Verizon, Cricket or AT&T. Please verify with your network to ensure complete compatibility.
Spoke to a tech at Cricket and he said my phone currently isn't compatible with them
Click to expand...
Click to collapse
I work at a prepaid carrier store (not Cricket) and am having to tell customers the same thing. It's not just about if your phone has the radios necessary, they have to have the IMEI approved in their system and if it's not then you can possibly escalate to someone who can help get it approved but you probably won't get very far. I can't activate my own OnePlus device with my company either, even though it's currently running on our parent network. I have spoken with internal support folks about it multiple times and have gotten nowhere so I gave up.
jeffrimerman said:
I can't imagine Cricket shutting off tons of new ish phones just because they aren't bought from Cricket.
Click to expand...
Click to collapse
Believe it. It sucks and it sounds insane but it's really happening. For me? I have to tell everyone with a Samsung Galaxy S5-S10 that they have to buy a new phone to be compatible with our new network changes. And I can tell you here that it's (probably) not the sales rep lying to you to make a commission sale, our tools are indeed forcing us to do that.
jtaylor991 said:
I work at a prepaid carrier store (not Cricket) and am having to tell customers the same thing. It's not just about if your phone has the radios necessary, they have to have the IMEI approved in their system and if it's not then you can possibly escalate to someone who can help get it approved but you probably won't get very far. I can't activate my own OnePlus device with my company either, even though it's currently running on our parent network. I have spoken with internal support folks about it multiple times and have gotten nowhere so I gave up.
Believe it. It sucks and it sounds insane but it's really happening. For me? I have to tell everyone with a Samsung Galaxy S5-S10 that they have to buy a new phone to be compatible with our new network changes. And I can tell you here that it's (probably) not the sales rep lying to you to make a commission sale, our tools are indeed forcing us to do that.
Click to expand...
Click to collapse
I'm just wondering why they are saying my phone currently isn't compatible when it obviously is. It works great. Even streams HD in an instant on Crickets network. Corporations aren't super efficient at checking all things under the sun. They are just checking phones they approve. They told me the same thing that my imei currently doesn't work but it does. Unless they are trying to be like Verizon and only allow specific phones in the future I'm still thinking once they shut off 3g then when someone wants to switch from Tmobile to Cricket with their unlocked working fine non 3g phone they still can or are they saying no they are going to be like Verizon and it has to be a Cricket branded phone. I don't think it's the later. I think they are just saying what will work, but not saying what won't work. Let's find out =( hehe
Read a discussion from 8 months ago. Seems like most are fine, one guy with a 1905 had issues on ATT. One guy did what I did so maybe that's why mine is fine for now. I haven't had issues like dropped calls etc but maybe the real issue I will have if Cricket adds wifi calling and VoLTE is if they use a specific frequency and the 1907 is missing it then I won't be able to use those. If Cricket only uses VoLTE then yes I am screwed in February =/
https://www.reddit.com/r/oneplus/comments/kf0hfo
"I am currently using a 7t that was advertised as factory unlocked on ebay, when it showed up and I turned it on the big bright pink Tmobile boot logo came by. I did some research and found the convert to international/global thread on xda, I got rid of the crap hydrogen OS that came with the "unlocked" Tmobile phone. Using ADB I was able to flash the international firmware Oxygen OS and haven't had any problems with at&t now."
If it's an IMEI issue, flashing with the hd1905 fw probably won't help matters. I have a hd1905 on cricket since 2019, everything but wifi calling works. The same cricket sim in a samdung s9+ yields working wifi calling.
So while the hd1905 and 1907 are essentially the same hardware devices, the serial #/imei may determine what happens come 2022.
gpz1100 said:
If it's an IMEI issue, flashing with the hd1905 fw probably won't help matters. I have a hd1905 on cricket since 2019, everything but wifi calling works. The same cricket sim in a samdung s9+ yields working wifi calling.
So while the hd1905 and 1907 are essentially the same hardware devices, the serial #/imei may determine what happens come 2022.
Click to expand...
Click to collapse
Yup, I'm wondering if the hardware or the IMEI will determine things. I didn't even know Cricket had wifi calling. Did Cricket even let you download the wifi calling app but it didn't work or did they not allow you to download it?
Edit: I looked it up. Looks like wifi calling will work on phones that have it built in to their OS settings. I probably won't use it if I end up buying another OnePlus phone. I wonder if there are any phones where wifi calling is working on Cricket that isn't on the list but is in the OS settings.
Wifi calling app? The s9+ was hybrid flashed. Everything but the main OS came from the U firmware (carrier), while the rom came from U1 fw. Result was working carrier features (volte/wifi calling) without the bloat.
gpz1100 said:
Wifi calling app? The s9+ was hybrid flashed. Everything but the main OS came from the U firmware (carrier), while the rom came from U1 fw. Result was working carrier features (volte/wifi calling) without the bloat.
Click to expand...
Click to collapse
The s9+ is probably the same as the s9 as far as the wifi calling since "+" isn't mentioned on their list.
Huh? It's right under the s9.
I have a Samsung S21FE (Snapdragon) model SM-G990U bought from Samsung and originally configured for Verizon. I've used it on the Verizon network since I got it, but just recently switched to T-Mobile. The phone is still using the Verizon firmware however data IS working, as well as calling, texting, and voicemail. But there are still a few things that don't seem quite right and I'm wondering if a firmware update would solve it (also, what is the best to update the firmware?).
For instance, I used to see "5G UW" when I was on Verizon, and now on T-Mobile it should display "5GUC" but I'm just seeing "5G". Also, when it boots up I still see the Verizon logo. Also, even when it's displaying "5G" I am not getting true 5G speeds --> more in the range of 70-100 Mbps. I use the OpenSignal app and it tells me other T-Mobile users in my area are getting way faster speeds. I thought the S21FE had all the necessary bands to get full 5G but either it doesn't, or maybe the firmware is blocking it?
For comparison, we also just switched my daughter's Galaxy S21 at the same time from Verizon to T-Mobile. On her phone, the first time she booted up with the T-Mobile SIM card, she started seeing the T-Mobile logo on bootup and now she sees "5GUC" next to her signal (I do not).
In the Software information section under Service provider software version, my phone has: SAOMC_SM-G990U_OYN_VZW_13_0017 VZW/VZW/VZW.
My daughter's S21 now says "TMB" in her software version.
It seems like her phone automatically updated the firmware over to T-Mobile but mine did not.
Again, not sure if a manual firmware update would solve any of the above issues, and what is the best way to change the firmware. Anyone have any experience with switching carriers on a S21FE? Did you update firmware?
skokielad said:
I have a Samsung S21FE (Snapdragon) model SM-G990U bought from Samsung and originally configured for Verizon. I've used it on the Verizon network since I got it, but just recently switched to T-Mobile. The phone is still using the Verizon firmware however data IS working, as well as calling, texting, and voicemail. But there are still a few things that don't seem quite right and I'm wondering if a firmware update would solve it (also, what is the best to update the firmware?).
For instance, I used to see "5G UW" when I was on Verizon, and now on T-Mobile it should display "5GUC" but I'm just seeing "5G". Also, when it boots up I still see the Verizon logo. Also, even when it's displaying "5G" I am not getting true 5G speeds --> more in the range of 70-100 Mbps. I use the OpenSignal app and it tells me other T-Mobile users in my area are getting way faster speeds. I thought the S21FE had all the necessary bands to get full 5G but either it doesn't, or maybe the firmware is blocking it?
For comparison, we also just switched my daughter's Galaxy S21 at the same time from Verizon to T-Mobile. On her phone, the first time she booted up with the T-Mobile SIM card, she started seeing the T-Mobile logo on bootup and now she sees "5GUC" next to her signal (I do not).
In the Software information section under Service provider software version, my phone has: SAOMC_SM-G990U_OYN_VZW_13_0017 VZW/VZW/VZW.
My daughter's S21 now says "TMB" in her software version.
It seems like her phone automatically updated the firmware over to T-Mobile but mine did not.
Again, not sure if a manual firmware update would solve any of the above issues, and what is the best way to change the firmware. Anyone have any experience with switching carriers on a S21FE? Did you update firmware?
Click to expand...
Click to collapse
What's the model number?