yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] magnamentis:
exactly

absolutely right and since we're already at it i take the opportunity to bring up a point with an example.

i'm using the night hours as a battery testing period, means that i each night, same times, same config, same kernel

same rom, same night stand ( wifi and cell signal identical ) so same, same, same and identical situations all over.

and guess what, the battery drain on my nexus 5 as well as on the n7100 and all other phones ( my wife's ) differ !!!!!

this means. i usually get something aroun 0.3% per hour drain but once of a sudden, ( remember: same, same same, configs )

one or the other device ( all of them ) consume only 0.1% and/or 0.7% per hours.

so what is my point? it's the fact that all those who try to proof that undervolting gives them better battery life can never

really proof it because the range ( tolerance ) of the usage even under identical conditions differs by factor 5-10.

and as many experienced users say: this is not worth the hassle which might occur with undervolting, specially for

unexperienced users who don't even recognize that undervolting is the culprit for their problems and then blame

it to the rom and or the kernel because? yes because it only happend after flashing a custom kernel which allows for

undervolting. by the way would i be a kernel dev i would probably state this in the op and cut undervolting out from features :) :)

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Agni 2.7.7, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] PetritH:
Hahaha, this made me lol, u ask for a bigger explanation a post before and when the guy explains u don't understand ?
[Nexus 5 Original Android Development] benfiller:
Basically franco removes MP Decision in order to save battery, not every app requires 1.27 Ghz minimum frequency and some might think 3 seconds is a long times.

Personnally, I don't really care about battery life, as long as my phone last a day, I can plug it every night. I just want a smooth and reactive phone and for me Elementalx has been great for that !

But to have a better opinion, there is no better way than trying them yourself and see wich one suits your needs better.
[Nexus 5 Original Android Development] flar2:
Elemental has more features, read the first post for a list.

Also 100% stable and no tweaking required, runs good out of the box.
[Nexus 5 Original Android Development] LiquidSolstice:
I've been noticing some strange visual glitching/artifacting on AICP using the latest .38 update (yes, I'm using the CAF one currently).

I searched and found several posts talking about them, but I'm still not sure what the cause is? Some people say it's because of the governer, but I'm hesitant to point at that because I've used ElementalX on several devices now and I trust flar2's judgement concerning kernels.

I've tried to get ADB logs, but it's too unpredictable. It does seem to happen when opening articles in Feedly with the Dark Theme, and during the first few seconds after opening the camera (but again, not consistently).

I'm on a brand new RMA device, but it was doing this on the previous device as well. I just didn't get down to really thinking about it until today. Any ideas? The glitches don't happen enough to really even bother me, but out of curiosity I'd like to find out why they're happening.

And before anyone jumps down my throat telling me that I'm being a troll, that's the last thing I'm doing. I realize it's entirely possible it's my ROM or an app I use, so I'm looking for suggestions, not hate.

EDIT: I should mention the following:

I use Display Control by franco to control the settings and have noticed these glitches even with the app uninstalled and the profile stock.

I use AICP's built in kernel control only to change the vibration from 63 to 50 (no other options are touched).

The only other root-based utilities I use are V4A and FX File Manager with the root module (and I still get these glitches every so often).
[Nexus 5 Original Android Development] kayl2:
Same boat here, so don't feel silly!:)
[Nexus 5 Original Android Development] xbxjunkie:
used this kernel for a few days 'cause i wanted the knock features of my G2 and loved it. my only issue with it is the battery drain with the knock

option enabled. other than that, this kernel rocks :good:
[Nexus 5 Original Android Development] szucsgf:
The additional battery drain caused by the screen wake options have nothing specifically to do with this kernel; any kernel that has those features would have the same additional battery drain. So you can scratch the "other than that" part and just say "this kernel rocks"! :)
[Nexus 5 Original Android Development] t0mas_:
i am guessing here, but it might be the experimental graphical drivers if the rom has them included or maybe you even flashed them separately? they are not completely stable or at least they weren't the last time I checked. (which was admittedly quite a while ago)

if you haven't flashed them yourself, try searching your rom's thread if they are included.

I hope I'm not shooting in the wrong direction here, good luck solving your issue.
[Nexus 5 Original Android Development] magnamentis:
read this to understand the following: http://xdaforums.com/showpost.php?p=52332151&postcount=7735

in the above linked post, some time ago i promised to check a few things and come back with results as soon as i feel that i've something

to contribute to shed light on the matter. no i hope this is the case, while final and absolute conclusions are very rare due to the variety of

possible configs around.

so the first thing i've changed is to change from cooler colors to profiles in franco's fku. since you mention using the same

app i have to ask you here to check whether you have the cooler colors active ( by accident or on purpose ) and then post

back here to let me know bacause:

i've never encountered those glitches again after they occurred a few times on 0.38 as well as 0.34, after having disabled cooler colors on the

1st of may. then later on the 6th of may i've changed to CM11 M6 and again no graphic glitches anymore. so i right now have to think,

that, exactly as i suspected, that the combination of CM11 and cooler colors might play a role in this issue.

so the only thing i don't know is wheter it's a CAF/cooler colors thing or a cooler color issue only. i suspect the first. so should it happen that

you have cooler colors deactivated, ( elementalX config file > cooler colors should be set to 0, if it's set to 1 they are active ) in that case

i'm back to where i started since you are using another rom than i and your cooler colors would be off and still glitches occur.

in that case the only remaining common thing i know about ( many apps could still be the same ) would be CAF-stuff included in the configuration.

so i'm looking forward to some feedback from you ( after you check the 0 or 1 in elementalX.conf file ) to narrow things down further.

and/or map out certain possibilities as a cause.

finally, and this is for sure, currently runnding CM11 M6, EleX 0.38, FKU, amoled profile, not one single glitch for the last 12 days.

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Agni Kernel 2.7.7, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] yashade2001:
How much s2w or dt2w drain battery ? With slim kernel I can use for 30 hours (normal usage), if i enable s2w or dt2w how many hours will i get approximately ?
[Nexus 5 Original Android Development] xbxjunkie:
while running this kernel with knock enabled, i was getting 30-34 hours on a single charge with light use. using the stock kernel i was getting

close to 44-48 hours on a single charge with light use.
[Nexus 5 Original Android Development] jfim88:
Does the cooler colors have any battery impact? Im testingnit now...

Im loving this kernel in combination with CM11 M6...

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] PetritH:
Nope, i use it since forever, same battery
[Nexus 5 Original Android Development] flar2:
There was a discussion about this a few weeks ago. There was an app or something that may cause it. Perhaps someone could refresh my memory?
[Nexus 5 Original Android Development] micmor_:
What are the biggest problems running art?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] peecs121:
For me nothing. It's smoother on ART

Nexus 5 powered by AICP/ElementalX
[Nexus 5 Original Android Development] szucsgf:
Honestly the only recent "problem" I've seen is that ART and Xposed are incompatible. If you don't rely on Xposed, I recommend trying ART. It's noticeably smoother on every ROM I've tried. No negative impact on battery (theoretically might improve battery I've heard).

In the beginning some apps were incompatible, like Whatsapp and Titanium backup, but those apps were made compatible with ART long ago.
[Nexus 5 Original Android Development] :
It takes up storage, causes a little bit of trouble with ROMs and kernels, and is incompatible with a lot of apps. After all, it is still in beta stages.

However, it does speed up opening apps and saves battery.

Do what you will with that information. I prefer Dalvik because I flash a lot, but either option makes sense.
[Nexus 5 Original Android Development] CRIME INC.:
The only time I got the graphic gliches was after using the app softkeyz. And it was only in the messaging app. Reflashing the kernel stopped them

Sent from my Nexus 5
[Nexus 5 Original Android Development] thereal_bigjake:
I've never used softkeyz and I have had it randomly on different roms and with different kernels. A reboot always fixes it and it happens about every 2 weeks at random.
[Nexus 5 Original Android Development] bigknowz:
Screen glitch

[MENTION=4684315]flar2[/MENTION], Had the same issue on lockscreen. Have to use PIN code for work exchange email security settings. While entering PIN, a small semi-transparent window would pop up near the number.

Also, was having weird drain overnight. Used to be about 2-3% (only have voice on, mobile data off), Last week or so has been 7-8%.
[Nexus 5 Original Android Development] magnamentis:
confirmed :)

hi, to complete the picture a bit more and because i never mentioned that before, now that you posted it, it came to

my mind that during the period ( few days ) when i have encountered those glitches, i as well had that very same

battery drain. basically same story, usually 2-3% per night, during that period 7-9% per night + graphic gllitches

during that very same period of time, mainly on locksreen.

please read my various posts concerning the matter because i got rid of both, back to normal battery and no more graphic glitches.

want to stress here that i'm on the same kernel which is EleX 0.38, only thing changed is changed cooler colors from 1 to 0

and later, but when the issues had stopped already updated to M6 from CM11 M5.

until someone proofs the opposite i still suspect CAF-Roms in combination with cooler colors but need more serious

( means solution oriented instead of only complaining ) input to narrow things further down.

ohh... almost forgot this, i mentioned it in my 1st post about this matter, that it happend the first time to me while

on chaos kernel which has the cooler colors as well. so what both kernels had in common which i'm aware of,

ist that i had the cooler colors on while using cm11 in both instances. so that would not contradict my assumption

but raise the chances that things lay in that direction.

until now nobody clearly stated that he/she had cooler colors off when it happened and/or was not using a ROM with CAF commits.

such a statement would proof my suspicion wrong and as a consequence would allow to look further to find the real culprit.

so what i'm looking for here, till now to no avail, is that someone clearly denies one or better both: a) using caf, b) using cooler colors

this might be because everyone had exactly that config but then it would be nice if as many as possible would confirm that when it

happened to them, that they were using a caf based rom and/or cooler colors with any kernel providing it at he same time

only with such clear denials or confirmations can we find out whether it's worth looking into it in one or the other direction.

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Agni Kernel 2.7.7, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] bigknowz:
Stock + Regular colors

Unfortunately, I was running stock ROM and colors.
[Nexus 5 Original Android Development] magnamentis:
thanks

ok, good to know so one possible source less, remains the fact that you were using the colors :)

so no we need someone who for sure did not use the colors, for sure means go and look

whether it's set to 0 and not to 1 in the elementalX config file : storage/etc/elementalx.conf

albeit i don't think that the colors alone do that, if the colors are involved at all, it is probably

a kind of compatibility problem with some apps. i say some apps because the one app which

was mentioned earlier in this thread i have never used. so it cannot be only that app because

i had the problem without it, but again it could be some apps in combination with the colors.

as usual these things can be tricky to find but albeit i solved it for me, i'm interested to find

out what it is finally, a) to avoid it for the future and b) for those who still suffer from it.

thanks in advance

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Agni Kernel 2.7.7, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] miguepereira77:
Wow! Amazing...

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] magnamentis:
nice for you

i'm aware that i could gonna get sam bashing for this but i find it somehow boring and annoying

to find on almost every page, average probably even more often, some kind of benchmark and

battery stats. after reading a few pages we know that this kernel is good on the battery and

performs well so what is the benefit of this.

especially since the results are mostly very similar, 5-6h SOT + 20-30h battery life with that usage,

( or something close to that i know that some have 6h+ etc. )

however it is, just wanted to say that once, will not happen again :) but please consider that many users

come to read when they get signaled a new post, just to find this, as i said, in my opinion, bragging non-sense.

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Agni Kernel 2.7.7, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] fkloznica:
Same here.. It happens out of the blue. Every 15,20 days. Next time i will record it. Think i have a faulty device
[Nexus 5 Original Android Development] miguepereira77:
Deleted
[Nexus 5 Original Android Development] Globespy:
Biggest difference for me is that I love all of Faux's apps, and since I've been less impressed with his recent releases, I can still use all of his wonderful apps. MPdecision is turned off via FauxClock, so this should not be an issue?
[Nexus 5 Original Android Development] szucsgf:
Sharing something from the OP FAQ:

"Q. Should I disable mpdecision?

A. No."
[Nexus 5 Original Android Development] PetritH:
OP is a great place to hide your credit card details, since nobody reads it :silly:
[Nexus 5 Original Android Development] letmedanz:
hahahahaha.. unbelievably true
[Nexus 5 Original Android Development] jumparound246:
Like the other guys said: it's not recommended as stated in the op.

I've disabled it and have no issues, though...
[Nexus 5 Original Android Development] bigknowz:
What is mpdecision?

The mpdecision file runs in our system as a vendor executable file and what it does is that it controls the governor for cpu, this file is very important as it defines performance of your cpu1, the file gets executed every time your screen goes off, hence cpu1 scripts are useless because the mpdecision file overwrites the cpu1 governor settings to userspace ondemand, userspace is the governor when cpu1 is online and ondemand when offline.

from here: http://www.scottsroms.com/showthread.php?447-CPU1-governor-change-with-MPDECISION-file-script
[Nexus 5 Original Android Development] Globespy:
I get better performance/battery with it off. Each to their own.
[Nexus 5 Original Android Development] paychex:
But I like tinkering!!!
[Nexus 5 Original Android Development] bobby_sucker:
The temperature limit is 70 C° on the latest version?
[Nexus 5 Original Android Development] Globespy:
I'd never seen (or bothered to look) a description like this.

But in the end, often what's right on paper isn't actually better in reality.

If there's no obvious issues switching it off, and your happy with your phone then that's the best choice for you.
[Nexus 5 Original Android Development] RobbieL811:
I am just coming to ElementalX from another kernel. I have a question. Is it the general consensus that .34 has the best battery life?

Sent from my Nexus 5
[Nexus 5 Original Android Development] szucsgf:
Some people swear by .34 because they experience better battery life. However some people say they're the same. flar2 (the dev) had said that 34 and 38 are so similar there shouldn't be a difference. 36 was worse due to something that was reverted in 38. So going with either 34 or the latest 38 should be fine.

Don't forget to dirty flash your ROM before flashing ElementalX.
[Nexus 5 Original Android Development] aldur999:
I'd like to open a serious parenthesis regarding Undervolt.

I premise that, at this time, I know that UV is, how to do it the right way, while keeping stability as good as stock: on my previous Galaxy Nexus I managed to undervolt, at first by lowering global the freqs, and then by refining each single frequency, step by step, keeping the configuration stable for months and months.

My question now is, I know for sure that, at least on the Galaxy Nexus, the best gain regarded the produced heat, and I didn't notice any battery life improvement. It should be the same on the N5, but generally, could it

decrease performance or battery life

? Some posts ago I've read that the CPU would need more cycles to accomplish the same tasks, is it true in anyway? How could it be? Apart from that, in my logic, given less voltage, the CPU should use less power and hence increment, at least in an imperceptible way the battery life. What do you think? I'd like to hear about some meaningful test, or about ideas to conduct them by myself.

And, furthermore, the table of voltages, refers to a single core? e.g. each core, at 300MHz, will use given voltage?
[Nexus 5 Original Android Development] szucsgf:
Underclocking would increase the number of cycles, not undervolting. I remember the post you're referring to; I believe the poster was mistaken.

Power = Capacitance*(voltage^2)*frequency.

Therefore undervolting does theoretically decrease power use and therefore increase battery life. The amount would depend on how much time your CPU spends at various frequencies, and of course only has any impact when screen is on. I can try to use the power formula above to roughly calculate how much power would be saved by 25mV undervolt using a recent frequency usage chart on my own phone and share here later. It would be purely theoretical though.

I once undervolted my GNex (coincidentally) to its lower limit and experienced worse battery life. Removing undervolt improved battery life again. I don't know why this happened. I've read that extreme undervolt can cause instability which makes your device work harder even if it doesn't crash, but I've never verified this. I also didn't experience it on my N4 or N5.

I believe that undervolting does save battery but only a very little bit. I believe that battery savings from undervolting are controversial because the small battery savings are drowned out by the larger random fluctuations in battery life caused by the variations in our everyday use and changes in environment.
[Nexus 5 Original Android Development] paychex:
P=IE

So yes decreasing voltage, decreases your wattage. If you don't have enough power to to accomplish a task in one cpu cycle it will need another cycle or a cycle at a higher frequency.
[Nexus 5 Original Android Development] ck.chunkeat:
Hmm, So today I missed my alarm clock. The reason was there was no sound from my phone anymore. I had to reboot my phone to get the sound back. Happened a few times before but previously i had a sound mod on. Now that I removed the sound mod around 1 month ago, the problem still happen again. Is it something wrong with the software? or is it hardware problem and I should be worry.

Stock rom + elementalx 0.38. running on ART, nothing else.
[Nexus 5 Original Android Development] szucsgf:
Awesome. Thanks for clarifying.
[Nexus 5 Original Android Development] flar2:
I think you should reflash the stock Rom then reinstall EX kernel.

There's nothing like a nice clean system.
[Nexus 5 Original Android Development] Globespy:
I never dirty flashed my ROM (Kangakat)? I was on Faux, so I flashed the stock kernel, allowed my phone to boot then went back to recovery and flashed elementalx.

Everything works great.....
[Nexus 5 Original Android Development] ck.chunkeat:
Yes, I figured I should reflash everything to stock to keep it clean again. But thought I'd wait till 4.4.3 come so that I don't have to do it twice. But sadly 4.4.3 isn't coming anytime soon. >.<

Weird though, cause I saw a few other users facing the same problem. This problem happens rarely. :/
[Nexus 5 Original Android Development] :
Just for future reference, you don't have to clean install for a new Android version.

Also, it's not a problem with the kernel. I'm not sure of the technical jargon, but there's not a lot you can do besides check to ensure the sound is working when you go to sleep. Also, be absolutely sure that you have wiped everything when flashing.