[AT&T Samsung Galaxy Note II] lucaoldb:
Regarding battery drain, let me share my recent experience, which I hope could be useful for some of you, because I have been moving from one rom to another (tochwiz and AOSP) for a couple of months.

Now I own a N7105 and I am using the vanilla version, 4.1.2 bootloader, the latest agni kernel 3.94 and all sync on (excepting google now, which I don't like that much, sync is on for gmail, calendar etc, 2 exchange mail accounts, 2 PEC mail accounts with pocket pec, Dropbox, Flipboard). GPS is always activated and wifi is on and my carrier is 3g only, so there is no choice for 2g, if I need data, as I do... Well, with these settings and a fairly intensive use, the battery drains something like a 4% per hour and just 1% if I don't touch the phone and no wakelocks at all. I still use a 4.1.2 modem.

On the other side, all the roms with note 3 features let my battery drain at least 3% per hour even if I don't even touch the phone (same settings as above) and, with the same use, battery drains 6-7% per hour in comparison to 4% (in case of Seanz's vanilla version).

My opinion is that people who are always playing with their phone very likely don't notice that battery drain in idle is huge, just because the screen is always on. I had not noticed it myself the first time I flashed a rom with note 3 features, because I was on holiday and I was constantly trying such new features but, when I went back and put my phone into my pocket, I immediately realised that something was going wrong... Deep sleep comes late and is at most 30-35% ot total time, even if the phone is just "sleeping" on the table.

So, according to my experimental findings, agni kernel doesn't cause any wakelock to vanilla roms as well as devil's kernel (the second one requires more battery juice, anyway) while there must be something, may be even a little silly thing, going wrong for the roms which sport note 3 features, at least for the ones I have flashed (i.e. the ones by Seanz and Ditto rom, which are both very good, all of them in several versions).

For example, while I was using Ditto rom, google play services kept the cpu to 1600 Mhz for a quarter of an hour and, though I had used the agni tool to set max cpu at 1000 Mhz, cpu did not scale lower than 1000 for at least 10 minutes more. Even moving to an area where 3g signal was bad caused the cpu to heat my phone just like a formula one engine.

It seems that note 3 features somehow let the phone behave weird when something is not average: 3g signal, low wifi, google play store updates pushing etc..

I feel that's not very "technical", but even logcats did not help a lot.. Or at least they did not help me much.

I am almost sure, anyway, that samsung sync is not responsible for these issues, because unticking all the choices did not change anything. I was pointing to Samsung sync, because for N3 rom it's a bit different from the standard one of Note 2. I can't even blame SVoice, because I don't use it. Smart scroll fetaures were disabled as well... It's not the modem, because even when just wifi was on that did not do the trick. May be some sensor...

What can I say for sure is that vanilla rom with agni kernel, though I am still sticking to 4.1.2 bootloader, does not drain battery more than 4.1.2. roms and is the best choice for me, so there is no need to upgrade the bootloader to get more battery juice.

I would like to come back to N3 roms, but sadly the trade-off is not worth to go, at the moment... Does any of you have any suggestion about the info we could share to solve the problem?

Just slightly OT: if you plan to move to CM11, don't activate ART, because it randomly keeps CPU to 100%. On the other side, for Omnirom wakelocks are reportedly gone after that a zip to fix sensors has been released.

---------- Post added at 06:41 PM ---------- Previous post was at 06:32 PM ----------

Yes, there is a way to disable buttons and even to change their behavior, I did it myself some months ago, but it is not very useful, imho.

Anyway, there is a thread somewhere:) You must edit something which is inside /system/user/keylayout/