I've seen ROMs like Paranoid Android who only have 5 or 6 official team members listed on their website and they only support nexus devices and the Opposed Find5.....but then I see ROMs that say "Official Paranoid Android" for the note 2 or w/e phone....
Does "official" mean that its compiled from source no matter who makes it and an unofficial ROM or Port is just that....unofficial?
I mean I've seen this for a lot of ROMs not just Paranoid
Official is compiled and maintained by a team member or maintainer from the group who developed the ROM in general.
Unofficial is compiled and maintained by whoever decided to build it
Sent from my Nexus 7 using xda premium
Dubbsy said:
Official is compiled and maintained by a team member or maintainer from the group who developed the ROM in general.
Unofficial is compiled and maintained by whoever decided to build it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply man
Dubbsy said:
Official is compiled and maintained by a team member or maintainer from the group who developed the ROM in general.
Unofficial is compiled and maintained by whoever decided to build it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
hi ,which one is better and why?
or which one do u preffer? n why?
ahmad990 said:
hi ,which one is better and why?
or which one do u preffer? n why?
Click to expand...
Click to collapse
Official is better to go with if possible, as know when the source is updated and will push out updates since they're assigned to it. Unofficial just may be behind on updates but that's really it.
Sent from Black<3's I337 running Hyperdrive
DeadlySin9 said:
Official is better to go with if possible, as know when the source is updated and will push out updates since they're assigned to it. Unofficial just may be behind on updates but that's really it.
Sent from Black<3's I337 running Hyperdrive
Click to expand...
Click to collapse
Didnt get .Sorry
Hii..I have to ask that is there any risk in installing unofficial custom ROMs like AICP for lenovo k3 note
What is the difference between official build and weekly build
Vinay chintu said:
What is the difference between official build and weekly build
Click to expand...
Click to collapse
Your confusing the Release Type and the Build Type...
Hello Everyone!
I, personally, have always defined the differences of the different Firmware ROM's as follows:
RELEASE TYPES
OFFICIAL = From Original Development and signed off by one or more of the Original Developer(s).
UNOFFICIAL = A Development based upon the Original Development by a third party developer.[/B]
BUILD TYPES
EXPERIMENTAL = Typically an Experimental build is a tool used to aid in Migrating/Transitioning from an older Android version to a newer one.
NIGHTLY/WEEKLY = Are builds that's automated by software and are released on a daily/weekly basis (in most cases they are approximate timing). In Most (but, not All) cases there are no/little real human interaction in this. Typically an automated process for the release.
*** One example of the automated process is If you look at Open GApps... This is typically all automated with human interaction being little to none (the human interaction is usually on a case-by-case basis when the need calls for it).
SNAPSHOT = (aka STABLE) This is typically when an actual individual has reviewed and deemed that everything within it is considered "feature-complete" and "reliable". In most cases, these releases are considered being without bugs.
*** I specified "in most cases" because I've seen those releases with a missed issue/bug but, this doesn't happen very much at all (thankfully).
This is not a Dictionary definition and there's much much more to it.
I just did my best i could (via text) to simplify it to help any noob members...
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Ibuprophen said:
Your confusing the Release Type and the Build Type...
Hello Everyone!
I, personally, have always defined the differences of the different Firmware ROM's as follows:
RELEASE TYPES
----------------------
OFFICIAL = From Original Development and signed off by one or more of the Original Developer(s).
UNOFFICIAL = A Development based upon the Original Development by a third party developer.
BUILD TYPES
-----------------
EXPERIMENTAL = Typically an Experimental build is a tool used to aid in Migrating/Transitioning from an older Android version to a newer one.
NIGHTLY/WEEKLY - Are builds that's automated by software and are released on a daily/weekly basis (in most cases they are approximate timing). In Most (but, not All) cases there are no/little real human interaction in this. Typically an automated process for the release.
***One example of the automated process is If you look at Open GApps... This is typically all automated with human interaction being little to none (the human interaction is usually on a case-by-case basis when the need calls for it).
SNAPSHOT = In short... A Stable build. This is typically when someone reviewed and deemed that everything within it is considered "feature-complete" and "reliable". In most cases, these releases are considered being without bugs.
This is not a Dictionary definition and there's much much more to it.
I just did my best i could (via text) to simplify it to help any noob members...
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Click to expand...
Click to collapse
Thanks for the information
Currently I'm using resurrection remix and they release official builds every week
I mean why is that. They rolled out weeklies for 3 out 4 weeks and then official builds and these officials are also published weekly. What is the difference in these builds
Vinay chintu said:
Thanks for the information. Currently I'm using resurrection remix and they release official builds every week. I mean why is that. They rolled out weeklies for 3 out 4 weeks and then official builds and these officials are also published weekly. What is the difference in these builds
Click to expand...
Click to collapse
I can't speak for them (and I may be wrong) but, I believe that this is because of that "human interaction".
More than likely (i can't state definitely) an actual individual reviews and signs off on them before it's released.
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Ibuprophen said:
I can't speak for them (and I may be wrong) but, I believe that this is because of that "human interaction".
More than likely (i can't state definitely) an actual individual reviews and signs off on them before it's released.
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Click to expand...
Click to collapse
Thank you
Related
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [i9100], ROM for the Samsung Galaxy S II
Contributors
CarbonDev, Myself5
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Beta
Created 2014-02-14
Last Updated 2014-06-07
Reserved
Reserved
Hello Guys.
I'm your i9100 device maintainer.
I meanwhile tweaked the Rom specially for the i9100 so its difference to our other devices is:
Compiled using SaberMod arm-eabi 4.7 (Kernel code) and SaberMod arm-linux-androideabi 4.8 (ROM code) toolchain compilers
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
F.A.Q.:
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124. Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
Greetings
Myself5
Nice Work Dude !
Mine
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Whats Up Whith "Mine" ?
great ...thanks ....will try it surly
Great!! carbon finally arrived gonna try
Sent from my GT-I9100 using Tapatalk
im not able to see the download link in carbon page, i select our device but the links to download the ROM doesnt appear, can someone share the download link?
attack11 said:
im not able to see the download link in carbon page, i select our device but the links to download the ROM doesnt appear, can someone share the download link?
Click to expand...
Click to collapse
I have found that this link:
http://carbon-rom.com/downloads/?device=i9100&type=nightly&country=US
Showing some dates but still no luck with working link...
Послато са GT-I9100 уз помоћ Тапатока
Will this rom contain the tweaks/things that Myself5 added to his unofficial build?
It seems like we're currently having some issues with our download page getting accessed by mobile browsers. Please use your computer to download until we fixed it.
@GreekBlood: All in all the most tweaks I made were coommits from gerrit, so sooner or later they will be included
http://carbon-rom.com/downloads/?device=i9100&type=nightly&country=BE
Here i can see the downloads perfectly and they also work.
And here is the latest nightly for our SII :> http://eu1.dl.carbon-rom.com/files/i9100/nightly/CARBON-KK-NIGHTLY-20140215-0148-i9100.zip
congrats myself5 on getting to be the maintainer for this great rom on our s2.
i think i will just dl from the official carbon page,and then just use the updater to get all the improvements and fixes moving forward!!
well first hour whit this rom.and everything seems good after all! just one question,how i can enable wheater widget in the lockscreen? i cant find an option..
also some translations are missing (in spanish) i can help if you want.
also another question Halo will be added on the future?
i flashed newest rom all good.kernel included is not compatible with stweaks.
I plan on flashing gustavo 2\09 kernel.
will nightly updates flash a another kernel each update??
thnx
A little problem
I have a little problem,when i try to install gapps it says that i have insufficient space. How would i fix that? I`m using PA-GOOGLE APPS (FULL MODULAR PACKAGE) .
And another question. Previous versions that were unofficial had TWRP, how could I get that back too?
@attack11 the Weather Widget is called cLock. HALO will be added it just has some small bugs ATM we need to fix. Thanks for your help, I will later PM you all files you need to translate.
@saskrider: It will flash a new Kernel every Update. However when you later (as soon as it's working) use CarbonDelta to update there will be a option to add Custom Zip's to flash after the Rom (like GApps and Custom Kernels)
@Pecka40: the S2's Sytem Partition is to small for these GApps, use some smaller ones
Greetings
Myself5
Sent from my GT-I9100 using Tapatalk
Myself5 said:
@attack11 the Weather Widget is called cLock. HALO will be added it just has some small bugs ATM we need to fix. Thanks for your help, I will later PM you all files you need to translate.
@saskrider: It will flash a new Kernel every Update. However when you later (as soon as it's working) use CarbonDelta to update there will be a option to add Custom Zip's to flash after the Rom (like GApps and Custom Kernels)
@Pecka40: the S2's Sytem Partition is to small for these GApps, use some smaller ones
Greetings
Myself5
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! And there is no way of making it bigger?
And could you please answer the other question. About how can I get TWRP on it.
I9100 CyanogenMod 13
Powered with: Linaro and SaberMod!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In brightest day, in blackest night, no lag shall escape my sight. Let those who worship Apple's might, beware my power, Green Lantern's light!
Click to expand...
Click to collapse
cm-13.0-20161216-MARKOX89-i9100 is UP!
Download Folder on AndroidFileHost
AFH calculates md5sum for every build: please, always check it before flashing!
Highlights of the main features:
Kernel is compiled with latest Linaro arm-eabi-4.9 toolchain
Source:
https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-13.0
ROM is compiled with latest SaberMod arm-linux-androideabi-4.9 toolchain
Source:
https://github.com/CyanogenMod
https://github.com/CyanogenMod/android_device_samsung_i9100/tree/cm-13.0
https://github.com/CyanogenMod/android_device_samsung_galaxys2-common/tree/cm-13.0
ART tweaks for devices with less memory, as provided by arter97 and JustArchi
Fix for Google Play Services crashes, as provided by fusionjack
Fix for the infamous "music bug", as provided by Lanchon and zeitferne
Support for Screen Mirroring through Chromecast
Changelog:
BACKPORT: perf: Allow the PMU driver to choose the CPU on which to install events CyanogenMod/android_kernel_samsung_smdk4412
BACKPORT: perf: Introduce perf_pmu_migrate_context() CyanogenMod/android_kernel_samsung_smdk4412
BACKPORT: lockdep: Silence warning if CONFIG_LOCKDEP isn't set CyanogenMod/android_kernel_samsung_smdk4412
BACKPORT: perf: Fix event->ctx locking CyanogenMod/android_kernel_samsung_smdk4412
perf: protect group_leader from races that cause ctx double-free CyanogenMod/android_kernel_samsung_smdk4412
net: ping: Fix stack buffer overflow in ping_common_sendmsg() CyanogenMod/android_kernel_samsung_smdk4412
fbmem: Check failure of FBIOPUTCMAP ioctl CyanogenMod/android_kernel_samsung_smdk4412
fbcmap: Remove unnecessary condition check CyanogenMod/android_kernel_samsung_smdk4412
drivers: video: Add bounds checking in fb_cmap_to_user CyanogenMod/android_kernel_samsung_smdk4412
netfilter: Change %p to %pK in debug messages CyanogenMod/android_kernel_samsung_smdk4412
smdk4412-kernel : do not ignore COB wifi chips CyanogenMod/android_kernel_samsung_smdk4412
smdk4412-kernel : kona wifi module is COB type CyanogenMod/android_kernel_samsung_smdk4412
mobicore: Fix pointer narrowing issues CyanogenMod/android_hardware_samsung_slsi-cm_exynos7420
soundtrigger: fix memory corruption CyanogenMod/android_frameworks_av
version: Set version string to 13.0.5 to reflect security update CyanogenMod/android_vendor_cm
Updating Security String to 2016-12-01 CyanogenMod/android_build
Fix out of bound access in libziparchive CyanogenMod/android_system_core
Unexport OmtpMessageReceiver CyanogenMod/android_packages_services_Telephony
Restrict SipProfiles to profiles directory CyanogenMod/android_packages_services_Telephony
mm-video-v4l2: vdec: Disallow input usebuffer for secure case CyanogenMod/android_hardware_qcom_media
Fix potential NULL dereference in Visualizer effect CyanogenMod/android_hardware_qcom_audio
Handle color bounds correctly in GIF decode. CyanogenMod/android_frameworks_ex
ExifInterface: Close the file when an exception happens CyanogenMod/android_frameworks_base
Isolated processes don't get precached system service binders CyanogenMod/android_frameworks_base
Fix divide by zero CyanogenMod/android_frameworks_av
Fix potential NULL dereference in Visualizer effect CyanogenMod/android_frameworks_av
Decoder: Fixes in handling errors in Mbaff clips. CyanogenMod/android_external_libavc
Decoder: Ignore few dpb errors CyanogenMod/android_external_libavc
resolve merge conflicts of 849c5c7 to mnc-dev CyanogenMod/android_frameworks_opt_net_wifi
wifinative jni: check array length to prevent stack overflow CyanogenMod/android_frameworks_opt_net_wifi
wl12xx: Common WLAN KM build target for reuse by devices CyanogenMod/android_hardware_ti_wlan
Add Reliance Jio India IMS volte apn's CyanogenMod/android_vendor_cm
Fix Reliance Jio India APNs. CyanogenMod/android_vendor_cm
Enable support for groups in External contacts accounts CyanogenMod/android_packages_apps_ContactsCommon
macloader : add n5120 murata MAC address CyanogenMod/android_hardware_samsung
macloader : add n5110 murata MAC address CyanogenMod/android_hardware_samsung
build: repopick: Avoid failing on commits lookup CyanogenMod/android_build
vendor: cm: Add some more BQ maintainers/devices CyanogenMod/android_vendor_cm
build: repopick: Support squashed commits for Change-Id detection CyanogenMod/android_build
build: repopick: Support projects with less than 10 commits CyanogenMod/android_build
repopick: handle revisions with slashes CyanogenMod/android_build
repopick: don't re-pick duplicate changes CyanogenMod/android_build
repopick: try to use remote's default revision CyanogenMod/android_build
Settings: Fix the failing strings CyanogenMod/android_packages_apps_Settings
Contributors: Add maintainer for Xiaomi Redmi 3/Prime (ido) CyanogenMod/android_vendor_cm
SystemUI: Don't vibrate on touchscreen camera gesture CyanogenMod/android_frameworks_base
ActivityControler: Fix BadPacelableException in certain scenarios CyanogenMod/android_packages_apps_UnifiedEmail
Check if Volte is enabled in ImsManager to determine Volte support CyanogenMod/android_packages_apps_PhoneCommon
cmhw: Account for devices that don't use manager0 sysfs paths CyanogenMod/android_hardware_ti_omap4
Support for MODE_ASK in commandline CyanogenMod/android_frameworks_base
AppOps: Do not prune apps that are not present CyanogenMod/android_frameworks_base
cm: Add more Mi 5 maintainers CyanogenMod/android_vendor_cm
Contributors: Add Xiaomi Mi 5 maintainer CyanogenMod/android_vendor_cm
More...
Buildbot:
CPU: Intel Core 2 Quad Q8300 2.50 GHz
MotherBoard: ASUS P5K
RAM: 4 GB Corsair DDR2 667 MHz
Main HD: SanDisk SSD SDSSDP-128G 128 GB SATA 6 GB/s
ccache HD: Western Digital Raptor WD1500ADFD 150 GB SATA 1.5 GB/s
OS: Linux Lubuntu 16.04 "Xenial Xerus" x64
Kernel version: 4.4.0
Donations:
If you're enjoying my work you may consider sending a small donation using this link
Special Thanks:
CyanogenMod Dev Team
Linaro Dev Team
sparksco and the whole SaberMod Dev Team
IAmTheOneTheyCallNeo
Lysergic Acid
JustArchi
fusionjack
Android-Andi
Ziyan
tuxafgmur
Infected_
-Grift-
prace86
jamal2367
XDA:DevDB Information
[ROM][I9100][MM][6.0.1][Linaro][SaberMod] CyanogenMod 13, ROM for the Samsung Galaxy S II
Contributors
Markox89
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: CWM Recovery
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: CyanogenMod 13
Created 2014-03-19
Last Updated 2016-12-17
How to: Installation and Bug Reporting
Disclaimer (read it before installing the ROM for the first time):
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.
Regarding the compatibility with mods or apps, these builds are as compatibile as official CyanogenMod nightly builds.
Click to expand...
Click to collapse
Installing CyanogenMod 13 on your Galaxy S II:
Copy CyanogenMod 13 zip and a light GApps package of your choosing to your Internal or External SD card;
Make sure you are not running a kernel with the MMC-Superbrick-Bug and you are using latest version of a MarshMallow compatible recovery;
Boot into recovery;
Flash CM 13 zip;
Flash GApps package;
If you're coming from another non-CyanogenMod ROM do a Data Wipe / Factory Reset (otherwise your device will be stuck at boot);
Reboot.
Posting Bug Reports (comply these requisites is mandatory, otherwise your report won't be considered):
Use the newly added Bug Reports tab;
I always test my builds before releasing them and use the latest build as daily ROM for my devices: do not claim it doesn't boot or it gives you force close loops (if this is your case it's either a corrupted download or your phone needs a full wipe);
Clearly state which build are you using (for reporting a bug it needs to be the latest);
Clearly state that you're using the kernel that comes with the build and not a modded one (if you're experiencing issues using a modded kernel, you should refer to the kernel's developer thread);
Clearly state which mods are you using (e.g. Xposed Framework): try to remove the mod and see if the bug is still there;
Clearly state which runtime are you using (e.g. Dalvik or ART); if you're using ART try to switch to Dalvik and see if the bug is still there;
In addition before posting bug reports, test if your bug is also present in the same day's official CyanogenMod nightly; if it is present there, wait until the CyanogenMod Team fixes it or report directly to them;
As a small courtesy, please don't report bugs that can easily be fixed with well known patches (e.g. CWM zips);
GApps related crashes should be reported to GApps package maintainer (at least at first).
F.A.Q (Frequently Asked Questions)
Uff, our device is slow and Screen Mirroring is laggy, can you fix this?
Nope, our device is old and OEM support lacks.
You shouldn't complain about the overall performance or about the performance of some specific features (e.g. Screen Mirroring through ChromeCast).
Your latest build isn't working at all, can you fix it?
I personally test every build before releasing it, so the device will always be usable.
If you experience weird issues or something that's a showstopper for you, you should consider switching to CyanogenMod's official builds, or to another ROM: your device or setup may be incompatible with my builds.
Where can I find CyanogenMod's official builds?
If you're looking for something common or some common infos, you should definitely use xda search engine or Google.
May you give me some informations about your builds?
All the infos about my builds (e.g. technical compilation infos, features and installation guide) are in the first three posts: you should definitely read them before posting.
I saw this cool feature on another ROM, can you include it in your builds?
Nope, sorry, I'm not taking Feature Requests (see that the correspondent tab is missing from OP): you should make Feature Requests to CyanogenMod Team in the ways you prefer.
In addition, you can look for some Xposed Module, maybe you'll find one that can add to my builds what you're looking for.
A new "SnapShot" build is out! When you'll compile a build based on it?
Never, sorry. My builds are compiled from the nightly branch. The "SnapShot" builds are compiled from a dedicated branch; "SnapShot" releases doesn't influence in any way my builds.
I need some technical explanation about the tools you're using, may you provide them?
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124. Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
Glad to see you're on your feet now. Good. Looking forward to some good cooking from you. All the best.
Sent from my GT-I9100 using Tapatalk
Glad to see your own thread! :laugh:
Glad to see you in your own new house Markox89 ! Im downloading and trying your new build 1603 :good:
Dear colleagues, my friend has a problem. After installing the firmware and restore applications using Titanium Backup is a window appeared. Today it has been updated on a regular nightly, but it reappeared window. Can this be fixed without full wipe?
blinoff82 said:
Dear colleagues, my friend has a problem. After installing the firmware and restore applications using Titanium Backup is a window appeared. Today it has been updated on a regular nightly, but it reappeared window. Can this be fixed without full wipe?
Click to expand...
Click to collapse
Have a look at this
Hey @Markox89......
Glad to see you here fella.....keep up the DAMN FINE work.......
Sent from my Markox powered, KitKatted S2.....
Nicely Done :good:
New thread, niiice
via Tapatalk
drdays said:
Glad to see you're on your feet now. Good. Looking forward to some good cooking from you. All the best.
Click to expand...
Click to collapse
blinoff82 said:
Glad to see your own thread! :laugh:
Click to expand...
Click to collapse
aiyeumiforever said:
Glad to see you in your own new house Markox89 ! Im downloading and trying your new build 1603 :good:
Click to expand...
Click to collapse
keithross39 said:
Hey @Markox89......
Glad to see you here fella.....keep up the DAMN FINE work...
Click to expand...
Click to collapse
scorpion.hbs said:
Nicely Done :good:
Click to expand...
Click to collapse
MPL92 said:
New thread, niiice
Click to expand...
Click to collapse
Many thanks to all of you...this means a lot to me, for real :')
great work
but this rom better than slimkat and EHNDROIX
amrtare said:
great work
but this rom better than slimkat and EHNDROIX
Click to expand...
Click to collapse
@Markox89 Well done! Sorry to keep you awake to build.
@Markox89 Good luck and thank you for still supporting our s2 [emoji106][emoji106]
I updated from 2014-02-28 build to 03-16 but camera is always crashing while opening... Even after clearing the Caches again and clearing camera app Data... Is there a fix?
cubflyer said:
I updated from 2014-02-28 build to 03-16 but camera is always crashing while opening... Even after clearing the Caches again and clearing camera app Data... Is there a fix?
Click to expand...
Click to collapse
Try replacing the Camera apk with this one, or the one extracted from latest official nightly
Next build should fix the issue, but this can be a good workaround
Sent from my GT-P5110 using Tapatalk
@Markox89 Thanks man!
Thanks for this cook.
Will put an eye on it. Will Try it in the next future.
Any screenshots, or known bugs?
Sent from my GT-I9100 using Tapatalk 2
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Very Nice.!!! :fingers-crossed:
nathanchance said:
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Click to expand...
Click to collapse
Thanks for everything Sir.
You really are techno-Jesus, here to teach the ways of kernel perfection. I love your work, dedication, and care for your kernel users. Flash4lyfe.
Yes, please flame me for being a fanboy. You can never show enough appreciation for our beloved xda developers (especially the ones that don't treat users like ****).
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
AndroidGX said:
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
Click to expand...
Click to collapse
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
nathanchance said:
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
Click to expand...
Click to collapse
No worries
Thanks, it works like a charm now (currently trying my kernel on .116), again good job :highfive:
Cheers'
4.4.117 has been merged in.
4.4.118 has been merged in (conflict notes).
4.4.119 and OOS 5.0.4 have been merged in.
4.4.120 has been merged in (conflict notes).
thanks for making this, trying to build lineage and I keep getting the following error:
Code:
drivers/bluetooth/btfm_slim.c:26:23: fatal error: btfm_slim.h: No such file or directory
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
Use an out folder.
mkdir out
make O=out mata_defconfig
make O=out -j$(nproc --all)
Click to expand...
Click to collapse
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
aeppacher said:
thanks for making this, trying to build lineage and I keep getting the following error:
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
Click to expand...
Click to collapse
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
nathanchance said:
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It booted perfectly, thanks so much! I would use the thanks button but it doesn't seem to be working :/
4.4.121 has been merged in.
I will have a new tree based on the 8.1 sources out tonight.
Sent from my Google Pixel 2 XL using XDA Labs
I have added a new branch for the 8.1 beta source; I will continue to update both 8.0 and 8.1 until 8.1 goes stable.
https://github.com/android-linux-stable/op5/commits/oneplus/QC8998_O_8.1
4.4.122 has been merged in.
4.4.123 has been merged in.
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
If anyone wants to reupload to a better file hosting site please do.
For future updates.
I do realize this is in the Pixel XL section. Please feel free to remove it. The hope is that others would take up the process for the Pixel XL.
Can you please link to the kernel source, if not all repos used to build this?
jisoo said:
Can you please link to the kernel source, if not all repos used to build this?
Click to expand...
Click to collapse
They are located on the OP under "Instructions used to build"
jahrule said:
For future updates.
I do realize this is in the Pixel XL section. Please feel free to remove it. The hope is that others would take up the process for the Pixel XL.
Click to expand...
Click to collapse
MODERATOR NOTICE:
The development section is not a place to share ROMs or hope that someone will take up developing a ROM that you post here. In this section you are only allowed to post your own work, and it must meet the requirements for posting in the Development section as laid out in the sticky titled Device Forum Rules (Please Read before posting).
THREAD CLOSED
Invictrix ROMFor the Moto G5 Plus (potter)
Welcome to Invictrix!! Our goal is to provide users with a unique staple in Android Development which aims at stability and optimizations along with what we feel is the perfect amount of features. We hope you enjoy this ROM as much as our great team has had while building it. With that said, We are in no way shape or form responsible if you brick your phone.
Features:
More features to come
Downloads:
ROM -
Here
GApps -
Pico | Nano | microG
Installation:
See Below
Issues:
See Below
Source:
ROM - InvictrixROM
Device Trees - InvictrixROM-Devices
Kernel - Kernel Source
Reporting Bugs:
Logcat, Logcat, Logcat
Please submit logs if you're having an issue. If there is no log we cannot help you. Simply clogging the threads with “This issue happened, fix it” will get you nowhere and you will be ignored. To Also add to the Log Criteria, Your bug report won't be used if:
- You are not on a clean flash of the ROM
- If you're using Xposed
- If you’ve flashed any other mod that tweaks System in any way
So help us to help you and provide logs for issues. Thanks.
Other:
Feel free to join our Telegram community, Google Plus, and check out our website
https://invictrixrom.com
Google Plus
Our Telegram Chat
XDA:DevDB Information
Invictrix, ROM for the Moto G5 Plus
Contributors
coldhans, Snuzzo, Yuki Coc
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: GZOSP
Version Information
Status: Nightly
Current Stable Version: 1.0
Stable Release Date: 2018-07-21
Created 2018-06-29
Last Updated 2018-07-21
Reserved
Reserved
meh.
Natd32 said:
meh.
Click to expand...
Click to collapse
Assuming you've tried the ROM since you're posting in its development thread, did "meh" mean it was only so-so, and what specifically did you like or not like about it?
Screenshots courtesy of @dhinesh_cool
Dahenjo said:
Assuming you've tried the ROM since you're posting in its development thread, did "meh" mean it was only so-so, and what specifically did you like or not like about it?
Click to expand...
Click to collapse
Dont mind him every thread has atleast one troll.
deleted
Fine, it's odexed now, you savages: https://www.androidfilehost.com/?fid=11050483647474829562
sinchan_nohara said:
Dont mind him every thread has atleast one troll.
Click to expand...
Click to collapse
He's the troll on every thread.
New build
Download: https://potterroms.me/Invictrix/Invictrix-potter-8.1.0-1.0-UNOFFICIAL-20180706-2220.zip
Telegram: https://t.me/InvictrixROM
Official weeklies should be ready soon... :highfive:
coldhans said:
New build
Download: https://potterroms.me/Invictrix/Invictrix-potter-8.1.0-1.0-UNOFFICIAL-20180706-2220.zip
Telegram: https://t.me/InvictrixROM
Official weeklies should be ready soon... :highfive:
Click to expand...
Click to collapse
Bugs?
apexashwin said:
Bugs?
Click to expand...
Click to collapse
The only very minor issue I've had is that in the "About phone" part, if i touch "System updates" then the settings app closes. There aren't any updates, so no real reason to touch that, but it's something I've noticed.
New build with July security: https://potterroms.me/Invictrix/Invictrix-potter-8.1.0-1.0-UNOFFICIAL-20180714-0333.zip
Official Invictrix is here!
Official OTA builds have begun as of this week. The first can be downloaded HERE.
I've updated the OP with new links to the Invictrix OTA page and recommended GApps packages from GZR (pico gapps) and Beans (nano gapps), as well as a link to NanoDroid's microG implementation by @Setialpha if you prefer to go without Google.
Happy flashing!
What WireGuard module version is included in this ROM?
wrkerr said:
What WireGuard module version is included in this ROM?
Click to expand...
Click to collapse
Check the kernel source link in the OP. Wireguard-related commits are in there. iirc, it pulls the latest version via http when the build is started, so it should always be up to date.
Has anyone tried dirty flashing this over Omni?