Hello everyone.

I try to figure how I can debug the vibration/haptic issues I have sometime and leads me to reboot my phone.

It appears to be triggered by various scenarios. Like few minutes ago, using "back gesture" multiples times in a row in Vanadium and boom haptic is out of order.

Sometimes I have the issue if there is an incoming call in regular Phone or other apps (like Molly, SimpleX and so on) and I am unlocking my phone by typing my pin (2FA activated or not). I feel the haptic when I press numbers and it vibrates during the same time and boom everything is shut off.
I want to add a precision about this, I do not type my pin to be able to answer phone calls, it is just coincident. Like you grab your phone in you pocket, you type your pin and someone in that precise window calls you.

I had the silent notification from Remote Attestation that triggered the issue few times so now I have set Auditor to vibrate when doing a remote push.

I had no problem since ages doing that.

I had the issue with another app I have set to silent/reduced notification.

I do not believe it is an hardware issue at all. It was even an upstream bug once. I haven't switched back on PixelOS on this 6a, but I have done it on another one that has the same issue and under PixelOS I am unable to trigger this behaviour at all.

Is anyone able to tell me in log viewer which info I should look at ? If I use the regular log level I have thousand of lines with vibrate=false when I look for "vibrate" in regex filter. Nothing in warn or error level.

I would like to help on this point but I must admit I am clueless. 🤔

I am on 2025021100.

I will greatly appreciate help, little or big, it is what it is and I will be glad 😎

I hope this helps in some way
I also use a P6a on 2025021100 and have haptics toggled on.
I tried replicating your fault ( back gesture in Vanadium) 8 times on three different occasions, but it did not manifest itself. I can only conclude that, if the back gestures work as intended without haptics toggled on, the motor (probably a solenoid of some description) in your 6a, has or is in the process of shaking itself or its solder connections to bits.

    area51

    It is not an issue with back gesture or vanadium at all.

    My thoughts are on an app that grab and hold the vibration motor and don't release it.

    I know that's not how it works under the hood but you catch my point.

    I have installed myself only 16 apps so I will sort this pretty quickly I guess. And not all 16 use notifications nor trigger vibrations

      19 days later

      Ok folks, after almost 20 days I believe I have found the root cause of my problems.

      Orbot is/was spamming notifications so much, that even with vibration disables for it, it "grabs" the haptic process and f*ck things up.

      I do not know the underlying function of that but I am pretty sure this is related.

      My logs are not full of useless lines regarding this.

      I would like to debug further but I don't know how to manage it.