yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] lBrownThunderl:
I am rooted but I have to turn the head unit server on for obd2aa to work am I doing something wrong. I'm using a rooted OnePlus 6t, and my head unit is a pioneer avh2300-nex
[Paid Software Announcement and Discussion] Dr. Claw:
Does this behavior occur only when attempting to use OBD2AA, or does AA work normally?
[Paid Software Announcement and Discussion] Hodgo1981:
AA can still work normally. Since the reinstall when I plug it in and prompts for AA or Obd2aa, I have been choosing just once option, and with AA it works, but not with this app.
[Paid Software Announcement and Discussion] bggold:
There are ways to do it and all I can say is do a Google search.
[Paid Software Announcement and Discussion] Dr. Claw:
Hmmm... Looks like you may need to capture a bug report and send it to Emil. When I had this issue I had to change USB cables
[Paid Software Announcement and Discussion] bggold:
As for the head unit there is a big that [MENTION=224120]Emil[/MENTION] will hopefully fix soon. Use Tasker or automate to turn it on and off and make sure to deny root to obd2aa.
[Paid Software Announcement and Discussion] FizzGiGG:
Ever since some update that occurred in the last couple of days/week, obd2aa says that the Google Assistant is running and is a competing app, or whatever the error is. It won't run anymore. Sorry if this was already discovered and talked about earlier. I have auto updates disabled, so it was probably a week ago...

Google Pixel 2

Android 9

AA 4.4.592344-release

Google 10.16.6.21.arm64
[Paid Software Announcement and Discussion] d3mon_fx:
I just got the "Restricted apps found-google assistant" on the stable version. Installed the Beta, AA will work but OBD2AA will not. It has worked for a year without problems... anyways I know Emil is probably working on a fix but for the time being, any workarounds?

Using a Note 8 SM-N950U non-root and a Pioneer AVH-2300NEX
[Paid Software Announcement and Discussion] bggold:
What is the version of your Google app and playstore services?
[Paid Software Announcement and Discussion] cameronkelley28:
OBD2AA stopped working for me this morning when the Google app updated from 10.12 to 10.16. There were no errors and android auto worked fine on my headunit but nothing from OBD2AA was taking affect.

After downgrading the Google app back to 10.12 I can confirm that OBD2AA is now working fine again for me.

For those with root, here are steps to manually downgrade to 10.12:

Download Google app 10.12

https://www.apkmirror.com/apk/google-inc/google-search/google-search-10-12-5-release/

Open a file explorer with root access. I use solid explorer.

Navigate to /data/app/com.google.android.googlequicksearchbox-70j6Bjw1Ww4q6hjwCfN7Eg==

NOTE: the ending after com.google.android.googlequicksearchbox may be different for your phone

Rename base.apk to base.apk.bak

Rename the downloaded Google app apk to base.apk

Copy the renamed 10.12 base.apk to your Google app system dir

Eg. /data/app/com.google.android.googlequicksearchbox-70j6Bjw1Ww4q6hjwCfN7Eg==

Ensure permissions of the apk are correct (644)

After a reboot you should be back on 10.12

For those without root, unfortunately the only option as far as I know is to open the app info page for the Google app in system settings and choose "uninstall updates" from the three dot menu on the top right. The location of that button might vary per phone.

This will wipe the data for the Google app.

After that you should be able to download 10.12 from APKMirror and install normally.

MAKE SURE TO DISABLE AUTO UPDATES OF THE GOOGLE APP AFTER DOWNGRADING
[Paid Software Announcement and Discussion] ChainringCalf:
I'm getting the same error on a Galaxy S9 (SM-G960U1) and (2018) Mazda system. I just downloaded the app for the first time today, though.

Play Store: 15.4.22

Google: 10.16.6.21.arm64
[Paid Software Announcement and Discussion] bggold:
Guys I have done some tests for [MENTION=224120]Emil[/MENTION] and confirmed the issue and a possible fix for him with the Google app v10.16. I'm sure he will work on the fix soon.

Probably no need to report it anymore as it will just clutter up the forum.

I am in close contact with him so he is definitely aware of it.

By the way the temporary fix is a few posts up. It will probably be a little while before Google forces the update.

Hang tight.

Thanks
[Paid Software Announcement and Discussion] NU13:
Yep this same problem I'm getting to. Keeps asking me to uninstall competing app Google assistant.
[Paid Software Announcement and Discussion] Goon818:
I have the same Google version. But it's working.

Use you opd2aa with option one or two?

I use option one.
[Paid Software Announcement and Discussion] froader:
So, I accidentally uninstalled OBD2AA and when I reinstalled it I once again selected AA as the default since OBD2AA had not been working as the default once AA headunit server was running. I can say that I am able to see my torque gauges once again as intended.

Pretty strange, I was previously not able to see the gauges when AA was set as the default and only when OBD2AA and headunit server running.

This was working with Android 10 Beta4 and also with Beta5. I'm pleased this is working!

BTW, I'm no longer rooted for the first time in history!! No feasible Google Pay workarounds finally did it and the maturity of Android really helped!
[Paid Software Announcement and Discussion] Emil Borconi:
Fix to be expected tomorrow, as it's being tested on the road today. Normally it won't require tests, but as I had to rebuild a significant part of the app I prefer to test before release.
[Paid Software Announcement and Discussion] froader:
Thanks Emil. Good luck with the testing and looking forward to any update as always. PM me if you'd like to discuss a backup scenario. It's a small part of what I do for a living and there are many ways to do so!
[Paid Software Announcement and Discussion] Emil Borconi:
Thanks, well I do know that, but you know when you are too sure of yourself, oh this will never happen to me.... type of thinking... well I've paid the high price...

Learned from the mistake, auto-backup is in place now :)
[Paid Software Announcement and Discussion] horrorshow21:
Just in time. My Google just finally updated last night breaking obd2aa. Lol.
[Paid Software Announcement and Discussion] d3mon_fx:
I can confirm that this works, actually works very good because it didn't use to work on my Focus RS with sync 3 and now it does. I wish there was a way to create separate profiles for different cars, Is this possible?
[Paid Software Announcement and Discussion] Emil Borconi:
App updated, let me know if you face any problems.
[Paid Software Announcement and Discussion] froader:
I hear ya and it stings more in that situation. Anyway, glad you got it sorted out now.

Also, thanks for the app update. I'll check the OP for a changelog and install.
[Paid Software Announcement and Discussion] horrorshow21:
Working here. Thanks!
[Paid Software Announcement and Discussion] mailkeulkeul:
By opening tpms, the app close when I want to input the sensors
[Paid Software Announcement and Discussion] tek_ids:
It work again!
[Paid Software Announcement and Discussion] FormelLMS:
Oh, with the latest update, OBD2AA stopped working for me. It doesn't start when plugging in.

My installation routine was option 1. Do I have to do the stuff again?
[Paid Software Announcement and Discussion] Emil Borconi:
I'll check.
[Paid Software Announcement and Discussion] Emil Borconi:
You will probably need to redo the steps.

Edit: Does it stopped working all together or did it stopped auto-starting, meaning if you open the 5th tab you can see and open obd2aa, just id doesn't auto-start?
[Paid Software Announcement and Discussion] buck2202:
I'm seeing this as well. There's a persistent and noticeable position error using google maps for navigation, and occasionally it indicate it's lost its position lock. I don't notice any issue in Waze.

Any information that would be helpful in debugging?
[Paid Software Announcement and Discussion] froader:
Update on the update. On Android 10 Beta 5. As previously mentioned, I've not had any issues since reinstalling and using method 1 in the OP (I was previously unaware of working...). Anyway, since the new update all is still well and working awesome! Thanks Emil!
[Paid Software Announcement and Discussion] Emil Borconi:
Try to turn off the 6 tap limit remover
[Paid Software Announcement and Discussion] buck2202:
Uh oh, that's the main reason I purchased the app...is this expected behavior? I'll give it a try the next time I'm in the car.
[Paid Software Announcement and Discussion] Emil Borconi:
No but on some devices it does play up for some reason... :(
[Paid Software Announcement and Discussion] BKGarrison:
Sorry if this has been covered, but search didn't find it.

Trying to install this for the first time today and ran into a problem enabling developer settings in Android Auto. It seems you no longer click on the "About Android Auto" header. You now need to go into settings and click on "Version and permission info" 10 times.

Then the 3 button link shows up as normal. This is on Pixel 2, AA version 4.4.592344
[Paid Software Announcement and Discussion] buck2202:
Alright, so disabling the tap limit remover did eliminate the issue from maps navigation...I'm guessing Waze isn't affected because only maps currently uses the car GPS? When you say "some devices," do you mean my phone or my head unit?

Is there any hope of a workaround? For example, are there any tunable parameters for how much/how often sensor data is modified to avoid the tap limit? Like, if you're doing something like "every x seconds freeze car gps position for y seconds", is it possible that some other combination of x/y would work without messing with navigation? Or is it possible to make the sensor modification happen on an "as needed" basis (like, only when the tap counter is non-zero) rather than presumably happening in the background all of the time?

Happy to provide any information that would be helpful
[Paid Software Announcement and Discussion] Emil Borconi:
Email me directly please on borconie@gmail.com
[Paid Software Announcement and Discussion] FormelLMS:
Hi Emil. Unfortunately it doesn't did the trick.

It seems that it stopped working completely.

After first start it asks which app I've wanted to use, ticked "Android auto" instead of OBD2AA and normal Android Auto comes up. No night/day setting and no speed camera alert.
[Paid Software Announcement and Discussion] Emil Borconi:
But does obd2aa shows up in the fifth tab or not?
[Paid Software Announcement and Discussion] froader:
A little more feedback. Since using option 1 for running OBD2AA, gauge output has been great. Today, the gauges weren't getting any data, however I verified that Torque was connected and receiving data. The next drive was the same thing. I'll do a reboot and see if that helps.

Is there anything I should be checking to narrow down the issue?
[Paid Software Announcement and Discussion] Emil Borconi:
No idea to be honest but if this happens trim on debugging and capture a bug report please.
[Paid Software Announcement and Discussion] froader:
FYI, after the reboot the gauges were back reporting data, but all of a sudden the top of the screen started to get cut off and all pixelated. My head unit was pretty frozen up until I unplugged my phone. I did notice that after removing from the head unit, Torque was still running whereas it would previously close on exit, but then again, I was also using metod 2 using this app.

Pics attached and I have debugging all setup for the next drive, which should be this evening.

Thanks!
[Paid Software Announcement and Discussion] FormelLMS:
Uh, oh, totally unseen this. Sorry!

You are right. I can see OBD2AA on the fifth tab and can start it, but it doesn't autostart.

After starting it manually, the screen goes to day theme as expected. After shutting light off and on again it stays in dark mode as if OBD2AA stopped working immediately. No speed camera alerts are seen.

So I think it doesn't autostart and it is shutting off immediately if not staying on the fifth running tab.
[Paid Software Announcement and Discussion] froader:
Well if course not a single issue both times since the reboot...
[Paid Software Announcement and Discussion] FormelLMS:
Update to not starting automatically issue:

If I enable the street names, it doesn't atuostart, too, but it stays alive the whole drive.

But: It doesn't shut down after stopping AA then.

Without street names, I can start with the fifth tab, but it disables immediately. I see it, when I switch off the headlights and on again, it stays in dark mode (as silly google has programmed their "cool" AA)
[Paid Software Announcement and Discussion] Dr. Claw:
I was having issues with the beta on a OnePlus 7 Pro (@Emil Borconi, I sent you the logs). No crashes thus far since the update.
[Paid Software Announcement and Discussion] froader:
[MENTION=224120]Emil[/MENTION]

Using install option 1, I've noticed that Torque Pro remains running some times after unplugging from AA. Should the normal behavior close Torque as it did with install option 2 that I previously used?
[Paid Software Announcement and Discussion] Emil Borconi:
I'll check now, the mentioned issues with option 1. When I rebuild the app I used the latest SDK and I think the problem is caused by removal of implicit intents starting with nougat SDK, those intent allowed the app to listen when it entered car mode and when it exited. Of course this will have no effect when you start the app with second method as the app is aware of the USB connection to the car, but not when you run AA normally. I might have to add an option to listen for BT hansdfree connection as that is one of the very few implicit intents which still works.
[Paid Software Announcement and Discussion] Antony_b:
Not sure if this has been covered elsewhere in the thread(I had a look but didnt see anything)

Is there a way (or possible feature suggestion?) that with the Boost/Vacuum gauge(ff1202,0), that one can make the percentage arch read from the 0 point, not from the lowest-scale-value point(eg: -20)?

Otherwise i'm exceedingly happy :) Keep up the great work Emil
[Paid Software Announcement and Discussion] tinleo:
I have just bought this app and Torque pro, but when I connected to Mazdaconnect. I got black screen with option 2, and I got only Street card if start with option 1 There is no OBD2AA ON 5TH tab of Android Auto
[Paid Software Announcement and Discussion] Dr. Claw:
[MENTION=842765]Emil Borconi[/MENTION], I spoke too soon. I'm getting random OBD2AA crashes while in motion on my OP7P.

Using the beta channel of OBD2. Sent you a log file.
[Paid Software Announcement and Discussion] roro4g63:
If any Samsung S9 users here, I found a work around to use Torque with AA.

I had to turn off auto start Torque App in OBD2AA settings

connect with Torque App.

After "ECU OK," connect to my HU (Pioneer NEX 3400).

At promp connect with AA.

Go to 5th tab, select OBD2AA

After a few seconds, Gauges began working

Before, I would occasionally get the engine up to temp, but when going to gauges, it would work for a few seconds and freeze.

App runs fine now, but only problem is Spotify volume randomly decreases like when directions are being given. Didnt do that before.

Sorry for long post
[Paid Software Announcement and Discussion] jeromeo01:
I have been using S9+ for almost 2 years now with no problem.

Never had to disable anything.

Until yesterday with last update where I cannot select obd2AA anymore. Only return to Volkswagen option.
[Paid Software Announcement and Discussion] froader:
Are you saying with Torque autostart turned off, once connected to AA selecting OBD2AA Torque starts up?

I have autostart enabled and the issue I'm having is that Torque continues to run after disconnecting from AA.

What happens to torque is your instance?
[Paid Software Announcement and Discussion] roro4g63:
After I disconnect, I close all apps. Sometimes AA still keeps Do not disturb, so I just got used to closing all apps.

My issue with Torque is it would freeze if it actually loaded via OBDAA2. AA would run fine, maps, calls, google assistance and Spotify worked properly; just Torque would not run.
[Paid Software Announcement and Discussion] Goon818:
I have a similar problem. OBD2AA is not starting everytime and it's not stopped always. Two times I have the problem that the phone is vibration that the update from the database for the speed cameras are updated. And I'm not seating in my car over a hour.
[Paid Software Announcement and Discussion] bggold:
Hey guys it is great that you are reporting these issues, but Emil cannot fix them without some info.

Please do the following:

1. In developer options increase the log size to the max.

2. In OBD2AA enable logging.

3. In developer options of AA enable logging.

4. reproduce your issue.

5. grab a bugreport.

6. email it to Emil and include what head unit you are using, phone model, android version and if you have root or not.

7. go back to steps 2 and 3 and disable logging. If left enabled it will spam your logs.

I know from working with Emil that he is able to fix most issues from looking at the logs.

Thanks
[Paid Software Announcement and Discussion] froader:
I plan to and have a bug report, however I've not been able to get clarification on using Install version 1 should close Torque when unplugged from AA. Torque currently stays running while my previous experiences have all been with install version 2 which did in fact close Torque upon AA disconnect.

If there is no bug to report, I certainly don't want to pester Emil, however if there is unexpected behavior, I'm certainly happy to help.
[Paid Software Announcement and Discussion] bggold:
Hey no problem. It was more for the "it doesn't work" posts with no info. I will confirm today if torque closes on exit. I have a flow that kills obd2aa and torque because of an issue I had a while back and never changed it since I had no issues. I just removed those and when I go out later I will test for you.

Thanks
[Paid Software Announcement and Discussion] froader:
All good! That will be great and to make sure we are using the same setup are you using install version as I am? Since I got rid of root after countless years I had to factory reset my phone and simply reinstalled apps. OBD2AA does in fact take advantage of Android backup, so it restored settings. Other than that I've not done a thing other than setting AA as the default app. Pleasantly to my surprise I've still had OBD2AA working displaying data. So, that's where I'm at these days install version 1.

Best!
[Paid Software Announcement and Discussion] bggold:
Method 1 used and torque shuts down for me.

Thanks
[Paid Software Announcement and Discussion] froader:
Thanks for verifying your setup and that Torque shuts down. I'll go ahead and send that bug report over to Emil then.

Thanks!

Edit, looks like I did send it over a couple of days ago...
[Paid Software Announcement and Discussion] tristanmartel:
Got her working sort of. Thank you emil for your efforts.

Just having an issue where torque loses all the data streams as soon as my phone screen locks. Huawei P10, wondering if it's an easy setting adjustment.

Also, wondering if there's a good resource to find all the available PID data for my 99 4runner.
[Paid Software Announcement and Discussion] sacberg:
New user - install no problem. I do have two non displaying PIDs. Oil temperature and a custom one for GM oil pressure. Works in Torque. I searched the thread but couldn't see if there was a method to resolve. If there is please point me to it if you could. Thanks.
[Paid Software Announcement and Discussion] jeromeo01:
If your custom PID works in torque but display in OBD2AA stay at 0, just wait and keep using it. It will eventually works. I'm not sure why and how but it works for me. (Had to use it for a while.)
[Paid Software Announcement and Discussion] sacberg:
Well the custom PID worked for a little while today I guess I will just hope it gets better with time. The Torque defined oil temperature PID has not started working. Coolant temp works fine so it is not a big deal
[Paid Software Announcement and Discussion] maxmike181:
Has anyone tried the app with the brand new AA2019 update? I know we used to access our gauges through the "exit" menu, I'm wondering if the app works on the new version or if we should hold off? And if anyone does have it working, how does it show up on the screen? Thanks.
[Paid Software Announcement and Discussion] jeromeo01:
Does for me. But had to disable 6 taps option.
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry guys for being radio silent, as you might know I'm preparing to move at the end of August from UK to RO and gush, if you think coding is hard, try to get a team of builders to do the job on time, and sort out all the bureaucratic hell in RO....

Small update currently in beta:

- CarMode is now detected based on BT state (should fix obd2aa not auto starting and closing when connected trough AA directly. This is where you use the PlaceHolder trick to activate obd2aa scenario)

- Added a workaround for GPS lag when using tap limit remover.

Again, if you need me and there is no sign of me on the thread please email me as I will always reply to emails much quicker and easier then to the thread.

Also, if anyone has the new AA and can share some screenshots will be nice :D
[Paid Software Announcement and Discussion] fold93:
Hi Emil

About new AA - grab the latest APK from apk mirror, install it and delete cache&data of Android Auto.

Afterwards open the app on the smartphone, go into settings and activate the "Test new interface" blabla.

Now you are all set up to test it on your own.
[Paid Software Announcement and Discussion] Emil Borconi:
That doesn't work for everyone, as it's a server-side switch as well.

I found a way how to activate it though but it's root only: https://www.google.com/url?q=https:...383000&usg=AFQjCNFaPdr2xaJ7K1iFYGBmAGwa7De4_g
[Paid Software Announcement and Discussion] ttlycnfuzd:
[MENTION=842765]Emil Borconi[/MENTION] - sorry for the potato quality, but here's some quick pics of the new interface, with OBD2AA running as well. DPI change works as well... 160 (default) seems too large, and 120 makes the dialer teenie-tiny, so 140 fits nicely in the middle. Makes certain elements smaller and out of the way. And, yes, I'm a minimalist when it comes to my gauges... haha

Thanks again for all the support on this app!
[Paid Software Announcement and Discussion] Emil Borconi:
Thanks for sharing!
[Paid Software Announcement and Discussion] jeromeo01:
I installed AA4.5.5 but still got old interface.
[Paid Software Announcement and Discussion] shineangelic:
Same here. Tried many times, following instructions and changing various options/start order. The best I could do was street name in AA home, but no 5th tab. I had "hack running" notification and torque connected, but no new screen. Using both stable/beta on Lineage, android 8, nexus5X and ax100 head unit
[Paid Software Announcement and Discussion] shineangelic:
After many trials I could get it working, but it's not stable, it sometimes hangs when exiting and then never works again until restart. The problem is that under these circumstances i cant use Android auto at all, I see the running icon and all, but at that point AA is started on my phone and not on the HU.

Sorry to say, I had to uninstall it. I understand this app's task is non-trivial, as I'm a developer myself and integrating intents is rarely easy. But with my current setup OBD2AA simply isn't reliable enough for daily usage.