Hall Sensor

roadman666

New member
Hi

my s10 got a custom rom and, for whatever reason, hall sensor based flip cover doesnt initiate any screen on/off actions. And than microdroid came to my mind.

Following logcat entries have been identified

04-14 21:48:57.277 0 0 I : [1: kworker/1:0: 2269] [keys] flip_cover_work flip_status : 1 (open)
04-14 21:49:19.623 0 0 I : [3: kworker/3:1: 869] [keys] flip_cover_work flip_status : 0 (close)

So I have tried using e.g. *flip_status : 0* and *flip_status : 1* as a trigger - it works!!!!

Alternatively I could jump on these entries:
04-14 21:58:12.530 0 0 I : [1: HubConnection: 5653] [SSP] send_hall_ic_status HALL IC ON/OFF, 1 enabled 0
04-14 21:58:13.718 0 0 I : [3: HubConnection: 5653] [SSP] send_hall_ic_status HALL IC ON/OFF, 1 enabled 1

But of course it would be much more elegant to just select the hall sensor in the sensor list :)

Whatever your decision will be, great work you guys are doing!!!!!
Thanks
 

FrameXX

Well-known member
I recently noticed logcat trigger slowing down MacroDroid extremely. I hope it works without problems for you. I already reported it.
 

roadman666

New member
I didn't realize any "measurable" effect till now, neither on battery consumption, nor on device speed as such. And as these 2 sceanrios are two only in microdroid till now - also not on the app performance as such.
 

roadman666

New member
Ok, some expriences gathered. Logcat triggers are quite unreliable. And its not because of the way MD handles them. Seemingly some messages are surpressed, for whatever reasons. Therefore my feature request remains relevant to me ;-) Am I the one only? :) Thanks guys!
 
Top