On Nov 10, 2017, at 1:39 PM, Dirk Hohndel wrote:
>
> On Nov 10, 2017, at 1:01 PM, Jan Mulder wrote:
>
>> On 10-11-17 21:48, Dirk Hohndel wrote:
>>
>>> We need to figure out why we are not talking to BT. Simon, any idea?
>>
>> Just for completeness.
On Nov 10, 2017, at 1:39 PM, Dirk Hohndel wrote:
>
> On Nov 10, 2017, at 1:01 PM, Jan Mulder wrote:
>
>> On 10-11-17 21:48, Dirk Hohndel wrote:
>>
>>> We need to figure out why we are not talking to BT. Simon, any idea?
>>
>> Just for completeness.
On Nov 10, 2017, at 1:01 PM, Jan Mulder wrote:
> On 10-11-17 21:48, Dirk Hohndel wrote:
>
>> We need to figure out why we are not talking to BT. Simon, any idea?
>
> Just for completeness. Just tested a 3 day old AppImage on Arch Linux native,
> so no VM or things.
>
>
I just tried it again, after downloading the latest, latest Continuous
AppImage. Still doesn’t work.
I think I described the behavior slightly incorrectly before. It displays a red
bar at the bottom of the main window, that says “Failed to connect to
C2:02:D5:CD:61:A8: ‘Cannot find local
On 10-11-17 21:48, Dirk Hohndel wrote:
We need to figure out why we are not talking to BT. Simon, any idea?
Just for completeness. Just tested a 3 day old AppImage on Arch Linux
native, so no VM or things.
OSTC3 downloads just fine over BT and BLE.
--jan
Adding the mailing list back in (with Stuart’s permission) and changing the
subject line to be more appropriate…
On Nov 10, 2017, at 11:18 AM, Stuart Vernon wrote:
> I am now running the latest AppImage.
Which of course is literally constantly changing, so it’s always