yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] bobby janow:
I beg to differ. Although not necessarily burn in it does take some time for apps to adjust to a new kernel it seems. Flash, charge then reboot in 2 days. You'll see what I mean.
[Nexus 5 Original Android Development] :
Yeah, it seems like the battery is a bit buggy even though all I did was battery saving fixes. I am currently at 30% - are you saying that I should run it into the ground then charge with my phone off for two days?
[Nexus 5 Original Android Development] bobby janow:
No not at all. Just run it as you do. Reboot the phone in 2 days. Charge whenever. Done. Never run it into the ground.
[Nexus 5 Original Android Development] daftlush:
Can we get a new version for CAF that has new CM commits and works with the new F2FS commits. The new F2FS kernel (the one we need to flash first for the ram disk) doesn't work with .36

I read something about .img files working better for f2fs kernels. Is the ramdisk included in .img files.
[Nexus 5 Original Android Development] drawde40599:
if u feel your not getting good battery ( should be at least 1hour better than stock IMO ) letting your phone die, charge it while off to full then some more after u turn it on ,always makes my battery act right afterword's . but Bobbie j is right charge it whenever u feel like it , its actually good for the battery

I run my devices " into the ground " ALL the time , it being bad for them is a myth ;P
[Nexus 5 Original Android Development] k3mik4l:
Aicp and elementalx running like a dream. Thanks for the kick a$$ kernel!
[Nexus 5 Original Android Development] peecs121:
Couldn't agree with you anymore. It's perfect

Super powered Nexus 5 running AICP/ElementalX/Greenify
[Nexus 5 Original Android Development] notbrodie:
so do i. i don't know where are getting this information about it being bad
[Nexus 5 Original Android Development] magnamentis:
both is true :)

a) technically it is not a myth, those batteries (LI-ion) indeed suffer from being emptied to zero but !!!!!

b) the software does not allow them to, so if you run your phone into the ground as you says, it will switch

....of and appear empty but as a matter of fact it isn't, there is still juice left but you are not allowed to use it

....so to prevent "a"

as to the kernel burn in, yes there is an effect but it's not kernel specific, you can flash anything that affects the system

and the deeper innards of a system, specially when wiping caches etc. is included but not exclusively then, and this effect

will show, it really has to do with the various software components to learn again to play together nicely.

futher there are longer processes upon every reboot, even longer ones after flashing, performing in the background.

the most powerconsuming one is media scanning process which can take many minutes next to other processes and this alone

can reduce your battery by 2-3% or even slightly more.

the information you find for example in wikipedia or google it in non-android specific, but li-ion specific pages.

you can find easy explanations and you will come across very scientific explanations but the result is the same

emptying li-ion batteries to 0ma left kills them quickly, more sooner than later you will not be able to charge them anymore.

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, AGNI Kernel 2.7.5_r3, 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, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] stumpy352:
Actually, the nexus 5 has a lithium polymer battery. Does this still apply?

Sent from beyond the neXus
[Nexus 5 Original Android Development] szucsgf:
Just adding to your excellent information.

Not only is it harmful to your li-ion battery to fully discharge, it's harmful to fully charge up to 100%. The the negative effects are only visible after a few hundred charges, which is why people can fully charge and discharge their device and not at any consequences.

http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
[Nexus 5 Original Android Development] magnamentis:
yes

sorry for not going into all the variations but yes, the same applies to lithium polymers, the difference between Li-Ion

and Li-Polymer is not that big, it's about the insulation between the layers which is different, again, this you find very well

explained in good wikis about batteries. usually a range of batteries is covered there from Ni-Cd over Ni-Mh to Li-Ion to Li-Polymer etc.

[MENTION=4783761]szucsgf[/MENTION] you are absolutely right, but as well, the same applies to the software again, which will not allow the battery to be over-charged.

latest edge computers and smart devices defer from last generation mostly in efficiency and power management in general, while the

battery management is part of the game almost from day "2" after Li-Ion technology was implemented.

if one would be allowed to charge a Li-Ion Accu like a Li-Mh accu it would explode, so software was necessary from day one to avoid serious security risks.

by the way OT i found out the hard way when i once tried to open one of those batteries haha.... the child in men you know. it was a very unpleasant

experience when two layers, once disposed of their appropriate insulations shook hands :)

regards

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, AGNI Kernel 2.7.5_r3, 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, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] orangekid:
I just flashed the 0.36 aosp kernel, and in the aroma settings I put it on DT2W full screen, but now it still only does it if I double tap in the bottom half of the screen.

I'm on carbon nightly from April 09...

Anyone have anything like this come up or know how to get DT2W always on the entire screen?
[Nexus 5 Original Android Development] magnamentis:
try this :)

i don't know the reason for this but can at least let you know what i would do to first check if the settings are set correctly

go to etc > elementalx.conf and open this file with an editor and check if the number under Doubletap2Wake Settings is:

DT2W=2

if yes i don't know if no type in 2 and save and reboot to see whether it works then

good luck

EDIT: [MENTION=1698146]orangekid[/MENTION] _ yeah i suspected that according to your records :) just trying, interesting however, just post the solution once you got it, just in case to remember :)

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, AGNI Kernel 2.7.5_r3, 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, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] orangekid:
Thanks for the advice.

It was already at 2 (see attached screenshot).

Any other ideas?
[Nexus 5 Original Android Development] flar2:
Check /sys/android_touch/doubletap2wake

Make sure there isn't an app setting it to 1. I don't think apps like trickstermod, etc. know about the fullscreen/halfscreen setting. IIRC, it should be set to 2 for fullscreen.
[Nexus 5 Original Android Development] orangekid:
I think that's what it is, funny because I don't have a kernel app installed, but probably something I had before.

Now i don't have permission to edit it even though I've got R/W access in system...

That part I can probably figure out, thanks for pointing me to the right file..
[Nexus 5 Original Android Development] paychex:
That anecdotal evidence. I have yet to see anyone produce one linux document to back it up. Once the cache is built "Android is updating" it's done.

http://rootzwiki.com/topic/17090-kernel-break-in-fact-or-fiction/

http://xdaforums.com/nexus-4/orig-d...ernel-r201-t2002782/post44518329#post44518329

---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------

It actually was bad for old NiCd batteries. Li-Ion/Li-Poly aren't really affected
[Nexus 5 Original Android Development] magnamentis:
sorry but

if already you make such posts for topics that have been resolved, which are old and thus are just a way to show that you as well want to say something,

it should at least be correct and not a flat out misinformation, bad for those who don't know the facts and annoying for those who do!

NiCd Batteries were exactly the ones which HAD TO be emptied before recharge so to avoid the memory effect which occured

on the level where the batteries usually were when the discharge ended and the recharge started. so that means that if somebody

regularly discharched his NiCd battery down to 30% and put it on charger the capacity was reduced over time by the remaining 30%

and only the regularly used 70% remained available.

as well the thing with battery consumption was explained and it's a fact that it happens the way it was explained so what are these two

posts about? it's filling the thread for nothing and wrong to make it worse. i hope this thread remains more or less free of this, interesting

to see by the way how many times after such posts where they are coming from, kernel wise i mean haha....

http://xdaforums.com/showpost.php?p=51944748&postcount=7042

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, AGNI Kernel 2.7.5_r3, 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, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] paychex:
First off you wanna talk about wasting space here and then grace the thread with--putting it nicely--verbose prose such as "if already you make such posts for topics that have been resolved, which are old and thus are just a way to show that you as well want to say something" and "as well the thing with battery consumption...". When you try so hard to look smart you sound very dumb.

Secondly what are you doctor battery? I've worked may years in construction and have seen many many dewalt NiCa batteries. And again FULL discharge IS bad for them. The more you know bub...

http://www.hardwaresecrets.com/article/The-Truth-About-NiCd-Batteries/292/2

http://en.wikipedia.org/wiki/Memory_effect#Deep_discharge

http://en.wikipedia.org/wiki/Memory_effect#True_memory_effect
[Nexus 5 Original Android Development] drawde40599:
Actually [MENTION=5372360]magnamentis[/MENTION] is correct in everything he said about PHONE battery's read his posts agn. Then agn on how a PHONE handles charging and discharging...
[Nexus 5 Original Android Development] r0cky0790:
This forum is almost shot to hell with this bickering displayed not only here but many other threads. Let's respect Flar and keep it clean fellas.
[Nexus 5 Original Android Development] fcisco13:
If you wanna drain it drain it and STFU!! Back on topic.

Whatchu talking bout willis!
[Nexus 5 Original Android Development] paychex:
too bad that's not what he replied to me--incorrectly--about
[Nexus 5 Original Android Development] m0bstr:
For the aicp room which kernel do I use? Cm or aosp?
[Nexus 5 Original Android Development] Spinergy02:
What is that rom based on?

Edit: they are using the cm kernel apparently, so you'd probably need the cm one.
[Nexus 5 Original Android Development] peecs121:
CM

Super powered Nexus 5 running AICP/ElementalX/Greenify
[Nexus 5 Original Android Development] Geordie Boyo:
Am using the Purity ROM. Is this kernel compatible?
[Nexus 5 Original Android Development] Tylog:
Yes, Aosp one is the one you need

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Geordie Boyo:
Thanks.
[Nexus 5 Original Android Development] howard bamber:
:D sounds like artificial intelligence devoping taste!

Joke:P

From my mobile telephony device.
[Nexus 5 Original Android Development] :
If it let's me keep my man card... It was the Star Wars version lol
[Nexus 5 Original Android Development] vin4yak:
Just noticed that we have crossed the 1 million views mark! :D

This is simply the best kernel I've seen on my Nexus! :)

Kudos for this awesome effort!
[Nexus 5 Original Android Development] Sh0rty007:
Obe little question. I've just rooted my nexus 5. I'm on stock ROM and use xposed for all tweaks that I want so don't need a custom ROM. Can I flash this if I first install a custom recovery and flash it again if I want to change a setting (aroma). Or do I miss something here? :)

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] danarama:
Yes you can
[Nexus 5 Original Android Development] szucsgf:
Yes, you can flash this kernel (AOSP version) with a custom recovery on stock ROM. Many people have this setup.

To change settings after initial install, you could re-flash to go through Aroma again it just manually edit the values in /etc/elementalx.conf. Or use a kernel app like trickster or faux clock if you're careful not to inadvertently mess up your min CPU frequency.
[Nexus 5 Original Android Development] bobby janow:
Bobby Janow said:

I beg to differ. Although not necessarily burn in it does take some time for apps to adjust to a new kernel it seems. Flash, charge then reboot in 2 days. You'll see what I mean.

Yes it is anecdotal as it states in my original post "it seems". I'm not saying it's documented in linux tomes, however one might just want to give it a reboot when they see partial wakelocks eating the battery for some unknown reasons. It only takes about a minute and it might help a great deal. If it doesn't then you lost a minute of uptime. Anecdotally, a couple of days ago my battery lost 33% overnight when it usually only drains 0.5% / hour. Didn't install anything or change anything. Rebooted and for the past 2 nights it's back to 0.5% or less. Go figure.
[Nexus 5 Original Android Development] kraven001:
Software is imperfect, hardware is imperfect. "Random" wakelocks are just bugs that appear as a matter of circumstance (some other software running, some network issue, some whatever).

I got instant "boost" from this kernel every time I apply it. I go back and fourth due to my nature (I want something new, experiment, etc.) but always return here for stability and constant similar behavior. Do I get random "wakelocks" - heck yes, I guarantee it (the camera bug is "built in", there are apps like g+, fb, whatever that suck processor cycles like mythic vampires). The one thing that counts is that the randomness happens less often here because there is no crazy feature set (good for some, bad for others, can't please all), it's just what you need.

Settling in is just a myth like it is with everything when it comes to software. There is nothing to settle, there is no "gear" to be worn out, no "magic juice" to get in the right spot. Everyone that dealt with software in his life knows this. Everything has bugs, it's just some bugs are rare or not that bad. The longer you keep the same kernel the numbers will help you get better results. It's numbers, it's mathematics, the constant is the "bugs" the variable is the time, make the time "bigger" and guess what - your kernel has settled.

The conclusion in my mind is simple, there are a lot of good reviews here and everywhere. Try it, try it for more than a few minutes, give it a chance, try to see if it "settles" to your usage scenarios. You might be amazed, you might get frustrated. Either ways this is a lot better than the stock one because you will have the one thing stock doesn't have - passion.
[Nexus 5 Original Android Development] bobby janow:
Nice post and well thought out. One thing, however, (you knew there was a but in there) doesn't software on a computer have a cache that it builds for quicker starts and tasks? Even Open Office which took like forever to launch at the beginning is quite speedy now. (well that's relative) And other programs .. sometimes they go so darn slow and a reboot brings it back to normal. So is it possible that those wakelocks or bugs are simply cleared on a reboot thus bringing the system and kernel back to normal? It's rare we pay much attention to battery life on a laptop because we just know we have to plug it in withing a few hours. But perhaps there is something similar going on in the background.

Nonetheless, this kernel does the best I've seen on my device and any device prior though that is a moving target. Flar nailed it with this version.
[Nexus 5 Original Android Development] kraven001:
There is no need to "spam" the thread. I was trying to make a point I usually fail to follow myself (since I am a hopeless geek) - we are missing out on things because we over think things, we focus on small things, we have these small obsessions.

Caches are good and bad (trust me I work in software). In a perfect world we would have endless memory, but we're still not there. The sad truth is that since everything moves so fast, every bit of software is rushed to some arbitrary deadline. In some circumstances a bit of code will act not as the developer intended. Multi-threaded / event based software is very hard to debug (sort of like an art). Running that software on systems that you don't control is going to create new situations.

To summarize rebooting will "help" because you start clean, the "bad" situation will have to occur again (and this is like aligning the stars). Software moves that fast and routines being ran in a different order can cause other (unpredictable) behaviors.

My initial point was (and I guess it still is), once your usage patterns settle you will take out some of the hazard of bad things happening. If you usage behaviors are leading to the same outcome, then that would be a debugging scenario (or a bug reproducing scenario) but on your device (and usually you can find some rogue app). Having your device would allow most Devs to pinpoint issues faster; instead they rely on logs, bug reports (and how many of us submit does, or even get a chance to submit such things when a "wake-lock" happens). You can have 99 apps out of 100 that work fine, and that 1 app that is problematic is going to cause all the chaos to break loose.

This kernel is a flash and forget kind of thing. No need to tweak (there is tweaking possible). It is stable and has the right features. So for me (personal experience of running this for more than a few days - heck I am running version 0.36 since it came out) this is the go to kernel when I want to focus on other things (rather than keeping an eye out for hectic behavior).

There are just a few (usually) praise post around here. People tend to "go nuts" when something doesn't work and that gets picked up. I hereby just tried to point out that we are dealing with a complex piece of software that flar got right (hats down!).

Is it bug free? Maybe not, but for most (and I think there are a lot) it works just fine with (or without) any potential hidden bugs.

What needs to be done? Just flash it. Run it for a while; don't fall to myths or other things. At the end of the day we should just enjoy it.
[Nexus 5 Original Android Development] fcisco13:
Whatchu talking bout willis!
[Nexus 5 Original Android Development] yunzo:
As I wrote at #6891 in this thread, current Elemental-X does not support SD card reader without USB HUB.

You should buy SD card reader for Android which have extra USB-A port (female connector).

These card readers have USB HUB internally for extra USB, and they are more compatible with devices/kernels.

You should *NOT* buy any card readers without USB-A, even if they look smaller and easier to carry.

They are less compatible and may not work in several environments: Xperia pro + stock/Lupus kernel, Nexus5+current ElementalX
[Nexus 5 Original Android Development] Sh0rty007:
Just flash this kernel. Everything standard. We'll see :)

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] :
OK we will ALL wait for your approval.
[Nexus 5 Original Android Development] Ntress:
Hi, just installed the kernel after using Linaro kernel, is there a recommended custom settings for battery?
[Nexus 5 Original Android Development] El Nino1977:
Just install defaults in aroma and enjoy.

Why is everyone obsessed with battery, I guess everyone is too busy to charge their device these days...
[Nexus 5 Original Android Development] Sh0rty007:
Because people want a battey that comes easily true the day without worrying every time they put the screen on.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] shayan1103:
tnx flar2 for elementalX v 36:good:

I have some micro Lag in launcher(stock rom)

how fix it?
[Nexus 5 Original Android Development] sirovai:
Same probleme here. Revert to stock Purity kernel for now. (Nova Launcher)
[Nexus 5 Original Android Development] szucsgf:
Don't worry guys, battery is excellent with this kernel. Try a few cycles with default settings. It's already tuned to be more battery friendly than stock kernel without sacrificing performance.

The best tips I can give to save battery are not kernel related: control wakelocks, make sure you have the best radio, lower screen brightness. These impact battery more than kernel settings changes.

Here's a few screens if you like that kind of info, keeping in mind that usually battery stats are too personal to be useful to others. https://www.dropbox.com/sc/9p203cy5gaa7giy/TkefIrSpgX

Slim ROM, .12 radio, stock auto brightness, high accuracy location, everything always connected always synced even overnight.
[Nexus 5 Original Android Development] mikeius89:
Nova launcher and purity latest build runs flawless for me on 36. :D
[Nexus 5 Original Android Development] AhmedFaiz:
V 0.36 flying on my device. Since it was out. Nice to be here to read all this info.

Thanks. :)

Nexus5/PA4.2 Beta4/ElementalX v0.36
[Nexus 5 Original Android Development] drawde40599:
I use nova with default kernel settings with no issues , but there was someone else having your issue and said changing the scheduler fixed it , u may want to try that
[Nexus 5 Original Android Development] D-m-x:
Today was the first time i tried this Kernel, and i have to say I'm impressed. It is working fine, and has some nice Features like S2W Timeout/off after pressing the Power Button. And also it does work with Francos App and others, so one can use the Color Profiles. Very nice work indeed!
[Nexus 5 Original Android Development] Lowresolution:
Hi ,

I am on stock Rom using the latest version of this kernel +stock rom ( very satisfied with the speed / battery life ) . However i am experiencing a weird issue , sometimes my screen flikers (like screen tears for a bit ), as in the colors jumble up and then come back to normal .

I was not having this issue on the stock kernel + stock Rom . I installed the kernel with all the recommended / stock settings in aroma . Any help guys ?
[Nexus 5 Original Android Development] drawde40599:
I run on stock and em not experencing this . but Did u install the Qualcomm GPU updates ?