[APP][5.0+]OBD2 Plugin for Android Auto - Use Torque with AndroidAuto

[Emil Borconi]

Just a quick update to the issue I am having. Was using the originally released version successfully (other than the issue with the MPG jumping around when the value was over 100). I have a 2010 Prius and the custom PIDs worked fine.

I wiped my phone last night to try to address battery issues on my Nexus 6P, so I did a fresh install of both Torque Pro and OBD2AA 1.2 on the current non-beta version of Android O. I am now back to the issue where the custom PID values read zero, but the standard PID values work. I have the first 3 gauges set with custom values and the last 3 gauges use standard PIDs.

Puff...

I will probably need more details on that, I will email you on Sunday or Monday, calling it a day today and I'm out all day tomorrow.

 

[spiff72]

Puff...

I will probably need more details on that, I will email you on Sunday or Monday, calling it a day today and I'm out all day tomorrow.

If you like, I can create another bug report like I did previously. Part of me wonders if the order of the gauges makes a difference. When i submitted the report previously, I think I had the "standard" gauges first, and the customs last. And I think the ones that were missing are the ones that were getting data from the previous gauges. I am in no hurry for support - it is a holiday weekend here. I can always revert back to the old version.

Thanks again!

 

[Emil Borconi]

If you like, I can create another bug report like I did previously. Part of me wonders if the order of the gauges makes a difference. When i submitted the report previously, I think I had the "standard" gauges first, and the customs last. And I think the ones that were missing are the ones that were getting data from the previous gauges. I am in no hurry for support - it is a holiday weekend here. I can always revert back to the old version.

Thanks again!

I'll like to finish with the next version, mainly because I do change a bit the things around (the way I pull data from torque) so I'm hoping that will fix your issue as well but if not we will need to dig deeper.

Thanks for bearing with me.

 

[spiff72]

I'll like to finish with the next version, mainly because I do change a bit the things around (the way I pull data from torque) so I'm hoping that will fix your issue as well but if not we will need to dig deeper.

Thanks for bearing with me.

Sounds good - I will just sit tight then...

Thanks!

 

[m00n61]

Hello Emil,
OBD2AA does not show in my list.
Here's my setup:
Lenovo Yoga3 tablet running latest HUR on Android 6
Samsung S8+ with Android 7 and latest versions of Torque and AA (Play Store both)
ELM327 v 2.1 BT
OBD2 adapter is seen by Torque OK
OBD2AA starts OK on the phone.
AA in developer mode
HUR works OK on tablet, no errors
Any idea where I should start?

 

[Emil Borconi]

Hello Emil,
OBD2AA does not show in my list.
Here's my setup:
Lenovo Yoga3 tablet running latest HUR on Android 6
Samsung S8+ with Android 7 and latest versions of Torque and AA (Play Store both)
ELM327 v 2.1 BT
OBD2 adapter is seen by Torque OK
OBD2AA starts OK on the phone.
AA in developer mode
HUR works OK on tablet, no errors
Any idea where I should start?

In android Auto, under developer settings make sure you enable unknown sources.

 

[m00n61]

In android Auto, under developer settings make sure you enable unknown sources.

Thank you, that was it. Working now
P.S. Getting CamSam Plus notifications in AA would be awesome.

 

[ardicli2000]

Do we also need a bt adaptor to ceonnect to the ECU? Since Torque app requires so.

Of thats the case pls update the OP and let people know exactly what they need. Cause all of us dont come from torque app site or somewhere else related with the isuue. Thanks.

 

[Emil Borconi]

Do we also need a bt adaptor to ceonnect to the ECU? Since Torque app requires so.

Of thats the case pls update the OP and let people know exactly what they need. Cause all of us dont come from torque app site or somewhere else related with the isuue. Thanks.

Hi yes it does need an OBD2 adapter, and this is a quote from the OP:

This app requires Torque Pro in order to run as well as an OBD2 adapter. In case you do not have Torque Pro yet, please purchase make sure your purchase it from: Google Play

 

[ardicli2000]

Sorry I missed adapter part.

A requirement tab would be nice than. Like:

1. Torque app from play store (costs 3.55€)
2. OBD2 bt adapter (to be bought from market separately)
3. OBD2forAA to be bought from xda lab (costs 2€)
4. Applicable car display, etc.

 

[astobelix]

I have buy the application , but is it working on MTCD device with android 6.0 with PX5 ?

 

[Emil Borconi]

I have buy the application , but is it working on MTCD device with android 6.0 with PX5 ?

No this works with Android Auto, not Android powered headunit. Find out more about it here: https://www.android.com/auto/
If you have purchased already please let me know by sending me an email to [email protected] and I will issue you a refund.

 

[Emil Borconi]

The bad:
- TomTom does not update the notification in services meaning I cannot read out the Speed Camera notifications
The Good:
- CamSam Plus does and I was able to integrate it quite nicely.

Next version is getting close, hopefully by the end of this week we can all enjoy the updated version...

 

[MrShibby]

The bad:
- TomTom does not update the notification in services meaning I cannot read out the Speed Camera notifications
The Good:
- CamSam Plus does and I was able to integrate it quite nicely.

Next version is getting close, hopefully by the end of this week we can all enjoy the updated version...

The notification for blitzer.de is what i was looking for. Great Work!

 

[FormelLMS]

Yes, me too. Sounds good.
@Emil: do you think, you can make an automatic startup from your app while starting Android auto?

So we could be sure, that your services are running every drive we do?

 

[Emil Borconi]

Yes, me too. Sounds good.
@Emil: do you think, you can make an automatic startup from your app while starting Android auto?

So we could be sure, that your services are running every drive we do?

Not without root. CamSam does not export them but it has an option to start automatically when you connect to a Bluetooth device so that will do the trick.

 

[FormelLMS]

Yes, thats true. I think I have to try those things out.

---------- Post added at 08:26 AM ---------- Previous post was at 08:22 AM ----------

One Problem I've encountered today: I've chosen the Pid for GPS height but its standing still at 100 meters the whole time. GPS speed is working.

 

[ControlNode]

Knock (PID 220404) gauge is just using the value of the gauge before it. I've had it after Vac/Boost (ff1202)and Timing Advance (0e).
IAT (0f) is showing values as C even though in Torque I've set temps to be F and OBD2AA even indicates it detected F from Torque by the F being in the gauge, but the value is still in C.
I still do not understand when you said the min/max comes from the ECU. If that is true how is it that in torque it is getting values outside the range in OBD2AA from the ECU if the ECU defined a max less than that? See Fuel Rail (23) in pictures.
Also, AFR(m) (ff1249) looks great in position 6, but in 3 it's like the max is much higher as instead of 14.7 being close to 12 o'clock it is at about 9 o'clock.

Car is 2016 Focus RS with Sync3 ver 2.2
OBD2 Adapter is PLX Kiwi BT
Phone is Pixel XL now on Android 8.0.0

 

[Emil Borconi]

Knock (PID 220404) gauge is just using the value of the gauge before it. I've had it after Vac/Boost (ff1202)and Timing Advance (0e).
IAT (0f) is showing values as C even though in Torque I've set temps to be F and OBD2AA even indicates it detected F from Torque by the F being in the gauge, but the value is still in C.
I still do not understand when you said the min/max comes from the ECU. If that is true how is it that in torque it is getting values outside the range in OBD2AA from the ECU if the ECU defined a max less than that? See Fuel Rail (23) in pictures.

Car is 2016 Focus RS with Sync3 ver 2.2
OBD2 Adapter is PLX Kiwi BT
Phone is Pixel XL now on Android 8.0.0

- I have already fixed the temp conversion for next release.
- Also looking to get the issue with wrongly updated PIDS sorted.

This is the documentation for torque plugin: https://torque-bhp.com/api/ITorqueService.aidl

This is the method used to get the min/max values for pids:

 /**
    * Return all the PID information in a single transaction. This is the new preferred method to get data from PIDs
    *
    * The unit returned is the raw unit (used for getPIDValues) - you can get the users preferred unit by using the relevant API call 
    *
    * Format of returned string array:
    *  String[] {
    *       String "pid information in csv format"
    *       String "pid information in csv format"
    *       ...(etc)
    *    }
    *  
    *  Example:
    *
    *   String[] {
    *      "<longName>,<shortName>,<unit>,<maxValue>,<minValue>,<scale>",
    *      "Intake Manifold Pressure,Intake,kPa,255,0,1",
    *      "Accelerator Pedal Position E,Accel(E),%,100,0,1"
    *   }
    */
   String[] getPIDInformation(in String[] pidIDs);

And this is how I'm supposed to get the values:

  /**
     * Return the current value only for the PID (or PIDs if you pass more than one)
     *
     * Use this method to frequently get the value of PID(s).  Be aware that the more PIDs you request, the slower the update speed (as the OBD2 adapter will require to update more PIDs and this is the choke-point)
     * This method is asynchronous updates via the adapter
     */
    float[] getPIDValues(in String[] pidsToRetrieve);

This is all I know, but yes as you said values returned by this function sometimes do not match what is shown in Torque. I did try to get some help from the Torque developer but I haven't got a response till now.
Also the second method is supposed to return an array with the values for the PIDS in question, during debugging I did saw that the array sometimes returns same value for multiple pids which makes no sense to me. If there is no update or no value for a pid I will expect the function to return 0 or NULL or something like that, having multiple pids returning the same value doesn't help at all.

The only way I think I can overcome this is to fetch each pid separately instead of bulky but that has a performance hit cost, however that way I can at least control the returned data.

As for min/max I saw strange ones as well, Torque reported a max value of 100 when I got a report on the pid, but when I started fetching the data, it returned 700.... The lesson is that I cannot really trust what Torque is reporting. In the next version, if the fetched value is more than the max reported value, the app will adjust the max value of the gauge to match the newly fetched data... not ideal but better than now. I was under the impression that torque function which provides the information about a PID reads the data from the ECU, but I'm not so sure about it now.

 

[ControlNode]

@Emil Borconi No problem. I definitely interested in what they say about that float array duplicating a return value in two indexes for different PIDs.