06-23-2022, 08:44 AM
(06-08-2022, 07:02 PM)dood_son Wrote:(06-07-2022, 08:14 PM)BlueWave Wrote: Did you install any additional software or did any modifications in config file? Did you update Raspberry PI OS to the latest version using apt tool? Did you update Pis firmware to the latest version?
Have you ever used rpi-update tool?
1. Did you install any additional software or did any modifications in config file?
No.
2. Did you update Raspberry PI OS to the latest version using apt tool?
No, shall I?
3. Did you update Pis firmware to the latest version?
No, shall I?
4. Have you ever used rpi-update tool?
No.
All the "tweaks" that I had done are:
1. enabling custom splash screens (from the package purchased from you)
2. sound (I have changed one value in PulseAudio'a default.pa file)
3. showing the mouse coursor (sudo bwscursor show)
4. hiding the trash icon on desktop (edited the file at /etc/xdg/pcmanfm/LXDE-pi/desktop-items-0.conf)
Are there are any log files that I could provide you with to help solve the problem?
SOLVED - there is no sound distortion during phone calls anymore.
I have reverted the change mentioned in [2] of the above "tweaks" list. The tweak that I have just reverted was replacing a line in /home/pi/.config/pulse/default.pa:
load-module module-udev-detect ignore_dB=1
with:
load-module module-udev-detect tsched=0 ignore_dB=1
So the only question that remains (but apparently has no real-life effect on the functioning of the whole setup) is [4] from my post at 06-20-2022, 07:26 PM:
4. Moreover, both CSR dongles create an error message when asked to "Search" [3] after a fresh boot-up of the RPi. In order to apparently fix this issue it is enough to remove the dongle from the RPi and plug it back in. Then the "Search" and "Pair" steps described in [3] are possible. Such an error is never produced by the ASUS dongle.
Moreover the ASUS dongle with a Broadcom chip seems to be fully functional now. I will do some more tests and reconfirm but so far it acts exactly like the CSRs but does not produce the error described in [4] above. So to recap, the following dongle (although NOT CSR) seems to work just fine:
BCM20702A0 - looks like this, but I cannot be sure if mine is branded as BT400 as I have already thrown away the packaging:
Product ID: 0x17cb
Vendor ID: 0x0b05 (ASUSTek Computer Inc.)
Version: 1.12
Serial Number: 5CF370A6C81F
Speed: Up to 12Mb/sec
Manufacturer: Broadcom Corp
Location ID: 0x14100000 / 4
Current Available (mA): 500
Current Required (mA): 100
Extra Operating Current (mA): 0
Thank you BlueWave for the help and comments! I hope that my case will help out someone else. If your CSR dongles do not work straight out of the box with OpenAuto Pro do the updates described by BlueWave and you should be golden.