yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] c3ph3us:
I got the error 16 if I select AA. I'm sending you the bug report.

BTW, I'm not using cloned apps, this is a stock MIUI system with minimal configuration that I use solely on my car.
[Paid Software Announcement and Discussion] crzyazn:
Just sent you the bug report.
[Paid Software Announcement and Discussion] Schulle1234:
Hi Guys, i have a Xiaomi Redmi Note 4. Same issues as posted above. Choosing AA Always gets The 16 Error. Phone is not rooted and has No custom stuff installed. I Hope we get any solution.
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry but it does looks like Xiaomi MIUI asses up quite a few things, AppOps is changing some userid's which is causing problems. I don't think there is too much I can do about it.

If you bought the app and a Xiaomi user please email me for a refund.
[Paid Software Announcement and Discussion] Emil Borconi:
The good news is that it looks like I've managed to fix the problem with Force Close on Pie as well as the problem of occasional hanging one some devices (especially when switching to maps and back to obd2aa).

I'm doing a bit more of code clean up, also trying to make the tap limit remover to work correctly and probably I will be pushing out an update in the near future, this update will be bug fix and stability fix update, no new features or changes will be included.
[Paid Software Announcement and Discussion] FormelLMS:
Hi Emil,

sorry, I was in France the last weeks.

On my Pixel XL OBD2AA doesn't show the alerts. Street names are working, day/night switcher works, too.

For me, the speed cam alerts are important. I don't run the server thing, only installed the app, give it their permission and checked the developer options in AA.

Should the speedcam thing work?
[Paid Software Announcement and Discussion] Jon Avalon:
Hmm I keep getting myself stuck after Step 6. AA doesn't connect to the headunit and stops connecting in general. It was launching fine before I started. I eventually tried another cable to get AA working again so I uninstalled everything and started over again. But same thing happened by the time was doing step 6. Am I doing something wrong?

I've cleared defaults, rebooted, even uninstalled OBD2AA and AA but nothing works. There is also no defaults to clear for Google Play Services. The phone charges fine, just AA doesn't connect. My iPhone launches carplay no problems so any ideas would be appreciated.

Phone: Samsung S9

OS Version: 8.0.0

2018 Subaru headunit
[Paid Software Announcement and Discussion] bggold:
Have you tried enabling developer mode on your device?
[Paid Software Announcement and Discussion] Jon Avalon:
Yep it's enabled. I think there is just something up with the way this is all working with the phone. After letting the car sit for a while and I came back to it to drive out somewhere and it worked fine. I still had to battle Bluetooth issues with the OBD2 adapter and the app constantly disconnecting. The issues eventually stopped, it functioned fine while driving around for a bit. But then when I disconnected the phone, turned off the car to go into a shop and come back..........the original issue returned

So I'm not really sure what's up lol
[Paid Software Announcement and Discussion] Emil Borconi:
Version 3.1 release:

- Compatibility fix for Pie devices.

- Freeze issues fixes.

- Tap limit remover now working on all device

- Tap limit remover allows Maps to be searchable even when driving.

- Can be used for those who have problem with the parking brake wire.

I suggest those who struggled with version 3.0 to get the connection up to give this version a try.

Sad news for Xiaomi user, this will not work on your devices, due to MIUI braking things, if you purchased the app and have Xiaomi please contact me for a refund.
[Paid Software Announcement and Discussion] bggold:
Emil great work in such a short period of time.

No more Pie issues.

Seems to be much faster than previous version.

Tap limit removed, can search from maps. Also noticed on my rooted device I no longer need to manually start or stop hu server.

Thanks
[Paid Software Announcement and Discussion] tdiman:
Hi Emil,

If I have no interest in Torque but am interested in removing the tap limit, do I still need torque Pro? What's the most minimal install?

Thank you!
[Paid Software Announcement and Discussion] Emil Borconi:
Just obd2aa will suffice, but you still need to follow the op on how to get it running.
[Paid Software Announcement and Discussion] FormelLMS:
Hey Emil, is headunit server needed for speedcam and the day/night automatic?
[Paid Software Announcement and Discussion] Emil Borconi:
The headunit server is needed for obd2aa to be able to interact with the car if you aren't using obd2 data, select android Auto when prompted and don't bother with the server, notifications should still display
[Paid Software Announcement and Discussion] FormelLMS:
Emil... Did I say already, that I love you?

Thanks. Missed your app in France ?
[Paid Software Announcement and Discussion] NU13:
Great work on the update Emil. Will the update help those of us with the Samsung connect issues? In particular the unsupported device issue. Thanks
[Paid Software Announcement and Discussion] Emil Borconi:
Should do, but since I don't have a Samsung I couldn't test, if it doesn't I will get my hands on an S7 for test purpose, I need some feedback please.
[Paid Software Announcement and Discussion] FormelLMS:
I wasn't on my car, but I can see, that OBD2AA starts Torque at start, even if unchecked this option.
[Paid Software Announcement and Discussion] Emil Borconi:
I'll check
[Paid Software Announcement and Discussion] FormelLMS:
Hi Emil,

I'm sorry, but I can't get the speed camera alerts to show.

Street cards are showing on my Sony xav ax, but not the speed cams.

Using an unrooted Pixel XL with Pie.
[Paid Software Announcement and Discussion] alexdets7:
Android auto won't start on my car at all now ?

Sony xav ax5000

Pixel 2

Says USB device not supported
[Paid Software Announcement and Discussion] Kingcraft:
Thanks a lot for the update Emil!

I was driving around with it today for about 1:45h and have some feedback now.

First of all, a big thank you for fixing the bar unit for the boost gauge, it is working now!!! :)

No crashes during the drive today, very stable. Did some random switching, music playing and playing around, found nothing that looked wrong.

But what I noticed, Speedcam warning is not working anymore.

Notifications are ok, engine temperature was shown, but I think the database is not downloaded, because in the past, I got a notification that the database was updated/downloaded, when I opened OBD2AA for configuration purpose. This is not the case anymore. So I guess, I get no warnings, because I have no data for the Speedcams at all.

Phone is Samsung S7 with stock Android 8, no root.
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=9394207]alexdets7[/MENTION] - Can you please contact me by email? I will need a bug report but first I need you to send another version of the app.

I will check the SpeedCamera warning, I did some clean up on there as well, so might have manged to accidentally break something, sorry about that.
[Paid Software Announcement and Discussion] Jackos:
Hi Emil,

what about the GPS issue (GPS keeps looking for location) after Android Auto is disconnected?

Any status update for this issue?
[Paid Software Announcement and Discussion] Emil Borconi:
Yes that should be fixed in version 3.1, do you still experience the problem?
[Paid Software Announcement and Discussion] Kingcraft:
You are the last one to say sorry, this is absolutely no problem.

You can't make an omelette, without breaking eggs! ;)
[Paid Software Announcement and Discussion] Jackos:
I have not yet tried the new version. Ill do that tommorow and will keeo you in the loop. Thanks for the update and great support :)

---------- Post added at 08:01 PM ---------- Previous post was at 07:54 PM ----------

One further question, does the "overriding 6 tap limit" feature work even if I do not use "start head unit server" on an unrooted device?
[Paid Software Announcement and Discussion] bggold:
On an unrooted you have to start the head unit server in order for the app to work to launch aa. It will then override 6 tap limit.
[Paid Software Announcement and Discussion] Jackos:
Makes sense, thanks for the quick reply. :)
[Paid Software Announcement and Discussion] poopnoodles:
Just tried the new release, but still doesn't work for me. I think the issue is my headunit. The app seems to work fine and doesn't crash when I choose it from the prompt, so I'm pretty sure it's not the app.

When starting AA I have to select it on my headunit, but the option stays grayed out when selecting obd2aa on the prompt once I connect my device to the car.

May have to just give up on this, thanks anyways Emil :/

Pixel 2 XL

Hyundai Elantra GT
[Paid Software Announcement and Discussion] Emil Borconi:
Don't give up yet. Do you have an option on the car to auto-launch Android Auto when you connect the phone? Please email me I will send you a different version of the app and then request a bug report, to see what's happening there.

I do not have a Hyundai, to test, but I guess you experiencing this due to some timing issues between the headunit and the phone.
[Paid Software Announcement and Discussion] CeldeSuS:
I'm having the same issue with a Samsung Galaxy S6 Edge (non-root) and Alpine X802D-U head unit. As soon as I choose OBD2AA as default, Android Auto doesn't launch on the Head Unit anymore no matter what I would do.

I can provide any logs you need.
[Paid Software Announcement and Discussion] Emil Borconi:
Yes if you can email me some logs that will be great, please email me on borconie@gmail.com for a different version of the app in first-place.
[Paid Software Announcement and Discussion] poopnoodles:
No option to auto launch unfortunately. Have to manually press to launch AA normally. I'll send you an email. Thanks.
[Paid Software Announcement and Discussion] Jon Avalon:
Thanks for the update!

I think this update may have fix some of the initial issues I was having with just getting AA to launch on the headunit. I haven't tested it much but the three times I connected everything up today I was able to get it to launch. The only issue I'm still having though is the OBD2AA constantly disconnects from my adapter. I have to keep backing out of the app and reopen to see if it reconnects. The adapter works just fine with Torque.
[Paid Software Announcement and Discussion] Zephyrite_:
I have a OnePlus 5T running the latest software, everytime I come to connect to Android Auto and select OBD2AA, the app seems to either crash or tell me I do not have Torque Pro installed. I have tried every thing, and I paid for your app so I could use it. Is there a solution?
[Paid Software Announcement and Discussion] mic18u:
3.1 is working fine with a Pixel 2 XL on Android Pie with a Pioneer unit and in a vw golf..

But is the head unit server supposed to run all the time?
[Paid Software Announcement and Discussion] froader:
[MENTION=224120]Emil[/MENTION]

Thanks for the 3.1 update. This has fixed the OBD2AA crash on Pie, however the head unit server doesn't automatically start.

Stock rooted Pie Pixel 2

OBD2AA 3.1

Pioneed 4100NEX

AA worked just fine before

Play services defaults cleared

Plug in Pixel 2 select OBD2AA always

OBD2AA states head unit server not running

Open AA and start head unit server

AA successfully launches on Pioneer and OBD2AA opens showing gauges

Unplug and plug back in - Head unit server not running...

OBD2AA is verified as allowed under superuser in Magisk.

Any ideas? I'm certainly happy to see this progress. Thanks!
[Paid Software Announcement and Discussion] Goon818:
Thank you very much. Emil

I have no crash in the last three drive. I look so that is very stable.
[Paid Software Announcement and Discussion] Emil Borconi:
Can you please try to deny root to the app, make sure the headunit server is always running and try like that? The Pixel I have has a locked bootloader so I cannot root it, therefore I can't test to see if it's all working correctly with root.
[Paid Software Announcement and Discussion] Emil Borconi:
Well every time you connect to the car, if you have root the app should start it for you, but based on other user reports this might not work correctly 100% of the time, so my suggestion is just keep it running. If the notification bothers you, you can simply hide it.
[Paid Software Announcement and Discussion] Emil Borconi:
Hi.

Sorry to read that, I've just tested now on a OnePlus 5 and I couldn't reproduce the crash. If you do not have Torque Pro (and only interested in the other functions of the app) please do as follows:

1) Uninstall obd2aa

2) Plug in the phone to the car to make sure AA start up

3) Install obd2aa

4) Open obd2aa and grant all the required permissions, once that is complete ignore the message about Torque not being installed

5) Make sure that Headunit Server is running!

6) With your phone being unlocked, plug in the phone to the car

7) Select obd2aa and always instead of Android Auto.

If the crash problem persist, please see OP on how to get a bug report and send it over so I can see what's going wrong.
[Paid Software Announcement and Discussion] Zephyrite_:
I just did this, did not result in anything differently. The screen will flicker once and nothing happens, the Android auto buttons turn grey you you can't press them.
[Paid Software Announcement and Discussion] Emil Borconi:
Can you please provide a logcat? (see details in opening post on how-to).
[Paid Software Announcement and Discussion] Zephyrite_:
I held down the power button and all it does is being up my power off and restart options
[Paid Software Announcement and Discussion] Emil Borconi:
Right, forgot you are on oneplus and that has a custom power menu, sorry.

Instead of pressing the power button, go back to Settings -> Developer options and press take bug report, chose full.
[Paid Software Announcement and Discussion] froader:
I deleted OBD2AA from root and started the head unit server. I'm heading out in a couple of hours, so I'll update you. I know that yesterday as long as I manually started the head unit server I'd get AA working on my Pioneer.

If working properly with root is ORB2AA supposed to also stop the head unit server once unplugged from the stereo?

Also, does AA unknown sources still need to be checked?

By the way, if there is anything I can do to help get the root part work, please let me know.

Thanks:good:
[Paid Software Announcement and Discussion] Yamarocket630:
Emil, I previously purchased this app but don't have it installed right now.

I last had version 3.0 installed until the beginning of the month.

When I tried to download the update it is asking me to pay again.
[Paid Software Announcement and Discussion] pacmantravis:
I too am having this same issue. It is asking me to repurchase the app, and I bought it a week ago.
[Paid Software Announcement and Discussion] OSUJaws:
Same issue here
[Paid Software Announcement and Discussion] bitstra:
Same issue Here !

XDA labs Problem???
[Paid Software Announcement and Discussion] Emil Borconi:
Guys do not pay again for it. I will let XDA labs maintenance know about this ASAP.
[Paid Software Announcement and Discussion] bggold:
Yes with root it will also stop it.
[Paid Software Announcement and Discussion] froader:
Thanks. That's what I was hoping.

[MENTION=224120]Emil[/MENTION]

I removed OBD2AA from root access, started head unit server manually and the next connection I denied root. AA came up on my Pioneer along with the gauges, but no data flowed through.

Now the trip back home, I again removed OBD2AA from root and turned off the head unit server. I connected up and when asked for root, I allowed and AA immediately came up on my Pioneer with data flowing to the gauges.

I unplugged and then replugged a couple more time and still working.

Also HU Server ends once unplugged!

AA starts way faster than it did without obd2aa!!

So stoked. All I can suggest for root users is to remove OBD2AA from root to reinitialize.

Yahoo!! Thanks!!

---------- Post added at 08:30 PM ---------- Previous post was at 07:47 PM ----------

Unfortunately, that was short lived immediately after the above post. Regardless of allowing or denying root, starting HU server or not, there just does not seem to be any consistency and can't get this working. Even after deleting app defaults as well as obd2aa from root I'm not prompted for the app or root. It's really strange. I think there is 1 firmware update for Pioneer, but the notes stated Apple car play.

Android auto hacker running

Head unit server running

Android Auto connected to car

= Invalid USB device

https://photos.app.goo.gl/pgVMpwHLZf6z2L2o8

FYI, this is even well after I'm disconnected from my car

What can I do to get some info over to you Emil?

Thanks
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=351703]froader[/MENTION] - Email me directly please ( borconie@gmail.com )
[Paid Software Announcement and Discussion] barry666:
Is working well on note 9 in server mode. Didn't work on note 8. On ford focus st sync 3 [emoji12]
[Paid Software Announcement and Discussion] Ahpigsy:
Happy now it's more stable when switching AA pages. No lockups found. Samsung S8 and Ford Sync3.

Do have a slight problem with one of the gauges that I don't think was there before. I've set my boost gauge with a minimum value of 0.0. But it displays a negative value when the car isn't under load or at idle. I know this is the correct reading but I don't want it to display negative values, only positive boost values. Pretty sure it only showed 0 previously instead of negatives,.
[Paid Software Announcement and Discussion] Zephyrite_:
Next post
[Paid Software Announcement and Discussion] froader:
[MENTION=224120]Emil[/MENTION]

Before I tie up your email, I troubleshot further. I uninstalled AA, removed OBD2AA from root and removed defaults. Play services had no defaults. Installed AA and connected. Chose OBD2AA always and then allowed root.

3 times in a row AA successfully connected with live OBD2AA data.

Could the previous AA Unlocker have goofed up AA from working this time around although it's been removed for a while?

I'll keep an eye on this and hope it continues to work.
[Paid Software Announcement and Discussion] Zephyrite_:
So I'm not sure if this means anything, but I managed to get it working. I didn't give it any permission for location or storage, the phone is rooted, I do have Android Auto Mirror, and started AA on the head unit through Android auto and NOT OBD2AA. Pressing on that section brings up both OBD2AA and Android Auto Mirror.
[Paid Software Announcement and Discussion] Emil Borconi:
That means you have AA Unlocker installed on your phone, which unlocks both AA Mirror and OBD2AA as well.
[Paid Software Announcement and Discussion] Zephyrite_:
Interesting, meaning there's some sort of incompatibility, I'm using ROM Beta 14 which runs a 8.1.0 version of Android. Could that be of use?
[Paid Software Announcement and Discussion] bggold:
Did you use aaunlock before?

I just tested how you said and they do not show up. Not even obd2aa.

You must still have it installed or active.
[Paid Software Announcement and Discussion] Zephyrite_:
I didn't use it before as I was unrooted, I rooted the phone this morning and gave it another shot, I didn't realise unlocker would allow both to be compatible
[Paid Software Announcement and Discussion] horrorshow21:
New version is working well. Only issue I still have is having to reboot my phone every time. So for example, I drive home from work and everything is working well. The next morning I plug my phone in and get the dreaded "can't connect make sure your phone is unlocked" message. I reboot my phone, restart the hu server, and plug in. All works well again. I am currently not rooted. Pixel XL with Android P. I'll get a log when I have the issue next.
[Paid Software Announcement and Discussion] Goon818:
I have a similar problem. After every reboot from the phone I must select obd2aa again to standard. I selected always.
[Paid Software Announcement and Discussion] schaffer970:
[MENTION=224120]Emil[/MENTION]

I purchased the app some time ago. It is asking for payment again. I saw the discussion above and have been waiting for things to get fixed, but so far it still isn't working. I keep getting a "Network connectivity issue!" in the XDA LABs app. Are they having problems?

THANKS!
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=5398355]horrorshow21[/MENTION] [MENTION=3112762]Goon818[/MENTION] can you try to force-stop obd2aa and see if that helps?

[MENTION=4647016]schaffer970[/MENTION] - Yeah XDA Labs is having problems for the last 2 days, nobody can make purchases or download previously bought apps, they are working on it. Till then feel free to email me for a copy.
[Paid Software Announcement and Discussion] Ahpigsy:
I'm also finding I have to reboot the phone the next session. Except I'm getting a "Sync is unable to initialise Android Auto. Check device settings." message.
[Paid Software Announcement and Discussion] OSUJaws:
Hey Emil,

I emailed you a copy of the Bug Report, but unfortunately the version 3.1 doesn't appear to work still on the Kia Stinger Headunit. I did test it on my wife's Honda CRV and it worked perfect so I believe I can safely say it's not the Samsung Phone that is the issue, rather it's the Headunit. Thinking about it a bit more I've noticed that several other Kia/Hyundai owners have had issues getting the app to launch on their headunit, do you think this could be due to the UVO software that Kia puts on their Headunits? Also could I email you for this different version of the software to try out? Thanks

Phone: Samsung Galaxy S7 Edge: Oreo

Car: 2018 Kia Stinger
[Paid Software Announcement and Discussion] Emil Borconi:
However this approach screws up the mpg for example. Mpg is reported between 0 and 100 but it can return value of 512 as well when in gear and not accelerating. If I adjust the max to 512 than normal mpg values will be very low on the gauge.... So it's a bit of a minefield
[Paid Software Announcement and Discussion] ControlNode:
Agreed. Actually in Torque when I use the MPG gauges I alway set the max to about 50 to prevent just that.

I'm going to test some more. I've added the fuel pressure to my Torque screen with a manually set max to 2000 for that gauge. Then in OBD2AA I changed to some other PID and then back to Fuel Rail. Hoping that maybe by having a gauge in Torque the manual max value will be pulled from it. Before picture above I had not set a Fuel Rail gauge up in Torque, only after seeing max at 9 did I add it. Maybe with the refresh in OBD2AA it gets better values now. Will let you know once I get back to the car to test results.
[Paid Software Announcement and Discussion] ControlNode:
Nope, even after adding a fuel rail pressure gauge in torque and refreshing gauge in obd2aa showing 9psi.
[Paid Software Announcement and Discussion] Michealtbh:
Just to be clear, this is only for Android Auto headunits to have a Torque plugin? It won't work on a phone being used as a car's AA device to give an additional tab within AA which shows Torque data?

Thanks
[Paid Software Announcement and Discussion] spiff72:
You are correct, I think a previous post showed someone who tried showing the extra tab in the AA interface with their phone as the AA disolay, and it didn't work. A head unit is needed in the vehicle that supports Android Auto for this to work, PLUS torque pro app is needed.
[Paid Software Announcement and Discussion] adfurgerson:
Running Emil's other app on a phone will allow the use of this app.

https://xdaforums.com/general/paid-...adunit-reloaded-android-t3432348/post73680628
[Paid Software Announcement and Discussion] Michealtbh:
https://play.google.com/store/apps/details?id=com.bitspice.automate

I might just try this. It's not AA, but it has most of the same features with Torque already integrated