Ammako Depends, are the 4 words in any dictionary in the first place?
They definitely are if you were able to select them randomly in a secure way to begin with. Whether the list is published or not is another thing, but keeping it secret actually add very little extra entropy per word, so no real reason to keep the list secret either.
Remember, the brain is the worst random number generator ever made. So you need a word list.
ryrona It starts with scrypt in the OS but it finishes with a device-dependent key derivation algorithm in the TEE. We can't modify the final phase of key derivation at the end since it's done in the Trusty-based TEE. We could increase the scrypt parameters but we want to determine precisely what happens across each device generation. It would be best if we filed an issue report requesting specific improvements to the TEE key derivation after putting research into it and got them to improve things there. It would be far better if it spent 100ms there using a good hardware accelerated algorithm with a hardware-bound key instead of 100ms in the OS with scrypt, but we can raise what the OS does in the meantime. However, anything we do will need to be a supported encryption format until the end-of-life of each of the devices since users may be upgrading from a very old version to the latest one over 6 years from now for devices with 7 years of support. That's a huge long term support commitment. That's why we haven't been fiddling with this. If we're going to change it, maybe we should replace scrypt instead of tuning it to take longer and use more memory.
Where is the charge limit toggle? I do not see it in Battery Settings nor by searching "limit" in settings
jumpdeer It is the 4th position under Battery settings
phone-company
Not completely.
I'm not a beginner. Of course, I have already deactivated vibration and haptic feedback.
But it doesn't help when switching on, it still vibrates.
My device has rebooted by itself after the install but I have configured to do not autoreboot after install
Do I understand correctly that bypass charging is enabled automatically when charging limit is enabled?
It would make sense, though I expected a separate toggle or at least a mention of this on settings page.
Eagle_Owl okay will check it later on my test device
W1zardK1ng You have to first register a fingerprint, and then enable fingerprint unlock, then you'll see it.
Been waiting for this update for a while. Already using fingerprint unlock plus pin, and loving it.
Fingerprint has been something I have never used. Reasons should be obvious. PIN + FP authentication is all new to me and I am liking it.
Perhaps the only thing I don't especially like is after a number of failed FP attempts it reverts to passphrase, but it is too easy to back out to FP. On that, I would like to see a lockout policy. Enforce the passphrase or lockout for say 10 minutes persistent across a reboot.
And 80% charge limiting... Great! 👍
I am sure there is more, but these two features stand out the most for me.
A big thank you to the devs for their work.
HMC Perhaps the only thing I don't especially like is after a number of failed FP attempts it reverts to passphrase, but it is too easy to back out to FP.
Can you say more about "backing out" to fingerprint unlock? For example, a list of steps to reproduce?
HMC On that, I would like to see a lockout policy. Enforce the passphrase or lockout for say 10 minutes persistent across a reboot.
I think a reboot forces use of the primary unlock? According to design, a successful primary lock should enable the secondary unlock.
Again, all created PWAs Apps from the standard launcher again after the update reboot.
Thank you very much for long awaited/longed for feature (restricted charging). An audio cue (i.e. notification), may be beneficial for those who wish to unplug the device upon reaching desired charge. Thank you. Worth donating, soon I guess.
HMC Perhaps the only thing I don't especially like is after a number of failed FP attempts it reverts to passphrase, but it is too easy to back out to FP. On that, I would like to see a lockout policy. Enforce the passphrase...
Well... I found it does enforce the passphrase after a few more (10?) failed FP attempts, so that is good.
Unfortunately mobile data is still broken on the verizon mvno Total Wireless on my pixel 6. This issue first cropped up in version 2024120900
nazar-pc Yes, it's enabled automatically and shows the shield icon when it's active.
HMC It only permits 5 failed unlock attempts with fingerprint unlock. If you use the 2nd factor PIN, it counts failures to enter that correctly towards the limit of 5. You can't bypass this by using the back button. The user interface showing is still there but it won't accept it anymore after 5 failures. Fingerprint unlock can only be used After First Unlock and for 48 hours since the last successful unlock with the primary unlock method. It also has the limit of 5 failures. On the stock OS, the attempt limit is 20 split into 4 sets of 5 failures with 30 second delays between them which we didn't think made sense so we removed it. Removing it also allows quickly locking it out by purposely failing to scan with the wrong finger 5 times.
HMC It shows the primary unlock method after 3 failed attempts but it has a hard limit of 5 attempts. It's not 10. The fact that it's split this way is useful since it can help stop you getting locked out of using it via accidentally touching it in a pocket, etc. This is all the standard way it works on Android beyond us making the initial soft lockout for 30 seconds into the hard lockout instead of permitting 4 sets of 5 attempts for a total of 20 attempts.
