You had mentioned it was a "demo" version. I don't know what that means. I just went to Play Store and installed the Sirius XM app. I think when I started it up it asked some registration questions, and I indicated I was already subscribed and gave the info about my car's account. That was a couple years ago, but it was only a couple months ago when I added my smart TV using the same credentials. Again, only one streaming device can rin at a time. I'm not sure if that includes the original physical satellite receiver.
BTW, I've heard that with a good internet connection the streaming app has better audio quality than the satellite receivers. Probably has better bandwidth unless your ISP is congested.
The unregistered version of Sirius/XM plays one channel urging you to register with them. That's what I meant by demo version. It was downloaded from the Play Store.
The streaming app on my phone was installed some months ago - let me check it and see if there is any registration info.. it seems to be registered to my Sirius account. I'll have to look at the one on the headunit in the car and see how I can get it registered.
UPDATE - looked. Registered it - works fine. I wonder how they're making money with this scheme...
Meanwhile - after lots of needless complexity - I managed to get Android-Auto to connect wirelessly - no hands - twice in a row (yea!) now we'll see if it still does that tomorrow.
Basic technique for AA
- Open your phone BT settings. Make sure the phone is connected to the headunit. If it isn't - connect them. I'd suggest shutting down any other BT devices in the area just to make things simpler (like the OBD-II Bluetooth dongle for Torque - I just unplugged it..) SO - connect phone to the headunit.
Just don't count on this being automatic. Sometimes it is - sometimes I have to go break the Bluetooth connection, remake it and then start up Bluetooth, go to the phone/bluetooth app on the headunit, reconnect to the phone, then hit the app on the headunit, and after some data churning - it opens.
Sigh - it's not what I'd call immediately "user friendly" - I suspect the apps all are having difficulty with Bluetooth. What's interesting is the AA app mentions using WiFi to connect (set phone as a hotspot then connect with the headunit to the phone..) I'll have to try that. I did try connecting with a straight USB connection, and it didn't work, but I didn't spend much time on it.
More as it evolves..
Update - 05/25/23.. on using Android Auto (hereafter "AA")..
I've gotten it to work well enough that I'm not really frustrated with it. There are however some issues.
To initially get it working, make sure Bluetooth (BT) is turned on in your phone. There should be a menu selection in settings for this, and part of that will also allow you to see what, if anything is connected to the phone.
In the headunit
- you can name the BlueTooth connection or a default is given for it.. in my case it named itself "SYU-Android" - I have no idea how it came up with the name, but it's unique so that's good enough for me.
IF your phone is working through the headunit - you already have a BT connection, but before starting up AA, I'd strongly suggest breaking that connection and remaking it. I've found that easy to do on my phone. Part of the menu for BT will let me disconnect and then quickly reconnect to the headunit. DO THAT before starting up AA on the headunit.
At this point - the headunit has been up and running for perhaps 30 seconds or more(*) - you can press the app button that starts AA - CarBitLink 2.0.
A blue screen will open up - with a small banner message in the center of it - announcing that it's connecting to the phone. After a few seconds it's found the connection it needed and the banner changes to simply "Connecting"..
This page may stay up a bit of time (30 seconds or so) - apparently this indicates the headunit is grabbing info from your phone (phone book, calls, message, etc) and loading the general configuration setup for AA on your phone.
When it's done doing that - the screen will go black, and shortly after that your phone screen will also go black. Again - this will take from 5-45 seconds before a second blink and another black screen (short one - maybe 5 seconds) and the magically the AA screen will open on the headunit.
And there'ya are. AA working wirelessly on the unnamed headunit. Whod'a thunk it - the Porsche PCCM+ can't do that.
Now the glitches:
- once or twice the two stopped talking to each other. I'm not certain why - but they did. It did reattach automatically - but the connection still seemed flakey, so without shutting anything down, I went into my phone BlueTooth menu, disconnected and reconnected to the headunit and all was well again.
- (*) - from above. t turns out there are too many settings in too many places, some of which try to achieve the same goal, but fight other ones trying to achieve the same goal. And example is the boot loading.
There is a place in the Agama Loader menu where you can tell it that it's the Launcher of choice - and loaded on booting up. There is also a place in the factory menu where you can select the Launcher that opens on bootup. And if you select both of these (and I think I'm forgetting a 3rd spot it can be chosen), it will load up, the blink and go away and then load up again when the headunit boots. If - as I did -- you've chosen a music player Agama tries to open it on boot up. There's a setting under Factory settings where you can chose up to 3 apps that will load on bootup.
What happens then, CarBitLink on the headunit has a setting for automatically loading it - and 3 choices. None of the choices are don't load it. (1)It's load it automatically, (2)or load it if it ran the last time the headunit was used (3)or load it according to system instructions.
Given the choices, there's a fair chance It's going to load pretty much whatever you do.
If all the settings for what loads when are wrong - you'll end up with blinking screens - things opening then being switched to something else opening and finally to another thing opening AND THEN it repeats this around 4 times. That's not good.
My advice - the Agama loader has the option to set certain apps to load on boot up, with a time delay before they open. Turn any other references to loading the Agama loader OFF. Use that delayed option to load the music player - delayed maybe 10 seconds. Then set the CarBitLink to open after 20 seconds.
Life will be much calmer for you..