10-17-2022, 01:19 PM
(10-17-2022, 12:38 PM)TheOldPresbyope Wrote:(10-17-2022, 09:42 AM)romain Wrote: I posted a comment on Google Play to point out the problem, below the reply of the developer:
"Hey Romain, the user agent header is not relevant. Interruptions are normally related to Android's 'app optimization' that reduces background apps like AirMusic. Please contact me at support@airmusic.app for help, it's normally easily solved. Cheers and kind regards."
I've sent him an email and will post the solution here if the problem is fixed.
Interesting. It’s not quite true that the header is irrelevant since we don’t know what the receiving app does or doesn’t do with it. Still, if he thinks the problem is easily solved then great. Does he happen to say that his app supports AirPlay 2?
Nice to see how responsive the AirMusic dev is, BTW.
Regards,
Kent
Kent, here's the follow up to my email:
"Hello Romain,
thanks for contacting me directly.
AirPlay2 should work fine too - AirMusic is used on many Homepods or Sonos for example without issues.
It might be possible that your AP2-device uses another Wifi-frequency than your AP1-device, or your AP1-device has a wired-connection?
On your Android, you might have a look at Android's "app optimization", it's a killer for background-apps like AirMusic:
https://dontkillmyapp.com/
If the problem persists, can you reproduce it, then open AirMusic's menu -> About AirMusic -> "Create & send logs"?
Maybe we can see something useful in the background :-)
Best regards from Germany / Mit freundlichen Grüßen,"
I'll send him the application log file when I'm back home in the evening