BenzWorld Junior Member
Date registered: May 2008
Vehicle: 1991 560SEC, 1992 500SEL, 2006 C230
Location: Edmonton, Alberta
Mentioned: 0 Post(s)
Quoted: 2 Post(s)
My daughter came by this morning and we gave it a try. Turns out the Drivebot wasn't communicating with her phone. Her ML and the device worked just fine recognizing one another however, her phone (an older Samsung Note 2) was the fail culprit. Using my phone (a nearly as old Google/LG Nexus 4) it worked and we achieved Bluetooth connection. The problem with her phone is simply a technical one. My phone has an up to date Android Kernel 5.1 whereas Carmen's phone is an older version 4.1. Due to Samsung's proprietary "TouchWiz" O/S layer her phone won't update it's kernel etc. etc. I guess that's one advantage of having a Virgin Mobile/Google phone.
The Drivebot itself is slick. It is small and does not in anyway intrude into the passenger foot well when plugged in. The device is new to Android, apparently only 2 weeks in since it was made available outside of iOS. Therefore, as Carmen describes it, early adopters such as her will encounter bugs. One annoying thing was the need to delete her vehicle to test it on Cecil. So currently the Drivebot app has the capacity to store the particulars of only one vehicle at a time. If more than one vehicle will ever be available remains to be seen.
As far as the code reading abilities, all of the "P" codes are available for powertrain, emissions, and, electronics. Sadly, no chassis and climate control error codes reading capability.
Overall score 8/10 because it has a lot of up potential and it is compact.
I've had a few over the last 37 years (I was 16 when I bought the '67 230)
My dad's first: A 1936 170V purchased in 1947 in Suhl, Thueringen in exchange for truck/bus tires and the rest is history...