[Q] Nexus 5 radio refuses to turn on - Nexus 5 Q&A, Help & Troubleshooting

Hi all,
My Nexus 5 was working perfectly fine on Purity ROM for months. A week ago, the battery ran down and the phone turned off. I charged it overnight, and when I powered it on next day, It had no mobile service. Trying to search for networks, I get "Error while searching for networks".
I toggled airplane mode... no change.
I rebooted the phone... no change.
I checked the phone status, signal strength was zero, and the radio showed as off.
SIM was replaced to no avail, and the original SIM works fine in another phone.
To troubleshoot, I reflashed to current stock images (KTU84P) and wiped cache; no luck.
I have now tried every stock ROM back to KOT49H, and even tried the dev preview of L.
I also tried flashing Carbon, SlimKAT, and MIUI, nothing changes.
Dialling *#*#4636#*#* brings up the testing menu, but I can't turn on the radio. No error, it just won't toggle the button.
I tried to flap the radio via adb shell using
radiooptions 0<reset radio>
radiooptions 5 <turns radio on>
radiooptions 6 sp.telus.com <sets APN>
At one point it came alive enough to tell me I had voicemail, showed my phone number, and showed me a list of available APNs, but that's it. It still wouldn't find any networks.
I checked the radio log:
logcat -b radio
This pops up when I try to search for networks
D/RILJ ( 1413): [0735]> QUERY_AVAILABLE_NETWORKS
D/RilRequest( 1413): [0735]< QUERY_AVAILABLE_NETWORKS error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
and this when I try to manually turn on radio in testing menu:
D/RILJ ( 1413): [0738]> RADIO_POWER on
D/RilRequest( 1413): [0738]< RADIO_POWER error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
I rooted and installed GetRIL; it reports "Unknown RIL found", and the only RIL it has available for install is M8974A-1.0.25.0.23 (from build KOT49H). I suspect the database is out of date.
Any suggestions? I can't believe this is a hardware failure out of the blue.
Thanks in advance for any help.

Same problem here
upright_animal said:
Hi all,
My Nexus 5 was working perfectly fine on Purity ROM for months. A week ago, the battery ran down and the phone turned off. I charged it overnight, and when I powered it on next day, It had no mobile service. Trying to search for networks, I get "Error while searching for networks".
I toggled airplane mode... no change.
I rebooted the phone... no change.
I checked the phone status, signal strength was zero, and the radio showed as off.
SIM was replaced to no avail, and the original SIM works fine in another phone.
To troubleshoot, I reflashed to current stock images (KTU84P) and wiped cache; no luck.
I have now tried every stock ROM back to KOT49H, and even tried the dev preview of L.
I also tried flashing Carbon, SlimKAT, and MIUI, nothing changes.
Dialling *#*#4636#*#* brings up the testing menu, but I can't turn on the radio. No error, it just won't toggle the button.
I tried to flap the radio via adb shell using
radiooptions 0<reset radio>
radiooptions 5 <turns radio on>
radiooptions 6 sp.telus.com <sets APN>
At one point it came alive enough to tell me I had voicemail, showed my phone number, and showed me a list of available APNs, but that's it. It still wouldn't find any networks.
I checked the radio log:
logcat -b radio
This pops up when I try to search for networks
D/RILJ ( 1413): [0735]> QUERY_AVAILABLE_NETWORKS
D/RilRequest( 1413): [0735]< QUERY_AVAILABLE_NETWORKS error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
and this when I try to manually turn on radio in testing menu:
D/RILJ ( 1413): [0738]> RADIO_POWER on
D/RilRequest( 1413): [0738]< RADIO_POWER error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
I rooted and installed GetRIL; it reports "Unknown RIL found", and the only RIL it has available for install is M8974A-1.0.25.0.23 (from build KOT49H). I suspect the database is out of date.
Any suggestions? I can't believe this is a hardware failure out of the blue.
Thanks in advance for any help.
Click to expand...
Click to collapse
Hey man, I'm having the exact same problem. Have you been able to fix it?

Please, don't let the thread die!
I'm also facing the same problem here. I flashed stockversion multiple times to fix, but no success.
I'm getting the same errormessages at logcat, mostly:
isDataAllowed: not allowed due to - Attached= false - SIM not loaded
after 20 hours of investigation still no result.
I'll get in contact with the Google Support tomorrow and I still won't believe this is a hardware problem, especially because my warranty exceeded at f**king Wednesday 27th of January 2015 (one day before the problem occurred).
Please help!

I'm having the exact same issue - phone was working fine until the battery went completely dead during the night. It took me a while to even get it to boot up again and when I did there was no network connection (also says 'no sim card' on lock screen) but everything else is working fine. I flashed stock 5.0.1 onto it and did a factory reset but nothing worked (SIM card also works fine in another phone so its not a network issue). I found this post after finding out about the testing menu and the turn radio on button not responding. I had a look at logcat and it prints out those same messages for me. I think this is probably the first time i've rebooted or let the power get that low in a long time so I'm wondering if cutting the power to the radio triggered something or some sort of internal battery died. Anyone any ideas?

I checked the RIL sequence in a working phone when it has no sim card inserted and it's different to the POWER error shown in the OP's post:
D/RILJ ( 2002): [0049]> RADIO_POWER
D/GSM ( 2002): Radio State: SIM_LOCKED_OR_ABSENT
D/RILB ( 2002): Notifying: SIM locked or absent
so it seems it's unrelated to a missing/broken sim card. I guess it must be down to a hardware fault in the qualcomm chip or connections to it, e.g. damaged pins, modem firmware corrupted, something shorted or dirty etc.
Is there anything I can do to verify this is the case? Like maybe try to send some AT commands directly to the modem, or inspect the phone for damage/dirt (I'm unsure as to where the modem chip/antennas/contacts are on the phone)? It seems to be not an uncommon problem after a year or so of use. I tried to examine the kernel logs e.g. dmesg but didn't notice anything obvious and not really sure what to look for.
Any help much appreciated as the phone is out of warranty (albeit only slightly) and probably not worth the repair cost (if it's even possible to fix).

Did any of you ever find a fix for this issue? I seem to be having the same problem.

lazytt said:
Did any of you ever find a fix for this issue? I seem to be having the same problem.
Click to expand...
Click to collapse
This issue is called "side effects of custom roms".

Is it contagious? Because I dont run custom roms

lazytt said:
Is it contagious? Because I dont run custom roms
Click to expand...
Click to collapse
No. Then you don't need a doctor. You can get a new SIM card or switch to other network provider.

zagorteney said:
No. Then you don't need a doctor. You can get a new SIM card or switch to other network provider.
Click to expand...
Click to collapse
I tried a different network/sim card with the same results. This phone was working fine just a few days ago. It suddenly stopped connecting.

Are they any noticeable bulges to the battery on the rear of the unit? Any battery problems during normal use?

Hello guys. Same problem.. I bought a nexus 5 from someone on ebay and I was ripped off... At first I had the "red light of death" when plugged in.. Then after a few minutes it turned on but was stuck on infinite boot loop and couldn't get past the welcome screen. So I left it for an hour and came back and it managed to stay on for 5-10 minutes at a time. Then I tried my sim card to see if it would connect.. And it didn't it just keeps saying searching.. then it said "error while searching for networks" choose automatically says "cannot connect to this network at this time. try again later" I tried a few self troubleshooting tips but nothing worked...
I went into phone info and it says radio is off and like others, radio cannot be toggled on.. The sim card works in my other phone but not this one. And the APN settings show up..... so im guessing from what people are saying about this problem is that perhaps someone tried to flash a rom that wasn't compatible? And can anyone verify if someone can reflash the stock image or firmware or w/e is that'll do it? Can anyone help me please

povertyd said:
Hello guys. Same problem.. I bought a nexus 5 from someone on ebay and I was ripped off... At first I had the "red light of death" when plugged in.. Then after a few minutes it turned on but was stuck on infinite boot loop and couldn't get past the welcome screen. So I left it for an hour and came back and it managed to stay on for 5-10 minutes at a time. Then I tried my sim card to see if it would connect.. And it didn't it just keeps saying searching.. then it said "error while searching for networks" choose automatically says "cannot connect to this network at this time. try again later" I tried a few self troubleshooting tips but nothing worked...
I went into phone info and it says radio is off and like others, radio cannot be toggled on.. The sim card works in my other phone but not this one. And the APN settings show up..... so im guessing from what people are saying about this problem is that perhaps someone tried to flash a rom that wasn't compatible? And can anyone verify if someone can reflash the stock image or firmware or w/e is that'll do it? Can anyone help me please
Click to expand...
Click to collapse
Open up a eBay dispute and they'll refund you

dicecuber said:
Open up a eBay dispute and they'll refund you
Click to expand...
Click to collapse
Heh... Problem is guy listed it for "parts only" (plz dont burn me just read my reason why..)but the description only said phone gets warm when charging and battery doesn't last all day.. I could have lived with that except the phone was a steaming pile and there were several issues.. After speaking with him yesterday and today, he only offered a 50 usd partial refund or to send it back and get 120 USD back. I talked him into a 60usd refund... I wasnt sure if I could get any money back at all if I went through ebay or paypal. I'll either keep it as an iPod now or sell it as is. And lose only 50 bucks or something.
So tonight I found a guy locally who knows how to root androids and fix issues like this stuff... He spent an hour and a half on my phone... Tried everything... And NOTHING worked. So.. Whatever... Lesson learned...

lolcakes203 said:
Are they any noticeable bulges to the battery on the rear of the unit? Any battery problems during normal use?
Click to expand...
Click to collapse
no and no

I've been busy so wasn't able to look into this any further since. I think it might be related to the battery somehow, as I've read several reports of how it started when the phone ran out of juice completely. My next step was to try to send AT commands directly to the modem to see if it responds at all but I reckon something got fried or a particular power circuit cut out.

Same problem
I wish someone would post a fix for this. I'm having the same problem

I have this problem too. Starts on saturday after run out of battery. Someone found a solution?! please!!!

same error messages but not the same phone
http://forum.xda-developers.com/gen...rk-caterpillar-s50-help-t3142484#post61543201

upright_animal, did you solve the problem?

Related

[Q] Wifi Error (but not your usual error)

ok, so weird issue for me.. and idk if anyone else is experiencing it cause it doesn't seem like it.. I'm getting wifi error (and before anyone says anything about my router, it's already configured). It just won't turn on no matter what. I hit it, it says a grayed out "Turning On..." and then error again. No attempt or anything. I go into wifi settings and everything under Wi-Fi is grayed out, that's the network notification at&t wifi hot spot setting and wifi networks. I've been trying hard and absolutely no resolution. A google search only affords me more "fixes" for my router and that's not the issue. If i can get a referral somewhere else that doesn't talk about the router being the issue then i'd greatly appreciate it.
**update**
sorry for the "vote for.." whatever it says, i didn't mean to i was trying to subscribe so please don't get upset about it. kthksgb
Vahnyyz said:
ok, so weird issue for me.. and idk if anyone else is experiencing it cause it doesn't seem like it.. I'm getting wifi error (and before anyone says anything about my router, it's already configured). It just won't turn on no matter what. I hit it, it says a grayed out "Turning On..." and then error again. No attempt or anything. I go into wifi settings and everything under Wi-Fi is grayed out, that's the network notification at&t wifi hot spot setting and wifi networks. I've been trying hard and absolutely no resolution. A google search only affords me more "fixes" for my router and that's not the issue. If i can get a referral somewhere else that doesn't talk about the router being the issue then i'd greatly appreciate it.
**update**
sorry for the "vote for.." whatever it says, i didn't mean to i was trying to subscribe so please don't get upset about it. kthksgb
Click to expand...
Click to collapse
I've never heard of that error before so I don't know. Are you rooted? What version of Android are you running? What I'd do is backup all your apps, text messgs, contacts, etc., and do a factory reset and see if that fixes it. Worst case scenario you could flash a fresh new version of 2.3.5 via RSD Lite and you'd almost surely have the problem fixed, unless it's a hardware issue.
I actually started off on 2.3.5 with the issue, and then i started having problems with my ability to actually get past FB, so i had to do a the rsd fix where i force stock on there again. From that point since it still wasn't working I went and pushed ota which took forever and got onto blaze hoping/praying that it would finally work after that. ultimately nothing worked so I'm here now at the mercy of the forum hoping some guru might have something that I could try.
Vahnyyz said:
I actually started off on 2.3.5 with the issue, and then i started having problems with my ability to actually get past FB, so i had to do a the rsd fix where i force stock on there again. From that point since it still wasn't working I went and pushed ota which took forever and got onto blaze hoping/praying that it would finally work after that. ultimately nothing worked so I'm here now at the mercy of the forum hoping some guru might have something that I could try.
Click to expand...
Click to collapse
Wow brother, if you flashed the 2.3.5 fxz to it and still had the problem, i'm thinking there's a hardware issue.
yea, i figured. so i've already contacted motorola and since i'm still under warranty i can return it and they'll send me another one. them's the break, but i got 2 weeks before i even have to decide on that so its not something i'm rushing towards lol
Try going to adb shell
su
ifconfig tiwlan0 down
(toggle airplane on then off)
ifconfig tiwlan0 up
(toggle airplane on then off)
Maybe that will bring your adapter back up. Hope that helps.
hope this doesn't mean anything bad, but it says error no such device
i did adb shell in cmd prompt, it started up went [email protected] then i did su and it changed to [email protected] and i did what you said.. and it gave me that error
Had the same error problem a few ago using blaze v3 rom. After reboot, it was solved and I could connect to my wifi again.
Have no idea what caused the problem, as I didn't do anything out of the ordinary with the device since the update from blaze 2.5.
Sent from my MB865 using XDA
I am facing same issue on Droid 3. it does not work with Stock ROM, but works with CM9 or AOKP based rom.
wifi error afterusing motofast fast script 2.3.5
i am having the same problem also. it just started right after i did the "flash back to 2.3.5 moto fast script" the first time i used it everything was fine but this time ..which i did the same process....i am getting that same error.and when i try to ota to 2.3.6 it says that i need to turn on wifi ????since then i have tried factory reset and still had the issue.then i rooted 2.3.5 and using cwm i was able to restore a backup.so now i am back on 2.3.6 and i am still having the same problem.i have tried a few wifi fixer apps from the playstore but nothing seems to work. and i still dosnt want to OTA without wifi working :confused........so it seems like there is something nthat went wrong with the motofast script or something got erased ???i hope this will help to try and figure out a solution ......btw im new to this somewhat so please bare with me
trev1134 said:
i am having the same problem also. it just started right after i did the "flash back to 2.3.5 moto fast script" the first time i used it everything was fine but this time ..which i did the same process....i am getting that same error.and when i try to ota to 2.3.6 it says that i need to turn on wifi ????since then i have tried factory reset and still had the issue.then i rooted 2.3.5 and using cwm i was able to restore a backup.so now i am back on 2.3.6 and i am still having the same problem.i have tried a few wifi fixer apps from the playstore but nothing seems to work. and i still dosnt want to OTA without wifi working :confused........so it seems like there is something nthat went wrong with the motofast script or something got erased ???i hope this will help to try and figure out a solution ......btw im new to this somewhat so please bare with me
Click to expand...
Click to collapse
only once did i have problem with wifi on this phone and i never fixed it on 2.3 ...
after a lot of trial and error though, i got it fixed with upgrading to ics.
other than that, does your bluetooth do the same? because symptoms like these usually mean water damage. you might want to check the indicators, (if the a2 has any) --- if you broke your wifi by updating rom, this probably isnt the case.
I noticed that the description for the wlan interface is different in the build.prop between GB and ICS. So you might check your /system/build.prop.
Look for this towards the top of your build.prop
Code:
# wlan interface
wifi.interface = tiwlan0
softap.interface = tiap0
In GB wifi.interface = tiwlan0
In ICS wifi.interace = wlan0
So make sure the value is correct, if the value is wrong it will show your wifi "greyed out" in the settings. Anyway, it's something to try, and I hope that helps. If you change the value, make sure you reboot then check to see if it is fixed.
Since I don't know if anyone is still looking into this at all because I haven't seen many updates to this thread, I'm wondering if anyone has checked the kernal information. I was able to do some searching (btw I haven't sent in my atrix 2 in yet because of work) and I found that there was some issues in regards to the Kernal. I don't know if thats true or not but I would like to see someone test it out or try it out or what have you and see if they can shed some light on the situation because the situation is rather bleek, and i'd rather not have to send in a perfectly good phone that was working just fine before the flash, and still wouldn't work after reflashing the AT&T rom.

[RESOLVED] OPO crashed, got hardbricked and now is having issues getting cell signal

It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Hi, Last week I had my phone connected to power bank over night with "Sleep as Android" turned on. In the morning I got my wake up alert but I was unable to wake up my screen to turn it off... so I had to keep the power button down and shutdown the phone.
After that I have faced boot loop (phone worked fine previous evening).
I have tried rebooting phone couple of times but nothing worked so I have restored backup of last CM11s from TWRP (I was running on CM12 nightly during the crash). Phone booted up poperly and I thought everything is fine however after couple of hours I noticed my phone is asking me for my PIN so it has apparently rebooted. It appeared that it is rebooting every couple of hours and after every call (like 5 sec after call ended)...
I have tried restoring other backup but I was facing the same issue. I have done clean install of current CM12 nightly and got the same...
Facing that I decided to clean my phone completely... I have backed up all my data and did wipe and format of everything of everything I could from TWRP. Then via fastboot I have been tring loading YNG1TAS17L 64GB (from here) by flash-all.bat file. After loading bootloader I have received message <waiting for device> and my phone got hardbricked...
I managed to recover it using this guide.
Then I loaded TWRP again and installed COS 12.
On that point my phone started working stable but after a while I noticed that is started losing cell signal. Sometimes it was just for couple of seconds and sometimes it lost it for good (while tring to hardcode cell operator I was getting "error while searching for networks" and I was able to restore connectivity after couple of reboots).
I decided it could be radio/modem related so I have applied full firmware. No go. Loaded CM12 nightly - the same, loaded that modem from oxygen again - no go.
I have tried installing latest BlissPop, Mahdi ROMs and Oxygen and still facing the same issue.
Tested SIM card on other phone and it works fine, tested other SIM card on my OPO and still the same issue so it is phone related.
Getting the following in logcat during time phone is unable to connect to cell signal:
Code:
05-31 11:57:36.265 D/GsmDCT ( 2457): [0]isDataAllowed: not allowed due to - SIM not loaded and not NV subscription
05-31 11:57:36.265 D/GsmDCT ( 2457): [ApnContext:mms] getApnSetting: apnSetting=null
05-31 11:57:36.268 D/GsmDCT ( 2457): [0]isDataAllowed getRecordsLoaded=false
Anyone has any idea what could be a reason of this issue and how to fix it? At this moment everything is working fine except phone calls and Internet over network operator (Wifi works fine). Thanks in advance.
UP
Anyone has any idea? I believe I have narrowed the problem down a bit. It seems 2G/3G is affected only. As long as I'm in LTE range the connection is stable (that explains why I noticed the problem after few hours when I left home).
I have played a bit with hardcoding band and noticed that LTE is running stable (with GSM Signal Monitoring app). When switching to 3G it is dropping every couple of seconds. The strange thing is that 2G is sometimes affected and sometimes not... When switching LTE->2G it seems to be running pretty stable but when switching from 3G->2G it is acting the same way as 3G.
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
spx2000 said:
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
Click to expand...
Click to collapse
OP updated the post with how it was fixed. Sorry to bump the thread, but thought I'd inform spx that there was an update. Glad it worked out for you OP, I've saved this in case it ever happens to me, and good luck to spx. Hopefully someone puts this info in a sticky so others can try that if they are stuck too.
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO
artiwal said:
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Click to expand...
Click to collapse
Where is the 44S that OP used? I have something similar happening with my phone. I revived my phone from a hard brick and now it's not connecting to the cell network. Wifi works, IMEI shows when SIM is inserted, no EFS partition backup (I didn't know that was a thing to do until it was too late).
FWIW, my current build is KTU84Q and I'm running CM-11-20141008-SNAPSHOT-M11-bacon

signal issue

I boot up the phone with an inserted sim card and displays "No Service", I had it on android 4.4.4 before and changed radios, did pretty much everything that I can find on the internet (did a lot of searching) this is my main sim card I use for my other phone, just paid my bill today...
went to the service menu via #*#*4636#*#* > phone settings "0 dbm 99 asu" and just steady on there never changes.
changed the rom to cyanogenmod 13 because I just use this phone as a storage device/communication phone but would be nice to get it working, I'm sure there's a way to fix this.
I'm using Wind Mobile.
Please comment and tell me what suggestions you have below.
Thanks.
-Trippz
Has the phone always been like this? Is the imei correctly displayed from the dialler menu? Is it possible that the imei has been blacklisted? You have the d820?
Maybe it is a hardware issue..
There are two wires that run along the edges with a connection point at each end, maybe check those? Also, the daughterboard contains an antenna also. I am just throwing out ideas.. I would attach relevant photos but XDA isn't letting me yet.
audit13 said:
Has the phone always been like this? Is the imei correctly displayed from the dialler menu? Is it possible that the imei has been blacklisted? You have the d820?
Click to expand...
Click to collapse
IMEI is displayed whenever I turn it on, I bought the phone like this with a cracked screen still had the same problem, I changed the screen nothing happened... maybe happened from the impact of the phone falling.
I had a spare phone and tried to change the board with the antennas located at the bottom of the phone didn't make a difference, I changed the motherboard with one that works and used the same antenna board at the bottom and it works, so it could be a hardware issue, might try re-flow in the oven/use a heat gun if I can't find anything to fix it.
LiLTrippz said:
I boot up the phone with an inserted sim card and displays "No Service", I had it on android 4.4.4 before and changed radios, did pretty much everything that I can find on the internet (did a lot of searching) this is my main sim card I use for my other phone, just paid my bill today...
went to the service menu via #*#*4636#*#* > phone settings "0 dbm 99 asu" and just steady on there never changes.
changed the rom to cyanogenmod 13 because I just use this phone as a storage device/communication phone but would be nice to get it working, I'm sure there's a way to fix this.
I'm using Wind Mobile.
Please comment and tell me what suggestions you have below.
Thanks.
-Trippz
Click to expand...
Click to collapse
Good morning brother I have one just like a similar problem Might decirmer if in service mode * # * # 4636 # * # * in mDcPowerState line = you appear in my case comes 2147483647 which apparently is a mistake , it should be number one .
I've got the same problem. Someone help?

No SIM (possible radio malfunction?)

This issue is driving me crazy.
For the past few months, every so often (semi-rarely), I would lose cell service and then the phone would say "No SIM" -- can't make calls, send SMS, etc. Then the problem would resolve itself on a reboot.
Last night, however, the "No SIM" issue happened and I couldn't resolve it on a reboot.
I've tried everything I can think of:
- Toggled airplane mode and every other easy OS setting I can think of
- Ejected and inserted the SIM card and cartridge multiple times
- Flashed a few different ROMs
- Flashed different modems/firmware multiple times
- Confirmed the IMEI is still intact
- Mucked around in the *#*#4636#*#* menu to no avail (after everything else failed)
I don't think it's a issue with the SIM card itself, as I already tried an older card I had; the problem persists. So I was wondering... is it possible the cellular radio has malfunctioned hardware-wise? Is this something that has happened to other users?
P. S. The Wi-Fi radio works fine, and I imagine Bluetooth does as well. It's just the cell radio that's problematic.
If there's a specific detail I forgot to mention, let me know and I will clarify. Thanks for reading.
FYI, I believe I fixed the problem. The solution was just maintenance/cleaning.
Pried off the back of the phone where the battery is for the first time; cleaned all the copper endpoints sticking out, as well as the antennae traces on the rear panel with alcohol. Stuck a piece of sticky paper on the back of the SIM caddie so it wouldn't move around in the slot so much.
That seems to have done it. Haven't experienced a "no SIM" message yet, but I'll post back here if it returns.

Problem dropping calls

Hey
Does anyone experience problems of phone having full signal and then dropping it.
The problem I'm experiencing is frequent dropout during calls and being unable to establish them afterwards.
I can send texts and use the internet one minute and the next the phone doesn't work and drops my calls as well as doesn't accept them.
I tried swapping SIMs, rebooting, flight mode, you name it. The phone starts working again after about five minutes.
Here is the error:
https://drive.google.com/file/d/1e6_D3RM6luCK_LWDQSmOq-gJmmxjQOd9/view?usp=sharing
I would really appreciate some help. I highly suspect that this started happening with one of the latest updates.
I'm on a vanilla 12.0.3 Global rom.
Cheers
DavidMarmon said:
Strange
Click to expand...
Click to collapse
Yup. I have it pinpointed to a software problem as the phone worked just fine until a couple of updates ago. I can't however work out what could cause it.
I'm currently trying toggling VoLTE and changing APN settings (APN had wrong settings but still worked). Maybe the combination of both could cause problem.
I have also found out that SMS and data connection works fine all the time. It's just the calling function that causes the problem. I can listen to Spotify all day and it will work but as soon as someone tries to call me the signal will drop and everything stops. When I call the same thing happens. The bars just drop to 0 and playback stops. It resumes right after and works fine as long as I don't try to call. If I do the same thing happens.
The issue resolves itself after 5-30 minutes or so and then everything works totally fine.
So yeah if I had a rooted phone I would definitely contribute this to faulty rom or a rogue app. But I don't have one so it should work fine.
I've managed to capture it on video (sorry for the shaky camera but it was hard to film using one hand):
https://www.youtube.com/watch?v=kxusuCwsiBc&t=2s
Reboots, flight mode, swapping SIM cards (using a brand new one), using a SIM in slot 1 or slot 2, heck both slots, VoLTE on or off... I have literally tried everything. Nothing changes. Placing the same card in my other phone is fine. The problem happens everywhere and not only in one place so it's not reception. Also it doesn't matter if I'm moving or not so it's not switching between towers.
Same prob
I have the same prob, and I also tried every thing even flashing lineage didn't help, did u manage to find solution????
fautsoops said:
I have the same prob, and I also tried every thing even flashing lineage didn't help, did u manage to find solution????
Click to expand...
Click to collapse
Sort off. I had to send it to a service center and they've returned my money as it was deemed irreparable.

Categories

Resources