AndrOBD crashes when establishing USB connection to ELM327 adapter

[20210213]

Describe the bug

When establishing the USB connection in the usual way, recent versions of AndrOBD crash as follows:

Steps to reproduce the behavior:

1. plug USB cable from the adapter into the cellphone
2. confirm to open AndrOBD
3. The proposed USB connection is displayed. Click on it to confirm.
4. Android displays that AndrOBD has crashed.

Expected behavior

Instead of crashing according to item 4, AndrOBD should open and communicate with the ELM327 adapter.

AndrOBD Debug log files

Please attach AndrOBD debug log files.
AndrOBD.log.1.txt

Important details on your environment:

• Android OS version: 9
• AndrOBD version: 2.6.13
• OBD adapter type: noname ELM327 USB adapter

Additional context

Note: When no USB connection is established, e. g. with no cable connected to the cell phone, AndrOBD 2.6.13 will start.

The last version which worked OK with the same adapter was 2.6.7.

We encountered an identically looking issue already in February 2021; it was fixed after a bug report.

[fr3ts0n]

Thank you for your report,
I can reproduce the problem on connecting to my USB adapter.
(Pls remind me to include this as a smoke test for releases)

I can see following error message in the android logcat output when the USB device class is instantiated:
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.hardware.usb.UsbEndpoint.getMaxPacketSize()' on a null object reference

I'll contact @mik3y who is the developer of the USB device library used by AndrOBD.
Reverting the library to the version 3.3, which was used with V2.6.7 (your reported last known good version) would fix the problem.
However, there are several extensions and fixes listed in the changelog of the library.

[fr3ts0n]

mik3y/usb-serial-for-android#611