yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] Khaon:
Oh my my like I post earlier, the issue of the two buttons was not related to the rom itself but simply the ramdisk.

I have just built and boot on cm with my own kernel repacked with cm12's ramdisk.

Here is the image

you can flash it with Warning: only for people having data formated with f2fs

fastboot flash boot boot.img

from bootloader.

--------------------------------------------------------------------------------

Will provide CM12 bionic libraries for stock users, will bring performance boost:good:

--------------------------------------------------------------------------------

Could anyone that has data f2fs and stock lollipop try booting with this image?

Just to know if CM ramdisk is compatible or not with stock one

you can do so(without having to flash the kernel) like this

fastboot boot boot.img
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=4577448]Khaon[/MENTION] I succeeded in booting lollipopalooza ROM on your cm boot.img from fastboot. No error messages but two very minor issues: 1) no su binary (not unexpected, so if I were to flash boot.img I would just flash supersu 2.27) and 2) tablet asked me to re-authenticate my computer's adb connection. Otherwise everything seems to work just fine!

I will now move to your cm12. Been so looking forward to it!
[Nexus 10 Original Android Development] Khaon:
Good to now, because the opposite was not working properly: booting with stock ramdisk on CM12 was resulting in having two buttons missing in the navigation bar :silly:.

There is on my mediafire a cm12 build that I have been using the whole day. However, I will now try compiling with others toolchains than google's. I have brunched one try with sabermod 4.8.4, it is being compiled. After I'll try also sm 4.9.x and linaro's.

Then, I will adjust compiling the flags, for example, the build compile with neon instead of neon-vfpv4.
[Nexus 10 Original Android Development] brees75:
Dude, you are awesome! !!!! Converted data to f2fs, flashed your rom with PA gapps, and the performance boost is insane. On f2fs copying files from my computer was so much faster i don't know why i took so long to convert. Anyway, now i am rooted, the rom is perfect, thank you very much!

---------- Post added at 12:40 PM ---------- Previous post was at 12:22 PM ----------

Getting an "unknown error on install -505" when I try to install Rom Toolbox Pro from Google. Anyone else use this? It's one of my must have apps so I'm kind of freaking out. Haven't had this problem yet even with lollipop. Could be the f2fs file system since it's a low level application. I could try side loading it but the error is happening when it's installing not downloading. Anyone have any ideas?
[Nexus 10 Original Android Development] brees75:
I fixed it by copying it to system/apps in recovery, definitely a f2fs issue because it cant see the data folder.
[Nexus 10 Original Android Development] necropuppy:
Just to report. I tried your CM12 11/23, with your latest kernel on f2fs (cache/data) and CM12 would not boot after 15 min. powered off and it went to upgrading, but then there were tons of FCs and couldn't access anything. I then tried to flash rascarlos lastest lollipop and that worked better, after playstore update of the apps, but root wouldnt work. read back in your thread and I see why.

Your kernel ext4 build was working awesome on Rascarlo's build, battery life and responsiveness was pretty awesome on some of the configurations with ktweaker that are going around . Thanks!!!

I'm going to try the CM12 as ext4, after.

The only thing that I'm using diff is TWRP official 2.8.2.0 , that has built in f2fs support it seems, which is pretty cool.
[Nexus 10 Original Android Development] b1g.p0ppa:
/cache as f2fs isn't currently supported. Just /data.

---------- Post added at 01:47 PM ---------- Previous post was at 01:44 PM ----------

I noticed back on KitKat that anything I pushed or created while in recovery mode was not available when booted to android. In recovery mode I change the uid/gid that own the file/directory to match those I am able to access when in android and that works.
[Nexus 10 Original Android Development] necropuppy:
This might be why I'm having problems... Prob should read back more thoroughly.
[Nexus 10 Original Android Development] audie2k3:
I'm thinking it's a Rom issue because I'm unable to install it on my LS980 CM12.
[Nexus 10 Original Android Development] Khaon:
The ROM or Lollipop might be the culprit, I have no idea, if anyone could tell us if this app was working on top of a f2fs data partition on KitKat.

------------------------------------------------

I am uploading a new CM12 build,

nothing changed but compilation flags:

neon-vfpv4 instead of neon for the whole build( fallback to -mfpu=neon for clang as it doesn't support neon-vpfv4)

pass -O3 flag to clang compiler

O2 for thumb c
[Nexus 10 Original Android Development] b1g.p0ppa:
I'm getting a "Unfortunately, System UI has stopped" error message on your new ROM that I cannot get past. ADB just says waiting for device. I downloaded twice and have 16c947186afef57cb2db3196c04233d3 for md5sum both times.

I'm going to try again without installing SuperSU 2.27 zip. Also, I was dirty flashing. When I wiped data it wouldn't proceed past boot animation. That's why I'm suspecting supersu as I've heard similar stories.

EDIT: It's still not working, but I think there's something going on with it understanding my f2fs /data. I was stupid and flashed khaon_kernel_manta_linux_mainline-11-16-2014_f2fs.zip as a matter of habit since I had it on my device (deleted it now). When I flash just your ROM and try to boot I get a "To start Android, enter your password" dialogue that I (with no real evidence) believe is just error handling assuming that since it cannot read /data then it must be encrypted.
[Nexus 10 Original Android Development] Khaon:
Hm weird, as usual before making a post I flash on my device, I sideload'ed the archive, then installed su 2.27, gapps, and my kernel, and everything poped up.

The "enter your password" window is met also when your device fails at mouting your /data partition

This time, however, I did not included my kernel inside the ROM, it is shipped with original CM's. I forgot to mention that. I guess that's why you are having this window
[Nexus 10 Original Android Development] b1g.p0ppa:
OK, restored boot from TWRP backup and new ROM is up and running! Thanks, Khaon.
[Nexus 10 Original Android Development] necropuppy:
I don't know what I'm doing wrong.

I cannot seem to use either of these kernels ext4/f2fs with either your CM12 builds nor rascarlos latest build. Just stuck booting. this is with your unofficial TWRP recovery freshly loaded after a fresh 5.0 re-image using the google binary images. I HAD it working on ext4 w/ rascarlos, but nothing no longer works. I been f***ing with it for 2 days now. I'm just giving up. I got your CM12 to boot w/ the stock kernel on ext4, no probs. as soon as I flash the f2fs and convert /data over to f2fs and reboot, nothing. I really love your kernels. I'm not sure what I'm doing wrong, but I'm just going to give 5.0 a chance to be released and then try again later. Thanks for all your development Khaon!!!
[Nexus 10 Original Android Development] b1g.p0ppa:
Make sure that your /cache is ext4 and not f2fs. I could have saved myself a lot of unnecessary troubleshooting if I had paid attention to that.

If you're game to give it another go, you could flash Khaon's latest 1125 cm12 ROM, then reboot to bootloader and "fastboot flash boot boot.img" the boot.img file he posted in post #308 in this thread from your PC. /data is my only f2fs partition and I am running 1125 no problem. The procedure:

Boot to TWRP

format /data as f2fs

format /cache as ext4

format /system as ext4

install cm12

install gapps

reboot to bootloader

(connected to PC,, run from same directory as boot.img is located) fastboot flash boot boot.img

back into recovery mode

flash supersu 2.27

profit

Barring unknown variables, I really think this procedure will work for you. I hope it does! Sorry in advance if it does not because formatting /data as f2fs will wipe out any TWRP backups you may have made. Also, as you probably know, everything on /sdcard will be wiped as well.
[Nexus 10 Original Android Development] Khaon:
I have uploaded two new flashable zip's for CM12. One is meant for set ups with full ext4 and the other f2fs only on /data.

Apparently, CM12 ram disk is compatible with stock roms, whereas the opposite is not the case. Users on stock rom please report any bugs if there are so.
[Nexus 10 Original Android Development] necropuppy:
This new kernel worked perfectly with your latest cm12 build!
[Nexus 10 Original Android Development] frontalot:
Anyone else having trouble with kernel settings, specifically CPU frequencies, sticking? I select a max CPU frequency of 1900 MHz, but it keeps switching back to 1700 MHz.
[Nexus 10 Original Android Development] tavocabe:
I was about to ask this exact question. Tried with two different tweaker apps with no luck.
[Nexus 10 Original Android Development] brees75:
I don't think sysfs is modifiable in the 2nd kernel build, can't get any init.d scripts to work either. Even after a clean flash, when i dirty flashed over the initial rom build wifi wouldn't connect so i had to start over.
[Nexus 10 Original Android Development] zerocool79346:
Anybody have multi user profiles working with this kernel? Trying to troubleshoot if it's this or Rastapop giving me issues.
[Nexus 10 Original Android Development] brees75:
Khaon

Turns out it is this rom that is preventing Rom Toolbox Pro from installing.

Also, the kernel breaks root on other roms. I can root no problem but once i install this kernel it says binary not installed, even after trying to reinstall the latest SuperSu.
[Nexus 10 Original Android Development] Khaon:
I guess you used su v2.35++?

If yes, then I suppose the issue you are talking about is due to recent ramdisk changes( switched from stock to CM12's). I assume if you flash a former kernel, for example this one : http://www.mediafire.com/download/q...rnel_manta_linux_mainline-11-16-2014_f2fs.zip, root won't be broken?
[Nexus 10 Original Android Development] b1g.p0ppa:
I'm not having any issues with root. Yesterday I (dirty) re-flashed the 11-25 ROM, the 11-26 kernel, gapps and supersu 2.36 in that order all at once in TWRP.

On a side note, holy cow what a diff your compilation flags make! I tried out the other cm12 ROM and could really notice the difference. No disrespect to that ROM or Dev intended, he's been supplying awesome nightlies for the manta for years and I very much appreciate his work.

Downloading the 11-30 ROM now.

Edit: 11-30 running flawlessly. Flashed kernel, gapps and supersu as described above and no issues with root. Noticed that neither AdAway nor Viper audio needed re-applied so I guess you're not wiping /system out. This must be why brees75's having trouble. I did not try manually wiping /system but I bet he does.
[Nexus 10 Original Android Development] Khaon:
Indeed, the updater-script just flash the system image, it does not wipe out system's content before doing so.

BTW, Chainfire's SU is no longer mandatory on CM12 to bring root rights, CM12's root built-in features is working again.

-----------------------------------------------------------------------------------------------------------------------

Went a step further in the compilation's optimizations levels.

The while diff between cm-12 build and mine can be seen there

Using more optimizations flags doesn't result necessary into more performance. 25/11 build was enabling O2 and neon-vfpv4 for the whole build and O3 for clang. So any feedbacks are welcome.

The rom is shipped with my kernel for a full ext4 setup
[Nexus 10 Original Android Development] brees75:
Initially I tried 2.36, but I also tried 2.27 and that didn't work either.

With regards to ROM Toolbox I think the issue is CM in general and not your build, someone on a N4 had the same problem.

---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------

I'm not having any issues with root on this ROM either, i literally meant OTHER roms like lollipalooza. Since they are stock it's most likely due to CM base.
[Nexus 10 Original Android Development] b1g.p0ppa:
I'm experiencing Chrome crashing on some web pages on the 11-30 ROM. Example: http://www.express.co.uk/news/uk/542351/Charles-Bronson-challenges-Mickey-Rourke-to-boxing-bout . Sometimes I can open that page and sit there for a few seconds and some times it crashes right away. Sorry I didn't think to get a logcat but hopefully it will be really be easy to recreate. Had the same experience with Chrome Beta. Flashed back to 11-25 ROM and am not experiencing this issue. Reminiscent of early days of SaberMod ROM when AOSP browser kept crashing. Not sure if they ever figured it out but I think I remember them blaming some compile flag.

Edit: Setup when I was experiencing crashes was 11-30 ROM, 11-26 f2fs kernel and /data formatted as f2fs. Using bfq and interactive with all their defaults. No OC/UV.

Another weird thing was the game Monument Valley was 'glitching'. It didn't ever crash, but it definitely didn't behave like it does on the 11-25 ROM. Objects didn't interact the same after running it a couple of minutes. Sorry for the vague description but I wanted to communicate that it wasn't just Chrome misbehaving.
[Nexus 10 Original Android Development] Khaon:
Yep indeed, I have also FC only but with Chrome, I mainly use my tablet for browsing so I am on it. I think the reason of this is some strict aliasing breaks. Either fall back to 25/11 or use another browser that is not crashing, such firefox.
[Nexus 10 Original Android Development] Khaon:
Uploading new build without aliasing optimization, chrome doesn't seem to crash anymore, at least it doesn't now on the link your shared.
[Nexus 10 Original Android Development] frontalot:
Can you look into the issue of kernel settings not sticking?

Thanks.
[Nexus 10 Original Android Development] necropuppy:
having issues with chrome FCing on the new build as well as the previous. Love the build otherwise. Just gonna use a diff browser for the time being.
[Nexus 10 Original Android Development] joeski27:
I flashed the new 12/1 rom with the 11/26 f2fs kernel (and the 11/09 regular gapps) but got stuck in bootloop world. Flashed back to the previous version of the rom with the same kernel and no problems. Not sure what that could be about...?
[Nexus 10 Original Android Development] Khaon:
Hello, sorry for that, seems because of cm12 in early stages, the ramdisk tends to change, so using a rom with an older ramdisk/kernel may results in those issues.

I am working on another solution, it is based on evolved anykernel 2.0:

it will dump your current rom's ramdisk, check with blkid your partitions's filesystems, patch your future fstab accordingfly to your fs's, repack the kernel image with the new patched ramdisk, and flash that image. The kernel would become back universal that way.
[Nexus 10 Original Android Development] Lokian69:
Chrome is crashing on my nexus 4 as well, I think it is reasonanble to assume it's a bug of Chrome itself on lollipop.
[Nexus 10 Original Android Development] Khaon:
Seems I could get rid off the chrome FCs. It was induced by one flag.

Chrome didn't crash for one hour on the build I am testing. Well I might be wrong we will see.

The one I am using right now was compiled with Google toolchain, will try with linaro and release the stablest.

EDIT: haven't got no FCs so I assuming it is fixed. Next new builds are on their way.
[Nexus 10 Original Android Development] Khaon:
Latest build I uploaded on media fire doesn't seem to have any longer FCs. The culprits were some flags that are enabled by O3. I couldn't trace,neither logact or kernel debug messages, where the error came from to force it to be let's say o2 or Os. Anyway the whole build is at least O2 and O3 for clang. It was compiled with linaro 4.8. None of 4.9 seem to work.

Comes with default cm kernel and target f2fs for data. Will provide full change log later and latest kernels

Sent from my nexus 10.
[Nexus 10 Original Android Development] ericp2:
Hi khaon just installed cm12 plus latest kernel. It works very well but iam still getting fc's on chrome. It's unclear what you have updated because all files have the same name and dates... Could you be more specific as to what you have uploaded? Gapps kernel or cm12?

---------- Post added at 03:10 PM ---------- Previous post was at 02:55 PM ----------

Additional note: i ununstalled chrome completely and reinstalled from playstore. It seems to work ok now!
[Nexus 10 Original Android Development] brees75:
Can this be used with ext4 data partition? I'd like to give this another shot since your kernel will only work properly with cm12.
[Nexus 10 Original Android Development] Khaon:
Yeap, chrome doesn't crash anymore !

Here is the full changelog of today builds!

Rom:

Compiled with linaro 4.8.4-3011 (android build)

07/12 nightly

Kernel:

Restarted from scratch, here it was it includes at the moment.

Base: Google's android 3.4 lollipop 5.0.1

compiled with linaro gcc 4.7.4-0602014 full O3 neon-vfpv4

governors:intelliactive,intellimm,ktoonservative,interactive,conservative,performance

io scheduler: noop, deadline, row, zen, bfq, cfq, fiops,sio

ksm

OC/UC: from 100Mhz to 2100GHz

CPU voltage control

lz4 kernel support

f2fs (07/12)

Kernel zip flashable package:

It uses now @osm0sis 's anykernel solution with an extra add: patching the fstab depending on your partitions schema. Soit should increase the kernel's compatibility with other roms. You just have to make that before flashing, the current kernel is working.(explanations on how it works)
[Nexus 10 Original Android Development] necropuppy:
Did a full wipe and flashed the latest cm12 build and kernel, Bluetooth will not enable. Says Bluetooth share has stopped working.
[Nexus 10 Original Android Development] brGabriel:
After going back and forth between other 5.0 ROMs (and back to 4.4.4), I've finally found the lollipop experience I've been looking for. Your latest CM12 ROM + f2fs kernel are fantastic. Keep up the great work. :good:
[Nexus 10 Original Android Development] Khaon:
Bluetooth issues are rom side issue. I will take a look at this for the next build.
[Nexus 10 Original Android Development] frontalot:
07/12 kernel can't decrypt / mount F2FS data on stock Lollipop.

EDIT: And it seems to have completely hosed my previously working system with the 16/11 kernel. I get the error "Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. Any way to fix this or do I need to wipe and reinstall everything?
[Nexus 10 Original Android Development] Khaon:
Can you send an output of adb shell mount please
[Nexus 10 Original Android Development] frontalot:
adb shell mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

tmpfs on /tmp type tmpfs (rw,relatime)

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

/dev/block/mmcblk0p7 on /cache type ext4 (rw,relatime,data=ordered)

/dev/block/dm-0 on /data type f2fs (rw,relatime,background_gc=on,user_xattr,active_logs=6)

/dev/block/dm-0 on /sdcard type f2fs (rw,relatime,background_gc=on,user_xattr,active_logs=6)

----

I have /data formatted F2FS and everything ext4. It was working fine with the 16-11 kernel, but 07-12 hosed it.

I can still see my data in recovery so I tried reflashing the 16-11 kernel, but that didn't work.
[Nexus 10 Original Android Development] CazeW:
Your problem sounds a bit like a problem mentioned in the Lollipopalooza thread. The problem they had was that they couldn't access the internal SD in Lollipop but could access it in recovery. They fixed it with running:

su
restorecon -FR /data/media/0

Could be worth a shot. If you can't access any files on your /data partition, you could try running that for the whole /data.
[Nexus 10 Original Android Development] Khaon:
off topic: Can anyone send me an invitation for an Oneplus one?
[Nexus 10 Original Android Development] frontalot:
restorecon: SELinux is disabled

I'm guessing there's something wrong with the fstab on the latest kernel.
[Nexus 10 Original Android Development] Khaon:
If you have already went back to a former kernel. You can try fastboot boot boot.img to prevent having to flash again.

adb shell cat fstab.manta

adb shell cat fstab.org

Would print your current tab
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=4577448]Khaon[/MENTION], this is from right after installing 1207 ROM and then anykernel2 while still in TWRP. My /data is formatted f2fs. I too am greeted with the screen asking for the encryption password which I have come to believe means /data is not mounted and android is assuming that is because it is encrypted. Adb shell does not work at that point so I cannot run those commands as I can't boot into android. Flashing your 11-26-2014_F2FS kernel allows me to boot properly.

EDIT: attached recovery.log (renamed to .txt so upload would work) to this post.

$ adb shell cat fstab.manta

# Android fstab file.

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

# The filesystem that contains the filesystem checker binary (typically /system) cannot

# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/platform/dw_mmc.0/by-name/system /system ext4 ro wait

/dev/block/platform/dw_mmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check

/dev/block/platform/dw_mmc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/dw_mmc.0/by-name/metadata

/dev/block/platform/dw_mmc.0/by-name/efs /factory ext4 noatime,nosuid,nodev,ro wait

/dev/block/platform/dw_mmc.0/by-name/boot /boot emmc defaults defaults

/dev/block/platform/dw_mmc.0/by-name/recovery /recovery emmc defaults defaults

/dev/block/platform/dw_mmc.0/by-name/misc /misc emmc defaults defaults

/dev/block/mmcblk0boot0 /bootloader emmc defaults defaults

/devices/platform/s5p-ehci auto auto defaults voldmanaged=usbdisk:auto

[dcoffman@dcoffman-archtop ~]$ adb shell cat fstab.org

cat: can't open 'fstab.org': No such file or directory

$
[Nexus 10 Original Android Development] Khaon:
The recovery uses its own kernel and thus ramdisk.

I will upload latest build and I ll paste one procedure to help me reproduce your bug.

On my device installing the rom and anykernel do work after a full clean installation.
[Nexus 10 Original Android Development] Khaon:
uploading new builds online:

Rom:

10/12 nightly

AdAway added to system apps

BBS v2.0.0.0RC2 added to system apps (thx to [MENTION=1330150]chamonix[/MENTION])

Experimental: some sub parts of the build were compiled with O3 instead of O2. Chrome doesn't crash at all.

I have uplodaed three archives:

One is flashing a ramdisk for a full ext4 device,another one for data partition and the last one is anykernel2.

Anykernel dump your current rom's ramdisk and patches it. My current setup is f2fs on /data and that's all, however I am booting.

So to users who gonna try again anykernel2, please do the following thing if you want to report a non working anykernel2:

from recovery

and AFTER having flashed anykernel2.zip

, you can dump the new boot image it produced(it is locacted into the temporary folder), do the following:

adb pull /tmp/anykernel/boot-new.img OUTPUT_PATH

It will dump your new boot.img to the output dir you specify.

Just provide this new boot.img so by unpacking it I can see if the /data mount point options are corrects.
[Nexus 10 Original Android Development] b1g.p0ppa:
Dirty flashed 12-10 kernel over the top of 12-07 ROM and it is booting, not prompting for decrypt password. My /data is f2fs and I am not using encryption.

Edit: Waited 10 minutes at boot animation and it never booted up. Adb logcat says waiting for device. Attaching /tmp/recovery.log. There are some not found errors running the script.