AndrOBD icon indicating copy to clipboard operation
AndrOBD copied to clipboard

Experience with specific vehicles / adapters / mobiles

Open fr3ts0n opened this issue 3 years ago • 11 comments

Hi community,

Based on some user requests / issues I would like to initiate a information exchange about your user experience to use AndrOBD on certain vehicles, adapters mobiles. Some of us do have problems using certain adapters for certain vehicles.

This query could help many others to find good working adapters for their vehicles.

Please post comments with following information

  • Vehicle (make, model, year, engine)
  • OBD adapter (make, model, product link)
  • Mobile (OS, version)
  • Your experience
  • Rating of usability ⭐⭐⭐⭐⭐

Thank you very much

Bet regards fr3ts0n

fr3ts0n avatar Dec 31 '21 10:12 fr3ts0n

Vehicle: various OBD adapter: ObdLink MX, product link Mobile: Asus Zenfone 6, official Android 11 Your experience: ObdLink MX is reverse compatible with ELM327, so that's why i assume it works very good with AndrOBD, since AndrOBD also shows all the information i need that official app offers. on some cars it didn't work but that wasn't andrOBD's issue, since it worked with no apps due to vehicle's connectivity problems. I would like to see full support for STN chips (some extra features afaik). Rating of usability: :star::star::star::star::star:

aha999 avatar Jan 07 '22 02:01 aha999

OBD adapter: Mini ELM327 Scanner

Vehicles:

  • Ford Focus ~2006,
  • Hyundai i10 ~2013,
  • Hyundai i30 ~2015,
  • Nissan Micra ~2002
  • ...

Mobile: Various No-Names (Android 7 - 11)

Experience: Adapter was sold as KKMoon at time of ordering (2015). Since it is so tiny, I always have it in my backpack ...

  • Adapter works surprisingly good on vehicles with CAN system
  • Rather bad on ISO9141 systems (Nissan Micra 2002)
    • Manual pre-selection of ISO protocol did help, but poor performance / response times

Rating of usability:

  • CAN systems: ⭐⭐⭐⭐
  • ISO9141 systems: ⭐

fr3ts0n avatar Jan 07 '22 08:01 fr3ts0n

OBD adapter: KOEY OBD2 Diagnosegerät

Vehicles:

  • Ford Focus ~2006
  • Hyundai i10 ~2013
  • Hyundai i30 ~2015
  • Nissan Micra ~2002
  • ...

Mobile: Various No-Names (Android 7 - 11)

Experience:

  • Adapter was sold as "Tinxi Bluetooth EOBD OBD 2" at time of ordering (2012).
    • was around 30€
    • I didn't open it up, but I assume it contains a real ELM327 chip
  • Works well on all vehicles / protocols I got my hands on

Rating of usability:⭐⭐⭐⭐⭐

fr3ts0n avatar Jan 07 '22 09:01 fr3ts0n

Vehicle: Ford Focus MK3 FL (2014-2018)

OBD adapter: Viaken VSCAN STN1170 (Scantool FTDI drivers)

Mobile: Android 11 (Samsung One UI 3.1)

Your experience:

  • App do not read modules errors, it did not show any error. Probably because of two CANs (HSCAN and MSCAN) in newer Fords.
  • It read some PIDs, but it looks like only from PCM.

Rating of usability ⭐⭐

SylwesterZarebski avatar Feb 22 '22 07:02 SylwesterZarebski

  • Vehicle: 1998 Subaru Legacy GT, EJ25 engine (also briefly tested with a few other vehicles with similar behavior)
  • OBD adapter: (Veepeak Mini WiFi OBD II Scanner)
  • Mobile: Oneplus 5T, LineageOS 18 (Android 11)
  • Experience:

Connection with ECU drops almost immediately after it begins. Sometimes it stays connected long enough to get a list of trouble codes, but it takes a few tries, and it always disconnects after a short time. This makes looking at any real-time data like RPM impossible.

Also, the WiFi-based adapter is a pain to connect to, because Android judges its WiFi network to have "no internet". I have to wait for a "no internet" notification to pop up, then click "yes, stay connected", otherwise AndrOBD's attempts to connect to 192.168.0.10 get routed to my phone's LTE connection, even while my phone is connected to the device's WiFi network.

  • Rating of usability :star:

lesbianlizard avatar Apr 07 '22 01:04 lesbianlizard

OBD Adapter: Mini ELM 327 https://www.aliexpress.com/item/2251832764943250.html?spm=a2g0o.order_list.0.0.2a521802V6qndn

Phone: Pixel 5a

The phone will bluetooth-pair with the adapter. That part seems to go fine. When the app starts, the OBDII device shows up on the list of devices, but when I select that device, the app tries to connect for a few seconds, then gives up. No error messages.

donpdonp avatar Jun 30 '22 02:06 donpdonp

  • Vehicle: Nissan Micra K13 2011
  • OBD adapter: Veepeak Bluetooth 4.0
  • Mobile: Android 12
  • Your experience: I could do what I intended to do: clear the engine light for an error that has been checked by 3 different mechanics and could not be solved (and doesn't impact in any way the driving):
  • Rating of usability: :star::star::star::star::star:

Petemir avatar Apr 19 '23 13:04 Petemir

Vehicles: 2019 Ford Ecosport 1998 Ford Explorer

OBD Adapter: FIXD Bluetooth OBD Scanner

Mobile: Pixel 3a, CalyxOS (Android 13 Custom Rom)

Experience: I was able to see pretty much everything about the Ford Ecosport, but no vehicle info for the Ford Explorer, which was most likely due to it being 2 years after OBD became a standard, and is most likely not capable of displaying vehicle info. However, this device did show me OBD information, as well as codes for both vehicles, despite their large age gap.

EDIT: Newer models of this OBD sensor don't work properly at all, giving false codes, as well as not showing obd data. Would not recommend unless you are getting what I believe is the 1st generation of this scanner. Rating is changed accordingly.

Rating of usability: ⭐⭐⭐

slender100 avatar Aug 27 '23 00:08 slender100

Vehicles: 2019 Ford Ecosport 1998 Ford Explorer

OBD Adapter: BAFX Products OBD2 Scanner

Mobile: Pixel 3a, CalyxOS (Android 13 Custom Rom)

Experience: This scanner can be slow at first, and can sometimes not show data unless the section you are trying to view is re-selected, but works great. This scanner may also be difficult to plug into some OBD2 ports depending on the vehicle. For example, the scanner had to be jiggled onto the OBD2 port of the Ford Ecosport, but only had to be pushed into place by just a bit on the Ford Explorer. Overall, I would recommend this if you are wanting to get a product that is quality controlled when compared to the other cheap chinese ELM327 scanners.

EDIT: Scanner stopped being functional in communication with the Ecosport, but still works with the Explorer. Rating changed accordingly.

Rating of usability: ⭐⭐⭐ and 1/2

slender100 avatar Sep 02 '23 02:09 slender100

Vehicles: 2019 Ford Ecosport 1998 Ford Explorer

OBD Adapter: Generic OBD2 ELM327 "Branded" Adapters

image

Mobile: Pixel 3a, CalyxOS (Android 13 Custom Rom)

Experience: This scanner works well. Virtually no delay or issue with connectivity. This scanner is also very lightweight, as the pcb is smaller, yet still works as good as others. This scanner typically can go for really cheap on ebay or aliexpress, around 5 USD or less. Be sure to look for scanners of this chassis type, and general look.

Rating of usability: ⭐⭐⭐⭐⭐

slender100 avatar Jan 29 '24 05:01 slender100

Vehicles: 2019 Ford Ecosport 1998 Ford Explorer

OBD Adapter: "HHOBD Advanced" Adapter

image

Mobile: Pixel 3a, CalyxOS (Android 13 Custom Rom)

Experience: This scanner isn't too good. When I tried connecting to the Ecosport's ECU, it would keep having issues connecting until I fully turned the vehicle on. This scanner would refuse to connect to the Explorer completely. Avoid.

Rating of usability: ⭐⭐

slender100 avatar Feb 07 '24 22:02 slender100