Hi! If we want to really embrace using the vibrator for haptic feedback, then I certainly think it would be good to have a way to configure it with different patterns by indices. I wonder how much you think the approach of using the vibrator is really worth though -- the current generic implementation is only done for long presses, where accuracy is really not needed at all. However, when we use it for example in the keyboard on some devices the vibrator is so "mushy" that the effect isn't really all that good.
As far as the timing, yes this definitely needs to be improved. I think your idea of being able to submit the pattern to the HAL layer for it to do the timing would be great. Even better, I think, would be to have a driver for this as you suggest, and just let each process open it and submit patterns to it. This would require that each process hold the vibrator permission though... we'd need to decide how much it is worth having that permission vs. having some other scheme for accessing the hardware. For example, an extravagant approach could be to have the driver keep track of each client, with the window manager able to tell it which of those is allowed to vibrate based on which ones have visible windows. The reason for the current routing through the window manager is that this allows the window manager to do just this kind of control, rejecting calls from windows that are not visible. (Plus it allows customization in the PhoneWindowManager, to use other hardware besides the vibrator that might be available for haptics.) But yeah, this is a pretty excessive amount of overhead just to do haptics. On Mon, May 11, 2009 at 8:44 PM, wen yi <wen...@gmail.com> wrote: > > Hello, > > In the new Cupcake release, APIs are added in the framework to > facilitate widget level haptics. The new design makes it easy to > implement haptics feedbacks consistent across applications from ISPs. > I especially liked the idea that the types of feedback are linked to > vibration patterns with an index. It is now possible to customize the > haptics patterns for use cases and hardwares. > > I am wondering if it is worthwhile to use a configuration file to map > the haptics index to vibration patterns. That setup allow customizing > of the patterns without changing code. > > I noticed that the timing control in the vibratePatther thread in > HardwareService.java sometimes is less than exact. Wondering if it > makes sense to move that logic into HAL or even device driver. > > It appears that View.performHapticFeedback() is merely routed through > WindowManagerService, PhonePolicyManager and to Vibrator. Functional > wide it sounds equivalent to calling Vibrator.vibratorPattern() > directly in View class. Wondering if new fucntionality will be added > on in future releases and what it will be. > > Thanks. > > - Wen > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
