Alright,
Phone: Nexus 5 2013
Android: 5.1.1
Country: Canada
So I've started to get a lot of issues on my Nexus 5 that I ordered back in November 2013 (when it was released) and they are too big to be left alone. If I cannot fix them, I'll have to buy a new cellphone and there's none that interest me right now, nor that I want to change my current Nexus 5.
Issues:
My Nexus 5 doesn't connect to my cellular network anymore. I'll stay on "No service" and refuse to connect to any Operator Network stating that the network is unavailable at the moment, even thought it is. Sometimes, it'll connect to the network for 15 to 30 minutes, before losing it for the next 8 hours.
It becomes hot really, really quick randomly. The upper back part of it becomes hot, and according to the Nexus 5 architecture, the battery isn't even located there so I don't know what could make it heat up like that. This happens even without it being charged, and without me using it a lot (games, apps, etc.)
The phone will randomly restart for no reason, and sometimes stay stuck on a "boot loop" (Starting apps X of Y... before restarting).
The vibrate mode is messed up. It'll vibrate every 30 seconds for a notification (email, Facebook, SMS, etc.) despite the fact that there's nothing, absolutely nothing. Right now I disabled the vibration/sound mode to avoid that issue.
The battery gets drained really, really fast. Like overnight, while not being used it'll fall from 100% to 5%. It never used to do that. When I don't use it overnight, it would lose maybe 20%, even less than that. It started recently as well.
All these issues were present in past versions of Android, starting at 4.4 so I doubt the version is in cause here, but it's still a possibility I guess.
I got my SIM card changed for a brand a new one, troubleshooted the phone with everything I could find online before giving up and restoring it to it's default settings, but the issues are still present. I don't know what I should check anymore. If you have any comments, experiences or solutions I could try to solve my issues, please let me know since at this point I'll most likely try all of them. Also, if you need more information on my phone, system, etc. let me know as well.
Thank you.
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
firemaned said:
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It used to be rooted, but it's not anymore. Any way I can make sure that it's rooted or not? When I used the SuperSU app back then I realized at some point that it wasn't rooted anymore (it was telling me that this app can only be used on rooted devices). I think the bootloader is unlocked because when I open my device, it shows me the little lock icon, but it's open (unlocked). Also, it's freshly reset to factory default (from yesterday).
dahawthorne said:
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
Click to expand...
Click to collapse
I already did a Factory Reset on my phone yesterday, so I guess I don't have to do another one? Right now, if I follow what you just told me, I should wait until the release of Android 6.0 (M) and upgrade to it then see if it solves my issues. I just hope that it won't take a long time to be pushed to my phone like it was with Android 5.0. Or your other solution is to flash the latest preview for Android 6.0 (M) on my phone and see how it goes, right?
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
dahawthorne said:
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
Click to expand...
Click to collapse
That was my original plan. I called the Play Store support this week and they told me that my phone was elligible for a replacement till April of 2016. I found that weird because it would make it a 2 years and a half guarantee but at least I had my backup plan in mind. Then I called today to order a replacement and the guy told me that my guarantee expired back in November 2014 (1 year after I bought my Nexus 5, which made sense) so now I'm stuck with this one. I don't know why, but since this morning (after creating this thread), the cellular network cameback. It still drops sometimes but only for a few seconds and if not, I enable/disable the Plane mode to make it connect again. However, the battery drain, phone heat, random restart and messed up vibration issues are still present. I can deal with them however until Android 6.0 (M) gets released. The most important thing was the cellular network. We'll see tomorrow how it goes. Still awaiting tips and tricks for my other issues if anyone have some.
For the battery draining issue, I think I have the paid version of Greenify somewhere and was thinking of using it to see if it helps, even though I didn't have that issue at the beginning.
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
CalculatedRisk said:
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
And I imagine that the factory image is still present on the device? This is what I find weird, because when I "reset" my factory to defaults, it restores it to Android 5.1.1 even though the device came with 4.x. I come from the computer field, and a Factory Reset on a computer uses the manufacturer's image present on the CD, DVD, USB or partition given with the computer to reinstall the original OS that was present on it and the OEM software as well. If the computer was eventually upgraded to Windows 8.1 and came with Windows 7, Windows 7 will be restored, not Windows 8.1. So I can understand now that a "Factory Reset" doesn't really return the device to its factory state, right?
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
dahawthorne said:
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
Click to expand...
Click to collapse
I did have an OTA update to 5.1.1, yes.
And I talked to one of my friend who's really into phones (used to work for Bell and he's usually the person I go to whenever I have issues with my cellphone), and he suggested me to wait until Android 6.0 comes out, and then to fastboot it on my Nexus 5 since OTA updates can be buggy sometimes. I could actually fastboot the phone right now (well tonight) with Android 5.1.1, but if Android 6.0 is to come out next week (or the one after), it might worth the wait, depending on whether or not I can keep the cellular network working. Otherwise I would have to go through 2 flashboots in 2 weeks and I can't really be bothered to do that
And I don't know where the CPU is in the Nexus 5 (I could look it up) but the zone where the heat is isn't where the battery is so there's that. However, my friend told me that the fact that my cellular network isn't working could explain why the battery is being drained so fast, but can't explain the vibrate mode and random restarts issues.
I was having battery issues on Stock ROM, but now I am using CM12.1 so battery is not draining very fast.
When I am inside my home or in some other house or building, the network disconnects very often. However, if I am outside, the network works pretty well.
The notification LED, when being configured using CM12.1 settings, shows blue color on green color selection and green color on blue color selection.
I had some of the same problems with my phone, it would reboot randomly throughout the day. With mine if I charged it overnight with it off when I turned it on in the morning it would only be at 85%. I ended up contacting LG and I paid $170 to get it fixed, they have replaced the mainboard twice so far. After the second time it had no issues, and that lasted a couple months but I have sent it back again to be fixed. If you bought the phone on a credit card they usually extend the warranty by a year, that's what I did, filed a claim and they sent a cheque for the repair cost, very simple actually. But I suspect it might be the same problem as mine, some hardware issue, especially if you've reset the phone.
Just for info, the CPU is indeed at the top rear of the phone, so this is undoubtedly where the heat is coming from.
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016 - see step 11 saying "The Quad-core, 2.26 GHz Snapdragon 800 SoC is layered beneath the RAM".
I reckon it's a rogue app, which I hope isn't a system app, running wild - a system app will be hard to cure.
A ROM refresh is probably a good place to start, and if you can wait for Android 6.0 then why settle for less...
Wiped my os on nexus 5 trying to install nethunter only comes on in twrp. very new to this be easy on me ive previously installed a vm lab with kali linux.
I have downloaded adb and fastboot
Using winace . Before this my pc would not recognize my device, "no drivers". But now it shows up on the pc control panel as active and found
However snap pea still cant find drivers although now it says are you fornatting your phone with only one option "yes" then it just dissappear. ... but before I downloaded adb, fast boot ... snap pea was simply saying no drivers found.... Please help. ..thank you.
Sent from my GT-I8190 using XDA Free mobile app
Here's an update on my situation: the cellular network is back at both my house and my workplace. The way it works, it seems that it takes it a day to "adapt" itself to the location and then gives me network. So at first after the Factory Reset, I didn't have network at my house, the day after I did. Now, when I went to work on Monday I didn't have network, but when I did on Tuesday, I did. My job is an hour of road away too, and at some places on the road I don't get any network, but it happens less and less as I travel back and forth.
The random restart and overheating issue are still present however. I didn't test the notifications (on vibrate) but I will soon. As long as I have my cellular network, I don't care about the other issues, until Android 6.0 (M) gets released and I fastboot it on my phone.
Now, since I bought my Nexus 5 using a MasterCard, I remembered that they have a promotion which double the guarantee on electronics (up to a 1 year), which means that I have a 2 years guarantee on my phone. So I called LG, and they have a promotion right now, $150 to get my phone repaired by their tech center IF it can be repaired. If they can't, they send it back and gives me a 50% refund (around that number).
My current plan of action is to wait for Android 6.0 (M) to get released, flashboot it on my phone and see how it goes from there.
Thank you for all the replies so far, they really helped me and still help me today
Good luck man. Keep us updated.
Sent from my Nexus 4 using XDA Free mobile app
Alright so, I fastbooted Android 6.0 on my Nexus 5, and it seems to have done the trick. I have network everywhere now, even on the road. I still lose it from times to times (a few seconds only), but this is a "normal" behavior considering the carrier I have. The notification issue is also gone, and so does the restart issue since I didn't have it once so far. But I only fastbooted it yesterday evening so it might be too soon to say that.
Now, I still have the "overheating" issue, but it could be from me playing Fallout Shelter, I really don't know. I used to play Clash of Clans alot, and graphically speaking, I think it's more demanding than FS, but I never had that overheating effect before. One thing I noticed however is that after fastbooting Android 6.0, my battery drops real fast, even when idle. I thought that Android 6.0 was supposed to improve the battery life. I'll try to see what process, app or activity is taking the most juice out of it, but I'm sure this isn't normal.
Alright so it took me an hour to go from my house to my workplace, and my battery went from 34% to 12%, while being on standby. This isn't normal I guess. I'll need to charge it to 100% once, and then use the Battery setting to see what's taking all the juice.
Might have spoke too soon. When going to work today, I went in a room where there's usually no signal (or the signal is very weak), and lost the network. It's normal in that room so I didn't pay much attention to it, but now I'm not able to get back on the network. Even searching for the Network Operator fails. Sigh, it really looks like I'll have to send it to LG for repair. I guess I need to fastboot it first to erase all my data, because they need to use my phone to test the repairs they make?
Hello there!
So from today (After much waiting and checking the updater app) I can update to EMUI 5 (B360)!
But I'm a little bit unsure if I should update because many people have reported issues with it, will just factory reseting the phone after updating to EMUI 5 fix the problems or should I stay on Marshmallow until full Nougat comes out?
Hello there!
So from today (After much waiting and checking the updater app) I can update to EMUI 5 (B360)!
But I'm a little bit unsure if I should update because many people have reported issues with it, will just factory reseting the phone after updating to EMUI 5 fix the problems or should I stay on Marshmallow until full Nougat comes out?
Click to expand...
Click to collapse
This is the only Nougat your going to get
And sure a factory reset is always good after a major OS update
Sent from my Nexus 6P using Tapatalk
If you care about battery life you shouldn't upgrade imo
salihss said:
If you care about battery life you shouldn't upgrade imo
Click to expand...
Click to collapse
I can confirm my battery life took a dive. I am now *charging* my phone when I drive home from work. I didn't need to do this before with MM. Sadly Huawei screwed up the battery life and no solution in sight.
Here are some likes and dislikes on it. I do suggest you read before you update. Once updated, rollback would require you to reset.
https://forum.xda-developers.com/honor-8/help/honor-8-nougat-emui-likes-unlikes-t3556351
Hello there!
So from today (After much waiting and checking the updater app) I can update to EMUI 5 (B360)!
But I'm a little bit unsure if I should update because many people have reported issues with it, will just factory reseting the phone after updating to EMUI 5 fix the problems or should I stay on Marshmallow until full Nougat comes out?
Click to expand...
Click to collapse
I personally can´t recommend it. Battery for me isn´t bad but I´m having a ridiculous amount of graphical glitches, bugs with notifications and sometimes apps like camera, can´t be opened on the lockscreen cause some lockscreen elements overlay and won´t allow interaction with the camera app until I restarted my phone.
Seems like people having all kinds of different issues, that others don´t have.
Really weird.
I have been running EMUI 5 since the UK beta ( about 3 months)
I have only ever put official OTA updates on my phone.
I'm having none of the issues with my phone.
No glitches, no lags no problems.
My battery life is excellent it lasts from 8am through to 7am the following morning and normally has about 30℅ left when I charge it each morning between 7-8am
I use my phone heavily all day and watch TV on it in bed every night for at least 2 hours
I'm very pleased with my honor 8
John
Sent from my Honor 8 using XDA Labs
Battery is a tiny bit worse, but it fixed the NFC issues, so definitely worth upgrading (no more red lights 1/3 of the time rendering it useless on Transport for London services, and it can read a passport now, and an HK Octopus card consistently...).
A factory reset was needed after upgrading to fix some weird behaviour.
johnhux7 said:
I have been running EMUI 5 since the UK beta ( about 3 months)
I have only ever put official OTA updates on my phone.
I'm having none of the issues with my phone.
No glitches, no lags no problems.
My battery life is excellent it lasts from 8am through to 7am the following morning and normally has about 30℅ left when I charge it each morning between 7-8am
I use my phone heavily all day and watch TV on it in bed every night for at least 2 hours
I'm very pleased with my honor 8
John
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Updated, and well the battery is draining faster than usual but it drains about the same speed that it drained when I first got the phone.... But I believe that the battery will be back to normal in a couple of days.
AllieKitty said:
Battery is a tiny bit worse, but it fixed the NFC issues, so definitely worth upgrading (no more red lights 1/3 of the time rendering it useless on Transport for London services, and it can read a passport now, and an HK Octopus card consistently...).
A factory reset was needed after upgrading to fix some weird behaviour.
Click to expand...
Click to collapse
I have updated and I must say, I really love the new features and that they fixed some of the bugs
Only glitch I've found is with the gyroscope. Only had the phone a day so not sure what it was like before the update, but this video suggests it only happened after updating;
https://m.youtube.com/watch?v=TBFz-i_ruXc
Whether anyone else has had this problem?
My Galaxy S7 (AT&T SM-G930A) was recently updated to Android 8 (Oreo). Since the update I am having issues with the volume. I plug my phone into a stereo receiver at work and we listen all day 12 - 14 hours. Nougat would often reset my volume after about 10 hrs of playing and display a warning about the dangers of listening to high volumes for extended periods. Since updating to Oreo the volume will reset randomly. It will not display a warning or reason it just resets. At first I thought it was because I was receiving a call or text or email but the random volume resets do not correspond to any notifications. This happens three or four times a day since the update.
The volume issues are just a minor issue compared to my battery life. I have a 33% reduction to battery life. Prior to the update I would plug in (to the stereo) my phone in the morning and after a 12 hr shift I would have about 20-25% left. Since the update I plug in (to the stereo) and after about 10 hrs I'm at 10-15%. I have not installed any new apps since the Oreo update and there are no other causes for the change in battery life.
The other main issue I have is speed. The phone is noticeably slower. Apps take longer to open and there is definite lag. Earlier today it took me a little over three minutes to pull up my navigation app and get directions. Prior to the update it would take around 30 seconds.
Here are my questions.
1) CAN I INSTALL A CUSTOM ROM? I had Cyanogenmod on my S4 and really liked it over the stock ROM. I think I would like to give Lineage a try but I still can't get a definite answer as to whether or not this can be done. Obviously I have the Snapdragon processor. Most of the information I'm finding is telling me that we can't install a custom recovery on Snapdragons yet, which means, no custom ROM. If I am wrong please provide me some current links.
2) If I can't install a custom recovery/ROM; CAN I REVERT TO NOUGAT OR MARSHMALLOW?
3) If I can't revert; WHAT CAN I DO THAT WILL PROVIDE ME WITH MORE IMMEDIATE SATISFACTION THAN WAITING FOR AT&T OR SAMSUNG TO FIX THIS CRAP?
1) No, US model S7's have locked bootloaders preventing custom firmware/recovery. You'll need an international G930F/FD to do anything custom.
2) No, the bootloader being locked prevents OS downgrades. You can only sidestep or upgrade.
3) Unfortunately your hands are pretty tied. All I can suggest is backup anything important and do a full clean flash, which may resolve some of the anomalies.
Beanvee7 said:
1) No, US model S7's have locked bootloaders preventing custom firmware/recovery. You'll need an international G930F/FD to do anything custom.
2) No, the bootloader being locked prevents OS downgrades. You can only sidestep or upgrade.
3) Unfortunately your hands are pretty tied. All I can suggest is backup anything important and do a full clean flash, which may resolve some of the anomalies.
Click to expand...
Click to collapse
Beanvee,
Thanks for the quick and concise reply. I just wanted to offer a belated but brief follow up. I backed up and restored Android. It took a little while to get everything back where I wanted it but most things seem better now. The only complaint I have at this time is that my streaming music app(s) seem to drop the connections too often when running on WiFi. If I turn off the WiFi and use mobile data there aren't any issues. The WiFi issues happen at home, at work and when connected at my mother's home and friend's homes. I rarely have mobile data over-runs so it isn't an issue per se; it just bugs me a little.
Once again, thanks for the help.
I'm afraid that's something I've not experienced and wouldn't know where to look. Best I can think of is check battery saving options, and under WiFi > advanced, make sure Keep WiFi on during sleep is set to Always
Over about the last week my Watch4 Classic (SM-R890) went from lasting about 2 1/2 days on a charge to well less than a day. I could not figure out what was going on. I ended up resetting my watch and uninstalling/reinstalling all software on phone. After this I could not setup/sync watch to phone. I did everything I saw on-line to resolve this issue. No luck. My watch is unusable. I saw some reports on-line that there are issues with Watch4 and Android 13. It then occurred to me that I started having the battery issues about the time I updated my phone ( Pixel 6 Pro) to Android 13. Is anyone else here having battery/sync issues since updating to Android 13?
So I was able to setup watch finally. Surprisingly I was able to setup watch correctly when I disabled wifi on my phone. I have no idea on why this worked. After resetting my watch and uninstalling/reinstalling all software on phone I sill have battery issues. Definitely well less than a day. Last night as I slept I lost about 50% battery and I had bedtime mode on. Two weeks ago I would lose 5 - 8% overnight with bedtime mode. Other people are having this issue:
https://www.reddit.com/r/GalaxyWatch/comments/wqo3iu
https://www.reddit.com/r/GooglePixel/comments/x6fb76
I'm not running Samsung health on phone. This is apparently probably not a watch software or watch hardware issue. This is being reported with multiple wearos devices across manufacturers (Like TWP3). It appears to be related to Android 13.
Is there anyone here that has Android 13 on their phone who is not having battery issues?
Not that anyone cares based based on replies but apparently the Sept. Android 13 update addresses Bluetooth issues.
https://9to5google.com/2022/09/06/android-13-pixel-september-update/
I'm in US on Verizon. Apparently Verizon updated yesterday (9/12) the Pixel 6 Pro (TP1A.220905.004.A1). I keep checking for update, not yet. It is definitely Bluetooth issue with Android 13. I turned off Bluetooth on my phone and battery on watch is same as before Android 13 update. Hoping update fixes....
Sorry bro for no replies, it's just that we don't have Android 13 yet.
I am on the Android 13 beta on my Samsung S22 Ultra with the Watch 4 Classic. The watch has the latest load on it since I was on the watch beta. I have had no issues with my watch not lasting at least a full day. I have seen no difference from Android 12 to Android 13.
I received the Android 13 Sept. update (TP1A.220905.004.A1) and sadly this does not fix the issue. Such a bummer. You would think that Google would get this fixed. Given this is an issue with other wearos watches I wonder if this will impact the Pixel Watch...
Fixed issue. After trying many things ultimately it ended up the issue was related to updating from Android 12 to 13 instead of clean update. When I factory reset my phone the watch's battery life is back to normal. It was not Google Assistant or Samsung Health.
Android 12 battery & watch syncing has been working good for me. I have not tried 13 yet....
GW4C and A13, no issues at all..
Sorry people weren't replying and showing you love princess.