1147729 - [wifi]Can't connect with AP via WPS if already connected with a AP

Status: RESOLVED INVALID

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

Description

[sync-1]

PR Reporter:欧阳文丽
  contact:0752-2639312(61312)		
 
  DEFECT DESCRIPTION:
 >Can't connect with AP via WPS if already connected with a AP
 
  REPRODUCING PROCEDURES:
 1.Connect with an AP1.
 
 2.Connect with AP2 via WPS while connected with AP1.
 
 3.Check the wifi screen, it displays connected with AP2
 
 4.But it is not in the AP2 connected users list, and it can't visit webpage via AP2. -- KO1
 
  EXPECTED BEHAVIOUR:
 >Can connect with AP via WPS if already connected with a AP
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[Josh Cheng [:josh]]

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

Comment 2

[Josh Cheng [:josh]]

Hi Kai-Zhen,
Could you please help to check the problem? Thanks!

Comment 3

[zhensen.su]

Attachment: main_log

Hi Kai-zhen,

There are log in attachment.It's unstable issue,but it can be easy to reproduced.

Comment 4

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

I follow step 1~4 in comment 0, I can't reproduce the error.

Can you do more test and provide more information?

1. Connect to AP2 make sure connection on AP2 does work properly.

2. Verify as steps in comment 0, but revert AP1 and AP2.

3. After connected to each AP, check the connection status and wifi setting. 
   such as:
     adb shell netcfg
     adb shell cat /data/misc/wifi/wpa_supplicant.conf
   You could also do more checks.

Comment 5

[Shine(Leave from Mozilla)]

Attachment: VIDEO1214_Compress.MP4

Hi Josh,
I tried the problem on latest build of Woodduck 2.0 and Flame 2.0/2.1/2.2. The wps function is working normally. The STR is as follow:
1.Connect with an AP1.
2.Device launch WPS(Button/PIN) to connect AP2.
Actual result: Device will connect to WPS AP2 successfully and it is in the connected users list; Launch Browser on device, I can surf normally.
See attachment: VIDEO1214_Compress.MP4
Rate: 0/5 (Woodduck 2.0 and Flame 2.0/2.1/2.2)
Device:
Woodduck 2.0:
Build ID               20150327050314
Gaia Revision          7b6a61871b2dfefe9ec9868da99de5b85e0076e2
Gaia Date              2015-03-19 02:12:16
Gecko Revision         80ba91d2044bee5179425e9b515ad67322d9410d
Gecko Version          32.0
Device Name            jrdhz72_w_ff
Firmware(Release)      4.4.2
Firmware(Incremental)  1427403898
Firmware Date          Fri Mar 27 05:05:17 CST 2015

Flame 2.0:
Build ID               20150326160207
Gaia Revision          896803174633fc6acd3fd105f81c349b8e9b9633
Gaia Date              2015-03-10 06:32:26
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/adb9d7679526
Gecko Version          32.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150326.192953
Firmware Date          Thu Mar 26 19:30:02 EDT 2015
Bootloader             L1TC000118D0

Flame 2.1:
Build ID               20150326001202
Gaia Revision          6f39e4e876152de1dcdcc0e7656197f22f105e4b
Gaia Date              2015-03-25 11:16:16
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/e00ae73d67a2
Gecko Version          34.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150326.035122
Firmware Date          Thu Mar 26 03:51:33 EDT 2015
Bootloader             L1TC000118D0

Flame 2.2:
Build ID               20150326002504
Gaia Revision          e59ac067a1d22b7a72cbebc892ec652723f2a557
Gaia Date              2015-03-26 00:02:53
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/04b4b9d1faae
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150326.042521
Firmware Date          Thu Mar 26 04:25:30 EDT 2015
Bootloader             L1TC000118D0

Comment 6

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

(In reply to Kai-Zhen Li [:kli][:seinlin] from comment #4)
> I follow step 1~4 in comment 0, I can't reproduce the error.
> 
> Can you do more test and provide more information?
> 
> 1. Connect to AP2 make sure connection on AP2 does work properly.
> 
> 2. Verify as steps in comment 0, but revert AP1 and AP2.
> 
> 3. After connected to each AP, check the connection status and wifi setting. 
>    such as:
>      adb shell netcfg
>      adb shell cat /data/misc/wifi/wpa_supplicant.conf
>    You could also do more checks.

zhensen,
since we cannot reproduce this, could you please help check comment 4?

Comment 7

[Josh Cheng [:josh]]

Update: Issue is caused by partner own code. They will fix it by themselves. 
Close this as invalid until further issue.

Comment 8

[zhensen.su]

Hi Josh,

Sorry for update late.This issue is fixed by rollback some code,but according to comment#5 test result,i think you should test more,it's unstable,because we use you build '20150323054814-user.zip' can't connect sometimes,then i saw your code doesn't merge the patch 'https://bugzilla.mozilla.org/show_bug.cgi?id=1094665#c22'.
Besides,you can try Join hidden network(Add AP doesn't in area,you can random input ssid and pwd,it can be easier to reproduce) on Manage networks before connect to WPS.
@Shine Could you try it again?Do more test on Woodduck 2.0.

Thanks!

Comment 9

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

Hi Shine, 

According to comment 8, could you try it again using build '20150323054814-user.zip' and latest build? Thanks.

Comment 10

[Shine(Leave from Mozilla)]

Attachment: VIDEO1307_Compress.MP4

Hi Zhensen,
I'm sorry, I really cannot reproduce this bug by the STR you mentioned in Comment 8. I have tried the STR more than 15 rounds on build '20150323054814-user.zip' and build '20150408050314-eng.zip'. The STR is as follow:
1. Flash build '20150323054814-user.zip'/build '20150408050314-eng.zip'.
2. Launch Settings app and enter "Wi-Fi" screen.
3. Tap "Manage networks" -> tap "Join hidden network".
4. Random input ssid and pwd ->tap "OK".
5. Device launch WPS(Button/PIN) to connect AP quickly.
** The AP can be connected and it can visit webpage via AP successfully.
See attachment: VIDEO1307_Compress.MP4

Comment 11

[zhensen.su]

Hi Shine,

Sorry for my description unclear,PBC is ok,PIN sometimes no ok,so you only test with PIN,when it connect suc,you can forget hidden network,then retry STR 3-5.I can see use PBC in your video.

Thanks!

Comment 12

[Shine(Leave from Mozilla)]

(In reply to zhensen.su from comment #11)
> Hi Shine,
> 
> Sorry for my description unclear,PBC is ok,PIN sometimes no ok,so you only
> test with PIN,when it connect suc,you can forget hidden network,then retry
> STR 3-5.I can see use PBC in your video.

Hi Zhensen,
By the STR you mentioned in comment 11, I've tried 20 rounds altogether on two APs. Device succeeds to connect and access the Internet for only 4 times. And it fails to connect WPS the other 16 times, with device showing “WPS is in progress...” all the time, and AP server prompting “connection timeout“.
See attachment: VIDEO1331_Compress.MP4 & AP Server.PNG & logcat_0642.zip
Device:
Woodduck 2.0
Build ID               20150413050314
Gaia Revision          37e63db3af0f76fe9c71a4ce23aef9771491124f
Gaia Date              2015-04-12 07:28:35
Gecko Revision         55d4aed15c552fff5e1faca44c63a8abc1f65241
Gecko Version          32.0
Device Name            jrdhz72_w_ff
Firmware(Release)      4.4.2
Firmware(Incremental)  1428872689
Firmware Date          Mon Apr 13 05:05:08 CST 2015

Comment 13

[Shine(Leave from Mozilla)]

Attachment: VIDEO1331_Compress.MP4

Comment 14

[Shine(Leave from Mozilla)]

Attachment: AP Server.PNG

Comment 15

[Shine(Leave from Mozilla)]

Attachment: logcat_0642.zip

Comment 16

[zhensen.su]

Hi Josh,

From shine's test,it also has issue on your build,so i suggest merge patch 'https://bugzilla.mozilla.org/show_bug.cgi?id=1094665#c22' on your code,then do more test.

Thanks!

Comment 17

[Josh Cheng [:josh]]

Hi Kai-Zhen,
Could you please help to check the comment 12? Thanks!

Comment 18

[zhensen.su]

Hi Kai-zhen,

Whether you can merge this patch?Do more test?

Comment 19

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

There is a working solution, but it is more likely a workaround as the root cause is not found. I think the patch shouldn't be landed before the root cause is found.