What I did with mine was download mqb-pm and "open" the APK as an archive and take some of the dials/backgrounds and use that when setting up. Its the last setting in the individual gauge settings. Just make sure to set gauge style as clear.
Yeah, I encountered the same problem with one plus 8 pro with Verizon sim. I tried everything, changing permissions, notification settings, cleared storage and cache for obd2aa, phone, call management, services, everything. No luck tho. Ended up just getting rid of it as "the main app" and only run it for gauges only inside android auto.Has anyone faced this weird issue? I have obd2aa installed, dpi set to 110 and fermata auto as player. Every time after i disconnect my phone from car, after using aa with this setup, I'm unable to make phonecall from my phone (not over bluetooth). Since i really need aa to work and phone as well I'm forced to ditch ond2aa until a fix will be found. Thank you for your help
Hi there,Yeah, I encountered the same problem with one plus 8 pro with Verizon sim. I tried everything, changing permissions, notification settings, cleared storage and cache for obd2aa, phone, call management, services, everything. No luck tho. Ended up just getting rid of it as "the main app" and only run it for gauges only inside android auto.
*bump*"Could not connect to Torque Pro.
Is the app installed on your device?
You need to have Torque Pro installed in order to use this app."
Any ideas?
- Huawei P30 Pro (Android 10)
- Torque Pro v1.10.120 (Sep 2020)
- OBD2AA v3.6b (Jan 2020)
For the dial issue, start up Torque manually before plugging into your head unit, and it will likely work. I've had this issue with a vehicle specific dial since I set it up. Occasionally it works fine but normally I have to start Torque first.HI,
I just purchased Torque Pro and the OBD2AA app. Inside Torque I can see all dials working perfectly, including GPS speed. On Android Auto with OBD2AA, most dials seem to work fine, EXCEPT the GPS Speed dial. This stays on 0. The GPS accuracy and other dials all work fine, so there doesn't seem to be any problem with the GPS NMEA data received from the OBD2.
The OBD2AA settings are set to NOT use the GPS from the phone, but even with that setting enabled the GPS speed dial still doesn't work in OBD2AA.
Another issue is that the "day/night mode override" doesn't seem to work. My head unit still uses the headlight setting (Suzuki Jimny 2021).
Any way I can provide more debugging info to help sort this issue?
I just tried this, and indeed, the GPS related dials work, but ONLY when the Torque App is open AND active on the phone. The moment I turn the phone screen off, the dials stop working. This kind of defeats the purpose of having a head unit. My phone is connected via USB and in a dash-bag, so I really can't have my phone screen on...For the dial issue, start up Torque manually before plugging into your head unit, and it will likely work. I've had this issue with a vehicle specific dial since I set it up. Occasionally it works fine but normally I have to start Torque first.
I think to change your headunits DPi it usually requires an app to "request" full screen which is often achieved by apps using root. I know that using an AAWireless device (made and sold by this dev) enables you to force split screen meaning you can run two apps on screen. As for using OBD2/torque if it's just reading data so should work fine - sounds abit odd that you couldn't use OBD2 to clear codes etc that would get annoying.Hi maybe you can help me with the following questions. I have an Alfa Stelvio and my motivation around obd2aa is mostly to get the Android Auto split screen via change of DPI settings. I would also like to remove the tab limit. My questions are:
1) do I need the OBD adapter/reader to change the DPI setting and remove tab limit or is torque pro + odb2aa app enough ?
2) if yes - my Alfa seems to have a security gateway on ODB port which means you probably cannot write to the port (or at least things like error messages cannot be canceled) - do you need to write to the ODB port to change the above settings?
sorry if those are obvious questions but I am not an expert in the field.
thanks, Luke
Hi thanks for the response. I am aware of the AAwireless and have actually preordered the device but the shipment date seems to be quite distant ; I thought that obd2aa would have the ability to change the DPI setting and based on some other discussion I read that seems to be done on the headunit so I thought it is via the OBD2 connector facilitated via obd2aa app so that it is done properly - am I wrong?I think to change your headunits DPi it usually requires an app to "request" full screen which is often achieved by apps using root. I know that using an AAWireless device (made and sold by this dev) enables you to force split screen meaning you can run two apps on screen. As for using OBD2/torque if it's just reading data so should work fine - sounds abit odd that you couldn't use OBD2 to clear codes etc that would get annoying.
Changing the DPI doesn't need an OBD adapter, just needs to be requested by the device running AA. You should be able to change it without using torque or an OBD adapter.Hi thanks for the response. I am aware of the AAwireless and have actually preordered the device but the shipment date seems to be quite distant ; I thought that obd2aa would have the ability to change the DPI setting and based on some other discussion I read that seems to be done on the headunit so I thought it is via the OBD2 connector facilitated via obd2aa app so that it is done properly - am I wrong?
<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>