Vibration no longer working - XPERIA X1 General

Just realised today. Anyone know if it could be a software issue? When I switch the phone on, i hear a click (I'm sure that once upon a time, it used to vibrate?!).

Please use the search function on the forum, there have been at least two threads on this subject already.
Some people have said that it's down to one of the "torch/flashlight" applications, where the constant use of the LED at high brightness has melted/deformed the housing for the vibration motor/cam and so has stopped vibration from working.
e: After a quick search on the keyword "vibration":
http://forum.xda-developers.com/showthread.php?t=456477&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=472647&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=467993&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=465180&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=460252&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=450627&highlight=vibration
I didn't realise there were quite so many myself...

SquidgyB said:
Please use the search function on the forum, there have been at least two threads on this subject already.
Some people have said that it's down to one of the "torch/flashlight" applications, where the constant use of the LED at high brightness has melted/deformed the housing for the vibration motor/cam and so has stopped vibration from working.
e: After a quick search on the keyword "vibration":
http://forum.xda-developers.com/showthread.php?t=456477&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=472647&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=467993&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=465180&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=460252&highlight=vibration
http://forum.xda-developers.com/showthread.php?t=450627&highlight=vibration
I didn't realise there were quite so many myself...
Click to expand...
Click to collapse
Pretty sure this is the reason. You probably used Htorch on high level for more than a minute. Its is easy to fix once you open the case and move the led so it is not in touch with the vibrator motor.

Same symptom on my phone,i used the torch/flashlight program before.Luckily my phone still under warranty.

Related

Keyboard backlight time

I know some people wanted to increase the keyboard backlight time. In case this hasnt been posted already, mad monkey has a cab for it:
http://www.dweiniger.com/tips/k-jam.shtml
No i have not seen this posted. tried on my qtek did not work - does it work on your device. i have seen a hack for the universal not wizard
cheers
nope this don't work on the T-Mobile MDA (US model)
Is it supposed to be a DWORD value? Anyone has gotten this to work?
ch4kk said:
Is it supposed to be a DWORD value? Anyone has gotten this to work?
Click to expand...
Click to collapse
No joy here
didnt work either on 2.8
nope - doesn't work
http://forum.xda-developers.com/viewtopic.php?t=38314
You would think someone at HTC would know how to do it. Do any of those guys/girls post on this forum?
not that I've ever seen - not on any of the official retailer sites either. good luck
p.s. the question might not be 'how to do it' but 'can it be done'
yeah, I'm beginning to believe that the whole thing is completely implemented with hardware: a keypress starts a LED "On" timer. This is also why the kbd doesn't illuminate when it gets extended. Even though WM senses this and flips to landscape, it has no control over the backlight: It takes a keypress to start the timer circuit that illuminates the backlight you see.
bummer.
Sleuth255 said:
This is also why the kbd doesn't illuminate when it gets extended. Even though WM senses this and flips to landscape, it has no control over the backlight: It takes a keypress to start the timer circuit that illuminates the backlight you see.
Click to expand...
Click to collapse
Working under the assumption that it is indeed in-hardware, there would've been nothing to prevent the engineers from making the magnetic switch enable the backlight, too
Working under the assumption that it's purely software, there should be nothing to prevent WM5 from doing this... other than that nobody has coded it to do so
Working under the assumption that it's hardcoded in the driver, somebody would have to hack the driver to extend the backlight; adding functionality to turn the backlight on would be a bit more difficult.
ZeBoxx said:
Working under the assumption that it is indeed in-hardware, there would've been nothing to prevent the engineers from making the magnetic switch enable the backlight, too
Click to expand...
Click to collapse
I'll give you "glass half full" on that one :wink:.
However.... the magnetic switch would be more difficult to implement than a simple key press which also resets a timer circuit. You'd have to tie that additional input into a circuit that could be hard-wired with the keyboard itself.
there's my "glass half empty" viewpoint.... I've just got a bad feeling on this one..... sorry.
I guess I'm going to have to take a closer look at some of the disassembled wizard pictures to make up my mind on this.
I sure hope a way is found to fix this as well as control those other blinking leds.....
well the point was, basically, there already -is- a magnetic switch. It's used to signal the OS that the keyboard has extended, and allow it to react on that; the chosen reaction being that the screen orientation is changed.
There would be nothing whatsoever stopping the engineers who actually put the thing together (not talking about somebody taking it apart and tinkering in there and whatnot) to have hooked that up to the backlight control /if/ that is in hardware %)
And if it's in software, then nothing would have technically stopped the software developers from making the keyboard slide-out trigger the backlight that way; assuming they already do as much on keypresses.
exactly. But the kbd does't light up when you extend it you see.... This behavior shoud be obvious
ok weird doesnt even put this into perspective ... i edited that value and softreset my phone. backlight timeout is still 5 seconds and now my bottom ( previously skinned) bar has gone back to default colours ... tried removing the value and resetting again had no effect either ... lovely hack this is now i can try and figure out why the hell this just happened ... running newest official qtek rom only for info
I think this is one of the largest downsides to this device. When I pull the keyboard out the lights should come on AND it should be longer then 5 seconds. It would also be nice if it had a light sensor (like on the SMT5600) to know if the light SHOULD come on or not.
If someone (or HTC) would fix this it would be awesome.
oh, they'll fix it - for their next device models The Universal already works that way, and you can tweak the backlight time. I'm sure by now they've gotten all the feedback they need to decide that that is better than the fixed behavior of the Wizard (not sure who at HTC ever figured that would be a good idea to begin with).

Haptic touchkeyboard for wm6?

Has anyone made a haptic touch plugin for wm6 devices?
Would love the phone to slightly vibrate when I use the touch keyboard.
I'm on a htc diamond btw.
I think it would be cool too, but I think one of the biggest problems is the time delay between hitting the key and feeling the vibration. I also wonder about the effect on battery life... anyways I would still like to try it!
You might want to do a search because I remember reading about something like this but think it was for the dialer.
I will post here if I find the thread.
-bridic-
Yea I am pretty certain one of the Iphone dialers is haptic or something...perhaps it's a dailer you have to pay for.
I have a couple kinda sorta solutions..
I'm at work so I don't have them here.. But I have one .cab that will vibrate when you press the number buttons on your dial screen, and it work's perfectly. And then I have an .exe that make's every screen tap vibrate, and it kinda sorta work's. I've looked for feedback programs for months, and have found nothing. The best thing i've determined which took me forever, is enabling screen tap sounds, and going into the registry and changing the default sound to vibrate instead.. I can also look up how to do this for you when I get home.. But really there's no good solution out there. On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Raven1467 said:
I'm at work so I don't have them here.. But I have one .cab that will vibrate when you press the number buttons on your dial screen, and it work's perfectly. And then I have an .exe that make's every screen tap vibrate, and it kinda sorta work's. I've looked for feedback programs for months, and have found nothing. The best thing i've determined which took me forever, is enabling screen tap sounds, and going into the registry and changing the default sound to vibrate instead.. I can also look up how to do this for you when I get home.. But really there's no good solution out there. On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Click to expand...
Click to collapse
Tnx a lot walter, and thanks for explaining the difference between haptic and tactile
Posting a guide on changing the registry or giving me a link to the two programs mentioned over would be great.
Raven1467 said:
On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Click to expand...
Click to collapse
uh, not quite sure what "haptic" technology you're talking about, but any feedback of mechanical vibration would definitely be considered "haptic feedback". From wikipeida: "Haptic technology refers to technology which interfaces the user via the sense of touch by applying forces, vibrations and/or motions to the user."
Also, to address concerns a little further up the thread: If implemented correctly, there is no perceptible delay between screen contact and vibration feedback. Me and a couple friends whipped up a little test application based on the WM6 SDK's application template, wherein if you tap anywhere in the application window, the vibration motor is toggled for ~50ms (this can be adjusted based on preference, but 50ms was a nice barely perceptible 'thud' with each tap). The feedback is, for all intents and purposes, instantaneous. Also, since the vibrator is only active for 50ms, you'd need to tap 20 times before you've drained the same battery as a 1 second text message alert, or 40 times for 2 seconds, and so on... really, I think the battery drain would be negligible. Anyway, proof of principle for using the vibration motor for haptic feedback is there, and the affect is quite nice, but we never got much further because of a lack of time and programming knowledge. By the way, if anyone has any information on how to hook into touch.dll (which would be the proper way of implementing a system-wide haptic response), I'd be very interested in hearing about it.
This sounds a very interesting idea! Not every program visually responds to touch when operated with finger, so sometimes I was just left wondering did I make the touch? Did the touch go through? Then one or two seconds later (yes my phone is that slow) something happens. This should help if not eliminate that problem.
Here is the cab for the haptic-esque dialpad if anyone was interested
i've noticed that when haptics is on, it tends to vibrate only every other press
such intensive vibration is probably bad for your phone
a_lazy_dude said:
Also, to address concerns a little further up the thread: If implemented correctly, there is no perceptible delay between screen contact and vibration feedback. Me and a couple friends whipped up a little test application based on the WM6 SDK's application template, wherein if you tap anywhere in the application window, the vibration motor is toggled for ~50ms (this can be adjusted based on preference, but 50ms was a nice barely perceptible 'thud' with each tap). The feedback is, for all intents and purposes, instantaneous. Also, since the vibrator is only active for 50ms, you'd need to tap 20 times before you've drained the same battery as a 1 second text message alert, or 40 times for 2 seconds, and so on... really, I think the battery drain would be negligible. Anyway, proof of principle for using the vibration motor for haptic feedback is there, and the affect is quite nice, but we never got much further because of a lack of time and programming knowledge. By the way, if anyone has any information on how to hook into touch.dll (which would be the proper way of implementing a system-wide haptic response), I'd be very interested in hearing about it.
Click to expand...
Click to collapse
That sounds pretty perfect. Would be nice if someone finished your project.
DiemetriX said:
That sounds pretty perfect. Would be nice if someone finished your project.
Click to expand...
Click to collapse
I've installed this but can't find it anywhere. Looked in programs, personal and settings. I've even looked in the windows folder. I have an HTC Raphael.
Any pointers please...?

[REQ]Answering calls using the Light sensor or Gsensor or proximity sensor?

I was thinking if is possible to make a program that uses the light sensor to answer calls! (when u receive a call just put the phone to your ear and auto answers). I think that would be cool!
The author of Answerkeys Disabler looked at the the usability of the light sensor - his conclusion was that it was not sensitive enough for most applications - and I would expect that to include answering calls. Have a read through that thread for more info.
I think it's a daft idea anyway - lots of situations could cause a call to be accidentally answered.
Well, i think it would be a bad idea (sorry ).
What if you had it in your pocket or jacket? And when your asleep, and you get a call, then what? Your friend can hear you snoore or having a good time, with your gf
H3IN3K3N said:
Well, i think it would be a bad idea (sorry ).
What if you had it in your pocket or jacket? And when your asleep, and you get a call, then what? Your friend can hear you snoore or having a good time, with your gf
Click to expand...
Click to collapse
you are right
It could check the default state. If it's dark (probably in the pocket) then wait to be light(out of pocket) and than dark again to answer(ear).
But the problem is this will not work if it's night and you are somewhere outside and there's no light for the sensor to notice... Than again the application could have a setting to be active only during daylight and after sunset it would automatically disable itself.
How's that?
IIRC, the light sensor is updated at a fixed interval. So it may not be so accurate to answer a call (eg: you put the phone to your ear but the call is answered after a bit).
Maybe it would be better to use the GSensors to capture the phone movement you made to answer a call.
Marshall
Nom nom nom.. Interesting thread. Please do post your good ideas, then all of a sudden someone might invent the killer app
About the light sensor. The thing wont measure anything above 0 if lighting is poor. I mean not only in the middle of the desert at 4 AM when its darker then my coffee, but also in my fluorescently lit hallway, in which I can perfectly read a book. So the thing will always measure 0, you cannot detect changes in that, unfortunately.
Ideea
is it possible to connect the LIGHT sensor with GSensors? (ex: based on the G force produced when you look at the phone to see who's calling an then the light sensor is kicking in, if you want to answer put it at your ear, if not turn the phone face down and it shuts the ringing off!)
Just thinking......
drvdijk said:
Nom nom nom.. Interesting thread. Please do post your good ideas, then all of a sudden someone might invent the killer app
About the light sensor. The thing wont measure anything above 0 if lighting is poor. I mean not only in the middle of the desert at 4 AM when its darker then my coffee, but also in my fluorescently lit hallway, in which I can perfectly read a book. So the thing will always measure 0, you cannot detect changes in that, unfortunately.
Click to expand...
Click to collapse
something poped out in my head. When the phone rings the light comes on, is the sensor able to pickit up?
Nope. Tried this in the toilet in which the light was broken. It wouldn't get above 0. Taking a dump without lights is pretty hard by the way..
No other ideas?
Well...I keep my phone in it's luxurious pvc htc slide out pouch, it's pretty dark in there, if the light sensor is able to detect when the phone is in the shade of your ear it must be quite sensitive or else that just would not be possible. So imagine the phone locks automatically when it rings and then unlocks and auto answers when the light sensor detects an increased light level, You would need a few options I can't think of right now, but the normal answer button should still work in case no change is detected. So if your phone was in your pocket or pouch there would be no accidental button presses/call rejections and you would not have to press a button to answer it. = killer app.
Leave your phone face down on your desk, just pick it up to answer a call.
uniqueboy said:
Well...I keep my phone in it's luxurious pvc htc slide out pouch, it's pretty dark in there, if the light sensor is able to detect when the phone is in the shade of your ear it must be quite sensitive or else that just would not be possible. So imagine the phone locks automatically when it rings and then unlocks and auto answers when the light sensor detects an increased light level, You would need a few options I can't think of right now, but the normal answer button should still work in case no change is detected. So if your phone was in your pocket or pouch there would be no accidental button presses/call rejections and you would not have to press a button to answer it. = killer app.
Leave your phone face down on your desk, just pick it up to answer a call.
Click to expand...
Click to collapse
Is that possible right now then? I'd be very interested in the software that disables the screen as soon as it hits your ear.
Can anybody help to make this app?
Give me $50 and I'll make it for you, with the limitations as noted in this thread
drvdijk said:
Give me $50 and I'll make it for you, with the limitations as noted in this thread
Click to expand...
Click to collapse
I don't mind donating but being so upfront asking for money is a little inappropriate in my mind but if that's what it takes let's see how many people wants it, and donate for your cup of coffee!
Sorry, my point wasn't to ask for money (allthough my post clearly indicates that, I now notice). My point was that I need a very good reason to develop a program of which I know in advance will not work as we both would like to see it work.
So there is no way to make an app that auto answers when you put your phone at your ear (using GSensor or Light sensor)?
P.S. No more ideas? Or close this thread Forever!!!!
How about an application that implements a "proximity sensor" that other phones seem to have? It's kind of annoying to have the touchscreen turned off randomly when you need to punch in some numbers for automated hotlines.
Lawliet said:
How about an application that implements a "proximity sensor" that other phones seem to have? It's kind of annoying to have the touchscreen turned off randomly when you need to punch in some numbers for automated hotlines.
Click to expand...
Click to collapse
i think is a good idea!

Problem while on hands free....the phone is unlocked in pocket!!!!!

Hi all
So i got my HTC HD2 nice feel to it....but..
2 things :
1:while i have handsfree on i answer a call as always and the phone unlockes in my pocket a.s.a i answer and then...well buttons keep pushing and calls keep shutting off e.t.c
i called HTC and they said nothing they can do and that there is a 3rd party app to fix this....well i am to "stupid" cause i cant find it..
plz help.
2:Very sensitive screen and i have dificulty figuring out hoe to change that..
thnx allot guys for "listening" hope to get some answers...esspecially for nr1 its a pain....
Hi,
I know you are new on here but a few threads up from yours you would have found this one...http://forum.xda-developers.com/showthread.php?t=583638
Take time out to read it and you should find answers to at least some of your problems.
Good luck
WB
The screen is capacitive, so it shouldnt be possible for anything to be pressed in your pocket.
loomx said:
The screen is capacitive, so it shouldnt be possible for anything to be pressed in your pocket.
Click to expand...
Click to collapse
Whilst the screen is capacitive, the material of a pocket may be thin enough to still allow a key press to register.
Also I believe the hard keys would still be available to press and could hang up the call.
I think there is an issue with the keypad becoming active while on a call.
I've used this phone since launch and it's driving me nuts.
One of the main problems is the proximity sensor which should turn off the touch screen during an active call intermittently doesn't work.
I called my wife today and cut her off at least twice because of this bug.
There is a reg tweek to reduce the sensitivity of the screen- you have to google it.
SMS is alos occasionally sticking.
I'm going to start a new thread to ask if 1.61 cure these issues.

Annoying Auto LCD Turn Off While Making Call

Hi all, I absolutely love the HD2. However, I find one really annoying problem about the "auto LCD shut off between dialing and after a call is connected, and this has been really driving me crazy! I'm not sure why no one has mentioned about this, is it because it is my problem of mis-using it or no one has bothered to voice it up?? I apologized if this has been posted but I couldn't find one solution so far.
It is about the auto LCD shut off sensor feature while making a call. My English is not that good, my mother tongue is Chinese, I will try my best to describe the problem written in English. I've tried so many cooked roms, all have the same old frustrating issue. After when I've dialed a number, as most ppl do, I will put the phone near my ear while waiting for the call to get connected. However, in the process while making the call while the phone is near my ear, the LCD will shut off by itself, and when a call is connected, the annoying issue will occur! When a call is connected, the LCD will turn back on by itself even though the phone is still in tack with the ear, as a result, part of our face will make contact on the screen and very often pressing one of the on-screen buttons! Also, it is not only this problem will happen after a call is connected, during a process of calling or during a conversation, if there is a notification prompted out, for example, a sms have been received, or a email has been received or low battery notification, the LCD will always turn back on and make the face accidentally press on one of the on-screen button, this is really annoying, is there a solution to let the sensor shut off the LCD for good until the phone has really get away from the ear and the face???
It's not a problem
It's an advantage
HTC did that to prevent you from touching anything with your ear and you cheek and maybe without this you could end the call accidentally or lunching apps so and so .....
Some people have found that this happens when their screen protector is too close or covering the sensor. Cutting away a small ammount of the screen protector to make sure it doesn't interfere with the sensor seems to be the answer.
Not sure you have read his question correctly - it turns off when he puts it to his head, which he wants, but then it turns back on again when the call connects.
I have the same problem, (incidentally had the same problem with a Diamond and Omnia II with Tachi phone canvas). Only solution was to breifly move it away from your head and back again, which I just got used to.
No idea how to solve it though. Sorry.
[APP] Proximity Sensor for Screen Off v0.2
Maybe you should look for this little app, it could work for you.
I can't post links, so make a search inside xda, there's a topic with that title.....
peacebank said:
Not sure you have read his question correctly - it turns off when he puts it to his head, which he wants, but then it turns back on again when the call connects.
I have the same problem, (incidentally had the same problem with a Diamond and Omnia II with Tachi phone canvas). Only solution was to breifly move it away from your head and back again, which I just got used to.
No idea how to solve it though. Sorry.
Click to expand...
Click to collapse
yes, the first 2 replies didn't get what my question is, sorry for the misunderstanding if I've made any.
giegi_dc said:
[APP] Proximity Sensor for Screen Off v0.2
Maybe you should look for this little app, it could work for you.
I can't post links, so make a search inside xda, there's a topic with that title.....
Click to expand...
Click to collapse
thank you so much! I will look for it, and hope it is a solution.

Categories

Resources