If you look in the system log (logcat -b system
) it will show you the core system service's logs. The VibrateService only makes a couple in the latest version of Android, which will tell you what vibration pattern is being started. Unfortunately, it won't show you what UID/PID is responsible for the request. Beyond that, you may be able to find some information from the kernel by digging around to figure out which device interface (e.g. /dev/gpio1
) is the one used by the vibrator service. If that driver exposes some stats/debug on /proc
or debugfs
you might be able to figure out which process is responsible.