3 ms·
> I can't find a single reason to change my pixel for anything else, Fingerprint reader on the Pixel 7 works about half the time. I had to program one finger
by com2kid 4y ago
> I can't find a single reason to change my pixel for anything else,
Fingerprint reader on the Pixel 7 works about half the time. I had to program one finger in 4 times to make it work that often. My Oneplus 6 (immediately previous phone) had a functional fingerprint reader.
OnePlus used to have a better UI as well, minor improvements on the stock Android UI that made it just a little bit nicer in places.
When I got my Pixel 7 though, I realized that for whatever reason, gboard on my oneplus 6 is unusually terrible. Like, 80% accurate typing terrible, and that gboard isn't always that bad.
> Gmail works perfectly
Gmail was the first good web email client. Everyone else realized they had to stop sucking, and now they are good. Gmail was realized in 2004 and is from a completely different era of Google.
- jvolkman 4y agoMy Pixel 7's fingerprint reader works near 100% of the time. The only time I have problems is if my finger or the screen are wet.
- com2kid 4y agoWhat finger do you use? I use my left thumb, pick up the phone, no go. It is a complete sad joke. After a few weeks I think I've been trained by the phone on exactly how to hold is to the fingerprint reader works more often, but the fact I can only have to use all the programming slots for fingers on just one finger is sad. Edit: OMG, I just read online that rebooting the phone after recording fingerprints improves recognition from 20-50% to almost 100%. I just got my phone a month ago and haven't rebooted it yet, after a reboot the sensor now works reliably. What an absurd and stupid bug.
- jvolkman 4y agoI usually use my left thumb after taking it out of my left pant pocket. I also use a TPU screen protector, not glass. I've read that various glass protectors can interfere.
- com2kid 4y agoI'm using the screen protector that I bought from Google with my phone. But yeah, after rebooting, works fine. I cannot believe a bug like that is still on a device that has been out so long.