Ram Heavy Duty Forum
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
OBD2 on Android Auto
- Thread starter blbrown
- Start date
I'm going to be checking this out a little more after installing it.
www.autoevolution.com
The World's Number One OBD2 App for Android Now Available on Android Auto With a Catch
A new Android Auto plugin enables users to display data imported from Torque on Android Auto, including even custom PIDs
www.autoevolution.com
blbrown
Active Member
- Messages
- 191
- Reaction score
- 100
- Points
- 43
I've been watching this as well, I'm hopeful that their app will also be able to use on Android Auto soon without having to enable developer mode and other steps. DashOBD is pretty simple but I'm hopeful it will encourage other app developers also get their apps approved for use on AA and available on Google Store.I'm going to be checking this out a little more after installing it.
The World's Number One OBD2 App for Android Now Available on Android Auto With a Catch
A new Android Auto plugin enables users to display data imported from Torque on Android Auto, including even custom PIDs
Work in Progress, still figuring out which PID work and which don't and build out a few panels that will be useful. I think I have some funky PID's in Torque though I do have the "old" Cummins PID's imported which probably needs some refresh/validations.
I wasted most of my idle time in the school pickup line just trying to get the vLinker connected to Torque. Had it in my BT on my phone from when I bought it, but it started acting weird and showing the "IOS" BLE only. Seems there may be some oddity with the BT/BLE on either the vLinker or my old trusty S9. I may put my MX+ back in to see if it's more stable. The gauges also seem to drop a little data with this setup.
I see some blurbs about vLinker only supporting BLE (shows as vLinker MC-IOS) and I paired with that, but I'd also seen it come up as vLinker-MC Android and that's the way Torque sees it and the way I paired it first with AlfaOBD. I'm also seeing info the BLE was funky on S8/S9 phones.
Now the vLinker doesn't show in the known device list in AlfaOBD or the phone. Weird.
I wasted most of my idle time in the school pickup line just trying to get the vLinker connected to Torque. Had it in my BT on my phone from when I bought it, but it started acting weird and showing the "IOS" BLE only. Seems there may be some oddity with the BT/BLE on either the vLinker or my old trusty S9. I may put my MX+ back in to see if it's more stable. The gauges also seem to drop a little data with this setup.
I see some blurbs about vLinker only supporting BLE (shows as vLinker MC-IOS) and I paired with that, but I'd also seen it come up as vLinker-MC Android and that's the way Torque sees it and the way I paired it first with AlfaOBD. I'm also seeing info the BLE was funky on S8/S9 phones.
Now the vLinker doesn't show in the known device list in AlfaOBD or the phone. Weird.