Related
*Originally I posted this in the Help section of the G3 forums but got no help, so I am posting this here*
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.
I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.
GuyInTheCorner said:
I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.
Click to expand...
Click to collapse
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/
iDefalt said:
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/
Click to expand...
Click to collapse
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?
Sounds like your phone is superstitious
Sent from my LG-D855 using XDA Free mobile app
GuyInTheCorner said:
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?
Click to expand...
Click to collapse
Yeah I thought that but I wanted to know if anyone here has had the same issues.
iDefalt said:
Yeah I thought that but I wanted to know if anyone here has had the same issues.
Click to expand...
Click to collapse
the WiFi issue seems like its something to do with battery saver/quiet mode (to me anyway). Unless your router is kicking the phone off at that time?
EDIT:
oh and regarding the Voice Mate issue it could be either the jack or your headphones?
Please do not double post. It is a violation of Forum Rules.
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer
Click to expand...
Click to collapse
This thread is closed. Your original will remain open here: http://forum.xda-developers.com/lg-g3/help/couple-weird-glitches-occuring-help-t2974077
Some background info.
I bought my pixel XL from the Google store and I believe it came with the 63L build out of the box. I have since made it a point to completely wipe and fastboot flash the latest image Everytime an update is release, right now I am on the 26U build. The only thing I have done to my phone (and these bugs happen before and after) is bootloader unlock and root.
The bugs.
Every once in a while, my volume controls will quit working. I notice it happen more if I cast to my Chromecast and play a song or video (seperate) on my device. I'll hit the volume button and literally nothing will happen. To fix this I usually have to turn the display off, wait a few seconds, wake it back up, then the controls work fine again. I do not believe it is a hardware issue because i can fix it Everytime it happens.
The second bug, probably the most annoying, is that my nav bar will become completely unresponsive occasionally while in landscape orientation. Say I'm watching a video on YouTube in full screen, if I swipe to pull out my nav bar and hit the home/recent/back button, nothing will happen. I will see the animation however no vibration (feedback) or a action occurs.
This happens in games, YouTube, web browsers, doesn't matter as long as my phone is in landscape mode. Also note that when this happens, my device refuses to rotate back to portrait. This leaves my only solution (same as the volume bug) to turn off the display, wait a few seconds, and then I back on. Sometimes, however, this don't even work, and I'll have to jump straight to settings from my lockscreen to force the phone to portrait where the functionality of the nav bar returns.
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
I've been discovering my pixel has many small issues that no one else has. Such as the horrible transfer speed explain in my earlier thread, these bugs above, refusing to charge when the device is off, etc.
Has anyone had similar problems?
@noidea24,
I've had none of those issues. In fact, my Pixel XL has been flawless.
Not good. I guess I'm going to try and force a RMA.
noidea24 said:
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
Click to expand...
Click to collapse
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
muzzy996 said:
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
Click to expand...
Click to collapse
A factory reset is far from a pain in the ass, and yes, i have done it many times. the only things that makes it suck is when i have to transfer files back to my device because (as mentioned) i have terrible transfer speed from pc to device.
i have literally done everything i can to make this devices worth the price, and things are only getting worse. Since the post (later that night) i factory flashed once again, and re locked the bootloader. No root, No extra apps, hell, the only apps i had on my phone to begin with were facebook messenger, and that pixel car racer, i dont use anything else. ive had an even worse bug come in where my phone completely freezes when opening google camera and swiping to the video section. ill have to hold power until it force resets.
ive been with xda since my Motorola droid, Ive built roms for the community for my lg g2 and my nexus 6. hell, i even built kernels for my 5x (not public), so im a little past your average user complaining about some things that dont work due to user error. these are legitimate device flaws and malfunctions, and i was simply asking if anyone else has experienced them. and since it seems no one has, i have deemed my device faulty. now i have to come up with $600 for a service hold to get it replaced.
My experience with Googles first official flag ship has been pathetic, and im hoping that this replacement device i get (eventually) will persuade me not to go back to my 6p.
Well if that's the case then yeah I hope a replacement device will solve your issues. Sounds like it will.
Didn't mean to rile you up, just looking for clarity.
Good luck!
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.
Some info: Pixel XL, one-year-old, rooted with Magisk, android up-to-date version 9, Build number PPR2.181005.003
Some weeks ago I started to see some weird behaviour related to sound. First, while listening to Spotify and Google Podcasts (from now on called "The Apps"), the phone would simply stop producing any sound through the headphone (or speakers when the headphones are then unplugged). A restart would fix it until the next random time it would happen again.
After a while, I've decided to factory reset the phone and reinstall the Android system from scratch and root it again (I've been doing this kind of stuff for years now, so I'm pretty knowledgeable about these procedures), to no avail. The problem was still there.
I've started to try to pinpoint what the main problem would be, and then I've started debugging other stuff. What I've found is:
- If I restart the phone and immediately try to play Spotify or Google Podcasts, it will not work and only a restart will fix it.
- If I restart the phone and wait a few minutes (around 5 minutes) everything works, until the next random failure.
- After a restart, my widgets on the home screen will take a few minutes to load (Google Calendar and The Weather Network)-- if I try The Apps before that, no sound will come out through the headphones (or speakers if I disconnect the headphones)
- Sometimes the sound will come out through the phone's speakers, even if the headphones are connected. Only a restart will fix this.
- Sometimes a loud cracking sound will come through the headphones and after that, no sound is played whatsoever by the phone -- a restart fixes this.
- Both The Apps would randomly stop playing (as if the pause button is pressed). Pressing the Play button again restores the sound, but with different volume level. If it was lower, it will become louder, and vice versa. I didn't test this without the headphones as I would need to isolate myself from the world LOL.
- No sound is produced during phone calls either. A restart fixes this until the next random failure.
- The volume indicator will randomly lag to display after pressing the volume buttons.
- The volume indicator will appear randomly and change small amounts (up or down) while I'm using the phone.
I am slowly removing less-used apps to try to pinpoint which one could be the offending factor, with no luck so far.
I've unrooted my phone today to try and see if this has any effect on those problems (no effect).
Any ideas what I can try next? Any idea what can cause these problems?
daniel3ub said:
Some info: Pixel XL, one-year-old, rooted with Magisk, android up-to-date version 9, Build number PPR2.181005.003
Some weeks ago I started to see some weird behaviour related to sound. First, while listening to Spotify and Google Podcasts (from now on called "The Apps"), the phone would simply stop producing any sound through the headphone (or speakers when the headphones are then unplugged). A restart would fix it until the next random time it would happen again.
After a while, I've decided to factory reset the phone and reinstall the Android system from scratch and root it again (I've been doing this kind of stuff for years now, so I'm pretty knowledgeable about these procedures), to no avail. The problem was still there.
I've started to try to pinpoint what the main problem would be, and then I've started debugging other stuff. What I've found is:
- If I restart the phone and immediately try to play Spotify or Google Podcasts, it will not work and only a restart will fix it.
- If I restart the phone and wait a few minutes (around 5 minutes) everything works, until the next random failure.
- After a restart, my widgets on the home screen will take a few minutes to load (Google Calendar and The Weather Network)-- if I try The Apps before that, no sound will come out through the headphones (or speakers if I disconnect the headphones)
- Sometimes the sound will come out through the phone's speakers, even if the headphones are connected. Only a restart will fix this.
- Sometimes a loud cracking sound will come through the headphones and after that, no sound is played whatsoever by the phone -- a restart fixes this.
- Both The Apps would randomly stop playing (as if the pause button is pressed). Pressing the Play button again restores the sound, but with different volume level. If it was lower, it will become louder, and vice versa. I didn't test this without the headphones as I would need to isolate myself from the world LOL.
- No sound is produced during phone calls either. A restart fixes this until the next random failure.
- The volume indicator will randomly lag to display after pressing the volume buttons.
- The volume indicator will appear randomly and change small amounts (up or down) while I'm using the phone.
I am slowly removing less-used apps to try to pinpoint which one could be the offending factor, with no luck so far.
I've unrooted my phone today to try and see if this has any effect on those problems (no effect).
Any ideas what I can try next? Any idea what can cause these problems?
Click to expand...
Click to collapse
I'm sure you have already looked into this - but just in case....make sure that the "Apps" are NOT set to Optimize Battery nor to Restrict Background Usage. There was another thread recently about a user having Spotify stop playing randomly for them and the issue was the app was set to Restrict Background Activity. Good luck!
sb1893 said:
I'm sure you have already looked into this - but just in case....make sure that the "Apps" are NOT set to Optimize Battery nor to Restrict Background Usage. There was another thread recently about a user having Spotify stop playing randomly for them and the issue was the app was set to Restrict Background Activity. Good luck!
Click to expand...
Click to collapse
Thanks for the confidence you projected on me LOL, I had NOT looked at it! Indeed, both apps are set to "optimize battery". I'll change this setting and give it a go.
Thanks!
sb1893 said:
I'm sure you have already looked into this - but just in case....make sure that the "Apps" are NOT set to Optimize Battery nor to Restrict Background Usage. There was another thread recently about a user having Spotify stop playing randomly for them and the issue was the app was set to Restrict Background Activity. Good luck!
Click to expand...
Click to collapse
I must say a LOT of the related problems are, if not completely, at least partially solved. I've seen way less problems since I disabled the battery optimization for Spotify and Google Podcasts.
Thank you so much!
I'll keep tracking them and running some more tests just to be sure, but it seems this was the main issue here.
Amazing how one single app and setting can bring a phone to an almost useless state!
Hi all,
Hoping someone brighter than me can figure this sound issue out.
THE PROBLEM:
Half of my sounds don't work, rendering my phone useless in the current state. As the title says, Ring, Notification, & Alarm sounds do not work. You know, as in the important stuff that makes your phone, a phone? And makes you wake up in the morning? None of these respective sliders under Sound & Vibration settings make any noise when making adjustments. By contrast, my Media and Call volume sliders DO make noise when adjusting. And sure enough, once on a phone call, I hear things just fine (Call). And YouTube, Spotify, et al. (Media) also work just fine.
Because some sounds work but others don't, this has to be a software issue, right? This would be easy if it was hardware and 0% of sounds worked, but nope, it's partial.
BACKGROUND:
This pixel 3 xl is relatively new to me, but has ran A10 and A11 with a few different ROMs with 100% of sound working flawlessly. But out of nowhere, sounds suddenly stopped working correctly as described above. And it didn't occur immediately or shortly after a new rom flash or update or anything like that. Just stopped working, months into a well-running ROM.
I've tried a couple different ROMs now to fix the issue from a completely clean install (/format data + flash latest google factory image as 1st step) but none have fixed the issue. Specifically, pixeldust (A11) and evolutionX (A11) were my latest troubleshooting attempts with no avail. Pixeldust was the ROM that was formerly working and then after months of 100% sounds working, suddenly stopped.
It's odd that searching throughout the ROM threads that no one else seems to be having this issue. Again, this would be easy if it was a hardware failure. But that doesn't explain how it works for Youtube/Spotify but not for other things, so it has to be software.... I think?
I figured I'd start a thread here rather than start posting in each and every ROM I've tried to troubleshoot this. Thank you!
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
xdateddybear said:
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
Click to expand...
Click to collapse
ManImCool said:
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
Click to expand...
Click to collapse
I think I may have finally found the solution!! Sometimes it's the simple things in life that work, rather than reflashing a billion different ways that finally gets things working again.
In this case, I simply cleared the cache and storage for the 'Sounds' apps under Settings -> Apps & notifications -> See all apps -> Click 3 dots in upper right corner -> Show system. Then, I deleted cache and storage for TWO apps, both called 'Sounds' with 2 different icons. I'm not sure which is the system app and which is not nor do I know if clearing only one of them was necessary, but this is what has worked for me and has survived several restarts thus far. Good luck!