Dronelink crashes
|
Popular Resources
-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (block.name) { %><% if (block.html_url) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% } %> <% if (block.description) { %><%= block.description %>
<% } %>
<% }) %>
Comments
21 comments
Are you referring to the mobile app, or the web app?
Ether one in my account.
Not sure what new/old dashboard is but clicking on Dashboard it opened without any problem. My DroneLink app has never been updated since I installed it from Google Play. I have no idea is it new or old version. Yesterday I tried to reinstall it the same way. May be it is new.
Mobile app. Web works perfect.
You can test opening the mission in the classic dashboard by configuring it from the main menu.
I was able to open Барсуки on my Pixel 6 in the modern dashboard without any issues. Do you have an alternate device you can try the modern dashboard on?
The mobile app home screen continues to use google maps, it just has a different theme no (no satellite imagery because it isn't a mission planning interface).
Got it.
Ok, got it too.
Ok, I switched to Classic one (there was Modern when app crashed). In classic I was able to open my both plans. Next I switched to Modern again and the app opens both plans without any issue. I quited the app and then tried to open the plan again. It crashes while in Modern mode. Next I closed the app and started it again: all started working as expected (both plans were opened). I rebooted the phone to make sure all will work and all works as expected in both modes (classic and modern).
I have no idea what that was but any way - it works and that's great.
Thanks a lot for your fast and greate support!
No problem - we would be grateful if you left a 5-star review in the Play Store!
Sure.
I can confirm the same issue for me. Air 2S. App version 4.0.0 (219) | kernel 4.0.0. galaxy 22 Ultra, Android 12.
I did wipe the cache, same thing. Cleared app data and logged in to the app, it worked fine until I went to fly dashboard or tried to open a project. A couple of times, I got it to fly a few feet up and it crashed again. Right now, the app is working fine without drone plugged in. I can browse projects and maps and dashboard without any errors.
I will try what you said tomorrow.
Ok, today I decided to check it again. And again it started crashes (app closes without any message when I try to open any flight plan). However, switching to Classic, opening any flight plan, switch to Modern mode back makes it working without any issue.
Unfortunately there is very bad weather so I can't test it in flight but when the weather changes I'll definitely do the flight test.
May be there is some debug build of the app exist? If so I do really happy to run it and send the logs back so you can fix the issue.
I tried it and that method worked for a bit. But I heard a airplane way off and wanted to see if it showed up on the Dronelink map. When I tried to zoom in/out, the app crashed, my drone stopped, and every time I tried to restart the flight, it continued to crash. Then I switched it to classic mode, and it worked fine the rest of the mission, including using the map.
Yes, I think its problem with modern UI on Android 12. I played a bit with drone connected and faced mor or less similar problem (app freezes and/or crashes). With classic UI it works without any problem. I had no any issue with it (Modern UI) on Android 10.
I think more specifically it is on lower performance devices, not necessarily Android 12. We already default to the classic dashboard for legacy Android devices but we may need to increase the size of that list, at least for determining when to default it to modern vs classic dashboard. To be clear, classic is going into maintenance mode and will not receive any new features so if modern isn't working on your device, you may want to consider upgrading eventually to enjoy all the new features and benefits of modern.
Probably, but why it worked on Android 10? I can understand that new features may require more handrware resources but don't follow Microsoft. I am a software developer and I know that it is always possible (if you are a good developer) to support all features even on old devices, not a big deal actualy to optimize your code.
Also I can't say that my device is "legacy". It is still on support and all modern app works without any problem. I also tried to run the app on Huawei P30, same crashes/freezes (Android 12).
Samsun S22 also does not look as legacy one.
The modern dashboard was not crashing on Android 10, and now it does only on Android 12?
When you have control over the code sure, but alas we live in a world of frameworks and libraries that aren't always open source. In this case, Modern relies on Flutter platform views. The classic dashboard is written in native code (Java on Android and Swift on iOS) and it is more performant because I wrote it and have direct control over it - and thus was able to optimize it as you say. We chose to move in the Flutter direction (which is what the rest of the app is written in beyond the flight dashboard) because it reduces the dashboard to one code base for both platforms, and it allows a velocity of development that is not possible in native land. If you have any bright ideas about how to squeeze more performance out of Flutter platform views, I am all ears. We don't have the time or the resources to implement modern in native code so it isn't going to happen. This is the main reason we left classic in the app (as an escape hatch for people with devices that can't handle it).
You may be interested in the performance discussion here. Per their comments, If there was going to be a different between modern Android versions and older ones, it would have been Android 9.
That's exactly what I wrote in my first post (I wrote that problem appeared since my device updated to Android 12 from Android 10). I also wrote that I had no idea in which mode it runs (Modern or Classic) because I have never need to switch them. And once I switched them yesterday/today I see that it always was in Modern mode. I also wrote that my DroneLink app has never been updated since first time installed.
Better stay with .NET (Mono) than Flutter. I know what I'm saying. (Just IMHO)
That was Android 10.
Your recommendation is to rewrite the entire app in .NET?
This is the bit I am referring to:
I have about the highest performing android phone there is - Samsung Galaxy 22 Ultra.. So personally I don't think that is my issue.
If you minimize the map in the modern dashboard does it still have issues?
Of course no, use any tool you think is better for your task.
Not sure I understood that. My device was not "prior" Android 10. It was Android 10, now it is Android 12. So nothing changed in this:
It started with map minimized (in Classic mode which I set as default for startup), then I resize map to full screen, then minimize it back, then to left side, then minimize again, exit from dashboard, changed flight plan and did the same steps: no issue. Switched to Modern mode and repeated the steps above - works. I can't test with drone in flight because of weather but with simple connected drone it also works.
It's hard to reproduce each time because it appears randomly. However if it started crashing - it crashes until I switch to classic and back. Then it works for some time.
Ok, DroneLink has been updated today and now all looks more or less working. At least it does not crash anymore but I had no time to test it in flight yet.
Please sign in to leave a comment.