When choosing an OBD2 sensor, the appeal of a color LCD screen and wireless connectivity led me to select the BlueDriver Bluetooth OBD2 Sensor over options like the ScanGauge II. The idea of using a dedicated, older Android phone as a display seemed like a smart, clutter-free setup. However, my experience with the BlueDriver revealed a few crucial aspects that potential buyers should be aware of, particularly if you’re envisioning a seamless, always-connected monitoring system.
The most significant hurdle I encountered was the BlueDriver’s requirement for an internet data connection every time you want to pair it with your vehicle. Yes, you read that right – each and every restart necessitates an internet connection for the initial pairing process. While subsequent data streaming to your phone relies on Bluetooth, that initial handshake demands internet access to validate and connect. This immediately threw a wrench into my plan of using a standalone, non-data Android phone. To get it working, I had to resort to using my primary phone’s Wi-Fi hotspot to grant the BlueDriver app on the secondary phone internet access to the vehicle database. Once paired and running, the hotspot could be turned off, but features like data logging would become disabled. This was far from the “set and forget” wireless system I had anticipated.
Another point of consideration arose when attempting to integrate the BlueDriver with Android Auto. Like many, I use Android Auto in my vehicle, connecting my primary phone to my Kenwood Excelon head unit via USB. Android Auto is fantastic, providing navigation, music, and communication features seamlessly. However, upon connecting to Android Auto, Bluetooth on the phone is disabled. This means that running both BlueDriver and Android Auto simultaneously on the same phone is impossible. For those who frequently use Android Auto and desire continuous vehicle monitoring, this limitation is a significant drawback.
Furthermore, delving into the BlueDriver manual revealed that its primary function leans more towards a diagnostic tool rather than a continuous, real-time monitoring system like the ScanGauge II. While it’s certainly useful for occasional diagnostics and checking fault codes, it may not be the ideal choice for users seeking constant gauges for parameters like engine load or DPF temperature always displayed. While I intend to use my BlueDriver for specific diagnostic tasks, in retrospect, for my needs, the ScanGauge II might have been a more suitable purchase given its always-on display and independent operation. If you are looking for a dedicated monitoring solution without internet dependency and Android Auto compatibility concerns, it’s worth considering alternatives that prioritize these features.
