d10bfe185c336d813845c9beb1f4041c5daa1669 |
|
14-Dec-2010 |
Jeff Brown <jeffbrown@google.com> |
Improve documentation on Vibrator.vibrate. Bug: 3135537 Change-Id: I961e32990d754dc6b5f86ffea8515685f8ade40f
/frameworks/base/core/java/android/os/Vibrator.java
|
ea9020e0854427d47e566a1394df6749f3265410 |
|
04-Nov-2010 |
Dianne Hackborn <hackbod@google.com> |
Add API to find out if there is a vibrator. Change-Id: If29f6ee19448222433cad9fad325d0095a8e5737
/frameworks/base/core/java/android/os/Vibrator.java
|
26e9cf38b229b738b4e56c3e08be82a9c0f11e64 |
|
19-Oct-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Fix Vibrator permission CTS test broken earlier. Bug: 3106964 Change-Id: I76138780ac64f761fe09ef8ba74382c7ee05d794
/frameworks/base/core/java/android/os/Vibrator.java
|
e331644cb570e74a8739cb21ffcc5875663ffa58 |
|
15-Oct-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Don't crash on null Vibrator during reboot. Bug: 3099305 Change-Id: I9af126f7a719f36ae544f517a2fccd0d33339389
/frameworks/base/core/java/android/os/Vibrator.java
|
3a32213c4029a03fe39486f3d6ebd0ea18928ee1 |
|
24-Nov-2009 |
Mike Lockwood <lockwood@android.com> |
Remove HardwareService and move vibrator support to VibratorService. The lights support is only needed by PowerManagerService and NotificationManagerService, so we do not need a Binder API for it. Move backlight and notification light support to new LightsService class. The camera flash is now handled directly by the camera HAL, so the flash Hardware service flash support is obsolete. Change-Id: I086d681f54668e7f7de3e8b90df3de19d59833c5 Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/core/java/android/os/Vibrator.java
|
18dd5f0d25f1004e123dc265dc498a8bf8897af9 |
|
02-Jul-2009 |
Patrick Scott <phanna@android.com> |
Improve the Vibrator service by keeping track of multiple vibration requests. There are 2 types of vibrations: simple and repeated. Simple vibrations run for a given length of time while repeated patterns run until canceled or the calling process dies. If a vibration is currently running and another request is issued, the newer request always takes precedence unless the current vibration is a simple one and the time left is longer than the new request. If a repeating vibration is running and a new request overrides that vibration, the current vibration is pushed onto a stack. Once the new vibration completes, the previous vibration resumes. IBinder tokens are used to identify Vibration requests which means that multiple calls to Vibrator.vibrate with the same Vibrator object will override previous vibrations on that object.
/frameworks/base/core/java/android/os/Vibrator.java
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/os/Vibrator.java
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/os/Vibrator.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/os/Vibrator.java
|