yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] zzhhzz:
Got it. Thank you. I figured that would be the case, as I had to do it for Pure Nexus and Elemental X on my Nexus 6. Here is a link in case anyone needs it.

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[Nexus 7 (2013) Original Android Development] nfremd:
Ok I must be doing something wrong. Because when I flash the latest ElementalX Marshmallow Kernel I get bootloops. I first dirty flashed the rom, then flashed Chainfire's boot.img for razor, then I flashed ElementalX = bootloop. Can anyone help me out? I'm running PureNexus Rom (latest).
[Nexus 7 (2013) Original Android Development] bmatney:
PureNexus doesn't play well with third party kernels
[Nexus 7 (2013) Original Android Development] nfremd:
That odd, because my Nexus 6 which is running Pure Nexus plays well with any 3rd party kernel. Wonder why Flo does not.
[Nexus 7 (2013) Original Android Development] zzhhzz:
I had the same issue. I flashed Pure Nexus, then chainfire's boot.img, then elementalx, and then permissive.zip.

Have you tried that?
[Nexus 7 (2013) Original Android Development] nfremd:
I did not try the permissive.zip yet because I thought that wasn't needed. I'll give that a whirl.
[Nexus 7 (2013) Original Android Development] DroidIt!:
I know for instance AICP has some pretty big differences between their N6 and N7 versions. There's just a lot of user setting and some framework differences as I'm sure there is with Pure Nexus. But, you could compare the op's of PN on the N6 and on the N7 and see what differences in features there are. For framework differences you'd need to ask the dev and if you tell him that ElX works with PN on the N6 and not the N7 maybe he'll look into it. I've never used Pure Nexus but that's what I'd do. :)
[Nexus 7 (2013) Original Android Development] sniperfox47:
Still no answer on the topic of encryption support...?
[Nexus 7 (2013) Original Android Development] seanvree:
so If i flashed the stock 6.0 firmware can I use this kernel? I DO NOT have a custom ROM, however I already have busybox and SU with TWRP?

Thanks,
[Nexus 7 (2013) Original Android Development] NovaSlim:
Most users of this kernel are running stock 6.0 atm, if you have rooted with SuperSU2.52 already you should be fine with flashing EX5.04
[Nexus 7 (2013) Original Android Development] quickdraw86:
Can confirm elemental x working on purenexus M with the same installation procedure you used.
[Nexus 7 (2013) Original Android Development] TheC92:
Do you plan to support systemless?

http://xdaforums.com/showpost.php?p=63197935&postcount=2
[Nexus 7 (2013) Original Android Development] flar2:
Already supported
[Nexus 7 (2013) Original Android Development] HaRdC0r3:
I'm having an issue..... Not sure how to about it. I like your kernel when it's working.....I get random reboots and not sure what the problem is as I have not checked. I replaced the powermsm.blah with the one from the factory image and now my tablet is running very well without the reboots
[Nexus 7 (2013) Original Android Development] NovaSlim:
Immediately upload the last_kmsg.txt file to here so flar2 can take a look and figure out what went wrong.
[Nexus 7 (2013) Original Android Development] AnkeshReborn:
Boot loops with DU
[Nexus 7 (2013) Original Android Development] quickdraw86:
You're far more likely to get a good response if you provide the software version of DU that you're using, since they're building L and M right now, the build date or version number, and the version of elemental x you attempted to install... Your installation procedure will also be useful information, as some custom M ROMs require the installation of chainfire's boot image before elemental x...
[Nexus 7 (2013) Original Android Development] gorilla p:
I'm having the same problem.

Installed latest DU 10 (6.0/M) test for Flo. Works great with stock kernel.

Did a factory reset, tried installing EX at same time as ROM and got boot loop.

Wiped again and installed ROM without EX and everything works fine.

Tried flashing EX on its own with stock settings, now that ROM has been successfully installed and it caused a bootloop again.
[Nexus 7 (2013) Original Android Development] flar2:
It's because many of the custom ROMs don't work with selinux enforcing.
[Nexus 7 (2013) Original Android Development] gorilla p:
Hmmm... I believe I saw a flashable permissive setting patch. I will give that a try tomorrow.

Thx for the idea.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

-enforcing/permissive is now optional. Permissive.zip is no longer needed if you uncheck "Enforcing" during installation.

You don't need to flash Chainfire's boot.img anymore.

For stock ROM, it will automatically add the correct sepolicy.

For custom ROMs that need permissive mode, make sure you uncheck "Enforcing" in the installer options.

Download

ElementalX-N7-5.05

Changes:

-enforcing optional

-installer updates
[Nexus 7 (2013) Original Android Development] NovaSlim:
Thanks, flashed express on mine and everything is fine :good:
[Nexus 7 (2013) Original Android Development] DaveImagery:
Working great here as well.

Thank you!
[Nexus 7 (2013) Original Android Development] Diljinder:
Was flashing Chainfire's boot.img a requirement before?

Earlier, I just flashed previous kernel version, then flashed Super SU & everything worked just fine for me.

I thought Chainfire's boot.img was for those who wanted root while remaining as close to stock kernel as possible.
[Nexus 7 (2013) Original Android Development] flar2:
I think there was one version where you had to flash Chainfire's boot.img, and it was required when flashing EX on certain custom ROMs.

But now it's not required in any case
[Nexus 7 (2013) Original Android Development] MatVekk:
Not work in "FLO pure nexus project" ... Boot loop

Inviato dal mio Nexus 5 Cataclysm 6.0
[Nexus 7 (2013) Original Android Development] flar2:
I have literally answered this about 100 times today.

Uncheck the "Enforcing" option during installation.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Makes you wonder, does it not...?
[Nexus 7 (2013) Original Android Development] NovaSlim:
I keep having nightmares that flar2 will get so frustrated by such posts that he turns into Franco :silly::silly: Then he will rage on every single "bug" post/Tracks down everyone who give his app less than 5 stars on playstore and dress them down :p
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Well, we can only hope...?
[Nexus 7 (2013) Original Android Development] gorilla p:
Yup, I had same bootloop issue with DU v10 test. I unchecked the enforcing option during installation and all is well.
[Nexus 7 (2013) Original Android Development] lolcopter:
Reading is half the battle
[Nexus 7 (2013) Original Android Development] MatVekk:
Uncheck but not work. No problem, the problem is the rom, in stock rom work very fine [emoji6]

Inviato dal mio Nexus 5 Cataclysm 6.0
[Nexus 7 (2013) Original Android Development] nokiagye:
My friends have you find any good Marshmallow for flo?
[Nexus 7 (2013) Original Android Development] Natakranta:
Flo Pure Nexus + EX 5.05 works fine. No problems.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Truth. A great combination too FWIW.

---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------

Find? There are several good options in plain view... Pure nexus and Oct-M are excellent choices... VRToxin, screw'd M (currently in alpha), and a couple others are coming along nicely. That synopsis doesn't even include two great stock options that are readily available in the forums.
[Nexus 7 (2013) Original Android Development] Natakranta:
Indeed. My little tablet is super fast and responsive. It is looking at my wife's newer Galaxy Tab S 8.4 bloated with Touchwiz, slow and laggy, and is laughing out loud on it :D

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Nexus 7 (2013) Original Android Development] 53l3c7a:
CleanROM 7.1 and ElementalX 5.04 here - I've never had such great battery life before! Running great. Smoother than ever, as well.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Lol. Touchwiz had been on a mission to seek and destroy free system resources for years now, and accomplishes its mission with ruthless efficiency.
[Nexus 7 (2013) Original Android Development] lmulli:
I find http://xdaforums.com/nexus-7-2013/development/rom-stock-5-1-1-lmy48i-t3175835 pretty good. Never been one to remain on Stock roms for any length of time, however, seems to do everything I need and with xPosed for Marshmallow hopefully due this week, see no reason to swap it to AOSP at this time.
[Nexus 7 (2013) Original Android Development] 53l3c7a:
Looks nice - pretty much exactly what my setup entails, but with less work on my part. Good find!
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
Greetings,

After years of running Rascarlo ROMs and Franco's kernels, I've switched over to CM 12.1 Nightly for the N7 (and N5 too). I purchased the ElementalX app and installed on my two encrypted N5's with no problem (one N5 wouldn't boot into recovery from the app, so I just rebooted to TWRP and flashed it. The other N5 *would* boot to recovery from the app...weird. Both on CM 12.1 Nightly. ) Anyway, my encrypted N7 just sits at the boot screen, never gets to the password entry screen. I'm on the "regular" CM 12.1, not the CAF version. In the app, it pre-selected "Cyanogenmod/CAF" so I left it at that. Any ideas on how to get this kernel working on an encrypted N7 using CM 12.1? Thanks!
[Nexus 7 (2013) Original Android Development] flar2:
Someone else said the kernel wouldn't work with encrypted data. I don't think I changed anything in the kernel around that, but I'll check. I don't use encryption on /data on this device, as it is not encrypted by default.
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
Ok, thanks for looking!
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
I don't know if you looked at encryption for 4.05, but it's still boot-looping. If you need a tester, let me know.
[Nexus 7 (2013) Original Android Development] flar2:
It's on my list for this weekend
[Nexus 7 (2013) Original Android Development] Ronaldo Forenucci:
Thank you Sir! :good:
[Nexus 7 (2013) Original Android Development] flar2:
I'm not sure why it won't work.

Can you send me kernel logs?

Install ElementalX

Reboot

If it stops on the bootanimation, connect with adb shell and get dmesg output:

adb shell dmesg > dmesg.txt

If it bootloops, immediately after the reboot, hold the volume down key to reboot to recovery and copy /proc/last_kmsg:

adb shell cat /proc/last_kmsg > last_kmsg.txt
[Nexus 7 (2013) Original Android Development] zapty:
Great kernel !

But [MENTION=4684315]flar2[/MENTION] the sluggishness that is found in flo is mainly because of the GPU its not that powerful to power that high resolution of a screen .

Qualcomm released new drivers for GPU , users reported smoothened interface and higher benchmark score.

arter97 integrated them in his kernel for 5.x and it was wonderful.

Maybe you could integrate them that would be wonderful.

Thanks.

;)
[Nexus 7 (2013) Original Android Development] Ænimal:
Qualcomm's latest GPU drivers for lollipop (extract the zip, it contains flashable zips for nexus 5, 7 and a third nexus device)

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

Edit: Beware, there are reports of YouTube and ggl maps not working after flashing these drivers

(Link provided by the dude abides)

For marshmallow see themes and apps section
[Nexus 7 (2013) Original Android Development] zapty:
Thanks but I was asking him to integrate these in the kernel itself !!
[Nexus 7 (2013) Original Android Development] ArclightX:
Hi! So I'm having the same problem.

The Details:

Device: 32MB FLO (WiFi Only)

OS: Stock Android Marshmallow v6.0.0 (MRA58V)

- Did a full factory image reinstall, (several times now actually)

- Rooted SuperSU (Beta v2.52)/Custom Recovery (TWRP v2.8.7.0)/BusyBox

- Encrypt Device (because it's a fresh OS install usually this just takes only 4mins or so)

- Flashed ElementalX v5.05 through Recovery leaving default settings as is

This is where the issues sorta start. After doing all that my device doesn't "Bootloop" persay. It starts up, shows the new Marshmallow "Loading" animation with the 4 colorful circle things and remains there forever and ever. I left my device plugged in overnight just to force the issue and when I woke up, (8hrs later), the Marshmallow animation was still going. Never even made it to the "enter your decryption PIN" screen.

You should also know that the order doesn't matter. That is if you flash your kernel first everything is fine, but once you encrypt, the perpetual boot animation happens. If you encrypt first everything is fine, but when you flash your kernel afterwards same deal. (Yes I tried both just to rule something funky out).

I tried this and I get the following message: error: device not found

I'm entering this command while the device is in the perpetual "boot animation" stage prior to entering the encryption PIN (which the device never progresses to anyways)

After I unsuccessfully tried the first command I shut off the device by long pressing the power button, then did the power button volume down trick to get into the custom recovery and from there i entered both commands:

adb shell dmesg > dmesg.txt

and

adb shell cat /proc/last_kmsg > last_kmsg.txt

I've attached both .txt files for you to have a look at. Not sure how useful they are but here they are.

Anyways, if I can be of more assistance please ask away and I'll see what I can do.

Thanks again for all your work and effort! it is greatly appreciated!

Cheers!
[Nexus 7 (2013) Original Android Development] Greedybro:
No boot, no enforcing

Hi !

I can't boot my nexus 7 Flo with the latest version. I read the thread, so i know i have to uncheck "enforcing", but there is no option that says "enforcing" in the aroma installer. On the last page everything is unchecked, and I did read all the pages a dozen times.

Any advice ?

Thanks
[Nexus 7 (2013) Original Android Development] NovaSlim:
Rom Version/Build number? EX kernel used and settings?

Also, Selinux Enforcing is checked by default on the last page(Other settings), scroll down and you will see it.
[Nexus 7 (2013) Original Android Development] Greedybro:
While I checked infos in order to answer you, i realised that it was not the 5.05 version i was trying to flash. Your app proposed me to install 4.05 so i didn't think there was a problem. But i dl the correct version and it works.

Sorry for wasting your time, many thanks for taking the time =D

And for your awesome work !
[Nexus 7 (2013) Original Android Development] NovaSlim:
I am not the developer, [MENTION=4684315]flar2[/MENTION] is so thanks should go to him.

App proposed you to install 4.05 because your rom is Lolipop based, 5.0X kernels are for Marshmallow Roms!
[Nexus 7 (2013) Original Android Development] flar2:
I will look at the logs and work on the encryption problem next weekend. Right now I'm 2000 miles from home for my day job.
[Nexus 7 (2013) Original Android Development] zapty:
[MENTION=4684315]flar2[/MENTION] it would be awesome if you integrate [MENTION=5161352]JustArchi[/MENTION] 'S optimizations into the kernel ..

Archi optimizations 4.0 , they are just amazing made s3 smoother than n7 .

he has them in his kernel i9515 devs have integrated them and they work flawlessly maybe you could integrate them.

that would jump the antutu scores way higher .

back over at s3 thanks to these opts we get 30k on antutu and with these opts in this kernel nexus will fly again..

I hope you look into them before [MENTION=5161352]JustArchi[/MENTION] modifies them to fit his oneplus 2 now.

Hope you look into it . it would really help us nexus 7 users.

thanks ..
[Nexus 7 (2013) Original Android Development] curiousde2002:
ElementalX-N7-5.00 to N7-5.05

My Nexus 7 2013 deb is presently on stock MRA58V with ElementalX-N7-5.00.

I just used this kernel and BETA-SuperSU-v2.50 to get root again by flashing both with TWRP 2.8.7.1.

Now I have 2 questions:

1. Can I just flash the new N7-5.05 over the N7-5.00 with TWRP and without doing anything else like reflashing SuperSu?

2. Could I also flash the stock kernel over the N7-5.00 without losing root?

Thanks for your help!
[Nexus 7 (2013) Original Android Development] NovaSlim:
You could, but should root with SuperSU-v2.52 after you flash EX5.05
[Nexus 7 (2013) Original Android Development] Greedybro:
My ROM is marshmallow 6.0 stock for nexus 7 ! The app is still proposing me to install 4.05 even though I have 5.05 installed.
[Nexus 7 (2013) Original Android Development] NovaSlim:
Screenshot plz, that's just hard to believe :confused:
[Nexus 7 (2013) Original Android Development] _jis_:
[MENTION=4684315]flar2[/MENTION]: I don't know if these bugs are known for EX Kernel Manager 2.30 and 2,31 regarding Battery Monitor:

Battery Monitor tile often show wrong information in "Stats while on battery", see both attached snapshots.

Sharing doesn't work. File /sdcard/Pictures/Screenshots/battery.jpg is saved, but for example Gmail show toast "Can't attach empty file".
[Nexus 7 (2013) Original Android Development] DroidIt!:
Not sure about the first, but the second is more than likely media scanning on your device or where the pics are being saved. I'd try moving the saved jpg to a folder where your camera pics are normally stored, reboot so your tab scans for media and see if you can attach that way. Something along those lines should work. But regardless, not kernel related. :)
[Nexus 7 (2013) Original Android Development] _jis_:
Sure, I didn't say it. My bug report was about app "EX Kernel Manager 2.30", but there is no dedicated thread for this app so I reported here.
[Nexus 7 (2013) Original Android Development] flar2:
Both of those bugs are known, I haven't had a chance to fix
[Nexus 7 (2013) Original Android Development] _jis_:
I am really sorry if my report was redundant, I searched hard, but have found nothing about it. I wanted to help improve EX Kernel Manager because this app deserve it :)
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
I'm getting random restarts. Will past a last_kmsg next time it happens.
[Nexus 7 (2013) Original Android Development] NovaSlim:
last_kmsg have been deprecated in M, you need to post the content of your sys/fs/pstore folder instead.
[Nexus 7 (2013) Original Android Development] flar2:
It's actually deprecated in linux 3.10, which is used on newer devices. This one still uses linux 3.4, so last_kmsg is still used.
[Nexus 7 (2013) Original Android Development] NovaSlim:
Thanks for the clarification:good:
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
Funnily enough, it just happened again and I can't find any info in either location.

Thoughts on how to do this?
[Nexus 7 (2013) Original Android Development] flar2:
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt

last_kmsg is always there, it will show the kernel log from the previous boot.

I would suggest, however, that you do a full wipe and clean install if you have instability. Or at least make sure you're not overclocking or undervolting. This kernel has been in a stable state for long time.
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
When I installed, the only thing I changed was set it to permissive for Viper4Android and turned off the magnetic sensor because I have a cheap as folio case the turns off the screen when folded back.

I'll see about getting that last_kmsg, I those commands before in Terminal Emulator and they did not work.
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
It looks like last_kmsg isn't in /proc. I went and looked with root Explorer and it is not there.
[Nexus 7 (2013) Original Android Development] NovaSlim:
Use ElementalX Kernel Manager you can save the last_kmsg directly to sdcard.
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
Tried that as well, get "not available".
[Nexus 7 (2013) Original Android Development] NovaSlim:
Works just fine for me, did you give EX Kernel Manager Storage Permissions?
[Nexus 7 (2013) Original Android Development] gorilla p:
Im using latest EX and am getting crashes/reboots with a specific Synapse profile and Im not entirely sure why. Im getting some issues within Synapse as well, but not major. I uploaded last Kmesg, Logcat, DMesg. Could you please take a look and let me know why this may be happening? If you can confirm its kernel related, i will provide the specific settings to help troubleshoot,

KMesg

http://m.uploadedit.com/ba3m/144805446643.txt

LogCat

http://m.uploadedit.com/ba3m/1448054587303.txt

DMesg

http://m.uploadedit.com/ba3m/1448054627985.txt
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
Yup.

I guess I'll backup with Titanium and do a full reinstall and see if that will fix it.
[Nexus 7 (2013) Original Android Development] flar2:
If you can't see it in be terminal or a file explorers, then it won't work in EXKM either.

How are you rooted?
[Nexus 7 (2013) Original Android Development] flar2:
L2 error, never seen this before. Could be a hardware glitch.

Reinstall without ElementalX l2/bus optimization. If you are overclocking or undervolting, go back to defaults.
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
It's rooted the traditional way.
[Nexus 7 (2013) Original Android Development] tungdil:
If you haven't done so yet and want to do further analysis (using adb shell as I think this is easier than going via a terminal emulator; even though it should work there too):

uname -a

will show you details of the kernel that is actually running.

For checking if you're properly rooted you could, for example, do

su
chmod 444 /proc/last_kmsg

You shouldn't see a Permission denied message and an ls -l /proc/last_kmsg should display the attributes -r--r--r-- instead of -r--r-----

Additionally you could have a look at the following directories and try analyzing what you find there:

/data/tombstones/
/data/dontpanic/
/data/system/dropbox/

Finally (you'd need root and, I think, also busybox)

su
setsid cat proc/kmsg > /sdcard/kmsg.txt &

will constantly copy kernel messages to /sdcard/kmsg.txt and should enable you to analyze the kernel messages after the next crash.
[Nexus 7 (2013) Original Android Development] gorilla p:
I will see if I can narrow it down a bit more today. I don't believe I used any settings that weren't in other profiles, but just a different combination of things (creating exportable Synapse profiles).
[Nexus 7 (2013) Original Android Development] maigre:
Any change of the RGB sliders in Kernel Adiutor's Screen settings causes the display to instantly turn the same teal color as is the Material Design theme color for KA. I have to reboot to have the N7 be usable again. Anyone else had this problem? Is there any way to successfully do color tweaks?
[Nexus 7 (2013) Original Android Development] mdamaged:
Use flar2's app, or complain to the dev of KA.
[Nexus 7 (2013) Original Android Development] Krunk_Kracker:
Unfortunately I've already reinstalled from scratch, but thank you so much for this info. I'm about to install the kernel so we'll see how it goes.
[Nexus 7 (2013) Original Android Development] 623baller:
usb OTG + Charge work around

if you have issues with USB OTG + charge working at the same time especially for people who install nexus 7 in their cars, this work around is for you.

this is very similar to the usb reset work around mentioned in the earlier threads.

basically, someone wrote a script to turn on and off USB port, it simulates plugging and unplugging USB cable. see below link

http://xdaforums.com/nexus-7-2013/n...b-recognize-boot-solved-t3234773#post63980109

only thing i added to my set up is download script manager widget, so i can add a button to execute the script whenever i wish instead of waiting for reboot.

only down side is i now get a loud thump when i turn on ignition switch in the car , no idea why. confirmed working for nexus 7 running Android 6.0 clean rom and Elemental X kernel 5.05.