Related
ive only noticed this a couple times, but its going to start getting annoying if it is a reoccurring thing. I wanted to know if anybody else is having these issues.
Its normally just one tiny, maybe finger sized spot, that does not recognize a touch. I was able to confirm using multitouch visualizer that it worked everywhere except this one spot. After turning my screen off and then back on, it went away.
i have a launch day evo 3d without the ota.
Where is it on your 3D? I notice about 3/4 of an inch from the top left corner of the screen there's a spot that is unresponsive at times...
I got some issue just yesterday. Mine is where the letters e and r when u pull out the keyboard. Reboot cleared it up. Very weird...
Sent from my PG86100 using XDA App
I had it to today, keyboard area. My guess is its somethingti do with temp root and kernel. Reboot fixed it...
Sent from my PG86100 using XDA App
i just returned my old 3Evo because the notification bar area would stop recognizing touch randomly and it became annoying i battery pulled and factory reset the device and it still did it, the new device so far so good
Mine too. Couple times now... Different areas different times. Screen off then on fixed it.
Sent from my HTC Evo 3D.
So has everybody here tried temp root? I have, not sure if it was temp rooted when I was having issues though.
By the way, the two times it happened so far one was top middle, the other was bottom middle on my keyboard.
I was not and have not used temp root.
Sent from my HTC Evo 3D.
So is everybody having these issues? I'm pre ota and it seems even more prevalent now.
I'm starting to wonder it it's hardware or software, if it's software I can deal with it until it's fixed but if it's hardware then I need to get a replacement. It's good to know I'm not the only one though.
I wonder if updating to the newest firmware would help. The reason i never did it was for rooting issues but it doesn't seem the update closed any exploits
it has only happened to me twice in 3 weeks I have had the phone, and second time was today. It was aroud e and r on the keyboard it kept on recognizing the shift key everytime I would hti a key in that area.
I locked it and unlocked it and it worked fine again. It seems like a software glitch to me.
nkd said:
it has only happened to me twice in 3 weeks I have had the phone, and second time was today. It was aroud e and r on the keyboard it kept on recognizing the shift key everytime I would hti a key in that area.
I locked it and unlocked it and it worked fine again. It seems like a software glitch to me.
Click to expand...
Click to collapse
what firmware are you on? im trying to figure out if maybe the update fixed it.
Do any of you guys with this issue have screen filter installed? It was messing with my phone some like that, when I had it.
You may want to try it without Screen Filter and see if it persists.
hockey4life0099 said:
what firmware are you on? im trying to figure out if maybe the update fixed it.
Click to expand...
Click to collapse
I have the latest OTA installed.
Rickster747 said:
Do any of you guys with this issue have screen filter installed? It was messing with my phone some like that, when I had it.
You may want to try it without Screen Filter and see if it persists.
Click to expand...
Click to collapse
What's screen filter?
hockey4life0099 said:
What's screen filter?
Click to expand...
Click to collapse
An app to disable the bright ass led's on the bottom buttons
Sent from my 3rd Dimension of Evolution
i have the same issue with my 3d... i either lose the top part or around the n key on the keyboard
It happens to me sometimes at the top left corner of the screen. No modifications done to phone.
Sent from my PG86100 using XDA Premium App
Happens to me alot. Usually on my space bar. I would have to press it on the left corner for it to work, if I press it in the center its unresponsive. I also noticed this when in Google sometimes it doesn't allow me to search by clicking the magnify class. I have to press enter to search.
Only clears up when I reboot
Space bar for me too. Screen filter not installed, screen lock then unlock fixes it.
Hi all,
I am trying to figure out why my scanner is not operating. It was operating and suddenly stopped, wondering if it has to do with custom roms etc... I have tried to restore backups, factory reset phone, and tried recalibrating my prints. The scanner registers swipes when I have not touched it, and says swipe too short while trying to setup scanner password lockpad. so I want to know the software path in order to eliminate the possibly that its a software malfunction. I have read a few articles about the hardware being the issue but want to be sure its not something I may have mixed up.
Thanks in advance for any useful and/or helpful posts.
Sent from my MB860 using XDA App
Anyone?? Anything? Also after I reboot I swipe about 10-20 times before it registers one swipe, saying swipe too short.
Sent from my MB860 using XDA App
Or better yet will Motorola repair it if the bootloader is unlocked.
Sent from my MB860 using XDA App
been here before. I am not sure if the root cause is the scanner has gone buggy on you (hardware not software related) but what I ended up doing to fix it was getting a new fingerprint scanner and swapping them out ($20+20 min to do the swap - might take you a bit longer)
I originally it was from the power button being misaligned (if I opened it up and adjusted, it would work for a period of time).
the x factor here was that it could have just been misaligned with the cover as i bought a new one but did not end up actually using it.) so that could be a possible fix as well.
the alternative? send it in to moto and wait for them to repair. Should be covered under warranty but who knows, haven't heard stories about people sending in their devices with a hardware problem with an unlocked bootloader to moto.
Will my warranty cover it, I know it's been void by unlocking the bootloader, but the scanner doesn't seem to me a piece of hardware that is altered by rooting. I have talked to Motorola ( forgot to mention the bootloader )and they say it is covered by warranty and want me to fill out a ticket etc. And send in for repair
Sent from my MB860 using XDA App
Have you tried pulling the battery for a minute? Not just powering off, but actually pulling out the battery. It's known to fix some issues with FP scanner.
Robert Havens said:
Have you tried pulling the battery for a minute? Not just powering off, but actually pulling out the battery. It's known to fix some issues with FP scanner.
Click to expand...
Click to collapse
Just tried that. Booted back up and had 5 ghost swipes ( I didn't touch the scanner, but it said swipe too short and vibrated ). Also tried swiping after and no response. I'm leaning towards hardware malfunction.
Sent from my MB860 using XDA App
I feel something diffrent
I had finger print reader problem so offen ... I have to restart my phone all time...
But I notice that it many time happens after i come back from swimming and even i wash my hands and not dry it proparlly I always have problem with finger print sensor.... While I upgrade to new firmware... and Taking care about my wet fingers... i dont swip if my finger is wet...and I dont remember I ever had issue after that...
Please try wiping the sensor with isopropyl alcohol (rubbing alcohol).
Let it dry completely.
then test again.
Dave__C said:
Please try wiping the sensor with isopropyl alcohol (rubbing alcohol).
Let it dry completely.
then test again.
Click to expand...
Click to collapse
I will try that cause it is kinda oiled up, but that doesn't explain the ghost swipes.
Sent from my MB860 using XDA App
Are you stock our ruining a specific ROM?
Phoneguy589 said:
Are you stock our ruining a specific ROM?
Click to expand...
Click to collapse
I am on alien v4 with theme
Sent from my MB860 using XDA App
i have this exact same problem
I had some issues with Alien as well. I'm not sure if its from some of the debloat removed or what..but I installed Aura ROM with full Blur..and my fingerprint scanner has never worked better. It hasn't missed ONE swipe. On froyo I sometimes had to swipe twice to unlock..but this one is mint. Give it a try and then you at least know if its hardware it software. Just be sure to do a good clean wipe (fastboot) before install.
Rickroller said:
I had some issues with Alien as well. I'm not sure if its from some of the debloat removed or what..but I installed Aura ROM with full Blur..and my fingerprint scanner has never worked better. It hasn't missed ONE swipe. On froyo I sometimes had to swipe twice to unlock..but this one is mint. Give it a try and then you at least know if its hardware it software. Just be sure to do a good clean wipe (fastboot) before install.
Click to expand...
Click to collapse
Installed aura.. problems persisted.
Edit: any new ideas?
My overclocked alien atrix
My problem was not software related, Motorola has repaired my phone, the fps hardware was to blame. Solved.
For about 4 days now my screen has been acting up and giving me quite the annoyance. It initially started while i was on Deck's "gbsense-e3d-deck [1.0]" ROM. I wiped cache and dalvik then re flashed the ROM twice but the screen kept malfunctioning. I was forced to perform a factory reset and re flash a new downloaded file of the same ROM which fixed nothing. I wanted to see if it was a ROM specific issue so i flashed CyanogenMod 7 VALPHA3 and the issue was still present but to a much less annoying degree. Now it seems as if my device doesnt register touch around the midsection. That makes me unable to select anything that may be in that area. I have tried multiple multitouch apps and testers to "diagnose" what is going on with my touch screen, but all i can gather is that my screen might be ****ed. The phone works flawlessly excluding the touch screen's unresponsive zone, so i don't know whether it's a hardware or software issue. Any insight concerning this matter is welcomed, Thanks.
I have attached a video demonstrating my screen while using the app "multitouch paint"
Anybody? 140 views 0 Responses
Could it be a ground issue? Try holding the phone in your hand and see if it still does it. I remember my OG Evo having a similar problem when I laid it on something non conductive.
husker91 said:
Could it be a ground issue? Try holding the phone in your hand and see if it still does it. I remember my OG Evo having a similar problem when I laid it on something non conductive.
Click to expand...
Click to collapse
It occurs both while in hand or on a surface. An example is if i pull down the notification bar, depending what hits the affected zone, i'm unable to select it. I used SBM quite often and now when drawing for example a straight line up it would look like this _____________ __________ (vertically of course) the gap being my speculated affected area but much wider.
MindSplit said:
It occurs both while in hand or on a surface. An example is if i pull down the notification bar, depending what hits the affected zone, i'm unable to select it. I used SBM quite often and now when drawing for example a straight line up it would look like this _____________ __________ (vertically of course) the gap being my speculated affected area but much wider.
Click to expand...
Click to collapse
Is it possible that both of the roms you tested are using the same kernel? I would swap out the kernel with the stock one just in case. At least it'll rule it out lol.
husker91 said:
Is it possible that both of the roms you tested are using the same kernel? I would swap out the kernel with the stock one just in case. At least it'll rule it out lol.
Click to expand...
Click to collapse
I'd take it one step further and return completely to stock, if it STILL does it, then I would guess it's a problem with the digitizer and you would either have to buy a replacement one, or take it to Sprint. If you don't have TEP then HTC's warranty should suffice.
Possibly related?
http://forum.xda-developers.com/showthread.php?t=1267124
It looks similar to this issue, but you are getting it with a single touch instead of with a multitouch. I get EXACTLY the same thing if I use a second tap while drawing a line. Try "multitouch visualizer 2" from the market and see if it registers one tap that is on all the time or if you can actually get the full 4 touches at once. I doubt it will be insighful, but it can't hurt--and if you have an "always on" (perhaps in the button area below the screen) then you know the digitizer is bad.
If it is the same issue, try restarting and give it time. Mine has gone from happening often to happening about 1% of the time. It is software and can be "corrected" by either time or a restart. It is WORST on the first boot after flashing something (even JUST a stock kernel). I have absolutely no idea why.
Good luck. I hate this junk. My Evo 4G never had this sort of glitchy garbage, but, whatever it is, it is likely due to HTC's glitchy kernel!
MindSplit said:
For about 4 days now my screen has been acting up and giving me quite the annoyance. It initially started while i was on Deck's "gbsense-e3d-deck [1.0]" ROM. I wiped cache and dalvik then re flashed the ROM twice but the screen kept malfunctioning. I was forced to perform a factory reset and re flash a new downloaded file of the same ROM which fixed nothing. I wanted to see if it was a ROM specific issue so i flashed CyanogenMod 7 VALPHA3 and the issue was still present but to a much less annoying degree. Now it seems as if my device doesnt register touch around the midsection. That makes me unable to select anything that may be in that area. I have tried multiple multitouch apps and testers to "diagnose" what is going on with my touch screen, but all i can gather is that my screen might be ****ed. The phone works flawlessly excluding the touch screen's unresponsive zone, so i don't know whether it's a hardware or software issue. Any insight concerning this matter is welcomed, Thanks.
I have attached a video demonstrating my screen while using the app "multitouch paint"
Click to expand...
Click to collapse
My friend us having the exact same issue. If you figure anything out, please let us/me know.
Sent by my Supercharged dual core from the 3rd Dimension
I would also like to know whats going on.. I have two evo's 3d and my friend was telling me that he is having issue with the touchscreen he is still on stock... and my was rooted the same day I got it and has no issues.. He mentioned that the same area mentioned in this thread is the are affected in his phone... could this be cause by the screen digitizer??
Ignore this... Thought I found what my issue was... But wasn't the case
I had the same problem but it only seemed to be in one horizontal strip of my screen. Im not sure what caused it maybe its from me dropping it or what. I also did try to flash other roms and kernals but still no fix so i said to myself im going to put it back to stock and take it to sprint. There they looked it for about 2 minutes and deemed it was a hardware issue. The guy asked if i had a warranty. Two days later i received a refurbished phone.
So in all revert it back to stock... search on htcevohacks . com
Take it back to sprint and show them your problem. They should also deem it as a hardware issue and send you a replacement
MindSplit said:
For about 4 days now my screen has been acting up and giving me quite the annoyance. It initially started while i was on Deck's "gbsense-e3d-deck [1.0]" ROM. I wiped cache and dalvik then re flashed the ROM twice but the screen kept malfunctioning. I was forced to perform a factory reset and re flash a new downloaded file of the same ROM which fixed nothing. I wanted to see if it was a ROM specific issue so i flashed CyanogenMod 7 VALPHA3 and the issue was still present but to a much less annoying degree. Now it seems as if my device doesnt register touch around the midsection. That makes me unable to select anything that may be in that area. I have tried multiple multitouch apps and testers to "diagnose" what is going on with my touch screen, but all i can gather is that my screen might be ****ed. The phone works flawlessly excluding the touch screen's unresponsive zone, so i don't know whether it's a hardware or software issue. Any insight concerning this matter is welcomed, Thanks.
I have attached a video demonstrating my screen while using the app "multitouch paint"
Click to expand...
Click to collapse
This thread started off as a mod request because I thought it was my proximity sensor causing the issue. After further investigation I'm completely stumped as, disabling my proximity sensor didn't work (or the disable wasn't effective, not sure). Highly modified original post to make the thread relevant to the direction that its going.
Issue details - screen will not stay on while in call unless enabling speakerphone mode. After call initiates, screen promptly turns off. Pressing power key wakes the screen up but the second a finger is touched ANYWHERE on the screen it turns off again forcing one to wait for the call to disconnect itself or pull the battery to hard reset the device (whichever comes first). The issue seems to be somewhat inconsistent, as some calls I get more responsiveness out of the screen than others. It DOES seem to be software related as this issue is very, very specific. It only happens while a call is active. The screen and standby functions work 100% of the time otherwise.
Facts:
-issue was not present before obtaining s off and upgrading to ICS
-issue is present when doing a clean install of the Rom (energy, though I'm inclined to think its not Rom related for obvious reasons)
-issue persisted even when restoring an old back up of a gingerbread state from days prior to obtaining s off and flashing ics.
I know I'm not the only one experiencing this issue. I've spoken with several others who are having the same problem. Hoping an xda elite on here might be able to figure out what might be causing this to happen. Any help would be greatly appreciated.
----------------------------
(Original post) -
My proximity sensor is on the fritz and making it impossible to multitask anything while on a call (so much to the point where sometimes I can't even hang up and have to pull my battery). It's killing the screen the second I touch the screen anywhere while on a call.
Can someone tell me how to, or would someone even be able to put something together that'd allow me to disable my proximity sensor entirely? I don't really need it anyways since I can just manually hit standby before I hold my phone up to my ear. Any help anyone could provide would be greatly appreciated =)
Sent from my HTC_Amaze_4G using xda premium
Too tricky? No one? I know I'm not the only one encountering issues with their proximity sensor freaking out while on a call.
I guess ill just have to live with the inability to do anything on my phone while on a call unless I activate the speaker. Not the end of the world.
But if anyone can write a script/throw something together that'd turn it off you could save ne a lot of trouble and help others that are having this issue as well. Nbd ::shrugs::
Sent from my HTC_Amaze_4G using xda premium
would a piece of tape work? just tape it over the sensor.
No cuz then itd just stay off. The problem is that the screen won't stay on while in a call. If I touch the screen anywhere while on a call the screen shuts off immediately. =( very annoying. Can't even hang up sometimes.
Sent from my HTC_Amaze_4G using xda premium
Should work even though it's a different device, but haven't tried myself so no guarantees
How to/Solution to disable proximity sensor incall
Just a quick search found that
I tried to find the file in sys/class/optical-sensors/proximity .... But I didn't know which of the other files needed to be edited.
Wait....I sent this with Tapatalk?
Nativedude said:
Should work even though it's a different device, but haven't tried myself so no guarantees
How to/Solution to disable proximity sensor incall
Just a quick search found that
Click to expand...
Click to collapse
Totally worked. My proximity sensor seems to be off but oddly the screen still won't stay on while in call unless I have speakerphone enabled lol.
I figured it HAS to be related to the proximity sensor cuz the screen shuts off the instant my finger touches it... But apparently the problem is related to something else entirely. Thanks though =)
Just a slightly annoying glitch I can live with. Guess I'm gonna have to lol
Sent from my HTC_Amaze_4G using xda premium
AndroidAutobot said:
Totally worked. My proximity sensor seems to be off but oddly the screen still won't stay on while in call unless I have speakerphone enabled lol.
I figured it HAS to be related to the proximity sensor cuz the screen shuts off the instant my finger touches it... But apparently the problem is related to something else entirely. Thanks though =)
Just a slightly annoying glitch I can live with. Guess I'm gonna have to lol
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Totally reflash your rom, leak, whatever.. that bug sounds like something didn't take fully on initial setup. Can't hurt to try. I say this because it sounds VERY similar to the problem I had with my Vibrant.. and many of the issues I keep reading people having make me think that the install methods aren't perfect and fool proof.
If you're on the leak you'd have to make a nandroid, but if on a rom that doesn't wipe data partition you can just wipe the system and reinstall- or worse case restore a nandroid of data partition.
Silentbtdeadly said:
Totally reflash your rom, leak, whatever.. that bug sounds like something didn't take fully on initial setup. Can't hurt to try. I say this because it sounds VERY similar to the problem I had with my Vibrant.. and many of the issues I keep reading people having make me think that the install methods aren't perfect and fool proof.
If you're on the leak you'd have to make a nandroid, but if on a rom that doesn't wipe data partition you can just wipe the system and reinstall- or worse case restore a nandroid of data partition.
Click to expand...
Click to collapse
Yeah. That was my first suspicion. Sadly it persisted even when I restored a backup of when I was running nrg's gingerbread Rom. Think it might be some kind of weird hardware failure since it persists no matter what I do (clean install from scratch with everything wiped/cleared).
Nit a huge deal. If j ever have to look something up while on a call all I gotta do is throw the speaker on which is normally do in that situation anyways he he. Just bothersome when there's an issue you haven't been able to fix no matter what you've tried ya know? =)
Sent from my HTC_Amaze_4G using xda premium
AndroidAutobot said:
No cuz then itd just stay off. The problem is that the screen won't stay on while in a call. If I touch the screen anywhere while on a call the screen shuts off immediately. =( very annoying. Can't even hang up sometimes.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I have the same issue, I thought it was just my phone. It's such an annoying issue, can't even hang up half the time. I love the phone but that one issue is really irking me. I never had this issue til I updated to ICS.
Sent from my HTC_Amaze_4G using xda premium
Headshots4life said:
I have the same issue, I thought it was just my phone. It's such an annoying issue, can't even hang up half the time. I love the phone but that one issue is really irking me. I never had this issue til I updated to ICS.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
That's the really strange thing of it is that I never had the issue till I flashed ICS as well, but then the issue persisted when I restored an old gingerbread backup. Hopefully someone might see this that might have a better understanding and be able to figure out what's causing this to happen. =L. I'll change the subject of the thread to hopefully draw attention to it.
Question for you (let's compare) are you s off? And what Rom are you currently running? I'm inclined to think its not Rom related since the issue persists even when restoring a nandroid back up from days before I ever obtained s off and flashed ics. It'd be nice to confirm this is happening on Roms other than energy. Don't feel like going through all the steps to flash revolutionary or any of the other ics roms at this moment just to confirm what I already suspect.
Sent from my HTC_Amaze_4G using xda premium
Hello, under Gingerbread I used to really like the pattern unlock feature, but since ICS it has become a real hassle. Because the circles are much smaller, you have to be much more accurate. I used to be able to unlock it without looking directly at the screen, but with ICS I no longer can.
I assume this change was done for security reasons, but it DOES NOT make the phone any safer, because if I was a thief that had just stolen this phone and was trying to circumvent the pattern unlock, I would make sure that I was putting my finger right through the centre of the circles anyway. The only person that will now find it more difficult to get into the phone is the owner.
Anyone know if there's a way of changing the size of the cirles to something like what they were in gingerbread?
Secondly, sometimes (no obvious pattern for it) I would turn on my screen and try to do the pattern unlock, but it's as if it fails after about two circles and I have to start again. This is not related to the size of the circles because it happens even if I right through the middle of the circles. It'll fail even though my finger is still drawing the pattern. Sometimes it takes 3 or 4 attempts to get it to unlock.
Any ideas what might be causing this? I guess it's because the phone is busy doing something else. But what?
Thanks.
I don't have a solution, however I am just replying to say that I am also suffering from the seconds problem. It does get quite frustrating especially when you have an urgent task to do.
A thief would simply shut your phone down by holding the power button, boot into download mode & flash a new rom ;-) I also use pattern unlock & I'm not aware of any way to fix the issues you've mentioned; both the small circles & the issue where it takes you a few tries to successfully draw the pattern because your swipes aren't registered on the screen properly. I stick with it because it's slightly more easy to sue/convenient than a pin (for me anyways).
At the end of the day, there probably isn't a great deal you can do to stop someone nicking your phone & wiping it. Some security apps claim do to lots of things, I can't personally verify whether they're effective or not as I don't use one.