Fix for pairing issues

[donagrejja]

Managed to find what was causing the pairing issues. It was the simple-agent script for pairing that was the culprit.

Replaced it with a working script. also moved enabling the bluetooth interface to the main.conf bluetooth daemon instead of the bt-setup.sh script.

Try it out if you'd like. Works for me at least.

[morrolinux]

I think it's mostly alright, thank you. powering up the BT device from daemon's config file was a good idea which I didn't happen to think about, but udev reload is needed to make sure BT events are always detected. Tomorrow I'll test the bluetooth-agent script you provided (it is non-interactive, right?) and test the whole thing on my Pi as well.

[donagrejja]

The scripts is non-interactive yes =)

I'm running this version already without the "systemctl force-reload udev systemd-udevd-control.socket systemd-udevd-kernel.socket".

Anyway =) you go ahead and do your tests but i suggest you also test without the force reload stuff. it does work for me.

Noticed you said "from time to time" in the commit. But afaik the bt-setup is only being run at boot so it's currently not being run "from time to time" either =) or did i miss something ?

[morrolinux]

Exactly. It's not really necessary, except for when (a random day) you could see that nothing happens when you connect via bluetooth. I've already been through this. It's not a pairing issue, googling around I discovered udev sometimes could "hang" and overlook (some?) events. Hence, the issue. So yea. It might work perfectly without, but it's proven to be a potential issue "from time to time", that's why I need it there anyway

2018-01-24 0:38 GMT+01:00 Stefan Andersson notifications@github.com:

The scripts is non-interactive yes =)

I'm running this version already without the "systemctl force-reload udev systemd-udevd-control.socket systemd-udevd-kernel.socket".

Anyway =) you go ahead and do your tests but i suggest you also test without the force reload stuff. it does work for me.

Noticed you said "from time to time" in the commit. But afaik the bt-setup is only being run at boot so it's currently not being run "from time to time" either =) or did i miss something ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/morrolinux/mpradio/pull/19#issuecomment-359969375, or mute the thread https://github.com/notifications/unsubscribe-auth/ATWqbrCLpHnBGoBqT29SFFJZh5c_g-Wkks5tNm1fgaJpZM4RqS4d .

--

per il supporto tecnico rivolgersi a

Moreno Razzoli__ Avvertenze ai sensi del D.Lgs.196 del 30/06/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o files allegati, sono da considerarsi strettamente riservati. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nello stesso. Costituisce violazione ai principi dettati dal D.Lgs. 196/2003: trattenere il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo o utilizzarlo per finalità diverse. Qualora riceveste questo messaggio senza esserne il destinatario Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Grazie.

[donagrejja]

Ah ok. So you mean from time to time upon boot.

Gotcha =)

[morrolinux]

Tested and working! Merging now, thanks for contributing to the project

[mich-de]

Ciao Morro tutto funzionante, testato con raspbian lite e raspberry Pi zero w. Wifi disabilitata. Eng. Hi Morro, working properly 👍 , tested on raspian lite and raspberry pi zero w. Wifi disabled.