Closed Bug 987038 Opened 6 years ago Closed 6 years ago

[Tarako][V1.3T] All WIFI signals are full

Categories

(Firefox OS Graveyard :: Vendcom, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(blocking-b2g:1.3T+, b2g-v1.3 unaffected, b2g-v1.3T verified, b2g-v1.4 unaffected)

VERIFIED FIXED
blocking-b2g 1.3T+
Tracking Status
b2g-v1.3 --- unaffected
b2g-v1.3T --- verified
b2g-v1.4 --- unaffected

People

(Reporter: whsu, Assigned: xinhe.yan)

Details

(Whiteboard: 1.3tarakorun1, [tarako_only] [POVB])

Attachments

(1 file)

Attached image WIFI_Signal.jpg
* Description:
  The WIFI signal strength is always displayed the "Very Good" status(full signal icon) no matter the signal is good or not.
  Attach the screenshot. (WIFI_Signal.jpg)

* Reproduction steps:
  1. Go to settings page
  2. Tap "Wi-Fi" item
  3. Tap "Search again" button
  4. Repeat step 3 many times.

* Expected result:
  - WIFI page displays the correct WIFI signal

* Actual result:
  - The WIFI signal strength is always displayed the "Very Good" status(full signal icon)

* Reproduction build:( V1.3T )
 - Gaia      a4b3223fb2c2109cdde86f1d5595aa90f05e9a39
 - Gecko     947861d9d32a313d3a0f5f480ea458c9e70baf26
 - BuildID   20140319180709
 - Version   28.0
Whiteboard: 1.3tarakorun1
blocking-b2g: --- → 1.3T?
Probably should include steps like move away from the wifi hotspot. 

This doesn't occur on 1.3, 1.4 buri:
Gaia      f7742fb4929cc57c9f72955ce5cebb8279745ac0
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/e42b778a010f
BuildID   20140324004001
Version   28.0
ro.build.version.incremental=324
ro.build.date=Thu Dec 19 14:04:55 CST 2013
Buri
Hi Sam, is it possible for you to check this bug first? Since our design is working fine on other platform.
Flags: needinfo?(sam.hua)
ok
add xinhe
Flags: needinfo?(sam.hua)
Ken, can you test on hamachi? This bug can be found in hamachi.
In 'Avaiable networks', connected AP signal is almost zero. 
But in status bar, the signal is 3 or full.

Very easy to reproduce.
(In reply to Xinhe Yan from comment #4)
> Ken, can you test on hamachi? This bug can be found in hamachi.
> In 'Avaiable networks', connected AP signal is almost zero. 
> But in status bar, the signal is 3 or full.
> 
> Very easy to reproduce.
Hi Vincent, did you get the same problem before?
Flags: needinfo?(vchang)
triage: incorrect wifi signal display, 1.3T+
may be tarako only base on our QA testing, Vincent can you clarify this? Thanks
Assignee: nobody → vchang
blocking-b2g: 1.3T? → 1.3T+
Whiteboard: 1.3tarakorun1 → 1.3tarakorun1, [tarako_only]
(In reply to Xinhe Yan from comment #4)
> Ken, can you test on hamachi? This bug can be found in hamachi.
> In 'Avaiable networks', connected AP signal is almost zero. 
> But in status bar, the signal is 3 or full.
> 
> Very easy to reproduce.

Hi Xinhe, I can't reproduce this using hamachi and unagi.
Flags: needinfo?(vchang)
The signal levels are different between hamachi and tarako. When signal level from scan results is greater than -50, it is treated as signal full.  
http://dxr.mozilla.org/mozilla-central/source/dom/wifi/WifiWorker.js?from=wifiworker.js%20&case=true#1419

I think this should be fixed by parnter. 

Signal level for tarako :
-----------------------------------------------------------------------------------------
> bssid / frequency / signal level / flags / ssid
3c:94:d5:7c:11:82	2462	-42	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:7c:11:80	2462	-38	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:7c:11:88	2462	-42	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
bc:ae:c5:c4:22:44	2462	-39	[WPA2-PSK-CCMP][WPS][ESS]	MozKFC
3c:94:d5:7b:b8:02	2462	-39	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:7b:b8:08	2462	-42	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
3c:94:d5:7b:b8:00	2462	-41	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:7b:b8:06	2462	-40	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:76:17:40	2437	-26	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:76:17:42	2437	-25	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:76:17:46	2437	-25	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:76:17:48	2437	-26	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
4c:e6:76:a3:07:e8	2412	-34	[WPS][ESS]	tttttttttt
3c:94:d5:7c:11:86	2462	-42	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:7b:87:46	2412	-47	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:7b:87:48	2412	-45	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
3c:94:d5:7b:87:40	2412	-48	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:7b:87:42	2412	-51	[WPA2-EAP-CCMP][ESS]	Mozilla
98:0c:82:4c:98:ef	2437	-48	[ESS]	1qqqqqqqqqqqqq
3c:94:d5:78:77:06	2462	-50	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:78:77:08	2462	-50	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile


Scan results for hamachi:
--------------------------------------------------------------------------------------------
bssid / frequency / signal level / flags / ssid
4c:e6:76:a3:07:e8	2412	-43	[WPS][ESS]	tttttttttt
3c:94:d5:76:17:40	2437	-42	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:76:17:42	2437	-51	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:76:17:48	2437	-51	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
3c:94:d5:7b:b8:00	2462	-52	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:76:17:46	2437	-52	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:7b:b8:06	2462	-53	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:7c:11:84	2462	-55	[WPA2-EAP-CCMP][ESS]	
3c:94:d5:7b:b8:08	2462	-55	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
3c:94:d5:7c:11:86	2462	-56	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:7c:11:80	2462	-56	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:7c:11:88	2462	-58	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
3c:94:d5:7b:b8:02	2462	-58	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:7c:11:82	2462	-58	[WPA2-EAP-CCMP][ESS]	Mozilla
bc:ae:c5:c4:22:44	2462	-58	[WPA2-PSK-CCMP][WPS][ESS]	MozKFC
3c:94:d5:7b:fb:06	2437	-61	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
08:81:f4:58:ca:80	2412	-62	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:7b:fb:02	2437	-62	[WPA2-EAP-CCMP][ESS]	Mozilla
08:81:f4:58:ca:88	2412	-63	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
3c:94:d5:7b:87:48	2412	-63	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
00:24:01:a1:8e:e5	2437	-63	[WPA-PSK-TKIP+CCMP][WPA2-PSK-TKIP+CCMP][WPS][ESS]	WhatAAPP
3c:94:d5:7b:fb:00	2437	-63	[WPA2-EAP-CCMP][ESS]	Mozilla-G
08:81:f4:58:ca:86	2412	-63	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:7b:87:40	2412	-64	[WPA2-EAP-CCMP][ESS]	Mozilla-G
08:81:f4:58:ca:82	2412	-65	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:7b:87:46	2412	-66	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:7b:87:42	2412	-66	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:7b:87:44	2412	-66	[WPA2-EAP-CCMP][ESS]	
3c:94:d5:78:77:06	2462	-71	[WPA2-PSK-CCMP][ESS]	Mozilla Guest
3c:94:d5:78:77:00	2462	-71	[WPA2-EAP-CCMP][ESS]	Mozilla-G
3c:94:d5:78:77:02	2462	-71	[WPA2-EAP-CCMP][ESS]	Mozilla
3c:94:d5:78:77:08	2462	-72	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
d8:c7:c8:eb:17:12	2462	-84	[WPA2-PSK-CCMP][ESS]	Mozilla Mobile
d8:c7:c8:eb:17:10	2462	-85	[WPA2-EAP-CCMP][ESS]	Mozilla-G
98:0c:82:4c:98:ef	2437	-41	[ESS]	1qqqqqqqqqqqqq
d8:c7:c8:eb:17:11	2462	-82	[ESS]	Mozilla Guest
00:19:be:1e:d4:d8	2417	-86	[ESS]	A8_SafeMode_0019BE1ED4D8
Whiteboard: 1.3tarakorun1, [tarako_only] → 1.3tarakorun1, [tarako_only]
ni? Xinhe
Flags: needinfo?(xinhe.yan)
(In reply to Vincent Chang[:vchang] from comment #8)
> The signal levels are different between hamachi and tarako. When signal
> level from scan results is greater than -50, it is treated as signal full.  
> http://dxr.mozilla.org/mozilla-central/source/dom/wifi/WifiWorker.
> js?from=wifiworker.js%20&case=true#1419
> 
> I think this should be fixed by parnter. 
> 
Vincent, Thanks. I will contact with our engineer.
Flags: needinfo?(xinhe.yan)
Whiteboard: 1.3tarakorun1, [tarako_only] → 1.3tarakorun1, [tarako_only] [
Hi! James,

I think this is wifi driver or even board issue.
Could Sprd take this? Thanks

--
Keven
Flags: needinfo?(james.zhang)
Whiteboard: 1.3tarakorun1, [tarako_only] [ → 1.3tarakorun1, [tarako_only] [POVB]
I will take it.
Hi! Xinhe Yan,

Reassign to you. Thanks

--
Keven
Assignee: vchang → xinhe.yan
It is owned by partner.
Component: Wifi → Vendcom
(In reply to Keven Kuo [:kkuo] from comment #11)
> Hi! James,
> 
> I think this is wifi driver or even board issue.
> Could Sprd take this? Thanks
> 
> --
> Keven

Xinhe will take it.
Flags: needinfo?(james.zhang)
We got incorrect signal from HW. This bug already assign to our hw engineer.
(In reply to Xinhe Yan from comment #16)
> We got incorrect signal from HW. This bug already assign to our hw engineer.

Is there any update? Thanks.
Flags: needinfo?(xinhe.yan)
Signal strengt related to our phyical register 0x57.
We found this register value is wrong. We already contact RF vendor to adjust this.
Flags: needinfo?(xinhe.yan)
can this be fixed by firmware update? thanks
Flags: needinfo?(xinhe.yan)
We will fix this bug in three days. The solution is update NV(NOT-VOLATILE), not firmware.
I will talk with Steven how Mozilla to update NV.
Flags: needinfo?(xinhe.yan)
Xinhe has fixed this bug on my side, but mozilla need upate nvitem with download tool.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Verified fixed in today's build


1.3t Environmental Variables:
Device: Tarako 1.3t
BuildID: 20140429014002
Gaia: b5adc5a943d3abbd6ab070a47c847f2c24891cc5
Gecko: e9890f5d4709
Version: 28.1
Firmware Version: sp6821
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.