Here is the differences between the iOS version and the android version. I’ve circled it in yellow.Not sure why you’re not seeing it on iOS app. Mine shows it at the very top, near the center.
I don’t know about you, but I find that strange, since it’s not a sophisticated functionality!I've noticed the same thing. IOS app doesn't show the numeric value, but Android does.
I don’t know about you, but I find that strange, since it’s not a sophisticated functionality!
You’re probably right and admire your optimismI'm thinking it's just an oversight, probably fixed in an upcoming release.
Hi,Software developers here know exactly what (likely) happened.
One platform is the reference platform, that code being ported to the other platform. At some point the subordinate platform had to freeze it's development for testing before release, which had one of the two methods of displaying battery. After that, the superior platform got an additional change, which released, but wasn't included in the already well-under-way-testing platform release candidate.
Sounds a little complicated, but it really isn't when you think about it a bit.
Sure! The answer is, truly, very simple.Hi,
Thanks for the insight, much appreciated.
On another topic, could you please give us some insight on the frame skipping and video lag issues that everyone has been complaining about, especially with Bluetooth RCs, including MFI certified ones.
It was in a prior version. They updated the app and changed it for whatever reason..I'm thinking it's just an oversight, probably fixed in an upcoming release.
Hi,Sure! The answer is, truly, very simple.
A cell phone is a very poor WIFI transmitter. This is because it has no (real) antenna. Yes, there's a wifi antenna internally, and it does an amazing job for what it is, but it really isn't suitable for transmitting and receiving high bandwidth signals beyond 30ft or so. You'll notice that the Tello video stream is great when it's right by you. Get it out 50 ft away or so, and it starts to freeze, skip, lag, etc.
Want to make it worse? Put something between your phone and the Tello that really dense with water. Meat works well. Hey! That's a Human Body! Fly your Tello behind you and your range will drop fast.
It's all in the phone. And transmission characteristics for wifi can vary greatly among different phone models.
Contrast this with my Mavic Air, also only wifi, that made it 2.5 miles (13,000ft) unobstructed before I lost the video and brought it back (still had a control connection). However, the MA remote has two external antennas, and a more powerful transmitter.
You'll have problems with occasional dropped frames within a few feet if the drone is moving. Wifi is not designed for moving stations. There are entirely different (and far more robust) transmission protocols that do very well with moving sources.Hi,
Thanks for the detailed explanation, however I’ve seen frame skipping within a few feet away especially when a Bluetooth controller is being used.
I’m sure there’s something that Ryze and/or DJI can to improve it or even fix it. In fact, in another post on this forum a member received an answer from Ryze and DJI stating that they are aware of the issue and that it should be fixed in the next firmware release (they did not say, however when that will be).You'll have problems with occasional dropped frames within a few feet if the drone is moving. Wifi is not designed for moving stations. There are entirely different (and far more robust) transmission protocols that do very well with moving sources.
You will notice few, if any dropped frames when your Tello is sitting still on the ground. You can even walk quite a distance away and, when stop and stay in place for a short bit, again stable video without dropped frames.
The problem is not range; it's misuse of a wireless technology for a circumstance it isn't designed to handle reliable.
Okay.I’m sure there’s something that Ryze and/or DJI can to improve it or even fix it. In fact, in another post on this forum a member received an answer from Ryze and DJI stating that they are aware of the issue and that it should be fixed in the next firmware release (they did not say, however when that will be).
We use essential cookies to make this site work, and optional cookies to enhance your experience.