Laggy Pixel - almost impossible to make/receive phone calls - Google Pixel Questions & Answers

Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
Ive updated to latest ota on pixel 1 and had no problems so far. You could check the dialer app is set as default dialer and all permissions are granted and maybe clear the apps storage/cache, force stop it and re open it and see if that solves anything? Could also check background apps and running services in developing options to see if an app is banging out the memory causing it to lag?
Sent from my Pixel using XDA Labs

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
if you already did factory reset then it must be a sign of motherboard is dying soon or bad nand chip. motherboard failing on pixel is very common but it happens to less than 1% of people. there are plent of threads on reddit/xda on this.

What's the status of your Pixel? Is the bootloader unlocked? Rooted? Did you have any such problems on the December udpate?

As mentioned - I did factory reset as I thought it may help cure the problems, but it didn't.
I have never unlocked bootloder and phone is not rooted. All standard here.
I have the latest update installed and same problems persist ;/
I'll try another factory reset today.

Related

Random reboots mostly after unlocking, am I the only one getting them?

Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
MarkMRL said:
Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
Click to expand...
Click to collapse
If you provide some logs then maybe someone can see what is happening....
Or even basic information, like the configuration and setup of your device.
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Info
MarkMRL said:
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Click to expand...
Click to collapse
Factory Reset can solve ur problem /based on personal experience
I did that already less than two months ago and I refuse to believe I have to factory reset this thing every month to get stable operation. Also I'm not even rooted and I haven't messed with the system itself so why would I need to factory reset? Factory reset implies that there is something that has changed and needs to be re-set, and I haven't changed anything special that would require such a drastic solution. Not having done anything special, the issue would come back sooner or later if I don't spot the real cause.
Anyway, in diagnostics I have 21 application incidents for systemUI... Could it be caused by a bugged theme? Does this happen to anyone else?
Today I had two and I had another one last week. A off these were weird half reboots like I described above. I only noticed one because I was at my desk and the phone lighted up for the boot animation.
These reboots show up in diagnostics (phone info menu) as system events. Can you please check out if you have any system events and post here? I want to know if this is a widespread problem. Post here if you have any and also if you have a solution or way to troubleshoot.
Nobody at all? Really?

Problem - touchscreen not working properly sometimes

Hi all,
I have this annoying problem that occurs ones a day or twice and I have to restart the phone because of it.
Sometimes for no reason in different apps when I type or even use the touchscreen I have this annoying bug that the phone presses the screen few times when I press it just ones, for example when I try to type something it presses the letter 5 times instead of ones and its practically unusable untill I restart the phone.
Any one had this problem before? Any ideas if there is a way to fix it?
I am using the stock is, with Google launcher on top bu this happened even before I used the Google launcher. All stock here and I am using the 16gb eu variant of the phone
Thanks in advance for any help and suggestions
Have you try it factory reset?
No, nothing like that yet to be honest
Seems my huawei ascend mate is having same issue, Have you managed to solve the issue. Share so that I also can try..?
tixoo said:
Hi all,
I have this annoying problem that occurs ones a day or twice and I have to restart the phone because of it.
Sometimes for no reason in different apps when I type or even use the touchscreen I have this annoying bug that the phone presses the screen few times when I press it just ones, for example when I try to type something it presses the letter 5 times instead of ones and its practically unusable untill I restart the phone.
Any one had this problem before? Any ideas if there is a way to fix it?
I am using the stock is, with Google launcher on top bu this happened even before I used the Google launcher. All stock here and I am using the 16gb eu variant of the phone
Thanks in advance for any help and suggestions
Click to expand...
Click to collapse
I don't have this problem with my HAM7, though I did previously experience it with an old Sony Xperia. Like you mentioned a reboot temporarily fixed the issue but I had to ultimately do a factory reset to rid the phone of this annoying bug.
Quick question: are you using the original charger that came with the phone? That was another thing that I noticed with my Sony. Its stock charger had died and I replaced it with a cheap third-party one found in the Chinatown of my city. This seemed to trigger this bug, and also caused screen taps to register way off compared to where I physically tapped the screen. This continued until after the factory reset, but still happened when the phone was on charge.
TLDR: Do a factory reset. If that doesn't help it'll probably be a hardware issue.
Hope this helps otherwise good luck!
Ok , listen
when this happens
go to settings , manage aps ,running apps .. then force close FB messenger .. it will be solved that's a bug in fb messenger. u will c
Sent from my HUAWEI MT7-TL10 using Tapatalk
ERM... I changed that phone like over half a year ... Good memories tho rocking the p8max now ... No issues

Marshmallow problems with spontaneous launching of Google Now, taking over device.

My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be too basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Stoksie said:
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be to basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Click to expand...
Click to collapse
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Stoksie said:
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Click to expand...
Click to collapse
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Stoksie said:
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Click to expand...
Click to collapse
It could have been something in system that got changed during the update but the data from before the change is still there and conflicting with whatever changes were made. Some kind of saved system data that can only be wiped by factory reset or reflashing.
Sent from my SM-S903VL using Tapatalk
I did a factory reset, lost a lot of photos that had started being saved on the phone and not the sdcard after the upgrade to Marshmallow. Have had to accept that but unfortunately the bizarre behavior did not stop and it continues on and off, sometimes so bad that I cannot dial a number on it and other times it happens but I can get in between the action and dial or send a text etc. I have gradually been stopping things like notifications from google apps and traffic reports from google maps (this may have had a good effect) and anything that might be doing constant checks. It seems to have quietened down over the last day or so and I even got to play a game on it but the next option is to send it away to an engineer. I just thought that I would let you know the outcome of the factory reset.

Why does my Google Pixel randomly reboot?

Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.

Question AOD and screen wake on notifications stopped working

Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!
Czarls said:
Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!
Click to expand...
Click to collapse
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.
Lada333 said:
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.
Click to expand...
Click to collapse
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?
Czarls said:
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?
Click to expand...
Click to collapse
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue
Lada333 said:
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue
Click to expand...
Click to collapse
I'm trying to figure out if it's a software issue in a ROM or some applications impact..

Categories

Resources