yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Malnilion:
v38 seems to be working just fine on CM with F2FS.
[Nexus 5 Original Android Development] peecs121:
Same here

Super powered Nexus 5 running AICP/ElementalX
[Nexus 5 Original Android Development] bobby janow:
Is there any movement on the fact that some of us with a timeout on dt2w is not working? Unfortunately I did not enable the power button turn off and my battery took a huge hit over the past few days. I reflashed the kernel, enabled that so now it's ok. But my timeout is just not working on v38 and now I'm wondering if it worked on 37 or 36. Anyone?
[Nexus 5 Original Android Development] unsivil_audio:
I'm betting those of you with D2TW issues have some sort of rogue process keeping the timer from starting. Did you try this on a fresh clean install?
[Nexus 5 Original Android Development] bobby janow:
Fresh clean install of the ROM? No way. I'd rather just disable it. I'm still on stock from day 1. I'm not sure why I would want to do that with stock.
[Nexus 5 Original Android Development] :
Dt2W is always gonna eat battery, timeout or not. And if you reach for your phone often to check this or that, its going to be active more often than not.

Its an awesome feature....just not to practical for those that want great battery life. If you're a guy that enables everything and doesn't care about charging mid day....then yeah, its a great feature.

Just my 2 cents. ;)

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Nexus 5 Original Android Development] v3rsatile23:
Will this kernel work on slimkat? If so is it aosp?
[Nexus 5 Original Android Development] letmedanz:
It is quite strange.. cos as far as i've seen, it's the 2 of you only who are facing this & both of you are on stock..

the only explanation i can think of is some app that is generated crazy wakelocks..

perhaps [MENTION=4684315]flar2[/MENTION] would have some idea
[Nexus 5 Original Android Development] bobby janow:
Yes, I totally agree. But the point is that if I set a timeout on d2tw then it's not on all the time. If I forget to power button off then I only have about 15 minutes of drain which is quite doable. But it's not going off at all no matter what. So if I don't power button off then it drains all the time no matter what I set the timeout for. Now if no one else is having this issue then I'll just disable it since something else is at work here and it would be up to me to figure it out. But if there is an issue with the feature itself then perhaps it should be addressed.
[Nexus 5 Original Android Development] NexusFanBoy:
With 0.38 I'm having some strange screen flash (750uv) dunno why, but returned back to 0.36 for now

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] szucsgf:
Yes it will work. AOSP.
[Nexus 5 Original Android Development] drawde40599:
Just because your running stock dosent mean u can't have ROM issues causing kernel issues . fresh wipe or dirty flash may be good idea . I'm running stock and it works fine, at least try a dirty flash , here's 99% stock ROM its same exact ROM Google gave us its just rooted http://xdaforums.com/google-nexus-5/development/rom-android-4-4-2-kot49h-rooted-busybox-t2557523
[Nexus 5 Original Android Development] flar2:
Could you check /sys/android_touch/wake_timeout ?

Whatever value is there is the number of minutes until the timeout. If it's 0, then it's disabled.

Make sure there's a number in there, like 1 for example, then shut the screen off. Wait until it's supposed to be triggered, then send me the output of dmesg

eg: dmesg > /sdcard/dmesg.txt

Not the kernel
[Nexus 5 Original Android Development] drawde40599:
Did u try no UV before u went back ? Do u have GPU updates installed ?
[Nexus 5 Original Android Development] bobby janow:
The wake_timeout was indeed set to zero. I changed it to 1 and rebooted. Sent the output to you too.
[Nexus 5 Original Android Development] simplyazn04:
I havent checked this thread for a couple of days because 0.36 is so stable for me and thought flar2 mentioned he wouldnt release another update until 4.4.3 roll out but this is a pleasant surprise! Will test for a couple of days and post results now that i can post in development section :highfive:

-Also see a lot of familiar posters in this thread from the Mahdi rom thread, coincidence? I think not

-Also wanted to thank Flar2 for your awesome work. I was a former Franco kernel user when i first rooted my N5. I originally flashed this kernel because i wanted dt2w but it drained too much battery for me. I went back to Franco and there was a significant difference (to me) in terms of smoothness so i just disabled dt2w. Have not looked back since, great work you're doing here!
[Nexus 5 Original Android Development] PetritH:
Yeah, ElementalX + Mahdi rocks
[Nexus 5 Original Android Development] szucsgf:
ElementalX + Anything rocks [emoji6]
[Nexus 5 Original Android Development] Syk69:
Truth! I would even consider running IOS if it came with elementalx lol. Too far? :D
[Nexus 5 Original Android Development] Venomous Viper 119:
The UV setting we get to choose in the aroma installer says -75min. I thought it was -75mV & chose it. I don't have any issues but its meaning turned to be something else. Is -75min = -75mV? Also wouldn't it be more convenient if the UV options are mentioned in the mV in aroma installer?
[Nexus 5 Original Android Development] GCbard:
I have not tried it yet. No one has responded thus far. Looks like not many people use it.
[Nexus 5 Original Android Development] drawde40599:
Ya , the F2fs thread says there's pretty big improvement, and there are some serious android users in here but ya your right no one seems to use it . I wanna try it but just don't have the time to backup since it erases everything on the phone
[Nexus 5 Original Android Development] FuMMoD:
It's a hassle because if you flash a rom that doesn't support it then it wipes your phone. I'm not sure what roms are even supported but I fear anything I flash will format my phone and wipe everything.
[Nexus 5 Original Android Development] Pretoriano80:
A ROM should never wipe your sdcard no matter if you are on EXT4 OR F2FS,normally it will only wipe /system, /cache or /dalvik.

With F2FS any ROM should work as long as you flash an F2FS kernel after flashing the ROM. You only need to wipe your sdcard when switching from EXT4 to F2FS or viceversa.
[Nexus 5 Original Android Development] 7ewis:
I'd like to know this too. It is quite confusing!
[Nexus 5 Original Android Development] CyberScopes:
A bit off topic to the current conversation but just a warning to those who disable fsync - my /data got wiped a few weeks back and after looking for a reason the only thing that could actually relate to the random wipe was this. Luckily i had a backup. Either way this kernel is still the best out there :good:
[Nexus 5 Original Android Development] Pretoriano80:
Disabling FSync is always a bad idea (at least this is my opinion) because there are high chances to corrupt your data and especially with F2FS ( fsck only detect error with F2FS but can't repair).
[Nexus 5 Original Android Development] CyberScopes:
Yeah i always leave it enabled now
[Nexus 5 Original Android Development] NexusFanBoy:
with 0.36 i had 725mV, instead stock values and it worked good! Then Flashed 0.38 (same values) and noticed that screen behaviour.

Trying now 0.38 with no UV...Sorry what do u mean for GPU updates???
[Nexus 5 Original Android Development] pcphobic:
Totally agree.
[Nexus 5 Original Android Development] FuMMoD:
Ah that's not so bad then. When I read it it was still very early in development. Might consider trying it now. Okay that's enough OT for me lol.
[Nexus 5 Original Android Development] Venomous Viper 119:
So nobody has an answer?
[Nexus 5 Original Android Development] PetritH:
Would like to know if anyone is experiencing lags on homescreen or app drawer with nova launcher? Thanks
[Nexus 5 Original Android Development] waallen:
I am getting those screen flickering flashes too. Using default settings (no uv) besides gboost being disabled.
[Nexus 5 Original Android Development] NexusFanBoy:
Thank you so I'm not the only one...

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] flar2:
This problem is not due to the kernel. Wipe and reinstall if bothers you.

Is it possible that you have enabled the wake timeout? It will turn the screen on and off quickly at the specified timeout.
[Nexus 5 Original Android Development] marshall39:
Sorry for my probably stupid question , but at the beginning I wanted to keep my Nexus fully stock , but I miss only one thing ; double tap to wake.

So , if I flash the stable version 0.34 , is it possible to keep everything stock (voltage etc) and only add the double tap? Is it the way the kernel is made or will I have to tweak anything to adjust everything like stock ?

Cheers
[Nexus 5 Original Android Development] waallen:
No, I don't have it enabled. Anyway I have flashed 0.34 back and the screen isn't acting up anymore.
[Nexus 5 Original Android Development] szucsgf:
Some of this kernel's default settings are different from Google Stock kernel settings, if that's what you mean.

You can flash this kernel using all its default settings + dt2w and you'll be just fine. But if you want to bring things closer to Google Stock settings:

Governor: Ondemand

Scheduler: cfq

RAB: 128

Voltages on this kernel are the same Google Stock.

But it might be a good idea to try default kernel settings, as they're more battery friendly than Google Stock without sacrificing performance.

And don't forget dt2w will cause noticeable additional battery drain while your screen is off.
[Nexus 5 Original Android Development] PetritH:
Ok, if you are running art u dont have that lag with nova launcher.. interesting
[Nexus 5 Original Android Development] benfiller:
To keep stock settings just choose stock options (cfq and read ahead 128 as szucsgf said) during the aroma installer and write a script and put it in init.d folder with rwx-rx-rx rights :

#!/system/bin/sh

# CPU Governor

echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

# TCP Congestion Control

echo cubic > /proc/sys/net/ipv4/tcp_congestion_control
[Nexus 5 Original Android Development] DarkRyoushii:
I am interested in converting my partitions to F2FS. Currently I'm running OmniROM and ElementalX 0.38. I was reading up on this and and saw in the OP

I was wondering if you could expand on this a bit as to what it means and how I can achieve what I'm after,

Thanks!
[Nexus 5 Original Android Development] flar2:
There are different mount options in the ramdisk for F2FS. ElementalX reuses the ramdisk from the previous kernel.

Basically, all you need to do is get up and running with F2FS, then install ElementalX as the last step.
[Nexus 5 Original Android Development] ali262883:
Finally after a long use of 0.34 i directly Flashed 0.38.. Its better.. Thanks for the great kernel :) elemental x for life
[Nexus 5 Original Android Development] drawde40599:
Qualcomm has updated GPU software on there site for this phone , some ROM devs are including them into there Roms even tho there not stable for everyone , and they can cause issues for some .
[Nexus 5 Original Android Development] NexusFanBoy:
No I did not enabled any wake timeout, simply problem gone away returning back to 0.36...then I returned to 0.38 and now all works good...dunno

Inviato dal mio Nexus 5

---------- Post added at 06:13 PM ---------- Previous post was at 06:09 PM ----------

Also stock ROM, where I am???

Inviato dal mio Nexus 5

---------- Post added at 06:20 PM ---------- Previous post was at 06:13 PM ----------

Ok understand. That's a flashable GPU driver. Now I'm going to try it

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] 7ewis:
Can someone explain to me why I might be getting such bad battery life?

I flashed 0.38 last night, so the kernel has had time to settle in. My phone has been on for about 10 hours, and SOT of about an hour. I haven't done anything processor intensive, I usually use it a lot more during the same time frame.

Anyway, my battery is now down to 60%. Which by Nexus standards, is awful! On the stock kernel, I could get around a day with 5 hours SOT. I thought by flashing this, and underclocking, and undervolting slightly it could improve on that, but it appears I was very wrong.

There isn't anything that could be conflicting, because I'm on a fresh stock ROM, with only a few apps installed. I have the brightness set low, and Location off.

I did briefly have DT2W on, but also had the Power toggle, and a 15 minute sleep for it (Which did work, I have seen some people saying it wasn't working for them). But after I started noticing the huge drain, I disabled it all; the drain is still occurring though.

Unfortunately I haven't installed BBS yet, as I didn't think it would be necessary.

I love the idea of custom kernels, and want to be able to brag about the improvements; this is the first kernel I've ever flashed! I'll post screenshots later, if that could help find out what's happening.

What has happened to my battery?
[Nexus 5 Original Android Development] drawde40599:
If your on stock ROM then u don't have the updates and ignore me ;) , if your not stock and didn't install them then read threw changlog of your ROM . I was just wondering if u had them because that could been your issue because some do have issues with them . but I would do what flar2 said few posts back if was me .
[Nexus 5 Original Android Development] NexusFanBoy:
Ok i was on stock rom without GPU update. Just flashed now to see what changes

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] gut4:
Where I can find kernel logs? I get crash on 0.38. Dt2w was on, but stop working and screen doesn't wake up even with power button. Only long hold power button give me reboot.
[Nexus 5 Original Android Development] GragonV:
humh, why the one for Nexus 5 doesn't have the in pocket function (for disable dt2w/s2w) like other versions??

on .36 and notice that ondemand can give better performance comparing to elementalx :( (in dolphin and some game). Wonder how's this .38 doing (a lot of crash comment above.. :-SSS)
[Nexus 5 Original Android Development] r0cky0790:
You can't consider the kernel settled in overnight, especially off of one charge.
[Nexus 5 Original Android Development] GragonV:
May I know your setting? :) or it's all default :D

Mine is pretty disappointed with .36 and a bit lag when running dolphin and some 3d game :(
[Nexus 5 Original Android Development] Tylog:
Gpu 320 , deadline , disable gboost, no more changes at the moment :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] nealkoy:
Hi any chance of using cf.lumen and uninstalled the drivers? Cause that's what happened to me with my screen acting up and flickering here and there. reinstalled the Lumen drivers and everything worked back to normal.

Definitely not kernel, just sharing :)
[Nexus 5 Original Android Development] flar2:
No pocket detection because I don't know how to control the proximity sensor from kernel.

0.38 is completely stable, nobody is having crashes due to the kernel.
[Nexus 5 Original Android Development] waallen:
Hi, thanks for your reply! No, I have been using Lux for several months now. I just dirty flashed the new vanir nightly and then flashed 0.38. I noticed the screen flashing thing (it's as if the whole display is coloured with random pixels for a split second) quite soon, then proceeded to flash 0.34 back (over 0.38, without reflashing the rom) and everything is smooth now. I don't mind being on 0.34 that much anyway.

However someone mentioned that it could be caused by the unstable gpu drivers that are being used by some rooms, I guess it's not my case since there's no trace of it on vanir xda thread nor in the changelogs.

Edit: not hinting that the flashing is caused by the kernel. Just reporting what's happening and what's working for me.
[Nexus 5 Original Android Development] EdgA#1:
what rom u're using? I've no problems on Mahdi, ele 38, and lux

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] giarob78:
+1
[Nexus 5 Original Android Development] netinetinet:
..

I'm on CM (currently M5), I had no problems with neither build .. 038 is the best..
[Nexus 5 Original Android Development] giarob78:
and I'm on last Carbon ROM, last aosp El kernel and no micro lags on GEL, everything is fast, smooth and amazing! thx for this amazing kernel [MENTION=4684315]flar2[/MENTION].
[Nexus 5 Original Android Development] DrErect:
Tried opening the camera this morning and it failed several times. But a reboot seemed to solved the issue.
[Nexus 5 Original Android Development] fkloznica:
I was on slim and elemental for 30 days and one day screen flashing started. I never seen that before,on any mobile device. Every 30sec my display turns in random pixels ,and that stays for 0.5 seconds and than its normal for 30 sec and than again. I was 30 minutes from selling my device but then I clean flashed slim ROM and after that elemental and now for 3 days all is OK.

Don't know what happened
[Nexus 5 Original Android Development] bobby janow:
Tried it again and this time it worked. I saw the screen flash and I knew it had timed out. What is the point to the elementalx.conf timeout value if it's the above value that matters in the wake_timeout file? Because I set it to 5 minutes and that's when it timed out. But in the conf file it's set to 1 minute. Since it's working I'd rather not mess around with anything at this point.
[Nexus 5 Original Android Development] flar2:
Whatever is set in elementalx.conf is what it gets set to at boot.

If it's set to something else, thwr is either something changing the setting or the init.d script is not being executed at boot.

To see if the init.d script is working, check /data/local/tmp/elementalx.log
[Nexus 5 Original Android Development] hooliganx:
everything's fine here.

no lags or problems.

0.38 much more battery friendly than 0.36.

(for me).

thanks [MENTION=4684315]flar2[/MENTION]

N5*SlimKat.b4*Elementalx.038

*ART*TWRP.2.7*0.23
[Nexus 5 Original Android Development] bobby janow:
Ok. the elementalx.log has timeout value= with nothing there. The init.d script was a little complicated for me to figure out so I just reinstalled the kernel. In the wake_timeout it's once again set to zero even though the .conf file has a default of 15. So my init.d script doesn't seem to be working if I read this correctly. How do I correct this? And of course, thanks for your time.
[Nexus 5 Original Android Development] adl:
Sorry for noobish question, got the Nexus three days ago (coming from the S4). Can I flash this Kernel on top of Slimkat ROM? I am just hesitating, cause it says "no custom Kernel" but Slimkat uses it's own custom / modified Kernel, as far as I know. Do I have to flash some stock kernel before flashing elementalX? Thanks for any help.
[Nexus 5 Original Android Development] jcpq:
.36 and .38 on mahdi rom drain battery very faster.
[Nexus 5 Original Android Development] toocool4all:
Hmmm I m asking my self why was I not using this in first place ??

Sent from SOKP ROM with chaos kernel .
[Nexus 5 Original Android Development] letmedanz:
Yes.. you can flash elemental kernel (AOSP) version on to slim kat...

nothing else needs to be flashed
[Nexus 5 Original Android Development] Tylog:
Yes adl. Aosp is the one you need, no need for stock kernel.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] :
Check your setup and look for rogue apps.

Have gsam or something similar to see what's draining your battery?

Its not the kernel. ;)
[Nexus 5 Original Android Development] :
Sounds like you undervolted too much.

Battery life is very important to me. I never used 0.34 and am currently on 0.36. Some people are saying that 0.38 is bad too. Should I revert?
[Nexus 5 Original Android Development] paychex:
you should be fine. make a backup and dirty flash your rom first. make sure you flash the right kernel aosp/caf
[Nexus 5 Original Android Development] PetritH:
To me, .34 had great battery life which I didn't get on .36. Now on .38 im getting better battery life than in .36
[Nexus 5 Original Android Development] Spinergy02:
Best benchmark I've had on this device. Overclocked to 2.75ghz with the second thermal throttling option. Been quite stable with excellent battery life too.

Edit: running 0.38 on CM11 nightly
[Nexus 5 Original Android Development] _Infamous_:
Getting freezes on .38 I have to hold power to get phone working again flashed back to .36 and no issues
[Nexus 5 Original Android Development] drawde40599:
Your the first one in the whole thread to report anything like this . what ROM ?, are you UV , OC , patches , hacks , GPU , GBOX did u try a different kernel in between ? u should Give some more info if u want help , but its something on your end most likely
[Nexus 5 Original Android Development] trungquan_it:
Hm... I'm running AICP with 0.38-cm version and I had a strange issue. I can't see any comment in Facebook app. Then I revert back to 0.36-cm and everything is normal.

I used same settings for 0.36 and 0.38, only lower CPU frequency to 1.4Ghz and UV to 700.

It's funny :D
[Nexus 5 Original Android Development] JJsevol:
I had the same issue! I also had loading problems in apps like Instagram and podcasts. I switched to .36 and everything started working.
[Nexus 5 Original Android Development] Spinergy02:
I just checked Facebook on 0.38 and it's working fine.
[Nexus 5 Original Android Development] _Infamous_:
Man people are so protective not every phone works with every kernel build. I'm running mahdi rom no tweaks no uc,UV,oc or any thing else and only have 10 apps installed. It mostly happens when in Facebook and some times no picture or feed like others stated
[Nexus 5 Original Android Development] trungquan_it:
Hm... I found out why I had this issue. When updating to 0.38, after I switches wifi on, Play Store is auto updated Facebook, but when I check, the latest update version is the same version I had and the update date is 16/04/2014. So it means Facebook is updated even when I'm running the latest version. After update, the problem occur as I said before.

So I restore the backup, check on Play Store, my Facebook app is up to date. But when I flash 0.38 and boot up, Play Store is updated my Facebook again. If I cancel the update, everything works fine.

Do you know why Play Store keep telling me to update Facebook even I had the latest version? This only occurs if I update 0.36 to 0.38. Hm... it's strange...
[Nexus 5 Original Android Development] drawde40599:
Protective ? Ok . There are many many many here using that ROM without any issues . good luck
[Nexus 5 Original Android Development] flar2:
This kernel works on every single nexus 5 ever manufactured unless it's broken or defective.
[Nexus 5 Original Android Development] _Infamous_:
There are 3 people above me that have issues with this kernel when on Facebook that's all I was stating .36 just works better for me no big deal. This is the only kernel I use its my favorite by far I was just stating a big I was having :)

---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------

Really is isn't know that. Nowstop replying to my post and let's move on. I love this kernel and .36 just works better for my phone.
[Nexus 5 Original Android Development] gut4:
[MENTION=4684315]flar2[/MENTION] I think we have a problem with 0.38.
[Nexus 5 Original Android Development] _Infamous_:
+1 thankyou
[Nexus 5 Original Android Development] PetritH:
Reverted back to my lovely .34, nothing can beat this version :)
[Nexus 5 Original Android Development] josemedina:
Best Kernel there is. Elemental X by flar on my HTC One(M7) and on my Nexus 5. Fantastic on both devices.

Thank you for all that you do.

This guy is an absolute beast!!!
[Nexus 5 Original Android Development] hanschke:
rename the 38 to 36 and all people will say 36 is great and we have a placebo :D
[Nexus 5 Original Android Development] -Johannes-:
It's a problem with your Rom, i had the same problem with this Rom. Now on pac with all the same apps and settings and also elemantal x kernel, no problem!

Gesendet von meinem Nexus 5 mit Tapatalk