[LineageOS] Roaming after phone call - One (M7) Q&A, Help & Troubleshooting

S-Off, TWRP, Rooted, LineageOS 14.1 - 1/30 Nightly Build
HTC ONE M7 Verizon
Wondering is anyone else is having this particular problem. I'm not sure if it's just a visual glitch or there is an underlying issue that actually makes it show Roaming when it indeed is.
Signal shows LTE. After a I make a phone call it shows R (for roaming obviously). LTE will not show up until I reboot. Network type is CDMA+LTE/EVDO. Sub is RUIM/SIM.
Should I update to a newer nightly or do I need to make some changes to settings?

Related

[Q] Failing to recognize that the device is roaming?

I got a device swap today on my Nexus One, so I rooted the replacement phone and restored a nandroid backup of my previous setup with CM6.1 RC1. No problem so far.
Within a few hours of doing this, I noticed my phone still had the FRF91 (4.06) radio. On my previous N1 I'd flashed the 5.12 radio and it was working well, so I flashed it using the appropriate update.zip.
I should point out that I always keep my phone in 3G mode because my provider, WIND Mobile, does not have a 2G network, and any time it's on 2G it is roaming on a partner network at a higher cost to me. I also have data roaming disabled.
After the phone restarted, I noticed within a few minutes that it was connected to the roaming network (WIND Away) and using EDGE data - even though it was set to 3G-only mode *and* no data roaming! I quickly disabled data and flashed back to the 4.06 radio. I didn't see the problem again.
But now upon further testing, I'm still seeing something disturbing. If I flip it to EDGE mode it connects to WIND Away, but the signal indicator doesn't have the roaming "R". Somehow the phone does not recognize that it's roaming anymore. This is incredibly dangerous because it could rack me up huge data charges. Prior to the device swap, any time it was on Wind AWAY I would get the "R". And when I put in my T-Mobile SIM while in Canada, I do get the "R" as well.
Any thoughts on what to do?
I'm having the same problem. I don't think it's related to the radio, but rather 6.1 rc (or in my case nightly ver 245). I'm using radio 5.12.00.8, and when I restore a nandroid backup of cm 6.0, using the same radio the roaming indicator works as it should. Looks like it might not confined to NexusOne http://forum.cyanogenmod.com/topic/9065-is-cm61-rc1-better-than-cm6-stable-for-you/page__view__findpost__p__83991 Hopefully it's not some Wind quirk with cm 6.1
Hammy
hammies said:
I'm having the same problem. I don't think it's related to the radio, but rather 6.1 rc (or in my case nightly ver 245). I'm using radio 5.12.00.8, and when I restore a nandroid backup of cm 6.0, using the same radio the roaming indicator works as it should. Looks like it might not confined to NexusOne http://forum.cyanogenmod.com/topic/9065-is-cm61-rc1-better-than-cm6-stable-for-you/page__view__findpost__p__83991 Hopefully it's not some Wind quirk with cm 6.1
Hammy
Click to expand...
Click to collapse
Yikes, glad to hear I'm not the only one. Let me summarize:
- WIND SIM roaming on T-Mobile: Roaming symbol.
- T-Mobile SIM roaming on Rogers 2G: Roaming symbol.
- T-Mobile SIM roaming on WIND 3G: Roaming symbol.
- WIND SIM roaming on Rogers 2G: No roaming symbol, tries to access EDGE data (OUCH! expensive).
This should probably get its own topic at the CyanogenMod forum.
The Testing screen (*#*#4636#*#*) also has an entry for "Roaming", and when I'm on WIND Away it says "Not roaming" - boo.
I created a thread about this on the Cyanogen forum :
forum.cyanogenmod.com/topic/10193-cm61-rc1-and-roaming-indicator/
But so far it's mainly me :/
Sent from my Nexus One using XDA App
Just an update, the problem has been resolved for future builds of CM. Read the link to the CM forums for more detail.

Issue with CM12.1 signal

i have a m7vzw, using a gsm sim card (Vietnam Vinaphone operator). Recently i decided to switch my rom to CM12.1. It was great, only one issue that my signal is very low ( 1 bar in signal bar). I dont have this issue when i use santod's GPE+ or nusenseven or stock sense roms. I tried to switch the "preferred network" from global to GSM only but it doesnt improve anything. I also delete all APNs and set it manually (exact number like with other roms). I read a post about SKU or something in M7 general forum, but i found out that CM12.1 does not have the /system/customize/acc/default.xml so i dont know what to do
FYI my country doesnt support 4G yet, HSPDA only
Bump. Anyone?
Well I have a T-Mobile M7_UL with CM 12.1 and I can tell you that the signal bars arent very accurate most of the time, so dont freak out

Phone refuses to connect to LTE - Android N

Greetings folks. I own a Nexus 6 XT1103 Unlocked. I'm on MetroPCS currently (piggybacks off T-Mobile LTE).
On Android 6.0.1 ROMs the device connects to LTE networks with no issue whatsoever. The real issue arises when I flash an Android 7.x ROM. The device connects to 3G (UMTS/HSDPA) and remains there even though the network setting is on LTE.
The phone momentarily connects to LTE when I reset the radio from LTE Discovery app and then reverts to 3G (the LTE signal detected just drops off to N/A). Also when the device is momentarily connected to LTE, the carrier label changes to 'No Service' even though network is available and LTE data works for those few moments. After those few moments it's back to UMTS and the carrier label returns to 'MetroPCS'
I've tried the following things to fix this (all in vain)
1. Flashed different radios (05.32, 05.34, 05.42) and bootloaders
2. Flash Android N stock image and then flash custom 7.x ROM
3. Go to the *#*#4636#*#* menu and set LTE only.
4. Resetting APN to default and manually adding APNs (both MetroPCS and T-Mobile)
I know the LTE network in the area is fine otherwise and anyway the moment I'm back on MM the issue the device connects to LTE properly (with a valid MetroPCS carrier label). This issue occurs on any Android 7.x ROM but it didn't happen as often in the Dev Preview, if I remember right.
I request all of you folks to help out if you've seen something like this or have any solutions. Cheers.
PS: Google Connectivity Services installed/uninstalled/disabled doesn't fix it
Have you tried a network settings reset? This worked for me when I lost LTE connectivity.
Settings>Backup & reset>Network settings reset.
Make sure you select network settings reset and not factory reset. They're right next to each other, so if your finger slips and you select the wrong one you'll be very unhappy.
Fixed it!! Flashing the 05.39 radio on fastboot before flashing the ROM seems to do it. Now LTE works with the proper carrier label too. I'd forgotten about the 05.39 radio as it was the one bundled with the N Dev Previews.
Cheers!

Data Issues after upgrading rom and radios

I recently switched from an older version of Pure Nexus to Lineage OS. Lineage recommended flashing the latest radios which I did before upgrading, but now I'm having issues. At first I didn't have any LTE connection, 3G would work if I was in an area that was typically 3G only. I figured out that the APN settings were set to one that said "CDMA 0" and didn't appear to have any settings. I changed that to Sprint Internet n.ispsn and LTE comes on. However, this doesn't stay set and keeps going back to CDMA 0 and yesterday, while I was driving all of my cell service, kept dropping out for 5-30 seconds at a time before coming back on. I'm not sure if this is a ROM issue or a radio issue since I flash those too. Anyone know?
jst07 said:
I recently switched from an older version of Pure Nexus to Lineage OS. Lineage recommended flashing the latest radios which I did before upgrading, but now I'm having issues. At first I didn't have any LTE connection, 3G would work if I was in an area that was typically 3G only. I figured out that the APN settings were set to one that said "CDMA 0" and didn't appear to have any settings. I changed that to Sprint Internet n.ispsn and LTE comes on. However, this doesn't stay set and keeps going back to CDMA 0 and yesterday, while I was driving all of my cell service, kept dropping out for 5-30 seconds at a time before coming back on. I'm not sure if this is a ROM issue or a radio issue since I flash those too. Anyone know?
Click to expand...
Click to collapse
I have also had some issues with LTE after flashing the latest radio but no problems with the APN settings. I haven't done it yet since the June update should be out soon but if the update doesn't have a new version of the radio I'm going to try flashing an older version to see if that helps.
You can always roll back the radio. Just flash an older one and test it. I haven't been on cdma for a while but if you can update the PRL still you might get better reception.
Sent from my Glade[emoji768] Plugins
To update this for anyone having a similar issue, I went to the APN settings and did Reset to Default. Seems to have fixed it.

VOLTE T-Mobile, not working (WORKING as of last update)

I'm experiencing issues with VOLTE on T-Mobile. My phone switches immediately from an LTE+ DATA connection to HSPA the moment a call is placed. Of course, VOLTE is enabled on the settings side. I'm running an unmodified system, upgraded to PIE.
I've been on the phone with T-Mo to make sure the APN is correct (nothing special to mention here). I've also tried different connection combinations using the *#*#4636#*#* with different results but, even though the phone connects really fast to DATA (LTE+), I cannot get VOLTE to function in any case. On the other hand, WiFi calling works just fine.
On a chat with Razer, they just told me that VOLTE is unstable with T-Mobile and, to disable the function altogether from settings.
Before I give up, I'm asking the geniuses here for ideas or experiences? Any ideas anyone?
cabegol said:
I'm experiencing issues with VOLTE on T-Mobile. My phone switches immediately from an LTE+ DATA connection to HSPA the moment a call is placed. Of course, VOLTE is enabled on the settings side. I'm running an unmodified system, upgraded to PIE.
I've been on the phone with T-Mo to make sure the APN is correct (nothing special to mention here). I've also tried different connection combinations using the *#*#4636#*#* with different results but, even though the phone connects really fast to DATA (LTE+), I cannot get VOLTE to function in any case. On the other hand, WiFi calling works just fine.
On a chat with Razer, they just told me that VOLTE is unstable with T-Mobile and, to disable the function altogether from settings.
Before I give up, I'm asking the geniuses here for ideas or experiences? Any ideas anyone?
Click to expand...
Click to collapse
I hope this can be figured out. Im waiting for my Razer 2 phone delivery and also on T-Mobile. What OS are you running? Android Pie?
Yes, I'm on Pie.
Good news! with today's update (3-20-2019), my phone is using VOLTE technologies to connect audio calls. Phone calls sound immensely better now (the "HD" icon shows up during the call and the "LTE+" connection indicator in the status bar remains through the call).

Categories

Resources