Still wrong thread.
Its overratedWith the device or without it, this kernel is the most stable out of all ,tried all of them even Raphael's distrubt , true they all are full of features and also full of bugs and sudden reboots and freezes , if you are gamer then maybe they perform better but someone who needs stable phone for work then this build has never failed for me, please do keep your kernel going however you wish, I don't Want to advice or anything but it's also not good to fall for the trap of these naysayers, you still have a lot of users who enjoy your builds , no need to leave cause of couple of douchebags.
He wants attention. An attention seeker to be precise. If he hates developing just let it go!A few weeks ago went to telegram and saw a post linking to the donation amount for arter to buy the pocophone and there were already ~ 200 usd being donated. I find hard to belive that he couldn't get the 300-350$ needed to buy the poco. Even so, I can't understand why most of the devs get so offended by the community. It's the snowflake generation or what ? Devs claim they do this work for free out of the goodness of their hearts but is not like that, most of them want the fame, they want to be praised and glorified even if they don't realize this. If I were a dev i would just look through the posts to get user feedback and logs and simply just IGNORE the ****ty unrelated comments. As simple as that. So why all the drama ? Just do what you do, leave a donation link for us to repay your work, move on and stop complaining on tweeter of how your feelings got hurt.
This has nothing to do with arter97 kernel. Please get this post deleted or moved to the Q & A section.
No it's not that first dirty install the rom or flash the boot image of default rom you use then reflash the kernal you want or magisk if you want root that's it don't miss lead
I flashed arter successfuly on 2020 Jan pe build. Fyi I m using unencrypted version with f2fs.
arter97 kernel for Poco F1
/* Details */
Latest CAF msm-4.9 kernel fully merged
This kernel contains more cutting-edge changes from Qualcomm than the regular sdm845 tag
Latest Linux 4.9 subversion merged
Use CONFIG_HZ = 300
- This changes context switching interval from 10ms to 3.33ms
- Pixel used this for years and Google recommends other vendors to do the same for fewer jitters
Memory management improved(from Pixel 2 & 3)
Pixel's lowmemorykiller used
Scheduler commits cherry-picked from Pixel 3
RTL8152/8153 USB LAN adapter support
Built with -O3 speed optimizations
Built with latest GCC
Westwood as default TCP network congestion control
Entropy hook on storage removed
Latest mainline f2fs support with GC fixes
CFQ I/O scheduler backported from mainline
Systemless installation (the kernel itself doesn't touch /system or /vendor)
Modules support disabled for lighter kernel
Removed RTB(interrupt) logging entirely
/* Development */
I do not own a Poco F1.
This was developed by sharing most of the bits from my OnePlus 6 and Razer Phone 2 kernel.
I won't be doing device-specific changes to this kernel(e.g. improvements to the touch panel drivers) until I get my hands on an actual device.
This also means this kernel is/will be developed conservatively.
If you're interested in contributing to a fundraiser for me to get a Poco F1, please check post #2.
/* f2fs */
This kernel fully supports f2fs for /data and I encourage everyone to use f2fs with my kernel for better performance.
See here as to why you might want f2fs.
To use f2fs, download zip files from http://arter97.com/browse/f2fs
Flash f2fs_tools_for_twrp.zip from TWRP. This won’t format your /data partition.
This will replace TWRP's f2fs tools with the latest version and pass the correct parameter to mkfs.f2fs, which is necessary.
This needs to be done everytime you enter TWRP, if you want to re-format to f2fs.
After formatting, or flashing a new ROM or an OTA, /vendor’s fstab needs to be changed.
Flash f2fs_fstab.zip to convert fstab to f2fs again. This won’t format your /data partition.
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Thanks to */
nathanchance - for android-linux-stable
/* Instructions */
You can use the zip file to flash the kernel from your existing TWRP recovery.
If you don't have TWRP installed already, you can use the img file to flash the kernel directly from your PC via fastboot.
Both methods will install both kernel and modified TWRP recovery.
You can check if the modified TWRP is installed by looking at TWRP's version name.
It should say "arter97".
/* Downloads and links */
arter97 kernel for Poco F1, Kernel for the Xiaomi Poco F1
Kernel Special Features:
Last Updated 2019-10-28
deleted.This is not based in fact and an insulting guess.
arter97 may or may not update the kernel, but he hasn't said either way. Granted, his update schedule isn't as frequent as other developers, but he's already done 11 revisions and is supporting both PIE and Android 10 Q.
If u change your system from ext4 to f2fs you need to format your all data including internal storage so please keep backup before proceed.Hey, I've been wanting to install F2FS to see the performance difference between ext4 and f2fs. But I'm worried if I will lose my data. Should I take a backup first or will converting to f2fs not result in data loss? And can anyone please give me an Installation guide? I dont want to mess this up.
Love your kernel. Thank you!
If you don't know what formatting means I think you should wait until you have a bit more experience. If you choose not to wait use search. All the steps have been explained multiple times already. You will lose all data so backup to your sdcard first.Hey, I've been wanting to install F2FS to see the performance difference between ext4 and f2fs. But I'm worried if I will lose my data. Should I take a backup first or will converting to f2fs not result in data loss? And can anyone please give me an Installation guide? I dont want to mess this up.
Love your kernel. Thank you!
No, those “invalid segments” generated from f2fs is not used as a cache in its lifetime. It’s a thing on LFS(Log-structured File System). LFS gives a lot of advantages to flash storage but the growth of invalid blocks is the biggest downside of LFS design. f2fs aimed to effectively solve this via GC.
It NEVER results in data corruption, it just causes a hit on write performance after free segments are gone. Then, GC must be triggered on every write requests.
I’m not sure I’d use “little slow performance” here, it’s quite the contrary. f2fs’ background GC detects idle time to run GC, which is by default set very conservatively to avoid any performance degradation when I/O request spikes while GC is running.
Traditional Linux I/O benchmarks don’t represent daily Android I/O workloads. Android I/O workloads are VERY different from traditional desktop/laptop’s workloads.
Not sure how much of an improvement you would start call “massive”. The LFS nature of f2fs allows fsync() to bypass barrier without sacrificing integrity, which uplifts the bottleneck in write performance. In practice, this gives about 5-6x improvements in write performance.
I’m not gonna sugarcoat it. You’re correct.
btrfs aims to throw you every functions a file-system could possibly offer, which is why people say it’s unstable. btrfs/zfs is not comparable to f2fs.
Totally incorrect. Journalling itself gives ext4 a disadvantage about 30% over f2fs and its GC shenanigans. This is the main reason why f2fs is enforced on Android Go devices.
What’s wrong with Pixel 3’s f2fs? I’m yet to see an issue caused from f2fs instability.
Isn’t qcom’s implementation of ICE a mess anyways. This is not an issue of f2fs. f2fs just exposed multiple issues on qcom’s implementation of ICE.
ICE on f2fs should be good if you have the latest CAF stuffs.