Database Info

[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.

Interesting findings on the newest OTA (MD3)

I read about all of the issues people are having with the newest OTA (MD3). I decided to give it a try anyway, because I love writing emails to Verizon pointing out their flaws.
I followed the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1762709 to go back to stock, using the Official VRALG1 4.0.4 Firmware. I wiped the Data and Cache partitions after installing. After this, I applied each patch in succession BEFORE installing any other software or programs. When I was done, I immediately disabled the Caller Name ID app. I have NONE of the reported bugs:
* Texts send immediately on the first try
* Battery life is no different than it was on the last firmware
* Phone switches easily between Wifi, 3G, and 4G LTE
* 4G LTE speeds are normal
I am no stranger to unlocking, flashing ROMS and Radios, etc, but I am most certainly NOT a dev. I'm posting this information here so that someone with more knowledge than I may be able to glean some information useful to those that ARE having a problem from this post.

I was having issues with the ota and I went back to the oldest update then took the otas.
Then rerooted mb1 and flashed bonestock 2.0 with the mb3 radio/modem....still had signal issues. And that rom has all bloat removed. So I flashed the mb1 radio/modem and now I get better signal.
Ha thats my story.....definitely a mess up from Big Red.
Sent from my SCH-I535 using xda app-developers app

I wiped and then installed the stock deodexed MD3 ROM and firmware and had data issues...low signal, frequent drops to 3g or 1x, etc. Ran it for a few days and it was noticeable wherever I went. Restored my CleanROM nandroid and flashed the MB1 firmware and my signal has been much more consistent again.

I was weary of the rumored issues so I completely wiped my internal storage for a fresh install, and MD3 has been nothing short of amazing for my phone. If anything the only knock on it is that the signal has degraded about a bar in areas where I'd normally have full bars. Data connectivity is fine, data speeds are fine, the kernel with this update deep sleeps better than most that I've flashed in the past month. It's been nothing but good so far
Sent from my SCH-I535 using Tapatalk 2

cvsolidx17 said:
I was weary of the rumored issues so I completely wiped my internal storage for a fresh install, and MD3 has been nothing short of amazing for my phone. If anything the only knock on it is that the signal has degraded about a bar in areas where I'd normally have full bars. Data connectivity is fine, data speeds are fine, the kernel with this update deep sleeps better than most that I've flashed in the past month. It's been nothing but good so far
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
For a device that already had bad radios for low signal areas, the reception issue is bad. It is not like going from great radios to good radios, but going from barely okay radios overall to worse. Everything is relative and the radio changes absolutely suck in that regard.

rushless said:
For a device that already had bad radios for low signal areas, the reception issue is bad. It is not like going from great radios to good radios, but going from barely okay radios overall to worse. Everything is relative and the radio changes absolutely suck in that regard.
Click to expand...
Click to collapse
I"d say this thread is now dead since Samsung / Verizon have now pulled the OTA and will release a fixed version later, That usually means 1 day for Samsung to fix it, and 3 months for Verizon to test and approve the release.
In comparing the S3 to two other Verizon Motorola phones in my family, I find the S3 signal to be as good or better to the Motos when running the current stock software, (not the broken MD3 OTA) . SO I'd say its pretty good as Verizon goes. Interestingly, I find that the Verizon S3 is not nearly as good in signal as my wife's Sprint S3 , Surprising because VErizon and Sprint often share cell towers.

rushless said:
For a device that already had bad radios for low signal areas, the reception issue is bad. It is not like going from great radios to good radios, but going from barely okay radios overall to worse. Everything is relative and the radio changes absolutely suck in that regard.
Click to expand...
Click to collapse
This is exactly the thing. After using MB3 update a whole week, giving it a chance....my phone would still WORK in areas with strong signal, but everywhere else it went from ok to UN-usable!
There is a clear issue here but if you are in areas with only great signal you may not notice as much but it's there.

DigitalMD said:
I"d say this thread is now dead since Samsung / Verizon have now pulled the OTA and will release a fixed version later, That usually means 1 day for Samsung to fix it, and 3 months for Verizon to test and approve the release.
In comparing the S3 to two other Verizon Motorola phones in my family, I find the S3 signal to be as good or better to the Motos when running the current stock software, (not the broken MD3 OTA) . SO I'd say its pretty good as Verizon goes. Interestingly, I find that the Verizon S3 is not nearly as good in signal as my wife's Sprint S3 , Surprising because VErizon and Sprint often share cell towers.
Click to expand...
Click to collapse
What they should do is release here first. There are no better beta testers then XDA members and we could probably find every flaw within a day, and heck our devs can probably fix most of them for Samsung anyway.

[email protected] said:
What they should do is release here first. There are no better beta testers then XDA members and we could probably find every flaw within a day, and heck our devs can probably fix most of them for Samsung anyway.
Click to expand...
Click to collapse
Samsung usually releases a test release on KIES for their own stuff, but Verizon of course won;t let them do that for Verizon phones because Verizon has their own professional way of doing things....hahahaha

Signal drops since 4.2.2

Hi everyone.
I owned a Nexus 5 one month ago, but unfortunately, it does not work as expected. On 4.4.0, I had multiple issues concerning network already (unable to switch to 3G networks only, very variable HSPA signal reception (from 4/4 bars to Edge exactly at the same place), ...). This issues were supposed to be fixed with 4.4.2 and most of them are, excepting HSPA signal which is still very weird. However 4.2.2 brings my phone another issue that I didn't noticed on 4.4.0 which is a very annoying and repetitive complete signal blackout (no reception at all (Edge/HSPA), even for emergency calls I guess). Signal drop can happen twice in an hour, twice in 10 minutes or may not happen at all 3-4-5 hours long. It's completely unpredictable. After a while, Edge signal (not HSPA !!) gets back by itself. If I wait 10-20 more minutes, HSPA comes back again, until it drops again.
Moreover, at phone boot, just after typing my PIN Code, it usually takes 2 or 3 minutes to catch a signal. Very slow isn't it ?
It does not seem to be a network issue, since my Samsung Galaxy S III doesn't encounter this using the same SIM card.
I read on Google forums and probably some XDA threads that I was not the only one to face this kind of network issues, even on 4.4.2, but issue description was each time a bit different from mine, thus I tought that it may be useful to post a new thread to describe precisely what was my problem.
Edit : My Nexus 5 is unlocked and rooted, but issue is present on untouched 4.2.2 also.
Edit 2 : http://forum.xda-developers.com/showthread.php?t=2525583 is probably my issue.
Do no hesitate to answer if you're thinking that you have the same issue (or kind of) or if you think that you know something that may help.
Thank you .
KennyG9

You can flash the radio from version 4.4 that helps a lot, I'm at work just search this forum the directions are here, it's easy.
Sent from my Nexus 7 using Tapatalk 4

^^ He appears to be talking about the link below. You can flash different modems that may work. Some people say different modems helped but I've had no such luck. I've flashed every modem available and still don't have data almost everywhere I go. I have data at home but that doesn't really matter since I don't need my phone at home.
http://forum.xda-developers.com/showthread.php?t=2514095

Did you try flashing your carrier's specific radio?
Team Nexus 5 sucks

dicecuber said:
Did you try flashing your carrier's specific radio?
Team Nexus 5 sucks
Click to expand...
Click to collapse
Were would one find the carrier specific radio? I'm on T-Mobile but have only found the thread with modems. Nothing carrier specific.

Thanks for your answers. Unfortunately, flashing different modems does not seem to help .

i've read, the .15 is good with t-mobile.
i'm testing it today too. my problem is not only a signal drop, i have only edge too and my modem won't switch back to umts or hspa(+).
i'm in germany with t-mobile (congstar).

Sprint Users: How's The 4.4.4 Radio Working?

All the guys over at S4GRU are saying that the new 2.0.50.1.16 radio that came with the Android 4.4.4 update is holding onto LTE signals better than the .13 radio that came with 4.4.3, especially while driving and bouncing off towers left and right. I plan to go out later tonight and test it out. Has anyone done any tests yet? What kind of results are you having? Better? Worse? Discuss.

Yes with the 4.4.3 radio my LTE was dropping down to 3g at home because I have a weak signal here but it use to stay on LTE before 4.4.3.
Since flashing the 4.4.4 radio it has returned to before and staying on LTE.
Edit: I'm on T-Mobile not Sprint
Sent from my Nexus 5 using XDA Premium 4 mobile app

Nexus 5 5.1 Radio

Greetings,
First off as general context, the greatest complaint that I have had with the Nexus 5 has always been its radio and I've been a user since Nexus 5 launch. I am a Canadian user on the Rogers network, and I have found many areas that other phones (any of the iPhones, Samsung Note 2, Samsung S4, HTC One m8) receive signal on the Rogers network (at least 2 bars) while I have zero reception. Most of these areas are basement level areas or complete concrete buildings. Has anyone else encountered this problem? This is especially annoying as I tend to be in basement areas often.
Second off, I am a rooted user on Carbon ROM for 4.4.4 KitKat but running 4.4.2 radio. I've found that the 4.4.4 radio was highly unstable for me, losing signal every few minutes or so while being in areas where I receive full bars and remaining stationary. Thus I reverted to 4.4.2 radio only and it fixed my problem. Now that 5.1 build is out, I would like to update only my radio and bootloader for 5.1 as I am not ready to enter Android 5.x with the memory leak problems and other features. All i would like to try out is mainly the radio to see if it fixes my first issue. Would flashing only the radio and bootloader of 5.1 be okay? I'm not sure if there is some sort of problem with flashing radios and bootloaders of a whole different build (5.x onto a 4.x). Thanks.

xtremeryo said:
Greetings,
First off as general context, the greatest complaint that I have had with the Nexus 5 has always been its radio and I've been a user since Nexus 5 launch. I am a Canadian user on the Rogers network, and I have found many areas that other phones (any of the iPhones, Samsung Note 2, Samsung S4, HTC One m8) receive signal on the Rogers network (at least 2 bars) while I have zero reception. Most of these areas are basement level areas or complete concrete buildings. Has anyone else encountered this problem? This is especially annoying as I tend to be in basement areas often.
Second off, I am a rooted user on Carbon ROM for 4.4.4 KitKat but running 4.4.2 radio. I've found that the 4.4.4 radio was highly unstable for me, losing signal every few minutes or so while being in areas where I receive full bars and remaining stationary. Thus I reverted to 4.4.2 radio only and it fixed my problem. Now that 5.1 build is out, I would like to update only my radio and bootloader for 5.1 as I am not ready to enter Android 5.x with the memory leak problems and other features. All i would like to try out is mainly the radio to see if it fixes my first issue. Would flashing only the radio and bootloader of 5.1 be okay? I'm not sure if there is some sort of problem with flashing radios and bootloaders of a whole different build (5.x onto a 4.x). Thanks.
Click to expand...
Click to collapse
The bootloader and radio are separate from everything else on the Nexus 5, you can use any version with any version of Android.