W1zardK1ng You have to first register a fingerprint, and then enable fingerprint unlock, then you'll see it.
GrapheneOS version 2024123000 released
- Edited
Been waiting for this update for a while. Already using fingerprint unlock plus pin, and loving it.
- Edited
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.
- Edited
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.
- Edited
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.
xdg-7 It's because we don't include the Verizon bloatware apps. It no longer works on Android 15 QPR1 without them. Need to switch carriers since it's not feasible to solve without using their apps.
DeletedUser69 It's useful to keep it plugged in because it has bypass charging to use power directly from the charger without going through the battery. It shows the shield icon while doing this. The battery will last even longer if you leave the device plugged in since it's avoiding using it.
GrapheneOS It's because we don't include the Verizon bloatware apps. It no longer works on Android 15 QPR1 without them. Need to switch carriers since it's not feasible to solve without using their apps.
Is that true of Verizon MVNOs, or Verizon's own service?
GrapheneOS Thank you for the restrictive charging function, I love it. But I got an issue that is triggered by it. Seedvault backup fails, and it fails once a second when the charge level reaches the limit of 80% (has happened two times now). It sends a notification every second, and the only way to get it to stop is to reboot the phone. If I go into the Seedvault settings, some of the options is strobing on/off tens of times a second. Seems like Seedvault really didn't like the restrictive charging 😅
Options that are strobing:
Backup placement (top option)
Check integrity
Backup now (inside the three dots menu)
Restore backup (inside the three dots menu)
Thank you for both 2-factor fingerprint unlock and restrictive charging. I really love them.
It's useful to keep it plugged in because it has bypass charging to use power directly from the charger without going through the battery. It shows the shield icon while doing this. The battery will last even longer if you leave the device plugged in since it's avoiding using it.
As also asked in the dedicated "New Battery Bypass feature in GOS?" thread:
Does the battery bypass require the use of a USB-C Power Delivery charger with PPS (Programmable Power Supply) feature support?
Or does it work with any USB power source?
Samsung devices apparently require the use of a USB-C Power Delivery charger with PPS feature for the battery bypass (called "Pause USB Power Delivery" on Samsung devices) to work.
In the following random example video, the power meter seems to indicate that the phone is essentially constantly drawing around 8 Volts from the PPS power supply when using the battery bypass mode:
https://www.youtube.com/watch?v=YvAWT-zIWhQ
Maybe this is because batteries typically output around 3.7 to 4.2 Volts and therefore maybe a phone still requires this voltage range when bypassing the battery. Maybe in this case the phone has a built-in voltage step down converter to half the around 8 Volts to around 4 Volts to then constantly operate at around 4 Volts in the battery bypass mode.
That maybe could explain why a PPS compatible USB-C power supply is required for the battery bypass. Because only PPS compatible power supplies are able to output variable and dynamic inbetween voltage values, whereas non-PPS power supplies are limited to fixed voltage values such as 5 Volts and 9 Volts for example.
Maybe someone can clarify if Pixel devices also require a PPS compatible power supply for the battery bypass feature to work.
DeletedUser130 generally, you manipulate amperage, not voltage. The voltage always stays constant. The amperage goes up or down depending on power draw.
de0u did you happen to find this out?