[MODULE] [7.x.x] Enable sdcardfs - 7/13/2017

[MODULE] [7.x.x] Enable sdcardfs - 7/13/2017 - Magisk

Introduction
Hello everyone! This is an incredibly simple module to enable sdcardfs on any Nougat 7.x ROM (SDK 24 or higher). sdcardfs is a replacement file system for FUSE, used to mount the /sdcard partition; you can read about this change here.
Some notes
sdcardfs is in constant development (at least two to three patches per week on average), meaning it could become unstable at any point. Certain apps do not play with sdcardfs, which can lead to crashes and corruption. Enable it at your own risk!
Your kernel MUST have sdcardfs support for this to work. Please ask your kernel/ROM developer if they have included all of the proper support commits for it to work. They can be found in AOSP's kernel/common repo (or a quick search of the AOSP Gerrit).
You MUST have this system/core commit. There is no reason that every 7.x ROM should not have this commit as it comes straight from Google but you never know.
Frequently Asked Questions
1.1 Q: How do I use this?
1.1 A: Flash it in recovery or add it in Magisk Manager > Modules.
1.2 Q: How do I check if the module works?
1.2 A: Go into a terminal emulator and type the following:
Code:
su
df -t sdcardfs
If you see something like the following, the module worked! If not, it is most likely because you either don't have sdcardfs support in your kernel OR you do not have the system/core commit I mentioned above.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.3 Q: I'm having xyz issue.
1.3 A: Great! Please give me a logcat, dmesg, and Magisk log and I'll be happy to assist.
Changelog
Version 3.0:
Update template to v4 and use system.prop instead of post-fs-data.sh
Version 2.1:
Improve print_modname so it looks right while flashing in recovery
Don't install on anything less than Nougat (thanks @veez21)
Version 2.0:
Add logging to Magisk log
v13 snapshot support
Version 1.0:
Initial support
Downloads
Primary | Mirror
Source

Hooray for bleeding edge break my phone stuff!
Sent from my Nexus 6 using Tapatalk

Hahahaha. I'm not sure I should try that on my stock MM Rom. Even with Firekernel.
Enviado de meu MotoG3 usando Tapatalk

Uploaded version 2.0 which adds some info in Magisk's log and adds support for the unified magisk binary in the v13 snapshot builds floating around.

The Flash said:
Uploaded version 2.0 which adds some info in Magisk's log and adds support for the unified magisk binary in the v13 snapshot builds floating around.
Click to expand...
Click to collapse
do we update by just flashing the newer build over the existing one?

xflowy said:
do we update by just flashing the newer build over the existing one?
Click to expand...
Click to collapse
Yes.

The Flash said:
Uploaded version 2.0 which adds some info in Magisk's log and adds support for the unified magisk binary in the v13 snapshot builds floating around.
Click to expand...
Click to collapse
Cheers for doing this. Glad I could test it for you.

@The Flash U just broke my MM installation cause I was tested blind, I don't know what happende I just didn't read it was only for sdk24 +
I seem it after I flashed it, I didn't restarted and was going to uninstall on magisk, but then magisk lost root (wasn't happened before on the stock rom), I had to restart, I deleted it from magisk.img using the magisk mount module, and now it stays on Android is starting forever, and does not start up. :/
You can blame me xD But, can help me?
What files I have to edit/delte so I can completely disable it?

justjr said:
@The Flash U just broke my MM installation cause I was tested blind, I don't know what happende I just didn't read it was only for sdk24 +
I seem it after I flashed it, I didn't restarted and was going to uninstall on magisk, but then magisk lost root (wasn't happened before on the stock rom), I had to restart, I deleted it from magisk.img using the magisk mount module, and now it stays on Android is starting forever, and does not start up. :/
You can blame me xD But, can help me?
What files I have to edit/delte so I can completely disable it?
Click to expand...
Click to collapse
The script doesn't actually fire if you are on Marshmallow: https://github.com/nathanchance/magisk-modules/blob/sdcardfs/common/post-fs-data.sh#L32
Even then, that prop doesn't actually do anything on Marshmallow or below. Your issue is unrelated to this. Dirty flashing your ROM should fix it.

The Flash said:
The script doesn't actually fire if you are on Marshmallow: https://github.com/nathanchance/magisk-modules/blob/sdcardfs/common/post-fs-data.sh#L32
Even then, that prop doesn't actually do anything on Marshmallow or below. Your issue is unrelated to this. Dirty flashing your ROM should fix it.
Click to expand...
Click to collapse
@The Flash, check this out
https://github.com/nathanchance/magisk-modules/pull/1/commits

@The Flash - May I know your keyboard name??? ?

mkshakya said:
@The Flash - May I know your keyboard name??? ?
Click to expand...
Click to collapse
It's Gboard themed with Deep Darkness for Substratum, coming soon.

The Flash said:
....
Click to expand...
Click to collapse
edit

Hello, do you know if EX kernel supports sdcardfs? Sorry if I asked here but I thought you know since I always see you on all of the forums :silly:

RonnellTapawan said:
Hello, do you know if EX kernel supports sdcardfs? Sorry if I asked here but I thought you know since I always see you on all of the forums :silly:
Click to expand...
Click to collapse
Yes: https://github.com/flar2/bullhead/commits/ElementalX-4.00/fs/sdcardfs
It does not have all of the AOSP upstream commits but it should be fine without them.

I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.

franciscofranco said:
I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.
Click to expand...
Click to collapse
Why does my dog do back flips?

franciscofranco said:
I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.
Click to expand...
Click to collapse
While I agree that users tend to be less informed than developers are, I have made it fairly clear in the OP that this is experimental and to enable at their own peril. I like bleeding edge and many other users do as well, knowing fully the risk of it. I'll take to heart the concern though, thank you.
To any kernel developer (and users): If your users start complaining about crashes and such, please let me know and I'll remove the module.

Hey, I complained but stated that was my fault. Now I installed DU after my data partition gone to hell, and found out the same prop was already set to true on that ROM. And nobody gone there to ask them to take the ROM down. Pocketcasts complained a little but I managed to make it work. No problems.

franciscofranco said:
I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.
Click to expand...
Click to collapse
WTF franco.. .I thought this was a development friendly forum..
Bleeding edge and experimentation should be applaud, not criticize.
PS I know that this forum turn into anything else but developer friendly, but still, you should've known better than asking another developer that.

Related

[KERNEL]HydraCoreNirvana n16[ENDED]

Although this kernel is ended. I think I should put the downloads here:
http://sourceforge.net/projects/maxfuacm/files/Kernel/HydraNirvana/GT-N7000/
Critical Remind:
Flashing this kernel will make your phone Lose Warranty. So please Fully Get Understand of what you are doing. I have no responsibility of any of your lose by flashing this.
Before you download and flash, to farthest avoid bootloop or bricking your phone, please make sure you have read and understand sections from 4 to end.
Please be wisely use the "search this thread" at the top right corner, if you can not see it, click
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
there. And be sure you have already read the OP. New-asked-but-already-answered questions will be ignored and maybe disliked or even scoffed by other members.
I will never talk about ETAs (Estimated Time of Arrival). So please save your keyboard or touchscreen.
Please forgive me if I did not answer your question, even you asked before some one I answered. Please informe with message if you need me to answer it. Although I can not guarantee I will answer questions promptly, the carefulness of the answers is guaranteed. If the answer is important to you, please bookmark it cause I may edit the answer post with update instead of posting another one.
And if anyone don't like any part of my word. Please send me a message instead of posting here. All words above are my begging for the nattiness of this thread. I won't open another thread of discussion, cause I saw the discussion theads were mostly useless. Holding one thread is easier.
Thanks to:
@g.lewarne, @hardcore, @chandler929, @Formhault, @androidindian, @noteandfound, @chasmodo, @TeamHacksung, @samsung, @CyanogenMod team, ......,
and a lot of names to add.
Brief:
First, I would like to thank the people I mentioned and not mentioned in section 2. Notably g.lewarne, you are always the owner of HydraCore. Thank you for your great work. Galaxy Note now became a legend with your masterpiece.
Secondly, I would like to thank all people who gave me support, encourage and advise. Under your help, HydraCore has became a really universal and almost perfect kernel.
In this new thread, the legendary Universal Kernel has a new name -- HydraCoreNirvana. I think the word Nirvana can tell the story of HydraCore. With the new name, the kernel steped onto a new stage -- bootable on JB leaks. It is not fully functional, but it is a good beginning.
I have to say that I am not a dev. And I am another Child's Slave who use lavatory time as off hours. I really don’t know how far I can go on this. So please, forgive me if someday I got stuck and be absent like Gavin.
......long after n6......
For a long time I kept absent. I really found it hard to go on especially after the CM team upgraded the Mali driver. I am not the right guy to do the library job. So I switched to Samsung Opensource codes.
The first thing I did was building the Speedmod. I succussed. Meanwhile I made a build with Speedmod kernel image and PhilZ touch recovery initramfs. These builds worked fine with new released TouchWiz Jelly Beans. However, the CM code is going away with the Samsung Opensource codes. There are too many differences between them. The HOME button key issue was one result of this. It is harder and harder to combine CM and TouchWiz in one kernel. It is not just an universal initramfs, the kernel image itself needs to be universalized.
So I have to make a lamentable decision that from now on, I will stick with Samsung Opensource codes. So TouchWiz Jelly Beans will be supported prior to CM and other AOSP roms which have good enough kernels. Legacy features of HydraCore will be transplanted to the new builds one by one with careful test. CM and other AOSP roms maybe bootable with the new builds, but the functionality will not be guaranteed.
At last, thank you all for your long time support. I will keep on building this kernel and try my best to keep it Hydra for everyone. But for now, I can only step on one side, and I choose TouchWiz.
......more to add......
Technical Description:
Safety: mem_cap_erase disabled, so this is a safe kernel.
ROM Support:
ICS (4.0.X):
TouchWiz Based: TouchWiz ICS fully supported. Official MIUI still can not boot to system, adb works.
AOSP Based: CM9 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.1.X):
TouchWiz Based: TouchWiz JB, MIUI made by TWJB + Patchrom from http://www.miui.com/extra.php?mod=download/rom&fid=133 fully supported.
AOSP Based: CM10 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.2.X):
TouchWiz Based: Not out even leaked yet
AOSP Based: CM10.1 has bootloop with display.
Recovery: CWM 6 non touch recovery from @Phil3759: http://forum.xda-developers.com/showthread.php?t=1927097.
Root privilege: ADB and LBE superuser.
Usage:
Place the ZIP in the TF card.
Root the phone: If you and if you are sure that you have a safe kernel with CWM jume to next. If you phone is unrooted, Flash the TAR version in Odin to get Root and CWM.
Now you may meet bootloop, Press UP + HOME + POWER until you see the CWM interface. (the phone will never boot to the system with a stock rom flashed a TAR version)
Flash the ZIP in CWM.
Enjoy
Please don't ask me how to use CWM. If you don't know, don't flash any kernel.
Download with Changelog:
Instructions:
These are SourceForge folders, so open in a browser. The corresponding source is included in the same folder.
Not all releases will be kept in this post, find the old ones in the repository. I will keep all files as long as possible. (It seems SourceForge don't delete old files.)
Little trick: maybe you can try middle-click the links, a new tab maybe opened.
Notice: If you met black screen or bootloop after flashing the tar file. Try the zip package (The recovery should be working). The standalong Mali libraries might fix the problem.
n16:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n16/
Changelog:
Kernel: Pushed kernel version to 3.0.83.
Defconfig: Reverted pmem settings to fix video overlap. The bug is reported fixed.
Defconfig: Reenabled Samsung MTP. The hang of the MTP software on my MIUI v5 TouchWiz Patchrom fixed.
Makefile: Brought more legacy HydraCore tweaks including cpu and fpu tweaks.
n15:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n15/
Changelog:
Kernel: Pushed kernel version to 3.0.82.
Network: Fixed wifi tethering.
Audio: Fixed mic in software like talking animals, recoders, etc.
Mali: Tweaked thresholds to reduce lag on some heavy interface like MIUI desktop. Further tweaks may be needed.
Tweaks: Some small tweaks.
Platform: Switched to coLinux. Now it is ideal for me. It is a real linux like vmware, it uses less resource like cygwin, and it is fast like a directly installed linux.
Toolchain: Switched back to Linaro 4.7 with LTO.
n14:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n14/
Changelog:
Kernel: Pushed kernel version to 3.0.81 with cma port.
Superuser: Switched to LBE superuser with some simple permission management.
Defconfig: Brought more legacy HydraCore options which may be not noticeable.
HydraFS: Some workaround to MIUI. Now official MIUI v4 can boot to adb, positive. But the system is still not usable.
Platform: Switched to cygwin.
Toolchain: Switched to cygwin 4.6.3.
Filename: Yes, X.Y.Fu is still me, it is my name in short.
test builds:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Testbuild/
These builds are test builds. They usually contains new features or fixes. These changes need test. Read the README file in folders for more information.
build environment:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Platform/
Just follow the readme file.
TODO and TOFIX:
Add Multi-ROM-on-SdCard support.
Investigate the reason of the CM10 and CM10.1 failure boot.
Make MIUI v4 bootable. Fix CM boot problems.
AOSP MIUI JB support.
Bring back more HydraCore features.
Bring ability to set GPU frequency. This is extremely hard to me.
Bring ability to set CPU voltages. Found the location of the settings. Working on it.
Bring more ability to alter the kernel without reflash.
Tweak all the script included.
Study on offcial source code of JB.
64GB cards. I am not sure. 64GB exceeds Fat32 limitation. and exfat is not supported correctly.
Vibration Strength not alterable on AOSP roms. I am still working on this, maybe compile two different modules will solve the problem.
Q&A Collection:
How to flash: like I said if you don't know how to flash, then don't flash. Or you can read section 4.
Can I flash on ...?: Please get to know you rom type, AOSP or TouchWiz based, then please read section 4.
Bootloop/Freeze/..., help!: please be concrete, I can not answer questions simple like this.
Possible reasons of Black Screen: From n9, standalong Mali libraries are located in the zip. Try to use the zip package. It might fix the problem.
Possible reasons of Bootloop:
Please check your rom type see whether your rom is supported.
Another reason is the unsuppored modules. Look in to /system/lib/modules if it exist. And delete dhd.ko, j4fs.ko, scsi_wait_scan.ko and Si4709_driver.ko if they exist. Deleting dhd.ko may also fix WIFI problem.
Possible reasons of Lag: Check the governor and IO settings. Or maybe just clean the RAM. At last, reboot.
Possible reasons of Freeze: Usually happens after a heavy load work. Try to reboot. Reboot usually works.
...adding...and...collecting...
Old Versions:
n13: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n13/
n12: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n12/
n11: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n11/
n10: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n10/
n9: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n9/
n8: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n8/
n7.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n7.JBT/
n6.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n6.JBT/
n5.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n5.JBT/
n4.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n4.JBT/
n3.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n3.JBT/
n2.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/6th_v7.6.JBT/
n1: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/5th_v7.6.2/

Great maxfu. You have a lot to say and we'd love to listen
Sent from my GT-N7000 using Tapatalk 2

Finally...
ANG.MAHAL.NG.NOTE.KO

maxfu said:
My sixth compilation with experimental TWJB leak support:
https://sourceforge.net/projects/maxfuacm/files/Galaxy Note/MaxFu_HydraCore/v7.6.JBT.1/
Click to expand...
Click to collapse
Seriously? We can finally OC the jb leaks? AWESOME!!!

I guess cm10.1 kernel is next?
ANG.MAHAL.NG.NOTE.KO

It's fantastic, thanks man.

Thanks man a new life for our great Hydracore..............

Another awesome release from Maxfu
thanks man.

Will it really work on JB Leaks ???
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )

Immortal Nerd said:
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )
Click to expand...
Click to collapse
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.

Haints said:
Seriously? We can finally OC the jb leaks? AWESOME!!!
Click to expand...
Click to collapse
Yes, you will have OC. But camera maybe gone.

maxfu said:
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.
Click to expand...
Click to collapse
Is there any critical problems in the sixth compilation for leaked jb? If not, I well flash this right away
Edit : so the camera is break in the latest kernel? Hmm alright I think I will wait for the next compilation really great work maxfu, thank you for make the hydra core can run in leaked JB :good:

XXLSC Wait,.,
Sent from my GT-N7000 using xda premium

Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462

Should be. But not on CM 10.1
cuba462 said:
Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462
Click to expand...
Click to collapse

Hi maxfu. The original HydraCore 7 is unsupported by the awesome jellybam. This would be?
Sent from my GT-N7000 using xda premium

MaxFu_HydraCore_v7.6.2_OC.zip is corrupted

capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
download it again ?

capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
Have you already checked md5?
ANG.MAHAL.NG.NOTE.KO

noteandfound said:
Have you already checked md5?
Click to expand...
Click to collapse
Oh, yeah, sure, no doubt...

Lineage OS XT907_JBBL

Lineage OS 14.1 for Moto Razr M JBBL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all!
I'm have ported LineageOS 14 for the xt907_jbbl
lineage-14.1-20170707-port-ilichva-xt907_jbbl
lineage-14.1-20170804-port-ilichva-xt907_jbbl
Enjoy.
XDA:DevDB Information
Lineage OS 14 for Moto Razr M_JBBL, ROM for the Motorola Droid RAZR M
Contributors
ilichva
ROM OS Version: Android 7.1.2 Nougat
Version Information
Status: Nightly
Created 2017-03-23
Last Updated 2017-08-05

Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?

trivialPotato said:
Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?
Click to expand...
Click to collapse
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4

ilichva said:
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4
Click to expand...
Click to collapse
Hm... Interesting... That means that a custom kernel would allow them to boot, right?

The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.

ilichva said:
The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.
Click to expand...
Click to collapse
Hm, I didn't get that, replacing the kernel would not allow them to boot? They'd need to be built from scratch?

Hello ilichva, big thanks. And what about root???

mastnacek said:
Hello ilichva, big thanks. And what about root???
Click to expand...
Click to collapse
Install SuperSU...

ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
I just found this thread. When I flashed this ROM, I installed Magisk for root and haven't noticed anything negative, but have found benefits (e.g. installing/running Viper, work around for failing init.d etc). It also appears to be the choice on other devices, in newer ROMs .
@ilichva is there any specific reason you suggested SuperSU? or is it just that you haven't personally tested Magisk?
Originally I was kind of worried that the vanilla style of Lineage OS would bug me (as I am used to ROM's with a lot of customisations). However, I have Magisk (the apparent latest way to root), V4A, a Linux Swap Partition and have Xposed the...err...heck! out of the ROM (8 Xposed modules), including "Settings Editor" which enables you to add things to the settings menu that makes the additions (eg Viper) appear like they are actually part of the ROM.:good:

ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
Thanks, works. In CM13 was supersu already. Good work.

I'm using supersu2.76 zip and install viperatmos stock5.4 and using exposed too, all working well on enforcing mode

dedik46 said:
all working well on enforcing mode
Click to expand...
Click to collapse
Do you have or are you using any boot scripts? ie init.d

DiamondJohn said:
Do you have or are you using any boot scripts? ie init.d
Click to expand...
Click to collapse
No...i didn't use init d or any script

dedik46 said:
No...i didn't use init d or any script
Click to expand...
Click to collapse
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.

DiamondJohn said:
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
Click to expand...
Click to collapse
I've never try to use any script on init.d and i don't know if init.d is working or not, maybe i will try to use magisk for the next update..

dedik46 said:
I've never try to use any script on init.d and i don't know if init.d is working or not
Click to expand...
Click to collapse
And that's what I was checking. init.d does not work in this lineage ROM, nor in another devices (Nexus 5) lineage based ROM; ie Resurection Remix on N5. I am really surprised how little attention this artifact is getting.
dedik46 said:
maybe i will try to use magisk for the next update..
Click to expand...
Click to collapse
Although not an issue for me, it has extra features such as allowing some apps that wont run on rooted phones, to have su hidden from them. I like the fact that is has pre-built modules to support extra's such as V4A. I also liked the fact that it has its own init.d functionality that I use since the ROM's init.d does not work. And it appears to be the direction newer custom ROM's are heading for root.
Really, your already thinking about the next build? I am more thinking about the method/steps I did wrong or could of done better from the flash of the last build.

Wifi issue is not only our device
Some people have noted an issue with Wifi. I too have had the issue with the wifi loosing its connection and not automatically re-connecting. even though the Wifi is available and well within range.
I looked into it a little further (created a quick app that logged numerous broadcast messages, and logged them to a file), and as part of that I also tested the "pass" situation on my spare Nexus 5 phone, also connected top my Wifi. However, it too failed! it was however better in that it didn't randomly loose the wifi.
With the N5, if I was connected to Wifi (very strong signal), went into settings, turned off the wifi. When I turned the wifi back on, it did NOT automatically re-connect.
The N5 is running a MM Resurrection Remix (one of the latest builds, based on Lineage I think)
So, It would appear that this wifi issue is not specific to our devices. I am not sure if thats a good or bad thing.
Anyway, I have my logging test app running, and like a watched kettle, it hasn't lost its Wifi connection

Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.

DiamondJohn said:
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
Click to expand...
Click to collapse
I got the recents working again.
I tried turning all my xposed modules off (including a couple that affected the navbar), but it was still failing.
Then I noticed that for the first minute or so it would work every boot, but then eventually stop. So I thought it was some installed app/config that only started later in the boot sequence. This "app" must have root to do such damage, so I went down that path. Thought it might be Magisk (since I appear to be one of the only on it). So I uninstalled Magisk, and flashed SuperSU. Still failed.
Anyway, I got it working again by turning off Super User access to all apps individually (after a restore back to my original starting point), then turning it back on (with a few reboots between). I couldn't identify exactly which caused it, but now it all works :highfive:, and I have a technique to hopefully correct it in the future.:good:

and downloading now!
http://4pda.ru/forum/index.php?showtopic=403669&st=21880#entry60269538
Thank you @ilichva:good::good::good:
-------------edit
just noticed the link is in the first post

[EOL] [OP6] [OOS 9.0.2/OB6] [4.9.136] [CLANG 7.0] Flash Kernel 2.15

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
NOTE: This kernel is currently not being updated. I recommend using Franco Kernel instead.
Hello everyone, this is my personal kernel for the OnePlus 6. While I am not a super star kernel developer, I do know my way around it. My philosophy on kernels is pretty simple:
Follow stable Linux always. Updates will be delivered within 24 hours of their release to kernel.org.
Stable kernel rules work best (only add small things when possible).
Security and stability are paramount. Vulnerabilities are patched as soon as they are disclosed.
Features will be added only as needed (I have a list of things in the FAQ I will NOT add, even if requested).
Hopefully you enjoy
Important thread information!
I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Keep things civil, I do NOT tolerate flaming of any kind.
OT is allowed.
Features
Here are the major features of the kernel (feel free to explore Github)
Up to date with OxygenOS 9.0.2/Open Beta 6
Up to date with the latest stable Linux version (4.9.136)
Up to date with the latest Qualcomm changes (LA.UM.7.3.r1-05900-sdm845.0)
Power efficient workqueues enabled by default
Westwood as the default congestion algorithm
Latest WireGuard snapshot (0.0.20181018)
Sultanxda's boost driver (smooth experience while still staying sane on battery)
The following user facing features:
KCAL color control
Minimum backlight control
Sound control
Wake gestures (thanks to @flar2)
Vibration control
Built with a self compiled Clang 7.0 toolchain with a local initialization sanitizer
Attempts to hide bootloader unlock from SafetyNet (can still fail through other means)
Available to flash with AnyKernel2 (thanks to @osm0sis) [zip will automatically detect when Magisk is installed and patch the kernel so reflashing Magisk becomes unnecessary]
Downloads
Primary: https://github.com/nathanchance/op6/releases
Installation
NOTE: These sets of steps should work for both initial installations and upgrades. All sane kernels on this device are just replacing the kernel image and maybe adding some cmdline parameters, which this kernel won't care about. If there are ANY issues after flashing this kernel over another, be sure to flash the stock boot image for your ROM, TWRP + Magisk if you want them, then the kernel before reporting any issues.
Through TWRP:
See their instructions for further information, you can install the kernel with TWRP temporarily booted or permanently installed.
Boot into TWRP.
Flash the zip (flashing Magisk is not necessary if you already have it installed).
Reboot and enjoy!
Through FK Kernel Manager (requires root):
Download the zip (and optionally, the md5) from my server
Tap on "Manual flasher"
Navigate to Download
Tap on the zip, select Auto-flash, and choose one of the options.
Reboot and enjoy!
Changelog
Latest release post!
Commits
Frequently asked questions
1.1 Q: I am having an issue, can you help me?
1.1 A: I am not an amazing kernel developer but I will certainly try my best. First, start by reading the release posts, as I may make note of a particular issue. Also search the thread to see if I have discussed it before. If you see nothing, please provide me with a dmesg/last_kmsg and logcat, your ROM/kernel version, and a detailed description of the issue, following this guide. If I can't reproduce reliably, I'm not going to fix the issue.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not go digging super hard for commits and I will ignore requests that don't include this information. I won't promise that I will merge every request but I will always take it into consideration. I will NOT add the following:
Overclocking or underclocking of CPU or GPU
Undervolting
Any governors other than schedutil
Any schedulers other than cfq
Anything that compromises performance
1.3 Q: How do I control the kernel?
1.3 A: I want to be very clear: the kernel does NOT need to be tuned to be useful. Most of the improvements are under the hood and don't require any user intervention to take advantage of them. In fact, if you don't know what you are doing, you could degrade the experience.
To control the user visible features of the kernel listed above, I recommend using either @franciscofranco's FK Kernel Manager (which has Flash Kernel support for downloading and automatically flashing the latest kernel zip along with some nice, user friendly ways for tuning the kernel) or @flar2's EX Kernel Manager.
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery, use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
OnePlus for the device through their developer program
The various other developers for their patches (specifically @zx2c4 for WireGuard)
@osm0sis for AnyKernel2
@franciscofranco for adding Flash Kernel support to FK Kernel Manager
@phantom146 for the thread banner
All of you guys for viewing the thread
A note about donations
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Kernel source links
8.1 (OxygenOS 5.1.5+): [url]https://github.com/nathanchance/op6/tree/8.1[/URL]
9 (OxygenOS OB1+): [url]https://github.com/nathanchance/op6/tree/9.0[/URL]
DISCLAIMER: I openly welcome off topic in my threads. Mods, please do not clean off topic discussion and users, do not complain about off topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.

Reserved

Good to have you here! Been a Fan on the 5T!

Yay, favorite kernel!! Thank you Nathan!

Mine!

nathanchance said:
Follow stable Linux always. Updates will be delivered within 24 hours of their release to kernel.org.
Click to expand...
Click to collapse

Woot ?

Oh yes! U are here! Missed you since I sold my pixel 2 xl

mgear356 said:
Oh yes! U are here! Missed you since I sold my pixel 2 xl
Click to expand...
Click to collapse
Sold mines too, but the pixel 3 looks beautiful. They keep trying to take my money lol

Great to see you. Welcome on board Nathan
Sent from my ONEPLUS A6003 using Tapatalk

Great to see you here!

can it be flashed on 5.1.6?

Awesome to see your kernel here buddy!!!
Sent from my OnePlus6 using XDA Labs

tbalden said:
Great to see you. Welcome on board Nathan
Click to expand...
Click to collapse
Glad to be here, I'm glad you got up and running
Muntasir Mahmud Saif said:
can it be flashed on 5.1.6?
Click to expand...
Click to collapse
Well... The title says 5.1.6 and the OP says it's up to date with 5.1.6 so... Yes, it can be flashed on 5.1.6 lol.
Sent from my Pixel 2 XL using XDA Labs

Thanks, runs nicely on my op6

The Best kernel is here!
Enviado desde mi ONEPLUS A6003 mediante Tapatalk

nathanchance said:
Glad to be here, I'm glad you got up and running
Well... The title says 5.1.6 and the OP says it's up to date with 5.1.6 so... Yes, it can be flashed on 5.1.6 lol.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I'm extremely sorry bro..i didn't see that.. extremely sorry to bother you..

It is a pleasure to see you here too!

nathanchance said:
Glad to be here, I'm glad you got up and running
Well... The title says 5.1.6 and the OP says it's up to date with 5.1.6 so... Yes, it can be flashed on 5.1.6 lol.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
but..... are you absolutely sure?
:silly:

@nathanchance Your signature needs to be updated to include OnePlus 6 alongside all the others
Edit:
Word.

[ROM][8.1][UNOFFICIAL][MP260&TP260] LineageOS 15.1 for LG K20 Plus

Changelogs:
2-6-2019
Fixed reboot recovery and 2D gaming issues

Travis, Try this Apn_Conf I had way more stable data and ip6
https://www.dropbox.com/s/3xramb2cbkq7gas/apns-conf.xml?dl=0

New build is up with reboot to recovery and 2D gaming fixed

Aw man.
Good to see the official thread take off!

@Travisholt92 unless I'm doing something wrong when trying to play a couple games (Idle Hero's being one) it won't allow me to play Via data it won't connect unless I'm on Wi-Fi? I can get a log but just wanted to let you know also if anyone wants what seems to help data a bit including faster switches from 3g to lte after calls try flashing this
https://www.dropbox.com/s/rak3v7mc6it4vqm/Apn_and_More.zip?dl=0
Also cleaned up build.prop and added some tweaks to it
---------- Post added at 05:51 AM ---------- Previous post was at 05:44 AM ----------
Also posted in your 7.1.2 thread that Magisk 16.0 doesn't freeze up

hawknest said:
@Travisholt92 unless I'm doing something wrong when trying to play a couple games (Idle Hero's being one) it won't allow me to play Via data it won't connect unless I'm on Wi-Fi? I can get a log but just wanted to let you know also if anyone wants what seems to help data a bit including faster switches from 3g to lte after calls try flashing this
https://www.dropbox.com/s/rak3v7mc6it4vqm/Apn_and_More.zip?dl=0
Also cleaned up build.prop and added some tweaks to it
---------- Post added at 05:51 AM ---------- Previous post was at 05:44 AM ----------
Also posted in your 7.1.2 thread that Magisk 16.0 doesn't freeze up
Click to expand...
Click to collapse
Yeah that data issue is related to ipv6 not allowing full network connectivity. Change that to ipv4/ipv6 in your APN and you'll be golden. It's something kernel related preventing full IPv6 connectivity. I'll check out your build.prop tweaks though. I plan to change the built-in APNs to address that issue until I can get that issue resolved. I probably won't work on debugging that until Pie since its not quite a high priority issue.

I installed the mentioned game just to make sure that was the issue. Loaded up just fine over LTE with ipv4 enabled

Dirty flashing from a previous Oreo build to 2/7 will likely result in a bootloop if you had magisk installed. You will need to reflash magisk and possibly gapps to resolve this issue. Its because I changed the filesystem type for certain partitions from ext4 to f2fs for a slight performance boost.

Travisholt92 said:
Dirty flashing from a previous Oreo build to 2/7 will likely result in a bootloop if you had magisk installed. You will need to reflash magisk and possibly gapps to resolve this issue. Its because I changed the filesystem type for certain partitions from ext4 to f2fs for a slight performance boost.
Click to expand...
Click to collapse
Lol, sure after I find out the hard way

hawknest said:
Lol, sure after I find out the hard way
Click to expand...
Click to collapse
Sorry about that lol
I'm going to revert those changes since they were personal preference but the change won't affect users that had issues installing the most recent build.

I am not sure what's up, I've flashed 2/9 a bunch and just bootlooping.. Clean install and fresh magisk flash
EDIT: Tried a few more times and no go.. I'll wait for the revert

I'm starting to think people don't know this thread exists yet

hawknest said:
I am not sure what's up, I've flashed 2/9 a bunch and just bootlooping.. Clean install and fresh magisk flash
EDIT: Tried a few more times and no go.. I'll wait for the revert
Click to expand...
Click to collapse
Revert build is up under the same name as yesterdays build with yesterdays build renamed to the proper date. It will work with ext4 and f2fs now. Its likely your issue was from cache being formatted as EXT4 which yesterdays build didn't support, today's does.

hawknest said:
I'm starting to think people don't know this thread exists yet
Click to expand...
Click to collapse
Me too lol. Once I get a new screen I'll get a YouTube video up with a side by side comparison between lineage 15.1 and stock. Should make for a very enlightening video.

Travisholt92 said:
Sorry about that lol
I'm going to revert those changes since they were personal preference but the change won't affect users that had issues installing the most recent build.
Click to expand...
Click to collapse
imma slap it on an give it a whirl ... uhhh...any way you could mix in magisk like with RR .. i can flash a backup...maybe
just wondering? i can take no for an answer
and i canT find the LIKE button.....serious
i've looked over the OP 10+ times...

Cyconumnum said:
imma slap it on an give it a whirl ... uhhh...any way you could mix in magisk like with RR .. i can flash a backup...maybe
just wondering? i can take no for an answer
and i canT find the LIKE button.....serious
i've looked over the OP 10+ times...
Click to expand...
Click to collapse
I can but won't for users who for some reason prefer SU, but magisk installer is baked into PBRP so close enough right? Lol also a new build is being uploaded now with overall performance improvements. Maybe I'm just crazy but even networking seems faster on 2/08. Should be up in about an hour. I'm off to bed now. Enjoy the super fluid 2/8 build.
Its a thumbs up lol

Going to need help testing something that everyone wants ??

hawknest said:
Going to need help testing something that everyone wants ??
Click to expand...
Click to collapse
Obviously I'm up for it. Lol.

reboot to recovery :good:
just flashed the 2/8 build 20-30 minutes ago, all is great so far.

[CLOSED] [Kernel] [Custom ROM] [Singularity-Kernel-V-1.0.9] [4.19.279] [OnePlus 8 Series/9R] [Android 13] [3/29/2023]

It's simple. I threw together this kernel out of necessity for micro lag fixes and better battery life.
Please expect only necessary updates.
If you have an issue, please provide a detailed report and please provide a logcat
Enjoy.
V-1.0.9 Zip download link = https://www.androidfilehost.com/?fid=4279422670115732041
V-1.0.9 Boot Image download link = https://www.androidfilehost.com/?fid=4279422670115732040
##################################
OP9R BUILD/ZIP only
OP9R-V-1.0.9-ZIP = https://androidfilehost.com/?fid=4279422670115732053
the boot.img is not pre-rooted. Please use the zip to remain rooted.
Kernel Source = https://github.com/APOPHIS9283/Singularity_Kernel

apophis9283 said:
It's simple. I threw together this kernel out of necessity for micro lag fixes and better battery life.
If you use Evolution-X this will break Fsync toggle as I opted for Dynamic Fsync instead. Past that you tell me.
Please do not expect a ton of updates.
If you have an issue, logcat or GTFO.
There is no Telegram link.
Enjoy.
Zip download link = https://www.androidfilehost.com/?fid=4279422670115706910
Boot Image download link = Coming soon.
Kernel Source = https://github.com/APOPHIS9283/Krieg_Kernel/commits/13
Click to expand...
Click to collapse
Been using this for a while and very happy with performance..

Works smooth like a criminal

Thanks for release.
Running on OOS 13.
I missed custom I/O schedules & TCP algorithms.
Great to see that you had set Zram compression to zstd algorithm.
Cannot wait to see your next release !

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ty dev for the kernel. Kernel is fine overall but scrolling performance could be a bit better.

Which device is your evo_defconfig for ?
I'm new to kernel building, just wondering .

hightech316 said:
Which device is your evo_defconfig for ?
I'm new to kernel building, just wondering .
Click to expand...
Click to collapse
This was actually an idea I had using EvoX for OP8T.

efx7n said:
View attachment 5798177Ty dev for the kernel. Kernel is fine overall but scrolling performance could be a bit better.
Click to expand...
Click to collapse
Thats probably because I use 300HZ timer interrupt frequency which I have no issue bumping to 1000HZ which Ill drop tomorrow for you all, along with a few minor changes.

I have updated the kernel. Addressing issue brought forth in the comments.

My camera doesn't seem to work . Everything else is doing great!
OOS Cam and Open Cam .
Running latest OOS13 stock .
Attached log.

hightech316 said:
My camera doesn't seem to work . Everything else is doing great!
OOS Cam and Open Cam .
Running latest OOS13 stock .
Attached log.
Click to expand...
Click to collapse
I missed that you were running stock. I probably should've mentioned that. This was only meant for custom ROMs. I am truly sorry I overlooked saying that.

Can u please try to add support for 9r. Coz both 8t and 9r are the same. Just some minor changes ig.

apophis9283 said:
I missed that you were running stock. I probably should've mentioned that. This was only meant for custom ROMs. I am truly sorry I overlooked saying that.
Click to expand...
Click to collapse
No worries .
OnePlus released their OOS13 kernel .
GitHub - OnePlusOSS/android_kernel_oneplus_sm8250 at oneplus/sm8250_t_13.0.0_op8
Contribute to OnePlusOSS/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
How big of a pain would it be to take the blobs ( if that is even what is needed ? ) From that release onto yours ?
Or are they completely different and non compatible since one being AOSP and other OOS?

projektx said:
Can u please try to add support for 9r. Coz both 8t and 9r are the same. Just some minor changes ig.
Click to expand...
Click to collapse
This was based off EvoX's kernel. If they use it for the 9r as well it should work, but if it doesn't. Sure when I get time, I'll peek at it. The zip probably would fail but the boot.img would be fine. Just have a backup to flash if it fails.

Always nice when you pop in and bless us with some butter. Running great and thanks for your work as always

Does it work on OnePlus 8 Verizon (IN2019)? I am on Kaleidoscope Rom (Android 12).

Zombify01 said:
Does it work on OnePlus 8 Verizon (IN2019)? I am on Kaleidoscope Rom (Android 12).
Click to expand...
Click to collapse
Yes, I ran it on the IN2017 T-Mobile OnePlus 8 and it worked.
Unfortunately, I got rid of it because, as mentioned in the thread, FSync was replaced with Dynamic FSync. This prevents you from losing data if the screen is off, but not when it's on.

hammerhaigh said:
Yes, I ran it on the IN2017 T-Mobile OnePlus 8 and it worked.
Unfortunately, I got rid of it because, as mentioned in the thread, FSync was replaced with Dynamic FSync. This prevents you from losing data if the screen is off, but not when it's on.
Click to expand...
Click to collapse
EDIT: use the boot.img and not the zip, the zip enables dynamic fsync
Fsync is enabled always, it only syncs while screen off if you enable it. Dont touch dynamic fsync and it remains as fsync on as always.
Im also testing a twrp build I made for oos13 firmware a13, all partitions should mount. EROFS. I dont keep up with everyones work, I dont think theres a recovery yet that has that possibility but I could be wrong.

Must be on op8t f15 firmware with a rom that uses erofs. You should be able to mount all partitions. If you want to test, you can get with me on telegram. I am only using TG due to the nature of this.
Testing twrp
t.me
Also heres v-1.2 of the kernel boot.img only not pre-patched

apophis9283 said:
Must be on op8t f15 firmware with a rom that uses erofs. You should be able to mount all partitions. If you want to test, you can get with me on telegram. I am only using TG due to the nature of this.
Testing twrp
t.me
Also heres v-1.2 of the kernel boot.img only not pre-patched
Click to expand...
Click to collapse
Only OOS atm? Pretty sure the evoX filesystem isn't erofs.

Database Develop

welcome