When turned on, Wi-Fi hotspot is not detected by devices around. Update on changes made under setting for Wi-Fi hotspot requires a restart to reflect. Steps to produce. 1. Under settings, select Internet Sharing then -> Hotspot settings 2. Change either the network name, password or security type then press OK. Expected outcome: name, password and/or security details change on the Internet Sharing settings as per the changes you made Actual outcome: Internet sharing settings remain the same and only get updated once you restart the phone Device/Software Details: LG Optimus Build Identifier: 20130131033112 Gaia: v1-train Git commit info: 2013-02-12 22:46:40
I can't confirm this. Changing settings worked for me without restarting the device. I'm using a ZTE Build: 20130219070200 Since you were using a much older build, I'm WFMing here. Please reopen if it's still happening with a new build.
Created attachment 730231 [details] logcat This occurs with the MOZRIL on yesterday's master build. Master build : 2013-03-26-07-02-04 "mozilla-central" revision="28b048ffb7a7" "integration/gaia-central" revision="44f6a17f24d4" "gecko.git"revision="a800f14ea7022a78966f7fe14a9b0d11c569b151" "gaia.git" revision="ace1eb32a313da1232bbdf9cff2581a4b036356d" In the logcat : Need at least 2 interfaces
We believe v1.0.1 is affected given the original reported date. Naoki, are you able to repro with the commercial RIL? If not, this wouldn't block any release.
Unable to reproduce on Unagi v1-train. Network name & security settings were correctly represented when scanning wifi from two other phones.
I cannot reproduce it in v1.0.1. qawanted to check this in v1.0.1. tef- in the meantime.
Commercial ril looks like it works fine: Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/dc653b5b2339 Gaia 6dbf0b68622aa80d079fee2af660ddc47f7cd7df BuildID 20130328070204 Version 18.0 Thanks for the explanation, Alex. I think my bug might be separate if that's the case and perhaps a regression. I had tested on master when I reopened this bug. How should we proceed with this bug?
This seems to have been fixed since the original report. Please reopen if it reoccurs.