[Galaxy Note 4 General] hoangbv15:
I have a N910H and I'm experiencing the exact same problem. My phone's battery drains only 3-5% a night without wifi being turned on. With wifi on, it flushes a whooping 30% down the toilet. I guess this problem is not only restricted to N910C users.

I followed the post about using adb shell dumpstat, and I think I found something interesting.

Here is a list of all wake locks during the night with wifi on:

All kernel wake locks:

Kernel Wake lock PowerManagerService.WakeLocks: 1m 46s 734ms (0 times) realtime

Kernel Wake lock wlan_rx_wake: 12s 583ms (20 times) realtime

Kernel Wake lock sec-battery-vbus: 5s 799ms (1 times) realtime

Kernel Wake lock ssp_wake_lock: 1s 843ms (0 times) realtime

Kernel Wake lock wlan_ctrl_wake: 1s 87ms (1 times) realtime

Kernel Wake lock sec-battery-monitor: 820ms (4 times) realtime

Kernel Wake lock charger->chgin: 708ms (1 times) realtime

Kernel Wake lock usb_notify : 595ms (1 times) realtime

Kernel Wake lock dwc3-otg : 594ms (1 times) realtime

Kernel Wake lock l2_hsic : 322ms (1 times) realtime

Kernel Wake lock PowerManagerService.Broadcasts: 227ms (0 times) realtime

Kernel Wake lock alarm : 144ms (21 times) realtime

Kernel Wake lock wlan_wake : 78ms (236 times) realtime

Kernel Wake lock NETLINK : 47ms (394 times) realtime

Kernel Wake lock battery : 7ms (4 times) realtime

Kernel Wake lock sec-battery-cable: 5ms (1 times) realtime

Kernel Wake lock eventpoll : 4ms (396 times) realtime

Kernel Wake lock 13800000.decon_fb: 4ms (0 times) realtime

Kernel Wake lock PowerManagerService.Display: 4ms (0 times) realtime

Kernel Wake lock KeyEvents : 1ms (3 times) realtime

Kernel Wake lock binder : 1ms (2 times) realtime

All partial wake locks:

Wake lock u0a7 DocumentService WakeLock: 1m 31s 519ms (0 times) realtime

Wake lock u0a39 c: 13s 0ms (6 times) realtime

Wake lock 1000 TimaService: 1s 116ms (1 times) realtime

Wake lock u0a225 Poweramp scan: 339ms (2 times) realtime

Wake lock u0a39 *alarm*: 187ms (7 times) realtime

Wake lock u0a64 CalendarIntentService: 139ms (1 times) realtime

Wake lock u0a14 Event Log Service: 71ms (1 times) realtime

Wake lock 1000 *alarm*: 64ms (2 times) realtime

Wake lock u0a112 *alarm*: 61ms (3 times) realtime

Wake lock u0a39 b: 46ms (22 times) realtime

Wake lock u0a14 Icing: 42ms (1 times) realtime

Wake lock u0a226 *alarm*: 27ms (1 times) realtime

Wake lock u0a114 *alarm*: 27ms (1 times) realtime

Wake lock u0a14 GCM_CONN: 25ms (1 times) realtime

Wake lock u0a14 *alarm*: 22ms (3 times) realtime

Wake lock u0a164 StartingAlertService: 11ms (1 times) realtime

Wake lock u0a14 Event Log Handoff: 10ms (1 times) realtime

Wake lock u0a211 *alarm*: 6ms (2 times) realtime

Wake lock u0a64 *alarm*: 6ms (2 times) realtime

Wake lock u0a64 TrafficIntentService_onHandleIntent: 5ms (1 times) realtime

Wake lock u0a14 GCM_HB_ALARM: 3ms (1 times) realtime

Wake lock 1001 RILJ0: 2ms (1 times) realtime

Wake lock u0a14 GCoreFlp: 2ms (1 times) realtime

Wake lock u0a147 *alarm*: 1ms (1 times) realtime

All wakeup reasons:

Wakeup reason 717:dhdpcie_host_wake realtime

Wakeup reason 513:s2mps13 realtime

Wakeup reason 745:flip_cover realtime

Wakeup reason 745:flip_cover:717:dhdpcie_host_wake realtime

Wakeup reason 738:hostwake realtime

Wakeup reason 738:hostwake:717:dhdpcie_host_wake realtime

Wakeup reason 513:s2mps13:717:dhdpcie_host_wake realtime

Wakeup reason unknown realtime

Wakeup reason 561:max77843-irq realtime

Wakeup reason 512:arizona realtime

and I've noticed that there are 3 kernel wake locks that were the most active:

Kernel Wake lock wlan_wake : 78ms (236 times) realtime
Kernel Wake lock NETLINK : 47ms (394 times) realtime
Kernel Wake lock eventpoll : 4ms (396 times) realtime

I'm guessing that wlan_wake is for keeping the device connected to the wifi network, since I have "wifi always on" checked in order for my messaging and email apps to continue receiving new messages. However, I have no idea what the other two are for.

I think the argument about unchecking "wifi always on" to preserve battery is invalid, since I also have "wifi always on" checked on my Note 3, and battery life on it was vastly better, I only lost about 5% per night.

Another interesting thing to note is that this one

wake_reason=0:"717:dhdpcie_host_wake"

appeared in the detailed wake lock log every few seconds.

For example:

+6h11m51s858ms (2) 067 -wake_lock wake_reason=0:"717:dhdpcie_host_wake"

+6h11m53s740ms (2) 067 +wake_lock=u0a39:"b"

+6h11m53s744ms (1) 067 -wake_lock

+6h11m54s957ms (1) 067 -running

+6h11m57s469ms (2) 067 +running wake_reason=0:"717:dhdpcie_host_wake"

+6h11m58s604ms (1) 067 -running

+6h11m59s450ms (2) 067 +running +wake_lock=u0a39:"c" wake_reason=0:"717:dhdpcie_host_wake"

+6h12m04s480ms (1) 067 -running -wake_lock

+6h12m10s422ms (2) 067 +running +wake_lock=u0a39:"b" wake_reason=0:"513:s2mps13"

+6h12m10s592ms (1) 067 -wake_lock

+6h12m12s002ms (2) 067 +wake_lock=u0a39:"b"

+6h12m12s006ms (1) 067 -wake_lock

+6h12m13s185ms (1) 067 -running

+6h12m14s444ms (2) 067 +running +wake_lock=u0a39:"c" wake_reason=0:"717:dhdpcie_host_wake"

+6h12m19s464ms (1) 067 -running -wake_lock

+6h12m25s465ms (2) 067 +running +wake_lock=u0a39:"*walarm*:com.sec.spp.push.ALARM_TIMER_ACTION" wake_reason=0:"513:s2mps13"

+6h12m25s637ms (1) 067 -wake_lock

Do you think this is abnormal? I can see this log having entries with dhdpcie_host_wake every few seconds from last night until this morning, making the size of the text file very large (my output.txt file is 1.394 MB)