tl;dr: lock function no longer working after upgrade from official 1.6 to 2.1
I know this is a duplicate post from two others, but they never got any replies, I'm just trying my luck here.
New phone, preloaded with 1.6, no third party apps other than carriers bloat. Lock screen functions just fine on 1.6 and I have never attempted any "rooting" to this device.
Once I perform the official update with Samsung Kies Mini, the lock screen never shows up. It boots right to the home screen and the lock button now only turns off the back-light.
Tried enabling pattern lock, but it never shows. Performed system reset back to 1.6 and the lock screen returns. My carrier, Rogers (Canada), has never heard of this and is going to exchange my phone. However I want to find out if anyone else has a cure for this weird bug before my replacement arrives Friday (Nov 5).
Try changing backlight timeout in settings- on 2.1 screen is locked when light goes off. Maybe somehow system is set to "never"
Hi everyone ...
[Updated in post #3]
I faced a terrible lag with my SM-900 after 4.4.2 update and I read a lot about this bad combination (S View + Lock with PIN) but I was forced to use the lock screen bcz of the company email server.
So, I decided to go into some experiments:
- Wiped cache partition: didn't solve
- Flashed stock Rom: didn't solve
- Used stock cover: didn't solve
- Removed the exchange account and lock screen: didn't solve
So, I decide to start from scratch. I flashed the stock rom with Odin then a factory reset without the S View cover. I didn't install except very few apps (FB, Whatsapp and viber). The lag disappeared and the system was snappy and very smooth. After couple of days I put the S View cover and the system kept running smooth as is. After another couple of days I enabled the lock screen with PIN and the system is still in a very good shape and the clock of the lock screen always shows the right time and the home button response to wake up is perfect.
That eliminates the theory of SV+LS cause of lag. However, I 'll wait for few days then I will configure the company exchange account and update this post again.
Hope this is useful for some people who's facing this annoying problem.
Biso007 said:
Hi everyone ...
I faced a terrible lag with my SM-900 after 4.4.2 update and I read a lot about this bad combination (S View + Lock with PIN) but I was forced to use the lock screen bcz of the company email server.
So, I decided to go into some experiments:
- Wiped cache partition: didn't solve
- Flashed stock Rom: didn't solve
- Used stock cover: didn't solve
- Removed the exchange account and lock screen: didn't solve
So, I decide to start from scratch. I flashed the stock rom with Odin then a factory reset without the S View cover. I didn't install except very few apps (FB, Whatsapp and viber). The lag disappeared and the system was snappy and very smooth. After couple of days I put the S View cover and the system kept running smooth as is. After another couple of days I enabled the lock screen with PIN and the system is still in a very good shape and the clock of the lock screen always shows the right time and the home button response to wake up is perfect.
That eliminates the theory of SV+LS cause of lag. However, I 'll wait for few days then I will configure the company exchange account and update this post again.
Hope this is useful for some people who's facing this annoying problem.
Click to expand...
Click to collapse
Hi,
Please keep updating about this LAG issue. I have the same problems and have the same configuration of corporate exchange email and PIN lock.
Did not find a solution for the lag yet.
Thanks!
Update:
I configured the Exchange account for 5 days now. The device is still working very fine with no "noticeable" lag. However, I have noticed the following:
- for only once the screen didn't come on with an incoming phone call.
- Now the clock on the lock screen always doesn't match the system clock when you flip the S View cover.
Conclusion: I tend to believe that 4.4.2 for Note 3 has a bug somewhere in the lock screen process, and this bug is building the lag issue with time. Also, I believe as well that the OTA process for 4.4.2 on top of existing data brings this issue very fast. I think the best way is to do a factory reset then update/flash the device with the stock 4.4.2 (through Odin) then to start by enabling the lock screen with PIN before configuring the Exchange account.
I don't have a scientific explanation to prove this will work for everyone, but that what worked for me
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks!:crying: I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet and never had a flip cover or any sort of case so literally don't know why it happened.
Thanks in advance,
Max
Hi
I had the exact same issue with mine, I was on LineageOS and could access the logs so I was able to determine it was an hardware failure.
Went to a repair shop to replace the home button, and Bam it worked again.
If you didn't flash a custom ROM it is likely an hardware issue just like I had.
Hi, first of all I apologise if this question has been asked but I don't know how to search just this place.
I'm using everything stock, no root, stock launcher.
I have my phone set up to ask for the password on reboot. I have my fingerprint reader set up to unlock my phone. I also have the fingerprint reader set up to wake the screen.
However under certain circumstances the fingerprint reader does not unlock the phone. The most reliable way to trigger this behavior is to plug the phone in to charge.
I exclusively lock the screen with the power button.
The fingerprint reader is still responsive and it still wakes the screen but there's no vibration feedback and it does not unlock. After I unlocked the phone with my password and lock it again the reader works again.
So what's going on here? How should I debug this?
After reboot it is normal to ask for password first time. Sometimes i have also seen this but when i unlock with pattern (my backup way) and lock again it works fine. I can not trace this to be related with charging or something else and it happens rarely but i have seen it also. Maybe a software bug.
Looking back to the days when i have LG V10 i remember that i had the same problem with fingerprint sensor not working sometimes. It was more frequently related to heat buildup as it was hot phone anyway.
I had the same problem these days, I think the fingerprint reader won't work if your hands are really cold.
Hmm I don't think my U Ultra is getting particularly hot and, no, my hands are certainly not very cold either. This behavior happens indoors.
It's just extra security plan and simple
Sometimes, not very often though, my fingerprint reader refuses to respond. Not even a misread where you get haptic feedback and not a lot else.
Just using the power button and entering my back up security (pattern in my case) and it comes back to life.
I don't particularly worry about it, but I suppose it's nice to see that it's not just me
Will see if the upgrade to 8.0 fixes it.
I met this problem.The solution was very interesting.I use Yandex.disk app.This problem did occur after the Yandex.disk app is update.I hard reset my phone.The problem was not in my phone.But I setup Yandex.Disk app the problem repeat occur.İf you installed Yandex.Disk, uninstall the application.if you don't use Yandex.Disk,The last apps update uninstall to try.
Good Lord I have so many apps installed though...
Then go to a full factory reset and see if it helps, thats the 1st thing you do when you have problem.
After a bit of experimentation this behavior seems to have stopped after I disabled/removed all Smart Lock Trusted Places -- a feature that is already known to be buggy.
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Garkan said:
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Click to expand...
Click to collapse
8 fixed this bug for me but i found more bugs in oreo so i am thinking to roll back to 7.0 and meet fingerprint sensor bug again because oreo problems are disgusting - car bluetooth does not works as it should - i can't read addressbook in my car head unit - it shows error. i found that is some bluetooth software parts was not included in 8.0 but successfully fixed in 8.1. and i'am pretty sure we will never receive 8.1 for u ultra.
in russian 4pda forum i found some reports (unconfirmed yet) that fingerprint bug disappeared. maybe somebody here can confirmed it?
No i have android 8 and issue still occurs sadly did not found a fix.
I've suddenly had this issue a couple of days ago a couple of times. I didn't do anything (except a couple of reboots) and it was fixed again.
Now after updating to Oreo and again using leedroids ROM, i didn't experience theissue again..
I talked to a htc representative and said to clear credentials from security/encryption and credentials seems to be a conflict in security certificates. For the moment it works.
Hello everyone,
after the pie update 10.0.4.0 I am noticing a strange problem, which I am trying to figure out right now.
It began, that after waking up and picking up my phone, the lock screen pattern was enabled again (I am using the smart lock feature at home when connected to my wifi). On the phone there was a notification like "After a reboot you have to enter the pin again to unlock the phone" or something similiar.
After some time I noticed, that the phone wakes up by itself, the screen comes on and there is no carrier signal ("emergency calls only") for a very short time (maybe a second or two). After that the notification "Checking SD-card" appears. So it seems like the SIM & SD-card would have been unmounted by the system. It can happen everytime and is not related to a specific app.
What I did:
1.) I put the SD-card into my PC and checked it for corruption
2.) Disabled some gallery apps, which I installed last december
3.) Waited for the february 10.0.5.0 update
Unfortunately, without success.
Today I was able to note the exact time the issue happend again (14:51 o'clock) and pulled a logcat. I wanted to read an Focus news article from the notification tray and then it happened. Because I am not sure, if a hardware or software problem is the cause , I need your help:
It would be awesome, if someone could have a look at the attached logcat and give me some hints and advices what might be the problem.
Thank you very much!