- Joined
- Apr 21, 2015
- Messages
- 99
- Reaction score
- 23
Since getting my replacement Nvidia Shield tablet (battery recall), I had been having problems with the controller disconnecting randomly. I'd be flying around, and suddenly the DJI Go app would say DISCONNECTED (or something similar). No warning, no weak signal, just a sudden disconnect. I'd still be within radio range, the P3P would still respond to all inputs via the controller, RTH still worked, but the app would remain disconnected. Restarting the app would have no effect; only when I turn the controller off and back on again, then restart the application, would it re-establish communication.
Since the RC still had radio communication with the P3P, and due to the immediate nature of the disconnect, it made sense to me that maybe maybe the USB cable was to blame. I tried 2 other cables, but no difference. The disconnect was very random. It could be 2 minutes into the flight, it could be 15, or anywhere in between. The only other thing I could think of was that maybe I had a flaky USB port on the tablet. So I contacted Nvidia support. They agreed with my testing and diagnosis but wanted me to try a factory reset the tablet first before issuing an RMA. So I gave it a shot. I have only had 3-4 flights since the factory reset, but have not had any disconnects.
A realization occurred to me a couple of days ago...when I reinstalled the DJI Go application, and reconnected to the P3P, it never asked me to enable USB debugging. I went and looked at the settings - sure enough, Developer options were not yet enabled. When I did enable them, I was able to verify that USB debugging was not enabled. I factory reset my old Nvidia shield several times in the past to troubleshoot various issues, and always recall it requesting to enable USB debugging after reinstalling the app.
So my question is this...when did DJI stop requiring USB debugging be enabled for proper communication? It wouldn't surprise me if this was the root cause of the problem.
Thanks!
Happy Flying
Since the RC still had radio communication with the P3P, and due to the immediate nature of the disconnect, it made sense to me that maybe maybe the USB cable was to blame. I tried 2 other cables, but no difference. The disconnect was very random. It could be 2 minutes into the flight, it could be 15, or anywhere in between. The only other thing I could think of was that maybe I had a flaky USB port on the tablet. So I contacted Nvidia support. They agreed with my testing and diagnosis but wanted me to try a factory reset the tablet first before issuing an RMA. So I gave it a shot. I have only had 3-4 flights since the factory reset, but have not had any disconnects.
A realization occurred to me a couple of days ago...when I reinstalled the DJI Go application, and reconnected to the P3P, it never asked me to enable USB debugging. I went and looked at the settings - sure enough, Developer options were not yet enabled. When I did enable them, I was able to verify that USB debugging was not enabled. I factory reset my old Nvidia shield several times in the past to troubleshoot various issues, and always recall it requesting to enable USB debugging after reinstalling the app.
So my question is this...when did DJI stop requiring USB debugging be enabled for proper communication? It wouldn't surprise me if this was the root cause of the problem.
Thanks!
Happy Flying