Quote:
Originally Posted by Prog
As opposed to having both on the same unit? I guess if you want less functionality, whatever works for you. I prefer to have the option of either.
|
Except you won't. I have seen no indication of any Android Auto-compatible head units having any Android functionality whatsoever unless they're connected to a suitable phone (or tablet, presumably). Without a connected Android device, it's just a "dumb" head unit. Even when you do connect your phone, the selection of apps that work with Auto is limited--It'll grow over time, sure, but I can just about guarantee you'll run into a few apps that you want to use with it and can't.
Quote:
Originally Posted by bwthor
I wouldn't order this one. I ordered what was listed as a USB OBDII 1.4 adapter, but what came was this one which is 1.5a. Will not work. Tried all sorts of things. Apparently there is an issue with 1.5a not being "official" or something.
|
Since I posted that link, I've ordered that exact one myself, and it's working perfectly.
The only issue--and from what I've read, this can crop up with
any USB OBD2 adapter and Torque--is that if Torque is running and already polling the adapter for data before the ECU fully initializes (which can happen if the Dashlinq4 resumes from standby and Torque was running when it went to sleep), it can pop a CEL with code U0073 ("something network something something", basically the OBD2 adapter pulling data too soon interferes with the sensors and the ECU talking to each other).
To prevent this, either don't use the resume function (fuck this), or make sure Torque is fully exited and not running before putting the head unit to sleep.
To clear the CEL if it does trigger, scan for it in Torque (to make sure U0073 is the only one), then exit Torque and open the task manager to make sure it's fully exited and not running, then turn the car off, give it a few seconds, and turn it back on. The CEL should turn off, and you can now open Torque, scan for it again, and clear the code.