Closed
Bug 1001387
Opened 10 years ago
Closed 10 years ago
[Tarako][Hamachi]Can not open Airplane mode when wifi is enabled
Categories
(Firefox OS Graveyard :: Vendcom, defect)
Tracking
(blocking-b2g:1.3T+)
RESOLVED
WORKSFORME
blocking-b2g | 1.3T+ |
People
(Reporter: xinhe.yan, Assigned: xinhe.yan)
Details
(Whiteboard: [sprd303154])
Attachments
(1 file)
245.96 KB,
application/x-gzip
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/11.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 Steps to reproduce: 1 Enable wifi(no need to connect ap) 2 Enable Airplane mode in Setting Actual results: Airplane mode is gray and Wi-Fi displa Initalizing
04-25 17:10:01.005 86 86 I Gecko : -*- WifiWorker component: State change: UNINITIALIZED -> INACTIVE 04-25 17:10:05.535 86 86 I Gecko : -*- WifiWorker component: manager.setWifiEnabled false state UNINITIALIZED
OS: All → Gonk (Firefox OS)
Hardware: All → ARM
I can't seem to turn wifi on which is bug 997791. Xinhe, are you using a build on the device?
Flags: needinfo?(xinhe.yan)
Updated•10 years ago
|
blocking-b2g: --- → 1.3T?
Whiteboard: [sprd303154]
You can check this bug 999388. Bug 999388 did not fix now. I have to apply patch in bug 999388 to avoid block our PTR1 test. I guess we need some time to fix 999388.
Flags: needinfo?(xinhe.yan)
Comment 4•10 years ago
|
||
Triage: 1.3T+ this is a blocker. we need to be able to set flight mode on any time ni? Vincent Chang
blocking-b2g: 1.3T? → 1.3T+
Flags: needinfo?(vchang)
Comment 5•10 years ago
|
||
Per comment 3, this should be duplicated of bug 999388.
Flags: needinfo?(vchang)
Comment 6•10 years ago
|
||
Xinhe, I think you opened this bug for tracking the status in your side. If not, please tell us what help we need to provide.
Component: Wifi → Vendcom
Comment 7•10 years ago
|
||
Per comment 5, set this case as duplicated of bug 999388. -- Keven
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
This bug happens one time after we fix bug 999388. Unfortunately, Gecko wifi log is not open. BTW, the rate to reproduce this bug is very slow. I think gecko wifi status is not correct. Gecko receive disable from fly mode. But setWifiEnabled will just return because state is UNINITIALIZED. I will add more log and try to repro this bug.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
(In reply to Xinhe Yan from comment #8) > I think gecko wifi status is not correct. Gecko receive disable from fly > mode. But setWifiEnabled will just return because state is UNINITIALIZED. Before fix bug 999388, wifi status is wrong is gecko did not receive CTRL-EVENT-TERMINATING. Please ignore comment 8. After fix bug 999388, this bug still can reproduce. 01-01 00:55:47.810 85 306 W WifiHW : wifi_command: TERMINATE 01-01 00:55:49.170 85 306 E WifiHW : wifi_stop_supplicant sleep 1 second to wait CTRL-EVENT-TERMINATING 01-01 00:55:49.510 85 306 D WifiHW : Unable to unload driver module "itm_ap": No such file or directory 01-01 00:57:47.820 85 306 W WifiHW : wifi_load_driver enter 211 01-01 00:57:47.900 87 165 W WifiHW : wifi_change_fw_path: /system/lib/modules/itm_sta.ko 01-01 00:57:48.110 87 165 D WifiHW : Unable to unload driver module "itm_ap": No such file or directory 01-01 00:57:48.310 87 165 D WifiHW : Unable to unload driver module "itm_sta": No such file or directory 01-01 00:57:48.510 87 165 W WifiHW : wifi_load_driver enter 211 01-01 00:57:48.510 87 165 W WifiHW : DRIVER_MODULE_PATH=/system/lib/modules/itm_sta.ko DRIVER_MODULE_ARG= 01-01 00:57:48.510 87 165 W WifiHW : insmod filename=/system/lib/modules/itm_sta.ko args= 01-01 00:57:49.900 87 165 W WifiHW : driver insmod complete 01-01 00:57:51.900 85 306 E WifiHW : Leo ensure_config_file_exists config_file=/data/misc/wifi/wpa_supplicant.conf 01-01 00:57:51.900 85 306 E WifiHW : daemon_cmd=wpa_supplicant:-iwlan0 -c/data/misc/wifi/wpa_supplicant.conf 01-01 00:57:51.910 85 306 E WifiHW : Unable to open connection to supplicant on "wlan0": No such file or directory 01-01 00:57:52.920 85 306 W WifiHW : wifi_command: LOG_LEVEL 01-01 00:57:52.920 85 306 W WifiHW : wifi_command: STATUS 01-01 00:57:52.920 85 306 W WifiHW : wifi_command: LOG_LEVEL DEBUG 01-01 00:57:52.920 85 306 W WifiHW : wifi_command: LIST_NETWORKS 01-01 00:57:52.920 85 306 W WifiHW : wifi_command: DRIVER MACADDR 01-01 00:57:52.930 85 306 W WifiHW : wifi_command: AP_SCAN 1 01-01 00:57:52.930 85 306 W WifiHW : wifi_command: SAVE_CONFIG 05-04 06:02:20.349 85 306 W WifiHW : wifi_command: DRIVER SCAN-ACTIVE 05-04 06:02:20.489 85 306 W WifiHW : wifi_command: SCAN 05-04 06:02:20.489 85 306 W WifiHW : wifi_command: DRIVER SCAN-PASSIVE 05-04 06:02:21.899 85 306 W WifiHW : wifi_command: SCAN_RESULTS 05-04 06:02:21.909 85 306 W WifiHW : wifi_command: DRIVER SCAN-PASSIVE By now, everything is correct. At 06:06:51, tester click fly mode again which can be verify by RIL log. 05-04 06:06:55.299 96 373 D RILC : [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_OFF} 05-04 06:06:55.299 96 373 D RILC : [UNSL]< UNSOL_RESPONSE_VOICE_NETWORK_STATE_CHANGED 05-04 06:06:55.299 96 373 D RILC : [1023]< RADIO_POWER 05-04 06:06:56.869 102 376 D RILC : [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_OFF} 05-04 06:06:56.869 102 376 D RILC : [UNSL]< UNSOL_RESPONSE_VOICE_NETWORK_STATE_CHANGED 05-04 06:06:56.869 102 376 D RILC : [0919]< RADIO_POWER Gecko log 05-04 06:06:55.329 85 317 I Gecko : RIL Worker: [0] Radio state changed from 'ready' to 'off' 05-04 06:06:56.879 85 317 I Gecko : RIL Worker: [1] Radio state changed from 'ready' to 'off' 05-04 06:06:55.369 85 85 I Gecko : -*- RILContentHelper: Received message 'RIL:SetRadioEnabled': {"clientId":0,"data":{"requestId":"id{e8fad325-64a9-4656-a711-4010ec4f33e0}","enabled":false,"rilMessageClientId":0,"rilMessageToken":68,"rilMessageType":"setRadioEnabled","rilRequestType":23,"rilRequestError":0}} 05-04 06:06:55.369 85 85 I Gecko : -*- RILContentHelper: fire request success, id: id{e8fad325-64a9-4656-a711-4010ec4f33e0}, result: null 05-04 06:06:56.909 85 85 I Gecko : -*- RILContentHelper: Received message 'RIL:SetRadioEnabled': {"clientId":1,"data":{"requestId":"id{48e59f49-9cb9-42ad-af76-22fdf49b87f8}","enabled":false,"rilMessageClientId":1,"rilMessageToken":71,"rilMessageType":"setRadioEnabled","rilRequestType":23,"rilRequestError":0}} 05-04 06:06:56.909 85 85 I Gecko : -*- RILContentHelper: fire request success, id: id{48e59f49-9cb9-42ad-af76-22fdf49b87f8}, result: null We need find out why no TERMINATE command was send to wpa_supplicant. But without gecko wifi log, it is hard to analyse.
Comment 10•10 years ago
|
||
Xinhe, since you are working on this, assign this bug to you for now. Thanks
Assignee: nobody → xinhe.yan
Assignee | ||
Comment 11•10 years ago
|
||
This bug not reproduce on our side.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•