When I download older version it demand update in order to work. Even in plane mode it knows that update is avaliable. Which version exactly did you installed?
Same thing for me.
When I download older version it demand update in order to work. Even in plane mode it knows that update is avaliable. Which version exactly did you installed?
I have downloaded Version 7.0.614103. You have to shut off auto update for the app. I get notices to update when I run the software. But its been working perfectly fine with this version.When I download older version it demand update in order to work. Even in plane mode it knows that update is avaliable. Which version exactly did you installed?
Would be awesome to have it enabled through AAwiresless eventually - still happy to hear we'll be able to use OBD2 again regardless of how. Damn Google and their changes...I know you are all waiting and I know I'm not active here due to being busy with everything else, but some good news, I've managed to load a custom animation using the official Google Library now I need to port it all to obd2aa.
I think mid / end of January you should be able to see the gauges again.
It's already available on AA Wireless if you have OBD2AA on your phone. Just make sure to enable developer options in AA Wireless once Emil takes care of the fix.Would be awesome to have it enabled through AAwiresless eventually - still happy to hear we'll be able to use OBD2 again regardless of how. Damn Google and their changes...
Yeah I'm meaning if it was supported through the AAwiresless app to allow native launching/automatically rather than needing to use unconventional patches/hacks etc. I did run it wirelessly previously before Google blocked aftermarket apps. The reason I say this is because alot of the time patching apps into Android auto caused AAwiresless to refuse a connection and other issues for a fair few users that I know - wired connection was fine.It's already available on AA Wireless if you have OBD2AA on your phone. Just make sure to enable developer options in AA Wireless once Emil takes care of the fix.
Before AA was updated, it natively worked with the AAWireless. I've been running OBD2AA ever since I got AAWireless early last year without any hacks.Yeah I'm meaning if it was supported through the AAwiresless app to allow native launching/automatically rather than needing to use unconventional patches/hacks etc. I did run it wirelessly previously before Google blocked aftermarket apps. The reason I say this is because alot of the time patching apps into Android auto caused AAwiresless to refuse a connection and other issues for a fair few users that I know - wired connection was fine.
Unless OBD2AA was patched using a varient of Phenotype Patcher, it wouldn't appear in Android auto as with any other unofficial Android auto app as far as I'm aware hence my previous comments.Before AA was updated, it natively worked with the AAWireless. I've been running OBD2AA ever since I got AAWireless early last year without any hacks.
F5 F5 F5We already have some news about the resolution ?
I already miss the screen app in my car.
Yeah, we're stuck waiting until the developer finds time to work on this paid app again but he's tied up with the aaw development. Emil mentioned we should have had it up and running by end of January so hopefully something's not far off in the worksI was fine having to clear the data/cache, having to reinstall, etc. AAA Was working great up until this morning. No matter how I try and work around it, obd2aa will not show up, period. Even when installing various older versions of Android Auto. It just tries to take me to Playstore to have me install Weblink host when I plug into my headunit. Bummer.
I've been checking back every day since we had a mention of late January I guess it's been difficult modding apps to run on the latest AA
<FrameLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:tag="wrapper_layout">
<!-- Left column -->
<View
android:layout_width="226dp"
android:layout_height="226dp"
android:layout_gravity="center_vertical|start"
android:tag="gauge_2"
/>
<!-- Middle column -->
<View
android:layout_width="match_parent"
android:layout_height="match_parent"
android:layout_gravity="center"
android:tag="gauge_1" />
<!-- right column -->
<View
android:layout_width="226dp"
android:layout_height="226dp"
android:layout_gravity="center_vertical|end"
android:tag="gauge_3" />
</FrameLayout>