Related
I'm still on Lumia Amber update on Lumia 822 which is Verizon carrier-based.
However, I'm not in the US. I spend most of my time in UK and China, using different SIMs in the phone depending on where I am.
So how can I update to the latest Lumia versions (e.g. Black) or even the 8.1 update (if I can)?
If these updates are pushed out by their carriers, is it dependent on the carrier the phone was made for, or the phone network that I'm currently using?
What was so bad with being able to download offline update packs and install them manually?
OK, after painfully sitting through a series of updates for over an hour, I have the Lumia Black update. However, when I first heard about this update, it was mentioned that it would be rolled out through carriers and when they specify it will be released to their customers. So how does this work?
Because as I mentioned earlier, the Nokia Lumia 822's original (and somewhat "exclusive") carrier is Verizon. However, due to my travel with work, when I go to other countries, I'm using local SIMs and native phone networks (the secret benefit of a Lumia 822 being factory unlocked). How does this affect when I get selected for updates, and who is responsible for me getting the updates? Or is it just a load of old hogwash, having nothing to do with the carriers and networks whatsoever, and I receive updates just like every other Nokia/Windows Phone user when my phone's WiFi connects to the Nokia/Microsoft update servers?
Retail updates are always based on the carrier you (or whoever) bought the phone from; the carrier pushes out updates for "their" phones (regardless of current SIM) after doing their own testing and whatever. In the case of open-market (carrier-free) phones, it's based on the OEM; all carrier-free phones of a given model will receive an update at the same time, regardless of their current SIM card.
It is possible to instead get updates immediately and directly from Microsoft, using the "Preview for Developers" program (there's a free app on the store to join). That's how some people have 8.1 already
GoodDayToDie said:
Retail updates are always based on the carrier you (or whoever) bought the phone from; the carrier pushes out updates for "their" phones (regardless of current SIM) after doing their own testing and whatever. In the case of open-market (carrier-free) phones, it's based on the OEM; all carrier-free phones of a given model will receive an update at the same time, regardless of their current SIM card.
It is possible to instead get updates immediately and directly from Microsoft, using the "Preview for Developers" program (there's a free app on the store to join). That's how some people have 8.1 already
Click to expand...
Click to collapse
Thank you very much for the info. So what you're saying is, Verizon are still pushing out updates to my phone, even thought I've not used their SIM card in my phone for over 18 months? And this is simply because the Lumia 822 was specifically built for Verizon? Interesting. Especially since I use it as if it was one of the carrier-free Lumia 820's as I'm forever changing my SIM depending on where I am.
So how does Verizon pass on the information to my phone to tell it that it has updates pending for it, if I'm not using their SIM? Is my phone constantly polling Verizon update servers whenever have a WiFi connection?
The phone checks the Windows Update servers periodically (or you can force a check from Phone Update in Settings). Much like Windows Update for PCs, the phone reports various information about itself, including the operator its ROM is/was associated with (and whether you have dev preview updates enabled). Since your phone is running a Verizon image and isn't in the dev preview program, Windows Update will not report any updates for your phone until Verizon approves them. However, at the end of the day, all updates actually come from MS.
GoodDayToDie said:
The phone checks the Windows Update servers periodically (or you can force a check from Phone Update in Settings). Much like Windows Update for PCs, the phone reports various information about itself, including the operator its ROM is/was associated with (and whether you have dev preview updates enabled). Since your phone is running a Verizon image and isn't in the dev preview program, Windows Update will not report any updates for your phone until Verizon approves them. However, at the end of the day, all updates actually come from MS.
Click to expand...
Click to collapse
Brilliant! Thanks very much for that. I know it's a little off-topic but I'm a DreamSpark member (and student) until October this year so I would like to get registered as part of the developer programme for Windows Phone. Can you point me in the right direction and what I need to do?
If you mean the stuff about actually submitting apps to the Windows Phone Store, start here: https://dev.windowsphone.com/. It's got links to tools and account creation, tutorials, etc. I don't know for sure about the DreamSpark signup process though; I finished university before WP came out.
If you mean enabling dev preview updates for your phone (so you can get 8.1 immediately) you need the "Preview for Developers" app from the store (it's small and free, from Microsoft). You'll also need to have your phone developer-unlocked. This doesn't actually require signing up for anything (you just need a Microsoft account in general) though I recommend using the account associated with your DramSpark-based dev account as it should let you sideload more apps at once. To dev-unlock, you use the "Windows Phone Developer Registration" tool (it's included with the WP8[.1] SDK). Once your phone is dev-unlocked, run the Preview for Dev app and check the box; pretty simple. After that, go to Settings -> Phone Update and you should see a short series of updates to install (the phone will reboot many times; the whole process may take about half an hour if you have a fast Internet connection) and then you'll have WP8.1!
FYI, I am a new Android user.
Two weeks ago I got the Nexus 6 from T-Mobile. When I first got the phone there were no updates available for the phone. And I know at that time only version 5.0.1 was out, and it won't update that. And since then I haven't received an update for the phone. When version 5.1 was release I was excited to update. The phone tells me that my phone is up to date every time I check it throughout the day. My phone is still running version 5.0.
I did see that the update(5.1) was available when I erased my phone. I had no accounts signed in to the phone and I prevented anything to update except 5.1, but it went away and never downloaded.
I have forced stopped "Google Services Framework" multiple times and deleted the information, restarted the phone, and still no update.
I have called T-Mobile tech support to get help from them and they sent me a new phone, and still no luck.
What can I do to get the update? Is it possible that the SIM card I am using is from my iPhone 6 is preventing this?
I see that everyone is downloading updates and side loading them, but all the guides are pretty vague. I am on a Macbook so I don't understand the commands, but I do know how to use the terminal. I would like to stay away from side loading because my lack of experience.
Just be patient
The update comes out in waves, some get it later then others. You'll get it eventually
First, look here:
http://www.droid-life.com/2013/11/2...or-updates-on-nexus-devices-isnt-helping-you/
Also, try pulling out your Sim card and rebooting the phone. Let it sit without Sim and see if update returns.
I bought this phone over the Note 4 because of permanent root capability.
Now I'm finding that AT&T locked the bootloader and locked down rooting.
Is it even possible or do I now own a piece of junk?
I hate touchwiz, I wanna install a real rom...
changoland said:
I bought this phone over the Note 4 because of permanent root capability.
Now I'm finding that AT&T locked the bootloader and locked down rooting.
Is it even possible or do I now own a piece of junk?
I hate touchwiz, I wanna install a real rom...
Click to expand...
Click to collapse
If it's already on stock 5.0, then yes. Currently no root methods avaliable.
nutt_case said:
If it's already on stock 5.0, then yes. Currently no root methods avaliable.
Click to expand...
Click to collapse
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup. Word to the wise: Don't sign into Google on your first boot if you ever want to root this phone! I never had the opportunity, now I've gotta sell a brand new phone, ugh
changoland said:
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup. Word to the wise: Don't sign into Google on your first boot if you ever want to root this phone! I never had the opportunity, now I've gotta sell a brand new phone, ugh
Click to expand...
Click to collapse
Not to rub it in, but since other people may read your advice: It is not google or restoring the application that upgraded the phone to 5.0. You most likely got an OTA (over the air update) notice from AT&T which prompted you to update, then you did it, and updated your phone to lollipop.
najoor said:
Not to rub it in, but since other people may read your advice: It is not google or restoring the application that upgraded the phone to 5.0. You most likely got an OTA (over the air update) notice from AT&T which prompted you to update, then you did it, and updated your phone to lollipop.
Click to expand...
Click to collapse
Not to contradict you and come off like an asshole, but that is exactly how I got the 5.0 update. It was fresh out of the box and asked me if I wanted to restore content from my previous phone. I was never prompted for an OTA update and I never in a million years would have ever accepted or agreed to that. I'm just trying to warn anybody else who might end up in the same position I ended up in.
changoland said:
Not to contradict you and come off like an asshole, but that is exactly how I got the 5.0 update. It was fresh out of the box and asked me if I wanted to restore content from my previous phone. I was never prompted for an OTA update and I never in a million years would have ever accepted or agreed to that. I'm just trying to warn anybody else who might end up in the same position I ended up in.
Click to expand...
Click to collapse
I'm sorry, I am not questioning your judgment about this and as always I would like to be wrong about this because then I can I learn something new. The way I understand update mechanisms is that there are three ways things get updated in one's phone: the first is by Google and traditionally Google has only updated parts of the operating system that have to do with Google such as the Play Store or the Google framework etc. and these are considered minor patches to the OS. I have never heard or seen that Google would modify the /system partition as that would defy the entire notion of factory reset. The second is through Samsung. unless you live in certain countries where Samsung sells you a phone unlocked and unattached to a mobile operator the update you get from Samsung is limited to Samsung applications and security patches. Finally, in the United States and countries where phones are sold by cell phone operators the OS update is delegated to the phone companies such as AT&T and t-mobile. that's how you get an update for example from kit Kat to lollipop in the us. there is no documented mechanism that shows how Google can update the OS on a phone sold to you by a phone company. but if you find non anecdotal evidence to the contrary, I would be glad to stand corrected.
najoor said:
I'm sorry, I am not questioning your judgment about this and as always I would like to be wrong about this because then I can I learn something new. The way I understand update mechanisms is that there are three ways things get updated in one's phone: the first is by Google and traditionally Google has only updated parts of the operating system that have to do with Google such as the Play Store or the Google framework etc. and these are considered minor patches to the OS. I have never heard or seen that Google would modify the /system partition as that would defy the entire notion of factory reset. The second is through Samsung. unless you live in certain countries where Samsung sells you a phone unlocked and unattached to a mobile operator the update you get from Samsung is limited to Samsung applications and security patches. Finally, in the United States and countries where phones are sold by cell phone operators the OS update is delegated to the phone companies such as AT&T and t-mobile. that's how you get an update for example from kit Kat to lollipop in the us. there is no documented mechanism that shows how Google can update the OS on a phone sold to you by a phone company. but if you find non anecdotal evidence to the contrary, I would be glad to stand corrected.
Click to expand...
Click to collapse
I mean, I'm not stating that it was Google who pushed this update, it is an AT&T ROM after all. The reality of my situation is that the phone was doing an initial startup and the very first thing that happened was it launched into the initial setup. Once it got to the screen that asked me for my Google login to re-install all the apps that were linked to my account, that was the last time I had any input over the matter. It had to be during this time that the 5.0 update was downloaded/installed as well because this process took about an hour while it downloaded everything. Unfortunately it gives no information about whats going on whatsoever except for showing a splash screen that you can't escape from as it continued to download everything. Once it finished, I was at 5.0. I never once saw the phone operating or a home screen on anything that wasn't 5.0. So it very well could have been that AT&T pushed the OTA update during this process. I just had zero control over what was happening and was never prompted for an OTA update. I just entered my Google credentials, it went to the splash screen, and when it finished it spit me out to the home screen at 5.0.
changoland said:
I mean, I'm not stating that it was Google who pushed this update, it is an AT&T ROM after all. The reality of my situation is that the phone was doing an initial startup and the very first thing that happened was it launched into the initial setup. Once it got to the screen that asked me for my Google login to re-install all the apps that were linked to my account, that was the last time I had any input over the matter. It had to be during this time that the 5.0 update was downloaded/installed as well because this process took about an hour while it downloaded everything. Unfortunately it gives no information about whats going on whatsoever except for showing a splash screen that you can't escape from as it continued to download everything. Once it finished, I was at 5.0. I never once saw the phone operating or a home screen on anything that wasn't 5.0. So it very well could have been that AT&T pushed the OTA update during this process. I just had zero control over what was happening and was never prompted for an OTA update. I just entered my Google credentials, it went to the splash screen, and when it finished it spit me out to the home screen at 5.0.
Click to expand...
Click to collapse
My S5 looks for system updates on the initial setup each time. It probably upgraded to the new OS as your were doing your initial setup of the device.
That's correct it does look for updates on initial setup. I have made it a good practice not to connect to Internet during the initial setup. This will keep it from looking or installing any updates. Updates will not push unless your connected to Internet ( unless it's been days and you keep denying them ).
This is the procedure I follow each time I buy a new phone:
1- Take the sim card out and turn the phone on. If the phone co-operates go to step 3.
2- Put the sim card back in and turn the phone on.
3- During the initial setup decline to connect to WiFi if the phone accepts that.
4- Immediately after the set up is complete, go to Settings -> Security -> security policy updates (or something like that) and turn automatic updates off AND set your preferred networks to WiFi only.
5- go to Settings -> about device -> software update, AND IF THERE IS AN OPTION PRESENT, disable automatic updates.
6- Root the phone if possible. If not move to step 8.
7- After obtaining root, disable the update related apks. They are typically called: LocalFota.apk, FotaClient.apk, SamsungApps.apk, SPDClient.apk, SyncmlD.apk, and wssyncmlnps.apk, or variations of these names. They are all under either /system/app or /system/priv-app.
8- It is now (relatively) safe to connect to the internet.
9- The first time you log in to playstore, quickly go to its settings and disable automatic update.
najoor said:
This is the procedure I follow each time I buy a new phone:
1- Take the sim card out and turn the phone on. If the phone co-operates go to step 3.
2- Put the sim card back in and turn the phone on.
3- During the initial setup decline to connect to WiFi if the phone accepts that.
4- Immediately after the set up is complete, go to Settings -> Security -> security policy updates (or something like that) and turn automatic updates off AND set your preferred networks to WiFi only.
5- go to Settings -> about device -> software update, AND IF THERE IS AN OPTION PRESENT, disable automatic updates.
6- Root the phone if possible. If not move to step 8.
7- After obtaining root, disable the update related apks. They are typically called: LocalFota.apk, FotaClient.apk, SamsungApps.apk, SPDClient.apk, SyncmlD.apk, and wssyncmlnps.apk, or variations of these names. They are all under either /system/app or /system/priv-app.
8- It is now (relatively) safe to connect to the internet.
9- The first time you log in to playstore, quickly go to its settings and disable automatic update.
Click to expand...
Click to collapse
Those are good steps, one side note that i do is i don't connect to Internet until after i sign into Google play and set the update to " do not update ". I also hardly ever connect to the Internet anyhow since my phones data is faster than my slow a$$ Internet. Ha
dirtydodge said:
Those are good steps, one side note that i do is i don't connect to Internet until after i sign into Google play and set the update to " do not update ". I also hardly ever connect to the Internet anyhow since my phones data is faster than my slow a$$ Internet. Ha
Click to expand...
Click to collapse
Yeah, but somehow that never worked for me. Play store doesn't let me log in until I connect to the internet and before logging in I cannot change the settings.
najoor said:
Yeah, but somehow that never worked for me. Play store doesn't let me log in until I connect to the internet and before logging in I cannot change the settings.
Click to expand...
Click to collapse
If you open the play store and log in that way it normally won't, but if you go to settings, accounts, and add your Google account that way, let the phone set about 5 min while it sets up then you should be able to log in.
changoland said:
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup...
Click to expand...
Click to collapse
What makes you think it didn't come from at&t with 5.0 already installed? I had to have my phone replaced recently and the new one definitely had 5.0 pre-installed.
I just received one, 5.0 out of the box also.
Ok, so I'm not the only one who received a 5.0 out of the box. too bad AT&T are such pieces of s***
Yeah, I entered this thread with the intention of posting that it was to my understanding that unless you find some old stock somewhere, all new AT&T Galaxy S5s are coming with 5.0 pre-installed.
If the OP had taken an OTA while setting up his phone I'm sure he would have noticed the reboot to recovery and the little Android dude with the blue progress bar under him as his phone updated. OTA updates don't silently install.
The days of walking out of the store with a brand new S5 and rooting it right away have gone away until someone finds a new exploit that will work on the stock 5.0.
I'm looking for a used S5 to use on Straight Talk. I want to root it and use the mobile hotspot feature. Is their a particular build number or kernel I should be looking for? I want to have 5.0 also. Maybe a ROM like Sixperience
THANKS
Downgrade and root?
I had the same issue, replaced my broken S5 and the new one came with 5.0 stock.
Would it possible to downgrade, to 4.4.2 KitKat, root via Towelroot, and then upgrade again? Would be tedious, but I am sick of AT&T's bull****. It's a moral victory as much as just looking for more ease-of-use.
bigben7310 said:
I had the same issue, replaced my broken S5 and the new one came with 5.0 stock.
Would it possible to downgrade, to 4.4.2 KitKat, root via Towelroot, and then upgrade again? Would be tedious, but I am sick of AT&T's bull****. It's a moral victory as much as just looking for more ease-of-use.
Click to expand...
Click to collapse
Not possible as of now
Sent from my SAMSUNG-SM-G900A using Tapatalk
Hey folks,
I'm wondering with all the recent monthly builds that Google has been releasing, what build # my Verizon Nexus 6 should be on. Currently, it's on LMY48M but it's been acting really strange. Text messages won't always go through, sometimes half of my wallpaper disappears, and the phone's settings don't always work.
By phone settings, I mean I'll be in a setting page like accounts, trying to change the sync settings for my accounts and it won't let me choose a specific account to manage the sync settings. It's weird.
I'm not sure what's happening, or if it's just the build # that's wrong. I'm also rooted and unlocked, but using stock kernel and stock build.
My Nexus 6 is unlocked and rooted using WugFresh Toolkit, and I bought the device straight from Google about a year ago.
Thanks!
P.S. If anyone knows what I can do, Enhanced 4G LTE does not work on my phone at all. People cannot hear me, and calls are dropped all the time. I've had to turn that off. Any suggestions on how to get that working would be greatly appreciated too! I'm not sure if this is related to my radios or not.
Many thanks folks.
NexusReach said:
Hey folks,
I'm wondering with all the recent monthly builds that Google has been releasing, what build # my Verizon Nexus 6 should be on. Currently, it's on LMY48M but it's been acting really strange. Text messages won't always go through, sometimes half of my wallpaper disappears, and the phone's settings don't always work.
By phone settings, I mean I'll be in a setting page like accounts, trying to change the sync settings for my accounts and it won't let me choose a specific account to manage the sync settings. It's weird.
I'm not sure what's happening, or if it's just the build # that's wrong. I'm also rooted and unlocked, but using stock kernel and stock build.
My Nexus 6 is unlocked and rooted using WugFresh Toolkit, and I bought the device straight from Google about a year ago.
Thanks!
P.S. If anyone knows what I can do, Enhanced 4G LTE does not work on my phone at all. People cannot hear me, and calls are dropped all the time. I've had to turn that off. Any suggestions on how to get that working would be greatly appreciated too! I'm not sure if this is related to my radios or not.
Many thanks folks.
Click to expand...
Click to collapse
first off, what build you are on has absolutely nothing to do with your issues, nothing at all. your issues are caused by your use of the phone(most likely). by your use i mean what apps you install and use, what mods you make to your device, etc. and you need to turn on enhanced lte in your phone and in your verizon settings, its called Volte(voice over lte). personally, id factory reset and start all over again. oh, and do some research about your nexus 6. itll be beneficial to you. i know you didnt do research about your device(at least not enough) because of your use of the toolkit. you should never use a toolkit the first time you root a nexus because you will learn nothing. doing it the right way, takes 3-5 minutes once you learn, and you get to learn stuff about your device. afyer doing it right the first time, next time you can use toolkits.
simms22 said:
first off, what build you are on has absolutely nothing to do with your issues, nothing at all. your issues are caused by your use of the phone(most likely). by your use i mean what apps you install and use, what mods you make to your device, etc. and you need to turn on enhanced lte in your phone and in your verizon settings, its called Volte(voice over lte). personally, id factory reset and start all over again. oh, and do some research about your nexus 6. itll be beneficial to you. i know you didnt do research about your device(at least not enough) because of your use of the toolkit. you should never use a toolkit the first time you root a nexus because you will learn nothing. doing it the right way, takes 3-5 minutes once you learn, and you get to learn stuff about your device. afyer doing it right the first time, next time you can use toolkits.
Click to expand...
Click to collapse
Thanks for the advice. I've been a long time flasher with my Galaxy Nexus which I had for 3 years. Flashed a ton of different ROMs, radios, kernels, the whole shebang. I could learn more about my device, so I'll certainly take that into consideration. I asked about which build I should be on because I've read that the build # you need for your Nexus 6 depends entirely on your carrier. Some build #'s are designed for T-Mobile, some are designed for AT&T, and some are designed for Verizon or Project Fi. It get's really, really confusing trying to keep track of which build goes with which carrier, which is why I'm asking if I got it right or not.
I know how to turn on enhanced LTE, but when I do, nothing works. No one can hear me, calls are dropped, and it just doesn't work. When I turn it off, everything is fine. It's very possible it could be my one little area where I'm at (in Salt Lake City), but wanted to know if I was having issues because of flashing the wrong radio or something. I used the toolkit for that as well.
Perhaps all my issues come from using the toolkit, and I'll definitely take responsibility for that. I've never had issues using it though and I've been doing this for years without any problems.
So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.
robertkjr3d said:
So many people are reporting with the 3/1 sweep by AT&T, that they are blocking almost all Unlocked phones: See: Downdector Link We personally have a S10 (G973U1). AT&T is saying on this list: AT&T approved phone list that it is supposed to work. But like many other people "calls" end immediately, but we can text and data work. It is some sorta ploy by AT&T to force us to upgrade our phones. They want us all to upgrade to S22s. Anyway I was ranting. Anyway, if you look at that link, they are saying that the phone has to be on the latest software. The last update from AT&T or the manufacturer was in January. I checked the firmware site, and Android 11 is the latest in January. I'm wondering if there is some hack to get us on to '12' or something. An update might solve this issue. We know that a new SIM does not work. Calls seem to be rejected on the network, just based on the phone model or Android version.
We are aware that a version 12 is out there for the phone, just that firmware is not for our US-unlocked model yet. But maybe it can be hacked?
Edit: It appears this thread may be linked with this older one... But it is ever more pressing issue now:
S10 Unlocked phone with AT&T Firmware here they explain how, and the problems with flashing. This was back in 2019, so I'm not sure if this will still work. Even then it didn't work for everyone. Some in that forum claimed that it did. AT&T seems to now be blocking from their calling network any phones not enabled with VOLTE and the extended AT&T services that are not present in Unlocked phones.
Click to expand...
Click to collapse
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.
robertkjr3d said:
I was helped by a user to achieve ascendance onto the AT&T network. I'm not sure if I'm to reveal his name. We 1) go into Developers mode on the phone. 2) Hack the Kernel. 3) Flash the rom to the G973U (model)... with the AT&T firmware. So that the Wifi-Calling and 5G features would work, and AT&T would allow it on their network.
Click to expand...
Click to collapse
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!
Agreed, I didn't know such a thing was possible, but I'd love to hear more about this!
skrapmetal said:
I've literally been searching for an answer to this for days now. My wife and I have S10's. I work far from home so I really need her phone working in case of emergency. Can you please point me in the general direction? Thanks!
Click to expand...
Click to collapse
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.
KennyG123 said:
At first I had to use the Samsung Band Selector app from the Play store and go into More Network Settings > AT&T > Preferred Network Type and choose 3G. Unfortunately this killed LTE so all data and calls were going through H+. As I was mostly on wifi I could live with it since I could actually use the phone again.
Then Friday morning I checked for updates and there was the update to take me to Android 12. I took the update then when it finished it said it needed to reboot to connect new SIM to carrier services....it wasn't a new SIM. I let it reboot and everything was working with VoLTE again.
Hope this helps.
Click to expand...
Click to collapse
I appreciate you getting back to me. Unfortunately I am still on android 11 with a custom ROM and also this is a global phone so that app didnt work for me. I dont receive OTA updatez. I'll update to a new ROM and see what happens. Thanks