Hello,
i am using lagfix on my nexus s. But by default , only /data partition is selected for trim command.
Can i check /system and trim it also safely without bricking or any other issues?
secondly.. the /cache partition is disabled altogether.. and i get a prompt that the /cache partition isnt supported due to hardware or due to the limitations of the kernel on the device. So my query.. whats the limititation? the h/w or the default cm10 kernel? is there a kernel that i can use so as to get trim to run on /cache partition? is it possible..
please share your opinion.
my nexus s seems to start lagging a lot . i want to bring it back to life.. any proven suggestions would be appreciated.
Thanks so much XDA community.
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
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,
I am now using F2FS for the data and cache partitions of my Nexus 5.
my kernel is blu_sp★rk r56
my rom is Cataclysm
Everything is OK and my Nexus 5 is snappier!
BUT, from time to time, the /data partition becomes read only... which causes the crash of lots of applications. Most of the time, this happens during the night and I notice it on the morning. This never happened when the /data partition was ext4.
What could be the cause of this problem? How to investigate it?
Thanks in advance for your help !
Phyl
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.
Anyone tried F2FS with android 9?
Wondering how it performs in our phones and if it's reliable enough
I used to try it on my old Nexus 7... Memory flash on it was very slow and using f2fs the tablet performed really well.
In those days you needed a capable kernel and ROM to use f2fs in /system e /data partition