Is that Raspberry Pi case a metal case? If so, most metal cases hamper the Pi WiFi connectivity. A plastic case is than a better option.
Hi @Sailor, Raspi Wi-Fi is fairly weak due to the lack of any real antenna. There are some articles about adding a proper antenna, tho’ the operation is pretty dicey. Your best option is disabling the onboard Wi-Fi and using a USB Wi-Fi ‘dongle’ with decent antenna, which also sidesteps attenuation from a metal case. While widely available and quite inexpensive, be careful to select a Wi-Fi dongle that has proper Linux support.
1 Like
Thank you for the dongle suggestion! Will Look into it and ask here if I choose a Linux-compatible one.
1 Like
The case is aluminium, so I don‘t know about shielding effects. I can disassemble the raspi and see if WiFi performance becomes better. In any case, I‘ll pursue @Press250‘s suggestion for a WiFi dongle.
Hello, I’m writing to you.
I followed the procedure to install CorePlayer on a Raspberry. The installation went well.
When I try to connect with my smartphone (Audirvana Remote), I get the following error:
“Check your computer’s firewall to make sure that the Audirvana application is authorized to access your network”.
I’m on the same network.
How can I solve this problem?
I had the same problem on my Android phone but strangely no problem on my iPad. My iPad is quite old so it is not 5G. The raspberry pi is only 2.4G i think, so maybe it has something to do with that?
Can you connect to a 2.4G on your phone?
I’m not familiar with the distros for Raspberry, but many distros have the firewall (ufw) enabled by default. Is that the case with the distro you have installed? Can you turn off the firewall and test whether the remote works then?
Thank you @Chri6699 for this solution.
It works on ipad /iPhone. Too bad it doesn’t work on Android.
I tried from my old iPad on WiFi 2.4 AND 5G and it works.
Maybe a problem with the Android Remote app.
Anyway. I was able to access Audirvana.
I installed it on a NUC(Debian) and work well. I still have a little problem. I can’t get my music folder to scan into Audirvana. I’ve mounted the USB disk and it appears in /mnt/, but when I try to add a folder to the local Audirvana library, I get a “request error”.
Any ideas?
My USB disk is in Extfat
@Jud, I have the same problem with Debian on my NUC.
Look in the log file to see if there are any error messages. In the Audirvana Remote app go to Settings > Account (a tab at the top of the screen) and scroll down to ‘open log file’.
I also had this problem!
Then i searched on YouTube and found this fantastic video;
Follow his instructions carefully and it should work.
After reading your problems with the Audirvana remote, I decided to use an old android phone (non 5G), and it connected with no problems after install. So I think it is a 5G issue.
Does anyone know if Raspberry pi can be updated to 5G connection?
I just tried again with my Android smartphone in 5G and 2.4.
In the logs, I get the error:
“Remote: event websocket lost with error: Connection reset by peer”
I would advise to send an email to support and include the log, describing your problem.
Hi @Chris6699, Raspi 4 and Raspi 5 have dual band Wi-Fi, 2.4 and 5GHz.
1 Like
It works like a charm !
I’m connected to Qobuz and get all the editorial content like the Qobuz app !!!
Mac app perfect, Android app perfect !
Sound seems to be better from what I was used to.
Happy to have changed !
Better than Volumio !
If you are connected to your raspberry trough SSH, just use this command to copy the package with:
scp ./audirvana-studio_2.9.5_arm64.deb [email protected]:/home/myuser
3 Likes
Has anyone had the problem when modifying the etc/fstab file for auto mounting an external drive on the Raspberry Pi 4 that it goes into emergency mode after a reboot? It seems to be a known problem.
I don’t have a Pi and therefore haven’t had the specific problem. But I’m always modifying my /etc/fstab file to automount an external drive on my PC whenever I try out a new OS, and I manage to avoid problems on rebooting with the following steps:
- Make a backup of the original /etc/fstab file by copying and renaming it.
- After you’ve modified the original /etc/fstab, see whether it works without rebooting by issuing the command sudo mount -a.
- If that command results in error messages, correct the errors if you can and reissue sudo mount -a. If you aren’t able to correct the errors, replace the modified /etc fstab with the original and do sudo mount -a once more to be sure.
This will at least save you the hassle of not being able to reboot.
Thanks for the advice!
Where do you store the original etc/fstab file? In case the modified etc/fstab file fails to work, how do you resort to the original one?
Issue a command to copy /etc/fstab to /etc/fstab.bak .
If the modified /etc/fstab doesn’t work, first sudo rm -rf /etc/fstab , then copy back /etc/fstab.bak to /etc/fstab .
Sounds all logical, thanks!
However, when in my first attempts I used the mount-a command after editing the etc/fstab file, I had no warnings whatsoever. So I rebooted and it went into emergency mode. After that, no way to get access to the original etc/fstab file.
My suspicion is that the Raspberry didn‘t lile the format of my SSD drive, as it was formatted in Apple way (APFS). When after re-booting I used exFat, it worked immediately. But that‘s only a suspicion.
Thanks for the advice anyway. Linux, at least for me, is still full of surprises.