0
I'm new to Android environment, so I'd like to know how much can we Motorola Pro+ owners do with the OS source on the following link:
http://sourceforge.n...PRO%2B%20EMARA/
There are some instructions on the README text, which will be quoted below. If those files are compiled according to the instructions, do we get a Gingerbread vanilla ROM for this device? Is it possible to cook a custom ROM with this? Thanks in advance!
Quote
1. Download Gingerbread release from Google to your workspace
2. Overlay Motorola-provided repos on top of original Google versions
3. Apply the following change in file build/core/base_rules.mk:
diff --git a/core/base_rules.mk b/core/base_rules.mk
index 54bbb68..2fbae18 100644
--- a/core/base_rules.mk
+++ b/core/base_rules.mk
@@ -99,7 +99,7 @@ ifneq ($(filter $(LOCAL_MODULE_TAGS),user),)
$(warning * PRODUCT_PACKAGES section of)
$(warning * build/target/product/core.mk)
$(warning * )
- $(error user tag detected on new module - user tags are only supported on legacy modules) + $(warning user tag detected on new module - user tags are only supported on legacy modules) endif endif 4. Build user space components my_top_dir=<top dir of your workspace> cd $my_top_dir . build/envsetup.sh lunch generic-user make BOARD_HAVE_BLUETOOTH=true <target> For example: make BOARD_HAVE_BLUETOOTH=true out/target/product/generic/system/bin/bluetoothd 5. Build kernel and kernel modules kernel_out_dir=<kernel intermediates directory> cross=$my_top_dir/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ msm7630-perf_defconfig make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ headers_install make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ INSTALL_MOD_PATH=$kernel_out_dir/build \ modules make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ INSTALL_MOD_PATH=$kernel_out_dir/build \ modules_install
2. Overlay Motorola-provided repos on top of original Google versions
3. Apply the following change in file build/core/base_rules.mk:
diff --git a/core/base_rules.mk b/core/base_rules.mk
index 54bbb68..2fbae18 100644
--- a/core/base_rules.mk
+++ b/core/base_rules.mk
@@ -99,7 +99,7 @@ ifneq ($(filter $(LOCAL_MODULE_TAGS),user),)
$(warning * PRODUCT_PACKAGES section of)
$(warning * build/target/product/core.mk)
$(warning * )
- $(error user tag detected on new module - user tags are only supported on legacy modules) + $(warning user tag detected on new module - user tags are only supported on legacy modules) endif endif 4. Build user space components my_top_dir=<top dir of your workspace> cd $my_top_dir . build/envsetup.sh lunch generic-user make BOARD_HAVE_BLUETOOTH=true <target> For example: make BOARD_HAVE_BLUETOOTH=true out/target/product/generic/system/bin/bluetoothd 5. Build kernel and kernel modules kernel_out_dir=<kernel intermediates directory> cross=$my_top_dir/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ msm7630-perf_defconfig make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ headers_install make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ INSTALL_MOD_PATH=$kernel_out_dir/build \ modules make -C kernel ARCH=arm \ CROSS_COMPILE=$cross \ O=$kernel_out_dir \ INSTALL_MOD_PATH=$kernel_out_dir/build \ modules_install
