RuneAudio 0.4-beta for Raspberry Pi2/3

[rlsten]

Hi,

had the same problem after creating a wifi-profile. I had to disable the access point manually in settings to make my wifi-profile work.

This should not be necessary, because it is designed different.
The Access Point should only be started if no wifi connection is available.
What can happen is, that your wifi connection takes to long to get an IP.

The AP is enabled by default to get easy access to Rune.
If not needed it is a good idea to disable the AP anyway.

Frank

I am very excited about the AP functionality, but I had similar problems with it.

But doesn't disabling the Access Point create a kind of chicken and egg problem and defeat the purpose of the AP functionality. If I set up a mobile Rune/DAC device with my home network and then disable the AP, what do I do if I take the device away from my home network? Do I have to reenable it every time I leave home, and then disable it when I come back?

I thought the way the AP function was supposed to work was that if Rune detected a working WiFi profile, it wouldn't go into AP mode, but if there was no working WiFi profile, then Rune would create an access point.

Am I missing something?

Rod

[neanderthaler]

@Frank, mo86:
Well, what is and what should be...
The created and "stored" Wifi-profiles get lost, with next reboot they're just vanished.
It is also not possible to connect to a fresh created profile.
So I gave mo86's method of disabling AP a try.
Now I have no wireless access to the Pi at all, what a pity.
I doubt it will become better when using cable.
Any idea how to store a WiFi-profile which will work and survive reboot?

[mo86]

@neanderthaler: you can try connect via cable, create a new Wi-Fi-profile and try again. That worked for me, also with rebooting

[hondagx35]

The screensaver works a little bit funny. He comes for only half a second, then switches back to the normal playback screen. Can anyone confirm this?

Chris

I had this once or twice with my 7" TFT, but now it works.
This seems to be an issue with the touch driver.
I will check this again.

Frank

[hondagx35]

Hi Rod,

I thought the way the AP function was supposed to work was that if Rune detected a working WiFi profile, it wouldn't go into AP mode, but if there was no working WiFi profile, then Rune would create an access point.

Am I missing something?

No, you did not miss anything.
On my systems it works exactly this way.

Frank

[hondagx35]

Hi neanderthaler,

Any idea how to store a WiFi-profile which will work and survive reboot?

No, because on all my devices (3 RP3 and 2 RP2) it works without issues.

I'll try to make a video from the setup process.

Frank

[rlsten]

Hi neanderthaler,

Any idea how to store a WiFi-profile which will work and survive reboot?

No, because on all my devices (3 RP3 and 2 RP2) it works without issues.

I'll try to make a video from the setup process.

Frank

That would be great, Frank. I hope you will do the setup video using just WiFi, no wired connections at all.

Thanks,
Rod

[neanderthaler]

Yeah!!! Got it!!!

Nothing to do with cabling, switching AP on and off or something like this. Also not a matter of PEBKAC.
Problem was: Firefox.
I use Firefox 52.0 on LinuxMint, some (few) settings in Rune just don't work with it.
Sounds funny? Yes. But I had similar problems with setting up my router some years ago.

Now I tried chromium browser, and voila: Everything works out-of-the-box, including the ingenious AP functionality.

Thanks a lot!

Ich freu mich wie Schnitzel!

[n8dgr84]

If I disable WIFI AP mode, does that turn the WIFI adapter off?
I'm trying to use eth only (and disable all wifi and bt) on the Pi3.

[hondagx35]

Hi n8dgr84,

If I disable WIFI AP mode, does that turn the WIFI adapter off?

No.

See here

Frank