Every once in awhile, my shortcuts on my lockscreen will disappear. In it's place is a "return to call" box. Sometimes it's after a phone call, other times it's completely random. I'm completely dumbfounded by this and can't find a possible cause. Here is a screenshot. I'm rooted with xposed. I posted this here because I'm not sure if it's device specific.
Should be some kind of interference with Xposed. Never happened to me before (no Xposed).
Related
After rooting my v.6.1 KF, manually updating to 6.2, and getting Gapps, Market, Go Launcher, WidgetLocker, etc., working my notification volume now goes to zero after setting it to > zero. Also, when choosing a notification sound, even with volume turned up, you get no notification sound. Other sound is fine (Pandora, for example).
Any thoughts? I have a 'mute' icon for volume in the upper right notification area (where WiFi is). Seems like this was not an issue last night and might have been mucked up by WidgetLocker. I'll be trying a workaround based on that theory later today but for now work calls :\
EDIT: Solved! See below.
There is an app called "Volume Control" that will let you set the various types of notifications individually. e.g. it separates notification from media from system. Very helpful.
Just had to deal with a similar problem.
As somebody else on this forum stated, the probable culprit is Widgetlocker.
I had it installed for a while, played with the settings and unintentionally changed the ringtone to mute (the right slider on the lockscreen). Had to re-install the app (had it uninstalled), changed the ringtone back to normal and voila - notification sounds are back.
Oh my God I can't believe that after all the relatively complex things I've done over the past two days that my answer to the one problem which kicked my butt hard enough to post about it was "you broke it yourself" lolol. The WidgetLocker volume slider was the problem. I had slid it to mute and never thought about it again. Everything's back to normal. Can't wait to get TWRP and CM7 running over the holidays!
Thanks for this! It made me look at the icon I thought meant "Mute" and really meant "Do Not Disturb". Turning that off brought the sound back. Thank God. Lol. I was also looking for complicated issues and blamed Amazon. Sorry!
It seems that sometimes my calls get muted when my phone leaves the on-going call screen and switches to a something else/a different app.
Hopefully that makes sense, but I'm not even sure how/when it happens so it's difficult to describe. But basically, randomly, when I'm on a call the other person won't be able hear me. Every time this happens when I look at the screen I'm no longer in the phone app/on-going call screen. Once I swiped down on the notification menu and re-enter the ongoing call they can hear me again.
I've tried to duplicate the behavior by switching apps but can't seem to do so...Has anyone else experienced this? I'm wondering if it has something do with the the automatic do-not-disturb that enables during calls...?
Thanks
When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?
I dont have this problem.
pogano_celjade said:
When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?
Click to expand...
Click to collapse
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.
lbsilva said:
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.
Click to expand...
Click to collapse
Yes, it is very weird and annoying. Not happens every time, but sometimes... ?
This happened to me yesterday for the first time, but I thought that was a problem of the person that was calling me.
It was a number I didn't have in my contacts, and after the bug I immediately called back that number, but it was not available.
I thought the person that was calling me had a very low battery charge and while calling me his phone turned off, causing the bug (because immediately after the bug it was unavailable).
To this date I still did not have this problem.
Me too, i cant answer and reject calls when i upgrade to android pie
Solved: Screen not turning on with incoming calls
Step 1: Go to Dialer or Phone app settings. To do so, you can either go to main settings, then open ‘Apps’, and then scroll down to Dialer or Phone App.
You can also access App Info page by long pressing the app icon, and then tapping the App info option or the small ‘i’ icon in the corner.
Step 2: Now select “App notifications” option and turn it "on"
Step 3: Now if App notifications are turned off, your display won’t wake up when someone calls you. Also if only the “Incoming calls” permission is off, your screen will not light up with incoming calls. Make sure required permissions are turned on and your issue will be fixed.
Xiaomi Mi 2 Lite. I cannot get incoming calls to show on my screen, so I can't answer. Tried switching notifications off and on again, tried forcing stop. Two days ago I did a factory reset and was OK for 2 days. I think this is since latest Android update about a 10 days ago.
Call answer bug
I have similar issue on Mi A1, been going for a while. Sometimes, call comes in, the answer key cannot pick and cannot reject the call. This happened after a certain update I just dont know which. I have noticed that this mostly happens at some particular GSM antennas, sometimes, just by moving away from that antenna (that's when in a car) solves the problem. But as long as I remained in that location at that time, i cannot pick or reject calls, I also can't make calls, I get the promt, network problem, even though the service bars r showing. And in some cases the people calling will tell me, that calls to me are not going through.
This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.
PeterSharpe said:
This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.
Click to expand...
Click to collapse
Clear data and cache of the "phone" App and if necessary reinstall the application
Every once in awhile, my notifications pull-down won't pull down.
If I lock the phone, then unlock it, the pull-down starts working again.
It's been like this through multiple clean OS re-installs.
Am on Magisk 17.3.
I've had more software bugs on the PXL3 than any other phone before, including the PXL1.
I have the same damn problem. It just doesn't work all the time. I also had the issue of bright white screen on double tap to wake. So, I called Google Support for this, and the guy on the other said made me clear the cache of the phone app, force stop it, turn the phone off for 2 mins and then restart for both issues. I even asked him how this relates to the fingerprint sensor not detecting, he replied some stuff that, phone app controls the vibration and the display waking up.
Of course both problems does not occur for me frequently, so after that procedure I did not encounter the white screen problem, but fingerprint gestures were still kinda hit and miss. Although they work pretty good now, less miss count. For me they work when I swipe just the edge of index finger lightly, also if finger is very dry, it doesn't detect.
I tried the pulldown five times while this logcat was running.
I'm on Nova Launcher but think it happened on stock launcher too.
For as long as we have had these phones, I have dealt with numerous bloatware apps I had to uninstall ala adb command line args, but one aspect of it i'm trying to deal with proves to be stubborn to a massive fault: Wi-Fi Call Notifications
Multiple times this aspect of my phone refuses to stop giving me notifications on "hey, guess what, if u enable wifi call and blah blah blah". Yeah, I get that its an alternate way to call if phone lines are down or for emergency reasons or whatever, but I DON'T CARE!!! Yet the option to turn off notifications for it are unavailable for me, greyed out, and I even set the delivery of said notifications to silent and quiet by long pressing the notification on my top-down menu when extended, but nope, still here
I need help, is there a way for me to disable these notifications in some way that wont bad times my phone, or better yet, is the wi-fi calling app, while an integrated system app and whatnot, relatively safe enough for me to adb/pm uninstall it without my phone having a hiccup and bricking itself? I just want to shut it up already, I don't want to use it, I will NOT use it, never and no how. pls halp
I'm trying to figure this out now as well... Did you solve it already?
This is probably of little help to you both, but I kept receiving that notification concerning Wi-Fi calling (USA unlocked firmware) until I stopped notifications from whatever app was displaying the Wi-Fi calling "offer", perhaps by tapping on the notification itself, or long pressing on the notification (it's been a while).
Unfortunately, I don't remember which app served the notification. In any case I haven't been bothered by it subsequently, although I don't know what else I might be missing! (Nothing that I've noticed.)