07-17-2020, 10:30 AM
Please reproduce the issue and provide use /home/pi/.openauto/cache/openauto.log file.
07-17-2020, 10:30 AM
Please reproduce the issue and provide use /home/pi/.openauto/cache/openauto.log file.
07-17-2020, 11:22 AM
(07-17-2020, 10:30 AM)BlueWave Wrote: Please reproduce the issue and provide use /home/pi/.openauto/cache/openauto.log file.Sorry, but i don't know how/where is this file, but when i exit openauto and go to raspbian desktop it says "couldn't find matching udev device". I tried with 2 phones and they do the same.
It is located at /home/pi/.openauto/cache/openauto.log. Directories with name stared by dot (.) are treated as hidden. Without logs we are not able to figure out what heppens. Udev error means that your phone denied to mount it as a massive storage device. It does not matter in this case.
Please also have a look at this post https://bluewavestudio.io/community/show...6#pid10776.
IGNORE THE POST THAT FOLLOWS. After the original post, I switched out the USB Bluetooth adapter, reset bluetooth connections between phone and Pi and rebooted. Everything connected this time. It appears the problem I had was the USB adapter.
ORIGINAL POST: The fixes made in oap 9.1 now allow me to connect instantly without having to do manual acrobatics to connect. AA and attached apps work very well. Too, I didn't need to do anything special to enable my hifiberry AMP2. THANK YOU, thank you, thank you. However, the bluetooth is not fully operational. I am successful in pairing my phone to the PI. When I check the pairing options, both music and phone sound options are on. When I checked on Connected Pro, it would not connect. I checked the USB setting on my phone (since it was a previous issue). The USB connection in OAP 9.1 now defaults to file transfer. When it wouldn't work in 9.0, it defaulted to charge this phone. I manually changed the setting to Connect a MIDI device and then tried Connected Pro again. This time it DID connect. Then, I tested the bluetooth connection. When the call came in, it did display on my screen. The phone ringing sound file DID NOT play. The phone (which was previously set up to only ring) DID NOT ring but did vibrate (??). I thought that when tethered to OAP, it would do neither. When the call was accepted, it connected through the phone's speakerphone feature. The OAP bluetooth sound system WAS NOT engaged. The same happened when I attempted a call out. Also I noticed a difference between the volume level set in OAP and the significantly reduced volume level on the phone. It should be noted that when I play music, it plays through the OAP system and car speakers. One other issue I am facing. In OAP 9.0, I was using my own python script for a horizontal flipped backup camera. The script backupcamstart.py was called by /etc/rc.local. Now in OAP 9.1, the script is not connecting. The only difference between then and now are the standard updates to Pi and this update to OAP 9.1. Your assistance please. Pi 4b usb bluetooth usb mic samsung galaxy S7 edge OAP 9.1 Connected Pro
We suggest to double check Bluetooth on your phone on dongle connected to the Raspberry PI. We are not able to reproduce any of the issues you are mentioned (using various phones) so the issue must be somewhere in used components (dongle/phone).
Regarding the script, nothing but update of Raspberry PI OS changed in the newest version. Everything else is OpenAuto Pro internals that does not even touch camera functionalities. Please post the script you are using we will check it in our reference setup.
07-18-2020, 02:17 PM
(07-17-2020, 09:27 AM)D4vid Wrote: Hello to everyone. Exact same problem here. Everything worked great in OAP 7, 8 and 9. After 9.1 update everything works except AA. Just a black screen. No hardware change since OAP 7. Also using PI 3B+. I think OAP 9.1 lost compatibility with PI 3B+. Need do downdate to 9.0. (07-18-2020, 02:17 PM)Great Wrote:(07-17-2020, 09:27 AM)D4vid Wrote: Hello to everyone. https://bluewavestudio.io/community/show...6#pid10776
07-19-2020, 09:45 AM
(07-18-2020, 03:06 PM)BlueWave Wrote:(07-18-2020, 02:17 PM)Great Wrote:(07-17-2020, 09:27 AM)D4vid Wrote: Hello to everyone. Unfortunately this did not help. Adding "enable-shm = no" to does files didn't solve the problem. I attach the log file if that helps.
07-19-2020, 10:57 AM
(07-19-2020, 09:45 AM)Great Wrote:(07-18-2020, 03:06 PM)BlueWave Wrote:(07-18-2020, 02:17 PM)Great Wrote:(07-17-2020, 09:27 AM)D4vid Wrote: Hello to everyone. Looks like log file has not been attached. Try also change resample method in /home/pi/.config/pulse/daemon.conf to
If that helps, please consider upgrade of your Raspberry to model with higher amount of RAM. soxr-vhq resample method provides dramatically higher sound quality but requires more resources to work.
07-19-2020, 12:38 PM
(07-19-2020, 10:57 AM)BlueWave Wrote:(07-19-2020, 09:45 AM)Great Wrote:(07-18-2020, 03:06 PM)BlueWave Wrote:(07-18-2020, 02:17 PM)Great Wrote:(07-17-2020, 09:27 AM)D4vid Wrote: Hello to everyone. I really appreciate your help but that didn't solve it either. Here is the log file. |
|