yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] flar2:
Something is definitely wrong. Marshmallow is very smooth, and so is this kernel.
[Nexus 6  Original Android Development] :
I'll try and report back. Thanks.

Edit: I updated my rom Xtrasmooth and 3.02 is baked in. If I flash another rom I will update.
[Nexus 6  Original Android Development] Krunk83:
Don't have them anymore. Would it maybe be the kernel app I am using?

Nexus 6 M
[Nexus 6  Original Android Development] :
For a little more clarification/information...

Watchdogs are typically hardware (in phones and cheaper electrician it's usually software running independent of the main process) failsafes that will check parameters from time to time. If something looks like it's it off from preset allowed parameters, ie: frozen, endless loop, temperatures rising, etc etc etc... The watchdog circuit/process terminates it.

There is no clean shutdown, with a hardware watchdog it often just cuts power to the circuit. With software it terminates the process. This is the reason that logs will just abruptly end in a watchdog shutdown instead of going through until the end with debugging information.
[Nexus 6  Original Android Development] Krunk83:
Could it be doing this because I am using Franco Kernel Updater app to control the kernel?
[Nexus 6  Original Android Development] Amos91:
I use both the ElementalX app and the Franco Kernel app (for preset colours etc) just fine - no issues.
[Nexus 6  Original Android Development] Lawstorant:
I don't get you people. What's with selinux permissive kernels? Just use SElinux mode changer app. Works like a charm.

Wysłane z mojego Nexus 6 przy użyciu Tapatalka
[Nexus 6  Original Android Development] magnamentis:
+1
[Nexus 6  Original Android Development] 420p:
ain't JDX full of init.d-scripts ...
[Nexus 6  Original Android Development] NLBeev:
You forgot something

http://xdaforums.com/devdb/project/dl/?id=12506
[Nexus 6  Original Android Development] Krunk83:
My phone freaks out when I have this app installed on my phone. Tells me to remove it immediately.

Nexus 6 M
[Nexus 6  Original Android Development] magnamentis:
it does not freak out, simply click on the notification and then "keep it anyway" together with checking the box which says "never warn me again* or someting like that and you're good to go. google does not like selinux changing apps, hence why
[Nexus 6  Original Android Development] mibgeneral:
Love the doubletap to wake feature, can't live without it. Thank you sir for the kernel.
[Nexus 6  Original Android Development] simms22:
im STILL using the old app, the one that got booted from the play store. its simple, and i kinda like it. anyways, im on marshmallow, and i just got the oddest notification. lol :o
[Nexus 6  Original Android Development] buffal0b1ll:
You never got that on lollipop? I got it all the time whenever I'd clean flash and reinstall the old app. Been a while since I've seen it. I switched to the new app for continued updates, it's worth the jump.
[Nexus 6  Original Android Development] flar2:
I initially put a link to the apk on my website and it immediately got blacklisted as a malicious site. So I had to remove the link.

I am still able to access exactly one statistic about that app on my developer account: current installs

Despite all the warnings, it is still installed on 1,576 devices.

I also still get several emails per week about the incident
[Nexus 6  Original Android Development] simms22:
na, this is the first time ever :eek:
[Nexus 6  Original Android Development] appro77:
Still haven't been able to flash this without a bootloop. The OP says:

CAUTION:

Do NOT flash this over other custom kernels!

You should only flash ElementalX over the kernel that came with your ROM!!!

Problem is all the roms I've tried come with a custom kernel of some description. Is there any way I can flash this on Chroma without ending up with a bootloop?
[Nexus 6  Original Android Development] CroW_D:
Someone have a good config for performance/battery mix for me ?

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] LGtMgG2t:
Did you try flashing the M stock kernel or the modified stock kernel from Chainfire? I was able to flash the latest Elemental over top of what Pure Nexus M provided and Despair's UberMallow. I think the caution in the OP is indicating to not flash this kernel over top of a kernel that YOU flashed on the ROM already. Hope that makes sense.
[Nexus 6  Original Android Development] flar2:
Some roms need the permissive zip in the OP

It's not as big of a problem on this device as on others.

But honestly I wish more would just use the stock kernel.
[Nexus 6  Original Android Development] flar2:
Default settings
[Nexus 6  Original Android Development] Yahoo1:
Hey, [MENTION=4684315]flar2[/MENTION]. Great work. Can I flash this kernel over the modified stock kernel by Chainfire? I think I can but want to be on the safe side... Thanks.
[Nexus 6  Original Android Development] tealio:
I did on stock marshmallow ROM and have no problems...
[Nexus 6  Original Android Development] flar2:
You can flash this over stock, and you can flash it over Chainfire's modified boot.img
[Nexus 6  Original Android Development] mattmtx:
Hi, this its normal?

Iddle d rain always in 0%?

I have xposed with greenify y amplify (donation).
[Nexus 6  Original Android Development] flar2:
Sometimes the battery monitor gets screwed up, reset it
[Nexus 6  Original Android Development] Beakhole:
Pocket Detection

[MENTION=4684315]flar2[/MENTION] I love using your Wake Gestures app for the pocket detection. But how does the pocket detection in that app work? I'd like to be able to enable pocket detection with an init.d script, just like how any wake gesture can be enabled on boot with a script, such as setting /sys/android_touch/doubletap2wake to "1". Is there a similar setting that gets modified whenever pocket detection is enabled in your Wake Gestures app?
[Nexus 6  Original Android Development] Alxoom33:
Is there a setting in the EX app to turn off the led when the phone is connected to the dock at night. JDX 4.01has charge led always on by default. Thanks.
[Nexus 6  Original Android Development] foxfire450:
You can disable it entirely under Miscellaneous -> LED Trigger change to "none".
[Nexus 6  Original Android Development] garyHal:
Interesting, I didn't know flar2 had an app for this. Is it free? How does it compare to GravityScreen?
[Nexus 6  Original Android Development] Beakhole:
It uses the proximity sensor to know when it's in your pocket so none of your wake gestures turn on the screen, such as doubletap2wake or sweep2wake. I'd really like to know if the same task could be done with a shell command of some kind so I can put it in an init.d script.
[Nexus 6  Original Android Development] flar2:
It can't be done with an init script. I call the proximity sensor programmatically in the app. The kernel is not involved at all, the wake gestures service has to be running.
[Nexus 6  Original Android Development] Beakhole:
Ok thanks for the response. I appreciate it.
[Nexus 6  Original Android Development] appro77:
OK, thanks. Flashed the permissive zip then the kernel. All good now.

Can anyone explain how the high brightness mode is supposed to work? The setting only seems to stick until the screen is turned off. After that it reverts to "disabled". Is this how it is supposed to work?
[Nexus 6  Original Android Development] Beakhole:
I have this same question that I've wondered about for a while. [MENTION=4684315]flar2[/MENTION] do you have any idea why that is and how to work around it?
[Nexus 6  Original Android Development] appro77:
I've just discovered and purchased the widget from the Play store. It toggles high brightness mode. I'm guessing that this should be used sparingly to prevent screen damage? Can someone confirm that?
[Nexus 6  Original Android Development] :
I believe this is intentional. The high brightness mode via the EX-Kernel manager app is only temporary.

The High Brightness Mode Widget that Flar2 sells (for like $0.99) gives you a widget, persists across reboots & screen on/off, and provides contexts to enable/disable it from third part apps that can send contexts (tasker). I've bought it, it's definitely worth the money even if it is a very specific use feature set.
[Nexus 6  Original Android Development] Alxoom33:
Thanks, but that's what I initially tried. But it only dims the charge led slightly.

Turns out the solution is replacing a system file from an earlier JDX build. Now EX's led control works perfectly!
[Nexus 6  Original Android Development] nagato86:
[MENTION=4684315]flar2[/MENTION] Hello everyone ... I installed elementalx 3.02 on my nexus 6 with pure nexus rom but when I connect the phone to the PC is not recognized as a mass storage ... also does not show the notification debug ... why ?! thank you all
[Nexus 6  Original Android Development] RandomPooka:
Same thing happens here, but I assumed that it was ROM related and not kernel related.

I'm able to get the USB Debug icon by going into Developer options and toggling the debug option, and I can get it to say it's in file transfer mode if I manually set it each time I connect to the PC. But, it doesn't ever show up on the PC side of things no matter what combination of settings I use, and no matter what the phone thinks is happening.
[Nexus 6  Original Android Development] NiNJAwitaRaZR:
Been running this ROM awhile now with slimLP by yank and every time I try to install the kernel with anything higher than 2880 MHz I get bootloops, it'll get the the "Android is upgrading " screen then right back to Google splash screen and then slimLP boot animation
[Nexus 6  Original Android Development] LGtMgG2t:
Don't take this wrong but you do realize 2649Mhz is the stock speed, right? Anything over that is overclocking and going to be hit and miss. Overclocking any device is going to be dependent on MANY variables. Recently I read the CPU governor might play a big part in how much you can overclock this device.
[Nexus 6  Original Android Development] flar2:
Yes, I believe this is a rom issue
[Nexus 6  Original Android Development] nagato86:
the same rom with other kernel works ... :(
[Nexus 6  Original Android Development] RandomPooka:
Aww, that is a bummer.
[Nexus 6  Original Android Development] flar2:
I didn't change anything to do with that...

I would advice using the stock ROM if things aren't working.
[Nexus 6  Original Android Development] Krunk83:
Just downloaded the app the other day. Nice job.

Nexus 6 M
[Nexus 6  Original Android Development] K-alz:
Running pure nexus Marshmallow. Flashed this kernel. Could someone please tell me the perfect settings for battery saving and performance? Thanks in advance.
[Nexus 6  Original Android Development] Krunk83:
I leave everything stock with the elementalX governor and it's pretty sweet. The only things I change are color control and vibration.

Nexus 6 M
[Nexus 6  Original Android Development] K-alz:
Oh! That's what I did, thought I needed to change something. Thanks a lot.
[Nexus 6  Original Android Development] NevaX1:
Works perfectly with Chroma !

Thanks for this kernel :)

It support the CIFS ?
[Nexus 6  Original Android Development] mattmtx:
Thanks!!!! It's working fine now.
[Nexus 6  Original Android Development] mibgeneral:
Works perfect with Lightrom. Thanks
[Nexus 6  Original Android Development] aoleg:
When installing ElementalX (using v3.02 with stock M at the moment), I enabled the charging LED. However, the green charging LED only works when I charge the phone fully booted. If I turn off the phone and then put it on a charger, the charging LED is not activated (I can only see the charging icon). If my memory serves me well, the LED used to work in some older version of ElementalX (or am I wrong here?)
[Nexus 6  Original Android Development] Woody:
[MENTION=4684315]flar2[/MENTION] Are you going to offer Express.zips once things settle down? Once I set up the kernel in the initial install with aroma, I like to just flash express thereafter (unless there is a drastic change or something like that). Obviously things are still being worked out here and there with MM, so I would imagine if you are going to make them that is why we haven't seen any yet? Or are you abandoning that idea?
[Nexus 6  Original Android Development] magnamentis:
if you check the download and install section in the EX app and click on update ( blue button ) you should get a choice, express or custom, hope i understood you well :)

EDIT: added screenshots for N6 & N5 to illustrate the above
[Nexus 6  Original Android Development] Woody:
Got ya. I just remembered that option from inside the apk now that you mentioned it. I was thinking on his AFH page and not in the apk itself. Been a long time since I clean flashed a new OS and kernel combo. Thanks man.
[Nexus 6  Original Android Development] flar2:
Update

For Android 6.0 Marshmallow

-no changes to the actual kernel

-if you are stock and not rooted, you must flash Chainfire's boot.img and use SuperSU 2.52 or later

-if you are stock rooted or on a custom ROM, just flash

-recommended to reflash your ROM before flashing this

Download:

ElementalX-N6-3.03

Changes:

-better compatibility for custom ROMs
[Nexus 6  Original Android Development] RandomPooka:
So, if I'm running 3.02 with Pure Nexus6 and it's just fine, is there any reason to upgrade this if the running kernel is the same?
[Nexus 6  Original Android Development] flar2:
If everything is good, then no need.

However, I do suggest that users of custom ROMs reflash teh boot.img that came with the ROM and then flash EX 3.02
[Nexus 6  Original Android Development] inzaghi75:
Is it permissive kernel?

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] flar2:
No

If you need permissive, flash the permissive zip.

However, permissive should be discouraged
[Nexus 6  Original Android Development] nathanchance:
I got a bootloop with Pure Nexus after reflashing it over 3.02 then trying to flash 3.03. It was running fine with Enforcing on 3.02 so I flashed Chainfire's boot.img and it started fine on 3.03 after that. Just a heads up for anyone wanting Enforcing on Pure Nexus. Should probably work by just flashing the permissive zip but I did not try that.
[Nexus 6  Original Android Development] IcipherPT:
I can't select any freq above 2.88ghz on EX Kernel, if I select one, my phone just reboots.. Don't know if it's kernel or app related and ofc if it was already mentioned in this thread :)
[Nexus 6  Original Android Development] flar2:
3.03 no longer incorporates the modified sepolicy for root. I had to take it out because it might conflict with custom ROMs.

If it is needed, then you must flash Chainfire's modified boot.img

Your phone can't handle it
[Nexus 6  Original Android Development] :
Where can I get the boot.img?
[Nexus 6  Original Android Development] nathanchance:
http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[Nexus 6  Original Android Development] :
Thanks it, worked.
[Nexus 6  Original Android Development] Alxoom33:
Express upgrade using EX express update worked great!
[Nexus 6  Original Android Development] RandomPooka:
I'm having a mental block here. Wouldn't flashing Chainfire's boot.img overwrite ElementalX, and wouldn't flashing ElementalX overwrite the boot.img from Chainfire?

If not, in the event of boot problems, would the steps go as follows?

1 - Flash ROM (PureNexus 10/17 build)

2 - Flash Appropriate gapps (Also Pure 10/14 release)

3 - Flash Chainfire boot

4 - Flash ElementalX 3.03

5 - Flash SuperSU 2.52

6 - Listen to the Flash Gordon theme song by Queen (3x to be sure)

---

Normally, I would just flash ROM, gapps, SuperSU, and ElementalX in that order, while listening to the Ohio Players or the Commodores

---------- Post added at 05:35 AM ---------- Previous post was at 04:57 AM ----------

By bootloop, are you referring to crashing, burning, and rebooting before even getting to the boot animation, or the phone just hanging out on the bootani for hours if you let it?

I'm also still unclear on how Chainfire's boot.img and ElementalX play together when flashed on the same device. If there's no changes to the kernel between 3.02 and 3.03, couldn't custom ROM users just flash 3.02 if they've got it?
[Nexus 6  Original Android Development] magnamentis:
why are you surprised. this is overclock and obviously your CPU cannot deal with higher than that clock speeds. everything above stock cpu frequency is not certain to work properly, same applies to underclocking. it seems that your CPU's ASV/PSV level ist on the poorer end.
[Nexus 6  Original Android Development] nathanchance:
For the process you have above, you don't need to flash SuperSU because it is built into PureNexus. I got a boot animation for 15 minutes before I went into the bootloader, did the above process, and it booted up in 2 minutes. Chainfire's boot.img allows SELinux to run in Enforcing. ElementalX 3.02 had the modifications from that boot.img in its own SEPolicy, whereas 3.03 does not.
[Nexus 6  Original Android Development] NLBeev:
Because the 'why' is missing. . . . ROM's with enforcing SElinux enabled has the pro of some protection. Malware will be denied access. Probably the same can happen with some bad coded or obsolete apps. [MENTION=4684315]flar2[/MENTION] correct me when I am wrong,
[Nexus 6  Original Android Development] RandomPooka:
The SuperSU bit aside (It's a reflex when flashing the pile of zips in TWRP to just add it to the list), this still doesn't explain how flashing Chainfire's boot.img doesn't completely overwrite the ElementalX boot.img and vice versa. I get that the sepolicy is modified and replaced, and totally get the adb command line process in Chainfire's OP where the boot.img can be downloaded. What I don't get is how the changes made aren't eradicated when flashing the EX boot.img after the Chainfire one.

Knowing that a thing works is fine, but not enough. I want to know WHY it works. How can you do an incremental image flash like that? Or, does the EX Aroma installer not flash an image as much as copy certain files directly into the boot partition, leaving some intact and replacing only what's relevant? I'm digging around on this now, but I'm unfamiliar with how the Aroma installer works as opposed to just writing/dumping a static boot.img with an updater-script.

Actually, I think I'm answering my own question as I ask it.

-- edit --

I love when you just keep questioning things until you come up with a possible explanation that you can check for your damn self.
[Nexus 6  Original Android Development] danarama:
Usually a Boot.img contains 2 major components. Kernel & RAMdisk.

When you flash a stock kernel, you flash both the above.

In order to have root on Marshmallow, you need a change in RAMdisk..

Chainfires boot.img contains these changes in RAMdisk.

ElementalX.actually does NOT contain RAMdisk.. It modifies existing RAMdisk on your device.

So to get root in an unrooted system, you.must flash chainfires boot.img to get the RAMdisk.. Then when you flash elementalx, which doesn't replace the RAMdisk, you keep those chainfire changes.

If you have flashed a pre-rooted rom,.it will already have a modified ramdisk. Flashing elementalx alone will be enough.

Hope this clarifies..
[Nexus 6  Original Android Development] iKarido:
Flashing Elemental 3.03 after flashing PureNexus puts me in a bootloop. If I dont flash Elemental the rom boots fine. any help?
[Nexus 6  Original Android Development] armaki:
same here:(
[Nexus 6  Original Android Development] franck811:
Same here ROM pure Nexus :crying:
[Nexus 6  Original Android Development] flar2:
Maybe you need the permissive zip

ElementalX, the kernel, works with every custom ROM. The problem today is installing things in the right order so everything is correct in the boot.img. I don't know what the formula is for each ROM. But it can be done.

Usually the problem is they set the kernel permissive, and then enforcing kernels don't boot. I don't know why they do this. All the kernel devs are making enforcing kernels, because that is the way it should be.
[Nexus 6  Original Android Development] franck811:
I have flashed the permissive zip but still bootloop

I have flash ROM - ZIP and KERNEL
[Nexus 6  Original Android Development] flar2:
Other people have it working. Are you sure it's not just optimizing apps? That can take ten minutes or more.

In any case, I would recommend a nice clean install.
[Nexus 6  Original Android Development] franck811:
yes because I have bought your application and I also tried updating since app since 3.02 but bootloop and I waited 20 minutes sorry
[Nexus 6  Original Android Development] LGtMgG2t:
After you flash the ROM and the PN Gapps, are you then booting up and going through the setup? I always suggest booting with the stock kernel at loeast 1 time before you flash a custom kernel. I flashed 3.02 and wiped caches on PN M a few days ago without issue.
[Nexus 6  Original Android Development] NLBeev:
Did you flash M-bootloader and M-radio. There 'zips' in the OP of the thread about the JDX rom.
[Nexus 6  Original Android Development] franck811:
yes M-bootloader and M-radio. 3.02 Working but not 3.03
[Nexus 6  Original Android Development] flar2:
Doesn't make sense. They are literally identical.
[Nexus 6  Original Android Development] DroidIt!:
Just as an aside :) Radio matters not at all. You can be on the gingerbread radio if it works best for you. Have you tried with a different ROM? The issue is almost always ROM side 95% of the time BTW in my experience ;)
[Nexus 6  Original Android Development] iKarido:
I tried flashing everything Rom then Gapps then Kernel but got bootloop. Tried to boot without kernel then go through the setup then went back to flash the kernel but i still got bootlooped. Bootloader and Radio are flashed. The PureNexus Rom has Permissive SELinux Status. Maybe I need to flash the modified Boot.img before flashing the kernel? or should I flash the permissive.zip from OP?
[Nexus 6  Original Android Development] LGtMgG2t:
Strange. You shouldn't have to flash the modded boot. img or at least I didnt. Have yu tried flashing ROM, Gapps and then the SuperSU 2.52 zip file? Wipe caches and then see if it will boot to setup and after setup then reboot to try and flash this kernel.

Other than that, I'm out of options.
[Nexus 6  Original Android Development] iKarido:
Since the rom (PureNexus) is already rooted with SuperSU 2.52 I dont think it will matter. Will flash the Permissive.zip then the Kernel and see if it boots.
[Nexus 6  Original Android Development] flar2:
If you can't get it working, I would really suggest the stock ROM. All my devices are running better than ever with stock Marshmallow and ElementalX. Zero problems.
[Nexus 6  Original Android Development] RandomPooka:
Pure 10/17 needs either Elemental 3.02 or ChainfireBoot+Elemental 3.03

We literally just had this conversation for 45 minutes or so, right before the post mentioning a bootloop problem with Pure and EX
[Nexus 6  Original Android Development] iKarido:
Just saw it. Thanks. will try right now
[Nexus 6  Original Android Development] magnamentis:
not sure if that is the order you flashed but if you flash permissive before the kernel, the kernel will set back to enforcing, the permissive zip has to be flashed after the kernel IMO further, again, use a SELinuxMode Changer app because it makes you independent of rom and kernel, it can even be on if a kernel is permissive, doesn't to any damage, is just always right like that. this is especially good in api transition periods like we have it now. if everyone would use such an app we would have zero posts on the matter. it's just the way we want it, no matter what we flash and in which combo, just sayin' further i can's see why selinux would have an impact on boot capability.

---------- Post added at 06:29 PM ---------- Previous post was at 06:23 PM ----------

it might indeed has to do with the rom since both with the same problem are on pure nexus while it works fine on stock and cataclysm. cataclysm is stock + 9 lines of code, the closest to stock pluse a choice of meaningful features one can get without xposed.