yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] shishir4866:
Hi Emil,

I have an aftermarket TPMS installed in my car (VW Polo 1.2 TSI). Any idea, how I can display the air pressure through Torque Pro on my Android Auto enabled head unit?

Specifications:

1. TPMS : Aftermarket, internal sensors, communicate via bluetooth to a mobile app(BLE TPMS)

2. OBD2 adapter: ELM27

3. Car: VW Polo 1.2 TSi

4. Head unit: RCD 340G (with Apple Car Play and Android Auto, OEM)

5. Mobile phone: Samsung S8 Plus(stock)

6. Torque Pro

Best Regards,

Shishir
[Paid Software Announcement and Discussion] kenweise:
So I was a functional user before the 3.0 ban, and of course it stopped working. I have been following this thread to see when to jump back in and decided today was the day. Here is what I did:

1) Cleared Data from OBD2AA app.

2) Set up one gauge that I know worked (turbo boost pressure)

3) Started Head Unit Server

4) Plugged in the phone. Unlike the instructions, there was never a "select which app to use."

5) Tapped the right button, and only got "Return to Sync." No OBD2AA option

6) The location notification DOES show up on the AA home screen.

A bit about my environment

Phone: LG G6 H872

Android Version: 8.0.0

Car: 2016 Fiesta ST with Sync3 V2.3.

Any guidance?
[Paid Software Announcement and Discussion] Emil Borconi:
It will only work if Torque supports TPMS for that, but I don't think that is possible (unless the BLE TPMS has a Torque plugin)
[Paid Software Announcement and Discussion] Emil Borconi:
Open Settings -> apps -> all app -> Google Play Services -> Clear defaults (not data!)

Now try to repeat step 4.
[Paid Software Announcement and Discussion] kenweise:
That was it. Then had to restart the phone, restart the server and step through the AA setup screens on the phone and headunit. Now I have my gauges back! So excited.
[Paid Software Announcement and Discussion] Emil Borconi:
I've been doing some research today on the Torque pro plugin and how can I improve thing, clean up code, fix errors and so on, and I cam across a bug mentioned by others in Torque Pro Plugin interface which is dated back in 2012, bu apparently it's still not fixed in 2018.

This bug has to do with how Torque Pro returns data, essentially, there is a function, where you request values for an array of PID's and the function is supposed to return an identical array with current values for the PID's, however if one sensor is not available at the moment of request for any reason, the returned array will be filled with previous sensor data, which throws a few spanners in the work.

The said part of this, is that this bug was reported so long ago, and it's not addressed. It looks like the only way around it is to use the deprecated functions which were marked as deprecated years ago, but apparently still returns good data.

Anyway I'm working on this now to have crashes and hangs fixed as well as the other mentioned issues.
[Paid Software Announcement and Discussion] niteNarmor:
Thank you for this app. Just purchased a Kenwood DDX9904S with Android Auto and was looking on how to this. This does work flawlessly with my environment. Thank you for your hard work.
[Paid Software Announcement and Discussion] Framingr:
Emil. Looks like the app doesn't play will with Android P. My guess is you need to compile against the new sdk. It crashes when the aa unit is plugged in. Hopefully you can resolve it easily
[Paid Software Announcement and Discussion] bggold:
Had the same issue.

I sent Emil a bug report. I had the same issue when using it with AA plugged directly in, but when I use aagateway wireless it works fine.
[Paid Software Announcement and Discussion] kenweise:
Well, I spoke too soon. Worked the first time it was plugged in, hasn't worked since. AA won't launch on the head unit (works on the phone).
[Paid Software Announcement and Discussion] Emil Borconi:
Android P issue.

- It looks like they have changed some things regarding SSL TrustManager which is causing it to crash on P. I will try to work around this, but since I don't have a device which runs P it will be slightly harder.
[Paid Software Announcement and Discussion] Framingr:
Please let me know if you need an Android P tester.
[Paid Software Announcement and Discussion] Emil Borconi:
Email me please
[Paid Software Announcement and Discussion] xZaKax:
I follow all the steps but OB2AA doesnt work. Android Auto appears in the notification bar but Android Auto doesnt start in my head unit.

Mobile: PIXEL 2 XL

CAR: Opel Astra K (2015)
[Paid Software Announcement and Discussion] FormelLMS:
Hey all together,

was a bit quiet last time because I was very happy with the day/night and speedcam thing, so I've never updated.

Now I was to fast with updating to Android Pie on the Pixel.

Seems, that OBD2AA crashes and get Google Maps to die.

Unfortunately a few days before our holiday trip.

Now fingers are crossed that emil can fix this issue.

Without that, this could be an expensive driving (here comes the ape with the hands in front of his eyes)
[Paid Software Announcement and Discussion] Emil Borconi:
Well.... uhhhh..... ahhhh..... not sure about that. The fact that I lack a Pixel device and that there is no other way for testing on Pie for the moment, means I'm a bit stuck with this at the moment. However simply uninstalling the app, and installing it again, and NOT choosing it as the default should make AA work normally, with speed camera notifications still showing (but gauges won't work)
[Paid Software Announcement and Discussion] FormelLMS:
Unfortunately that is, what I did
[Paid Software Announcement and Discussion] warmq:
Do you think its possible for your app to add stuff onto the home screen of android auto? just like a widget with a gauge there?:)
[Paid Software Announcement and Discussion] xZaKax:
I have a Pixel 2 XL and now the OBD2AA doesnt work. I choose the app (im not root) and Android Auto never starts.
[Paid Software Announcement and Discussion] NU13:
Quick update Emil. I redone OBD2AA to run a bug report to send you (concerning the unsupported device issue when obd2aa tries to launch). How ever the problem now seems worse because I don't even have to have the app running now for the unsupported device issue to pop up, just having obd2aa on my A8+ on the phone is enough to bring up unsupported device on the Hu.
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=8786319]NU13[/MENTION] - Sorry I'm not following this.

Edit.

I have re-read and I understand what you are saying, but that makes absolutely no sense at all. The only reason why a headunit/car will complain about unsupported device is if it fails to contaminate with the device over USB. If obd2aa is not running, and AA is doing the talking to the car, then I don't understand how that will cause such an issue... it just doesn't make sense...
[Paid Software Announcement and Discussion] Emil Borconi:
A HUGE thank you to [MENTION=5437072]bggold[/MENTION] and his device donation. Thanks to him by next week I should be able to see what's going wrong on Android Pie.

THANK YOU (in the name of all)
[Paid Software Announcement and Discussion] FormelLMS:
WOW!!! Big thanks to [MENTION=5437072]bggold[/MENTION]
[Paid Software Announcement and Discussion] androidarmy:
Hi guys

I had install the app but when I open it it says no torque pro found but I have torque pro and it's connected to obd2 and have Android auto install on my phone. Have a look...

Can anyone help me out
[Paid Software Announcement and Discussion] Emil Borconi:
second image doesn't load.

Based on first image, it sounds like Torque Pro is not installed. Is your Torque version up to date?
[Paid Software Announcement and Discussion] androidarmy:
Yes torque is installed. I also have Android auto install. Do you think it's cuz of that?
[Paid Software Announcement and Discussion] NU13:
Yes it surprised me too. Last time i tried use the app it would tell me the phone was unsupported when i selected OBD2AA. But this time it told me the phone was unsupported as soon as i connected it to the USB without even attempting to open the app.

I'll try my old S5 on the weekend but i suspect i will have the same issues.
[Paid Software Announcement and Discussion] luisgodinho:
Hi, I'm having trouble on connecting the device. Without obd2aa installed, android auto works fine. When I install obd2aa, android auto won't connect to my car. On the phone shows a red screen and mentions the error 16 (whatever it means). How can I fix it?
[Paid Software Announcement and Discussion] Emil Borconi:
Haven't seen Error 16 till now... Can you please see the OP on how to get a bug report and send one over?
[Paid Software Announcement and Discussion] luisgodinho:
How can I send you a video of the recorded screen? It won't load over here.
[Paid Software Announcement and Discussion] Emil Borconi:
Probably easiest if you upload it to youtube or similar.
[Paid Software Announcement and Discussion] luisgodinho:
Emil, I sent it to your email! Please take a look... Thanks
[Paid Software Announcement and Discussion] jeromeo01:
I used to have red screen on my phone. Deselecting "use of bluetooth for output" fixed the issue for me.
[Paid Software Announcement and Discussion] luisgodinho:
Where can I disable it? On the phone settings, android auto or obd2aa?

I have a Xiaomi with Miui rom wich is diferent from pure android.

On the other way, I found some forums reporting a fix related with cloned apps. I will try both..
[Paid Software Announcement and Discussion] Emil Borconi:
It's inside the obd2aa preference screen
[Paid Software Announcement and Discussion] luisgodinho:
No way! I can't get it connected. The error won't go away...

Some say it's because of cloned apps but I disabled it and still get the error.
[Paid Software Announcement and Discussion] bggold:
Do you have developer mode enabled on your phone? If not try that.
[Paid Software Announcement and Discussion] luisgodinho:
Tried that but still nothing!

Disabled clone apps

Enabled full permissions

All steps were fulfilled

Still getting the communication error 16 on Android Auto when I have the Obd2aa installed.

When obd2aa is not installed, Android Auto works fine...

I don't get it..
[Paid Software Announcement and Discussion] Emil Borconi:
Under android Auto go to about, developer settings and enable force logging, then follow description in the op on how to get a bug report..
[Paid Software Announcement and Discussion] gbch:
I am stuck on step 6. I have a Galaxy S6 and a 2017 Hyundai Elantra. After I select OBD2AA, I am unable to launch Android Auto on my head unit so I can select the last tab on the right.
[Paid Software Announcement and Discussion] Emil Borconi:
I'll try to get my hands on a Samsung phone. I think it not all but most of the person's who reported problems at connection setup are Samsung users.
[Paid Software Announcement and Discussion] peterdowney01:
I accidentally hit the option to use AA by default when plugging in to my car instead of obd2 to aa. Is there anywhere that I can reset that or be prompted for the choice again
[Paid Software Announcement and Discussion] Emil Borconi:
Settings - > apps > all apps > Google play services > clear defaults
[Paid Software Announcement and Discussion] luisgodinho:
Today I gave the ultimate chance for it to work. Factory reset...

I give up...

Maybe someday with a new phone.
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry to read that. If you need a refund please email me.
[Paid Software Announcement and Discussion] luisgodinho:
Thanks for your concern. Not yet. Tomorrow I'll regain hope... Thanks! Anyway, if someone finds the problem, please tell me here.
[Paid Software Announcement and Discussion] Emil Borconi:
What phone are you using?
[Paid Software Announcement and Discussion] gbch:
Thank you. For my 2017 Hyundai Elantra, after I connect my phone via USB, there's an icon on the headunit that changes from "phone" to "android auto," that I have to select to start AA on my headunit. After step 6, when I connect my phone via USB, the icon on the headunit stays on "phone."
[Paid Software Announcement and Discussion] Villdius:
AA freezing after instalation OBD2AA

Hello, yesterday I bought OBD2AA and it worked great, torque connected, gadgets were showing everything. But when I drive the AndroidAuto freezes after 2-5mins. It doesn't matter if it's connected to OBD or without the OBD device, it just freezes. When I open the phone it seems like the AA app is closed, when I try to open it up again it doesn't appear on my car only on my phone. To this day AA worked without any issues, without freezing, just after the instalation of OB2AA. Is anyone having the same issue, or is there any solution? Thank you.

Samsung S8, 8.0 Oreo, AA version 3.2.581534, Opel Astra K ST 2017.
[Paid Software Announcement and Discussion] Emil Borconi:
If it freezes again can you please produce a bug report? See op on how to.
[Paid Software Announcement and Discussion] poopnoodles:
G

This is what happens to me as well - have a 2018 Elantra. Hopefully a fix comes soon.
[Paid Software Announcement and Discussion] Emil Borconi:
Are you a Samsung phone user by any chance?
[Paid Software Announcement and Discussion] poopnoodles:
Pixel 2 XL on Android P
[Paid Software Announcement and Discussion] seorohana:
I wish I could change the Text size on clear gauge style. The initial text size is too small.
[Paid Software Announcement and Discussion] Emil Borconi:
Android P isn't working at the moment, I'm waiting for a donation phone to arrive so I can test.
[Paid Software Announcement and Discussion] cgtdev:
First of all, congratulations on the development. I was able to properly launch the head unit using odb2AA app.

However, iilt seams that the connection with the phone is not 100% stable yet:

If I only select the gauges tab, works great. However, if I start to switch between tabs or select a map app (Google maps or Waze), it is just a matter of time for the head unit to crash. When that happens, I have to either disconnect and re-connect the USB plug or, at some cases, reboot my device (pixel 1 xl with Android 8.1.0).

Would a bug report help?
[Paid Software Announcement and Discussion] Emil Borconi:
Yes it will. The donation pixel arrived to the UK but currently stuck at customs, I really hope I will receive it at some point next week which will enable me to relaunch the development, fixing the problem you are mentioning, as well as pie relating problems and try to figure out why some devices are just not connecting.

Before you collect a logcat please make sure you enable debugging in the obd2aa app preferences.
[Paid Software Announcement and Discussion] OSUJaws:
Hey Emil,

Just curious if you have had any luck figuring out how to fix the AA not starting when connected to the car. Let me know if you have any fixes you need beta testing on as I'd be more than happy to support fixing the app. Thanks again
[Paid Software Announcement and Discussion] Emil Borconi:
No waiting for the PIXEL to arrive so I can carry on with testing, in the meantime I'm benging my head against a brick wall because of my HUR app. I've rewritten it and while it's working very nicely for quite a few persons and on all my test devices, for days I'm trying to find a bug which makes it crash on other, and it does so without any error....
[Paid Software Announcement and Discussion] apmarmotta:
Hi! Anyone have tried to install torquepro and obd2aa plugin on raspberry pi3? I think to use the rasp as fixed on my car and connected to my Android auto capable head unit.
[Paid Software Announcement and Discussion] luisgodinho:
Xiaomi Redmi Note 4

I've been trying but without success.

Something on OBD2AA is causing Android Auto error 16.

Android Auto alone works fine.

---------- Post added at 01:25 PM ---------- Previous post was at 12:48 PM ----------

java.lang.RuntimeException: Unable to start service uk.co.boconi.emil.obd2aa.HackerService@1edc92c with Intent { cmp=uk.co.boconi.emil.obd2aa/.HackerService (has extras) }: java.lang.SecurityException: User has not given permission to accessory UsbAccessory[mManufacturer=Android, mModel=Android Auto, mDescription=Android Auto, mVersion=1.0, mUri=[url]http://www.android.com/auto,[/url] mSerial=0000000012345678]

at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3426)

at android.app.ActivityThread.-wrap21(ActivityThread.java)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1648)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:165)

at android.app.ActivityThread.main(ActivityThread.java:6365)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:883)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:773)

Caused by: java.lang.SecurityException: User has not given permission to accessory UsbAccessory[mManufacturer=Android, mModel=Android Auto, mDescription=Android Auto, mVersion=1.0, mUri=[url]http://www.android.com/auto,[/url] mSerial=0000000012345678]

at android.os.Parcel.readException(Parcel.java:1683)

at android.os.Parcel.readException(Parcel.java:1636)

at android.hardware.usb.IUsbManager$Stub$Proxy.openAccessory(IUsbManager.java:473)

at android.hardware.usb.UsbManager.openAccessory(UsbManager.java:379)

at uk.co.boconi.emil.obd2aa.HackerService.onStartCommand(Unknown Source)

at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3406)

... 8 more
[Paid Software Announcement and Discussion] Emil Borconi:
That basically implies that the app does not have permission to access UsbAccessory I think saw this at one more person (also with Xiaomi) despite the person granting permission by selecting the obd2aa app.

Is your phone rooted by any chance? Is this the stock ROM you are using?

EDIT. Do you see the prompt to chose between Android Auto and OBD2AA when plugging in the phone to the car?
[Paid Software Announcement and Discussion] luisgodinho:
No root. Updated MIUI version.

When I plug the usb cable, I get both options: OBD2AA or Android Auto.

Entering Android auto: communication error 16

Entering OBD2AA: the error I sent.
[Paid Software Announcement and Discussion] Emil Borconi:
Selecting obd2aa did you check the "Always" option? Otherwise the system might think it does not have permission... but still don't understand how the hack that error 16 comes on when you simply install obd2aa....
[Paid Software Announcement and Discussion] luisgodinho:
Not this time.

Other occasions I tried to check it but still didn't work.

Xiaomi Miui has a double profile integrated. Although I don't have it enabled, it could be related to it.

Many users refer the cloned apps as being the issues.

I don't have enough experience on android to identify if it could be the root of the problem.

---------- Post added at 03:22 PM ---------- Previous post was at 03:11 PM ----------

Not connected to car, it seems OBD2AA seems to function... Take a look at the image...

I also tried to identify the problem on Xiaomi Forum. A lot of people reporting the problem but no solution...
[Paid Software Announcement and Discussion] karma_n:
OBD2AA

I am also facing the same issue

i am using a Xiaomi Note 5 'i

ive been trying but without success.

Something on OBD2AA is causing Android Auto error 16.

Android Auto alone works fine.

---------- Post added at 04:17 AM ---------- Previous post was at 03:54 AM ----------

I am getting the foll0wing error messages

Java.lang.RuntimeException: Unable to start service uk.co.boconi.emil.obd2aa.HackerService@c37ad4 with Intent { cmp=uk.co.boconi.emil.obd2aa/.HackerService (has extras) }: java.lang.SecurityException: User has not given permission to accessory UsbAccessory[mManufacturer=Android, mModel=Android Open Automotive Protocol, mDescription=Test Application, mVersion=1.0, m.om, mSerial=0000000012345678]

at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3447)

at android.app.ActivityThread.-wrap21(ActivityThread.java)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1665)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:163)

at android.app.ActivityThread.main(ActivityThread.java:6396)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:794)

Caused by: java.lang.SecurityException: User has not given permission to accessory UsbAccessory[mManufacturer=Android, mModel=Android Open Automotive Protocol, mDescription=Test Application, mVersion=1.0, mUri=hm, mSerial=0000000012345678]

at android.os.Parcel.readException(Parcel.java:1684)

at android.os.Parcel.readException(Parcel.java:1637)

at android.hardware.usb.IUsbManager$Stub$Proxy.openAccessory(IUsbManager.java:466)

at android.hardware.usb.UsbManager.openAccessory(UsbManager.java:380)

at uk.co.boconi.emil.obd2aa.HackerService.onStartCommand(Unknown Source)

at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3427)

... 8 more
[Paid Software Announcement and Discussion] Villdius:
Hello, I used to get red screen and error 16. For me worked - settings - uncheck "use bluetooth for audio output" since then it didn't pop any error. Hope it's gonna work for you too.
[Paid Software Announcement and Discussion] karma_n:
OBD22AA

thanks for the reply but where should i uncheck the

use Bluetooth for audio output" , i cannot find it in settings

thanks again
[Paid Software Announcement and Discussion] Villdius:
Open OBD2AA - 3dots - preferences - there you should find it
[Paid Software Announcement and Discussion] Emil Borconi:
Android Pie phone arrived today, a HUGE thanks to [MENTION=5437072]bggold[/MENTION] I've installed obd2aa and Android Auto on it, plugged it in to my Sony headunit, selected obd2aa and it worked.

The phone is on stock Pie rom and there is no root.

Now this makes it quite interesting.... Is there anybody with Pie who is having difficulties connecting?
[Paid Software Announcement and Discussion] luisgodinho:
Thanks for the tip. Still get the error. It must be something on MIUI rom.
[Paid Software Announcement and Discussion] Emil Borconi:
Open Android Auto, go to About -> developer options -> enable force logging then close android auto.

Now see the OP for how to capture a bug report, please capture one and email it over so I can have a look, maybe there is a hint there relating that error 16.
[Paid Software Announcement and Discussion] c3ph3us:
Hi Emil,

I'm getting exactly the same SecurityException also on a (rooted) stock ROM Xiaomi. OBD2AA was working perfectly fine with the AAUnlock hack before upgrading.

I uninstalled and reinstalled, gave all the asked permissions, but OBD2AA crashes AA as soon as I make the choice on the prompt. The "Bluetooth audio option fix" is a no go.

Are there any further tests I can run to try to debug the crash?

Thanks.

---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------

Well, answering my own question, I'll send you a complete bug report tomorrow.
[Paid Software Announcement and Discussion] Emil Borconi:
:) OK

If you have root you can still download the unlocker: https://github.com/slashmax/AAMirror/blob/master/apk/aa_unlock.apk in which case when you are prompted to use AA or OBD2AA simply select AA and always.

Hope you don't have an error 16 as soon as you install the app.

By the way from what users have described, this my be indeed caused by twin app system on Xiaomi... I don't have a Xiaomi device to try and test myself, but it's highly likely.
[Paid Software Announcement and Discussion] crzyazn:
Using a Pixel 2 XL with stock/not rooted Pie and obd2aa crashes instantly when selecting "always" or "just once". AA works just fine.
[Paid Software Announcement and Discussion] froader:
I'm on a Pixel 2 stock Pie rooted with ElementalX kernel. Same exact experience as quoted above.
[Paid Software Announcement and Discussion] Emil Borconi:
Those of you with AA crashing instantly can you please email me a bug report?

This is so weired.... I was expecting it to crash on every pie device...