yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] franciscofranco:
Sigh... ****ing custom roms.
[Nexus 5 Original Android Development] Balino:
Cataclysm ftw [emoji4]

With torch bug fixed in your kernel I can finally go back to cataclysm! Thank you.

It seems to work pretty good, I'm trying to stress the flash and camera and all seems good
[Nexus 5 Original Android Development] lynnux:
My upgrade this morning had a small hiccup, too. Did it automatically through fku, it rebooted, everything seemed fine at first, LMT pie control was working (meaning I had root), but asking for accessibility, which seemed strange. Then all of a sudden LMT stopped working and I didn't have root any more. Confirmed this through Root Checker and Tibu. Reflashed su2.66 and everything was fine. Maybe if I'd waited longer root would have returned?

This was on stock 6.01 that I'd flashed from factory images a few days ago, rooted with 2.66, then flashed r78.

This is my first experience with your kernel, thanks, it's great.
[Nexus 5 Original Android Development] Semtronix:
Alright this is a new one for me. Just auto flashed r79 and went to boot recovery to flash SuperSU, but TWRP isn't there anymore. I don't even have a recovery anymore. Very confused. Anyone experience anything like this?
[Nexus 5 Original Android Development] fatspirit:
See installation instructions in the OP, especially pos. #2.
[Nexus 5 Original Android Development] diddly3000:
Could anyone recommend which supersu to flash with latest cataclysm to install this kernel? All this system and systemless crap is a pain in the ass lol. Cheers ☺
[Nexus 5 Original Android Development] fatspirit:
Unrelated to the kernel. You must enter recovery right after you've flashed it, otherwise stock one will be restored.
[Nexus 5 Original Android Development] Semtronix:
That's what I did though. It's how I've done all the latest releases. Auto-flash kernel, quick reboot to recovery. It's not a huge deal. Just never seen it before.
[Nexus 5 Original Android Development] holigan360:
bootloops in Chroma!...
[Nexus 5 Original Android Development] lynnux:
Thanks. :o I knew that at one time, forgot about it.
[Nexus 5 Original Android Development] fatspirit:
Is it pre-rooted?
[Nexus 5 Original Android Development] holigan360:
yes SuperSU 2.66
[Nexus 5 Original Android Development] paaaulo:
No, Chroma 10.12 is 2.52. Flash UnSU, then FK and 2.66 after that.
[Nexus 5 Original Android Development] holigan360:
Well, where I can find the Unsu file?
[Nexus 5 Original Android Development] Semtronix:
http://xdaforums.com/showpost.php?p=63615067
[Nexus 5 Original Android Development] GamaX320:
first thanks for your reply, for the osmOsis build how the procedure rom> gapps > osmOsis build france? Do I still need to unsu and flash supersu 2.62?
[Nexus 5 Original Android Development] coffeecore:
People, is reading that hard?
[Nexus 5 Original Android Development] franciscofranco:
Yes. After more than 2 years since this thread is open it gets kinda hard to read :cool:
[Nexus 5 Original Android Development] cheeze.keyk:
i got bootlooped also in Chroma. I already tried unsu.zip, flash FK and flash 2.66 but still bootlooped. :confused:

did you manage to install it?
[Nexus 5 Original Android Development] osm0sis:
Read the OP, then flash my AK2 zip.
[Nexus 5 Original Android Development] 777.300:
Strange, working fine on my N5 with Chroma.

Flashed Chroma, flashed Unsu, flashed FK and than flashed SuperSU 2.66 and rebooted.

Did you try to switch Kernels?

When switching kernel it is necessary to first flash your ROM again to get rid of your old kernel.

Sent from my Nexus 7
[Nexus 5 Original Android Development] cheeze.keyk:
I already got it working on my device. i flashed the AK2. :good:
[Nexus 5 Original Android Development] myvijay:
I have been without root or custom kernels since 6.0 , finally decided to go back to FK. Just wanted to know what should be done each time google issues the security update. Is it enough if I just flash the system image. I seem to remember there were couple of files that were modified in the system image for this kernel. Is this still true ? If so should I flash to stock , update and then flash FK and then SU every month to get the security updates. I did go through the OP and searched a bit on this thread but I couldn't find any answers.
[Nexus 5 Original Android Development] franciscofranco:
What I always do is (considering I have 0 changes on /system):

1 - Open SuperSu, scroll down and do "Full unroot"

2 - Say "Continue"

3 - Say "No"

4 - Let it boot back up

5 - Reboot to bootloader (adb reboot bootloader)

6 - Flash back stock boot.img

7 - Boot back to system and install the OTA through Android System Update

7a - If you have the OTA.zip just boot to recovery directly from the bootloader and sideload it there

This takes less than 5 minutes and it's very straightforward. I just did it on my N6P and N5X.
[Nexus 5 Original Android Development] franciscofranco:
FKUpdater 14.0.3 is out.
[Nexus 5 Original Android Development] osm0sis:
Please check out the issues in the N7 '13 thread.
[Nexus 5 Original Android Development] franciscofranco:
Didn't know there were issues. I'll check it.
[Nexus 5 Original Android Development] peecs121:
Running great along with Cata. Having zero issues. Best kernel for our N5. Thanks!!!
[Nexus 5 Original Android Development] Gallardo994:
Sadly latest FKU still doesn't apply custom per-app profiles properly. Setting 300-300mhz with powersave governor still causes CPU freqs to jump.
[Nexus 5 Original Android Development] phantom146:
It does apply that the problem is the workload. Setting it to 300-300 will certainly destroy your cpu and even syncing requires more than that frequency. Fku forces your cpu to get a maximum of 300mhz but if the workload exists by a certain threshold, instead of staying to 300 and make your phone bootup or worse, hang like theres no tomorrow.. Itll go up for a certain grace period to accompany workload..

And why the heck would you want a 300-300 freq gov :/
[Nexus 5 Original Android Development] Gallardo994:
Some applications like book readers don't require any performance and I don't mind laggy scrolling as long as it saves battery. That's why I said per-app profiles behave strange when they are custom.
[Nexus 5 Original Android Development] luckana:
This kernel is the sh*t, real talk. Had never made it to 50% with 2h30min of SOT before. I am impressed
[Nexus 5 Original Android Development] phantom146:
They are not :3

Have you ever tried more than 10 kernels?

I did.. And have you asked to yourself why do they have a sync_frequency or an optimal_freq? Or even an input_boost and all of those are set to either 1190mhz to 1267mhz?

Ever wondered about it?

This is easy :3, its because after thousands times of testing, they found out that those frequency are the best balance between battery and performance. If for example, you have underclocked to 652mhz with all four cores online, you might notice that its pretty good on battery consumption the problem if its not laggy is its not completing tasks behind your back. As per reading, underclocking to a certain point that people "think" they are saving battery isnt true. Though it may help power consumption, the r/w speed slows down and the tasks that you arent aware of(syncing,alarms,wakelocks,doze etc) takes 30% more time to finish which in turn is both inefficient plus drains more battery because of the time frame.

Try to read a lot of guides. I know for a fact because i spent 12 hrs a day reading all i can in xda, linux docs, androidpolice and many more. Knowledge is power :)

If you dont like the frequency ramping up too often then increase the input load and disable input boost :) thats it

Cheers!
[Nexus 5 Original Android Development] Arstoien:
You are correct, if we're talking about general usage. He was talking specifically about per-app profiles (different governor and cpu settings for different active apps).
[Nexus 5 Original Android Development] phantom146:
The problem for him was his per-app not sticking. It does stick to me but too much underclocking will destroy your phone 300-300 is too much, and fku releases that maximum freq if the workload is too heavy thats why the normal logic would be "why isn't it sticking?" :p
[Nexus 5 Original Android Development] osm0sis:
If I were to guess I'd say it's cpu-boost keeping the profiles from working correctly; it seems to mess with the display of the interactive max/min as well.
[Nexus 5 Original Android Development] phantom146:
Its the input_boost who has the touch frequency up and also cpu boost.. Turn those 2 off he might get the result he wants ;)

But still not recommended lol
[Nexus 5 Original Android Development] oifi:
how to set boost freq for just two cores? afaik it's not possible with the fku app
[Nexus 5 Original Android Development] phantom146:
Its not possible bec. Franc removed hotplugging so it'll avoid creating headers for on/off cores which saves more batt
[Nexus 5 Original Android Development] franciscofranco:
It's currently not possible through FKUpdater, only through scripts. I have been thinking about adding granular input_boot_freq control since the Kernel driver allows it.
[Nexus 5 Original Android Development] Arathon:
[MENTION=3292224]franciscofranco[/MENTION] Does your kernel include/use Faux Sound? Because I wanted to use a sound mod and its developer said that your kernel using Faux may create issues. Sorry for asking but until now the search option isn't working.
[Nexus 5 Original Android Development] widofmaker:
[MENTION=3292224]franciscofranco[/MENTION] selecting ondemand governor causes system to crash and reboot. All other governors work with no problem.
[Nexus 5 Original Android Development] franciscofranco:
No.

Ok. I'll reproduce and fix it. I wouldn't use Ondemand if I were you though.
[Nexus 5 Original Android Development] Disrupthor:
[MENTION=3292224]franciscofranco[/MENTION], Does your kernel have support (or will it have) for F2FS? It would be a great feature. Thanks.
[Nexus 5 Original Android Development] Balino:
If I rember correctly franco doesn't like f2fs at all, so no support.

I may be wrong
[Nexus 5 Original Android Development] franciscofranco:
I don't really care about F2FS, but I've added it on other devices. I thought I had added it on this one. I can do it though.
[Nexus 5 Original Android Development] luckana:
Honestly, has anyone felt benefits of f2fs, i was on it for nearly 6 months when i switched back to ext4, i just didn't see noticable difference whatsoever.
[Nexus 5 Original Android Development] phantom146:
There is sir,

Try to do a benchmark, and you can see the difference, or should i say the expinential difference. Multitasking will be faster also the app launches :). It was battery friendly too due to the io performance and cutting down heurestic analysis ehich is unnecessary.

On the overall feel it depends really on your device since nexus5 is fast enough you wouldnt be able to notice the difference... But behind the system there definitely is
[Nexus 5 Original Android Development] tylerdurden83:
On slower memory devices like my nexus 10, yes, on the n5 i didn't even try it thought, and i doubt that i'd feel it.
[Nexus 5 Original Android Development] franciscofranco:
Do you have numbers pre-f2fs after-f2fs? Numbers will tell you all.
[Nexus 5 Original Android Development] phantom146:
I had but i just recently clean wiped/ went nuclear reflashing my 6.0 firmware so i can find out who wrecked my radio so i cannot help with this one.
[Nexus 5 Original Android Development] Disrupthor:
If you could Francisco I for one would be much obliged.
[Nexus 5 Original Android Development] franciscofranco:
New Naptime update: https://plus.google.com/u/0/+FranciscoFranco1990/posts/cMTv9wfBKyN
[Nexus 5 Original Android Development] duffymm:
Hi Franco

first of all thanks a lot ! I'm using your kernels since ages !

Can I steal you just one minute to understand more "Naptime" ?

I'm actually using Greenify (beta version) with some experimental features for android 6.0.

How does Naptime work ? Does it replace greenify ? Can they both work simoultaneously ?

Sorry for using this N5 kernel space for this offtopic questions.

Thanks
[Nexus 5 Original Android Development] Arstoien:
I can answer you. Naptime's job is mainly to allow you to change the settings of Doze. To understand that, google exactly what Doze is. Greenify's feature of "aggressive doze" is similar to franco's aggressive doze feature – and that's the only overlapping of the two. No conflict will happen, just keep no more than one of them active ("aggressive doze"), if you really want to use aggressive doze.
[Nexus 5 Original Android Development] franciscofranco:
You ducking nailed it.
[Nexus 5 Original Android Development] phantom146:
Actually upon testing franc's aggressive doze sticks more and faster than greenify.. Just saying :3

Sometimes i have issues with greenify letting the sensors or interactive time run wild, though i like the aggressive notification rhingy lol
[Nexus 5 Original Android Development] Rapper_skull:
FKU keeps crashing when per-app profiles is enabled.
[Nexus 5 Original Android Development] franciscofranco:
I'm aware of that crash, already fixed on my local build.
[Nexus 5 Original Android Development] Rapper_skull:
Thank you, waiting for the release.
[Nexus 5 Original Android Development] franciscofranco:
Alright folks, it's play time! r80 is up here: http://kernels.franco-lnx.net/Nexus5/6.0/anyKernel/ and now FK will work on any rom! If you're on a custom rom just dirty flash it before flashing r80 to have their stock boot.img loaded in. If you're on stock it'll be fine. SuperSu installations will persist through FK flashes starting with r80!

FKUpdater will be updated sometime Monday/Tuesday to allow download & auto-flashes with this new method too.

Also F2FS is included on r80 for those who asked!

You're ****ing welcome.
[Nexus 5 Original Android Development] phantom146:
Is the ondemand governor here fixed franc?
[Nexus 5 Original Android Development] moddroid:
Stuck at google boot logo with r80!

dirty flashed over r79 with Xtrafactory it's my fault or bad zip?
[Nexus 5 Original Android Development] franciscofranco:
What did I say on my post? Dirty flash your rom to remove my old boot.img entirely, then the zip...
[Nexus 5 Original Android Development] phantom146:
Franc said to flash your rom first before flashing again your r80 zip :)
[Nexus 5 Original Android Development] moddroid:
I missed "to have their stock image loaded in" sorry it's late here hahah

Btw thanks, awesome kernel ????
[Nexus 5 Original Android Development] franciscofranco:
It's 5am here too...
[Nexus 5 Original Android Development] udnekzl:
Thanks for the update!

and... you decided not to release your kernel in boot.img format anymore?
[Nexus 5 Original Android Development] franciscofranco:
Apparently if it's a zip it's not a boot.img :p
[Nexus 5 Original Android Development] phantom146:
Franky is the ondemand governor fixed here? So i can switcheroo again back to your awesome kernel.. Just want to know before i reflash everything :3
[Nexus 5 Original Android Development] franciscofranco:
No. Why do you want Ondemand so bad?
[Nexus 5 Original Android Development] udnekzl:
yeah, I see it

little sad because I'm one of few people who prefer boot.img, but it's your kernel and decision anyway :)

always support you & fK

big fan of fK since maguro days.
[Nexus 5 Original Android Development] franciscofranco:
I prefer it too, but there are too many users who run stupid roms and they'll want to flash and bootloop, and it's a terrible experience.
[Nexus 5 Original Android Development] udnekzl:
sorry for that... the way I use fK is during the process of (clean) flashing factory image via fastboot, I flash fK boot.img instead of stock boot.img.

always worked flawlessly:good:
[Nexus 5 Original Android Development] rubaboo:
I'm on stock ROM with systemless root. If I want to switch from ElementalX to this, do I have to flash stock kernel in-between? Thanks!
[Nexus 5 Original Android Development] luckana:
Yes you do
[Nexus 5 Original Android Development] gaz41:
If I flash this kernel, by default selinux state will be enforcing? Is it possible to change it to permissive via fku app? Or how can I change it?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Rapper_skull:
[MENTION=3292224]franciscofranco[/MENTION] How will the root keeping method work? Currently the SuperSU installer first restores the backup and then patches it.

If now I flash r80 and then SuperSU, it will make a backup of r80. Let's say tomorrow there will be r81 and I flash it without reflashing SuperSU. Root will be kept, but SuperSU will still keep the backup of r80 (or I'm wrong?), so that when I flash a newer version of SuperSU, that backup will be restored and patched, returning to r80.
[Nexus 5 Original Android Development] emanuele1986:
Which folder are in f2fs? System data and cache or only data and cache?

Thank you
[Nexus 5 Original Android Development] udnekzl:
data and cache partition is encouraged. I don't think f2fs for system partition is worth it.

as far as I know in normal use, system partition is working read-only and reading is fast enough with ext4.

also you need f2fs-supporting ROM (not only kernel) to use f2fs for system partition.
[Nexus 5 Original Android Development] CataHd:
Any one else got stuck on google logo with r80?
[Nexus 5 Original Android Development] amaces:
He may have been asking about fstab support. Looking inside the r80 ZIP, /data and /cache are supported as F2FS.
[Nexus 5 Original Android Development] imrock0:
Me. May be this will help ?
[Nexus 5 Original Android Development] newcastle9:
Installed this on cm running perfect with your app
[Nexus 5 Original Android Development] WettbackMartyr:
Just a quick tip to all. I'm on stock 6.0.1 mmb29s running FK r79 and su 2.67. When I attempted to flash r80 and su it would appear to work flawlessly and boot properly but my kernel had not been updated to r80, about device still showed r79 as did fku. This happened 3 times. I then flashed stock boot image in fastboot and reflashed r80 w su 2.67 and now it shows the device has been correctly updated. So maybe flashing stock boot image or dirty flashing your ROM is good advice for everyone updating to r80. Maybe just my dumb luck I dunno. Just my 2 cents. :thumbs:
[Nexus 5 Original Android Development] Semtronix:
I had to do the same. Flashing r80 over existing stock with r79 and SuperSU would result in either a bootloop or the kernel not actually flashing.
[Nexus 5 Original Android Development] franciscofranco:
Thats why I said on the frickin post to dirty flash your rom or flash back stock boot.img if you were on stock rom.

Reading is hard.
[Nexus 5 Original Android Development] :
I just fleshed it and got boobloob.
[Nexus 5 Original Android Development] Mrcactuseater:
Hahahahaha
[Nexus 5 Original Android Development] franciscofranco:
Boobloop ?
[Nexus 5 Original Android Development] franciscofranco:
I re-uploaded r80 again, I had a typo in the fstab file and the performance profiles were outdated.
[Nexus 5 Original Android Development] jordirpz:
[MENTION=3292224]franciscofranco[/MENTION]

If i flashed r80 and my phone boots, can i flash the new r80 directly? Or i need dirty flash rom before? Thank Francisco
[Nexus 5 Original Android Development] amaces:
F2FS Support

Are you using the hammerhead_defconfig in the GitHub repo? While the F2FS code and fstab support are in place, I think that it's not enabled in the kernel .config: # CONFIG_F2FS_FS is not set.
[Nexus 5 Original Android Development] franciscofranco:
Flash directly.

My defconfig is in /proc/config.gz
[Nexus 5 Original Android Development] 777.300:
Thanks again for the update Franco. Running great on Latest Chroma ROM.
[Nexus 5 Original Android Development] 777.300:
Donation: done.
[Nexus 5 Original Android Development] amaces:
Thanks, I was trying to figure out why the first version of r80 was stuck at the boot animation (after re-flashing stock /boot and /system). All good with the current ZIP.

Also, I'm using the extracted config.gz for personal images; any better way to keep up to date with your configuration changes beside installing official FK images?
[Nexus 5 Original Android Development] Scar107:
Does this version allow for dt2w? If so. How do you set it up?
[Nexus 5 Original Android Development] fantamadnesss:
This kernel never had that feature (i guess).
[Nexus 5 Original Android Development] Scar107:
If true that kinda makes me sad, but I'll live.
[Nexus 5 Original Android Development] Alex Kane:
f2fs works great:D
[Nexus 5 Original Android Development] jawz101:
By Any ROM we don't mean cm13 Hammerhead-CAF, right
[Nexus 5 Original Android Development] phantom146:
Caf is a completely different code but who knows lol
[Nexus 5 Original Android Development] Semtronix:
No, you said if we're on stock ROMs that we'd be fine. It works so I don't really care.
[Nexus 5 Original Android Development] franciscofranco:
Thank you very much!

I don't usually push my defconfig because it's always shipped to /proc/config.gz and it's easily stripped using a script inside rootKernelDir/scripts/.

No, double tap to wake on the N5 kills your battery like there's no tomorrow.

How should I know? Try and let us know.

Then I'm a moron, because I should've said "if you're stock rom + FK you should flash stock boot.img to go back to pristine state". Sorry about that.
[Nexus 5 Original Android Development] aR_ChRiS:
Similarly, you can extract the boot.img file from the rom zip, flash it then flash the kernel afterwards, if you are on a custom rom that is.
[Nexus 5 Original Android Development] franciscofranco:
That's what I would do, but try to explain that to normal users.
[Nexus 5 Original Android Development] RucaNebas:
Hi Franco,

Just a detail but the latest release say r79 instead r80 after installed

Obrigado!! :)
[Nexus 5 Original Android Development] paaaulo:
http://xdaforums.com/showthread.php?p=64960969
[Nexus 5 Original Android Development] charlykwon:
Hello.. Sir.. Whats different between r79? I really happy to using your kernel r 79! Something big difference?
[Nexus 5 Original Android Development] Ryrynz:
What's the best thing to do when R80 is downloading and reaching 100% (and still showing as downloading) but nothing happens?

Currently rooted and Franco has permissions set. R79 went smoothly some days ago, now I've rooted again and it won't take.
[Nexus 5 Original Android Development] franciscofranco:
???

FKUpdater doesn't work with the new format just yet, needs an update coming out today/tomorrow. So now it thinks its downloading r80 but it isn't.
[Nexus 5 Original Android Development] luckana:
3g only. Wifi 20 mins. Blown away
[Nexus 5 Original Android Development] luckana:
Via terminal emulator, type

su

setenforce 0
[Nexus 5 Original Android Development] gaz41:
Does it survives reboot?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] 777.300:
Using this mod will definitely survive reboot:

http://xdaforums.com/showthread.php?t=2524485
[Nexus 5 Original Android Development] franciscofranco:
I strongly suggest you to leave SELinux alone. It's enforcing for a reason.
[Nexus 5 Original Android Development] jawz101:
Fyi cm13 hammerhead-caf

Doesn't work. Hangs at Google logo. I switched to regular cm anyways. myfluxi stopped maintaining it last week.
[Nexus 5 Original Android Development] sshuter:
I'm on cataclysm + elemental x. However, I want to test franco's kernel. Which steps should I follow in order to install cataclysm + franco kernel? Thanks you all
[Nexus 5 Original Android Development] d1n0x:
......

Jesus f*cking Christ.
[Nexus 5 Original Android Development] Diablos86:
i have stock rom but now i'm stuck on google logo. Pls someone can post a little guide to resolve this? I cannot understand "dirty flash" please. And sorry. just translate the dirty flash lol

edit: maybe fastboot boot.img is good?

uhm but i have the stock rom, strange... help me