• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

CyanogenMod 13

Search This thread

jgcaap

Senior Member
Sep 22, 2009
9,910
19,227
Porto
bKE72V5.png


Hello everyone, after long studying both kernel and ROMs, i've decided to start building a ROM of my own.


Download

If you want to use Xposed. After flashing rom, boot it and only after that flash Xposed.

GAPPS

Support and a complete pack with other stuff (cm-12.1)

It is recommended to use F2FS.

Recovery - Wipe - advanced wipe - Select internal card - FS options - Check F2FS and swipe.

Remember that you'll loose everything on your internal memory.

Partition configuration i recomend for best speed:
cache --> F2FS
Internal Data -->F2FS
System --> EXT4


Features:
Updated SQL to 3.14.1
Optimized SQL code for faster Read/Write
CM Super User (for now is the most stable one)
CameraNext from COS13
New Kernel
Improved Code of frameworks
Optimized Build with custom toolchain on ROM and Kernel
Optimizations for our chip
Improved sound with speex resampler
Improved bionic with many optimized libraries (faster rom)
Improved Art with upstream patches
More than 100 mem fixes not included on cm builds
Optimized native frameworks for our device
LZMA updated to the latest
Proguard 5.3
Google Webview
F2FS ready for data and cache
Immersive mode
Expanded Notifications
Network Monitor
K1 Camera (Color OS camera and plugins)
ColorOs Blobs (much better quality)
More coming soon



I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.

Thanks :)

You problably wondering why i say is CAF+Google+CM. It's in fact very easy... and i have seen many threads which mislead the interpertation. Google provides AOSP+ kernel patches for the nexus devices which are for our chipset.
Qualcom provides CAF changes which is over linux kernel changes and google changes. (in other words kernel is linux based and frameworks/art/bionic are based on the google stuff which is also based on linux)
We still have CM changes.

So basically how it works? i'll simplify

We use Google as base which includes CAF changes and CM changes... and with this ROM... jgcaap changes :)

So why Add CAF on some roms at tittle?
Basically is linux kernel with CAF changes without google or CM changes on kernel (and kernel only)

But let me add you some knowledge here. What you call CAF is in fact Oxygen OS kernel. In other words, what Devs which have on title CAF which is related to 3.4.0 kernel is in fact linux+CAF+Oxygen OS.

Oxygen OS changes is only compatible with blobs which are from oxygen OS, and we do not use it. So because of that, the rom problably won't boot in case you flash a "CAF" kernel

Why some Devs use the called CAF and some CM source?

Depends on preference. I prefer CM because i believe is the best not only on performance but also never had issues with it. But there might be different experiences regarding the phone you have since we all have different batches. There are devs which believe that compability issues might be related to some CM commits. As also, there are devs which think the other way around.



Join out Google+ community

Big thanks to @RobbieL811 for the patience and help he provided to create these builds.
Thanks also for the experience i won with @ak @savoca @Lord Boeffla @ZaneZam by discussing and learning about the kernel. A big thanks to @dorimanx. Thank you @franciscofranco for commits to improve kernel!
Thank you @Markox89 on being first help on rom building. @katinatez for guiding me to create better builds! @arter97 for his toolchains and commits.
Thanks @supervis0r for the headbanner.
As you might know, all credits go to CyanogenMod Team.


Source Code
OnePlus Thread
If you like my work, please consider a donation.
 
  • Like
Reactions: Markox89

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    bKE72V5.png


    Hello everyone, after long studying both kernel and ROMs, i've decided to start building a ROM of my own.


    Download

    If you want to use Xposed. After flashing rom, boot it and only after that flash Xposed.

    GAPPS

    Support and a complete pack with other stuff (cm-12.1)

    It is recommended to use F2FS.

    Recovery - Wipe - advanced wipe - Select internal card - FS options - Check F2FS and swipe.

    Remember that you'll loose everything on your internal memory.

    Partition configuration i recomend for best speed:
    cache --> F2FS
    Internal Data -->F2FS
    System --> EXT4


    Features:
    Updated SQL to 3.14.1
    Optimized SQL code for faster Read/Write
    CM Super User (for now is the most stable one)
    CameraNext from COS13
    New Kernel
    Improved Code of frameworks
    Optimized Build with custom toolchain on ROM and Kernel
    Optimizations for our chip
    Improved sound with speex resampler
    Improved bionic with many optimized libraries (faster rom)
    Improved Art with upstream patches
    More than 100 mem fixes not included on cm builds
    Optimized native frameworks for our device
    LZMA updated to the latest
    Proguard 5.3
    Google Webview
    F2FS ready for data and cache
    Immersive mode
    Expanded Notifications
    Network Monitor
    K1 Camera (Color OS camera and plugins)
    ColorOs Blobs (much better quality)
    More coming soon



    I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.

    Thanks :)

    You problably wondering why i say is CAF+Google+CM. It's in fact very easy... and i have seen many threads which mislead the interpertation. Google provides AOSP+ kernel patches for the nexus devices which are for our chipset.
    Qualcom provides CAF changes which is over linux kernel changes and google changes. (in other words kernel is linux based and frameworks/art/bionic are based on the google stuff which is also based on linux)
    We still have CM changes.

    So basically how it works? i'll simplify

    We use Google as base which includes CAF changes and CM changes... and with this ROM... jgcaap changes :)

    So why Add CAF on some roms at tittle?
    Basically is linux kernel with CAF changes without google or CM changes on kernel (and kernel only)

    But let me add you some knowledge here. What you call CAF is in fact Oxygen OS kernel. In other words, what Devs which have on title CAF which is related to 3.4.0 kernel is in fact linux+CAF+Oxygen OS.

    Oxygen OS changes is only compatible with blobs which are from oxygen OS, and we do not use it. So because of that, the rom problably won't boot in case you flash a "CAF" kernel

    Why some Devs use the called CAF and some CM source?

    Depends on preference. I prefer CM because i believe is the best not only on performance but also never had issues with it. But there might be different experiences regarding the phone you have since we all have different batches. There are devs which believe that compability issues might be related to some CM commits. As also, there are devs which think the other way around.



    Join out Google+ community

    Big thanks to @RobbieL811 for the patience and help he provided to create these builds.
    Thanks also for the experience i won with @ak @savoca @Lord Boeffla @ZaneZam by discussing and learning about the kernel. A big thanks to @dorimanx. Thank you @franciscofranco for commits to improve kernel!
    Thank you @Markox89 on being first help on rom building. @katinatez for guiding me to create better builds! @arter97 for his toolchains and commits.
    Thanks @supervis0r for the headbanner.
    As you might know, all credits go to CyanogenMod Team.


    Source Code
    OnePlus Thread
    If you like my work, please consider a donation.