maemo.org Bugzilla – Bug 1170
Excessive power consumption with certain wlan access points
Last modified: 2008-06-03 20:59:06 UTC
You need to
before you can comment on or make changes to this bug.
With some wlan access points the device consumes excessive power even when
idle. The device is noticeably warm to the touch and consumes a full battery
within a couple of idle hours. This problem appeared with my Zyxel P660HW-61
after updating to the latest firmare V3.40(PE.11). The problem occurs with
both b/g modes and both static IPs and DHCP. The N800 has the latest firmware
OS 2007 edition v. 3.2007.10-7. The wlan is configured to basic g-only mode
Excessive N800 power consumption in connection with WLANs has been confirmed by
others and discussed in the newsgroup - here's a link to the thread:
Accepted and reported to upstream developers
Are the count of bytes sent and received (shown in Connection manager) steadily
increasing when you're connected to this network? I have observed N800s getting
warm while they flood the network with superfluous DHCP requests (bug #1627).
Sorry, I didn't notice that you said it happens with a static IP too; disregard
my last message.
Just thought I would add some more notes to which may help with detecting this
I can confirm this is present in: OS2008 2.2007.51-3 on an N800
The router in question is: Linksys BEFW11S4 (B only)
The internet works fine, and connects first time. Signal strength is also very
good, and there's no noticeable lag when viewing web pages.
Am I surrounded by access points with a different SID (multiple with same SID).
The one I'm connected to is a single access point.
In other locations I have been connected to wireless fine when surrounded by
other access points (but not multiple with same SID).
Also happened with ZyXEL P-660HW-D1 where a firmware update fixed the
Nearly all cases describing these problems that I have found turned out to be a
problem of the access point violating WLAN specs.
According to the internal ticket, Nokia people worked on a workaround, but
"applying it might break something else, would violate the spec and would solve
the problem only partially. Thus marking this bug as wontfix."