Over the last week my screen stopped shutting off during calls. I've looked everywhere for a fix. Tried "prevent accidental presses". But the screen still stays on.
Anyone else seeing this?
Did you try to reboot? I have this happen from time to time and a reboot always fixes it. Don't know why it happens, it's annoying but reboot seems to be a temporary fix. I didn't have this issue tough until after the Oct.2017 security patch update I received in mid-Nov.
Took it to big red....they performed a test #test on the dialer. Found out my prox sensor was bad.
New phone on its way
Related
[Q] Priority notification mode turning off on its own, even on "Indefinitely"?
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Yaqoub_H said:
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Click to expand...
Click to collapse
I never figured it out. Switched back to using Light Flow for notifications...
jeffreii said:
I never figured it out. Switched back to using Light Flow for notifications...
Click to expand...
Click to collapse
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Having same issue, no additional notification apps installed. Stock android on nexus 6 no root or anything yet. Thought I was loosing my mind thinking I never set it. Happens almost every night. Seems like a bug.
I'm having the opposite. On boot, priority mode is enabled even though it was off on shutdown. I turn it off then throughout the day I notice it come on again. I haven't been able to track anything down yet. I don't use lightflow.
Are there any logs that I can see that might tell me what is turning it on? There are no Downtime schedules.
Pure 3.95 / Franco r7
Yaqoub_H said:
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
Click to expand...
Click to collapse
So I finally got tired of Light Blow being buggy on the Nexus 6 and uninstalled it a few days ago...two nights in a row I set priority to "indefinitely" and when I woke up I found it had been turned off...so I don't think it's Light Flow causing the problem.
I've recently flashed the stock rom for my Xperia V as described below for locked bootloader.
http://forum.xda-developers.com/showthread.php?t=2796554
Since then I face problems with the display/phone acting weirdly . About twice a day I can't turn the display back on (display unlock). In this state the phone actually freezes somehow. One strange exampled I've seen today: I received a mail message, with the set signal sound and notification LED. I wanted to check the message but couldn't turn on the display. So I checked if I can call myself with another phone but the mailbox turned on immediately. The notification LED was still active so I'm not sure if the phone actually freezed or not. The only thing I can do at this state is to remove the battery and restart the phone.
Another problem I've since flashing the rom is that when I start a call is that the display turns off immediately no matter if I place my finger/face over the proximity sensor or not. Funny thing is that the call can be held as usual, but after that I'm not able to hold the call as the display won't turn on until the call partner ends it. When he has ended the call the display turns back on. Right now I really don't know what to do.
Here is the history how the problem started:
- dropped phone on floor and display broke
- exchanged display
- I've had installed Xposed installer on external SD card and modified some things on the launcher. While I was waiting for the new display I've used the SD card in a different phone. This has somehow messed with the Xposed settings I assume.
- After I booted my phone with the new display in place and external SD inserted the UI crashed all the time and the launcher won't come back. So I've restored the system with the androids included function.
- This is where I first saw the above described problem.
- I've tried a different, modded rom. With this the display problem didn't occur but the battery performance was really bad.
- Installed stock rom from link above. Now problem with display present again. So maybe there is an issue with the original 4.3 rom?
Has anybody experienced the same issues as I do right now? I really don't know what to do but the problems really annoy me.
Thanks!
Try to repair it using PC companion
Didn't work. Same problem remains.
Ok, I was able to fix the issue with the display turning itself off during voice call.
The headphone connector does somehow connect the light and proximity sensor to the phones mainboard. This connector didn't sit properly inside the middle phone case which cause a bad connection to the sensors. I've reassembled the whole phone and now this problem has disappeared.
The other problem still remains, I hoped it is linked to the display proximity sensor problem, but now it is clear that this has some other source.
Is there some kind of app monitor available? I assume that there is some app which causes the various hang up, but I have plenty of them installed and deinstalling always just one of them and monitor for various days will last for months.
Is there any possiblity to find out if the lock ups are caused by some app?
Really nobody in here who has any ideas? I've now exchanged the display to a new one as I thought it's caused by a faulty display connector, but the problem remained. I'm running out of ideas now.
Ever since updated to the Nov 1st update. When I turn my screen on there is a 1 in 3 chance that the screen will be at max brightness. The only way to fix it is to wait 5 seconds or turn the screen back on then on. Anyone else seeing this?
Yea it started happening to me about two weeks ago after I installed GravityBox , don't knowwhat to do it's very annoying .
Known issue. I've filed a bug, please star it. Here's the link where we discussed this in detail.
http://forum.xda-developers.com/showthread.php?t=3256165
Thanks @andr0idfreak. I was starting to worry I was alone. From the bug report seems a lot of people are seeing it.
This happened to me yesterday and that was completely by mistake. I had the marshmallow update for sometime now and not experienced any major issues other than the random heating (while charging) and some drains at times.
The major issue occurred to me yesterday, when my mutli-window function got disabled by some how and then the phone did not respond to any of my finger touches anywhere on the screen. I have a password lock screen and that too stopped working because the touch response system was not usable. After a struggle for many hours and one sleepless night, the next morning, when I was just thinking of sending the phone to the service center; it just came to my mind and I tried out the SPen and that was working just fine. :victory:
So, using SPen I unlocked my phone and tried to understand what changed. As I normally enable a few functions on my phone, it easily came to my notice that the multi-window function was disabled. So, again using the SPen I enabled it and Voila!! the finger touch started working back.
This is pretty crazy and never experienced this before the marshmallow update.
PS: Even the backlit hard buttons ( left one, home, back right ) had stopped working for me for that instance.
Anyone has any clue on it?
Did you do a reset after the upgrade?
donalgodon said:
Did you do a reset after the upgrade?
Click to expand...
Click to collapse
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
vaibhavgaikwad said:
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
Click to expand...
Click to collapse
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
donalgodon said:
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
Click to expand...
Click to collapse
I think I have been more clear and transparent, if you says the multi-window is not an issue then it may be something else which I am not aware of. Though I know that over that particular day nothing new was installed on my phone (so I doubt it can be other software).
Why I am sure its the marshmallow update is because the older version I had tried disabling the mutli-window and the phone worked well, only with the marshmallow update the phone got weird (that too with that multi-window disabled) and enabling the multi-window made it work, so that's my point.
To answer you question on "Did I do a reset", the answer is no I did not, I rebooted (and shut) it couple of times thinking its overloaded but it did not change my situation. Only after I realized that SPen was working fine I could unlock the phone and enable the mutli-window and there after it started responding well to my finger touches too. It's working good today as I write this response. I can once again disable mutli-windows and check if it goes weird again. Let me know if you want me to do that?
Regards.
I recognize that doing a reset can be a pain, but it's probably worth it in the long term. It's up to you, but if it were me, I'd do a reset and start fresh.
When you make major version leaps, the chances of problems increases dramatically over point releases. (i.e. going from 5.x to 6.x is bigger than going from 5.0 to 5.1)
I'm really stumped here. I haven't been able to find any solution to this issue through searching, so I figure I might as well post something about it.
For the past few months, I've been having an issue with my watch screen turning itself on then dimming after a few seconds. This seems to occur every few minutes or so even when theater mode is enabled and when always on screen and wrist gestures are disabled. This issue persists even after unpairing with my LG G4 and after a factory reset (on both the watch and phone). It should also be worth noting that I have recently rolled my phone back from the latest VZW Marshmallow OTA to a rooted 5.1 image in an attempt to resolve the aforementioned problem, but from what I can tell, it has only become worse.
From what I've been able to gather from battery/wakelock monitoring apps and bug reports is that the phone is regularly sending wake requests at semi-regular intervals. I have not installed any third-party wear apps and I've disabled pretty much every Google sync function but the problem persists.
I am at wits end here as to what I can do here. This coupled with my phone suddenly developing a severe wakelock problem has made me seriously consider switching to another manufacturer, and this time I may not exclude Apple as a choice.
Has anyone else experienced an issue like this that might have some insight as to what's going on?
Thanks!
PS: If needed, I can provide the full bug report along with a quick spreadsheet I made to organize the kernel wake source info found in the report.