yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] zurik:
I don't know... The overall performance is not same when I tried also stock . And fingerprint recognition is not too fast as stock .... Or all these is my illusion...
[Nexus 5X Original Android Development] pkelly517:
Dirty flash.
[Nexus 5X Original Android Development] zurik:
Dirty flash what?
[Nexus 5X Original Android Development] jugoslavpetrovic:
Well, my experiences with franco kernel is as well not the best as performace, it is slower then other kernels for sure. Running on balanced, not that much balanced. Never tried performance mode cuz it says it would work as on maxed cpu.
[Nexus 5X Original Android Development] pkelly517:
Dirty flash your ROM. Go with the stock kernel.

All your problems with Franco will be a thing of the past.
[Nexus 5X Original Android Development] Nicktheprofessor:
Yeah, see this is why these types of discussions are pointless, the UI resides in memory at all times and is wholly unaffected by schedulers and file systems.

The ONLY thing where it should actually make any form of improvement is in how fast your device boots up and starts applications and since the difference is negligible there is no good reason to use a less tested and more unreliable system.
[Nexus 5X Original Android Development] LazerL0rd:
I corrected myself. Look ?
[Nexus 5X Original Android Development] Nicktheprofessor:
Still wrong, Antutu is a benchmark, not "user experience" and you wouldn't be able to clock the speed difference by using a stop watch since it's so small that the time it takes for you to react is longer than the time difference between the two file systems.

But if you "feel" that it's faster then great, use f2fs.
[Nexus 5X Original Android Development] LazerL0rd:
AnTuTu HAS a UX benchmark. I've gotten higher in it with f2fs. That's all I said.
[Nexus 5X Original Android Development] Nicktheprofessor:
Well it is a Samsung invention and thus it will always be aimed to perform at it's best when running benchmarks. ;)

If you like it, use it but do not expect it to be as reliable as ext4 because it never will be. Ext4 has been used in production servers and desktops for a very long time and has a history of it's origins that dates back over 30 years while f2fs is a few years old and in that time it has not matured at all on the reliability part.

This whole discussion reminds me of one i had regarding ReiserFS once upon a time.
[Nexus 5X Original Android Development] LazerL0rd:
Yeah I just like how it is faster. I've used ext4 on my mini servers and stuff so yeah it's reliable. But have you heard of ReFS? Now that's gonna be perfect when it releases properly.
[Nexus 5X Original Android Development] Nicktheprofessor:
ReFS has been around since 2012, it's a proprietary file system that does it's best to mimic XFS but is both slower and... did i mention proprietary? It's an improvement over NTFS i suppose but "perfect"? Not even close.

Just use XFS for larger storage units (especially database servers) and you'll be very happy with the performance, it's the fastest and most reliable solution out there.

XFS would be faster on your phone than either ext4 or f2fs too and there is kernel support for it as well as tools (i built them myself so i know there are) but as with f2fs there is just about nothing to gain from it.

With that i'm out of this discussion and my apologies to Fransisco for derailing his thread.
[Nexus 5X Original Android Development] jcmm11:
ReFS? Perfectly non-transparent, proprietary, patent encumbered. BTRFS is a better solution, unless you swim in the MS pool. So is ZFS for that matter. It's probably the most reliable at the moment, although it will never find it's way into the Linux kernel due to license conflicts. Besides they both can do things that ReFS can't (deduplication, compression, cow snapshots). Ultimately I'm pretty sure BTRFS wins out over ZFS, but it's not quite there yet. Although even now it depends on your use case. If you don't need some of the advanced RAID capabilities that ZFS provides then BTRFS should be fine even today. I picked these 2 because they're closest to ReFS feature wise. A full discussion of various filesystem pros and cons is obviously not for this thread.

And now I think we've gone off topic quite enough, unless Franco plans to start incorporating some of these filesystems :laugh:
[Nexus 5X Original Android Development] ndarkside93:
Sorry to go off topic but ReFS is a Microsoft file system unlike ext4 however with their new found love of Linux, there is still hope.
[Nexus 5X Original Android Development] franciscofranco:
FS discussions are interesting.

Regarding earlier posts about FK being less performant, well, I do reduce input boost duration quite a lot compared to stock, so you're free to set it up higher if you want. Next release has some performance improvements anyway that I've been working on the last couple days, will release soonish.
[Nexus 5X Original Android Development] zurik:
Thanks for advice. I dirty flashed the ROM... And reflashed the FK. It's quite fast now ... I don't want to reflash stock LOS stock kernel because its drains battery with regular use.... like a cup of coffee... FK on my device is battery efficient!
[Nexus 5X Original Android Development] Giorgos Chatziioannou:
this is my post couple pages ago, user experience is greatly enchanced by f2fs. i dont know about load times, i only bothered with f2fs cause ext4 was not smotth no matter what kernel, governor, etc i used. i dont get your comments about reliability either, never heard anyone experience such issue, so what you say sounds completely theoretical
[Nexus 5X Original Android Development] franciscofranco:
He's 100% right about reliability. ext2 has been around for 10k years, ext3 too, ext4 is the natural evolution and has been deployed into all sorts of machines all around the world for decades, it's maintained by VERY and I mean VERY smart people. It's been patched to death. It's probably the most reliable FS in the world at this point.

F2FS is very new and it's not battle tested. Even if you don't "see" the issues, F2FS will probably have more bugs than you can count, and it's certainly not deployed in servers (which are the definition of needing reliability to function).
[Nexus 5X Original Android Development] Cozzmy13:
[MENTION=3292224]franciscofranco[/MENTION]

Hi!

Sorry for the off topic, I started kernel development a few months ago for a similar device to the Nexus 5x(same SoC) and since I fixed various bugs included in the source released by the manufacturer, it's been getting some traction, and I've got a ROM maintainer to use it. Users reported that battery life is a bit worse since the ROM changed to my kernel, which I also noticed, but I don't really know what causes it or how to improve battery life. The only thing I did differently than the older kernel is that I haven't updated the CAF sources from which I started to the latest 3.10.y. Could this be the problem?

Sorry for he off-topic again, but I didn't have any other means of contacting you.

Please take a look and tell me if merging linux-stable(or should I merge kernel_common?) is worth it and if there is anything I could do to further improve the battery.

Thanks!

Source: https://github.com/Demon000/kernel_xiaomi_libra
[Nexus 5X Original Android Development] franciscofranco:
That's nearly impossible for me to say. Commits seem ok. There's so much that affect battery life... you need some numbers under some form of controlled environment with stock Kernel vs yours, otherwise you can't even start to figure out what might be. My bet is always apps ****ing battery life, or signal strength, but I can't guess. What you're asking is for me to find a special grain of sand in a beach.
[Nexus 5X Original Android Development] franciscofranco:
New Franco Kernel version for the Nexus 5X

r35

1. Offload a lot of background daemons to the system-background group, which only allows them to run on cpus 0, 1 and 2, freeing all other cores, specially the big cluster. This will reduce needlessly cpu wake-ups from idle, and largely reduce processing power requirements from cpu 3, 4, and 5 (4 and 5 are part of the big cluster, which uses a lot of energy)

2. Lower power consumption from the big cluster by lowering the occurence of sample rate which'll in turn make the big cluster cpus less nervous and say in lower frequencies more often. In contrast little cluster is a little more forgiving and scales up a little easily. Since the little cluster uses 4 times less power, this is just fine

3. Tweaked Performance Profiles, Power-saving now turns off the big cluster to save precious power, but the little cluster will be boosted for longer during input touch events

zip: https://kernels.franco-lnx.net/Nexus5X/7.1/anyKernel/fk-r35-anykernel2.zip

Franco Kernel Manager & Updater is the best companion for this Kernel (https://play.google.com/store/apps/details?id=com.franco.kernel)

If you don't (yet) have my full featured app you can always just download its free counter part which lets you seamlessly and automagically update Franco Kernel on your device. It's free and my cat approves! (https://play.google.com/store/apps/details?id=com.franco.kernel.free)

I also strongly suggest you install Naptime (https://play.google.com/store/apps/details?id=com.franco.doze), for free, to achieve the best battery life through out the day. Try it, you won't be disappointed!
[Nexus 5X Original Android Development] Mrcactuseater:
Sweet, cheers dude!
[Nexus 5X Original Android Development] zurik:
Nice! Thanks!
[Nexus 5X Original Android Development] :
Thanks a lot for your update and thank you for listening me and add tweak to put off Big cores when power save mode is activated!

---------- Post added at 09:47 PM ---------- Previous post was at 09:31 PM ----------

Il tested "new power save mode" and Big cores don't turn off, what I need to do?

I flashed properly your last kernel version and activate power save mode in your app.
[Nexus 5X Original Android Development] Giorgos Chatziioannou:
ye, but this is a phone not a server ;)

also, bugs that dont brick or slow the phone or dont cause jerky acts are essentially not bugs for normal users

i should had express myself better, but when i said theoretical i meant it only matters for people involved in development, as the rest people will only see gains with f2fs :)

and cheers for the new update :good:
[Nexus 5X Original Android Development] franciscofranco:
I don't know what app you're using to check it, but cpu4 and cpu5 go offline just fine.

That's not how any of this works...
[Nexus 5X Original Android Development] vedantdude:
Cores do go offline, checked with the system monitor app. No problems here.
[Nexus 5X Original Android Development] Giorgos Chatziioannou:
maybe, but most users dont care how it works ;)
[Nexus 5X Original Android Development] tyroneballz:
hiiiii

this version works on 7.1.2?? :):):):) thanks
[Nexus 5X Original Android Development] Schneewitzchen:
yes
[Nexus 5X Original Android Development] LazerL0rd:
Thanks for the update! I didn't think you could make the battery any better, but you just did. Just wondering, would this lose any performance at for the system? Or have you increased the clock of the LITTLE cluster to compensate for no Big cluster being used?
[Nexus 5X Original Android Development] Mirarchi:
How Can install when coming from other kernel? Clear Dalvik cache and then install?
[Nexus 5X Original Android Development] ulxerker:
if you're on another custom kernel first flash the kernel (boot.img) that came with your ROM, then flash franco.Kernel. clearing dalvik cache is not needed.
[Nexus 5X Original Android Development] LazerL0rd:
Well, I'm using Hawktail governor settings and it seems to work perfectly with this. I went though and compared it to yours. It's always based on little core but pushes performance at big cores. Thanks again [MENTION=3292224]franciscofranco[/MENTION] for making this great update.
[Nexus 5X Original Android Development] franciscofranco:
Just a heads-up Franco Kernel Manager & Updater is on a limited time -50% sale because of my birthday https://plus.google.com/u/0/+FranciscoFranco1990/posts/fZTLkaFHdpd
[Nexus 5X Original Android Development] leolawliet:
Happy birthday Franco!
[Nexus 5X Original Android Development] Giorgos Chatziioannou:
happy birthday, best wishes to you :highfive:
[Nexus 5X Original Android Development] jugoslavpetrovic:
[MENTION=3292224]franciscofranco[/MENTION] how would userspace govs for cpu and gpu act compared to interactive with your kernel? Any advice on how to set it up with thermal or core?

Latest build seems better performance on default. Thanks for update.
[Nexus 5X Original Android Development] codfx:
Happy birthday Franco! I just bought the app. Surprise!!! :laugh:
[Nexus 5X Original Android Development] LazerL0rd:
[MENTION=3292224]franciscofranco[/MENTION] could you add an option to the f2fs mount? It's from the Moto Z and apparently gives a bigger speed increase than f2fs itself. Could you add "nobarrier" to the mounting options please. There are some other mount options that help too.

Source: http://taras.glek.net/post/Moto-Z-has-10x-less-lag-than-pixel/

EDIT: How do I edit the fstab without being stuck at boot? I also read it's a bit risky though, but isn't f2fs risky itself? I'm guessing you might not implement this so I have a question. Should I leave the "wait" mount option?

Wanted:

userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,nobarrier,extent_cache,active_logs=6,encryptable=/dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata

PS - After all this FS talk and research, I've been been wondering if you'd add the "lazytime" mount option (https://lwn.net/Articles/621046/). I'm not sure if it's still necessary but apparently some apps still use atime and this enables it only when needed.
[Nexus 5X Original Android Development] Dread This Day:
Just bought FKM, thank you for all of your work. My 5X wouldn't be the same without it.
[Nexus 5X Original Android Development] NxStep:
Hi Franco!

These tweaks sound pretty interesting but I can't seem to find the related changes on your github. Or are they implemented in the init? Can you please point me where to find them?

Many thanks!
[Nexus 5X Original Android Development] LazerL0rd:
Yeah, I know those but I'm just pasting them as Motorola had them. I tried editing the fstab from the franco kernel zip but couldn't boot. Replacing and adding these commands both didn't work. You mentioned remounting but where is the one that I CAN edit.
[Nexus 5X Original Android Development] franciscofranco:
Userspace governor is special and not really meant for mobile phones.

Nope, nobarrier doesn't guarantee data integrity, it's like welcoming data corruption in your front door.

That's inside init.special_power.sh. I basically run that after boot, do a query to find out the process ID of those services, and then I add the ID to the system-background group.
[Nexus 5X Original Android Development] LazerL0rd:
[MENTION=3292224]franciscofranco[/MENTION],

Okay then, two things:

1) How come when I edit the fstab.bullhead it doesn't boot? I've tried it though modifying your zip's fstab file. Could you tell me how I could do it? Those commands (inc. nobarrier) shouldn't really stop booting.

2) Your init.special_power.sh mod clashes with my su.d governer setting. I'm finding that an issue as that means it's running ~90 seconds post-boot. Isn't that a bit late? Ik this as my governer settings which previously worked only sets on the LITTLE cluster and input boost. It doesn't load on the Big cluster until run much later. Obviously, I'll increase my governer profile's time to compensate but yeah just saying.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Ok, but its present in your kernel for mobile device.
[Nexus 5X Original Android Development] ndarkside93:
Is there because all the standard Linux governors that are baked into the upstream android kernel are there. You can use it if you choose, but myself or [MENTION=3292224]franciscofranco[/MENTION] wouldn't recommend it.
[Nexus 5X Original Android Development] jcmm11:
That was my initial reaction as well, and for ext4 it's definitely true. But it seems that since f2fs is log based rather than journaled it's not true here. The quote I have came from f2fs.txt of the kernel documentation. Since the phone is all nonvolatile memory (afaik) it seems that it could work here.
[Nexus 5X Original Android Development] indian84:
Thank you [MENTION=3292224]franciscofranco[/MENTION].

Amazing battery and great performance.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Is there anything else not recommended for our devices but present in all kernels so we dont screw up?
[Nexus 5X Original Android Development] ndarkside93:
Not that I can think of. There are a lot of tunables available that most people shouldn't touch, especially I/o. It's not that they aren't good for our phones, but that most people don't know what they do or how they affect the device.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Thanks.

I never played with io tuning cuz I didnt get them to figure out, but changing cpu govs sure to try and see the difference. I got to say I tried userspace cpu gov for short time and device is very responsive and faster I think. I didnt ger into geek stuff to check cpu times and all, also measuring batt but just for very short time.
[Nexus 5X Original Android Development] ndarkside93:
User space will be very smooth and responsive but the battery life suffers dramatically.
[Nexus 5X Original Android Development] Nicktheprofessor:
Which explains why this completely pointless discussion between people who know and people who do not know is taking place.

It's useless, this is FLOSS, don't like it? Change it.

---------- Post added at 03:41 AM ---------- Previous post was at 03:37 AM ----------

Well it will run all CPU's on both clusters at maximum speeds without a userspace governor so it will be very smooth.

Without a userspace governor it's the same as running performace but with the addition that all CPU's are online at all times.

It's meant to be used with virtual machines that regulate CPU's via a userspace governor.
[Nexus 5X Original Android Development] :
Guy is it possible to use my phone as speaker with the aux cable?
[Nexus 5X Original Android Development] ulxerker:
No as there isn't a line-in port.
[Nexus 5X Original Android Development] :
OK thanks for answer ?
[Nexus 5X Original Android Development] :
is it only me or the default power saving settings are 'too' aggressive on r35? i experience stutters more often than r34 but i must admit, battery is much better. :)
[Nexus 5X Original Android Development] franciscofranco:
That's the point of the profile. You can try a higher input boost frequency, but the whole point of the profile is maximizing battery life while sacrificing performance.
[Nexus 5X Original Android Development] LazerL0rd:
[MENTION=3292224]franciscofranco[/MENTION], this is what I meant. Jolla's added it to his kernel too, I guess you could ask him if he's got any corruption yet but no one has reported it.
[Nexus 5X Original Android Development] kimikim0:
im sorry, do i need to enable all set on boot option for everything ? i just prefer stock franco setting and not into tweaking stuff, so do i need to ?
[Nexus 5X Original Android Development] SlimSnoopOS:
No. However, if you run a custom rom then the default governor may need to be switched to Interactive. Some roms have an issue where it sets the governor to Performance on boot. Just switch it to Interactive and enable on boot. Every remaining kernel settings is set properly on flash.
[Nexus 5X Original Android Development] kimikim0:
so the others just leave it as default no need to change or enable anything right ?
[Nexus 5X Original Android Development] SlimSnoopOS:
Correct
[Nexus 5X Original Android Development] franciscofranco:
Evidently if you don't need anything to be restored on boot you don't enable that option.
[Nexus 5X Original Android Development] ndarkside93:
[MENTION=3292224]franciscofranco[/MENTION] Thank you for everything you've done for this device, and the help you always provide. Like last time, off to bigger and better things. Can't wait to try your OP3 kernel. Thank you and happy late birthday. ????
[Nexus 5X Original Android Development] jugoslavpetrovic:
There is the vomer twaeks thread but it seems abendoned. Is it recommended to use it with this kernel still?
[Nexus 5X Original Android Development] franciscofranco:
I strongly recommend you to not use it.
[Nexus 5X Original Android Development] franciscofranco:
New quick Franco Kernel Manager & Updater sale to test the new Sales feature of the Play Store. If you missed Saturdays sale this is your chance!

https://plus.google.com/+FranciscoFranco1990/posts/43VBdEdLWs2?iem=4&gpawv=1&hl=en-US
[Nexus 5X Original Android Development] buffer overflow:
This app is all must like L Speed... Promise a lot.
[Nexus 5X Original Android Development] jugoslavpetrovic:
It was highly recommended for Franco and ElementalX kernels only. Franco says not to use, so I will not.
[Nexus 5X Original Android Development] buffer overflow:
Exactly ! Franco & ElementalX is all ready the best from... other kernel and is very tweaked/tunable, so in that case what is the point to "extra" tweak !? ?
[Nexus 5X Original Android Development] jugoslavpetrovic:
Right. But I tried to figure what and how vomer is doing to kernel on that dead thread cuz it says sh*t in the app. But somewhere was recommended so I got interested, and why for only Franco and EX. But if its not recommended then who cares.
[Nexus 5X Original Android Development] buffer overflow:
Definitely not me or you ! :good::)
[Nexus 5X Original Android Development] SKUndef:
[MENTION=3292224]franciscofranco[/MENTION] Could you add the possibility to turn off big cluster through Per-App profiles? I would like to have power-saving settings for some apps without the screen brightness reduce. Thanks
[Nexus 5X Original Android Development] BS86:
you can set a Big Cluster thermal threshold in the per-app profiles.

Just set it to 10°C or something that you are always above, and it will work in the way that you want to use it ;)
[Nexus 5X Original Android Development] SKUndef:
I will try, thanks for the tip!
[Nexus 5X Original Android Development] franciscofranco:
That's a possibility.
[Nexus 5X Original Android Development] Zach1928:
Hi all, has anyone had any issues with the latest FK version on stock ROM? I'm looking to unlock the bootloader and use fastboot to fire up a live image of TWRP and sideload the zip rather than replace the stock recovery
[Nexus 5X Original Android Development] franciscofranco:
No issues. Only magic.
[Nexus 5X Original Android Development] :
What exactly with magisk ?

And I already told you but after few time Big cores are enabled again with power save mode.
[Nexus 5X Original Android Development] franciscofranco:
I don't control if there are other services (such as thermal engine) that online those cores back on again. I can make them unable to online by changing the file node permissions, but I don't think that's a really great policy...
[Nexus 5X Original Android Development] :
OK I understand what you mean.

Thanks for answer?
[Nexus 5X Original Android Development] :
You must read this if it's not already the case https://www.xda-developers.com/onep...s-with-conservative-governor-for-some-reason/
[Nexus 5X Original Android Development] franciscofranco:
I already told the writer to fix the article to prevent people from spaming me with this. Conservative isn't magic, it's just how it decices to ramp up/down by default that causes that effect.
[Nexus 5X Original Android Development] :
Oh OK sorry for spaming I thought it will interest you.
[Nexus 5X Original Android Development] franciscofranco:
You're not spamming. But I know how conservative works.
[Nexus 5X Original Android Development] :
Yeah as I want to study computing I checked your career on LinkedIn so I know that you know how conservative works ? but next I will better read before sharing ?