Dear Adrianbaugh,
thanks for notifying me such UI issue.
I will check as soon as I can and I will let you know if something is wrong in the code.
Hi Gamephate,
could you please send me a zip file containing a folder and a file with Chinese or Japanese characters? I will try to check and solve also this.
I suspect it’s due to the fonts I’m using not containing such characters; but I need to check with proper files/Folders.
Thanks guys I appreciate a lot your comments and the fact you are using this App. It means it seems useful for you!
after updating to Volumio 1.5 I have to admit that the app keeps constantly crashing.
This happens always when I access the database if it does not crash right away it shows "Empty Folder " ( on my Nexus 5 )
On the Nexus 7 with CyanogenMod 11 it crashes whenever I try to access the database.
Great if it would be possible to reset the configuration per room ( or device) in the near future. I would also perhaps introduce a kind of “global” settings tab valid for all rooms/devices ( e.g. the NAS part should be global ).
A good feature would be a “party group” … select some devces, group them and then let them all play the same.
Hi Torsten,
I need to update app to support fully Volumio 1.5.
There some changes on v1.5 that needs also app changes. I need some free time for coding
About the Global part: if you go on menu of rooms screen you can find an “add NAS” function that is global.
About reset config for single room I will think about it. Thanks for the suggestion!
that sounds reasonable … and I finally found the global settings
Another: I run two WLAN at home ( just because on different floors ) they are in one LAN but i looks like that the APP struggles a little when I roam between the WLANs with the Nexus ( I will have to have a deeper look into that before I “complain” )
Hi Michelangelo,
I just had possibility to have a quick view to the new v1.5. Very interesting updates…
I would just ask you if possible to bind mpd to all addresses and not only to “localhost” into mpd.conf.
Currently it seems the mpd service is bind only to localhost and this will not permit to connect to any PC or phone client.
Is it possible?
In the meantime I saw new MPD version changed the format of some outputs so I need to change the client to fully support new MPD and so new Volumio v1.5
Currently I need to inform Sound@home APP (until v2.4) supports VOLUMIO v1.4 and not yet above.
I will improve that as soon as I will have time
Hi All,
new version of sound@home v2.5 has been released on Google Play.
It now supports Volumio OS v1.5 but please remember you need to modify mpd.conf file on Volumio OS v1.5 to let any MPD client to connect to Volumio:
etc/mpd.conf
bind_to_addres “localhost” --> needs to be --> bind_to_addres “any”
Thanks for all the hard work on sound@home, I have been using it with an older version of Volumio for a while but have just upgraded to Volumio 1.5.
However I don’t understand how I’m meant to modify the mpd.conf file, where do I find this, is it within the files on the memory card or do I do it through the web app?
Hi benwhite89,
You need to use ssh connection with a PC to Volumio and access to Volumio folders.
In the folder /etc/ you will find the file mpd.conf to be modified.
Thanks for the reply, have managed to get into the right bit, but it was already the right setting “all” so didn’t have to change anything after all.
One more quick question, does the latest version support the spotify player in Volumio 1.5? I only seem to be able to change the volume when playing from spotify through volumio.
Just to confirm the UI problem reported by Adrianbaugh. (Using latest Volumio and Sound@home versions here)
I too am experiencing this with the buttons missing at the bottom of the screen.(Worst in landscape mode.)
I have an android ‘Galaxy Young’ phone.
The UI does not seem to be scaling correctly and perhaps this is most noticeable with lower resolution devices…?
Hi bobdbob,
Unfortunately sound@home doesn’t support ldpi and mdpi phone resolution models.
In case of Adrianbaugh it was different case since his phone is hdpi resolution and it is supported by sound@home.
ldpi and mdpi models are not supported since the screen is too small and putting all player nedded stuff there will result in a non usable application.
Sorry for that but this is an application design decision.
Maybe in the future we will try to find time to have totally different UI for ldpi and mdpi device in order to support also them.
Hi Digx!
Since I update Volumio and Sound@home, got the following problem :
In the database, if there is a accented character in the artist name (à or é used in France) no songs appears when I click on the name of the artist ( as if it was empty).
If for a artist without accented character I select a song with a accented character name , I 've got the message “error connecting device”.
If I use the web UI from Volumio, no problem.
If I use a mpd client no problem.
It was ok some previous version ( I can’t tell you which one exactly).
That 's it
Thank you!
Hi balbuze,
thanks so much for such feedback.
Let me try to better understand the problem so I can try to solve it.
First case:
Do you mean the artist name with accented character is visible as artist in the “Artsists” database view? Is it visible with correct accented character?
But when you select it you have empty list of songs associated to this artist right?
Second case:
When you select an artist in the “Artists” view you can see a list of the songs of such artist; but if you select a song with accented character it cannot be played since “error connecting device” is shown right?
Digx,
For the first case, I use the file mode. So I can see the artist name with wrong caracters (please see picture) 3rd line. But if I select no files appears.
Second case, with other artist ( without special caracters) I see all songs, but if I select one with special caracters (see picture 2), I ve got the message : “error connecting to the device”.
Hope it’s clearest… Tell me if you need other explanations
Regards
Hmmm, hdpi,mdpi,ldpi ??? my device is 320 x 480 pixels (HVGA) what does that equate to…?
The Sound@home app displays 95% in portrait mode and it is just the lower transport icons that are showing only their topmost with the rest of the icon not visible. I can still use them (just) . All other functions work fine.
In landscape mode the transport icons work and are visible but now are above the play-mode icons which don’t work.
By rotating the phone I can access all options at some point using both orientations but not all icons are available in a single orientation.
My screeshots seem the same as Adrianbaugh.
Hi bobdbob,
it’s quite a technical point however I will try to explain you.
Mainly there are many UI developer should prepare, one for each resolution (ldpi - mdpi - hdpi - xhdpi etc…).
UI is not impacting functionalies but just how the screen is presented on different Android phones with different screens.
Android try to resize automatically the UI for some density if not explicitly programmed by the developper but error can happens.
Coming to Sound@home case: the ldpi and mdpi reolution UI are not supported, that means if you install the application on a ldpi or mdpi phone the UI is presented as resiozed fromAndroid automatically but it will not fit exactly the screen in the right way.
Your phone is ldpi phone (small resolution) and it is not supported by sound@home currently.
Thank you. Yes that explains it. I have also researched the android developer pages and while most of it was way over my head I grasped the basics as you have outlined.
One day in the future I look forward to a version suitable for my device.
Meantime, as I noted earlier, the app is useable on my device and I am able to access all functions.
I just have to switch between portrait and landscape to access the icons that are needed.
So far it is running smoothly in all respects otherwise.
Thank you for your continued developement and patience
Hi bobdbob,
happy to see the app is working smoothly.
If you could post screenshot for portrait and landscape screen of your phone I can try to check what I can do.