Recently, a few of my keys on the left side have been acting up. They still work, I just have to push them very hard. Is there anything I can do to fix this? I am betting it is because of the many time I've dropped it.
Sent from my DROID3 using xda premium
I have the same problem, epsecially with my A and alt keys. Very annoying.
Sent from my DROID3 using xda premium
I have a feeling it's just a general design fault - I'm having the same problem with the XT860. It feels very similar to the problems associated with the Milestone/Droid 2 which lacked the appropriate "debounce" functionality.
Cheers,
Steve.
StevePritchard said:
I have a feeling it's just a general design fault - I'm having the same problem with the XT860. It feels very similar to the problems associated with the Milestone/Droid 2 which lacked the appropriate "debounce" functionality.
Cheers,
Steve.
Click to expand...
Click to collapse
This. My old M2 had the same problem. Was a mix of lack of debounce driver and natural degradation of the keys
Sent from my XT860 using xda app-developers app
Well that sucks. I am always missing "a"s now. Also, I just noticed this while typing this message, certain keys are now doubling some times. I guess I'll switch to just using the on screen keyboard in preparation for my next device.
Sent from my DROID3 using xda premium
slayer621 said:
Well that sucks. I am always missing "a"s now. Also, I just noticed this while typing this message, certain keys are now doubling some times. I guess I'll switch to just using the on screen keyboard in preparation for my next device.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
That's what I've been doing. I never touch the hard keyboard. Try swiftkey keyboard. It learns from your typing, once you've been using it for awhile it gets quite accurate for prediction
Sent from my XT860 using xda premium
Hello!
I have the same problem.
I have a lot of keys with the same problem, i want to fix it in a motorola representant.
i can´t fix it ?
That´s a shame.
Calen77 said:
Hello!
I have the same problem.
I have a lot of keys with the same problem, i want to fix it in a motorola representant.
i can´t fix it ?
That´s a shame.
Click to expand...
Click to collapse
Yes you can. The double letters can be fixed with a debounce driver, folks interested in porting it to the M3/D3 check out M2 android dev forum, there is a thread about it. Or you can ask Motorola to change your keyboard.
I'm another in favor of SwiftKey. It's just great. It also works for the hw keyboard, if anyone is interested
Sent from my XT860 using xda app-developers app
Whhhow!
I will look in D2 forum.
Eu só não mandei para uma autorizada no Brasil pois estava pensando que iriam ficar uns 3 meses com meu celular por lá...
Valeu, um abraço gaucho para ti !!!
Ya I was having big problems with the left side of the spacebar but I just pressed it hard and a lot and I think I fixed it. I was having trouble with Alt, but then I found out I wasn't holding it down when I wanted say a "?". I'm not sure if that's what's supposed to happen but it works for me now
Possible solution?
FWIW (and I realise it's early days) but I swamped my keyboard in lubricating switch cleaner a few hours ago, and now I've managed to type this message without any keyboard anomolies at all.
Perhaps the "degrading" is due to a build up of crud under the keys?
If the keyboard continues to work like this, then I'm a happy chap, even if my phone does smell a bit at the moment. ;-)
Obviously, I can only advise you to do this at your own risk. If people are interested in the exact stuff I used, then let me know, and I'll dig it out when I get home later.
Cheers,
Steve
Calen77 said:
Whhhow!
I will look in D2 forum.
Eu só não mandei para uma autorizada no Brasil pois estava pensando que iriam ficar uns 3 meses com meu celular por lá...
Valeu, um abraço gaucho para ti !!!
Click to expand...
Click to collapse
Check M2 forum. It's on legacy devices section.
Also, if you send the phone to warranty and they take more than a month to fix your problem, you can ask for a new unit. It's written on the consumer rights.
StevePritchard said:
FWIW (and I realise it's early days) but I swamped my keyboard in lubricating switch cleaner a few hours ago, and now I've managed to type this message without any keyboard anomolies at all.
Perhaps the "degrading" is due to a build up of crud under the keys?
If the keyboard continues to work like this, then I'm a happy chap, even if my phone does smell a bit at the moment. ;-)
Obviously, I can only advise you to do this at your own risk. If people are interested in the exact stuff I used, then let me know, and I'll dig it out when I get home later.
Cheers,
Steve
Click to expand...
Click to collapse
Wow, lubricant. I never thought of it. What kind, brand, how did you do that, yadda yadda yadda you know the drill =p
Edit: here is the M2 topic about debouncing module. Might give it a try.
http://forum.xda-developers.com/showthread.php?t=1058544
And here some dev porn: http://forum.xda-developers.com/showthread.php?p=13927675
Sent from my XT860 using xda app-developers app
I've tried the MS2 debounce app, and it wouldn't load the module for me. :-(
The way I cleaned my keyboard was to spray it with Servisol Super 10 Switch Cleaning Lubricant. I sprayed enough so that the keyboard was totally flooded with liquid, and then tried to work it into the underside of the keys through pressing, rubbing, and spraying (lightly) with an air duster can. I repeated this 3 or 4 times, and then wiped off the residue with a cloth. I haven't seen any repeat behaviour of the sticking or non-responsive keys since I did that - how long it will last, of course, I've no idea, but I would definitely class it as "fixed" for now.
Cheers,
Steve
It happened to me with the spacebar
I managed to fix it by pressing it a few times in different spots
StevePritchard said:
I've tried the MS2 debounce app, and it wouldn't load the module for me. :-(
The way I cleaned my keyboard was to spray it with Servisol Super 10 Switch Cleaning Lubricant. I sprayed enough so that the keyboard was totally flooded with liquid, and then tried to work it into the underside of the keys through pressing, rubbing, and spraying (lightly) with an air duster can. I repeated this 3 or 4 times, and then wiped off the residue with a cloth. I haven't seen any repeat behaviour of the sticking or non-responsive keys since I did that - how long it will last, of course, I've no idea, but I would definitely class it as "fixed" for now.
Cheers,
Steve
Click to expand...
Click to collapse
It has to be ported to the D3, if I'm not wrong it uses/edit some build.prop lines
Sent from my XT860 using xda app-developers app
My gf's daughter had the same issue. Brought it in to bell and they fixed it somehow under warranty. Im having issues with space bar so I may do the same
Sent from my XT860 using xda premium
As an update, I've found that the "fix" of cleaning the keyboard would only last a week or so. I've also found that trying to get behind the keys with fluid is a waste of time (the keys are simply stuck on to a membrane). This means that either the fluid is a red herring, or perhaps the fluid needs to go behind the membrane down the outside edge of the keyboard. Maybe it's the rubbing that improved things?
There's defintely an improvement after the physical act of cleaning, but I still wonder whether there's a software debounce fix that could be more effective.
Cheers,
Steve
Hardware Keys skipping/doubling fix
StevePritchard said:
As an update, I've found that the "fix" of cleaning the keyboard would only last a week or so. I've also found that trying to get behind the keys with fluid is a waste of time (the keys are simply stuck on to a membrane). This means that either the fluid is a red herring, or perhaps the fluid needs to go behind the membrane down the outside edge of the keyboard. Maybe it's the rubbing that improved things?
There's defintely an improvement after the physical act of cleaning, but I still wonder whether there's a software debounce fix that could be more effective.
Cheers,
Steve
Click to expand...
Click to collapse
A bit more info for anybody that's interested...
I've found that CAREFULLY lifting the edge of the keyboard (in the corners next to the ALT and right cursor keys) with a toothpick, and then spraying the switch cleaner into the exposed area under the edge, and then rubbing the keyboard seems to be a much more effective way of getting a longer lasting, and more comprehensive fix. I think lifting the edge of the keyboard actually exposes the microswitches under the membrane, and so it's those that are being targeted when we spray the cleaner in there.
The edges of the keyboard go back down no problem, so there's no visible indication that they've ever been lifted. Obviously, quite a bit of care has to be taken not to over do it - I suspect that permanent damage could occur if too much force is used, or if they are lifted too high.
The difference between the keyboard before/after the cleaning is like night and day, and I'm now enjoying my phone again. Please be aware that I can't be held responsible for any damage caused if you do choose to undertake this fix.
Cheers,
Steve.
thanks!
StevePritchard said:
A bit more info for anybody that's interested...
I've found that CAREFULLY lifting the edge of the keyboard (in the corners next to the ALT and right cursor keys) with a toothpick, and then spraying the switch cleaner into the exposed area under the edge, and then rubbing the keyboard seems to be a much more effective way of getting a longer lasting, and more comprehensive fix. I think lifting the edge of the keyboard actually exposes the microswitches under the membrane, and so it's those that are being targeted when we spray the cleaner in there.
The edges of the keyboard go back down no problem, so there's no visible indication that they've ever been lifted. Obviously, quite a bit of care has to be taken not to over do it - I suspect that permanent damage could occur if too much force is used, or if they are lifted too high.
The difference between the keyboard before/after the cleaning is like night and day, and I'm now enjoying my phone again. Please be aware that I can't be held responsible for any damage caused if you do choose to undertake this fix.
Cheers,
Steve.
Click to expand...
Click to collapse
You are my hero <3
Can you take a video to demonstrate?
Related
Ok.. So I searched a while, and I'm not sure if I was just using the wrong terms, but I couldn't get a result that answered my question.
Anywho.. I'm using Fresh Toast 2.0b2, and I'm having an odd problem when playing games that have touch input.
For example... Whilst playing the game "Radiant" The phone slows down considerably when I use the touch screen to move my ship.. I would say framerates cut almost in half.. but clear up as soon as I lift my thumb from the screen..
Same thing happens in the game "Blow Up" When I tap-hold the bottom of the screen to pick up the bombs to drag to the beams, the phone slows WAAAYY down, but clears up the moment I drop the bomb/lift my finger from the screen..
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
jUgGsY said:
Ok.. So I searched a while, and I'm not sure if I was just using the wrong terms, but I couldn't get a result that answered my question.
Anywho.. I'm using Fresh Toast 2.0b2, and I'm having an odd problem when playing games that have touch input.
For example... Whilst playing the game "Radiant" The phone slows down considerably when I use the touch screen to move my ship.. I would say framerates cut almost in half.. but clear up as soon as I lift my thumb from the screen..
Same thing happens in the game "Blow Up" When I tap-hold the bottom of the screen to pick up the bombs to drag to the beams, the phone slows WAAAYY down, but clears up the moment I drop the bomb/lift my finger from the screen..
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
Click to expand...
Click to collapse
FreshToast is buggy right now - hence the DEV rom titleing.
I also have noticed general touch bugyness. Especially slow responses to touch.
Kcarpenter said:
FreshToast is buggy right now - hence the DEV rom titleing.
I also have noticed general touch bugyness. Especially slow responses to touch.
Click to expand...
Click to collapse
So should it be considered an actual BUG for FT?
jUgGsY said:
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
Click to expand...
Click to collapse
Not a ROM problem, Not specific to your device. I feel like its a problem with HTC's multitouch drivers.. Ive noticed the same problem since I got the phone in October. I'm pretty certain when you touch the phone, the Hero is looking for another touch point so it delays the phone.. The HTC Hero doesn't use the same multitouch drivers as other 2.1 devices even on the 2.1 ROMs, Thats why most multitouch programs on the market dont work right for the Hero, and also why I'm jumping to EVO, Hopefully HTC EVO doesn't have the same problem.
mental26 said:
Not a ROM problem, Not specific to your device. I feel like its a problem with HTC's multitouch drivers.. Ive noticed the same problem since I got the phone in October. I'm pretty certain when you touch the phone, the Hero is looking for another touch point so it delays the phone.. The HTC Hero doesn't use the same multitouch drivers as other 2.1 devices even on the 2.1 ROMs, Thats why most multitouch programs on the market dont work right for the Hero, and also why I'm jumping to EVO, Hopefully HTC EVO doesn't have the same problem.
Click to expand...
Click to collapse
That definitely makes sense. Wish I would've known about the EVO previous to my purchase of the Hero..
So I did 2 neocores. One without touching the screen got me 25 dos. Then I touched the screen thru the whole benchmark and got 4.9 dos. Wow that's a big difference!
-------------------------------------
Sent via the XDA Tapatalk App
Kcarpenter said:
So I did 2 neocores. One without touching the screen got me 25 dos. Then I touched the screen thru the whole benchmark and got 4.9 dos. Wow that's a big difference!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
That should be seen as a deal breaking bug for the Hero.. We should all go to Sprint and DEMAND EVOs.
Unless its not present in the official 2.1, I'm going to do what I can to get an EVO.
yeh its really weird how it works right. .27 and touch input didnt play well. at all. the biggest problem is the sh*t digitizer we have. it only senses x OR y moving AWAY OR TOWARDS eachother. it isnt true multtouch. a good example is to download multitouch paint from the demo market. it will read both fingers fine until one crosses the x or y axis in opposite directions.
but anyways back to when you touch, i think toasts source is amazing for the .29 but once htc releases the real .29 source he will really work his magic. .29 fixed alottt of the issues with stuff like music and touch having their own "processes". in .27 they were all bunched together and that made ultra lags while using bt and messing with phone.
This is fixed in Fresh Toast 2.1Final.
I love those two guys.
Hey guys!
I thought you might be interested in the tutorial I made about the rocket science of "how to replace this frakkin' ****ed up keyboard"...
Haven't found any useful instructions on the web so I just made a tutorial myself. I hope it will help someone in desperate need of a new piece of typing plastic.
Yeah the keyboard is not that durable for "holycrapIcan'tbelievehowmuchI'mtyping"-typers.
Enjoy!
http://www.stilbruch.at/2011/03/how-to-replacerepair-hardware-keyboard.html
Cheers
+1 for your effort and writing up a guide
good write up. but with the two different lay outs on the keys, how does the phone know what buttons are being pressed? i.e. where the d-pad is??
thanks, now i can type so much faster. and to the person with the question. the keyboard has 3 layers
the breadboard which contains 2 terminals per key,
the cap which is metal and gets pressed against the terminal, registering a letter
and the cover where there are 2 styles, one flat and the old version which was bubbled
the tutorial covers replacing the cover
the pink part contains the caps(which i tore off accidently, good thing i had an extra)
Nice tutorial. Thanks!
Beautiful guide! Love the humor in it as well.
Thanks guys, I'm glad you all like it hopefully I'll write a few other tutorials in the near future for the milestone and the Galaxy Tab.. if I break them
Yeah and watch out for the pink thingy... also ripped it nearly out ^^
Sent from my GT-P1000 using XDA Premium App
Did anyone fix the key repetition problem in Motorola Milestone/Droid?
lumiden said:
Did anyone fix the key repetition problem in Motorola Milestone/Droid?
Click to expand...
Click to collapse
Try it without the rubber-keypad... just boot it and press the keys on the pink luminative-foil... If the reason was the old keypad, you should already see the difference, before installing the new replacement-pad
I would be happy to do it. Sadly, I'm from Argentina, so this part takes a month to arrive and it costs more. I was expecting someone with the same problem and more access to the spare parts would try it before I order one.
Thank you for this guide. I've done it a few days ago and now my Milestone works great again.
Thanks for the tutorial man. Been debating doing this for a long while and now I'm sure it's relatively simple I'm just looking forward to my new flat keys!
Like you, I was disappointed not to be able to find a UK QWERTY keyboard (with a £ symbol), but I don't really give much of a crap about that to be honest.
Thanks again.
my keyboard after 1.5 years of usage showing same wear and tear as yours.
is the flat-type keyboard better to type on than the bubble one? I've read that the bubble version is bettery many times before. How do you type on the keyboard?
Thanks
hey Buddy thanx for the guide. Changed my keypad n i just cant stop texting
Wow this looks great! I want to try it Thanks!
Is it much better? Just got a milestone and know what you mean about the "sucky" sound. How does the new keyboard compare, is it worth swapping over even if the old one works?
please guys do some review
Nice tutorial. Thanks!
Nice tut, I can't see how you guys are having so many issues with ur keyboards though.. I use my constantly and theres no wear or tear in mine at all looks and still functions like the day I got it... I prolly send over 500 texts a day..
how long do you have your milestone? do you have it overheating due to overclocking?
Sometimes when I'm tapping certain icons at certain times I will have to tap twice becuase the first time it didn't recognize my tap. Sometimes even multiple times. But other times my phone will run as smooth as butter. Hardware or software issue?
Same issues ...
I have the same issues.
This issue occurs often after I unlock my Phone and also during use.
In my opinion that's not acceptable!
How did you act?
Did you send it in?
Pet hate: "Smooth as butter" ARGGHHHHHHHHHHHHH!!!!!!!!!!!!
And relax.
Yes, sometimes it doesn't recognise it. Even sometimes it will actually highlight the icon, so it's recognised I've pressed, but then done nothing with the action.
I would say software issue.
cspius said:
I have the same issues.
This issue occurs often after I unlock my Phone and also during use.
In my opinion that's not acceptable!
How did you act?
Did you send it in?
Click to expand...
Click to collapse
I returned my phone because it was driving me insane.. but yes it's probably a software issue. I bought a Nexus S from google, and it's better, but sometimes it still happens on my NS, however much less often then on my O2X. But i would say just try using a different kernel or rom. CM7 still had the touchscreen issue. So that's why I kind of gave up on this phone.
Scougar said:
Pet hate: "Smooth as butter" ARGGHHHHHHHHHHHHH!!!!!!!!!!!!
And relax.
Yes, sometimes it doesn't recognise it. Even sometimes it will actually highlight the icon, so it's recognised I've pressed, but then done nothing with the action.
I would say software issue.
Click to expand...
Click to collapse
hahaha yeah sorry I don't know why I included the "smooth as butter" cliché. I didn' want to but somehow it just popped into my head. And I'm as relaxed as relaxed can get
I have noticed that o2x screen is not that sensitive. For example in "where is my water " it was difficult to draw lines as precise as on an iphone or gs2. Maybe my fingers are faulty
buluba89 said:
I have noticed that o2x screen is not that sensitive. For example in "where is my water " it was difficult to draw lines as precise as on an iphone or gs2. Maybe my fingers are faulty
Click to expand...
Click to collapse
I agree. I now have a nexus s therefore i think that Samsung>LG.
From the moment I installed RC's ics cm9 I never had touchscreen issues again. On the contrary, now I find the screen too sensitive.
nuvo84 said:
From the moment I installed RC's ics cm9 I never had touchscreen issues again. On the contrary, now I find the screen too sensitive.
Click to expand...
Click to collapse
Screen sensitivity has been fixed in the latest kangs.
Sent from my LG-P990 using xda premium
hisham027 said:
Screen sensitivity has been fixed in the latest kangs.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I know.
That's funny... I'm still running stock 2.2 on my O2X and I had no trouble triple ducking all levels in where's my water... Now I'm cutting ropes
Hi, i personally dont think this is a problem with our touch screens, i have it happen to me when unlocking the phone etc, but i think its because we try to tap an icon to quickly before we give the phone chance to fully unlock, i've noticed if i wait just a second or 2 after unlocking it doesnt happen, i think its lack of ram in the o2x, it not quite fast enough for our speedy fingers, lol.
---------- Post added at 05:06 PM ---------- Previous post was at 04:43 PM ----------
wayneace8888 said:
Hi, i personally dont think this is a problem with our touch screens, i have it happen to me when unlocking the phone etc, but i think its because we try to tap an icon to quickly before we give the phone chance to fully unlock, i've noticed if i wait just a second or 2 after unlocking it doesnt happen, i think its lack of ram in the o2x, it not quite fast enough for our speedy fingers, lol.
Click to expand...
Click to collapse
Also i forgot to mention, if i turn off all animations this also decreases the chance of this happening.
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=39892
it's pretty sad that there's only 45 votes on this issue. Here's a hint: bugs won't get fixed if people don't speak up about them. And don't think your voice exactly resonates here on XDA.
Just star it, and leave a comment. Doesn't have to be anything long winded either.
Sent from my Nexus 10 using xda premium
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Troute said:
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Click to expand...
Click to collapse
While agree it's not the end of the world, it's a complaint I see often here in kernel and ROM threads. While a lot of it is due to wonky behavior due to OC (either CPU or GPU), it's really just exacerbating an issue that is already present.
Besides, UI bugs are some of the most prevalent and immediately noticeable to more "common" end users. While functionally it's not debilitating, it's an aesthetic scar that doesn't need to be there.
Sent from my Nexus 10 using xda premium
Hmmm.. So I assume it doesn't matter that I need exactly 15 seconds everytime I get a notification to pull down the status bar, caused by flipbacks. Okay I'm like 1000% sure Google noticed it anyway, cause its on most devices, also 100% stock ones (like me) so...
Sent from my Galaxy Nexus using xda premium
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
jbdan said:
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If it would bounce back after a reboot one time, I wouldn't care, but its always there, it doesn't matter what I do, it bounces every time... So its a bit annoying.. This is the only thing which sometimes makes me want to throw the 7 at a wall...
Sent from my Galaxy Nexus using xda premium
Thanks OP, have added my star.
I had not noticed this problem but I was intrigued.
I could not duplicate the problem, but I am using Apex launcher, not the stock launcher. Does the problem occur in all launchers? Also I am not using the stock ROM.
I wonder if this problem happens with only some units, or perhaps it relates to those user's expectations. Maybe they expect their device to react more quickly than it is able to.
Far be it for me to be dismissive of people's satisfaction with their devices, but that bug-report thread has a lot of problems. It contains over-reaching claims and supposed knowledge of the problem's causes and solutions.
Again, I don't write off these people's unhappiness but I personally would not star that issue.
i too have this problem when on stock rom..now on PA beta 9 with m-kernel, the problem still exist...and it's very annoying...i even thought there was a problem with my touch screen panel and sent it to asus for repair but when i got it back, the same problem still remains..
Not starring because it does not bother me.
Life has too many other issues to worry about having to occasionally re-swipe.
Now pop-up ads in the Yahoo app could get me started...
squshy 7 said:
Come on guys, with all the members here and all the people who like to complain, it's pretty sad that there's only 45 votes on this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
I noticed this issue minutes after pulling this thing out of the box, this might not bother you people who casually use their tablets, but top those of us who have been using android since the G1 notice this. It bothers me so much that I am considering taking this junk back and using the money to get a real tablet from Samsung.
This issue is so annoying to me, I not only notice it on the stock launcher, but also Nova and Apex. Now, the launcher I can deal with, but where I becomes a deal breaker for me is the browser, whether it's chrome or the stock browser in CM10. Trying to scroll around the OS that requires some flicking reminds me of trying to flick scroll on a resistive touch screen, I think that best describes the issue.
I just wanna know if it's fixable through a software update or a hardware problem, cause if it's the latter, this thing is going back, and that's too bad because it was a Santa gift, so I'll have some explaining to do.......
compact_bijou said:
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
Click to expand...
Click to collapse
As I stated (not in precise terms sorry) in the OP, it would be a mistake to think that xda threads are the first place companies like Google and Asus check to see what issues people are having. They have issue and bug trackers for a reason. The universe does not revolve around our little community.
Also, this issue pertains to the general consensus that touch screen issues (like bounce back) have become exacerbated on 4.2 and above. Not anything regarding physical QC issues (though, to be fair, may very well be the root cause, but that is an entirely different issue; the fact of the matter remains that anecdotally it appears the touchscreen responded better on 4.1.2)
And besides, I'm just looking out for the well being of this device's future. Reporting bugs on bug trackers is important to these developers.
Sent from my Nexus 10 using xda premium
to be honest, this annoys me a lot.
starred and commented.
This really annoys me as well. I voted and commented. Hopefully they can get this fixed soon. Otherwise I might switch to CM10.
Sent from my Nexus 7 using xda app-developers app
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
leonclement said:
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
Click to expand...
Click to collapse
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
farmerbb said:
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
Click to expand...
Click to collapse
Yea the notification bar is better on 4.2.2, but the launcher still does it, nova prime does it too, and even when on dolphin or boat browser sometimes when you flick it will scroll nicely & sometimes a flick wont move the page much at all, weird and annoying, would be a much better experience if it was fixed!
This is a huge issue for me. Is there a way to increase or decrease sensitivity? Maybe that would help.
Sent from my Nexus 7 using xda app-developers app
Interesting, I thought I was the only one who had noticed this. Don't know why I haven't seen this thread earlier.
For me I solved this by using apex launcher, somehow you never get those annoying jumpbacks. I tried nova launcher as well but it worked as bad as the original launcher. Going to star tomorrow.
Sent from my GT-I9300
As many people have noticed, the home/back capacitive/virtual buttons often do not work.
http://www.pocketables.com/2013/04/...-issues-with-capacitive-hardware-buttons.html
http://www.androidauthority.com/htc-one-capacitive-button-problems-198220/
http://forum.xda-developers.com/showthread.php?p=40538985
http://forum.xda-developers.com/showthread.php?t=2231832
http://forum.xda-developers.com/showthread.php?t=2243961
http://forum.xda-developers.com/showthread.php?p=40574171#post40574171
http://forum.xda-developers.com/showthread.php?t=2248951
http://www.youtube.com/watch?v=uvxi6KUR-WA
http://www.youtube.com/watch?v=V7zKpBSluKU
http://www.youtube.com/watch?v=7v5Oc5-7rbA
http://www.youtube.com/watch?v=wxkwyyvOkZ8
http://forums.androidcentral.com/htc-one/270508-home-button-shorting-out.html
http://forums.overclockers.co.uk/showthread.php?p=24147320
http://forums.androidcentral.com/htc-one/270811-back-button.html
http://forums.androidcentral.com/htc-one/271243-button-issue-htc-one.html
http://community.sprint.com/baw/message/569148
Personally, I find it to be *incredibly* annoying and pretty much ruins the experience of using this otherwise good phone. I have already been to the Sprint store to possibly exchange it, but their demo unit had the exact same problem (and the employee I was talking to had also noticed the problem). I have also ran "getevent -lt /dev/input/event6" from adb shell (/dev/input/event6 seems to be the raw output of the touchscreen, some people said it is event5 on theirs rather than event6). This shows you raw data every time you touch the screen. However I noticed that when my touches of the home button go undetected, nothing is read from /dev/input/event6...so I am afraid it may be a hardware problem. I have 11 more days before my 14 day Sprint satisfaction period ends, so I'm on the fence on whether or not I should return it and wait for a better phone, or exchange it and probably get another with the same problem, or...wait for HTC to try to fix it with software.
Some have said a recent update to the Taiwan version of the One solved the problem...:
patato2 said:
doing a bit translation from Taiwan version if you guys can't wait. not sure if I used the correct words though, hope you don't mind.
1.29.709.12(214.04MB)
1. virtual button sensitivity adjusted
2. slow motion video quality improved under low lit
3. better Beats Audio experience
4. better background noise when using headphone
5. better bluetooth device matching
some said back button issue fixed after upgrading.
Click to expand...
Click to collapse
Further evidence that a software patch fixed the home button:
http://translate.google.com/transla...a=X&ei=fy91Ua_5HYaQqgHi_ICwCA&ved=0CGgQ7gEwAw
Poor Google Translate translation:
Did not receive update notifications
Through Settings> About> Software Update> Check Now
We can immediately receive an update notification
After the update the virtual keys become normal
There is a need to go faster
PS: Please note that this is the official update, Brush, may not be updated automatically through the official update to brush back the official
Click to expand...
Click to collapse
Here is the response I got from HTC:
Thank you for retrieving the information for me, [xxxxxx]. I did some research and there will be an MR update to fix this issue with the virtual keys. We do not have any information as to the date the update will be released since it will be released via Sprint your network provider, and it is currently being worked on.
I realize that not having the specific details such as the date is annoying, but we do appreciate your patience. I want to thank you again for sending me that information because that really helps us out a lot. Let me know if you have any other questions I may be able to address with you at this time.
Sincerely,
Casey
HTC
Click to expand...
Click to collapse
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Most likely what you are actually noticing is that not all presses are registered and you are rationalizing it by assuming that you just missed the target. In reality, there is a problem with the home/back buttons that HTC needs to fix, soon.
chogardjr said:
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
I have this issue as well. Seems like you have to hit the button in almost the perfect spot to get it to register.
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
treIII said:
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
~Sent in beast mode using my HTC One~
chogardjr said:
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Hey chogard. Waaazz up? Where's your Rom if you have the one. Wheres that odexed beauty?
Sent from my HTCONE using Xparent Blue Tapatalk 2
Lots more confirmations that OTA 1.29.709.12 solved the problem for the Taiwan variant HTC One. WHEN WILL SPRINT/HTC GIVE US AMERICANS THIS FIX?
patato2 said:
Here's some information about 1.29.709.12 upgrade (Taiwan version), and some responses I read from other forum.
And... sorry guys, I really don't know when will your updates come. and i don't have the phone yet . I envy you!
.
1.29.709.12(214.04MB)
1. virtual key sensitivity adjusted
Lots confirmed the home/back key issue fixed, looks solid.
2. slow motion video quality recording improved under low lit
Didn't see anyone post about it
3. better Beats Audio experience
Some said the left / right sound are better balanced.
4. reduce background noise when using headphone
a few guys said noise is "significantly" reduced.
5. better bluetooth device matching
a few guys confirmed bluetooth device matched faster.
Click to expand...
Click to collapse
For anyone interested, the Taiwan OTA firmware is available here:
http://www.androidrevolution.nl/downloader/download.php?file=1.29.709.12.zip
http://forum.xda-developers.com/showthread.php?t=2182823
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
jaybombz said:
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
Click to expand...
Click to collapse
I prefer to tap with my fingertip and this is rarely detected by the home/back buttons, which is SOOOO annoying. I'm debating trying to swap it out for a new one. From what I can tell the problem seems to affect EVRYONE, although many people might not notice or be annoyed by it. So the question is, is it truly a pure software fault, or is it a hardware fault that software (ie, an OTA) can mask or at least partially correct.
That's my preference as well - it has been an adjustment and one that I'm not terribly pleased with. I'm surprised the issue didn't show up in pre-release testing but I have to imagine it's something that software can fix with a remap of the area the system recognizes as buttons.
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Where's the Rom Fernando?
Sent from my HTCONE using Xparent Blue Tapatalk 2
It's really not an issue with the "area", as I can touch the dead center of the home button and it still won't work. Seems to me that it is either not sensitive enough, or some other problem.
Regardless, word is that an OTA fixed this problem on the Taiwan HTC One 2 days ago, so now I guess we just need to complain loud enough that HTC/Sprint pump out the fix to us ASAP before we all return our phones.
Mines like this as well, you can hit the back button dead on and no response. Hopefully they issue a fix somewhat quickly.
Sent from my HTCONE using Tapatalk 2
Having this problem as well. My device was built April 9th 2013. I can sit there and tap on the home button for 30 seconds or more in every way possible and have no registration of the contact.
This might just be wishful thinking but for some reason clicking the app drawer icon seems to fix the issue right away making me think this is software.
Other than this the build quality and everything else seems perfect.
Sent from my HTCONE using xda app-developers app
HTC needs to admit they have a problem here and advise us whether we should be returning these or waiting for an OTA patch which will be coming VERY soon.
I saw some people talking about this and didn't know what they were referring to.. I got my phone on launch day and have no issues with it, that looks super annoying
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
mang0 said:
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Calibration does not resolve the issue.