As a car enthusiast and expert in automotive diagnostics, I understand the desire to monitor your vehicle’s performance in real-time. That’s why I’m excited to delve into OBD2AA, an application that ingeniously brings OBD2 data directly to your Android Auto head unit. While the original developer has announced the end-of-life for this project and made it open source, the value and functionality of OBD2AA remain significant for those seeking deeper insights into their car’s operation.
This article serves as a comprehensive guide to OBD2AA, drawing from the original developer’s notes to provide you with a clear understanding of its capabilities, requirements, and setup process. We’ll explore how you can leverage this open-source tool to display crucial engine data right on your car’s screen, enhancing your driving experience and vehicle awareness.
Understanding OBD2AA: What It Does and Why It Matters
OBD2AA is an Android application designed to bridge the gap between your car’s On-Board Diagnostics (OBD2) system and your Android Auto head unit. In simpler terms, it allows you to view real-time data from your car’s engine and sensors directly on the screen in your dashboard, via Android Auto.
For car enthusiasts, mechanics, and anyone interested in vehicle health, this is invaluable. Instead of relying solely on dashboard warning lights, OBD2AA empowers you to monitor parameters like engine temperature, RPM, speed, and much more. This data can be crucial for:
- Performance Monitoring: Keep an eye on engine performance metrics during driving.
- Early Issue Detection: Identify potential problems before they escalate into costly repairs.
- Customizable Gauges: Create a personalized dashboard displaying the data most relevant to you.
- Speed Camera Alerts: (Feature mentioned, functionality may vary with open-source version and database updates) Receive notifications about speed cameras and street speed limits.
While the original developer, Emil Borconi, has moved on from active development, the open-source nature of OBD2AA means the community can potentially keep it alive and even enhance its features.
Essential Requirements to Run OBD2AA
To get OBD2AA working in your car, you’ll need a few key components:
- Torque Pro App: OBD2AA relies on Torque Pro, a popular and powerful Android OBD2 application. You’ll need to purchase and install Torque Pro from the Google Play Store. It acts as the data source for OBD2AA.
- OBD2 Reader: This is a Bluetooth or Wi-Fi adapter that plugs into your car’s OBD2 port (usually located under the dashboard). The OBD2 reader retrieves data from your car’s computer and transmits it to your Android phone.
- Android Auto Compatible Head Unit: Your car’s head unit must be compatible with Android Auto. Alternatively, you can use the Headunit Reloaded App (HUR) on a non-Android Auto head unit to simulate Android Auto functionality.
- Android Phone: An Android phone capable of running Android Auto and the required apps.
Image: OBD2 Reader connected to car’s OBD2 port
It’s important to note that using Android Auto directly on your phone screen will severely limit OBD2AA’s functionality. Gauges and Torque data display will not work in this configuration; you’ll only see speed camera and street card notifications. To fully utilize OBD2AA, you need a proper Android Auto head unit or HUR.
Setting Up OBD2AA: Installation and Configuration
The setup process for OBD2AA involves a few steps, and the method you choose might depend on your device and car compatibility. Here are the two primary options outlined by the developer:
Option 1: General Compatibility (Limited Features)
This method is designed to work with most phone and car/head unit combinations. However, certain advanced features like AutoPlay Music, 6 Tap limit remover, and DPI change might not be available.
- Install OBD2AA: Download and install the OBD2AA application. (Since the original distribution via XDA Labs might be outdated, you’ll likely need to compile it from the open-source code on GitHub: https://github.com/borconi/obd2aa).
- Beta Testing (Potentially Outdated Step): The original instructions mention signing up for beta testing on Google Play. This step might be irrelevant now that the app is open source and end-of-life.
- Disable Auto-Update & Reinstall: Disable auto-updates for OBD2AA in the Play Store, uninstall, and reinstall from your chosen source (likely a compiled APK from the GitHub source).
- Connect to Android Auto: With your phone screen unlocked, connect it to your car. When prompted to choose an app, select “Android Auto.”
Option 2: Full Functionality (Device Dependent)
This method aims to unlock all OBD2AA features but might not work on all devices, particularly Xiaomi phones according to the original developer.
- Install OBD2AA: Install the OBD2AA application (again, likely compiled from the open-source GitHub repository).
- Remove Conflicting Apps: Ensure no other third-party Android Auto apps are installed to avoid conflicts.
- Initial OBD2AA Setup: Open the OBD2AA app on your phone and configure basic settings like colors and gauge numbers. The app interface should guide you through this.
- Enable Headunit Server in Android Auto Developer Settings:
- Open Android Auto on your phone.
- Go to “About” in the settings menu.
- Tap the “About Android Auto” header 10 times to unlock developer options.
- In the developer options menu (accessible from the three-dot menu in the top right), select “Start Headunit Server.” (Rooted users can skip this step as the server can start automatically).
- Close Android Auto.
- Connect to Car and Select OBD2AA: Ensure your phone screen is unlocked. Connect to your car. When prompted to choose an app, select “OBD2AA” and choose “always.” If using Headunit Reloaded (HUR), select “Android Auto” and “always.” If you don’t see the prompt, clear defaults for Google Play Services in your phone’s settings (Settings -> Apps -> All apps -> Google Play Services -> Clear Defaults) and try again.
- Select OBD2AA in Android Auto: In Android Auto on your head unit, navigate to the app selection screen (usually the last tab on the right). Select OBD2AA from the app list.
- Data Acquisition: Allow some time for OBD2AA to establish a connection with Torque Pro and begin pulling data.
Image: OBD2AA Gauges Displayed on Android Auto
Key Features and Customization Options
OBD2AA, even in its end-of-life, open-source state, offers a wealth of features and customization possibilities:
-
Customizable Gauges: Display a variable number of gauges (1-15) showing real-time data from your car’s sensors.
-
Gauge Customization: For each gauge, you can customize:
- Colors (3 colors per gauge)
- Text color
- Needle visibility
- Arch visibility
- Units display
- Scale
- Decimal places
- Text display
- Warning limits (percentage-based, relative to PID max value from Torque Pro)
- Reverse mode (useful for gauges like fuel level)
- Custom background and needle images
-
Units Conversion: Units are automatically converted based on your Torque Pro preferences.
-
TPMS Screen: If you have PIDs (Parameter IDs) for Tire Pressure Monitoring System (TPMS) data, you can display tire pressure values on a dedicated TPMS screen within Android Auto.
-
Low Fuel and Warm Engine Warnings: Set up heads-up notifications for low fuel level and when the engine is warmed up.
-
Speed Camera Warnings: (Functionality dependent on database and updates) Receive warnings about speed cameras and street speed limits.
-
Street Information Card: Displays the current street name and speed limit (if available).
-
Layout Options: Different layout options for gauge display.
-
Styled Gauges: Option for styled gauge designs.
-
Custom Backgrounds: Use custom background images for gauges.
-
Needle Color Adjustment: Change the color of gauge needles.
-
Adjustable Gauge Arcs: Customize the indent, position, and length of gauge arcs when using custom backgrounds.
-
Multi-Language Support: Includes translations for French, Danish, Finnish, Spanish, and Italian (contributed by the community).
Important Considerations and Troubleshooting
- Performance and Phone Speed: Choppy audio or performance issues might occur, especially on slower phones. This can be due to phone processing speed, head unit buffer, and other factors.
- Bluetooth Audio Output: Bluetooth audio output might not work on all devices and head units. Some systems might disable car Bluetooth capabilities when Android Auto is running, leading to sound output from the phone speaker instead of car speakers.
- Tap Limit Override: The tap limit override feature (disabling Android Auto’s driving restrictions on touch input) is only effective on head units with GPS.
- “Android Auto Still Connected” Message: In rare cases, after disconnecting your phone, you might see a message indicating Android Auto is still connected. Force stopping Google Play Services on your phone usually resolves this.
- Headunit Server Requirement: Unless you have root access on your Android phone, the Headunit Server needs to be running for OBD2AA to function correctly.
Open Source and Future Potential
The developer’s decision to open-source OBD2AA is a significant opportunity. While official updates have ceased, the community now has the power to maintain, improve, and expand upon this valuable application. For those with development skills or an interest in contributing, the GitHub repository (https://github.com/borconi/obd2aa) is the place to explore the code, contribute bug fixes, or even add new features.
However, it’s crucial to respect the original developer’s license. The open-source release is for personal use, and redistribution of modified versions under a different name is not permitted.
Conclusion: OBD2AA – A Powerful Tool for Car Enthusiasts, Now in Your Hands
Despite being end-of-life, OBD2AA remains a powerful and customizable tool for displaying OBD2 data on your Android Auto head unit. Its open-source nature offers both challenges and opportunities. While users might need some technical know-how to set it up and potentially maintain it, the rewards are significant: real-time access to crucial vehicle data, customizable gauges, and enhanced vehicle awareness.
If you’re a car enthusiast, a DIY mechanic, or simply someone who wants to understand your car better, exploring OBD2AA is well worth the effort. With the open-source code available, the future of OBD2AA is now in the hands of the community, and its legacy as a valuable tool for automotive enthusiasts can continue.
