Hi,
I have a S4 GT-I9505 running lineage_jfltexx Version 20190912 nightly.
After a few days, I was not able to unlock the screen with my pin.
When I entered the correct Pin, the unlock screen appeared again after a few seconds.
Entering a wrong pin gave an error message - wrong pin entered.
The current fix I'm using is:
Setting screen-lock-mode to 2 (instead of 0) in /data/system/profiles.xml
This disables the screen lock altogehter.
I found out a work around by creating a new user and a new profile with a lock-screen feature.
When I use the lock-screen feature profile, I cannot unlock as primary user (infinity loop).
Switching to the new user, I can unlock the phone, switch to a profile without lock and
switch to the primary user again.
So there has to be a problem with the user profile of the primary user.
How can I reset this profile for the system settings?
I tried clearing the system settings cache, but this did not work.
Thanks.
Hi fkno,
Same issue for me.
Do you succeed to deal with this issue in a better way?
Thanks
fkno said:
Hi,
I have a S4 GT-I9505 running lineage_jfltexx Version 20190912 nightly.
After a few days, I was not able to unlock the screen with my pin.
When I entered the correct Pin, the unlock screen appeared again after a few seconds.
Entering a wrong pin gave an error message - wrong pin entered.
The current fix I'm using is:
Setting screen-lock-mode to 2 (instead of 0) in /data/system/profiles.xml
This disables the screen lock altogehter.
I found out a work around by creating a new user and a new profile with a lock-screen feature.
When I use the lock-screen feature profile, I cannot unlock as primary user (infinity loop).
Switching to the new user, I can unlock the phone, switch to a profile without lock and
switch to the primary user again.
So there has to be a problem with the user profile of the primary user.
How can I reset this profile for the system settings?
I tried clearing the system settings cache, but this did not work.
Thanks.
Click to expand...
Click to collapse
Koputy said:
Hi fkno,
Same issue for me.
Do you succeed to deal with this issue in a better way?
Thanks
Click to expand...
Click to collapse
Not yet.
I tried to track the problem. Changing the pin / trying to unlock the phone and
see, which sections in the user profile got a new timestamp.
For me, it looks like it is in the com.google.android.gms section of the user profile.
I'm not sure, wether I can delete or overwrite this directory while the phone is running.
And if I delete this section, wether it will be recreated when rebooting the phone.
Hi,
Why don't you move to Lineage OS 17.1 ? It is awesome thanks to JDC team and LOS teams.
https://forum.xda-developers.com/ga...y-s4-i9505-t3517706/post70049958#post70049958
djibe89 said:
Hi,
Why don't you move to Lineage OS 17.1 ? It is awesome thanks to JDC team and LOS teams.
https://forum.xda-developers.com/ga...y-s4-i9505-t3517706/post70049958#post70049958
Click to expand...
Click to collapse
FYI, I have the same identical problem on LOS 17.1 but on a different device (marmite). This is an Android issue, not something related to this or that LOS version.
Related
Hello. I am using i9505. No matter whichever ROM I use, pin lock doesn't set in immediately. Only after a minute or so, pin lock appears. Before that it remains unsecured with swipe to unlock.
Any idea?
Sent from my GT-P5100 using XDA Free mobile app
lalit.kultham said:
Hello. I am using i9505. No matter whichever ROM I use, pin lock doesn't set in immediately. Only after a minute or so, pin lock appears. Before that it remains unsecured with swipe to unlock.
Any idea?
Sent from my GT-P5100 using XDA Free mobile app
Click to expand...
Click to collapse
Did you find a solution?
I have the same issue. It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result, basically the PIN lock does not activate untill 30 seconds or so after the phone boots up.
Same issue and same model, only using stock rom i coukd fix the problem. Doesn't matter the kernel etc. It does not work.
Did you find a different solution?
scott2ride said:
Did you find a solution?
I have the same issue. It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result, basically the PIN lock does not activate untill 30 seconds or so after the phone boots up.
Click to expand...
Click to collapse
I changed to a pattern lock for now. And to increase security I don't have the swipe tail/trail displayed.
I was able to solve the issue, it was a problem with permissions and file ownership.
I have replaced the owner of /data/system/locksettings.db, locksettings.db-wal and locksettings.db-shm to system and also password.key, gesture.key.
Before doing that please execute a nandroid backup, if not you could probably run into an unbootable device.
cloudlord said:
Same issue and same model, only using stock rom i coukd fix the problem. Doesn't matter the kernel etc. It does not work.
Did you find a different solution?
Click to expand...
Click to collapse
cloudlord said:
I was able to solve the issue, it was a problem with permissions and file ownership.
I have replaced the owner of /data/system/locksettings.db, locksettings.db-wal and locksettings.db-shm to system and also password.key, gesture.key.
Before doing that please execute a nandroid backup, if not you could probably run into an unbootable device.
Click to expand...
Click to collapse
Hello guys. Adam Kernel fixes this issue.
Anyone tried CM12 on their Nexus 10 yet?
I installed it, and then tried to add new user (wife), wizard started, i entered gmail acount and password and then weird things started to happen.
Accessibility option was immediatelly started and I am unable to switch it off (Accessibility means the tablet starts to speak what you see, you can't click normalny on things, pretty annoying).
Tried it with different accounts too.
Any help would be appretiated how to disable this auto-accessibility starting after new user is added..
Currently Guest profile seems to be working ok, the drawback is, that after switching you have to confirm you want to continue in previous guest session..
EDIT: Forgot to mention that CM12 on my Nexus10 runs pretty fast compared to stock 5.0.1 (unfortunatelly, I installed CM12 day before Google announced 5.1 lollipop).
Settings > Users > Add New User Help
sarnowak said:
Anyone tried CM12 on their Nexus 10 yet?
Click to expand...
Click to collapse
Settings > Users > Add New User
While Creating New user it just stuck at cyanogenmod logo and light blue screen and with processing for a long long time and it never complete.
Any help in this matter please.
All things are successfully done. Rooting, Flash, Recovery, Rom, Gapps, All set and working for owner user fine and fantastic, but New user creation is nor finishing it just continuously processing and processing and processing.
Tried installing Rom many times.
CM12-maguro
Nightly built cm12 20150313 fixes this issue.
I can now create new profiles with no problem.
sarnowak said:
Nightly built cm12 20150313 fixes this issue.
I can now create new profiles with no problem.
Click to expand...
Click to collapse
Can you provide a download link!
Put in Google: cm12 manta download
Well, I configured my 6P with the fingerprint/pin combo at startup and was using it like that...
I then disabled any security, and that meant wiping off my fingerprints.
I then tried to set everything up again, that means fingerprint+PIN. It set up correctly, I even set up to ask for PIN each time I reboot the device... This is where it gets weird.
When I booted up for thr first time, and went through Imprint+PIN setup, whenever I'd restart the phone, it would greet me with the secure startup screen , asking for my PIN in order to continue starting up the device. It would then boot me to my lockscreen. Where I'd have to input my PIN/fingerprint in order to unlock to desktop.
Now that I re-set it up, it will ask me for my PIN before booting up, but now it won't boot me to my lockscreen, but directly to desktop.
If I disable asking for PIN at boot, I get booted to lockscreen.
How can I restore functionality? Is this normal?
Since this is an Android N Dev Preview regarding issue, you should report it to Google if at all. Dev Preview is not meant to be used as a daily driver and some bugs should be expected to experience.
neisor said:
Since this is an Android N Dev Preview regarding issue, you should report it to Google if at all. Dev Preview is not meant to be used as a daily driver and some bugs should be expected to experience.
Click to expand...
Click to collapse
But it was working accordingly on N. I bet it's an issue even on MM.
benleonheart said:
But it was working accordingly on N. I bet it's an issue even on MM.
Click to expand...
Click to collapse
I do not think this issue is affecting MM.
Anyway, was the security working before on Dev Preview 4? Or it worked on previous Dev Previews and on the 4th it's not?
neisor said:
I do not think this issue is affecting MM.
Anyway, was the security working before on Dev Preview 4? Or it worked on previous Dev Previews and on the 4th it's not?
Click to expand...
Click to collapse
Workes on previous and on 4.
Disabled PIN/fingerprints and re enabled them and set them up again but to no avail...
For starters, ive been using the same lockscreen pin on ALL of my devices for the past3 years, I know im using the right one. I recently installed the Evolution ROM and set it up with fingerprint and PIN. Fingerprint was working just fine, I rebooted the phone after installing a magisk module and now its telling me the pin for the lockscreen and TWRP is wrong. Again, I only use ONE pin and its telling me its wrong. Tried deleting the locksettings.db file to take off the screen lock and that worked but now phone just stays on "Phone is starting" and TWRP is still excrypted but lets me see all of my files, correct storage amount, and install zips.
When you installed did you format data?
I know this says Lineage, but it works for most custom ROMs, post #2 has the cliff notes version: [Guide]Installing Lineage
As for the locksettings.db, this isn't like older Android devices. You can't just do that, it doesn't fix the problem here.
hi all,
Just got my 6t, come from 5t. as usual unlocked then latest twrp from @mauronofrio "thnx" and on defaul 10.3.4.
had strange problem with screen lock section. ive tried with pin, password, pattern all the same, its asks for 2 times as usual then i am setting up all is ok till here. then it never accepts i had to delete password db things under system with twrp file manager.
does any one had the issue?
any solution?
thnx