[mako] Cannot connect to hidden wifi network (touch|android)

[Seth Forshee]

There's no UI for this right now that I can find, but if I try to connect to a hidden wireless network on mako by manually creating the wpa_supplicant.conf file and launching wpa_supplicant by hand, authentication with the network fails. The same operation works fine on maguro, so odds are this is a driver bug. The network in question has WPA2-PSK security.

[Tony Espy (awe)]

@Seth

Didn't you also mention that this fails when running stock Android as well?

[Tony Espy (awe)]

@Seth

Two more questions...

1. If you change the security to WEP or none, does connecting work?

2. What frequency ( 2.4 vs. 5 )?

[Seth Forshee (sforshee)]

It does also fail on stock android. Didn't try different security, although maguro worked fine with WPA2-PSK. This was with a 2.4GHz only AP, but I didn't note exactly what channel it was on at the time.

[Antti Kaijanmäki (kaijanmaki)]

Go to System Settings -> Wi-Fi -> Other network.

There you can specify the name and security for the hidden network. Please verify that you can connect.

[Seth Forshee (sforshee)]

I just reflashed my mako device using ubuntu-device-flash and cannot find the "Other network" option. I see there are updates, but none of them look related (and they won't install anyway for some reason). Plus there seems to be some timeout or something on the wifi password dialog that disregards user input, as I'd get almost done entering the passphrase for a non-hidden network and it would just disappear (I use long, complex passphrases which take a while on mobile keyboards). On another network it was failing to connect, so I wanted to check or reenter the passphrase, but I can't find any way to do that, nor any way to forget the network. So in all I am _not_ having a good experience with the wifi settings UI.

If I need to do something specific in order to test this, please let me know.

[Seth Forshee (sforshee)]

All right, it turns out I didn't run ubuntu-device-flash the right way and ended up with an old image. I tested with devel-proposed, and I'd say that it's mostly fixed.

The UI is there, and I can use it to connect to a hidden network, but I did have a few of problems. First, when the keyboard was present on the screen to setup up the network it resulted in the test field for entering the passphrase getting covered by buttons, making it impossible to select the field until I dismissed the keyboard. Second, once connected I didn't have the little "wifi connected" icon in the top bar that I get when connected to a non-hidden network, just a blank space where it should have been. Finally, after I connected to the hidden network the list of available networks showed that network twice, once with a check mark and high signal indication and again unchecked with the graphic showing no signal. When I tapped the network with no signal it just disappeared.

Oh, one more thing. The hidden network always appears at the bottom of the list of available network, regardless of relative signal strength, and even when I'm connected to that network.

[Antti Kaijanmäki (kaijanmaki)]

OK, but you _can connect_ to the hidden network, so this bug is Fix Released.

the keyboard issue: bug #1333135

Could you file a new bug about the indicator visual problem and attach the following information to it:

=== with phablet-shell from the device ===
$ dbus-send --session --print-reply --dest=com.canonical.indicator.network /com/canonical/indicator/network/phone org.gtk.Menus.Start array:uint32:1,0 > menumodel.txt

$ nmcli d wifi list > nmcli_d_wifi_list.txt

$ dbus-send --print-reply --dest=com.canonical.indicator.network /com/canonical/indicator/network org.gtk.Actions.DescribeAll > actiongroup.txt
======

=== on the host computer with the device attached via USB ===
1. open the network indicator and take a screenshot of it's wrong contents:

$ phablet-screenshot indicator.png
======

Download the files from the device with adb:
    $ adb pull /home/phablet/<filename>

[Seth Forshee (sforshee)]

Okay - bug #1354560.

Just one note though - bug #1333135 talks specifically about landscape orientation, but I was using the phone in portrait orientation.