Menu
Forums
New posts
Search forums
What's new
New posts
New media
New media comments
New profile posts
Latest activity
Media
New media
New comments
Search media
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Search
Search titles only
By:
Search titles only
By:
Menu
Welcome DJI Spark Pilot!
Jump in and join our free Spark community today!
Sign up
Forums
DJI Spark Forums
Spark Discussions
Another one bites the dust
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="NyJosh" data-source="post: 36255" data-attributes="member: 6744"><p>To OP, I'm terribly sorry to hear you lost your Spark. I'm pretty sure that's the one thing all of us dread the most.</p><p></p><p>I'm sure this won't be popular, but I am just not comfortable even considering flying with an OTG cable. To my knowledge, DJI has never supported it on the Spark. Just because people discovered it worked and you "could", doesn't mean you should.</p><p></p><p>I know it overcomes various issues and improves some user experiences, but I have to assume that if it was tested and known to be safe, DJI would have publicly stated it's a supported option.</p><p></p><p>The fact that they haven't (to my knowledge) and in recent app versions seem to have actively eliminated normal function with it, makes me think it's not safe and may even have known issues that haven't been publicly disclosed. Being in an engineering community, I can easily imagine the scenario went something like "let's build OTG support into the upcoming Spark drone! Ok! Hey boss, we did some last minute testing on OTG and found some problems we haven't figured out how to fix. OK, well it's too late to change the hardware to remove the option, but we just won't support it or cover it in documentation".</p><p></p><p>When one of my users comes to me saying "Hey, I've been using your product in this unsupported way and your latest update broke that ability!" my answer unfortunately has to be "it's unsupported for a reason and just because you found that you could do something in a way it wasn't intended, doesn't mean you should and we certainly can't support you doing it that way".</p><p></p><p>From a purely engineering standpoint, the right answer is to solve the issues people have been using the OTG cable for within the app and hardware that IS supported. Fix the issue and people won't look for a workaround.</p><p></p><p>If the limitation is on the user's phones / tablets, there isn't much DJI can do about that beyond publishing a list of devices they've successfully tested to work with their products and produce the results they say their product can achieve.</p><p></p><p>That's ultimately the toughest nut to crack - there are tens of thousands of smart phones and tablets out there in unlimited combinations of OS and hardware versions. It's all but impossible to certify / decertify even a fraction of them.</p></blockquote><p></p>
[QUOTE="NyJosh, post: 36255, member: 6744"] To OP, I'm terribly sorry to hear you lost your Spark. I'm pretty sure that's the one thing all of us dread the most. I'm sure this won't be popular, but I am just not comfortable even considering flying with an OTG cable. To my knowledge, DJI has never supported it on the Spark. Just because people discovered it worked and you "could", doesn't mean you should. I know it overcomes various issues and improves some user experiences, but I have to assume that if it was tested and known to be safe, DJI would have publicly stated it's a supported option. The fact that they haven't (to my knowledge) and in recent app versions seem to have actively eliminated normal function with it, makes me think it's not safe and may even have known issues that haven't been publicly disclosed. Being in an engineering community, I can easily imagine the scenario went something like "let's build OTG support into the upcoming Spark drone! Ok! Hey boss, we did some last minute testing on OTG and found some problems we haven't figured out how to fix. OK, well it's too late to change the hardware to remove the option, but we just won't support it or cover it in documentation". When one of my users comes to me saying "Hey, I've been using your product in this unsupported way and your latest update broke that ability!" my answer unfortunately has to be "it's unsupported for a reason and just because you found that you could do something in a way it wasn't intended, doesn't mean you should and we certainly can't support you doing it that way". From a purely engineering standpoint, the right answer is to solve the issues people have been using the OTG cable for within the app and hardware that IS supported. Fix the issue and people won't look for a workaround. If the limitation is on the user's phones / tablets, there isn't much DJI can do about that beyond publishing a list of devices they've successfully tested to work with their products and produce the results they say their product can achieve. That's ultimately the toughest nut to crack - there are tens of thousands of smart phones and tablets out there in unlimited combinations of OS and hardware versions. It's all but impossible to certify / decertify even a fraction of them. [/QUOTE]
Verification
Post reply
Forums
DJI Spark Forums
Spark Discussions
Another one bites the dust