yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] nigelhealy:
Yes, CM13 does support f2fs. I tried that combination.

The issue is CM13 follows Google's use of forced encryption if the platform passes a small benchmark showing to itself its not significantly slower. So be careful. As the move to f2fs involves a full wipe anyway of /data then you can certainly simply try it, in an Android shell use mount command and see what is f2fs, and look in settings if the encrypt tablet option is there showing its not encrypted. If you find CM13 is encrypting, then do a full wipe (data and encryption gone), ensure its back to /data and /cache f2fs, and then flash fed_encryption patch in recovery before booting. That's quite a set of changes, ROM, fed patch, ElementalX. Cyandelta is recommended as it then ensures you run fed patch after every ROM flash so you don't forget.

I'm on Pure Nexus, it doesn't have forced encryption. Probably very few N7 are encrypted as its too slow and fail the benchmark to encrypt.
[Nexus 7 (2013) Original Android Development] tesna:
Hi,

I just installed elementalx kernel on mine (on cm13, /data and /cache on f2fs) and seems works fine so far. I installed using the flashable zip and enable OTG + charging and usb fast charge in aroma installer. However the tablet wont charge on OTG. Figured out maybe needs to install EX kernel manager to enable it, then I purchase it on the play store and sure it did the OTG+charging is enabled and working fine. However, how do I make the settings stick after each reboot? after each reboot it seems the OTG + charging option is back to disabled and I need to enable it manually.

EDIT: I'm a moron.. i think I found it
[Nexus 7 (2013) Original Android Development] BS86:
by restoring a twrp backup, you also restore the file system format. meaning if you take a backup of ext4 /data, then convert /data to f2fs, then restore the old ext4 /data backup, the /data partition will be ext4 again.

edit: what would work is the following: taking a backup of /data, changing the filesystem to f2fs, setting up your device - and after that use titanium backup to restore the data of selected apps (by choosing "extract from nandroid backup" in the menu - it requires the paid version of titanium as far as I remember)
[Nexus 7 (2013) Original Android Development] lollyjay:
Yes that's what I did. It works.
[Nexus 7 (2013) Original Android Development] nigelhealy:
No.

TWRP mounts the filesystem and copies the files. It doesn't do a block device image.

Watch twrp backup it is copying files, not copying just bytes.

I have backed up ext4 and restored to f2fs and it worked.

The only problem is if you copy an encrypted filesystem it copies something to do with unlocking over and doesn't fully work.
[Nexus 7 (2013) Original Android Development] sunilknj.273:
is overclocking on stock rom causes hard brick.......????
[Nexus 7 (2013) Original Android Development] Tmzdroid:
No
[Nexus 7 (2013) Original Android Development] quickdraw86:
No. Outside of preexisting hardware issues, you'd almost have to try to brick a nexus. At worst, extreme clock settings in either direction, or changes to voltages, will make your device randomly reboot, difficult to use, or unable to boot into system. All of those difficulties can be remedied by a quick trip to recovery...
[Nexus 7 (2013) Original Android Development] fuzzie:
I have ElemntalX and CM13 lastest nightly. Fastboot power on works great when usb is attached (or car is turned on). Wireless charging works when the battery isn't at 95% to turn on the screen, but when the battery is more full, it won't come on. So I either need to adjust the max charge to 94% or figure out how to get double tap to wake it from deep sleep. Any suggestions?

Thanks!

Fuzzie

UPDATE: I found a post referring to this, and tried this: svc power stayon true Stay tuned on whether it solves the problem!
[Nexus 7 (2013) Original Android Development] Philaphlous:
It works now! Downloaded in opera browser...
[Nexus 7 (2013) Original Android Development] flar2:
Is it chrome that gives the bad downloads?
[Nexus 7 (2013) Original Android Development] lpachuong:
think i am one of the unlucky people who JSS15Q didn't work :(
[Nexus 7 (2013) Original Android Development] celkin:
Really want to get this booted, looks AWESOME btw.

Question though, i have attempted install twice now. Both attempts were downloaded with opera and firefox (file size matched, so i dont think its a bad dl). But both boots resulted in a google lock screen hang, rebooted as the op says and sa!me thing. Just hangs on Google splash..

Thoughts?

Nice disclaimer btw! Cant ***** bout a bricked device after going through that! Lol
[Nexus 7 (2013) Original Android Development] flar2:
Once it boots it won't happen again. Try reinstalling.

If I can get get it to happen again I'll try to fix it tonight. It might just need caches wiped or something
[Nexus 7 (2013) Original Android Development] celkin:
Was actually just about to delete my post. Read back a few pages from he end. Sorry, on my first coffee. Usually don't flash anything this early, just got excited to see this kernel. :)

Will play around a bit n get er running, im sure.

Thanks!

**EDIT** third install with dalvic and cache wipe was the charm, although didnt do anything different? But regardless! Tap to wake is dope!
[Nexus 7 (2013) Original Android Development] djdarkknight96:
The latest update is too flawless...I kinda feel cheated now it has no bugs...bugs have protein and help the circle of life....Lmfao Awesome job on the update!

Sent from my Nexus 7 2013 using ClearJellyed Tapatalk 4
[Nexus 7 (2013) Original Android Development] y3mita:
Just flashed this on a latest AOSP ROM and so far so good, just random FCs on some apps (browser, opera, Facebook) unsure if kernel related? I UV 800 and everything else default.
[Nexus 7 (2013) Original Android Development] Kevin Goot:
Anyway to turn off fast boot?
[Nexus 7 (2013) Original Android Development] Habs69M:
had 2 power off (while in standby) with1.1, reflashed 1.0 but glitched at lockscreen (screen off when trying to unlock) then again 1.1, no power down for now, finger crossed :)

oh and i have selected double tap and magnetic on/off only
[Nexus 7 (2013) Original Android Development] tiny4579:
What do you mean? Fast boot is an HTC Sense thing. There is another fastboot and it's for sending commands in the bootloader mode.
[Nexus 7 (2013) Original Android Development] noneabove:
I know the unnoficial cm has fastboot (like HTC) in it, if that's what he's talking about then that's under performance in settings
[Nexus 7 (2013) Original Android Development] Tiffany84:
If you could add some kind of sound control I'd never see the need to flash anything else. Great work as always :)
[Nexus 7 (2013) Original Android Development] noneabove:
I'm having more touch screen issues than I was with 1.0.. I get random long holds, some dragging turns into a tap, touches showing up in other places, never had any issues on 1.0
[Nexus 7 (2013) Original Android Development] celkin:
Running perfect here, even been pushing the cpu's trying to make it studder. This things playing 720p mkv in vlc on 2 cores floating at about 40-55% over wifi.

This is on stock settings. Needless to say, I'm impressed!

**Edit** Actually, my N7 is currently out performing my S4 (stock/debloated), running the same file, the 2 running cores float 65-75%.
[Nexus 7 (2013) Original Android Development] Chadneu:
I never had the multitouch issues until this newest kernel.

I'm going back to 1.0.
[Nexus 7 (2013) Original Android Development] Toaster Strudels:
Works so well. :)
[Nexus 7 (2013) Original Android Development] xraytedjim:
This would make my day!

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] boykomac:
Same here!

---------- Post added at 10:41 PM ---------- Previous post was at 10:39 PM ----------

This is about multi touch issues - 1.1 seems to mess with my touchscreen, going back to 1.0
[Nexus 7 (2013) Original Android Development] NekroWolfen:
What "multi-touch issue" are you guys talking about?, I mean, exactly what happens? I'm trying to figure out if what happens to me while using photoshop it's the same. Although that is happening to me even before elementalx, so I doubt it has anything to do with it. Righ now I'm using bulletproof, no issue that I've know of.
[Nexus 7 (2013) Original Android Development] danieldawson:
Having a problem with EX Kernel Manager. Whenever I try to update, it appears to download the whole file, then it says, "Download failed". Happens every single time. I can only update ElementalX by going through recovery. Any ideas what the problem could be?
[Nexus 7 (2013) Original Android Development] flar2:
I have no idea why that would be. Did you give EXKM sdcard permissions?

You can always download from elementalx.org and flash manually.
[Nexus 7 (2013) Original Android Development] Woody:
I have seen this only on my N7. Express downloads just fine, but the full Aroma version does what you say. Gets almost all the way and then fails. Been like this for a few weeks (2-3 maybe), but then I just....

...do this if I need to.

Works perfectly fine on my N5 and N6.
[Nexus 7 (2013) Original Android Development] danieldawson:
Huh. I hadn't thought of trying that. It works. In fact, it seemed to be instant, i.e. didn't even download anything, or at least not much, as if it already had the file.

Yeah, I'm on a N7 (2013) as well. So, I guess it's something related to this device.

I know I can do it manually, and I've done it plenty of times. But that's less convenient, you know?

Anyway, thanks for ElementalX and EXKM. I love the USB fastcharge and wake/sleep gestures.
[Nexus 7 (2013) Original Android Development] flar2:
The file must be corrupt or something. Luckily the app does an md5sum check on downloads before it tries to flash it. I'll re-upload tonight.
[Nexus 7 (2013) Original Android Development] Tex99:
Last version works great thank you!!

Guys do you know what are the commands "echo / etc ....." to be inserted in the terminal emulator to change the RGB values? thank you (sorry for english)
[Nexus 7 (2013) Original Android Development] Glock3am:
Did you check the symbol on the far-right that enables it on boot? It's a circular arrow with a small line intersecting it at the top of the circle, reminiscent of a power symbol.

I had a similar issue when I first used the manager, I didn't know what they were for. The guide on the website cleared it all up though: http://elementalx.org/exkm-user-settings/
[Nexus 7 (2013) Original Android Development] fuzzie:
Great kernel!

I'm running 3.4 5.08 CM with Cyanogenmod 13 nightly (just scaled this back to 20160210 to troubleshoot).

I have an OTG cable and the tablet used to charge while audio or data was coming out of the OTG cable. I've tried wired and wireless charger. If I reboot, only the data comes out of the usb cable (can't charge wired or wirelessly), if I unplug the OTG cable, it will charge either wirelessly or wired if I plug in a wired power usb cable.

The kernel is set to use OTG+USB charging.

I've tried several OTG cables, same result.

Any suggestions?
[Nexus 7 (2013) Original Android Development] fuzzie:
OTG cable either runs audio and steering wheel controls or charges, but not both. I tried wireless too, but same result.

Switched to CM 12 instead if 13 nightlife, same result.

Anyone else experiencing that?
[Nexus 7 (2013) Original Android Development] devilnat:
[MENTION=4775959]nigelhealy[/MENTION] for your F2FS installation guide. Right now, I'm running Pure Nexus on F2FS no problem here.
[Nexus 7 (2013) Original Android Development] nigelhealy:
Did it do you any good?

Stock was fast enough for me, if it is any faster I can't tell. It was much more apparent on my Nexus 9.
[Nexus 7 (2013) Original Android Development] ABQNM:
[MENTION=4684315]flar2[/MENTION] did you remove KSM from 5.08-CM? I just upgraded from 5.07 and can't find it anymore in the ElementalX app. I find that KSM is a big help in devices with only 2GB of RAM. (Heck, it's a big help in my G3 with 3GB even.) I didn't see anything mentioned in the change log, so I'm wondering if it's a compatibility issue with the latest nightly of CM or if you removed it for a reason. Thanks!
[Nexus 7 (2013) Original Android Development] flar2:
I never added ksm. But I can add it to the next update.
[Nexus 7 (2013) Original Android Development] ABQNM:
Huh. I believe you, but that's odd. It was there yesterday when I had 5.07 installed because I adjusted the scan interval. Maybe it was just a residual setting that was somehow left over from the CM kernel (though your app was telling me how much RAM the merges were saving, so it was functional). Or probably more likely 5.07 never installed properly and was actually still the CM kernel entirely (though it was displaying 5.07 in the ElementalX app).

At any rate, if you could add it without too much trouble, I'd certainly appreciate it. Thanks again!
[Nexus 7 (2013) Original Android Development] homebrew01:
Can I install ElementalX on an "locked" device?

Hello,

in the title post I read, that I can install the kernel as well on a device with stock rom unrooted.

My questions is now, do I need to unlock the device first?

And second question, can I install it on my LTE device?

My N7 is on Android 6.0.1, Security Patch 1. Feb. 16, Kernel 3.4.0-g8ba2631, Build MMB29Q

thanks Werner
[Nexus 7 (2013) Original Android Development] flar2:
You can install in lye model and with stock ROM

You need to unlock the bootloader to install anything on a device.

Unlocking the bootloader will completely wipe everything, so backup any photos or files you want to keep

Other than that, you need to install TWRP recovery.

Root is not necessary, but without it, you can't change any kernel settings.
[Nexus 7 (2013) Original Android Development] homebrew01:
It worked, thanks a lot!
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

Minor changes for the March security update.

Add KSM, it is disabled by default. You can try it out with EX Kernel Manager.

I have removed the enforcing option from the installer. Selinux is enforcing by default, just as it was before. Removing this option will allow you to use setenforce again. There is no reason to run in permissive mode, but if you must, then use the permissive.zip found here: https://www.androidfilehost.com/?fid=23991606952602503

Download

ElementalX-N7-5.09

Changes:

-March security update

-remove enforcing option

-add KSM (disabled by default)
[Nexus 7 (2013) Original Android Development] mixy76:
thx man, this is the best kernel ever for my FLO
[Nexus 7 (2013) Original Android Development] devilnat:
I have noticed that when I use apps, it runs quite faster than ext4. And the other experience is I think battery runs out quickly comparing to ext4.
[Nexus 7 (2013) Original Android Development] nigelhealy:
F2FS enabled version of newest , if you open zip and look in boot/edit_ramdisk.sh you see the edit. Nothing else changed.

Update: I've now installed it on my N7 and working. Playing with KSM ;)
[Nexus 7 (2013) Original Android Development] sunilknj.273:
sir... i m just a beginner..... so i dont know lots about f2fs.... but i saw some videos about it and it seems that f2fs inhance the speed....... so please tell me process to install it.
[Nexus 7 (2013) Original Android Development] nigelhealy:
Flar's current kernel modified for f2fs one message above and guide. The guide uses the version of the kernel at the time, use the newer one now.

Perhaps I'll update my old post to newer version....

---------- Post added at 01:06 PM ---------- Previous post was at 12:49 PM ----------

I've been on the newest kernel with KSM enabled a few hours and using it generally normally, it is telling me that KSM is freeing up 123MB and terminal is showing me free RAM 907MB.

FWIW I have a Nexus 9 alongside running the identical applications and its showing 422MB free RAM with no KSM. Making me looking at KSM for my N9 now....
[Nexus 7 (2013) Original Android Development] flar2:
I put KSM in my N9 kernel a while ago
[Nexus 7 (2013) Original Android Development] sunilknj.273:
which rom support f2fs
[Nexus 7 (2013) Original Android Development] nigelhealy:
Stock doesn't. Odd as stock on N9 does. If you try it takes ages to boot and its just reformatted to ext4.

Cm13 does. Flar doesn't seem to have updated ElementX this time for CM. Go back a page or 3 to see an edit I did of the most recent cm kernel for f2fs.

Pure Nexus does. That's what I'm running.
[Nexus 7 (2013) Original Android Development] lightningzsoul:
I was able to get /data and /cache converted to EXT4 to F2FS on Stock 6.0.1 MMB29V [Nexus 7 2013]; I did all the steps on the guide although after wiping and convert it to F2FS I restored back up immediately and flashed the EX Kernel 5.09 F2FS.zip you attached and booted up and it worked :good:
[Nexus 7 (2013) Original Android Development] Viggen66:
I can't make DoubleTap2Wake to work with cm13, has anyone experienced the same?
[Nexus 7 (2013) Original Android Development] nigelhealy:
Good to know. Perhaps when I tried stock + elementalx I'd not yet realised I needed to edit the kernel to allow f2fs.
[Nexus 7 (2013) Original Android Development] Kmias:
Hello! What does KMS stands for? Or what does it does?
[Nexus 7 (2013) Original Android Development] marsaltito:
I bought EX Kernel Manager and setup in it . Before without app didnt work! :(
[Nexus 7 (2013) Original Android Development] lightningzsoul:
But I did notice some problems along the way, but this could be related to how recent F2FS was developed and it isn't as mature as EXT4 which is still widely used :)
[Nexus 7 (2013) Original Android Development] Viggen66:
In order to work you also need to install super su after that it works properly
[Nexus 7 (2013) Original Android Development] nigelhealy:
http://bfy.tw/4iQ5
[Nexus 7 (2013) Original Android Development] efan3719:
is that your way of saying you dont know what it stands for?
[Nexus 7 (2013) Original Android Development] nigelhealy:
I didn't know, then I searched, then I did know. It was the 3rd hit.
[Nexus 7 (2013) Original Android Development] Ritchiejoe:
Which version is compatible with Pure Nexus?
[Nexus 7 (2013) Original Android Development] quickdraw86:
The only 5.09 version, which is AOSP. It doesn't matter which version of PN either, both the CMTE and layers versions use the same kernel.
[Nexus 7 (2013) Original Android Development] flar2:
Update!!!

For Cyanogenmod and other CAF based ROMs only!!!

Minor changes for the March security update.

Add KSM, it is disabled by default. You can try it out with EX Kernel Manager.

I have removed the enforcing option from the installer. Selinux is enforcing by default, just as it was before. Removing this option will allow you to use setenforce again. There is no reason to run in permissive mode, but if you must, then use the permissive.zip found here: https://www.androidfilehost.com/?fid=23991606952602503

Download

ElementalX-N7-5.09-cm

Changes:

-March security update

-remove enforcing option

-add KSM (disabled by default)
[Nexus 7 (2013) Original Android Development] Axel85:
I updated the kernel but now I m in a bootloop

Cm13+5.09 updated after app notification

I tried to wipe system dalvik and cache and reinstall last working nightly + 5.08 but sadly nexus 7 bootloop
[Nexus 7 (2013) Original Android Development] flar2:
logs?

I can't test the cm version myself.
[Nexus 7 (2013) Original Android Development] Techamazon:
[MENTION=2563184]Axel85[/MENTION] Using DU here which is CM13 based if I'm not mistaken. CM based kernel posted recently does not work at all and the same goes for 5.08-cm. BUT, the AOSP-based one works flawlessly so keep that in mind. I have no info on upstream changes, but it looks like something was changed a while ago hence the incompatibility.

[MENTION=4684315]flar2[/MENTION] would logcat work if one is stuck on bootlogo? Just thinking I might help in any sorta way.
[Nexus 7 (2013) Original Android Development] quickdraw86:
DU rebased to AOSP some time ago, hence the AOSP EX kernel working on your installation.

You need to collect and submit a last last_kmesg to document a bootloop.
[Nexus 7 (2013) Original Android Development] quickdraw86:
I wouldn't worry about it. 5.09 CM working great on the latest CM nightly here. Thanks for an excellent update!
[Nexus 7 (2013) Original Android Development] EisDave:
USB DAC no stereo sound + OTG charge and reconnect problems

I got the newest build of the stock rom running with ElementalX-N7-5.09, but I got a few problems. I installed the Nexus 7 deb to in my car and use a USB DAC from Behringer (UAC-222). With our Galaxy Note 4 i get stereo sound with out problems, but using the Nexus 7 I only have mixed Channels. Can anybody help me with this issue, because I want better sound with the USB DAC and now I got a much worse sound? The sound works over bluetooth, build in speakers and headphone connector, but not over USB. I alread checked the audio_policy.conf, where USB has the same settings like bluetooth.

Second the OTG charge mode did not work after rebooting the Nexus 7, if it's pluged the whole time to the OTG charge cable (doesn't charge, until reconnection). This is a big problem for the fixed installation in my car, because it is not easy to dis- and reconnect the OTG cable. Also USB devices are not found, if the power of the car is shutted down and the USB devices turned off. When I start the car again the Nexus 7 doesn't search for USB devices, so they didn't work until I reconnet the Nexus.

I hope you can help me with my problems,

greetings from Germany.
[Nexus 7 (2013) Original Android Development] drlenny:
Running CRDroid, and it's running fine. Must be something else wrong with their setup, not your kernel.
[Nexus 7 (2013) Original Android Development] sunilknj.273:
can i increase system partition size because my device shows /system partition full.......... during download a plugin.... not during app installation.

i wanna use twrp recovery for increase size.
[Nexus 7 (2013) Original Android Development] Axel85:
The only last thing I can try before a wipe data is to change twrp recovery version. What version you have?

Other than that I suspect there are bad nand problems. I m not a noob, I had an hd2 and all nexus devices (missed nexus one) with cm since cm7
[Nexus 7 (2013) Original Android Development] flar2:
Were you using permissive mode before?

I removed that option and it has caused some people some problems. I'm just preparing people now for a future where selinux permissive is a thing of the past.
[Nexus 7 (2013) Original Android Development] Axel85:
No never used permissive mode, I will post you a log, when I have time. I have to read somewhere how to start a log from fastboot to catch the bootloop
[Nexus 7 (2013) Original Android Development] flar2:
After it bootloops, immediately go to recovery and do "adb shell cat /proc/last_kmsg > last_kmsg.txt"
[Nexus 7 (2013) Original Android Development] Axel85:
OK thank you ,I will do it and post here when I get home
[Nexus 7 (2013) Original Android Development] quickdraw86:
I just upgraded to TWRP 3.0 official. I installed ROM, gapps, and EX 5.09 CM From a full wipe, all in the same queue. If it were a recovery issue, there would likely be error output in the recovery log, I doubt that using TWRP 2.8.70 as opposed to 3.0 would be the source of the issue. I would try a clean flash of the ROM prior to installing the kernel, just my opinion.
[Nexus 7 (2013) Original Android Development] Axel85:
I only updated the kernel the last time... Elementalx app notified me an update and I chosed to update the cm kernel in express mode. I had cm13+5.08 clean flashed the 2 days before. I post the log in 20 minutes
[Nexus 7 (2013) Original Android Development] Axel85:
here is the log ,as you can see at the end I had to reboot because it got stuck at boot logo (sorry I said bootloop,but it s stuck at boot logo)
[Nexus 7 (2013) Original Android Development] flar2:
The log is full of selinux permission errors. I have no idea what they are from. Do a clean install.