Current version of the OpenAuto Pro is 12
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problem with hands-free telephony cracking, dropouts
#1
I have had massive problems with the phone function of OAP for a long time.
It is completely unusable for me since, I think it was some 9 version.
Before that it worked fine (with the same hardware I use now).
I have a Pi 3b+ with the following components:
Bluetooth: LogiLink BT0015 nano
Sound card: https://www.amazon.de/gp/product/B00NMXY2MO/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

I have already tried the following:
- Different Bluetooth adapter, same Bluetooth adapter but bought new
- Other sound card
- New installation of OAP V11 (no update installation as before)

Here a video where you can see the problem:
https://youtu.be/tLyHZnM-qXY
Reply
#2
Please try to test the solution from this https://bluewavestudio.io/community/showthread.php?tid=2142&pid=12356#pid12356 reply and report the result.

Edit: please also post output of lsusb command.
Reply
#3
(11-02-2020, 11:31 AM)BlueWave Wrote: Please try to test the solution from this https://bluewavestudio.io/community/showthread.php?tid=2142&pid=12356#pid12356 reply and report the result.

Edit: please also post output of lsusb command.

The changes at default.pa makes no difference.

Here is the output of the lsusb command:
Bus 001 Device 012: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)
Bus 001 Device 011: ID 04d9:0321 Holtek Semiconductor, Inc.
Bus 001 Device 010: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 009: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 007: ID 2341:8037 Arduino SA
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 004: ID 0eef:0005 D-WAV Scientific Co., Ltd
Bus 001 Device 006: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Reply
#4
Did you restart the PI after changes in default.pa file? How HFP works with different phone? Please post content of /boot/config.txt file and output of hciconfig command.
Reply
#5
(11-02-2020, 04:36 PM)BlueWave Wrote: Did you restart the PI after changes in default.pa file? How HFP works with different phone? Please post content of /boot/config.txt file and output of hciconfig command.

Yes I resarted the Pi bevor testing again. And the other Phone I have can't connect to OAP both can't find the other. But I use the same phone I used as it works And audi over bluetooth works with that phone.

hciconfig


hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:08  ACL MTU: 310:10  SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:5922032 acl:16870 sco:8012 events:1135 errors:0
        TX bytes:458259 acl:930 sco:7895 commands:140 errors:0


/boot/config.txt

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=off
dtoverlay=disable-bt
disable_splash=1
dtoverlay=vc4-fkms-v3d

#[pi3]
#gpu_mem=256
#max_framebuffers=1

[pi3+]
gpu_mem=256
max_framebuffers=1

#[pi4]
#max_framebuffers=2

# LCD
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_drive=1
hdmi_cvt 1024 600 60 6 0 0 0
enable_uart=1


max_usb_current=1
Reply
#6
Try to quit OpenAuto Pro before pairing the new phone. Some USB dongles have problems with simultaneous discovery and connect operations.
Reply
#7
(11-03-2020, 10:14 AM)BlueWave Wrote: Try to quit OpenAuto Pro before pairing the new phone. Some USB dongles have problems with simultaneous discovery and connect operations.

The Galaxy A20 seems to be difficult to use with bluetooth...
I have quit OAP and then I can pair both. After that I reebot but I can't connect, after quiting OAP I'm able to connect.
But a phone call shows the same benavor, massive cracking and dropouts like in the video.
Reply
#8
Please have a look at Bluetooth module docs at https://www.freedesktop.org/wiki/Softwar...oth-policy

Please try to test it with auto_switch=0 mode. In order to due that modify below line in /home/pi/.config/pulse/default.pa

load-module module-bluetooth-policy

to

load-module module-bluetooth-policy auto_switch=0

Also it might be good to test another brand of Bluetooth dongle to exclude problems with the hardware or drivers.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)