cancel
Showing results for 
Search instead for 
Did you mean: 

Bluetooth Headset connected but has no sound

willhess
Level 7

Sometime in the last 2 weeks, my Ally X started having the "connected but no sound" problem where the bluetooth device successfully connects to the Ally X, but no sound comes through the headset.  The headset works with other paired devices and we tested a second set of bluetooth headphones with the Ally X but they experienced the same "connected but no sound" situation.

I have updated the Bluetooth driver (uninstalled and installed the latest from the ASUS support site).  I have also completed all other windows and bios updates.  Right now the only Bluetooth driver installed shows as Media Tek Bluetooth Adapter version 1.1043.2.545.  I also spoke with ASUS support who was unable to resolve the issue.

I'm not sure what else to try to resolve this issue.   Does anyone have any suggestions?

452 Views
1 ACCEPTED SOLUTION

Accepted Solutions

cl-Albert
US Customer Loyalty Agent

Hi,

Can you check under device manager for system devices and the AMD Audio CoProcessor to see if the driver version is 6.0.3.116 and rollback the driver in the device manager properties to version 6.0.0.113 if it is and reboot?

Also check device manager for the sounds, video, and game controllers for the AMD Bluetooth Audio Device to see if the driver version is 6.0.3.37 and rollback that driver in the device manager properties to version 6.0.0.34 if it is and reboot to see if there is any improvement?

View solution in original post

3 REPLIES 3

cl-Albert
US Customer Loyalty Agent

Hi,

Can you check under device manager for system devices and the AMD Audio CoProcessor to see if the driver version is 6.0.3.116 and rollback the driver in the device manager properties to version 6.0.0.113 if it is and reboot?

Also check device manager for the sounds, video, and game controllers for the AMD Bluetooth Audio Device to see if the driver version is 6.0.3.37 and rollback that driver in the device manager properties to version 6.0.0.34 if it is and reboot to see if there is any improvement?

Thanks so much! I did the first prt of rolling it back to 6.0.0.113 and rebooted it and now it works great. I can not tell tell you how thankful I am after spending 5+ hours trying to fix this issue. 

cl-Albert
US Customer Loyalty Agent

Thanks for reporting this problem and sharing what happened which can hopefully help others running into the same problem.

Also, not sure how long it will take, but expect there will be a newer driver released later which doesn't have this problem.