once i got the pixel 3 xl i got to tinkering with it, rooting, twrp, a few hacks and tweaks i do to all my phones to see if i could get more performance out of it
here are my findings coming from a oneplus 6
1. exremely poor ram management compared to my op6, redraws, apps reloading, slower app loading compared to my tweaked op6.
2. if you run decrypted data you can no longer register a fingerprint, the option is completely gone, and the screen pin can not be changed once set in settings, to change it you must delete the locksetting.db file in /data/system
3. sometimes running slow, not sure if its kernel related (i would like to think so because it sometimes becomes speedy out of nowhere) opening apps, switching apps, etc etc is slower than my op6
4. no journaling, the first phone i have ever seen to not run a journal on the file system partition, this has always been my #1 tweak when i unlock a BL - great move by google
5. notifications not appearing for google pay - or are delayed by tens of minutes eventhough the payment has gone through, i have done all the tweaks to disable battery management etc but still no go
currently i am experimenting /data partition formatted to EXT4 (if possible) since F2FS is running the encryption of a secondary partition (i believe this was a drawback of f2fs back in the day)
tweaks i have used:
editing the fstab to remove unneccessary options (i.e barrier, discard, background_gc, blockvalidity, etc)
there exists a journal on the /metadata partition - i have removed it with no consequence
edit:
i can not run /data as EXT4 - even after modifying the fstab and changing to ext4 in twrp - it returns with a corrupt error and only option is to try again or format data.
if anyone has any ideas on how to get it successfully working
yet to find a way on how to boot with /data as EXT4
keep failing boot once i edit the fstab to include EXT4 on the /data partition, and tells me to format my data before i can boot into OS
if anyone has any ideas on how to format /data as EXT4 please let me know
i have suspicions that EXT4 will run better on the /data partition
Related
Rather than making a loopback filesystem, I've been trying to reformat the data partition as ext4, but haven't been able get past the galaxy "S" screen yet (the big S on boot). Here's what I did
* Compile a kernel with ext4 and modified init.rc to mount /data as ext4.
* Reboot into recovery and format /dev/block/mmcblk0p2 as ext4.
* Reboot into download and flash the custom kernel.
It was stuck at "S" for a while, then the screen went dark, and the only thing I could do was to pull out the battery. Then I went into recovery mode and found the partition was trashed, i.e. I couldn't mount it as ext4 again. I had to format it back to rfs and restore the stock kernel to get it to boot. I have to believe that there's something other than init.rc that assumes data partition to be in a certain format. Has anyone had success on a similar task?
BTW, the same process DID work for /dbdata, but I see no visible improvement in Quadrant score...
I has a similar thing occur on my first attempt with nilfs2. Did you remove anything that would attempt to mount as rfs? I think the rfs driver will claim pretty much anything that might be rfs, so if your format left the backup FAT intact, that might be your problem. By the way, the nilfs2+user_init kernel I posted in the mimocan fix thread does support ext4 as well, and allows you to customize the mount without rebuilding your kernel.
Sent from my SAMSUNG-SGH-I897 using XDA App
Now, i know there are a *few* places in the dev section that have ext4 optimizations. But these "optimizations" are for the conversion from ext3 to ext4 without having the reformat and everything.
I've been trying (unsuccessfully) to change some of the ext4 mount flags for better speed. My problem is, everything i do in making a CWM flashable with a ext4 optimize sh script errors out with a Status 0. it doesn't even run.
But this time, i though i'd try a few things using adb shell. I got some tune2fs stuff working, so i thought i'd run an fsck on it. There isn't any fsck located on the phone. So i copied over a fsck.ext4, ran it but then got this error (and it also left my rom unuseable, but luckily i had a nandroid):
Code:
***file system was modified*** invalid argument passed to ext2 library while rewriting block inode bitmaps
.
And when doing an ls of /sbin, there isn't anything in there related to ext4, let alone ext3. So i'm wondering, why is our phone supports ext4 partitions, but doesn't actually have anything to support them?
EDIT: running just the tune2fs seems to have worked, just need to test out any differences found first.
Hey guys
Recently I've got a ZTE V970M (MT6577) phone and so far it's awesome. However, some people have been asking for a way to extend the /data partition because some games are heavy 'n stuff. That's alright.
There is a method which resizes the partitions by altering the MBR on the EMMC and that way the /data partition ends up with 2GB (from [email protected]) + 512MB (the assigned for /data), but I want to do something different, without having to edit the MBR that way. Dunno, it's fishy imo.
My idea was to format [email protected] (which comes in vfat) as ext4 and then editing init.rc and change the partition mount points from [email protected] to [email protected]
If I do that without formatting, the phone boots but it asks for an encryption key. Reading on the net, it's not asking for an encryption key, it's the fallback mode for when it can't mount the /data partition and then it believes it's encrypted, but it isn't.
If I format the [email protected] to ext4 (mke2fs -T ext4 /dev/block/mmcblk0p6), parted shows it's on ext4 and all that shiz, but the phone seems to disconnect itself from ADB once it finishes booting, and hangs in bootloop. Since I can't ADB it, I don't know wtf is going on with the phone. Something tells me I'm close to reaching the goal though.
Looking on the net I found this useful link -> http://blog.kangkang.org/index.php/archives/242 which talks about extending /data the way I want to do (for the Tegra2 one, but it shouldn't matter). However, Chinese isn't my main or secondary language (lol) and google translate does an horrible job at translating it.
So, anyone got ideas on how to extend such partition? I just want to swap the normal /data partition with the internal SDcard partition, so in theory if I format it to ext4 and swap the mount points it should work, it's just a swap, but why it isn't?
Any ideas are greatly appreciated!
Thanks in advance!
- DARKGuy
I hate bumping but, nobody yet? I've seen this being done in other phones... any ideas?
I can't believe no one has an idea yet... come on, this is XDA... wtf is up?
Yeah, I wanna know this too. If formatting the EMMC on my Note1 to anything other that the FAT32 will help?
Hi all! I'm running CM13 Snapshot, with ElementalX. As now I formatted /data and /cache in F2FS. Would it be worth to also format /system in F2FS, since is mostly read-only?
Well you simply can't, every ROM installation will re-format /system to ext4 automatically. And even if you could, you probably can't notice any improvements on the Nexus 5. The Nexus 5 still has pretty powerful hardware which can handle almost everything without any problems so I wonder why you would want to have /system formatted to F2FS. In my experience things never really got that much better with the /cache and /data formatted to F2FS, only benchmarks scores got a bit higher. In my opinion F2FS is pretty useless on this device. Could be helpful for lower end ones.
Thanks for the answer! I must say i jumped on the f2fs train without doing any benchmarks, and also going from KK to LP long time ago, so I couldn't do a proprer comparison. Also I didn't think about the rom installation process reformatting...well than my question is pretty useless
Short answer, no. From what I've read, F2FS has slightly better write speeds than ext4 and slightly worse read speed. On a partition that you write often to, such as data and cache, it could be beneficial because of the better write speed. But on the system partition, it would even cause performance drop since it's read-only.
No.
The system partition is mounted mostly with ro permissions anyway.
Write operations are few and rare.
Finally, f2fs seems to have more overhead (allocates more space) which might be an issue for devices with small-ish system partitions.
I have a Mi A2 lite (msm8953), and I am trying to boot on two different data mounts. I managed to do it by mounting user data partition as /preData then mounting /preData/second on /data on vendor partition init files, and I booted successfully.
But when going back to the /data as /data, my unlocking pattern doesn't work and I have to delete "/data/system/locksettings.db".
My question is, since the process of booting to a subdirectory (/data/second instead of /data) of the actual data does not touch the actual /data/ files at all, how did the lock process get messed up for the primary data?
My guess is there's a specific partition involved in the lock process that's being modified, if I am correct, which one is it ?