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.
Related
Hi
I recently bought Amaze. Pretty awesome! I was all happy and clicking lots of pictures and stuff after which I decided to root because of the battery problem. Never mind that all good. But yesterday I randomly opened up the G-Sensor settings in display and I noticed some lag in the movements of those bubbles, I was confused and I knew this isn't how those bubbles move. I downloaded AndroSensor to check if everythings alright. But it wasn't I think there is some problem with my Accelerometer and Gyroscope :l those number besides the Accelerometer and Gyroscope keep on changing even if the phone is kept on the ground without any motion. If someone has experienced this or has a solution to it please help. I really don't want to ruin my experience with this phone.
Sent from my HTC_Amaze_4G using xda premium
Seriously no one? :O
Sent from my HTC_Amaze_4G using xda premium
I would just say get it exchanged man. I haven't had any issues along those lines and rooting shouldn't have any effect on those sensors =/
I also got probably a similar problem with the accelerometer. The phone began rotating the pictures as well as application windows absolutely wrong, unexpectedly and may say randomly.. and it isn't rooted yet..
P.S. I decided to go for the factory reset..
Now re-installing and re-setting all my operational environment
Anyhow the G sensor seems to resume its duly performance.. ))
jauhien said:
I also got probably a similar problem with the accelerometer. The phone began rotating the pictures as well as application windows absolutely wrong, unexpectedly and may say randomly.. and it isn't rooted yet..
P.S. I decided to go for the factory reset..
Now re-installing and re-setting all my operational environment
Anyhow the G sensor seems to resume its duly performance.. ))
Click to expand...
Click to collapse
Try and get AndroSenser from Market and let me know if the accelerometer values keep on changing even if the phone is kept on a surface with no movements.
Sent from my HTC_Amaze_4G using xda premium
Well my Amaze also has a prob with the g-sensor. it doesnt work at all there is no auto rotation , nothing. i have just had the phone for 2 days now. any solutions?
Try removing the battery and let sit for about a half hour. I had the same issue and this worked for me. Good luck.
the-other-gordo said:
Try removing the battery and let sit for about a half hour. I had the same issue and this worked for me. Good luck.
Click to expand...
Click to collapse
didnt work for me what should i do ? my other sensors are also not working
Got the same issue, at this point it doesn't work at all yet if I flash a rom with out a full wipe it'll work again until I restart. That being the case it feels like a driver issue to me... I'm not sure if anyone has a tool that will allow me to flash the proper drivers?
gunjan_25 said:
didnt work for me what should i do ? my other sensors are also not working
Click to expand...
Click to collapse
Call HTC as far as i know the phone hasnt even been out a year yet which means they should all still be under warranty. Htc sent me a new back, a battery and charger for things i made up so i could have back ups should anything go wrong. All sent for free and they dont even ask for the bad parts back. Their customer service is great. Unless you like messing with stuffvif a factory reset dosent fix it. Get a new one. & to the guy with the? About the accelerometer numbers they always dance around a little even when set down flat. As long as the phone rotates correctly and maybe get a game that uses it and az long as everything functions your good dont freak out because the numbers dont hold completely still.
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, people of xda-dev.
I just recently encountered a frustrating problem. One third of my touch screen is unresponsive. It just randomly happened over night.
I unlocked it and rooted it a little while ago (for the android battery app and such).
I tried the second method on this thread with no success : http://forum.xda-developers.com/showthread.php?t=1131649
I also tried restoring to factory state a couple of times and erased the cache.
I am running Android version 2.2.2
If you need more information, ask away!
Thank you.
If you search there is lots of threads about this issue. Only way replace digitizer
Its a common Atrix problem
I had this problem for about 6months now
Sent from my MB860 using XDA Premium App
So it wouldn't be something like, I don't know, a partition messing up or something? (since I unlocked it)
Thank you for your reply.
PhoenixFFX said:
So it wouldn't be something like, I don't know, a partition messing up or something? (since I unlocked it)
Thank you for your reply.
Click to expand...
Click to collapse
nope sorry m8
Aww.. well thanks!
So I need to buy a new digitizer and replace it?
Does it mean the new one will probably fail after a couple of months too?
Wow.. I removed the battery (again) and opened it again.
Same vertical dead line, but this time it's about half smaller, and a little shifted to the right :l (I'm testing it with Touch Test)
Do you really think it's hardware related?
If you still have warranty coverage, flash sbf to unlocked stock. Send it in. They will send you a brand new phone.
At least that is my experience with two separate atrix units.
PhoenixFFX said:
Wow.. I removed the battery (again) and opened it again.
Same vertical dead line, but this time it's about half smaller, and a little shifted to the right :l (I'm testing it with Touch Test)
Do you really think it's hardware related?
Click to expand...
Click to collapse
I know its that area that needs looking at. I had the issue. Used some tape near top of phone battery area. And everything worked again. Did a couple of battery pulls due to deving and now its lost again. Now it wont work again
Sent from my MB860 using XDA Premium App
A small part of my screen does not work. The part above the menu button. It has been this way for a while and the phone is usable. I can't type w,e,s,z and the comma in portrait mode. I thought the digitizer was damaged but last night everything started working and did so for quite some time until I charged my phone. After that it has been the same. Anyone ever have this problem before and could someone suggest a solution?
PS: The pds partition fix did not work.
Sent from my MB860 using XDA Premium HD app
What caused this? Did you recalibrate the screen with aroma installer?
Sent from my MB860 CM7.2 RC3 36p Radio
darkhokage said:
A small part of my screen does not work. The part above the menu button. It has been this way for a while and the phone is usable. I can't type w,e,s,z and the comma in portrait mode. I thought the digitizer was damaged but last night everything started working and did so for quite some time until I charged my phone. After that it has been the same. Anyone ever have this problem before and could someone suggest a solution?
PS: The pds partition fix did not work.
Sent from my MB860 using XDA Premium HD app
Click to expand...
Click to collapse
There are random reports of Jokersax's CM9 causing issues, and my phone is currently out on warranty repair with the same issue (dead area in digitizer). I have also heard that Motorola used crappy digitizers in the Atrix, and for this reason rolled the Atrix 2 to market quickly. All of these theories are unsubstantiated.
I tried the PDS fix (after backing up my PDS partition), a Google Play screen fix solution, flashing different ROMs on a fully wiped phone, SBF'ing to stock, and another calibration solution I found on XDA, but none worked. At that point it was back to Motorola with the phone. Hoping for a 2 week TAT. Good luck.
Soldier-2Point0 said:
What caused this? Did you recalibrate the screen with aroma installer?
Sent from my MB860 CM7.2 RC3 36p Radio
Click to expand...
Click to collapse
I don't know. This happened a few months after I bought the phone. Since I am in Pakistan, the phone came without the international warranty and repairs are not that easy. Up until a day ago, when everything started working, I thought that the digitizer was broken but now I have started to think differently.
Sent from my MB860 using XDA Premium HD app
tobnddl said:
There are random reports of Jokersax's CM9 causing issues, and my phone is currently out on warranty repair with the same issue (dead area in digitizer). I have also heard that Motorola used crappy digitizers in the Atrix, and for this reason rolled the Atrix 2 to market quickly. All of these theories are unsubstantiated.
I tried the PDS fix (after backing up my PDS partition), a Google Play screen fix solution, flashing different ROMs on a fully wiped phone, SBF'ing to stock, and another calibration solution I found on XDA, but none worked. At that point it was back to Motorola with the phone. Hoping for a 2 week TAT. Good luck.
Click to expand...
Click to collapse
I guess I will just have to live with it. The incident where everything started to work still gives me hope though. I will keep on trying and let you guys know if I make progress.
Sent from my MB860 using XDA Premium HD app
I had the same exact issue. If you still have warranty, send it in. This is a well documented problem.
If you have unlocked the bootloader, just flash the proper sbf back to stock.
That's what I did, and they sent me a brand new phone.
Okay people, I just got my S3 last night, and after about 3hrs of use, my problems developed. My problem is intermittent, but nonetheless, very aggrivating. When I press the power or home button, screen wakes, but touch is unresponsive. I thought it might have been a lockscreen issue, but I've tried all variants including no lockscreen and have the same problem. Is there any updates or fixes that anyone knows of or do I have a defective phone? Any thoughts are welcomed. For what its worth, I also rooted my device, and it installed supersu. I don't know if that could be related, but I'm going to give a full unroot reset a try as well.
Sent from my aokp_tenderloin using xda premium
Are you connected to charger, that can cause pro lems when getting unstable current
Sent from my GT-I9300 using xda app-developers app
On or off the charger, makes no difference. I Fully factory restored, pulled root, triangle counter reset, and everything else in between, and the issue still remains. Even tried another rom and kernel, sames results. Seems like I have a fancy light up paperweight for the most part. First samsung phone in over 10 years, and this is what I end up with. Great job samsung.
For how long is there no response.anyway try disable s-voice in settings.that is directly related to home button.power button hmm, don't know..
So, factory reset the phone, reflashed stock rom, even booted phone up with no sim or memory card, fresh from a reset. On the main setup screen, if I lock the phone, then wake it up, touch is dead. Definitely a hardware problem. Called samsung uk because anyone who used DAILYSTEALS.COM will find out if their phone ever needs service, that the phones sold via them came from the UK. Not really happy this wasn't explained on their website prior to purchase, as I would have held off. Now my 3 day old phone with not even 24hrs of use on it is off to a UK service center.
Word to the wise when buying online, check the origin of your phone if the retailer isn't an official seller. now my money saved is going right back.
zodiaxe66 said:
For how long is there no response.anyway try disable s-voice in settings.that is directly related to home button.power button hmm, don't know..
Click to expand...
Click to collapse
As stupid as it may be, I want s-voice to work, shouldn't have to disable something to make the phone work properly out the box.