[r11] arter97 kernel for Poco F1

Status
Not open for further replies.
Search This thread

willybarca

Senior Member
Apr 7, 2010
422
129
sydney
With 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.
 

sachin5555

Senior Member
Nov 15, 2015
419
77
28
Shimla
@arter97 sir u are pro in your work that's why i see your name in the list when i type in google top 10 kernel developers in xda. I personally feel that this kernel is 100% stable perfect for battery and performance. I never get any random reboots or screen freezing issue. If anyone ask me which is best and most stable kernel i definitely suggest arter or franco and u both are great and we all appreciate your work. Thanks for this awesome kernel.
 
  • Like
Reactions: haldaios

jackiass

Senior Member
May 22, 2011
903
606
OnePlus 3
Xiaomi Poco F1
Arter please continue updating your kernel, you. I beg you, because your kernel is best! You can lock this post so no one can comment but please do not quit because soooome people (sorry but we all know who but not gonna say it) are being very rude and entitled!!!
Did you read the tweet? He is not quitting because of comments. He is not learning anything from coding for poco so he'd rather move on to new challenges. I don't know why people keep trying to turn this into some kind of imagined racial problem.
 
Did you read the tweet? He is not quitting because of comments. He is not learning anything from coding for poco so he'd rather move on to new challenges. I don't know why people keep trying to turn this into some kind of imagined racial problem.

Did you? I never said it was the ONLY reason but he said it was one of the major reasons he quit. Also im not sure what you mean with racial problem

Sent from my Poco F1 using XDA Labs
 
  • Like
Reactions: Sendertrii

suolrihm

Senior Member
Jul 3, 2017
170
102
I can see the previous racist posts were deleted so I can understand the confusion.
Yeah. I've seen some groups hating the device like it's only "an Indian" problem - The racists postings are sadly a thing.

At this point: Thanks to the mods for removing those kind of posts. Racism got no place in any community and/or open source projects in general.

Regarding the tweets: I also don't like the community around the Poco, as a user. It feels like there is aggression and arrogance spread around some user... Even tho it would be sad if arter would drop the support, it is understandable. If there is no learning curve whatsoever and the trolling is as that annoying, why go through the hassle anymore? No matter if he is still maintaining it or drops it, I just want to say thank you again for some very pleasant months with the kernel, really appreciate your work.
 
Yeah. I've seen some groups hating the device like it's only "an Indian" problem - The racists postings are sadly a thing.

At this point: Thanks to the mods for removing those kind of posts. Racism got no place in any community and/or open source projects in general.

Regarding the tweets: I also don't like the community around the Poco, as a user. It feels like there is aggression and arrogance spread around some user... Even tho it would be sad if arter would drop the support, it is understandable. If there is no learning curve whatsoever and the trolling is as that annoying, why go through the hassle anymore? No matter if he is still maintaining it or drops it, I just want to say thank you again for some very pleasant months with the kernel, really appreciate your work.


No offense but i and many others agree "they" are the majority of the people that are 'agressive and arrogant'. Really sucks that it made him and probably other devs quit but i understand it, Budget phone communities are very toxic because of "them" and it isn't very fun to put effort while they keep being so toxic.

Sent from my Poco F1 using XDA Labs

---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------

I can see the previous racist posts were deleted so I can understand the confusion.
Don't even try to deny it you are just lying to yourself. Many people agree w me.

Sent from my Poco F1 using XDA Labs
 
Last edited:

strongst

Senior Moderator - Developer Committee
Staff member
Sep 18, 2007
13,254
16,167
thank's
HTC Desire
Smart Watches
XDA-Developers is a multicultural community where every faith or personal belief is accepted. Insulting the faith or nationality of another member is a serious rule violation and this kind of behavior will not be tolerated here.

I recommend to read the FORUM RULES especially those:



2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.


If you come across this just hit the report button and let the mods handle it, do not respond or become part of such a discussion. We don't need bloated threads with those discussions:good:

Do not engage in this activity any further, as ignoring this warning will be subject to a sanction being applied. If the thread won't turn back to topic, we'll temporarily close it.

Now everyone back to the technical topic regardless what decision the dev will take in the future.

Thank you all for your understanding and have a nice day :)

strongst
Forum Moderator
 

saintjimmy1984

Senior Member
May 13, 2018
366
145
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.
 

MMN

Senior Member
Mar 1, 2006
93
15
For decrypted f2fs assuming you do a clean install of your OS (this deletes everything on your internal storage so backup first if you need to):
wipe data system cache
flash f2fs tools for twrp
go into wipe section select data > change/repair file system then format your data to f2fs
flash firmware (V10.3.6.0.PEJMIXM)
If your OS doesn't come with vendor, flash it now.
flash OS
flash gapps
flash fstab
flash f2fs optimize
reboot to recovery
reboot to system
reboot to recovery
flash magisk
reboot to system
reboot to recovery
flash arter kernel
reboot to system

Thank you for the instructions. What's the right doing for encryption?
I did the same for encrypted /data partition (f2fs) - except for the zip files I took ALL from the ENCRYPT directory:
wipe data, system, cache
flash f2fs tools for twrp (I used official TWRP 3.3.0.0 and 3.2.3.0-decrypt)
format /data to f2fs
flash OS (here Evolution for PocoF1, comes with vendor and gapps)
flash fstab
flash f2fs optimize
reboot to recovery
reboot to system
-> So far everything works very well. OS starts, the phone is encrypted.
But if I
reboot to recovery
(1) I can not see internal data (because is encrypted)
(2) after flashing magisk and rebooting to system -> the phones hangs after "swipe to unlock" in a loop ("Phone is starting ........")

Where is my mistake?
Or is there a guide that I have not seen / found yet?
 

jackiass

Senior Member
May 22, 2011
903
606
OnePlus 3
Xiaomi Poco F1
Thank you for the instructions. What's the right doing for encryption?
I did the same for encrypted /data partition (f2fs) - except for the zip files I took ALL from the ENCRYPT directory:
wipe data, system, cache
flash f2fs tools for twrp (I used official TWRP 3.3.0.0 and 3.2.3.0-decrypt)
format /data to f2fs
flash OS (here Evolution for PocoF1, comes with vendor and gapps)
flash fstab
flash f2fs optimize
reboot to recovery
reboot to system
-> So far everything works very well. OS starts, the phone is encrypted.
But if I
reboot to recovery
(1) I can not see internal data (because is encrypted)
(2) after flashing magisk and rebooting to system -> the phones hangs after "swipe to unlock" in a loop ("Phone is starting ........")

Where is my mistake?
1Or is there a guide that I have not seen / found yet?
I don't use encryption so I don't know
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 140
    arter97.png

    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
    Timer optimizations
    RTL8152/8153 USB LAN adapter support
    Permissive SELinux
    Passes SafetyNet
    Built with -O3 speed optimizations
    Built with latest GCC
    Westwood as default TCP network congestion control
    UFS optimizations
    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
    WireGuard support
    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 */

    TheCrazyLex
    xboxfanj
    Tim Murray
    RenderZenith
    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 */

    Removed
    Kernel source

    XDA:DevDB Information
    arter97 kernel for Poco F1, Kernel for the Xiaomi Poco F1

    Contributors
    arter97
    Kernel Special Features:

    Version Information
    Status: Testing

    Created 2019-04-07
    Last Updated 2020-01-26
    79
    There are soooo many misinformation regarding f2fs, but I don’t blame you. f2fs documentation sucks and there’s not much details on the internet except for its original paper.

    Here’s a discussion that went on a Telegram group. I’m sharing it here to correct some misconceptions regarding f2fs.

    F2FS is faster than ext4
    One of the reasons is the cache files that it generates
    Later these files remain as garbage Becoz no use
    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.

    Soon they increase to a huge size
    And may corrupt your data
    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.

    Kernels can enable background Gc flag
    Which may lead to a little slow performance
    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.
    My rapid GC disables background GC because it’s enough to clean-up invalid segments.

    F2FS itself just replacing EXT4, in fstab for example, isn't actually that much faster. Many many backend are up on the web to prove it.
    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.

    The ability to turn off journaling safely in SQLite is so far the biggest advantage f2fs has over ext4. Check the piece I wrote on AnandTech for more details: https://www.anandtech.com/show/13474/the-google-pixel-3-review/2

    SSR also allows f2fs to reduce performance regression when the utilization is nearly full. This is indeed, very noticeable. If you compare side-by-side f2fs with ext4 both with more than 80% full, f2fs remains more responsive.

    However, when you use it configured a bit with nobarrier, etc. it can show a decent improvement (still not massive otherwise everyone would be using it).
    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.

    Google enforces f2fs on Android Go devices. I think it’s a pretty good indication of “everyone is starting to use it”.

    Finally, it is no where near as stable as EXT4. It may have stabilised across the years but does not compare.
    I’m not gonna sugarcoat it. You’re correct.
    f2fs used to run into funky issues when a corner-case workload’s been thrown at it(which I’m yet to see in the recent year).

    But I’m genuinely curious why the heck people are saying f2fs is unstable for regular Android users to use it. I would LOVE to see some real data and fact behind someone saying f2fs is unstable.

    You won’t run into corner-case when you’re running Android. If any, it should be better than ext4 to its LFS nature.

    You heard of Btrfs before? Well it's considered still pretty unstable and corrupts data.
    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.

    IIRC EXT4 has flags to lower wear and tear too and it's basically meaningless on UFS nowadays.
    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.
    Well if you’re gonna compare f2fs to ext4 without journalling, you don’t deserve to know these details.

    I'm saying just because you or even if this entire group didn't have issues with F2FS, that's not gonna give it the title of stable. Just look at Google's PXL3 implementation.
    What’s wrong with Pixel 3’s f2fs? I’m yet to see an issue caused from f2fs instability.

    F2FS is still missing things such as ICE support officially.
    Google used a proprietary implementation of ICE from CAF Partner tag
    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.

    With other developers and my opinion I got to the conclusion that while F2FS is still unstable the only reason not to use is cause ICE F2FS isn't very ready yet.
    ICE on f2fs should be good if you have the latest CAF stuffs.
    52
    45
    r10 is up.
    I cooked up a separate Android 10 kernel since users seem to care.

    r10
    Novatek touch firmware updated to 10.3.7.0 (by Akhil)
    Separate Android 10 kernel released
    Swap compressor backend(LZ4) updated
    LA.UM.8.3.r1-06100-sdm845.0 merged
    Linux v4.9.196 merged
    Wi-Fi drivers updated to 5.1.1.74O
    Latest f2fs-stable merged
    43
    I'm discontinuing Poco F1 development on XDA.

    Follow @arter97 on Twitter for status updates.