I can only think it is something I am doing but I don't know what, why or how to remedy it.
I've used a Lenovo Chromebook and Asus Chromebook both of which have the same problem. Half way though listening to music last night on some Soundcore Q30 Bluetooth headphones after abut 10 minutes there was a crackle the music went very loud and so tinny (oddly enough the same sort of thing happens to my Google Pixel Buds pro) I tried turning the volume down low on the Chromebook using the headphone amp in case it was signal saturation - the headphones were fully charged. The only work around I have is to turn Bluetooth and the headphones off and on again. I am pointing towards Bluetooth as USB headphones aren't affected. This has been going on ever since I have been using Chromebooks.
Is it the headphones? Is it the laptop? Is it the OS? No matter how many updates I install the problem doesn't go away. I can't believe Google would not address this bug which is why I'm thinking its something to do with the headphones?
Can anyone recommend a good quality Bluetooth headset that's immune to this issue or has a proper work around with flags?
PS. I caried on using my old Linux laptop with no issues for the rest of the night
I've used a Lenovo Chromebook and Asus Chromebook both of which have the same problem. Half way though listening to music last night on some Soundcore Q30 Bluetooth headphones after abut 10 minutes there was a crackle the music went very loud and so tinny (oddly enough the same sort of thing happens to my Google Pixel Buds pro) I tried turning the volume down low on the Chromebook using the headphone amp in case it was signal saturation - the headphones were fully charged. The only work around I have is to turn Bluetooth and the headphones off and on again. I am pointing towards Bluetooth as USB headphones aren't affected. This has been going on ever since I have been using Chromebooks.
Is it the headphones? Is it the laptop? Is it the OS? No matter how many updates I install the problem doesn't go away. I can't believe Google would not address this bug which is why I'm thinking its something to do with the headphones?
Can anyone recommend a good quality Bluetooth headset that's immune to this issue or has a proper work around with flags?
PS. I caried on using my old Linux laptop with no issues for the rest of the night
