Also can confirm they fixed the “On The Fly” missions saving in build (213). DL is pushing out Beta builds so quickly I didn’t get a chance to check it but, I flew some two days ago and they are all saved in build (214). Great work 🤙🏼
I have totally different versions than all of you. My phone says 3.4.1 (208) Kernel 3.4.1.
My desktop computer says Drone/Link Beta 4.0.0 Kernel 4.0.0.
When I try to download from their download site like Martin suggested my phone will not let me saying that I have to change settings but when I choose this option Dronelink is not even listed.
I initially started looking into the versions because I was having trouble with my remote connecting with my phone. I used different cords, even a different phone and I still have sporadic connections. Jim McAndrew said it was "a bug in the DJI UXSDK". In the meantime he asked if I tried the latest v4 build in Beta. I can't find it.
In the meantime I am arguing with DJI, they are saying it is because I am using a 3rd party app. I proved them wrong by performing 3 screen recordings of a launch with only DJI Fly and I could not launch due to the failure of the R/C not being able to connect to the portable device. I do not think it the R/C because when I can't connect with DJI I can still fly with the R/C, I just can't see where I am going.
DJI has currently put their "Senior Engineers" on the problem. It's been a week with no word. I am on my 3rd level of engineers. The last one wrote me and said, "So I see by our conversations (I have had numerous) that you are having trouble connecting your Remote Control to your Aircraft?"
This is the screenshot I sent them. I am losing a lot of confidence in the engineers at DJI.
Bob. Your version for the Browser Web app is correct. The Beta versions we are taking about are for the Native flight app.
The one I’m using is the Apple “Test flight” app for IOS for the Native flight app. Not sure what app Android devices uses. To get the Beta versions you need to sign up for Beta testing in that link to get the newest of the Beta Native app.
The drones can be flown without the app but obviously you lose everything to include video feed. Since you can fly I still believe it can be the connector in the controller. Those micro connectors are known to fail which won’t let it connect to the app. A bad or broken pin or even a cold solder could cause it to not communicate. I don’t think the Beta is going to fix your issue though.
I’ve read it’s better to download and install the correct APK pack directly from the DL page for Android instead of using Google Play. Those links for either 32 or 64 bit depending on which bit your specific device is.
Comments
6 comments
I downloaded mobile app v214 from Google Play.
Follow the instructions here
https://support.dronelink.com/hc/en-us/community/posts/360053000733-How-do-join-the-Dronelink-beta-
Also can confirm they fixed the “On The Fly” missions saving in build (213). DL is pushing out Beta builds so quickly I didn’t get a chance to check it but, I flew some two days ago and they are all saved in build (214). Great work 🤙🏼
Yeah, just downloaded 214, yet to fly with it
I have totally different versions than all of you. My phone says 3.4.1 (208) Kernel 3.4.1.
My desktop computer says Drone/Link Beta 4.0.0 Kernel 4.0.0.
When I try to download from their download site like Martin suggested my phone will not let me saying that I have to change settings but when I choose this option Dronelink is not even listed.
I initially started looking into the versions because I was having trouble with my remote connecting with my phone. I used different cords, even a different phone and I still have sporadic connections. Jim McAndrew said it was "a bug in the DJI UXSDK". In the meantime he asked if I tried the latest v4 build in Beta. I can't find it.
In the meantime I am arguing with DJI, they are saying it is because I am using a 3rd party app. I proved them wrong by performing 3 screen recordings of a launch with only DJI Fly and I could not launch due to the failure of the R/C not being able to connect to the portable device. I do not think it the R/C because when I can't connect with DJI I can still fly with the R/C, I just can't see where I am going.
DJI has currently put their "Senior Engineers" on the problem. It's been a week with no word. I am on my 3rd level of engineers. The last one wrote me and said, "So I see by our conversations (I have had numerous) that you are having trouble connecting your Remote Control to your Aircraft?"
This is the screenshot I sent them. I am losing a lot of confidence in the engineers at DJI.
Bob. Your version for the Browser Web app is correct. The Beta versions we are taking about are for the Native flight app.
The one I’m using is the Apple “Test flight” app for IOS for the Native flight app. Not sure what app Android devices uses. To get the Beta versions you need to sign up for Beta testing in that link to get the newest of the Beta Native app.
The drones can be flown without the app but obviously you lose everything to include video feed. Since you can fly I still believe it can be the connector in the controller. Those micro connectors are known to fail which won’t let it connect to the app. A bad or broken pin or even a cold solder could cause it to not communicate. I don’t think the Beta is going to fix your issue though.
I’ve read it’s better to download and install the correct APK pack directly from the DL page for Android instead of using Google Play. Those links for either 32 or 64 bit depending on which bit your specific device is.
https://support.dronelink.com/hc/en-us/articles/360033520874-How-do-I-install-the-beta-native-app-
Bob. I sent an email to you. Let me know.
Please sign in to leave a comment.