andrewilley Posted October 4, 2021 Share Posted October 4, 2021 @rg94130 To check if this is the Google app bug, roll the 'Google' app back to original defaults and see if that corrects the problem. Unfortunately it will update itself automatically fairly soon, but you can check if that's the issue anyway. Andre Link to comment Share on other sites More sharing options...
Amitoj Singh Posted December 17, 2021 Share Posted December 17, 2021 Simply enable Show On Lock Screen in PA Settings within Lock Screen. The earphone remote buttons will start working properly. Link to comment Share on other sites More sharing options...
andrewilley Posted December 17, 2021 Share Posted December 17, 2021 @Amitoj Singh Show on Lock Screen is a visual thing, the wired or BT headset buttons should work whether you have this enabled or not. Andre Link to comment Share on other sites More sharing options...
Rachidulric Posted December 13, 2023 Share Posted December 13, 2023 Samsung A54, running on Android 14, worked sometimes but it's not working now. Long press to skip works correctly. Here's the log: ================== 16:19:51.537 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_DOWN name=TTGK Technology USB-C Audio Consumer Control source=0x101 sources=0x6103 virt=false repeat=0 actionTime=1421060 sourcePak=android flags=0x8 playerState=1 ================== 16:19:51.538 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_UP name=TTGK Technology USB-C Audio Consumer Control source=0x101 sources=0x6103 virt=false repeat=0 actionTime=1421065 sourcePak=android flags=0x8 playerState=1 ================== 16:19:52.157 PlayerService TOGGLE_PLAY_PAUSE from PSMediaButtonReceiver pausePlaying ================== 16:19:53.319 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_DOWN name=TTGK Technology USB-C Audio Consumer Control source=0x101 sources=0x6103 virt=false repeat=0 actionTime=1422845 sourcePak=android flags=0x8 playerState=2 ================== 16:19:53.325 PlayerService RESUME from PSMediaButtonReceiver resumePlaying ================== 16:19:53.337 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_UP name=TTGK Technology USB-C Audio Consumer Control source=0x101 sources=0x6103 virt=false repeat=0 actionTime=1422850 sourcePak=android flags= 0x8 playerState=2 Link to comment Share on other sites More sharing options...
maxmp Posted December 13, 2023 Share Posted December 13, 2023 @Rachidulric thanks for log, but no double press there. Double press is 2 presses within 600ms, while from your log these are two presses within 1.8 sec. Link to comment Share on other sites More sharing options...
andrewilley Posted December 13, 2023 Share Posted December 13, 2023 I also suspect the device issuing the button presses might be reinterpreting them too, and transmitting its own variations. In your example, the first BUTTON_DOWN event (button has been pressed) and its following BUTTON_UP event (button has been released) are far too close together for human dexterity - just 1ms apart. 16:19:51.537 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_DOWN 16:19:51.538 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_UP Andre Link to comment Share on other sites More sharing options...
Rachidulric Posted December 14, 2023 Share Posted December 14, 2023 18 hours ago, andrewilley said: I also suspect the device issuing the button presses might be reinterpreting them too, and transmitting its own variations. In your example, the first BUTTON_DOWN event (button has been pressed) and its following BUTTON_UP event (button has been released) are far too close together for human dexterity - just 1ms apart. 16:19:51.537 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_DOWN 16:19:51.538 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY_PAUSE ACTION_UP Andre Hey, my phone somehow activated the "ignore repeated presses" by itself lol, disabled it and the double skip works again. Link to comment Share on other sites More sharing options...
andrewilley Posted December 14, 2023 Share Posted December 14, 2023 @Rachidulric Great, glad you got it sorted. I rather suspected the headphones were applying some sort of logic of their own to the button events. Andre Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now