[Galaxy S II Android Development] deepongi:
FAQ and Tutorial

What is the difference between these builds and the official builds?

These are unofficial builds of CarbonRom (Android 4.3) for the i9100.

ROM is built using the same source code (github) like the official one but with these following additions:

Compiled using linaro arm-eabi 4.7.4 13.10 (kernel code) & sabermod arm-linux-androideabi 4.9.0 13.07 (rom code) toolchain compilers

May contain some custom cherry-picks. Always see changelog for details.

Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM

What is Toolchain?

Source: http://en.wikipedia.org/wiki/Toolchain

What is SaberMod?

The term "SaberMod" is coming from:

Source: http://xdaforums.com/show....php?t=2158698

What is Linaro?

Source: http://www.linaro.org/linux-on-arm/

About GCC main compiler cflags

Q: I love Carbon but I don’t type in English. How can I change my default keyboard language to <insert your language here>?

A: The stock android keyboard in Carbon comes with the ability to download a variety of language packs. To change it go to Settings>Language & input>Android keyboard (AOSP) settings button>Input languages. Uncheck “use system language” and select the language that you would like to use.

—————————————————————————————————————————–

Q: I see you make something called “Nightly Builds”. What are those?

A: Nightly Builds are experimental builds that are released each night with the latest features, and bug fixes, which keeps you up to date but may also be dysfunctional due to the adding a new features and code.

—————————————————————————————————————————–

Q: How do I switch from my current ROM over to Carbon?

A: (These directions are assuming you are already rooted and have installed a recovery manager, preferably CWM Recovery)

(1.) Decide whether you would like to use the stable release version of Carbon, or whether to use the nightly version of Carbon

(2.) Once you have decided, download the correct file of Carbon for your specific device using the goo app on your phone or from the goo website (make sure you know your device’s codename)

(3.) Download the corresponding GApps file using goo app on your phone or from the goo website (20130813)

(4.) Make sure you know where both files are on your phone’s sd card and then reboot to recovery

(5.) MAKE A NANDROID BACKUP of your current ROM so you have something to go back to in case anything goes wrong

(6.) If you are switching to Carbon from another ROM, you must do a full wipe before flashing Carbon, please follow these steps to wipe: Factory reset, wipe system partition, wipe cache and dalvik once more.

(7.) Now once everything is wiped, flash the Carbon zip you downloaded and then IMMEDIATELY after flash your GApps zip.

(8.)(Optional) If you have a custom kernel you would like to flash, flash it now.

(9.) Reboot your device and allow it a few minutes to startup, it may take some time on first boot.

(10.) You’re all done. Enjoy using Carbon!

—————————————————————————————————————————–

Q: What is “dirty” flashing?

A: Dirty flashing is when you do not wipe any of your data or the system partition before flashing a newer version of Carbon.

—————————————————————————————————————————–

Q: I am using the stable version of Carbon, can I switch over to the nightly builds (and vice versa) without clean wiping?

A: If you are already running Carbon you can switch over to any version of Carbon by dirty flashing (unless directly stated that a wipe is required in the changelog).

—————————————————————————————————————————–

Q: If I am already running Carbon, do I have to reflash GApps every time I dirty flash the newest updates?

A: No, Carbon has a built in script that backs up the system partition and will reapply your GApps automatically when you flash the newer version of Carbon.

—————————————————————————————————————————–

Q:How do I update my version of Carbon?

A: If you are already running Carbon and would like to update to the latest version, you can simply dirty flash the newest version on top of your current setup (unless otherwise stated in the changelog).