Develop Bugs

New recalled Note 7 - Issues with Media/Lag/Wifi/Heat

Hey all,
I'm becoming increasingly frustrated with my Note 7 (recall replacement one).
1. It lags like HELL! I've done all the animation scaling off/force GPU rendering etc, but I shouldn't have to. Just a simple thing like pulling down the notification bar noticeably lags every couple of times.
2. I use Android Auto, which I always have to reconnect manually to use (never did on the S7).
3. When listening to Spotify over Android Auto, I occasionally get stutter/glitches in the sound. Once the glitch was so bad the phone froze and it had to be reset.
4. The thing gets hot. Annoyingly hot, even if I'm just browsing Chrome, or reading G-mail etc. It's not like I'm gaming!!
5. WiFi is very sporadic. The connection is rock solid, but often it will be downloading an app...sit at 100% of download and progress no further. This happens quite frequently.
With all the above, (bar number 2), none of it applied to the pre-recalled Note 7.
I'm frustrated to say the least. Does anyone else get any of this whatsoever? I can't go through not having a phone again, or sending this for what Samsung will insist on a repair. This phone is jinxed and I'm gutted.
Any suggestions (bar a hard reset haha) will be greatly received.
PS. I have disabled loads of apps with the AppDisabler to try and help it along but I think there's an issue with the RAM or some of the internal modules (at a guess). Thanks all

I have just managed to reduce the lag quite a bit by uninstalling Samsung Good Lock (which was forced upon me earlier today)! I liked it, but serious lag creation!

Did you use Smart Switch to change phones? I've found quite a few apps don't like to be transferred. Android Auto apps don't move right via Smart Switch and I had to uninstall/reinstall them.
Be careful what you disable. Some of Samsung's seemingly benign system apps are called by other apps and if they don't respond are constantly polled. That could cause a lot of background processes and may be a source of your overheating. My pre-exchange phone did what you're describing the first couple of days after I set it up. It would maybe once or twice a day get blocky when scrolling as if something was running in the background. The (U.S.) PH1 update made it go away. But we're S-820 in the U.S. and I think you guys are Exynos. So different problems different solutions.

Thanks for your reply Barry. Actually not Smart Switch, but I let it restore my 100+ apps from my previous Note 7 (near the end of the initial set up). The apps were downloading but strangely, every so often nothing was happening after they'd reached 100% downloaded, just before "installing..." (over WiFi). I cancelled that specific app and the restore continued (this happened over and over). Turning WiFi on and off sorted it temporarily but I couldn't download more than 3/4 without this really strange issue.
I also observed the longest lag ever! I went into the OS update screen, pressed update and the device didn't respond. 5 mins later while doing something completely different, the update screen popped up about 12 times (as I'd pressed it 12 times 5 mins previously). This happened again after a reboot too!
Now, I've just bitten the bullet and performed a hard reset. This time the WiFi seems great, although now I'm speculating that it was getting stuck at 100% post download perhaps because the security thing was having trouble scanning it for malware prior to install.
I also take your note re:disabling stuff! I'm going to do something unheard of and just try it stock for a bit and see how it goes. For such amazing hardware, the fact my note 3 was running 10 times smoother means something drastic is going on. I hope this hard reset is the end of it!

Chances are the hard reset won't do anything, though I hope you have better luck than I did. I went through three phones (on my 4th). I did the hard reset as soon as I picked up the 2nd handset and onward before I did anything with the phone. Sadly you should not have to disable anything, the phone should just work for 900.00. Some will say otherwise.. Wi-FI is good for me but the reception is garbage. On various phones with T-MO including other android devices that colleagues have - they get 4/5 bars and usually double the download speed on Speedtest. The head I had on the first I don't get as bad on this one. But the lag I do...
Did you get the update from your provider as well?

I just picked up my replacement Sprint Note7 today so not much time with it though seems identical except 1 small issue. I had my first Note 7 rooted, Viper4Android and Dolby Atmos flashed along with Xposed and it worked flawlessly. The replacement Note fails with binary invalid using the exact same odin version, Sun7 systemless root etc that I have on my pc from the first Note 7 and the second Note 7 was given to me not updated, in other words its on the exact same firmware as the first one!
I am very proficient with rooting, adb, etc and this has me baffled.
Has anyone successfully rooted a replacement N930p that came with PH9? using freeza's guide?

jonboyuk said:
Thanks for your reply Barry. Actually not Smart Switch, but I let it restore my 100+ apps from my previous Note 7 (near the end of the initial set up). The apps were downloading but strangely, every so often nothing was happening after they'd reached 100% downloaded, just before "installing..." (over WiFi). I cancelled that specific app and the restore continued (this happened over and over). Turning WiFi on and off sorted it temporarily but I couldn't download more than 3/4 without this really strange issue.
I also observed the longest lag ever! I went into the OS update screen, pressed update and the device didn't respond. 5 mins later while doing something completely different, the update screen popped up about 12 times (as I'd pressed it 12 times 5 mins previously). This happened again after a reboot too!
Now, I've just bitten the bullet and performed a hard reset. This time the WiFi seems great, although now I'm speculating that it was getting stuck at 100% post download perhaps because the security thing was having trouble scanning it for malware prior to install.
I also take your note re:disabling stuff! I'm going to do something unheard of and just try it stock for a bit and see how it goes. For such amazing hardware, the fact my note 3 was running 10 times smoother means something drastic is going on. I hope this hard reset is the end of it!
Click to expand...
Click to collapse
Yea disabling seems like a great idea at first but it actually creates problems. I run it completely as is except uninstalling the preloaded games. Didnt disable anything. Disabling stuff caused massive lag on my note 5 and same with note 7.

Thanks chaps.
I've gotta say, the hard reset has made the world of difference. Which to me is strange, I've never had to hard reset a new device, but it's done the trick.
Regarding the disabling of services, there must be *some* that are safe to disable? I agree if you're tinkering with potentially integral things like S-Voice it's not a good idea. But then stuff like OneDrive surely that's okay? Maybe, things like the Disabler package are a bad plan. You can disable software by default without it, but only certain apps. Maybe that's why Samsung prevent the disabling of certain bloat...?

jonboyuk said:
Thanks chaps.
I've gotta say, the hard reset has made the world of difference. Which to me is strange, I've never had to hard reset a new device, but it's done the trick.
Regarding the disabling of services, there must be *some* that are safe to disable? I agree if you're tinkering with potentially integral things like S-Voice it's not a good idea. But then stuff like OneDrive surely that's okay? Maybe, things like the Disabler package are a bad plan. You can disable software by default without it, but only certain apps. Maybe that's why Samsung prevent the disabling of certain bloat...?
Click to expand...
Click to collapse
I only disable the useless apps, such as all the Microsoft bloat (OneDrive, Excel, Word, etc), Facebook (and all its services), and any Carrier bloat.

GibMcFragger said:
I only disable the useless apps, such as all the Microsoft bloat (OneDrive, Excel, Word, etc), Facebook (and all its services), and any Carrier bloat.
Click to expand...
Click to collapse
Disabling facebook services will broke gear VR.

It's a tricky one! I guess it's a bit of trial and error.

yussuf007 said:
Disabling facebook services will broke gear VR.
Click to expand...
Click to collapse
That's cool. I have no interest in Gear VR.

I have heard somethings about latest version of chrome causing batt drain, could possibly contribute to lag also, I cant tell much as I am expecting my note 7 exchange, but I have seen some posting about it

Have no problems when I used package disabler and chose "disable all bloat"...but after doing that, I looked through the list and enabled around 3 to 5 that I thought didn't need disabling.
No problems since.
Oh...that option doesn't disable facebook, messenger, hangouts etc. So if you don't use those, you need to add them.

Thanks all. Well, after all that, and a hard reset my phone is running perfectly again. Then, this morning I received this from Oculus...
"We recently pushed an Oculus Software update that has inadvertently caused some people to experience phone performance issues."
I haven't put my phone into my Gear VR since the hard reset and I can almost guarantee it was that blimmin thing. Samsung have also updated their Good Lock app to remove lag yesterday!
Damn you Oculus!

Oh..and strangely, the first few hours I got the phone..it got pretty hot...especially since I was using it while charging. I turned off fast charging and no difference. Anyways I just cooled it down w the aircon now and then.
Long story short, it doesn't get hot anymore.
Maybe it's because I used package disabler snd greenify...but whatever I do...Even while charging..it barely gets warm...
Shrugs

koppee1 said:
Oh..and strangely, the first few hours I got the phone..it got pretty hot...especially since I was using it while charging. I turned off fast charging and no difference. Anyways I just cooled it down w the aircon now and then.
Long story short, it doesn't get hot anymore.
Maybe it's because I used package disabler snd greenify...but whatever I do...Even while charging..it barely gets warm...
Shrugs
Click to expand...
Click to collapse
Yea they always get very hot for the first few hours while installing all the new apps! I'm not sure you need Greenify these days do you, since android tends to close apps that are not in use (giving you the same options as Greenify)?

Simples
Wipe data start again.
Set up as new phone and download apps again
Sent from my SM-N930F using XDA-Developers mobile app

ChimpNippl3s said:
Simples
Wipe data start again.
Set up as new phone and download apps again
Click to expand...
Click to collapse
^^^^^
This. I just spent two days doing that and its like a totally different phone. I started a thread highlighting my experiences.

i am quite annnoyed with the lag too. it's nothing too bad, but there's noticeable keyboard lag, and whenever you go into settings to search for something, it takes like two seconds to load. i don't even think this is a case by case situation here, this phone just isn't as fast as a oneplus 3, lg g5 or iphone 7 plus. again, it's not terrible, it's just not the fastest or smoothest.

Strange [and serious] lag issue, please help

I had my Pixel 2 XL since first release, running stock releases updated each month, stock kernel, and using Magisk. I also have a Pixel 2, configured exactly the same way as the 2 XL and the exact same apps. Apps are updated at the same time, same for patch releases. I carry both and use them interchangeably each day. They provide carrier/coverage diversity and allow for a longer day without charge.
A few days ago, with no known reason, my 2 XL started exhibiting a very strange lag behavior. In trying to resolve the issue, I have tried clearing Dalvik, flashing back to February, re-flashing March, and today flashing to April. I have also cleared certain app data and tried a custom kernel Nothing has helped. The problem does not exist on P2.
The lag I have observed so far:
1) I use the Google Calendar "agenda" widget. On boot, the widget is blank and shows "loading" and can take 10 or 15 minutes for the agenda items to populate (as opposed to immediately upon start up).
2) Playstore app updates: It downloads the app, but seemingly hangs and the update is VERY VERY slow.
3) On flashing the April patch, on first boot, the "Completing Android update" notification progress bar took about 45 minutes to complete (as opposed to a few seconds like it should).
4) I use Lightflow. On launching the app, I keep getting "app not responding" message. If I keep tapping "wait", it will eventually load. It is just loading VERY slowly.
I firmly believe that all of these issues are related to a single problem, like a system resource that causing these lags. At this time, I cannot update apps because it would take hours just to update one app.
I really don't want to do a factory reset if I can help it. Too many things to reconfigure, even with TiBu. Does anyone have any idea as to what might be the cause? I would really appreciate any input.
Thanks.

snovvman said:
I had my Pixel 2 XL since first release, running stock releases updated each month, stock kernel, and using Magisk. I also have a Pixel 2, configured exactly the same way as the 2 XL and the exact same apps. Apps are updated at the same time, same for patch releases. I carry both and use them interchangeably each day. They provide carrier/coverage diversity and allow for a longer day without charge.
A few days ago, with no known reason, my 2 XL started exhibiting a very strange lag behavior. In trying to resolve the issue, I have tried clearing Dalvik, flashing back to February, re-flashing March, and today flashing to April. I have also cleared certain app data and tried a custom kernel Nothing has helped. The problem does not exist on P2.
The lag I have observed so far:
1) I use the Google Calendar "agenda" widget. On boot, the widget is blank and shows "loading" and can take 10 or 15 minutes for the agenda items to populate (as opposed to immediately upon start up).
2) Playstore app updates: It downloads the app, but seemingly hangs and the update is VERY VERY slow.
3) On flashing the April patch, on first boot, the "Completing Android update" notification progress bar took about 45 minutes to complete (as opposed to a few seconds like it should).
4) I use Lightflow. On launching the app, I keep getting "app not responding" message. If I keep tapping "wait", it will eventually load. It is just loading VERY slowly.
I firmly believe that all of these issues are related to a single problem, like a system resource that causing these lags. At this time, I cannot update apps because it would take hours just to update one app.
I really don't want to do a factory reset if I can help it. Too many things to reconfigure, even with TiBu. Does anyone have any idea as to what might be the cause? I would really appreciate any input.
Thanks.
Click to expand...
Click to collapse
I don't have a good answer for you my friend other than trying to run it in Safe mode for a while to see if it helps. Other than that, only other thing you probably can do is a factory reset, which, I know, bites the big one!

Badger50 said:
run it in Safe mode for a while to see if it helps.
Click to expand...
Click to collapse
Thanks for that suggestion! The only condition I was able to test was to update apps. It went fine in Safe Mode. I rebooted back into regular mode and app update would hang. Based on what I read, the culprit would be a 3rd-party app?
I looked through all the apps that were updated in the past few days and do not see an app that would have the sort of large impact. There is no abnormal CPU utilization. Keep in mind that my Pixel 2 has the exact same apps and are updated at the same time. It has no such issues. I'm still lost.

The only update that could have an impact is Google Play Services. I'm on beta 12.5.21. Again, no issues w/ Pixel 2. I assume others don't have issues, we would otherwise heard about it by now.
Edit: Does safe mode run the ROM version of the Google Play Services?

snovvman said:
The only update that could have an impact is Google Play Services. I'm on beta 12.5.21. Again, no issues w/ Pixel 2. I assume others don't have issues, we would otherwise heard about it by now.
Click to expand...
Click to collapse
Yeah the only slowdown I've ever had was I think right before the February update. I never restart my phone or let it die so I had been 25+ something days of uptime. Restart was all I needed and it was the only 25+ days uptime that had any slowdown. I'm stock and only beta app I'm running is LastPass.
Sent from my Pixel 2 XL using Tapatalk

My phone lags BADLY when I use Snapchat and facebook.

Considering the affected apps (Google Calendar agenda widget, Lightflow, Playstore "install" process, etc.). What do all these have in common?

snovvman said:
Considering the affected apps (Google Calendar agenda widget, Lightflow, Playstore "install" process, etc.). What do all these have in common?
Click to expand...
Click to collapse
Did you ever figure this out?
I'm still on March and have started having this issue. It's related to charging the device. Whenever I charge (and even after pulling off the charger) Lightflow becomes extremely laggy. Also, installing apps from the Play store exhibits the behavior you described in OP. Interacting with notifications is very laggy as well (i.e. - tap a notification to open the corresponding app, and the notification disappears and nothing happens...then 2 minutes later the app opens). This goes on until a reboot. After that, everything is fine until I charge again. Which, fortunately for me, is only once every 3 days.
Was not having this issue until recently and have been on March for a few weeks.

Str0ntium said:
Did you ever figure this out?
I'm still on March and have started having this issue. It's related to charging the device. Whenever I charge (and even after pulling off the charger) Lightflow becomes extremely laggy. Also, installing apps from the Play store exhibits the behavior you described in OP. Interacting with notifications is very laggy as well (i.e. - tap a notification to open the corresponding app, and the notification disappears and nothing happens...then 2 minutes later the app opens). This goes on until a reboot. After that, everything is fine until I charge again. Which, fortunately for me, is only once every 3 days.
Was not having this issue until recently and have been on March for a few weeks.
Click to expand...
Click to collapse
I have not, unfortunately. The Playstore app install has, for the most part, resolved itself, but the hang does return from time to time. Lightflow is still a problem. I wrote the dev but there is no response. The other issue is the Google Calendar agenda widget. It takes 10-20 minutes to load on reboot. Mind you, the month widget works just fine.
Take a look at these threads:
https://forums.androidcentral.com/moto-z-force/803793-calendar-widget-doesnt-load-data.html
https://forums.androidcentral.com/google-pixel-pixel-xl/855985-screen-widget-loading-8-1-boot.html
They describe similar issues. I've also found other, similar observations but with no resolve.
I am on April and have tried a custom kernel. No joy.
Edit: Since I cannot test the calendar widget nor Lightflow in Safe Mode, I don't know if it actually is a system-related issue.
Edit 2: I do see a strange connection with charging, especially with Playstore installations and lags.

snovvman said:
I have not, unfortunately. The Playstore app install has, for the most part, resolved itself, but the hang does return from time to time. Lightflow is still a problem. I wrote the dev but there is no response. The other issue is the Google Calendar agenda widget. It takes 10-20 minutes to load on reboot. Mind you, the month widget works just fine.
Take a look at these threads:
https://forums.androidcentral.com/moto-z-force/803793-calendar-widget-doesnt-load-data.html
https://forums.androidcentral.com/google-pixel-pixel-xl/855985-screen-widget-loading-8-1-boot.html
They describe similar issues. I've also found other, similar observations but with no resolve.
I am on April and have tried a custom kernel. No joy.
Edit: Since I cannot test the calendar widget nor Lightflow in Safe Mode, I don't know if it actually is a system-related issue.
Edit 2: I do see a strange connection with charging, especially with Playstore installations and lags.
Click to expand...
Click to collapse
The only widget I use is the Fit step counter. That has always taken a minute or so to even show up on the home screen after a boot (8.0/8.1) for me. I don't feel it's related to my issue as that has persisted through all software versions I've used so far.
I'm beginning to think the lightflow issue is just that....a lightflow issue and it is affecting notifications, globally. And, it is somehow tied to charging state. I've seen lightflow do some weird crap over the years. I remember a simple gmail update caused lightflow to send my then device (htc tbolt) into constant reboots.

Str0ntium said:
I'm beginning to think the lightflow issue is just that....a lightflow issue and it is affecting notifications, globally. And, it is somehow tied to charging state. I've seen lightflow do some weird crap over the years. I remember a simple gmail update caused lightflow to send my then device (htc tbolt) into constant reboots.
Click to expand...
Click to collapse
Well sir, you are EXACTLY correct. Based on your ideas, I disabled Lightflow and rebooted my phone. All was back to normal. Once I re-enabled LF, the problems came back. Thank you very much for pointing out your observations. I would have not considered LF to be the source of the problem, but it is now so clear. Again, I can't thank you enough (I'll "thank" both of your posts)!
I will try clearing the LF data to see if that solves the problem. I will report back.

snovvman said:
Well sir, you are EXACTLY correct. Based on your ideas, I disabled Lightflow and rebooted my phone. All was back to normal. Once I re-enabled LF, the problems came back. Thank you very much for pointing out your observations. I would have not considered LF to be the source of the problem, but it is now so clear. Again, I can't thank you enough (I'll "thank" both of your posts)!
I will try clearing the LF data to see if that solves the problem. I will report back.
Click to expand...
Click to collapse
Light Manager might be a viable alternative for you if LF doesn't play nice for you. Works great without any lag issues :good:

snovvman said:
Well sir, you are EXACTLY correct. Based on your ideas, I disabled Lightflow and rebooted my phone. All was back to normal. Once I re-enabled LF, the problems came back. Thank you very much for pointing out your observations. I would have not considered LF to be the source of the problem, but it is now so clear. Again, I can't thank you enough (I'll "thank" both of your posts)!
I will try clearing the LF data to see if that solves the problem. I will report back.
Click to expand...
Click to collapse
Well, that's not exactly the news I wanted to hear lol.. I've tried light manager before and didn't like it at all. Light flow is kind of a crucial app for me. I guess I will just charge the device in the off state. Everything works fine until it gets charged overnight.
Now that you've sort-of confirmed light flow as the cause, I wonder if it might have to do with the charge state hooking. Do you have charging/charged profiles set up in light flow? If it's as simple as removing those, I could deal. I'm at work so can't really afford to test it right now.

Str0ntium said:
Well, that's not exactly the news I wanted to hear lol.. I've tried light manager before and didn't like it at all. Light flow is kind of a crucial app for me. I guess I will just charge the device in the off state. Everything works fine until it gets charged overnight.
Now that you've sort-of confirmed light flow as the cause, I wonder if it might have to do with the charge state hooking. Do you have charging/charged profiles set up in light flow? If it's as simple as removing those, I could deal. I'm at work so can't really afford to test it right now.
Click to expand...
Click to collapse
I first endured the slowness and made a LF backup. Then 1) I cleared the data and rebooted the phone without launching LF, the phone restarted normally, calendar widget was fine, 2) launched LF and granted notification access, restarted phone, all was well, 3) restored from LF backup, restarted, all is still well and LF launches fine. Corrupted data?
At least I'll know what to do next time. For your similar issue, just make a LF backup, clear data, reboot, restore, and hopefully it resolves the issue for you. Let me know.
Edit: Regarding your question on charge state hooking--I had LF running for many years and on the Pixel 2 XL since new. The problem only surfaced recently. My Pixel 2 is also fine. I would guess that there was bad data somewhere. Like I wrote above, a reset/restore brought everything back as before.

snovvman said:
I first endured the slowness and made a LF backup. Then 1) I cleared the data and rebooted the phone without launching LF, the phone restarted normally, calendar widget was fine, 2) launched LF and granted notification access, restarted phone, all was well, 3) restored from LF backup, restarted, all is still well and LF launches fine. Corrupted data?
At least I'll know what to do next time. For your similar issue, just make a LF backup, clear data, reboot, restore, and hopefully it resolves the issue for you. Let me know.
Edit: Regarding your question on charge state hooking--I had LF running for many years and on the Pixel 2 XL since new. The problem only surfaced recently. My Pixel 2 is also fine. I would guess that there was bad data somewhere. Like I wrote above, a reset/restore brought everything back as before.
Click to expand...
Click to collapse
Yeah, I went through all of that last week. I went from the newest version back to the last known stable (for me) version. I always keep a back up of the settings txt file as well as a TiBu file. My current version (previous stable) was installed from scratch.
Everything was fine for the first two or so weeks on March build. This just started after I applied the libs from the multi-touch fix. I removed that as I had hoped it would be related to the phantom swiping when scrolling (I don't game on the device) but it doesn't seem to be related the swiping. At first I thought that module was causing the issue as it started the day or two after adding it. That's the only change I have really made since setting up the March build. Not sure why it would just start out of the blue when it had been working fine for at least 2 weeks before.
I'll try some things over the next few days. First thing is going to be removing the charging profiles from light flow and see if that makes a difference.
Have you tried hooking up the charger since cleaning your data?
If removing charging profiles doesn't help, I'm going to reflash March build (removing -w from batch file) to both slots, redo twrp, elx kernel, magisk. I may do this anyway, even if removing charging from light flow fixes it.

Str0ntium said:
I'll try some things over the next few days. First thing is going to be removing the charging profiles from light flow and see if that makes a difference.
Have you tried hooking up the charger since cleaning your data?
If removing charging profiles doesn't help, I'm going to reflash March build (removing -w from batch file) to both slots, redo twrp, elx kernel, magisk. I may do this anyway, even if removing charging from light flow fixes it.
Click to expand...
Click to collapse
I have connected/disconnected a generic charger twice and once connected to a PC (slow charge). So far, still all good. The problem began in late/mid March. The April patch did not solve the problem. I am using Magisk. Stock/ElementalX made no difference. I will see if the problem resurfaces.
The likely cause that there are code issues with LF. I had LF slow down regardless of charger connection so I'm curious to know if removing the charging hooks help. I'm on the latest version.
Just curious--what not go to the April patch?

snovvman said:
I have connected/disconnected a generic charger twice and once connected to a PC (slow charge). So far, still all good. The problem began in late/mid March. The April patch did not solve the problem. I am using Magisk. Stock/ElementalX made no difference. I will see if the problem resurfaces.
The likely cause that there are code issues with LF. I had LF slow down regardless of charger connection so I'm curious to know if removing the charging hooks help. I'm on the latest version.
Just curious--what not go to the April patch?
Click to expand...
Click to collapse
I'm an "if it ain't broke" kinda guy. Everything except the phantom swipes has been perfect on March build. At this point I'm convinced the swiping issue is due to LG and therefore nothing to be done about it. I'm getting too old to flash a new ROM every week like I used to

Str0ntium said:
I'm an "if it ain't broke" kinda guy. Everything except the phantom swipes has been perfect on March build. At this point I'm convinced the swiping issue is due to LG and therefore nothing to be done about it. I'm getting too old to flash a new ROM every week like I used to
Click to expand...
Click to collapse
Gotcha! Since my last post, I have connected/disconnected charger five times. Each time with several minutes of wait time in between. I have also tested functionality while the charger is plugged in. All still good.
One side note, I have noticed, with many phones, that strange and undesirable things happen when you connect the charge while the phone is mid-boot. In my situation, the LF problem may have surfaced because of that.

snovvman said:
Gotcha! Since my last post, I have connected/disconnected charger five times. Each time with several minutes of wait time in between. I have also tested functionality while the charger is plugged in. All still good.
One side note, I have noticed, with many phones, that strange and undesirable things happen when you connect the charge while the phone is mid-boot. In my situation, the LF problem may have surfaced because of that.
Click to expand...
Click to collapse
Well for me I was just charging normally. Hope it holds up for you. If so I'll do a clean install again and setup from scratch.

Try clearing excess text messages and cache for apps. A friend of mine had thousands of text messages and social media buildup, and the phone got very slow and buggy, especially the camera app. After deleting thousands of texts, switching to Textra, clearing the app cache for frequently used apps, the phone is back to very fast again.

wifi and bluetooth won't turn on

My wife's pixel 3xl recently started having this problem. It is completely unmodified stock, locked bootloader, reports it is on the latest update.
Wifi and bluetooth won't stay on. A reboot fixes it, but eventually they shut off again. Sometimes it lasts a few days after a reboot, sometimes less. Once they shut off, they can't be turned back on again. You can try and toggle them on with quick settings, but it doesn't actually work. Only a reboot fixes it.
I tried a factory reset a couple of weeks ago. That seemed like a cured it for about a week, but it's back.
It's a pretty aggravating problem. If I can't fix it soon, she's probably going to end up with a new phone. Anyone else seen this, or better yet, know a fix? I've done some searching in the forum and on the web in general, but I didn't find anything informative other than one webpage that talked about some pixels, especially the 4a, having problems like this after updating to android 11.

Well, I got fed up with android 11, and downloaded the last android 10 factory image.
After flashing that and factory resetting, I'm having different problems. Now the phone takes like 5 seconds for the screen to come on when waking with the power button.
I'm starting to think this thing is cursed, or has hardware problems. Anyone have any ideas?
Edit: I have no idea why this would make a difference, but I switched unlocking method from swipe to none this morning and that eliminated that long wake-up delay. It's back to fast and responsive like it should be.
Now to see if wifi and bluetooth are going to behave better on android 10.

jason2678 said:
Well, I got fed up with android 11, and downloaded the last android 10 factory image.
After flashing that and factory resetting, I'm having different problems. Now the phone takes like 5 seconds for the screen to come on when waking with the power button.
I'm starting to think this thing is cursed, or has hardware problems. Anyone have any ideas?
Click to expand...
Click to collapse
You can try wakelock V3 and select 'CPU' and set as autostart on boot in the app settings to see if it wakes faster.

I can't believe that it worked for me. I was facing the same issue and I got frustrated. I was just serching and came across a reel showing fix regarding it. In that video person switched off his pixal tapped it on his leg (backside of phone) and then started it and keep tapping it on his leg while starting. It's really weird but I gave it a try. And can't believe it worked. Wife and Bluetooth both fixed now. Getting "on" now.

Question Every 3-4 days I must reboot

Ok, so like the title says, every 3-4 days I must reboot my phone.
When I play games, the game icon will show up in the lower right corner, I have everything for the game stuff turned off. I can click on the icon and it will ask me to turn on. I back out and it's gone for a few minutes. Mostly until I swipe back, then it will reappear. I can reboot the phone and it will work fine again for a another 3-4 days.
There are other instances that force me to reboot as well, one happened last night. I was scrolling through a local news app and the touch stopped working. I could not scroll up or down, and swiping back did not work. I had to lock the phone and just as the screen went dark, the phone scrolled in the directions I did and it backed out. This only happened when I hit the lock screen.
Is there a fix for this? Has anyone else experienced this?

My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.

thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Mine does not reboot or shutdown on it own, not once... I have to reboot every so often to keep it functional.

@thepersona My phone doesn't auto reboot either. I'd say do a backup and run https://flash.android.com/welcome to fully Factory Reset the phone and see if that helps (Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Like the OP I do have to reboot my phone about every 3-4 days, but I don't attribute that just to Google Android, coders have become lax on how tight they keep their code, and I say that because in Windows 10 and Windows 11 you have to reboot every few days as well or see an increase in weird issues.

card13 said:
@thepersona Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Click to expand...
Click to collapse
Just to clarify this, most carriers prevented the December update from releasing as Google has asked them to prevent it from going through, primarily due to an issue with calls dropping.
I always manually update my phone, however, I noticed the call dropping bug one day for about an hour straight.
But aside from this meaningless info, I agree with what you said: Attempt a factory reset and see what happens. I turn my phone off every night and charge it, so I don't notice any issues similar to what OP has mentioned.

thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!

wilpang said:
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
Click to expand...
Click to collapse
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol

thepersona said:
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
Click to expand...
Click to collapse
Yeah I was lucky and it was only once a week which was tolerable!
Something is definitely not right, hopefully is not a dodgy app but that would be preferable than something unfixable.

Ok guys you are missing my point and question. I DO NOT have the random reboots most have, but I have other issues that no one seem to have. Example, I listen to Spotify over night, I fall asleep to music, but 2 days ago it would randomly pause. At first I thought it was do not disturb that I just turned on, on my watch. It was not. Then I thought I may have been hitting my watch, I took it off and it still paused. I rebooted my phone and it's been fine since, no random pauses. Another example is, I play a game but I have the game dashboard turned off, but there times where the icon will pop up in the lower right. When I go into the settings for it, it shows it's off. When I go back to the game the icon is gone for a few minutes then it reappears. The only way for me to get it to stop showing for a few days is to reboot my phone.
I know you shouldn't have to reboot your phone every few days, and by few I mean sometimes it's 3-4 times a week. That tells me something is wrong.

Are you on the November or December update?
If November, I would try the December one.
Rooted or not rooted?
Either way, I would try a factory refresh and don't restore your apps from backup. Manually install only your most critical apps and see if you have the problem. Even better would be not install any additional apps at all and see if the problem happens. If it doesn't happen, install another small group of your most important apps and test again for long enough. Etc.
If you try thre update and/or factory reset, you could try restoring your cloud backup as normal and see if you have any problems still, but if you do, be prepared to factory reset and try like I mentioned in the above paragraph.
Until you can narrow down if the phone has this problem on the December update before you even change settings and add your favorite apps, then you won't know if it's the phone itself (possibly hardware problem), an app you have installed, a problem particular to a combination of factors including if you're on the November update, or what.
Good luck! Please let us know what happens.

I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.

darbylonia said:
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
Click to expand...
Click to collapse
Awesome!!! This is the kind of news I like to hear..... Just waiting for att to send it through. I checked this morning as my work Verizon Samsung phone got an update.

Question A13, another "Am I the only one?" Thread!

Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.

You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s

nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).

Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.

Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.

jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.

roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?

For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.

Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/

jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.

Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!

roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".

jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.

Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).

I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.

96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.

jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.

Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.

jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.

96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.