Related
I've searched and didn't find any thread with this kind of issue specifically. I have a Verizon Galaxy S4 that doesn't seem to like GSM SIM cards; it looks like it is not GSM unlocked. I have tried every trick to get it to switch to GSM but it doesn't. I have flashed the same version firmware it came with (ME7) just to be certain it's factory restored, and also updated to MK2, yet no GSM. It sees the SIM card but doesn't show a signal, even when I manually switch to GSM/UMTS. I have programmed a CDMA number on it manually then tried the GSM switch again, yet no GSM signal. It sees CDMA signal fine though and can even make calls on CDMA. I even had to check the MEID/IMEI and it came back clean so I'm just surprised at all this. I have done this before successfully on a Verizon S3 and it worked well, how come the S4 has refused to work on GSM?
Please help, anyone?
Did you input APN's?
I thought APN settings had to do with data. I will do that now. I'm willing to try anything now.
Thanks.
I am having the same issue with a couple s4s from verizon as well. Checked the IMEI/MEID and they come up clean but they will not catch a signal with a gsm SIM card. I have tried several active AT&T and T-mobile SIM cards in the phones with the same results, no service/signal. Very strange as I have never had an issue with verizon S4s working on AT&T or T-mobile. The weird thing is that with a verizon SIM they catch signal and 4G just fine. Toggled GSM/CDMA and put in APNs and still no luck. I'll keep trying to work this out but right now I am stuck.
I had the same problem here
My GT-I9505 Rom Stock 4.4.2 ZTO(Brazil) had the same problem about signal problem.
Everytime i lock my phone (turning off the screen), by the time i light it on (lock screen), immediatelly my phone turns the signal to "No service".
In this time, i need to wait 1-2 minutes to the phone turns okay. Just wait.
I search for a lot of solutions and didn't find anything.
Notice too that the problem appears only network 2-3g. 4G didn't have the problem.
I solved this problem after Lollipop update. The problem simple dissapear!
(Sorry my bad english)
This may be totally obvious and non informative to some and for that I apologize, but I'm putting it out there anyways.
I recently traveled around South Africa for a bit and was able to use my Verizon LG G3 VS985 rooted bumped running official CyanogenMod 11 latest nightlies (via cyandelta) with absolutely no problems. I put the Vodacom sim (South African cell company) in the phone and it worked perfectly. I was able to get HSPA, 3G, and EDGE without any problems and no modifications made to anything. The phone did all the work automatically.
Supposedly there was LTE available in some parts of the country, but I could never get it. I tried switching APNs, changing radio radio bands in the *#*#4636#*#* and still could not get it. I was tempted to try and unlock the other LTE bands (as seen in a thread that I'm too lazy to look up at the moment) but I decided to hold off until later.
I also put the Vodacom sim into my LG G2 that was running a stock rooted something and that worked perfectly too(still no LTE). Was weird using that again though after the G3. Made me really appreciate the bad ass-ness of the G3.
Anyways hope this was not a waste of post. Rock on G3
Always good to hear a firsthand account from a traveler.
It would be useful if you could post what you used for APN entries as well.
trent999 said:
Always good to hear a firsthand account from a traveler.
It would be useful if you could post what you used for APN entries as well.
Click to expand...
Click to collapse
All the APNs were auto populated and I just experimented with a couple different ones. Vodacom.sa and vodacom.lte.sa were the two that I tried. Ended up just keeping it on the LTE one hoping that it would pick up LTE at some point. Both APNs gave me similar performance and service. I never had to mess with the actual APN settings or manually input anything.
That's great, but pretty strange since the vs985 requires a new APN setting to be manually entered in the USA each time I switch to either my T-mobile or AT&T sim.
Sent from my VS985 4G using Tapatalk
OK, so I was with T-Mobile forever, and I bought this phone from them at launch. I decided to switch over to MetroPCS by T-Mobile because it's cheaper, so I paid off my phone then unlocked it (Even though I didn't need too, the Metro SIM worked in it before I unlocked it).
It worked fine for two weeks, and I had WiFi calling and everything, and then the RJ5 (I believe?) update came out, and when my phone booted up it said new sim detected, and WiFi calling was gone. My APN settings were set to MetroPCS', so I set it back to the T-Mobile one since it's essentially the same network, but the WiFi calling option is *completely* gone; it's not there, trust me. I call MetroPCS support and they said they can't enable it for devices that weren't bought from them, and I tried to argue like sure you can, send it up to a higher level support team, but I could hardly understand her and gave up.
I went into a MetroPCS store and they had a spare T-Mobile SIM, popped it in, boom WiFi calling was back.
Come OneUI Pie update one, I opt in and update, and voila, WiFi calling is back!
I just downloaded the second update last night, and now it's gone again. This **** is driving me crazy, if anyone can help me figure out a way to fix this I will love you forever.
Wow, that was a gripping good yarn! I think there's a good chance that if you switch to the unlocked G965U1 firmware, it might work. I have an unlocked Verizon S9+ running on TMO, and once I flashed it to U1, wifi calling and volte worked automatically. I'm not positive how it will be with Metro but it is worth looking into. When you flash the collect unlocked firmware, when the phone boots up it will detect your sim and then reboot and configure all the settings for you.
P.S. I don't suppose there's Metro firmware out there?
I don't think there's Metro firmware, because my updates still come from T-Mobile. T-Mobile owns Metro. So what you're saying is flash the firmware via Odin and my phone would be like truly unlocked and I would get updates from Samsung rather than T-Mobile? I don't want to go through all this if it isn't a a certain fix, but sadly there's no way to tell that.
YrrchSebor said:
Wow, that was a gripping good yarn! I think there's a good chance that if you switch to the unlocked G965U1 firmware, it might work. I have an unlocked Verizon S9+ running on TMO, and once I flashed it to U1, wifi calling and volte worked automatically. I'm not positive how it will be with Metro but it is worth looking into. When you flash the collect unlocked firmware, when the phone boots up it will detect your sim and then reboot and configure all the settings for you.
P.S. I don't suppose there's Metro firmware out there?
Click to expand...
Click to collapse
I don't think there's Metro firmware, because my updates still come from T-Mobile. T-Mobile owns Metro. So what you're saying is flash the firmware via Odin and my phone would be like truly unlocked and I would get updates from Samsung rather than T-Mobile? I don't want to go through all this if it isn't a a certain fix, but sadly there's no way to tell that.
For some carriers, the Wifi calling requires the phone to have carrier firmware. Verizon is one. I bought my 9+ from Samsung unlocked, and it didn't have wifi calling on Verizon until I reflashed the phone (using Patched ODIN) to a Verizon firmware and Wifi calling works... as does the Verizon bloat, but most of that can be disabled with Package Disabler pro or similar app.
creedicd said:
For some carriers, the Wifi calling requires the phone to have carrier firmware. Verizon is one. I bought my 9+ from Samsung unlocked, and it didn't have wifi calling on Verizon until I reflashed the phone (using Patched ODIN) to a Verizon firmware and Wifi calling works... as does the Verizon bloat, but most of that can be disabled with Package Disabler pro or similar app.
Click to expand...
Click to collapse
I don't think MetroPCS has it's own firmware for the s9+. Plus, they're owned by T-Mobile now. The plan I'm on is called MetroPCS by T-Mobile lol. This is driving me nuts.
C-4Nati said:
I don't think MetroPCS has it's own firmware for the s9+. Plus, they're owned by T-Mobile now. The plan I'm on is called MetroPCS by T-Mobile lol. This is driving me nuts.
Click to expand...
Click to collapse
Out of curiosity I read around a little bit and it seems to be really hit and miss, which definitely seems to match up with your experience. I did find this post on Reddit from someone saying they got Wi-Fi calling to work with a Metro Sim: https://www.reddit.com/r/tmobile/co...g_volte_not_working_with_metropcs_sim/cymnvhf
Have you come across that, tried any of that?
YrrchSebor said:
Out of curiosity I read around a little bit and it seems to be really hit and miss, which definitely seems to match up with your experience. I did find this post on Reddit from someone saying they got Wi-Fi calling to work with a Metro Sim: https://www.reddit.com/r/tmobile/co...g_volte_not_working_with_metropcs_sim/cymnvhf
Have you come across that, tried any of that?
Click to expand...
Click to collapse
I have not, thanks for the link, I shall try that. Funnily enough, there was a hotfix pushed out last night and WiFi calling not working was on that list. I now have the WiFi calling icon in the notification bar, and it shows like it's on, but it doesn't actually work, and me pressing it does nothing. The setting itself still isn't in connections or anywhere in the settings. This is so dumb, lol.
Hey guys,
After using my V30 for a few days I realized I couldn't make or receive calls. This is weird because everything else works. The carrier is cricket.
I suspect a VoLTE configuration issue, but I don't know enough to dig into that.
Here's everything I know:
Old phone works with same SIM
SMS, MMS, and LTE data all work on V30
when placing calls, phone just says "calling" for 15-30s before showing "call ended"
when receiving calls, caller hears ring before going to voicemail
phone is new H931 frankensteined to US99820b/20h (have tried both)
Have tried reboot/reset several times
Cricket support was not much help and I don't have high hopes for LG support. Anyone experience a similar issue with their V30 or know enough about the secret menu to troubleshoot?
Thanks
I have had the US998 for 9 months and have had similar issues. I also have Cricket and for the first month, before I even rooted it, I had great service with the phone. Then I unlocked the bootloader and rooted it... Ever since I've had poor reception with the phone almost anywhere, especially when indoors. I have fine 4G internet speeds but have to go outside to make any phone call. I'm currently on rooted stock Pie through TWRP zip but I've tried countless Oreo roms, stock included, but the same problem has been with the phone for the past 7 months. I've tried every APN setting there is but keep in on global normally. Is it possible that we've messed up our modem partition? I'd think Cricket would use the same LTE bands as AT&T but I could be wrong.
johnnokomis said:
I have had the US998 for 9 months and have had similar issues. I also have Cricket and for the first month, before I even rooted it, I had great service with the phone. Then I unlocked the bootloader and rooted it... Ever since I've had poor reception with the phone almost anywhere, especially when indoors. I have fine 4G internet speeds but have to go outside to make any phone call. I'm currently on rooted stock Pie through TWRP zip but I've tried countless Oreo roms, stock included, but the same problem has been with the phone for the past 7 months. I've tried every APN setting there is but keep in on global normally. Is it possible that we've messed up our modem partition? I'd think Cricket would use the same LTE bands as AT&T but I could be wrong.
Click to expand...
Click to collapse
I have no problems with AT&T signal on my rooted US998 V30+.
No, you haven't messed up your modem partition.
I have AT&T Prepaid. The only difference between that and Cricket is I have actual AT&T data servers (vs Cricket data servers) and my speeds are not capped. You're never going to see the speeds I have, because AT&T caps Cricket at 8mbps.
Why are you using "Global"? You should be using settings similar below: GSM/HSPA (sometimes called WCMDA)/LTE. Don't confuse "WCDMA" with "CDMA". They are totally different. WCDMA is HSPA, if you don't see HSPA in your settings.
GinR said:
Hey guys,
After using my V30 for a few days I realized I couldn't make or receive calls. This is weird because everything else works. The carrier is cricket.
I suspect a VoLTE configuration issue, but I don't know enough to dig into that.
Here's everything I know:
Old phone works with same SIM
SMS, MMS, and LTE data all work on V30
when placing calls, phone just says "calling" for 15-30s before showing "call ended"
when receiving calls, caller hears ring before going to voicemail
phone is new H931 frankensteined to US99820b/20h (have tried both)
Have tried reboot/reset several times
Cricket support was not much help and I don't have high hopes for LG support. Anyone experience a similar issue with their V30 or know enough about the secret menu to troubleshoot?
Thanks
Click to expand...
Click to collapse
1) Check your APN. Make sure it's set to what you need for Cricket. Google Cricket APN.
2) You are not currently using AT&T firmware, so you will not have VoLTE. You need to turn VoLTE off in the settings if you see it. AT&T only allows certain phones on Cricket to use VoLTE -- and you currently have "US998", not H931.
If you see VOLTE setting turn it off, see if your phone calls can be made? Trying to use the VoLTE setting when you aren't allowed VoLTE will cause phone calls to fail.
If you bootloader unlock your phone and re-flash the AT&T H931 TWRP flashable zip, it's possible you get VoLTE IF Cricket is allowed VoLTE on H931 phones. Many AT&T postpaid customers are using rooted, bootloader unlocked H931 phones and have VoLTE because they flash to the H931 TWRP flashable zip.
What was your previous phone? Just saying your "old phone" tells us nothing whatsoever. Was it AT&T branded?
Are you sure you had VoLTE on your old phone with Cricket? Or you just assume you did? If it was an iPhone, then it's possible you had VoLTE on Cricket. If it wasn't, then you may just be assuming you did. I'm not current with the phones which have VoLTE with Cricket, I just know it has been very few.
Because AT&T keeps VoLTE as a premium feature -- although they have been giving it to more phones recently. But still usually with AT&T branded phones (which my US998 V30+ is not). I do not have VoLTE on AT&T Prepaid with my US998 -- and I couldn't care less.
You don't actually need VoLTE. When you make a phone call your phone can drop down temporarily to HSPA while you have the phone call and you will still have data. When the phone call finishes your phone will then return to LTE.
I have AT&T Prepaid, as does my wife and my mother -- and all our US998 V30/V30+ phones do exactly that. We do not have VoLTE and don't care.
See screenshot. If you find this setting, turn off VoLTE see if you can make/receive phone calls until you can flash the H931 TWRP flashable zip. But also find out if AT&T H931 can use VoLTE on Cricket.
LG V30 AT&T H931-20Q ROM
https://forum.xda-developers.com/lg-v30/development/lg-v30-att-h931-20f-rom-t3872926
Thanks for the detailed response.
My previous Cricket LG M327 definitely has VoLTE on Cricket per this list:
cricketwireless[dot]com/support/great-big-network/compatible-phones.html
There's also a settings option for it, and I can tell the difference between calls with/without.
If AT&T considers it a premium feature, you're probably right that it's limited to branded phones.
On my V30 I don't see an option for VoLTE in the option menu. I also don't have nearly as many options for mobile network mode as you do.
I will try flashing H931 to see if that changes anything.
GinR said:
Thanks for the detailed response.
My previous Cricket LG M327 definitely has VoLTE on Cricket per this list:
cricketwireless[dot]com/support/great-big-network/compatible-phones.html
There's also a settings option for it, and I can tell the difference between calls with/without.
If AT&T considers it a premium feature, you're probably right that it's limited to branded phones.
On my V30 I don't see an option for VoLTE in the option menu. I also don't have nearly as many options for mobile network mode as you do.
I will try flashing H931 to see if that changes anything.
Click to expand...
Click to collapse
Check your APN also?
ChazzMatt said:
Check your APN also?
Click to expand...
Click to collapse
I did check that. All correct.
I went to try it this morning and suddenly it worked on US99820b. I refurbished to 20h which is the version I want and switched to LTE/GSM network mode and it works.
Thanks for your help.
It worked for a day or so, then stopped working again. I think the issue is that Cricket is trying to provision the phone for VoLTE, but then their backend won't actually allow this IMEI to make VoLTE calls. I obtained an active SIM on another carrier and confirmed that the handset can make/receive both VoLTE and non-VoLTE calls.
Do any of you guys know how to disable VoLTE via adb/hidden menus? There is no option in the normal Settings menu with the cricket sim installed. My other option is to switch carriers.
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
Carrier texts should theoretically still work as they are "data". It's the "voice" part of VoLTE that won't work. That's why I can still receive carrier texts on my Galaxy Note 9 with AT&T -- which still has older firmware (so I can be rooted). A few months ago, I lost the ability to make/receive phone calls on my AT&T number when 3G towers were decommissioned in my area... But luckily I have Google Voice number, which also uses "data" (VoIP) so I make/receive all my Google Voice phone calls. (That's been my main phone number for years.)
However, I no longer can make/receive AT&T phone number calls -- which is fine. I switched Google Voice settings to data/Wi-Fi only instead of piggy backing on carrier phone number. Yet, I still receive AT&T texts, which is good because my bank insists on using a "real" (carrier) phone number for SMS security code confirmation.
Amer28 said:
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Click to expand...
Click to collapse
You are in Portland? What carrier are you using that still has 2G and Edge?
ChazzMatt said:
You are in Portland? What carrier are you using that still has 2G and Edge?
Click to expand...
Click to collapse
I'm with a company that uses T-Mobile towers. I connect just fine with 4G LTE, and get reasonably good speeds over it. But when I'm on 4G, I cannot make or receive calls or text. It says Emergency Calls Only.
So far, I've tried everything. I resettled network. I looked for different APN values that may fix the issue. When I couldn't think of anything else, I did a factory reset. (I mean, I wiped Data, and all other partitions in TWRP except for System and SD Card.) There have been no changes.
I'm starting to think the issue may be hardware, I did drop the phone a couple of times the day it stopped working. Though I usually end up dropping the phone once a day or every two days. I can't believe the screen hasn't cracked yet, at all. Could a drop from 3-4 feet on hard surface like tiles damage the antenna in such a way that only 4G data works?
I'm ready to give up and buy a new phone even though I can't really afford it. It would be awesome if I can get this to work.
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
I want to also mention that my carrier website has been talking about a data migration that would affect phones using their old SIM Card.
When I saw that, I called them and had them send me a new SIM. I thought surely this must be it, but the new SIM works exactly like the old one.
Perhaps the migration or whatever it is they did that required new SIM cards just doesn't work well with my phone? Even though, before putting the order in, the rep I spoke to did check my IMEI and said that my phone is compatible.
Agreed, it doesn't sound like an IMEI issue.
FWIW, I showed a 4G connection on a phone (I don't remember if it was my V30 or a Galaxy S10+ that I was going to replace it with). On that phone, at one point, but there was no actual connection. So, the indicators aren't always accurate. That's why I thought maybe the data isn't really working, and if data isn't working then VOLTE won't work... and with many of the carriers switching off non-VOLTE calling, that could kill the ability to make calls?
In your case, you said data worked... but if VOLTE was never enabled, and the carrier dropped non-VOLTE, then, again, you may lose calling.
In any case, these were my theories. I think you're on top of the situation but I don't have any other ideas for you to try...
Instead of buying a new phone, have you considered installing and setting up Google Voice, as ChazzMatt said? I recently had to do that because AT&T's 3G shutdown meant that I could no longer place or receive calls. My quick guide on doing that is here: https://forum.xda-developers.com/t/...-based-custom-roms-when.4138223/post-87342453
I don't know why you can't also send or receive texts, but the Google Voice app has the ability to do that, so maybe try using that after you've set it up.
Amer28 said:
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
Click to expand...
Click to collapse
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
ChazzMatt said:
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
Click to expand...
Click to collapse
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Amer28 said:
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Click to expand...
Click to collapse
tried a rom on a j7 2015 because android 6 is going to be left and I only get emergency calls on lte and on 3g, no problem. It's not imei problem maybe exynos processor. I went back to 6.0.1 and no problem with 4g lite. By the way, I'm not in the USA.