Modem/reception issues. - ONE Q&A, Help & Troubleshooting

A few months back I updated my phone (was on stock) ever since then I am having issues with the reception in my phone (signal dropping out, going down to 3G from LTE and so on)
I unlocked the bootloader and installed TWRP, tried multiple ROMs, even tried flashing different firmwares but nothing seemd to help, I also sent my phone to a lab (when I still had warranty), they replaced the antenna but there wasn't any difference, has anyone experienced this issue before and managed to fix it?
I am currently using the latest Cyanogenmod nightly version.

Related

[Q] Help! Unable to acquire network signal. Tried everything!

Hello XDA,
I've been having problems with my Nexus S and I've tried everything I can think of to fix the problem but failed. Just wondering if someone would be able to help me.
Background:
I was using ICS Brainmaster's Koush version. I've been following the ICS builds since Drew Garen's SDK port. Then onto Kwiboos then I was flashing which ever ones I could get my hands on. Never a problem with installing on top after clearing cache. I had tried full wipes when I had problems but I installed v4-6 on top of the previous build.
The Problem:
So on the latest Brainmaster's build, one day I was low on battery so I turned on 2G networks only (not the first time I've done this on this rom) and proceeded with using it. When I was able to get a charger I tried to switch my 3G back on. At this point I could not get onto 3G anymore. Only edge. I tried toggling airplane mode, reboots, and playing around with the *#*#4636#*#* settings. Doesn't work.
So I gave up trying to fix my ICS rom and was thinking a full wipe would help. So I did a full wipe and installed the latest Brainmaster's rom (Koush ver). My memory fails me a little bit now but from what I remembered, on reboot I only had EDGE still. I tried Kwiboos ICS rom same thing. I tried Koush's b11 version same thing. I even tried a regular CM 7.1 rom and still no 3G.
At this point my phone isn't even connecting to EDGE anymore as well. I wasn't sure what was making it worse or what was fixing it. I even tried switching radios to the newest radio for i9020a and also reverted back to my stock radio for i9020a. I even tried the XX radios like the KD1 (the one I was on before all the problems) and the newest one as well.
In the "About Phone" section it shows that I don't have a network at all. When I try to search for networks I cannot see Rogers anymore but instead only one weird network 302490 (it stands for the Wind Carrier network).
I give up and hope that XDA has some ideas for me.
TL;DR
what I have tried
-Wiping does not help
-using different APNs (Rogers has two APNs)
-using different radios
-using different roms
-I even switched my sim card to my sister's NS and confirmed my 3G still works. I also tested my 3G on an Atrix and it works.
-restoring to an old nandroid didn't work
-playing around with the *#*#4636#*#* didn't help (like switching to GSM (auto) WCDMA etc, AND changing radio bands to USA)
xqz said:
Hello XDA,
I've been having problems with my Nexus S and I've tried everything I can think of to fix the problem but failed. Just wondering if someone would be able to help me.
Background:
I was using ICS Brainmaster's Koush version. I've been following the ICS builds since Drew Garen's SDK port. Then onto Kwiboos then I was flashing which ever ones I could get my hands on. Never a problem with installing on top after clearing cache. I had tried full wipes when I had problems but I installed v4-6 on top of the previous build.
The Problem:
So on the latest Brainmaster's build, one day I was low on battery so I turned on 2G networks only (not the first time I've done this on this rom) and proceeded with using it. When I was able to get a charger I tried to switch my 3G back on. At this point I could not get onto 3G anymore. Only edge. I tried toggling airplane mode, reboots, and playing around with the *#*#4636#*#* settings. Doesn't work.
So I gave up trying to fix my ICS rom and was thinking a full wipe would help. So I did a full wipe and installed the latest Brainmaster's rom (Koush ver). My memory fails me a little bit now but from what I remembered, on reboot I only had EDGE still. I tried Kwiboos ICS rom same thing. I tried Koush's b11 version same thing. I even tried a regular CM 7.1 rom and still no 3G.
At this point my phone isn't even connecting to EDGE anymore as well. I wasn't sure what was making it worse or what was fixing it. I even tried switching radios to the newest radio for i9020a and also reverted back to my stock radio for i9020a. I even tried the XX radios like the KD1 (the one I was on before all the problems) and the newest one as well.
In the "About Phone" section it shows that I don't have a network at all. When I try to search for networks I cannot see Rogers anymore but instead only one weird network 302490 (it stands for the Wind Carrier network).
I give up and hope that XDA has some ideas for me.
TL;DR
what I have tried
-using different APNs (Rogers has two APNs)
-using different radios
-using different roms
-I even switched my sim card to my sister's NS and confirmed my 3G still works. I also tested my 3G on an Atrix and it works.
-restoring to an old nandroid didn't work
-playing around with the *#*#4636#*#* didn't help (like switching to GSM (auto) WCDMA etc, AND changing radio bands to USA)
Click to expand...
Click to collapse
isnt the KD1 radio for the 9020t not the 9020a? thats my favorite radio to use with my 9020t on tmobiles network.
there is a KD1 for all versions I'm pretty sure. I was using it for the last few weeks with no problems anyways. I switched back to the ones specific for i9020a as well but it didn't help me
Edit: The radio used from this thread: http://forum.xda-developers.com/showthread.php?t=1116884
"Radio for I9020a/I9020t/I9023
Radio JK1/Radio JK8
Radio KB1
Radio KB3
Radio KD1
Radio KF1"
No one has any idea? Simms22?
If not I think I'm going to restore, lock, and try to get a warranty from Rogers..
First make sure you have setup your gmail over wifi. Pull the sim out. Keep rebooting your phone(this can take a while) until it says no sim card at the lock screen. Pull your cover and slide your sim in while its on. The put it in airplane mode and turn airplane mode off and it should connect.
You may also want to try toggling airplane mode on and off between reboots. Sometimes the airplane won't go away when you do this until you reboot, don't worry about that. I've also had better luck getting this to work while connected to Wi-Fi.
I'd also try to minimize kernel flashing after you get it working, it usually causes total network loss again when you wipe dalvik. Putting you back at square one. Also be patient this can take a while. I'd also minimize reboots as they can force total network loss as well.
Also I've already sent my phone in for this issue and Samsung rejected the claim stating there was corrosion due to water damage. But magically all of my water indicators are still white.
Sent from my Nexus S using xda premium

[Q] Little to no signal and no mobile data access

Well I'm on the latest CM nightly (CM 10.1 -20130312) and I just came from CM 10. I tried CM 10.1 before but I had little to no signal and I've decided to give the latest nightly a chance and well, I still have the same problems as before. I flashed the 3.18 radio on it and it literally made NO difference at all. I hate the AT&T variant of the phone. On the CM 10 version I didn't have this problem but there were times that I'd go half an hour to a full hour without getting any texts and then they'll all come in at once (and I know its no coincidence because some of those messages contain people wondering why I haven't replied yet). So can anyone help me with this problem please?? I really like CM 10.1 but not having any mobile data and an even worse signal is a REAL deal breaker for me.
I was having the same issue until I went into settings and changed it to GSM/WCDMA.
Sent from my HTC One X using xda premium
ItsKarriD said:
Well I'm on the latest CM nightly (CM 10.1 -20130312) and I just came from CM 10. I tried CM 10.1 before but I had little to no signal and I've decided to give the latest nightly a chance and well, I still have the same problems as before. I flashed the 3.18 radio on it and it literally made NO difference at all. I hate the AT&T variant of the phone. On the CM 10 version I didn't have this problem but there were times that I'd go half an hour to a full hour without getting any texts and then they'll all come in at once (and I know its no coincidence because some of those messages contain people wondering why I haven't replied yet). So can anyone help me with this problem please?? I really like CM 10.1 but not having any mobile data and an even worse signal is a REAL deal breaker for me.
Click to expand...
Click to collapse
I used to be tech support for att. Obvious question: has this happen before? Now to put my xda hat on. Did you change APN settings? Is this the only rom you flashes? Also call att (611) and have them cancel registration. This basically kicks you off the network and bring you back on. Sim cards are not the issue as the are unable to determine signal strength. Hope you get it fixed.
Sent from my Carbon-ize Evita using xda-developers app
I think it has something to do with the 3.18 radio. I never had problems until flashing it. I have tried multiple roms. Sense based and aosp. It happens on both although it seems to be worse on aosp. I went out of state and lost signal completely while running the latest Chameleon. I went into settings and as soon as I stopped it from searching for LTE it went to full signal. Maybe a tower upgrade issue? 3.18 radio issue? I guess it's something for devs to look into. I know not all towers are the same. 3.18 maybe conflicting with the area he is in. Somebody will get it figured out lol.
Sent from my HTC One X using xda premium
Venomtester said:
I think it has something to do with the 3.18 radio. I never had problems until flashing it. I have tried multiple roms. Sense based and aosp. It happens on both although it seems to be worse on aosp. I went out of state and lost signal completely while running the latest Chameleon. I went into settings and as soon as I stopped it from searching for LTE it went to full signal. Maybe a tower upgrade issue? 3.18 radio issue? I guess it's something for devs to look into. I know not all towers are the same. 3.18 maybe conflicting with the area he is in. Somebody will get it figured out lol.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
That's just weird. I flashed 3.18, and still get the same coverage (4-5 bars, 6mbps data). I don't see how it can effect you. The device is dual HSPA+/LTE. So if the device cannot find LTE, it will always back (circuit switch fall back). Even when I went to an LTE area (Nashville, TN), it still work perfectly. Could be something up with the physical radio inside of the phone. The LTE towers are suppose to be backwards compatible, but we know how companies can be. If your device is working in one area, and not the other, then it is a tower issue. Even though AT&T may find that their towers are ok, it is a tower issue, and there is no doubt around that. Now if it just gives you random coverage, no matter where you are, then it is the phone itself.
Having the same issue on CM. Just tried changing to WCDMA and my signal doubled. That is weird but thanks you guys.

Reverting the Radio because of signal issues?

Since getting my N5, it's been great in EVERY respect. Since 4.4.1 and 4.4.2 update (both Sideloaded rather than OTA) I have been suffering the same issue(s) as others in respect to signal and I have read that some people have flashed back the original radio from 4.4 to resolve this, whilst still on 4.4.2 OS.
The issue i am having, in spots where I leave my phone it usually obtains signal within 5 seconds and rises to 3-4 bars which is great. Since the update, if i put my phone in that exact same spot, it takes 45-60 secs to get the signal, and then it gets 3-4 bars. The signal also drops off more when I pick the phone up, its almost like the radio power has been nerfed.
Anyway, moving on ... I am currently 4.4.2 stock, un-rooted. I realise in order to flash the original radio, I do not need to be rooted, but need an unlocked bootloader.
I plan on following step 1 from this guide http://forum.xda-developers.com/showthread.php?t=2507905 in order to unlock the bootloader, and then flash the Radio (I will find the correct instructions for this)
Has anyone else done this yet or can comment on my plan? I have no intention of been fully rooted as I do like the use the latest Barclays Mobile Banking App which wont run on rooted phones but I need my signal issue sorting!
Appreciate your help

Pro/Con Updating pre-recall original LTE to marshmallow from 5.1 (Modem/Charging/ETC)

I have a pre-recall original shield tablet LTE that has not been updated to any stock rom since the recall.
I RMA'd it and never sent it in, so its likely on NVIDIA's kill-list however I havent run anything with tegraota since booting the replacement.
The newer system images have various modem and firmware adjustments I dont believe are on custom roms.
Q.
My radio is buggy on both tablets, neither have gone past early 5.1.1, do newer system images have more reliable radios/modem firmware? (LTE connection/data drops etc)
Is there a chance my RMA'd device's serial is in the newer firmware and set to kill it on boot?
Can older OTA updates downgrade the modem/etc?
Are there any other changes I should consider (besides root) before booting a newer official update?
Bootloader is only unlocked on one.
______________________________________________________________________________________
I've combed the threads on XDA/google and haven't found a direct answer to these questions and I think the ramifications of firmware updates accompanying OTA's should be clearly understood by the greater community. Thanks!
did the update on the replacement, saw a huge increase in battery life and the modem appears to work much more reliably, i havent tested speeds yet. the notegraota.zip failed to remove tegraota from /system/priv-app/ i had to do it manually via twrp. i might do some side by side benchmarks with the pyro as im a bit worried a hidden killswitch list in the new firmware killing before it can even reach the net.
ive noticed that although the modem is more reliable (less connection drops) it no longer connects to LTE, i can switch sims to my pyro tablet and it jumps right onto band 4 LTE.
No matter how many airplane mode toggles or reboots, I cant get the updated tablet to connect to any LTE band. I've even left it running over night with a script toggling airplane mode and logging any LTE connection, no dice.
Is there anyway to downgrade the modem?

Getting frequent kernal crashes the last couple of days

Wanted to see if anyone else has been experiencing the same thing.
I've got a T-Mobile variant S8+ which I switched over to Verizon, currently rooted via SamPWND and running unlocked firmware for 2 months or so now. Everything has been perfect up until 2-3 days ago when I would look down and the phone would be on a factory reset styled crash screen. It would run a series of tests and say there was a kernal error, most of the time dealing with the modem, which I would then have to restart the phone without issues and carry on.
Is there any way to test or check what the issue is all of a sudden, or a direction I should go to update to a newer firmware while still retaining root. On baseband G955U1UEU1AQG2, kernal 4.4.16 (dated Mar 26), Build NRD90M.G955U1UEU1AQG2. SW Service provider SAOMC_SM-G955U_OYN_VZW_0177, VZW/VZW/TMB.

Categories

Resources