Closed
Bug 1092365
Opened 11 years ago
Closed 7 years ago
[flame] [Wifi] Cannot turn on
Categories
(Firefox OS Graveyard :: Wifi, defect)
Tracking
(b2g-v2.1 unaffected, b2g-v2.2 affected)
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| b2g-v2.1 | --- | unaffected |
| b2g-v2.2 | --- | affected |
People
(Reporter: gaby2300, Unassigned)
Details
(Keywords: regression, Whiteboard: qawanted)
Attachments
(8 files)
I found this bug using base image v188, 2.2 and the latest OTA updates.
STR:
1. Turn on Wifi.
2. Note nothing happens or no networks are found.
Actual behaviour: Wifi cannot be turned on or no networks are found.
Expected behaviour: Wifi should turn on and networks should be found.
Frecuency: 50%
Workaround: restart the phone
|
||
Comment 1•11 years ago
|
||
adding qawanted for help. Gabriela, can you tell us the version of the build you are running? also, does this work after you restarted the phone?
Keywords: qawanted
|
Reporter | |
Comment 2•11 years ago
|
||
Tony,
2.2.0.0 prerelease.
Plataform: 36.0a1
Build Id: 2014103161804
Update channel: nightly
Git commit info: 2014-10-30 23:54:58 a0799471
After restarting the phone, sometimes it worked, sometimes it didn't
|
|
||
Updated•11 years ago
|
QA Contact: ckreinbring
|
|
||
Comment 3•11 years ago
|
||
The bug repros on Flame 2.2 nightly (full flash) and engineering (shallow flash).
Actual result: When launching Settings then Wi-Fi, the Wi-Fi setting will be off. Tapping it will move the switch, but nothing else will happen.
Flame 2.2 engineering
BuildID: 20141031131456
Gaia: 5964f1339f37e7595aff7de7512b8529bc640b76
Gecko: 12ac66e2c016
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Flame 2.2 nightly
BuildID: 20141031061804
Gaia: a07994714f0552f89801d6097982308d8b0a1ee1
Gecko: 6bd2071b373f
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
--------------------------------------------------------------------------------------------------------
The bug does not repro on Flame 2.1 nightly (full flash) or engineering (shallow flash).
Actual result: When launching Settings then Wi-Fi, the Wi-Fi setting will be on. A list of available networks will also be shown on the page.
Flame 2.1 engineering
BuildID: 20141031084110
Gaia: 18289d3b6136a6cf3efafcaeed677a99ef5362a4
Gecko: 1f1017a1eff5
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flame 2.1 nightly
BuildID: 20141030001201
Gaia: 3e585d8be5e2dffc376f83313299c9b6d53c3db4
Gecko: b643d78a23c6
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Platform Version: 34.0
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → unaffected
status-b2g-v2.2:
--- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted → regression
|
|
||
Comment 4•11 years ago
|
||
Nomming for 2.2 - broken functionality in WiFi
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: regressionwindow-wanted
QA Contact: ckreinbring
|
|
||
Updated•11 years ago
|
QA Contact: ckreinbring
|
||
Comment 5•11 years ago
|
||
I can't reproduce the problem using image in https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-kk-eng/latest/flame-kk.zip
Here is the version info,
Gaia-Rev c2c55870de22d596de4f41612c0b44090f90ebad
Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/0b81c10a9074
Build-ID 20141102160202
Version 36.0a1
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20141102.193342
FW-Date Sun Nov 2 19:33:56 EST 2014
Bootloader L1TC00011880
I can't find the image you used from pvt server, can you provide the link?
Flags: needinfo?(ckreinbring)
|
|
Reporter | |
Comment 6•11 years ago
|
||
The base image link is the following: http://cds.w5v8t3u9.hwcdn.net/v188.zip
|
|
Reporter | |
Comment 7•11 years ago
|
||
And the master build 2.2 link: https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame-kk/
|
|
||
Comment 8•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #7)
> And the master build 2.2 link:
> https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-
> flame-kk/
Hi Gabriela, do you know how to upgrade b2g to this link? It's *.mar file.
|
|
||
Updated•11 years ago
|
Flags: needinfo?(gmontagu)
|
|
Reporter | |
Comment 9•11 years ago
|
||
Hi Vincent, I'm sorry but I don't understand what build you mean. It's not so easy to upgrade for me though because I use Windows.
Flags: needinfo?(gmontagu)
|
|
||
Comment 10•11 years ago
|
||
Regression window
Last working
BuildID: 20141029054810
Gaia: a9a847920b51b79c4ad4ad339f0a005777a6228c
Gecko: c6989e473f97
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
First broken
BuildID: 20141029131614
Gaia: 0dfc1996eb583c8b507a82bf6b8319624bba23ea
Gecko: 8345ae427a3f
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Working Gaia / Broken Gecko = Repro
Gaia: a9a847920b51b79c4ad4ad339f0a005777a6228c
Gecko: 8345ae427a3f
Broken Gaia / Working Gecko = No repro
Gaia: 0dfc1996eb583c8b507a82bf6b8319624bba23ea
Gecko: c6989e473f97
Gecko pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c6989e473f97&tochange=8345ae427a3f
B2G Inbound
Last working
BuildID: 20141029073813
Gaia: 30e37915865af8eb8164a50e7512e68f40967961
Gecko: 817df6f416b3
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
First broken
BuildID: 20141029091112
Gaia: 30e37915865af8eb8164a50e7512e68f40967961
Gecko: f5b374bb59ab
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Working Gaia / Broken Gecko = Repro
Gaia: 30e37915865af8eb8164a50e7512e68f40967961
Gecko: f5b374bb59ab
Broken Gaia / Working Gecko = No repro
Gaia: 30e37915865af8eb8164a50e7512e68f40967961
Gecko: 817df6f416b3
Gecko pushlog: http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=817df6f416b3&tochange=f5b374bb59ab
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ckreinbring) → needinfo?(jmitchell)
Keywords: regressionwindow-wanted
|
|
Reporter | |
Comment 11•11 years ago
|
||
I found a variation of this bug: the wifi turns on, it doesn't find any networks available (when there actually are some) and it turns off.
Should I file this other issue as a new separate bug?
|
|
||
Comment 12•11 years ago
|
||
likely broken by Bug 1087152 or Bug 1083449 - can you take a look Henry
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(hchang)
QA Contact: ckreinbring
|
||
Comment 13•11 years ago
|
||
(In reply to Joshua Mitchell [:Joshua_M] from comment #12)
> likely broken by Bug 1087152 or Bug 1083449 - can you take a look Henry
Okay I will be looking into this issue. Thanks!
Flags: needinfo?(hchang)
|
|
||
Comment 14•11 years ago
|
||
I tried the following config which is said to broken:
First broken
BuildID: 20141029091112
Gaia: 30e37915865af8eb8164a50e7512e68f40967961
Gecko: f5b374bb59ab
Platform Version: 36.0a1
Firmware Version: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
but it works totally fine.
Chris,
Could you please double check the test result or
it requires any specific step to reproduce it? Thanks!
Flags: needinfo?(ckreinbring)
|
|
||
Comment 15•11 years ago
|
||
How many times did you try it? Remember that the bug does not have a 100% repro rate. I did my window with 20 attempts each unless I reproed the bug.
Flags: needinfo?(ckreinbring)
|
|
||
Comment 16•11 years ago
|
||
(In reply to Chris Kreinbring [:CKreinbring] from comment #15)
> How many times did you try it? Remember that the bug does not have a 100%
> repro rate. I did my window with 20 attempts each unless I reproed the bug.
Chris,
After doing more than 30 attempts, I've still never seen this issue.
Gabriela mentioned the repro rate is 50%. What's the repro rate from
your side?
Thanks!
|
|
Reporter | |
Comment 17•11 years ago
|
||
(In reply to Chris Kreinbring [:CKreinbring] from comment #15)
> How many times did you try it? Remember that the bug does not have a 100%
> repro rate. I did my window with 20 attempts each unless I reproed the bug.
I tried lost of times in a restaurant, where I discovered the issue, at home where I have my own wifi network and at work. In all these places my Samsung SII phone shows a list of at least 5 different networks.
|
|
Reporter | |
Comment 18•11 years ago
|
||
Today I tried again at the same restaurant as before.
First, the wifi turned on but no networks were found and it turned off by it's self. I tried this about 10 times and got the same result.
Then, the wifi turned on and showed a list of networks. I found the restaurant's one, I entered the correct password but it didn't connect (no error message showed up, it just didn't connect). The restaurant's network kept showing but tapping it nothing happened. I tried several times with the same result.
Then I restarted the phone and it connected by it's self to the restaurant's network and the emails started downloading.
|
|
||
Comment 19•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #18)
> Today I tried again at the same restaurant as before.
>
> First, the wifi turned on but no networks were found and it turned off by
> it's self. I tried this about 10 times and got the same result.
>
> Then, the wifi turned on and showed a list of networks. I found the
> restaurant's one, I entered the correct password but it didn't connect (no
> error message showed up, it just didn't connect). The restaurant's network
> kept showing but tapping it nothing happened. I tried several times with the
> same result.
>
> Then I restarted the phone and it connected by it's self to the restaurant's
> network and the emails started downloading.
We can't duplicate the problem here. To move the bug forward, can you turn on settings/developer/WiFi output in ADB option and help to capture wifi log?
After turning on wifi debug option, please turning wifi off/on to output wifi debug message to "adb logcat".
|
|
Reporter | |
Comment 20•11 years ago
|
||
I'll do whatever it takes to move the bug forward but I don't quite understand the procedure to capture the log.
I would appreciate step by step clear instructions. Please keep in mind I am a Windows 7 user.
|
|
Reporter | |
Comment 21•11 years ago
|
||
(In reply to Vincent Chang[:vchang] from comment #19)
>
> We can't duplicate the problem here. To move the bug forward, can you turn
> on settings/developer/WiFi output in ADB option and help to capture wifi
> log?
> After turning on wifi debug option, please turning wifi off/on to output
> wifi debug message to "adb logcat".
I did what I understood, I hope it helps:
e at 0x0
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
D/qdhwcomposer( 211): hwc_blank: Blanking display: 0
I/qdhwcomposer( 211): handle_blank_event: dpy:0 panel power state: 0
D/qdhwcomposer( 211): hwc_blank: Done blanking display: 0
I/QCOM PowerHAL( 211): Got set_interactive hint
I/AutoMounter( 211): Changing mode from 'Enable-UMS' to 'DisableWhenUnplugged'
I/AutoMounter( 211): UpdateState: ums:A1C1E1 mtp:A1C0E0 mode:2 usb:1 tryToShare
:1 state:UMS_CONFIGURED
I/AutoMounter( 211): UpdateState: Volume sdcard is Shared and inserted
I/AutoMounter( 211): UpdateState: Volume sdcard1 is Shared and inserted
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [LOWI-SERVER] unknown deliver t
arget [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [LOWI-SERVER] unknown deliver t
arget [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/Profiler( 211): 2014-11-12 16:23:47: range_map-inl.h:91: INFO: StoreRange fai
led, an existing range contains or extends higher than the new range: new 0xffff
0000+0x1000, existing 0xffff0000+0x1000
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:70: ERROR: Module
[vectors] could not be stored
E/Profiler( 211): 2014-11-12 16:23:47: stackwalker.cc:125: INFO: Couldn't load
symbols for: /system/lib/libc.so|92577142DFE642610A586D7CF6EEDF360
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xb6ad31c0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x1
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xb3dcdcc0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: stackwalker.cc:125: INFO: Couldn't load
symbols for: /system/b2g/libxul.so|A87D21D8B4D968E9946D7932BD9DC12D0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x728597
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xb6ad31c0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xb3dcdd88
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xa7b0d680
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x14
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xbeb96001
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xa7b0d680
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xa7b0d640
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xb3dcdcc0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x1
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xbeb96014
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xa7b0d680
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x8
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x1
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xc4
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xbeb96070
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x1
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xa7b0d640
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xbeb96070
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xa7b0d640
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xaedd0c30
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xafdaee60
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xa7b0d640
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xaed93640
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0x0
E/Profiler( 211): 2014-11-12 16:23:47: basic_code_modules.cc:88: INFO: No modul
e at 0xbeb960c0
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [LOWI-SERVER] unknown deliver t
arget [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 215): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 305): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
Note: I'm at home, where I have my own wifi network. Sometimes I get this issue, sometimes it connects flawlessly. When it doesn't, the only way to be able to turn on the wifi is restarting the phone, then the wifi turns on and connects in an automate way to my network.
I have the same issue at work where there's a free network and at the restaurant where I discovered the bug.
|
|
Reporter | |
Comment 22•11 years ago
|
||
I've pasted the wifi log 2 weeks ago by vchang's request but got no further comment.
I'm sorry but I'm changing the priority to major because I'm still seeing this bug using base image v188, 2.2 and the latest OTA update (Plataform version 36.0a1, Build ID 20141125040289, Update channel: nightly, Git commit info: 2014-11-25 06:30:17 824a61cc) and I think it's a very important issue.
Severity: normal → major
|
|
||
Comment 23•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #22)
> I've pasted the wifi log 2 weeks ago by vchang's request but got no further
> comment.
>
> I'm sorry but I'm changing the priority to major because I'm still seeing
> this bug using base image v188, 2.2 and the latest OTA update (Plataform
> version 36.0a1, Build ID 20141125040289, Update channel: nightly, Git commit
> info: 2014-11-25 06:30:17 824a61cc) and I think it's a very important issue.
Sorry for late response and thanks for the log. However, the log is not complete.
We need the log including "wpa_supplicant" or "WifiWorker". Please make sure
you run logcat since booting up so that we can get the helpful log to go further.
Thanks!
|
|
Reporter | |
Comment 24•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #23)
I've tried again at home and I got the same result with today's morning OTA update.
I captured the log again trying several times. I can see "wpa_supplicant" and "WifiWorker" included so I hope I did it right this time. If not, just tell me and I'll do it again. I am very interested in having this issue fixed because it's a very important feature that doesn't work as it should and it may affect a lot of people!
Thanks!
Here is the log:
D/WifiHW ( 210): priority=8
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="GABRIELA"
D/WifiHW ( 210): psk="01412528435"
D/WifiHW ( 210): key_mgmt=WPA-PSK
D/WifiHW ( 210): priority=184
D/WifiHW ( 210): frequency=2457
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="Portthru"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): priority=171
D/WifiHW ( 210): mode=1
D/WifiHW ( 210): frequency=2452
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="Xerox"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): priority=194
D/WifiHW ( 210): mode=1
D/WifiHW ( 210): frequency=2457
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="dd-wrt_vap"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): priority=7
D/WifiHW ( 210): frequency=2437
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="BA WiFi"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): priority=190
D/WifiHW ( 210): frequency=2452
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="AREPO_ARENALES"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): auth_alg=OPEN SHARED
D/WifiHW ( 210): wep_key0="arepo"
D/WifiHW ( 210): priority=51
D/WifiHW ( 210): frequency=2437
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="HP-Print-4B-LaserJet 1102"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): priority=126
D/WifiHW ( 210): frequency=2412
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="HPF0D397"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): priority=193
D/WifiHW ( 210): mode=1
D/WifiHW ( 210): frequency=2457
D/WifiHW ( 210): }
D/WifiHW ( 210):
D/WifiHW ( 210): network={
D/WifiHW ( 210): ssid="invitados areatres Labs"
D/WifiHW ( 210): key_mgmt=NONE
D/WifiHW ( 210): priority=16
I/Gecko ( 210): -*- WifiWorker component: detected SDK version 19
E/WifiHW ( 210): Unable to open connection to supplicant on "@android:wpa_wlan
0": No such file or directory
D/wpa_supplicant(13700): wpa_supplicant v2.1-devel-4.4.2
D/wpa_supplicant(13700): Add randomness: count=1 entropy=0
D/wpa_supplicant(13700): random pool - hexdump(len=128): [REMOVED]
D/wpa_supplicant(13700): random_mix_pool - hexdump(len=8): [REMOVED]
D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random pool - hexdump(len=128): [REMOVED]
D/wpa_supplicant(13700): random: Added entropy from /data/misc/wifi/entropy.bin
(own_pool_ready=2)
D/wpa_supplicant(13700): random: Trying to read entropy from /dev/random
D/wpa_supplicant(13700): Get randomness: len=20 entropy=1
D/wpa_supplicant(13700): random from os_get_random - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random from internal pool - hexdump(len=16): [REMOVED]
D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random from internal pool - hexdump(len=16): [REMOVED]
D/wpa_supplicant(13700): mixed random - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random: Updated entropy file /data/misc/wifi/entropy.bi
n (own_pool_ready=2)
D/wpa_supplicant(13700): Global control interface '@android:wpa_wlan0'
D/wpa_supplicant(13700): Using Android control socket 'wpa_wlan0'
I/wpa_supplicant(13700): Successfully initialized wpa_supplicant
D/wpa_supplicant(13700): Override interface parameter: ctrl_interface ('(null)'
-> '/data/misc/wifi/sockets')
D/wpa_supplicant(13700): Initializing interface 'wlan0' conf '/data/misc/wifi/wp
a_supplicant.conf' driver 'nl80211' ctrl_interface '/data/misc/wifi/sockets' bri
dge 'N/A'
D/wpa_supplicant(13700): Configuration file '/data/misc/wifi/wpa_supplicant.conf
' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant(13700): Reading configuration file '/data/misc/wifi/wpa_supplic
ant.conf'
D/wpa_supplicant(13700): ctrl_interface='/data/misc/wifi/sockets'
D/wpa_supplicant(13700): disable_scan_offload=1
D/wpa_supplicant(13700): update_config=1
D/wpa_supplicant(13700): p2p_disabled=1
D/wpa_supplicant(13700): p2p_no_group_iface=1
D/wpa_supplicant(13700): Line: 7 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=6): 76 65 72 73 75 73
D/wpa_supplicant(13700): PSK (ASCII passphrase) - hexdump(len=9): [REMOVED]
D/wpa_supplicant(13700): key_mgmt: 0x2
D/wpa_supplicant(13700): priority=8 (0x8)
D/wpa_supplicant(13700): PSK (from passphrase) - hexdump(len=32): [REMOVED]
D/wpa_supplicant(13700): Line: 14 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=8): 47 41 42 52 49 45 4c 41
D/wpa_supplicant(13700): PSK (ASCII passphrase) - hexdump(len=11): [REMOVED]
D/wpa_supplicant(13700): key_mgmt: 0x2
D/wpa_supplicant(13700): priority=184 (0xb8)
D/wpa_supplicant(13700): frequency=2457 (0x999)
D/wpa_supplicant(13700): PSK (from passphrase) - hexdump(len=32): [REMOVED]
D/wpa_supplicant(13700): Line: 22 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=8): 50 6f 72 74 74 68 72 75
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=171 (0xab)
D/wpa_supplicant(13700): mode=1 (0x1)
D/wpa_supplicant(13700): frequency=2452 (0x994)
D/wpa_supplicant(13700): Line: 30 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=5): 58 65 72 6f 78
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=194 (0xc2)
D/wpa_supplicant(13700): mode=1 (0x1)
D/wpa_supplicant(13700): frequency=2457 (0x999)
D/wpa_supplicant(13700): Line: 38 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=10): 64 64 2d 77 72 74 5f 76 61 70
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=7 (0x7)
D/wpa_supplicant(13700): frequency=2437 (0x985)
D/wpa_supplicant(13700): Line: 45 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=7): 42 41 20 57 69 46 69
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=190 (0xbe)
D/wpa_supplicant(13700): frequency=2452 (0x994)
D/wpa_supplicant(13700): Line: 52 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=14): 41 52 45 50 4f 5f 41 52 45 4e 4
1 4c 45 53
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): auth_alg: 0x3
D/wpa_supplicant(13700): wep_key0 - hexdump(len=5): [REMOVED]
D/wpa_supplicant(13700): priority=51 (0x33)
D/wpa_supplicant(13700): frequency=2437 (0x985)
D/wpa_supplicant(13700): Line: 61 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=25): 48 50 2d 50 72 69 6e 74 2d 34 4
2 2d 4c 61 73 65 72 4a 65 74 20 31 31 30 32
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=126 (0x7e)
D/wpa_supplicant(13700): frequency=2412 (0x96c)
D/wpa_supplicant(13700): Line: 68 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=8): 48 50 46 30 44 33 39 37
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=193 (0xc1)
D/wpa_supplicant(13700): mode=1 (0x1)
D/wpa_supplicant(13700): frequency=2457 (0x999)
D/wpa_supplicant(13700): Line: 76 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=23): 69 6e 76 69 74 61 64 6f 73 20 6
1 72 65 61 74 72 65 73 20 4c 61 62 73
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=166 (0xa6)
D/wpa_supplicant(13700): frequency=2412 (0x96c)
D/wpa_supplicant(13700): Line: 83 - start of a new network block
D/wpa_supplicant(13700): ssid - hexdump(len=25): 48 50 2d 50 72 69 6e 74 2d 37 4
3 2d 4c 61 73 65 72 4a 65 74 20 31 31 30 32
D/wpa_supplicant(13700): key_mgmt: 0x4
D/wpa_supplicant(13700): priority=167 (0xa7)
D/wpa_supplicant(13700): frequency=2437 (0x985)
D/wpa_supplicant(13700): Priority group 194
D/wpa_supplicant(13700): id=3 ssid='Xerox'
D/wpa_supplicant(13700): Priority group 193
D/wpa_supplicant(13700): id=8 ssid='HPF0D397'
D/wpa_supplicant(13700): Priority group 190
D/wpa_supplicant(13700): id=5 ssid='BA WiFi'
D/wpa_supplicant(13700): Priority group 184
D/wpa_supplicant(13700): id=1 ssid='GABRIELA'
D/wpa_supplicant(13700): Priority group 171
D/wpa_supplicant(13700): id=2 ssid='Portthru'
D/wpa_supplicant(13700): Priority group 167
D/wpa_supplicant(13700): id=10 ssid='HP-Print-7C-LaserJet 1102'
D/wpa_supplicant(13700): Priority group 166
D/wpa_supplicant(13700): id=9 ssid='invitados areatres Labs'
D/wpa_supplicant(13700): Priority group 126
D/wpa_supplicant(13700): id=7 ssid='HP-Print-4B-LaserJet 1102'
D/wpa_supplicant(13700): Priority group 51
D/wpa_supplicant(13700): id=6 ssid='AREPO_ARENALES'
D/wpa_supplicant(13700): Priority group 8
D/wpa_supplicant(13700): id=0 ssid='versus'
D/wpa_supplicant(13700): Priority group 7
D/wpa_supplicant(13700): id=4 ssid='dd-wrt_vap'
D/wpa_supplicant(13700): Reading configuration file '/system/etc/wifi/wpa_suppli
cant_overlay.conf'
D/wpa_supplicant(13700): disable_scan_offload=1
D/wpa_supplicant(13700): p2p_disabled=1
D/wpa_supplicant(13700): Priority group 194
D/wpa_supplicant(13700): id=3 ssid='Xerox'
D/wpa_supplicant(13700): Priority group 193
D/wpa_supplicant(13700): id=8 ssid='HPF0D397'
D/wpa_supplicant(13700): Priority group 190
D/wpa_supplicant(13700): id=5 ssid='BA WiFi'
D/wpa_supplicant(13700): Priority group 184
D/wpa_supplicant(13700): id=1 ssid='GABRIELA'
D/wpa_supplicant(13700): Priority group 171
D/wpa_supplicant(13700): id=2 ssid='Portthru'
D/wpa_supplicant(13700): Priority group 167
D/wpa_supplicant(13700): id=10 ssid='HP-Print-7C-LaserJet 1102'
D/wpa_supplicant(13700): Priority group 166
D/wpa_supplicant(13700): id=9 ssid='invitados areatres Labs'
D/wpa_supplicant(13700): Priority group 126
D/wpa_supplicant(13700): id=7 ssid='HP-Print-4B-LaserJet 1102'
D/wpa_supplicant(13700): Priority group 51
D/wpa_supplicant(13700): id=6 ssid='AREPO_ARENALES'
D/wpa_supplicant(13700): Priority group 8
D/wpa_supplicant(13700): id=0 ssid='versus'
D/wpa_supplicant(13700): Priority group 7
D/wpa_supplicant(13700): id=4 ssid='dd-wrt_vap'
I/wpa_supplicant(13700): rfkill: Cannot open RFKILL control device
D/wpa_supplicant(13700): nl80211: RFKILL status not available
D/wpa_supplicant(13700): nl80211: Using driver-based off-channel TX
D/wpa_supplicant(13700): nl80211: Using driver-based roaming
D/wpa_supplicant(13700): nl80211: TDLS supported
D/wpa_supplicant(13700): nl80211: TDLS external setup
D/wpa_supplicant(13700): nl80211: Supports Probe Response offload in AP mode
D/wpa_supplicant(13700): nl80211: Supported vendor event: vendor_id=0x1374 subcm
d=10
D/wpa_supplicant(13700): nl80211: Use separate P2P group interface (driver adver
tised support)
D/wpa_supplicant(13700): nl80211: Enable multi-channel concurrent (driver advert
ised support)
D/wpa_supplicant(13700): nl80211: Driver is new enough to support monitor-less m
ode
D/wpa_supplicant(13700): nl80211: interface wlan0 in phy phy0
D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95 (Ope
ration not supported on transport endpoint)
D/wpa_supplicant(13700): nl80211: Try mode change after setting interface down
D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95 (Ope
ration not supported on transport endpoint)
D/wpa_supplicant(13700): nl80211: Interface mode change to 2 from 0 failed
E/wpa_supplicant(13700): nl80211: Could not configure driver to use managed mode
D/wpa_supplicant(13700): netlink: Operstate: linkmode=0, operstate=6
D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95 (Ope
ration not supported on transport endpoint)
D/wpa_supplicant(13700): nl80211: Try mode change after setting interface down
D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95 (Ope
ration not supported on transport endpoint)
D/wpa_supplicant(13700): nl80211: Interface mode change to 2 from 0 failed
E/wpa_supplicant(13700): wlan0: Failed to initialize driver interface
D/wpa_supplicant(13700): Failed to add interface wlan0
D/wpa_supplicant(13700): wlan0: Cancelling scan request
D/wpa_supplicant(13700): wlan0: P2P: Station mode scan operation not pending any
more (sta_scan_pending=0 p2p_cb_on_scan_complete=0)
D/wpa_supplicant(13700): wlan0: Cancelling authentication timeout
D/wpa_supplicant(13700): Get randomness: len=20 entropy=0
D/wpa_supplicant(13700): random from os_get_random - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random from internal pool - hexdump(len=16): [REMOVED]
D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random from internal pool - hexdump(len=16): [REMOVED]
D/wpa_supplicant(13700): mixed random - hexdump(len=20): [REMOVED]
D/wpa_supplicant(13700): random: Updated entropy file /data/misc/wifi/entropy.bi
n (own_pool_ready=2)
E/WifiHW ( 210): Supplicant not running, cannot connect
E/WifiHW ( 210): Supplicant not running, cannot connect
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 214): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/WifiHW ( 210): Supplicant not running, cannot connect
E/WifiHW ( 210): Supplicant not running, cannot connect
E/WifiHW ( 210): Supplicant not running, cannot connect
I/Gecko ( 210): -*- WifiWorker component: Supplicant died!
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 214): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target
[OS-Agent]
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver tar
get [OS-Agent]
E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver tar
get [OS-Agent]
V/WLAN_PSA( 214): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
|
|
||
Comment 25•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #24)
> (In reply to Henry Chang [:henry] from comment #23)
>
> I've tried again at home and I got the same result with today's morning OTA
> update.
>
> I captured the log again trying several times. I can see "wpa_supplicant"
> and "WifiWorker" included so I hope I did it right this time. If not, just
> tell me and I'll do it again. I am very interested in having this issue
> fixed because it's a very important feature that doesn't work as it should
> and it may affect a lot of people!
>
> Thanks!
>
> Here is the log:
>
> D/WifiHW ( 210): priority=8
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="GABRIELA"
> D/WifiHW ( 210): psk="01412528435"
> D/WifiHW ( 210): key_mgmt=WPA-PSK
> D/WifiHW ( 210): priority=184
> D/WifiHW ( 210): frequency=2457
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="Portthru"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): priority=171
> D/WifiHW ( 210): mode=1
> D/WifiHW ( 210): frequency=2452
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="Xerox"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): priority=194
> D/WifiHW ( 210): mode=1
> D/WifiHW ( 210): frequency=2457
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="dd-wrt_vap"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): priority=7
> D/WifiHW ( 210): frequency=2437
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="BA WiFi"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): priority=190
> D/WifiHW ( 210): frequency=2452
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="AREPO_ARENALES"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): auth_alg=OPEN SHARED
> D/WifiHW ( 210): wep_key0="arepo"
> D/WifiHW ( 210): priority=51
> D/WifiHW ( 210): frequency=2437
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="HP-Print-4B-LaserJet 1102"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): priority=126
> D/WifiHW ( 210): frequency=2412
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="HPF0D397"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): priority=193
> D/WifiHW ( 210): mode=1
> D/WifiHW ( 210): frequency=2457
> D/WifiHW ( 210): }
> D/WifiHW ( 210):
> D/WifiHW ( 210): network={
> D/WifiHW ( 210): ssid="invitados areatres Labs"
> D/WifiHW ( 210): key_mgmt=NONE
> D/WifiHW ( 210): priority=16
> I/Gecko ( 210): -*- WifiWorker component: detected SDK version 19
> E/WifiHW ( 210): Unable to open connection to supplicant on
> "@android:wpa_wlan
> 0": No such file or directory
> D/wpa_supplicant(13700): wpa_supplicant v2.1-devel-4.4.2
> D/wpa_supplicant(13700): Add randomness: count=1 entropy=0
> D/wpa_supplicant(13700): random pool - hexdump(len=128): [REMOVED]
> D/wpa_supplicant(13700): random_mix_pool - hexdump(len=8): [REMOVED]
> D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
> D/wpa_supplicant(13700): random pool - hexdump(len=128): [REMOVED]
> D/wpa_supplicant(13700): random: Added entropy from
> /data/misc/wifi/entropy.bin
> (own_pool_ready=2)
> D/wpa_supplicant(13700): random: Trying to read entropy from /dev/random
> D/wpa_supplicant(13700): Get randomness: len=20 entropy=1
> D/wpa_supplicant(13700): random from os_get_random - hexdump(len=20):
> [REMOVED]
> D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
> D/wpa_supplicant(13700): random from internal pool - hexdump(len=16):
> [REMOVED]
> D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
> D/wpa_supplicant(13700): random from internal pool - hexdump(len=16):
> [REMOVED]
> D/wpa_supplicant(13700): mixed random - hexdump(len=20): [REMOVED]
> D/wpa_supplicant(13700): random: Updated entropy file
> /data/misc/wifi/entropy.bi
> n (own_pool_ready=2)
> D/wpa_supplicant(13700): Global control interface '@android:wpa_wlan0'
> D/wpa_supplicant(13700): Using Android control socket 'wpa_wlan0'
> I/wpa_supplicant(13700): Successfully initialized wpa_supplicant
> D/wpa_supplicant(13700): Override interface parameter: ctrl_interface
> ('(null)'
> -> '/data/misc/wifi/sockets')
> D/wpa_supplicant(13700): Initializing interface 'wlan0' conf
> '/data/misc/wifi/wp
> a_supplicant.conf' driver 'nl80211' ctrl_interface '/data/misc/wifi/sockets'
> bri
> dge 'N/A'
> D/wpa_supplicant(13700): Configuration file
> '/data/misc/wifi/wpa_supplicant.conf
> ' -> '/data/misc/wifi/wpa_supplicant.conf'
> D/wpa_supplicant(13700): Reading configuration file
> '/data/misc/wifi/wpa_supplic
> ant.conf'
> D/wpa_supplicant(13700): ctrl_interface='/data/misc/wifi/sockets'
> D/wpa_supplicant(13700): disable_scan_offload=1
> D/wpa_supplicant(13700): update_config=1
> D/wpa_supplicant(13700): p2p_disabled=1
> D/wpa_supplicant(13700): p2p_no_group_iface=1
> D/wpa_supplicant(13700): Line: 7 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=6): 76 65 72 73 75 73
> D/wpa_supplicant(13700): PSK (ASCII passphrase) - hexdump(len=9): [REMOVED]
> D/wpa_supplicant(13700): key_mgmt: 0x2
> D/wpa_supplicant(13700): priority=8 (0x8)
> D/wpa_supplicant(13700): PSK (from passphrase) - hexdump(len=32): [REMOVED]
> D/wpa_supplicant(13700): Line: 14 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=8): 47 41 42 52 49 45 4c 41
> D/wpa_supplicant(13700): PSK (ASCII passphrase) - hexdump(len=11): [REMOVED]
> D/wpa_supplicant(13700): key_mgmt: 0x2
> D/wpa_supplicant(13700): priority=184 (0xb8)
> D/wpa_supplicant(13700): frequency=2457 (0x999)
> D/wpa_supplicant(13700): PSK (from passphrase) - hexdump(len=32): [REMOVED]
> D/wpa_supplicant(13700): Line: 22 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=8): 50 6f 72 74 74 68 72 75
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=171 (0xab)
> D/wpa_supplicant(13700): mode=1 (0x1)
> D/wpa_supplicant(13700): frequency=2452 (0x994)
> D/wpa_supplicant(13700): Line: 30 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=5): 58 65 72 6f 78
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=194 (0xc2)
> D/wpa_supplicant(13700): mode=1 (0x1)
> D/wpa_supplicant(13700): frequency=2457 (0x999)
> D/wpa_supplicant(13700): Line: 38 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=10): 64 64 2d 77 72 74 5f 76 61
> 70
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=7 (0x7)
> D/wpa_supplicant(13700): frequency=2437 (0x985)
> D/wpa_supplicant(13700): Line: 45 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=7): 42 41 20 57 69 46 69
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=190 (0xbe)
> D/wpa_supplicant(13700): frequency=2452 (0x994)
> D/wpa_supplicant(13700): Line: 52 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=14): 41 52 45 50 4f 5f 41 52 45
> 4e 4
> 1 4c 45 53
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): auth_alg: 0x3
> D/wpa_supplicant(13700): wep_key0 - hexdump(len=5): [REMOVED]
> D/wpa_supplicant(13700): priority=51 (0x33)
> D/wpa_supplicant(13700): frequency=2437 (0x985)
> D/wpa_supplicant(13700): Line: 61 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=25): 48 50 2d 50 72 69 6e 74 2d
> 34 4
> 2 2d 4c 61 73 65 72 4a 65 74 20 31 31 30 32
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=126 (0x7e)
> D/wpa_supplicant(13700): frequency=2412 (0x96c)
> D/wpa_supplicant(13700): Line: 68 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=8): 48 50 46 30 44 33 39 37
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=193 (0xc1)
> D/wpa_supplicant(13700): mode=1 (0x1)
> D/wpa_supplicant(13700): frequency=2457 (0x999)
> D/wpa_supplicant(13700): Line: 76 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=23): 69 6e 76 69 74 61 64 6f 73
> 20 6
> 1 72 65 61 74 72 65 73 20 4c 61 62 73
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=166 (0xa6)
> D/wpa_supplicant(13700): frequency=2412 (0x96c)
> D/wpa_supplicant(13700): Line: 83 - start of a new network block
> D/wpa_supplicant(13700): ssid - hexdump(len=25): 48 50 2d 50 72 69 6e 74 2d
> 37 4
> 3 2d 4c 61 73 65 72 4a 65 74 20 31 31 30 32
> D/wpa_supplicant(13700): key_mgmt: 0x4
> D/wpa_supplicant(13700): priority=167 (0xa7)
> D/wpa_supplicant(13700): frequency=2437 (0x985)
> D/wpa_supplicant(13700): Priority group 194
> D/wpa_supplicant(13700): id=3 ssid='Xerox'
> D/wpa_supplicant(13700): Priority group 193
> D/wpa_supplicant(13700): id=8 ssid='HPF0D397'
> D/wpa_supplicant(13700): Priority group 190
> D/wpa_supplicant(13700): id=5 ssid='BA WiFi'
> D/wpa_supplicant(13700): Priority group 184
> D/wpa_supplicant(13700): id=1 ssid='GABRIELA'
> D/wpa_supplicant(13700): Priority group 171
> D/wpa_supplicant(13700): id=2 ssid='Portthru'
> D/wpa_supplicant(13700): Priority group 167
> D/wpa_supplicant(13700): id=10 ssid='HP-Print-7C-LaserJet 1102'
> D/wpa_supplicant(13700): Priority group 166
> D/wpa_supplicant(13700): id=9 ssid='invitados areatres Labs'
> D/wpa_supplicant(13700): Priority group 126
> D/wpa_supplicant(13700): id=7 ssid='HP-Print-4B-LaserJet 1102'
> D/wpa_supplicant(13700): Priority group 51
> D/wpa_supplicant(13700): id=6 ssid='AREPO_ARENALES'
> D/wpa_supplicant(13700): Priority group 8
> D/wpa_supplicant(13700): id=0 ssid='versus'
> D/wpa_supplicant(13700): Priority group 7
> D/wpa_supplicant(13700): id=4 ssid='dd-wrt_vap'
> D/wpa_supplicant(13700): Reading configuration file
> '/system/etc/wifi/wpa_suppli
> cant_overlay.conf'
> D/wpa_supplicant(13700): disable_scan_offload=1
> D/wpa_supplicant(13700): p2p_disabled=1
> D/wpa_supplicant(13700): Priority group 194
> D/wpa_supplicant(13700): id=3 ssid='Xerox'
> D/wpa_supplicant(13700): Priority group 193
> D/wpa_supplicant(13700): id=8 ssid='HPF0D397'
> D/wpa_supplicant(13700): Priority group 190
> D/wpa_supplicant(13700): id=5 ssid='BA WiFi'
> D/wpa_supplicant(13700): Priority group 184
> D/wpa_supplicant(13700): id=1 ssid='GABRIELA'
> D/wpa_supplicant(13700): Priority group 171
> D/wpa_supplicant(13700): id=2 ssid='Portthru'
> D/wpa_supplicant(13700): Priority group 167
> D/wpa_supplicant(13700): id=10 ssid='HP-Print-7C-LaserJet 1102'
> D/wpa_supplicant(13700): Priority group 166
> D/wpa_supplicant(13700): id=9 ssid='invitados areatres Labs'
> D/wpa_supplicant(13700): Priority group 126
> D/wpa_supplicant(13700): id=7 ssid='HP-Print-4B-LaserJet 1102'
> D/wpa_supplicant(13700): Priority group 51
> D/wpa_supplicant(13700): id=6 ssid='AREPO_ARENALES'
> D/wpa_supplicant(13700): Priority group 8
> D/wpa_supplicant(13700): id=0 ssid='versus'
> D/wpa_supplicant(13700): Priority group 7
> D/wpa_supplicant(13700): id=4 ssid='dd-wrt_vap'
> I/wpa_supplicant(13700): rfkill: Cannot open RFKILL control device
> D/wpa_supplicant(13700): nl80211: RFKILL status not available
> D/wpa_supplicant(13700): nl80211: Using driver-based off-channel TX
> D/wpa_supplicant(13700): nl80211: Using driver-based roaming
> D/wpa_supplicant(13700): nl80211: TDLS supported
> D/wpa_supplicant(13700): nl80211: TDLS external setup
> D/wpa_supplicant(13700): nl80211: Supports Probe Response offload in AP mode
> D/wpa_supplicant(13700): nl80211: Supported vendor event: vendor_id=0x1374
> subcm
> d=10
> D/wpa_supplicant(13700): nl80211: Use separate P2P group interface (driver
> adver
> tised support)
> D/wpa_supplicant(13700): nl80211: Enable multi-channel concurrent (driver
> advert
> ised support)
> D/wpa_supplicant(13700): nl80211: Driver is new enough to support
> monitor-less m
> ode
> D/wpa_supplicant(13700): nl80211: interface wlan0 in phy phy0
> D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
> D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95
> (Ope
> ration not supported on transport endpoint)
> D/wpa_supplicant(13700): nl80211: Try mode change after setting interface
> down
> D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
> D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95
> (Ope
> ration not supported on transport endpoint)
> D/wpa_supplicant(13700): nl80211: Interface mode change to 2 from 0 failed
> E/wpa_supplicant(13700): nl80211: Could not configure driver to use managed
> mode
>
> D/wpa_supplicant(13700): netlink: Operstate: linkmode=0, operstate=6
> D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
> D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95
> (Ope
> ration not supported on transport endpoint)
> D/wpa_supplicant(13700): nl80211: Try mode change after setting interface
> down
> D/wpa_supplicant(13700): nl80211: Set mode ifindex 22 iftype 2 (STATION)
> D/wpa_supplicant(13700): nl80211: Failed to set interface 22 to mode 2: -95
> (Ope
> ration not supported on transport endpoint)
> D/wpa_supplicant(13700): nl80211: Interface mode change to 2 from 0 failed
> E/wpa_supplicant(13700): wlan0: Failed to initialize driver interface
> D/wpa_supplicant(13700): Failed to add interface wlan0
> D/wpa_supplicant(13700): wlan0: Cancelling scan request
> D/wpa_supplicant(13700): wlan0: P2P: Station mode scan operation not pending
> any
> more (sta_scan_pending=0 p2p_cb_on_scan_complete=0)
> D/wpa_supplicant(13700): wlan0: Cancelling authentication timeout
> D/wpa_supplicant(13700): Get randomness: len=20 entropy=0
> D/wpa_supplicant(13700): random from os_get_random - hexdump(len=20):
> [REMOVED]
> D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
> D/wpa_supplicant(13700): random from internal pool - hexdump(len=16):
> [REMOVED]
> D/wpa_supplicant(13700): random_mix_pool - hexdump(len=20): [REMOVED]
> D/wpa_supplicant(13700): random from internal pool - hexdump(len=16):
> [REMOVED]
> D/wpa_supplicant(13700): mixed random - hexdump(len=20): [REMOVED]
> D/wpa_supplicant(13700): random: Updated entropy file
> /data/misc/wifi/entropy.bi
> n (own_pool_ready=2)
> E/WifiHW ( 210): Supplicant not running, cannot connect
> E/WifiHW ( 210): Supplicant not running, cannot connect
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver
> target
> [OS-Agent]
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver
> tar
> get [OS-Agent]
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver
> tar
> get [OS-Agent]
> V/WLAN_PSA( 214): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
> E/WifiHW ( 210): Supplicant not running, cannot connect
> E/WifiHW ( 210): Supplicant not running, cannot connect
> E/WifiHW ( 210): Supplicant not running, cannot connect
> I/Gecko ( 210): -*- WifiWorker component: Supplicant died!
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver
> target
> [OS-Agent]
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver
> tar
> get [OS-Agent]
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver
> tar
> get [OS-Agent]
> V/WLAN_PSA( 214): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver
> target
> [OS-Agent]
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver
> tar
> get [OS-Agent]
> E/QCALOG ( 343): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver
> tar
> get [OS-Agent]
> V/WLAN_PSA( 214): NL MSG, len[048], NL type[0x11] WNI type[0x5050] len[028]
Thanks for providing this. It seems the wpa_supplicant didn't run normally
and with a weird pid for unknown reason.
Can you attach the init.qcom.rc and every file under path "etc/wifi/"?
Not sure if any of these file is corrupted.
Thanks!
|
|
Reporter | |
Comment 26•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #25)
> Thanks for providing this. It seems the wpa_supplicant didn't run normally
> and with a weird pid for unknown reason.
>
> Can you attach the init.qcom.rc and every file under path "etc/wifi/"?
> Not sure if any of these file is corrupted.
>
> Thanks!
I'm sorry but I don't understand what you are asking for. If you could please provide me some step by step instructions to obtain the init.qcom.rc and every file under path "etc/wifi/", I would greatly appreciate it as I want to do whatever it takes to move the bug forward and hopefully fix it soon. Please remember I'm on Windows so any Linux/Mac commands won't work for me. Also, please consider that while I'm a very keen QA tester, I'm no dev nor a thechie person, that's why I'm asking you for step by step guidance to be able to get the information you need.
|
|
||
Comment 27•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #26)
> (In reply to Henry Chang [:henry] from comment #25)
>
> > Thanks for providing this. It seems the wpa_supplicant didn't run normally
> > and with a weird pid for unknown reason.
> >
> > Can you attach the init.qcom.rc and every file under path "etc/wifi/"?
> > Not sure if any of these file is corrupted.
> >
> > Thanks!
>
> I'm sorry but I don't understand what you are asking for. If you could
> please provide me some step by step instructions to obtain the init.qcom.rc
> and every file under path "etc/wifi/", I would greatly appreciate it as I
> want to do whatever it takes to move the bug forward and hopefully fix it
> soon. Please remember I'm on Windows so any Linux/Mac commands won't work
> for me. Also, please consider that while I'm a very keen QA tester, I'm no
> dev nor a thechie person, that's why I'm asking you for step by step
> guidance to be able to get the information you need.
Hi,
I assume you managed to run adb on your windows so following is the steps:
1) adb pull init.qcom.rc
2) adb pull /etc/wifi/
Please attach the files and that might be helpful! Thnaks!
|
|
Reporter | |
Comment 28•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #27)
> Hi,
>
> I assume you managed to run adb on your windows so following is the steps:
>
> 1) adb pull init.qcom.rc
> 2) adb pull /etc/wifi/
>
> Please attach the files and that might be helpful! Thnaks!
Many thanks for your quick reply!
Yes, I can run adb so I'll do what you need as soon as I get back home from work. Thanks again!
|
|
Reporter | |
Comment 29•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #27)
Here is what I obtained:
1) adb pull init.qucom.rc
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Users\Gabriela>adb pull init.qcom.rc
adb server is out of date. killing...
* daemon started successfully *
815 KB/s (25065 bytes in 0.030s)
C:\Users\Gabriela>adb pull init.qcom.rc
2039 KB/s (25065 bytes in 0.012s)
2) adb pull /etc/wifi/
C:\Users\Gabriela>adb pull /etc/wifi/
pull: building file list...
pull: /etc/wifi/wpa_supplicant_overlay.conf -> ./wpa_supplicant_overlay.conf
pull: /etc/wifi/wpa_supplicant_ath6kl.conf -> ./wpa_supplicant_ath6kl.conf
pull: /etc/wifi/wpa_supplicant.conf -> ./wpa_supplicant.conf
pull: /etc/wifi/p2p_supplicant_overlay.conf -> ./p2p_supplicant_overlay.conf
pull: /etc/wifi/WCNSS_qcom_cfg.ini -> ./WCNSS_qcom_cfg.ini
5 files pulled. 0 files skipped.
496 KB/s (39624 bytes in 0.078s)
C:\Users\Gabriela>
I'm not sure it's what you asked for though. I obtained the above while trying tu turn on the wifi without success. If it's not what you need, please explain me again.
Many thanks!
|
|
Reporter | |
Comment 30•11 years ago
|
||
Henry, where you able to check if the last logs I added where correct/useful for you?
Changing the status to critical because I still have the issue, lots of people may be affected and wifi not working is a very important issue.
Severity: major → critical
|
|
Reporter | |
Comment 31•11 years ago
|
||
I should add that the only workaround is resetting the phone. I have to do it every time I want to connect at different places: at work, at a restaurant, at home and at any other place with a wifi network. The result is a drained battery which is a huge problem in itself.
|
|
||
Comment 32•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #31)
> I should add that the only workaround is resetting the phone. I have to do
> it every time I want to connect at different places: at work, at a
> restaurant, at home and at any other place with a wifi network. The result
> is a drained battery which is a huge problem in itself.
Hi,
What we need is the files :p Could you please attach the files you pulled?
Pulling those files whenever your wifi is not working.
Please also pull those files after resetting the phone.
Also, do you have another flame for reference?
Sorry for late response since we were all in a business trip last week.
Thanks!
|
|
Reporter | |
Comment 33•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #32)
> (In reply to Gabriela [:gaby2300] from comment #31)
> > I should add that the only workaround is resetting the phone. I have to do
> > it every time I want to connect at different places: at work, at a
> > restaurant, at home and at any other place with a wifi network. The result
> > is a drained battery which is a huge problem in itself.
>
> Hi,
> What we need is the files :p Could you please attach the files you pulled?
> Pulling those files whenever your wifi is not working.
> Please also pull those files after resetting the phone.
> Also, do you have another flame for reference?
>
> Sorry for late response since we were all in a business trip last week.
>
> Thanks!
No problem for the late response :)
I'm sorry but I don't understand what you mean when you ask me to "pull" the files and attach them. I thought I had already done this but it seems not, so I suppose I did something wrong. Please give some step by step instructions so I can do what you need. I would greatly appreciate them!
Many thanks!
|
|
||
Comment 34•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #33)
> (In reply to Henry Chang [:henry] from comment #32)
> > (In reply to Gabriela [:gaby2300] from comment #31)
> > > I should add that the only workaround is resetting the phone. I have to do
> > > it every time I want to connect at different places: at work, at a
> > > restaurant, at home and at any other place with a wifi network. The result
> > > is a drained battery which is a huge problem in itself.
> >
> > Hi,
> > What we need is the files :p Could you please attach the files you pulled?
> > Pulling those files whenever your wifi is not working.
> > Please also pull those files after resetting the phone.
> > Also, do you have another flame for reference?
> >
> > Sorry for late response since we were all in a business trip last week.
> >
> > Thanks!
>
> No problem for the late response :)
>
> I'm sorry but I don't understand what you mean when you ask me to "pull" the
> files and attach them. I thought I had already done this but it seems not,
> so I suppose I did something wrong. Please give some step by step
> instructions so I can do what you need. I would greatly appreciate them!
>
> Many thanks!
Hi,
You are supposed to have downloaded files in C:\Users\Gabriela
like init.qcom.rc, wpa_supplicant_overlay.conf, ..., which are
the files we need!
Thanks!
|
|
Reporter | |
Comment 35•11 years ago
|
||
Sorry for the rather stupid question but.... I suppose I must search for those files is in my PC and not in the phone. Am I right? If so, I'll do it later when I get back home.
|
|
||
Comment 36•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #35)
> Sorry for the rather stupid question but.... I suppose I must search for
> those files is in my PC and not in the phone. Am I right? If so, I'll do it
> later when I get back home.
You got it :)
|
|
Reporter | |
Comment 37•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #36)
You got it :)
Right, I'll do it later then. Thanks!
|
|
Reporter | |
Comment 38•11 years ago
|
||
The adb log
|
|
Reporter | |
Comment 39•11 years ago
|
||
|
|
Reporter | |
Comment 40•11 years ago
|
||
|
|
Reporter | |
Comment 41•11 years ago
|
||
|
|
Reporter | |
Comment 42•11 years ago
|
||
|
|
Reporter | |
Comment 43•11 years ago
|
||
|
|
Reporter | |
Comment 44•11 years ago
|
||
|
|
Reporter | |
Comment 45•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #34)
Hi Henry,
I've attached the files, I hope they are the ones you need this time! Thanks!
|
|
||
Comment 46•11 years ago
|
||
Yes they are! Thanks! But they look like the fresh ones. Did you pull them
at the time the issue happening?
|
|
Reporter | |
Comment 47•11 years ago
|
||
I'm sorry for the delay.
Yes, I did! As I explained before, I have the issue every time I want to turn on the wifi at home or anywhere else.
I think I don't quite understand your question, could you please explain it some further? Thanks!
|
|
||
Comment 48•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #47)
> I'm sorry for the delay.
>
> Yes, I did! As I explained before, I have the issue every time I want to
> turn on the wifi at home or anywhere else.
>
> I think I don't quite understand your question, could you please explain it
> some further? Thanks!
Because I was guessing the config files was corrupted and caused wpa_supplicant
cannot turn on. Well, can you get another flame to see if it's a common issue
in your environment or a specific hardware issue of your phone?
Thnaks!
|
|
Reporter | |
Comment 49•11 years ago
|
||
Is there a way to fix the config files's corruption if you think that may be?
I don't think I'll be able to get yet another Flame. This one is my second device. The first one I received powered off by it's self so often it wasn't reliable enough to use it as my primary phone. It's been difficult enough to get this second one, so I doubt very much the availability of a third one.
I'd like to know why you think it may be a hardware problem and not the phone's wifi issue? Why would it be a common issue in my environment? It's the only device I have this problem with. I never have the wifi problem with neither of my other phones (other Firefox OS phones Chinese phone, Samsung Galaxy SII) nor with my netbook. So surely it's not my environment?
Many thanks!!
|
|
||
Comment 50•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #49)
> Is there a way to fix the config files's corruption if you think that may be?
>
> I don't think I'll be able to get yet another Flame. This one is my second
> device. The first one I received powered off by it's self so often it wasn't
> reliable enough to use it as my primary phone. It's been difficult enough to
> get this second one, so I doubt very much the availability of a third one.
>
> I'd like to know why you think it may be a hardware problem and not the
> phone's wifi issue? Why would it be a common issue in my environment? It's
> the only device I have this problem with. I never have the wifi problem with
> neither of my other phones (other Firefox OS phones Chinese phone, Samsung
> Galaxy SII) nor with my netbook. So surely it's not my environment?
>
> Many thanks!!
Hi,
Your files all look good so it may not due to the corruption.
Besides, I am not saying there's anything wrong with your environment.
Probably our code/hardware has something conflict to your environment.
If you are not able to get another phone or mail the device to us,
could you grab the log again but make it as complete as possible?
Run 'adb logcat > log.txt' from the very beginning with wifi log enabled.
Thanks!
|
|
Reporter | |
Comment 51•11 years ago
|
||
(In reply to Henry Chang [:henry] from comment #50)
> Hi,
>
> Your files all look good so it may not due to the corruption.
Good!
> Besides, I am not saying there's anything wrong with your environment.
> Probably our code/hardware has something conflict to your environment.
Understood!
>
> If you are not able to get another phone or mail the device to us,
I can't for 2 reasons: it would be too expensive and I wouldn't be able to receive it back due to Argentinian Custom's laws.
> could you grab the log again but make it as complete as possible?
> Run 'adb logcat > log.txt' from the very beginning with wifi log enabled.
So, I open the command window and type "adb logat > log.txt" just like that, in the same line without the quotes?
Many thanks to you for your patience!!!!
|
|
||
Comment 52•11 years ago
|
||
it's been a while after the bug was reported and engineers are trying hard but can not reproduce. qawanted again to check if this still happens in latest 2.2 master, thank you.
Whiteboard: qawanted
|
|
Reporter | |
Comment 53•11 years ago
|
||
The last time I checked was using the December 16 OTA update and the bug still reproduced.
I'm sorry but I can't update to the latest build 2.2 yet due to https://bugzilla.mozilla.org/show_bug.cgi?id=1093827.
I use Windows so it won't be easy for me to flash the base image and 2.2.
I will do it as soon as the above bug is fixed.
|
|
Reporter | |
Comment 54•11 years ago
|
||
I have updated to today's OTA build. I'm still having the issue no matter where I try to use the wifi.
|
|
||
Comment 55•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #51)
> (In reply to Henry Chang [:henry] from comment #50)
>
> > Hi,
> >
> > Your files all look good so it may not due to the corruption.
> Good!
>
> > Besides, I am not saying there's anything wrong with your environment.
> > Probably our code/hardware has something conflict to your environment.
> Understood!
> >
> > If you are not able to get another phone or mail the device to us,
> I can't for 2 reasons: it would be too expensive and I wouldn't be able to
> receive it back due to Argentinian Custom's laws.
>
> > could you grab the log again but make it as complete as possible?
> > Run 'adb logcat > log.txt' from the very beginning with wifi log enabled.
> So, I open the command window and type "adb logat > log.txt" just like that,
> in the same line without the quotes?
>
> Many thanks to you for your patience!!!!
Happy new year :)
Yes. Running 'adb logcat > log.txt' would redirect all output the log to file
log.txt. Please remember to enable wifi logging first in the developer options
just as what you did before.
Thanks!
|
|
||
Comment 56•11 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #54)
> I have updated to today's OTA build. I'm still having the issue no matter
> where I try to use the wifi.
Hi Gabriela, can you follow the guide in [1] to update your base image in Windows? You should install ADB and usb driver in you Windows. If you have problems install them, please following the guide in [2].
Let's us know if it helps to recover wifi function of your Flame device.
[1] https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame/Updating_your_Flame
[2] https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame/Initial_setup
|
|
Reporter | |
Comment 57•11 years ago
|
||
Hi Vincent,
1) I already have base image v188 in my Flame.
2) I already have installed Firefox OS 2.2.
I'm sorry but the base image and the OS have been installed for me because I'm no techie and installing these using Windows isn't easy for me. I don´t want to brick the phone because if I do, I'll have to ask someone else to reflash it for me.
I have yet to run 'adb logcat > log.txt' to obtain all output the log to file log.txt.
as Henry suggested. I'll do it over the weekend. Let's hope it will help to understand why I still have the issue.
|
|
||
Comment 58•11 years ago
|
||
Triage: remove the nom first as can not reproduce.
Severity: critical → normal
blocking-b2g: 2.2? → ---
|
|
Reporter | |
Comment 59•11 years ago
|
||
I'm sorry but I changed the state to critical because I still have the issue and I think it's a very important problem.
Severity: normal → critical
|
|
Reporter | |
Comment 60•11 years ago
|
||
> > (In reply to Henry Chang [:henry] from comment #50)
> Yes. Running 'adb logcat > log.txt' would redirect all output the log to file
> log.txt. Please remember to enable wifi logging first in the developer
> options just as what you did before.
>
> Thanks!
I'm very sorry for my delay!
I wanted to run 'adb logcat > log.txt today but I couldn't reproduce the issue. Maybe it's fixed in today's OTA update? I sincerely hope so! I'll try tomorrow at my work place and then at home again and I'll let you know.
Many thanks!!!
|
|
Reporter | |
Comment 61•11 years ago
|
||
|
|
Reporter | |
Comment 62•11 years ago
|
||
Today I was able to repro the bug at work and at home. I ran adb logcat > log.txt at home, the result was very long so I attached here. I hope it helps you discover the problem, many thanks!
|
|
Reporter | |
Comment 63•10 years ago
|
||
(In reply to Gabriela [:gaby2300] from comment #60)
> > > (In reply to Henry Chang [:henry] from comment #50)
>
>
> > Yes. Running 'adb logcat > log.txt' would redirect all output the log to file
> > log.txt. Please remember to enable wifi logging first in the developer
> > options just as what you did before.
> >
> > Thanks!
Hello Henry, could you please check the log I added in comment 61 as I still have the issue? I would greatly appreciate it!
> Many thanks!!!
|
|
||
Updated•10 years ago
|
Flags: needinfo?(nhirata.bugzilla)
I'm not sure exactly how to reproduce this issue. Henry, Since she's a contributor it would mean that she would have to be on a base build and then OTA. I think we need to know her base build.
Gabriela, can you give the output of : adb shell getprop ro.bootloader
Please?
Henry, it looks like her interface failed:
D/wpa_supplicant( 8571): nl80211: Set mode ifindex 22 iftype 2 (STATION)
D/wpa_supplicant( 8571): nl80211: Failed to set interface 22 to mode 2: -95 (Operation not supported on transport endpoint)
D/wpa_supplicant( 8571): nl80211: Try mode change after setting interface down
D/wpa_supplicant( 8571): nl80211: Set mode ifindex 22 iftype 2 (STATION)
D/wpa_supplicant( 8571): nl80211: Failed to set interface 22 to mode 2: -95 (Operation not supported on transport endpoint)
D/wpa_supplicant( 8571): nl80211: Interface mode change to 2 from 0 failed
E/wpa_supplicant( 8571): wlan0: Failed to initialize driver interface
D/wpa_supplicant( 8571): Failed to add interface wlan0
D/wpa_supplicant( 8571): wlan0: Cancelling scan request
D/wpa_supplicant( 8571): wlan0: P2P: Station mode scan operation not pending anymore (sta_scan_pending=0 p2p_cb_on_scan_complete=0)
D/wpa_supplicant( 8571): wlan0: Cancelling authentication timeout
Flags: needinfo?(nhirata.bugzilla)
Flags: needinfo?(hchang)
Flags: needinfo?(gmontagu)
|
|
Reporter | |
Comment 65•10 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #64)
> I'm not sure exactly how to reproduce this issue. Henry, Since she's a
> contributor it would mean that she would have to be on a base build and then
> OTA. I think we need to know her base build.
>
> Gabriela, can you give the output of : adb shell getprop ro.bootloader
> Please?
Naoki, of course! Its the following:
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Users\Gabriela>adb shell getprop ro.bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
L1TC000118D0
Flags: needinfo?(gmontagu)
|
|
||
Comment 66•10 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #64)
> I'm not sure exactly how to reproduce this issue. Henry, Since she's a
> contributor it would mean that she would have to be on a base build and then
> OTA. I think we need to know her base build.
>
> Gabriela, can you give the output of : adb shell getprop ro.bootloader
> Please?
>
> Henry, it looks like her interface failed:
>
> D/wpa_supplicant( 8571): nl80211: Set mode ifindex 22 iftype 2 (STATION)
> D/wpa_supplicant( 8571): nl80211: Failed to set interface 22 to mode 2: -95
> (Operation not supported on transport endpoint)
> D/wpa_supplicant( 8571): nl80211: Try mode change after setting interface
> down
> D/wpa_supplicant( 8571): nl80211: Set mode ifindex 22 iftype 2 (STATION)
> D/wpa_supplicant( 8571): nl80211: Failed to set interface 22 to mode 2: -95
> (Operation not supported on transport endpoint)
> D/wpa_supplicant( 8571): nl80211: Interface mode change to 2 from 0 failed
> E/wpa_supplicant( 8571): wlan0: Failed to initialize driver interface
> D/wpa_supplicant( 8571): Failed to add interface wlan0
> D/wpa_supplicant( 8571): wlan0: Cancelling scan request
> D/wpa_supplicant( 8571): wlan0: P2P: Station mode scan operation not pending
> anymore (sta_scan_pending=0 p2p_cb_on_scan_complete=0)
> D/wpa_supplicant( 8571): wlan0: Cancelling authentication timeout
You can re-pro the bug by allowing the device to go in deep sleep mode.
|
|
||
Comment 67•10 years ago
|
||
This issue can be usually "solved" by adding the following line to the /system/etc/wifi/wpa_supplicant_overlay.conf
tdls_external_control=1
else hardware issue.
Flags: needinfo?(gmontagu)
|
|
Reporter | |
Comment 68•10 years ago
|
||
My base image is the following:
C:\Users\Gabriela>adb shell getprop ro.bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
L1TC000118D0
Flags: needinfo?(gmontagu)
|
|
Reporter | |
Comment 69•10 years ago
|
||
(In reply to u548974 from comment #67)
> This issue can be usually "solved" by adding the following line to the
> /system/etc/wifi/wpa_supplicant_overlay.conf
>
> tdls_external_control=1
>
> else hardware issue.
I don't know how to do this, could you please explain me step by step? I would really appreciate it!
|
||
Comment 70•10 years ago
|
||
(In reply to u548974 from comment #67)
> This issue can be usually "solved" by adding the following line to the
> /system/etc/wifi/wpa_supplicant_overlay.conf
> tdls_external_control=1
> else hardware issue.
seems to be a solution for my issue:
Flame (fxos2.6 or 2.5 or 2.0, new base images) would connect to certain wifi access points but would not connect to certain other wifi access points because "out of range" although in same small room with wifi router (where other devices do connect without problems, e.g. inari or androids).
Procedure with linux connected to flame via usb:
$ adb root
$ adb pull /system/etc/wifi/wpa_supplicant_overlay.conf
$ echo "tdls_external_control=1" >> wpa_supplicant_overlay.conf
$ adb remount
$ adb push wpa_supplicant_overlay.conf /system/etc/wifi/wpa_supplicant_overlay.conf
$ adb reboot
No connection problems since
|
|
Reporter | |
Comment 71•10 years ago
|
||
(In reply to m from comment #70)
> (In reply to u548974 from comment #67)
> > This issue can be usually "solved" by adding the following line to the
> > /system/etc/wifi/wpa_supplicant_overlay.conf
> > tdls_external_control=1
> > else hardware issue.
> seems to be a solution for my issue:
> Flame (fxos2.6 or 2.5 or 2.0, new base images) would connect to certain wifi
> access points but would not connect to certain other wifi access points
> because "out of range" although in same small room with wifi router (where
> other devices do connect without problems, e.g. inari or androids).
>
> Procedure with linux connected to flame via usb:
> $ adb root
> $ adb pull /system/etc/wifi/wpa_supplicant_overlay.conf
> $ echo "tdls_external_control=1" >> wpa_supplicant_overlay.conf
> $ adb remount
> $ adb push wpa_supplicant_overlay.conf
> /system/etc/wifi/wpa_supplicant_overlay.conf
> $ adb reboot
> No connection problems since
Good to know!
!
I am on Windows though, I would greatly appreciate if you could please give me some similar procedure for my OS!
|
|
||
Comment 72•10 years ago
|
||
(In reply to m from comment #70)
> No connection problems since
Have to draw back, sorry! Yesterday all went well after "reconfiguring" wpa_supplicant as described, today (maybe after wifi router restart) same issue as before: Out of range syndrome at specific access points.
Strongly believe that it is a flame driver/wifi configuration issue in combination with specific routers or router configurations because our 3 flames behave identically and other devices have no connection issues.
Trying to keep on fishing in the mud ...
(In reply to m from comment #70)
> I am on Windows though ...
The next windows system is ~25 years away :-) If you have a shell and adb the procedure may be exactly the same
|
|
||
Comment 73•10 years ago
|
||
Hypothesis after a few hours of mud fishing:
Flame won't (always?) connect to wifi routers in 2.4 GHz band above channel 11 (> 2462 GHz).
Observation: A "flame incompatible" wifi-router was set to automatic channel search in 2.4 GHz band and had chosen channel 13 (2472 GHz). After manually setting many different channels the range 2412 GHz to 2462 GHz yielded stable connections. Can this be confirmed?
|
|
||
Comment 74•10 years ago
|
||
4-digit figures above in MHz of course, sorry
|
|
||
Comment 75•10 years ago
|
||
OK, facts:
Trying to connect Flame to an old D-Link router (with original firmware) in Germany on wifi channel 12 or 13 is unsuccessful whereas channel 1 to 11 connect.
Unsuccessful means, after activating wi-fi button on flame,
- if network is unknown, it is not shown in the list of availible networks,
- if network is known, it is shown as "Not in range".
Log snippet of connection attempt showing unplausibel regulatory information resulting (?!) in not connecting on channel 12/13 (but connecting on channel 1-11):
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: driver param='(null)'
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: Regulatory information - country=US
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: 2402-2472 @ 40 MHz
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: 5170-5250 @ 80 MHz
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: 5250-5330 @ 80 MHz
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: 5490-5600 @ 80 MHz
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: 5650-5710 @ 40 MHz
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: 5710-5835 @ 80 MHz
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: 57240-63720 @ 2160 MHz
01-02 22:38:02.988 D/wpa_supplicant( 9324): nl80211: Added 802.11b mode based on 802.11g information
Tests with different Fxos-device (Inari Fxos 2.0) were positiv (means device connects without flaws).
Tests with different router (newish Fritzbox) on channel 12 and 13 were positiv (means flame connects without flaws). Corresponding log snippet of successful connection:
01-03 14:52:06.037 D/wpa_supplicant( 5293): wlan0: Event CHANNEL_LIST_CHANGED (31) received
01-03 14:52:06.037 D/wpa_supplicant( 5293): nl80211: Regulatory information - country=DE
01-03 14:52:06.037 D/wpa_supplicant( 5293): nl80211: 2400-2483 @ 40 MHz
01-03 14:52:06.037 D/wpa_supplicant( 5293): nl80211: 5150-5250 @ 80 MHz
01-03 14:52:06.037 D/wpa_supplicant( 5293): nl80211: 5250-5350 @ 80 MHz
01-03 14:52:06.037 D/wpa_supplicant( 5293): nl80211: 5470-5725 @ 80 MHz
01-03 14:52:06.037 D/wpa_supplicant( 5293): nl80211: 57240-65880 @ 2160 MHz
01-03 14:52:06.037 D/wpa_supplicant( 5293): nl80211: Added 802.11b mode based on 802.11g information
Tested with
- Flame, Fxos 2.5, newest base image, Platform 45.0a1, Build-Id 20151105004500
- Flame, Fxos 2.6, newest base image, Platform 46.0a1, Build-Id 20160104150223
- ZTE Open, Fxos 2.0, newest Mexmod build
Assumptions and Questions:
It seems as if "plausibility" of routers wifi configuration is checked by flame. Can this be possible? If so is there a way to remove the devices responsibility for "maybe odd or wrong" router configurations? If so a reasonable amount of wifi bugs may be adressed.
I'm new to Bugzilla, sorry for mistakes and please advise me to file a new bug or add further infos if required. Dankeschoen :)
|
||
Comment 76•9 years ago
|
||
Clean needinfo request since Henry is not working on Wi-Fi and FxOS now.
Please raise the needinfo request again if necessary.
Flags: needinfo?(hchang)
|
||
Comment 77•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•