Hi Team,
I'm using MMW from a few years and set MMA as my default audio player on my phone.
I have even disabled 'Google Play Music' on phone.
I noticed this weird error where my Phone Audio Profile changes on opening MMA.
I set my phone in Vibrate mode always and on opening Media Monkey Android player, the Audio profile changes to General. After the current song completes and next song starts playing, The Audio profile changes to silent at times. This automatic change is profile is irritating me as I've missed a few calls and reminders just because the profile changed!
I have used the below devices from more than a year and I'm sure this error/bug is reproducible. Else I can share the screen recording via email.
Pixel 2 - Android Pie, Android 10
Nokia 8 - Android Oreo
Expecting this bug to be fixed soon!
I did try reaching to the email ID mentioned in Google Play Store - support@mediamonkey.com.
I received an automated response stating the email could not be delivered.
I also reviewed the product on Play Store and didn't get any response.
Android Phone Audio Profile Changes on Launching MMA [#16247]
Moderator: Gurus
-
- Posts: 12
- Joined: Wed Dec 11, 2019 2:24 pm
Re: Android Phone Audio Profile Changes on Launching MMA
Send a debug log from About in MMA when you experience this. You can open a Support Ticket (mediamonkey.com/support) with the logID's to be able to correspond with developers regarding this problem.
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
-
- Posts: 12
- Joined: Wed Dec 11, 2019 2:24 pm
Re: Android Phone Audio Profile Changes on Launching MMA
I missed the reply.
Sent the Log files - GN415P2FTM
Basically Phone was in Vibrate before app launch, Then it changed to Silent. I pressed Play and skipped a few tracks, So the audio profile changed to General and back to Silent.
Sent the Log files - GN415P2FTM
Basically Phone was in Vibrate before app launch, Then it changed to Silent. I pressed Play and skipped a few tracks, So the audio profile changed to General and back to Silent.
-
- Posts: 241
- Joined: Thu Nov 14, 2013 5:23 pm
Re: Android Phone Audio Profile Changes on Launching MMA
Hi thanks,
the issue is tracked as https://www.ventismedia.com/mantis/view.php?id=16247
the issue is tracked as https://www.ventismedia.com/mantis/view.php?id=16247
-
- Posts: 12
- Joined: Wed Dec 11, 2019 2:24 pm
Re: Android Phone Audio Profile Changes on Launching MMA [#16247]
Hello,
Any ETA on the bug fix ?
Any ETA on the bug fix ?
-
- Posts: 241
- Joined: Thu Nov 14, 2013 5:23 pm
Re: Android Phone Audio Profile Changes on Launching MMA [#16247]
Fixed in next build 1.3.7.904, coming published tomorrow.
-
- Posts: 12
- Joined: Wed Dec 11, 2019 2:24 pm
Re: Android Phone Audio Profile Changes on Launching MMA [#16247]
Hi,
It would be really helpful if the support ID is working. That's the default way of communication as many use Play store to install and read the updates of this app.
I get this response on sending a mail -
It would be really helpful if the support ID is working. That's the default way of communication as many use Play store to install and read the updates of this app.
"I did try reaching to the email ID mentioned in Google Play Store - support@mediamonkey.com.
I received an automated response stating the email could not be delivered.
I also reviewed the product on Play Store and didn't get any response."
I get this response on sending a mail -
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
support@mediamonkey.com
LMTP error after RCPT TO:<support@mediamonkey.com>:
552 5.2.2 <support@mediamonkey.com> Mailbox is full / Blocks limit exceeded / Inode limit exceeded
support-noreply@mediamonkey.com
(ultimately generated from support@mediamonkey.com)
LMTP error after RCPT TO:<support-noreply@mediamonkey.com>:
552 5.2.2 <support-noreply@mediamonkey.com> Mailbox is full / Blocks limit exceeded / Inode limit exceeded
Re: Android Phone Audio Profile Changes on Launching MMA [#16247]
Hi,
Due the increased number spam you can sometimes get such message. It is always suggested to submit support ticket at https://www.mediamonkey.com/support/ instead of direct mailing to us.
Due the increased number spam you can sometimes get such message. It is always suggested to submit support ticket at https://www.mediamonkey.com/support/ instead of direct mailing to us.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Re: Android Phone Audio Profile Changes on Launching MMA [#16247]
fyi, it's been published to the MediaMonkey for Android beta track (you have to register for betas on the play store via https://play.google.com/apps/testing/co ... ediamonkey ).
Re. the support address--I'll look into the problem--it's supposed to redirect you to our esupport system, but something's obviously gone wrong.
-Rusty
Re. the support address--I'll look into the problem--it's supposed to redirect you to our esupport system, but something's obviously gone wrong.
-Rusty
-
- Posts: 12
- Joined: Wed Dec 11, 2019 2:24 pm
Re: Android Phone Audio Profile Changes on Launching MMA [#16247]
Thanks a lot for the fix !
I checked the Beta version from Play Store on Android 10 - Pixel 2 device.
The audio profile is not changing on Opening the app / Changing tracks / Controlling media playback from bluetooth !
It was a really annoying bug. Thanks again
I checked the Beta version from Play Store on Android 10 - Pixel 2 device.
The audio profile is not changing on Opening the app / Changing tracks / Controlling media playback from bluetooth !
It was a really annoying bug. Thanks again