Hello,
I’m a developer for MPDroid and I need a little information. Got a user who is having problems connecting to Volumio with the new version of MPDroid. Fine, but testing using virtualization is a pretty high bar, is that all there is? Or maybe I need to break down and buy a RaspPi 
Alternatively, Is there a diff between MPD and the MPD implementation used in Volumio, or is it kept stock to the standard implementation?
For me on latest volumio and MPDroid everything is ok, no problems at all.
Welcome avuton and kudos for mpdroid!
The issue that has been reported is probably related to a bug in Volumio which came with default mpd.conf (where bind to address field doesn’t allow mpdroid to connect). This issue has been solved.
Here is custom mpd.conf in Volumio:
###################################
# Auto generated mpd.conf file
# please DO NOT edit it manually!
# Use player-UI MPD config section
###################################
follow_outside_symlinks "yes"
follow_inside_symlinks "yes"
db_file "/var/lib/mpd/tag_cache"
sticker_file "/var/lib/mpd/sticker.sql"
log_file "/var/log/mpd/mpd.log"
pid_file "/var/run/mpd/pid"
music_directory "/var/lib/mpd/music"
playlist_directory "/var/lib/mpd/playlists"
state_file "/var/lib/mpd/state"
user "mpd"
bind_to_address "any"
port "6600"
zeroconf_enabled "yes"
zeroconf_name "volumio"
samplerate_converter "Fastest Sinc Interpolator"
volume_normalization "no"
audio_buffer_size "2048"
buffer_before_play "20%"
filesystem_charset "UTF-8"
id3v1_encoding "UTF-8"
gapless_mp3_playback "yes"
auto_update "no"
group "audio"
max_connections "20"
decoder {
plugin "ffmpeg"
enabled "yes"
}
input {
plugin "curl"
}
audio_output {
type "alsa"
name "Output"
device "hw:3,0"
mixer_control "PCM"
mixer_device "hw:3"
mixer_index "0"
dop "no"
}
If you need additional info let me know!