Closed Bug 935487 Opened 11 years ago Closed 6 years ago

[first run] connecting to hidden Wi-Fi network fails

Categories

(Firefox OS Graveyard :: Wifi, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: aryx, Unassigned)

References

Details

Boot2Gecko 1.2.0.0-prerelease 20131104224010 on Keon, update channel 'default'

After factory reset and also while just running the First Run app, I don't succeed to connect to a hidden Wi-Fi network (haven't tested with SSID broadcasting networks).

Steps to reproduce:
1. Launch First Run app from Settings > Device Information > More Information > First Run app.
2. When you get to the Wi-Fi screen, choose to connect to a hidden network, enter the SSID and the password (it uses WPA-PSK here).

Actual result:
Connecting never succeeds.

Expect result:
Connecting succeeds like when performed from the Settings app.
The content of /data/misc/wifi/wpa_supplicant.conf differs when adding a hidden network from the First Run app compared to the Settings app:


First Run:

ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
update_config=1
wfd_session_mgmt_ctrl_port=554
wfd_device_max_throughput=10

network={
	ssid="MySSID"
	psk="MyPassword"
	key_mgmt=WPA-PSK
	priority=1
}


Settings:

ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
update_config=1
wfd_session_mgmt_ctrl_port=554
wfd_device_max_throughput=10

network={
	ssid="MySSID"
	scan_ssid=1
	psk="MyPassword"
	key_mgmt=WPA-PSK
}
blocking-b2g: --- → 1.3?
Does this reproduce on 1.1?
Keywords: qawanted
This doesn't reproduce on 1.1 because the feature landed for 1.2, see bug 824366.
blocking-b2g: 1.3? → 1.3+
Keywords: qawantedregression
Fernando,

Please check if you can take this issue.
Flags: needinfo?(fernando.campo)
Keywords: regressionqawanted
Keywords: qawantedregression
Sorry, right now I'm unable to take it :(

Maybe in a few days, so it depends on the urgency
Flags: needinfo?(fernando.campo)
QA Contact: mvaughan
This issue reproduces on the first 1.2 build from 06/21/13. Therefore this is not a regression since this build is when the feature landed.

Environmental Variables:
Device: Buri v1.2 MOZ RIL
BuildID: 20130621031231
Gaia: e2f19420fa6a26c4287588701efaec09a750dba1
Gecko: 7ba8c86f1a56
Version: 24.0a1
Firmware Version: V1.2-device.cfg
Not a regression - per comment #6 this is also not working in 1.2. We didn't block that release on it so we should not block this release on it.
blocking-b2g: 1.3+ → 1.3?
(In reply to Dietrich Ayala (:dietrich) from comment #7)
> Not a regression - per comment #6 this is also not working in 1.2. We didn't
> block that release on it so we should not block this release on it.

Sounds good to me. Moving to blocking-
blocking-b2g: 1.3? → -
+1 (as I was about to file the same bug), indeed experiencing this ever since 1.2 and up.

It might be related to the fact that there is an OK button in the top right when doing this from within Settings, but a Connect button during FTU (in master - I believe this is a little different in previous versions), so something might go wrong with accepting or sending the password. Unfortunately I wasn’t able to verbose logging from an access point in order to see what (or rather if a) password string is sent.
blocking-b2g: - → backlog
Whiteboard: [systemsfe][priority]
Whiteboard: [systemsfe][priority] → [systemsfe], [priority]
This still reproduces on Master (2.0.0-pre) builds on various devices.
Component: Gaia::First Time Experience → Wifi
Whiteboard: [systemsfe], [priority]
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.