Volumio 2 on Odroid Boards

For the time and effort spent on getting stuff to work well with this board, perhaps it is better to move to a different board that is known to work. This is even more so when Volumio Buster is released, as you can be sure that it won’t appear on Odroid C1 (Edit: my mistake).

The fact is, the 3.10.x kernel for the Odroid C1 is old and buggy. Mainline kernel has limited support and I don’t think further development will be made on the S805 SoC.

There is a reason why Raspberry Pis lead the crowd in terms of popularity. With my old Pi 3B, at least I know I’d still be able to run the latest kernel on it.

Your assumption? Wrong.
Get your info first before making up stories :wink:

C0/C1/C1+
Volumiobuster-3.066-2021-04-16-odroidc1

Ahh… I stand corrected.

So what kernel version is it running?

when you scroll up a few posts you will see which one and why

@itsmaxdd , why not try Buster beta then? There will be no need to upgrade MPD and you can see if the scan works.

judging by the date of release it might be that plugin manager (or pluings) is not working properly.
I read they fixed it in later stages but i might be wrong.
@gkkpch can you suggest on this?

They purposefully disabled plugins for the beta. You can still install volumio-ytcr through ssh like you did with 2.x

But before installing any plugin, test whether scanning works as it should.

sorry, please read info on Volumio 3 beta, it was clearly communicated that it is without plugins and users are not supposed to install manually. Do NOT ask for support when you did.
That said, the next version will be a rc1 with support for the new plugin store.
Note, Odroid betas are ‘preview’, focus is on RPi, Tinkerboard and x86.
So when rc1 is announced, it will still take time before I can build the community portings.

This goes without saying~

@gkkpch can you forsee a beta release date for odroid c1 perhaps?
while what you are saying make sense i still think that you might be interested in some testers so i could as well make a try for the science

I understand and appreciate the test help you’re offering, but this is not a fulltime job for me and currently more priority is given to getting the x86 rc1 tested and released.

1 Like

A little Off Topic, but I realised we made this for some other issue today – should give you an overview :slight_smile:

Device Base Arch VOLUMIO_HARDWARE VOLUMIO_DEVICENAME Kernel Type Status
cuboxp armv7 armhf cuboxp Cubox Pulse 4.14.y C P
kvim1 armv7 armhf kvim1 Khadas VIM1 4.9.y C P
kvim2 armv7 armhf kvim2 Khadas VIM2 4.9.y C P
kvim3 armv7 armhf kvim3 Khadas VIM3 4.9.y C P
nanopineo2 armv7 arm64 nanopineo2 NanoPi Neo2 4.11.y C, O P
nanopineo3 armv7 armhf nanopineo3 Nanopi Neo3 5.4.y C, O T
odroidc1 armv7 armhf odroidc1 Odroid-C1 3.10.y C P
odroidc2 armv7 armhf odroidc2 Odroid-C2 3.16.y C P
odroidc4 armv7 armhf odroidc4 Odroid-C4 4.9.y C P
odroidn2 armv7 armhf odroidn2 Odroid-N2 4.9.y C P
odroidxu4 armv7 armhf odroidxu4 Odroid-XU4 4.9.y C P
orangepilite armv7 armhf orangepilite Orange Pi 5.4.y C T
pine64base armv7 armhf pine64 Pine64 5.7.y C P
pine64plus armv7 armhf pine64plus Pine64+ 5.7.y C P
pine64solts armv7 armhf pine64solts soPine64-Pine64LTS 5.7.y C P
pi arm armhf pi Raspberry Pi 5.4.y S T
rockpis armv7 armhf rockpis ROCK Pi S 5.6.y C P
rock64 armv7 armhf rock64 ROCK64 4.4.y C P
tinkerboard armv7 armhf tinkerboard Asus Tinkerboard 4.4.y S P
vszero armv7 armhf vszero Voltastream Zero 4.1.y C P
x86_amd64 x64 amd64 x86_amd64 x86_64 5.10.y S T
x86_i386 x86 i386 x86_i386 x86 5.10.y S T

Do note that this is an evolving list, things change!

Thanks ash~

As Volumio 3 is available for all Odroid devices, I’ll close this topic soon.

1 Like

Hello,

I installed the following version “Volumio-3.224-2022-02-10-odroidn2”.

I was using the I2s with GENERIC DAC I2S on a raspberry pi 4.

How to activate i2s on an ODROID N2+?

Thank you very much for your feedback,

Sincerely.

Did you read the wiki at Odroid?
https://wiki.odroid.com/odroid-n2/application_note/gpio/i2c

There is no more support for Odroid, except re-building images for the C4 and N2/N2+ at certain times because of their performance.
That being said, explore the first post in this thread. It shows how to handle a generic i2s DAC where no extra interfaces are needed through i2c (like volume control). The shown C4 example is 1:1 compatible with the N2.

Hello it’s not the i2c but the i2s !

read my post again, btw i2s is on the j7 port, not on the 40-pin gpio.