Database Develop

Nexus One hardware issue.

ok it doenst happen when i lay the phone down on the surface and click on the screen it works perfectly
however when i hold it with my right hand and touch the middle of the screen with my thumb
it opens up phone dialer, or appdrawer or vibrante cause it clicks the capacitive button.
when i hold it with my left hand it gets a little bit better but it still does.
if i hold the nexus carefully and touch the screen , it works, when i hold it like this
the things gets better when i put a thick case like otterbox..
is this a hardware issue? ( found similar video on youtube)
my phone is rooted but can i still get a replacement phone?( already put everything back to stock)
and if i do get a replacement, are they going to charge me with anything?
my current nexus one trackball doenst scroll up but everything else works.
How many of you guys got a replacement even though your phone was rooted?

Make sure part of your hand doesn't touch the screen.
Sent from my Google Phone

it's a hardware issue...
all you can do is not grip the phone too closely to the edge of the screen. It registers touches even if you are not touching the screen completely. But that to be a problem you have to have giant hands
I've had this happen to me once since I had it from launch day. It did happen with my Otterbox commuter series, and a clarivue screen protector. But I turned it off and on again and it was fine.
anyway as stevio jobsio whould say, you're holding it wrong

ChongoDroid said:
Make sure part of your hand doesn't touch the screen.
Sent from my Google Phone
Click to expand...
Click to collapse
ok so it is a hardware issue?
no i am not touching any part of the screen. i made sure i wasnt touching the screen.
but it does happen when i hold my phone closely to the edges.
i never had this kind of issues with other touch screen phones..

Well I dunno... One finger at a time and your good to go unless you got fat hands lol
Sent from my Google Phone

I can confirm that my device too does this. When lying in bed I browse the net with one hand and try and scroll....the edges of the touchscreen seem to register depression when the chassis is pushed or gripped too hard also.
It's a minor irritation to me, but I agree it is a hardware issue.

Touch screen issues...

So I am wondering if any of the wonderful people here at XDA are experiencing screen issues with the nook color. I have had my unit about a week, and have had numerous episodes of the screen registering touches randomly. This issue is apparently not isolated as there are youtube videos and a B&N support forum thread discussing the matter.
So is anyone out there having any touchscreen craziness? If so are you doing anything about it? Not sure if I should return my unit and get another or wait for some possible firmware update...
As always any wisdom is appreciated!

http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
Says at the top recalibrating will fixes "phantom touches" or inaccurate touches, or not respond to reasonable touches.

Mine was doing the same. I bought a screen protector and so far it hasn't happened.

My screen wasn't having "phantom touches," but at times I would press near the top and bottom edges, it seems to not be very responsive there. For example, pressing the search button in the marketplace that's at the very top right. Or pressing one of the buttons at the bottom menu.
I wiped my device back to factory and then did the latest Auto-Nooter, and started using Go Launcher. Things are much better now it seems. I think it may still happen occasionally though.

camwinnn said:
...recalibrating will fixes "phantom touches" or inaccurate touches, or not respond to reasonable touches.
Click to expand...
Click to collapse
Not just the phantom but inaccurate touches which sounds like yours, atm thats all ive seen about fixing screen stuff.
But other threads have been started where others have the same problem on the outer parts of the screen so it could be a Firmware/Hardware problem.
GTOMEX09 said:
works for me, in that the process completes, but the touchscreen is the same. The sensitivity issue at the edges is universal and very frustrating.
Click to expand...
Click to collapse
rboatright said:
Try running calibration while holding a finger on the screen near the edge.
Click to expand...
Click to collapse

[Q] Touch screen issue

Well, i have noticed that if i lift my finger a little bit from the screen (a few mm), this one is like if i still touching it only responses when a lift more my finger, so i cant type fast, anyone else is having this issue?
Sorry for my bad english

Yes, do a search in questions sub forum. But several people including myself have this Phantom touch issue. Screen is too sensitive.

As someone who uses phone as Mini Computer for.presentations , proposals with photos sent in desktop
Email- this could be a problem for typing.
Is sensitivity reduced tempered glass protector ?

thunderfox1 said:
Well, i have noticed that if i lift my finger a little bit from the screen (a few mm), this one is like if i still touching it only responses when a lift more my finger, so i cant type fast, anyone else is having this issue?
Sorry for my bad english
Click to expand...
Click to collapse
Even at over a full mm? Is glove mode enabled by any chance?

degraaff said:
Even at over a full mm? Is glove mode enabled by any chance?
Click to expand...
Click to collapse
Hmm, the glove mode is disabled, and i'm having this issue even whith a crystal screen protector , This is kinda disappointing, anyway glad to know that i'm not the only one with this problem, i hope it fixed soon.

proximity sensor issues? att varient

Anyone notice their proximity sensor is very flaky?
The screen will not shut off when I close my wallet cover over it. It will shut off when I start talking on the phone, but then will not "wake" when I move it away to hang up. I actually couldnt find anyway to wake it up so i just waited until the other side hung up (it was a recorded msg).
Any ideas? I may just shut off the proximity sensor and wait till I can swap it in store. Of course this was right after i installed a tempered glass screen .... would that impact it at all??thx!

http://forum.xda-developers.com/showthread.php?t=2922645
It seems that certain brands of tempered glass screen protectors are causing the same issue that you describe.

k2buckley said:
http://forum.xda-developers.com/showthread.php?t=2922645
It seems that certain brands of tempered glass screen protectors are causing the same issue that you describe.
Click to expand...
Click to collapse
thanks. mine was from extremeguard. i removed it. wait and see until the next person calls me. i contacted ATT and they said i have 11 days to return it (no exchanges available), and to try a master reset first

didnt seem to work after moving the glass. did a full reset and now it works....
ill try the glass again tomrrow and see if it stops working again. bizarre.

k2buckley said:
http://forum.xda-developers.com/showthread.php?t=2922645
It seems that certain brands of tempered glass screen protectors are causing the same issue that you describe.
Click to expand...
Click to collapse
this fixed the problem. thank you for saving me time and anguish returning the phone

eb50 said:
this fixed the problem. thank you for saving me time and anguish returning the phone
Click to expand...
Click to collapse
You're welcome. I'm glad you got it straightened out

k2buckley said:
You're welcome. I'm glad you got it straightened out
Click to expand...
Click to collapse
My tempered glass has a cutout for the 2 sensors on the left, are there any sensors on the right of the speaker? My proximity sensor also is not working. I will probably return my tempered glass also if this is the case...

This is happening to me and I don't have a screen protector. It's really getting annoying.

I'm having issues as well.... Not using any screen protector or whatsoever...

Yeh same here.. Looks like the sensor is maybe too sensitive. Hope sw can fix this.

+1 for the issue.
Cannot hang up after a call because the screen is black. Have to push the power button to wake it up first.
No screen protector.

mikkelwe said:
+1 for the issue.
Cannot hang up after a call because the screen is black. Have to push the power button to wake it up first.
No screen protector.
Click to expand...
Click to collapse
I just restored a backup of the original rom and the problem went away. So it's probably an issue with cm. Was on cm nightly from 01-13-2014

Did you try going to settings , accessibility , power button ends call, toggle that on and off.
After completing the above mentioned step. Reboot your phone and try making a call. I hope the issue get resolved.
I tried this step on an unrooted phone, which was recieved just yesterday.
I got this fix from some other thread.

Is there a way to turn off proximity sensor without rooting? Looked through setting and must have missed it. Thanks in advance.

Still having this issue as well. I tried toggling the power button option then restarting my phone, it seems to help for a very short period of time (few hours maybe). I have tried several different screen protectors, the most recent ones having a cut out for the sensor and there is a decent gap between the two. Reloaded my phone several times and installed 5.0.1
The sensor doesn't really work to turn on the display when I go to pickup the phone and is spotty when making a call. In the first minute or so of the call, I can take the phone away from my head and it will register, illuminating the screen, after that it stops working.
I can't understand how it could be the screen protector at this point, it's no where close to obstructing the sensor.

Guess it's time to send this thing back. I must be nuts because I keep trying this power button suggestion and it just doesn't work for me longer than a few hours.

Same here, using a plastic rinkage screen protector no bubbles in it and the edge falls a good few MM from the sensor.
CM12 nightly builds still do it I'm on the 2/19th build with Franco kernel.

Best solution is get rid of the junk and get a Note 4. Mine is such a crap phone. It doesn't even do anything special except be big.

Hi,
Just to tell that I've got this pb since I installed the Spigen crystal protection, not even a tempered glass.
Before that I still had the original cheap film you get when you unbox, with the white corner.. the crystal is really nicer but it screws the sensor...

I believe it is software related. I have a tempered glass screen protector that does not cover the proximity sensor. I have noticed that about 60% of the time the screen does not turn back on when I move the phone away from my head. It seems to happen more when the phone call is longer than one minute. I also had a tempered glass protector that covered the sensor and had the same behavior. I did use an app to test the proximity sensor and with both screen protectors it worked 100% of the time using the app.
Sent from my Nexus 6 using XDA Premium HD app

Double tap to wake. Or more like quadruple tap to wake, eh?

I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?

If you move your phone first, then it will work by double tapping.
I think that quadruple tap works because one of those first two taps moves the phone.

Not from my experimentation. It doesn't seem to matter if i've moved it first or tapped it directly when it's sitting on the table. Then only factor that seems to matter is time since screen off.
Thanks for the input though.

It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.

pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
Click to expand...
Click to collapse
I'm on A.5.77, which is the latest, right?
I have this issue about 5% of the time, 95% of the time even if I have the phone lying still on the table double tap works. Must be something (also) else than the firmware!

pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake
Click to expand...
Click to collapse
double tap works first time every time even if the phone has been sitting still and idle for 10 hours.
I know theres a few people who have this problem but its something other than just the new firmware.

I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.

pipspeak said:
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
Click to expand...
Click to collapse
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...

had a tempered glass protector on from day one, phone has always been stock, no other launcher. T2W worked brilliantly until the latest firmware update. frustrating when the phone is the car mount, i have to hit the power button to get the screen on instead of just tap-tap.

quarrymanpaul said:
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
Click to expand...
Click to collapse
Full day's use now and replacing Nova launcher with Apex has definitely improved things.
Might help others in the same situation who are scratching their heads wondering why everyone else seems to have perfect tap2wake.

Tried Apex for a day as well. No different than Nova for me.

hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap

AM Radio said:
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Not working here.
I have a Nillkin tempered glass on mine though.

quack3d said:
I have a Nillkin tempered glass on mine though.
Click to expand...
Click to collapse
me too. weird. fingers crossed the next update takes care of this, properly.

AM Radio said:
...TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Works for me too. [emoji4]

Did Lollipop fix this problem?

quack3d said:
Did Lollipop fix this problem?
Click to expand...
Click to collapse
Not really. In fact it got worse.

quarrymanpaul said:
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
Click to expand...
Click to collapse
Well, I can tell you why this is happening. this happened to me, because I just had too many xposed modules.. once I got rid of them, everything went back to normal

Been a long time since I've posted here but found this thread as had the same issue when the phone is flat on a table.
Anyway, think I've found a solid solution or work around, depends how you look at it. If you use just an extended finger, all other fingers closed or away from the phone, it's very inconsistent but mostly unresponsive.
Solution: grip the top and bottom of the phone lightly with your thumb and middle or 4th finger at the same time as tapping the screen with your index finger. Works every time for me.
So Sony's reduced the sensitivity to the point where it needs additional capacitance so it knows you are holding the phone and it won't unlock in your pocket. Makes sense.

pretty frastrating here too.. but really can't find out the main reason of the problem here as immediately when I got the phone I rooted it, flashed .77, replaced stock launcher with nova, installed expsed and 2-3 modules :crying:
will try the three-taps and olding-phone+index-finger-tapping workarounds, thanks for the hints