well they have FCC compliance, so i'd hope it's just internal interference due to lack of rf separation on the board. unless the fcc test is so busted that they were able to activate a less-problematic pixel clock and never tried the full possible range? :D
since i don't have a github account i don't think they will listen to me about my issues with the device. but anyway they should hire an RF engineer and not me. if they tried the common combinations at all they should have noticed themselves, no ? i have been using 4k@60hz when i experienced my problem, bluetooth cannot be switched to 5ghz. i'm just happy it works at all, i was just gonna return it otherwise like i did with the earlier rpi version. don't have time to make bug-wishlists for future raspberry christmas trees (took them 8 years already to make the first rpi with working ethernet+usb). On 11/14/20, Bakul Shah <ba...@iitbombay.org> wrote: > There were reports of 2560x1440 res generating RF noise in the 2.4GHz band > wifi channel 1. The proposed solution (by Eben Upton) was to use channel 4 > or higher or use 5GHz wifi band at this res. And supposedly there is a > firmware fix for this. No idea about the bluetooth issue. You should report > these issues either on their forum or one of their github repos. > >> On Nov 14, 2020, at 7:14 AM, hiro <23h...@gmail.com> wrote: >> >> well, for me hdmi reliably stops working when i turn on the bluetooth >> keyboard and versa. >> clearly RF interference was none of their concern when they made this >> chip. >> if your monitor suggests a different pixel clock you might get lucky >> and it's just good enough, but your signal quality is gonna suffer no >> matter what ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te91377223453b8c0-M99276b0fa02ff05d3a4ace1f Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
