yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] k20-:
Did I mention about touching the recovery? If you want to repair your broken recovery, you can simply use this app https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools (fast and easy).

No need to delete the twrp. That's my way.
[Nexus 5 Original Android Development] drawde40599:
His recovery is corrupted common issue with twrp , u told him to resore or wipe which will do nothing .... Ya I own a nexus I don't need apps like that
[Nexus 5 Original Android Development] letmedanz:
Thanks FuMMoD :)
[Nexus 5 Original Android Development] suneet mehta:
I don't know what the problem is, but this is happening a lot on 0.35 cm version.. The frequencies change themselves.. I don't know why.. It happens anytime.. Even when I select to set kernel settings on boot in trickstermod..!!:/

Rocking BAM with ElementalX.

Hit thanks if I helped you.;)
[Nexus 5 Original Android Development] drawde40599:
Have u looked or watched freq with a app like prefmon or system monitor ? Trickster may be lying to u ( mpdecision )
[Nexus 5 Original Android Development] doomed151:
I'm getting microstutters with 0.35, can sometimes be felt when using normally but is most noticeable during video playback (juddering). Reverted to 0.34 and all is well. Running Omni nightlies.
[Nexus 5 Original Android Development] letmedanz:
i've had issues with Trickster on Elemental.

uninstall it & see if the issues persist
[Nexus 5 Original Android Development] bobby janow:
With the programmable settings on dt2w/s2w that shouldn't be the case. Unless, of course, you have it set to never timeout. I have it set for 30 minutes and I get hardly no drain at all during that time. 15 should even be better.

---------- Post added at 12:22 PM ---------- Previous post was at 12:20 PM ----------

Kernel wakelocks never told me much of anything. Take a look at partial wakelocks for a clearer picture of what is waking your phone.
[Nexus 5 Original Android Development] letmedanz:
Actually i have set it for 5 mins :)

but i have wi-fi on & some or other app would cause a drain of 8-10% for say 6 hours..

as an average..

am quite ok with that though cos i haven't really greenified anything :p
[Nexus 5 Original Android Development] bobby janow:
That seems like a lot of drain for no SOT. I mean if you're ok with it then so be it, but come on man. You got to find out what it is for us. :D Inquiring minds want to know. BBS partial wakelock should tell you I think. I have found that the donate Greenify will even tell you what woke the app giving you the wakelock. Not that there is anything I can do about FB waking Instagram or Pandora waking Google + but at least I can yell at something.
[Nexus 5 Original Android Development] droidshadow:
curious about this kernel...

I have used the ElementalX Kernel for both N7 FLO and Nexus 7 DEB.

I am going to order the Nexus 5 directly from Google because I want the 32GB model. Has this kernel been tested on the Nexus 5 32GB phone or only the 16GB model?

-droidshadow
[Nexus 5 Original Android Development] thereal_bigjake:
I have been running this kernel on my Nexus 5 32gb for a few months and love it [emoji1]
[Nexus 5 Original Android Development] drawde40599:
I'm noticing the same with the stutters and 35 , its not all the time tho , trying find a way to produce 100% of the time but no luck yet . I'm stock running ROM with Gbox no patches or hacks
[Nexus 5 Original Android Development] letmedanz:
haha.. true.

but i haven't really had time to read & understand how it works..DUH

Especially since the BBS page is like what 1000 pages??

though i have greenify donate & bbs, haven't really gotten down to it..

BUT now that you posted what you did, i guess it's time to get this done!
[Nexus 5 Original Android Development] drawde40599:
It makes no difference , I have both a 16 and a 32
[Nexus 5 Original Android Development] letmedanz:
May cos it's stock? :D

i've had 0 stutters or any issues actually..

in fact it's just been 2 cycles since installation & the phone already seems to have set in nicely..

IMO i've seen better (the slightest) performance & battery with CM roms than AOSP

currently running crDroid & its really great..

not over loaded with unnecessary features, stable but with features that make sense

i know you love being on stock, but i guess you could give this baby a run
[Nexus 5 Original Android Development] jumparound246:
<br />

I'm noticing the same with the stutters and 35 , its not all the time tho , trying find a way to produce 100% of the time but no luck yet . I'm stock running ROM with Gbox no patches or hacks<br/>

[/QUOTE]

Guess gbox isn't compatible with art but i if it is compatible or you can live without using it you should try art. No lag or stutters whatsoever...
[Nexus 5 Original Android Development] drawde40599:
Ya I'm done with custom Roms/kangs ;P . 34 and 35 being the same kernel basically I think it may be this new I/o code . stutter not bad at all but I see it in apps like G+ pretty good and it gos away going back to 34 .
[Nexus 5 Original Android Development] letmedanz:
Not only GravityBox, but Xposed itself is incompatible with ART
[Nexus 5 Original Android Development] jumparound246:
Thanks for clarification.

And after rereading the posts i'm not sure if art was a good suggestion...it stutters while video playback, art is for smoothness in every way. Don't know if it would also help with the explained issue...it's definitely worth a try, though.
[Nexus 5 Original Android Development] letmedanz:
ART is definitely the way forward, no doubt about it, but it still has some distance to go.

perhaps by Android 4.5?? :P
[Nexus 5 Original Android Development] bobby janow:
Only thing holding me back from ART. But the Dev did say once Google formalizes the standard ART he will support it. If I recall the reason is that it might change before release and it was just too much work to support various iterations.
[Nexus 5 Original Android Development] eug89:
It could be the patch from faux that flar2 added in 0.35. On faux's github franco commented that it causes some lag, probably similar to what you're experiencing : https://github.com/faux123/Nexus_5/commit/fd47ebdf86c832fbc659e2b4a26762ea9b31c03b
[Nexus 5 Original Android Development] ralpheboyo:
Honestly I have no idea what you guys are talking about...I have no glitches or lag...(row/512)...
[Nexus 5 Original Android Development] ali262883:
Elemental x 0.34 will be the final version for me.. Seems like i'll stick with it for life :) just loving it

---------- Post added at 03:13 AM ---------- Previous post was at 03:08 AM ----------

Awesome this is
[Nexus 5 Original Android Development] drawde40599:
I'm using same set up as u r but every phone is different so makes sense were all not feeling it . its not bad but when your used to not having anything wrong u get spoiled ;P
[Nexus 5 Original Android Development] DoesntPostAThing:
I also noticed micro stutters in 0.35, and possibly coincidental event-x kernel wakelocks. For now going back to 0.34, which was awesome for me.
[Nexus 5 Original Android Development] droidshadow:
that's good news...

Thank you so much for your response...I am a big fan of the ElementalX kernel myself and have been using it with both of my Nexus 7 2013 tablets. As soon as I get my next paycheck I am going to order the Nexus 5 from Google and I can't wait flash this kernel!

Thanks again for the response...

-droidshadow
[Nexus 5 Original Android Development] flar2:
I notice occasional micro stutter on .35 as well, will be reverting the experimental sched changes
[Nexus 5 Original Android Development] Venomous Viper 119:
Weird but I didn't notice any stutters whatsoever. Why is it that many people even on the Franco kernel thread as well as here have 2 different experiences? Some experience stutters, while the others don't at all. It's weird.

Btw, you can avoid using greenify by completely rebooting your device once before it sleeps in your pockets for hours. This way you can ensure that all the apps that may have run due to the data connection being on, etc. will be totally suspended. Also don't leave your data on when you're not using it to prevent unintended background app activity. This way you can minimize the wake locks & get more standby time. It's very rare that you loose no juice for 5 to 6 hours of standby but I'm sure that this way you'll loose just 1% for 5 to 6hrs of standby.
[Nexus 5 Original Android Development] maidenboston:
was able to install 9.0 with kitkang cm11...

seems solid, thanks
[Nexus 5 Original Android Development] Phazmos:
Neither. OK on a few different roms and kernel combos, this and Franco cause the crash. Tried clearing data, checked for leftover files and folders, still crash. My money is on an antutu problem. It also doesn't like Franco.
[Nexus 5 Original Android Development] DemosZevasa:
So I'm cheating on Trinity with this kernel and I'm loving it, good battery life and performance! Great work [MENTION=4684315]flar2[/MENTION]

Sent from my Nexus 5
[Nexus 5 Original Android Development] dead0:
I've managed 35640 on antutu with stock cpu & uv with 0.8 :)
[Nexus 5 Original Android Development] Shudder123:
do i need to flash 0.8 before 0.9? or i can just flash 0.9 directly? a bit confused but the whole existing ramdisk thing..
[Nexus 5 Original Android Development] flar2:
Nope, just flash 0.9
[Nexus 5 Original Android Development] opz187:
So for some reason this kernel and bricked kernel have my phone running extremely hot. Like hitting 100° hot, and that's not doing anything intensive, like browsing the web. Franco and others run fine. It sucks cuz the performance on this is unmatched, but I don't wanna bake my phone to death. Any suggestions?
[Nexus 5 Original Android Development] NoobieExtraordinare:
I'm currently on the stock kernel and stock everything. I still don't understand how the attached picture makes any sense? My device is a Nexus 5.
[Nexus 5 Original Android Development] Vortex1969:
PSX and version 0.9 at 2700 kernel just keeps getting better.:thumbup:

PSX for Nexus 5 under the hood
[Nexus 5 Original Android Development] sirbanger:
As a first time flash running stock rom/kernel do you recommend 0.9 or 0.9b?
[Nexus 5 Original Android Development] dead0:
If coming from stock, either should be fine
[Nexus 5 Original Android Development] GUGUITOMTG4:
Can I skip this update if I don't use any Wake features? I'm on 0.8
[Nexus 5 Original Android Development] jeanmauri90:
Is this kernel compatible with cataclysm ?
[Nexus 5 Original Android Development] Flakito97:
What is your exact set up. TCP congestion? Scheduler? Min frequency? Max frequency? Mp decision on or off? Fsync on or off? Under volt? Every thing else that you have tweaked? Numbers to me really aren't nothing. I'm just wondering how everyone is getting these numbers when I can barely reach 22000 at 2.4 GHz Ovclocked ? And when I over clock a bit more or change my setting in trickster mod, antutu benchmark makes my phone reboot...
[Nexus 5 Original Android Development] dead0:
im still running 0.8 with cataclysm rom. running very smooth
[Nexus 5 Original Android Development] benzso63:
Yep they do. I didn't install them.
[Nexus 5 Original Android Development] nealkoy:
Have you tried flashing dalvik optimization?
[Nexus 5 Original Android Development] Shudder123:
With 0.9b I seem to be getting a freq. Cap at 1.5 GHz. Keeps reverting no matter how much I change it... Anyone?
[Nexus 5 Original Android Development] JmPTaz09:
Not sure... I don't use any kernel control apps... Recommend just setting this up in the installer and letting it rip; performs great for me. I just use all the preselected options since those happen to be exactly what I'm looking for!
[Nexus 5 Original Android Development] MrFishiz:
Hey I got a question .. What does using existing redmisk means ? If I came from faux kernel then it will use it's redmisk? And what is redmisk
[Nexus 5 Original Android Development] flar2:
It's very subtle. Most people probably won't notice it, or care.
[Nexus 5 Original Android Development] FuMMoD:
Rare to lose no juice in 6 hours eh? Wifi and data on all the time too. Just got to learn to greenify everything and make sure you don't have wakelocks. Dt2w and s2w features off of course.
[Nexus 5 Original Android Development] Venomous Viper 119:
Obvious as it is. People that can understand it can at least try it out.
[Nexus 5 Original Android Development] ali262883:
Especially while opening Facebook and chrome
[Nexus 5 Original Android Development] Venomous Viper 119:
I said rare, not impossible. Every n5 differs & the way people analyze the wake locks & then greenify differs too. Also the way everyone uses their phones differ too. The approach is to minimize the battery drain over standby as much as possible & I'm not contradicting your experience. Let's contribute to enhance the experience together.

Btw, what's the screen on time you get?
[Nexus 5 Original Android Development] :
I also can not confirm that the .35 Version isn't that good like the previous Version. All here is stable and working great with top battery life. Dont know whats wrong with the other N5's??
[Nexus 5 Original Android Development] doomed151:
I'm not sure about battery life but everyone should have the stuttering issue with 0.35, either you notice it or not.
[Nexus 5 Original Android Development] hellsgod:
I had this problem with the stutters in my kernel, too. franco had it also and dorimanx, too. After reverting one sched commit, they went away. Not everyone sees all stutters. I see stutters where the most people don't see any for example :D faux reverted this sched commit, also: github

hells
[Nexus 5 Original Android Development] FuMMoD:
I average 5 hours screen on time of moderate usage. I disabled everything I don't use, especially location reporting features.
[Nexus 5 Original Android Development] Venomous Viper 119:
Hmmm.. Good sot. I get around 5hrs 30 mins sot. As of now, the battery is at 69% & the sot is 2hrs & 15mins. I'm getting a hint that the 5hrs & 30 mins. sot I used to get is going to be prolonged.
[Nexus 5 Original Android Development] magnamentis:
different people use different means to achieve their goals so far so good but honestly speaking, i find this thing with the reboot not

such a good idea to recommend to others because:

did you consider how much juice is used during boot, media library check and update and all the apps starting in the background when not

hindered to do so can eat up to 3% of juice in the first 10 minutes after boot and so i believe that this recommendation instead of greenifying

does somehow not really fit in when talking about improving battery live. with these 1-2% used after boot my device lives about 10-11 hours

through the night for example :)

EDIT: of course this could work when booting under charger and disconnect the charger about 10 minutes afeter boot but that would

mean that there is a condition which has to be met which can be inconvenient. i mean sometimes i just wanna leave without big preparations & procedures :)

just confirming again, i had now 3 out of 5 days less than 1% usage in 8 hours over night. 1 of the 5 days was the day after updating to 0.35 and the other when that great result was not achieved

was when i tried to activate profiles by means of alarm clock instead of tasker which produced me nothing but 2 missed alarms with the appropriate wakelocks.

so i remember when i tried to achieve 5% in 10 hours with my note 2 and now i get 0.9% in 8 hours with my nexus 5 and 3% in 8 hours with the

n7100 which is so great that finally i consider the battery as the main goal for improvement for myself as solved

enjoy

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.35, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )

Please Click The Thanks Button If I Helped You Out ______________________________________________________________________________
[Nexus 5 Original Android Development] indian84:
For Mahdi ROM, which Kernel should I flash? AOSP or CM based?
[Nexus 5 Original Android Development] Venomous Viper 119:
I usually reboot when the device is 100% charged & after booting up, I leave it for charging for another 30mins or less. This time usually coincides with me going to my college where my phone stays on standby for 5 to 6hrs. Greenify is not at all a bad idea. There are just different ways of doing the same things. Either you suspend the apps before standby by rebooting or just hibernate them using greenify. Both help in a better standby.
[Nexus 5 Original Android Development] PetritH:
AOSP
[Nexus 5 Original Android Development] gpvecchi:
[MENTION=4684315]flar2[/MENTION] Could you please add vibration intensity in Aroma? It's in cfg, but it needs manual editing...
[Nexus 5 Original Android Development] hooliganx:
don't see where is the problem do it manually. [MENTION=4684315]flar2[/MENTION] made a great kernel for us... change one number in root explorer and reboot is not so difficult.

N5*SlimKat.b4*bricked.exp-g64bab97*dalvik*Xposed*TWRP.2.7*0.23
[Nexus 5 Original Android Development] RhapsodyK:
Try "Kernel Tweaker" from Play Store. It's free and it is user friendly. Also you can easily change the vibration intensity.
[Nexus 5 Original Android Development] sirovai:
Try new builds of other kernels those days. Elemental still remains the smoothest, more battery friendly and more features built in. Good work flar2!

P. S. : Can i ask you why all other kernel devs remove MP decision from their kernel while you use it? With MP on everything is smoother, i dont understand why the first thing that a dev do is remove it...

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Chochiwpg:
Because some feel that it is too aggressive at ramping up the CPU frequency when the screen is turned on and touched. I personally prefer it, but a lot of people think it's a waste of battery when this constantly happens. As flar shows you can keep MP active while still having great battery. So it's all about preference I guess.
[Nexus 5 Original Android Development] PhoenixAG:
As others have noticed, 34 was amazing at battery life. 35 with same settings isn't as good.

Lots of random wakelocks (events).

Same rom same usage.
[Nexus 5 Original Android Development] sirovai:
Also I prefer MP active, i guess that kernels without mp need to keep freqs higher to reach the same smoothness. Imho

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] veedubrocks:
I just installed this kernel and I'm loosing my data connection. Any ideas? I'm on Slimkat

Thanks in advance.
[Nexus 5 Original Android Development] rachanta:
No such problem here. I must say AICP with ElementalX is a breathtaking combination. My AICP in steroids.

I really do hope I succeed in doing an integrated ElementalX + AICP build soon.

Great work [MENTION=4684315]flar2[/MENTION]!
[Nexus 5 Original Android Development] FuMMoD:
Screen on time is totally dependant on the user and apps that are running. If i treated my phone like my old S2 by turning off data whenever I didn't use it and completely disable everything except mobile signal I could get easily over 7 hours sot. I have my data on all the time though.
[Nexus 5 Original Android Development] hooliganx:
and....??

more details!

came from stock slim kernel? other kernel?

what modem/radio do you use?

fresh flash? dirty flash of rom?

N5*SlimKat.b4*bricked.exp-g64bab97*dalvik*Xposed*TWRP.2.7*0.23
[Nexus 5 Original Android Development] Venomous Viper 119:
Definitely. Now I've got 6hrs & 23mins of sot. Data wasn't off all the time. Includes nearly 3 hours of heavy use. 3% left.
[Nexus 5 Original Android Development] veedubrocks:
Came from a clean install of slim

Came from stock slim kernel

0.23 radio

Wipe dalvik/cache before and after installing this kernel. So dirty.

Telus
[Nexus 5 Original Android Development] drawde40599:
Just a guess but those kernel dev's that remove it use there own hotplug code they have been working on and perfecting since galaxy nexus days . I've always liked Google's mp decision just hated how they set the throttling

---------- Post added at 08:33 AM ---------- Previous post was at 08:31 AM ----------

Do u still have a imei # . Have u reset your APN ? Or reset your Sim card? ( pull it out and reboot )

---------- Post added at 08:33 AM ---------- Previous post was at 08:33 AM ----------

Do u still have a imei # . Have u reset your APN ? Or reset your Sim card? ( pull it out and reboot )
[Nexus 5 Original Android Development] veedubrocks:
Thanks for the advice . Will try those and report
[Nexus 5 Original Android Development] biggofer:
stock

I no i can just reflash my stock ROM but is flashing stock boot.img , erasing elementalx.conf file and file in init.d folder enough to get me back to 100% stock kernel ? I didn't see anything in OP I may have missed it , I did look .
[Nexus 5 Original Android Development] Jonnyredcorn:
I searched for event0, event1, event,2 etc..wakelocks and came with nothing I was surprised. I have been getting these wakelocks with 34.cm version only along with the powermanagemenwakelock. Was wondering if anyone had found a fix or setup? I'm running gummy. I'm using interactive govenor and deadline i/o. system.ui is also usually at the top of my battery userage which never happened before, but that might be ROM related.

Image of the betterbatterystats
[Nexus 5 Original Android Development] rachanta:
Building aicp+elementalx again. Have decided to give it serious shot this weekend. Anybody who has done this? Pl do share steps if possible.
[Nexus 5 Original Android Development] NovaSlim:
Because every other phone should behave exactly like your phone?
[Nexus 5 Original Android Development] FuMMoD:
An idle phone of the same exact model will still perform like an idle phone. If there are no wakelocks or syncing going on in the background they will perform exactly the same.
[Nexus 5 Original Android Development] drawde40599:
No but he's right , if there's isn't something acting up in background everyone should see pretty close to those results . I do ....
[Nexus 5 Original Android Development] :
Exactly. ?

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Nexus 5 Original Android Development] flar2:
Reverted the sched tweaks that may have been causing microstutter.

Download

Stock/AOSP:

ElementalX-N5-0.36 *BETA*

ElementalX-N5-0.36-express *BETA*

Cyanogenmod/CAF:

ElementalX-N5-0.36-cm *BETA*

ElementalX-N5-0.36-cm-express *BETA*

Changes:

-revert sched tweaks
[Nexus 5 Original Android Development] NovaSlim:
I understand that part, except I could easily have different background apps running than you are in addition to different cell reception. There is no also need for me to "Check your wakelocks " when I already know what they are, I just need figure out a way to only hibernate at night with tasker+greenify.

Just because I posted idle battery results that are not as good as yours, it doesn't mean I am intentionally doing so to troll this thread.
[Nexus 5 Original Android Development] :
Issues are issues....and most can be fixed. Tasker should not be needed to help standby. ?

I'd troubleshoot those issues and not complicate them by involving tasker.

Just my advice. But to each their own. ?

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Nexus 5 Original Android Development] NovaSlim:
I will install BBS and investigate more, but most of my drains are from background syncing or poor cell reception.