Crash on connect

[keyoss]

java.lang.NullPointerException
at com.ftdi.j2xx.FT_Device.isOpen(FT_Device.java:487)
at com.ftdi.j2xx.FT_Device.openDevice(FT_Device.java:424)
at com.ftdi.j2xx.D2xxManager.tryOpen(D2xxManager.java:1065)
at com.ftdi.j2xx.D2xxManager.openByIndex(D2xxManager.java:1136)
at com.ftdi.j2xx.D2xxManager.openByIndex(D2xxManager.java:1151)
at org.droidplanner.android.communication.connection.UsbFTDIConnection.openAndroidConnection(UsbFTDIConnection.java:40)
at org.droidplanner.android.communication.connection.AndroidMavLinkConnection.openConnection(AndroidMavLinkConnection.java:57)
at org.droidplanner.core.MAVLink.connection.MavLinkConnection$1.run(MavLinkConnection.java:83)
at java.lang.Thread.run(Thread.java:856)

2.7.2 RC1-15

[m4gr3d]

@arthurbenemann the NPE is comming from the ftdi library. Do we have access to the source?
For now, I'm wrapping the call with a try...catch.

[m4gr3d]

@keyoss does this happen all the time, or sporadically?
And what devices is this happening on?

[keyoss]

Its on a KOBO Arc 10 HD
just the 3DR Telemtry connected

it happens ALWAYS..

the only working APK for now is the old 2.6.(1?)

[keyoss]

the only release wich seems to work right now is 2.6.0 RC1

[m4gr3d]

@arthurbenemann it's probably related to the change of usb drivers.

[keyoss]

kobo android version is :
4.2.2

kernel
3.4.35

not rooted or modified

[arthurbenemann]

@ne0fhyk We don't have access to the source of the FTDI library.

The library used for FTDI devices is now the D20XX library (form FTDI), because we where having problems with the open usb library.

@keyoss One possible solution is to add a setting that forces the app to always use the open usb-library.

[keyoss]

i guess its managed by code?
i am not able to recompile anything at my side..

if its possible todo/change anything on my device.. tell me what to do, but keep in mind its not rooted... sadly

[arthurbenemann]

@keyoss Yes, it needs to be modified on the code.

[m4gr3d]

@keyoss I posted a debug version of the app with an updated usb connection layer for testing.
Could you try it out on your device, and let me know if that fixes your issue: https://github.com/ne0fhyk/droidplanner/releases/tag/v2.7.2.1

Bear in mind that you will have to uninstall the beta install (and thus lose saved preferences) in order to successfully install the debug release.

[keyoss]

works! up and running for 4hours!
several restarts performed and several reconnects done... smooth as it should be!

i always deinstall, delete related folders, reboot, reinstall, reboot, run the software..
only thing i back up is the offlinemaps ;)
'approved alpha/betatester since stoneage' ;)

cool seems file can be closed!
thanks..!

[m4gr3d]

That's great!
@keyoss Could you also check if you're successfully able to retrieve, and update the drone parameters.
@arthurbenemann I'll clean up the branch, and merge it into master before closing this issue.

[keyoss]

@ne0fhyk directly after connection are parameters already loaded or where does the values come from?
i refreshed parameters and they are fast and successfully loaded.

did 3 restarts/coldstarts and also some close/open connections - close/open droidplanner and everytime successful and fast parameter download. tbh.. faster than before? and it doent stuck while downloading.
also i noticed it sometimes depends on the device power if it stucks at parameter refreshments, but this was the case with old DP versions.

btw: nice additions.. like calibration possibilitys etc ;)

[arthurbenemann]

This has been fixed by #1042, thanks for reporting it @keyoss