It's fixed with 701 for me.

On the About screen in MMA you can enroll in the beta program.

I am also experiencing this issue. I still have 6.9.4. Trying to figure out how I get involved in beta. Don't see anything regarding beta in the Play Store at this time, but I may not know where to look.

699 is better than 694, but it is still draining the battery for me too.
Overnight, with the phone unplugged for 14h, the battery is down to 77% while it's usually ~90%. MMA has been awake for 7h.

Logs: ZPPGV46RK4
Phone Galaxy S6
Android 6.0.1

[quote="martin.bohac"]... Did you use AndroidWear?[/quote]
Yes, I'm using a moto 360 2nd.edition.The wear song navigation is shown on clock during playback but when I close mediamonkey the control on clock disappears.

So from "user side" mediamonkey is closed.

Listened to music yesterday (Chromecast)
Stopped by Pausing, doing "Stop Casting", Hitting "Stop" in the notification and closing MMA from recent apps
Charged Phone to 100% - left it on table overnight not in use at all
Woke up to phone at ~85% battery - it's usually at ~96%
This is about 5h and 20m after the phone was taken off the charger:
[img]http://i.thinimg.com/img/l7s.png[/img]

LOG: ZVZRUDEW2G

MMA vers .0669
Galaxy S8
Android 7.0

I have the same issue, running MMA build 699 (beta) on a Galaxy S8 using Android 7.0.

See debug log ID UX3A9H9AXU.

According to the battery tab on settings, I have had the phone on for over 27 hours. The use details for MMA show CPU total 2h 45m 9s, Stay Awake 8h 15m 34s, computed power usage 268 mAh.

Thanks for your help!!

From the log I can see client com.google.android.wearable.app is binded to MMA (it means browsing tracks from AndroidWear). Until the client is binded,playback service can't be destroyed and stays awake.
Did you use AndroidWear?

Uploaded log "ZDUSDY21ZP"

1) Listened to music yesterday evening.
2) Music stopped by themself (last tracked finished)
3) Closed mediamonkey over "Taskmanager / close all apps" (Samsung S7 Edge)
4) 1h40 after charging mediamonkey already used 1% of battery, CPU 14m58s, CPU foreground 18s, Stay awake 55m18s, received 1068 bytes over WLAN, send 1921 bytes over WLAN, used battery 53mAh.

Can it be, that some "upnp stuff" ist running in background?

Yes, from About screen when you're seeing this.

Do you have Crossfade enabled?

I've the same problem, that 695 keeps sometimes running "in the backgound". After some hours it's the highest consumer of current. Only a "force close" solves it.

A solution would be fine - could a debug log help in that case? If yes, how to make one... Never made it... :-?

Gerd

Yes, if issue persists in some cases, debug log would be useful.

[quote="Peke"]Try to use latest MMA version and if it still happens and you are sure that MMA was not closed Send us log and write its ID here so that we can tweak if needed.[/quote]
This is from when I woke up after 5 hours 51 minutes of the phone not being in use and off the charger overnight, after doing a "Close All" programs before bed...
[img]http://i.magaimg.net/img/ifb.png[/img]

Version is 695.

I've restarted the phone since, but I'll send a log next time I notice it.

I can confirm that 695 is working as expected. Thanks for your excellent support!

/Tomas

Try to use latest MMA version and if it still happens and you are sure that MMA was not closed Send us log and write its ID here so that we can tweak if needed.