yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] suneet mehta:
Did an antutu benchmark and stability test on the 0.17 build. I gotta tell you man the stability is a lot better than the 0.14 build. The benchmark is also great. But i suppose someone had here got a lot better benchmark score. I got 31141 score. Please share the settings or tweaks if you had a better one.

Check out my custom backplates for the spigen ultra hybrid case for the N5 here :- https://mega.co.nz/#F!xd8lGYSS!J9vcXf3IWOqlcng1zE4bpA .

Hit thanks if i helped you.;);)
[Nexus 5 Original Android Development] suneet mehta:
Which app is that?!

Check out my custom backplates for the spigen ultra hybrid case for the N5 here :- https://mega.co.nz/#F!xd8lGYSS!J9vcXf3IWOqlcng1zE4bpA .

Hit thanks if i helped you.;);)
[Nexus 5 Original Android Development] letmedanz:
I understand.

Not a problem, ill live with it :)

Regarding the screen protector, i do have one, but the ear piece, front camera & ear piece have small round pieces cut out.. but that could still be the reason...

Post my last comment regarding battery, i turned wifi off & went to sleep.

I just had 1.5% battery drain per hour!

That's quite great by itself completely discounting the total awesomeness dt2w

:good:
[Nexus 5 Original Android Development] flar2:
Technically it is possible, but I would rather this be picked during driver initialization. You wouldn't see much difference in benchmarks or anything, overclocking this gives only a a tiny edge.

This depends mostly on the governor. Looks like franco is tuning more for performance now.
[Nexus 5 Original Android Development] flar2:
Question for you guys: does this still work with cyanogenmod or are they starting to deviate from pure Nexus again?
[Nexus 5 Original Android Development] dvdivx:
Works on CM based roms I've tried. I don't know how often AOSP updateds their stuff though. At least with CM it's clear what's getting updated.
[Nexus 5 Original Android Development] Syk69:
[MENTION=4684315]flar2[/MENTION], would you consider tweaking elementalx governor CPU boost to be 2 cores? Or is that not tweakable due to mpdecision? Thanks.

Edit: have noticed on touch only 1 core boosts to 1.2 ghz, and the other goes to 300 mhz. I imagine the 300 is due to the input_event_min_freq set as 300? But seems like it always goes to the minimum on input.
[Nexus 5 Original Android Development] ollidiemaus:
I just wanted to report that dt2w is not limited to the button 2,5 cm but the whole screen...

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Grondinm:
is it supposed to be...who says it was?? all implementations i have used work across the whole screen
[Nexus 5 Original Android Development] monkboy24:
Yea it's still working. However its seems to drain battery faster then the stock cm kernel.
[Nexus 5 Original Android Development] stumpy352:
Having no problems at all on cm nightlies here. Awesome battery life too. Less than 1% drain per hour at idle with s2w & dt2w off. Getting about 20hrs battery with about 5hrs SOT. Best kernel all round I think.

sent from beyond the neXus
[Nexus 5 Original Android Development] ollidiemaus:
Trickster Mod says this xD but I'll remember it was like this on the HTC One so Idk

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] highKo:
i'm using your kernel with CM since "the beginning". no issues at all

what rom are you using?
[Nexus 5 Original Android Development] flar2:
Sync freq would control that.

Mpdecision prevents me from changing core online/offline too much, but I've found that generally only two cores come on for most things

When I added dt2w on other phones it was limited to the bottom inch of the screen. I was thinking about doing that here too, since it wakes up pretty easily.
[Nexus 5 Original Android Development] BabboDemonio:
Thanks man it works!
[Nexus 5 Original Android Development] :
Did not happen to me. About 7 hours ago I was on stock 4.4.4 and dirty flashed bigxie's stock 5.0 , new radio, Elemental X kernel and super su and been in recovery a few times (twrp 2.8.1.0) and all has been fine. Had to clear playstore data but all smooth since then.

Kernel running great op. Much tks!!! ;)
[Nexus 5 Original Android Development] flar2:
For everyone asking about root, this is exactly what I did.

The main thing is flash kernel then flash supersu. I have not looked into cfautoroot, because flashing supersu zip is easy and works.
[Nexus 5 Original Android Development] Jax Teller:
For the record, I flashed factory images, then cf-autoroot, then TWRP, then ElementalX kernel and root is still perfect.:D
[Nexus 5 Original Android Development] Lownita:
I used cf autoroot to root. To my understanding this also installs a modified kernel. So my question is, can I flash elementalx after using cf autoroot without problems?
[Nexus 5 Original Android Development] rawdealer:
Yes you can.
[Nexus 5 Original Android Development] Co.Tibi:
I didn't have time to flash eX but I managed to root using cf autoroot. Almost all root apps work except ES file explorer (can't write to system).
[Nexus 5 Original Android Development] ramjet73:
You can "fix" ES File Explorer and some other nonstandard root apps by flashing the PIE patch.

The problem with CF-AutoRoot is that it requires a PC, a USB cable and a phone in the bootloader mode. That procedure loads (without flashing) a custom kernel which works its magic with the scripts and utilities that are included in its ramdisk.

The combination of a permissive kernel and SuperSU can be done in recovery without a PC. If rooting only had to be done once it wouldn't be a big deal but at this point it seems that every new ROM that's flashed requires a re-root.

Hopefully that will change in the future and the ROM developers will figure out how to pre-root their offerings, but in the meantime IMO CF-AutoRoot is a lot more cumbersome than just flashing the kernel and SuperSU in recovery.

ramjet73
[Nexus 5 Original Android Development] AndrasLOHF:
Thanks for this info. I used the toolkit to root this go round. I've never used a toolkit for root before in my years of fiddling and was unsure exactly what it was doing(not smart I know but I trust Chainfire). I was a bit confused on whether the toolkit had actually replaced the stock kernel with a permissive one.

Thanks again.
[Nexus 5 Original Android Development] anshmiester78900:
Can I install this kernel on final lollipop build
[Nexus 5 Original Android Development] flar2:
Just to be clear:

You don't need a permissive kernel for root to work with EX

You don't need to flash a kernel or root before installing EX
[Nexus 5 Original Android Development] MikeLibbey:
Noob question.. how do i flash cf autoroot? I just downloaded the zip to platform-tools. do i unzip it and then simply adb flash the folder?
[Nexus 5 Original Android Development] yanleites:
Why don't you use wugfresh root kit? It does everything quick and great!
[Nexus 5 Original Android Development] and313:
Try to avoid toolkits. Unzip it somewhere then reboot into fastboot. Connect the phone and double click on the bat file in the root of the folder. Make sure you have a working fastboot connection and unlocked bootloader before doing so
[Nexus 5 Original Android Development] gut4:
Is here any way to control wake gestures on android 5.0? While no xposed for 5.
[Nexus 5 Original Android Development] MikeLibbey:
hmmm I just did exactly that and the red android came and did its thing and everything but root checker says its not rooted..
[Nexus 5 Original Android Development] and313:
Is the supersu app installed? And you mind want to continue thid talk over pm since its offtopic

If the app is installed all should be ok
[Nexus 5 Original Android Development] luckana:
What am i supposed to do when i wanna flash EX over another custom kernel ??
[Nexus 5 Original Android Development] jayplusone:
Dirty flash your ROM first. Then flash EX.

Sent from my Nexus 5
[Nexus 5 Original Android Development] ramjet73:
Doesn't that imply that ElementalX itself is using its ramdisk to set SELinux as permissive since AFAIK that's required for SuperSU 2.19 to work without either setting permissive mode another way or using CF-AutoRoot first?

Speaking for myself, I never intended to imply that another kernel needed to be flashed before yours to get root with SuperSU only, but that some kernel in a boot.img that sets permissive mode must be flashed over the stock 5.0 kernel before flashing the SuperSU zip file.

ramjet73
[Nexus 5 Original Android Development] relevant_placeholder:
Did fastboot system but had to use CF. Easy peasy.
[Nexus 5 Original Android Development] yuhenyo:
Hi. Will this work with the recent lollipop factory images for the n5?
[Nexus 5 Original Android Development] sarcoptic:
Yep...install elementalx then immediately install supersu 2.19 beta and reboot. You will have the new kernel and root ability. If you want apps like ES File Explorer you need to follow up the supersu 2.19 beta with the pie patch. So my setup was

Flash Factory image with flash-all (this will start your phone over from day one including wipe storage)

Flash TWRP 2.8.1.0 back on

Boot to TWRP

Flash ElementalX 2.03

Immediately flashed SuperSU 2.19 Beta

Immediately flashed PIE patch

All apps worked like AdAway, ES File Explorer, Busy Box, ElementalX Config App
[Nexus 5 Original Android Development] ramjet73:
You're welcome.

[MENTION=631273]Chainfire[/MENTION] doesn't publicize his rooting methods, but I'm pretty sure the boot.img that is the main component of his CF-AutoRoot process contains what is known as an insecure kernel, which the WugFresh Nexus Root Toolkit downloads automatically for you. An insecure kernel is able to setup the files in the system partition required for root.

ramjet73
[Nexus 5 Original Android Development] flar2:
ElementalX modifies the existing boot.img during installation to work with root. I use Chainfire's method. If people with to set selinux to permissive, they could flash a permissive kernel before installing EX or turn off setenforce manually.

I haven't looked at Chainfire's autoroot, but I suspect it fastboot boots a special boot.img that modifies /system for root and then returns to bootloader to fastboot flash a boot.img with the ramdisk modification necessary for root. It can all be done with a script.
[Nexus 5 Original Android Development] jtwlbz:
did you update the bootlader as well? or staying with KK one?
[Nexus 5 Original Android Development] BreckZeBoulay:
and for who wants to install LRX21O in secondary rom with MultiRom, this method of root works also perfectly !
[Nexus 5 Original Android Development] flar2:
I did the complete factory update. Thought it was about time to start over.

However, I forgot to copy my photos before I did it...whoops, all gone. I can't remember if I had any that I wanted to keep on there, probably a few.
[Nexus 5 Original Android Development] jtwlbz:
Do you know if I flash bootloader only in fastboot if it deletes anything?
[Nexus 5 Original Android Development] ramjet73:
Thanks for the explanation.

So technically, using the previous [MENTION=631273]Chainfire[/MENTION] method results in a "relaxed" rather than permissive SELinux environment, but still allows a flashed SuperSU to work properly.

The only reason I can think for changing from that method is not wanting to touch the boot.img at all especially for the stock kernel. I haven't looked at what gets modified in the system partition with his new CF-AutoRoot but maybe he's figured out a way to accomplish that.

As long as root is dependent on ramdisk processing that is going to create problems for the developers who don't use the anykernel installation method and think they own the ramdisk as part of their kernels. :rolleyes:

ramjet73
[Nexus 5 Original Android Development] dechronic:
I personally flashed everything except the recovery, the via the custom recovery, I installed ElementalX 2.0.3 and then SuperSU 2.16 initially and later upgraded to 2.19. The Nexus cwm bootunlocker still works with the new boot loader.

NOTE/WARNING: Flashing the userdata.img will erase all of your data. Back up all data to a PC first. I use the adb pull /data/media/0 method after doing a Titanium Backup backup.
[Nexus 5 Original Android Development] sn0warmy:
Just wanted to chime in and say that after flashing the stock 5.0 image and rooting, I flashed this kernel and have been extremely happy with it, thus far.

I know a few pages back someone asked about running the ondemand governor to help improve gaming. I can say that with the elemental governor I was getting some pretty steady lagging with a relatively simple game (Ski Safari) that I wasn't getting on the stock kernel/governor. After switching to the ondemand governor the lag is completely gone.

Thanks for your hard work flar2! :highfive:
[Nexus 5 Original Android Development] anshmiester78900:
Anyone mind replying ?
[Nexus 5 Original Android Development] danarama:
Yes you can. Reading the thread helps answering your own questions.
[Nexus 5 Original Android Development] anshmiester78900:
Thanks
[Nexus 5 Original Android Development] jtwlbz:
What i am wondering is that let's say you flashed flashable 5.0 and working fine. And later on what if you flash bootloader in fastboot itself? Does it erase anything?
[Nexus 5 Original Android Development] dechronic:
Flashing the bootloader doesn't affect the system or userdata partitions.

Correct me if I am wrong
[Nexus 5 Original Android Development] flar2:
All that Chainfire does to the boot.img is comment out a single line so that the su daemon can run in a system wide context when started from install-recovery.sh. It does not change selinux, it's just a way to start the su daemon at boot. This is a simple modifcation to the ramdisk, does not affect the actual kernel at all, and devs can easily incorporate it into ROMs or kernels. The anykernel method is not necessary and it shouldn't cause any problems for devs.
[Nexus 5 Original Android Development] danarama:
Just had that maximum 1958MHz issue. Only using elx app. 2265 is in the list but pressing it did nothing as if it was already selected. Had to select below 1958 then it let me select it and now all good.
[Nexus 5 Original Android Development] ramjet73:
That certainly clarifies the method used by [MENTION=631273]Chainfire[/MENTION] for gaining root in the previews but I think he said on one of his G+ pages that he wasn't satisfied with that as a permanent solution and would be looking for alternatives.

I just posted in his SuperSU thread asking him to explain if/how the rooting method in his new CF-AutoRoot differs from his previous method that you are using for the ElementalX kernel and I will be very interested in his answer. Perhaps it is just combining the ramdisk mod with the installation of SuperSU, as you suggested earlier, but it's always good to hear it "from the horse's mouth". ;)

Thanks again for your explanations. :good:

ramjet73
[Nexus 5 Original Android Development] swat4samp:
After flashing cf auto root, simply installing supersu from playstore is enough?
[Nexus 5 Original Android Development] v3rk:
Using cf auto root will install SuperSU for you
[Nexus 5 Original Android Development] swat4samp:
Thanks, if I want to flash this kernel, then no need to flash cf auto root right?
[Nexus 5 Original Android Development] vin4yak:
Nope..

Flash images

Flash twrp

Flash ElementalX

Flash supersu

-Sent from a Lollipop'd Hammerhead!
[Nexus 5 Original Android Development] ramjet73:
New CF-AutoRoot

I found this post on [MENTION=631273]Chainfire[/MENTION]'s G+ page which answers my questions about his new CF-AutoRoot versions for Lollipop and confirms that he is still modifying the ramdisk in addition to installing the SuperSU files in the system partition.

ramjet73
[Nexus 5 Original Android Development] danarama:
Yep, which is exactly what [MENTION=4684315]flar2[/MENTION] said.
[Nexus 5 Original Android Development] ramjet73:
Yes, and now it's confirmed by [MENTION=631273]Chainfire[/MENTION]. :)

ramjet73
[Nexus 5 Original Android Development] danarama:
Super. I also confirm it.. Thats three.
[Nexus 5 Original Android Development] anshmiester78900:
After installing this kernel my phone went into boot loop . using latest lollipop build .

Edit : After clearing the cache and dalvic cache in TWRP the phone booted but the battery drain is high as in kernel tweaker app i can see that the phone was at 2.3ghz for about 3 minutes and the back of phone became hot as hell
[Nexus 5 Original Android Development] JoshDB:
I, too, am getting insane battery drain and CPU heat. Going to go back to stock for now
[Nexus 5 Original Android Development] doomed151:
Dirty flash the ROM beforehand if coming from another custom kernel.
[Nexus 5 Original Android Development] flar2:
These problems are with your setup, the kernel does not cause drain.
[Nexus 5 Original Android Development] JoshDB:
I just flashed this over stock lollipop, with stock clock settings and such, so I don't know what could be wrong. Guess I'll wipe and reflash everything and see if it changes.
[Nexus 5 Original Android Development] Lancez:
2.0.3 is awesome, no problems whatsoever, battery life is as good as latest KitKat kernel.
[Nexus 5 Original Android Development] :
I agree! Been great the last 24 hours or so for me on stock 5.0 rom. :)
[Nexus 5 Original Android Development] Jax Teller:
I have a question which is not kernel related but since we all here have the same setup (LRX21O + ElementalX + TWRP), I thought it's good to ask here.:)

Can you guys see the TWRP folder with the backup in /storage/emulated/0?

I can only see it in the /data/media/0.

From what I understand if anything goes to /data/media/0 while we are in TWRP doesn't show later in /storage/emulated/0.

Is that a TWRP fault or is it the way Android works now?:confused:
[Nexus 5 Original Android Development] csolanol:
+1 Same behavior here.
[Nexus 5 Original Android Development] ramjet73:
This may help.

ramjet73
[Nexus 5 Original Android Development] Lownita:
Link doesn't work [emoji20]
[Nexus 5 Original Android Development] Tylog:
Link is fine http://teamw.in/DataMedia
[Nexus 5 Original Android Development] :
Actually Tapatalk sucks
[Nexus 5 Original Android Development] Tylog:
True story :)
[Nexus 5 Original Android Development] memogoren:
Um, can we use kernel in LRX21O?
[Nexus 5 Original Android Development] Lownita:
Right, it's redirection was the problem...
[Nexus 5 Original Android Development] jfim88:
So CF Auto Root is the correct method to root stock, but if i want a custom kernel, isn't needed? Only flash SuperSU after kernel?
[Nexus 5 Original Android Development] zioxda:
Correct
[Nexus 5 Original Android Development] flar2:
On stock or not, you just have to install ex and then supersu
[Nexus 5 Original Android Development] jfim88:
But if i install Ex i dont need to install CF Auto Root, only to flash SuperSU. Is correct?
[Nexus 5 Original Android Development] gpvecchi:
Is there still the need of flashing permissive kernel before EX? Thanks!
[Nexus 5 Original Android Development] :
No for GOD's sake no!
[Nexus 5 Original Android Development] danarama:
It depends what you want. You can have root with just elementalx, but you wont be permissive so it depends if you need that particularly.

I personally prefer to be permissive so I do flash that boot.img first.

I believe though, that the "pie patch" achieves similar?

---------- Post added at 01:17 PM ---------- Previous post was at 01:16 PM ----------

Yes, you were just told that
[Nexus 5 Original Android Development] relevant_placeholder:
Your preaching is in vain, I'm afraid.

This and PIE patch are the this years 'disable UAC' and 'run as Admin'
[Nexus 5 Original Android Development] danarama:
UAC is the first first thing to go for me :)
[Nexus 5 Original Android Development] ssauger:
Stock Kernel

I am on Stock 5.0 atm and like to try ElementalX. Is there a flashable Stock kernel in case i will go back without flashing the hole image again?

Thanks in advance
[Nexus 5 Original Android Development] chubby65:
I wish people would learn to read and save the rest of us from sifting thru page after page of the same ****
[Nexus 5 Original Android Development] flar2:
Backup system and boot in recovery so you can go back if you need to.
[Nexus 5 Original Android Development] danarama:
There is. You can extract the boot.img from the factory image and flash it with fastboot or flashify. That said, sometimes it may just be cleaner to flash a stock ROM.zip
[Nexus 5 Original Android Development] AndrasLOHF:
Definitely better to flash a full zip or to also fastboot flash the boot and system image. There is a config file or two that will get left over in the system. I had noticed it when going from Elemental to Hellscore when running Sykopompos n6 ports and a setting or two was reverting to Elemental.
[Nexus 5 Original Android Development] relevant_placeholder:
I think we're not on the same page.
[Nexus 5 Original Android Development] fkloznica:
Where can i find that PIE patch ? Thanks
[Nexus 5 Original Android Development] SuperSalvo:
WOW!!!

I'm here only to report my expirence with this kernel. It was the best kernel with kitkat and it is even better now with Lollipop!

I'm on stock Lollipop final build from bigxie + ElementalX 2.03.

My phone is flying. I have set my Freq at 2,49 Ghz + row + 256 + 750 uv. With this setting i have an antutu scor of over 42000 (!) points. Holy **** i love this kernel even more now! thx flar! :highfive:
[Nexus 5 Original Android Development] chubby65:
Have you tried the search function yet?

HIGHLY RECOMMENDED :D
[Nexus 5 Original Android Development] ssauger:
Is USB fast charge working on the lollipop kernel? I ask cause its charging slower than on kitkat. Also current widget reports around 200mah, on kitcat it was around 500mah on the same USB port.

Edit: after replug usb it indicates faster charge now.
[Nexus 5 Original Android Development] dakore:
8 seconds... You could be even faster because I was eating popcorn with my dominant hand.

http://lmgtfy.com/?q=pie+patch+android
[Nexus 5 Original Android Development] navahoo:
Guys, I´ve tried to install the captured OTA on my N5 and reverted to stock kernel before. Now I´m receiving a error message in TWRP that my device is using test-keys instead of neccessary release keys. Is there a way to change the keys? Thanks!!
[Nexus 5 Original Android Development] wund3rground:
Is anyone running stock rooted 5.0 with 2.03 and having issues with embedded video playing. Not working for me at all.

---------- Post added at 08:49 AM ---------- Previous post was at 08:43 AM ----------

Hmm. Never mind, seems to be the latest update to Chrome that's breaking it for me.
[Nexus 5 Original Android Development] bionemesis:
Need a bit of advice on this one. I installed the pie patch on my already setup 5.0 final in order to enable permissive mode for an app I need (CallRecorder). Unfortunately, it didn't result in CallRecorder working and it also caused some issues with WhatsApp and a general performance hit (ex: after a second boot, it took 2-3 minutes for WiFi to come up and a further few minutes for it to connect to my carrier). Long story short, I'm going to reflash fresh/clean and basically want permissive mode, Elemental-X, and running nearly stock release from bigxie. What's the best way to do this, preferably via TWRP?
[Nexus 5 Original Android Development] Tylog:
Haha ? The faster you must be young Padawan student
[Nexus 5 Original Android Development] gpvecchi:
I try to make the point on permissive kernels (if I understrood...): EX and Chainfire's ones are partly permissive, so no need to flash Chainfire's before EX.

Now, to be fully permissive, you have now to flash the PIE patch, or flash Sykopompo's full permissive kernel before EX, right?
[Nexus 5 Original Android Development] flar2:
For permissive, you need sykopompo kernel. PIE patch is for the linker. Two different things.
[Nexus 5 Original Android Development] wund3rground:
Okay, my Android nerdery only goes so far. All this PIE talk has me confused. I Googled it and read up but it's above my pay grade. I'm running stock rooted 5.0 with Ex 2.03. Do I need to worry about this PIE patch?