is it possible to boot omnirom from emmc of the compute module 4 ?
thanks
Related
http://code.google.com/p/synergy-kingdom/wiki/WhatIsGodMode
Looks like it yields really good results
You call request features over on the issue tracker. Not sure if it would make it into 7.1 though.
Sent from my T-mobile G2 using Tapatalk
Sorry but where can I find the issue tracker lol I looked around but didnt see anything that jumped out at me
LOL. No, this wouldn't help.
First off, this is strictly for devices with an MTD storage chip. We have eMMC. eMMC incorporates wear levelling automatically, and takes the extX partition straight up. If you look at all the I/O benchmarks of HTC VISION and compare them with GN1, you'll notice that the Vision blows the GN1 out of the water. That is because the function of the yaffs partition in your link is built in to the eMMC chip already!!! Nothing to gain by adding a crazy layer of uselessness!!!
What this sillyness does is it keeps the base MTD partitions formatted as yaffs2 partitions (because you can't partition an MTD device using a conventional filesystem). It then creates a single file in each of those filesystems and formats that FILE as an extX filesystem, then loopback mounts those to the usual places.
What we do with eMMC is we just format the eMMC partitions to extX straight away and mount as normal.
Reading more on F2FS trying to formulate a plan of attackx. Latest TWRP 2.7.1.0 is able to repair/format F2FS partitions, so I'm covered there before installing a ROM.
Some ROMs have the boot.img fstab files mount just /data as F2FS (like a Moto X). Others mount all partitions as F2FS (haven't found any threads comparing benefits of doing all vs. just /data)
/META-INF/Com/Google/android/updater-script needs to be modified to format and mount the appopriate partitions as F2FS.
So for a phased approach, say getting toes wet with just setting up /data for F2FS, is it just
1) editing the ThunderKat_manta-KTU84M-20140607.zip boot.img fstab and changing
Code:
/dev/block/platform/dw_mmc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,
data=ordered 0 0
to
Code:
/dev/block/platform/dw_mmc.0/by-name/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,
data=ordered 0 0
2) editing the ThunderKat_manta-KTU84M-20140607.zip /META-INF/Com/Google/android/updater-script so that it will now do a destructive format of /data to F2FS
Code:
format("f2fs", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/userdata", "0", "/data");
3) doing the install from TWRP?
Am I on the right track? Miles off?
If I'm on the right track, what's required to do all partitions as F2FS? Would I have to put the ROM to be installed on a USB stick via USB OTG so that the recovery could find it after all the formatting?
I've been messing with this today and so far, I'm getting permissions issues quite possibly related to SELinux. Issues with SELinux relabeling issues are not allowing writing on F2FS partitions...
EDIT: Confirmed my suspicion that it was SELinux related. Attached screenshot shows CM11 4.4.3 with ThunderKat kernel and data partition mounted as F2FS
Just an idea cause it's so convenient: On my N7 there's an app called "Convert to F2FS" - Play Store. It converts ANY rom to f2fs. It also works for N4 & N5's. Dev states that he'll add other devices if contacted. It works brilliantly & is about a buck & 1/2. It doesn't work on 4.4.3 yet tho
Sent from my Nexus 7 using Tapatalk 2
Hi Craig,
will the latest ThunderKat still fail due to SELinux relabeling if installed on F2FS? Would a tool like this one make a difference?
http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
craigacgomez said:
I've been messing with this today and so far, I'm getting permissions issues quite possibly related to SELinux. Issues with SELinux relabeling issues are not allowing writing on F2FS partitions...
EDIT: Confirmed my suspicion that it was SELinux related. Attached screenshot shows CM11 4.4.3 with ThunderKat kernel and data partition mounted as F2FS
Click to expand...
Click to collapse
vprasad1 said:
Hi Craig,
will the latest ThunderKat still fail due to SELinux relabeling if installed on F2FS? Would a tool like this one make a difference?
http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
Click to expand...
Click to collapse
I haven't tested this yet with the new release. Will do so this weekend.
Sent from my Nexus 5
craigacgomez said:
I haven't tested this yet with the new release. Will do so this weekend.
Sent from my Nexus 5
Click to expand...
Click to collapse
FYI latest TWRP 2.8.0.1 does not have F2FS format in wipe, whilst it is in the 2.7.1.0.
Hi guys,
Having a real problem with Link2SD and was hoping you could shed some light on what i'm doing wrong.
I'm consitently gettiong the following error:
"Mount script cannot be created.
mount: mounting /dev/block/vold/179:66 on /data/sdext2 failed: Invalid argument"
Specs:
-Samsung S4 i9505 international
-Rooted and running Antaresone & Alucard CM12 2015013 ROM
--Sandisk 64Gb class 10 Sd Card
-Partitioned with minitool as follows:
-60GB fat32 partition (primary)
-4GB Ext4 parition (primary)
I've tried using ext2/3 and 4 for the second partition to no avail, and I haven't been able to get link2SD to work on any of the previous builds of Antaresone & alucards Optimised Cm12 ROM builds.
Is this not supported by the ROM/phone or am i doing something stupid?
Any help would be greatly appreciated!
Bump in the name of my Sd card woes and sanity
Sorry for the desperate bump, but can someone even go so far as to confirm wether link2sd works on antaresone CM12 build?
So based on my experimentations, I have concluded that to use adoptable storage with no bugs or errors as such you won't be able to access sd card because the random bug appears out of nowhere, is that you only have to follow these 3 steps;
1. Use latest stock kernel of lineage os,
2. Micro sd card i/o scheduler is to be set as "noop"
3. Enable sdcardfs with the help of magisk module
To set I/O schedulers use the kernel manger.
To enable sdcardfs here is a procedure https://forum.xda-developers.com/apps/magisk/module-enable-sdcardfs-t3603375
I have tested with other kernels but it causes a problem to install big playstore apps like more than 100mb where it doesn't get installed with the adoptable storage that's the only issue but the bug which I mentioned earlier does not appear.
And I'm using nougat based os.
This is specific to regard of Redmi Note 3 and maybe it will work in other devices if you have a problem as specified above.
A while ago I started following the LOS 17,1 thread and saw a post about the storage reading speeds and was amazed how fast it was because when I did the test on my klteduos it only reached about half that speed.
What file system for each partition + external SDcard do you recommend for optimal performance? All internal to F2FS instead of Ext4?
I'm planning on upgrading to LOS 17.1 (and later 18) in case that's important. See my attached screenshots below.
I'm referring to this thread:
[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants
Edit: FYI the LineageOS S5 klte family maintainer created a new thread here: [ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*) *** #include "std_disclaimer.h" /* * Your warranty is now void. * * I am not responsible for bricked...
forum.xda-developers.com
I don't think your external SD card would be close to internal memory speed even if you format it to EXT4 or F2FS.
I have Data formatted to F2FS and the phone loads apps much faster compared to EXT4 (as far as I can tell). If I recall correctly, you cannot use F2FS for system partition, because it simply won't boot. As for internal storage, I have it as EXFAT just to be accessible on Windows PC (I have no idea, if you can reformat it).
My phone is G900F, running latest Lineage 17.1 official build.
Reformatting is easily done through TWRP, so it's easy to experiment, just don't forget about backups (save them on your pc, if you gonna mess with Internal partition)