Great...... Got this message appearing and can't rescan a fingerprint I need to. Can't do anything with the scanner now really. It still works with the prints that are scanned but I've noticed it's unpredictable.
I'm trying not to root this phone as I would like to use Samsung pay when it comes, so don't want to trip Knox. However, if I was rooted I reckon this would be a fairly easy fix. As it is, I can't find a way. I've deleted cache and data for the fingerprint app but it's having no effect. I could factory reset but this started for no reason, so it will start again after a factory reset no doubt.
Did you reboot? What carrier/model do you have?
Clean the button?
Reflash your firmware that should fix it use smart switch
In case this happens to anyone else - I found a fix.
I had enabled developer options and then enabled oem unlock. I had done this as I was going to install TWRP and then root the phone, but decided not to for reasons mentioned in my first post.
Anyway, I disabled oem unlock and developer options and now the scanner works again. Worked for me - hope it works for you.
But oem option not see in my phone s6 edge G925W8
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 recently unlocked my Honor 8, and then installed this RROS Rom which I used for about a week. I had some issues with the camera and reboots while driving, hearing music over bluetooth and using Google Maps at the same time, so I tried a few other Roms (LineageOS, halogenOS, AOSPA).
With my first RROS installation, I could use my lockscreen + fingerprint sensor as usually. The problem is, after installing another ROM (I believe I tried AOSPA first), I'm not able to configure Settings->Security->Screen Lock to something other than Swipe. Everytime I try to set one of these, I can create a PIN, password or pattern, but when confirming it the settings app just force closes. When I reopen it and click on Screen Lock again, the settings app just asks me to confirm e. g. my PIN again, and force closes when I do so, without anything changed on my lock screen.
I tried installing all Roms mentioned above, and I even tried to wipe my internal storage in case there's something messing it up. Yet when starting one of the ROMs, I cannot set anything for Screen Lock.
I found this thread, and thought that maybe I could either clear credentials (but it's grayed out) or change Storage Type from Hardware-backed to something like Software-backed, but it seems I cannot change this option.
Has anyone any advice what I could do to regain the ability to set a lock screen (and therefore also use fingerprints again)? Thanks in advance!
A friend helped me analyse errors in MatLog and find a solution:
It seems the fingerprints from my first RROS installation were still stored in the phone, I had to delete all folders in /data/misc/keystore/ and then reinstall my ROM, then I could set fingerprints again!
daxlero said:
A friend helped me analyse errors in MatLog and find a solution:
It seems the fingerprints from my first RROS installation were still stored in the phone, I had to delete all folders in /data/misc/keystore/ and then reinstall my ROM, then I could set fingerprints again!
Click to expand...
Click to collapse
When you say reinstalled, you mean a clean installation? Or only flashing ROM?
Sorry, it's so long ago I can't really remember. I guess it was a clean install - mostly went that path for fixing problems - but can't say for sure.
I've been using the Pixel 3 for a few days. Today, it apparently rebooted itself overnight.
I knew because two things happened. 1) My alarm did not go off, 2), when I opened the phone it requested pattern unlock rather than fingerprint since it had been restarted.
The strange thing is that the startup process was "frozen" until I authenicated with the pattern unlock. Bluetooth devices like my watch were disconnected . Once I unlocked, I saw Bluetooth connect, and apps and notifications started loading and appearing.
My experience with prior Android phones is the system will fully load background tasks and apps when restarted, even if the user doesn't unlock it.
Is this something new for Anroid 9 or the Pixel? Is there any way to allow everything to load on restarts?
Is there any logging (other than ADB debug) that can identify the cause of spontaneous reboots?
timg11 said:
I've been using the Pixel 3 for a few days. Today, it apparently rebooted itself overnight.
I knew because two things happened. 1) My alarm did not go off, 2), when I opened the phone it requested pattern unlock rather than fingerprint since it had been restarted.
The strange thing is that the startup process was "frozen" until I authenicated with the pattern unlock. Bluetooth devices like my watch were disconnected . Once I unlocked, I saw Bluetooth connect, and apps and notifications started loading and appearing.
My experience with prior Android phones is the system will fully load background tasks and apps when restarted, even if the user doesn't unlock it.
Is this something new for Anroid 9 or the Pixel? Is there any way to allow everything to load on restarts?
Is there any logging (other than ADB debug) that can identify the cause of spontaneous reboots?
Click to expand...
Click to collapse
This is normal. Until you unlock it,there's only a few things that will be available. Phone calls come to mind as one of them. Anything like Facebook Messenger, Snapchat, your bluetooth devices or any other apps won't have notifications until you unlock it. It's different than it used to be. It's a security thing. That said, I'm surprised the alarm won't work since it's a system app. I don't use it very often so I don't know it that's normal or not. From what I've read though, most apps aren't allowed to load completely after rebooting until you unlock the phone.