yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] zaclimon:
Yeah because HellsDoctor is using the anykernel method which in theory leaves your ramdisk *intact* while it's only the zImage (kernel binary) that has changed. It means that you only need to have f2fs support in the kernel binary to have your device running correctly. However franco's method is to compile a kernel + ramdisk which overwrites all of your kernel. The reason franco did this was probably because he has some special ramdisk.

I could use anykernel but it could remove some of franco features which I don't want to happen. The other solution would be to modify franco's ramdisk to support f2fs. (since the binary kernel already support) However as I said, if I succeed, I would have to support 4 builds which I don't feel like to do.

I have a 3rd solution for people using f2fs for the moment, I could use anykernel but it would remove potential franco's improvements to the ramdisk. What do you think about it? (even then I would still need 2 kernels because of AOSP/CM)

EDIT: I've found a compromise but that may take some time.
[Nexus 4 Android Development] gharrrrrr:
Ahh that's right. Forgot Franco uses his own ramdisk. Look forward to what's this compromise may be. Thanks for your time.
[Nexus 4 Android Development] zaclimon:
I just seen that this guy can put the same franco ramdisk using anykernel here:

http://xdaforums.com/nexus-4/general/f2fs-roms-kernels-23-4-2014-t2728201/page48

I may try to do something with this no? :p Btw what are you running?
[Nexus 4 Android Development] Maibol:
did you keep graphite technology ?
[Nexus 4 Android Development] zaclimon:
Yes graphite is still present in this release.
[Nexus 4 Android Development] gharrrrrr:
I'm running all F2FS with AOSPAL (PA SaberDroid) ROM and, funny enough, this guys f2fs Franco kernel. But I've been a long time fan of this kernel and would love to use it again.
[Nexus 4 Android Development] zaclimon:
Hmm alright then, I'll try to get something tonight for you.

Envoyé de mon Nexus 4 en utilisant Tapatalk

EDIT: Here I attached an AOSP version of the SM kernel, please report back if it works.

EDIT2: Not good anymore.
[Nexus 4 Android Development] Maibol:
f2fs is working great here ;)
[Nexus 4 Android Development] keyra74:
i'm losing root on cm with 208
[Nexus 4 Android Development] gharrrrrr:
Well, it booted up just fine. But didn't have WiFi. Did a dirty flash of rom, just to be safe, booted and WiFi worked. Reflashed this test build and after boot no WiFi. Reflashed Franco kernel was using from that f2fs thread and wifi back again.
[Nexus 4 Android Development] slipknot31:
is not my case, flash SuperSU
[Nexus 4 Android Development] zaclimon:
Damn I forgot the wifi for the kernel him I'll repush the kernel later today.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] zaclimon:
[MENTION=4270551]gharrrrrr[/MENTION] Can you try to see if this zip works. :)

EDIT: Not good anymore.
[Nexus 4 Android Development] gharrrrrr:
Still no WiFi.
[Nexus 4 Android Development] jkyoho:
Looking for the new release link ;)
[Nexus 4 Android Development] zaclimon:
Yeah true I forgot again that the system is mounted as f2fs. -.-

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] desiromeo719:
Zaclimon would it be possible for you to add dt2w feature to this kernel. I've only heard good things from this version made by mckael. http://xdaforums.com/showthread.php?p=51892830

Franco fears of people complaining about problems..but we won't complain :)
[Nexus 4 Android Development] zaclimon:
My purpose of doing this kernel is that I will keep franco and xstacy objectives. I could try to add it but if there's more issues than any real improvements, I will remove it. (I don't really like d2tw or s2w myself)

Also [MENTION=4270551]gharrrrrr[/MENTION] and [MENTION=4201935]jkyoho[/MENTION] this zip should be the good one.
[Nexus 4 Android Development] gharrrrrr:
Working perfect! Appreciate the time and effort you put into this.
[Nexus 4 Android Development] jkyoho:
wifi works now. but reflasing supersu doesn't not get back "root".
[Nexus 4 Android Development] zaclimon:
Ok This time should be the last one. Sorry that I have to make so many zips to get it working. This one should fix root.
[Nexus 4 Android Development] jkyoho:
franco.Kernel-nightly-r208-F2FS-autoV2.zip doesn't help getting back root access either:crying:
[Nexus 4 Android Development] zaclimon:
Hmm, can I see all the contents of your /sbin folder?
[Nexus 4 Android Development] jkyoho:
ok, trying to copy the sbin from recovery
[Nexus 4 Android Development] zaclimon:
That's not necessary, you could just have shown me the screen shot of it from an app like root Explorer. (because the contents of a recovery /sbin may be different from the "regular" /sbin.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] jkyoho:
dumped sbin from recovery

View attachment sbin.7z
[Nexus 4 Android Development] jkyoho:
reversing back r207 root access back
[Nexus 4 Android Development] zaclimon:
I'm wondering how you could get r207 if you had f2fs? (unless you were with the regular f2fs franco)

Here's a third try. (Hope this one is the good one)
[Nexus 4 Android Development] jkyoho:
ohh, I know what the problem is now. I am not f2fs but ex4*
[Nexus 4 Android Development] zaclimon:
Ahhh, in this case, this one should be for you:

http://xdaforums.com/showpost.php?p=52900171&postcount=399

Nonetheless I'm surprised it was working on ext4. It means that the zip somewhere verifies first if the system is ext4 or f2fs prior to flashing the kernel. I could use this model for further releases. I'll speak with those scripts authors to know if I can use them.

Thanks for your testing. :good:
[Nexus 4 Android Development] gharrrrrr:
No issues with root for me. But I'm using SuperSU.
[Nexus 4 Android Development] desiromeo719:
Ok np. I'm glad your continuing his work. I haven't tried it myself, but have heard it being stable and working great. Thanks for listening.
[Nexus 4 Android Development] gharrrrrr:
I can not begin to thank you enough for this. With AOSPAL SaberDroid, this kernel, and F2FS, this phone is flying. Thanks for the continued support and updates.
[Nexus 4 Android Development] GruZone:
I'm on crDroid (CM) not on f2fs and i lose root. What could be the cause?
[Nexus 4 Android Development] zaclimon:
I don't specifically know the issue about it yet (trying various combinaisons) though a quick workaround would be to flash SuperSU and to disable "Respect CM Root Settings"

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] GruZone:
After unchecking this in supersu reflash your kernel again?
[Nexus 4 Android Development] zaclimon:
That's not mandatory to reflash the kernel after.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] GruZone:
Fixed the issue.
[Nexus 4 Android Development] jkyoho:
I switch to all f2fs partition now. This R208 kernel works great. No issue on supersu. No need for v2 v3 reversion I think. Thanks for [MENTION=4217103]zaclimon[/MENTION] .
[Nexus 4 Android Development] Maibol:
[MENTION=4217103]zaclimon[/MENTION] i hope you make a 209 version :)
[Nexus 4 Android Development] zaclimon:
r209 will most probably come tomorrow, I'll try to work on it today. :)
[Nexus 4 Android Development] zaclimon:
Big update!!

Geez sorry guys, I need to make better timings but I was finalizing some quirks I had with the kernel. So without any other due here it is. :p

r209:

- Based upon r209 test from Franco

- Fully compatible with Android 4.4.3

- Linux 3.4.92

- Reverted the custom prima drivers (to keep compatibility and also because the Wifi drivers has been updated with 4.4.3)

- Compiled with my own build of the SM toolchain (With updated stuff)

- Added DT2W (Thanks [MENTION=4464223]McKael[/MENTION])

- Now supports both Ext4 and F2FS (Thanks to [MENTION=2002216]jolinnard[/MENTION])

Download:

AOSP: http://d-h.st/D51

CM: http://d-h.st/4nV

I used McKael's DT2W following [MENTION=4293648]desiromeo719[/MENTION] advice. This implementation seems cleaner in my opinion and better to use.

Here's McKael's explanation on how to use it:

http://lilotux.net/~mikael/pub/android/kernel/N4/README_dt2w.txt

And here's an example of a d2tw.conf file:

http://lilotux.net/~mikael/pub/android/kernel/N4/dt2w.conf

You can also use trickster to enable/disable it.

Enjoy!! :)
[Nexus 4 Android Development] desiromeo719:
Thank you so much! This is the best kernel ever!
[Nexus 4 Android Development] TheDarkDefender:
hi, thanks for this. few questions:

is this of the anykernel format?

do you a have link for your source? checked the one in your xda profile. I'd like to check the d2w commits, found this

https://github.com/zaclimon/mako-linaro/commit/34e685827719832f86c705b88d3b9bcfee537d8e

Is that a squashed commit of all of mckaels work?
[Nexus 4 Android Development] zaclimon:
Yes the kernel now uses the anykernel format as opposed of Franco's boot.img because of the use of the Ext4/F2FS partitions. The source for anykernel is here.

As for my kernel source, it is indeed the link you've linked below. I didn't change the history of each of the commit, just make a merge and each individual commits should be on their respective dates. It's basically a squashed commit looool XD. Though here's McKael commits so you can see what's all about:

https://github.com/McKael/FrancoKernel-mako/commits/dt2w

Nothing was added/changed since the merge. (from my side)
[Nexus 4 Android Development] jkyoho:
I lost wifi (cant open wifi) on r209-sm. It was working fine on r208 with PA4.4rc1.

I am on f2fs partition

------stuff on my phone--------

PA 4.4rc1 (4.4.3)

Baseband:hybrid 102/27

kernel: r208-sm-f2fs-auto
[Nexus 4 Android Development] zaclimon:
Yep, knew it would happen someday, somewhere... I kept stock drivers for compatibility as they were updated and thus doesn't have much issues now. As you flashed r208 before, your wifi drivers aren't correct and you need to put stock back on.

The solution I would say is either find the stock 4.4.3 drivers somewhere or, dirty flash PA on top to regain the wifi working on r209.
[Nexus 4 Android Development] jkyoho:
I alway do kernel cleaner script before I flash new kernel. So, it should not be r208 left before I flash r209.

Anyway, I will try dirty flash first.

---------------just did dirty flash------------

It works now. Thanks [MENTION=4217103]zaclimon[/MENTION] for new kernel.
[Nexus 4 Android Development] zaclimon:
Alright! :) I'm pretty sure it'll be fine after.
[Nexus 4 Android Development] desiromeo719:
So this is what I notice of the wifi drivers. On stock, my 5ghz link rate is never more then 72 mbps. And speed tests I only get 10 mbps down on a 50 mbps connection. On 2.4 ghz I get full 50 mbps down. With prima drivers, on 5ghz wifi I get full link speed of 150 mbps and full 50 mbps down. Always had these issues with stock drivers idk why. Anybody else?
[Nexus 4 Android Development] zaclimon:
Probably the custom prima drivers removes the limit given by Google concerning the range/speed and/or there's more optimizations going on knowing it's from CAF.

That would be my 2 cents but maybe the others have something else.

If you guys are happier with the caf drivers, I'll reinstate them without issue.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] philosophics:
Fine by me. :)

Update: I seem to have a much warmer device than before. All settings remain the same. It could also have something to do with paranoid saberdroid. Not really sure.
[Nexus 4 Android Development] desiromeo719:
So I realized that my phone( or maybe an android issue) doesnt like the higher channels my router was using on the 5ghz band. I dropped the channel from 153 to 40 and now my phone gets full speeds on 5ghz band too. So looks like theres no need for prima drivers.

Only thing is the link rate never goes to 150mbps on 5ghz like it does with the prima drivers. The speeds are the same tho.
[Nexus 4 Android Development] WiwiPouPou:
[MENTION=4888112]xcstacy[/MENTION] Amazing kernel performance and battery life ! Wow.

I know you want to stay close to Fransisco idea but...

Dare I ask for porting exponential brightness from semaphore kernel (also implemented in hellsdoctor) ?

That mode is really comfortable at night by allowing a really lower brightness state, way better than any screen dimmer app... + it could help more to save some battery when reading.

Also, touchwake (only activated for a time set after screen goes off by itself), stratosk implementation too, could be a real plus !

Again thanks for your work ! =]

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] zaclimon:
Ohh that's interesting indeed, well it's not necessary to put the prima drivers anymore unless somebody else had issue with the stock drivers.

For the moment, xcstacy can't build any kernel so I'm building them instead. As I'm only a builder for newer franco release, I won't get really outside of xcstacy's territory regarding what he intends to do with his kernel. As for touch2wake, I've already implemented McKael's way of doing it which is a bit more better in my case because you can actually configure it in a .conf file which will be inside you /sdcard or /storage/emulated/0.

EDIT: Looks like it was an asked feature from xcstacy a while back. (if I see from the poll) I'll try to see what I can get from it. Thanks for the suggestion. :)

EDIT2: Looks like stratosk hasn't implemented a brightness drivers saying that the light sensor is userspace based and not kernel based unless I'm missing something somewhere.

http://xdaforums.com/showpost.php?p=47392814&postcount=4968
[Nexus 4 Android Development] WiwiPouPou:
Thanks to you then =], sorry I've read to fast...

about exponential brightness, which is not a driver for auto brightness, you can find it in the changelog the 10/03/2013 :

"lm3530_br_mode: sets the linear (default 1) or exponential (0) brightness mapping mode.

The sysfs path is /sys/devices/i2c-0/0-0038/

Please note that the exponential brightness mode uses a very low LCD brightness on a low external light. You may need to increase the min_br for better results"

i try to find the commit but I'm not really use to github, semaphore and hellsdoctor kernels always use it.

As written before, it's a mode that you can enable or disable with UKM or Semaphore app, or in my case with a command line via tasker : "echo 0 > /sys/devices/i2c-0/0-0038/lm3530_br_mode"

Too bad i can't find the commit.... :/

Thanks anyway for your time, that's very kind !

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] zaclimon:
With 4.4.4 and Android L release, I thought I'd give a little update for our unlucky N4's ;)

r209.2

- Based on recent franco patches for mako (including futex fixes)

- Linux 3.4.94

- Optimized even more the kernel (Now using -Ofast and added some new graphite flags)

- Compiled with an up-to-date SM4.9 toolchain (built myself)

- Added the exponential brightness driver from stratosk (Merci [MENTION=3020594]WiwiPouPou[/MENTION])

As you already know, it's compatible with Ext4 and F2FS...

Download:

AOSP: http://goo.gl/wnze20

CM: http://goo.gl/Sd84Vj

Enjoy!! :)
[Nexus 4 Android Development] desiromeo719:
Thanks zaclimon! This is great ☺
[Nexus 4 Android Development] keyra74:
thx man :)

is it possible to add the touch control module...;)

i get : error insmod failed on touch control app
[Nexus 4 Android Development] zaclimon:
I won't add it because I think it's plenty to have dt2w. Let's keep things simple.
[Nexus 4 Android Development] keyra74:
i knew you would say that but d2w is a pain for me since it wakes up my phone in most of my shorts, s2w doesn't :/

also opera max says vpn not supported, did u remove tun.ko?
[Nexus 4 Android Development] WiwiPouPou:
Wow that's amazing !!! Thank you !! :))
[Nexus 4 Android Development] zaclimon:
The tun support is inside the kernel and there's no module for it. Though it is strange that it isn't working.
[Nexus 4 Android Development] jeckooo:
hi, i installed r209.2 sabermod on cm last nightly and it works but all the times that i try to chose interactive my phone reboots, it stays on performance
[Nexus 4 Android Development] Jeckoo:
Reinstalled the rom and then flashed the kernel, now it works, thanks

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Android Development] Tanmaynarang:
Are the sources for r209.2 uploaded on GitHub? If so, what branch? Thanks! :D
[Nexus 4 Android Development] zaclimon:
Here's the source :

https://github.com/zaclimon/mako-linaro

AOSP branch : kitkat-2014

CM branch : kitkat-2014-cm
[Nexus 4 Android Development] Tanmaynarang:
Awesome, thanks! I'm gonna be including this in my ROM, so it'll automatically add your commits when available.
[Nexus 4 Android Development] zaclimon:
Alright, just be sure to add the Franco stuff inside the ramdisk so everything will be working fine. :p
[Nexus 4 Android Development] Tanmaynarang:
I'm using CyanogenMod as a base so I'm using the integrated kernel building, it automatically builds the ROM alongside the kernel and packages them together.
[Nexus 4 Android Development] zaclimon:
Even though you build using CM, you would need to add the Franco ramdisk changes inside the init.mako.rc and add the fkbootscript.sh with the rest of the stuff so all the stuff should work.
[Nexus 4 Android Development] Tanmaynarang:
Oh, alright. I'll take a look at the scripts.
[Nexus 4 Android Development] gharrrrrr:
I just flashed the AOSP version but it says kernel is 3.4.92 and build date June 12. Tried twice even.
[Nexus 4 Android Development] slipknot31:
all ok with OSE unoficial
[Nexus 4 Android Development] zaclimon:
Have you downloaded the zip on a mobile? If so, it looks like mediafire have some issues with downloading on mobile and can't download the whole file.

Try to download it on a computer, then sideload it.
[Nexus 4 Android Development] jkyoho:
Can I dirty flash from r209 or I need reflash system before flashing r209.2
[Nexus 4 Android Development] zaclimon:
You can dirty flash from r209 if you want to use r209.2.
[Nexus 4 Android Development] zaclimon:
Alright so here's an update again!

r209f (final)

Upstream franco.kernel commits (mainly hotplug cleanup)

Linux 3.4.96

Download:

AOSP: http://d-h.st/yah

CM: http://d-h.st/3RO

It's not that much of an update because I find that the kernel is pretty much stable and good as it is right now. For the moment, I'll concentrate myself on releasing SM builds of Franco for my flo. (Nexus 7 2013)

Enjoy!! :)
[Nexus 4 Android Development] keyra74:
and for mine so :p
[Nexus 4 Android Development] dfkt_:
Does this kernel have CIFS enabled?

That's the only issue I have with the original Franco Kernel, not being able to mount my network shares.
[Nexus 4 Android Development] ferrocene:
FYI this kernel works great with L!
[Nexus 4 Android Development] TheDarkDefender:
Is this of the any kernel format?

Using the L port, which has a lot of ramdisk hacks, so flashing a complete boot img would break it
[Nexus 4 Android Development] manulemaboul:
Flashed latest ZIP on L, it just works.

Found no issue with it, doesn't seem tout break anything.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] TheDarkDefender:
Does FKU work fine for configuring? Or do you use trickster?
[Nexus 4 Android Development] manulemaboul:
Fku FC once the first time I opened it, works fine since.
[Nexus 4 Android Development] zaclimon:
It uses indeed the anykernel format for easier use between f2fs and ext4. I'm happy to see that it is working with the L preview. :p
[Nexus 4 Android Development] TheDarkDefender:
Lol. Thanks man. Awaiting a similar anykernel build for L preview on my flo ;)
[Nexus 4 Android Development] zaclimon:
Well while I'm working on it, do you have any feature request for it? Because as it is, it will mainly be a r17 with optimizations. I'm not really feature hungry for my flo.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] loop4444:
doesent work at all for me. and i have paid version aswell

asks for root but it cant launch
[Nexus 4 Android Development] manulemaboul:
Are you on the L preview port beta 2 ?
[Nexus 4 Android Development] TheDarkDefender:
Neither am I. But the d2w, s2w features from elementalx would be a good addition. There are multiple patches for it. github.com/flar2/flo .
[Nexus 4 Android Development] ihendraX:
I quoted you to get your attention.

You sad that this kernel works on "L" but it does not for me...Both AOSP and CM versions. :rolleyes:

Any ideas?
[Nexus 4 Android Development] manulemaboul:
No idea, the AOSP version should work. Have you flashed it at the same time as the L port zip ?

First boot takes ages, more than 10min.
[Nexus 4 Android Development] ihendraX:
Later, much later...needed this for Touch Control. I tried both versions of Siber Mode, Helscore and Faux b40 (latest) and no result. At the end I instaled older Faux b37 and loaded touch module not for that kernel but for Semaphore and now it works:eek::)
[Nexus 4 Android Development] zaclimon:
That's weird. I flashed the L port this morning and tried the kernel to see if it works and it did worked. :confused:
[Nexus 4 Android Development] ihendraX:
Problem was that I flashed older version but now with latest version r209 I have problem with WiFi, It's not working and can't load Touch Control modules. After a long night of working I went back to kitkat...

Thanks for kernel but I will try L again in few days ;)
[Nexus 4 Android Development] zaclimon:
Yeah well I don't think I added the modules compatibility because I think dt2w is enough as it is. Also for the kernel version, there was some custom wifi drivers we were using. As of r208, we're using the stock drivers which is why you can see that the wifi isn't working.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] vampire36:
Hi awesome kernel...can you possibly look at this...

https://github.com/McKael/FrancoKernel-mako/commits/dt2w

Works very well...

Highly configurable...http://lilotux.net/~mikael/pub/android/kernel/N4/
[Nexus 4 Android Development] TheDarkDefender:
I think he already has added them.
[Nexus 4 Android Development] zaclimon:
It's basically this one I've added into the kernel. Sorry for the long reply hehe :p , I didn't saw it in my notifications.
[Nexus 4 Android Development] slipknot31:
this very good kernel. thanks to the dev that You work in the
[Nexus 4 Android Development] deedeeceleb:
Any chance you could provide us a r210 kernel? Really appreciate your work!
[Nexus 4 Android Development] zaclimon:
Sorry for the late reply, Franco didn't really added anything from r209f. (looks like either I've updated my commits to be synced with him or he didn't pushed his stuff yet)

Also is there any features do you guys want or you find that the kernel is enough as it is? :) (No new governors/io scheds..)
[Nexus 4 Android Development] illanxr:
I personally belive that Matrix v14.0 frequencies work better for both battery life and performance (192, 288, 540, 702, 1026, 1188, 1350 and 1512 MHz). I have been comparing these two kernels and it seems to have less battery drain with no performance nor smoothness cost (at least in my fast binned chip). For everything else, this kernel is amazing :)
[Nexus 4 Android Development] WiwiPouPou:
I haven't the same experience, that kernel is the best battery-wise, by far !

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

Adding touch to wake as helldoctor if possible ? Thanks a lot for your amazing work !
[Nexus 4 Android Development] zaclimon:
The frequencies looks fine so far for my standpoint but I can consider it if it does indeed increase the battery life of your device. :)

I already have the dt2w from McKael, no need for further touch wake inputs. :p
[Nexus 4 Android Development] WiwiPouPou:
Touch to wake is very different, it stays ON only few seconds after screen goes off by timer, then it's disabled, so no battery drain after the few seconds. It's an entire different philosophy ! Even the iPhones have it ^^

But that's fine as it is, that kernel is the best one !