-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPi3: Bluetooth impedes wifi #1552
Comments
see bug #1444 |
Is there any update regarding the issue? |
I don't think there is anything we can do without Broadcom/Cypress. They have expressed an interest and we have pointed them at the relevant threads, prodding occasionally, but so far I've heard no feedback. |
@pelwell Any reference at Cypress that I can ping? I would like to help if I can... |
They will see your comment, but I'd rather not overwhelm them. |
Ok, if there is anything that 'we' can help with regarding test etc., please let us know |
I would add this issue #1342 in bunch of the issues with WiFi and Bluetooth in RPi3, probably, they are interconnected. |
I already referenced this issue from #1342 .. The only reliable solution for a IIRC we created a modprobe.d-file to blacklist a couple of kernel modules
|
Perhaps, using an external usb wifi dongle could be a workaround for some projects but it is not a solution for users of RPi3 project as such. |
I would also have preferred things to just work and not having to spend some weeks on testing scenarios.. In the end the usb wifi path was a practical solution/workaround about 6-8 months ago (probably still is) if you do need it to work right now and not maybe work at a unknown future date. |
Hmmm, considering that Cypress have expressed an interest but these issues are now more than half a year old, it doesn't look like it has been that that high prioritised :-( It is a little bit sad as IMHO the wifi/bluetooth combo is really a key selling point for RPi3. Hopefully Cypress will give it some (more) attention. |
For reference this problem is not isolated to just the Pi. I have encountered the same problems on other platforms that have shared hardware for wifi/bluetooth (Intel Edison and Next Thing CHIP). I know the Edison also uses a Cypress/Broadcom chipset, but I'm not sure about the CHIP. |
Does anyone know if the pi3 B+ has the same problem? |
The Pi3 B+ has exactly the same problem, I can confirm that as I just did some testing. |
We did have improved firmware from Cypress that was supposed to help with BT/Wireless coexistence. I believe things did get better, but presumably, not much. Note that the chip on the 3B+ is different to that on the 3B, with different firmware (we presume), so its a shame that they both exhibit the same issue. Clearly there are hurdles to overcome with coexistence that is still a work in progress. I guess we need to prompt Cypress again, unless @pelwell has any comments? |
Out of curiosity, did you test with a 2.4G or 5G wifi connection? I thought that with 5G it might be using different circuitry so there would not be a coexistence problem. |
I used a 2.4G interface, I do not have a 5G router but you have just given me an excuse to go out and purchase an ASUS RT-AC86U. |
In August 2018 Cypress delivered some updated nvram-file parameters that have noticeably improved coexistence behaviour. I would suggest downloading a fresh Raspbian to a spare SD card and retesting. Alternatively you can grab the individual files:
Copy them into the /lib/firmware/brcm folder (you will need to |
I can confirm that Bluetooth and WiFi work much better together. I can stream from my phone via Bluetooth to a WiFi connected Pi without problems (using Moodeaudio). |
Any news on how resolve coexistence of bluetooth and wifi on pi0-w? |
Linux berry 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
Wifi gets extremely sluggish when Bluetooth is active. See forum topic for reference. Try pinging your next hop and resolve a (nonexistant) Bluetooth device (
hcitool name 11:11:11:11:11:11
) simultaneously.The text was updated successfully, but these errors were encountered: