Talk:OMAP vibration device - Revision history

Jnever1 at 18:37, 26 July 2010

2010-07-26T18:37:03Z

Jnever1 at 18:36, 26 July 2010

2010-07-26T18:36:14Z

Jnever1 at 18:34, 26 July 2010

2010-07-26T18:34:57Z

Jnever1 at 18:33, 26 July 2010

2010-07-26T18:33:47Z

Jnever1: Personal research demonstrates different results than those presented in article

2010-07-26T18:23:34Z

Personal research demonstrates different results than those presented in article

Jnever1 at 18:13, 26 July 2010

2010-07-26T18:13:15Z

Jnever1 at 16:07, 25 July 2010

2010-07-25T16:07:48Z

Jnever1: Personal research demonstrates different results than those presented in article

2010-07-25T15:47:16Z

Personal research demonstrates different results than those presented in article

New page

I mean to make of myself no linux afficionado in so posting but 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 roughly 17%, not 20% as stated.

Second, default ''duty_cycle'' is not 50, it is 99, 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.) Phone restart]

Each action will affect a duty_cycle value reset to the default 99.

@@ Line 19: / Line 19: @@
 </p>
 <p>
-Each action will affect a duty_cycle value reset to the default 99.
+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 ends of charge conservation via work load reduction at the vibration device node appears warranted.</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>

@@ Line 21: / Line 21: @@
 Each action will affect a duty_cycle value reset to the default 99.
 </p>
-<p>This 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 ends of charge conservation via work load reduction at the vibration device node appears warranted.</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 ends of charge conservation via work load reduction at the vibration device node appears warranted.</p>

@@ Line 21: / Line 21: @@
 Each action will affect a duty_cycle value reset to the default 99.
 </p>
-<p>This 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 ends of charge conservation via work load reduction at the vibration device node apears waranted.</p>
+<p>This 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 ends of charge conservation via work load reduction at the vibration device node appears warranted.</p>

@@ Line 1: / Line 1: @@
-<p>I mean to make of myself no Linux aficionado in so posting but my own research has offered certain different results than are identified in this article, and others which are not mentioned.
+<p>My own research has offered certain different results than are identified in this article, and others which are not mentioned:
 </p>
 <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.
+'''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.
 </p>
 <p>
-Second, default ''duty_cycle'' is 99, not 50, and can be demonstrated through the following methods:
+'''Second''', default ''duty_cycle'' is 99, not 50, and can be demonstrated through the following methods:
 </p>
 <p>
@@ Line 21: / Line 21: @@
 Each action will affect a duty_cycle value reset to the default 99.
 </p>
-<p>This 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 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 suspect a singular data point of a more permanent nature to exist.</p>
+<p>This 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 ends of charge conservation via work load reduction at the vibration device node apears waranted.</p>

@@ Line 15: / Line 15: @@
 c.) Luna restart<br>
 d.) Java Services Restart<br>
-e.) Any carrier initiated event (as in receiving a text message or inbound call)<br>
+e.) Any system initiated event (as in receiving a text message or inbound call - any event calling for an alert)<br>
 e.) Device restart<br><br>Essentially, any event not engaged through terminal command.
 </p>
@@ Line 21: / Line 21: @@
 Each action will affect a duty_cycle value reset to the default 99.
 </p>

@@ Line 1: / Line 1: @@
 I mean to make of myself no linux afficionado in so posting but 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 roughly 17%, not 20% as stated.
+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, it is 99, and can be demonstrated through the following methods: