alphapuggle

Seeing people say "GrapheneOS fixes this!" "It's only on old versions of Android!"

This is on a Pixel 8 Pro with the latest version of GrapheneOS. This is an issue and has been for a long time. Many apps detect root by looking for the Magisk package using this method, and many collect this information just for advertising (go ahead, export your Snapchat data)

Google domains bit me in the ass. No way they'd shut that down, I told myself.

Giving them your genetic data was fine, but your birthday was too much?

No, The OneNote UWP app is going away ("OneNote for Windows 10"), OneNote itself is still a part of office & still maintained

Gulf of Acrisure

Somehow they'll still make the hinges break

Tradeoff between speed & accuracy vs the amount of fingerprints. The data that would've been required to store a 5th is instead used to have better models of the other 4. Id rather have a faster reader that'll read it right in more angles than an extra fingerprint when I only really use my thumb and index anyway. (Also you can totally train 2 different fingers in one "finger" and it'll recognize both, just worse

Ah I see the concern there. Fingerprint data isn't handled as much on the software side as it is through the hardware. Android doesn't get access to what's actually scanned, just whether a scan was read and if it matched what the reader was expecting, Scanners are limited to a certain number of entries depending on how much space is available to store fingerprint data, which is why my 256gb phone can only store 4 fingers. It's also why you can't add separate fingers in separate apps, they all use android's API to determine whether a biometric scan was a success or not.

I've never had a phone that had one mounted anywhere other than the front, so under screen was natural muscle memory progression for me compared to side or back mounted.

I am curious of what you dont trust and why

The wording is a bit weird, but I'll try to explain what's actually happening here;

This is referring to the pixel's under screen fingerprint reader. Since it's an optical reader, it needs light to see what it's reading so it blasts a white circle around the reader. Currently if the screen is off (we'll get back to this in a sec) then it can't turn this circle on to read the finger. Basically there's an "off" and a "black" with oleds, they'll look identical, but If the screen is "off" you won't be able to light up a section. This can occur when the always-on-display is active, but not if it's disabled. From what I gather this leaves the display in an "black" state so it can still light up the reader, even if AOD is disabled

Also totally accidentally sent this when trying to check the MD ob "off", hopefully you haven't checked this message yet lol

While this is the ideal outcome, in reality people are just going to throw their trash in the bushes.

Yeah but it'd be kinda weird if the demo said "Idk man Toastify is aight I guess"