Database Info

Nexus 5 and various issues, anything that can be done?

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?

Should I update to EMUI 5?

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?

Android 8.1 beta now available

https://twitter.com/sarvikas/status/955753890770665472
Get it here :
https://www.nokia.com/en_int/phones/betalabs

Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace

I have been battering it since installing and i cant make it cough, splutter or hiccup, seems all but finished to me rather than a beta.

Not quite. I discovered and reported a rather annoying kernel wakelock that doesn't allow CPU deep sleep for hours, causing battery drain.

amunarjoh said:
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
Click to expand...
Click to collapse
Do you mind doing a system dump for me? If you need help look up how to do a system dump, but I think you need root and do adb /pull system .

xterminater07 said:
Do you mind doing a system dump for me? If you need help look up how to do a system dump, but I think you need root and do adb /pull system .
Click to expand...
Click to collapse
Hi, and thanks for asking. At the moment I am so happy with the barbone Android, that I don't see a reason to root. Maybe at some other point in time...
By the way, it took just a few seconds to enter Nokia beta and download the 8.1.

aoleg said:
Not quite. I discovered and reported a rather annoying kernel wakelock that doesn't allow CPU deep sleep for hours, causing battery drain.
Click to expand...
Click to collapse
Thats weird, everyone else is reporting better battery life.

amunarjoh said:
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
Click to expand...
Click to collapse
amunarjoh said:
Hi, and thanks for asking. At the moment I am so happy with the barbone Android, that I don't see a reason to root. Maybe at some other point in time...
By the way, it took just a few seconds to enter Nokia beta and download the 8.1.
Click to expand...
Click to collapse
I do not have the phone, I have another phone that uses the same sensors as the Nokia 8, that's why I would like to have the system dump so I can see some information regarding cameras. Or if you can link me to the beta download that would be great. I can try to pull files and info from it.

I haven't noticed any crashes on this beta, but the battery life is definitely worse for me.
This device has no root, so pulling the system will be difficult I think.

MrBelter said:
Thats weird, everyone else is reporting better battery life.
Click to expand...
Click to collapse
That's what beta testing is for. "Works on my computer", you know, is not an acceptable excuse for programmers doing paid work. In some circumstances, on some models, in some regions, with some mobile service providers, etc, etc, you get intermittent weird problems that are impossible to catch during the "closed" beta testing phase. On my phone, there is almost no CPU deep sleep due to some kernel wakelock (I cannot get more details than this without root access, and there's no root for this model). After 3 days on 8.1 beta, I rolled back to 8.0 stable; no wakelock issues whatsoever. Of course, I submitted a comprehensive bug report before rolling back, so hopefully HMD catches and squashes this bug.

If you set animations to 0.5x you can notice the speed improvement more. Though could be placebo. Before 0.5x was more choppy and 8.1 feels smoother.

8.1 is definitely smoother!
The double tap on recent apps (for fast change) are waaay faster and without a single hiccup for me.
Battery have better stand-by with wifi and auto sync on.
Less than 1% per hour! (almost two hours to drain 1%)
Sent from my Nokia 8!

aoleg said:
That's what beta testing is for. "Works on my computer", you know, is not an acceptable excuse for programmers doing paid work. In some circumstances, on some models, in some regions, with some mobile service providers, etc, etc, you get intermittent weird problems that are impossible to catch during the "closed" beta testing phase. On my phone, there is almost no CPU deep sleep due to some kernel wakelock (I cannot get more details than this without root access, and there's no root for this model). After 3 days on 8.1 beta, I rolled back to 8.0 stable; no wakelock issues whatsoever. Of course, I submitted a comprehensive bug report before rolling back, so hopefully HMD catches and squashes this bug.
Click to expand...
Click to collapse
Wow chill your beans, i am fully aware what beta testing is and i certainly do not need preaching to about it by the likes of you.
I was about to report that the standby times on my phone are also reduced but i don't think i'll bother now, you seem to have it all covered with your comprehensive report.

I observe that when i take my phone out of my pocket it automatically unlocks the screen lock( i put my finger on fp sensor when i take my phone out of my pocket). After that i checked if there is a problem with the light sensor, so i covered it so it couldn't get any light but still unlocked the phone when i used my fp to unlock it. Do you guys have that problem? Also to note that when i am making phone calls light sensor works like normal.
Sent from my TA-1012 using XDA Labs

USB tethering also doesn't seem to be working correctly and causes reboots.

still no ambient display......

Also the pop up when i want to disable the mobile data is frustrating. Is there a way to disable this?
Sent from my TA-1012 using XDA Labs

bluetooht not working
bluetooht also doesn't seem to be working correctly and causes reboots. when i make calls over carkit

hennieh said:
bluetooht also doesn't seem to be working correctly and causes reboots. when i make calls over carkit
Click to expand...
Click to collapse
I'm using Bluetooth with two different car kits, speaker and headphones. No issues at all. Actually it seems to be using less power than on 8.0.
On 8.0 sometimes I couldn't connect to car kit. On 8.1 this issue seems to be gone.

This is the kind of battery life i am getting now after a few days running the beta, i still think standby times are worse but not shockingly so.

Occasional stutter and slowdown

I started noticing recently serious stutter and slowdowns in the apps and GUI fluidity. This can happen now and then, like every few days, and goes away after a reboot. Why would this start to happen only now? I had this phone since the last year. I suspect the recent firmware updates have brought this issue. Incidentally, some people complained about such issues with the new Honor 7X too.

yes, my honor 6x us getting hang sometimes but it doesn't happens before the b360 update

Same here started feeling the device lagging and stuttering after the latest updates

It's been my experience with Android updates that sometimes a major update can ruin a phone unless you reset it to factory settings (deleting all your data and settings of course). This actually worked on my Nexus 5X after the Oreo update which seemed to effectively ruin the phone until a hard reset. Of course, I don't necessarily suggest that we do this on the Honor 6X yet. Lets wait and see what happens. Perhaps newer firmware will fix this. I also notice that this often starts to happen when I open something like 20 tabs in Chrome. *Mental note to self: Don't open 20 or more tabs in Chrome*

Akopps said:
It's been my experience with Android updates that sometimes a major update can ruin a phone unless you reset it to factory settings (deleting all your data and settings of course). This actually worked on my Nexus 5X after the Oreo update which seemed to effectively ruin the phone until a hard reset. Of course, I don't necessarily suggest that we do this on the Honor 6X yet. Lets wait and see what happens. Perhaps newer firmware will fix this. I also notice that this often starts to happen when I open something like 20 tabs in Chrome. *Mental note to self: Don't open 20 or more tabs in Chrome*
Click to expand...
Click to collapse
Chrome uses even more memory after their latest update

Akopps said:
I started noticing recently serious stutter and slowdowns in the apps and GUI fluidity. This can happen now and then, like every few days, and goes away after a reboot. Why would this start to happen only now? I had this phone since the last year. I suspect the recent firmware updates have brought this issue. Incidentally, some people complained about such issues with the new Honor 7X too.
Click to expand...
Click to collapse
Guys same thing is happening to me for last couple of days. Anyone has any idea for a fix? I am not rooted. only reason I am not rooting is because I dont want to lose data and settings

Pixel 3 hangs for 15-30 seconds when switching apps, typing

I know there are memory management issues with this phone; what I'm not sure though is if the behavior I'm experiencing is just a manifestation of this well-known problem or another issue.
Since I got the phone a month ago, after some period of use after rebooting, simple actions like switching between two apps can cause the phone to hang for a long time - usually 20 or 30 seconds. The phone isn't completely hung - I can still go back to the home screen, and do some things, but whatever app I tried to switch to will be non-responsive for this whole time. Eventually, it will just start working again.
Other times, typing using the google keyboard will get stuck - that is, I can still type, but nothing shows up in the field where the text should appear. After a while it will suddenly "catch up" and everything I typed appears.
These two issues both seem to start happening around the same time, so it seems memory use related, but the amount of time involved seems very excessive for swapping.
I can fix this just by rebooting, but it always comes back after a while. I suspect it's related to how many different apps I've loaded and not just time of use, though, since sometimes it won't happen for a day or two, but it always happens again at some point.
I removed a bunch of apps that were migrated from my old phone (a Motorola Z Force), too, to try to eliminate a badly-behaving app, but I never had any issues like this on that phone, and it didn't make any difference.
Is anyone else experiencing this? Or does it sound like a possible hardware problem? I don't want to swap the phone unless it's clear this is abnormal behavior. Thanks.

It's abnormal behavior. My first thought is it might be related to a balky network or intermittent connection. Just a wild guess. Do you see the same issue in airplane mode? Also, if you check battery or cpu usage is anything hogging resources?

samnada said:
It's abnormal behavior. My first thought is it might be related to a balky network or intermittent connection. Just a wild guess. Do you see the same issue in airplane mode? Also, if you check battery or cpu usage is anything hogging resources?
Click to expand...
Click to collapse
I've used the phone in exactly the same circumstances as my prior phone (and other devices) so I don't think it has to do with network connectivity; but next time it happens I'll try switching to airplane mode just to be sure. There's no visual indication of a network drop (e.g. wifi status icon). I haven't checked for anything hogging resources during these events, and generally I'm not having any battery life or performance problems. It's just switching apps that brings everything to a standstill for a while, and then it works fine again.

jamtre said:
I've used the phone in exactly the same circumstances as my prior phone (and other devices) so I don't think it has to do with network connectivity; but next time it happens I'll try switching to airplane mode just to be sure. There's no visual indication of a network drop (e.g. wifi status icon). I haven't checked for anything hogging resources during these events, and generally I'm not having any battery life or performance problems. It's just switching apps that brings everything to a standstill for a while, and then it works fine again.
Click to expand...
Click to collapse
Maybe check the temp when it's stalling. This app might show something: https://play.google.com/store/apps/details?id=com.glgjing.stark&hl=en_US

I have the exact same issue as OP describes.
Had a 64gb Pixel 3 when it was first released and it manifested the issue with the random hangs and freezes. I decided it was too buggy and returned it.
A month later got a 128gb Pixel 3 on the gift card promo and it is exhibiting the same issue as the OP and my original 64gb unit.
Doubtful it is a hardware issue since this is my second one with the same issue.
I have tried factory reset and removing any un-necessary programs on both, but the condition still persists.
Both phones were on Fi.
If the January patch does not fix the issue it will be time to switch back to iPhone.

mrchuckfl said:
I have the exact same issue as OP describes.
Had a 64gb Pixel 3 when it was first released and it manifested the issue with the random hangs and freezes. I decided it was too buggy and returned it.
A month later got a 128gb Pixel 3 on the gift card promo and it is exhibiting the same issue as the OP and my original 64gb unit.
Doubtful it is a hardware issue since this is my second one with the same issue.
I have tried factory reset and removing any un-necessary programs on both, but the condition still persists.
Both phones were on Fi.
If the January patch does not fix the issue it will be time to switch back to iPhone.
Click to expand...
Click to collapse
Mine's 128gb (Verizon). The January patch looks trivial so not expecting any change here...
Not going to switch to iPhone but troubling that you have had this with two different phones. At the same time, pp seemed to think this is not typical behavior, and if it's a common OS issue then wouldn't a lot of people be talking about it? I'm not a crazy power user or anything, I never play games, pretty much use Waze, whatsapp, camera, facebook (lite), spotify, etc... really pretty standard apps.
I wonder if there's something unique to us that could be involved here? I'm not using any apps I wasn't using on my old phone, but I also had Oreo before and not Pie, so not a direct comparison. When I first set up my phone, though, all my old apps were migrated, including some Verizon bloatware I couldn't delete from the old phone. Is it possible that apps that were automatically migrated (but later deleted) could have left something behind that's causing issues with PIe?

jamtre said:
Mine's 128gb (Verizon). The January patch looks trivial so not expecting any change here...
Not going to switch to iPhone but troubling that you have had this with two different phones. At the same time, pp seemed to think this is not typical behavior, and if it's a common OS issue then wouldn't a lot of people be talking about it? I'm not a crazy power user or anything, I never play games, pretty much use Waze, whatsapp, camera, facebook (lite), spotify, etc... really pretty standard apps.
I wonder if there's something unique to us that could be involved here? I'm not using any apps I wasn't using on my old phone, but I also had Oreo before and not Pie, so not a direct comparison. When I first set up my phone, though, all my old apps were migrated, including some Verizon bloatware I couldn't delete from the old phone. Is it possible that apps that were automatically migrated (but later deleted) could have left something behind that's causing issues with PIe?
Click to expand...
Click to collapse
I have have been on Google phones since Nexus 4 and upgrading like a good consumer every year.
Like yourself I am not doing anything crazy and have the run of the mill stuff like FB, Snap, kik, Whatsapp and IG. The only thing out of the ordinary I have on the phone is Cerberus and BlackBerry email.
Apps don't get migrated so that is not the issue. When you setup a new phone or transfer, some of the data is moved, but the app is re-downloaded from the app store.

mrchuckfl said:
I have the exact same issue as OP describes.
Apps don't get migrated so that is not the issue. When you setup a new phone or transfer, some of the data is moved, but the app is re-downloaded from the app store.
Click to expand...
Click to collapse
Right - but it installed -everything- I had on my old phone including some Motorola & Verizon apps, which I then uninstalled (but maybe even missed some). Just thinking it might be possible that something hardware-specific to my old phone got installed on the pixel. In theory shouldn't matter but there seem to be so many nuances to Android, particularly across major releases, that I wondered if this could have been involved in the problem.
Anecdotally, it seems like it's been happening less often over time. I haven't had it happen in a few days, though I installed the update yesterday so I'm within 24 hrs of a clean boot now.

jamtre said:
Right - but it installed -everything- I had on my old phone including some Motorola & Verizon apps, which I then uninstalled (but maybe even missed some). Just thinking it might be possible that something hardware-specific to my old phone got installed on the pixel. In theory shouldn't matter but there seem to be so many nuances to Android, particularly across major releases, that I wondered if this could have been involved in the problem.
Anecdotally, it seems like it's been happening less often over time. I haven't had it happen in a few days, though I installed the update yesterday so I'm within 24 hrs of a clean boot now.
Click to expand...
Click to collapse
I've been having exactly the same issues for the last couple of days. Have just done a factory reset but the problem persists. The biggest issue is that when the phone is locked it seems to freeze as well and takes about 15-20 secs to unlock. Also if you phone it while its locked (and frozen) the incoming call isn't acknowledged (no ringing !) until after its unfrozen. Looks like I may have to return it and get a different phone !
Mike

More than a few people have been having issues with their Pixel 3, but I've yet to experience a single issue with memory management or slowdowns. In fact, I've found the Pixel 3 to be a far smoother UI than the iPhone X on the newest versions of iOS. Maybe I got lucky, but I'm more inclined to think it's about use. Just like my desktop operating system, I start from scratch every time I do a reformat, reset, or upgrade of a device. I can see there being issues with migrating old data. I'm also a fairly light app user; I've got around 100 apps in my drawer, most of which are Google apps or banking apps. Are the people experiencing these slowdowns installing a lot of things or running more resource intensive apps like Facebook? Not to say you shouldn't be able to do that with your phone, but I'm curious how behavior differs in our situations.

Feb update?
OP here, so more than a week since the February update landed and I have not had this happen since then. I'm kind of shocked, honestly, and keep waiting for the other shoe to drop, but so far it looks like something they did fixed this.
The only other significant change I made was to uninstall the Facebook Lite app, a few days ago, but I've used that long before I had a Pixel 3 so doubt it's related. So... :fingers-crossed:!!

jamtre said:
OP here, so more than a week since the February update landed and I have not had this happen since then. I'm kind of shocked, honestly, and keep waiting for the other shoe to drop, but so far it looks like something they did fixed this.
The only other significant change I made was to uninstall the Facebook Lite app, a few days ago, but I've used that long before I had a Pixel 3 so doubt it's related. So... :fingers-crossed:!!
Click to expand...
Click to collapse
Maybe I should give Pixel 3 a try. Tried P3 twice since October and it was a phenomenal laggy mess specially under load ... My Pixel 2 had its ups and downs, specially with the Pie release. Took them 3-4 months to 'get it right' so I'd expect Pixel 3 to be no different.

I was experiencing some lag and short freeze (2 to 7/8 seconds) with my pixel after the latest update.
I tried a factory reset with little hope but it seems it did the trick for me. No issues ever since.