yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] gmi78:
.

no, i flash after full wipe... flash rom...flash su reboot and root work....flash 2.03 and su binaries are missing
[Nexus 5 Original Android Development] flar2:
I am going to lock the thread if there is one more comment about ElementalX breaking root.

It does not break root, end of story.

If you lose root, you have done something wrong.
[Nexus 5 Original Android Development] GCbard:
which rom were you running and which clock speeds and what scores?

---------- Post added at 02:17 AM ---------- Previous post was at 02:14 AM ----------

can one just flash the boot.img from the zip or are all the other files needed to run the kernel?
[Nexus 5 Original Android Development] jlsesler:
I am running cataclysm rom. I am running stock clock speed.

Antutu - 28693

Quadrant - 9518

Other kernels were running about 23k and 7.5k respectively.
[Nexus 5 Original Android Development] GCbard:
Thanks. i have read that some of the scores are low is because of thermal throttling. THe thing is clocked at 2.3gz. It should get higher. I had an HTC one and used elementalx. I scored above 30,000 on antutu several times with it.
[Nexus 5 Original Android Development] Lancez:
not trying to be an a$$, but just tested r9 for 15 min. then i flashed back to 0.2 immediately. 'nuff said :highfive:
[Nexus 5 Original Android Development] FuryriderX:
Bit of an odd issue, tried twice, same effect - I lose root when flashing 0.3 on top of SlimKat - I wonder if it is because Slim uses built in superuser?

Reflashing the rom brings back root access via the built-in superuser, but then flashing 0.3 again breaks it.

Flashing SuperSU 1.65 in recovery brings root back with 0.3 installed.

Using CWM 6.0.4.4, SlimKat alpha 1.1, ElementalX 0.3.
[Nexus 5 Original Android Development] Poser:
Silly question... But are you enabling root in Dev options after installing X? (Assuming it's built like slimbean).

booooom
[Nexus 5 Original Android Development] ballaz:
Glad to see you hear Flar2, best kernel on my HTC One. Quick question, I searched the thread to see if your kernel is compatible with ART. Found no results, so asking the source. I am running stock, rooted, busybox, and your kernel 0.3. If i missed the answer please redirect me to look again.
[Nexus 5 Original Android Development] cherrytontonne:
I flashed the kernel and switched to ART and everything was fine. But a couple important apps don't work with ART yet (like whatsapp for example) so I switched back to Dalvik.
[Nexus 5 Original Android Development] cyburke:
Looking forward to trying this one out!
[Nexus 5 Original Android Development] FuryriderX:
Yes i did check that, The setting still shows enabled for apps and adb. Toggling it on and off doesn't change anything, after X is installed.
[Nexus 5 Original Android Development] Niemer:
Is anyone having problems with exchange email accounts after installing this kernel? I'm no longer getting push notifications and the calendar sync is behaving strange. I have 0.3 installed.
[Nexus 5 Original Android Development] kayone73:
I'm having some fast drainage battery issues on my N5 running Cataclysm rom + faux kernel, thinking about trying this since it has voltage controls. Any recommended undervolt settings that won't hamper performance too much?
[Nexus 5 Original Android Development] ballaz:
Thanks.
[Nexus 5 Original Android Development] akaHardison:
Good kernel.Thanks for your work.And waiting update,want to fix music problem.
[Nexus 5 Original Android Development] Syk69:
Amazing kernel! Working great with no random reboots or freezes or SODs. Battery life has been great as well! Any chance of possibly adding a sound control to raise the speaker gain for notifications? It is so low by default. Thanks a lot! :)
[Nexus 5 Original Android Development] flar2:
Is faux sound working on this device?
[Nexus 5 Original Android Development] flar2:
No, it sets the voltage for the lowest cpu frequency only (ie, the freq where the cpu spends most of it's time)

Undervolting values are specific to your individual phone and require a lot of testing to make sure they're stable. I would just try the presets in the installer. It sets the voltage for the lowest frequency, where the cpu spends most of its time.

That is unrelated to the kernel.
[Nexus 5 Original Android Development] Syk69:
Yes it is.
[Nexus 5 Original Android Development] Manya3084:
I believe the current faux kernel supports it.
[Nexus 5 Original Android Development] flar2:
Ok, I'll add faux's sound patches.

Should have the next release in minutes....
[Nexus 5 Original Android Development] ollidiemaus:
Yeah I think like the same and you had like some sort of Poket Detection that was an awesome feature! :)

Thank you for the nice Kernel

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] FatBoy_Seconds:
Faux kernel app
[Nexus 5 Original Android Development] Vortex1969:
I would rather be able to disable fsync on my own because the I/O drops. I have never had a problem with it and have crashed hard. Just my take. Sorry if you disagree.
[Nexus 5 Original Android Development] ItzMar:
I can't seem to edit the config file using a text editor.

It opens alright but I get an error when trying to save.

Any advise?
[Nexus 5 Original Android Development] absoluterebirth:
would it ever be possible to remove the stock thermal control and use franco's thermal algorithm as well as replacing mpdecision for his custom hotplug driver?
[Nexus 5 Original Android Development] notbrodie:
Sure. Just flash Franco kernel.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Galaxysm:
Can anyone help me with the settings in the aroma installer?

Sent from My Nexus 5 ?.
[Nexus 5 Original Android Development] letmedanz:
Yes! That would be a great improvement for sure

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

If you are unsure of what to choose, just go with the default selects.

Flar has chosen the best options as defaults for those who may not want to experiment
[Nexus 5 Original Android Development] flar2:
In my testing, I found the performance was better with async fsync than with fsync disabled. Are you finding it worse? I'm not opposed to putting the option back in, but I thought it was unnecessary.

I'm not seeing any thermal issues, performance is excellent and there are no reports of instability. No sense in messing

​

it up.

Ask away, your questions will be answered
[Nexus 5 Original Android Development] flar2:
Make sure you have /system mounted as writeable
[Nexus 5 Original Android Development] Syk69:
Why does on touch boost core0 always goes to 300? No matter the current load or what frequency it is on at the time of touch. Core1 does go to the correct 1.2ghz though. I tried setting sync freq to higher value as well but still core0 goes down to 300.

If I switch to ondemand governor it does both cores on touch to 1.2ghz.
[Nexus 5 Original Android Development] flar2:
I might have misunderstood your original post. Core0 is always at 300, it can't be turned off or else the phone would be off.

On mine it behaves properly. On touch, core0 and core1 go to 1267, then a couple seconds later, core1 turns off and core0 returns to 300.
[Nexus 5 Original Android Development] Syk69:
I don't want core0 off just noticing that on touch with elementalx governor core0 goes to 300 core1 1267, but with on demand governor both cores go to 1267 as it should and behaving correctly. So I'm thinking might be a bug with elementalx governor? I mean I did clean install and flashed kernel again but still elementalx governor touch boost core0 goes to 300. Only ondemand governor both cores go to 1267 on touch.
[Nexus 5 Original Android Development] flar2:
That's weird, on mine they both go to 1267 on touch. What rom are you on?
[Nexus 5 Original Android Development] notbrodie:
I'm not seeing that. With elex gov stock settings, core0 and core1 both go to 1267 on touch, then core1 shuts off and core0 goes to 300.

Have you flashed a kernel prior to elex? If so, try flashing stock kernel, letting it boot, then flash elex

Sent from my Nexus 5
[Nexus 5 Original Android Development] Syk69:
Yes very weird because like you said both should go to 1267, if I switch to ondemand governor it behaves correctly. I'm on mahdi ROM right now and chose use current ramdisk or it won't work.

---------- Post added at 09:39 PM ---------- Previous post was at 09:38 PM ----------

OK thanks for trying. I'll try another ROM to see if its the ROM. No I went from stock kernel to elementalx.
[Nexus 5 Original Android Development] wklie:
From what I see in Trickster app, elementalx governor seems normal with Purity ROM.
[Nexus 5 Original Android Development] Syk69:
Ok I found the problem. Its the trickster app, if I turn on frequency Lock then the weird core0 on touch happens, if I turn off frequency lock then correct behavior works of both cores 1267 on touch. The weird part is that even if I turn on frequency lock in trickster, ondemand governor still behaves correctly only elementalx governor breaks.
[Nexus 5 Original Android Development] wklie:
Ideally a screen protector should have a cut out for the proximity sensor as well (on the top right hand corner, i.e. opposite the front camera), but in reality many protectors do not.
[Nexus 5 Original Android Development] flar2:
Yeah, you really have to watch those apps. Make sure they aren't set to apply on boot unless you are sure of everything that it will try to set.
[Nexus 5 Original Android Development] yanleites:
why are you so angry? i've moved from franco kernel to this one, and this is really awesome, just if you can make the dt2w drain less battery it will be great!
[Nexus 5 Original Android Development] theesotericone:
I feel your pain man. Can you make it a repeat offender sort of thing. Because you and I both know some knucklehead is gonna loose root because of lack of research. Then he's not gonna bother searching this thread for answers. Then he's gonna post about it here. Then you'll lock out a bunch of really stoked people who do do their research and don't have any issues. Kind of along the lines of one bad apple spoiling the whole bunch. I've said this before but the reason I don't post here as much as I should is this kernel has always been as solid as they come. Either way do what you need to and you'll always have my and many others support. Just some food for thought.:cool:
[Nexus 5 Original Android Development] willgare:
Slow USB Charging

If anybody has experienced slow USB charging a quick re-flash of the Kernel seems to fix it.

This has happened a few times to me on Elemental X kernels. Not sure why or how it happens, if anybody knows I would be grateful for any explanation.

Today, my phone would not charge past 75% until I re flashed kernel with Aroma installer.

Nexus 5 / Android 5.0 / EX kernel 2.03
[Nexus 5 Original Android Development] sykopompos:
Did you say SuperSU 2.03? Upgrade your SuperSU man, you are 19 releases behind and crying that the version you are using isn't working right when you aren't even using the correct one

Nvm, I saw 2.03 and thought SuperSU not ROM version
[Nexus 5 Original Android Development] Holer Togni:
Where are all these trolls coming from all of a sudden? Everyone who has used EX kernels for more than a few minutes knows they're no hit and miss stuff. Keep up the good work and don't let them annoy you!
[Nexus 5 Original Android Development] dechronic:
Let me put this out there....

Since you are not stating what ROM you are flashing..

Elementalx 2.X is ONLY for AOSP Android 5.0 lollipop at the moment.

Backup your phone entirely and copy the backup to a computer

Format your /system, /cache and /data partitions

Flash via fastboot the Lollipop image for Nexus 5, system.img, radio, cache (do not use the userdata if you have a 32GB Nexus 5)

Do NOT flash a flashable zip of lollipop.

Install ElementalX 2.03

Install SuperSU 2.23 BETA

If you have older apps that require root but they have not upgraded their code to work with the new PIE security features in Lollipop, you need to flash the PIE patch from here:

http://xdaforums.com/showpost.php?p=53741630&postcount=1

If you don't flash that patch older root apps will not work.

For the love of doing things right, do it in the order I just listed

EDIT2: ONLY USE TWRP RECOVERY 2.8.1.0 or higher for any flashing of zips

EDIT: For anyone reading this post... There is a search function in this thread and the entire XDA forums. Do a search for the problem you are having and read at least a page or two before and maybe three or four after the result you found in the search or keep reading past that until you find the resolution to the problem.

It has always worked for me.

Sent from my Nexus 5
[Nexus 5 Original Android Development] yanleites:
Just use wugfresh Nexus tool kit!

1. Flash lollipop

2. root+twrp

3. ElementalX 2.03

Quick and easy!
[Nexus 5 Original Android Development] silberj:
I happen to have root just fine using both of these (sp 2.23 and ex 2.03)
[Nexus 5 Original Android Development] Elpatii:
I test this kernel on my Nexus 5 with stock Lollipop rooted.

I have a poor battery on Lollipop : only with a few applications and without gaming, my battery last 1/2 day...
[Nexus 5 Original Android Development] dechronic:
You could try following the steps I have in my previous post.

I have 76% left with 52 min 50 sec screen time at this moment

Sent from my Nexus 5
[Nexus 5 Original Android Development] jayplusone:
For the love of Google's sweet tooth! Reading comprehension is at an all time low. [MENTION=4684315]flar2[/MENTION] patience my friend, this too shall pass. Keep up the great work.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Elpatii:
Your steps about flash Lollipop, kernel, SuperSU, etc. ?

I've already make that :)
[Nexus 5 Original Android Development] fugn:
Stop blaming the kernel for the rooting issues pls. If you know how to flash then its quite simple to troubleshoot.
[Nexus 5 Original Android Development] sykopompos:
A lot of it has to do with failure to even understand lollipop and the changes plus what has been done for root so instead of a little basic reading to make up for them not researching that things are different so old dirty flashing methods don't work and there is a bit more steps to understand, they rather blame the kernel.

A anykernel kernel can't break root but since selinux does interact with the kernel itself, a kernel can be set permissive in itself and when switching to an enforcing kernel, may cause issues (and vice versa) which may be the cause of what people are experiencing if they are kernel jumping (just a guess at the issues)
[Nexus 5 Original Android Development] Lancez:
Guess what, I think I've figured out why some people having issues with breaking root after flashing EX kernel...

Correct me if i'm wrong, they probably flashed rom zip instead of factory image!

I always flash factory image first when there's new version of android which puts my phone 100% fresh.

For Lollipop, (I use skipsoft tool)

1. flash factory image

2. get CF auto-root from chainfire's site and get rooted

3. then use the same skipspft tool to flash CWM image for N5 (it's old, but works in lollipop)

4. flash EX kernel (make sure you reboot your phone after every single step)

5. done!

If any of you poor guys thinking that the kernel breaks root, please hold your tongue and do what I just said, I can guarantee you that you won't have such problem.

Don't just come in here and blurting about things that you didn't do right in the first place. and please do not compare EX with any other kernels, it is extremely rude and I'm pretty sure it's against XDA rules too. Flar knows much,much,much more than any of you here, so when he said something you better believe it.
[Nexus 5 Original Android Development] jayplusone:
I flashed bigxie's stock lollipop rom zip file, flashed ex, flashed latest SuperSU afterwards. I even dirty flashed it over stock rooted KitKat (a big no no) and it worked without problem. AFAIK some people flash the zips in random order. I flashed CF Auto Root in recovery why no rootz haalps!. This, in the US Army, is called operator error ;)

Sent from my Nexus 5
[Nexus 5 Original Android Development] Cyvasse:
Or, if may I say,

1. flash factory image

2. flash twrp 2.8.1.0

3. flash EX 2.03

4. flash SuperSU 2.19.beta

5. flash PIE patch
[Nexus 5 Original Android Development] danarama:
Am I correct in saying there's no longer any benefit to deleting the powerHAL? And that with mpdecision (on/off) its a choice of hot plugging + touch boost / all cores online n no touch boost? Or in essence, you can't have no touch boost + hot plugging
[Nexus 5 Original Android Development] topgeardave:
From what I've understood you are correct, no touchboost with hotolugging
[Nexus 5 Original Android Development] GragonV:
Thanks much for the instruction

How about a custom rom like this one

https://plus.google.com/u/0/communities/109235522128893190473?cfem=1 (AOSP one)

normal, I will flash the custom rom (zip file), reboot, rooted (if the rom is not already rooted like these new android L roms recently), reboot, flash the EleX kernel and the root is still there

Actually, the process was going fine with AOSP 5.3

but since updating to AOSP 5.4 of this rom, after flash the EleX, the root....uhm...

Not an expert to conclude about the error, just finding a way to get a long with this combo :(

Thanks
[Nexus 5 Original Android Development] jayplusone:
Not sure, I am not expert myself. I stay with what works for me which is stock rooted roms or slightly modified stockish roms. Try flashing EX THEN flash SuperSU latest beta here http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Hope it helps. :fingers-crossed:
[Nexus 5 Original Android Development] coluichepensa:
I have the same problem. I tried all the possible combination but no way.
[Nexus 5 Original Android Development] nadrojcote:
Is anyone else having a really hard time getting this kernel to stick at the max cpu setting you have set? I have tried manually setting my cpu freq to 2.2 and 2.49 in the config file, but the elementalx app will usually show max of 1.5 if I try to set it to 2.2 or 2.49 in the app it will stay at 1.5 and sometimes move to 1.9. I checked with faux123 app and it says its set to 2.49 currently but it doesnt show the cpu jumping to 2.49 like it usually does.
[Nexus 5 Original Android Development] flar2:
1.5 and 1.9 are thermal throttle freqs. What is your CPU temperature?

The freq settings in the conf file only apply during express installation.
[Nexus 5 Original Android Development] scrack26:
Hello, i use this method but skip PIE Patch, root sticks, should i need to flash PIE patch? no errors.
[Nexus 5 Original Android Development] caeter:
The aroma installer starts when you flash the zip und guide you through the insrall process
[Nexus 5 Original Android Development] nadrojcote:
Thanks that makes sense, when I switch from stock thermal throttling to elementalx it jumps up to 2.49
[Nexus 5 Original Android Development] zioxda:
You can skip pie patch, it's only necessary for some apps not upgraded to lollipop yet
[Nexus 5 Original Android Development] dechronic:
PIE patch is/was needed for apps that haven't been updated to support Lollipop yet. It disables the PIE security feature it seems so that it can run the older apps.

So if none of your apps are broken and they are working as they supposed to then there is no need to install the patch.

Sent using:

Android 5.0 Lollipop by Google

+

ElementalX Kernel by flar2

+

TWRP Recovery by TeamWin
[Nexus 5 Original Android Development] DiST_EL:
Hey guys, I have a bug that android os (this is the kernel right?) is draining battery. It secured since I flashed ex, first it looked very promising, the phone showed me 3 days of runtime after the first few percent battery dropped and I was very glad to see it, but then android os got on first place in the battery stats.

I figured out that one cpu core is running all the time at full frequency, even when I am not doing anything. Since hours. Look at the screens. My phone is also warm.

So what can I do and can anyone tell me why I (likely) have this bug? Looks like a kernel problem to me?

Before that I tried stock and Franco kernel, after Franco I dirty flashed the ROM so the installation process is not the problem.

Edit: core 1 is the core running all the time, core 0 drops to 300mhz.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] flar2:
Did you reboot? Wipe caches? Nine times out of ten a reboot fixes it. Usually some service or app is running wild.

The GSAM app sucker tells you nothing. It always lists kernel as the biggest drain. The reason is because some process is asking to stay awake, so the kernel does not sleep. You have to find out which process is keeping the phone awake. I like Better Battery Stats, it shows you the processes causing wakeups.

As long as s2w/dt2w are disabled, you will get the best idle drain possible with this kernel.
[Nexus 5 Original Android Development] GragonV:
Thx, but it's not worked ^^
[Nexus 5 Original Android Development] DiST_EL:
Yes I already restarted, the problem is gone as I thought but still posted it to ask what caused the problem. I think you are right and an app went crazy, have to figure out which. Unfortunately bbs has root issues so I have to flash this patch I guess.

Thx for the quick response.

There is one more thing I wanted to ask: could it be that the lock and unlock sound is louder with this kernel?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] mayurH12:
I did everything u asked but when i reboot it goes back to recovery.
[Nexus 5 Original Android Development] lanjor:
Hi Noob here [emoji16]

I using N5X Rom 5.4 and ElementalX 2.03 + SuperSU beta 2.23.

Maybe this is what happen to people who said they lost root after flashing this kernel.

I too lost root, or maybe lost root for some of the APP like ex. adaway cannot obtain root after i flash ElementalX 2.03. When i click SuperSU app it said "binary is missing etc..." But it didnt happen with N5X Rom 5.3. So i am not saying this kernel break root, but it does happen after i flash ElementalX 2.03. I tried flashing it 2 times (rom + ElementalX kernel) with wipe system and cache.

Then i tried to flash skypompos permissive kernel, and then flashing ElementalX 2.03 after. And everything goes smooth again [emoji16]. All root app working.
[Nexus 5 Original Android Development] Calvin2394:
On stock LRX21O with Franco r68

Can i simply flash 2.03 over it?

Also, has anyone tested this on N5X AOSP 5.4?
[Nexus 5 Original Android Development] jfim88:
No. You need to flash stock before
[Nexus 5 Original Android Development] lanjor:
Read this [emoji16]

http://xdaforums.com/showthread.php?p=49025914
[Nexus 5 Original Android Development] parag60288:
My n5 is showing "Battery usage data isn't available" under battery section in setting after flashing 2.03....

can anybody help...?
[Nexus 5 Original Android Development] Calvin2394:
So all i have to do is flash 2.03 and choose Stock Ramdisk since I'm on LRX21O stock flashed image?

No need of a dirty flash?
[Nexus 5 Original Android Development] Brushstroke:
Was your battery at or near 100% when you saw that message? If so, it's normal and not related to the kernel.
[Nexus 5 Original Android Development] freakness51:
sorry guys, i've read previous posts but didn't find an exhaustive answer...

does elementalx for lollipop support double tap to sleep/swype to wake/etc???

if so, will it be like on kitkat? installing using aroma installer and selecting the option of s2w or so?
[Nexus 5 Original Android Development] rhamej:
Yes and yes.
[Nexus 5 Original Android Development] freakness51:
thanks and thanks! ^_^
[Nexus 5 Original Android Development] flar2:
Flash the stock boot.img, then flash elementalx