Skywatcher

Thank you for the reply. I'll keep an eye out for it in the future, then.

You'll need to buy a license. Otherwise you'll have a very nicely-designed paperweight. From https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs What happens when my license runs out? You can purchase a renewal through an authorized Meraki partner. If you choose not to renew, you will no longer be able to manage your device via the Meraki cloud, and your Meraki network device will cease to function. This means that you will no longer be able to configure or make changes to your Meraki network device, and your Meraki network product will no longer pass traffic. (I added the bold to the text)

Polestar models got it OTA (via wireless internet access) in the latest software update. If your Volvo model gets OTA updates you should get it on the latest version. If the updates are "wired" at the dealer, then you'll probably need to go in.

Detail is, most manufacturers using AAOS have not implemented Android Auto as they consider the Android ecosystem covered by default by AAOS. I think that's a bad move and we should have the choice between AAOS and Android Auto, to be honest. If you login with your google account in AAOS (allows for several user profiles), then it will sync a lot of information from your phone, as long as you don't toggle the privacy switches off. Your google searches and preferences, the trips you searched or saved in google maps, etc. all that comes across as it's just "another android" device you login into. Android Automotive OS will be the car's native OS, you are correct, Chris. All new Volvo (and their daughter company Polestar) are AAOS, and from next year so will start being Renault, Nissan, Mitsubishi, Honda, BMW (selected models), Stellantis* and GM. So, from 2023 onward you'll see an explosion of vehicles coming with it. * - Stellantis will only use AAOS for the infotainment system, but not for navigation. Stellantis owns Abarth, Alfa Romeo, Chrysler, Citroen, Dodge, DS, Fiat, Jeep, Lancia, Maserati, Mopar, Opel/Vauxhall, Peugeot and Ram. Carplay support phase 1 (via USB cable) should be out for selected models now. Wireless Carplay support has been promised for later this year. Android Auto, no plans apparently. Hence my question to the Qobuz team, since I could only see Spotify and Tidal in the AAOS Play store, but I'm a happy Qobuz subscriber.

Hi Qobuz team, A question for you guys. Are you planning on releasing an Android Automotive OS version of the app? (Not to be confused with Android Auto) I've just put down an order for a car that comes with AAOS as the infotainment system, so, no Android Auto. Since several brands are starting to pick it up for their 2022/2023 releases I was wondering if this is something you guys are considering like <others that shall not be named> did? 😉

Bitperfect only means that what comes in, comes out. Just like it came in. Bit perfect won't improve what came in 😉

@volpone @suresh3 Look what I just bought: Link

Running v157 here with no issues at all. (PCM up to 192KHz as my DAC doesn't do DSD). I think something went less well with your update, probably.

I think Lobbster only wants to install a simple upnp/DLNA renderer. Not installing JRiver MC.

Looking nice, hurka! What case is that in the USBridge?

From Allo's website the link goes to https://www.amazon.com/clouddrive/share/FUIonEVVyrNwWlsWDYBUW3lGie0OJX4Iw62SxVDDBDw?_encoding=UTF8&mgh=1&ref_=cd_ph_share_link_copy

I had a spare Sparky laying around so I decided to try it I downloaded the Volumio image from the site, placed it into an SD card, attached a USB Hard Disk with music files and my USB DAC to the Sparky and booted it. Volumio could see my music but no sound was coming out. Logging in showed me that volumio was trying to send the sound output to card 0 while my DAC was being listed as card 1. Changing the hardware output from 0 to 1 on mpd.conf solved it and I'm currently listening to Macy Gray's "Stripped" in 24bit/88.2KHz with no issues. So you probably have a solution there franz159.

Thanks. Not a deal breaker as it's easy enough to hide, more as a nice to have.

Jesus, A quick question. I'll do a refresh on my system in some months and will most likely put a microRendu in. Are you considering on making a black version available or will it just be the silver one? Asking just because all my other components are black.

@andervt I had the same problem when I installed windows 10 Pro. My DAC is not the same as yours but the symptoms were precisely the same. Installer program would run but the driver wasn't installed and I got that same error at Device Manager. Contacted my DAC manufacturer and they told me that happened because the driver wasn't a signed driver and they gave me the procedure to turn off Win 10 Pro signed driver enforcement so that other drivers could be installed. I did that and the driver installed successfully and no problems ever since. The procedure I followed was similar to the one described here: Windows 10: Disable Signed Driver Enforcement