The bug seems to be related with 4g, just disable it.
Go to settings-connections-mobile networks- and select 3g/2g mode.
Thats it bug fixed.
At least while samsung fix the problem, you can also downgrade to first android 12 version, or 11 the problem isn't at there.
Related
Hi all.
i flashed last nightly version of CM 13 to my d855.
I have two problems.
1- Mobile networks choosen at LTE (recomended). I cant change it. 2G or 3G option is looks like selectable but nothing happened when i select it. Phone always staying just 2G (edge) mode.
2- After the phone call there is a message appear on screen: Invalid number (with bleeping)
if you have any idea for the fix this problem please write.
Thanks.
musluzut said:
Hi all.
i flashed last nightly version of CM 13 to my d855.
I have two problems.
1- Mobile networks choosen at LTE (recomended). I cant change it. 2G or 3G option is looks like selectable but nothing happened when i select it. Phone always staying just 2G (edge) mode.
2- After the phone call there is a message appear on screen: Invalid number (with bleeping)
if you have any idea for the fix this problem please write.
Thanks.
Click to expand...
Click to collapse
I had the same as your Nº 1 Problem, i tried to go to *#*#4636#*#* and force the phone to change to 3g but it didn't work either.
So i went back to my previous rom (XenonHD 5.1.1) y enter the menu on *#*#4636#*#* and select wcdma prefered (and i dis change).
I flash again CM 13, and the phone got 3g, but i can`t change the network mode, so i only got 3g or 2g.
i think that the rom doesn`t actually have the right permissions to change that now, hope it gets solved.
Hope you find this helpfull. And sorry if i misspelled some word, english is not my home language.
Thanks i got clearly. Not my home language too
1. As for your signal problem, depends on your carrier as CM is trying to be universally available to all carriers.
2. And as for the "invalid number" error, it is a very well known CM 13 issue according to CM moderators and developers and has been pushed to get fixed in upcoming nightly releases.
Source: http://forum.cyanogenmod.org/topic/118917-lg-d855-invalid-phone-number-error/
Have the same number 1 problem. Htc one m8 dual.
Hello everyone
I've got a problem with my LG G3 my GPS stopped working or work for about 1 min and stops again
my software info is
android version 5.0.0
kernel version 3.4.0
i had this problem once and i took my phone to get repaired and they only did a factory reset on my phone (they said they won't, does f**kers)
this helped and i had GPS reception for some time but i think it was when i updated my phone to android 5.0.0 the problem came back
i tried using the program "GPS status & toolbox" but it cant even get any gps signal.
I tried using the update software option on my phone but it says I've got the up to date version
Is there a way to fix this? (preferably a way that doesn't include deleting the data on the phone)
Hi,
I have been facing problem of not getting 4G LTE network on my One Plus 5T. And after a while I realised that it's after the latest OS update of OOS 5.0.3. I am in a full 4G network area and my sim is also working fine when I put it into different phone. So I know for sure that it is not a problem of Network or Sim as both are working fine. I have also searched on google abt the same and lot of people are facing the same problem however I could not find any fix or resolution for the same. I have tried clearing the cache from the recovery but no help, also I have selected LTE only thru *#*#4636#*#* but still no help. Any help would be really appreciated. Thanks.
I'm assuming your APN name is correct?
It seems like almost all problems with Oreo updates are caused by dirty flashes. Typically a clean install fixes everything.
If you didn't do a clean install that's step one.
Solved, go to read my tread
Hello
For information:
On ROM O+ 9.0.4, the 4G hook works better on the "Global auto (PRL)" parameter.
Best Regards
Hi, recently some Oneplus 5t have problems wtih the new ROM, the smartphone is unable to catch 4G LTE network, and hard reset can't resolve thsi bug, to resolve you must use this code in the Dialer *#*#4636#*#*, go to info and then set preferred network type to LTE/TD-SCDMA/UMTS
Hi, I have the same problem. It seems to depend of the phone configuration and the carrier. I found no improvement with all the updates from OnePlus. I am reluctant to make a factory reset . I guess it could resolve the problem.
I think I will give a try with lineageos . I would appreciate if someone already tried it to solve this problem.
I just bought a Poco F3 to replace my Pixel 2XL (lineageOS 18.1 microg)
Anyhow, while I wait for the 7days counter, I wanted to see if tI should wait until Android12 MIUI 13 is officially released. This way I can get any firmware updates, etc... before upgrading to a custom rom.
Is waitting worth it to flash and upgrade everything before the change? Normally I wouldn't bother, but when I was testing the phone, I wasn't able to get data to work until I forced it to 3G only.... I was reading this is because of some weird voLTE issue and it needs to be turned off...
Is it likely that a firmware update bundled into the Android12 MIUI13 update will fix this?
Thanks!
Link to Issue and Resolution
ok, for anyone having the same issue, was able to replicate and verify the suggested fix.
The issue seems to happen when there is a mismatch between VoLTE support of the line and the phone.
If you don't have VoLTE enabled on your line but have it enabled on the phone settings, it seems some VoLTE specific queries happens during tower handover which then fails resulting in a kernel panic (F3 bug) which causes the modem to just reboot (losing internet for 10~15 seconds) or for the whole phone to reboot (depending on the firmware on the phone).
The fix is, to either call your carrier and make sure VoLTE is enabled, or just disable VoLTE on your phone (for lineage it's under "Settings" -> "Network & Internet" -> "Mobile Network"). I have confirmed that disabling VoLTE on lineage works and I no longer get the location-specific reboots I got when I enabled it a few weeks ago.
Click to expand...
Click to collapse