Related
Hello,
I don't know if it is common to the diamond, that the power-button gives nearly no tactile feedback by pressing it, perhaps its only with few devices.
When I'am pressing the button I'am only aware to have done it correctly, when the device gets on or off. The button is built relatively deep into the housing of the phone, so I have often press it twice.
Even If I press it gently with the fingernail to feel slightes response, I it is very hard to recognize the point where the microswitch is activated.
Is this a normal issue?
Kind Regards:
Token42
i suffer from no such issue, i think yours is borked
pwoyorkie said:
i suffer from no such issue, i think yours is borked
Click to expand...
Click to collapse
Thanks for feedback. Currently the button works for me, appart from beeing not suh responsive - so I keep the device until it gets wors.
If I press the button in the middle with my nail there is a minimal "click-feeling" , so the switch seems not completely broken, curriosely there is a little more tactile feedback, when I release it.
how long have you had it ?
I know at t-mobile if develops a fault within the first 28 days youre entitled to an exchange. If youve had it under a month it may be worth just changing it before a 28 day exchange turns into a 2 week repair.
Mine has the same thing too. It really isn't a big issue but it does get annoying at times.
Mine reacts the same way, as I think it has been designed into the device as a "feature"......in other words: have to actively press it to make it work, so that it cannot be turned on by accident (hence why it is mostly recessed)
I don't think your device is broken....suspect if you return it, you will get one with exactly the same feature
Many thanks for your comments!
I feel much better now, since I know others have the same issue and it has not be a fault on my device.
Even it where faulty, I could live with it, cause it works all in all, but I think it would be much better to have a decent tactile feedbak on the power-switch.
Perhaps the power-button is a solid peace of hardware, but often when I press it I think something like "how long will it take, till does not work anymore" - but this is only a psychological issue, perhaps.
Many regards!
the button should project just enough to feel it with your fingers
the earlier htc touch had a recessed power button which was a bit difficult to press....so the one on the diamond is relatively easier to press coz it projects out of the body
also, how ur holding the device whilst pressing the power button also makes a difference!
I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks
Legaleye3000 said:
I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks
Click to expand...
Click to collapse
Mine shuts off the screen when your face is close to it.
Settings -> Call Settings, do you have Keep screen awake checked?
I don't see that option. Settings, then call settings... I see voicemail, call forwarding... That's pretty much it. Running Stock 2.1
Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.
bluehaze said:
Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.
Click to expand...
Click to collapse
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.
Maybe you have a really skinny head that's not passing the sensor?
nmesisca said:
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.
Click to expand...
Click to collapse
Nope, I imagine this will happen to everyone at some point though. It doesn't happen very often, it just out of the blue will happen one day. I guess the more you talk on the phone the more likely you will be to eventually experience it Maybe it has something to do with enabling the keypad? As that is what I did last night to punch in an extension.
This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.
bofslime said:
This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.
Click to expand...
Click to collapse
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.
I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.
Legaleye3000 said:
I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.
Click to expand...
Click to collapse
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.
krohnjw said:
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.
Click to expand...
Click to collapse
Yea it's some kind of fluke, It happens so randomly I am thinking it might be something to do with the internet connection like checking mail or maybe the GPS doing something that wakes up the buttons while the proximity sensor keeps the screen off because everything will be fine then all of a sudden it happens while the screen is still blacked out.
Sounds like a factory reset might fix this issue... definitely not normal behavior.
I think this is happening to a bunch of people. I don't think a factory reset would help. I think its a bug...
uansari1 said:
Sounds like a factory reset might fix this issue... definitely not normal behavior.
Click to expand...
Click to collapse
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.
bluehaze said:
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.
Click to expand...
Click to collapse
Are you accidentally hitting the volume buttons on the side of the phone? It sounds like you might be turning the in call volume down, thus leading to it being muted.
^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.
Legaleye3000 said:
^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.
Click to expand...
Click to collapse
Figured I would ask... I sell cell phones, and I get about 1 person a day in that has muted their in call volum by accidently hitting the volume toggle button without knowing it... all different phones (BB's are the worst!).
Anyways, my proxy sensor works perfect! I even just tested it a bit, and it senses a single finger tip starting about 1" away from the screen anywhere along the top of the screen... worked on both the left and right side and everywhere in between just fine.
I use my phone a lot at work in call (calling in to CS, calling the manager, etc) and have not had a single proxy sensor issue in the week I have had my phone.
bluehaze said:
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.
Click to expand...
Click to collapse
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.
bofslime said:
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.
Click to expand...
Click to collapse
LOL shortsighted eh? It's a bug it will happen to more and more people eventually and you will see, i'm sure it will happen to you eventually as well. Only thing shortsighted is your reply.
Good day to you sir.
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
Hi all,
It seems my home button is way too sensitive, it sometimes(I say sometimes because it seems to vary) senses a touch from up to 3-5mm away from the screen. This becomes problematic because since it's range is so big, it can pick a normal press as a long-press or even seem to be pressing by itself and it's pretty annoying. Is there a way to lower/calibrate it's sensitivity or even better, to move the "hold" functionality to the back or HTC button?
This wouldn't have bothered me and I haven't even noticed it until I made a very favorable (for me) exchange with some guy and he calls me the next morning to tell me I tricked him because I gave him a faulty phone and the button presses itself, so I had to tell him I'll look at the phone and try to see what the problem is and if I can fix it by tomorrow, so any help would be appreciated!
Also, the guy said in 2 instances he put the phone down and it kept pressing itself.
Edit: apparently the problem might be liquids(water or sweat) on your finger, explains why it would keep activating after your finger was taken away. That moment when you're using a product wrong and blaming it on malfunctions. Can anyone replicate this for me? Wet your finger and press the home button, see if it registers as a long press(i.e. opens google now), I want to be sure it's not limited to my device.
Is anybody else experiencing unresponsive screen on some parts?
Couple of days ago I started having problems with letter "a". It wouldn't react unless I pressed it all the way at the left side of the key, which I attributed to being close to curve of the screen - if the phone was in my left hand then I pretty much punched it on the right spot every time, so I thought it had to be it. It's an ongoing thing.
But now I was making a video in Quik app, and in one of the screens the play/pause button is right at the place where the letter "a", and I found my self having to press the key like 10 times in a row before it reacted - on a couple of occasions. I doubt it's some sort of memory issue since this thing is a beast and no way a couple of pics in Quik app could make it unresponsive.
I am utterly crushed now, since I love this phone to death. I really hope it's not a defect :crying: