Related
Weird problem, had my Evo for a couple of days now and everything seemed fine for the first day but now when I run certain apps like google maps for pandora my Evo will reboot. This doesn't happen all the time but will eventually happen after an hour or two of usage. I did buy a case for my phone, maybe it's a heat issue?
taziz23 said:
Weird problem, had my Evo for a couple of days now and everything seemed fine for the first day but now when I run certain apps like google maps for pandora my Evo will reboot. This doesn't happen all the time but will eventually happen after an hour or two of usage. I did buy a case for my phone, maybe it's a heat issue?
Click to expand...
Click to collapse
I've had this happen on my hero. It is just clearing memory are you using autokiller ? It started on my hero when using autokiller. It's not a heat issue the led will flash red and green when the phone is hot.
I'm using advanced task killer but I don't think it's set to autokill apps. A hard reset has seemed to fix this issue for now, how do I ensure it doesn't happen again in the future?
It might help to check your preset in autokiller and set to moderate or optimum but some apps use more memory than others so you might see it from time to time. I still use autokiller set on extreme and would only see that once every week or two on the hero. So it's not that big of a deal. You could just uninstall it if it bugs you or to see if it stops. I have not seen it on my evo yet but I am just rooted no custom ROM yet (Waiting for fresh ROM with espresso theme). That might help contribute to it as well.
taziz23, I don't mean to hi-jack your thread but I've been chasing down the cause of random reboots also. I've been searching around for someone with a similar issue and all I've been finding are people talking about the reboot loop caused by an exchange account. I'm not using exchange at the moment so I know that's not what's affecting me.
It sounds similar to what you're talking about. About 30 minutes to an hour apart regardless of whether I'm using the phone or not. It just did it while sitting on the desk next to me with the screen off for at least 15 minutes.
I've hard reset a few times to see if it was related to the OTA, and turns out it happens to both .1 and .6
I've found out that if I don't associate my google account during the initial setup (or any other accounts like facebook, twitter, etc.) it doesn't seem to reboot anymore. Once I do setup an account and set it to auto sync, I start seeing the reboots happening. So I've been playing with different combinations of disabling calendar sync, contacts sync, etc. to narrow it down but so far, I've come up with nothing.
I've even exported my contacts to a .cvs file using my desktop browser and cleaning out any of the <HTCDATA> stuff that links facebook and twitter to make sure nothing is corrupt and reimported them, but as the reboots are still happening, it looks like that might rule out contact corruption.
I had made it through most of Friday before the reboots started. I recall installing the update to Facebook and TasKiller just before it started happening, but have hard reset since then and have not installed either of these again.
Has anyone else seen anything like this?
Two words: Kernel Panic.
Actually, that's just a guess. I'd imagine anything else would cause some kind of error message to show up like a force close for example.
It has happened with my Evo a few times so far. It also happened with my Hero when I use to use that.
It's probably just a module misbehaving which confuses the OS and causes the kernel panic, so I imagine it's nothing more than a software bug.
Yea... I was thinking some KP's might be happening, but if the release build is dated in April, I must have some fluky hardware right?
Maybe I'll run an `adb logcat` and just wait.
I remember the hard crashes on some of the early donut and eclair builds for the Vogue (CDMA Touch) and these are pretty much the same deal. Just drops out and goes straight to the bootsplash.
Regardless of the phone or OS, I've seen this happen on all the phones I've owned. Android is at least open to allow normal people to debug and fix these problems though.
Me too!
I had a seemingly random reboot happen today on my EVO as well... then it happened again.
Both times, I had Waze and Pandora running and was about 30 seconds into a phone call.
Advanced Task Killer is installed, and is set to kill "when screen off".
I'm pretty new to Android based phones, so I'm not even sure where to start with troubleshooting... but found this thread, and thought this info may help.
Krissy
(P.S. I love this phone so much, right now - I don't even care that it has rebooted on me twice in the middle of a phone call... but eventually the honeymoon will be over, and I'll want this figured out. LOL)
I am having an exact same ISSUE i got it from google I/O its just happened suddenly while you are using it I have no Idea .. Search is also not that great .. Platform need lot of work until it get mature .... I was definately enjoying 1st 2 weeks but not anymore its just killing me now ... Issues after Issues so many Bugs I have start noticing now.. I am not complanning but its just not solid they need to fix this asap... I was enjoying Pre it was slow but I like that OS .. not too much buggy... some apps just Crash randomly .. I was huh .. and its doing more and more now ..
After my hard reset a couple of days ago I haven't had any reboots. I do think it was related to the task killer I think it might have caused some data corruption possibly when killing an application. I set the auto killer to safe in the meantime. If it stats happening again I'll try uninstalling the task killer before I hard reset.
I had the same thing happen, but only once. I was using google maps I think. I also have advance task killer installed. Does the ignore list in advance task killer and setting it to auto kill, kill everything except for what's in the ignore list?
I'm not sure but I did notice that most of my reboots were happening when running google maps..
My Evo rebooted most days 4 or 5 times, day or night, in use or not. The store where I purchased it refused to replace it since I couldn't duplicate the problem to the local technical store. They acted like I needed someone to talk to and not like I had a problem needing resolution. After about 20 calls to customer support they told me to return it where I purchased it and they're sending me out a new one. Apparently no one at Sprint has ever heard that there's this issue. Mine was stock. Period.
I have had some reboot issues that I can't explain. I removed Advance Task killer and it seems to happen less frequent. Maybe once every two days, but never during a call. Waiting to see if this stops with Froyo.
Used to have similar, but less frequent, reboot issues and an occasional "frozen" screen with my previous Blackberry 8830.
I've only had it reboot once or maybe twice for no reason but When I use advanced task kill I almost expect it to happen. And I only use it to kill whatever app I was just using and any other ones Ive downloaded that have no business running.
I have had the same issue, only I am using the full version of Memory Booster..I am going to uninstall it and see if that helps, I also notice that my phone was very hot. It rebooted about 3 times before letting me use the phone again.
Any other suggestions?
Sent from my PC36100 using XDA App
Has anyone else been experiencing random applications opening on the device after the Oreo Update? I have the VZW Varient so i dont know if that makes a difference but im interested to know others feedback
I'm on T-Mobile variant as well as on oreo and have not had such an issue. Which applications have been doing such things?
i've got the similar issue for my z2f EU (xt1789-06) and i'n with 7.1.1
app: amazon, yahoo auction JP, chrome
Hmm..I did notice a couple apps do that..
FragmentedLogik said:
Has anyone else been experiencing random applications opening on the device after the Oreo Update? I have the VZW Varient so i dont know if that makes a difference but im interested to know others feedback
Click to expand...
Click to collapse
I've noticed it a few times. Nothing consistent. Probably just the Chinese government making tiny mistakes
Randon apps
Yes im experiencing the same problem with apps just opening over the top of what ever your doing. Apps that I haven't used in awhile. Would love to find out what is causing it
I don't have that issue. The application manager will opens temporarily when device reboots. The only bug I have found is that if I try to disable the amazon app my phone instantly reboots.
Sent from my Moto Z (2) using Tapatalk
I am on Sprint and have used this phone since Sept and never have experienced this, not even on Oreo since I updated on Tuesday.
just to add my two cents. I was having this problem. Turned off Moto voice security and I haven't seen this happen again.
I've got it too, can't figure it out. I'll have to try your suggestion JAWheat411, thanks!
Warning for those who are experiencing it: this bug has the capability to bypass screen locks. Opened up an app today that completely bypassed it. Interrupted my Spotify while at work and saw that app open instead. And I am sure that I locked my phone since I leave it on my toolbox, and don't want all my co-workers in my business.
I'm also having this very same problem. I will also try disabling Moto voice security and see if that rectifies the issue. I will report back in about 2 days.
3165dwayne said:
I'm also having this very same problem. I will also try disabling Moto voice security and see if that rectifies the issue. I will report back in about 2 days.
Click to expand...
Click to collapse
lol, I'm late. I still have the problem. It's very random and hasn't been happening as frequently but it still happens.
Same on my Note 8. Very frustrating.
rcbass said:
Yes im experiencing the same problem with apps just opening over the top of what ever your doing. Apps that I haven't used in awhile. Would love to find out what is causing it
Click to expand...
Click to collapse
This is exactly what is happening to my Galaxy S7 edge since the Oreo update. And it goes right past the lockscreen and my security. My phone is always locked, yet I find I've send a nonsense text, or pocket dialed someone, or that a gibberish email is half-composed, or that my calendar is open and a new nonsense event is half-entered. Somehow Oreo is doing all sorts of screen taps, or allowing my phone to wake up and let the pocket do that. And I have enabled the thing about disable touch when in pocket, and I've shut down smart unlock, but that hasn't made a bit of difference.
This problem is happening with my recently bought Moto Z2 Force. It started out random, but then became pretty consistent. I tried disabling the Moto actions (voice command, voice unlock and one button nav) but the problem kept happening afterwards too and became consistent.
It even opened outlook and managed to delete an important email from my boss that I hadn't read yet! Had I not been looking at my phone while it happened, I would have had one unhappy boss.
Even after unlocking the phone, it would just try random unlock codes for a while and eventually lock out the screen for 30 seconds, and then try again. Wouldn't even let me restart the phone. After struggling for more than 2 hours, I was finally able to restart in safe mode and the problem seemed to stop in safe mode. I disabled Moto actions app, deleted data from that app, and also just to be safe removed the HDR+ cam app that I ported. Planning to monitor for a couple of days and see what happens.
This sh!t is just bonkers!
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.
Hello everyone
I have been experiencing force close after force on my Pixel 3xl. I ordered my pixel 3xl on launch day. A week after receiving my device I started to receive sluggish and force close after force in several different apps. I have never experienced android behaving this way. I started to notice that the phone would get sluggish when using Android Messages. When I am receiving an MMS message the phone will lag and then the message will come through. After messages started to act up, other apps such as; Flamingo for Twitter, Instagram and Google plus would force close. For starters I don’t run any app killers, or ram management. I thought the December Pie patch would fix the issue, but I still see it on a daily basis. I reset my phone, and less than a week later, I would see this same behavior. The phone is basically unusable. I contacted Google for an RMA. They processed it and the new phone is still acting this way. This is really odd this behavior would be happening to 2 phones. I have reset the new phone from google once. Not only is this behavior odd, but it would be really hard for me to believe I am the only person experiencing this issue. Thought about rooting it but don't know if that would even help.
Side note: I have noticed when in flamingo for Twitter or Android messages that the phone takes awhile to open or back out of a picture. Sometimes a white space will show near the upper part of the phone (both sides of the notch)
Any help would be appreciated.
kid1da said:
Hello everyone
I have been experiencing force close after force on my Pixel 3xl. I ordered my pixel 3xl on launch day. A week after receiving my device I started to receive sluggish and force close after force in several different apps. I have never experienced android behaving this way. I started to notice that the phone would get sluggish when using Android Messages. When I am receiving an MMS message the phone will lag and then the message will come through. After messages started to act up, other apps such as; Flamingo for Twitter, Instagram and Google plus would force close. For starters I don’t run any app killers, or ram management. I thought the December Pie patch would fix the issue, but I still see it on a daily basis. I reset my phone, and less than a week later, I would see this same behavior. The phone is basically unusable. I contacted Google for an RMA. They processed it and the new phone is still acting this way. This is really odd this behavior would be happening to 2 phones. I have reset the new phone from google once. Not only is this behavior odd, but it would be really hard for me to believe I am the only person experiencing this issue. Thought about rooting it but don't know if that would even help. Side note: I have noticed when in flamingo for Twitter or Android messages that the phone takes awhile to open or back out of a picture. Sometimes a white space will show near the upper part of the phone (both sides of the notch) Any help would be appreciated.
Click to expand...
Click to collapse
Two phones exhibiting the same behavior? It has to be something you are adding (user apps and/or settings) as you set the phone back up. You said "less than a week later" you would see the same behavior- but that means for the first week it was acting normal, correct? Try running the phone in safe mode for a good while and see if the situation changes. If the issue goes away it will confirm it is one or more of your user apps is causing the issue. If it remains the same I would flash a factory image from fastboot mode and let the script wipe the phone (don't edit the script). This is different from a FDR (reset). Then when you set the phone back up add any user apps in stages, allowing a period of time between setting them up. Are there any apps you suspect? Any "non-market" apps? Rooting will not help you, so I would leave that variable out of it until you get the problem sorted.
v12xke said:
Two phones exhibiting the same behavior? It has to be something you are adding (user apps and/or settings) as you set the phone back up. You said "less than a week later" you would see the same behavior- but that means for the first week it was acting normal, correct? Try running the phone in safe mode for a good while and see if the situation changes. If the issue goes away it will confirm it is one or more of your user apps is causing the issue. If it remains the same I would flash a factory image from fastboot mode and let the script wipe the phone (don't edit the script). This is different from a FDR (reset). Then when you set the phone back up add any user apps in stages, allowing a period of time between setting them up. Are there any apps you suspect? Any "non-market" apps? Rooting will not help you, so I would leave that variable out of it until you get the problem sorted.
Click to expand...
Click to collapse
I don't use Facebook or Snapchat, I know those apps are really tough on the ram, so I stay away from those. I don't install apps that aren't from the play store. The weird part is I've installed the same apps from my pixel 2xl. I don't install alot of apps to begin with. Ive researched people having issues with the Android messages app and there is a Google forum for this issue, however I installed Textra and I still see the issue just not as bad. During the last reset, I took days to install flamingo for Twitterand Instagram because I suspected them being the issue. Yesterday, I installed them and I started facing the issue. I uninstalled those 2 apps but the issue persisted. Now, it could be those apps but to me it would be a widespread issue if it we're those 2.
List of apps
Most Google apps. Gmail, maps etc
Instagram
Backdrops
Flamingo for Twitter
Navy Federal
Wells Fargo
Vanguard
Ally
Vip access
Hbo now
Netflix
Showtime
ESPN
Relay for Reddit
Nova launcher
kid1da said:
I don't use Facebook or Snapchat, I know those apps are really tough on the ram, so I stay away from those. I don't install apps that aren't from the play store. The weird part is I've installed the same apps from my pixel 2xl. I don't install alot of apps to begin with. Ive researched people having issues with the Android messages app and there is a Google forum for this issue, however I installed Textra and I still see the issue just not as bad. During the last reset, I took days to install flamingo for Twitter and Instagram because I suspected them being the issue. Yesterday, I installed them and I started facing the issue. I uninstalled those 2 apps but the issue persisted. Now, it could be those apps but to me it would be a widespread issue if it we're those 2.
List of apps...
Click to expand...
Click to collapse
I still believe that because you experience this same issue across two different phones, it is something in your personal setup. No abnormal indications under battery usage or data usage (background or foreground)? As suggested earlier try running in safe mode for an extended period. If the problem is gone, you just work your way through the suspect apps until you find the offending one. You can also try resetting all app settings under System>>Reset options before resorting to a clean flash.
v12xke said:
Two phones exhibiting the same behavior? It has to be something you are adding (user apps and/or settings) as you set the phone back up. You said "less than a week later" you would see the same behavior- but that means for the first week it was acting normal, correct? Try running the phone in safe mode for a good while and see if the situation changes. If the issue goes away it will confirm it is one or more of your user apps is causing the issue. If it remains the same I would flash a factory image from fastboot mode and let the script wipe the phone (don't edit the script). This is different from a FDR (reset). Then when you set the phone back up add any user apps in stages, allowing a period of time between setting them up. Are there any apps you suspect? Any "non-market" apps? Rooting will not help you, so I would leave that variable out of it until you get the problem sorted.
Click to expand...
Click to collapse
v12xke said:
I still believe that because you experience this same issue across two different phones, it is something in your personal setup. No abnormal indications under battery usage or data usage (background or foreground)? As suggested earlier try running in safe mode for an extended period. If the problem is gone, you just work your way through the suspect apps until you find the offending one. You can also try resetting all app settings under System>>Reset options before resorting to a clean flash.
Click to expand...
Click to collapse
I am going to try the safe mode method.
kid1da said:
I am going to try the safe mode method.
Click to expand...
Click to collapse
Think Nova launcher. Back it up, uninstall it completely, then see how it goes.
I agree has to be a user app, my 3xl doesn't exhibit this issue. My crappy banking app does this but its very poorly optimized. App devs need to catch up to 9.0
bobby janow said:
Think Nova launcher. Back it up, uninstall it completely, then see how it goes.
Click to expand...
Click to collapse
I uninstalled Nova Launcher and did see a slight improvement. The issue came back a few days later though.
What about safe mode?
kid1da said:
I uninstalled Nova Launcher and did see a slight improvement. The issue came back a few days later though.
Click to expand...
Click to collapse
It's not Nova Launcher. You mention slow picture access so I would be looking at apps in that direction. Any apps consistently FC more than others? Do you use cloud backup for Photos? Do you have any super large photo speres, panos, or RAW photos on your phone?
Edit: another thought would be to run a quick check on the non-Googly apps for "last updated" timestamp on the Play Store. You may be running an older app that hasn't been updated in years and is written with an outdated API.
v12xke said:
What about safe mode?
It's not Nova Launcher. You mention slow picture access so I would be looking at apps in that direction. Any apps consistently FC more than others? Do you use cloud backup for Photos? Do you have any super large photo speres, panos, or RAW photos on your phone?
Edit: another thought would be to run a quick check on the non-Googly apps for "last updated" timestamp on the Play Store. You may be running an older app that hasn't been updated in years and is written with an outdated API.
Click to expand...
Click to collapse
The only apps force closing more than others are Android messages, flamingo for Twitter, and Instagram. It will start with Android messages, which causes the device to slow down, then the other apps follow by force closing. The device always seems to hang/lag when a group message is coming in. I only back up through Google photos on wifi. I combed through the settings and nothing stands out that could be causing the phone to force close these apps. For now, safe mode has the device working normal.
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.