I downloaded and installed a clear lockscreen with the green android guy on it. I'm trying to switch it back to the full clear lock screen, and I seem to be having trouble.
i downloaded and installed the clearlock 1.1 from fresh, and he's still there!!
can anybody help? thanks.
Check out the pre-kitchen package, it has a utility to purge the lock screen cache.
http://forum.xda-developers.com/showthread.php?t=606172
Just reflash the Rom. You'll keep all your settings and it should be all clear.
That should do the trick
The fix: grab the new clear lock screen. Noj made the android guy green lock, and he also made a couple of clear locks to wipe it: http://geekfor.me/kitchen/lockscreens/
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?
Skyrocket i727 running CM-10.1-20130807 nightly. Apex launcher. On Rogers with UCMC1 radio.
It's running stable with the (big) exception that occasionally (once or twice a day) the four buttons at the bottom (settings/home/back/search) will not respond to any touch. The only way to fix it is to restart the phone. I searched the forums and cannot find an answer to why this might be happening, nor to anyone else having this problem. I have the backlight on these buttons disabled (to save power).
Also, this might be related or maybe not, but on Monday I had a very strange crash. The HOME button wouldn't work, but the BACK button and SETTINGS button did. The notification bar wasn't functioning and no push notifications were coming through. The quick-settings panel was reverted to default, and the buttons within the quick settings panel were completely unresponsive.
Even stranger, Chrome was unresponsive, Maps/Navigation were constantly force-closing, and in general the phone was throwing a massive fit over almost anything I did. I pulled the battery but that didn't help. I was forced to go into recovery mode and perform factory reset, wipe dalvik cache, and reinstall the ROM. This has worked (although a PITA) but the issue I mentioned first (bottom buttons not working) has manifested itself since then.
Any ideas what to do here?
Much appreciated!
Eric
Run the recent nightly. Could be an issue with your rom, although I haven't seen your problem.
I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)
curls00 said:
I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)
Click to expand...
Click to collapse
You should be ok. I never go back and wipe caches
The original issue is still occurring even on newest nightly. Completely random (using different apps each time - Facebook, Messenger, Youtube, etc...).
Any idea if a setting I can change is causing this?
mtdew said:
Hardware failure.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
LOL time to sell then!
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.