Tolriq

Again there is no need for the service to be foreground for 99% of the cases. So either we can have a default communication or most people will be rejected....

@joaomgcd I don't know Tasker internals but since tasker is foreground it can just bind to the service and do not have any limitation in times. The 5 second limit...

You are not forced to go full bind and aidl :) You can just cheat the system. You bind to the service without anything special or calls to the service...

I can try tomorrow but I'm not an advanced Tasker user. So not sure I'll be able to test all. A part of the plugin export state I don't even...

@joaomgcd So tested with the hasToRunServicesInForeground to false and removing the FGS type from manifest to be sure and it does not crash and the simple commands like playpause works...

Yes and it crashed before I added the fgs types.

It will probably require some coordination between the lib and tasker to ensure no issue. If the library is updated to remove the fgs type we need to check that...

What I meant is if I update Yatse with a new lib that have the tag and no more FGS type. But the user on his phone still have an...

If tasker always startforeground calls and it's not the plugin doing something then there's not much. Only solution is to add a way to check tasker version in the library,...

Jumping in, but being able to keep the parsing but skip bitmaps would still be a nice addition. Until https://github.com/androidx/media/issues/418 the parsing can be useful for replay gains for example,...