Database Users

Touchscreen Controlling Itself

I picked up my Nexus 7 about a half hour ago, woke it up and all of the sudden it started clicking things on its own. I wasn't even touching the screen at all. I had to lock the device for it to stop doing it, and after waking it back up the touchscreen was twonky. I would touch, but it wouldn't register until like the 3rd click. I restarted the device and its fine again.
I have the screen separation issue, though its not bad and doesnt bother me so I havent considered sending it back. But now that it has a mind of its own, its kind of freaking me out. I am unable to replicate it so far and I can't find anybody on these forums who has the same problem. Any ideas what is going on?

it's another ghost unit...
Sent from my Nexus 7

sharp2G said:
it's another ghost unit...
Sent from my Nexus 7
Click to expand...
Click to collapse
So it's a hardware issue and I should get it replaced?

I had the same thing happen to me a couple weeks ago.
After waking it up from sleep it started touching itself.
I restarted the device and it hasn't happened since.
Hope I don't have to return it.

My god! IT'S ALIVE!
Sent from my Nexus 7 using xda premium

I had the same thing happen on Saturday. There were odd solid white line outlines around the icons as well. I had to force it to power off and restart it. It's been okay since.
Ken

I too experienced the issue. I can replicate the issue by running "Gallery" app, select an album, set it on Slide Show mode. Within 15 mins or so, it will start malfunctioning.

I've discovered how to reproduce the problem on my tablet:
1. Put the tablet to sleep by closing smart cover or using a magnet
2. Plug in wall charger
3. Open the smart cover and the touchscreen malfunctions
The screen does not malfunction when I put the device to sleep by pressing the power button and insert the charger.
Can anyone else confirm this happens to them or is it just me?

My nexus7 is controlling itself after 10 mins of playing a game... this is nuts?
EDIT:
Really PI$$ED off now. Travelled to the shop where I bought it. Told them they said "they have to see the problem" I sit there for 25 minutes playing a game, google earth...anything to create this problem.
NOTHING.
get back home!! gusss what? stupid tablet is controlling itself again! OMG this crap is annoying.
edit: I sold the nexus. It had a fault on the screen. I paid £70 and managed to get £80 for it so am happy with that at least

Same issue!! Is someone remotely hacking in??
I have seen the exact same issue on mine. Weird and very worrying. Have seen apps being opened and pages being scrolled. Has only happened twice in the past few weeks (that I have noticed). Have checked firewall logs on my home network, but unfortunately my ISP has made the UI more 'user friendly' even in advance mode so can't get any actually useful information from the logs (though I don't have any port forwarding active). My only guess is that it is therefore:
A) Random HW/SW issue - seems unlikely, but possible I guess
B) Some nefarious app giving external access (all apps from Play Store though)
Will try and get a video of it next time to put on Youtube nad have installed the logcat app (though to be honest I don't really know how to use it).
Anyone else seen this or have any suggestions on what to do?

drsp123 said:
I have seen the exact same issue on mine. Weird and very worrying. Have seen apps being opened and pages being scrolled. Has only happened twice in the past few weeks (that I have noticed). Have checked firewall logs on my home network, but unfortunately my ISP has made the UI more 'user friendly' even in advance mode so can't get any actually useful information from the logs (though I don't have any port forwarding active). My only guess is that it is therefore:
A) Random HW/SW issue - seems unlikely, but possible I guess
B) Some nefarious app giving external access (all apps from Play Store though)
Will try and get a video of it next time to put on Youtube nad have installed the logcat app (though to be honest I don't really know how to use it).
Anyone else seen this or have any suggestions on what to do?
Click to expand...
Click to collapse
May I ask. Have you used a case that has a magnet that may have touched the screen? I theorized that this may have happened to mine because right where the magnet clipped the case is right where fault started. When i touched the screen just on the edge in that spot it started going crazy.
So I sold as faulty

restlessrob said:
May I ask. Have you used a case that has a magnet that may have touched the screen? I theorized that this may have happened to mine because right where the magnet clipped the case is right where fault started. When i touched the screen just on the edge in that spot it started going crazy.
So I sold as faulty
Click to expand...
Click to collapse
Hi - I have briefly (only use it when travelling and have it in a bag to protect it from knocks and scrapes), but the case was never around when the screen has been off doing it's own thing....so I would be surprised if there was a link between a small magnet being near it a few times and a recurrent fault of some kind.

drsp123 said:
Hi - I have briefly (only use it when travelling and have it in a bag to protect it from knocks and scrapes), but the case was never around when the screen has been off doing it's own thing....so I would be surprised if there was a link between a small magnet being near it a few times and a recurrent fault of some kind.
Click to expand...
Click to collapse
I read somebody else used a case with a magnet and thought that slight chance that it could've caused the fault. I know on the one I had I could instantly recreate the problem by touching in that place a few times. perhaps just a coincidence?

Didn't work for me, just registers my own touches
Sent from my Nexus 7 using xda app-developers app

alimhaque98 said:
Didn't work for me, just registers my own touches
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My device has a similar issue randomly. Detects inputs that aren't there. Most of the time it is one prolonged input. Sleep then wake and problem solved. I don't know if I have the screen seperation issue or not. My device is only two weeks old and has never seen a magnet before.

formerfreeagent said:
My device has a similar issue randomly. Detects inputs that aren't there. Most of the time it is one prolonged input. Sleep then wake and problem solved. I don't know if I have the screen seperation issue or not. My device is only two weeks old and has never seen a magnet before.
Click to expand...
Click to collapse
Bought 4 Nexus 7's for the family for Christmas and one unit had this issue. Read up about it before returning it the next day. Apparently it's a problem with the digitizer (I think that was what the hardware piece was called). Basically made the N7 unusable because it'd detect other "ghost" touches. Especially annoying when trying to unlock the device. Long story short, the unit was returned to Staples and replaced with a new one. So if you're is still under the "new buy" warranty I'd definitely try for a replacement.

Aes28 said:
,,, Basically made the N7 unusable because it'd detect other "ghost" touches. Especially annoying when trying to unlock the device. Long story short, the unit was returned to Staples and replaced with a new one ...
Click to expand...
Click to collapse
Ditto, + 1 here and my ex-N7 16GB WiFi unit was from local Staples, 1 of 2 "open-box" ones that they had in stock, no wonder manager was "kind" enough to approve a 10% discount for it, hmmm - SOB quite possibly knew it was a problem unit returned by another customer & just wanted to pass it on. It had 4.1.2 loaded and intially, the OTA upgrade to 4.2 seemed to make things better (false.)
It was horrible with the sluggish & un-responsive touchscreen and even unlocking, especially bad over time as I had managed to unlock the bootloader & root it to load custom Rom. It's as if the hardware had a keylogger installed and/or was hacked remotely, trying to take over the tablet and typing its own command as I input gmail account info & password - freaking mad crazy, to the point as others said, I started checking the wireless router's firewall & security logs, etc. for signs of breach, etc. and even release the DHCP to get a new external IP on our Fios link. Disabling WiFi seemed to at least "calm" it down but made the device useless. GPS radio/receiver also seemed to be defective. To make a long story short, it has been returned to Staple as we are within the holidays/14 days technology product return & exchange timeframe - and, of course, all 16GB WiFi models are out of stock everywhere - ended up paying the difference & traded up to a 32GB WiFi model - S/N beginning with "CAO"s and has 4.1.2 on it
Noticed the immediate difference - this one is perfect and no hardware issues whatsoever - and so far so good and with all the issues cited about 4.2 - staying with 4.1.2 for now by disabling the fraemwork, etc. to stop the annoying OTA upgrade reminder. Unlocked & rooted, tweaked it with the goodies & Flash Player 11.x loaded with Chrome browser removed, this is what a N7 should be like.

I have had a similar issue twice. I was reading a webpage when all of a sudden a pop up appears asking where I want to send it to, then it gives me a list eg. Dropbox , email, etc. I never press anything and I didn't even know what wanted to be sent lol. Hopefully its nothing serious.
Sent from my Nexus 7 using Tapatalk HD

nexus7
Fowarek said:
I picked up my Nexus 7 about a half hour ago, woke it up and all of the sudden it started clicking things on its own. I wasn't even touching the screen at all. I had to lock the device for it to stop doing it, and after waking it back up the touchscreen was twonky. I would touch, but it wouldn't register until like the 3rd click. I restarted the device and its fine again.
I have the screen separation issue, though its not bad and doesnt bother me so I havent considered sending it back. But now that it has a mind of its own, its kind of freaking me out. I am unable to replicate it so far and I can't find anybody on these forums who has the same problem. Any ideas what is going on?
Click to expand...
Click to collapse
i have the same problem,had my nexus since nov 2012 just started to do this mind of its own thing 1 week ago at any time for no reason any ideas anyone?????

mine does it to all the time especially if i slightly squeeze the bezel? i get random touches all over the screen?

[Q] Overheating with WiFi

Hi,
I bought an HD2 off of ebay on Wednesday that was in `Perfect working order`.
Yea.
Not exactly.
It works perfectly, until you try and connect it to a wireless network, you then go on the internet for a while, and if you put your finger on the little black section underneath the screen where the HTC logo is, it's hot to the touch, it then does what an HD2 does when it overheats; freezes then reboots itself.. I've tried using the internet with the 3G connection and it doesn't heat up, so it's definitely the WiFi causing this phenomenon.
Is this fixable, or FUBAR?
Thanks
PS. Facebook, Twitter and O!Market, I presume this trend would follow to other apps that use internet, none of them work despite being connected to a network. They all say `No Connection` or similar, would like some advice on that as well.

lol I encountered the same thing recently, "almost new" my butt.
Since I don't use my devices with cell service (radio's turned off always), I obviously rely on Wi-Fi. But it seems to me that Wi-Fi is causing overheating, but it once went down when Wi-Fi was off, so I'm thinking that my device is just "propelled" faster by Wi-Fi.
but anyways, my device would heat up right above the buttons and in the bottom portion of the device on the back. So I opened it up, only to be surprised to find the Wi-Fi antennae in a corner on the top and the cellular radio in the bottom.
At this point, I'm assuming it's processor is just beginning to go, hopefully I can find another HD2 motherboard or dead device to salvage from.
Or maybe fashion a heatsink, because the region always hotter than the rest of the device when it crashes. (yes I did see the thread where it was said not to do)

Another option is thermal pads which has a much easier process of installation. Just need to be sure they are placed correctly.
Sent from my SGH-T889 using xda app-developers app

kingxklick said:
Another option is thermal pads which has a much easier process of installation. Just need to be sure they are placed correctly.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
yea maybe i'll consider that, but i guess it really depends on whether i want to keep adding duct tape (metaphorically) or try to get a Windows Phone and cut my time losses

ebay deals are not trustworthy

[Q] Proximity Sensor Problems

My proximity sensor just suddenly started to half work. When on a phone call I would cover the sensor with my finger and the screen will shut off. When I move my finger away, the screen won't turn back on. I got into the test menu to test the sensor and notice that the adc reading seems to track my finger fine but once the sensor detect my finger it always stays at "1" (with a green vibrating screen) I am close to restoring my phone back to stock with Odin to see if it will fix it. But if anyone has any other suggestions it would be much appreciated. I have an i337m running stock rooted.

kiru said:
My proximity sensor just suddenly started to half work. When on a phone call I would cover the sensor with my finger and the screen will shut off. When I move my finger away, the screen won't turn back on. I got into the test menu to test the sensor and notice that the adc reading seems to track my finger fine but once the sensor detect my finger it always stays at "1" (with a green vibrating screen) I am close to restoring my phone back to stock with Odin to see if it will fix it. But if anyone has any other suggestions it would be much appreciated. I have an i337m running stock rooted.
Click to expand...
Click to collapse
if a battery pull didnt fix it, an odin restore is def the next step. then from there its a warranty exchange (ewww!!)

hapticxchaos said:
if a battery pull didnt fix it, an odin restore is def the next step. then from there its a warranty exchange (ewww!!)
Click to expand...
Click to collapse
Well it seem like a factory reset and restore from Odin didn't work. Any other things I can try?.....trying to avoid a warranty claim as this is my only phone.

kiru said:
Well it seem like a factory reset and restore from Odin didn't work. Any other things I can try?.....trying to avoid a warranty claim as this is my only phone.
Click to expand...
Click to collapse
If you have AT&T, you can call their warranty center and they will send you out a refurbished phone. If you let them know that it's a brand new phone and you take care of your devices, and that you shouldn't be given a used phone after such a short period of time, they can also send you a brand new one. They'll include a pre-paid shipping label so you can return the old one once you've transferred everything to the new one.

Screen protectors and covers to close to the sensor would add craziness in the past.

johnus said:
If you have AT&T, you can call their warranty center and they will send you out a refurbished phone. If you let them know that it's a brand new phone and you take care of your devices, and that you shouldn't be given a used phone after such a short period of time, they can also send you a brand new one. They'll include a pre-paid shipping label so you can return the old one once you've transferred everything to the new one.
Click to expand...
Click to collapse
I am in Canada, so I guess I will try to go back to them and see what they can do. After testing the sensor I found out a few things. The proximity sensor will work indoors but when I go out doors it doesn't anymore. With that said, when indoor lights are really bright, it also stops working.
alphadog00 said:
Screen protectors and covers to close to the sensor would add craziness in the past.
Click to expand...
Click to collapse
I don't have anything covering the sensor what so ever.

In the past, having a case that was next to the proximity sensor was enough to illicit some odd behavior. If you have any kind of case with a lip, you should test without it on
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

alphadog00 said:
In the past, having a case that was next to the proximity sensor was enough to illicit some odd behavior. If you have any kind of case with a lip, you should test without it on
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I do have a case but it's the original Samsung protective cover case.

But have you tested the prox sensor without the case?
You have not confirmed that either way. If you want to exchange go ahead, but if it were me I would test everything I could first before I go to all the trouble of an exchange to find the problem persists.
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
Also, look into turning off the gesture and any in pocket detection to see if that makes a difference.

alphadog00 said:
But have you tested the prox sensor without the case?
You have not confirmed that either way. If you want to exchange go ahead, but if it were me I would test everything I could first before I go to all the trouble of an exchange to find the problem persists.
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
Also, look into turning off the gesture and any in pocket detection to see if that makes a difference.
Click to expand...
Click to collapse
Hi, yes I did test without the case as well and all my gestures are off except smart stay (which I turned off to test as well) I actually went to a shop around here that had two live S4s on demo. I went into that test menu *#0*# and looked at their proximity adc values. Both display models were nearly identical in values.... (would start from 2 onward to 255 when fully covered) as mine idles at 46+ when not covered. To me, it just looks like my sensor lost its calibration, but I don't think there is a way to calibrate it. I looked through the build prop.. even tried this through the terminal :
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
Still no luck. I think I am going to reach out to Samsung as I found a walk in service depot near my area. This issue only really started the last few days...and it is driving me nuts

kiru said:
Hi, yes I did test without the case as well and all my gestures are off except smart stay (which I turned off to test as well) I actually went to a shop around here that had two live S4s on demo. I went into that test menu *#0*# and looked at their proximity adc values. Both display models were nearly identical in values.... (would start from 2 onward to 255 when fully covered) as mine idles at 46+ when not covered. To me, it just looks like my sensor lost its calibration, but I don't think there is a way to calibrate it. I looked through the build prop.. even tried this through the terminal :
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
Still no luck. I think I am going to reach out to Samsung as I found a walk in service depot near my area. This issue only really started the last few days...and it is driving me nuts
Click to expand...
Click to collapse
Thanks for confirming... I know these were simplistic suggestions, but some phones in the past had really touchy sensors if anything was even nearby. Hopefully you will have good luck at the service center. I didn't know Samsung even had walk in centers.

alphadog00 said:
Thanks for confirming... I know these were simplistic suggestions, but some phones in the past had really touchy sensors if anything was even nearby. Hopefully you will have good luck at the service center. I didn't know Samsung even had walk in centers.
Click to expand...
Click to collapse
I also didn't realise they had the service centres. I found it on their web site.

Fingerprint scanner reliability

Hello! I have seen the ugly head come around that the scanner has not been super reliable. Now, I have the Tmo version and am on 9.0.0. Is that the reason currently? If not, It seems like the screen protector has smudges on it thus causing miss reads. If I try to wipe it off, it helps. Maybe we should be looking at a different screen protector? Thoughts?
Cheers
Joshua

I haven't had a fail to read yet... A few times it was slightly slower but still went through. Maybe try resetting up your finger. I know if my hands have been wet for a while my old phones wouldn't read.

EspElement said:
Hello! I have seen the ugly head come around that the scanner has not been super reliable. Now, I have the Tmo version and am on 9.0.0. Is that the reason currently? If not, It seems like the screen protector has smudges on it thus causing miss reads. If I try to wipe it off, it helps. Maybe we should be looking at a different screen protector? Thoughts?
Cheers
Joshua
Click to expand...
Click to collapse
Just got mine and the fingerprint reader is working with mine. I have the unlocked version with 9.0.1 right now.

Forgetfull said:
I haven't had a fail to read yet... A few times it was slightly slower but still went through. Maybe try resetting up your finger. I know if my hands have been wet for a while my old phones wouldn't read.
Click to expand...
Click to collapse
I have reset it up a few times now. Tried even setting it up twice and that still didn't help much (to do this, I just kept pressing it again and again and it finally logged a second finger).

EspElement said:
I have reset it up a few times now. Tried even setting it up twice and that still didn't help much (to do this, I just kept pressing it again and again and it finally logged a second finger).
Click to expand...
Click to collapse
The more i use the FP reader, the better it seems to be getting. One thing is that it requires more pressure than my old Moto Z Play, but that's been an easy adjustment. Give it a little more time and continue to use all the fingers that you have stored. I mainly use my right thumb, and it works all the time now. My left thumb is hit and miss, so I'm using it more.

Unlocked the display 30+ times on 9.0.4 and it didn't reject my finger once. Speed varied each time if you place your finger/thumb perfectly aligned will unlock almost instantly
Was an OTA for screen unlock improvements already not sure what it changed though

pkadavid said:
The more i use the FP reader, the better it seems to be getting. One thing is that it requires more pressure than my old Moto Z Play, but that's been an easy adjustment. Give it a little more time and continue to use all the fingers that you have stored. I mainly use my right thumb, and it works all the time now. My left thumb is hit and miss, so I'm using it more.
Click to expand...
Click to collapse
Ill try pressing harder. Good idea!

I have the TMo version and I don't really get failures for my main/first finger entered. It seems that the more I use a particular finger, the better it unlocks. So the first finger is fine. The second was ok and is getting better. Third and fourth are still a mixed bag but getting better. My suggestion is to make sure you are enrolling them as you would be using them. So if you're going to be using a particular finger while cradling the phone a certain way, enroll it that way. If you will use that finger while the phone is sitting on your desk, enroll it that way. That seems to be the main thing I've found.

It seems the scanner isn't reliable on mine. It is really snappy after the initial setup. Then it loses accuracy within minutes after the setup. It doesn't recognize any of the finger 90% of the the time. I ended up either enter in the pin or use face detection. I don't understand the problem. my oneplus 6t is a tmobile.

I've got a McLaren on OS 9.0.9, and can definitely vouch for unlock instability w/ the left thumb.
Still have the screen protector on from factory shipment, so don't know if removing it would help, but not enough of a nuisance for me to want to remove it...yet.

I'm having an even worse issue.. A friend is able to unlock my phone without adding his fingerprint to my phone.. OP isn't taking this issue serious when I report this to them and they keep telling me to add my fingerprints again..

I have a OP 6T McLaren Edition, and just registered my right thumb. When I can't use my thumb, I use face recognition.
So far it's been reliable after a few weeks of use, but I've noticed you need to learn the right spot and the way you put the finger also influences its accuracy.

Something I've noticed...
I didn't use the "face unlock" when I first got the phone. Just used the fingerprint...VERY quick. Then, I turned on the face unlock just to see how well it worked, and was surprised how well it DID work (just not with sunglasses...duh). I've noticed, that if I wake up the phone,
with it anywhere near my face and try to unlock it with the fingerprint sensor (habit), the phone will stutter while I assume it is trying figure out WHICH way to unlock it.
Any chance that is the issue with yours?
If I have the phone laying on a table, no where near my face, and hit the power button, the fingerprint sensor is VERY responsive, but, if my face is anywhere near the phone, it struggles if I hit the fingerprint sensor.
Just throwing it out there...

Hmm.. I did notice that. I'll try disabling face unlock on my phone and observe it.

Fingerprint Sensor Glitch

Currently testing on Tmo 6T - I am able to unlock my device with my middle finger knuckle -
This works 6 out of 10 times. I was also able to unlock using my daughter's knuckle. Has anyone else tested/experienced this. I saw that some other people have been able to unlock using fingers that arent registered by using just the edges.
I do not have smart / face unlock enabled. Nor my knuckles registered

WizCipher said:
Currently testing on Tmo 6T - I am able to unlock my device with my middle finger knuckle -
This works 6 out of 10 times. I was also able to unlock using my daughter's knuckle. Has anyone else tested/experienced this. I saw that some other people have been able to unlock using fingers that arent registered by using just the edges.
I do not have smart / face unlock enabled. Nor my knuckles registered
Click to expand...
Click to collapse
My knuckles are not unlocking my phone. Are you pressing it straight on? I tried with a few different knuckles.....

mang0 said:
My knuckles are not unlocking my phone. Are you pressing it straight on? I tried with a few different knuckles.....
Click to expand...
Click to collapse
Using my right hand, my middle finger knuckle works best to do this, I place at the top of the with a slight left right motion with it's lighting up.

My knuckle isn't working on my phone

Correction, its not the knuckle, the correct term is the proximal phalangeal Joint. The main bend in your finger. That portion unlocks my phone. I tried on my sisters device same thing. This is done using the skin portion, not the underside of the hand
https://www.onehealth.co.uk/orthopaedics-procedures-proximal-phalangel-joint-pip

Still not working here.
Bit annoying to test because of the awesome face unlock ?
But try to delete an retrain your fingerprints. Maybe you have a simple bug here

Only my fingerprints unlock my phone.

OP, check to make sure Google Smart Lock is not enabled. This is often the reason for cases like this so I'm guessing that's why you're able to bypass the security as well.

Discussion about this bug is going on for some days now over at Oneplus Community:
https://forums.oneplus.com/threads/fingerprint-massive-bug-other-people-can-unlock-the-phone.941931/
Only a few have yet encountered this issues, me counting

Doesn't work for me

I would guess that it's not a sensor problem but a problem/bug within the algorithm. Either this happens when enrolling the print or when the algorithm is trying to improve/learn reading your print. Maybe there is one point where the accepted pattern gets too vage, thus allowing even non-finger parts of the body as well as different prints?

Bäcker said:
I would guess that it's not a sensor problem but a problem/bug within the algorithm. Either this happens when enrolling the print or when the algorithm is trying to improve/learn reading your print. Maybe there is one point where the accepted pattern gets too vage, thus allowing even non-finger parts of the body as well as different prints?
Click to expand...
Click to collapse
Edit. Face-unlock was overriding the fingerprint/knuckle attempts in my case.

Tmobile is replacing my device - The Reps were able to unlock my device... kind of creepy