Difference between revisions of "Talk:OMAP vibration device"
(Personal research demonstrates different results than those presented in article) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <p>My own research has offered certain different results than are identified in this article, and others which are not mentioned: | |
| − | + | </p> | |
| − | First, as of 1.4.1.1 the low threshold for ''perceptible'' vibration, whether charging or on battery power, is | + | <p> |
| − | + | '''First''', as of 1.4.1.1 the low threshold for ''perceptible'' vibration, whether charging or on battery power, is nearer to 17%, not 20% as stated. | |
| − | Second, default ''duty_cycle'' is not 50 | + | </p> |
| − | + | <p> | |
| + | '''Second''', default ''duty_cycle'' is 99, not 50, and can be demonstrated through the following methods: | ||
| + | </p> | ||
| + | <p> | ||
(assuming ''duty_cycle'' has been set to a value other than default) | (assuming ''duty_cycle'' has been set to a value other than default) | ||
| − | + | </p> | |
| − | a.) cycle the ringer switch from vibe to ring and back (or just set to vibe if already on ring) | + | <p> |
| − | b.) open/adjust ringer volume via '''Sounds and Ringtones''' application | + | a.) cycle the ringer switch from vibe to ring and back (or just set to vibe if already on ring)<br> |
| − | c.) Luna restart | + | b.) open/adjust ringer volume via '''Sounds and Ringtones''' application<br> |
| − | d.) Java Services Restart | + | c.) Luna restart<br> |
| − | + | d.) Java Services Restart<br> | |
| − | + | e.) Any system initiated event (as in receiving a text message or inbound call - any event calling for an alert)<br> | |
| − | Each action will affect a duty_cycle value reset to the default 99. | + | e.) Device restart<br><br>Essentially, any event not engaged through terminal command. |
| + | </p> | ||
| + | <p> | ||
| + | Each action will affect a ''duty_cycle'' value reset to the default 99. | ||
| + | </p> | ||
| + | <p>Such evidence leads me to conclude that ''duty_cycle'' manipulation via ''echo'' interface functions as a conditional on/off switch rather than a permanent data point and is of little practical value otherwise. However, in observation of the proclivity for webOS to retain a default ''duty_cycle'' value under a multitude of varying conditions, one might speculate that a singular data point of a more permanent nature exists. Further research toward the end of charge conservation via work load reduction at the vibration device node appears warranted.</p> | ||
Latest revision as of 19:37, 26 July 2010
My own research has offered certain different results than are identified in this article, and others which are not mentioned:
First, as of 1.4.1.1 the low threshold for perceptible vibration, whether charging or on battery power, is nearer to 17%, not 20% as stated.
Second, default duty_cycle is 99, not 50, and can be demonstrated through the following methods:
(assuming duty_cycle has been set to a value other than default)
a.) cycle the ringer switch from vibe to ring and back (or just set to vibe if already on ring)
b.) open/adjust ringer volume via Sounds and Ringtones application
c.) Luna restart
d.) Java Services Restart
e.) Any system initiated event (as in receiving a text message or inbound call - any event calling for an alert)
e.) Device restart
Essentially, any event not engaged through terminal command.
Each action will affect a duty_cycle value reset to the default 99.
Such evidence leads me to conclude that duty_cycle manipulation via echo interface functions as a conditional on/off switch rather than a permanent data point and is of little practical value otherwise. However, in observation of the proclivity for webOS to retain a default duty_cycle value under a multitude of varying conditions, one might speculate that a singular data point of a more permanent nature exists. Further research toward the end of charge conservation via work load reduction at the vibration device node appears warranted.