yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] horrorshow21:
Hoping someone here might be able to help as I'm not sure if I have a torque problem or an obd2aa problem.

I have a custom PID setup in torque for boost. The custom PID reads boost from PUT (Pressure Upstream Throttle) instead of MAP. I'm doing this to circumvent the 23psi limit that the MAP sensor has. It works great and reads boost above 23psi for sure.

The issue:

Unfortunately it starts the reding at atmospheric (14.5 for me) so when I hit 26 psi of boost the gauge reads 40. I would like it to just show 26.

Here is the equation being used (A*256+B)*0.1 this reads in obd2aa no problem but with 14.5 added to the reading.

When I change the equation to (A*256+B)*0.1-99 to try and remove the 14.5 obd2aa will no longer read the data, boost just always reads 0.

Attached is a pic from torque showing the equation works and is generating data. Just don't understand why it won't show up in obd2aa.

Any ideas welcome.

Thanks,

Mike
[Paid Software Announcement and Discussion] jeromeo01:
Like lot of custom pids if it works in torque it will eventually works in OBD2AA just give it time and keep using it. I have seen this plenty of time.
[Paid Software Announcement and Discussion] horrorshow21:
Thanks. I do remember reading that. I'll give waiting it out a shot. The only reason I didn't apply that theory is because the custom PID works immediately until I change the equation, then it stops. So didn't seem like that was the issue.
[Paid Software Announcement and Discussion] jeromeo01:
Yes not sure. Custom pids really behave strangely for not apparent reasons. I'm using 2 of them and really it tooks weeks before working correctly.
[Paid Software Announcement and Discussion] jeromeo01:
Love new AA 4.5.5 easier to switch from OBD2AA to maps.

Always in bottom bar
[Paid Software Announcement and Discussion] tge101:
Since Q beta 5, AA is installed as a system app on my Pixel 2. I can't figure out how to set OBD2AA to launch instead.
[Paid Software Announcement and Discussion] sacberg:
I am also on beta Q5 and it works for me. I accidentally choose AA and had to reset. See the first post in this thread and scan for HUR to reset the default app to get the OB2AA choice
[Paid Software Announcement and Discussion] easyrider1982:
can’t get it work

HI Emil,

i’ve just bought the app and i have a: Samsung s8 Android 9, MZD AIO Tweak Head unit, AA last version (no beta), OBD2forAA 3.6 beta.

Can’t get it work; if i select as default start screen OBD2 i get a black screen only and can’t do anything until i disconnect my phone from the usb cable.

If i select AA home as default, everything starts, but can’t find OBD2forAA in the android auto apps.

Anyone can help?

i followed both the install procedures, but i don’t know what further tests i can do.

Thank you in advance ;)
[Paid Software Announcement and Discussion] cameronkelley28:
Thanks so much for this! Worked on my Galaxy S10. Loving the new interface and OBD2AA is working without a hitch.

For anyone that tries this that doesn't have the sqlite binary, this method is an easy way to get it.

https://xdaforums.com/android/general/how-to-install-sqlite3sql-database-t3283409
[Paid Software Announcement and Discussion] dkostesk:
I can't get it to work can someone please help!

Using a pixel 2 and aftermarket Sony ax3000 headunit.

My standard AA is a bit figetty and I can only get it to work if I force close the AA app then reset the phone before connecting it to the car.

Ive tried like 30 times and couldn't get this app to work though.
[Paid Software Announcement and Discussion] shineangelic:
same here, with a N5X and Sony AX100. I can tell you to try again over and over, it will eventually work. Do you get "street name" notifications or not? Have you tried "option 1"? (Selecting Android Auto instead of OBD2AA) And OBD2AA 3.5 ?
[Paid Software Announcement and Discussion] Antony_b:
I've also just received the AA update for RHD - worked perfectly for me, didn't need to change/adjust anything

[IMG="AA Update"]https://i.imgur.com/sXcjO8R.jpg[/IMG]
[Paid Software Announcement and Discussion] easyrider1982:
I have tried a few times even with 3.5 stable; i always get the “street name” notification, the same for engine coolant temperature warning and so on.

I have tried option 1, and it’s the same as the second as result. Just can’t find the ODB2AA app in AA, and since it’s not starting by default on OBD2AA page, i didn’t even get the black screen.

I’ve tried even reinstalling everything a few times: AA, OBD2AA, torque PRO…. just need to try to reinstall AA head unit on MZD-AIO.

---------- Post added at 08:15 AM ---------- Previous post was at 07:41 AM ----------

Have you tried with different versions of AA head unit of MZD-AIO ?

In your opinion a ROOT of my Samsung S8, should help in any way?
[Paid Software Announcement and Discussion] shineangelic:
I am no expert, I bought this app 2 weeks ago and only could get it running correctly once, I don't even know how.

My situation looks a lot like yours, tho, with street name, background services and all up and apparently running but no OBD2AA screen whatever the option chosen to connect (1 or 2).

Since I was very curious I checked out the code from github and I notice some POSSIBLE problems with CarModeReceiver. I wrote to Emil to know if I could help, but got no reply yet. The point is that the published code is not up to date (for "security" reasons let's say) and I really can't know if my bugfix eventually works or it's totally pointless. If you want to have a look this is the fork, where I also merged Arkon's refactoring job:

https://github.com/shineangelic/obd2aa/

And this is the patch I am talking of. Basically the app declares 3 AA related event, but the receiver only manages two and this, IMHO, could possibly cause some inconsistency when repeatedly connecting/disconnecting USB
[Paid Software Announcement and Discussion] easyrider1982:
I hope Emil finds some time to look at it; i think he will also send you the updated code if for a troubleshooting purpose.

Since the situation is similar, if you need to collect also my logs, just ask!

Just let me know if something’s changing? i will do the same :good:
[Paid Software Announcement and Discussion] shineangelic:
update:

after some struggling, I managed to get it working on debug Head Unit. Practicing with it I understood that our former problem may be in app integration/head unit server status, more than in OBD2AA itself. Hard to evaluate the impact of my edits, since they're mixed with a refactoring as mentioned.

I tho it would be nice to have the free version mantained by the community, but I really don't mean to offend anyone; I am just forking open-source code :)
[Paid Software Announcement and Discussion] Emil Borconi:
Are you using the latest version of the app? Do you have any other 3rd party apps installed?
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry I haven't seen your email.

Yes this has been addressed in 3.6 beta, the problem is that Google have restricted implicit intents, so that cannot be used any longer, also most people will connect using obd2aa in which case the carmode is not needed any longer. However for those who connect using AA, I've now move to bt intent receiver instead.
[Paid Software Announcement and Discussion] Emil Borconi:
Is the headunit server running in AA?
[Paid Software Announcement and Discussion] Emil Borconi:
Are you trying option 1 or 2? Did you install the placeholder and then revert back to current version?
[Paid Software Announcement and Discussion] domesia:
Pixel 3 and Sync 3 Ford

Hi Emil

I try your software on ford sync 3 and google pixel 3.

Unfotunately it doesn't work for me. Your app crash after i choose it on the AA starting page.

Hope you can fix it,

Many thanks
[Paid Software Announcement and Discussion] stpf77:
How does the app behave when interacting (and integrating) with the updated AA interface?
[Paid Software Announcement and Discussion] jeromeo01:
Perfectly. Works even better. It's easier to go from gauges to maps or music.
[Paid Software Announcement and Discussion] NU13:
Are those gauges and icons custom made?
[Paid Software Announcement and Discussion] jeromeo01:
Yes custom needles and gauges. Took me a while to align everything.
[Paid Software Announcement and Discussion] easyrider1982:
Hi Emil, thabk you for reaching out,

i’m using MZD-AIO tweak (https://mazdatweaks.com) with embedded HU, vesion 1.11.

Not sure if answered your question though.

---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------

Hi shineangelic,

great news!

would you be so kind to share your version? :fingers-crossed:i would be so happy to have OBD2AA working in my system too.
[Paid Software Announcement and Discussion] stpf77:
Trying to install this but keeps blocking me at this point (for reference I Do have paid for xda labs)

Any ideas? TIA?
[Paid Software Announcement and Discussion] NU13:
They look fantastic!

Would you be interested in sharing?

---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------

This is off topic I know but I was enjoying new android auto (Google driving assistant) but for reason my AA has reverted back to android auto. Does anyone know how I go back to Google assistant?

Thanks
[Paid Software Announcement and Discussion] Acheng1122:
Hi Emil

Nomather what the version is 3.5 or 3.6, i can't change the tpms setting.

When i choose the setting, i will back to the default page, immediately.

When i want to try second time, the app will show me there is an issue occurred,do i want to report?
[Paid Software Announcement and Discussion] dkostesk:
Not too clear on your question but I downloaded the stable version as opposed to Beta.

Not sure what you mean by placeholder and revert to current option
[Paid Software Announcement and Discussion] shineangelic:
I was able to get it working on PC, with head unit emulator but sadly the same version doesn't work in my car. Consider that public repository has an old version and I don't think it's worth investing more time there at this point, because many things changed in AA too, as Emil reported.

I tried so many times i think i'll just stop and hope for a working version. 3.5 nor 3.6 works for me, with none of the two connecting options. I point out there are at least 3 different instructions on how to get it working, i think the most recent one mentions that placeholder thing, but that's pretty unclear to me also because i can't find obd2aa on public play store (only beta) but only on xda labs and I can't guess how they relate.

An unified doc with some troubleshooting faq would be of great help I imagine, but My issue in the end is always the same and still there: I can see obd2aa notifications on android auto but no gauge screen. The phone has the 'running' notification of obd2aa and torque looks fine, but i have no 5th screen on head unit.
[Paid Software Announcement and Discussion] chrisonmoon:
Hi - beta version works perfect with sony xav1000 & AA 2019. Even no need to start server in AA with S10+

Chris
[Paid Software Announcement and Discussion] tydoo:
Hello all !

I'm french. Sorry for my bad english ^^

What is the good tutoriel for root user ?

- The tutoriel on the 1st page, or

- the tutoriel on xda labs ?

Thanks you
[Paid Software Announcement and Discussion] bioman78:
Hello,

I tried and run your app on an unrooted Huawei P30 and Honda CR-V V car, both on 3.5 (stable) and 3.6 (beta).

I cautiously followed each step of the tutorial but still remain unable to have your app work : my car says "incompatible smartphone" (when it does work with the standard AA).

Between each attempts, I cleared data, deinstalled, rebooted, reinstalled...

Any idea as for how I can troubleshoot the issue ?

Please help as I am stuck here :(

Thanks a lot in advance, BIOMAN ;)
[Paid Software Announcement and Discussion] Emil Borconi:
You need to install XDA Labs, please see the first post on how to.
[Paid Software Announcement and Discussion] Emil Borconi:
Try option 1 described in the OP please.
[Paid Software Announcement and Discussion] Emil Borconi:
Please see OP the section on how to get it running there are 2 options there.
[Paid Software Announcement and Discussion] gantonski:
i've been trying to research this stuff and its a crazy rabbit hole.

in the OP there is a line that says gauges wont work on a phone - are you using a different device? I'm confused by this!!

i really just wanna customize my gauge layout, connect and stream my music from my phone, and maps sounds like a bonus too!
[Paid Software Announcement and Discussion] jeromeo01:
Meaning you cannot only use your phone to see the gauges. You need to connect it to an Android Auto compatible car head unit.
[Paid Software Announcement and Discussion] gantonski:
GOTCHA! good news.

thanks !!
[Paid Software Announcement and Discussion] dkostesk:
Hi have taken a look at option 2 downloaded the beta testing thing from play store. Instructions are not too detailed so not sure what else I'm supposed to do but after downloading this but the obd 2 app doesn't let you do figure the guages any more.

And the Android auto app doesn't give you any more functionality.

Can you provide more detailed instructions or refund the price of the app.
[Paid Software Announcement and Discussion] thierrybo:
Hi,

first of all, I managed to run the software using option 1, option 2 did not work for me. However I didn't really understood what I did in option 1 :

I'm new to XDA app, I did not found an "update" option, so I installed the "beta" version instead of the standard one ??

I disabled auto-update globally in Play Store, but what is the purpose of that? Block updates for one app (which one?) or prevent downloading any of all others PlayStore apps to their beta version?
[Paid Software Announcement and Discussion] geronracing:
Works Great on a Samsung T380!

However, the scaling of the gauges doesn't work correctly. Cannot adjust the "0" of the gauge to a higher number. IE if a value of 19 should be the lowest on the gauge, and adjusting the range in the setting for the zero to be 19, it doesn't make 19 the lowest on the gauge, it seems to make it higher.
[Paid Software Announcement and Discussion] starfly2:
Hi together, was some years off, now back again and I've worked the whole day on the plugin. Or better said, tried to get it working.

Some notes from my side :

Phone : Total Stock SAMSUNG Note 9 (android 9, all updates)

Headunit : VW Discover Media, over USB Cable

Android Auto is the newest Version.

Android Auto works as long as I install Version OBD2AA.

Version 3.5 Crashes while launching after connecting the Cable, Android Auto starts and collapses instantly .

Version 3.6 crashes while launching after connecting the cable - same as 3.5.

Special Sidenote : Version 3.3 from archive works perfect - exactly for 2 starts, afterwards it crashes also randomly (reinstalled, cleaned etc.. No chance - works 2 times - game over since).

A little bit annoying is the fact that the old version 3.3 worked fine for 2 times - so something was working OK for my phone with the old version.

Deleting the app at all from the phone results in a instantly working Android auto.

My hope is to find someone with the same experience about version 3.3 and how to get it working again. 3.5 would be nice too, but this one never worked here.

Thanks a lot!
[Paid Software Announcement and Discussion] BradEvansClarke:
Did you ever work it out? I'm stuck at the same step... I installed and ran the XDA app on my phone loaded up the OBD2 app page and clicked install (from within the XDA app), and it told me to install it from the XDA app.
[Paid Software Announcement and Discussion] stpf77:
Yeah mate, install placeholder (from playstore link), uninstall it, open xda, download working version from xda app store, don't use links in the thread. That's how I got it working.

GL
[Paid Software Announcement and Discussion] froader:
Exactly, but the point of installing from the play store first is to sign up for the beta in the play store listing, then uninstall and install from XDA. Don't forget to uncheck auto-update in the play store for this app.
[Paid Software Announcement and Discussion] DavidFB1973:
Hi all,

In the new released version of Android Auto (new interface) I don't find the street cards anywhere. In the previous version, they appeared in the main screen.

Is there any way to see street cards in the new AA?

Thanks!
[Paid Software Announcement and Discussion] jeromeo01:
Yes press on little bell at bottom of screen. The one for messages.
[Paid Software Announcement and Discussion] stpf77:
Yeah, this.

The bit that was doing my head in was the link in post1 for the full app kept spitti g the placeholder out. Was pure serendipity that I figured it out - was in labs app store looking for something else and that bright green accent colour jumped out like a drop bear
[Paid Software Announcement and Discussion] DavidFB1973:
Nope... in the notifications screen (pressing on the little bell) I can see other kind of info. For instance, WhatsApp messages or missing phone calls.. But not the street cards. They do not appear there.
[Paid Software Announcement and Discussion] jb.traveller:
I gave up last year as I really thought Goo**l had stuffed us but I have just followed the new instructions and hay pressed O I am up and running again. Haven't been out on the road yet but sat in the car and watched the OBD2AA working. Thanks Emil great work.

PS Vauxhall Corsa 1.4 energy samsung s7.
[Paid Software Announcement and Discussion] starfly2:
Tell me exactly what you do - because I've tried it several times, no chance on samsung note.

Could someone post the "placeholder" app here? I don't have Google on my phone.
[Paid Software Announcement and Discussion] jb.traveller:
Emil, a quick question Google wants to update Play services should I. As OBD2AA is working and don't want it stoped.
[Paid Software Announcement and Discussion] boston460:
Hi Emil,

OBD2 for AA has been a great app. I mainly use it to monitor the soot load of my DPF.

However I'm unable to change the information in the TPMS, as soon as I try to change the values it crashes OBD2 for AA. I've tried the stable version and the Beta version and both options of installation. All with the same result.

I'm using a Galaxy S7 on Oreo

Is there anything else I should try?
[Paid Software Announcement and Discussion] froader:
Guys! I've been down the root road for a long long time, therefore used method 2 for making this app work. That was great and all, but required constant maintenance of stopping both OBD2AA and AA in order to start headunit server and then reconnect my phone to the headunit.

Interestingly enough, I've gone rootless since about beta 3 or 4 of Android Q and was surprised to see that OBD2AA still working. Now without the headaches of the rigamorol of making sure the headunit server is running and in the correct order for AA to work.

Simply follow the instructions in the OP to ensure that method 1 is used and that's all you have to do. FYI, the Play store install/uninstall deal is just to be signed up for the beta in the event Google allows Emil's bad ass app! If you are in that boat as I am, simply disable auto-update in the play store for OBD2AA and then instead of update all, you will have to update each app other than OBD2AA if you are presented with the opportunity, otherwise the apps will auto update per your settings as normal, just not OBD2AA.

I'd imagine the more of us stay locked to the beta signup, the greater likelihood we help Emeril get in the store. Of course you can unenroll from the beta in the Play Store and not be supportive. That's your call.

As far as questions about other apps and Google services, that need not be even messed with. Just let it roll and stop thinking about it. The new AA + OBD2AA are living fine and we'll together using install method 1 on my Pixel 3 XL on the latest Android Q beta.

That's it and that all folks. Really pretty straight forward!! There must be some issues with other phones or some overthinking going on... If you need to start over, either uninstall and reinstall each app or at least clear data and you have a clean start at step 1 from install method 1 in the OP.
[Paid Software Announcement and Discussion] robert.s79:
Obd2aa died on me last week. Everything was working fine for months then music began skipping and screen locked up. Then the next day i received the unsupported device error on my car unit when plugging in. Tried another cable, same error.

Bottom line, I've tried every single combination of option 1 and 2 and none work. They all create the unsupported device error on my head unit.

Once I try a method it locks up android auto to where i have to uninstall aa and obd2aa and reboot, reinstall aa.

Note: in the new aa, dev mode is entered by tapping the version icon 10 times. Interestingly, "start headunit server" exists in a fresh install of aa when without any install of obd2aa (placeholder or xda version)

4.5.592854 aa

Samsung s9+

Android 8.0.0

Is there a way to delete the "headunit server" and reinstall it? I'm thinking it's corrupted, or tell my why it's always there?

Any other ideas?

Thanks!

-Robert
[Paid Software Announcement and Discussion] bggold:
That is part of aa so if you installed aa then you removed the hu too.

Try turning the hu off and disable dev options then uninstall and reinstall.

Also could be your Google play services.
[Paid Software Announcement and Discussion] PeQuEsan:
Just discovered this app after some weeks thinking that the only way to make Torque show something in my AA enabled HU was rooting my phone. So many thanks for this app. I just used method 1 with not even a problem. I'm happy. :)

Just one thing: I would like AA to show this app by default when connecting my phone to the HU. I see there's an option inside settings that seems doing what I want (default screen at launch). I've configured that to Obd2aa, but AA is still booting Maps by default.

Is that option working at all? Could it be that I'm running new AA layout?

Thanks a lot.
[Paid Software Announcement and Discussion] PeQuEsan:
Another little bug. I don't know how many people using this app has upgraded to Android 10. I've got a Pixel 3, and yesterday evening I got Android 10.

From that moment, when you jump out of the car and car bt disconnects, Obd2aa doesn't shutdown itself... Then, when you click the notification icon, Obd2aa shuts down.

Can anyone in Android 10 (beta for example) confirm if this is happeing also for him, or it's my fault?

Thanks a lot.

EDIT: Could it be that this setting only works if obd2aa installed using method 2? I've installed it using method 1, which I assume is recomended one, and I would like to mess it now...
[Paid Software Announcement and Discussion] Goon818:
This is not a new bug. I have a pixel 3 too.

I have this problem since two month. You have to select in the option from obd2aa the alternative pulling and the car's Bluetooth.

I wish me , that I can select more as one Bluetooth device. I have to car's. Every time I must switch it.
[Paid Software Announcement and Discussion] PeQuEsan:
Sorry I don't understand you very well. Do you say you also have the problem that odb2aa doesn't close when you jump out of the car? Did you solve it some way? Using alternative pulling? Could you be more specific?

Desde el móvil...
[Paid Software Announcement and Discussion] Goon818:
Yes. OBD2AA need a new trigger to start and stop. For this reason has Emil make an new option. Look for the last beta. Now he use the Bluetooth connection from one device in your car. For example the audio device