Cannot get the lock screen shortcuts to work with hyperdrive rom.
Noticed the issue, thought possibly got a bad flash. So I did another triple wipe/cache clear and installed the rom again. Still the same issue.
You can get as far as moving around the preset shortcuts, but when you try to click the (+) to add more the screen goes black before it pops up a message that settings has stopped. Tried rebooting the phone and adjusting several other related setting and nothing would change.
If there is a known work around like a cfg or something that keeps track of the lock screen short cuts that would do the trick.
Thanks
DanGerousDroid said:
Cannot get the lock screen shortcuts to work with hyperdrive rom.
Noticed the issue, thought possibly got a bad flash. So I did another triple wipe/cache clear and installed the rom again. Still the same issue.
You can get as far as moving around the preset shortcuts, but when you try to click the (+) to add more the screen goes black before it pops up a message that settings has stopped. Tried rebooting the phone and adjusting several other related setting and nothing would change.
If there is a known work around like a cfg or something that keeps track of the lock screen short cuts that would do the trick.
Thanks
Click to expand...
Click to collapse
Known issue for Hyperdrive 14. It is being fixed for 15. In the mean time, start reading here: http://forum.xda-developers.com/showthread.php?t=2106830&highlight=lockscreen+shortcuts&page=462 for a way to fix it.
Thank you.
Let's hope I can figure this out.
Edit:
So I downloaded RLS13 and extracted the SecSettings.apk.
The question I have is do I simply overwrite the old one and reboot the phone, or should I zip the extracted file up and install it in TWRP?
Something strange and unexpected has happened with my Nexus 5... Upon first setting up my device after unlocking it and rooting it, I encrypted the phone before ever adding any of my info or apps to it, full knowing that I would forever have to use a locked screen etc. To side step the annoyance and lack of security that Android has with having the Encrypted boot time password being the exact same as the lockscreen's password I used this app 'Cryptfs Password' to change the boot time password to something much more lengthy and secure, while allowing me to have a standard simplified passcode for simple screen unlocks.
As time went on I found myself in need to wipe the device to troubleshoot an issue I was having with my wifi and wireless tethering no longer functioning properly, I wished to go back to an initial factory state to begin doing restores from Titanium to find the culprit per say and figur eout where I went wrong and borked my ability to toggle wifi.
Upon wiping the phone in TWRP (standard dalvik, cache, and ROM - not system or data) I rebooted and flashed my Titanium Backup.zip and Super USer.zip and then proceeded to set up the device again when I noticed something very odd...
I still needed to enter my previously exact password upon booting the device, however the lock screen no longer any security of any kind!
When I checked in settings this is what I found:
https://i.imgur.com/RR2SFxL.png
Clearly you can see the device is still encrypted however the default "slide" screen lock is now able to be used? Whaaaaat?!?!
Opening the Screen Lock settings menu reveals:
https://i.imgur.com/FtOqUY5.png
I have not yet sleected to change it to a PIN or PASSWORD as I am home and wanted to see if I could gather any other information about this first. I have a feeling that upon changing to a PIN or PASSWORD that I would not be able to change it back again.
Is this a flaw or error of some kind? I do not see any huge security vulnerability, I mean even though this does allow you to bypass the lockscreen, you still need the password at boot to even get into the phone or any Recovery - but this is interesting nonetheless. I was under the impression that it was IMPOSSIBLE to have both device encryption and essential NO LOCK SCREEN?!?!
I have seen threads such as this one: http://forum.xda-developers.com/showthread.php?t=1873700 where it is shown and discussed how to use the pattern lock for example, but this is obviously much different.
Can anyone else replicate this with their own android device?
EDIT:
Was able to find this thread https://groups.google.com/forum/#!topic/android-security-discuss/G4N5pBreyhM
where someone was able to essentially achieve a similar situation by using a 3rd party lock screen....
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.
Iv'e been having these issues for a few weeks now, maybe someone else had them too and can help with these...
1. There's a huge lag with the share menu on every app except for Google Photos. It takes about a minute to open and until it does the app just freezes. happens in Gallery, Facebook, Whatsapp and everywhere else.
2. There's also a huge lag when an app is trying to open another app. For example, if i click on a Youtube link in FB it would take about a minute to actually open the Youtube app. I tried changing the defaults in the settings but still nothing.
3. When i go to Settings, if i go to "Apps and Notifications", it takes about a minute for the menu to open. Once it does everything works ok but if i go into a certain app settings, and i hit "back" and it's supposed to go to the main apps menu, it lags again.
4. 90% of the time to "press power twice for camera" shortcut does not work. When i do it the phone vibrates like it always does but the Camera app doesn't open.
I am on 9.0.5, Magisk 19.1, XXX No Limits.
Things i tried:
- Reflashing the rom
- Uninstalling XXX and Magisk
- Wiping Cache in recovery
These didn't help much. I tried going to OB but i still had the problems so i went back to stable which wiped everything clean and solved the issues... until a few days later when they started again.
If anyone has any other suggestions, i would be happy to hear it. Thanks in advance!
If you did a clean flash and it reappeared, it's probably a rogue app. Do another and restore things one at a time until the problem recurs.
I'm also experiencing few bugs ever since switching to 905 on both slots, mostly WiFi issues and WhatsApp being very delaying with messages etc.
had the same setup as you thought I'll go use custom roms and it's the same on those, so I'm guessing it's 905 oos the bad Apple here
I confirm delay on Whatsup....
Can i revert to 9.0.3?
Did you try a Flash all by Fastboot?
You should have stayed with Oreo
I got myself in a bit of a pickle, I flashed Resurrection Remix 7.0.2 onto my Samsung Galaxy S5 yesterday for the first time (well actually, several times because I have no idea what I'm doing and soft-bricked my device more than once during the process) but what ended up happening was I got the phone set up how I liked it and then while playing around in display settings I turned on screen curtain, which makes the screen go black while the device still functions like normal.
I don't want to have to reflash it after I finally got it set up (although if I have to, I will), I saw a way to fix this for Lineageos through ADB and the vi editor. I Don't have enough posts yet as I am a new user (reddit /r/LineageOS/comments/90d0ku/lineageos_151_solved_accidentally_setting_screen/), the only problem is that I don't know what i would need to do in there for RR, so if anyone could help me out here I would appreciate it, thx.
MasterofAll43 said:
I got myself in a bit of a pickle, I flashed Resurrection Remix 7.0.2 onto my Samsung Galaxy S5 yesterday for the first time (well actually, several times because I have no idea what I'm doing and soft-bricked my device more than once during the process) but what ended up happening was I got the phone set up how I liked it and then while playing around in display settings I turned on screen curtain, which makes the screen go black while the device still functions like normal.
I don't want to have to reflash it after I finally got it set up (although if I have to, I will), I saw a way to fix this for Lineageos through ADB and the vi editor. I Don't have enough posts yet as I am a new user (reddit /r/LineageOS/comments/90d0ku/lineageos_151_solved_accidentally_setting_screen/), the only problem is that I don't know what i would need to do in there for RR, so if anyone could help me out here I would appreciate it, thx.
Click to expand...
Click to collapse
Go to system settings>apps, then look for the settings app, then open its app info page and select the storage option, then clear its data and cache then reboot the device. This should reset all of your settings and allow you to set everything back the way you want.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Go to system settings>apps, then look for the settings app, then open its app info page and select the storage option, then clear its data and cache then reboot the device. This should reset all of your settings and allow you to set everything back the way you want.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
The issue was that I wasn't able to see anything on the screen to even know what I was pressing, I did manage to get it figured out though, I had to use ADB and a computer. The file system settings path is exactly the same as for Lineageos.
I appreciate you actually replying though.