this post was submitted on 20 Oct 2023
106 points (98.2% liked)

Android

27895 readers
34 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

[email protected]


founded 1 year ago
MODERATORS
 

Hey folks. Got a pixel 7 pro, and it's been alright, except suddenly, if I press the fingerprint sensor on the lock screen for just a split second, it makes the WHOLE SCREEN go full-brightness, with a green tinge. I know it's always lit up the scanner area, which is all it lights up if I hold the sensor, but if I release it early it's actually very uncomfortable. Any suggestions besides the obvious "don't let go 5head"? Is this an android version bug, a hardware issue? Anyone else had this happen?

Edit: autocorrect

Edit 2:

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 33 points 1 year ago (1 children)

Just close your eyes 5head

[–] [email protected] 20 points 1 year ago (1 children)

Aw heck, I hadn't thought of that.

[–] [email protected] 12 points 1 year ago (1 children)
[–] [email protected] 6 points 1 year ago

It worked! I'm not blind this morning!

[–] [email protected] 18 points 1 year ago* (last edited 1 year ago) (3 children)

you probably have face/iris unlock enabled, I dont have that phone specifically, but some phones will use the screen to make sure there is enough light for the sensor to work

EDIT: I thin it might just be face unlock

[–] [email protected] 10 points 1 year ago (1 children)

No, face unlock on Pixels doesn't do anything to illuminate your face, it simply refuses to work if the lighting's too dim. It's actually worse than the face unlock in Google Smart Lock in dealing with low light environments.

[–] [email protected] 6 points 1 year ago (1 children)

*most pixels

The 4XL had the best face detection in the industry, employing an additional infrared camera with its own invisible light.

[–] [email protected] 3 points 1 year ago

I didn't buy a pixel 4 because it was Google's first attempt at face unlock. Decided to spice things up and get an iPhone for a change. FaceID is fanfuckingtadtic and I'm sad that my pixel 7 doesn't have proper face unlock.

Imo: rear mounted fingerprint sensor > proper face unlock > under screen fingerprint.

[–] [email protected] 9 points 1 year ago (1 children)

I did have face unlock enabled. I doubted it was the cause of the issue, but went ahead and disabled it, can confirm that it's still flashing me.

[–] [email protected] 3 points 1 year ago (1 children)

I can't say what it could be then. I would be inclined to think it a software bug considering it seems to only happen under this specific scenario?

[–] [email protected] 2 points 1 year ago (1 children)

In further testing, any use of the fingerprint sensor can cause it. Lock screen, or in app authentication. It's like the flash that's normally under just the scanner instead happens on the entire screen. It happens consistently if I tap the scanner for about the shortest possible time I physically can.

[–] [email protected] 3 points 1 year ago

ah, that might indeed be indicative of a hardware faliure

[–] [email protected] 3 points 1 year ago

I just edited OP with a video.

[–] [email protected] 15 points 1 year ago

I have a Pixel 7 and mine does the same flash bang thing on fingerprint. I just figured it was to "see" the fingerprint better. I only notice it when it's really dark.

Hilarious way to describe it. I knew right away what you were talking about.

[–] [email protected] 10 points 1 year ago (1 children)

Better than being fingerbanged by your flashprint sensor

[–] [email protected] 7 points 1 year ago (1 children)

At least that could be fun. This only hurts.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Lol, I guess.. 😃

[–] [email protected] 10 points 1 year ago (2 children)
[–] [email protected] 10 points 1 year ago (1 children)
[–] [email protected] 6 points 1 year ago

More accurate than the my description, turns out, but same energy.

[–] [email protected] 7 points 1 year ago

It's a meme lol. Like "you didn't think of the obvious solution? -hand on forehead-" but meme-ified

[–] [email protected] 6 points 1 year ago (1 children)

I've got a Pixel 7 Pro and this doesn't happen with mine so it's possibly a defect with yours. No idea how that could happen, though as it sounds more like a software issue

[–] [email protected] 3 points 1 year ago (1 children)

It's a really weird issue for sure. I've had nothing but issues with this screen. I've had it for all of 4 months, and had to have the screen replaced for a band across the center horizontally that was not accepting touch. Three screens later, and finally I have one that doesn't have any visual or touch defects, and now I get flashbanged if I fumble unlocking it. Ugh.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

If you're consistently having screen issues with your Pixel and it's not due to any accidental damage but straight out the box it could very well be a problem with the motherboard. Various ways to solve this like contacting Google and seeing if they'll do an in-warranty replacement device, or you could see if a Google authorized repair center will do a MOBO replacement. However the suggestion I commented elsewhere in this thread is the better 1st step to take

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (2 children)

Yeah, I've had 4 screens replaced. First one, a horizontal band just stopped taking touch input about 3/4 of the way down, and then they replaced it 3 times, each with unique display issues out of the box, and now this lol. This is my first Google phone and, honestly, probably my last.

Edit:just realized you were replying in a chain I had already explained all of that. Oh well!

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

To be perfectly honest this is why I don't like Pixels. Every manufacturer has issues of course. I'm not saying Pixels are bad, just I wouldn't get them because of personal preference and the design. The Pixel 4s constantly had battery issues because of the quality of the material used for the battery connector. The Pixel 5s were actually pretty good in terms of hardware issues. The Pixel 6s were nightmares. Constantly having battery or screen issues. As for the 7s I can't say as I stopped repairing phones a year ago

[–] [email protected] 2 points 1 year ago

This is my first pixel device, and probably the last TBH. Not a good introductory experience.

[–] [email protected] 2 points 1 year ago (2 children)

I will say, my used Pixel 6 (GrapheneOS) has worked beautifully so far, with no hardware defects. If I had to complain, the speakers aren't particularly loud, but I've had no hardware issues with it. I agree with other people, it sounds like it could be a bad motherboard? It would be interesting if you could post a video of the issue

load more comments (2 replies)
[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (3 children)

This could be a possible issue with your screen but it's most likely an issue with the Finger Print Sensor (FPS) Software. With Pixel 6 and up the FPS software works in conjunction with the LCD (Since it's on the screen). You should take it to an authorized Google repair center (for example a uBreakifix) and the issue will likely still be covered under the manufacturer's warranty(free of charge). There's a specific program that Google gives these repair centers to reinstall the FPS software on it each time they do an LCD swap. I'm sure that they would be willing to reinstall the software on your Pixel without going through the process of switching the LCD to see if it fixes your issue. Shouldn't take more than 20 mins but it could be longer if they're backed up on same-day repairs. Source: I had to do this a many times for the Pixel 6. And I vaguely remember a customer with a similar issue on the 6 pro.

P.S. Before doing this you could try a factory reset on your phone to see if it fixes the issue. Or start Android in safe mode to rule out any 3rd party software that could be causing the issue. (Though I doubt it, I have a feeling the issue will persist).

[–] [email protected] 9 points 1 year ago (1 children)

No need to go to a repair shop, Google offers this publicly https://pixelrepair.withgoogle.com/

It does factory reset the phone so make sure your data is backed up

[–] [email protected] 2 points 1 year ago

Cool, I'll give this a shot when I have some time. Hopefully it's just a software issue, I'll be a bit annoyed if i have to have ANOTHER screen replaced on a 4 month old phone lmao. Thanks for the info!

[–] [email protected] 2 points 1 year ago

I just edited OP with a video.

load more comments (1 replies)
[–] [email protected] 5 points 1 year ago (2 children)

I am not an expert, but that kinda sounds similar to my old phone when the screen connector broke. It went greenish white and really bright. I dropped mine though.

[–] [email protected] 2 points 1 year ago (1 children)

My fucking mobile does this now when it gets hot! If I play a game or put it on charge the screen will ping up but green-tinted and sometimes with part of it missing. As long as the temp is low it works A-OK.

Though, I threw my phone from the third floor of a hospital after a suicide attempt to stop the brain scanning tech inside from frying my brain and allowing UK armed-response police from tracking me.

The nurses rescued it from a puddle in a tarpauline covering the ground within 30mins.

3 days later I realised the brain scanning was a delusion and I was just "insane in the membrain" after the OD.

[–] [email protected] 3 points 1 year ago

I hope you get the help you need. Im glad that the phone was recovered. I threw mine down some hospital stairs too going to grab something from another floor. I also bent one in a car door. It had a 30° bend but worked fine.

load more comments (1 replies)
[–] [email protected] 5 points 1 year ago (1 children)

On Lemmy, You can embed a video like this:

![](https://i.imgur.com/2AIXZ3w.mp4)

Which looks like:

[–] [email protected] 3 points 1 year ago

Thank you! My lemmy-fu isn't that strong lol.

[–] [email protected] 3 points 1 year ago (1 children)

Had exact same issue on my Vivo X70 Pro+. And the cause was something I doubt will be there on a Pixel. My device has an option to always show fingerprint icon, or show only when screen is lit up.

Always showing the icon flashbanged me with light as well. You might try this if that option exists for you.

If it doesn't, then turn off AOD.

[–] [email protected] 2 points 1 year ago (1 children)

I don't believe the fingerprint option exists on the pixel, or equally likely, I'm blind, especially now. I'll check AOD though!

load more comments (1 replies)
load more comments
view more: next ›