Any Issue(s) with Using Dronelink on Samsung S23?
Just curious...
- Is anybody using Dronelink on the Samsung S23?
- Is anybody using Dronelink on the Samsung S23 with the Mavic Air2?
Thank you for any replies.
Kind regards, Kelly
Just curious...
Thank you for any replies.
Kind regards, Kelly
<%= block.description %>
<% } %>
Comments
12 comments
S22 had issues, so not sure if S23 will work either:
https://support.dronelink.com/hc/en-us/community/posts/5323971715731-Dronelink-Samsung-S22
Thanks Jim for the link and your reply.
1. Live video feed not working
2. No
Thanks for the second link.
The S23 was ordered yesterday and was what prompted this question/ thread.
Will report back re: test mapping mission after it arrives.
I am going to hold off getting the app, I am working on an S23 Ultra as well.
Is there any release date information for the MSDK
V. Kelly Bellis
Have you found a solution to this yet?
To be clear, the issues are with the S22. We have not tested with an S23 to see if those issues carry over.
DJI doesn't usually give release dates.
Thank you for such a fast response!
Higher in the thread it is stated that DJI was going to fix the issue in MSDK 4.16.5
If I read the DJI site, MSDK 5 is the current version, has the issue been resolve on the S22?
I assumed it was an issue with Android 12 and higher, but I might be misunderstanding it completely.
Again, thank you for your time and attention
Confusingly, DJI is currently maintaining two major versions of their SDK (v4 and V5). V5 is only for their new drones such as the M3E and M30.
Seems legit!
Thanks again
UPDATE 20230317 - Data and Apps from the old phone (Galaxy A71) were transferred to the S23 yesterday afternoon, phone allowed to fully charge and to sort itself out overnight. The following are initial observational notes that I wanted to share before further testing.
On the S23, first launch of the DJI Fly App (v1.9.4 originally installed 20230213 on the old phone), the behavior of the app was as if all things were new and starting from scratch with the logging into account, password, little tutorials, etc. A check of available updates showed the DJI Fly App was fine, but the FlySafe Database needed an update.
Still testing the S23 with the DJI Fly App, outdoors with the regular RC-N1 that came with my Mavic Air 2, and here again, it was as if all things were new and starting from scratch with the little tutorials, etc.. Ascended and shot pano without issue for this first test using the S23 with the DJI Fly App. The size of the S23 is a little bit shorter in length than the A71 and in its case is slightly thicker, but it was of no consequence in regards to the regular RC-N1.
Full power cycle off of everything. Charged aircraft batteries (only used a portion of batt-1) & phone.
On the S23, first launch of Dronelink v4.4.2 (238) Kernel 4.4.2, the previously reported issue related Aircraft Encoder Error still present. Work around to avoid seeing this has been to first run the DJI Fly App before running Dronelink.
On the S23, running Dronelink and this mission (see 1776_flightpath_beta2), received notice to increase height limit on aircraft, which I don't believe was an issue with the S23 because 1) the mission altitude was set at 118m, 2) the aircraft was reported at 119m, and 3) the ceiling was fixed at 120m. Bumping it up to 122m allowed the mission to fly successfully.
The mission: 1776_flightpath_beta2 began with importing a kmz with photo points circling a center with a radius of 888 ft. At each planned stop, the heading was set to point toward the center of the circle then the gimbal for photo 1 was pitched at -67° followed by the gimbal for photo 2 going to -36°
The only (potential) issue that I observed was a video delay when the gimbal switched very quickly from the -67° to the -36° pitch. The other thing possibly worth noting was the fake sound of the camera shutter heard seemed truncated. Minor things, but none the less observed.
20230318 On the S23, running Dronelink v4.4.2 (238) Kernel 4.4.2 and the Mavic Air 2, this mission (see 1776_flightpath_beta3) which added a mapping component to the earlier described (above) mission resulting in a battery pit-stop hot swap before returning to successfully complete the mission without issue.
During the mapping component execution, the fake camera shutter sound was truncated.
Please sign in to leave a comment.