by buckaroo » 02 Feb 2019, 04:41
by Mecworks » 22 Feb 2019, 22:00
by janui » 23 Feb 2019, 21:30
It is unchanged since 0.4, but really needs the whole network management part of Rune needs a complete rewrite. I wont be doing that in the near future, so I will modify the UI text to reflect the current situation. Thanks for the suggestion.Mecworks wrote:So, the UI needs to reflect current settings better. It's definitely broken.
The wifi profile is saved, and it will work after a reboot. Unfortunately the connect button will only work after Rune has been booted with its Access Point disabled. In the current release Access Point is enabled by default. This has already been changed, but will only be effective from the next release.buckaroo wrote:I can't save a wifi profile, nor will it connect to my router via wifi.
by englishtim » 24 Feb 2019, 13:02
The wifi profile is saved, and it will work after a reboot. Unfortunately the connect button will only work after Rune has been booted with its Access Point disabled. In the current release Access Point is enabled by default. This has already been changed, but will only be effective from the next release.
by janui » 25 Feb 2019, 12:27
Thanks for reporting this. It was not intended to work like this, a bug crept in with the latest changes. An upgrade to the latest patch level using git pull will fix it. See the first post in this thread for upgrade instructions.englishtim wrote:...Enabling the Access Point by default has caused problems for me, as I now can't switch it off - the AP stays active irrespective of my attempts to deactivate it...
by englishtim » 25 Feb 2019, 15:25
support RuneAudio