Package Details: bcm4350c5-firmware 1201710-8

Git Clone URL: https://aur.archlinux.org/bcm20702a1-firmware.git (read-only, click to copy)
Package Base: bcm20702a1-firmware
Description: Broadcom bluetooth firmware for BCM4350C5 based devices.
Upstream URL: http://asus.com
Licenses: custom
Conflicts: bcm4350-firmware
Submitter: Sonic-Y3k
Maintainer: None
Last Packager: Sonic-Y3k
Votes: 44
Popularity: 0.083869
First Submitted: 2015-10-10 09:48 (UTC)
Last Updated: 2017-07-10 18:12 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

beoldhin commented on 2017-01-13 13:44 (UTC)

I have two computers with bluetooth. One is a laptop with the latest Arch updates and another one is a desktop PC with the latest updates. The only difference between these two machines is that the laptop is running integrated BT with Cinnamon/blueberry while the desktop is running Gnome 3 (and desktop has btusb module modprobed). Both of them have pulseaudio-bluetooth installed. Now I try it with Plantronics Explorer 50. Laptop: Everything works flawlessly with the laptop. I can choose A2DP if I want to hear "stereo" and the configuration menu shows two speakers but they are actually only one physical speaker. Both of the testing buttons produce correct test sounds and there are no clicks, disconnects or noise when I listen to music etc. No problems at all. It never disconnects and even autoreconnect works perfectly. PC: It takes a lot of effort to even make the device pair. If it finally succeeds, configuration menus show ONE speaker in A2DP mode. If I press that testing button then I hear only "white noise" (like a radio between stations). The connection is broken after around 3 to 5 seconds and the sound menus are stuck (do not respond to user actions). If the UI doesn't get stuck then the headset selection is automatically removed from the menu. I've tried HCI reset and unblocking but it doesn't affect this problem. The headset is basically unusable with this BT adapter.

DOobR commented on 2017-01-11 11:47 (UTC)

I have wireless mini pci-e combo module with bluetooth via usb bus. Wireless module info: Network controller [0280]: Broadcom Limited BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: AzureWave Device [1a3b:2123] Bluetooth module info: Broadcom Corp BCM20702A0 PRODUCT=13d3/3404/112 Now bluetooth works well, ty for package maintaining.

neheb commented on 2016-12-29 03:54 (UTC)

Perfecto, soluciona problemas de controladores para bluetooth broadcom 43142a0

CReimer commented on 2016-09-11 13:00 (UTC)

Here's the extraction script in a more cleaned up version. It would be possible to remove some foreachs and use more regex instead but it's already quite difficult to read and understand. https://gist.github.com/CReimer/d8de01aa1bf2a0e097fc021829976730

nTia89 commented on 2016-09-07 08:15 (UTC)

you must remove the `sed` and `gawk` makedeps because they are part of base-devel group and as stated somewhere in the archwiki, base and base-devel packages belonging to these two groups must not be listed as makedeps

Sonic-Y3k commented on 2016-09-06 22:07 (UTC)

@CReimer thanks again for your contribution! An updated PKGBUILD should be available by now. I hope everything works as intended! Greetings, Sonic-Y3k

CReimer commented on 2016-09-06 21:23 (UTC)

And here's an updated list [1] for the newest driver package [2] 1: https://gist.github.com/CReimer/3ac17e008bf02cd39ae44073c5651ada 2: http://dlcdnet.asus.com/pub/ASUS/wireless/USB-BT400/DR_USB_BT400_1201710_Windows.zip

CReimer commented on 2016-09-06 21:16 (UTC)

BTW: I wrote a small but ugly script which extracts all hex files for all in Asus' driver package available firmwares Here's the result: https://gist.github.com/CReimer/d0e8a67a3280cb124037071cdea14cb9

CReimer commented on 2016-09-06 19:35 (UTC)

@Sonic-Y3k: Is there a reason you're relying on an amazonaws link for 0a5c:21e8? The necessary hex file is easily extractable from the Asus download. In fact it is BCM20702A1_001.002.014.1443.1459.hex. So you could remove this download an rely only on Asus' driver package again.