The Bluedriver Obd2 Bluetooth scanner presents itself as a modern solution for vehicle diagnostics, appealing to those who prefer the visual interface of a smartphone app over traditional handheld devices. Initially, the wireless Bluetooth connectivity and the promise of a color LCD screen via your phone are strong selling points. My experience, however, revealed some limitations that potential buyers should consider, especially when compared to alternatives like the ScanGauge II.
My initial attraction to the BlueDriver stemmed from a preference for a color display and the convenience of a wireless setup. I envisioned using it with a dedicated older Android phone, kept solely for vehicle monitoring. This is where the first hurdle appeared: the BlueDriver requires an active internet connection each time you pair it with your vehicle. This means every single startup necessitates a data connection to authenticate and initiate the Bluetooth pairing process. While the connection shifts to Bluetooth for data streaming once paired, the initial internet requirement is a persistent inconvenience. Currently, I have to use my primary phone’s Wi-Fi hotspot to provide internet access to the secondary phone running the BlueDriver app, just to establish a connection with my car’s OBD2 system. While the hotspot can be disabled after pairing, this also unfortunately disables data logging and other online-dependent features, diminishing the “set and forget” usability I had anticipated.
Another significant drawback arises when considering smartphone integration within the car. I routinely use Android Auto on my primary phone via a USB connection to my Kenwood Excelon receiver. Android Auto is invaluable for navigation, media, and communication while driving. However, activating Android Auto via USB inherently disables Bluetooth on the phone. This creates a direct conflict: I cannot simultaneously operate both the BlueDriver scanner and Android Auto on the same phone. This mutually exclusive functionality significantly reduces the BlueDriver’s practicality for users who rely on Android Auto or similar in-car smartphone integrations.
Furthermore, after reviewing the BlueDriver documentation, it became apparent that its primary function leans more towards diagnostic readings rather than continuous, real-time vehicle monitoring. While it serves adequately as an on-demand diagnostic tool, its limitations in connectivity and simultaneous operation make it less ideal for constant system oversight. In retrospect, for my needs and intended use case, opting for a ScanGauge II, despite its simpler text-based display, might have been a more suitable choice due to its dedicated, always-on monitoring capabilities without the connectivity constraints of the BlueDriver.
