TelloFpv v 1.3c which is the last one before the thread priority changes.Not yet, looks like it's going to be tomorrow morning before I can have time to do that. Also want to try it with more than one co-pilot, if I can get my wife to give up her phone for half an hour lol.
BTW what is that attachment in post #2558? It's labeled 13c
Then it was some power saving mode reducing max thread priority, thus the relatively heavy video processing was the thing that suffered first.When I lost a tello my phone battery was getting low, I was in vr mode and I could see by the bird in the center of the screen that the video feed was delayed but the commands and telemetry were not. I also noticed that if i leave my repeater on the sun and if it gets too hot I'll start having transmission issues. Watch you for that.
For the repeater & sun problem that is something I never heard before. Could be some freq inaccuracy, or maybe the internal processor of the extender is throttled to reduce temperature load.
as mentioned 1.3c is the last version before I changed the thread priorities. It already has copilot support, but no threading changes.It was with Copilot. As I have the test result having no issues without copilot, I now only test with copilot attached how to improve the situation here.
And yes, by default I always have a Gamesir T1d attached as this is my default way of flying the Tello. Therefore I also cannot switch off BT as it was suggested here by someone (ok for a test of course yes, but it cannot be the solution). For myself as a Workaround I potentially could change to a controller that doesn't need BT because it can be connected to the phone via USB (means additional invest as I currently don't own one).
But especcially for the approach I'd like to use the Copilot - using two Gamesirs via BT so that master and student both can have a real controller, the USB controller solution is again out (I don't want to have meters of cable between my phone and the student's controller).
I will give this a try in the evening and let you know.
1.3c is an older version than the one I received from Play Store?
An app creates threads, both long and short running ones, and assignes priorities. Thats all there is. How each of these threads is mapped to the cores is completely handled by Android.One more thought regarding Phones and threads.. Maybe it is worth to know that the Samsung Galaxy I think from S6 on is using the bigLITTLE processor pattern. Means you have 8 cores. 4 slower energy saving ones to run non-critical apps or tasks on that can live with lower performance, and 4 strong and power consuming ones for apps and tasks that need more power.
I don't know how your threads are organized and if they are split up among these 8 cores. Maybe it makes a difference if these threads are performed on one of the weak or strong ones (and if it is controllable from the outside or if the phone decides itself to which core it must delegate the thread).