[Galaxy Note 4 General] gekkehenkie11:
You guys dont have a bug. Let me explain what's happening here. That "wlan_rx_wake" you guys are seeing (after of course having disabled 'scanning always available' in your network settings) in GSAM are wifi wakelocks, keeping the phone from going to deep sleep. This happens when network traffic wakes up your phone. This literally could be anything: it could be your windows PC on your network doing broadcasts, it could be an app on your phone sending out wifi packets, it even could be your router. The best way to find out is:

1) Install an app from the playstore called 'network log', this is really an awesome app. Click the log button on the top right and dont use your phone for 5 minutes. Then check your log and be amazed by all traffic it's been sending while you thought it was just sleeping :) Mind you, to even accept network traffic, your phone must be awake, hence the 'wakelock'. So, a wakelock is not something 'bad' or 'wrong', it's necessary for your phone to process the network traffic, that's why it exists. It's simply your network adaptor telling your CPU 'hey dont go to sleep while I'm processing all this network traffic that's coming in, I need you !". However, while your phone is awake, it of course consumes battery. So that's why you'll want to cut down on all this network traffic. BTW I saw somebody complaining about wifi wakelock going through the roof while downloading: of course ! While it's downloading, your network adapter needs the cpu to be awake, hence it's always requesting a wakelock during download & upload. In fact, any time it process a network packet, it will request a wakelock. But hopefully I explained well what a wifi wakelock actually is, so you guys actually got that already ;)

BTW, to see the port numbers in this marvelous app, go to settings/general options and uncheck resolve hosts and ports in the network log app. You can swipe to the left to see the log and swipe back to the right to see the apps, both are very useful !

You can then investigate: which ports are sending/receiving, which apps are connected to those ports and is the other side a local network device like your windows pc ? Then find out what traffic it is, by googling the port numbers. Another useful method is:

2) use ADB, go to the shell and type 'netstat', there you will find the active network connections. With command 'fuser' you can then figure out which process it is. For example if you see port 4201 and you see that it's 'tcp6', type:

fuser 4201/tcp6

It will then show you the ID of the process that's using that port. with command 'ps' you can then lookup the process. Some of these commands might not be available on standard touchwiz though, not sure, they are on CM12 and many other custom ROMS'. If it's not available on TW, dont worry, the 'network log' app alone should be enough already to get to the bottom of all this !

Happy hunting ! And yeah most likely it's a combo of things: you guys probably need to reconfigure your windows network setup to stop it from sending broadcasts to your phone (here's a nice tutorial: http://xdaforums.com/google-nexus-5/help/getting-rid-wlanrxwake-wakelocks-t2519294 but there's more, google the port numbers you find to check what windows network protocols/processes are using those ports, for example if you see port 139 from your windows pc sending messages, you'll need to disable netbios etc), you guys probably have one or few accounts set up as 'sync' in your settings/accounts, you guys probably have your play store configured to do updating/inform you about new updates and then you will have apps like facebook, whatsapp, all doing constant network traffic, you guys will probably use a browser that is spying on you, sending data constantly to their creators (like UC browser or chrome, hint, use naked browser, it's the only browser that doesnt spy on you), dropbox that's syncing and more processes like that, which are constantly waking up your phone. Cut all that down and you will see the drain disappear. And when that happens and you enjoy good battery life again: hit the 'thanks' button ;)

Oh and lastly, yeah sometimes these apps like betterbatterystats and GSAM aren't even accurate. Since Lollipop you guys have now access to a much better battery tool: go to your windows command prompt and (after you have installed adb) type:

adb shell dumpsys batterystats >output.txt

Which will dump batterystats to output.txt. This is a VERY VERY useful too and actually accurate, instead of those other tools. The output is divided in several sections, scroll through them and you'll understand. Hint, a good starting point are the 'kernel wakelocks' and 'partial wakelocks', just like in those other tools, but now it's actually accurate ;)

[MENTION=5249000]shinasurada[/MENTION]: maybe it's an idea to edit your openings post to point to this post, cause it contains all the answers and solutions people are looking for in just 1 post. I took the time to write it out once and for all, cause I'm sure many many people suffer from poor battery life due totally unnecessary network wakelocks.