I seem fated to be finding workarounds for broken things. I've posted before about the gravity sensor that doesn't work with events only states.

Here's a profile+task with a logcat entry created by rotating the phone from face up to standing up. I filtered on an innocuous Sensor event.

This churns out the gravity sensor readings at about one per second. It might be enough to fake a gravity sensor event.

If you have any insight into what this is really doing, please tell.

Profile: Sensor Voodoo Event: Logcat Entry [ Output Variables:* Component:SensorsHub Filter:batch: handle=27 period=100000000 timeout=0 Grep Filter (Check Help):Off ] Enter Task: Gravity_Sensor A1: Test Sensor [ Type: Samsung Gravity Sensor Timeout (Seconds): 30 ] A2: Flash [ Text: %as_values() %lc_text Long: On Continue Task Immediately: On Dismiss On Click: On ]