Database Develop

Capacitive Button Responsiveness?

Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?

I've never had a problem with mine.
I saw a review saying that they got in the way when typing w/ the onscreen keyboard, but I haven't even had that, and I'd like to think that I have pretty normal-sized fingers.

Some people have problems, others don't i personally haven't. I wouldn't consider it to be something important enough to sway me from a sale though.

Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
Click to expand...
Click to collapse
Definitely! That's one of the biggest reasons why I want an N1. It has a good root and dev community and gets android updates first.
I just thought it'd be annoying to have to use a phone with crappy capacitive buttons, but I'm glad to hear that the problem has been fixed.
The only other thing I'm worried about is the dualtouch but it's most definitely going to get fixed in the next update.
Thanks to everyone for their input. I'll definitely be picking up an N1 soon

I have rooted and custom roms etc and I still hate the capacitive buttons with a passion. They are not nearly enough to topple the overall awesome that is the N1 but man I hate those things.

I only hate those buttons, when Nex is in my car mount!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Click to expand...
Click to collapse
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I also haven't noticed any change in the sensitivity with different ROMs or kernels. For me though, sometimes if I hit right on top of the button it won't register. I am used to just tapping it a little above and it works everytime.
As others have said, this is definitely not a deal breaker for me or shouldn't be for any person IMO. This phone's pros far outweigh the cons.

The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
Click to expand...
Click to collapse
When someone is doing that you should just say that it has Finger print authentication technology

absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...

xboomer55 said:
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
Click to expand...
Click to collapse
Did you just buy your N1 from Google brand new?

Those buttons are a pain in the bum, but you get used to them, the bigger problem is if the phone gets too cold it starts mis-registering the touchscreen necessitating a reboot or a bunch of mucking around to fix it. This is the biggest annoyance with the phone for me, hopefully they fix the screen calibration in 2.2!
Almost swapped mine for a Desire, thinking less of doing so now, unless anyone can offer a good reason

I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.

SilentMobius said:
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
Click to expand...
Click to collapse
Just realized that!!
It does not get the upward movement
It gets: right, left & down
So this means, one could set different options for different directions...

hacker01 said:
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
Click to expand...
Click to collapse
I have noticed no issues when holding the phone in my hands but the responsiveness is not that great if the phone is flat on a desk or a similar surface. I wonder what if anything the accelerometer may play a factor.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I dunna man, my 3-year-old daughter figured it out within a minute of getting my phone. I set her up in a game and she decided she wanted something else, so she messed with the capacitive buttons until she got out of the game. Once she had it once or twice (~5-10 seconds for her to figure out each time) it was pretty much instant after that. If a 3-yo can figure it out, I'm pretty sure it's not THAT difficult. Annoying, sure....but not difficult.

hacker01 said:
Did you just buy your N1 from Google brand new?
Click to expand...
Click to collapse
Yes. Direct from Google.

Wow there's definitely a good mix of answers. I thought that the newer batches of N1's fixed the capacitive button problem, but apparently not.
I guess there's not a definite answer. It seems the only conclusion you can make is that some N1's may still have the problem, some may not. Some can be fixed with custom roms and unlocking the bootloader and some cannot. Your results may very.
EDIT: After rereading some of the previous posts (more carefully. excuse my sleep deprived state lol), the capacitive button issue might actually be more of a feature than an issue. I've read similar posts about the capacitive buttons having that sort of "motion detection" thing to prevent accident presses. Hopefully for anyone still having the problem, you can reread some of the posts on this page and give their methods a try

I haven't had a problem with mine but I haven't had the problems most people say they have with the phone so I would recommend this phone to anyone that wants an android phone
-------------------------------------
Sent from my Nexus One

Thinking of getting it

Hi everyone, right whoever has this HD7 can you tell me what its like? I'm really not sure if I should get this or the omnia 7, they both look great. Thanks for ya time.
Sent from my HTC Hero using Tapatalk

Moved to General

liverpoolfchero said:
Hi everyone, right whoever has this HD7 can you tell me what its like? I'm really not sure if I should get this or the omnia 7, they both look great. Thanks for ya time.
Sent from my HTC Hero using Tapatalk
Click to expand...
Click to collapse
I just picked up one, its sweet. Go into any mobile shop and give it a test drive. I love mine.

I have had the HD7 for 4 days now and I am very impressed, however I also recognise that WP7 is very much a version 1 operating system and there are still a) a few bugs (nothing catastrophic) and b) some missing features. The promise is here though so if you don't mind a bit of "early adopter pioneering" go get one

if MS does not deal with the missing features and the bugs SOON I am selling mine again.
to name a few:
- No manual IP on Wifi
- No own ringtones
- no .avi container support - synch of 350mb movie takes aprox. 20 minutes.
- everything over 20mb needs to go over the marketplace (what do i have an unlimited data plan for?)
- no usb-hdd support
- no copy&paste (personally not missing this though)
- no proper multitasking. you can go back, but how do you go forwards?
- ringer only vibrates once, email sounds delayed
... i could go on

pencilcase said:
if MS does not deal with the missing features and the bugs SOON I am selling mine again.
to name a few:
- No manual IP on Wifi
- No own ringtones
- no .avi container support - synch of 350mb movie takes aprox. 20 minutes.
- everything over 20mb needs to go over the marketplace (what do i have an unlimited data plan for?)
- no usb-hdd support
- no copy&paste (personally not missing this though)
- no proper multitasking. you can go back, but how do you go forwards?
- ringer only vibrates once, email sounds delayed
... i could go on
Click to expand...
Click to collapse
What do mean by everything over 20Mb must go over the market place?

all downloads coming from the marketplace that exceed 20mb in size need to be downloaded with Wifi or over zune/cable.

pencilcase said:
all downloads coming from the marketplace that exceed 20mb in size need to be downloaded with Wifi or over zune/cable.
Click to expand...
Click to collapse
I think you'll find this is not just WP7 Devices, all smartphones these days do that including the iPhones, I suppose it was to cut down on the traffic and stuff on our carriers networks that are already overloaded with stuff.
Not saying it's right but that's the way it is.

ThePhoenix2007 said:
I think you'll find this is not just WP7 Devices, all smartphones these days do that including the iPhones, I suppose it was to cut down on the traffic and stuff on our carriers networks that are already overloaded with stuff.
Not saying it's right but that's the way it is.
Click to expand...
Click to collapse
Yeah, I remember reading somewhere about the carriers (including O2) having panic attacks about networks overloaded by legions of downloaders.

pencilcase said:
all downloads coming from the marketplace that exceed 20mb in size need to be downloaded with Wifi or over zune/cable.
Click to expand...
Click to collapse
This is very unfortunate! With my former HTC Desire running a custom rom (DeFrost) based on the ofiicial Android 2.2, I could download 136 MB on 3G, it was DeFrost roms, with were available through his DeFrost setup Tools. I never had an issue because the download speed was crazy fast! But I had to be in an area of very good coverage (all signal bars in the green) to have it within 20-25 minutes (sometimes up to 40 minutes). I used to do it during lunch time and flash from sd-card on my way back to the office. It's the only feature I miss from the Desire: the simplicity of the flash process, provided you have a custom recovery image, in my case, Clockwork recovery image.
f.

I've had mine for just over a week now and am thinking about returning it and getting a Omnia 7 instead, It has that reset bug that HTC said about, and the physical buttons on it are extremely annoying, none of them have a 'click' to them so you can never tell if your pushing it enough to activate it, also you end up pressing buttons without even noticing, I often end up launching the camera just because my finger rests on the button and activates it for example.

i love my hd7 so much but i would say this, if i could swap it for a 16gb omnia 7 i still would but i could not live with only 8gb even if there would be a work around, and i am to impatient to wait and see if anyone will stock it.

i pre-ordered HD7 for US Tmobile but i'm considering to cancel it and wait for the dell venue pro
people who got the device, what would you do ?

I am very pleased with the hd7, the feel of quality in the hand, the superb big screen together with those 16gb give it the edge IMHO.

adesonic said:
I am very pleased with the hd7, the feel of quality in the hand, the superb big screen together with those 16gb give it the edge IMHO.
Click to expand...
Click to collapse
This is also how I felt for the first couple days, but after you've had it for over a week like I have you might start to get frustrated with the problems I've had.

Milky1 said:
I've had mine for just over a week now and am thinking about returning it and getting a Omnia 7 instead, It has that reset bug that HTC said about, and the physical buttons on it are extremely annoying, none of them have a 'click' to them so you can never tell if your pushing it enough to activate it, also you end up pressing buttons without even noticing, I often end up launching the camera just because my finger rests on the button and activates it for example.
Click to expand...
Click to collapse
Some other people have reported very "soft" hardware buttons (volume in particular) that are a bit mushy, and therefore hard to tell if you are applying enough pressure. Some people have swapped their HD7 for another one for this reason.
My own HD7 thankfully doesn't seem to suffer from this as the volume keys have a definite "click"-feel when pressed, so you can tell that you're pressing them right even if it's in your pocket.
Same with the camera button on mine; it's a 2-step camera button and you have to press fairly firmly to get the camera to activate. I've yet to accidently initialise the camera.
My HD7 is an O2 branded one in the EU with the dark gray chrome-like band. Perhaps the HD7s with the brighter chrome band suffer from this?

wheresmybeaver said:
Some other people have reported very "soft" hardware buttons (volume in particular) that are a bit mushy, and therefore hard to tell if you are applying enough pressure. Some people have swapped their HD7 for another one for this reason.
My own HD7 thankfully doesn't seem to suffer from this as the volume keys have a definite "click"-feel when pressed, so you can tell that you're pressing them right even if it's in your pocket.
Same with the camera button on mine; it's a 2-step camera button and you have to press fairly firmly to get the camera to activate. I've yet to accidently initialise the camera.
My HD7 is an O2 branded one in the EU with the dark gray chrome-like band. Perhaps the HD7s with the brighter chrome band suffer from this?
Click to expand...
Click to collapse
Mine is O2 UK and it has a dark band, and every button is completely soft, I don't know if it would annoy everyone but it drives me insane.

Odd! Mine was an O2 one... the only mushy button was the camera button. Never accidentally launched the camera app, but the Search keeps randomly appearing.

Milky1 said:
This is also how I felt for the first couple days, but after you've had it for over a week like I have you might start to get frustrated with the problems I've had.
Click to expand...
Click to collapse
thats EXACTLY my opinion

I evaluated the HD 7 and found the absence of adequate configurable options most disappointing.
1. Unable to disable the haptics (vibrate on key press)
2. Unable to configure own WiFi settings, which means NO access to known hidden networks such as mine at home.
3. Level of java application support unknown
4. Co-Pilot not supported with localised maps when travelling
5. No MicroSD memory expansion
6. No file browser
That was enough to put me off ... although it is a fast and sleek new interface almost mimicking the i-phone monkey-see-monkey-do interface (dummies phone but vastly improving on WinMo, although so many things have dropped away such as the wifi router etc.
A great phone, but not for someone expecting more from their phone out of the box such as the HD 2 for example.

[Q] Screen inaccuracy issues

I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?

Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.

It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.

I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App

msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.

It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).

Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!

Most probably replaced the phone's MB.

Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...

I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.

ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App

pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?

xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.

The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.

Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.

The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.

Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.

Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App

Differen Nexus One hardware revisions?

Hello everyone,
I had a friend of mine purchase a T-Mobile Nexus One on eBay for me today and I am pretty excited coming from HTC Magic.
Today, I also realized that I haven't looked up Nexus One problems on the Internet. Being a fan of the android platform and going up and down through android blogs, I never read anything bad about the Nexus One and I totally forgot.
Just now I did a quick research and found out that the Nexus One has a bunch of problems which gets me worried.
Are there different revisions of the Nexus One hardware which don't have one another's glitches? Or are all the bugs I found fixed with the software updates? The problems I read about were experienced right after the Nexus one launch 1 year ago and people are running 2.1.
I'm pretty worried that I may have bought a faulty device since it's a used device even though it looks to be in excellent condition judging by the photos.
Any calming advice?
Here are the problems I found that people are experiencing
P.S. The phone will be used in Europe so I'm not sure about that 1st 3G issue.
1) 3G connectivity issue
2) Touch Screen unresponsiveness/sensing incorrect input
3) unresponsive trackball
4) WIFI connectivity issue
5) Lock button response issue
6) Proximity sensor sensitivity issue
7) Ambient light sensor issue
8)bluetooth issues: fails to operate; inadequate volume; intermittent failure to accept commands
9) speaker: horrible sound quality
10) ringer: insufficient volume
11) earpiece: insufficient volume
12) headset connector: headphones cord activates pause or other functions
13) manufacturer says phone cannot go in pocket
14) Phone mutes when calling people and can only be unmuted by turning mute on then off!
15) missed call notification trackball does not flash
Click to expand...
Click to collapse

The only worry of you is about 5) Lock button response issue it could fall down.
Besides the 2) Touch Screen unresponsiveness/sensing incorrect input which sometimes is annoying the other things can be resolved by software..
Anyway congratulation for the acquisition!

Thanks
And is the lock button issue fixable in some way? Also, is the touch screen issue observed on every device with every ROM? Is it a hardware issue?

1. Never existed in 1st place.
2. HW fault. Seems that you can't do anything about it.
3. Never existed.
4. WiFi sleep bug - solved in SW update a long time ago.
5. Power button is prone to failure. Use it lightly and avoid using it as much as you can (using trackball wake) - and it'll last.
6. Never existed.
7. Never existed.
8. Never existed.
9. Not horrible, just low volume. Hack exists in SW.
10. Hack exists in SW.
11. Hack exists in SW. And it's not a fault, anyway. Some complain that after the hack it's way too loud.
12. It's a feature, that doesn't work well with non-stock headphones. Can be deactivated easily.
13. All manufacturers do, and phones still go in pockets.
14. Never existed.
15. Most probably caused by incorrect update to Gingerbread. Reflashing solves it.

HTC One vibration sound

Picked up this phone just today and my god I love this phone to death but every phone comes with complaints. Most things arent big and will just take time to get used to but this one I cannot ignore. I love having the vibrate on keypress option selected and the HTC One when it vibrates makes this very unpleasant loose spring like sound whenever it vibrates. Am I the only one thats noticed this or is this every device?
Sent from my HTC One using xda app-developers app

many people do have this ... me too.... thats my second device and both of them got this crappy vibration sound...
i replaced it because of that .... but because of that i disabled every vibration functions on this phone to get rit of it ....
so i guess you have to live with it ... try to replace it and hope you get one with a good vibration motor or disable all vibrations

B-Man2005 said:
many people do have this ... me too.... thats my second device and both of them got this crappy vibration sound...
i replaced it because of that .... but because of that i disabled every vibration functions on this phone to get rit of it ....
so i guess you have to live with it ... try to replace it and hope you get one with a good vibration motor or disable all vibrations
Click to expand...
Click to collapse
Isnt that due to the OIS? Not sure about but all of my 4 Ones had that. The One of a friend also sounds like that. I´m ok with it.

shox22 said:
Isnt that due to the OIS? Not sure about but all of my 4 Ones had that. The One of a friend also sounds like that. I´m ok with it.
Click to expand...
Click to collapse
It's something you have to live with

shox22 said:
Isnt that due to the OIS? Not sure about but all of my 4 Ones had that. The One of a friend also sounds like that. I´m ok with it.
Click to expand...
Click to collapse
I'm sure there will be soon an option in custom roms to control vibration intensity, and put it to the value you like! it's only a matter of time, I'm sure!

[I'm sure there will I am currently facing the same issue with my replacement and thinking about replacing it again but hesitant because every device comes with its own minor defects, u only notice the alight clicking in a very quite environment and only on short vibrates such as when typing, but to be honest this is as perfect as it can get, everything seems to work with this device with no problems except this, and I might apply for a replacement and end up with a worst unit and another major issue, I have emailed HTC complaining about their quality control, cuz my first device had gaps and a tiny hair under the screen, my second device had a touchscreen problem and now this one which has a minor vibration sound.
The problem is I am too picky when it comes to this kind of stuff and a little ocd about them so I am positive that other people won't even notice the issue and even the repair tech might claim it's normal and in all devices. So yeah
my device is work related so giving it to them for 2 full days is kind of troublesome for me

add me to the list
I have had my HTC One for 2 days now. I too noticed this on mine. I just chalked it up to the phone being all aluminum case vs my old EVO was plastic/metal. I have a few other complaints too lol.
Ok the rants!
1. Why did you have to move all the buttons all over the place? Seems like every button is opposite to other android phones? Especially moving the power button to the far left? Who designed this? Must of been a left handed person. Come on at least compromise and put in the middle! Stupid!
2. Why limit to only 3 buttons at the bottom of the HTC one and in all actuality...you never enabled the "HTC" to be a button so we are stuck with 2! Most phones have at least 3! Again Stupid!
3. The Home button and back buttons. Ok maybe the person designed this drives on the wrong side of the road or goes in the exit door or something? The buttons need to be flipped in my humble opinion. Home first (left side) or at least in the middle, back button to the left or right sides. OH and bring back the quick access button!
4. Ok speaking of the "HTC" logo/button at the bottom. Why put in circuitry for it to be a button and then not enable it? Stupid #3!
5. The widgets for "Bluetooth", Wireless", "Mobile", and "GPS". Why light blue for the "on notification". Seems like a **** poor color choice. At least a green or red would be fairly noticeable considering the widget itself is blue? Hello.....great designing there.
6. The power button. More recessed then ever before making it difficult to push down or even find. No step up here.
7. Lock screen can only have 1 widget on it? Really? Wow...couple steps back here.
8. Full animated weather locking screen gone/no longer available because HTC forces you to use their one and ONLY ONE version their crappy line art weather on the lock screen. I don't mind the plain jane weather for showing up in the app list but placing it on the bottom of the lock screen with nothing else is horrible. I want my weather back to the lock screen. I know I have mentioned it a lot...sorry pet peeve, have it it so long on all my other phones.
9. I won't mention Blinkfeed. I have that pushed off the side and hear that sense 5.5 is around the corner which will allow you to finally turn the damn thing off.

Hey guys, I wanted to point out that you can reduce the vibration intensity, therefore getting rid of the "springy" feeling! Just download FauxClock. (Yes you need root of course). Gratefully this app doesn't require you to flash anything, it just needs BusyBox. The only downside to reducing the intensity is after so far you basically lose haptic feedback. (I wanted to reduce notification buzz.) And this is where I went with plan B.
Plan B (NO ROOT!): This method, you guys, will make you feel real dumb for not thinking of. Personally I did this to get rid of notification buzz but keep haptic feedback, but you can also just turn off buzz on certain apps. Simply open up App-ops on Android 4.3, go through all your apps, and untick the "Vibration" permission! That's it guys! Feel dumb now?
Note: to open App-ops is an activity, you can download App-ops launchers from Play Store or, in my case, I used a Tasker task.
--
<<< Say thanks if I was of help! :good: