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
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
sb1893 said:
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
Click to expand...
Click to collapse
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
sb1893 said:
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
Click to expand...
Click to collapse
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
sb1893 said:
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
Click to expand...
Click to collapse
The saga continues. The issue occurs immediately after the first call I attempt when connected to my BMW bluetooth system. From that point on, I experience a 30 sec to 3 min delay between attempting to make a call and the Pixel XL actually initiating the call. The quickest way I have found to resolve the issue is to plug the phone into a charger for a few seconds and I am then again able to place calls. I have verified that the BMW bluetooth software is up to date and has not been updated in over a year. (Again - this issue just started happening yesterday...and I've been on Feb security patch for several weeks). I just cleared cache from within Titanium Backup. Will see if that improves the situation. Very weird. I also was just able to recreate the issue using just a simple Plantronics headset. So I continue to think it is something related to the Bluetooth stack on the phone. But I am not sure how to check to see if any of that has been updated via app update since I upgraded to Feb security patches. (I reproduced the issue at my desk using the headset after clearing cache.)
S
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Racermanz said:
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Click to expand...
Click to collapse
No - but I'm at least somewhat encouraged to know I am not the only one dealing with the issue. Today I flashed factory images (but preserved my data by removing the -w from the flash-all.bat)...that did not resolve. I've tried the reset app preferences, reboot suggestion I found elsewhere - no dice. Google pushed a new Phone app yesterday - that also did not resolve. I've even tried uninstalling Magisk completely and dropping back to 15.4 - also no help. I'm running out of ideas. I've taken to carrying a charging cable in my car...so if I absolutely need to make a call when the phone isn't behaving, I can just quickly plug it in...which does clear up the issue temporarily. Also keep a charging cable at my desk now...so I'm limping along..but for an issue that just appeared out of nowhere this week...it's been pretty frustating to deal with. Also - I no longer believe being currently connected to Bluetooth is related to the issue. I've been able to get the issue to occur today while not connected to any bluetooth devices.
Try
settings>system>developer options>media>disable USB audio routing
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Thanks bros. This is such a strange bug. Right now it works before I have turned off USB audio routing. I have turned off USB audio routing. I will report back if this DOESNT work. If I don't post again we can assume this works.
Thanks DR3W5K1, great name bro.
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Just tried to toggle on, which looks to mean Disable. Then rebooted. No luck. Issue still occurs. Thanks for the suggestion. Willing to try anything even to just eliminate as possibility at this point.
Well - I have found a better workaround. When you attempt a call, if you get no response, you can toggle Airplane mode "ON"....You will then see the call you attempted fail. When you turn Airplane mode back "Off" you can can successfully make calls again. Better than having to plug into a charger cable to get the attempted call "unstuck"....still no idea what is going on....but this workaround at least is more palatable, portable, and take a few seconds...hope someone can figure out root cause soon and a proper fix becomes available.
EDIT: Even better workaround. Toggling Mobile Data OFF and ON has the same effect of clearing the issue. And works better when connected to Bluetooth in car as those connections will be maintained vs. using Airplane mode toggle. So - issue seems to be related to Mobile Data somehow - but I have already had Advanced Calling / LTE, etc...turned off as one of my first steps in troubleshooting this issue.
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
The.Yield said:
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Click to expand...
Click to collapse
I have tried that. Sorry for not mentioning it in this thread. At one point I revoked "Phone" permission from all apps other than Phone, Carrier Services, and Contacts. Rebooted. Issue still occurred.
DR3W5K1 said:
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
Click to expand...
Click to collapse
Ahhh...I had forgotten about this secret menu. Looks like I could permanently toggle off VoLTE, WifiCalling, etc...here. But - not sure I want to go that route...I'm OK at present with Toggling Mobile Data via Quick Settings tile. And hopefully this issue eventually gets solved as mysteriously as it was introduced via some update.
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
tesla45 said:
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
Click to expand...
Click to collapse
Interesting....I'm on Verizon and I do believe that they route calls over Mobile data at times. I'm going to stay tuned, but likely done with much more deep investigation at the moment. I've spent enough time down this particular rabbit hole and the Mobile Data toggle is workable for me (not ideal, obviously)...hopefully a permanent fix materializes soon. Thanks to all for their suggestions and moral support. Much appreciated.
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Install the stock again clearing all the data. Don't restore anything with titanium or install any extra apps. Then make a call.
tesla45 said:
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Click to expand...
Click to collapse
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
sb1893 said:
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
Click to expand...
Click to collapse
Glad the workaround helps you too. My emphasis CAPS in my last post was clearly misleading, I was actually suggesting NOT to reinstall/factory reset because I don't believe that solves the problem long term and its a huge ask for a customer (when really Google should be solving this problem for us).
Based on this little workaround its clearly a software problem that Google needs to address, I've raised the issues on many threads in their product forums ... hope it gets to the right people ASAP because I believe lots of Pixel users are running into the problem (both Pixel 2 and 1st gen, another indication its NOT a HW problem).
Keep the workarounds coming folks!
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.
Hi!
First of all, I'm new to this phone - I owned it for about 2 weeks. and I'm very happy with it. Nonetheless I have noticed an issue that I hope someone can help me out with:
Since the phone doesn't have the notification LED, I have tried out a couple of apps to facilitate this function. I ended up uninstalling them. Now I experience that some notifications are not coming through (so far I've noticed text messages). I'm trying to figure out whether this is an issue with the phone, or if it might have something to do with the notification apps that I tested? I configured the apps and settings/permissions as necessary to get them to work, but I never reset those same settings before I uninstalled.
The issue I am facing is e.g. if a text message is sent to my phone (with display not on), the text and/or notification randomly doesn't get through until I wake the phone. After waking it, the message comes through immediately. Could this have something to do with testing those notification apps? If so, is there any way to find the specific settings and reset them or am I facing a factory reset to get it to work properly again?
Any help or hint is appreciated
Ive noticed that certain apps were still leaking past the do not disturb mode, even though they are not in my exceptions list. Then, I noticed these were apps that were specifically newly installed/re-installed. For example, I had to uninstall Instagram and re-install it. Before this process, the notifications were being blocked properly, but now that its newly re-installed, I am now getting their unwanted notifications.
Another example of an app bypassing the exception list is a fantasy football app called Sleeper. I hadnt had it installed on my phone prior to do not disturb being enabled. Once it installed, I started getting multiple notifications, even though i didnt add it to my exceptions list?
I am going to try to restart and see if that helps, but does anyone else have any tips?
Turning off DND, restarting the phone and then turning DND back on did NOT fix it.
I just take out the trash instead of playing with it
Try clearing system cache.
Otherwise likely a settings issue.
There's no fixing a trashware though...