rusty wrote: ↑Mon Aug 04, 2025 8:40 am The betas rollout gradually--now to about 80% of users.

Thanks, Rusty, I'll reply again when I've received the update.

The betas rollout gradually--now to about 80% of users.

Thanks!

-Rusty

rusty wrote: ↑Fri Aug 01, 2025 6:12 pm To update immediately, go to MediaMonkey in the Play store and tap 'Update'.

It doesn't appear to have rolled out to me yet because 2.1.0.1264 isn't available. Google Play says I'm a beta tester but still shows the latest version as the one I already have installed - 2.0.6.1252.

Hi,

To test MediaMonkey beta builds:
- in MMA, tap Options > About | Register for test builds.
- if you don't have MMA installed, register directly via Google Play at: https://play.google.com/apps/testing/co ... ediamonkey

Once registered, your next update will be to the current MMA beta. To update immediately, go to MediaMonkey in the Play store and tap 'Update'.

Regards,
Rusty

If you're serious about music...
http://www.mediamonkey.com

rusty wrote: ↑Fri Aug 01, 2025 11:59 am Unfortunately, it looks like the detailed log attachment didn't make it through due to a problem on our end with log limits. We're going to make some changes to logging in the next beta to solve this, but in the meantime, can you let me know if 1264 solves this issue?

-Rusty

Thanks, Rusty, I'll let you know

rusty wrote: ↑Fri Aug 01, 2025 10:58 am Can you also try out 2.1.0.1264

Happy to try that, Rusty. Where do I get that version from?

Unfortunately, it looks like the detailed log attachment didn't make it through due to a problem on our end with log limits. We're going to make some changes to logging in the next beta to solve this, but in the meantime, can you let me know if 1264 solves this issue?

-Rusty

Hi Kiwichick,

Received--thanks! And looking into it.

Can you also try out 2.1.0.1264--it includes a new audio engine and may fix this as well.

Thanks!

-Rusty

rusty wrote: ↑Mon Jul 21, 2025 3:32 pm share the log ID here right after this occurs

Hi Rusty, did you get the logs?

rusty wrote: ↑Mon Jul 21, 2025 3:32 pm Hi KiwiChick,

I'm not seeing this with an S24. Would you mind submitting a debug log (via MMA > Help > Send logs) and share the log ID here right after this occurs?

Thanks!

-Rusty

Thanks, Rusty. Log ID: 5RG8GAL7MC. Sorry, it may come through twice because I forgot to get the log ID the first time

Hi KiwiChick,

I'm not seeing this with an S24. Would you mind submitting a debug log (via MMA > Help > Send logs) and share the log ID here right after this occurs?

Thanks!

-Rusty

MMA v2.0.6.1252
Phone: Samsung S21 FE - Android 14
Bluetooth device: JVC Media Receiver KD-X482BT

I don't have any 'Resume play on connection' settings enabled in MMA. 'Always respond to remote buttons' is turned off. The media receiver doesn't have an auto-play feature. It does have an auto-reconnect feature which is turned off but MMA still resumes playing when I connect manually my phone to it. I don't know if it's MMA or the receiver that's ignoring the settings but it doesn't happen when I use the Samsung Music app with 'Allow external devices to start playback' turned off. I have tried clearing cache, clearing data and re-installing MMA but it still resumes playing.