@JonPike
Your item 1 has already been addressed. As an aside, I'd say breaking only the integrated BT functionality would be pretty hard to do.
As for item 2, I'd want to try some basic diagnostic tests before I reached for a soldering iron. No clue what "moderate force" means but it seems more likely you've damaged the uSD card. Can you burn plain Raspbian to a different uSD card, boot, and run programs? If so, your RPi is probably OK and you can install moOde on this card. As always, name-brand cards from a known source are highly recommended.
I've been abusing various models of RPi for years. My only hardware failure has been an Ethernet port which went dead on an RPi2B some years ago; no clue why. As for uSD card sockets, my particular problem used to be forgetting if it was the older push-push socket and yanking out the card. Didn't turn out to be fatal but I suppose one could damage the socket mechanically.
Regards,
Kent
I think what you are seeing here is the result of the responsive/adaptive design of the UI rather than differences between browsers. Tim and his boon companions (yay, @swizzle) are trying to shoehorn a lot of information into limited real estate on mobile devices and make it readable. Try selecting "Desktop site" in Android Chrome to see what I mean. In the past, I've mentioned a few quirks in PMs to Tim but I don't find them objectionable. Going between portrait and landscape modes is particularly vexsome given that the aspect ratios are different on different devices. (Take my old Nexus 7...please!)
I don't see a "lower half" artifact on my Nexus 6P phone or my Nexus 7 and Nexus 9 tablets.
I think there will always be minor issues because of the wide variations in screens on mobile devices. Think about the new generation of devices with "notched" displays. Another nightmare for app designers.
Regards,
Kent
@mikaella
Ok, but keep in mind that building 4.1 will require the same steps as building 4.0 so you'll have to master the process regardless. As well, Tim has said that "4.0 --> 4.1 will be an in-place update" so building 4.0 now is not wasted motion.
I highly recommend using the automated moOdeOS image builder.
@jonners' post just below yours (http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-post5375271.html) gives links to great instructions. Ignore the fact that both links are labeled "Moode Audio Player for Raspberry Pi"; just click on them.
Regards,
Kent
RPi revision codes
FYI,
I just came across a better reference to the RPi revision codes:
Raspberry Pi revision codes - Raspberry Pi Documentation
I expect this is the latest version of what Tim used to create getHdwrRev().
FYI,
I just came across a better reference to the RPi revision codes:
Raspberry Pi revision codes - Raspberry Pi Documentation
I expect this is the latest version of what Tim used to create getHdwrRev().
Last edited:
Hi,
Assuming that the moOde 4.0 build that you made was successful i.e., on a fresh unmodified image the mosbrief log output showed END and the output of System info is error free, then below are some basic troubleshooting approaches:
Hardware
1. Using a fresh, unmodified image on a known good SDCard boot up a bare Pi-3B connected via Ethernet and not in an enclosure.
2. If it boots up and Nymeria, moode.local or ip_address brings up the UI then proceed to #3 below.
3. Menu, Configure, BLU to open the Bluetooth config screen and then just follow steps 1 and 2 in the instructions listed on the screen.
Software
In order to troubleshoot UI anomalies on devices I need (a) the screen height and width in pixels and (b) the exact device model. I can then recreate the resolution in a Safari viewport simulator and see how UI looks.
Firefox has been problematic in my experience so YMMV.
-Tim
I'm not sure what screen you are using but I'm not able to repro this on Pi Touch with Chrome overlay scrollbars enabled and running the new de-zoomed Pi Touch UI that will be part of upcoming moOde 4.1 release.
Hi,
Just a friendly reminder that the MoOde project needs your financial support in order to remain strong and to continue to provide technical support and troubleshooting, and to create these nice software releases that include support for the very latest Raspberry Pi system and audio technology
-Tim
Just a friendly reminder that the MoOde project needs your financial support in order to remain strong and to continue to provide technical support and troubleshooting, and to create these nice software releases that include support for the very latest Raspberry Pi system and audio technology
-Tim
Basically all. I’ve had no luck with dsf. I’m using a 502dac hat. Could it be my sound card needs to run in master mode or something? I noticed the pi cpu will heat up to 80+deg when playing dsf. Perhaps there’s some setting I can use to tame the beast?
There are unfortunately behavioral differences among the different browsers, and even between desktop and mobile versions of the same browser. Safari and Chrome are your best bets as far as compatibility though if there’s a reproducible bug we’ll definitely try to fix any problems regardless.
I haven’t seen that specifically but some weirdness undoubtedly happened with enabling .75 zoom on landscape mode for mobile devices, and while it lets more things fit on screen without much effort there are a lot of browser bugs that crop up. That experiment is over. There will eventually be new css checked into moode to accomplish basically the same thing, then we can get back to dealing with normal browser related “quirks”.
The landscape interface wasn’t ever really designed for a mobile screen size but the switch to responsive design made it possible. There are some hard coded values for things like modal heights that might cause problems if you use your phone in landscape mode exclusively. I have code somewhere that fixes the modal height on mobile landscape thing but I’m not sure that ever made it to Tim (reconciling differences between different versions of the code is non-trivial for Tim as he has to review everything to make sure nothing else breaks, etc.)
It would, but I'd have a long, dongally thing hanging off my case. Idea getting the slick Allo case was to have a nice compact package. In real life it does look slick, but with the flanges is bigger than it has to be, then there's the assembly/tweezers SD card thing. I was spoiled by the one thumbnail removal process on my original standard case. Grump mode off...
OTOH, thanks for letting me know about that cable extended socket. For embedded projects, I'd probably want to have a slot somewhere accessible for the card, without taking things apart, that's a nice option to know about.
Hi,
finally i got it work.....
now i want to add my nas it has ip address 192.168.1.157
nas synology the music in on the map public
no user id or password
please help me out
see
NAS Source
REMOVE this NAS source
MPD database update starts automatically after saving.
Settings SAVE Cancel
Mount error: Click to view moode.log for message text.
Source name
SONOS
Fileshare protocol
SMB/CIFS
Host or IP address
192.168.1.157
Remote directory
sonos/public
User id
Password
Advanced
Charset
UTF8 (default)
Rsize
61440
Wsize
65536
Mount flags
ro,dir_mode=0777,file_mode=0777
finally i got it work.....
now i want to add my nas it has ip address 192.168.1.157
nas synology the music in on the map public
no user id or password
please help me out
see
NAS Source
REMOVE this NAS source
MPD database update starts automatically after saving.
Settings SAVE Cancel
Mount error: Click to view moode.log for message text.
Source name
SONOS
Fileshare protocol
SMB/CIFS
Host or IP address
192.168.1.157
Remote directory
sonos/public
User id
Password
Advanced
Charset
UTF8 (default)
Rsize
61440
Wsize
65536
Mount flags
ro,dir_mode=0777,file_mode=0777
Check your remote directory. It should start with public/some_folder, not with sonos!
Tidal Playlists
For those suffering with the Tidal playlists issue with upmpdcli there is a fix.
There will be a new release coming out but in the meantime I have attached the diff file that JF sent me.
Remove the .txt from the end and scp to /home/pi.
Then from a terminal session try.
This seemed to work for me, however had already git cloned the source tree.
if you want to be a bit more secure and you are more comfortable with git then from /home/pi
there is no need to compile just copy __init__.py
from
~/upmpdcli-code/src/mediaserver/cdplugins/tidal/tidalapi/
to
/usr/share/upmpdcli/cdplugins/tidal/tidalapi
May be my ignorance but I have had too many funnies downloading downloading code outside of git to publish the url to the file for a simple wget or curl.
NB The developer made the same change for Tidal as well which I have not yet tested.
For those suffering with the Tidal playlists issue with upmpdcli there is a fix.
There will be a new release coming out but in the meantime I have attached the diff file that JF sent me.
Remove the .txt from the end and scp to /home/pi.
Then from a terminal session try.
Code:
cd /usr/share/upmpdcli
sudo patch -p3 < ~/upmpdcli-tidal-and-qobuz-playlists.diffThis seemed to work for me, however had already git cloned the source tree.
if you want to be a bit more secure and you are more comfortable with git then from /home/pi
Code:
git clone [url]https://@opensourceprojects.eu/git/p/upmpdcli/code[/url] upmpdcli-codethere is no need to compile just copy __init__.py
from
~/upmpdcli-code/src/mediaserver/cdplugins/tidal/tidalapi/
to
/usr/share/upmpdcli/cdplugins/tidal/tidalapi
May be my ignorance but I have had too many funnies downloading downloading code outside of git to publish the url to the file for a simple wget or curl.
NB The developer made the same change for Tidal as well which I have not yet tested.
In anticipation of 4.1, I purchased an RPi3 plus and have been unable to get it to boot on either:
1)the 3.8.4 image (known good SD card that worked in my RPi2 before and after the attempt with RPi3 plus).
2) a 4.0 image from the Moode download site loaded with Win32Diskimager with the ssh file added.
in both cases the red light comes up first, then the green, which shortly enters a repetitive flashing pattern: four flashes at about a flash every half second followed by four flashes about every .25 seconds. This eight-flash cycle repeats until the unit is powered down.
The RPi2 with an Allo Bossdac on 3.8.4 sails along fine.
I thinking that it isn't fully booting as the repititions begin in less than 15 seconds from power-up. If it really does boot that fast, it could well be a networking issue. Any thoughts?
Thanks, Skip
1)the 3.8.4 image (known good SD card that worked in my RPi2 before and after the attempt with RPi3 plus).
2) a 4.0 image from the Moode download site loaded with Win32Diskimager with the ssh file added.
in both cases the red light comes up first, then the green, which shortly enters a repetitive flashing pattern: four flashes at about a flash every half second followed by four flashes about every .25 seconds. This eight-flash cycle repeats until the unit is powered down.
The RPi2 with an Allo Bossdac on 3.8.4 sails along fine.
I thinking that it isn't fully booting as the repititions begin in less than 15 seconds from power-up. If it really does boot that fast, it could well be a networking issue. Any thoughts?
Thanks, Skip
Hi, Skip.
See R-Pi Troubleshooting - eLinux.org for a discussion of blinky lights during boot. According to this page, a repeating cycle of 8 flashes means you need newer firmware files (bootcode.bin/start.elf).
Have you tried burning the latest release of raspbian (which was released at the same time as the RPi3B+) to a uSD card and booting it?
(And, as always, make sure you have an adequate 5v supply.)
Regards,
Kent
I use it, but it does not seem to work reliably either. I wouldn't mind having it dropped, but I have just ordered a touchscreen, so it could be nice to display the played.
Best regards,
Rafa.
@Serverbaboon
Thanks for this. It worked a treat against my stock r4.0.
Regards,
Kent