[Galaxy Note II N7105 Android Development] R0B3RTF1SH3R:
i think posting a nandroid backup is against XDA rules.

*this may be repeating a lot of what everyone knows already, there are some very advanced users on here and this post is in no way telling you how to use your device/rom/kernel, this is just a rough guide of how i setup my device settings to get the battery life/smoothness i enjoy.

step by step how to setup nameless rom like i have. this is blazing fast, melted butter, i can flick thru apps/recents/menus toggles everything with almost no delay

firstly format everything and convert it to F2FS filesystem (sdcard i haven't, but you could)

you need nameless rom version 2015/01/11 *(this version has the devil kernel)

i use pa_micro_gapps. also tolte_sensorfix.zip (for sensors, works sometimes, most the time it doesnt) bug i need to fix.

INSTALL all using TWRP 2.8.1.0 (im not sure it makes a difference but try it)

the rom specific settings i have:

(disabled sync/gps etc) wifi i just leave on but disable scanning always avail and network notifications. if you are having trouble finding how to disable mobile data when not in use in the dropdown toggle list, the mobile signal bar, click it. then slide tab to off, yes that took me a while to find. haha

to fix GPS use TOPNTP and write your correct gps settings, reboot.

turn off adaptive brightness (even though I left that on, some people say it causes drain on other nameless builds)

the main key for ultra battery life is using the correct modem.

if your roms are depleting battery really fast (1-2 days on idle) you need to try a better modem

(one that works with your countries/carrier settings like fast dormancy etc)

also disable "Android Debugging" in developer settings, a lot of ppl say this will save lots of battery.

Devil Kernel Manager settings: (goto gplay and download it, the one by metalignus not the other one)

DKM Memory

Swappiness = 60

DKM CPU

Governor = Devilq or ZZmove ( sometimes devilq disables cores to quick and some feel stuttering, i don't notice this)

Max CPU = 1704

Multicore Power saving = 1

DKM GPU VOLTAGES

I personally use -25mv but default is probably best for stability

DKM SCREEN

MDNIE Mode = Standard

DKM AUDIO

Sound Control = ON

Speaker Tuning = ON

Mono Downmix = ON

DKM MISC

SD Read Ahead = 1024

I/O Scheduler = FIOPS ( Hands down the best)

Vibration Intensity = 36

Backlight Touchkeys = ON (this actually disables the hardware keys backlight)

EXTRAS

i use greenify,viper audio and xloud/bravia3

thats pretty much it.

im still using googlenow launcher. haven't been bothered changing to atom launcher

(i think works best with lollipop if your into form factor. hiding status bar and the way it operates works/looks well with LP) My goto is apex however, that was for 4.3/4.4 where i needed specific transparency settings and locking abilities apex provides. I also use Swiftkey. disable cloud.

also install greenify if you install apps that have cloud or sync issues.

after that. keep an eye on DKM - TIME IN STATES - statistics. this will let u know your phone is actually going to sleep.

Regards,

Rob

PS. keep an eye on nameless builds because some of the features and fixes will be hard to pass up for some users. ATM my biggest issue is sensors turning off screen when in calls. works 50% of the time but thats still an on going bug with some builds/users .

---------- Post added at 02:03 AM ---------- Previous post was at 01:53 AM ----------

yep. still broken. HW acc not working atm

EDIT UPDATE* i just hit 50% battery after 67 hours. only 1 hour 50 screen on time but this is by far the best battery I've experienced on Lollipop cm12. in 5 hours that will be 3 days. wow. estimated time says another 5 days (8 days total) but ill be happy to break my old record of 5 days 7 hours on an old version of beanstalk. now to resist the habit of plugin when goto bed. im only doing this to get to 1% battery to see total time i achieved. also if your carrier supports 2g/3g (mine only supprts 3g/lte) you could setup a toggle when screen off or deepsleep to switch to 2g/3g for even more savings, haven't setup this yet.

quick question.

can anyone confirm that with 4.0 and 5.0 (mainly lollipop in question). that with dev option "force GPU rendering". you dont need it ON anymore because 4.0 Onwards. the OS will enable it if apps request it?

does having it ON all the time consume more battery. if its not needed because OS implemented enabling it regards to APP request. then sweet. but I always wanted to know this