After upgrading to Lineage OS 15.1, I realize that if I have screen lock set to pattern, then it is extremely hard to unlock when the screen has been off for a while. The screen will stay black while when I'm holding power button the phone will vibrate as if I'm calling power menu. This black screen can last at least one minute. I also set long press to open flashlight when screen is off and that doesn't work. Those symptoms makes me believe that the phone is awake, yet for some reason can't get GUI rendering. Sometimes even when I enter the correct pattern and the animation moves dots and timer away, I can still draw unlock pattern on the hiding unlock dots, and phone will vibrate in a very laggy manner.
Currently I'm running with no screen lock as even "swipe" still cause the unlock process to be very painful. Is this a known issue for LOS or is there a way to fix it? I saw a post says the battery should be replaced if phone is laggy. Is that a possible cause?
LolitaPlus said:
After upgrading to Lineage OS 15.1, I realize that if I have screen lock set to pattern, then it is extremely hard to unlock when the screen has been off for a while. The screen will stay black while when I'm holding power button the phone will vibrate as if I'm calling power menu. This black screen can last at least one minute. I also set long press to open flashlight when screen is off and that doesn't work. Those symptoms makes me believe that the phone is awake, yet for some reason can't get GUI rendering. Sometimes even when I enter the correct pattern and the animation moves dots and timer away, I can still draw unlock pattern on the hiding unlock dots, and phone will vibrate in a very laggy manner.
Currently I'm running with no screen lock as even "swipe" still cause the unlock process to be very painful. Is this a known issue for LOS or is there a way to fix it? I saw a post says the battery should be replaced if phone is laggy. Is that a possible cause?
Click to expand...
Click to collapse
This isn't a known problem.
From what did you upgrade?
Which build are you using?
Did you do a clean install?
Which gapps are you using.
Do you have Expanded Desktop enabled?
Elektroschmock said:
This isn't a known problem.
From what did you upgrade?
Which build are you using?
Did you do a clean install?
Which gapps are you using.
Do you have Expanded Desktop enabled?
Click to expand...
Click to collapse
I was using Stock Android before, but I fully wiped everything before I install.
15.1-20180508-NIGHTLY-shamu
Yes.
I got my GApps from Open GApps, but didn't remember which variant but most likely nano.
I actually have this enabled. I'm gonna disable it and see how that works.
After turning off Expanded Desktop the issue seems to be gone. Though when turned on again after some times the lag is still somewhat exist.
there's a Xposed module fix for this http://repo.xposed.info/module/fr.merams.r.deepscreenoreo
Related
So, I downloaded and launched it perfectly... everything so far i tried is working fine except the lock screen... Some times when i press the Cancel key the button lights lid up but there is nothing on the screen and sometimes it appear the lock screen but nothing happen....
Do someone have any solution to this...
Thank you.
I have the same problem. I have been reading that possibly going back to an older kernel / roofs fixes this problem but have not seen and confirmed reports.
Can anyone confirm this and what version?
Thanks
Same problem at me. Both builds are running very fine for some tine but after that are running slow.I don't know why. Maybe is somehow related with the lockscreen problem?
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
+1 one for me... I have got a TOPA100, it's almost impossible to wake up the device, sometimes the lockscreen is visible, but it's impossible to move the unlock slider. Usually I need about 10 times and something around 5 Minutes to wake up the device.
Same problem here, would be great if this can be fixed...
RaZz0r12 said:
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
Click to expand...
Click to collapse
For me it's the same and the battery runs only for one hour, I think a (system?)process is running with 100% CPU time. I am new to android, so I don't know where to look.
Same here on an AT&T Pure. Sure would love to get this fixed however I'm reasonably noob to the Android world (not completely novice to linux in general, and I have successfully flashed my AT&T TyTN II thanks to this site.) Fixing this would be a huge help!
Thanks
More specifically on my device I encounter. The following:
- Turn screen off via end button.
- Turn on screen via call button.
HW button lights come on for a few seconds then cut themselves off.
Screen does not turn on at this point.
- Turn on screen via call button again
- Screen comes on with HW button lights
about half the time screen is unresponsive and will not all me to unlock with swipe of finger
Other times will accept input and unlock to the home screen
When unresponsive repeating entire process above will likely allow me to unlock successfully.
Thanks!
Sent from my AT&T Pure using XDA App
same
my screen never wakes up
end up using soft reset to windows mobile
(it could be something to do with startup??)
Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
nuhusky4 said:
Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
Click to expand...
Click to collapse
I have had similar issues with the 4.2.2 ROMs although not as often as you. It would happen to me maybe once a week. I would just hard reboot the phone when it happened. Not sure if it's an issue with the kexec kernel or what.
As for the transition animations I would assume they would be in the launcher settings somewhere.
Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Byrkoet said:
Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Click to expand...
Click to collapse
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
alray said:
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
Click to expand...
Click to collapse
Thanks for the info. I figured as much, I will try Exodus.
EDIT: I have tried Exodus, XenonHD and Dirty Unicorns. Though no success: none of them were able to turn on the display after it dimmed.
I've had this problem with 2 different roms now (PureNexus, Chroma) on a few kernels (stock, ElementalX) so I'm not sure whats causing it but I need a fix. In a call, many times the screen just stops responding. Sometimes I can turn the screen on/off using power button and its fixed. Other times nothing works and I have to do a hard reboot by holding down power key since nothing else works on screen.
This is on latest version of the rom/kernels. Any ideas?
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Only when in contact with ears?
akholicc said:
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Click to expand...
Click to collapse
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
ECrispy said:
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
Click to expand...
Click to collapse
I'm having a similar issue from the last month.. I'm on DP5
when i get a call most times the screen is off.
To answer the call i've to put on the screen, unlock the phone and then go to the heads up notification and choose answer there..
waiting for nougat final hoping it'll fix this.
Tried fiddling around with notifications importance setting.. it helped a little but then there was the annoying heads up showing along with the regular incoming call screen.
Sometimes (very rarely, has happened twice) the screen just remains black and will only work normally after a reboot.
Anybody have any suggestions?
I was having similar issues, also on the Developer Preview and I ended up noticing that the phone app was blocked from showing any notifications despite the fact that I never set it that way. I would hear the call ringing but would never see the screen to answer. Just changed that setting and everything was back to normal. Perhaps something is causing the phone app to fail to show notifications for you as well.
Hey guys,
Recently, I've been having issues with my fingerprint sensor/unlock screen. Sometimes when I pull my phone out of my pocket and attempt to unlock the phone witht he fingerprint sensor, it won't respond. I then press the power button, which turns the screen on and when I use the fingerprint sensor, i can feel the vibration from the button but the screen does not unlock. There is also no fingerprint icon at the bottom. I can't unlock by swiping and putting in my password either. This eventually fixes itself after 30-45 seconds, but its really annoying when I want to use my phone. I've tried switching launchers, thinking that this might have been the problem, but this did not fix it.
I'm running stock OxygenOS 4.1.6, kernel [email protected] #1. I'm using the google launcher currently.
Its something to do with the light sensor cause i have it happen at night time when i am listening to podcasts in bed, it comes up to press one of the volume buttons and back to bypass it - but after 10 seconds it lets you unlock it anyway?
Pocket mode, try turning that off. Pocket mode uses the proximity sensor (I think) to detect whether it's in a pocket or not. If it is, then the fingerprint scanner will refuse to work so as to prevent accidental touches in the pocket
Turned it off last night. It's still happening. And it happens even when the phone is sitting on my desk. I go to try and unlock it and it won't respond.3
Delete and reset them. I find it happens after a month or so of use. I'm on Sultans marshmallow.
Originally when it happened I thought the ROM had gone bonkers and flashed back to stock. I missed the battery life too much on the CM13 build so I tried his marshmallow again. And guess what? It happed again. So I just deleted them and reset my fingerprints and voila! Snappy again.
Let me know if it works for you!
Just delete your current fingerprints and reset them. Should become snappy once again.
Happened to one of my friends and that's how I fixed it for him.
Cheers.
Never had issues with. Maybe you use it wrong side of finger, i mean you must unlock with you finger horizontally and not vertically finger
moSess said:
Delete and reset them. I find it happens after a month or so of use. I'm on Sultans marshmallow.
Originally when it happened I thought the ROM had gone bonkers and flashed back to stock. I missed the battery life too much on the CM13 build so I tried his marshmallow again. And guess what? It happed again. So I just deleted them and reset my fingerprints and voila! Snappy again.
Let me know if it works for you!
Click to expand...
Click to collapse
My phone has started acting wonky, not only with the finger print sensor but sometimes the touchscreen will become unresponsive, but I'll be able to turn the screen on or off. I'll have to try resetting tonight.