Related
This stuff is making me nervous.
Recently I've started to experience a kinda strange bug. Sometimes, screen calibration goes nuts. When I click on the right part of the screen, the click actually goes to the left part edge. But if I scroll up/down on the right part - everything is ok.
At the beginning this bug appeared rarely and only till device is turned off/on. But for last few days it's almost impossible to use it. Bug appears a lot and doesn't go away even after soft reset.
So far I've experienced this bug in Opera and in TouchFlow shell.
Is this a hardware problem? firmware?
Screen looks great. But I'm having two issues.
First, the screen feels kinda rough dragging my finger across. By comparison my Galaxy S phone and iPad are very smooth and glide with no resistance.
Is this normal, can it be improved?
Second, the screen seems unresponsive at times. I'll have to tap more than one to get it to recognize an action. Maybe it's just being slow.
Also the calibration seems to be a bit off. I often seem to be clicking items below what I tapped on. Not sure it's completely user error since I don't seem to be having this much trouble with my 4 inch Android phone.
PS. The phone is rooted with AutoNooter and using LauncherPro and Dolphin browser.
Ravynmagi said:
Screen looks great. But I'm having two issues.
First, the screen feels kinda rough dragging my finger across. By comparison my Galaxy S phone and iPad are very smooth and glide with no resistance.
Is this normal, can it be improved?
Second, the screen seems unresponsive at times. I'll have to tap more than one to get it to recognize an action. Maybe it's just being slow.
Also the calibration seems to be a bit off. I often seem to be clicking items below what I tapped on. Not sure it's completely user error since I don't seem to be having this much trouble with my 4 inch Android phone.
PS. The phone is rooted with AutoNooter and using LauncherPro and Dolphin browser.
Click to expand...
Click to collapse
My screen is very smooth, and a little bit tacky... I'd prefer a less tacky, smoother feel, but it's okay.
Unresponsive I've not noticed really, but the calibration on the edges and/or corners is funky.. Like hitting the Search button in the market is hit and miss, otherwise other places I personally haven't seen any issues.
There's a thread on here / directions on nookdevs for how to recalibrate the screen. A lot of people have been reporting issues with the calibration on the edge of the screen. It doesn't bother me too much, so I haven't tried, but results are apparently quite good.
http://www.nookdevs.com/Recalibrate_the_NookColor_touch_screen
I've recalibrated the screen a few times. Even did the suggestion with placing the Nook face down for extreme sensitivity.
I still seem to be having the same problem where the touch is very unresponsive. It's most noticable browsing the web, I'll have to tap links multiple times before the browser does anything.
I'm wondering if I have a bad Nook or is this just how it is?
It could be the default browser. I had problems with unresponsive tapping as well but after switching to Dolphin Browser HD I havent really noticed them at all. However, it does seems like only certain apps or portions of them have problems with touch response...I can think of 2 off the top of my head..
1) The search icon in the Android Market. I have to really tap it hard or multiple times for it to open the search ability. Everything else in the market is a light, smooth, responsive tap, except the search ability.
2) ADW's settings menu, specifically the back button. Have to really hit it hard to work yet everything else works perfectly fine.
Maybe it's just me but I swear its only certain things which respond poorly to taps.
In regards to the screen being tacky, goto B&N and buy the Anti-Glare protective screen film. Make sure its the anti-glare one and not the regular screen protector. Not only will your fingers slide perfectly, but it also avoids all the annoying fingerprints the default glass seems to collect. Worth every penny. (You get 2 of them for 15 bucks)
I find that I have better luck ith a light touch & avoid a "tap". It took a bit of practice to know what part of my finger was actually making contact with the screen first & the reason for the perception that the screen was out of calibration.
I do have a problem with the center right area of the screen when playing crossword. Sometimes it is very hard to click on the rufgt side boxes. Interestingly, the same area of the screen is responsive in other apps.
Cheers,
kev
heers,
kev
I purchased the matte screen protector from them and it alleviated the tacky feel of the screen. Also resist oils and smudges so its a must have in my opinion.
Ravynmagi said:
I've recalibrated the screen a few times. Even did the suggestion with placing the Nook face down for extreme sensitivity.
I still seem to be having the same problem where the touch is very unresponsive. It's most noticable browsing the web, I'll have to tap links multiple times before the browser does anything.
I'm wondering if I have a bad Nook or is this just how it is?
Click to expand...
Click to collapse
I have the same problem at the very top edges of the screen. Pressing search in marketplace or a new tab in dolphin is really annoying. Requires many taps to work. Rest of screen seems to work fine. I did notice that the 2.2 Froyo was way worse for screen sensitivity. Maybe they can fix somehow with a firmware patch or something.
I have the same problem. Will try recalibrating later.
Tapiozona said:
It could be the default browser. I had problems with unresponsive tapping as well but after switching to Dolphin Browser HD I havent really noticed them at all. However, it does seems like only certain apps or portions of them have problems with touch response...I can think of 2 off the top of my head..
1) The search icon in the Android Market. I have to really tap it hard or multiple times for it to open the search ability. Everything else in the market is a light, smooth, responsive tap, except the search ability.
2) ADW's settings menu, specifically the back button. Have to really hit it hard to work yet everything else works perfectly fine.
Maybe it's just me but I swear its only certain things which respond poorly to taps.
In regards to the screen being tacky, goto B&N and buy the Anti-Glare protective screen film. Make sure its the anti-glare one and not the regular screen protector. Not only will your fingers slide perfectly, but it also avoids all the annoying fingerprints the default glass seems to collect. Worth every penny. (You get 2 of them for 15 bucks)
Click to expand...
Click to collapse
I don't think the market search button issue is a screen calibration issue. I initially thought there was an issue with the sensitivity/calibration in the top corner of the screen, but I have the same problem with market search when I am in portrait or landscape. Touching items in the same area of the screen in other apps is fine.
My screen is definitely more responsive after doing the commands.
I made sure to clean it completely with a microfiber cloth before running the commands.
As for the market search issue, it seems to have improved the sensitivity. In fact, to me it now feels as if I am getting the button push through, but it just takes time for the app to register it and take action (lag) and thus we think the button push did not go through and push it again...
my 2ยข
A lot of the discussion on this thread is for locale based calibration, but I had the issue where if you hold still on a drag and drop, before dropping the thing you are holding is jittery, as thugh your finger was being jittery. This calibration fixed that problem.
Under the thought that this might happen again, would be nice if there was a way to run the command locally on the system without having to connect to adb to recalibrate.
Any ideas on how that could be done? I was thinking maybe scripted terminal commands?
Had my S5 since launch day so I'm pretty comfortable with the overall feel and navigation of the device (came from a Note 3, miss the size but I'll get over it)...however, I do have some issues with the phone and if you know any trick to eliminate these issues or if you at least know what causes these issues, please let me know..these issues taint an otherwise great experience compared to my S4 last year.
1. Serious lag when pressing power button, home button, or opening up S-View cover to wake screen...literally takes 4-6 seconds to come on
2. When streaming a video, phone randomly turns screen off, meaning I have to press that power button again, confirm my fingerprint again, and press play...again...
3. Lock screen and S-View weather doesn't update if you don't have the Accuweather widget on your homescreen
4. Is it just me, or is the word recognition of the Samsung keyboard when using swype motions worse than its ever been?
5. recent apps takes about 2 seconds to come up after pressing the button
Other than that, I'm pleasantly surprised at battery life, never had wifi speeds like this before, screen looks great, S-View cover is still the sh*t, my fingerprint scanner works flawlessly, camera is really impressive, navigation has virtually no lag at all, and thank you Samsung for Private Mode...no more garbage Gallery Lock applications...
Sounds like you've got a bad device, I've got no lag at all, including when opening the s-view case. Might want to switch it out for another while you can.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
1. Serious lag when pressing power button, home button, or opening up S-View cover to wake screen...literally takes 4-6 seconds to come on
no lag at all here, smooth and fast, pry the first time I've ever used a stock Android device that's this smooth and fast out of the box.
edit: not sure of s-view cover as I don't use it, I use a Khomo Slim on my Tab3 8.0 and it's pretty quick waking up, just checked and it's like a second or so to wake up.
2. When streaming a video, phone randomly turns screen off, meaning I have to press that power button again, confirm my fingerprint again, and press play...again...
no issues here either
3. Lock screen and S-View weather doesn't update if you don't have the Accuweather widget on your homescreen
not sure as I'm using GoLauncher Prime and loose the Sammy widget, trying to find another good one as I have Beautiful Widgets Pro from before but haven't installed after seeing all the complaints about it now on newer devices
4. Is it just me, or is the word recognition of the Samsung keyboard when using swype motions worse than its ever been?
no problem here either, was fine for me on stock keyboard, switched to swiftkey though since I own it
5. recent apps takes about 2 seconds to come up after pressing the button
again no issue here, pretty much instant for me
composi said:
1. Serious lag when pressing power button, home button, or opening up S-View cover to wake screen...literally takes 4-6 seconds to come on
Click to expand...
Click to collapse
my lag is maybe 1-1.5 seconds, JUST on the border of being okay and annoyed. so it's okay for now
chillsen said:
my lag is maybe 1-1.5 seconds, JUST on the border of being okay and annoyed. so it's okay for now
Click to expand...
Click to collapse
Ah, the patented power button and home button lag. I remember them well from my Note 3. Samsung fanboys will try to tell you that it doesn't happen, but they are in denial. The Note 3 was the fastest Samsung device I have owned and it still did it. And the power button lag drove me mad.
Only issue i seemed to be having is that the display doesn't seem to be flush so I'm collecting dust on the top already.
Sent from my SAMSUNG-SM-G900A using Tapatalk
No lag here and certainly no 2 second delay for recent apps. But then again, I'm sure it's just because I'm a Samsung fanboy who's in denial.
karmuh said:
No lag here and certainly no 2 second delay for recent apps. But then again, I'm sure it's just because I'm a Samsung fanboy who's in denial.
Click to expand...
Click to collapse
Every time there's some kind of reported lag/delay for a device, there are always a handful of people with the device (thus invested in it and in need of validation for their purchase) who insist that the lag doesn't exist, even when every single review and blog site confirms it.
I wouldn't say that the multitasking lag is 2 seconds, but it's definitely there. It was mentioned in a few professional reviews and I confirmed it myself on a display unit. It's not a horrendous delay, but it's definitely not as instantaneous as it is on other phones. It may be that it's waiting to confirm that the button isn't being held for the secondary function (menu), which is the perils of using one button for multiple functions.
On my Note 3, sometimes the power button would work as expected and other times, you'd push it and it would be a full 2-3 seconds before the device would turn on/off. Even after I disabled every single service I didn't need/want, it persisted. I would love to think that Samsung eliminated all of these little delays, but the reality is that they need to rewrite Touchwiz from the ground up and optimize it.
greyhulk said:
Ah, the patented power button and home button lag. I remember them well from my Note 3. Samsung fanboys will try to tell you that it doesn't happen, but they are in denial. The Note 3 was the fastest Samsung device I have owned and it still did it. And the power button lag drove me mad.
Click to expand...
Click to collapse
Fanboy my a$$, also have an iPhone 5 and 5S. I have no lag with multi or home, maybe a split fraction of a second just like my iPhone (just as responsive as them) , guess I'll have to get a vid to prove it
If the split second is considered lag, then our iPhone 4S/5/5S are laggy too
I'm not saying the phone is garbage, just that it'd be nice for this phone to be close to the M8 in terms of reaction...anyone who has messed with an M8 will tell u that the moment you press something it comes up, zero lag, zero waiting for extra input.
However, I'll sacrifice that for imo a better overall phone.
Sent from my SAMSUNG-SM-G900A using xda app-developers app
1. Serious lag when pressing power button, home button, or opening up S-View cover to wake screen...literally takes 4-6 seconds to come on
No real lag for me. 1/2 a second or so it seems.
2. When streaming a video, phone randomly turns screen off, meaning I have to press that power button again, confirm my fingerprint again, and press play...again...
Haven't seen this issue on mine at all
3. Lock screen and S-View weather doesn't update if you don't have the Accuweather widget on your homescreen
This drives me nuts! I thought it was just me!
4. Is it just me, or is the word recognition of the Samsung keyboard when using swype motions worse than its ever been?
Works good for me. I so far haven't felt the need to go back to swiftkey which has been my go-to for nearly 2 years
5. recent apps takes about 2 seconds to come up after pressing the button
Takes about the same amount of time it takes the screen to power up from hitting the power button. 1/2 second or so.
I think I'd be visiting a store ASAP if your phone is having these lag issues. Have read a few reports about this but I haven't really seen it on my device so far.
Has anyone experienced app crashes lately? My phone has been working great for days now, then today it seems like every app in open crashes and stops responding. It will lock up my phone and won't stop until reset.
Sent from my SAMSUNG-SM-G900A using xda app-developers app
I have a quick gripe, I could be missing something though.
There is no real indication that I see if I am on wifi or not.
It still says 4g and the status bar doesn't seem to change unless I am missing something.
PunchLick said:
I have a quick gripe, I could be missing something though.
There is no real indication that I see if I am on wifi or not.
It still says 4g and the status bar doesn't seem to change unless I am missing something.
Click to expand...
Click to collapse
The wifi signal icon shows you are on wifi....
Oh then something is wrong with my phone or there is a setting that needs to be adjusted,
I do not see the wifi symbol anywhere
Turning wifi on and connecting it is the only thing you should have to do.
I can confirm multitasking and wake up lag.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Finally it works, I dont know if it helped, but I cleared cache, restarted and forgot and reconnected to wifi and now icon is back.
I honestly have no lag what so ever on practically anything. I am using Nova Launcher though if that changes anything. Swype is ****ty though, I just want root...
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Br4nd3n said:
I honestly have no lag what so ever on practically anything. I am using Nova Launcher though if that changes anything. Swype is ****ty though, I just want root...
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The only lag i experience is through Samsung apps and multitasking button. I'm guessing it's because it is waiting for a hold. Just like if you disable s voice on home key your back to home response time is much faster.
Sent from my SAMSUNG-SM-G900A using Tapatalk
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
Hi guys!
A few months ago I tried Pixel 6 as a replacement for my ageing OnePlus 5 and in the end had to return it because it was sometimes missing screen taps. Now I have Pixel 7 and guess what? The same thing. It is the most prominent when I want to wake the phone up with a tap (Google changed from double-tap, gods know why) and it often fails. I've tried double-tap, tripple-tap, turning off/on various settings, restarting, updating... The same stuff. There seems to be a lot of talk about it on reddit. The same works flawlessly on my Pixel 5 (and also many other things which are failing on Pixel 7).
Going through discussions it seems this plagues Pixel phones for some time and it seems to be some hardware issue.
Have you encountered the same issue?
Biges said:
Hi guys!
A few months ago I tried Pixel 6 as a replacement for my ageing OnePlus 5 and in the end had to return it because it was sometimes missing screen taps. Now I have Pixel 7 and guess what? The same thing. It is the most prominent when I want to wake the phone up with a tap (Google changed from double-tap, gods know why) and it often fails. I've tried double-tap, tripple-tap, turning off/on various settings, restarting, updating... The same stuff. There seems to be a lot of talk about it on reddit. The same works flawlessly on my Pixel 5 (and also many other things which are failing on Pixel 7).
Going through discussions it seems this plagues Pixel phones for some time and it seems to be some hardware issue.
Have you encountered the same issue?
Click to expand...
Click to collapse
My works flawlessly single tap, double tap, doesn't matter but I use nova launcher and Iam rooted
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
hammered58 said:
My works flawlessly single tap, double tap, doesn't matter but I use nova launcher and Iam rooted
Click to expand...
Click to collapse
Nova Launcher, my favourite app!
Seems like some shortcomings of Pixel 7 can be solved using the root access, however it seems crazy I need to root the phone to get the same functions as on a Samsung or a OnePlus phone :-/
bobbyphoenix said:
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
Click to expand...
Click to collapse
Yes, it is as you describe. But don't hope too much, this behavior about missing already animated taps had been reported for Pixel 6 by many people, but Google seems to ignore it or what, they just don't give a care?
I encountered this issue in the beginning. Try the following and see if it solves your phone being unresponsive to tapping to unlock the device. Go to: Settings>Display>Lock screen and turn off Lift to check phone, turn on Tap to check phone.
bobbyphoenix said:
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
Click to expand...
Click to collapse
Hey, same here sometimes. I got a pretty good but cheap tempered glass screen protector with which FP works 8/10 plus using face unlock. Better touch input option with protector is enabled in settings.
The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap ...
Click to expand...
Click to collapse
Exactly this happens more often and I had that on my Pixel 6 too which I replaced with a Realme GT2 Pro (no problems with the Realme) but on Pixel 7 now again. Still using three buttons navigation bar, and often the taps don't work there too.
LOL f* Google, can't they get their stuff fixed? I mean the company which codes the OS sucks regarding their flagships more than other OEMs which only adapt the OS. Jesus f* christ.