yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] flar2:
RE: doubletap2wake for notifications,

The kernel doesn't know anything about notifications, and I don't want the app to start getting into stuff like that (need to keep it simple). The other complication is properly disabling wakegestures requires the screen to flash on and off.
[Nexus 5 Original Android Development] vickyjusme:
Just bought the app. Seems really easy to use and all the customizations are easy to find.
[Nexus 5 Original Android Development] t3rmin:
Thanks for your reply. I've tried various apps including Lightflow, and though they can add notifications that utilize the LED I haven't found any that will disable/affect the charging LED behavior.

What would you think about making the charging LED function default off? Then ROMs with support for configuring charging LED (like CM) will still be fine but the stock ROM will get the stock behavior (no charging LED)?
[Nexus 5 Original Android Development] ArcMage:
Under what I presume to be the same kernel settings I seem to be draining battery about 1% faster under 2.0.5, but that's well within normal variance.

That's 4.6%/hr, which I'm given to understand is pretty good anyways, so I'm satisfied.

Aside from that, do you suppose we could get a changelog for the app?

baPelyelatno alNexus 5 aydpelyelano aPelyelatno
[Nexus 5 Original Android Development] flar2:
I'm pretty sure it's off by default. At least I haven't specifically enabled it.

I haven't kept a changelog for the app, I just post the changes on the Play Store for each version. The changelog would be a mile long I think.
[Nexus 5 Original Android Development] ArcMage:
Alright, that's valid.

baPelyelatno alNexus al5 aydpelyelano aPelyelatno
[Nexus 5 Original Android Development] daihard:
I agree with [MENTION=4684315]flar2[/MENTION]. I use Cataclysm 5.0.1 with ElementalX 2.05. The LED doesn't come on during charging unless I specifically enable it through the Cataclysm setting. This charging LED option was just recently added in Cataclysm. Before that, the LED never came on while the phone was charging.

Cheers.
[Nexus 5 Original Android Development] t3rmin:
Well I'm not saying there might not be something funky on my end, but I'm not running a custom ROM like perhaps most other folks in this thread. Cataclysm in particular *does* have charging LED support, so that ROM itself may default to disabling it.

This is a pretty fresh re-install of the bone-stock Google ROM. It's rooted, but that's it. I've got no special LED or notification settings apps installed. On the stock kernel, there was no charging light. When I installed ElementalX, all of the sudden I had a charging light. I just re-installed the stock kernel, and the charging light went away. :)
[Nexus 5 Original Android Development] danarama:
This is odd.

I ran stock with elex and no charging light. Then I moved to SlimLP which is aosp with elex, and charging light came back. Then slim team added option to turn it off and now its off...

But stock with elex was definitely off.
[Nexus 5 Original Android Development] vickyjusme:
[MENTION=4684315]flar2[/MENTION] you do like HTC made phones . Next phone will be HTC ones if recommended by you

Had a bitter experience with the updates for sensation xe btw
[Nexus 5 Original Android Development] C3C076:
Charging light is a matter of proper battery light support in /system/lib/hw/lights.hammerhead.so library (stock lib doesn't have it). This confirms what [MENTION=2872010]rootSU[/MENTION] wrote (not a kernel matter).
[Nexus 5 Original Android Development] daihard:
I said in my reply to you that the charging LED support was recently added to Cataclysm, and that I never saw the LED come on during charging in versions of Cataclysm without that support, with ElementalX 2.0x installed.

The Cataclysm dev did mention a change in the kernel that had to be made in order to support the charging LED, and he confirmed that the change was in place within the ElementalX kernel. However, that alone wouldn't automatically enable the charging LED.
[Nexus 5 Original Android Development] flar2:
I'm going to put charge led setting in my app, just haven't got around to it yet.
[Nexus 5 Original Android Development] michaelz93:
Hey ppl noob question, What is thermal? It's got 3 options Elemental(performance) cooler, or stock(coolest) what does this and which one to choose? any help please....

I already read the FAQ and didn't find something of this....
[Nexus 5 Original Android Development] danarama:
Thermal throttling.... How hot it gets before it starts to throttle CPU.
[Nexus 5 Original Android Development] michaelz93:
Thanks so the elemental is trottling at higher rates like 70+ grades... and coolest are lower than that I supposed
[Nexus 5 Original Android Development] danarama:
Yes. Though I'm not sure about the temp
[Nexus 5 Original Android Development] till22:
I'd suggest to leave it on elemental and in case you find the cpu going too hot you can always throttle the max temp later on ;)
[Nexus 5 Original Android Development] Tylog:
I wish you [MENTION=4684315]flar2[/MENTION] and all other a happy new year, thanks for the great app and the great kernel and lets start a new and hopefully great year.

Regards
[Nexus 5 Original Android Development] flar2:
Happy New Year!
[Nexus 5 Original Android Development] XTitaniumX:
Happy New Year 2015 to all XDA Members and Devs for the great support and roms u gave us in 2014 and Hope 2015 will be the same.Thanks :)
[Nexus 5 Original Android Development] astral2k5:
Happy New Year!

I have the Nexus 5 for a month. I have stock ROM 4.4.4 with ElementalX kernel 1.13 (default settings + double tap and swipe to sleep)

Yesterday after I've charged it as usually, I got a problem similar with this video:

https://www.youtube.com/watch?v=piNVUibC7ZY

For me the blurred vertical lines are only on the bottom bar zone and are there even on boot or TWRP screen.

After I encountered the problem I've flashed the kernel again with swipe and double tab disabled, the vertical lines were there on boot, but some minutes after boot, the screen was OK again. So I thought it was only a kernel issue and flashed the kernel again with double tap and swipe enabled and now the problem is back again, no matter what I do. Even with stock kernel (i had a twrp backup before flashing elementalX) is still blurred with vertical lines in the home button bar area.

So the question could it be related to the swipe to sleep feature ? can I fix it or is a hardware issue ?

Thanks...
[Nexus 5 Original Android Development] marvi0:
Which app please?
[Nexus 5 Original Android Development] danarama:
The elementalx app...

:/
[Nexus 5 Original Android Development] Tylog:
Yes, ElementalX App :) i love the App, my Number one Tweaking app :)
[Nexus 5 Original Android Development] Jax Teller:
I also love this app.

[MENTION=5047159]Tylog[/MENTION] do you use this app with other kernels as well or just with ElementalX kernel?
[Nexus 5 Original Android Development] Tylog:
I use it with any kernel.
[Nexus 5 Original Android Development] cocchiararo:
[MENTION=4684315]flar2[/MENTION]

Is your kernel incompatible with /system being formated in f2fs?
[Nexus 5 Original Android Development] danarama:
If your existing ramdisk is?
[Nexus 5 Original Android Development] cocchiararo:
i modified my ramdisk for /data and /cache to be in f2fs format, and flashed elementalx after changing those partitions to that FS and it works.

Now i changed the same ramdisk to also have /system in F2FS, and then changed /system, and flashed my kernel again (after restoring my partition data), and it stays at the google´s logo.

I might have botchd the ramdisk modification, but i took instructions from a knowledgeable user from another post, so i think this might not be the issue.

(i had to take a nandroid of /system, rename the files from ext4 to f2fs, format as f2fs, restore backup, flash my ramdisk and then flash elementalX egain, because my rom uses a .dat restore process instead of extracting files for it´s installation)

Edit: just tries RACER kernel and IT works. I guess elemental does not like f2fs-all, or my boot.img is bad?
[Nexus 5 Original Android Development] danarama:
Not really sure about all this .DAT business PR how TWRP handles f2fs. It might be easier finding an aosp ROM to test with that uses the traditional directory structure in the zip.

There isn't a lot of benefit to making /system f2fs. Quicker boot maybe but not much else.
[Nexus 5 Original Android Development] cocchiararo:
As my edit says, racer kernel supports it just fine with my ROM.

As soon as I can restore my phone I will go back to elementalx and /system set to ext4 I guess.

Nexus 5 - Tapatalk
[Nexus 5 Original Android Development] moropazzo96:
About battery? :(
[Nexus 5 Original Android Development] danarama:
Flash elemental x after racer. Elemental x just edits existing ram disk. If elemental works after racer (using racer ram disk), then the issue is your ramdisk. If elemental doesn't work, issue is elementalx..

Yes, nexus 5 has a battery
[Nexus 5 Original Android Development] humzaahmed155:
Flashed elemental x on top of my F2FS ROM, OptiPop. All my partitions are F2FS but after flashing the kernel it seems to convert my /cache partition to ext4, which makes the ROM bootloop. Any ideas?
[Nexus 5 Original Android Development] gverma1:
Am back to 2.04 after a week of 2.05. It appears to me that battery is slightly worse in 2.05, but that could be just me. Will see 2.04 battery performance for a few days for a better comparison.
[Nexus 5 Original Android Development] rfkw:
Anyone tried installing ElementalX after installing Optipop 1-1-2015 version?

I'm getting bootloops with it.

Previously on Optipop 20 December 2014 version, it works ok with ElementalX 2.04
[Nexus 5 Original Android Development] Elluel:
Try flashing the boot.img from factory images then flashing the kernel afterwards
[Nexus 5 Original Android Development] yanleites:
[MENTION=4684315]flar2[/MENTION], do you have a low memory killer in the kernel?
[Nexus 5 Original Android Development] daihard:
I may be ignorant, but should the kernel manage running apps in memory, or should it be the role of the upper OS layer?

Cheers.
[Nexus 5 Original Android Development] yanleites:
I know it's an option in other kernels, and people use this.

That's why I asked...
[Nexus 5 Original Android Development] yanleites:
I use ElementalX app, I didn't see it there.. [MENTION=4684315]flar2[/MENTION], can you add this option to your all please?
[Nexus 5 Original Android Development] danarama:
Its just an android thing. Values can be tweaked no matter what kernel you use including stock. Some tweak apps offer this, as do many simple scripts.
[Nexus 5 Original Android Development] DroidIt!:
If I remember right (excluding the os) the N5 has about 1.7ish GB of usable memory. Apex typically takes up around 140 MB of memory for me, that's the largest memory hog by quite a stretch and that's with it highly customized and locked in memory. Just curious, what do you need a low memory killer for? If you have something taking that much memory and only thing coming to mind is maybe xbmc, maybe you should try to trim down on memory hogs instead. Just a thought :)
[Nexus 5 Original Android Development] danarama:
Low memory killer is built in and used by default. People sometimes feel the need to adjust it so maybe it keeps more in memory. Personally I think default is fine.
[Nexus 5 Original Android Development] till22:
People like to change the defaults. "The defaults are boring and if I change this and that setting my phone will be better!"

What people forget about is that the default settings are usually the settings the dev uses and has been proven best in most circumstances :)
[Nexus 5 Original Android Development] Goku80:
Just wanna say many thanks for the kernel. First time user and normally use to flash Franco or faux kernels but flashing this one after a year in the dark side have to say I am loving this kernel
[Nexus 5 Original Android Development] flar2:
You shouldn't mess with the memory settings.
[Nexus 5 Original Android Development] DroidIt!:
...and that solves that [emoji16]
[Nexus 5 Original Android Development] danarama:
Haha. We knew it anyway ;)
[Nexus 5 Original Android Development] CyberScopes:
I wish i could make everyone shut up like that :D
[Nexus 5 Original Android Development] DroidIt!:
:) An answer is an answer [emoji16]
[Nexus 5 Original Android Development] tenghc:
I wish that the elementalx app have tasker integration so that I can toggle power save or performance mode easily without switching the app first. What do you think? Is it practical?
[Nexus 5 Original Android Development] danarama:
That would be brilliant
[Nexus 5 Original Android Development] wojwem19:
Yea that is actually really good idea. What do you think about it [MENTION=4684315]flar2[/MENTION] ?
[Nexus 5 Original Android Development] flar2:
It should work with tasker. I made the intents public weeks ago. I don't have tasker so this is untested.

flar2.elementalxkernel.powersaver.DISABLE_POWERSAVE

flar2.elementalxkernel.powersaver.ENABLE_POWERSAVE

flar2.elementalxkernel.performance.DISABLE_PERFORMANCE

flar2.elementalxkernel.performance.ENABLE_PERFORMANCE﻿
[Nexus 5 Original Android Development] danarama:
Yes, it works. Thanks for the info.
[Nexus 5 Original Android Development] Mikulec:
I am using Francos app for that. He has Per App Profiles, where u can set max frequencies of CPU and GPU.
[Nexus 5 Original Android Development] flar2:
I don't think per app modes are necessary. ElementalX governor automatically adjusts for most contexts. With my app u can just hit the performance button or widget if you need more, and easily disable it from notification are, button or widget when you're done.
[Nexus 5 Original Android Development] DroidIt!:
I really like you're approach to things: keep it simple, functional and not overly bloated with features that aren't needed. BTW, I've not really seen much bad said about this kernel, I wouldn't worry about that too much personally. I love it and say keep doing what you're doing: ie keep plugging at EleX gov and everything else you had planned. On slim 5.0.2 with your .16 release, my battery is far outlasting what my N5 got even with the bigger, higher res screen and my usage is roughly the same as it was before, with the same carrier and using the phone in the same locations. My opinion :)
[Nexus 5 Original Android Development] SpasilliumNexus:
I for some reason cannot get auto-mounting OTG working with this kernel and FAT32 formatted cards.

I have the commit needed in my ROM to get them to auto-mount, which works, but after I flash this kernel, it stops working.

I attached two screenshots. The first one is with no storage device plugged in, the second is when I have one plugged in.

When plugged in, my phone seems to see it but it will not mount it, even after tapping mount USB storage.

This is my logcat when it tries to mount

E/Vold ( 207): /dev/block/vold/8:1 failed to mount via VFAT (No such file or directory)
E/Vold ( 207): Volume usbdisk found no suitable devices for mounting :(
E/VoldConnector( 809): NDC Command {2 volume mount /storage/usbdisk} took too long (956ms)

E/Vold ( 207): /dev/block/vold/8:1 failed to mount via VFAT (No such file or directory)
E/Vold ( 207): Volume usbdisk found no suitable devices for mounting :(
E/VoldConnector( 809): NDC Command {3 volume mount /storage/usbdisk} took too long (941ms)

E/Vold ( 207): /dev/block/vold/8:1 failed to mount via VFAT (No such file or directory)
E/Vold ( 207): Volume usbdisk found no suitable devices for mounting :(
E/VoldConnector( 809): NDC Command {4 volume mount /storage/usbdisk} took too long (926ms)
[Nexus 5 Original Android Development] jbowwow02:
Hi. I've been afk for a few days, anything new?

Sent from my Nexus 5
[Nexus 5 Original Android Development] ramjet73:
I'm not familiar with your automount commit but I've had problems with StickMount if I don't have SuperSU and the Stericson version of busybox installed. That's probably not related to your problem but I thought I'd mention it for anyone that uses USB OTG with StickMount.

ramjet73
[Nexus 5 Original Android Development] krazeecracker:
Just wanted to ask, as I didn't see anything in the thread. Hammerhead support is not being dropped anytime soon right?
[Nexus 5 Original Android Development] Elluel:
Why would it be?
[Nexus 5 Original Android Development] krazeecracker:
I know a lot of devs are moving to shamu, and were falling behind update wise to kernels.
[Nexus 5 Original Android Development] Mehholoz:
Hi, I'm pretty interested in this Kernel. First of all, I'm sorry if that question has already been answered, I read the latest pages of the topic but obviusly I can't read 'em all. Can anyone tell me how much battery % does tap to wake drain? For now I'm running L with franco Kernel and my battery lasts 3 days, I could live with a 10% less per day. Thank you very much!
[Nexus 5 Original Android Development] danarama:
It depends entirely on your settings. You'll have to test that for yourself.
[Nexus 5 Original Android Development] DroidIt!:
Believe flar said he ran some tests and figured it at about .2% battery an hour, so really negligible, and that's about what I've seen as well :)
[Nexus 5 Original Android Development] Mikulec:
Per App modes has more flexibility. Some apps dont need the full performance of CPU and GPU so I can limit the CPU/GPU frequency for some apps (ebook reader for example), or games that are simple and not very "power hungry".
[Nexus 5 Original Android Development] Mikulec:
Is that a 0,2% or 2%? Cause I think 0,2 is too little, I always thought it sucks battery like vampire sucks blood on Nexus 5.
[Nexus 5 Original Android Development] Mehholoz:
Exactly what I wanted to hear, thanks mate!
[Nexus 5 Original Android Development] magnamentis:
just that it's not true

it's definitely roughly 1.8-2.0% per hour which is by no means neglible because 24h * 2% = 48% per day which is a lot.

but then there are ways to keep it on only for a limited time and switch it of with the power button etc. up to each his gusto,

i have the feature on the OPO and use it, but it gave me too many little inconveniences on this device with my usage.

i think many got it configured to their liking, for me it's easier to use an app like daydream with a shortcut.

so about 2.0% it is, 0.2% is the value of a well configured userspace without tap to wake on.
[Nexus 5 Original Android Development] ramjet73:
I've got DT2W set for a 15 minute timeout and the power button bypass set on and subjectively I can't really tell a difference in battery life with and without it activated.

ramjet73
[Nexus 5 Original Android Development] flar2:
Dt2w/s2w adds about 2% per hour
[Nexus 5 Original Android Development] ramjet73:
Presumably that would be while the phone is sleeping and the feature is active.

My understanding is that it doesn't add anything when the phone is awake and being used nor after the timeout kicks in and the feature is disabled while sleeping.

Is that correct?

ramjet73
[Nexus 5 Original Android Development] flar2:
Yes, exactly
[Nexus 5 Original Android Development] DroidIt!:
Oops, sorry. Thinking of the N6 [emoji56]
[Nexus 5 Original Android Development] jeromechrome1:
Guys I'm running cataclysm Dec 24 ROM with Franco r69 but whenever I flash this I keep getting a bootloop. Yes I reflashed my ROM before I flashed the kernel. I've read and read but haven't found a solution. Please help.
[Nexus 5 Original Android Development] LinearEquation:
Looks like r69 is still a little choppy with reports of random reboots. Cataclysm is closed source but seems to be stable. You should not have to re-flash a ROM before flashing a kernel. I know this kernel is very stable and should not cause any bootloops. Have you tried flashing this kernel over stock AOSP? I'm guessing after custom ROM's get more stable, there will be less issues with custom kernels as a whole.
[Nexus 5 Original Android Development] Roxas_:
Hi guys, noob question here... so forgive me.

Is it possible to just flash over a previous version of the kernel over the current one on my phone?

Say, from 2.04 back to 2.03?

Experiencing some freezing with 2.04, can't tell whether it's the kernel or Lollipop itself. :(

Thanks!!
[Nexus 5 Original Android Development] ramjet73:
You might want to try flashing the stock boot.img file from the 5.01 factory image via fastboot after flashing the Cataclysm ROM and before flashing this kernel. That will reset the ramdisk to the stock defaults and may resolve whatever is causing your conflict. There may also be files installed by the ROM in the system partition to support the Franco kernel but the updater-script for this kernel attempts to delete the ones that might cause conflicts between the two custom kernels.

Unfortunately re-flashing that ROM won't cleanup the ramdisk or the system partition if the custom kernel is integrated with the ROM.

ramjet73
[Nexus 5 Original Android Development] danarama:
Does anyone in this thread compile elementalx from source? I'm familiar with building ROMs but I've never built a kernel on its own before. A couple of questions,

- do I need to sync into a local aosp repo to build?

- using what commands for version 2?

I've got some audio commits I need to test on this kernel that I've been given to (form part of a) fix my microphone issues.

Any advice greatly appreciated
[Nexus 5 Original Android Development] dechronic:
[MENTION=4684315]flar2[/MENTION] You can probably change the FAQ in your OP concerning whether there is an app for your kernel as it still states to use the installer.
[Nexus 5 Original Android Development] Elluel:
I've compiled it.

You can either git clone or use "Download ZIP" on Github on the branch you want and extract the contents to wherever you want your build directory to be, and get a toolchain here and extract it: http://xdaforums.com/showthread.php?t=2098133

Get your required stuff using apt-get, I forgot which ones exactly you need but a Google search will bring them up.

My directory is like this in /home/lethargy/ (I'm booted into Windows right now so viewed in ext2explore lol):

cd ~/Kernel/ElementalX
export ARCH=arm
export CROSS_COMPILE=/home/lethargy/Kernel/Toolchain/arm-cortex_a15-linux-gnueabihf-linaro_4.9.1-2014.04/bin/arm-cortex_a15-linux-gnueabihf-
make elementalx_defconfig
make clean && make mrproper (optional, you will have to make elementalx_defconfig again after cleaning)
make
[Nexus 5 Original Android Development] danarama:
Cool thanks. I'd probably fork it first so I could commit the changes for cherry pick later.
[Nexus 5 Original Android Development] str90:
Upstream

Can you update your kernel if it`s possible to upstream of linux kernel. In caf repository i saw 3.7+ version.
[Nexus 5 Original Android Development] danarama:
To give you what benefit?
[Nexus 5 Original Android Development] theesotericone:
To have the latest and greatest, of course. lol

[MENTION=4684315]flar2[/MENTION] Still rock solid man. It's rad not having to worry about any stability issues. Whatever your doing keep it up.:cool:
[Nexus 5 Original Android Development] Mehholoz:
After the 15 minutes timeout I setted for the tap to wake disable, the screen flashes for a second. Is it a bug?
[Nexus 5 Original Android Development] Elluel:
To have a higher number of course. I mean, the number is what affects the kernel the most, right? :p
[Nexus 5 Original Android Development] rhamej:
No. That is supposed to happen.
[Nexus 5 Original Android Development] NoobieExtraordinare:
Anyone else experiencing abysmal battery life on the N5 with this kernel and lollipop? 5.01. I had great battery life with this kernel and kitkat but can barely break 3.5 hours on screen time. Wtf?