Related
Today my phone has been switching from no signal to signal
and now it refuses to get any signal
i have tried changing the radio
reflashed stock rom
then reflashed a modded rom
and each one has the same result ...
any other ideas what could be wrong?
i get signal if i put the sim in another phone
so its definately phone related
make sure the radio matches the rilphone.dll?
yep
same .dll from the radio package
have a feeling its some internal problem
cuz the sim is fine otherwise
grr
What about Edge?
I had a LOT of frustrations with mine a couple of weeks ago, then, just to play a hunch, I disabled 3G, and went back to edge and it worked perfectly. Sent an email to the deathstar, and they sent back saying they were having 3G problems. Reading over on boygeniusreport.com, a LOT of people are having trouble with 3G. At&t doesn't have the bandwith to support all the apple iPhone fanboys I guess.
Probably not what's causing your issue, but might be worth a try...save you from pulling your hair out.
Vish112 said:
Today my phone has been switching from no signal to signal
and now it refuses to get any signal
i have tried changing the radio
reflashed stock rom
then reflashed a modded rom
and each one has the same result ...
any other ideas what could be wrong?
i get signal if i put the sim in another phone
so its definately phone related
Click to expand...
Click to collapse
First Take your Phone out of the Faraday Cage.
p51d007 said:
I had a LOT of frustrations with mine a couple of weeks ago, then, just to play a hunch, I disabled 3G, and went back to edge and it worked perfectly. Sent an email to the deathstar, and they sent back saying they were having 3G problems. Reading over on boygeniusreport.com, a LOT of people are having trouble with 3G. At&t doesn't have the bandwith to support all the apple iPhone fanboys I guess.
Probably not what's causing your issue, but might be worth a try...save you from pulling your hair out.
Click to expand...
Click to collapse
If this doesn't help, disabling 3G, you may have to do a warranty exchange.
left battery out all night (last night)
then i reconneced it this morning
and everything seems to working fine
must have been some internal static
thanks dudes
Hello,
I'm at a point where I don't know what else to do. My signal is dropping and or changing from H to H+ to 3G to no connection constantly. I'm supposed to be on LTE. Everything had been working fine until this morning.
Here is what I've done to try and fix the problem:
- re-flashed ROM (Liquid Smooth, Paranoid Android, etc) Same results. And when I say I re-flashed I mean I started from scratch, cleared everything, etc.
- flashed different modems (3)
- went back to stock
- went to AT&T and tried a new SIM card
- pulled battery, pulled SIM, etc
Everything leads back to the same performance which is that my signal is not stable. I'm in NYC so I know my signal should be stable. It has been every day until today. And of course I did speak with ATT when I was there today and they said that there are no issues. I know they're right because every phone in there was getting LTE.
So now I'm thinking it's a physical problem with the phone?
Any advice is welcome. Thanks in advance.
-Tony
tonyfiore75 said:
Hello,
I'm at a point where I don't know what else to do. My signal is dropping and or changing from H to H+ to 3G to no connection constantly. I'm supposed to be on LTE. Everything had been working fine until this morning.
Here is what I've done to try and fix the problem:
- re-flashed ROM (Liquid Smooth, Paranoid Android, etc) Same results. And when I say I re-flashed I mean I started from scratch, cleared everything, etc.
- flashed different modems (3)
- went back to stock
- went to AT&T and tried a new SIM card
- pulled battery, pulled SIM, etc
Everything leads back to the same performance which is that my signal is not stable. I'm in NYC so I know my signal should be stable. It has been every day until today. And of course I did speak with ATT when I was there today and they said that there are no issues. I know they're right because every phone in there was getting LTE.
So now I'm thinking it's a physical problem with the phone?
Any advice is welcome. Thanks in advance.
-Tony
Click to expand...
Click to collapse
Hey tony i know the isues you having but one thing you have to understand is that Network carriers Label the 4G logos"4g" although you maybe in a Hspa/Hspa+ location(which is more of a 3g+) lol
as for the data connection drop this has been an issue with JB for awhile where the apns wont stick either on boot or time out etc.....
best bet to know if its your phone or not is to revert to stock and test it if stock keeps the data connection then you know the phone is fine if it doesnt then its just apart of JB issues more then half of JB runners run into this issue.
He did go back to stock...
If the issue is still happening on stock, I'd say have AT&T replace the phone.
Sent from my Slim Bean Skyrocket
Quando Omni Flunkus Moritati
Thanks for the replies.
Yes, at this point I've done everything I could think of with regard to trying different scenarios. I'm definitely leaning towards the fact that perhaps the phone itself is on the fritz. Unfortunately the phone is out of warranty so I can't just have it replaced. I'm not due for an upgrade until June. And I don't have insurance on the phone. That sort of limits my options. AT&T did credit me $100 for my troubles, which is better than nothing. For an early upgrade I'd have to pay like $250, I believe (minus the $100 credit) in addition to renewing my contract with AT&T. Just thought I'd give you guys the breakdown.
Also, I want to reiterate the fact that I am in midtown Manhattan (NYC) where the signal is always full bars of LTE service. It's been consistent for months. This started yesterday (the signal drops) and has been inconsistent ever since. Obviously I've polled other AT&T users around me and they are not having any connection issues. And yes, I'v e gone back to stock more than once. The signal definitely comes and goes constantly. It's not just what the meter says on top of the screen. I use an application to see what mobile network I'm connected to and I'm getting the same inconsistencies looking there as I do when I look up at the signal meter in the status bar.
I had this happen too. Turned out my phone was broke.
I've got best buy's warranty and they replaced the phone. Sorry I'm not more help, but the fact that the phone just doesn't get a signal is a possibility. And I just wanted to let you know, you're not alone
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hey everybody:
This is kind of a last gasp for me. My HTC One S suffers from the usual that you read about - "Preparing SIM" messages, constant error reports on bootup, random reboots. I honestly hate the phone.
So I installed a custom ROM. I unlocked the bootloader via HTCDEV, then I used the 12/20/13 CM11 (KitKat 4.4.2) with the 12/15 GAPPS.
The phone worked OK except now I was able to see what I've read about, and probably unknowingly experienced with the stock ROM, and that is the phone constantly flipping between Edge, 2g, HSPA, HSPA+, etc.
So, I decided to try a new radio. Did it a million times on my old G2. In order to get S-OFF to update it, I used the RLL to bring it back to stock Jelly Bean, then Moonshine to set S-OFF, SuperCID'd, and restored it with CWM. Then I installed the 1.20.x radio and at that point, all heck breaks lose with the data network connectivity and even cell signal. I might have no cell or data signal. I might have a cell signal with Edge. If I get up and move, it might go to HSPA, then I might lose everything again. This is much more pronounced than what I witnessed when I first installed the CM11 ROM.
I've tried reflashing the original 1.13 radio and it's no better. I went back to the 1.20 radio and even wiped and reflashed CM11 and GAPPS from scratch. Still very inconsistent data connectivity, so I'm not necessarily convinced it's the version of the radio because they're both pretty darned bad including the original version.
Has anybody been through this and gotten it straightened out? This is strange that even going back to the old 1.13 radio doesn't seem to help.
Thanks for any ideas...
Type: HTC One S, S4, S-OFF, SUPERCID
HBOOT: 2.15.4444 (Moonshined)
Image: CM11 (12/20/13 - 4.4.2)
Radio: 1.20.50.05.16_10.31.50.08L
Who is your carrier? If it is TMOUS you will probably need to make some adjustments to your /system/build.prop file. When I flash a new ROM I have to make the following additions/changes before my data connectivity is stable:
Code:
pm.sleep_mode=1
ro.ril.hsdpa.category = 24
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 4
ro.ril.radio.svn=19
ro.ril.fast.dormancy.rule = 0
The setting "ro.ril.fast.dormancy.rule=1" probably already exists in the file, so it will either need to be edited or removed. The other settings should not exist.
The changes that actually allow the phone to maintain a data connection (as I recall) are "ro.ril.radio.svn=19" and "ro.ril.fast.dormancy.rule = 0". "pm.sleep_mode=1" allows the CPU to completely power off, and the "ro.ril.h*" settings set max speeds for different data connections. I'm going off of what I've culled from various posts and forums, so I may be off the mark on some of my descriptions.
Here's one post briefly talking about these settings:
http://forum.xda-developers.com/showthread.php?p=48276115#post48276115
You will need root access and your /system partition will need to be remounted as read-write to make the changes. Ask or search if you need help with those. Of course if you're not on TMOUS, then I have no idea...
Yes, T-Mobile US is my carrier. There's another thing I found. If it go into the phone's testing facility (*#*#4636*#*#), I notice that it's set to WCDMA preferred. If I set it to WCDMA Only and give it a few, it does go to an HSPA/HSPA+ connection. However, that setting appears to be lost between restarts.
What I don't get is that when I first flashed the CM11 ROM, I at least had the intermittent E/2g/3g/HSPA connections. How, if I go into that testing facility, it is stuck on Edge (and more consistent since my last flash). I will read the thread you provided a URL to. Thanks very much!
benyto said:
Who is your carrier? If it is TMOUS you will probably need to make some adjustments to your /system/build.prop file. When I flash a new ROM I have to make the following additions/changes before my data connectivity is stable:
Code:
pm.sleep_mode=1
ro.ril.hsdpa.category = 24
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 4
ro.ril.radio.svn=19
ro.ril.fast.dormancy.rule = 0
The setting "ro.ril.fast.dormancy.rule=1" probably already exists in the file, so it will either need to be edited or removed. The other settings should not exist.
The changes that actually allow the phone to maintain a data connection (as I recall) are "ro.ril.radio.svn=19" and "ro.ril.fast.dormancy.rule = 0". "pm.sleep_mode=1" allows the CPU to completely power off, and the "ro.ril.h*" settings set max speeds for different data connections. I'm going off of what I've culled from various posts and forums, so I may be off the mark on some of my descriptions.
Here's one post briefly talking about these settings:
http://forum.xda-developers.com/showthread.php?p=48276115#post48276115
You will need root access and your /system partition will need to be remounted as read-write to make the changes. Ask or search if you need help with those. Of course if you're not on TMOUS, then I have no idea...
Click to expand...
Click to collapse
OK, I did these build.prop edits. Unfortunately, they've gotten me nothing. Then I went and investigated them a bit more and tried two other minor changes to build.prop (one of your parameters and added another). I'm still stuck on the Edge network. If you do a lookup, you'll see plenty of others. I think this phone is pretty much worthless - as it's been from day one. It will be my last HTC phone. By contrast, my old G1 and G2 are still working. There are tons of reports about One S phones suffering serious issues like this.
I appreciate your help and certainly, if anybody has a eureka moment, I'd love to hear about it. For the time being, I'll most likely see about getting my old G2 reactivated. Others have reported that the only way they've gotten this fixed is sending it back to HTC under warranty. Mine is out of warranty, which is the only reason I decided I'd do it. It was such a bad phone, I had nothing to lose. The next one I buy will most likely be the Moto X.
Thanks again for the help. I absolutely appreciate it.
whealton said:
Yes, T-Mobile US is my carrier. There's another thing I found. If I go into the phone's testing facility (*#*#4636#*#*), I notice that it's set to WCDMA preferred. If I set it to WCDMA Only and give it a few, it does go to an HSPA/HSPA+ connection. However, that setting appears to be lost between restarts.
What I don't get is that when I first flashed the CM11 ROM, I at least had the intermittent E/2g/3g/HSPA connections. How, if I go into that testing facility, it is stuck on Edge (and more consistent since my last flash). I will read the thread you provided a URL to. Thanks very much!
Click to expand...
Click to collapse
Sorry I can't be of more help. I'm still fairly new to this phone, but I quite like it. I suppose I've been more fortunate than others in that I haven't had any real problems with it.
It's not a problem and I'm grateful for you trying. The information you provided was also interesting from a learning perspective.
I reran the RUU on it, just to see if it would make any difference. This made it so I USUALLY have 2g connectivity, but that's as far as it goes and it's not good enough. I have lost that at times, but for the main part, it's consistent with 2g.
T-Mobile is sending me a new SIM to get my old G2 reactivated. While it's only about a quarter of the One S speed, it'll suffice. Unfortunately, the SIM it had couldn't be used because too much time had elapsed since the phones last use. That should be here Monday and that particular phone was WAY more tolerant of different images and radios (knock on wood!). It's currently running a Jelly Belly image of Android 4.2.2 (if I remember), so this should be interesting.
As for my HTC One S, I'll most likely give it to my son to use for games and media. With nothing more than 2g speeds, it's worthless to me. This phone has been a complete and utter piece of garbage since the day I got it. It's funny that my excellent experience with the T-Mobile G1 and G2 by HTC was my reason for buying the One S over a Samsung model. Now that phone is the reason I won't be getting another HTC. Strange how that works.
Again, thanks VERY much for the help!
benyto said:
Sorry I can't be of more help. I'm still fairly new to this phone, but I quite like it. I suppose I've been more fortunate than others in that I haven't had any real problems with it.
Click to expand...
Click to collapse
Weird, I had a desire z (same phone as g2) and it had really bad reception while holding it. Would lose all signal in the house. All my other phones used have been fine and pretty well equal - nexus one, desire hd, one s, my girlfriend's iPhone are all about the same.
This summer at a cottage my sister gs3 had no service all week, same network and the one s and iPhone
4s both could squeak some signal if you didn't touch them. A slight edge going to the iPhone most of the time I think.
Probably either a radio issue with that phone on your provider or defective hardware?
Sent from my HTC One S using xda app-developers app
It's not the provider (T-Mobile). My wife's Samsung has 4g here in the house - no issues. I took the One S out and had 2g everywhere. It's the phone.
I'm also guessing it's most likely the radio, as in a bad chip. Once you try to burn a new firmware into it, it finishes it off. Don't get me wrong, I'm certainly no engineer. It may or may not be that, or may be WAY more involved. Some people said the only way they got it fixed was by HTC replacing the main board.
The phone was a POS even before installing a custom ROM. Random reboots, constant startups with messages asking if I wanted to report the errors to HTC, random instances of NO data connectivity and then a message saying the phone is "Preparing the SIM card". I finally realize now that the occasional drops I would get while working remotely in Mexico (using a Movistar SIM) were most likely a result of this thing losing it's data connectivity while "Preparing the SIM card." The issues with this phone and the fact that it was out of warranty were the only reasons I took a chance on installing a custom ROM.
I'm sorry that I most likely sound like I'm ranting. However, I've searched all over and found SO MANY issues with this phone, that there's no way they should NOT have been recalled. Even T-Mobile told me there were many reported issues with these things. Both companies failed their customers.
350Rocket said:
Weird, I had a desire z (same phone as g2) and it had really bad reception while holding it. Would lose all signal in the house. All my other phones used have been fine and pretty well equal - nexus one, desire hd, one s, my girlfriend's iPhone are all about the same.
This summer at a cottage my sister gs3 had no service all week, same network and the one s and iPhone
4s both could squeak some signal if you didn't touch them. A slight edge going to the iPhone most of the time I think.
Probably either a radio issue with that phone on your provider or defective hardware?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Here in Canada we don't even have 2g on Telus, Bell, virgin mobile and koodo (I am on Telus), so the several phones that seem to have network problems on 2g or switching back And forth only have those issues on Rogers/fido or the small carriers like wind.
A guy I knew from highschool years ago works at fido and I remember him telling me last year this phone had some reception issues.
When telus had this phone on their website still they had pretty well all 5 star reviews. So my phone would probably be a piece of **** on a 2g/3g network too luckily they work perfectly on hspa only.
Sent from my HTC One S using xda app-developers app
Interesting. It's nice to have the option in the case of there ONLY being Edge/2g/3g service available, but not to be stuck on it when HSPA is there.
350Rocket said:
Here in Canada we don't even have 2g on Telus, Bell, virgin mobile and koodo (I am on Telus), so the several phones that seem to have network problems on 2g or switching back And forth only have those issues on Rogers/fido or the small carriers like wind.
A guy I knew from highschool years ago works at fido and I remember him telling me last year this phone had some reception issues.
When telus had this phone on their website still they had pretty well all 5 star reviews. So my phone would probably be a piece of **** on a 2g/3g network too luckily they work perfectly on hspa only.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
True, at least around here though the amount of area without service for Telus/bell or Rogers seems to be pretty equal. So I'm happy not to have the issues with switching between 2g, 3g and LTE. It's hspa or hspa I guess.
Sent from my HTC One S using xda app-developers app
I've started having some horrible issues with my phone connecting to Verizon networks properly. I used to be able to connect to 4G networks at my house and surrounding area with no issue, but now I've been having the worst time getting it to lock. Currently I'm connected to 3G at -99dBm in my household.
I originally was running stock, but fully rooted, S-Off. I've since switched to trying AOKP and now I've settled on Sinless GPe 3.4.7. I have not seen any real difference between them as far as getting a good connection to the network. I started switching ROMs well after I've noticed an issue, and I have not done much of anything to my phone in the last few weeks that I could attribute to the change. I've never dropped the phone or damaged it in any way.
I just recently traveled across the state and would run speedtests next to my wife's iPhone 5c and 19/20 times she'd show full bars with LTE service while I was either on 3G or no service at all. My phone will connect to 4G sometimes though, it's just not that often.
I read that there may be an issue with my SIM card, so I stopped in and had it replaced. The guy seemed very confused about the state of my phone software, so he blamed any issue I was having on the software installed. Regardless I did get a new SIM card installed. It did not seem to help at all. Can anybody help me? I'd hope to not have to go through the hassle of attempting to get the phone replaced!
Bootloader information:
HBoot-3.16.0.0000
Radio-0.89.20.0321
After rebooting my phone, my phone locked to an LTE signal at -112dBm. It does not speed test at over 3Mbps. Testing my wife's iPhone shows her at -100dBm and she was able to pull 30Mbps down.
There is talk of poor signal reception/speed in gpe threads. Cm based Roms, dunno. Try flashing a sense ROM, do some tests and report back
I recommend clean ROM or any other ROM on Verizon base
I just received my M8 yesterday and am having the same issues (both wifi and LTE) running the latest PA. Going to try something with a VZW base and report back.
wtoj34 said:
There is talk of poor signal reception/speed in gpe threads. Cm based Roms, dunno. Try flashing a sense ROM, do some tests and report back
I recommend clean ROM or any other ROM on Verizon base
Click to expand...
Click to collapse
I reloaded my backup of the Stock ROM and I am still seeing the same issues. It seems to connect sometimes but most of the time it will not. It seems like its just not getting a good lock. I am having trouble even using the phone at my house now whereas I've always had great service here. Doing a speed test now, the phone states 3G service, tested with 705 ping, download of 0.17, upload shot up to 58.19 (which obviously isn't true) and then froze while testing and has been here for over three minutes.
serotoninzero said:
I reloaded my backup of the Stock ROM and I am still seeing the same issues. It seems to connect sometimes but most of the time it will not. It seems like its just not getting a good lock. I am having trouble even using the phone at my house now whereas I've always had great service here. Doing a speed test now, the phone states 3G service, tested with 705 ping, download of 0.17, upload shot up to 58.19 (which obviously isn't true) and then froze while testing and has been here for over three minutes.
Click to expand...
Click to collapse
I would run the RUU and try again, and just see if something got boogered
Confirming as well that the reception isn't the greatest with this phone/radio in the so so service areas.
I live out in the country. Never had good reception with Sprint no matter the phone. Switched to Verizon with an LG G2 and service was fantastic at home for the 7 months I owned it. I moved to the M8 and now phone service is spotty at my house. It's the radio for sure. Wifes verizon moto works great at home as well.
I've had the same issue, updated radios, flash back to stock, and everything else. The radio on this phone IMO is terrible, even when it does get 4G I get like 8 mbps down with 4 bars of 4g. Once in a great while i'll get 18 - 20 down with 5 bars of 4g.
I've been experiencing the same things recently as well. It also affects sending SMS messages. I am on stock too (with s-off). Nothing changed on my phone though, it just started dying.
Never had signal issues. I live out in the boonies too. Signal is strong and switching between 3g and 4g has been smooth. I've been able to download torrents as fast as 5mb/s. Speed test results have been just awesome. As far as signal goes, it's been better than my note 3, DNA, and my wife's droid mini. And this is my second m8. My son has the first and it is the same as mine.
I would look into exchanging them if they don't keep up with other phones. The radio in this phone is actually pretty damn sweet, so if u got a funky one, I'd exchange it. Def try the ruu first, then exchange if that doesn't help.
Sent from my HTC6525LVW using Tapatalk
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
RoyJ said:
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
Click to expand...
Click to collapse
Sorry forget to mention I knew that was normal for the drop to H+, but yes the signal drop is not. Well it started out of the blue. IS there a thread on here with what should be the correct APN settings? Also my old nexus 5 started to do this before I returned it under warranty for refurbished, then I had a moto G lte for a month worked fine, got a refurbished (due to warranty) and started again.
Here is a graph of my network coverage to show that the signal just drops.
Sent from my Nexus 7 using XDA Free mobile app
same problem
jgr208 said:
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Click to expand...
Click to collapse
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
raptir said:
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Click to expand...
Click to collapse
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
cell radio fix
jgr208 said:
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
Click to expand...
Click to collapse
I found it here (just take away the spaces after .com and after 02/): ianmarmour.com /2014/02/02/ google-nexus-5-fixing-modemcellular-issues-on-34g-networks
It's an older post from February, but seems to have the best details and fixes. If you simply search nexus 5 cellular radio issues or nexus 5 4.4.4 call drops, you should find a lot of these recalls from lots of N5 users. I'm tempted to try it, but don't really feel like sorting all my files in case i brick my device. I'm also not sure if ota update will work if i tinker with cell radios. Otherwise that's the page containing all the details you'd need including links and step by step guides. And hey if it works for you, let me know, maybe I'll try it out if it goes well for you.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
Exactly, i know that's totally possible, but i wouldn't want a smartphone that has no lte and/or hspa+ service at this point in time. This seems to happen wherever lte isn't as strong or available but hspa+ is. I think the modem responsible for switching between lte and hspa+ causes calls to drop. I took note of it a couple hours ago when i attempted to make a few phone calls resulting in instant call drops. Seems to do it while switching from lte to hspa+ network. I just wish Google would stop burying their heads from the outside world like an ostrich, and get in top of this. I mean this is their flagship device until N6 goes on sale. They should seriously fix this issue or at least stop denying that they've never heard of any complaints with their N4 and N5 customers. I love this device, but a simple fix like this not being addressed by Google is not very professional, especially because it's primary function is to call people. I'm really tempted to flash those radios, but really want to see if Google addresses this issue with an official ota lollipop update.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Factor resetting it won't help, I've tried it already.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
simms22 said:
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
Click to expand...
Click to collapse
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
simms22 said:
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
Click to expand...
Click to collapse
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
anactoraaron said:
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
Click to expand...
Click to collapse
Def wasn't gonna try hardware and only software and great to hear! Did you try out lollipop yet?
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
simms22 said:
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
Click to expand...
Click to collapse
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
well, try the lollipop preview, it was working for the other guy, see if itll work for you. if it does, great.