yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] badabing2003:
Thanks Emil for all the digging, this really sucks.

What's the class / method name that checks if it is running on an emulator or not? And the response when running on an emulator?

With XPrivacyLua it's very easy to add a definition that would respond as emulator when the method is called.

Without even needing a reboot.

I can give it a try if you provide the details.

Thanks.
[Paid Software Announcement and Discussion] Emil Borconi:
Not that simple :)

There is a class chd.class which removes the items from the apps list:

paramawh = E((List)localObject1);
if (!"Developer".equals(xM())) {
paramawh.remove(bqe.aVx);
}

Which looks like this:

private static String xM()
{
try
{
Object localObject = bdv.aGs.aGU.lz();
localObject = bdv.aGs.aHm.a((GoogleApiClient)localObject, "car_app_mode", "Release");
return (String)localObject;
}
catch (CarNotConnectedException localCarNotConnectedException)
{
bam.c("GH.AvailableAppFinder", localCarNotConnectedException, "Error getting 1p manager.");
}
return null;
}

I think this method checks for Developer privileges and in case they aren't simply remove the app from the list. I guess Google employees and others who have developer privileges are able to use everything is cars, so one way would probably be to override the xM() function.

The other is bzj.class:

public final class bzj
implements bdq
{
private final bzk dT(int paramInt)
throws CarNotConnectedException
{
if (paramInt != ApplicationType.bWj)
{
paramInt = 0;
if (paramInt != 0) {
break label31;
}
}
label31:
while (!bdv.aGs.aHm.a(ww(), "allow_unknown_sources", false))
{
return null;
if (axi.mZ())
{
paramInt = 0;
break;
}
paramInt = 1;
break;
}
bam.f("GH.ServiceAuthorizer", "Ignoring unknown sources for full-screen app");
bdv.aGs.aHm.b(ww(), "allow_unknown_sources", false);
return bzk.bdb;
}

static Car.CarFirstPartyApi oa()
{
return bdv.aGs.aHm;
}

static GoogleApiClient ww()
{
return bdv.aGs.aGU.lz();
}

As you can imagine I haven't manage to get the bottom of this yet...
[Paid Software Announcement and Discussion] badabing2003:
Thanks Emil,

I think if we hook before on xM(), then it will bypass xM() code, we just return a valid string. Then we'll be a developer

Reference: https://github.com/M66B/XPrivacyLua/blob/master/DEFINE.md

Would that be enough, or we still have to fake to be in emulation mode?

My system hasn't yet updated to AA 3.0, and check for updates shows nothing, anyone knows where I can download?

Thanks
[Paid Software Announcement and Discussion] Emil Borconi:
I cannot test because I do not have xPosed and I cannot root because I'm using Android Pay on my phone...

You can grab AA 3.0 from: https://www.apkmirror.com/apk/google-inc/android-auto/android-auto-3-0-5705-release/

not sure if hooking before xM() will actually work... not sure how much you can do with the XPrivacyLua (I never used it) bit I think you should hook just before this:

Object localObject = bdv.aGs.aGU.lz();

and inject something like:

return "Developer";

I think that will do...
[Paid Software Announcement and Discussion] badabing2003:
Awesome thanks, will try it out.

Which class this method is in?

bdv.aGs.aGU.lz()

Thanks

BB
[Paid Software Announcement and Discussion] Emil Borconi:
axb.class

but you can also try to inject one line in the chd.class before this line paramawh.remove(bqe.aVx); just simply add a break; before that should also work.
[Paid Software Announcement and Discussion] bggold:
I can test Xposed module if you want. I have a test pixel 2 rooted with Xposed and can upgrade to AA 3.0

Would be nice as a universal patch. I have another app that does not work for the same reason.
[Paid Software Announcement and Discussion] Emil Borconi:
Ok, i have tested now and the "good" news is that actually we can still use older versions of Android Auto, I just installed 2.3 which is about 6 month old if not more and it still loads on stock Oreo, so this gives me some hope that we will be able to use 2.9 for a while, key is NOT to update to 3.0 and if you did update, roll back and disable automatic update.

Also I can confirm for sure that there is a way to get the app running even with Android Auto 3.0 but not from XDA Labs, which means in the next few weeks I will have to build a contingency plan to be able to shift away from XDA Labs ( really sad, about this it was so convenient... ).
[Paid Software Announcement and Discussion] ShannonPricePhoto:
I dl the 3.0 because I want to see if wifi projecton works on my car. I haven't side loaded it yet. If I do can I go back to 2.9? Easily? I'm torn... If wifi works I'd give up gauges on dash I think... If not I want to go back to 2.9
[Paid Software Announcement and Discussion] bggold:
Yes you can go back I did without any issues. BTW what head unit do you have?
[Paid Software Announcement and Discussion] Emil Borconi:
Going back it's easy and Wifi won't work I'm 99% confident. For Wifi to work it will need firmware update on the car as well, currently there is no unit out there which can make AA run over Wifi, they were demo-d at CES 2018 but the units are not yet available for purchase, and no car can handle it either for time being.
[Paid Software Announcement and Discussion] ShannonPricePhoto:
Ohh. Ok I didn't read up on it..so def won't work then. I'm gonna have to rig up a "dock" then
[Paid Software Announcement and Discussion] badabing2003:
I'm not writing an Xposed Module but rather XPrivacyLua Definition Script, which is much easier to write, and does not require constant reboots each time you change something while developing and testing.

Marcel the author of XPrivacyLua has done an amazing job, which makes writing definitions (which can replace Xposed module functionality) easy for the rest of us. (to top it off XPrivacyLua is one hell of an app to protect your privacy, an indispensable tool)

[MENTION=842765]Emil Borconi[/MENTION]

I'm getting class not found exceptions on

com.google.android.projection.gearhead.chd

com.google.android.projection.gearhead.chd.class

com.google.android.projection.gearhead.bzj

com.google.android.projection.gearhead.bzj.class

I'm receiving guests today, I'll continue working on this tomorrow, is it possible that chd and bzj are made up names by the apk decompiler and hence not matching the true classes?

Thanks
[Paid Software Announcement and Discussion] bggold:
Never have used it but if you have some ideas I am willing to test.
[Paid Software Announcement and Discussion] Alphaelectric:
This news comes at the worst possible time, really. Two days ago, my OBD2 LX arrived in the mail and today, I have finally found a gauge setup that makes driving the Magnum feel so much more like a late model car.

Thank you for this app and the efforts you have put into it! I purchased Torque Pro only to have this app pull relevant info up on my Sony XAV-AX100 head unit while driving.

I did wonder why this app is not available as a paid app on Google Play. It is in no way more mesmerizing than the late model dash boards from my colleagues 2017 Audi A4. Audi manages to overburden their digital dashes with so much useless info that it poses a much greater risk to the driver than the clean interface you provide.

Again, thanks for the great app. I hope things can get resolved for non-rooted regular users.

All the best
[Paid Software Announcement and Discussion] scoobdude:
Awww man. I hope Google plays nice. This is the one thing Android auto needed to make it awesome (maybe just my opinion). Thanks for continuing to try and keep us posted. If not maybe your other app can be used with the 3.0 features in the future. Fingers crossed buddy!!!¡
[Paid Software Announcement and Discussion] Emil Borconi:
It can be resolved, but for time being I don't want to make the solution public, I really don't want that youtube player and other similar apps working again, which might force Google hand to take even more radical solutions than current one. Bare with me a bit on this one.
[Paid Software Announcement and Discussion] Emil Borconi:
My other app is working fine, which again imho is a proof that Google only took this step because of people abusing the unofficial SDK. I even showed them both apps last year at the TC summit and they were impressed and liked both of them.
[Paid Software Announcement and Discussion] Emil Borconi:
I'm not entirely sure on the process dex2jar uses but the classes names shouldn't change afaik. The problem is that this classes are outside on the com.google.android.projection.gearhead package, they are classes without a package (in the root of the jar) not sure if/how you can reference them.
[Paid Software Announcement and Discussion] Emil Borconi:
Can I have a few testers please, currently only ROOT ones, for root users I came up with an easy way of how to make things work, but I need a few testers who can confirm that it's working.

To be a tester you need to:

1) Have a rooted phone

2) be willing to install/uninstall Android Auto 3.0 and test if its working

If you are interested shoot me an email to borconie@gmail.com.

As a positive note I did came up with an idea for easily solving the problem for non-root users as well. I'm holding off with details until I hear back from Google. I did sent them a relatively long and well argumented email asking for permission to push the app to Play Store, if they do approve it (I see chances of 1% max) then all discussion on this topic will become pointless. In case they don't approve it I will like to cloak the solution as much as possible to prevent others to try to implement it on Youtube and other dangerous apps. The last thing we need is to get Google so pissed of to take even more radical steps then this one (for example whitelisting apps from Server Side, that will be the end of it)
[Paid Software Announcement and Discussion] badabing2003:
I'm able to intercept the xM() method and return immediately without executing the xM() method code, but that is not solving the issue.

I can intercept the lz() method but am not able to return the correct expected type com.google.Android.gms.common.api.GoogleApiClient

BB
[Paid Software Announcement and Discussion] bggold:
Thanks for the effort. I am testing for Emil and it seems he has a possible working solution. I'm sure he will let us all know if it is a viable solution or not soon.
[Paid Software Announcement and Discussion] Emil Borconi:
Thank you for that. Well reversing code it's not always simple, finding the right method can be very tricky sometime. However as it has been said already, for ROOT users there is an easy way which will be built into the next app.

NON ROOT users also have a decent solution, but I'm waiting for Google's answer to the request of making the app official before going further, so hang on to your AA 2.9 version till then.
[Paid Software Announcement and Discussion] badabing2003:
Thanks Emil for an amazing job.

BB
[Paid Software Announcement and Discussion] njozsef1:
Hi Emil.

The relase of AA 3.0.570554

Checked unknown source,

Visible only the anyautoaudio. Obd2aa and widgetsaa not visible. I reinstall2. 9xx.

Othet question:

How to report wrong speed cam. Wrong direction. thx.
[Paid Software Announcement and Discussion] Emil Borconi:
As discussed, AA 3.0 is a killer for time being, I do have a fix in place but I'm waiting for Google's answer to see if they (maybe maybe ) allow the app on PlayStore, because that will change loads of things, if not or if I don't hear from them by the end of the week I'm going to release the patches.

As of speed camera, the information is taken from scbd database (the biggest in EU/World) so probably you should let them know about wrong camera.

Sorry for not replying in Hungarian, but since this thread is frequented by many (most none Hungarian speakers) it will be odd for me to reply in other language then English. If you do need help or you struggle with English you are welcome to shoot me a private message/email in Hungarian/Romanian anytime.
[Paid Software Announcement and Discussion] pkim003:
Hey guys,

I contacted Emil about testing the OBD2AA. I have a rooted Samsung note 5 with the xPosed module. I upgraded my AA to 3.0 and can confirm that it works. But now my other apks aren't showing up. I'm still testing it and waiting to see if there are any bugs or glitches. I'll keep Emil posted if there are any issues. But otherwise, if you're using his app on a rooted device, his app is a go. I can't say if it does work on non-rooted phones though. I'm not quite sure if the other developers will be able to get their apps back on 3.0, but all I can say is that I hope so... Except for the moron who developed carstream ruining it for other developers and endangering peoples lives. I mean sure it's nice to be able to stream video in a 1-2 ton motorized vehicle at 60+ mphs keeping yourself entertained. But the slightest moment of taking your eyes off the road potentially can change yours or the lives of others. I am not trying to start anything, I'm just stating my honest opinion because not having that option is worth living. Just my honest opinion.

But if you have a rooted phone and AA 3.0, get this app for your vehicle. It's awesome! And by the way for those thinking that I'm looking at the app while driving, I'm not. Ill take an occasional glance when I'm at a red light to see how pretty it is or I'm showing it off to friends and family, but I log my info and see how my vehicle is running.
[Paid Software Announcement and Discussion] :
I have also test new testing version of obd2aa to a rooted phone in android auto v3.0xx and working fine.

Although i have now reinstall previous version of android auto because i need mirroring to have Navigon navigation app working..

I don't agree about moron.

If someone is so moron that want to watch utube while driving, he will do it with his phone. There are phones now with bigger screens..

I don't believe that this was the main reason for Google of doing this.

But I do believe tha wasn't Google intension to block apps like obd2 android auto..

If Google want to resolve the issue with a good manner, will accept obd2aa and similar apps in playstore, although i won't believe this will happen soon..

Its all about the money..
[Paid Software Announcement and Discussion] Emil Borconi:
Hey guys looking for some non-rooted users for test, requirement:

- Already have the obd2aa app installed

- Can (or already have) update to Android Auto 3.0

- Have a Windows PC

- Does know how to enable usb debugging and has drivers installed for the phone

Once method confirmed and final changes are made I will create a easy to follow how-to for non-rooted users as well (but it will include the use of a Windows PC, Mac and Linux will need to wait a bit more...)

If you do qualify send me an email to borconie@gmail.com com
[Paid Software Announcement and Discussion] artem_alf:
Hi all, just wondering where I can get previous version of AA link that was posted is not working. Thank you.
[Paid Software Announcement and Discussion] Emil Borconi:
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=Android+Auto
[Paid Software Announcement and Discussion] Emil Borconi:
Updated OP with how-to get OBD2AA working with Android Auto 3.0 for non-rooted devices, app updated on XDA Labs will follow shortly (for the convenience of those who have rooted phones). Please give my your feedback on how easy is to understand and follow the instruction set for patching OBD2AA.
[Paid Software Announcement and Discussion] FormelLMS:
Happy to help here. You know my email address. Knowledge to make the tests is here.
[Paid Software Announcement and Discussion] Emil Borconi:
In that case you can have a look at the OP with the new instructions and tell me if you managed... :)
[Paid Software Announcement and Discussion] Emil Borconi:
Rooted users should try to updated to 2.0.1 beta, open app (outside AA) and apply patch.
[Paid Software Announcement and Discussion] FormelLMS:
Well, Reading seems not to be my best skill.

Thought, I've to download a new OBD2AA version.

Upps,

will give it a try after my meal and can check in car tomorrow.

Sorry for misreading o0

---------- Post added at 08:09 PM ---------- Previous post was at 07:33 PM ----------

Tried it with the new beta.

At first, app won't start anymore without patching. You can ignore or ok for root users. If you press ok on a non rooted phone you'll get the error code that you can't apply the patch caused by a non rooted phone. If you press ignore you'll get a white page and can do nothing within OBD2AA.

Then tried your patcher zip file on Windows and it works flawlessly on the first shot. The app runs now.

I have to leave in a few minutes for some online racing so I only can try the app tomorrow morning in car. I will give you more information then.

For now it seems that your skills are very great.
[Paid Software Announcement and Discussion] Emil Borconi:
Ups... yeap you are right forgot to attach an action callback for the ignore button.

Just to clarify, the intention is not to let the user configure the app without patching it first, otherwise I'm pretty sure some will not read the instructions (op is long indeed) and then they will start wondering why they cannot use the app... AA 3.0 is being rolled out at nice pace so eventually almost everybody will be faced with this problem even if they still use 2.9 for time being.

Updated the beta so now ignore button also give you error message with instructions on how to patch.
[Paid Software Announcement and Discussion] badabing2003:
Smooth as silk, working beautifully on a rooted device.

If one minor improvement can be suggested is that after clicking apply the patch, the app goes white screen and then it eventually closes with no indication if anything went as planned or not.

A simple feedback dialog would be great to inform the user that the App needs to be restarted.

Thanks for a great product that you continue to support.

BB
[Paid Software Announcement and Discussion] wbagdon:
Patch for non-root worked great.

Only small problem was, if the ADB daemon was not already running, the exe had to be run again.
[Paid Software Announcement and Discussion] nygmam:
Used the Windows patch file on non-rooted LG VEEP and seems to have worked fine. Thanks for fixing this so fast.
[Paid Software Announcement and Discussion] DaVinylSmith:
AA 3.0 Patch

Patch worked for me with non-rooted phone. Fresh install of beta and patch applied and it started right up. Only problem is that I have to reapply the patch if I reboot my phone.

...at least I think that's what my problem is. Will re-patch and update post tomorrow.

[Post updated with #1310]

My phone is an LG K10 with Nougat
[Paid Software Announcement and Discussion] Emil Borconi:
Reboot shouldn't do anything to the patch, only re-install of the app or update.
[Paid Software Announcement and Discussion] Emil Borconi:
Fair point going to modify it accordingly, thanks for spotting this.
[Paid Software Announcement and Discussion] FormelLMS:
So my experience on a non rooted phone

Patch has to be opened twice to apply because daemon is not running

Patching is successful

Patching is working after a reboot

OBD2AA is working as usual after that

Emil, do you know what happen, if you don't have a PC in the near, do the update but can't patch. Is the traffic cam and the sunset/sunrise thing working
[Paid Software Announcement and Discussion] Emil Borconi:
Going to fix to daemon in next patch release.

If you update and not able to patch camera warnings, street cards, night toggle will still work!
[Paid Software Announcement and Discussion] FormelLMS:
Yay! (If you haven't installed it new, because you can't get up to settings screens without patching)

Are there any news from google about your question?
[Paid Software Announcement and Discussion] esteptoporoto:
Where can I get the link to the non root patch ????

Enviado desde mi HUAWEI VNS-L23 mediante Tapatalk
[Paid Software Announcement and Discussion] Emil Borconi:
In case of update all settings are preserved so it won't affect you in any way. If it's a new install you cannot use the app properly without the patch.

No I haven't received any answer from them yet.
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry missed the question, the patch is available in the first post (op).
[Paid Software Announcement and Discussion] esteptoporoto:
Thanks. Any ideas why the Estimated fuel Remaining Indicator doesnt work.????

Enviado desde mi HUAWEI VNS-L23 mediante Tapatalk
[Paid Software Announcement and Discussion] Emil Borconi:
Depends... Probably car doesn't support it, in that case it will calculate it from vehicle profile, but you need to updated the profile every time you fill up.
[Paid Software Announcement and Discussion] esteptoporoto:
Thank you for your answer. !!

Enviado desde mi HUAWEI VNS-L23 mediante Tapatalk
[Paid Software Announcement and Discussion] mikera67:
Patch worked as advertised, thanks for your hard work!!!

Non rooted pixel 2 running Android auto version 3
[Paid Software Announcement and Discussion] jb.traveller:
Emil, Patch working on my unrooted Samsung s7 using AA 3.0.570554 on OBD2AA 2.0 thank you.

Easy to use patcher. :)

Will it work on the Beta as well?
[Paid Software Announcement and Discussion] Emil Borconi:
Yes it will but currently the only change in the beta is that it's detecting if the app is patched or not, and if the user has a rooted phone it will automatically patch it, so there isn't any need to updated to beta if you're on an unrooted phone. Goes without any saying that it will work with any future release of obd2aa as well, so unless Google changes something or I find another way to hack the system (which I'm investigating but not sure I call pull it of..) this will be the way forward...
[Paid Software Announcement and Discussion] jb.traveller:
I forgot to ask should I disable auto updates on AA?
[Paid Software Announcement and Discussion] Emil Borconi:
No need the patcher should work for any upcoming AA version unless they yet again change something...
[Paid Software Announcement and Discussion] jb.traveller:
Now it's working I will turn off Auto updates, your plugin is what AA is all about and I do hope Google let you go on the store.
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry double post...
[Paid Software Announcement and Discussion] DaVinylSmith:
OBD2AA Working Again

UPDATE: Tried finding what wasn't working on my end and eventually everything stopped working. I eventually uninstalled Android Auto & OBD2AA and did a fresh install (Android Auto from play store & OBD2AA Stable). Everything works now with non-root patch, even after a reboot of my phone.

This leads me to believe the choice of my gauges was causing the app to crash repeatedly. I will let you know when I start loading gauges if any cause it to stop working.

UPDATED UPDATE: Found the issue. Showing battery voltage, OBD2AA doesn't like Warning level 2 at 97.5%. Switching to 97 causes it to stop crashing.
[Paid Software Announcement and Discussion] spiff72:
Wow - this thread has exploded since the last time i was here!

I have not updated the OBD2AA app in quite some time and stumbled back here after the recent AA update broke the OBD2AA app.

Quick questions:

- I was going to update the app, but I am curious if there is a way to tell what version of OBD2AA i currently have installed?

- Since this AA 3.0 update, I have gotten verbal warnings stating "Caution, icy conditions" (or something close to this). Is this coming from the AA app, or from OBD2AA? I never heard this warning before, so not sure where it is coming from. I don't see an option for it in OBD2AA preferences.

- The notification cards (current street and engine coolant notification) still seem to work, so they aren't broken. The coolant update is how I noticed the next observation...

- (Not really a question, but an observation) My bluetooth OBD adapter seems to connect FAR more reliably now. Up until recently it would only connect if I unplugged it from the OBD port and then plugged it in, and accepted the pairing notification on the phone. My last 6 drives it has connected every time. This doesn't seem like an AA update fix - maybe the torque app was updated?

Thanks!