Originally Posted by rav4kar
Hi elherr, you are a great deal here to help us on network side.as I previously posted many times, my case is similar to that of burgess_boy! So, are these work wifi's ( which we don't have any control over at work..use it or loose it policy!) misconfigured or configured correctly for some... some... reasons such as security probes or anything . Throw us some ideas what we can go and tell network engineers at work..or how we can show them this problem on our phone while phone's connected on wifi and adb@adndroid#
*** Using a packet sniffer (e.g., Shark for Root) on a company network is typically frowned upon. Frowned upon as in: You-Have-Been-Sniffing-My-Network-WIth-A-Rooted-Device--I-WILL-KILL-YOU-NOW! ***
Having said that, you can run Shark and look for chatty broadcast/multicast in your capture. Unfortunately, a good portion of that traffic may be required by other hosts (computers) for normal operations, so it cannot be blocked on the network. There are too many variations in network design to say for certain.
What may work out is developing netfilter (iptables in userspace) rules to block some of the traffic at the phone interface. I have not played with this yet. If we can block traffic at the WLAN interface all is good. If the traffic has to be processed by the kernel then the exercise would be pointless, as that would mean you would still be generating wakelock just to have the kernel drop the packet.
As I've said before, I'm still learning how Android works, so take what I am saying with a grain of salt -- aside from the sniffer warning at the beginning. If you want to see a network admin develop cloven hooves, a forked tail, and glowing eyes, tell him you've been running a sniffer on his network.
Originally Posted by cyberpunk627
Guys multipdp and wlan rx and mail app (exchange polling every 15 mins, sync disabled to try and reduce this problem) are killing me with wake lock time and count.
I already disabled IPv6 on every networked PC and on my phone, and turned off dhcp (that god rid of the dhcp wake lock it seems...).
Any other suggestion? How to track which app is connecting so often and giving problems? I already ditched Facebook for friend caster..
Thanks a lot!
I have my domain hosted on Google and am syncing all services (Blogger, Browser, Calendar, Chrome Beta, Contacts, Currents, Drive, Mail, Photos, G+, etc). I also have Exchange ActiveSync Contacts, Mail, & Calendar active. On wifi I'm getting about 90% deep sleep during idle times. Obviously, when I have a truckload of email hitting my inbox this percentage declines. I'm pretty happy with this figure.
One thing that I did notice that was causing more wakes on wifi was what appeared to be Google location service scanning for nearby access points. I disabled Google location service and significantly improved sleep times. This was on CM9 0519.
DHCP should not cause issues unless the lease time is insanely short. I've set my lease time to two hours with WPA2 TKIP group rekey set to 10 minutes.
On HSDPA or 3G, my sleep time is running at 75% give or take. secril_fmt-interface and l2_hsic wakelock seem to be a couple of the top talkers. From what I am reading, 'secril_fmt-interface' is part of the Radio Interface Layer (RIL), and l2_hsic is (guessing here...) Layer 2 HSIC (High Speed Inter-Chip). HSIC is a variation on USB and is used by CPU to talk to various peripheral devices, including the phone's baseband... Bah! Learning Android is like drinking from the proverbial firehose.
If you have Shark for root installed, capture WLAN traffic during an idle period. See post #1 for instructions. I'd be happy to take a look at the capture.