Develop Bugs

[Q] Gnex (gsm) has lost its ability to connect to cell network

Hi everyone.
My wife's gnex has suddenly started prompting me with a no signal icon out of the blue. I up to that point it has been working fine for more the better 4 months. No changes have been made, and nothing installed outside the normal apps.
A no signal icon is displayed. When searching for a network a toast tells me that there is an eerror. And when I go into the power menu it shows that airplane mode is enabled, and a second later, without any interaction, it changes to airplane mode being off. In the settings, airplane mode is off. Wifi works fine.
I have tried to check if it's the simple card - the card from her device works fine In my gnex, and my sim doesn't s work in hers.
I've tried to do a data wipe - nothing has changed.
I don't have access to a computer for the next few days so I can't try to install another rom or a baseband.
Wify is currently completely phoneless, please help

Send the phone in for warranty if it's stock with locked bootloader
Beamed from my Grouper.

Not an option, since i'm outside the US, and the phone was bought there :\
Also, i've tried to flash radio-maguro-i9250xxlf1, it didn't help. For some reason trying to flash stock gets stuck on the system restore, for more then 20 mins

The plot thickens..
{
"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"
}

Have she dropped it? I also had this problem because I dropped it. Apparently something broke or came loose that made my phone not recognise the SIM card. Had to pay 150 to fix it... I also heard that it could simply be SIM slot problem, so I advise you to check your SIM card slot, see if anything looks broken
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

Nope, it wasn't dropped, and i've inspected the sim slot for hours without finding anything suspicious.

psychuil said:
Hi everyone.
My wife's gnex has suddenly started prompting me with a no signal icon out of the blue. I up to that point it has been working fine for more the better 4 months. No changes have been made, and nothing installed outside the normal apps.
A no signal icon is displayed. When searching for a network a toast tells me that there is an eerror. And when I go into the power menu it shows that airplane mode is enabled, and a second later, without any interaction, it changes to airplane mode being off. In the settings, airplane mode is off. Wifi works fine.
I have tried to check if it's the simple card - the card from her device works fine In my gnex, and my sim doesn't s work in hers.
I've tried to do a data wipe - nothing has changed.
I don't have access to a computer for the next few days so I can't try to install another rom or a baseband.
Wify is currently completely phoneless, please help
Click to expand...
Click to collapse
Same thing happened my wifes Gnex, It was 10 days old. It sounds like was the same issue -- error when I tried to search and unknown IMEI.
I ended up getting a new one from sammy..

Sending it to sammy and getting it back would cost me more then $100, so i'd rather avoid that if there's a possible solution.

ZV9 still didn't fix software issues.

{
"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"
}
Stock Sprint Optimus G. Updated to latest ZV9 firmware. Performance tweeks and new kernals are great and all, but the core functionality of the phone is still broken. The exchange email is inexcusable. A smartphone is designed as a personal assistant and organizer first before media or anything else.
The Bluetooth issue is embarrassing. I am using LG Tone+ 730's which shouldn't have any issue from the same manufacturer. My Jeep uses a base Uconnect 130s/RES system that is in numerous Chrysler vehicles and doesn't have the same issues with other devices like the Galaxy S3 or EVO LTE that I have previously used.
I know the dev community can't wave their hands and make it work, especially on a not rooted phone. But anyone have a clue how to push this up to LG outside of their awful support site?

Bump, recently moved thread.

What Bluetooth issue do you have and I don't use exchange so I wouldn't know anything about that issue

You bump your own 2 week old thread for issues that people apparently don't have. I know I sure don't. Of course I don't use Exchange and my bluetooth works fine
Sent from my LG-LS970 using xda premium

ZV9 fixed my Exchange issue, although it was not a connectivity issue. Are you sure your credentials are correct? SSL vs non-SSL? Tried on mobile network instead of wifi?

I use the same LG Tone and have 0 issues. And know customers that use exchange and have no issues. Are you sure its not the credentials?
Sent from my LG-LS970 using xda premium

RE: Bluetooth, I believe the OP is referring to the fact that this phone will randomly disconnect from a connected bluetooth device. I have two devices I regularly connect to, my car and my home phone system. The phone connects and remains connected to my car. However, it WILL disconnect from the home phone either randomly, or as soon as I try using the home phone to make or receive a linked call. The second image in the OP's post shows the message that comes up on the phone. It can't entirely be the fault of the connected home phone system because I used to connect my Optimus S to the system perfectly every time and never ever dropped a connection. The OG drops the connection to the home system without fail every single time. If I recall, it sometimes worked on ZV7 but never on 8 or 9.

my.ads0 said:
RE: Bluetooth, I believe the OP is referring to the fact that this phone will randomly disconnect from a connected bluetooth device. I have two devices I regularly connect to, my car and my home phone system. The phone connects and remains connected to my car. However, it WILL disconnect from the home phone either randomly, or as soon as I try using the home phone to make or receive a linked call. The second image in the OP's post shows the message that comes up on the phone. It can't entirely be the fault of the connected home phone system because I used to connect my Optimus S to the system perfectly every time and never ever dropped a connection. The OG drops the connection to the home system without fail every single time. If I recall, it sometimes worked on ZV7 but never on 8 or 9.
Click to expand...
Click to collapse
Thank you, THIS.
Instead of shook's dumb response. My screen caps aren't random. And I'm not the only person having these issues. There are actually numerous mixed threads floating around the general forum or elsewhere. I repeat, the core functionality of this phone is not stable.

I exchanged my phone and started getting the issue shown in screen shots by OP. Spent all week trying to resolve the problem just to find out that my work exchange server had updated security and only allowed ten devices to be connected. It did not remove my old devices from the list and so I had maxed my limit. The old device remove process is in the outlook web client only under web mobile options. MS Outlook did not give me any similar options.
Anyways, the point I am trying to make is it may be related to your exchange server. Have you looked into that?
mreniigma said:
Thank you, THIS.
Instead of shook's dumb response. My screen caps aren't random. And I'm not the only person having these issues. There are actually numerous mixed threads floating around the general forum or elsewhere. I repeat, the core functionality of this phone is not stable.
Click to expand...
Click to collapse

my.ads0 said:
RE: Bluetooth, I believe the OP is referring to the fact that this phone will randomly disconnect from a connected bluetooth device. I have two devices I regularly connect to, my car and my home phone system. The phone connects and remains connected to my car. However, it WILL disconnect from the home phone either randomly, or as soon as I try using the home phone to make or receive a linked call. The second image in the OP's post shows the message that comes up on the phone. It can't entirely be the fault of the connected home phone system because I used to connect my Optimus S to the system perfectly every time and never ever dropped a connection. The OG drops the connection to the home system without fail every single time. If I recall, it sometimes worked on ZV7 but never on 8 or 9.
Click to expand...
Click to collapse
Dont feel bad my bluetooth randomly disconnects as well and im on v8. My exchange to hook into my work email went flawless.
Sent from my LG-LS970 using xda app-developers app

ro.tandon said:
I exchanged my phone and started getting the issue shown in screen shots by OP. Spent all week trying to resolve the problem just to find out that my work exchange server had updated security and only allowed ten devices to be connected. It did not remove my old devices from the list and so I had maxed my limit. The old device remove process is in the outlook web client only under web mobile options. MS Outlook did not give me any similar options.
Anyways, the point I am trying to make is it may be related to your exchange server. Have you looked into that?
Click to expand...
Click to collapse
I was aware of the ten device outlook limitation. But I only have two devices registered currently. I have appropriately set up everything, the phone is just no good.

[Q] Give up on fixing bluetooth? Back to stock and disable OTA updates?

Forgive me if this question has already been asked and answered, but I've been trying for months everything i can with info found online and possible solutions, but Google refers me to a lot of different yet similar situations, and I cannot figure out what to do, and my situation is driving me crazy.
{
"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"
}
Long story short, I use a Bluetooth headset everyday, in my motorcycle helmet. After my phone auto updated to 4.1.1, I experience what can only be called intermittent functionality. I connect my toro nexus to the headset, and play music, and auto answer phone calls. I have no issues connecting the headset, but most often, after i connect the headset, and play music, the transmission of the music plays for like 5 seconds, then cuts out for a few seconds, and then repeats. There are no connection problems on the phone; the phone says BT is connected fine, etc. Sometimes it works, and i can make one commute a day with music and no interruption, but as far as i can tell, there is no situation that is repeatable, ie i cannot find a situation where it will work every time under the same set of variables.
This is extremely annoying for a guy who uses his phone pretty much exclusively to stream music to a BT headset. I have contemplated switching phones, but i love this one. With my Mugen battery, i go all day long, and then some.
I had thought that perhaps the newest incarnation, 4.2, and subsequently 4.2.1 would solve the issue, but no luck. This shieza does not work Bluetooth is officially broken. I have read that others report Bluetooth not working correctly as well, so as I understand it, it is Google's fault for making things wonky after 4.0.4 . I suppose there is a remote possibility that it is only MY PHONE that is busted, but i want to eliminate any doubt as to that by trying everything i can before going to Verizon and having them replace it.
So as a last straw I was thinking of going back to the original factory firmware, 4.0.4 (IMM76K) by following the guide here:
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40D)
I can use the 4.0.4 instead of 4.1.1, right?
And seeing if things go back to normal like they were when i first got the phone, and if it works, great, I will use that version.....but I remembered something...
If I remember correctly, this phone downloads updates over the air, (OTA right?) and then auto updates itself say on a reboot, right? I believe this has happened on the phone like...3 times since I got it.
Is there a way to disable the ota updates?
Many thanks for any who read/respond, I'm at whits end, and I need some help. Any/all input appreciated.
Thanks,
Sytheii

After looking through efrant's guide on back to stock, if i understand it correctly from reading this section of his guide, as long as one of the IMG's i have on the phone is different from the release package that i flash to the phone, I will get an update available notification, but it won't download and try to install automatically?
efrant said:
4) WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the corresponding boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically, but it will install using a custom recovery like CWM. See this thread for details.
Click to expand...
Click to collapse
I was planning on leaving TWRP on the phone anyway, so I could flash a custom rom or whatever at a later date, will that satisfy at least the "disabling" of the automatic ota updates?
Again, any contributions would be greatly appreciated.

For disabling : http://forum.xda-developers.com/showthread.php?t=1581614

madd0g said:
For disabling : http://forum.xda-developers.com/showthread.php?t=1581614
Click to expand...
Click to collapse
that's just the notifications, right?
i suppose i could do that if i followed through, but only if it isn't automatic, y suppose now that I'm looking for confirmation that as long as one of my partitions on the phone was flashed with a non stock img then it wont auto update...

All this has been debated over and over on the forum already.
Sent from my Galaxy Nexus using Tapatalk 2

madd0g said:
All this has been debated over and over on the forum already.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
sigh...well if it's a current debate, then i guess you mean to say that "it" is still up in the air? Since you're not being specific about what you mean, as there are a couple of possible "its" you may be referring to in my original post, I will put my hook in the water and see if you or others might bite, again...
Can anyone help me out with this?

Please read forum rules before posting
Questions go In Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

kennyglass123 said:
Please read forum rules before posting
Questions go In Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
My apologies! Thank you/sryy. I skimmed, rather than read in its entirety. :/

Well, I tried everything I could think to try, including going all the way back to stock, to ICS 4.0.4, I tried a "Bluetooth repair" app i found as well on play, but nothing worked, whatsoever. I incrementally installed updates up to 4.1.1 as well, and still no dice.
When i initially did the back to stock with 4.0.4, i noticed something new, but I think it had happened a few times before, but never constantly.
Playing music on the phone with either Google play music, or Pandora, worked fine, i hit play, and music played. I hit pause, and music paused.
But as soon as I connected the phone to an A2DP headset, the music would pause. When I tried to hit play again, the music would pause after a few seconds, and nothing would work to get it to play continuously, strange no? Disconnect from the headset, and playing music resumes fine.
I ended up getting a new device, but I still have my old one. Bluetooth works flawlessly on the new device, even with a 4.2 Jellybean rom, I decided on using Purity 4.3, with Anarky Purity Kernel. This makes me think that perhaps the phone was just plain busted, i had dropped it a few times, but besides a little nick or two on the other casing I never noticed anything wonky except for Bluetooth.
If anyone can think of anything i might be able to try to fix what might be wrong fireware-wise with the phone, anything I might be able to try out, then perhaps it might serve as a backup.

Question Boot Loop when attempting to access Call Forwarding settings via Phone App (after Sim Swap to eSim)

Hey All, Greetings from Australia.
I am facing some serious issues with my Pixel 6 Pro (well my 2nd brand new device). Looks like I have found a bug which causes the phone to enter a boot loop with no way to fix it. see below steps.
I have done the initial setup on the phone, entered my google account details, phone did its restore thing with no issues.
I activated my eSim service on the device, that seemed to work with no issues (data & calls working as should)
When entering the Call Settings via the Phone App, it immediately crashed, and displayed a Factory Data Reset screen.
It then displayed a recovery screen saying the OS is corrupt, and to perform a factory reset, when attempting this again, it will display multiple errors and continue to restart the phone and prompt for another factory reset
Not sure if the above makes sense, however this seems to be a serious flaw/bug with the new phone/OS, I've attached some pictures for reference and can provide a video of the boot loops.
To repeat, this is my 2nd Pixel 6 Pro device and the first phone was refunded due to the same above issue.
Has anyone experienced this behaviour before, as the phone is still relevantly new, I'm struggling.
Google Support are being absolutely useless thus far.
Looking at the attached video, you can see the eSim service turning off and on, IMO it seems that the eSim component / hardware on the phone is corrupt.
Troubleshooting Steps Perforemed.
1. Performed Full Factory Reset in recovery menu attached
2. Performed a full flash of the Factory Image using the Online Flash Tool - https://source.android.com/setup/contribute/flash
3. I have attempted Erasing the eSim in the Reset Menu, however this does absolutely nothing.
Thoughts??
{
"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"
}
Your browser is not able to display this video.

I just tried to recreate this and I did not get a crash. I'm also using an eSim. Its a weird bug for sure. Maybe it has to do with your carriers eSim. I'm using Google Fi.
Edit*
Just watched your video, that's crazy. Looks like a defective unit in my opinion, but what are the chances you got 2 of them. Have you tried setting it up on wifi, do app updates, then activate service?

eg1122 said:
I just tried to recreate this and I did not get a crash. I'm also using an eSim. Its a weird bug for sure. Maybe it has to do with your carriers eSim. I'm using Google Fi.
Edit*
Just watched your video, that's crazy. Looks like a defective unit in my opinion, but what are the chances you got 2 of them. Have you tried setting it up on wifi, do app updates, then activate service?
Click to expand...
Click to collapse
Hey eg1122
Thanks for attempting to replicate this , I would have felt horrible if you encountered the same issue, but thankfully not.
This definitely seems to be an issue with both my Carrier and eSim provisioning on the device.
To confirm, the behaviour was identical with both phones

Only solution I can think of is a physical sim card, at least until your carrier and/or Google fix it.

simon_mx5 said:
Hey All, Greetings from Australia.
I am facing some serious issues with my Pixel 6 Pro (well my 2nd brand new device). Looks like I have found a bug which causes the phone to enter a boot loop with no way to fix it. see below steps.
Click to expand...
Click to collapse
This just happened to me....aaaarrrrggg...now dealing with google support. Did you ever find a solution? I am with Telstra...so frustrating.

Update: Went to Telstra got a replacement physical sim and phone is back to working as it should...no more esim's for me. I hope this helps someone else.

OzBoy1 said:
This just happened to me....aaaarrrrggg...now dealing with google support. Did you ever find a solution? I am with Telstra...so frustrating.
Click to expand...
Click to collapse
No solution unfortunately, I just gave up on the idea of an e-sim

Not sure how this happened I had used call forwarding before with no issue but this time it was a PITA! I spent a couple of hours with google support and they couldn't help, a replacement was the option they provided.
The physical sim is the fix, I am not sure if you have to use the one that is associated with the eSim account (I did it worked) however I think it just needs a different sim to the eSim to use as set up. When setting up make sure you use the physical sim, not the eSim otherwise back to the boot loop. Once you get the phone set up go to Settings/System/Reset Options/Reset wifi, Mobile and Bluetooth then check the Erase downloaded SIMs, this will remove the problem.
I hope this helps someone else as it was a pain to reset and all the time lost when it was a pretty simple solution to fix....well as long as you have a physical sim handy!

Did you try the dialer commands for call forwarding?

cabagekiller said:
Did you try the dialer commands for call forwarding?
Click to expand...
Click to collapse
I used Phone/Settings/Calls/Call Fowarding.

I had major issues with this. Everything was working ok until i turned on call forwarding which sent the phone into a bootloop as above. I needed to insert a physical sim to get through the factory reset as it hung onto the esim otherwise and went back into another bootloop. Once the factory reset was done, i did another with sim data erase checked - and then when back up and running re-added the Telstra esim.
Whilst things where partially working i still had issues. I noticed that navigating to "Phone -> Settings -> Calling accounts" would crash the phone app.
I also noticed that the Telstra esim appeared as "null" in some places as it was unnamed. I gave the esim a name and now everything is working fine - i can access the Calling accounts menu.
Maybe the blank name causes the issues? This was on a Pixel 6 (not pro)

fish0 said:
I had major issues with this. Everything was working ok until i turned on call forwarding which sent the phone into a bootloop as above. I needed to insert a physical sim to get through the factory reset as it hung onto the esim otherwise and went back into another bootloop. Once the factory reset was done, i did another with sim data erase checked - and then when back up and running re-added the Telstra esim.
Whilst things where partially working i still had issues. I noticed that navigating to "Phone -> Settings -> Calling accounts" would crash the phone app.
I also noticed that the Telstra esim appeared as "null" in some places as it was unnamed. I gave the esim a name and now everything is working fine - i can access the Calling accounts menu.
Maybe the blank name causes the issues? This was on a Pixel 6 (not pro)
Click to expand...
Click to collapse
Sorry to hear about this, I know how frustrating this is. This issue did not go away for me, had ongoing issues, Ended up having to contact google support and they replaced the phone, haven't gone back to esim since. Good luck.

Question MMS not working after January 2022 Security Update

I just updated the P6P with the January update (OTA manually requested in System Update).
After the update, MMS is not working in the Google messages app.
I am on T-Mobile in US and phone purchased unlocked from Google Store
MMS settings haven't changed in the app.
SMS works
Unsure if this matters, but a couple MMS came in right at the time the phone was starting up after the update / when the notification of "finishing update" or something to that effect was showing.
Has anyone else experienced issues with Google Messages MMS with January or December update?
Thoughts on how to resolve this?
If a solution is posted elsewhere, let me know and I will ask the Mod to remove this post.

I'm on a stock P6P US Tmo with Jan. update. MMS is working fine for me, including airplane mode using wifi.

johninsf said:
I just updated the P6P with the January update (OTA manually requested in System Update).
After the update, MMS is not working in the Google messages app.
I am on T-Mobile in US and phone purchased unlocked from Google Store
MMS settings haven't changed in the app.
SMS works
Unsure if this matters, but a couple MMS came in right at the time the phone was starting up after the update / when the notification of "finishing update" or something to that effect was showing.
Has anyone else experienced issues with Google Messages MMS with January or December update?
Thoughts on how to resolve this?
If a solution is posted elsewhere, let me know and I will ask the Mod to remove this post.
Click to expand...
Click to collapse
New bugs? Again?
{
"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"
}
Jokes aside, best try to reset your network/messaging/phone services/apps. That might help you.

MMS is working again but it required factory resetting the phone. Resetting WIFI / mobile only didn't help. Nor did clearing storage in carrier services (if that matters).
On a positive note, signal seems a bit better with this update. I cleanly move from LTE to 5G to 5G UC walking down the hall in my flat. (e.g. my Bermuda Triangle of signals). I love the Net Monster app. I never knew where the cell points are located near me. I am between 2 LTE points which explains the bouncing back and forth. Interesting to see the 5G UC point which is much farther away than I thought.
I am glad that UC is in large letters now vs. the microscopic letters before the update.

I noticed android messages somehow had notification sounds set to nothing, which was odd as I never touched it, but wondered why my phone was vibrating and only playing a sent message tone. I cleared app data and it's back to default.
Try setting up your phones carrier settings manually and see if it helps, or try resetting the value to default.
Go to settings > network > SIMs > APNs (at the bottom) > three dots in the top right > reset to default.
What carrier do you have?

@RetroTech07 thank you! I will keep this in mind in the future.
I have had disappearing notification sounds for years with Android. Not this time though because I completely reset the phone.

Try this....1. turn wifi off. 2. Force stop messages. 3. Clear cache. 4. Open messages. 5. Check the status of "chat features", if it takes longer than a couple minutes to be "connected"...repeat steps 2 &3.

pedro6669 said:
Try this....1. turn wifi off. 2. Force stop messages. 3. Clear cache. 4. Open messages. 5. Check the status of "chat features", if it takes longer than a couple minutes to be "connected"...repeat steps 2 &3.
Click to expand...
Click to collapse
That doesn't really impact MMS though, it's just setting up to use advanced features like wifi and chatting through your PC if you wanted.

No not really. If you're setup to use RCS and it's not connected you will not get any MMS's. Hope you get it figured out.

That's not true. I don't use that feature and get MMS just fine.

Thanks for the options! MMS is working after the factory reset but if it stops again, I will give these a try.

johninsf said:
MMS is working again but it required factory resetting the phone. Resetting WIFI / mobile only didn't help. Nor did clearing storage in carrier services (if that matters).
On a positive note, signal seems a bit better with this update. I cleanly move from LTE to 5G to 5G UC walking down the hall in my flat. (e.g. my Bermuda Triangle of signals). I love the Net Monster app. I never knew where the cell points are located near me. I am between 2 LTE points which explains the bouncing back and forth. Interesting to see the 5G UC point which is much farther away than I thought.
I am glad that UC is in large letters now vs. the microscopic letters before the update.
Click to expand...
Click to collapse
I hate the large letters. Looks so stupid.

If I had better vision, the size might be too much. Poor vision sucks so I will take what I can get!
Sidebar: I hate menus at restaurants where the font is a 6 + poor lighting. I just order the special or a burger or salad. LOL.
Seriously, I take a picture of the menu and zoom in.