So I received an OTA update the other day, and now everytime I am playing music and turn off my phone it mutes it. It's made the phone almost unusable especially if I turn on the setting to wake the screen when I get notifications. I wondered if anyone could help me fix it without rooting as I thought that maybe it's a simple fix, and I'm just overlooking something. Here are my phone specifications.
Model Number BLN-L24
EMUI version 5.0.2
Android Version 7.0
Edit - I solved this by resetting all the settings in the backup & reset advanced settings in case anyone else has the same issue.
Related
I just install the factory image for lollipop. My screen doesn't turn on when I receive incoming calls. The ring tone will play but the screen remain turned off. I want the screen to turn on automatically with the incoming call dialer like kitkat or any other android version. so I can pick up the call. Any one else with this issue? How did you fix it?
idiopathic said:
I just install the factory image for lollipop. My screen doesn't turn on when I receive incoming calls. The ring tone will play but the screen remain turned off. I want the screen to turn on automatically with the incoming call dialer like kitkat or any other android version. so I can pick up the call. Any one else with this issue? How did you fix it?
Click to expand...
Click to collapse
I don't have this issue. maybe you had a bad install
I have the same problem on my N4, I installed the factory image two days ago, but just today I have this problem. When I turn on the screen, the call appears as a notification on the lockscreen, and I have to double tap it to answer it
I have the same issue. I installed the OTA. I had security certificates before which forced me to use a pin lock lock screen (My exchange account requires it). I installed a MOD to remove it so I thought that might be what was causing my problem. I removed the MOD by disabling the exchange APP but it didn't resolve it.
I have the same issue on about 50% of my incoming calls
Sent from my Nexus 7 using Tapatalk
I have this same issue. I even had it on the developers version. I also thought when you got text messages, emails, and other messages. You would get a black and white notification if you moved you hand over the phone. That doesn't work for me either. i have a Nexus 5 Build LRX21O. I installed it with the Nexus Root Toolkit.
I have the same issue on my Nexus 4 side loaded with Android 5.0 Lollipop. The screen won't turn on for any interactive incoming notifications like Phone Calls, Alarm calls..
It's an annoyance as you need to double tap the notification to answer, and the only way to go to speaker phone is to answer -> unlock -> Tap speaker
I checked around and my colleagues who use a Nexus 5 don't have this issue (OTA or Sideloaded). So I think this issue could be with a Nexus 4 build only (selectively that too). I am the only one who've posted this on reddit too.
/r/nexus4/comments/2mjoz7/screen_wont_turn_on_for_incoming_phone_calls/
I can also confirm this bug ... on Nexus 5 with LRX21O.
Same problem!
I have the same problem on my G3, but i didn't even installed Lollipop yet.
Same on my Nexus 5 with LRX21O.
I am having the same problem with my nexus 4, after a clean flash..
I unlocked the bootloader which triggered a full factory-reset and this issue went away on my Nexus 4 which is smoother than before.
I wanted to download a full ROM (since the issue was with OTA update), so was doing a bootloader unlock for the same. But i didn't even have to load up the full ROM as the issue went away.. :laugh:
jsgraphicart said:
I don't have this issue. maybe you had a bad install
Click to expand...
Click to collapse
after i updating my nexus 5 to android 5 during call screen doesn't auto turn off when i covered the screen sensor?
I noticed this too,not on all incoming calls, but on 1 out of 3 the screen stays black.
Do try a full factory-reset guys.. It solved my issue.. This update is really large and important to have such a major annoyance and work with that.. :angel:
gnanaswaroop said:
Do try a full factory-reset guys.. It solved my issue.. This update is really large and important to have such a major annoyance and work with that.. :angel:
Click to expand...
Click to collapse
I made a clean install (wiped everything) and the problem appeared.
I don't think it is a matter of dirty flash..
I also have this problem after installing from ZIP stock ROM (with format all things before).
Then I took a Google image and install it with ADB.
Now I don't have this problem.
screen doesn't turn off
My screen didn't turn off during phone calls with the developer preview and still doesn't with the official factory image from Google.
This is coming from a full flash via fastboot... Don't think this is a dirty flash issue.
Very annoying... No clue how this could be released.
It appears our problems are not related but I was able to fix mine
Nexus 5
OTA Flash
screen is blank for incoming calls and alarms, not periodic
I don't know which app specifically that was causing the problem but the problem went away after I uninstalled a bunch of apps. I am most suspect of a screen brightness app I was using to make the screen more dim than the default setting.
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.
First of all, hello everybody ^^
Vibration doesn't work on my Moto G since OTA update of stock kitkat to stock lollipop. Not in apps, not in google apps. Not even calls, or keyboard vibration.
I've tried every possible setting so I am pretty sure is not a settings problem.
I've read the post on how to downgrade but I am pretty lost. The process seems very complex.
Is there an easy fix to this situation?
You go to dialer and press *#*#2486#*#* , will have menu to test vibrate. If vibrate not work, mean hardware problem, not OS nor software.
Hi all,
My Xperia Z3 was working great until I updated to the dreaded 5.1.1. Along with the other known bugs (USSD, battery drain, etc..), my phone is not ringing at all. The ringer slider is grayed out and cannot be moved. After rebooting, the ringer works for 1 or 2 calls then it goes back to silent. Have anyone faced this issue?
totti808 said:
Hi all,
My Xperia Z3 was working great until I updated to the dreaded 5.1.1. Along with the other known bugs (USSD, battery drain, etc..), my phone is not ringing at all. The ringer slider is grayed out and cannot be moved. After rebooting, the ringer works for 1 or 2 calls then it goes back to silent. Have anyone faced this issue?
Click to expand...
Click to collapse
You need to do a factory reset.
I had that problem sort of. My phone after flashing a particular rom would basically go straight to voicemail. Called my isp, turned voicemail off, alls well.
Thanks for the answers. I noticed that when I disable background processes in Developer options the ringtones work fine. However, disabling background processes messes up the phone and many apps don't work properly. I might try factory reset but I was hoping for a simpler fix for this issue.
I have this weird issue since I've updated to OOS 10.01. When my phone is locked and I receive a phone call the screen flashes with the caller info for a second then goes back to the lock screen and then goes back to the caller info screen. This happens every time I receive a phone call when the phone is locked.
Any insights?
Thanks
Please help, any insights/suggestions?
This is driving me nuts
Thanks
Something causes this issue, I have not been able to pinpoint the cause. I tried stock and rooted OOS 10 but no difference. I experienced the problem with both setups. Does not happen after a fresh install, but after a while starts to happen all over again.
Anybody else experiencing the same problem ?
Thanks
OK just a short recap, haven't had the issue for a while now. Still trying to find the cause.
Things I did differently since the last full wipe:
- did not install viper4android
- did not enable call recording
- did not give "Auto Dark Mode" app write permissions via adb (this is the one I believe is the most likely candidate)