There seems to be a bug in 5.1.1 that for sure affects the N910T3 that comes with 5.1.1 and the Sprint Note 4 that has 5.1.1. It may or may not affect the N910T using ROMS based on the T3 5.1.1.
That is where my request comes in. For one I would like to get some feedback from users that use the fingerprint unlock.
To briefly describe the bug: The bug occurs when a user sets the unlock method of the phone to fingerprint. The bug will cause the phone to randomly lock in the middle of use. For example one could be texting someone and randomly the phone freezes, shows the wall paper will nothing on it, and then the phone locks.
The only solution to resolve the problem as of now is to not use the fingerprint unlock method. This clearly is not an acceptable solution.
At first I thought there was something wrong with the T3 and was posting on here to find the answer but I recently discovered that other Note 4 variants that received the 5.1.1 like the Sprint version also face the same exact issue.
So Devs with a T3 or a similar variant (one officially on 5.1.1) could you please help investigate this? I cant help but think perhaps one could find a solution to this bug by replacing something. Perhaps its impossible and we must wait for an official bug fix FW but one can hope.
Thanks!
That is where my request comes in. For one I would like to get some feedback from users that use the fingerprint unlock.
To briefly describe the bug: The bug occurs when a user sets the unlock method of the phone to fingerprint. The bug will cause the phone to randomly lock in the middle of use. For example one could be texting someone and randomly the phone freezes, shows the wall paper will nothing on it, and then the phone locks.
The only solution to resolve the problem as of now is to not use the fingerprint unlock method. This clearly is not an acceptable solution.
At first I thought there was something wrong with the T3 and was posting on here to find the answer but I recently discovered that other Note 4 variants that received the 5.1.1 like the Sprint version also face the same exact issue.
So Devs with a T3 or a similar variant (one officially on 5.1.1) could you please help investigate this? I cant help but think perhaps one could find a solution to this bug by replacing something. Perhaps its impossible and we must wait for an official bug fix FW but one can hope.
Thanks!
No comments:
Post a Comment