https://bugs.kde.org/show_bug.cgi?id=404576
--- Comment #2 from major-ma...@t-online.de --- Unfortunately, I am not an Android developer, but I found a discussion that seems to be interesting regarding this use case: https://issuetracker.google.com/issues/201546605 Especially the one quote from a Google dev seems promising: "For Cast-like use cases (but using some other non-Cast protocol, for example DIAL), we would still expect apps to integrate with MediaRouteProvider/MediaRouter, which should be sufficient for volume button clicks to be delivered." (https://issuetracker.google.com/issues/201546605#comment156) He is probably referring to: https://developer.android.com/media/routing/mediarouteprovider And I also found this demo project, that seems to be using a different (undocumented) approach: https://github.com/oliverClimbs/VolumeButtonDemo Request to make this API official: https://issuetracker.google.com/issues/333967641 Maybe also interesting: https://stackoverflow.com/questions/11318933/listen-to-volume-changes-events-on-android I would really appreciate hearing getting feedback on these approaches. -- You are receiving this mail because: You are watching all bug changes.
