Related
I've noticed over the past couple of days with my M8 that the notification light doesn't activate for anything but charging. I see that many people with Verizon versions are complaining of the same issue. Is anyone else experiencing this on their's? I already know that the only thing Tmo will tell me to try is a factory reset, or have the phone replaced (both a hassle this far into ownership).
Shift4g said:
I've noticed over the past couple of days with my M8 that the notification light doesn't activate for anything but charging. I see that many people with Verizon versions are complaining of the same issue. Is anyone else experiencing this on their's? I already know that the only thing Tmo will tell me to try is a factory reset, or have the phone replaced (both a hassle this far into ownership).
Click to expand...
Click to collapse
You may just want to RMA it so you have a new phone instead of finding something later down the line thats major. T-Mo will usually send you your replacement first and you mail your messed up one back. You could also just take it back to the store and do an exchange (I think) since it's within the 14 day period.
I've noticed it too. I get the amber light when charging and green when done, but thats it. I feel its more of a software bug than anything to do with the hardware.
Have you checked the "Notification Lights" setting under Display? It lets you choose which actions will activate the light.
That said, I have noticed the light is pretty minimal when compared to the SGS series notification lights. Additionally, I do not see a stock option to change the color of the light but no doubt that will come in time with Cyanogen Mod.
Booted into safe mode, tested the LEDs, they work fine. IMO, its definitely a software issue. Also, not sure if this is for everyone but booting into safemode also hoses your home screens. Now I have to redo all my folders.
SeanFloyd said:
Have you checked the "Notification Lights" setting under Display? It lets you choose which actions will activate the light.
Click to expand...
Click to collapse
I did check and play with that, yes. I even downloaded Lightflow with no success. I'm going to lean toward it being a software issue. Hopefully a patch gets compiled at some point.
small update. I was really wanted the stupid notification led to work. I didn't realize how much I looked at it when I'm at work. So I decided to wipe and start over. I made a nandroid backup just in case nothing worked and wiped. I read around the internet that if you don't log into your google account after the wipe, let it do its stuff that it would work so I did. Before I logged into my google account my wife texted me and bam, it worked. Ok, so far so good. I logged in and it still worked. Well, I don't want to go and redownload all my apps so I went into the custom recovery (Yes, I'm rooted and am using the rom in the development section that is rooted, deodexed and a few more things, but the rest is stock) and restored just the data partition. All my apps came back and the LED stopped. WTF is up with that!? I looked at all my apps and nothing was there that would affect the LED. I decided to use Titanium Backup and got all my apps backed up, wiped again, didn't log in to my google account until after the phone fully booted. Logged in, restored my apps via titanium backup and boom, the led was working and is still working. I also use an app called Helium to keep a few apps backed up to my Google Drive and happened to have my homescreen settings backed up (folders, background, etc) and restored that. All my folders came back and the LED still worked. I now have a working notification LED!
Another small thing too. I noticed that when I let my phone boot up before logging into my account, the experience was a little different. Certain things loaded on the phone that didn't load before. My only thought on that is that I had two Samsung phones before this one that maybe something downloaded from my google account, some setting it kept backed up for me, that broke the LED. If you don't log into the account until after you let it fully boot, there is no option to restore your settings from google. It all starts new.
the backup utility I use is called Helium. You CAN use it without root. YOu have to plug into your computer after each reboot but then it will work without being connected. It'll backup the apps data and restore it after you redownload it from the appstore and can also backup both the app and data. It'll backup the homescreens settings like folders. No, I'm not plugging it but its a huge time saver.
Anywho, I now have a working LED for notifications and that is the process i used. Its annoying but I'm glad it works now. Being able to backup and restore my apps is the only reason I did it. That process can be very long and annoying so being able to restore them all in 3 minutes is the only reason why I did the process.
Hope this helps someone and helps to realize its a software bug and not a physical bug.
My LED is working for notifications I just can't alter the color which is a bummer.
johnomaz said:
small update. I was really wanted the stupid notification led to work. I didn't realize how much I looked at it when I'm at work. So I decided to wipe and start over. I made a nandroid backup just in case nothing worked and wiped. I read around the internet that if you don't log into your google account after the wipe, let it do its stuff that it would work so I did. Before I logged into my google account my wife texted me and bam, it worked. Ok, so far so good. I logged in and it still worked. Well, I don't want to go and redownload all my apps so I went into the custom recovery (Yes, I'm rooted and am using the rom in the development section that is rooted, deodexed and a few more things, but the rest is stock) and restored just the data partition. All my apps came back and the LED stopped. WTF is up with that!? I looked at all my apps and nothing was there that would affect the LED. I decided to use Titanium Backup and got all my apps backed up, wiped again, didn't log in to my google account until after the phone fully booted. Logged in, restored my apps via titanium backup and boom, the led was working and is still working. I also use an app called Helium to keep a few apps backed up to my Google Drive and happened to have my homescreen settings backed up (folders, background, etc) and restored that. All my folders came back and the LED still worked. I now have a working notification LED!
Another small thing too. I noticed that when I let my phone boot up before logging into my account, the experience was a little different. Certain things loaded on the phone that didn't load before. My only thought on that is that I had two Samsung phones before this one that maybe something downloaded from my google account, some setting it kept backed up for me, that broke the LED. If you don't log into the account until after you let it fully boot, there is no option to restore your settings from google. It all starts new.
the backup utility I use is called Helium. You CAN use it without root. YOu have to plug into your computer after each reboot but then it will work without being connected. It'll backup the apps data and restore it after you redownload it from the appstore and can also backup both the app and data. It'll backup the homescreens settings like folders. No, I'm not plugging it but its a huge time saver.
Anywho, I now have a working LED for notifications and that is the process i used. Its annoying but I'm glad it works now. Being able to backup and restore my apps is the only reason I did it. That process can be very long and annoying so being able to restore them all in 3 minutes is the only reason why I did the process.
Hope this helps someone and helps to realize its a software bug and not a physical bug.
Click to expand...
Click to collapse
There was an issue like this with the m7, or at least the sprint version. It was after the first update they pushed, 4.3 maybe, though I'm not sure. If you installed the update you were fine, but if you installed it and then had to do a factory reset, if you signed in on the first boot up, the light wouldn't work. You had to let it boot to the sign in screen, restart, then sign in in order to get it to work right. It was really odd.
So I just got my phone. Do I have to wipe it and start over to get the damn notification light to work?? Kinda irritated...
E30Nova said:
So I just got my phone. Do I have to wipe it and start over to get the damn notification light to work?? Kinda irritated...
Click to expand...
Click to collapse
If its not working, yes. Annoying as hell but I am glad I took the time to do what my above post says. I guess I never realized how much I looked at the light.
Man, it was working for a bit, but only for gmail apparently.
I wonder, do the people that convert to the GPE RUU or flash a GPE rom have the same problem?
Yeah, the LED is definitely won't, but I also think it's a software thing. As long as it lights up when charging, the hardware is working, so... Sense bug. They also don't give you many options in the Settings as someone pointed out. I notice the issue more when using 3rd party apps, the stock Sense apps seem to be mostly working fine.
Remember - if you in any way shape or form are using any part of "do not disturb" - while it's enabled, there are no LED's as well and sounds and vibrations.
Yeah mine only works for charging. I tried restoring fresh (not rooted so didn't do titanium with old settings), however I did restore from HTC Backup. Mostly did it for my text messages. I may decide to restore one more time just to see if it works, but really this is software related. HTC should patch it up.
If anyone is still having this problem, theres an app in the play store that fixes this. Install it, run it once and uninstall. My notification light works perfectly now.
https://play.google.com/store/apps/details?id=de.jannux.switchledon
Hi,
yesterday I switched from Dalvik to ART on my D855 (Germany version, unrooted). Everything worked okay. I used my apps as usual.
Even todays morning I still used Whatsapp, Threema and Swype as my keyboard and some more.
I was in the city with only 2% battery left - no problem I thought. I left the phone on in my pocket until I noticed it turned off. Okay, also no problem.
When I came home, I plugged in the charger, booted the phone and left it charging. Some time later I noticed that some apps were missing. I couldn't find them, so I went ahead into the appstore and there I saw it: They displayed with the button "install" on them. Amongst them: Swype, Threema, Total Pool, aCalendar+.
Now Im wondering: What the heck? Automatically uninstalled apps? I used them before even.
And Im asking myself: Is there something wrong with my G3? Have I gotten a version with some production errors or what? Im so confused as I have never experienced this before. Did you ever experience such a behaviour?
Thanks a lot in advance
bubu. said:
Hi,
yesterday I switched from Dalvik to ART on my D855 (Germany version, unrooted). Everything worked okay. I used my apps as usual.
Even todays morning I still used Whatsapp, Threema and Swype as my keyboard and some more.
I was in the city with only 2% battery left - no problem I thought. I left the phone on in my pocket until I noticed it turned off. Okay, also no problem.
When I came home, I plugged in the charger, booted the phone and left it charging. Some time later I noticed that some apps were missing. I couldn't find them, so I went ahead into the appstore and there I saw it: They displayed with the button "install" on them. Amongst them: Swype, Threema, Total Pool, aCalendar+.
Now Im wondering: What the heck? Automatically uninstalled apps? I used them before even.
And Im asking myself: Is there something wrong with my G3? Have I gotten a version with some production errors or what? Im so confused as I have never experienced this before. Did you ever experience such a behaviour?
Thanks a lot in advance
Click to expand...
Click to collapse
When you switched to art did the reboot process complete on the phone (takes ages!)? Im guessing it didnt and as a result some apps werent optimized for Art.
Ive heard of a few people losing all data and other ussues with apps because of ART process not completing properly or being interupted. Old latent versions of the dalvik app can also somtimes reside in the app folders, making it impossible to reinstall the apps without deleting them manually (Needs root)
Do they work when you reinstall them on ART?
Actually, it did finish. It was charged fully and I let it take its 10-20minutes until it finished. That was yesterday evening. And afterwards I could use every app properly I tried. So there were NO problems. Also this morning, everything running smoothly.
And then, as I told you above: I was in the city, battery running empty which maked the phone shutdown itself. I came home, charged it, booted it and then apps were gone. That was so strange. Hopefully it doesn't happen again.
EDIT: Maybe it took a second reboot until every single app was recompiled and setup properly and the second reboot was only todays morning after the phone running empty. Would that be a possible reason?
EDIT2: Oh, maybe that does NOT make sense as I used those uninstalled apps after the first reboot and before the second reboot todays morning.
My Fire Phone has developed an odd issue. I am hoping something more knowledgable on such matters might shed some light on what to do.
It started occurring a few weeks ago. Many apps would crash a few seconds after opening them. I figured out it appeared to only be apps that have some relationship to Contact data. SUch as WhatsApp, all contact apps, all phone apps, dialer apps, etc. Apps with no association to contact data are fine.
I ended up factory reseting the phone and starting from scratch. Installing GApps, etc., as per originally.
The issue seemed to be fixed. Sigh of relief.
Today I used the phone in the morning, and it was fine. I pick it up to use some hours later in the late afternoon, and the default launcher (which was Arrow Launcher) would crash every two seconds. I couldn't get access to the phone. Rebooting made no difference. I discovered I could still use the double-click on the home button to pull up the carosel, and there could click the system settings. After trying many things, I eventually used that method to uninstall the launcher. I had a few lunchers installed already, so I picked another launcher. The other launchers are all fine, so I thought the problem was solved. BUT when I open any app that accesses contact data it was back to the same old story... it crashes in a couple of seconds. I suspect the Arrow Launcher itself has some feature whereby it access contact data, and that's why it was also crashing every 2 seconds.
I found one other person posting what sounds like a similar issue, back in March. https://forum.xda-developers.com/fire-phone/help/crashing-apps-t3575127
Doesn't indicate what he/she discovered or did to fix it.
Can any suggest how I could trouble shoot this? I am resisting going through the lengthy process of resetting the phone again, and getting it all set up, because I already did that, and the problem spontaneously returned.
Reinstall your rom, search on amazon website
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.
My Pixel 6 Pro has a similar problem ever since the Mar 5 update has been installed. Since then, every phone call I made comes with the non-stop notification tone literally every second. For now, I managed to get around it by enabling the "DND Mode", but it isn't a long-term solution.
Is there a way I can re-apply the same update? or flashing a new one would help?
To be clear, you're saying that you keep getting the notification tone even after answering the call? If so, is it the same as your ringtone?
Is your bootloader unlockable? If so, 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 wouldn't surprise me if that doesn't fix the issue, however. Have you tried rebooting? Maybe clear the cache and app data for the Phone app (but then you'd have to re-customize the settings for the phone app to your preferences).
I'm not on the March update, but I also don't receive many phone calls anyway.
that notification tone, during normal time, represents incoming message. It is very short, unlike a ringtone..
Tried rebooting and clearing cache and app data of the Phone app. In fact, that notification could likely come from anything like WhatsApp, Messenger, Twitter...
I noticed that the repeating tones would not happen if the phone is on silent mode. So for now this is my workaround.
Very interesting, and strange. There have been settings in some OEM's phone apps you could enable to get notification tones at regular paces - usually once a minute - while on a phone call, but the issue on yours is only similar since it's constant / every second.
I stick with my recommendation of clearing the app cache and data for the Phone app. I also assume you're using the stock Phone app that Google provides.
In my previous phone (OnePlus 6T), the very same tone happens once in a while, but only at the moment an incoming message arrives. Pretty sure I am not getting a new message every second this time around, and I think it was triggered by apps other than the Phone app. I just noticed that the same symptom showed up when I tried to play video clips from certain apps as well.
And yes, I am using the stock Phone app.
Sounds like a factory reset and only selectively installing and configuring apps, or trying to figure out which app is causing the issue.
If you factory reset, I would first not even restore any apps at all, so you can verify if you have the same problem without any third-party apps installed at first. I would suspect you won't have issues then. And then when you install apps, do it in groups of your most important ones first, maybe at the most 10 at a time, then re-verify each time if you have the same issue or not, then the next batch of app installs. It could be a particular setting in a app as well, so it's possibly merely installing an app might not be enough, so each group of apps you install, make sure and configure them as well.
If you don't factory reset, go the opposite way, uninstall your least important third-party apps and see if the issue disappears. Keep track of which apps you're uninstalling in each group. Keep doing this in reasonably sized groups of apps until you narrow down when the problem stops happening.
Once you find which group of apps being uninstalled keeps the issue from happening, you can reinstall in even smaller batches, among the ones you most recently uninstalled, and eventually find the one causing the issue. In some ways I think it's easier to go the other way around, though, start with a factory reset.
Found the culprit!
Kind of silly: I have installed this app "Internet Speed Meter Lite" when I first started using my P6P, which is for me to monitor my real-time network usage (courtesy of that endless WhatsApp - Google Drive restoring process....). It basically refreshes itself every second and this morning I tried temporarily disabling it, the problem goes away even when the phone is not set to silent mode.
Glad I didn't have to come to the point of factory resetting the device, as I really don't want to go through the WhatsApp restoring process.
Thanks for all the input, much appreciated.