Gen 1. Installed last night. Easy install, no issues. Here are my issues/questions:
The only way I can have EVPlay bluetooth audio as default is to completely remove my phone from Rivian 'ui.' Otherwise every time I enter the vehicle to use EVPlay I have to enter the Rivian Bluetooth setup and chose EVPlay. That's a PIA. That can't be right, I must be missing something. What is it? I'm sure its simple.
Twice now my EVPlay touchscreen capability has completely frozen. The first time I was in AA and was still able to use voice control. But no touch. Second time I was on the EVPlay screen and was completely frozen. Rivian UI touch worked fine but in both instances it was SUPER slow. Luckily I haven't stowed away the unit so I was able to power reboot. If this continues to happen that's a big problem. Is there on other way to reboot without powering on/off? Via the button? Keyboard?
Finally, is there a Gen1 can DBC file floating around out there? Is the can connection the EVPlay uses go through a gateway or is it directly on the can bus? I have a medium level of experience (hah!) with can decoding and would like to poke around. One of the features that was the deciding factor to trying EVPlay was the potential for future development fun stuff such as can bus based apps/screen/gauges/etc..
Gen 1. Installed last night. Easy install, no issues. Here are my issues/questions:
The only way I can have EVPlay bluetooth audio as default is to completely remove my phone from Rivian 'ui.' Otherwise every time I enter the vehicle to use EVPlay I have to enter the Rivian Bluetooth setup and chose EVPlay. That's a PIA. That can't be right, I must be missing something. What is it? I'm sure its simple.
Correct, if you plan on regularly using Android Auto, then you wouldn't need your phone to be paired to Rivian Audio. Therefore you want to unpair/forget your Rivian-Phone connection. I am working on a way to improve this, where you pair your phone directly to Rivian audio as you normally would, negating the need to have EV Play in the middle. In other words, how it is currently handled with CarPlay.
Twice now my EVPlay touchscreen capability has completely frozen. The first time I was in AA and was still able to use voice control. But no touch. Second time I was on the EVPlay screen and was completely frozen. Rivian UI touch worked fine but in both instances it was SUPER slow. Luckily I haven't stowed away the unit so I was able to power reboot. If this continues to happen that's a big problem. Is there on other way to reboot without powering on/off? Via the button? Keyboard?
This is sometimes happens when you switch a bunch of times back and forth and immediately try to use the touch screen. Give it a little breathing room. You can reboot EV Play by dragging down on the system tray, clicking on the power button icon, and selecting Restart.
Finally, is there a Gen1 can DBC file floating around out there? Is the can connection the EVPlay uses go through a gateway or is it directly on the can bus? I have a medium level of experience (hah!) with can decoding and would like to poke around. One of the features that was the deciding factor to trying EVPlay was the potential for future development fun stuff such as can bus based apps/screen/gauges/etc..
Not that I know of. I had to sit there for days just to figure out the gear and speed! Let me know if you find one.
Thanks, I'm just gonna unpair my phone for the moment. No real reason not to. I used it quite a bit today and it works great so far. Particularly for v1. I look forward to future improvements.
Regarding dbc file. I did find that the "tes lax" app has added some Rivian functionality. As of two year ago, when the following video was made, they had several dozen R1T signals decoded. This guy was also selling his canserver hardware for R1T. Looks like a common ESP32 based device with his own custom can shield. But it may simply be a generic ESP32 GVRET can device (which I have a few). Tes lax is only iOS based. If it had an Android brother I'd get the app, connect one of mine up and see what shows up. But it's not on my priority list of things to waste time on right now!
https://jwardell.myshopify.com/products/canserver
https://youtu.be/humSofAFUdo?si=7FAE2lLrdweviMva
https://github.com/joshwardell/CANserver/releases
Thanks, I'm just gonna unpair my phone for the moment. No real reason not to. I used it quite a bit today and it works great so far. Particularly for v1. I look forward to future improvements.
Regarding dbc file. I did find that the "tes lax" app has added some Rivian functionality. As of two year ago, when the following video was made, they had several dozen R1T signals decoded. This guy was also selling his canserver hardware for R1T. Looks like a common ESP32 based device with his own custom can shield. But it may simply be a generic ESP32 GVRET can device (which I have a few). Tes lax is only iOS based. If it had an Android brother I'd get the app, connect one of mine up and see what shows up. But it's not on my priority list of things to waste time on right now!
https://jwardell.myshopify.com/products/canserver
https://youtu.be/humSofAFUdo?si=7FAE2lLrdweviMva
My list of things to waste time on is far too long at this point!
Glad to hear it is working well - I think AA needs a little improvement so that's what I'm focusing on right now.
And yes, I played around with Tes-lax after purchasing Josh Wardell's CANServer...very cool piece of equipment. You may want to try the Comma Discord - those folks definitely have a line on the Rivian CAN message