• 28 Posts
  • 642 Comments
Joined 3 years ago
cake
Cake day: January 8th, 2024

help-circle


  • I think low battery notifications should be part of AOSP, so they should be in all Android flavors. So the fact that you don’t have them seems odd to me.

    Personally, I’m using an app called BatteryBot from FDroid. It doesn’t do much, but what it does allow you to do is set notifications at custom battery percentages. So I have it set to send an alert and vibrate my phone when it gets below 30% and then I plug it in and charge it up to 80% where the system has been set to stop charging it and I get another alert once it hits 80%. Well, okay, to be fair, I have it set to go off at 80%, but it does not go off until it’s above 80%, so I have the phone charged to 81%, and it doesn’t go off at 30%. It goes off when the charge drops below 30%, so it goes off at 29%.









  • I have touched the fingerprint reader on accident with the incorrect finger when picking the device up or something because it’s on the side with the power button, but I have never had an issue where I’ve meant to unlock my device with the correct finger and used the wrong finger instead.

    I have used the wrong finger on purpose in order to press the power button in order to bring up my lock screen without actually unlocking the phone to see the time or whatever, though so perhaps a 3 strikes your out rule would be best where if you hit the fingerprint reader with the wrong finger 3 times in a row it would then wipe

    Let’s say my pointer finger is the registered finger for the reader. If I want to unlock my phone, I’ll just touch the fingerprint reader with my pointer finger and the phone is unlocked. If I wanted to say interact with a running media file, or check the time, I would deliberately press the power button with my middle finger, that way it registers it as a press to bring up the lock screen, but does not unlock the phone. And then, when I want into the phone next time, I would touch the fingerprint reader with my pointer finger to unlock it. If I am picking my phone up off of a table, for example, and my ring finger just happens to touch the fingerprint reader, it’s obviously not going to recognize, and then once I get the phone in my hand properly, I would use my pointer finger to unlock it.

    This is why I think perhaps a three-time rule might work, where if you deliberately touch the fingerprint reader three times within a short period of time with the incorrect finger, it would initiate a wipe.

    I’m thinking maybe like within 10 seconds.





  • The problem for screen reader users is that the better the voice sounds, the slower you have to use it at. And screen reader users generally like reading things at high rates of speed, and so generally are more willing to put up with the lower quality voices to get the faster speed.

    For something like your map application that says in 300 feet turn left onto X name of road it’s fine but for a screen reader user it’s a problem.