@Del-Boy69
OK I managed a test session last night as promised (late - after the Grandkids had gone to bed, so my brain wasn’t at its sharpest).
I managed to find the bit in my notes re first Bluetooth Tests, which was from last November - so not a year ago, though it certainly feels like it! The problem I had then
wasn’t getting the Rosetta to find the BT device - it managed that OK - it was getting Rosetta to connect to the device after finding it.
From Test Notes Mid November 2018
Currently displaying traffic on SD via GDL90, with audio via a small BT speaker, though there was a slight ‘glitch’ getting the speaker to connect first time - possibly due to the speaker rather than PilotAware.
I told the speaker to ‘forget it’s previous connection’, then ran the BT ‘Scan’ on Rosetta Config and the speaker appeared on the Scan list almost right away - with its name: Mifa_A1.
When I then pressed ‘Connect’ (after waiting ‘til the Scan had finished) PAW went through its normal ‘Busy’ stage but no connection appeared - verified by no audio when I tried the ‘Test’ button, so I went back to the BT screen and pressed the correct ‘Connect’ button again. This time after the ‘Busy’ stage the button went Green and changed to ‘Connected’ - nice touch! - and all is now well.
This was just an initial glitch with that one particular speaker and I had no further problems during testing with that and a variety of other speakers and (domestic Hi-Fi type) headsets (My aviation headsets don’t do BT).
Unfortunately on last night’s session with a completely fresh install of 20190621 on a standard ‘Rosetta’, I failed to get the same Mifa_A1 speaker to appear on the Rosetta ‘Scan List’ at all - probably because the speaker kept automatically connecting to my phone each time I switched it on and my attempts to get it to forget the phone pairing and go back into ‘pairing mode’ didn’t work. I don’t have the speaker manual with me and it isn’t available on the Mifa website
, so this morning I Googled ‘Pairing Mifa A1’ and found I was pressing the wrong keys to get it to forget its previous pairing.
All well and good, reset the speaker and re-ran the Scan - speaker appeared in the scan list after a few minutes. After waiting for the Scan to finish, I pressed the relevant ‘Connect’ button and after a short while the speaker now shows as ‘connected’ (No ‘Green Button’ though Lee, so I guess you have changed something since the version I ran this on last - I didn’t get a chance to test BT in the run-up to this release, but more importantly
I’m getting no audio when I press the Audio ‘Test’ button in ’Config’ and there are no aircraft about to trigger any alerts. I need to do some further testing to see what is going on, but the Grandkids are now up and we are supposed to be going over to Mull today. I will get back to you.
Regards
Peter