[ROM][6.0.1][I9100][OFFICIAL] CyanogenMod 13 Nightly Builds

Search This thread

rINanDO

Senior Member
Dec 17, 2009
701
4,750
I just have formatted /data and /cache to f2fs. These are the results before with ext4.
 

Attachments

  • 1456348523778.jpg
    1456348523778.jpg
    53.5 KB · Views: 1,039
  • 1456348546536.jpg
    1456348546536.jpg
    52 KB · Views: 1,014

davidcie

Senior Member
Sep 30, 2005
118
60
Warsaw
And these are the results with f2fs.
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?
 

SAMDestroy

Senior Member
Jun 18, 2015
86
30
mkfs.f2fs -l f2fs /dev/block/mmcblk0p7 (that's for /cache)
mkfs.f2fs -l f2fs /dev/block/mmcblk0p10 (that's for /data)

trying to do this via adb shell and/or isorec twrp (pushed mkfs.f2fs to sbin) and getting error=1:
"CANNOT LINK EXECUTABLE: cannot locate symbol "__register_atfork" referenced by "mkfs.f2fs"
 

souler456

Senior Member
Jan 18, 2013
1,320
627
Calamba, Laguna
Is cash a common slang for cache? This is giving me a headache to read :p

I think he pronounces cache "cash", you know, like money cash - which is correct btw, rather in my country which says "cash-ay" - which is wrong btw, or "catch-ay" - which is horribly and annoyingly wrong btw, but he just didn't want to bother changing "s" to "c" and adding an "e" because I guess he's a busy guy and ain't nobody got time for that, or something... I hope not...

:D :) ;) :good:
 
Last edited:
  • Like
Reactions: Lysergic Acid

the.gangster

Senior Member
Apr 3, 2015
955
1,374
Samsung Galaxy S7
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.

Good news for the noobs, bad news for ...decide yourself.

Hm, it looks like the commit got really merged on last 20160224 nightly build.
I am still on nightly as of 23rd. So where can I look up what features exactly will be dropped with that switch from common_full_phone towards common_mini_phone.mk.

I personally think, now after the storm of users who "accidently" updated from 12.1 to 13 has calmed down there was no need anymore for such a change. If it had been done before gaining official status (before 12.1 nighly users got offered the update to 13 via OTA), I would have understood it better, but now?

@Lysergic Acid
any comment? Maybe I got things wrong? If not: Did you get forced to do it?
And can we get Lanchon's Trim-patch commits merged in return?
 
Last edited:

BlindEyes

Senior Member
Nov 3, 2014
76
5
Vigan City, Ilocos Sur
multiple user

The 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:
Code:
mkfs.f2fs -l f2fs /dev/block/mmcblk0p7 (that's for /cache)
mkfs.f2fs -l f2fs /dev/block/mmcblk0p10 (that's for /data)
Of course, mount /system first because that's where the mkfs.f2fs tool is located ;)


If the question is about multiuser, no it's not supported on physical sdcards, only on emulated, so we don't have it :)
I tried editing build.prop to have multi user but i've encountered force stop on the apps some only works
wishing you could support multiuser in the future builds sir THanks @Lysergic Acid
 

ssandyji

Senior Member
Jun 19, 2013
167
84
Indore
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
 

daniu

Senior Member
Feb 27, 2009
866
395
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
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
 

ssandyji

Senior Member
Jun 19, 2013
167
84
Indore
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
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.
thanx

Sent from my GT-I9100 using Tapatalk
 

stylemessiah

Senior Member
May 2, 2008
1,069
971
Sydney
Anyone want to tell me what the fascination is with mixing different filesystems on a phone with known issues with filesystems already is?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 351
    dpTPBzy.png
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #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.
     */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.

    IMPORTANT INFORMATIONS
    • For complete installation instructions click here.
    • Root is now disabled by default on CyanogenMod 13. To enable it go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
    • CyanogenMod 13 comes with Cyanogen Recovery by default, if you don't like it you can flash alternative recoveries using IsoRec.
    • If you get an error message when flashing GApps you're probably running out of space in your /system partition. It is recommended to have 1GB to fit the ROM and the GApps ( The stock partition table has 512mb for /system). This thread has a good guide for repartitioning and this one has a great tool for repartitioning without Odin.
    • If you're interested in BLN, check this thread for a complete support of this feature.
    • Google is your friend

    I'll not support users and answer questions from users which:
    - Are running a custom kernel
    - Have flashed mods
    - Modified system files
    - Didn't follow my instructions
    - Are unfriendly

    Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/I9100_Info
    Known Issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i9100
    Changelog: http://www.cmxlog.com/13/i9100/

    Basic first time installation instructions:
    • Download CM-13.0-XXXXXXXX-NIGHTLY-i9100.zip to your sdcard
    • Make sure you're using a Kitkat Compatible Recovery
    • Boot into Recovery
    • Wipe all your data
    • Flash CM-13.0-XXXXXXXX-NIGHTLY-i9100.zip from sdcard
    • (Optional)Flash Google Apps.zip from sdcard
    • Reboot

    CyanogenMod official nightly builds:
    http://download.cyanogenmod.org/?device=i9100

    Google Apps:
    https://wiki.cyanogenmod.org/w/Google_Apps

    Unofficial Builds: [SIZE="-1"](Just for the records)[/SIZE]


    If you like my work, consider making a small donation ;)

    XDA:DevDB Information
    CyanogenMod 13, ROM for the Samsung Galaxy S II

    Contributors
    Lysergic Acid
    Source Code: https://github.com/CyanogenMod

    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.0.x
    ROM Firmware Required: Kitkat Compatible Recovery
    Based On: AOSP

    Version Information
    Status: Nightly

    Created 2015-10-12
    Last Updated 2016-08-27
    126
    TRIM

    Very well, since there seems to be lot of demand for trim, I'll be merging @Lanchon patches on the official CM kernel. I think if anyone complain about it, he is able to provide me enough documentation on why trim is needed.
    If something bad out of it happens, I'll kill all of you who asked for it ( and revert the patch :) )
    That's all folks
    84
    New build

    I uploaded a new build with most of my progress on CM13. Internal sdcard doesn't work as expected, thanks Samsung for your weird partition table. SELinux is almost done, not a problem anymore. I'll be working on GPS today, seems to be easy to get it working, then I also need to update DRM stuff again and then we'll have all the basic hardware working.
    I'm uploading mostly as a xmas gift to everyone as that's the best I can give for the moment :)
    77
    New build

    I uploaded a fresh build with updated CM sources and fixes everywhere. The ROM now looks like a proper ROM, but a lot of stuff is still broken of course. I guess now we can start to fix the bugs.
    PS: Just realized I got the *Recognized Developer* title, very nice :eek:
    73
    Just as an information to everyone, new builds weren't released because we now have a libMali.so crash when waking up the device screen on CM13. It leads to a 2 sec black screen and then soft reboot. So it's not worth to release a new build, but I'm working hard to port M to this device, anyone following my gerrit changes is aware of that ;)