Related
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
leesumm said:
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
Click to expand...
Click to collapse
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
could be.
DvineLord said:
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
Click to expand...
Click to collapse
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Yeah I have found some of the Venom tweaks really affecting responsiveness. For example if you could figure power long press to turn on the flashlight it takes NOTABLY longer to wake the phone. I can see s2w having the same effect
Here I thought I was the only one experiencing this issue. I did a full wipe and format and flashed a bone stock (default configuration) flash of ViperXL to see if that would solve the issue. Screen issue doesn't occur as often as before bit it still happens. I found that if I block the light sensor, the screen begins to behave normally. I don't have a logcat yet but can upload if necessary.
Sent from my HTC One X using xda app-developers app
same problem again.
leesumm said:
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Click to expand...
Click to collapse
I thought wrong , again, tried this morning just moving an app from home screen to second screen. It will open but unable to move it or delete it from the screen. Rebooted and seems everything is normal again.
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
area51avenger said:
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Not really sure, I can't find anything that 4x5 is enabled. S2W I disabled also, this is not a big problem just irritating some times. Things usually start working normal when I reboot system .
You could try increasing the voltage.
ken bentley said:
You could try increasing the voltage.
Click to expand...
Click to collapse
At this point I am not sure I am that smart to be messing with volotage and such on the inside of this thing.
just stopped using a custom kernel. i stopped using them cause of freezing issues.
Using the stock launcher, this problem/feature just started popping up recently. I couldn't find any discussion on if this was part of the newer Google Search / GEL updates.
On the homescreen indicator that separates the dock, I now have a plus sign on the far right, which makes the regular indicating dots off center. Swiping left is Google Now like always, but now swiping right after the rightmost homescreen leads to a blank homescreen (screenshots attached). It used to just be that trying to swipe right on the rightmost homescreen would do nothing. How do I go back to this original function?
I'm using Cataclysm Rom [Nov 15] and franco.Kernel r14. I've searched through those threads for more information about this blank homescreen, but no luck. I've also dug through the Cataclysm Settings to see if I've ticked any options, but I can't find anything. I don't have the franco.Kernel app so I don't know if this might be a kernel setting, but again, I couldn't find anything in the franco.Kernel thread.
Thanks for any help!
Move an icon over there and move it back. That fixed it when mine did it.
MisterEff said:
Move an icon over there and move it back. That fixed it when mine did it.
Click to expand...
Click to collapse
Thanks, that temporarily got rid of it, but after a reboot, the plus sign and the blank homescreen came back.
Maybe it's just part of GEL now? Haven't found any discussions about it though :/
I too have this, it drives me absolutely nuts! It shows up after reboots and random times! No fix besides putting app there and deleting
It has happened to me twice so far. Can't figure out what it is.
Sent from my Nexus 5 using Tapatalk
MisterEff said:
Move an icon over there and move it back. That fixed it when mine did it.
Click to expand...
Click to collapse
Only had the problem once and this solved it.
Having the same issue, appears randomly and I have to either restart the phone or use the app move/unmove trick to get rid of it.
I haven't found a correlation to any thing in particular or any app but I'd like to know what's causing this..
I have experienced this as well. I just reboot the phone and it goes away. Pretty minor bug but yea i imagine it will get fixed in the next update.
I received OTA yesterday and so far found one bug. There is a black screen comes up randomly. Top and bottom bars are visible but I can't do anything to get out of it. The only thing that works is restart. I can't pinpoint the app that might be causing it. It happened while updating apps or using Firefox. Anybody else having this issue?
Sent from my Nexus 5 using XDA Free mobile app
Did you wipe your cash after updating? I had experienced several bags after the OTA update too, but i cleaned cash from the recovery mode and now everything works just fine.
Did wiped cache from recovery mode yesterday and it was OK. Today the black screen issue is back. It's quite annoying having to restart.
Sent from my Nexus 5 using XDA mobile app
Hi there, I am currently having the same bug on my Nexus 4 device.
It appears the same way, with the Softbuttons visibile and the top bar still able to be pulled down. Plus that there is no option if I restart to get my SIM card recognized. Pretty annoying when you have an encrypted nexus device and have to wait 2 minutes to restart with a 40% chance of NOT getting the black screen again.
My assumption is that it has something to do with the kernel. Any suggestions/confirmations?
Best regards
JYBM said:
Hi there, I am currently having the same bug on my Nexus 4 device.
It appears the same way, with the Softbuttons visibile and the top bar still able to be pulled down. Plus that there is no option if I restart to get my SIM card recognized. Pretty annoying when you have an encrypted nexus device and have to wait 2 minutes to restart with a 40% chance of NOT getting the black screen again.
My assumption is that it has something to do with the kernel. Any suggestions/confirmations?
Best regards
Click to expand...
Click to collapse
Same problem here... black screen with only softbuttons visible and notification bar working.
I think the problem occurs when an application is in full screen mode (no softbuttons visible) and you do a little swipe to make the softbuttons appear... It must be something with the way the softbuttons overlap the screen, I think.
Any help?
I am also seeing this problem on my Nexus 5 which I flashed the factory image with full wipe. I have had it when exiting apps and also when an app is open it can just happen. If i swipe up from the bottom sometime I get a flash of the screen during the animation so it is as if a layer is over the screen. I hope this is fixed as it is random, this morning it happened and after a reboot i logged in and it happened before I opened an app, reboot, then happened again a few mins later, but after a 3rd reboot has been ok???
For everyone that is experiencing this problem... do you have Tasker installed?
I disabled tasker and since then I don't have this problem... so far.
Still happening once in awhile and I do have Tasker.
Sent from my Nexus 5 using XDA Free mobile app
It happens to me. My current theory is that, in my case, it may have to do with a profile manager I use which turns the lock screen pattern lock on and off depending on where I am.
Cool_fury said:
For everyone that is experiencing this problem... do you have Tasker installed?
I disabled tasker and since then I don't have this problem... so far.
Click to expand...
Click to collapse
I also have tasker, don't want to disable it as I find it too useful, can you keep us all informed if it cures the issue.
rpudner said:
I also have tasker, don't want to disable it as I find it too useful, can you keep us all informed if it cures the issue.
Click to expand...
Click to collapse
I also find tasker very useful.. but I think it was causing the problem. No more black screens since then.
To try to narrow it down even further... do you have a profile to enable/disable the lockscreen in certain situations?
Cool_fury said:
I also find tasker very useful.. but I think it was causing the problem. No more black screens since then.
To try to narrow it down even further... do you have a profile to enable/disable the lockscreen in certain situations?
Click to expand...
Click to collapse
I do use tasker to disable the lock screen, I wish that the smart lock would completley disable the lock screen, and not just the secure section. I will take all the lock screen options out of my tasks and reboot, will test for a few days.
I tested over the weekend and had no black screens with all tasker/secure settings lock screen disables turned off, I left all other actions on , so I think you are correct. actualy got on OK using the smart unlock, although when in my house sometimes GPS is lost so it will relock, but not a real issue. Thanks for the heads up
Am I alone ?!
Lineage OS works fine, for a couple of days, then, out of nowhere, the homescreen and menu buttons are not responsive. Then, upon reboot, homescreen turns black, showing nothing except the status bar. The status bar can be swiped down, but everything you click is not responsive.
Wiped Dalvik and cache, issue is still there...
* After a reboot, the device shut down inexplicably. Upon next reboot, issue resolved... WTF is going on?!
jfpesant said:
Am I alone ?!
Lineage OS works fine, for a couple of days, then, out of nowhere, the homescreen and menu buttons are not responsive. Then, upon reboot, homescreen turns black, showing nothing except the status bar. The status bar can be swiped down, but everything you click is not responsive.
Wiped Dalvik and cache, issue is still there...
* After a reboot, the device shut down inexplicably. Upon next reboot, issue resolved... WTF is going on?!
Click to expand...
Click to collapse
I have the exact same problem! Installed LOS on Friday evening and it worked great until Monday afternoon. Screen was on and had full notification bar contents - it looked like the phone was working properly. It could even take calls, receive emails and texts, but the rest of the screen was black and the buttons reset to original settings and didn't even work correctly. The Home button did nothing except a double tap would create a brief white border around the edge of the whole screen. A single press did nothing. The back button worked properly. The switcher button did nothing at all. I think it was doing the Google assistant thing. Holding in the power button was setup to press restart and then give restart options, but it was reset to just restart and confirm.
Restarting never worked to correct it. Wiped cache and Dalvik cache, still no go. Letting it sit for over 30 mins did let it recover once and one other time while driving it went from this black state to fully functional for no reason. It was good for a few minutes and then the buttons stopped working again. The soft buttons did not help either. They behaved badly as well.
It seems to have no pattern. I wiped the phone and flashed the newest LOS on Monday evening and it worked great until tonight. I have no idea what is going on!
Glad to know I am not the only one... Just need a permanent fix!
Nice, a brother !
The back button worked properly.
Click to expand...
Click to collapse
Same thing here.
Also, I can't tell if receiving calls work, cause I didn't try, but I can confirm the quick settings tiles keep working. The drop down notifications show up, but clicking an individual notification won't bring up the app it is refering to.
So far, the "shutdown, wait a little and reboot" seems like the only thing resolving the issue temporarely. So yeah, before wiping everything and reflash LineageOS, keep calm and wait !
Also, be sure to do a backup your working OPO/LineageOS phone in TWRP mode, so you don't waste time reflashing OS, restoring apps with Titanium Backup and restoring settings manually, like I did three times over the past two weeks...
Too bad we don't see the changelogs with each weekly LineageOS builds releasing or any bug report compilation.
I am conducting some trial and error testing to help isolate the problem. So far it feel like it is related to profiles, specifically with either a trigger or disabling the lock screen. It seems when I add a profile to unlock and disable my lock screen via a wifi "on connect" trigger, that is when things seem to go down hill. generally shortly after is when I get the black screen. I am using the Pixel launcher and have added a Home profile with triggers for wifi and then set my lock screen to disabled. I am currently using the default profile and have not added any others and the phone seems to work well with no issues. It is still too early to say that is the problem, or even exactly what the specific problem is, but I will continue with the default profiles as-is for the next few days or week to see if it remains stable.
Maybe this will help steer someone else to find a fix...
Also this has just happened to me.
All was working fine for a few days since flashed now have same issue as above
Also had Profiles set up for home network for lock screen and sync etc
Phone is Redmi Note Pro 3 though
Stumbled across this while looking for info on this issue
https://www.nico-maas.de/?p=1537
That link is going down the exact same path as I am. Coming to the same conclusions. Thanks for posting it.
With the default profiles in use, I no longer get the black screen and everything is working fine. I will need to keep an eye on the change logs to see if a profiles fix come down the pipe.
For me, it was changing the Lockscreen to none (from pin) that caused the black screen. That link defiantly helped me out. Only thing I did was edit the "profiles.xml" and changed '<screen-lock-mode>' to 0 instead of 2
Yep, also using System profiles to disable lockscreen at home or in car.
Lately, I get no issue at home, but only in car, where my system profile is also setup to activate hotspot when Bluetooth connected to my radio. As soon as hotspot turns off, issue is resolved.
On another side, I mentioned earlier that LineageOS doesn't list its changelogs. I was wrong. You can find them here : https://www.cmxlog.com/14.1/
Fixed!
I experienced the same problem today with my OnePlus 2. Guess time does heal. I waited for a good half an hour and it seemed to fix itself.
When the screen is off, hold down the power button for a second and you should see the power menu. Select 'restart' and let the phone reboot. Simple as that!
Tell me if the problem still persists.
Still having issues.
Notification cannot be seen , I can only hear them.
I haven't configured any profiles.
Home and recents don't work.
Can't open developer options, its says its not available for this user
Anyone have ideas ?
Help me
I got issues with LO, my back, home, recent buttons not working (capacitive) so I'm using on screen button. But after all happen, now I'm having problems with my volume button, it didn't work at all, already restarting my phone many times, also, chance the system profile to default, sadly, it didn't help. Can someone help me with it.
This is not a new issue. I first encountered on CyanogenMod 3 years ago, and I'm disappointed to find that it still hasn't been fixed in
Lineage os. In CyanogenMod disabling "reduce power consumption" in the adaptive display section resolved it. But now with lineage is there doesn't seem to be any specific setting that causes it.
had the same issue - pretty sure it has something to do with "Profiles" set up. For instance, I set up profiles for turning off Lockscreen when Home - using the WiFi detection.
After a restart, the screen went black, but funny enough, the quick menu and the Bar still showed up. I turned on Airplane mode, to switch to the default Profile - which enables the Lockscreen when not in wifi and restarted. That worked.
So I think something with the Lockscreen + Profiles is a bit buggy.
It only occurs after a reboot.
I am using LineAge OS for M7 14.1 - which runs great!
AD
Have the same problem. Tried to update Lineage OS, but it didn't work out. Can anybody help me?
taalojarvi said:
Still having issues.
Notification cannot be seen , I can only hear them.
I haven't configured any profiles.
Home and recents don't work.
Can't open developer options, its says its not available for this user
Anyone have ideas ?
Click to expand...
Click to collapse
romap0 said:
Have the same problem. Tried to update Lineage OS, but it didn't work out. Can anybody help me?
Click to expand...
Click to collapse
I solved this by clean flashing ( Data wipe + LOS Reflash ).
It's a Known LineageOS source bug ( according to their reddit )
I've started getting this as soon as I tried getting the first time setup to work again. Try this:
adb shell
su
pm enable com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity
2. adb shell settings put secure user_setup_complete 1
and if it doesn't work try adb shell settings put secure user_setup_complete 0
I have a Nexus 10 running the latest 7.1 Lineage image and had the same problem after updating the system and the GApps... here’s how I solved this problem on my tablet... maybe it will help someone else...
1) Use TWRP as your recovery loader
2) Backup your image using TWRP
3) Install the latest GApps - I use the Nano version
4) Wipe the Cache after the install is complete
5) Reboot and wait for the system to settle
6) Reboot into recovery (TWRP)
7) Install the latest Lineage (I use nighties)
8) Wipe the Cache after the install is complete
9) Reboot and wait until everything loads
10) Problem solved.
So... install GApps over the existing install... reboot let it do it's cleanup, then reboot into recovery and install the nightly update... wiping the cache of course... its worked for me three times now.
AlexInvar said:
I've started getting this as soon as I tried getting the first time setup to work again. Try this:
adb shell
su
pm enable com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity
2. adb shell settings put secure user_setup_complete 1
and if it doesn't work try adb shell settings put secure user_setup_complete 0
Click to expand...
Click to collapse
Great! Setting secure user_setup_complete to 1 seems to work for me.
EDIT: Nevermind, the problem only occurs when I connect to wifi with the screen off, which I didn't test. So no solution yet.
hello there! i have a similar bug on lineageos 15.
everything worked fine until today. no new apps installed or settings changed.
i flashed on 1. December and im really happy with this ROM, but today the hardware touch-keys stopped working correctly. The back button is ok, home button don´t work (except the double-tap function which starts splitscreen) and the menu button wich is set to swich last app with a single tap and show all open apps with a long tap opens the app-menu instead (that function that we know from android 4...).
after rebooting everything start to work again but only for a random period of time.
sry for errors or bad english...
i hope it will be patched cause the ROM is really one of the best i had.
I turned off the Edge Panel feature on my phone but the handle bar won't go away from the home screen. I've tried to minimize the handle bar size as well as made it 100% transparent. On any other screen, the Edge Panel handle bar is completely gone but anytime I'm on my home screen, the handle is there and I can't find a way to make it go away.
I also downloaded the All In One Gestures app so my phone can have the swipe to go back feature. To use this feature, the app will place a shadow on the edge of the screen, indicating that the feature is active. I've tried to disable this feature as well to get rid of this shadow but it also won't go away from the home screen. Even if I uninstall the app, the shadow remains.
Anyone know a fix to this problem?
/Users/Jizay/Desktop/Screenshot_20180108-184215.png
I suspect you have a kink in the install or somehow have corrupted a file. I do not know of a 'fix', other than clearing cache on stock phone and re-boot. If rooted, clear cache/dalivk and see if that works.
If it were bugging me enough, I'd do a clean install.
JeffDC said:
I suspect you have a kink in the install or somehow have corrupted a file. I do not know of a 'fix', other than clearing cache on stock phone and re-boot. If rooted, clear cache/dalivk and see if that works.
If it were bugging me enough, I'd do a clean install.
Click to expand...
Click to collapse
Unfortunately clearing the cache didn't work. I may just do a clean install one day when I have time. Thanks for the help.