MediaMonkey forum

Hi,
When I go to ☰ -> Options -> General I get these options in 1061


After I tap on allow MediaMonkey to run in background I get prompt to allow that.

Peke wrote: ↑Sun Jan 22, 2023 12:38 pm Hi,
When I go to ☰ -> Options -> General I get these options in 1061


After I tap on allow MediaMonkey to run in background I get prompt to allow that.

Very strange. I have 1061 also but nothing about battery or background use. Just the crash log option.

Very strange. I have 1061 also but nothing about battery or background use. Just the crash log option.

That's because the current implementation removes the battery-de-optimization option if MMA is already set to 'unrestricted' in Android's battery options. We're aware that this isn't the most user-friendly approach and plan to improve on it

-Rusty

rusty wrote: ↑Sun Jan 22, 2023 9:52 pm

Very strange. I have 1061 also but nothing about battery or background use. Just the crash log option.

That's because the current implementation removes the battery-de-optimization option if MMA is already set to 'unrestricted' in Android's battery options. We're aware that this isn't the most user-friendly approach and plan to improve on it

-Rusty

Thanks. So does this mean MMA "thinks" it's already set to unrestricted? This is confusing because as I noted in an earlier post though, I can't seem to apply unrestricted settings to MMA the Android settings. Also, if true, it would mean there must be a different cause of the sync problem than the "timeout" idea suggested in an earlier post.

Let me know what you think. Thanks

What does Android show when you Tap-hold on the MMA icon > Tap 'i' > Tap 'Battery' ? (it should indicate whether MMA is Unrestricted / Optimized / Restricted).

-Rusty

rusty wrote: ↑Mon Jan 23, 2023 2:17 am What does Android show when you Tap-hold on the MMA icon > Tap 'i' > Tap 'Battery' ? (it should indicate whether MMA is Unrestricted / Optimized / Restricted).

-Rusty

Thanks. On the final screen there the "allow background activity" toggle is greyed out so I can't change it but it reads "background battery usage can't be restricted". Below that, the "optimize battery usage" setting reads "not optimized".

Hope that helps, thanks!

It tells us that the connection timeout is occurring for some reason other than this setting.

One other possibility: Samsung devices have a 'Power saving' tile in quick settings. Is that enabled?

-Rusty

rusty wrote: ↑Tue Jan 24, 2023 8:47 pm It tells us that the connection timeout is occurring for some reason other than this setting.

One other possibility: Samsung devices have a 'Power saving' tile in quick settings. Is that enabled?

-Rusty

No that setting is not enabled. Although, under device care>battery>power mode, the setting is "optimized" but as far as I can tell that is mostly dealing with screen brightness.

For what it's worth, I don't think I've ever changed the power settings and wasn't having this problem with MMA 1, and I don't have trouble with other apps continuing to function in the "background" or when the screen times out. This may not be related though.

Thanks

latest wifi sync fail debug log 6PWTL6NMMS

Version 1063

Wifi sync fail debug log 8PTP2BSZIW

Version 1066

Thanks! We still plan on looking into this.

-Rusty

Debug log 4ZP19BF9WS

Version 2.0.0.1070

The info on fixes for this version indicated failed downloads and sync failure would be addressed with this version. Was that supposed to address the problem I've been reporting here?

Hi,
2.0.0.1071 should be also available (as soon as Google authorize it), which have further optimization and fixes, along additional logged info in case of persisting issues like yours.

Would be great if you can generate new log using that version.

Peke wrote: ↑Sat Mar 04, 2023 8:08 am Hi,
2.0.0.1071 should be also available (as soon as Google authorize it), which have further optimization and fixes, along additional logged info in case of persisting issues like yours.

Would be great if you can generate new log using that version.

Hi, thanks. Will do.

Debug log ID LXK99PGVQ9

Version 1071

I think it went on for the longest time yet this time and I started to think the issue was resolved. It downloaded about 460 tacks but did crash eventually.