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 Help
No battery status when using remote
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="Peter Powers" data-source="post: 26198" data-attributes="member: 2759"><p>I don't know what you are playing at. I've made no claim of them breaking it intentionally, and I don't believe they did break it intentionally either.</p><p>Please refrain from putting words to my mouth.</p><p></p><p>What I said that they broke it is bad, and the way they deal with it is worse.</p><p></p><p>As a software engineer for many years I can read a few things from how problems in software manifest, and my best educated guess is that what broke OTG is a problem that could easily have been caught before rollout to the end user, as it's manifestation is very consistent, and either automated unit or integration tests should have caught it (and at least the unit tests should be there even if OTG us not supported, while integration tests can actually be missing as the full product doesn't officially require the functionality. In an ideal world a system like this would be worked on with both sorts of tests). Now bugs happen, so it's bad they are not testing, but if they would deal with the bug properly, priorizing it, and communicate clear and open about it, wgich they don't.</p></blockquote><p></p>
[QUOTE="Peter Powers, post: 26198, member: 2759"] I don't know what you are playing at. I've made no claim of them breaking it intentionally, and I don't believe they did break it intentionally either. Please refrain from putting words to my mouth. What I said that they broke it is bad, and the way they deal with it is worse. As a software engineer for many years I can read a few things from how problems in software manifest, and my best educated guess is that what broke OTG is a problem that could easily have been caught before rollout to the end user, as it's manifestation is very consistent, and either automated unit or integration tests should have caught it (and at least the unit tests should be there even if OTG us not supported, while integration tests can actually be missing as the full product doesn't officially require the functionality. In an ideal world a system like this would be worked on with both sorts of tests). Now bugs happen, so it's bad they are not testing, but if they would deal with the bug properly, priorizing it, and communicate clear and open about it, wgich they don't. [/QUOTE]
Verification
Post reply
Forums
DJI Spark Forums
Spark Help
No battery status when using remote