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.

[Q] Stock JB 4.1.2 OTA Update - Data Roaming Guard Nagging - Help?

I've kept my phone stock from point of purchase. Updated to ZV9 when it came out OTA and it did nothing but break ChompSMS's ability to send MMS which pissed me the hell off (can still do it from stock messaging app thank GOD). Hoped it would be fixed by the time Jellybean came around.
Then, the ZVB update "came out" (lies!) on the 7th and weeks passed and I never got the OTA, so I was kind of ticked off. Then the other day I decided before I updated I should try a factory reset to freshen things up and see if it fixed my MMS issue as well. Freshened things. Didn't fix MMS issue. Also, out of no-where - ZVB update prompt. Click that ****. Bam - Jellybean.
So, My MMS issue is still around, but now there's new stuff to annoy me! Yay!
I work in a building that's made of thick concrete and steel, so my phone switches to roaming quite often. Today (My first day back at work with JB) I notice the Data Guard prompt constantly coming on and telling me that the world might end and I might be upcharged for roaming. I check the *Don't show this again* box and click Roam. And it goes away. Turn off screen. Turn on screen. It's back. Same charade, check *shut the hell up* box and it goes away. Comes back next time I unlock the phone. Bottom line, this prompt isn't going away and staying away despite my checking the box. I've tried the settings and found something interesting. Turns out the Data Guard settings are greyed out! Joy! How annoying...
{
"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"
}
So, yeah. The nagging prompt literally doesn't go away. And this gets to happen to me everyday at work. Happiness.
That, and this bold font across the system UI is ugly as hell. Please let me not be the only one who feels this way. Tell me this can be changed (even if it means rooting).
Has anyone had this same bug/issue/nag? Can anyone suggest a solution? Feedback is much appreciated. I would try calling Sprint, but wouldn't want to confuse the novices on the other end of the line lol

I've seen that screen more than once, though not as frequently as you. My house gets terrible reception, so when I lose my Airrave signal and network signal, it pops up occasionally. Bugs the hell out of me. The setting just won't stick, even when it's set in system settings too.
You're not alone, I'm not a fan of the bold system font either.

Roaming and " avoid poor WiFi connections" don't seem to stick for some reason. The roaming nag has been with us since day 1.
Sent from my LG-LS970 using xda premium

Yeah, now that you mention it, the avoid weak wifi connections setting switched back on for me also. Very annoying. I was so confused why I suddenly couldn't connect to my wifi from my bedroom. Glad I thought to check.

Same here, noticed this a couple days ago.

This is literally bullcrap - I really hope there's another OTA soon to fix the bugs and bring back all the stuff they excluded. I'm so close to just reverting back to ZV9...

I ran into this tonight
Says I am roaming and to change my settings to allow data roaming. Yet, I get no data.

same problem here too, very VERY annoying...glad to know it's not just me

Mindspin_311 said:
I ran into this tonight
Says I am roaming and to change my settings to allow data roaming. Yet, I get no data.
Click to expand...
Click to collapse
I've also had something like this, even before the Jellybean update - Tells you to turn on roaming by going to settings, when it's already on.

I think I've found the solution - I was going through my settings and went to "Mobile Data" and hit the menu button. Turns out there's a list of settings that's hidden here under the menu button. Why they did this, I do not know. But the tick box for Data Roaming is there, unticked. So I ticked it. I'm not in a place where I can test whether the Roam Gaurd pops up, but the box wasn't checked before, so hopefully the Roam Guard will STFU.

Nice find, I have checked the box. Lets see if the issue gets better.

Mrichelo said:
I think I've found the solution - I was going through my settings and went to "Mobile Data" and hit the menu button. Turns out there's a list of settings that's hidden here under the menu button. Why they did this, I do not know. But the tick box for Data Roaming is there, unticked. So I ticked it. I'm not in a place where I can test whether the Roam Gaurd pops up, but the box wasn't checked before, so hopefully the Roam Guard will STFU.
View attachment 1899079
Click to expand...
Click to collapse
I know I'm bringing a thread back from the dead. But anybody have success with this issue in the stock ROM? After selecting the "Data Roaming" option, I will randomly see that it becomes unchecked and I still get asked to roam. Even with the roam guard appropriately checked. I've tried going through the build.prop as well, with no luck.

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.

General Google acknowledges Pixel 6 network bug following December update

https://www.androidcentral.com/pixel-6-network-problems-december-update

I just ran into this driving through an area where I usually lose signal and call drops. Today the phone did not reconnect to the network until about a half mile away from where it usually reconnects. Other than that, I've been experiencing better data connections since the December update.

For me personally, the mobile network quality on P6P (1 physical sim, one esim) is bad compared to my 2 physical sims Oneplus 5T, for both carriers. I am in Aus. My area does not have 5G covered, always at 4G. I have tried both A1 and A5 updates (for AU) and usually the mobile strength (I see the triangle bar) of A5 is even worse than A1 lol. I don't know what happens in the background, but I have not expected mobile network becomes a problem with a phone in 2021. And because the network quality is poor, the battery life saw immediate consequence. Maximum 4.5 hours SOT even with "Proxy" wakelock issue addressed and no heavy-tasking time.

I have a new Sim from Verizon arriving on Monday which I hope improves my cellular connection. I had to reboot my phone today while driving through a rural area in order to reconnect. Toggling airplane mode didn't work.

I hear on a certain telegram group that users are using the modem back from November. This solves the problem because the full signal is back. You have to unlock and flash the radio from november. When thats done your great signal is back! So there must be a problem with the radio from december.
You can simply remove the radio (modem) from the .zip of factory images. Then in fastboot flash it mode: fastboot flash radio radioblablabla or whatever it's called. The only drawback is that you have the bootloader must unlock and this at the cost of a complete wipe

Here's the proof that it works. It's not the pro version, but that doesn't matter.
{
"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"
}

@DanielF50 brought to my attention the following Reddit post:
DanielF50 said:
Apparently the latest beta for Carrier Services potentially fixes this, some people in the comments are still having issues though (not that I have/had this issue).
Source:
https://www.reddit.com/r/GooglePixel/comments/rk1hfk
Click to expand...
Click to collapse

Fixes for some people but not others and I am in the others camp!

I personally don't have this issue. However, I read that updating Carrier Services to the latest BETA version fixes it.

Taking a LONG time to join the Beta program for Carrier Services. Been over 10 minutes and still waiting for approval.
After 20 minutes, I was approved to join the Beta program. I cleared memory and rebooted. Hopefully this will improve my carrier connection. I have a new SIM from Verizon too.

swieder711 said:
Taking a LONG time to join the Beta program for Carrier Services. Been over 10 minutes and still waiting for approval.
Click to expand...
Click to collapse
Yeah happened to me, you can try to close the Play store and go back in and you should've joined and can update from there!

wilpang said:
Yeah happened to me, you can try to close the Play store and go back in and you should've joined and can update from there!
Click to expand...
Click to collapse
That's happened to me for some non-Google app recently too. Closed the play store, might have even rebooted, and then the beta version was ready for me to update to.

swieder711 said:
Taking a LONG time to join the Beta program for Carrier Services. Been over 10 minutes and still waiting for approval.
After 20 minutes, I was approved to join the Beta program. I cleared memory and rebooted. Hopefully this will improve my carrier connection. I have a new SIM from Verizon too.
Click to expand...
Click to collapse
You can also find the beta app on APK mirror

Downloading the carrier services beta version totally worked for me. I'm in Germany with T-Mobile (Congstar) and got the A1 December update. Since the update I had no signal at work most time but now it's on full power again.

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.