search

esironal / hackerskeyboard

Automatically exported from code.google.com/p/hackerskeyboard
0 stars 0 forks source link

Vibrate on keypress doesn't work on some phones #14

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Reported for:

Vibrant with Teamwhiskey BionixV
Samsung Captivate

(This is assuming that the "vibrate on keypress" option is switched on in the 
keyboard's settings. This is off by default.)

It may be caused by a too-short vibrate time interval. Does it never vibrate, 
or is it inconsistent?

Original issue reported on code.google.com by Klaus.We...@gmail.com on 26 May 2011 at 2:08

GoogleCodeExporter commented 9 years ago 
This should be fixed in the latest release candidate v1.12rc5, it supports a 
configurable vibrate duration: 
http://code.google.com/p/hackerskeyboard/downloads/list

Please let me know if this works for you.

Original comment by Klaus.We...@gmail.com on 27 May 2011 at 12:49

GoogleCodeExporter commented 9 years ago 
Should be fixed in v1.12rc7, now published on the Market.

Original comment by Klaus.We...@gmail.com on 28 May 2011 at 8:13

GoogleCodeExporter commented 9 years ago 
It works perfectly. :D  Thanks!

Original comment by awangil...@gmail.com on 4 Jun 2011 at 5:09

GoogleCodeExporter commented 9 years ago 
Bulk update - changing "Fixed" to "Verified" for old bugs.

(Background: I'm changing the "Fixed" status to be considered open, the next 
steps in the lifecycle will be the closed states "FixInTest" and "Verified". 
This lets me mark issues as "Fixed" in commit messages without hiding them from 
the issue tracker.)

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:33

GoogleCodeExporter commented 9 years ago 
Bulk update - changing "Fixed" to "Verified" for old bugs.

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:34

GoogleCodeExporter commented 9 years ago 
I am unable to make vibration on keypress.  version 1.37 Samsung Galaxy Note 
2014.
BTW, I also took the code, it seems that LatinIME.vibrate() is correctly called.
Any clue?

Original comment by pizzo...@gmail.com on 14 Jan 2014 at 6:28

GoogleCodeExporter commented 9 years ago 
Forget about my last comment. It looks like my device has three different 
settings for vibration (Phone call, notification, and tactile feedback). 
Notification was down to zero, rising it solved the problem.  So it seems that 
Vibrator.viber() emit a "notification vibration", still wondering what is the 
api to distinguish the different kinds of vibration. Nothing found on the web 
till now.

Original comment by pizzo...@gmail.com on 14 Jan 2014 at 8:44