Xperia XA2 H3113 Android 9 (50.2.A.3.77)
Hi,
I recently got an Xperia XA2 and I can't use VOLTE.
My previous phone the Samsung j5 pro worked, but the XA2 keeps dropping down to H+.
I have contacted Vodafone in Brisbane Australia and they say it is an issue with the handset and it may need an update.
Any help would be appreciated.
I tried *#*#4636#*#* , but VOLTE provisioned is greyed out and off.
Same problem here for over a year. *#*#4636#*#* dimmed out. Also see wifi calling under that is also dimmed out. Sometimes I spend a few days or a couple weeks trying to solve this with AT&T and a little bit with Sony. But then I have to get back to work eventually without an answer. No one seems to have an answer. Did you ever resolve this?
Sony support has informed me they have XA2 customers with VoLTE working on AT&T, and here is more confirmation it should work from Freedom Mobile.
Freedom Mobile VoLTE enabled on Sony Xperia XA2, XA2 Ultra, XZ2
Freedom Mobile's fledgling VoLTE service now supports the Sony Xperia XA2, Xperia XA2 Ultra and Xperia XZ2.
mobilesyrup.com
Hey @MatthewIsLost.
I'm not sure if you still have your XA2 like I do. I'm busy and just kept using it. I'm being forced to do something finally because my carrier is shutting down 3G and they think I have a 3G phone because it keeps switching to 3G for voice calls for months or maybe a year and a half. When I first bought the phone the switches in the OS were there for VoLTE and WiFi-calling, but I didn't know what they were and was busy. When I would work on my H or H+ calls problem every few months with AT&T I learned I wanted those features. Never could get it. Sony was patiently helpful over the last couple years about this and advised they would not update the phone OTA with an update that would take away any features of the phone such as VoLTE and WiFi-calling. They also gave me the URL last week that shows the XA2 as a Sony phone with VoLTE at this link...
https://www.sony.com/electronics/support/articles/SX570801
When it opens, click the "Applicable Products..." as shown below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With this recent push from AT&T to get a 4G phone, I finally decided it's time to figure this out. I spent some hours with tech support at AT&T and finally one rep listened to my symptoms and ran tests for about 45 minutes and finally asked me if my phone said AT&T at the top. It did not. That led to me finally spend more hours figuring out how to flash my Sony. Hadn't flashed with fastboot and adb since my old MotoX. Dialing *#*#4636#*#* has also shown dimmed out buttons like yours. No one could tell me what that meant. By the way, I stopped by Verizon store and they were very helpful and put in a Verizon SIM they had lying around and my phone booted with it and my screen said Verizon at the top left as it was supposed to. That was done with the flash of LineageOS ROM on my phone.
A few days ago I used the installation instructions at LineageOS to put LineageOS 18.1 on my XA2, so right now I'm running Android 11 (LineageOS 18.1) and have been testing it for a few days. Getting a new SIM I hope soon, and also hope to get a cleaner flash of LineageOS before that SIM. I still have trouble with my signal strength icon and it still doesn't say AT&T in the top left of my screen, but it now says AT&T in the settings menu next to signal strength icon. I also now have the VoLTE switch in Settings/Network/Mobile Network where it should be, and WiFi-calling switch is in the Phone app settings under calls where it should be, and they are also showing as all turned on now in *#*#4636#*#* menu. So it is real progress on learning something. Not sure what yet. Since I flashed, it doesn't switch to H or H+ any more on calls, but whenever I make a call it switches from LTE to 4G, so I'm still not allowed VoLTE for some reason.
Malware? With LineageOS, I also installed Protectstar's Anti Spy and it identifies "Data Transfer Tool" as malware and that the program's source is unknown. I cannot delete it. Search reveals a regular Data Transfer Tool is a Google app. So could this be a fake version of the real Google app, or a false positive? No idea. Maybe if Data Transfer Tool really is malware or is fake version of the real app that adds reporting capabiliy, could it be such a good fake that Google won't let me delete that part of the OS. I also accidentally found 1 app had permission to use Unrestricted Data and it was Google Play services. I don't know if it is supposed to, but I turned it off. The thinking on my part is it would fit in with how my phone behaves. It's like there is never too much damage, it has mostly been like someone is in the way hampering me and getting all my data. Makes it difficult to grow a business over years.
Also after this new Lineage flash, I noticed at boot up, even though I always keep location turned off, the little tear drop icon indicating "location on" would show up at the top of my screen for 1-2 seconds as though reporting my location. As I drove around town and tried to keep tabs on my signal I would see the location being turned on and off again and again from time to time. Since I reported this over email and voice calls, it seems to have stopped. Since I don't know much, I still think there is malware. I learned some time back there is SIM malware. SIMs have microprocessors too. Check out this...
SIM cards Forensic Analysis with Oxygen Software | Digital Forensics | Computer Forensics | Blog
www.digitalforensics.com
I hope to have a cleaner flash of my XA2 today or tomorrow and a new SIM soon to get my phone to say AT&T at the top. We'll see.
If anyone knows where I can read about securely overwriting my phone storage without losing the ability to flash a new ROM, it would be great to hear from you. I thought I remembered using TWRP years ago with an option to format and it took a long time for a 32 GB phone as it should. But I wasn't able yet to confirm on the Net that TWRP overwrites all partitions. I see the "fastboot format" but something I read made me think it was only for the user data. I have lots to read.
Update July 31, 2021: My posts will continue about this problem at my URL wigglemylegs.com. I am continuing to look for technical answer for how AT&T can say my phone is 3G when they have seen my phone talking to them live on 4G, using LineageOS 18.1. If anyone knows how to straighten this mess out with AT&T it would be great to hear from you. They are trying to force my 4G LTE phone off their system by February 2022, by claiming it is only a 3G phone.
MatthewIsLost said:
Xperia XA2 H3113 Android 9 (50.2.A.3.77)
Hi,
I recently got an Xperia XA2 and I can't use VOLTE.
My previous phone the Samsung j5 pro worked, but the XA2 keeps dropping down to H+.
I have contacted Vodafone in Brisbane Australia and they say it is an issue with the handset and it may need an update.
Any help would be appreciated.
I tried *#*#4636#*#* , but VOLTE provisioned is greyed out and off.
Click to expand...
Click to collapse
AT&T (and I presume it's MVNOs) is not just instituting a VoLTE only policy, they are instituting a device whitelist. So even if your phone is VoLTE capable and can use this technology on say T-Mobile, if it isn't on the AT&T whitelist, it is banned from their network. So aside from the "we must redeploy bandwidth" reason, AT&T is using this change as an excuse to strike down BYOD and presumably boost handset sales...as well as the monetization of their customers by giving them handsets with preinstalled software that can more easily harvest their information.
Hey,
I just sumbled upon this threat because I'm trying to get VoLTE working on my mothers XA2 Ultra. Old_Mil is right with what he said but there is some Qualcomm tool to import the setting for a carrier to the modem. I did it for my old OP 3. But it's probably very risky to brick the modem.
If you really want I'll look for the link and some BG info.
Pretty interesting. I found this bit here below.
How to enable VoLTE on Qualcomm devices running Generic System Images (GSIs)
The VoLTE-Fix mod can be used to bring back support for Voice over LTE on most Project Treble-compliant Qualcomm devices running Generic System Images.
www.xda-developers.com
I guess that's what you're referring to above.
Chris8top8he8r said:
Pretty interesting. I found this bit here below.
How to enable VoLTE on Qualcomm devices running Generic System Images (GSIs)
The VoLTE-Fix mod can be used to bring back support for Voice over LTE on most Project Treble-compliant Qualcomm devices running Generic System Images.
www.xda-developers.com
I guess that's what you're referring to above.
Click to expand...
Click to collapse
Does it work for anybody?
I've been so busy I haven't looked into any of that fix for myself. Anyone else have anything?
I spent many hours over years trying to familiarize myself with the technology involved on my XA2 and learn how to fix my phone with AT&T's help. They didn't want to help. They tortured me for years by removing my VoLTE after the first 2 months, by reclassifying my XA2 as 3G so their towers won't accept me. You can read about it at my handyman URL of
wigglemylegs.com
where I posted many details. If you scroll to the bottom of long thread you see a dateline summary. AT&T HQ told me they could see my phone was erroneously classified as 3G in their tables and they could see that it was clearly a 4G LTE phone, but they didn't have the resources to fix it. When I opened a complaint with the FCC they wrote a reply denying this. Their legal out when faced with getting caught up in corruption is to offer a free phone. They offered me several models of free phones, but I didn't want it, because it is the principle of the thing that is wrong. I currently am on Lineage OS (Android 11) using voice apps that use data only like Whatsapp and so forth. Works great. Limited on calling regular numbers, so use others for that. The HD voice quality is just super!!
May the VoLTE be with you!!
Related
I posted this over on the Lumia 900 forum, thought I'd post it here as well since it works with most devices. I noticed wpcentral posted something about forcing the update with cabs. While this works, for you people who don't know how, or are nervous about doing that, here's a little trick.
This method doesn't break future updates (even though we probably won't get any). This will allow you to upgrade to 7.8 if you aren't able to in Zune. And this actually updates the phone via Zune, so it's fairly simple! I don't know why WPcentral chose to post the .cab's method.
This involves using the old "disconnect" trick.
Instructions here: http://www.stephenwagner.com/?p=660
First Update (to):
7.10.8779.8
Second Update (to):
7.10.8783.12
Third Update (to):
7.10.8858.136
Zhariak said:
I posted this over on the Lumia 900 forum, thought I'd post it here as well since it works with most devices. I noticed wpcentral posted something about forcing the update with cabs. While this works, for you people who don't know how, or are nervous about doing that, here's a little trick.
This method doesn't break future updates (even though we probably won't get any). This will allow you to upgrade to 7.8 if you aren't able to in Zune. And this actually updates the phone via Zune, so it's fairly simple! I don't know why WPcentral chose to post the .cab's method.
This involves using the old "disconnect" trick.
Instructions here: http://www.stephenwagner.com/?p=660
First Update (to):
7.10.8779.8
Second Update (to):
7.10.8783.12
Third Update (to):
7.10.8858.136
Click to expand...
Click to collapse
I don't think the update is available for ALL WP users yet. Most users (non-L900 users) locked to a US carrier (ATT/Verizon/T-Mobile/Sprint) are still pending release. I think if you have a phone locked to a carrier, then I'd suggest not spending more than 20 minutes doing this.
There is the cab sender or custom roms though for those of you who try this and fail.
xconomicron said:
I don't think the update is available for ALL WP users yet. Most users (non-L900 users) locked to a US carrier (ATT/Verizon/T-Mobile/Sprint) are still pending release. I think if you have a phone locked to a carrier, then I'd suggest not spending more than 20 minutes doing this.
There is the cab sender or custom roms though for those of you who try this and fail.
Click to expand...
Click to collapse
I've had people report over 8+ different devices worked!
From what I've heard this has worked with all, except for 1 specific device out of all WP7 generation devices...
Zhariak said:
I've had people report over 8+ different devices worked!
From what I've heard this has worked with all, except for 1 specific device out of all WP7 generation devices...
Click to expand...
Click to collapse
Well yes, I understand that this has worked for different devices -which is basically because MS pushed out the update to all nonbranded/unlocked devices, but I was talking about the US carrier locked devices...From what I gather, the update is not available yet for these phones (EXCEPT the ATT L900).
I have 2 Titans and a Trophy - 1 Titan has a custom rom on it -which is not relevant to this conversation. The other is carrier locked onto ATT and the Trophy is back to carrier lock to Verizon after flashing the OSPL back on it.
BOTH the US carrier locked phones - the ATT Titan and the Verizon Trophy do not have any available updates. -Which is simply because they are not on the carriers servers yet.
odd
Strange when I set the phone to flight mode it takes 30 odd seconds to check and tells me that it can't check for updates - almost as if it is using the phone's data connection to check. When I turn flight mode off it is a shorter check and tells me no updates are available ?
xconomicron said:
Well yes, I understand that this has worked for different devices -which is basically because MS pushed out the update to all nonbranded/unlocked devices, but I was talking about the US carrier locked devices...From what I gather, the update is not available yet for these phones (EXCEPT the ATT L900).
I have 2 Titans and a Trophy - 1 Titan has a custom rom on it -which is not relevant to this conversation. The other is carrier locked onto ATT and the Trophy is back to carrier lock to Verizon after flashing the OSPL back on it.
BOTH the US carrier locked phones - the ATT Titan and the Verizon Trophy do not have any available updates. -Which is simply because they are not on the carriers servers yet.
Click to expand...
Click to collapse
Maybe it's just AT&T devices... This has worked on tons of different Canadian carrier locked devices. And actually numerous people have reported that it's worked on carrier locked devices all over the world.
carlos_c said:
Strange when I set the phone to flight mode it takes 30 odd seconds to check and tells me that it can't check for updates - almost as if it is using the phone's data connection to check. When I turn flight mode off it is a shorter check and tells me no updates are available ?
Click to expand...
Click to collapse
There's different ways to do it. In my case I didn't use airplane mode, just turned off Wi-Fi and turned off cellular data.
Keep in mind, you need to do a check for updates (so it says there are no new updates), then change to a different tab. Disconnect the phone, reconnect the phone, wait a minute...
Then go back to the update tab, and wait two seconds, then disconnect the internet from your computer (I unplugged the network cable). This is when it prompted me.
Done numerous tests - Zune will not check for updates if the data services (wifi or = 3g) are not enabled on the phone.
carlos_c said:
Done numerous tests - Zune will not check for updates if the data services (wifi or = 3g) are not enabled on the phone.
Click to expand...
Click to collapse
Hmm,
That's odd. I've had 3 devices that can do updates with no 3g or wifi enabled. All my updates have been done with 3g and wifi disabled...
Zhariak said:
Hmm,
That's odd. I've had 3 devices that can do updates with no 3g or wifi enabled. All my updates have been done with 3g and wifi disabled...
Click to expand...
Click to collapse
Well, for my HTC Arrive(sprint), this method has never ever succeeded, ever. And I tried a lot times, I mean a lot. But thanks to remind me, and I went for the cab push route, which works fine.
this disconnect method worked for me too in Ireland
But had to do the same thrice for all the three updates.
Zhariak said:
Maybe it's just AT&T devices... This has worked on tons of different Canadian carrier locked devices. And actually numerous people have reported that it's worked on carrier locked devices all over the world.
Click to expand...
Click to collapse
Nope, all US carrier locked devices still pending release.
xconomicron said:
Nope, all US carrier locked devices still pending release.
Click to expand...
Click to collapse
Weird,
I've have over 4-5 people chime in and say this has worked on AT&T and also T-Mobile.
What has 80072FA8 error or just no update found!
On this time I tried a long time update with disconnect trick. But... no updates.
NOW... from FIRST time update was found!
Solution:
yeah... first of all good things happen to UK. So we will use UK proxy.
Go to Settings - mobile network , then edit apn. In "APN, Username, Password" I typed my provider settings. In "Proxy server/URL" type 109.169.40.229 and in "Proxy port" type 8080. Here Done.
Next step: in computer STILL connected internet, in phone wifi is disconnected.
And last step: in Zune click update. Waiting about ~2 minutes, because proxy is very slow.
Result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for UK proxy :laugh:
There's no such a setting on my phone at all.
That didn't work for me minep. However, that could be for a number of reasons.
I have an AT&T interloped unlocked phone. Tried this with my target set as Rodgers and AT&T.
Taking reference from link mentioned in first post, and full credit to original post online, here is my blog in which I have mentioned steps to upgrade Windows Phone to WP7.8. I have mentioned steps to update using Internet disconnect method.
http://svknet.wordpress.com/2013/01/31/steps-for-windows-phone-7-8-update-on-samsung-omnia-w/
It worked for me very well in India. Only Patience is needed to keep trying several times.
Hi everyone,
I've got 3 weeks left before heading overseas for volunteer service. I'll be Lesotho, Africa for 27 months and surprisingly, they have cellular/edge/wimax/3G services there.
Has anyone unlocked our phone for GSM use before? I just want to get the facts straight before calling them up. I have my Dinc2 which is rooted and running CM7- will I need to flash stock to get the unlock prompt after they give me the code? Or will the prompt still display on a custom ROM?
I have a 2nd Dinc2 I just picked up on ebay. It is still "locked" as well but all stockified. I've read big red only allows 1 unlock per year.. but I bet with enough persistence I can get it done.
Thanks in advance
-rev
revile said:
Hi everyone,
I've got 3 weeks left before heading overseas for volunteer service. I'll be Lesotho, Africa for 27 months and surprisingly, they have cellular/edge/wimax/3G services there.
Has anyone unlocked our phone for GSM use before? I just want to get the facts straight before calling them up. I have my Dinc2 which is rooted and running CM7- will I need to flash stock to get the unlock prompt after they give me the code? Or will the prompt still display on a custom ROM?
I have a 2nd Dinc2 I just picked up on ebay. It is still "locked" as well but all stockified. I've read big red only allows 1 unlock per year.. but I bet with enough persistence I can get it done.
Thanks in advance
-rev
Click to expand...
Click to collapse
The phone itself is unlocked. If you plan to use Verizon service, I don't think you have to do anything. If you want to use local service provider there, you have to "Sim unlock" Dinc2 by calling Verizon and request MEP code. This can only be done in stock rom as far as I know. After unlocking Dinc2 to use different carrier sim, you can reflash with a custom ROM. So far I have tested and it works with CM7 rom in the States but at the moment MROM is not working with me when I'm back to Vietnam so I have to investigate further. But that is the general process.
startrek1312 said:
The phone itself is unlocked. If you plan to use Verizon service, I don't think you have to do anything. If you want to use local service provider there, you have to "Sim unlock" Dinc2 by calling Verizon and request MEP code. This can only be done in stock rom as far as I know. After unlocking Dinc2 to use different carrier sim, you can reflash with a custom ROM. So far I have tested and it works with CM7 rom in the States but at the moment MROM is not working with me when I'm back to Vietnam so I have to investigate further. But that is the general process.
Click to expand...
Click to collapse
This is exactly the advice I was looking for. Thank you very much startrek. I planned on using MROM but I'll be sure to have a copy of Official CM7 in the event it doesn't work.
Also, I'll note that VZW gave me the 2 unlocks codes for both my vivows, even though one of them was purchased on ebay. The customer service was surprisingly helpful.
revile said:
This is exactly the advice I was looking for. Thank you very much startrek. I planned on using MROM but I'll be sure to have a copy of Official CM7 in the event it doesn't work.
Also, I'll note that VZW gave me the 2 unlocks codes for both my vivows, even though one of them was purchased on ebay. The customer service was surprisingly helpful.
Click to expand...
Click to collapse
After spending a whole day testing and trying out, I finally figured out what was going on with MROM. Apparently the latest version of it (20130401) is not able to keep the phone sim unlocked after the first reboot when you are done flashing. I tried to downgrade from 2013-04-01 to 2013-02-15 without wiping data but the problem still existed. However, if you do a fresh reflash (wiping data, cache and all that jazz) of the 2013-02-15 version, the phone will work with GSM and it will NOT lock the sim back again as it happened to me with 2013-04-01 version.
The link is here if you still need it. http://goo.im/devs/mmontuori/mrom/vivow
However, I am still unable to get the data working. I've been trying but it hasn't worked. Probably have to take it to Customer Service Rep to figure it out. Other than that, voice and texts are fine.
And yes, Verizon rep are very comfortable with giving you the MEP code for some reason. They probably have had a lot of people requesting the same thing.
startrek1312 said:
After spending a whole day testing and trying out, I finally figured out ... the phone will work with GSM and it will NOT lock the sim back again as it happened to me with 2013-04-01 version ... I am still unable to get the data working. I've been trying but it hasn't worked.
Click to expand...
Click to collapse
A # of newcomers and semi-related questions about Sim-unlocking the GSM radio so that it can work with Sim cards other than VZW/vodafone Sim pre-installed in the DI2 - let me share my limited expertise in this area.
You do NOT need to flash the RUU before calling for the unlocked code from VZW - if you want to be as close to stock as possible, download AndyBone's ROM as his link is apparently down - I posted Dropbox link to mine, in case anyone is looking for it - http://forum.xda-developers.com/showthread.php?t=1219471&page=184 (see post #1831) Or, just use Nit's TSM Sense 5"m" with or w/o Ext.4 option - based on Sense 2.1 - that's what I use when I travel abroad.
To verify, (borrow one if you do not have it) a working AT&T Gophone (prepaid) Sim from someone (or, a T-Mobile prepaid Sim, although it's a bit more work to modify the APN to get data & the account has to be provisioned for it) - put the Sim into the DI2, power up & change network to GSM only - and you should be good with voice & SMS. Make a test call to confirm that you can dial out and receive incoming call on that mobile # - you do NOT want to find out that it's not working traveling inside Mexico, Japan or somewhere in Europe or what not.
For mobile data on your GSM provider to work - you need to confirm that APN settings are valid & working - and that it is saved to the device. Those are your APN Name, Proxy, Port, Username, Password, MMSC, etc. - some are blank, others are carrier-specific, etc. AT&T has theirs, ditto for T-Mo and other GSM providers. If they are not set or incorrect, mobile data might but most likely not work - generic settings for Android phones should be sufficient, but not always. If yours aren't working, confirm that the Sim card is valid & working on an unlocked quadband phone and try again. It is sometimes possible for the carrier to do OTA download to update the device so that SMS/MMS & mobile data can work by loading the APN's to the device, otherwise - it has to be done manually by going to the sub/menus.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Letitride said:
A # of newcomers and semi-related questions about Sim-unlocking the GSM radio so that it can work with Sim cards other than VZW/vodafone Sim pre-installed in the DI2 - let me share my limited expertise in this area.
You do NOT need to flash the RUU before calling for the unlocked code from VZW - if you want to be as close to stock as possible, download AndyBone's ROM as his link is apparently down - I posted Dropbox link to mine, in case anyone is looking for it - http://forum.xda-developers.com/showthread.php?t=1219471&page=184 (see post #1831) Or, just use Nit's TSM Sense 5"m" with or w/o Ext.4 option - based on Sense 2.1 - that's what I use when I travel abroad.
To verify, (borrow one if you do not have it) a working AT&T Gophone (prepaid) Sim from someone (or, a T-Mobile prepaid Sim, although it's a bit more work to modify the APN to get data & the account has to be provisioned for it) - put the Sim into the DI2, power up & change network to GSM only - and you should be good with voice & SMS. Make a test call to confirm that you can dial out and receive incoming call on that mobile # - you do NOT want to find out that it's not working traveling inside Mexico, Japan or somewhere in Europe or what not.
For mobile data on your GSM provider to work - you need to confirm that APN settings are valid & working - and that it is saved to the device. Those are your APN Name, Proxy, Port, Username, Password, MMSC, etc. - some are blank, others are carrier-specific, etc. AT&T has theirs, ditto for T-Mo and other GSM providers. If they are not set or incorrect, mobile data might but most likely not work - generic settings for Android phones should be sufficient, but not always. If yours aren't working, confirm that the Sim card is valid & working on an unlocked quadband phone and try again. It is sometimes possible for the carrier to do OTA download to update the device so that SMS/MMS & mobile data can work by loading the APN's to the device, otherwise - it has to be done manually by going to the sub/menus.
Click to expand...
Click to collapse
Thank you for such an informative post. Apparently I've been setting up my APN wrong. I have to set my APN Type to be "default, supl" After I did that, it's up and running! I blame Vietnamese carrier for NOT being helpful whatsoever! But thanks so much!
startrek1312 said:
Apparently I've been setting up my APN wrong. I have to set my APN Type to be "default, supl" After I did that, it's up and running! I blame Vietnamese carrier for NOT being helpful whatsoever! But thanks so much!
Click to expand...
Click to collapse
Happy to hear that you got it working - by any slim chance, it's MobiFone in HCMC, last used one of their prepaid Sim 3 years ago, voice was easy and just work. Our bilingual English tour guide tried all day as we got it while stopping for Pho near one of the older market in District 1, and no luck at all. Back at our hotel, we tried using the online website for self-help and it wasn't useful either, details within the English website were mostly in Vietnamese, except for the pictures - and, looked like nothing much has changed. This is off-topic, another recommendation for a local mobile provider should we plan another visit in the future?
Take care & have fun - and are you now getting 3G speed or at least showing that on the screen?
Letitride said:
Back at our hotel, we tried using the online website for self-help and it wasn't useful either, details within the English website were mostly in Vietnamese, except for the pictures - and, looked like nothing much has changed. This is off-topic, another recommendation for a local mobile provider should we plan another visit in the future?
Take care & have fun - and are you now getting 3G speed or at least showing that on the screen?
Click to expand...
Click to collapse
I'm glad you are thinking about returning to Vietnam. Most people don't after their first visit lol. I personally use MobiFone in Vietnam and I don't plan to change that. Their voice quality is really good and Customer Service number is toll-free unlike another popular carrier Viettel (or at least it was when I left Vietnam). I really enjoy using them and would recommend you to use them as well.
Are you talking about trouble getting SMS work or just data? My friend uses Galaxy Note 2 and everything automatically got set up and ready to go (APN and SMS centre) after she just popped the SIM in her phone so I blame the Dinc2 for being so troublesome. I can post their APN setting down here if you want to. I had to do a little bit of Googling but it shows up in the first 5 results.
And yes I am able to get 3G speed. MobiFone uses Hspda+ in Vietnam.
Sent from my Incredible 2 using xda app-developers app
I need a second opinion about the radio on my Galaxy Nexus. Help!
Context
I recently switched from the GNex to a Nexus 4. I wanted to give my old GNex to my sister, but the glass was slightly cracked from a fall a couple months ago. So before giving it away, I decided to purchase a glass/digitizer from eBay and replace it myself - the part was something like this. The process involved taking apart the frame from the digitizer/glass - which some of you know are fused together. Everything went well (or I thought so).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The new screen works, and I gave the phone to my sister. She popped in her SIM card (we're both customers of Fido in Canada). But she's now having problems getting the GNex unto Fido - actually, she can't see any network signal at all.
Screenshots / Symptoms
1. Lockscreen says "no service"
2. In Mobile Networks > Network operators, I can see the phone searching for available networks, but after 20-30 seconds, it just returns a blank list (no network displayed)
3. The baseband is correctly displayed in the About menu (i9250XXLJ1).
4. Under Status, the network is shown as "Unknown", mobile network type: "UNKNOWN:0", service state: "Out of service", and Mobile network state: "Disconnected"
5. The IMEI or phone number seem OK.
6. I went into the Phone info menu (*#*#4636#*#*). [ image 1 ] [ image 2 ]. Current network is blank. The signal strength feels weird (can anyone confirm if that number makes sense?).
7. Not sure if that's related, but I installed GPS Test and unable to get a GPS lock. It could simply be that I have no mobile signal in the first place, but Wi-Fi works fine, so shouldn't I be able to get a GPS signal anyway?
Here's what I tried so far to fix it:
1. Reboot / Battery pull: I did the usual reboot, battery pull, as well as toggling Airplane mode on and off - no dice.
2. Sim card: At first I thought maybe we needed a new SIM card, but it works fine when I insert it in a different phone (Nexus S). I also haven't seen any error message pertaining to the SIM - just "No service". We also tried another friend's SIM card and still seeing "No Service". So I don't think the SIM card is faulty.
3. Checking with carrier: I called our network carrier (Fido) and they're not seeing anything unusual on their end. Account in good standing, and as I said before, I can use the SIM card in an older Nexus S. I also made sure that the IMEI number wasn't blacklisted, which it doesn't appear to be. At this point, I'm confident the problem lies in the device and has nothing to do with network or coverage.
4. Cerberus anti-theft app: This one I'm unsure about. Before all this happened, Cerberus was installed on my GNex. I set it up so that unauthorized SIM cards would be reported to my email. When we swapped SIM cards, I got the expected warnings from Cerberus, which I ignored since I was the one who did the switch. But after experiencing the problems with the network, I went back to my inbox and noticed some emails displayed the Network operator as 302720 (Fido), and then some would show 0000 () - see the screenshot, the emails are just a few minutes apart but show different network data. I find that odd. Is there any chance that Cerberus may have messed with a setting and blocked the SIM card from the device? However, I did wipe the device and flashed back to stock. I also re-installed Cerberus and made sure my sister's SIM card is registered as authorized. We're still seeing "No service".
5. Factory reset / Flashing to stock The phone was previously rooted and used to run Paranoid Android v3.65 before I replaced the screen. I never had signal issues on that ROM. To make sure it wasn't the ROM or Cerberus causing the problem, I did a factory reset. That didn't fix it. So I flashed the phone back using Google's factory image (takju 4.2.2 build JDQ39) - completely back to stock, including bootloader, baseband radio-maguro-i9250xxlj1.img and a full wipe. Even on stock, I get the same results as shown in the screenshots (no signal, no mobile network).
6. Radio settings (*#*#4636#*#*): The last thing I tried to do is modify some of the radio settings: turning radio on and off, rebooting. And trying a different preferred network type (GSM Auto vs. WCDMA, etc). None of these worked. It keeps defaulting to WCDMA after a reboot, but I don't think that would prevent me from getting a signal (on the Nexus 4, that's exactly what I'm seeing, and it works on Fido).
I don't know what else to do. At this point, I think it's gotta be a hardware problem. Perhaps something went wrong when I manipulated the frame (the speaker/radio module at the bottom)? I also think that it's the modem (and NOT the SIM card holder) that I need to look into. My last resort is to purchase a new antenna off eBay and attempt to replace it in a couple days. I'm desperate and really hoping that can solve it.
In the meantime if anyone has a second opinion or suggestions, I'd be so grateful!!!
Is there anything else I can try or may have forgotten about?
Thanks!
I'm in the exact same boat! Apart from occasionally the lockscreen shows my network. I've flashed more things than a camera.
Have you got a generic IMEI? When I unlocked my phone it changed my IMEI to the generic one and I'm wondering if this may be the cause of my problems, check yours out.
EDIT: sorry reread it, yea your IMEI is fine, so my problem must have nothing to do with that either.
At least yours is occasionally picking up a network. Are you on stock, and did you try to use the SIM card on a different device?
Mine keeps saying "No service". I don't even have "Emergency calls only". Some people will see their network, then get "Can't connect right now. Please try again later". But mine is not even detecting any network. It's as if the antenna was off, even though the settings say it's on.
I'm hoping someone with a good knowledge of components/hardware can shine a light.
Mine varies between showing my network and no service. I'd just go for it and replace the antenna, its pretty easy to do. Let us know the results!
I've ordered one, so I'll let you know, should be tomorrow.
kylepsp said:
I've ordered one, so I'll let you know, should be tomorrow.
Click to expand...
Click to collapse
Great, I hope that fixes it for you. Mine should arrive within 2-3 days.
Please keep us informed. I have a similar problem with a Verizon galaxy nexus... I have tried all the fixes and flashes that you have stated with the same results. Very interested to find out if this works.
Sent from my large and in charge GN2 using Forum Runner
Replaced it, no difference I'm afraid.
EDIT: I also fixed my IMEI number, so my problem is not related to either of these solutions
kylepsp said:
Replaced it, no difference I'm afraid.
EDIT: I also fixed my IMEI number, so my problem is not related to either of these solutions
Click to expand...
Click to collapse
Well that's a bummer. If it wasn't software, I was hoping a hardware replacement would fix it for you. I'm really struggling to identify the problem at this point.
I'll replace my radio in a couple days and let you know if it did anything for me.
JLishere said:
Well that's a bummer. If it wasn't software, I was hoping a hardware replacement would fix it for you. I'm really struggling to identify the problem at this point.
I'll replace my radio in a couple days and let you know if it did anything for me.
Click to expand...
Click to collapse
Thanks good luck! I had managed to get a little signal in some places using a UgKL1 radio, try that one, got the best results
UrbanDroid said:
Please keep us informed. I have a similar problem with a Verizon galaxy nexus... I have tried all the fixes and flashes that you have stated with the same results. Very interested to find out if this works.
Click to expand...
Click to collapse
Sadly, replacing the radio module didn't fix the problem for me either. Still seeing "No service". I can't think of any other way to get a mobile signal. If anyone has any ideas, feel free!
At this point, my GNex is reduced to a WiFi-only device.
My last attempt is to flash the stock image for 4.3 released today by Google. I noticed the baseband is still XXLJ1. If that doesn't work, I'll try flashing an older radio.
I have the same problem. No signal, no IEMI..WIFI-only. I don't why..
someone said that maybe the EFS partition was corrupted. And then maybe a professional tool can fix it..SPT box..
JLishere said:
Sadly, replacing the radio module didn't fix the problem for me either. Still seeing "No service". I can't think of any other way to get a mobile signal. If anyone has any ideas, feel free!
At this point, my GNex is reduced to a WiFi-only device.
My last attempt is to flash the stock image for 4.3 released today by Google. I noticed the baseband is still XXLJ1. If that doesn't work, I'll try flashing an older radio.
Click to expand...
Click to collapse
The crazy signal strength values are due to an int32 buffer overflow when trying to calculate signal strength, and is typically due to the radio driver not loading correctly OR bad radio...
If you enable USB debugging and "adb logcat -b radio" do you notice anything interesting?
To whomever said they have signal in some places: sounds like someone inserted an external antenna into a port under the back cover, as a lot of us probably know, that permanently disables the internal antenna, leaving you without signal unless you're virtually next to a tower.
Sent from my Galaxy Nexus using xda app-developers app
CyberKitsune said:
The crazy signal strength values are due to an int32 buffer overflow when trying to calculate signal strength, and is typically due to the radio driver not loading correctly OR bad radio...
If you enable USB debugging and "adb logcat -b radio" do you notice anything interesting?
Click to expand...
Click to collapse
Hi, thanks for the suggestion. I did the logcat -b radio command but I'm not familiar with the results - can someone help me read through it? I get these lines:
Btw, I'm currently running stock 4.3, JWR66V build, I9250XXLJ1 baseband.
Hello all,
I was warned of an impending "update" a few nights ago. Since it hit, my mobile hotspot no longer works.
Does anyone else have an S7 Active on Red Pocket who has a working hotspot? If so, could you share the APN settings you are using, and the Android version you are on?
I think they rolled me back to January 2018. G891AUCU2BRB5
Would rather not factory reset or root, but getting very close to doing so. Neither RP or AT&T are helpful here.
Thank you,
Bob
Red Pocket Mobile Hotspot problem solved - stock Oreo 8.0 fixed it
Well, for anyone who might encounter this, I finally resolved it.
Pulled the SIM card and did a factory reset. Then it recognized the Oreo update over Wifi. Had to load an intermediate update first.
I put it Red Pocket's AP settings.
First time I tried Mobile Hotspot, it still didn't work.
Restarted the phone.
Still didn't work.
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
After ten hours of wading through poor advice, I'm back to where I was four days ago.
With one exception: I learned how to turn on Developer Mode (tap Build Number 7 times in Software Info)
AND SHUT OFF THE AUTOMATIC UPDATES UNDER DEVELOPER MODE SO IT WON'T HAPPEN AGAIN!!!
I have a stock S7 Active/G891A that I bought unlocked on eBay in March of 2018. It's currently running Oreo 8.0.0, build G891AUCS4CSA3. I just now disabled OTA updates thanks to you.
I've been trying to get Mobile Hotspot to work on this phone ever since I switched Consumer Cellular several months ago. Whenever I tried to enable hotspotting the phone screen would display a popup:
Please wait while verifying
Which was a normal message on the AT&T network, but now (using AT&T's network through Consumer Cellular), after 5-10 seconds a different window would appear:
Tethering/Mobile AP is unavailable.
A network issue may be preventing use of your Mobile Hotspot. Please call Customer Care at 611.
[excessive hard-coded line breaks omitted]
Over the course of several weeks in January I literally spent hours on the phone with several Consumer Cellular 1st and 2nd tier support techs trying to get past that error. Tier 2 support gave me new APN settings, had me do a network reset, and suggested that I do a factory reset. Which I did later, but that didn't work, either. Then CC tier 2 support gave up and bumped my ticket to tier 3. Tier 3 support then transmitted their version of an APN definition to my phone, but still no love. At the end of the 2nd week of phone tag, a Tier 2 tech told me that "it <Mobile Hotspot> just doesn't work with some phones not sold by us".
Maybe hotspotting won't work with my old Motorola Razor, but I was pretty sure that I'd eventually strike gold with my trusty G891A.
Because my S7 Active has version 4 of the boot loader (thank you, latest and final OTA), I haven't been able to find anything that resembles a working root. I even paid OneClickRoot to do it via remote desktop session, hoping that they had some good mojo that I hadn't yet discovered. But their support tech hit a wall, too, and ended up flashing my phone back to stock Oreo 8.0.0. They also refunded my purchase almost immediately which made me sort of happy but still sad that I had no Hotspot abilities.
While searching for possible workarounds (ROMS, root, mystical incantations) tonight I came across your posts:
bobcpdx said:
[snip]
Then I remembered one rep saying to switch MVNO type to "IMSI".
[snip]
Click to expand...
Click to collapse
So I followed your tip. I created a new APN definition and copied in all of the values from the CC Tier 3 definition . I then set Mobile virtual network operator type to imsi . This value was set to None in all in all of the other APN definitions on my phone.
I didn't even need to reboot the phone. I selected my new APN definition and enabled Mobile Hotspot. The first message about verifying came up. But then the phone didn't direct me to dial 611. Mobile Hotspot simply started working.
Thanks every so much for sharing this insight.
bobcpdx said:
Well, for anyone who might encounter this, I finally resolved it.
…..
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
….
Click to expand...
Click to collapse
WOW! Thanks so much for posting this. I've been struggling for a couple of months to find a way to hotspot my two unlocked LG's (G6 and a G7) on Cricket and Consumer Cellular. This trick enabled hotspot/tether quickly and easily.
My apologies to Cricket and CC, for my unflattering thoughts about them. I assumed it was their issue! Not sure why these unlocked LG's are fidgety like this. We got a Moto X4 (Android One flavor) in the family, and it can hotspot with no tweaking.
BTW - I have a similar issue with call forwarding on the LG's. Can't enable it, get an error. But the Moto X4 has no problem on either of these AT&T MVNO's. Anyone have an easy answer for that? Thanks.
This doesn't answer the call forwarding question. I'm not sure who pushes OTA updates, but soon after my last post I got a notification that an my phone needed to be rebooted for an update to finish. This was after I (at least thought that I had) disabled automatic updates. After the update the hotspot feature no longer worked. I checked APN settings and found that the update had reset the APN MVNO type to NONE . I manually changed it back to imsi and it's been working ever since. I also made sure (twice with reboot in between) that automatic OTA Updates are disabled.
Although enabling/disabling these features seems to be problematic with AT&T MVNOs, what I find more curious is that techs at Consumer Cellular claim not to know how to fix them. Maybe that's true, or maybe that's what they are told to say.
Was it coincidence that I received an OTA update within days of making this change, or is the Big Brother with the Blue Death Star logo watching us so closely?
Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.
Unless I'm misreading the list, this is a whitelisted device on the AT&T network.
Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?
They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.
I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.
(deleted, mistook carrier)
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.
From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.
FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.
Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.
I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.
The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE