yeah this has been bugging me for a while and i feel like the answer keeps changing depending on who you ask. i know the textbook answer is 2.4 for range and penetration, 5.8 for speed and less congestion in some cases, but i fly mostly in suburban areas and honestly the 2.4 band near housing is just absolutely saturated with wifi routers, smart home stuff, all of it.

running an Autel Evo Lite+ and it does the automatic frequency hopping thing but i still get occasional micro-stutters in the video feed when im flying over neighborhoods. not full disconnects but enough to be annoying especially if im doing any kind of slow cinematic stuff where a single frame glitch ruins the clip.

curious what people are actually seeing in practice in, not just the theoretical stuff. is 5.8 actually cleaner in a dense residential area now that the wifi 6 stuff has kind of pushed more devices up into those bands too, or is it still the better bet over 2.4 congestion. feel like theres no clean answer here but maybe someone has done actual testing.

honestly in my experience 5.8 has gotten worse in suburbs over the last couple years, not better. wifi 6 and 6e devices are everywhere now and a lot of them operate in that range. i did some informal testing with a spectrum analyzer app last summer and the 5.8 congestion in my neighborhood was actually comparable to 2.4 in terms of noise floor, which surprised me.

what actually made a noticeable difference for me was time of day. flying early morning before people are up and streaming and whatever, the video link on both bands is just cleaner. which sounds obvious but i hadnt really paid attention to it before. the automatic hopping on most modern systems is pretty good but its still reacting rather than avoiding.

the micro-stutters youre describing on the Autel might not even be frequency related tbh. ive seen that on mine and it ended up being a heat issue with the controller in direct sun. screen gets hot, processing slows slightly, video buffer hiccups. worth ruling out before going too deep into RF troubleshooting. just something to check.