Closed
Bug 1000081
Opened 11 years ago
Closed 7 years ago
Entering power saving mode kills wifi
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: past, Assigned: vchang)
Details
Attachments
(2 files)
Entering power saving mode will disable wifi as expected, but after disabling power saving mode again I never get usable wifi until I reboot the phone. Supplicant seems to die in the attached logcat.
This has been going on for the past few days on my Peak running the latest Geeksphone nightly builds (probably since 4/18 or so). It took me a long time to pinpoint the cause, because I had enabled the setting to enter power saving mode when battery was down to 25%. This would often happen at night and in the morning I had to reboot to get wifi back.
Reporter | ||
Comment 1•11 years ago
|
||
Sometimes even rebooting doesn't fix the issue. Seeing issues with netd in this log, I tried teh following to no avail:
adb shell stop netd
adb shell start netd
I saw some promising log messages, but the settings app kept spinning in the "Initializing..." state:
I/Gonk ( 129): Error connecting to : netd (Connection refused) - will retry
I/Gonk ( 129): Fail to connect to Netd
I/Gonk ( 129): Error connecting to : netd (No such file or directory) - will retry
I/Gonk ( 129): Fail to connect to Netd
I/Gonk ( 129): Connected to netd
Assignee | ||
Comment 2•11 years ago
|
||
Which device did you use ? Hamachi ? The wifi enable/disable is controlled by settings "wifi.enabled". Maybe you can reference the code snippet here.
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/wifi.js
Connect to netd error should not relate to wifi. Netd is used for wifi hotspot and network statistic stuff.
According to the log "logcat after reboot", it seems netd is crash due to invalid netd command. Maybe the command is not supported in this version.
/BandwidthController( 135): No such iface rmnet0 to delete
E/BandwidthController( 135): Need to have a prior interface quota set to set an alert
F/libc ( 135): Fatal signal 11 (SIGSEGV) at 0x11cf19e9 (code=1)
Assignee | ||
Comment 3•11 years ago
|
||
I don't have peak on hand, but I can help to check it with my unagi and see if I can reproduce the problem.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → vchang
Comment 4•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
•