1133159 - [FFOS2.0][Woodduck][WIFI]WIFI cannot search any AP after connect with a AP with MAC address binding

Status: RESOLVED DUPLICATE of bug 1146248

(Firefox OS Graveyard :: Wifi, defect, P2)

Description

[sync-1]

Created an attachment (id=1164217)
 mtklog
 
 PR Reporter:欧阳文丽
  contact:0752-2639312(61312)
 		
  DEFECT DESCRIPTION:
 >WIFI cannot search any AP after connect with a AP with MAC address binding
 
  REPRODUCING PROCEDURES:
 1.Connect with a AP with MAC address binding（Like"TMC_RD-PIC-HZ_2F
 "）.
 
 2.After connected failed, close wifi, wifi icon shows closed, but there has AP list -- KO1.
 
 3.Clear the recent app.
 
 4.Open wifi, cannot search any AP -- KO2.
 
 PS：log时间点为09:46
 
  EXPECTED BEHAVIOUR:
 >WIFI can work normally after connect with a AP with MAC address binding
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Attachment: mtklog

Comment 2

[sync-1]

Attachment: screenshot

Comment 3

[sync-1]

Attachment: screenshot

Comment 4

[Josh Cheng [:josh]]

Hi Norry,
qawanted for Woodduck 2.0M and Flame 2.0/2.1/2.2. Thanks!

Comment 5

[Norry.L.F(Leave from Mozilla)]

Hi Josh,

I can't repro this bug on woodduck 2.0M and Flame 2.0/2.1/2.2/3.0 latest build.
Repro rate: 0/10

Repro STR:
 1.Connect with a AP with MAC address binding.
 2.After connected failed, close wifi.
 3.Clear the recent app.
 4.Open settings > Wi-Fi.
Actual Result:
WIFI can search AP and work normally.

Flame 2.0
Build ID               20150215000240
Gaia Revision          ecb1bbc3b9c00f82df172427f65d6f67e34ed533
Gaia Date              2015-02-11 20:40:33
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/3051696eafcc
Gecko Version          32.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150215.040455
Firmware Date          Sun Feb 15 04:05:06 EST 2015
Bootloader             L1TC000118D0

Woodduck 2.0M:
Build ID               20150216050313
Gaia Revision          a1b5959728c8bc2a82354e197bb161922d419866
Gaia Date              2015-02-13 09:00:02
Gecko Revision         917050ccd94ab32278090e3d3fdf33e62096d449
Gecko Version          32.0
Device Name            jrdhz72_w_ff
Firmware(Release)      4.4.2
Firmware(Incremental)  1424034320
Firmware Date          Mon Feb 16 05:05:46 CST 2015

Flame 2.1 version:
Build ID               20150215001204
Gaia Revision          e8eba437af02820f74d122aec83b6001df6f89e3
Gaia Date              2015-02-13 05:26:11
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/9d04f9149ca4
Gecko Version          34.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150215.040742
Firmware Date          Sun Feb 15 04:07:53 EST 2015
Bootloader             L1TC000118D0

Flame 2.2 version:
Build ID               20150215002504
Gaia Revision          ea64caf6d4ab03fc4472eca9f41f20d651d55fa9
Gaia Date              2015-02-13 05:27:43
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/62c80c92b39e
Gecko Version          37.0a2
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150215.040852
Firmware Date          Sun Feb 15 04:09:03 EST 2015
Bootloader             L1TC000118D0

Flame 3.0 version:
Build ID               20150215010209
Gaia Revision          f0b93e0668ef9565bd6f050b15b4f794d59feb65
Gaia Date              2015-02-13 13:13:27
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/e0cb32a0b1aa
Gecko Version          38.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150215.043133
Firmware Date          Sun Feb 15 04:31:43 EST 2015
Bootloader             L1TC000118D0

Comment 6

[Norry.L.F(Leave from Mozilla)]

Attachment: Verify_woodduck.mp4

Comment 7

[Norry.L.F(Leave from Mozilla)]

And, In our build, there is no "Network notifications" function which is supported by the reporter's build from the screenshot.

Comment 8

[Josh Cheng [:josh]]

Hi Reporter,
We cannot repo this issue on our side. Can you try repo the issue with Mozilla Gaia/Gecko? Thanks!

Image link is: http://pan.baidu.com/s/1hqnDBtM
Access code: 9c9u
unzip password: erT14moz

Comment 9

[zhensen.su]

Hi Josh,

There are reproduce vedio in baidupan,the path and pass as follow:
path: http://pan.baidu.com/s/1bn94GrX pass: 7sl0

Thanks!

Comment 10

[Josh Cheng [:josh]]

Hi Norry,
Can you check again since partner can reproduce it per comment 9?

Comment 11

[Josh Cheng [:josh]]

Hi Vincent,
Could you please help to check the problem? Thanks!

Comment 12

[zhensen.su]

Hi all,

The vedio is using comment 8's version and 100% reproduced.

Thanks!

Comment 13

[zhensen.su]

Hi all,

The test AP is over the wall AP,other normal AP is not this issue,and when it connect this AP,it also not this issue.sometimes,it will come out turn on/off wifi continually.Please check it.

Thanks!

Comment 14

[Norry.L.F(Leave from Mozilla)]

Attachment: verified2.mp4

Hi Josh,
I can't repro this bug on 2.0m/2.0/2.1/2.1s/2.2/3.0 latest build,and on our side, device's response is not same as video of Comment 9, our device will show "connecting..."->"offline" status instead of  "Obtaining ip address.." status again and again.
I think this problem may relate to AP I use to test (NETGEAR WNDR3700v4).

see attachment:verified2.mp4

Comment 15

[zhensen.su]

Hi Norry,

Do you have over the wall AP?Please use over the wall AP for test,this AP have firewall.Other AP is normal.

Thanks!

Comment 16

[Vincent Chang[:vchang][changyihsin]]

Hi there, What is MAC address binding? Is it something like MAC filter? WiFi router(AP) is allowed to connect for mobile device with specific MAC address only?

Comment 17

[zhensen.su]

Hi  Vincent,

MAC address binding seems MAC filter,AP allowed connect with mobile device's MAC address in AP filter list.

Comment 18

[Vincent Chang[:vchang][changyihsin]]

Amy, can you help to check this?

Comment 19

[Amy Chung [:Amy]]

Hi Vincent,
Ok, I will confirm this issue.

Comment 20

[zhensen.su]

Hi Amy,

Has any progress?

Comment 21

[zhensen.su]

Hi Amy,

Could you analyze the log at first?Maybe it's special about this AP.

Comment 22

[Henry Chang [:hchang]]

Hi zhensen,

Are you able to 'adb shell' to the device when this issue occurs
to help us identify the root cause since we cannot reproduce from our side? 

$ adb shell
$ wpa_cli -i wlan0 -p /data/misc/wifi/sockets
$ scan
// Wait until 'CTRL-EVENT-SCAN-RESULTS' is received.
$ scan_results

Please paste the result after you sending 'scan_results'.
That would be helpful for this bug. Thanks!

Comment 23

[zhensen.su]

Attachment: log.txt

Hi Henry,

There are information you need in attachment.Please check it.

Thanks!

Comment 24

[Peipei Cheng (needinfo if you need my action)]

henry, could you please check the log in comment 23?

Comment 25

[Henry Chang [:hchang]]

(In reply to zhensen.su from comment #23)
> Created attachment 8575192 [details]
> log.txt
> 
> Hi Henry,
> 
> There are information you need in attachment.Please check it.
> 
> Thanks!

Just want to make sure you were obtaining this information
when you hit the issue. 

Thanks!

Comment 26

[zhensen.su]

Hi Henry,

I execute your support command,then reproduce the issue,copy the all print info.

Comment 27

[Henry Chang [:hchang]]

(In reply to zhensen.su from comment #26)
> Hi Henry,
> 
> I execute your support command,then reproduce the issue,copy the all print
> info.

You should reproduce the issue first. When the issue is happening, execute
the command then copy the printed info! Thanks!

Comment 28

[zhensen.su]

Attachment: log1.0.txt

Hi Henry,

The new info is in attachment,it contains two parts:
1.Reproduce issue before execute command,
2.Execute command before reproduce issue
It also prompt can't connect to wpa_supplicant.

Comment 29

[Henry Chang [:hchang]]

(In reply to zhensen.su from comment #28)
> Created attachment 8575748 [details]
> log1.0.txt
> 
> Hi Henry,
> 
> The new info is in attachment,it contains two parts:
> 1.Reproduce issue before execute command,
> 2.Execute command before reproduce issue
> It also prompt can't connect to wpa_supplicant.

Have you ever turned off wifi? It appears wpa_supplicant was terminated
due to either being turned off explicitly or a crash.

Comment 30

[zhensen.su]

Yep.We turn off wifi and clear the settings app,then turn on wifi,it's way reproduce the issue.

Comment 31

[Henry Chang [:hchang]]

(In reply to zhensen.su from comment #30)
> Yep.We turn off wifi and clear the settings app,then turn on wifi,it's way
> reproduce the issue.

Hi,

After you turn off wifi (step 4) and turn on wifi, execute the command and
print the info. In the last log you attached, there's no further info after
you turn on wifi.

Comment 32

[zhensen.su]

Hi Henry,

In this step,maybe can't open wifi completely,so prompt you can see info:
'Connection to wpa_supplicant lost - trying to reconnect
> scan_results
scan_results
Not connected to wpa_supplicant - command dropped.
'

Comment 33

[Henry Chang [:hchang]]

(In reply to zhensen.su from comment #32)
> Hi Henry,
> 
> In this step,maybe can't open wifi completely,so prompt you can see info:
> 'Connection to wpa_supplicant lost - trying to reconnect
> > scan_results
> scan_results
> Not connected to wpa_supplicant - command dropped.
> '

Did you mean:

"After step 4, no matter how long you wait, you'd never connect to wpa_supplicant?"

Comment 34

[zhensen.su]

Yep

Comment 35

[Wesly Huang (EPM)]

Hi Henry:

Like just mentioned, would you help check comment#34 then follow? Thank you.

Comment 36

[Amy Chung [:Amy]]

Dear Zhensen,
I found connection fail is the reason for delaying the wifi enable process.
Because it will connect to previous AP after wifi enable.
If the AP list can show list on setting panel, this function is normal.

Thanks!

Comment 37

[zhensen.su]

Hi Amy,

Why it connecting to previous AP before enable wifi?

Comment 38

[zhensen.su]

Hi amy,

Do you have time to handle today?

Comment 39

[Kai-Zhen Li [:seinlin][:kli]]

Attachment: [v2.0m] stopDhcp before dhcp_do_request

Zhensen, could you verify this patch?

Comment 40

[GitHub Autolander Bot]

Attachment: [gaia] Seinlin:bug-1133159 > mozilla-b2g:v2.0m

Comment 41

[Josh Cheng [:josh]]

Hi ZhenSen,
Can you confirm the patch fix the issue?

Comment 42

[Norry.L.F(Leave from Mozilla)]

Attachment: WPS.mp4

Hi Josh,

I tried the problem with/without patch, but both the two situations, the wps function is normal following this step:
1.Device connects to an ap.
2.Launch ap's WPS function.
3.Device launch WPS(Button) to connect other ap.
**Device will connect to an ap successful and I can surfing normally, if I skip step 2,Device will be always in "wps is in progress.." status without any error happening.

see attach：WPS.MP4

Comment 43

[Peipei Cheng (needinfo if you need my action)]

zhensen, 
any update on this? Since we could not reproduce this bug using mozilla build, could you please help verify the patch?

Comment 44

[zhensen.su]

Hi Peipei,

It seems ok now,but it lead other issue,i have submit new bug,you can close this bug now.

Thanks!