Related
i purchased g1 from ebay, right from day1 the screen does not respond properly in fact most of the times. i need to reset soft one to at least g1 working. i upgraded to jesusfrake adp1.1 but issue is same. looks like a s/w bug or problem as if it were a h/w problem it would not have worked at all. if iam lucky it works like a charm but stops responding once i get some sms/email alert or install any app from market. can someone help here!!
Have you already tried reflashing the firmware? If not, do that. Otherwise, why don't you contact the person you bought the phone from. It sounds like it may be a hardware problem which might be why that person was selling it.
i did flash everything from bootloader to firmware to rooting. but problem remains same...it works for 5 minutes and again screen stops responding but trackball is active....right now iam on latest JF formware..
is anyone facing a simillar problem??? any work arounds....
Sometimes my home screen goes completely blank on me and seems nonresponsive for about 30 seconds. Can be pretty annoying. It seems to happen when I'm switching from an app to the home screen.
Contact HTC directly and ask for an exchange or something. All G1's have been out for less than a year and so they should be covered by warranty.
I put a new screen protector on my G1. I noticed that it had a bad reaction with the touch and I took it off. After I took it off, my touch screen got much worse. It was very jumpy and unuseable. There was a practically invisible film on the screen (couldn't even really feel it. I took a little bit of soap on a lint free cloth and wiped the screen down and let it sit for just a minute (to soak any residue) and wiped away. My screen worked perfect after that.
I was ready to call in for a replacement.
could it be a bug as if it were a hardware problem it would prevent touch screen responding at all!!!
i downgraded to rc 30 and rooted the phone, now its working like a charm!! strange though.......
Edit: SOLVED
Problem: Water or some liquid mixture with water and other conductive chemicals can leak through the outer edges of the glass screen, causing electrical shorts on any of the navigation buttons. Thus avoid applying direct pressure with damp cloth along the perimeter of the screen.
Solution: Place the phone in a ventilated area as long as needed. In a severe case, this could take a very long time (a blow drier may expedite the process), so you may want to seek instructions on how to dismantle some of the phone components to allow drying, or disable the search key temporarily, or send the phone in for repair(last resort).
---------------Original Post-----------------------
As I type, my Samsung Captivate appears to be possessed with an obsession with clicking the search button all by itself, at random times. I've searched around the forums and have yet to find a solution that works for me.
I'm running Cognition 2.4
The phone is about 1 week old, with the problem starting at about 5 days.
I replaced the phone initially because it would shut down randomly. Now this one seems to have yet another malfunction
EDIT: Also note that the problem began shortly after cleaning my screen with a slight amount of monitor cleaning fluid and microfiber cloth. Whether this is coincedental or not, I don't know.
Does anyone know what might be causing this, or know how I would go about disabling the search button altogether?
i had the same problem, its kinda just went away for me haha
Hmm, I also hope it goes away as mysteriously has it appeared if a solution is not found.
I'm trying to make changes to "system/usr/keylayout/melfas-touchkey.kl" with "droid explorer", but every time I change the file, delete it, or replace it, the file always seems to revert back. Once I figure out how to do this, the problem should be temporarily fixed.
EDIT: My current theory for what causes this is that it occurs due to an electrical short after the screen has been exposed to liquid of some kind. If you look closely, there are thin cracks around the glass of the screen. Whether these cracks are water-permeable or not, I don't know. But due to the nature of this problem coming about randomly, and disappearing randomly for various owners, it would explain the effect of drying. I read someone say that he had this problem on two different phones, so maybe he cleaned both of them in such a way that affected the navigation buttons?
If anyone else can contribute to this theory, please do!
EDIT 2: The frequency of search button activation has increased significantly since the first symptoms appeared. I highly doubt this is software related. There is a apparently an issue with the circuit for that specific button. Considering that my cleaning of the screen was the only possible event that could have impacted the circuit, I am now leaning towards that prospect. There doesn't seem to be an easy way to completely dismantle the Captivate and let it dry.
EDIT 3: I'll focus a fan on the phone over night, then focus a blow dryer on it in the morning.
Had the same problem, it was like that since the first day I got it 07/18. It got worse for a period and now it mysteriously doesn't seem to have the problem anymore. No clue what it is from.
SOLVED
Problem: Water or some liquid mixture with water and other conductive chemicals can leak through the outer edges of the glass screen, causing electrical shorts on any of the navigation buttons. Thus avoid applying direct pressure with damp cloth along the perimeter of the screen.
Solution: Place the phone in a ventilated area as long as needed. In a severe case, this could take a very long time (a blow drier may expedite the process), so you may want to seek instructions on how to dismantle some of the phone components to allow drying, or disable the search key temporarily, or send the phone in for repair(last resort).
you might also try putting it in a ziplock bag with rice in it. (the rice will absorb the water)
Has the proposed solution worked for anyone?
Hi,
I am wondering if the proposed solution worked for anyone? What do you exactly do? Leave the phone in the sun for it to dry out. With combination of blow dryer?
With the battery out? I've had this phone since August and I initally thought it was a software issue. After couple of hard resets, roots and upgrade to 2.2 the problem still persists.
Any suggestions? Should I try all combinations? Rice Ziplock bag?
Just as a note. Used to have a lot of random search loads. Along with the moisture thing...a lot of us right handers contact the corner and it does need a direct tap of button to trigger as touch screen. If you notice the settings button never randomly pop up. Additionally, from wrar and use the plastic can gain some flexibility. Must my two cents to help avoid letting ATT screw up their phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
meadhros said:
Just as a note. Used to have a lot of random search loads. Along with the moisture thing...a lot of us right handers contact the corner and it does need a direct tap of button to trigger as touch screen. If you notice the settings button never randomly pop up. Additionally, from wrar and use the plastic can gain some flexibility. Must my two cents to help avoid letting ATT screw up their phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
And in no case...let best but put a screen protector on for you....that will take days to dry...
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I've had that issue in the past, on stock Eclair, and it was an easy fix for me. All I did was flash a custom ROM. I can't say that I tried it on stock 2.2, but an Odin didn't help, so I went custom and it disappeared.
WOW! Thought i was alone.. I also have the phantom button activation problem... but it's not the search button, it's the home button and back button. I know for a fact my phone has not been exposed to moisture. I noticed it after i flashed an OC'd kernel. I tried every OC/UV setting in the voltage control APP thinking it had something to do with the increased MHZ, but the problem didn't go away. I have since flashed a variety of custom roms and regular non OC'd kernels, but the problem still is present. I saw someone post a little while back about the same issue and that they sent their phone in and at&t replaced something having to do with "LIB." The submitter didn't have any idea whether the "LIB" was related to software of hardware. I'm considering sending my phone in, but i hate the idea of being without my phone for 2-3 weeks. If anyone stumbles upon a fix, please do share.
brianray14 said:
WOW! Thought i was alone.. I also have the phantom button activation problem... but it's not the search button, it's the home button and back button. I know for a fact my phone has not been exposed to moisture. I noticed it after i flashed an OC'd kernel. I tried every OC/UV setting in the voltage control APP thinking it had something to do with the increased MHZ, but the problem didn't go away. I have since flashed a variety of custom roms and regular non OC'd kernels, but the problem still is present. I saw someone post a little while back about the same issue and that they sent their phone in and at&t replaced something having to do with "LIB." The submitter didn't have any idea whether the "LIB" was related to software of hardware. I'm considering sending my phone in, but i hate the idea of being without my phone for 2-3 weeks. If anyone stumbles upon a fix, please do share.
Click to expand...
Click to collapse
Try a gingerbread rom.I've had the same problem,back and home key.No matter which froyo rom I run,it would act up randomly at times.I dont spend enough time on eclair to be sure that it does it,but I've been running GR-9 for two days,has not happened once.Coincidence?Maybe....Now running GR-11 for the second day,so far so good.
Sent from my GT-I9000 using XDA App
I agree with the op that the cause is water/moisture in the phone. I have had it on all android versions I have used. And the fact that that it comes and goes is strong evidence in my opinion
Sent from my SAMSUNG-SGH-I897 using XDA App
It might be moisture in some cases, but....
Post getting old, but new to me! My random search problem is definitely not moisture related(unless high humidity outside is considered a problem for a cappy). My phone stays dry, I even clean it with a lint-less cloth, so water isn't the issue(its in a otterbox). I read some post on other sites that show the only fix is either allowing samsung to work on it, or get a refurb from att. I think this problem is also related to all those wrong contact sent messages to, which has happened to me several times with some embarresing happenings . I updated to gb 2.3.5 and problem still exist, plus I use handcent for messaging, and I havn't sent a mis-message yet.
There's another thread on this (search 'crazy back button' and my tests on many roms indicates that it has to with the blk app that mods the buttons. Many roms come packed with versions of it.
No longer sent from my BlackBerry.
Add me to the list with this problem. At first I thought it was an old screen protector. I changed that out last light but I cleaned the screen first by spraying it with LCD cleaner I guess I'll have to wait for it to dry a bit more. I've also been playing with recent Glitch kernels with BLN issues so I can't figure it out!
Well I got the BLN issues sorted. Still can't figure out the search button. There's got to be some way to disable it completely
I get this problem at random times when using Google Maps / Navigate, while the phone is in the car dock. At random times, the search will just pop up. No idea why
While using the phone in the rain one day, the touchscreen pretty much became inoperable once there were multiple droplets on the screen. Luckily I did not have any seepage under the glass, though.
I also concur with meadhros- I've found that when gripping the phone in my right hand, the edge of the pad of my palm at the base of my thumb sometimes sets off the search, since it wraps around the edge of the glass slightly.
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
I want to say that I noticed something similar the other day, but it was short-lived, and I'm not 100% sure. It wasn't long enough or bad enough to make me think the phone is defective, but I'm a bit used to funky capacitive button responses from my N1 days.
I can't reproduce the issue right now, though. How much usage are you talking about needing to duplicate?
Does your phone get hot, or feel hotter than normal when this happens?
I'd see if there's some particular pattern or software that seems to trigger it if you're interested in trouble-shooting.
The problem goes away when I don't touch the phone for a while (it seems that 1 hour is enough to reset the problem).
It seems "recharging".
Then with normal usage, nothing in particular, just even browsing in the settings/maps/market/browser etc., in few minutes the problem appears. The button definitely loses his "power".
It's very annoying, and my friends confirmed the same behavior.
EDIT:
Forgot to sat that the phone is not getting hotter, everything else is really normal.
Cheers
Mine definitely can be used for much more than a few minutes without the problem you're describing appearing.
I'd take it back. Factory reset the phone to protect your private data before taking it back. After the factory reset, you might want to test the behavior again, if it went away, the phone's not defective, you just had some software glitch.
Reminder, factory reset erases everything on the phone, so if you do it as troubleshooting step, be prepared to have to set the phone up from scratch again...I'm sure you knew this, but just covering my butt in case you didn't. It's a good trouble shooting step no matter what if you don't mind the hassle of re-setting things up.
I have a similar experience with the back button. Not sure what to think yet.
Sent from my Nexus S using XDA App
I had a similar problem when I had the Vibrant. Just exchanged it and luckily I got a better one without any problems. I did find out though if you are using the screen protector that came with the phone, it can cause this type of problem.
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
michele72 said:
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
Click to expand...
Click to collapse
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
distortedloop said:
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
Click to expand...
Click to collapse
Thank you, giving it a try.
Anyway, today I factory-reset my telephone and the problem of the back button is still there. I am returning the device.
Back button non responsive
Hi,
I just got my new nexus S (about an hour ago) that I was really excited about and am faced with a problem with the back button too.
Its got factory settings, so it cannot be a downloaded software issue. Also, I have not yet charged the battery at all, its still running on the same battery power that it shipped with.
The other buttons at the bottom of the phone (home, menu and search) all respond fine, its only the back button that does not seem to work. After going through this thread, I tried long-pressing the button, hard-pressing it, pressing just above it, below it, etc. It just wont respond. I had removed the screen protector it shipped with, so that cannot be the issue either.
If this is a known hardware problem (i.e. others have faced it too), irrespective of whether it is acknowledged by Samsung / Google, I'll return the handset. I do not want to spend a fortune and be landed with a handset that does not work - forget working as desired, but it does not seem to be working as designed !
Thanks & Regards,
Rohan
Yep. Definitely a problem here with the back button. There's also two other threads here about it.
I'm having similar problems. I have to touch the button just right for it to work properly
Sent from my Nexus S using XDA App
I was experiencing the same thing with my Nexus S, wasn't sure if it was the case I was using! Took of case and still had problem. I eventually returned mine cause it seemed like it was getting worse! I have a new one worth no problems, definitely a hardware problem! Return it!
Sent from my Nexus S using XDA App
michele72 said:
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
Click to expand...
Click to collapse
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
same issue was with Nexus 1. less responsive buttons. thats why there is a bigger gap between the buttons and the screen for galaxy S phones. i dont know why they did such a thing again with the nexus S. its like samsung didnt learn from anything from HTCs mistake.
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
I think this is true ...
I have an HTC Desire with AMOLED screen.
When I play a finger intensive game, like "SkyForce Reloaded", after some times, the touch is not registered.
Then I must stop for a while, or change finger
Try that, you will know what I meant.
But, I don't have issue with the back button on HTC Desire because it is a hardware button. I am just trying to explain about loosing touch registration because finger interaction on (s)amoled screen.
PS: SkyForce Reloaded is an old school shot'em up game where you control a little space ship with your finger, shooting enemies.
ll_l_x_l_ll said:
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
Click to expand...
Click to collapse
The Desire's digitizer is the same Clearpad 2000 which is used in the Nexus One (and quite a few others), the problem there is that it's pants.
Rusty! said:
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
Click to expand...
Click to collapse
lol, isnt called like that because it registers the heat from your fingers. thats why if you try to use a pen, it wont register . and thus. the screen is NOT resistive type "where it will recognize anything since its being pushed by force ? "
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Rusty! said:
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Click to expand...
Click to collapse
from your link
"A capacitive touchscreen panel is one which consists of an insulator such as glass, coated with a transparent conductor such as indium tin oxide (ITO).[7][8] As the human body is also a conductor, touching the surface of the screen results in a distortion of the screen's electrostatic field, measurable as a change in capacitance. Different technologies may be used to determine the location of the touch. The location is then sent to the controller for processing.
sooo, yeah. my wife has the t959v. the screen cracked months ago, replaced it with one from ebay, works fine. a few weeks ago, it was involved in an accident and needed yet another screen replacement; ergo, back to ebay i go. installed the new screen yesterday, turn it on, all is well. for a bit.
now, the phone isn't currently, nor has it ever been rooted; pure stock tmo us 2.3.6. during boot, the splash screens and boot animation are gorgeous and perfect in appearance. the recovery menu is exactly as expected. android boots as you'd want it to, and then the display will do one of the following:
-work properly (rare)
-automatically turn off, capacitive buttons still lit, touchscreen unresponsive - turning it "off" darkens the cap buttons, turning it back on flashes the screen on for a half-second, then off, with cap buttons still lit (common)
-graphical corruption ("solarized" colors, completely wrong colors, pixel vomit in essence) (fairly common)
-screen tinting, blue most often, followed by pale yellow, then greenish, then red (almost constant)
-screen inversion - the display will show as rotated 180 degrees; grabbing a framecap in ddms shows it right way up. touches are also inverse; you have to touch where the onscreen element would be if it were displayed properly instead of where the element is; e.g. a button on lower-left will display in the upper right, upsidedown, but the screen registers the button when you touch the lower-left portion of the screen. (quasi common, equally infuriating and hilarious)
none of these problems will show up in a screenshot at all.
i can reliably reproduce any of the above by simply adjusting the screen brightness. this will, quite literally, cycle through every possible defective display mode randomly for a split-second before moving on to a different one as long as you move the brightness slider.
MOST of these issues are transient and are either fixed (temporarily) or replaced with a different listed issue if you lock/unlock the display. it feels like a hardware issue what with the solarizing and color horrors, but is acting like a software issue, considering that recovery and boot are perfect and have never displayed any of these issues. i tried gently flexing and stressing the case in areas that might be a weak connection point, but can't get it to bug out that way.
in no way am i suggesting that i didn't screw something royally in the reconstruction stage, but i tore down and rebuilt that phone 4 times with identical results, so i can guarantee it's not some loose ribbon connector or zif socket.
i beg of you, great minds of xda, what the balls did i muck up this time? any hope for a fix? are there different panels, drivers, something?
thanks in advance
OK, if your screenshots appear normal, then your phone appears to be working correctly!
or at least it thinks it is we can conclude that it isn't the rom, kernel, or anything that you can blame the phone for going screwy.
Try buying another screen??
The ribbon connector might be broken?
yeah, these were what i figured what my options were. it just seems odd that the boot process and recovery menus have error-free displays while only the full android os doesnt. oh well, i'll probably just have to make a stink about it on ebay or something.
thanks for reading
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
lumin30 said:
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
Click to expand...
Click to collapse
hell, warranty's void at this point anyway, right? may as well thanks much!
welp, all went well, screen was perfect through the whole heimdall/recovery process, but the problems still exist in the os c'est la vie. at least my wife's phone is finally rooted, i suppose. thanks anyway!
Have you tried opening it back up and reconnecting?
yup, 4 times, but i guess one more wont hurt
[edit]
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
zero01101 said:
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
Click to expand...
Click to collapse
That's interesting and could very well be a hardware problem with the screen. You wouldn't see that in recovery as the OS isn't loaded to mess with the brightness in that mode.
Does it do it on-demand if you mess with the brightness slider?
stephen_w said:
Does it do it on-demand if you mess with the brightness slider?
Click to expand...
Click to collapse
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
zero01101 said:
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
Click to expand...
Click to collapse
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
stephen_w said:
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
Click to expand...
Click to collapse
as fun as that sounds, unfortunately i bet i'll end up just getting my wife a used phone on ebay or somewhere similar and using this one as a development monkey. i was assuming that it wasn't something i could fix but hoping otherwise... yeah, that worked out
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
kristoper said:
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
Click to expand...
Click to collapse
nawp, nothing even close to a solution here i did end up buying my wife a whole new replacement phone and turned the broken one into my api10 development device. for what it's worth, yeah, autobrightness off does help a bit for when the phone is actively displaying content, but after you put it to sleep/screen off and try to turn it back on, it's a crapshoot. for a few horrifying hours, the screen was upsidedown even in recovery/boot animation and would NOT flip back to right-side-up until i ran the battery completely flat.
is no fun, 'tis truth. sorry for your troubles.
A bit of a strange issue. The fingerprint sensor has been working 100% without issue since getting the phone.
I let the kids use my phone for an hour to watch cartoons. After that it started not recognising my finger. I cleaned the glass, removed the case, re created the fingerprint profiles. I made a mistake and tried an OTA update, which then had to fully reset the phone, but that's another issue.
I am using a tempered glass protector. I took it off for 1 day to see if that made a difference and not really. Even being extremely careful after 1 day there were tiny scratches on the screen.
Wondering if anyone else has had an issue like this. I did reload it with the latest Miui 12 stable, but made no difference. Not sure if the kids were pressing it constantly, but no signs of damage.
It will vibrate and attempt to recognise my finger, but just fails. Then the next time it may work, but intermittent and really annoying.
I have found that it seems to work better when out of a case for some reason. Maybe the sides of the case resting on the glass.
Overall I think this is a great phone. Shame about no development happening. As I use it debloated with MicroG it means I can't do ota updates.
I'm considering getting a Galaxy, Oneplus or Pixel phone. Until the possibility of more development happens if ever
We've had ours for about 3-4 days now and I have found the FPS to be crap out-of-the-box. Exactly the same issues as you, and with just the default screen protector on it. Sometimes it works fine at first attempt, at other times I have no choice but to enter the PIN to unlock.
I made the mistake of letting my kids use the phone again a few days ago. After that the fingerprint sensor would sometimes not be detected. The phone randomly won't switch on and have to hold down power for about a minute then it turns on. Very annoying, but doesn't happen all the time. Did it almost all weekend, then today it's working almost fine.
Did test in TWRP and didn't have the same issue. So making me think it's either software or fingerprint sensor related, causing the issue.
Still think the phone is great and there's not really another phone on the market I'd prefer at the moment, just need some custom rom support. A work friend has a Note 8 and his will be 50% battery while this is still about 85% or so
Same
birleytweet said:
A bit of a strange issue. The fingerprint sensor has been working 100% without issue since getting the phone.
I let the kids use my phone for an hour to watch cartoons. After that it started not recognising my finger. I cleaned the glass, removed the case, re created the fingerprint profiles. I made a mistake and tried an OTA update, which then had to fully reset the phone, but that's another issue.
I am using a tempered glass protector. I took it off for 1 day to see if that made a difference and not really. Even being extremely careful after 1 day there were tiny scratches on the screen.
Wondering if anyone else has had an issue like this. I did reload it with the latest Miui 12 stable, but made no difference. Not sure if the kids were pressing it constantly, but no signs of damage.
It will vibrate and attempt to recognise my finger, but just fails. Then the next time it may work, but intermittent and really annoying.
I have found that it seems to work better when out of a case for some reason. Maybe the sides of the case resting on the glass.
Overall I think this is a great phone. Shame about no development happening. As I use it debloated with MicroG it means I can't do ota updates.
I'm considering getting a Galaxy, Oneplus or Pixel phone. Until the possibility of more development happens if ever
Click to expand...
Click to collapse
I have the same issue since I got the phone, the fingerprint sensor is ****, I opted to unlock it via bluetooth by recognizing my smartwatch.
Hydrate or moisturize your fingers/thumbs
Much faster accuracy unlock speed
Try to Change the Glass Protector
Your using alcohol based hand sanitizer, these remove moisture from the hands making them dry. Just put some lotion you'll have much better response.
What game were your children playing on phone?
Have you looked at their fingers?
I don't like on screen fingerprint sensors. Maybe too much pressure leads to an issue.
---------- Post added at 12:29 ---------- Previous post was at 12:22 ----------
Potterified said:
We've had ours for about 3-4 days now and I have found the FPS to be crap out-of-the-box. Exactly the same issues as you, and with just the default screen protector on it. Sometimes it works fine at first attempt, at other times I have no choice but to enter the PIN to unlock.
Click to expand...
Click to collapse
Peel off the screen protector, it is bull***t.
Also, I remember to have activated the "show touches" option on developer settings. It was almost unable to recognise fingerprint. Deactivated again.
Hardware fingerprint sensor is always better. :crying: