yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] Khaon:
Hello.

Thx for the report. Should not have been the case. I am using ext4 on system. I will check that later or tomorrow.

Envoyé de mon MI 2S en utilisant Tapatalk
[Nexus 10 Original Android Development] Khaon:
Hm no idea how this happend :D but there was a missing flag in the fstab for the f2fs system partition, I guess it was the source of the error.

New nightly beeing build, I will format to f2fs and see;

EDIT:

new build online: nightly 27/10 shipped with my kernel. Doesn't need to convert any updater-script. Just install and enjoy.

f2fs on /system isn't broken anymore
[Nexus 10 Original Android Development] mrdunlop:
Im confused, so other roms are still broken? I cant get my rom (Slimrom) to boot. Converted to f2fs and nexus will not pass boot logo
[Nexus 10 Original Android Development] brees75:
Do you need the modified recovery to use this rom even though all partitions are ext4?
[Nexus 10 Original Android Development] Khaon:
Nope! You do what ever you want. The modified recovery I released is just supporting mounting f2fs partitions.

Default one does already support mounting ext4 so you can go ahead. Furthermore my rom and kernel will detect your partitions's fs so you have nothing particulary to do.
[Nexus 10 Original Android Development] brees75:
On the last 3 builds that has not been the case using ext4. 10/20 build was actually the worst, just bootlooped. Before that it would at least boot but after 1 reboot it bootlooped. It detects f2fs even though all my partitions are ext4.
[Nexus 10 Original Android Development] Khaon:
So it is formating to f2fs your system partition?
[Nexus 10 Original Android Development] Khaon:
I f you can we c an meet on ts/skype.

Otherwise may you provide my

adb shell mount
[Nexus 10 Original Android Development] brees75:
I could try again but I went back to slim.

I am using the official twrp, all partitions are the stock ext4. The rom is just not detecting my configuration, it thinks I have f2fs when I don't.
[Nexus 10 Original Android Development] Khaon:
Hello didn't had time to write complete change log but new rom online !

Envoyé de mon MI 2S en utilisant Tapatalk
[Nexus 10 Original Android Development] Khaon:
change log

Tell me what you think about intelliactive and the setting have I set up, if you do and want to modify the tunnables,

watch out the kernel tweaker

you are using, some doesn't reproduce good two phase freq. Latest trickster mod supports intelliactive.

Here is how i set up intelliactive:

On load greater the 99%, or touch by the user, it goes for 2 cycles (so 40 ms by default) to 1,1 GHz then it falls back to 600 MHz.

If load exceeds 95 % and current freq is 1.3 GHz then the governors scales the freq to 1,7 GHz.

This is configured for browsing, navigating, etc, but might be not the best for gaming

Fell free to set intelliactive and not touching the tunnables and report its efficiency
[Nexus 10 Original Android Development] frontalot:
Latest kernel still can't be rooted with SuperSU on stock rom...

:(
[Nexus 10 Original Android Development] ericp2:
Wrong post

---------- Post added at 10:01 AM ---------- Previous post was at 09:56 AM ----------

It's working fine. I'm using intelliactive with default settings, and tablet feels quite responsive (i am not a gamer)
[Nexus 10 Original Android Development] Khaon:
Hello, did you try with towelroot? And with wug's toolkit? What is the super user binary you are using?
[Nexus 10 Original Android Development] Khaon:
For me too, I could notice frequencies on average being lower than with interactive. I do like the two phase concept, it allows you to have a nice bump at first.

I was always annoying by interactive or so, because while just browsing or reading stuff, due to the touch boost driver it would bonce non stop to high freq(1GHz by default)

When I take a look at frequencies history ( betterbatterystats, no frills, w/e) it seems to behave very nicely.

What is your kernel tweaker you are using? Some does not recognize two phase freq syntax : freq1,freq2. I have sent a mail to trickerstermod team, they have added the support since lastest version.

new build and kernel on their way
[Nexus 10 Original Android Development] Khaon:
New builts online:

ROM:

compiled with extra flag -ftree-vectorize

Kernel:

Merge with ours strategy remote-tracking branch 'cm/cm-11.0' into khaon

Merge with ours strategy remote-tracking branch 'common/android-3.10' into khaon

ARM: 8165/1: alignment: don't break misaligned NEON load/store

f2fs: updated to upstream branch

added fastboot mount option to f2fs partitions

This commit add a new mount option : fastboot
[Nexus 10 Original Android Development] Khaon:
lollipop build compatible

Hello, little update here:

changelog:

merge exynos/android-exynos-manta-3.4-lollipop-release branch

f2fs updated to upstream revision

F2FS is working, or at least on data and cache partitions

Root informations

After having installed the kernel you need to use Chainfire's autoroot.
[Nexus 10 Original Android Development] tavocabe:
[MENTION=4577448]Khaon[/MENTION] Hi, was trying to format data and cache to f2fs using the official twrp (2.8.1), do you know if this is still possible? F2fs option is missing.
[Nexus 10 Original Android Development] Khaon:
I don't think twrp comes with f2fs out of the box. you can however instead of installing my recoveries, that are older version, simply boot on one of those

fastboot boot image_recovery.img

will pop you into the recovery, there you can format your partitions.

However, official twrp doesn't mount f2fs partitions, which is not recquired to install on a ext4 system anyway.
[Nexus 10 Original Android Development] Khaon:
double post.
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=4577448]Khaon[/MENTION] this is not working for me. I used your TWRP 2.8.0.0 unofficial to change fs for /cache and /data to f2fs. I then rebooted to bootloader (from twrp without booting into android) and ran the CFAR tool. I am not seeing any notification or navigation bars at all.
[Nexus 10 Original Android Development] Khaon:
do you mean your tablet never executes the boot process?
[Nexus 10 Original Android Development] tavocabe:
It works. I followed [MENTION=4577448]Khaon[/MENTION] suggestion... booted up his custom recovery, format to f2fs, rebooted to official recovery, flashed kernel (had to use OTG because pc wasn't recognizing my device and I didn't know if booting was possible using f2fs/stock kernel), reboot, profit. This was done from a fresh installed factory image.

EDIT: I forgot the root process, it was the first thing I did after the factory image finished installed, however, when I finished the converting procces to f2fs, the supersu app couldn't find the su binary so I ran CFAR again and everything is fine. Now I'm all set and ready to go.
[Nexus 10 Original Android Development] b1g.p0ppa:
OK. It worked for me. I re-flashed the factory flash-all to bring it all back to stock. Then fastboot flashed your 11-15 recovery. Booted to your recovery, formatted /data and /cache to f2fs and installed your kernel. Booted back to fastboot and applied the CFAR tool. Booted up and it all looks good! Thanks, [MENTION=4577448]Khaon[/MENTION]! I am completely amazed at how fast you got this out!

EDIT: Supersu can't find the binary. Re-applying CFAR results in a msg saying 'failure or patch not needed''. Going to re-run from the beginning, this time flash Khaon's recovery, format to f2fs, back to bootloader to flash stock recovery, back to bootloader to apply CFAR.
[Nexus 10 Original Android Development] Khaon:
You can use my twrp 2.8.0.0, at least I used that and no official builds. Flash lastest kernel on mediafire and then reboot to bootloader and use CFAR should do.
[Nexus 10 Original Android Development] b1g.p0ppa:
Figured it out. CFAR copies boot.img to /cache but can't if it's formatted f2fs! Switched /cache back to ext4 and all is working!
[Nexus 10 Original Android Development] CazeW:
So the correct order would then be, flash recovery, flash kernel, CFAR and convert. Good to know. :)

Haven't yet converted back to f2fs after upgrading to lollipop but I'm not entirely sure if it's still "necessary" for the write speed. Entirely possible that Androbench is lying about the results but I'm now getting over 200MB/s read speeds and almost 10MB/s random write speeds (on KK I got around 1MB/s which is why I converted to f2fs).
[Nexus 10 Original Android Development] b1g.p0ppa:
So I've gotten myself into a situation that I simply cannot run either the 11-14 or the 11-15 kernel. :crying: I've tried repeatedly the following:

Wipe and flash factory 5.0 with flash-all.sh

Boot up and skip signing in (for expediency's sake)

Power off

Boot into bootloader and apply CFAR

Boot up and verify that root works

Power off

Boot into bootloader and fastboot flash recovery openrecovery-twrp-2.8.1.0-manta.img (sometimes I have just fastboot booted from the .img on my pc--same results)

Tell bootloader to boot into recovery. TWRP boots

adb push the kernel to /sdcard

Install the zip from TWRP

Reboot System​

The tablet will just sit there and never get past the flying color globes. Adb logcat just says waiting for device. Where am I going wrong?

Edit: I have tried all variations of USB and pogo charger attached or not.
[Nexus 10 Original Android Development] brees75:
Thanks for saving me a late night, i was just about to flash the kernel. ;)
[Nexus 10 Original Android Development] CazeW:
Based on Khaons post in the CF-Auto-Root thread, the code used to check whether the partition is ext4 or f2fs to mount properly is not working in lollipop. So for now it looks like the current kernels can only be used with /data and /cache formatted to f2fs.

[MENTION=4577448]Khaon[/MENTION] can correct me if I'm wrong. :)
[Nexus 10 Original Android Development] b1g.p0ppa:
Ah, that would explain it then. Since CFAR doesn't work with /cache as f2fs I was going to just try to get everything working on ext4 first. But CFAR reboots as its last step when /cache is still ext4. Thanks. I was going crazy!
[Nexus 10 Original Android Development] Khaon:
Indeed the script that is mounting partition for now can not be executed. I noticed that a bit late sorry :p

So until we find a way out I will release two build : one full ext4 support and another with only /data on f2fs.

I'll drop cache for the following reason: like stated chainfire the cache partition is barely used so having f2fs doesn't give any advantages but complications.

Chainfire stated he has been busy on the doc for dev about 5.0 root, when he will release that I will integrate in the kernel itself.

[MENTION=3721939]b1g.p0ppa[/MENTION]

CFAR is working like this : it boots into a simple recovery, mount cache data system, flash in the system supersu v2.20, then dump to cache the kernel, patch the kernel with some binary of chainfire and then reboot eventually.

So the correct steps are

1. flash your system

2. flash kernel

3. boot from bootloader into CFAR

4. boot into your os

I am building daily cm12 and I keep switching back from cm12 to stock and in return.

Never had problem with rooting the device. CM12 is not that stable at the moment, better stick with stock. When it runs better I will make it available.
[Nexus 10 Original Android Development] brees75:
Does the lollipop kernel have all the features that 4.4 had? i.e governors, schedulers?

Also does anyone know the path location for the lowmemorykiller? It is not in sys/modules/lowmemorykiller
[Nexus 10 Original Android Development] Khaon:
Two new builds online:

one for systems running ext4 on all partitions

the other mount data with f2fs

Just tried the f2fs version it's booting :eek:
[Nexus 10 Original Android Development] Khaon:
lowmemorykiller has been removed from default kernel configuration. No ideas why, on some other devices it is still enabled.

About features, it is the same kernel than before but has been merged with lollipop branch among others
[Nexus 10 Original Android Development] frontalot:
I was able to upgrade to Lollipop and flash your latest kernel. I still can't root on stock using SuperSU 2.19, though.
[Nexus 10 Original Android Development] brees75:
Cool, thanks for responding.

Did it break root or did you root afterwards? I am rooted already but i don't want to loose it obviously.
[Nexus 10 Original Android Development] Khaon:
Only CFAR shipped with 2.20 is working so far :)

You can grab it there go to to the bottom, and search for mantaray 5.0. Instructions are written just above the table
[Nexus 10 Original Android Development] b1g.p0ppa:
Thanks [MENTION=4577448]Khaon[/MENTION]. Installed your 11-16 f2fs kernel with only /data formatted as f2fs and everything is correct! Rooted and all.

---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------

Root is broken after installing kernel, but that is easily remedied by re-applying the CFAR tool while in bootloader. As I've learned the hard way, make sure that /cache is formatted ext4! Doesn't seem like that would be a problem for you now. Haven't tested the all ext4 kernel but I can say that the f2fs kernel is working as advertised.
[Nexus 10 Original Android Development] b1g.p0ppa:
Yep. 7 TCP congestion control options, 6 I/O schedulers (including your beloved sio;)), and 6 CPU governors.
[Nexus 10 Original Android Development] brees75:
Lol, well it bootlooped after flashing kernel and then rooting again. Going to try one more time because i may have caused it from trying to get busybox installed earlier.
[Nexus 10 Original Android Development] frontalot:
Nope, CF Auto-Root applies successfully but still no root. When launching SuperSU:

"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

I think something is broken when it comes to rooting with your kernel on stock. Can you try it yourself just to make sure I'm not crazy?
[Nexus 10 Original Android Development] Khaon:
Did you sort it out? what are the fs' of your partitions?

Nope, root is working. However, I came across what you are describing while keeping testing my kernels. Try this: uninstall supersu, boot to recovery and wipe your caches, boot to bootloader and run CFAR
[Nexus 10 Original Android Development] brees75:
Ext4 kernel with ext4 on all partitions running the ota factory image. Then i decided to switch to craigacgomez rom and root was still broken after flashing kernel but i haven't tried applying root again yet because it was late. When i get home from work tonight i will try rooting again.
[Nexus 10 Original Android Development] Khaon:
Try this: uninstall supersu, boot to recovery and wipe your caches, boot to bootloader and run CFAR.

Like I said, during my testing(I have flahed over dozens of times since lollipop was released), I came accross that with or without stock kernel.
[Nexus 10 Original Android Development] frontalot:
Root works after changing /cache to ext4. No removal or reinstallation of SuperSU required.
[Nexus 10 Original Android Development] Izeltokatl:
So I'm going for a swim with this kernel, but before I do, does anyone have the stock 5.0 kernel that can be flashed?
[Nexus 10 Original Android Development] Khaon:
Decompress the lollipop stock archive that is located with the scripts it contains original boot image

Just to remind anyone that missed this information:

Because of the new android's security restrictions introduced into android 5.0, the bash script that was executed during boot process to patch the fstab accordingly to your partitions setup is broken

, thus so far there are two kernel version : one that target full ext4 and the other full ext4 but f2fs for /data. There is already two workarounds to fix this, should be integrated next releases.

I could add a third one supporting cache for example, but it would bring more incompatibility issues also there is no tradeoff having f2fs on this partition.

To those who were running f2fs on system partition is not being supported at the moment.

CFAR's kernel doesn't have f2fs drivers so it won't be able to mount the system partition

. Thus you wouldn't be able to root your device

When chainfire releases the doc to have kernel patch built-in, we can have root on a system partition having f2fs. I am looking toward that to try the new fastboot mount opt

However, won't probably will be worth switch from ext4 to f2fs on that partition

http://git.kernel.org/cgit/linux/ke...4&id=d5053a34a9cc797b9d5d77574354b5555848c43c
[Nexus 10 Original Android Development] frontalot:
Thanks for the clarification.

Which kernel tweaker app are you using? Can you recommend one that allows modification of thermal throttling?
[Nexus 10 Original Android Development] brees75:
I am having a hell of a time trying to get this to work with Lollipalooza ROM and Root. Is there something with Android 5 that doesn't like us removing unneeded system apps? I can't install busybox because there is no space in the system partition so I removed some "unnecessary" apps but once I re-root it bootloops!
[Nexus 10 Original Android Development] Khaon:
Atm Aero . Hm I don't think you can edit thermal if not it requires only a sys interface with the concerned variables.

I have removed chrome,youtube.I needed space for viper4android, betterbatterystats, busybox,etc.

Does it bootloop or stays in the boot seq forever?

About root, you can try using supersu 2.23 instead of 2.20-the one shipped with auto-root. Must flash su.zip after autorooting.

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

Little update:

Some of you wanted an up to date twrp, here it is!
[Nexus 10 Original Android Development] brees75:
Yeah 2.23 was what I tried last night. You got me, technically it stays on the boot animation forever, but for all intents and purposes it's a bootloop since there is no difference in the end result of having to start over. Lollipolooza has busybox but it is missing some essential modules that I need otherwise I would be all set. I will give Rastapop a shot when I get home. After seeing how much awesomeness this kernel added the short time I used it I can't really live without this either. :D
[Nexus 10 Original Android Development] b1g.p0ppa:
That's exactly what mine did when I had /cache as ext4 on the previous kernel that expected it to be f2fs. Sure you got the ext4 version of the kernel?

[MENTION=4577448]Khaon[/MENTION] thanks for the updated twrp! Fastboot flashed it and is working well.
[Nexus 10 Original Android Development] Khaon:
Hm I hope you fix everything when back home, is it me or you keep having problems with rooting? I remember I had to try many times at some point before root success and sometimes worked first time. Today, for example, I rooted cm12 first attempt, but it has been not aways the case.

I have set in attachmnet a dump of my boot image, it expects data to be f2fs

However does anyone know or heard something about this bug? There is only back touch screen button. So no home and other app touch button. Was busy so far to check on that, too bad could have released cm12, its runs nice for the short tests I had but not having those two buttons is meh. Also the system image is less than 400 mb and most prebuilts are better. It includes out of the box bb for example.
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=4725047]brees75[/MENTION], did you know you still have to apply the CFAR? Just flashing supersu.zip is still not enough.

[MENTION=4577448]Khaon[/MENTION], I have not heard of that bug. I did get no buttons at the bottom once after a factory flash but I re-flashed and that went away.

Edit: [MENTION=4725047]brees75[/MENTION] , I really think applying CFAR is your answer. Now, my /data is f2fs so I'm not technically using the same kernel as you, but I just got Lollipopalooza all the way rooted and all the way booted. My procedure:

Boot to [MENTION=4577448]Khaon[/MENTION]'s twrp 2.8.1.0

Wipe data/cache/dalvik

Install lollipopalooza ROM, [MENTION=2322613]craigacgomez[/MENTION]'s gapps, [MENTION=4577448]Khaon[/MENTION]'s kernel

Reboot to bootloader

Apply CFAR

Boot up and wait

Reboot to recovery

Install supersu 2.23

Reboot
[Nexus 10 Original Android Development] Khaon:
Dunno why you want thermalt control :D but it is implemented for next release !

All credits goes to @ktoonsez

Or if you are too impatient and doesn't like to wait CFAR rebooting, you can just boot again to bootloader to go to recovery and directecly flash su 2.23 and reboot.

Anyway, on next releases, the kernel will always be pre auto-root kernel side pre patched. No more CFAR :D
[Nexus 10 Original Android Development] frontalot:
I can't seem to get CF.lumen to work with your kernel - http://xdaforums.com/showpost.php?p=56850394&postcount=408

Can you tell if this is something coming from CF.lumen, SuperSU, or your kernel?
[Nexus 10 Original Android Development] Khaon:
No idea never used.

Well, you could try with stock kernel rooted

you can flash with

fastboot flash boot boot.img

then i have set above in one or two post behind in attachment an image of the same partition set up than yours.
[Nexus 10 Original Android Development] brees75:
I held off on this kernel and flashed ROM, rooted, busyboxed, and everything was great. Rebooted a few times no problems. Flashed this kernel and it hung on boot, waited 30 minutes and gave up. I think I will wait for next version. Re downloaded ext4 kernel several times just to make sure.

Tried on OTA factory, Lollapalooza, and rastapop.
[Nexus 10 Original Android Development] b1g.p0ppa:
Bummer to hear. f2fs /data is working out great for me on lollipopalooza. Tested rastapop today and all was fine as well.
[Nexus 10 Original Android Development] brees75:
Anyone else have init.d running with this kernel? The problems don't seem to start until init.d is enabled.

---------- Post added at 12:47 PM ---------- Previous post was at 11:51 AM ----------

I also switched to this twrp and thinking about converting system to f2fs since everyone has had good luck with that kernel. How do i run the script to convert the rom i want to use? I could not find that info in the op
[Nexus 10 Original Android Development] b1g.p0ppa:
I thought SuperSU enables init.d? I have an init.d folder I did not put there and daemonsu processes in my ps.

The ROM conversion is only necessary if you want /system as f2fs. I think everybody agrees that there's not really any benefit to /system being f2fs because a) the lollipop version of [MENTION=4577448]Khaon[/MENTION]'s kernel does not yet support it and b) ext4 read perf is actually faster than f2fs. So /data is currently the only partition that is expected to be f2fs and you don't have to modify ROM zips for that.
[Nexus 10 Original Android Development] Khaon:
Did you migrate from ext4 to f2fs? Well if you want to keep current rom you can just format your data ! Warning: you will loose as swell internal storage so make a backup of important files

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

I strongly suggest anyone to take a look time o time to chainfire's blog/google+. I just tried with a non patched kernel SuperSU v2.27 beta and root does work.

Keep in mind Android 5.0 brought a lot of new security policies, so it will take a bit of time to make everything stable and working.

The doc hasn't been released yet, looking forward to it, as patching fstab is broken for now.
[Nexus 10 Original Android Development] brees75:
Little closer to perfection! With CM 12 nightly from makelegs it has built in root that works, but when i flashed this kernel i lost the home and recents buttons in the nav bar, and the lockscreen disappeared. But everything else still works!! If you could drop a CM 12 with his base and kernel included that would be amazing!
[Nexus 10 Original Android Development] Khaon:
Then it is ramdisk related, I am building cm12 atm, working on that.