I don't know the official name for the stylized image of a fingerprint that you touch to unlock the phone with your finger. But sometimes it displays in the wrong place when trying to unlock an app, for instance google pay or bitwarden password manager. It displays a little bit lower than the sensor location, so that if I put my finger on the image, it doesn't work. If I put my finger a bit above the image, it works. It always displays in the correct place for unlocking the phone. Here are some pics showing the problem. I put a stickie on the screen lined up to the bottom of the sensor. The first one is to unlock the phone. The second is when unlocking google pay and the third shows when I put a finger above the image. You can see how the bright white circle that lights up when you touch the sensor is in the correct place. I wonder if this is the same on the Pixel 6 and is one of the reasons that these phones have a reputation for unreliable fingerprint recognition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had this on day one after messing with the "Display cutout" settings in "Developer Options". I was unable to fix the issue but didn't spend too much time on it as I was just getting ready to unlock the bootloader which requires a wipe anyway. The wipe ultimately fixed the issue for me, and I haven't touched those settings since.
Perhaps try messing with the "Display cutout" settings, maybe it'll resolve the issue after some combination of changes.
benji said:
I had this on day one after messing with the "Display cutout" settings in "Developer Options". I was unable to fix the issue but didn't spend too much time on it as I was just getting ready to unlock the bootloader which requires a wipe anyway. The wipe ultimately fixed the issue for me, and I haven't touched those settings since.
Perhaps try messing with the "Display cutout" settings, maybe it'll resolve the issue after some combination of changes.
Click to expand...
Click to collapse
I've never gone into developer options, so that can't be the cause for me. I'm running a completely stock phone. When I was first trying to figure out what was happening, I was having the problem and I reboooted and that seemed to fix the problem for a day or two and then it came back. Then I rebooted a few times, but the problem was not fixed those times.
Fwiw...I noticed the damn 'fingerprint' sorta hops 'round in a circular pattern during fingerprint enrollment...thought I was seein' things!
Any way to fix it, in all the app it appears wrong
Related
I have a treo 750. Its used and I don't know what the guy before me tried to do with it, but it looks like all he did was install the official WM5 to WM6 update. My problem now (and part of the reason he sold it) is that there seems to be some serious screen corruption. I'm inclined to think there may be a driver issue? I cant even see the bootscreen. All I can see are a couple of vertical and horizontal bars (mostly around the top) with a multicolor spectrum. The rest of the screen is blank. Hard-reset, soft-reset, neither works to fix it. Oddly, if I access the device through MyMobiler and regedit/change to font to something that it hasn't used before (ex. calibri, arial) it seems to bring it back to life... still no boot screen, but the os will work fine. If I put it in standby mode and then try and bring it back on, I'm back to the corrupt screen. At the moment I've turned off the power-idle feature and just let it go to backlight off while leaving the device on all the time, but I cant leave it like that forever. Any thoughts? Am I able to update the display driver or something?
PS. Display works on my PC through MyMobiler with no problem.
Thanks in advance.
having exact same problem
I am having the exact same problem. The only way to avoid the display corruption seems, like you said, to avoid putting the phone in standby mode... but then leaving it like that all day will drain the battery very fast, obviously.
I'm curious as to what the cause is. My phone is out of warranty already. Purchased summer 2007.
rjackets, have you done anything since your post?
Hey i Still have the same problem, did anyone find an answer yet?
Is this what you're seeing? http://commons.wikimedia.org/wiki/File:Bootloader.jpg
no, it's like all the 1st vertical pixels get extended to the right end and the lines keep flashing, i kind find my battery atm but it looks something like this texture, just with pixels:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
//EDIT: i've posted a video on youtube that shows the error:
http://www.youtube.com/watch?v=BWMVaoMW9Us
and two 5MP Pictures:
http://img843.imageshack.us/gal.php?g=foto108.jpg
( direct links:
http://img843.imageshack.us/i/foto108.jpg/
http://img820.imageshack.us/i/foto109c.jpg/
)
Have encountered this twice with my replacement One S (first one had a weird refresh issue that I haven't encountered yet with the replacement). This is all using the stock Sense launcher with pattern locked enabled.
Basically coming out of a screen off situation I unlock via the ring and then get the pattern screen. However, everything is smaller and shifted far to the right so I can't see all of the dots and therefore can't unlock. Only solution is to restart the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just curious if others have run into this.
Just happened again.
Figured out a workaround to not have to reboot the phone. One of my lock screen shortcuts is the camera. When this happened I went directly to the camera from the lock screen and back to the lock screen and all of the dots appeared this time.
Sent from my HTC One S
Are you rooted, bootloader unlocked, or running a dif recovery? I have been using the gesture unlock since day one and have had no issues like what you describe. Perhaps a factory reset may help?
None of that. Stock out of the box. I'll monitor it and see if I can determine if it is specific steps that lead to it since it doesn't happen that frequently. Hasn't been happened at all today.
Sent from my HTC One S
This happened with me too, on my stock phone. It must be a bug that has to do with the camera unlock feature, I just stick to bare pattern and it works for me.
I have the exact same issue with my stock HTC One S. I don't use face unlock just the pattern.
Thanks for the camera thing work around, I was getting tired of rebooting my phone.
Question, when you open the app drawer and start tapping "Menu" on top right rapidly, does the UI start glitching?
It's happen to me as well, I'm using the face unlock now to avoid reboot. I'll try the camera work around.
I occasionally get that as well but turning the screen off and on again or even going in to the emergency dialer and backing out usually fixes it. I've never had to reboot because of it. I use the camera for security with a trace pin backup.
Sent from my HTC VLE_U using xda app-developers app
Afternoon all.
As per title. After installing Renovate 3.0 today, I noticed that I've "lost" about 5mm at the bottom - just a thin black bar under the display.
Thought the ROM was the culprit, but I've reflashed 5 or 6 Rims and it's the same.
I've tried all display resolutions, immersive mode, different themes, clean installs, soft reboots, too many restarts, toggled everything I can think of- the same. All screens, all apps.
Driving me absoeffinglutely nuts. Any help appreciated!
Have you tried flashing back to the factory firmware?
Take a screenshot, does the black bar appear in the screenshot? If not, the display panel is broken, if yes, it's a software glitch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No, doesn't show in screenie, didn't expect it to. Find it hard to believe it's physical damage - never dropped it, Otterbox Strada wallet, but somehow the display is FUBAR.
Seen one similar problem after googling, on the S8, no obvious cause or solution.
Going to wipe everything including system and all storage, flash a stock in Odin and cross my fingers.
B3311 said:
No, doesn't show in screenie, didn't expect it to. Find it hard to believe it's physical damage - never dropped it, Otterbox Strada wallet, but somehow the display is FUBAR.
Seen one similar problem after googling, on the S8, no obvious cause or solution.
Going to wipe everything including system and all storage, flash a stock in Odin and cross my fingers.
Click to expand...
Click to collapse
Very odd, if it appeared right after you installed the ROM, a software problem is possible. But I still wonder how it's possible for a part of the screen to render on a screenshot, but not on the actual screen.
Hey all,
My Pixel 3 standard started freaking out today. I have initiated an exchange, yet thought perhaps someone may have had/fixed similar issues. I was in the middle of playing a game and my screen kept shutting off. I closed the application and found that SystemUI was crashing at random intervals, which is what was causing the screen to blank. The phone was also very slow at this time and wouldn't respond to several inputs. I also had a few instances where the phone opened random apps on its own. I tried going into safe mode and I don't seem to experience the issue. I am presently unrooted and on the latest November OTA. I've also tried removing any apps that updated today as that's when the issues started.
I've started the exchange process, yet it's five days out for a replacement and it's going to be painful to be without a fully functional phone for that amount of time.
Any ideas of what to try? I thought perhaps crash logs, yet I'm not sure which to parse...
Thanks!
I too started seeing System UI isn't responding message. Tapping to wake the phone or pressing hardware buttons had a delay in both normal mode and safe mode. I tried reapplying an OTA image from December and same result. So I tried Factory image vs OTA image, same result. Turned off always on display to see if that improved. Same result. Removed any case and screen protector to see if that was contributing, but same result.
I'm having a harder time getting google to initiate the exchange as I bought my device off swappa and can't access the original owner's email or order id. Never thought that was needed - until now. Buyer beware. I bought pixel 1 and 2 straight from google, but went secondhand with the pixel 3. My mistake.
blueline-pq1a.181205.006-factory-af1829a6.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you factory restored?
I have tried to factory reset my phone and I'm still having this problem.
It happens at random when getting an incoming call, I can't see the caller screen, the UI is frozen, can't silence it pressing the buttons, can't wake up the screen until the phone decides to let me use it.
It's so annoying.
I am stuck with this issue during this lockdown, can somebody help? Or tell me what worked for them?
So I moved from a Note4 to this Find X2. In my previous phone, I had a setting to display a custom message in the lock screen "If you find this phone please call...". When yesterday I set my new FindX2 I was prompted to move my previous android configuration to the new one. So I did.
Now, I want to remove this message as I noticed it is wrong, it says to call to my own number, which, if phone is found, they would be ringing the phone itself... So anyway, I dont need the message there. You guessed it, there is no option (as far as I searched) to removed this setting. If any of you can lend me a hand on this... I wouldn't like to restart the whole setting and configuration from scratch again.. Please let me know if you know how to delete this message. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah that option doesn't exist. I miss it. You may need to do a factory reset to get rid of it..
Sage said:
Yeah that option doesn't exist. I miss it. You may need to do a factory reset to get rid of it..
Click to expand...
Click to collapse
What...? Seriously this is an issue they should solve. It makes no sense to import a setting that can't be set anymore.
demalmar said:
So I moved from a Note4 to this Find X2. In my previous phone, I had a setting to display a custom message in the lock screen "If you find this phone please call...". When yesterday I set my new FindX2 I was prompted to move my previous android configuration to the new one. So I did.
Now, I want to remove this message as I noticed it is wrong, it says to call to my own number, which, if phone is found, they would be ringing the phone itself... So anyway, I dont need the message there. You guessed it, there is no option (as far as I searched) to removed this setting. If any of you can lend me a hand on this... I wouldn't like to restart the whole setting and configuration from scratch again.. Please let me know if you know how to delete this message. Thanks.
Click to expand...
Click to collapse
I have a message on my Find X2 Pro too after moving from a OnePlus 6T.
Hopefully the option will appear on an update. If not, factory reset seems to be the only option.
I did a factory reset and didn't import anything this time, having to manually set some stuff.
Too bad, oppo, they even didn't reply as costumer service.