Difference between revisions of "Talk:OMAP vibration device"

From WebOS Internals
Jump to navigation Jump to search
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.
+
<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>
 +
<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>
Second, default ''duty_cycle'' is not 50, it is 99, and can be demonstrated through the following methods:
+
<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>
[e.) Phone restart]
+
d.) Java Services Restart<br>
 
+
e.) Any carrier initiated event (as in receiving a text message or inbound call)<br>
 +
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.
 
Each action will affect a duty_cycle value reset to the default 99.
 +
</p>

Revision as of 19:13, 26 July 2010

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.

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 carrier initiated event (as in receiving a text message or inbound call)
e.) Device restart

Essentially, any event not engaged through terminal command.

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