So you format cash from recovery?
Thanks for sharing! Funny how the raw MB/s and IOPS do not differ significantly but app startup times do. Is that coincidental and down to timing (eg. phone was checking email when doing the ext4 run) or something you can confirm having used the f2fs-formatted phone a day or two?
Is cash a common slang for cache? This is giving me a headache to read
Is cash a common slang for cache? This is giving me a headache to read
Hi,
what do you think about the necessity to PIT our phone? There is a commit in Gerrit http://review.cyanogenmod.org/#/c/133047/ that reduces the size of the ROM from approx. 445 MByte to 410 MByte. I assume that in this case the Pico GAPPs would again fit into the normal partition size of 512 MByte. But at the cost of almost all animated screen backgrounds, no sound recorder, no screencast and some other things.
Is it worth it?
@Klaerchen
I don't see the need for such a commit at all any longer, after @Lanchon made repitting that easy.
If only there was a powerfull recovery already in the CM Stock to make use it. The most complex action in repitting today is., to make the user find a way to have the requiered prerequisites and maybe to name the zip accordingly.
On the other hand, it would be possible to even make the resize prozess a part of the nightly flash process itself, beeing called on every flash of a CM13 nightly, but only increasing system by 100MB if running on stock partition layout.
But as long as we get nailed down to a CM-recovery it is useless to think about a progress like that.
I tried editing build.prop to have multi user but i've encountered force stop on the apps some only worksThe ROM now supports f2fs in /data and /cache. You'll need a recovery that can format in this filesystem or use a command like this in adb shell:Of course, mount /system first because that's where the mkfs.f2fs tool is locatedCode:mkfs.f2fs -l f2fs /dev/block/mmcblk0p7 (that's for /cache) mkfs.f2fs -l f2fs /dev/block/mmcblk0p10 (that's for /data)
If the question is about multiuser, no it's not supported on physical sdcards, only on emulated, so we don't have it
Why not?can we make dirty flash over 20160222 to 20160224 & any other step to do or not please suggest .
Sent from my GT-I9100 using Tapatalk
from 20160205 to till now i have dirty flash 3 times and no problem till now. i asking bcouse that any change in sdcard read write permission on 20160224 build that affect the any apps.Why not?
But hey: this is nightly, not some Samsung original ROM ... playing with nighly means: expect that major things are not working! For me that means: have a nandroid, check the new ROM immediately and just go back if there is a problem. I am still on 8/2 because all my attempts to update were not successful so far (gapps and titanium backup issues). (Got 2 nandroids waiting on my phone for further testing - well most likely I'm just deleting them and start from scratch ...)
You never need to ask questions like this, rather just test, report and make sure to be able to go back ...
generally I am not a fam of dirtyflashing because it is not so much effort to do it right and if something goes wrong with dirtyflashing you always need to ask if the reason was dirtyflashing ...
Regards
Sent from my x-phone using brain 2.0
Anyone want to tell me what the fascination is with mixing different filesystems on a phone with known issues with filesystems already is?
Sure, when you put it like that...Same as using an OS in "nightly" state for abandoned and old smartphone : fun
#include
/*
* 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 ROM
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/