yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] pb1379:
In one go, I flash kernel first, then SuperSu. I did flash 3.0 and SuperSu 2.50 first, though, because the former weren't available yet ? but I don't think that changes anything. With 3.0 and SuperSu 2.50 I did get root but didn't get writeable system (no warning, though, either).
[Nexus 6  Original Android Development] DeathGrind:
A bit off kernel topic, but do you still need the modified boot.img to root if using SuperSU 2.51?
[Nexus 6  Original Android Development] pb1379:
Nope.
[Nexus 6  Original Android Development] Joe92T:
could just be losing my mind, but i swear the half screen tearing thing is happening way more now then it ever did on stock kernal (never).

YouTube on full screen is a killer
[Nexus 6  Original Android Development] oak:
Yes, ex kernel manager is slick. Of all such managers, ex has the best interface. Very cool.
[Nexus 6  Original Android Development] bogus83:
I do have the paid version. Sorry for the blurry picture, but you can see the charging notification configured to be red, and the green light lit up. It continues to light up green whiled charging even if I completely remove the "battery charging" notification from light flow.
[Nexus 6  Original Android Development] chubby65:
Only thing I can suggest is to play about with your settings
[Nexus 6  Original Android Development] bogus83:
I just re-installed the kernel, this time leaving the "enable charge LED" option unchecked. Now I don't get ANY light when the phone is charging, but all other notification lights work. Light Flow also doesn't seem to see that the phone is charging, because there's nothing in "Active Notifications" while the phone is plugged in. I'm going to leave it alone since I was trying to disable that anyway, but it does seem to indicate that Light Flow isn't able to detect or handle charging notifications with this kernel, or that the settings are being overridden somewhere.
[Nexus 6  Original Android Development] chubby65:
It works well with this kernel mate

In led control have you checked this box
[Nexus 6  Original Android Development] bogus83:
Yes, I have that checked.

I just completely wiped my phone and installed this kernel fresh, with the "enable charging LED" option unchecked, and installed Light Flow again. I can go into the notification settings section and test the battery charging notification, which causes the LED to light up green (despite being configured for red), but otherwise Light Flow is unable to detect when the phone is being charged.

How does the kernel "enable" the charging LED? I still think that setting is conflicting with everything else.
[Nexus 6  Original Android Development] Lesser Version:
other than a nandroid backup, when flashing this kernel, does anything need to be wiped?? I am on an unencrypted stock kernel now. Thanks
[Nexus 6  Original Android Development] chubby65:
No mate
[Nexus 6  Original Android Development] drawde40599:
Nope .Nothing needs to be wiped when installing a kernel on a Nexus . only time you should wipe caches is when installing a ROM .
[Nexus 6  Original Android Development] adio201:
Question I just pick up my nexus 6 I'm coming from a nexus 5 running elementalx love the rom. My question is elementalx n6 is this kernel encrypted?
[Nexus 6  Original Android Development] BRKotucs:
You love the ROM or the kernel? ???

As for your question: No!!
[Nexus 6  Original Android Development] adio201:
Love the kernel
[Nexus 6  Original Android Development] resynx:
Kernel is running smooth with bfq, thanks flar :D
[Nexus 6  Original Android Development] adio201:
What setting you guy using
[Nexus 6  Original Android Development] celyko:
Kernel is awesome, thank you for your work. Whenever I'm in the dark on the phone, the power button won't work to turn on the phone. Works fine if its on speaker or if there is light for the proximity sensor. Any one else have this problem? Solutions?

Sent from my Nexus 6
[Nexus 6  Original Android Development] Krunk83:
When I change the CPU governor in the ElementalX app from interactive to power save the max CPU frequency stays at 1958MHz. Shouldn't that go lower or is powersave changing something differrnt?

nexus 6
[Nexus 6  Original Android Development] flar2:
That's strange, I will check mine later.

I've never used that governor before, I have no idea. I would stick with interactive for now. I'm hoping to get a release out this weekend with the elementalx governor.
[Nexus 6  Original Android Development] Krunk83:
Ah yes, I keep forgetting this app is a beta. Doh!

nexus 6
[Nexus 6  Original Android Development] flar2:
There's nothing wrong with the app, that governor could be borked though, it just comes along with Linux and I would never recommend using it. I'm not sure what the normal behavior is for it.
[Nexus 6  Original Android Development] celyko:
The only time I ever tried over clocking was with the original Motorola droid. Had no idea what I was doing, so of course I ruined my phone. I'm just trying to give my n6 that little edge. Can someone recommend the frequency and other settings that are fairly safe? I went 2880 frequency and stock on everything during install except dbl tap and charging led.

Sent from my Nexus 6
[Nexus 6  Original Android Development] drawde40599:
Just go up one or two steps from stock , no need for anything more.
[Nexus 6  Original Android Development] magnamentis:
yeah bad luck for some unfortunately, i'm on EX from day one and never ever have seen these glitches, just lucky as it seems. interestingly there is a similar problem with the nexus 5 which i also never encountered but flar2 himself does, albeit on stock kernel as well. over all from reading through dozens of threads for a long time now i must say that there are not that many with the problem. try performance governor in GPU settings. on the only device i ever had with display issues that solved it, not saying it does the job here as well. ahh... yes and raise the minimum frequency o of the GPU by on notch as well.
[Nexus 6  Original Android Development] garyHal:
My original N6 experienced tearing often with EX.

I had it replaced due to bad camera. What I have now is stock and does not experience any tearing from normal usage. I would only see tearing if I exit a game that was running full screen.
[Nexus 6  Original Android Development] NLBeev:
I was using double tap and had the same. Had to double double tap. But ... I think it has to do with the display. It works capacitively and dirt or the moisture in fingers causes you have to swipe/tap again.
[Nexus 6  Original Android Development] DarkSorcerer:
It worked perfectly. Thanks!

Now, just a little thing: adblock plus can't get its magic to work (not enough space?) and EX app says it needs BusyBox, I I try to install it and it says to try to install it in another location. Anyone?
[Nexus 6  Original Android Development] drawde40599:
Your system space may be to low to install busybox try to Delete some system apps . Apps like foreign languages you don't use , FI app...

---------- Post added at 04:02 AM ---------- Previous post was at 03:58 AM ----------

Yes, You still need a custom Kernel like this one or one of the stock modified kernels available.
[Nexus 6  Original Android Development] Joe92T:
If I want to go back to stock rooted M kernal, I can't just flash the boot and call it a day right?

I need to wipe system, restore my system nandroid that I took 5 seconds before flashing element, then flash stock kernal?

Shouldn't need to touch user data right? Just system
[Nexus 6  Original Android Development] flar2:
You can just flash Chainfire's boot.img
[Nexus 6  Original Android Development] reaper000:
Chainfire now recommends anyone who uses M to use SuperSU 2.52 for root. Here's the download link:

http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
[Nexus 6  Original Android Development] stinger4321:
That's a hardware issue.. My first N6 did that and i exchanged it through moto repair. This current one doesn't and I'm and running this kernel with powersave options on.. I did notice on my original N6 it would happen more. Often with underclocked kernels. If you google n6 screen split there's a couple of threads about it. I would definitely return.
[Nexus 6  Original Android Development] Joe92T:
My question is, if I return via moto repair direct do I get a refurb or a new device back? I don't want someone else's problem
[Nexus 6  Original Android Development] garyHal:
My exchanged one looks new, don't know about its internals though. Motorola will never say its new or refurbished. It's just in an opened box without all is accessories.
[Nexus 6  Original Android Development] stinger4321:
Mine also looked new.. Build date was 12/14 though... But all plastics and screen are mint. Either way it was worth it.. I have a working phone that i don't need to constantly turn the display off to fix the split screen issue
[Nexus 6  Original Android Development] ChelseaFan257:
Hallo all,

I've recently run into a weird problem with my N6 on Marshmallow. For some reason, since earlier today, my phone refuses to load up my EXKM color profile on boot. I did use recently "wm size" to override my screen resolution to 1080p, with a reduced DPI value (through build.prop) to match; could this be the culprit, I wonder?

It's not a huge problem, just a minor inconvenience. Everything else I've set to apply on boot - the CPU throttle temperature, max. screen-off CPU frequency, microphone volume gain, I/O readahead value, and TCP algorithm - is working just fine.

On a side note, I have found - as others have - that Solid Explorer doesn't seem to be able to edit build.prop and other /system files, but can copy and move files without issue. FX Explorer, on the other hand, is working flawlessly. Someone on Reddit mentioned to me that Hells Core kernel, meanwhile, is working just fine with Solid Explorer. Just curious as to what the difference is between the kernel-file manager combos that root functionality is affected so.

Danke very much.
[Nexus 6  Original Android Development] shwise:
[MENTION=4684315]flar2[/MENTION] Would you consider tweaking your current tap2wake implementation to provide tap 2unlock (http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344)?
[Nexus 6  Original Android Development] DeathGrind:
I have the 3.01 kernel installed but ex manager says there is a update. Is it OK to update?
[Nexus 6  Original Android Development] ohad129:
If you update you degradate its 3.0
[Nexus 6  Original Android Development] DeathGrind:
Kinda what I figured. Thanks for the clarification :)
[Nexus 6  Original Android Development] flar2:
Do you have the apply on boot switch turned on?

For root apps, some need to be updated to work with root and selinux enforcing. EX 3.00 is permissive EX 3.01 is enforcing.
[Nexus 6  Original Android Development] Krunk83:
I'm experiencing random reboots on 3.01 with JDX 4.0. Anyone else experiencing this? I've noticed that the phone randomly freezes when I using it, then reboots. This happens about two times a day. I'm running it with stock kernel settings.

Nexus 6 M
[Nexus 6  Original Android Development] flar2:
No problems here, mine is running better than it ever has on 3.01 and marshmallow
[Nexus 6  Original Android Development] Joe92T:
Yeah it's just a PITA cause I have a screenshield on it already and a Dbrand skin which would require removal and the screenshield is one time use so then I need that too...

I've gone back to stock rooted kernal and knock on wood so far have had zero issues and no screen tears. It only started after installing EX. So if it's a matter of just using a different kernal, and I can keep my same device, then I'm all for it
[Nexus 6  Original Android Development] flar2:
Just use interactive or increase the sampling down factor.
[Nexus 6  Original Android Development] Joe92T:
I was using interactive on the CPU governor the entire time. For GPU governor I tried a few different ones including performance and had no luck.

Unsure how to modify sampling factor? But I'm open to suggestions...

Also noticed in kernal auditor that the GPUs lowest clock speed would be 24mhz? But on stock rooted kernal lowest is 300?
[Nexus 6  Original Android Development] ChelseaFan257:
I do indeed, but it refuses to stick. As I said, my other on-boot settings are working just fine, so the fact that my only Graphics settings change is the one refusing to work leads me to think it is indeed somehow related to my resolution tweak.

Ah, I see. So Hells Core probably sets SELinux to permissive, I suppose?
[Nexus 6  Original Android Development] macboy3000:
Has anyone made a purchase in Android pay with this kernel?
[Nexus 6  Original Android Development] michigan66:
I have the same issue as above with the color settings sticking. Set on boot is enabled. Sometimes it will reset randomly after 15 minutes or so to a different color profile. I believe stock setting.
[Nexus 6  Original Android Development] magnamentis:
yes and it's by no means kernel related whatever the reason for your question is while it would have been nice if you gave more input as to the reason so that others could check as well and perhaps learn something.
[Nexus 6  Original Android Development] jk8260:
Same here
[Nexus 6  Original Android Development] agentfazexx:
Flashing Chroma now. Does this kernel support the vibration intensity changes and other changes provided by Kernel Auditor?
[Nexus 6  Original Android Development] macboy3000:
Sorry about that...it's because I'm on stock 6.0 with this kernel and it's not working for me. I was able to add my card by disabling root, but I get this when trying to pay at a store: http://i61.tinypic.com/2urwbox.jpg. So far I've tried these combinations: 1. disable root 2. set selinux to enforcing 3. do both 1 and 3. All three tries failed. These are the mods I have made: change maximum headphone volume, install busybox, and install the permissive zip linked in OP.
[Nexus 6  Original Android Development] flar2:
The correct question is, does Kernel Adiutor support it?

The answer is that kernel Adiutor supports some, but not all assertions on this kernel. The preferred app is EX Kernel Manager.
[Nexus 6  Original Android Development] flar2:
No idea why the color profiles arent being set.

I use one myself and it applies on boot.

Edit: there is something going on
[Nexus 6  Original Android Development] flar2:
Update

This should fix the color control problem.

Download:

ElementalX-N6-3.02

Changes:

-update kcal color control
[Nexus 6  Original Android Development] garyHal:
I haven't used your kernel in a long time, will your google store app update to 3.02?
[Nexus 6  Original Android Development] flar2:
Yes, I have pushed this version to the app.
[Nexus 6  Original Android Development] appro77:
Where can I source SU 2.5? The Play Store app doesn't check that SU 2.5 is present before installing 3.02.
[Nexus 6  Original Android Development] flar2:
It's up to version 2.52 now:

http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
[Nexus 6  Original Android Development] appro77:
Thanks. I was using 2.49. Would that have caused the bootloop I got? Restored from a backup that I'd done first.
[Nexus 6  Original Android Development] flar2:
Yes, that's why I've been afraid to push it to the app.
[Nexus 6  Original Android Development] appro77:
Thanks again. Have installed 2.52. Will flash kernel again now.
[Nexus 6  Original Android Development] appro77:
Is there any way to flash this over Hells Core kernel without ending up in a bootloop?

I'm guessing I need to flash the stock kernel first but I'm having trouble getting my hands on that.
[Nexus 6  Original Android Development] LGtMgG2t:
Ice looked around on here and Google. Is there no way to run the CPU minimum below 300MHz? I found the 4 cores in the /sys directory and changed the minimum freq there to 98Mhz but seems to have no effect.
[Nexus 6  Original Android Development] magnamentis:
use cooler colors, it's not only best but sticks all the time for 2 years now
[Nexus 6  Original Android Development] tealio:
If you've got a windows computer try WugFresh Nexus Root Toolkit. It's simple.
[Nexus 6  Original Android Development] jk8260:
You can always find the flashable stock parts here...

http://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
[Nexus 6  Original Android Development] flar2:
Lower than 300 is not available
[Nexus 6  Original Android Development] Krunk83:
What's the best way to grab a log the next time it happens?

Nexus 6 M
[Nexus 6  Original Android Development] Herk718:
When I run latest ElementalX with Pure Nexus 6.0, USB Storage(MTP) does NOT work at all. Even if I manually switch it in USB Configuration from "Charge Only" to "USB Storage(MTP)".
[Nexus 6  Original Android Development] LGtMgG2t:
Same problem here and I hadn't noticed till you mentioned it. I tried switching to different modes in the developer options and it doesnt seem to affect anything. In fact, my phone doesnt even show the icon in the status bar as though it is connected to USB.
[Nexus 6  Original Android Development] mgostom:
Currently I'm on EX Kernel 3.0 and SU 2.52. I tried to upgrade to 3.02 but it gets stuck at boot animation. I tried a couple of ways to upgrade, using the EX Manager app and flashing manually, both without success. It gets to the boot animation and sits there. I reverted back to 3.0 without any issue. Also, by doing it manually, I did reflash a rom before flashing the kernel. Anyone else experiencing the problem? Is there anything different I should be doing? Thank you.
[Nexus 6  Original Android Development] Herk718:
I find it kind of weird though, because I was running 3.01 perfect without this issue...Hope [MENTION=4684315]flar2[/MENTION] looks into soon, because I've deleted 3.01 and can't find it nowhere so I'm stuck with 3.02.
[Nexus 6  Original Android Development] Vinsanity232:
I had a problem going from 3.01 and supersu 2.52 to 3.02 as well. It would get stuck on the boot animation or bootloop. I ended up reflashing stock everything without wiping, and then reflashing TWRP. Then I flashed 3.02 and supersu 2.52 again. Everything is peachy keen now. Seems that is the only way I can do it without a bootloop.
[Nexus 6  Original Android Development] LGtMgG2t:
I've only tried 3.02. Did you try the 3.0 build? It's odd the debug notify doesnt show in the status bar here.
[Nexus 6  Original Android Development] Herk718:
Does your computer recognize your phone?
[Nexus 6  Original Android Development] Vinsanity232:
Yes
[Nexus 6  Original Android Development] Doughnut643:
Go to windows device manager, uninstall and delete driver software unplug nexus and reboot computer = profit. That's how I fixed it
[Nexus 6  Original Android Development] Herk718:
Found v3.01 just incase anybody is having issues with v3.02 like me and would like to revert back...

https://www.androidfilehost.com/?fid=24052804347832277

---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------

My device doesn't even show up in "Device Manager" :confused:
[Nexus 6  Original Android Development] Alxoom33:
I found the problem to be rom dependent. I could not flash SU 2.51 and EX 3.01 on Xtrasmooth rom but had no problems with doing so on JDX 4.0. I like to go back and forth between the two as each upgrades. Have not tried the latest, 12/10 Xtrasmooth rom version which comes with EX 3.0 and SU 2.49 baked in.
[Nexus 6  Original Android Development] mgostom:
I see. I'm using xtrasmooth, the initial version. I thought it could have been an issue. I was going to try a different one, but I wanted to ask if someone came across it. Thank you!
[Nexus 6  Original Android Development] Herk718:
[MENTION=4684315]flar2[/MENTION] After doing a little troubleshooting, I think I've found the culprit, windows doesn't recognize my device when "USB Debugging mode" is ON. Once I turn it off & set "USB CONFIGURATION" to "USB STORAGE(MTP)", all is well... just my 2 cents, hope this will help in your findings to a fix. :angel:
[Nexus 6  Original Android Development] flar2:
It's not a kernel thing. I didn't change anything even remotely related to that.
[Nexus 6  Original Android Development] Herk718:
I figured that, mainly because I was on M build a few days back (Don't remember exactly which one) and the OP had in the change log "Fixed annoying USB Debugging Bug". So this could be the case with Pure Nexus...
[Nexus 6  Original Android Development] flar2:
Remember, EX 3.00 is permissive, and EX 3.01 and 3.02 are enforcing. You may need to reinstall or wipe some stuff to get things working. There are still root apps that dont work properly, you may have to remove them. For me, no action was required.
[Nexus 6  Original Android Development] flar2:
Marshmallow is brand new, so custom ROMs are still figuring things out.
[Nexus 6  Original Android Development] miguelito18:
[MENTION=4684315]flar2[/MENTION] is version 1.10 last one lollipop?
[Nexus 6  Original Android Development] Vinsanity232:
Sometimes I have to select mtp twice. That being said, windows still recognizes my device when its on charging only...
[Nexus 6  Original Android Development] Joe92T:
Hey Flar,

just to touch base, in regards to the screen tearing issue. You said try upping my sampling rate as a fix?

On the stock kernal

Sampling Down Factor is 100000

On your kernal, Sampling Down Factor is 8

so its night and day difference... you think going back to 100000 will fix that?
[Nexus 6  Original Android Development] Alxoom33:
Why do we need the kernel to be enforcing?

For example, I couldn't edit the build.prop when kernel was enforcing, so with EX 3.1 I had to flash the permissive.zip. I take it I'm back to enforcing once I flashed EX 3.2?
[Nexus 6  Original Android Development] TsarFlow:
Will there be cooler colors as for the Nexus 5 ? I mean in the Aroma. :)

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6  Original Android Development] magnamentis:
why this is an amoled display would not work the same way but you can either tweak the colors in elementalX app or get the "high brighness" widget from [MENTION=4684315]flar2[/MENTION] which boosts screen brightness.
[Nexus 6  Original Android Development] Krunk83:
So here is a log of the freeze/reboot I had when I was texting someone. [MENTION=4684315]flar2[/MENTION]

https://docs.google.com/uc?id=0B33bWfk5j-HCT2dDSklwdE0yS2c&export=download

I'm on JDX 4.0 ROM with elementalX 3.0.2 and superSU 2.52.
[Nexus 6  Original Android Development] flar2:
The log just cuts off, was there anything else in the /sys/fs/pstore folder?

In any case, I'm guessing it's another watchdog bite, like some people were having on lollipop.
[Nexus 6  Original Android Development] Krunk83:
Yeah, two "pmsg-ramoops-0" files. What's a watch dog bite? Seems like these logs go on and on forever.

Nexus 6 M
[Nexus 6  Original Android Development] flar2:
If there is some kind of error that keeps repeating, it shuts down as a precaution. This device seems to have a lot of hardware issues.

If you still have those other files, could you post them?
[Nexus 6  Original Android Development] ManikandanGuru:
Bootlooped too.. I changed it to Permissive mode in TWRP.. and all is working fine.

But lots of apps are lagging heavily, even freezes for a minute or two. I don't know its because of this kernel or the Marshmallow itself. BTW I was already on SuperSU 2.50, i have no idea why the 3.01 Beta not worked.
[Nexus 6  Original Android Development] PhilDX:
no problems here with 3.01 and superSU 2.52 on stock
[Nexus 6  Original Android Development] :
So from what I'm reading on this thread. If I flash 3.02 I need to flash permissive.zip if the rom I'm on needs permissive? Did I miss something?
[Nexus 6  Original Android Development] galaara98:
Hmmm I don't think so

I flashed it, without anything special (I was already on the latest SuperSu)

As a matter of fact the reason to use 3.02 is because it Supports enforcing

Edit: maybe misunderstood... You want or need permissive? If so... Then yes, if you use 3.02, you would need to do something to get it back...

Something: being a variety of solutions, one of them would be a flashable zip as you have suggested

Aaron