Database Develop

[Q] It Anyone Else Having Touch Button Problems?

Is anyone else experiencing the occasional mixup when hitting the back button? As not always, but many times regardless of the application thats open, I'll hit the back button and the search will come up and I wondering whether thats a common problem or a sensor in my phone is defective and I need to exchange it for a new one...
Thanks in advance

im having a different problem with the buttons. a lot of times my first touch wont register and i have to press it multiple times for it to be recognized.

I've noticed that my touch buttons aren't as sensitive as the touchscreen, and that I need to use a lot of pressure to get them to activate on the first try.

not alone there.. same issue here. I have a clear screen protector over them though.. though it shouldn't be a problem.. I've had the issue even before the protector so..

I have a problem with the back button too, not the other ones. However, when I press a spot a little to the left of the back button and not exactly over the button, it seems to register the press correctly.

I have found that the buttons just do not like any other finger than the index finger try to use the thumb and it will go to search or do nothing.I also returned my first phone as the buttons were terrible 80 percent of the time they would not work.So there maybe be a flaw in some of the phones as this one works fine even with the phantom skins on.The first phone would not even register a response with the skin on.

The buttons on the Captivate suck.
Buttons, as a construct, are well known.
The functional priority of the button is not a mystery and hasn't been for 100 years.
It has to click or otherwise give the user an indication the button has been pressed far enough to take effect.
It has to be tacticle. You have to have some way of knowing that your finger is on the button before you press it.
You have to have some leverage to put enough force on the button to make it move.
It has to be about the size of a finger tip.
It has to be visible. If you can't see it you can't press it.
It has to be different than other buttons that are millimeters from it.
It has to react the first time you press it, or you will naturally press it again, achieving unwanted results.
In all of the above, the Captivate fails.
The T-Mobile Galaxy has more a lot more real estate below the buttons to allow your fingers to get on to them, and a raised ridge on the rear surface of the phone exactly to give your other fingers something to grip against to increase aim and pressure.
But the Captivate has a nice lot of space at the top OH YEAH!

The only problem I have with the buttons is that I can't see them in a dark room
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm getting something similar. Sometimes when I hit the home button the search button blinks as if I had pressed it, then brings up the search screen. On my first captivate (mfg. date 7/16) sometimes it would happen once out of every hundred presses and sometimes it would happen 3 out of 5, very inconsistent. I traded that one in for one with a later manufacturing date (8/10), and my new one does it too but maybe only 1 out of every 100-200 presses. The fact that the search button blinks makes me think it's some kind of short/hardware issue. The back button has only triggered a search for me once, and that was on my first phone.

So this is a hardware issue or a software issue?
My back button on my phone must be pressed 4-5 times sometimes before it will register. The phone did not have the issue when I got it, and a friend of mine who has the Captivate as well does not have this issue.
It may be my imagination, but the phone seems to register touches better after I run a task killer or after restarting the phone, but tends to have issues when multiple apps are up and running.

I was having a button problem as well but fixed it by upgrading to JH3. h t t p://forum.xda-developers.com/showthread.php?t=767666
Your mileage may vary but it worked for me.

May be my imagination, but it seemed to be more isolated to back button on JH3 than JF6 on my machine. My perception is that if I take an additional half-second pause before pushing back button it registers more often. Do not believe it is hardware though. I believe that your home page(button), settings (button), and search(button) all reference something that resides in permanent memory(ROM) whereas the back(button) is trying to recall something that is in temporary memory (RAM) and possibly similar to lag issues may be related to Samsungs somewhat proprietary file allocation system. I am by no means computer literate enough to ponder concept any deeper than just mentioned.

I was having a problem with pushing the home button and the search would come up. I took it to a AT&T store and because I was still in the first 30 days they swapped it out for me.

i'm having a completely different issue with my touch buttons. my back button will register multiple button presses even when i'm nowhere near it. it's quite frustrating to be in the middle of an app and all of a sudden the back button goes off 3 or 4 times and gets you back to the home screen. i've tried searching the forums for some resolution or to see if someone else has had this, but not yet.
Edit: I must not have searched thoroughly enough, found another thread on this issue. http://forum.xda-developers.com/showthread.php?t=858873&highlight=back+button+issue&page=2

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

Screen issues

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?

Super sensitive screen...

So far I'm diggin the HD, coming from the RAZR it's pretty similar. I'm a tiny bit annoyed by the sensitivity on screen, though... When trying to scroll, it keeps selecting instead of starting my scroll. In Play, when scrolling through my apps it selects when I'm trying to scroll. That's only annoying because Play doesn't keep your progress when scrolling through your list of apps (and mine is a LONG one). Even here in XDA, it keeps trying to thank or quote people I don't want to thank or quote... Lol.
Hopefully an update will come to fix it, or we'll get root and roms soon!
I took the red pill... It's the mAtrix for me...
http://android-gz.com

I sometimes have this issue as well. Sometimes even keyboard gets stuck and over types. Both swift and stock.
Sent from my MB886 using xda premium

Well i kinda have similar problem but not with screen sensitivity but with keyboard!! Sometimes i kinda fell i press wrong key more often than i would like!!! Dont knw if its problem with me or onscreen keyboard!!
Sent from my MB886 using xda premium

The screen seems a little INsensitive, so when I swipe my finger lightly it doesn't register as movement and thinks I tapped instead. Other times, I tap something and it doesn't register until I press harder.

I have a pretty thick screen protector. It seemed to have helped with the screen sensitivity issue.
It like to think you are taping instead of pressing and swiping. It tries to register the swipe as a finger lift for some reason.
anyways, I'm fine with my screen, and as I've said the thick screen protector kinda helps.

Button-less Wake!

The main defect with the Note 3 is that it requires a button-press to wake-up.
Let this thread be a collective bounty of alternative solutions until we can Slide2Wake which requires kernal changes and AT&T to unlock the bootloader.
Sign this petition in the meantime while you read on:
http://www.change.org/petitions/at-t-unlock-our-samsung-galaxy-note-3-bootloader
Working solutions:
-Use a proximity sensor app (very hit and miss) (https://play.google.com/store/apps/details?id=com.omd.autoscreenon&hl=en)
-Use the S View cover (also hit and miss and unpreferred by many)
Any other solutions please add!

Why would you want a huge wake lock like that? A simple press of the home button is much easier IMHO. I'd rather not have to swipe across the screen to turn the screen on

RErick said:
Why would you want a huge wake lock like that? A simple press of the home button is much easier IMHO. I'd rather not have to swipe across the screen to turn the screen on
Click to expand...
Click to collapse
You're right. It's a considerable battery drain. The surprising thing is.. in the end, the smoothness of button-free operation becomes *worth it* IMHO.
I turn my phone on and off a lot to check stuff. I'll look at my to do list then press the corner SwipePad shortcut to turn it off. Then I'll remember something while moving up a bit in the line and **without even looking down for a button** and half-entranced in contemplation still I'll swipe from one side of the phone to halfway to the other and it is ON by the split second both my hands hold it to to make a note or reminder, look up something, etc. after which i'll immediately press the corner shortcut again to turn it off and my phone stays in one hand while I people-watch.
For some reason this is much more relaxed and makes me feel like the phone is like a second brain where I don't even need to create mnemonic devices called loci as much like I used to.
Maybe that's what's making my memory kind of crappy. Maybe should go back to doing that for my to-do lists. Might improve my memory. ANYWAY. my point is:
(1) it's less mechanical effort to swipe and
(2) I like to save my buttons and don't want to eventually have to replace the home button on the Note 3 for like $50 or whatever.
I guess it's not that big a deal.
If I did have that feature though I wouldn't miss anything else from past phones especially since the Note 3 is big enough to fit in one hand BARELY and could do a HALF-swipe to wake feature.
**pretends to do it now**
I'm crazy.

I would like a solution to this as well. Tried the light sensor app but that wasnt working well. Really wish we had tap-on.
I really like not hitting any physical buttons because this phone is huge and unwieldy. Still love it though.

https://play.google.com/store/apps/details?id=com.spazedog.xposed.additionsgb
I assigned the power button to holding down the back button. That saves a little bit of button-life.
The app also is designed to support the same while the screen is off... but it doesn't seem to work yet.
Would be super awesome though to be able to turn the screen off and on while the back button is held. Just not there yet.
Screen on with swipe is the next best.. though much more battery intensive.

Has anyone just simply tried pressing the simple wake button on the side of the phone once? I mean you already have your hand on it most of the time since it is where your fingers are if you are holding the phone in one hand.
Also for you slider guys, it takes many more muscles to frown and it is the same to slide. Much better to smile and press one single button already under your thumb when you are holding the phone.

Solarenemy68 said:
Has anyone just simply tried pressing the simple wake button on the side of the phone once? I mean you already have your hand on it most of the time since it is where your fingers are if you are holding the phone in one hand.
Also for you slider guys, it takes many more muscles to frown and it is the same to slide. Much better to smile and press one single button already under your thumb when you are holding the phone.
Click to expand...
Click to collapse
Congratulations Captain Obvious. You are the first person to ever think of that!
/\/\ sarcasm /\ /\
Read above about my experience with button-less waking in the SGS2.
Besides that, you're wrong, my thumb is actually closer to the screen than the power button when I am holding it.
And it's no effort at all. That's the whole point. It's the same slide necessary in receiving a call. No physical PUSHING required.
I can turn my phone on twice per second easily by linking one of the touch buttons to "power" as well. With zero concern for screwing up any physical buttons.
Anyway please only write in this thread if you have something that will contribute to the idea of "button-less wake"
I'm only looking for creating solutions to that.

megamorphg said:
I can turn my phone on twice per second easily by linking one of the touch buttons to "power" as well. With zero concern for screwing up any physical buttons.
Click to expand...
Click to collapse
Well it looks like you've solved your own problem right? So should this be closed? I'll answer my own question, yes
Sent from my SM-N900A using xda app-developers app

Roundtableprez said:
Well it looks like you've solved your own problem right? So should this be closed? I'll answer my own question, yes
Sent from my SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I'm talking about my SGS2 (last phone).
If Note 3 has a button-less wake feature then can close this.
I think that won't happen till ATT lifts the lock tho..

Best buttonless Wake Achieved
S View cover
P.s.: for those who prefer a different case: just wait till bootloader is unlocked > kernel unlocked > slide function can be made.
thread closed.