Every time I flash a cm9 rom it never wants to connect to ubuntu. I run lsusb and it shows it's there but it can never connect. Anyone know how to fix this? Supermaster said I might need to set up some usb rules but I have no clue and some tutorials are meant for experienced devs and not for me. Any help would be appreciated
OK... I got this while trying to mount
[email protected]:~$ sudo mtpfs -o allow_other /mnt/Samsung
Listing raw device(s)
Device 0 (VID=04e8 and PID=685e) is a Samsung Galaxy Y.
Found 1 device(s):
Samsung: Galaxy Y (04e8:685e) @ bus 2, dev 4
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
Click to expand...
Click to collapse
# Configure USB:
1) Open/Create file 51-android.rules:
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
-> Add these lines:
Code:
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
2) Save & Close
3) Set proper permisisons: (Provide read permission to all users, in addition to whatever other permissions are pre-set)
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
Sent from my Nexus 7 using XDA Premium HD app
I tried doing that and was still unable to connect.
Sent from my YP-G70 using xda app-developers app
Probably a stupid post but...have you tried restarting/trying a different usb port? If not try Airdroid from google play, if your player and pc are on the same network you can transfer files and do almost anything with it...not trying to advertise just help
Sent from my YP-G70 using xda premium
augiem94 said:
Probably a stupid post but...have you tried restarting/trying a different usb port? If not try Airdroid from google play, if your player and pc are on the same network you can transfer files and do almost anything with it...not trying to advertise just help
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
Hmm I'll give it a shot thanks!
Sent from my YP-G70 using xda app-developers app
I tried AirDroid but for what I use it it was slow. I'd prefer using cable since I transfer videos and music to my player.
Have you tried a different cable? Ive had problems with almost any non-samsung cable charging or connecting my player
Sent from my YP-G70 using xda premium
augiem94 said:
Have you tried a different cable? Ive had problems with almost any non-samsung cable charging or connecting my player
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
Yeah, it's the original cable never had any problems with it and when I go back to a GB ROM, it works like nothing was wrong with it
Whos cm9 rom are you using?
Sent from my YP-G70 using xda premium
Supermaster's but it happens to all roms I use that aren't Gingerbread
Go into developper option and unselect usb debugging then go into storage and open the menu. Select usb connection and then enable mass storage. When you will plug it into the computer it will ask to start usb storage. This is working for me on my 4.0 with nebula CM9.
Thanks for the idea but sadly it didn't work. going to start from stock and work my way to Supermaster's ROM see if it was something that installed wrong
So I reinstalled the ROM and tried it on other pc's and it connects except on my Ubuntu :\
THanks everyone for the help but i guess I'll go back to my old rom.
Related
To compile Ice Cream Sandwich on Ubuntu I'm going to first give you steps to set up your computer to get this thing rolling.
This will NOT make a fully functional ROM, but will give you a place to start. Also I CANNOT fix every error you run into.
Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (or more) for a full set of builds.
Thanks dastin1015 - For base instruction for compile
1) You need the following:
- JDK 6 if you wish to build Ice Cream Sandwich
You can download it from oracle.com. Or:
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
for a Ubintu 11.10
sudo add-apt-repository "deb http://archive.canonical.com/ orcelot partner"
sudo apt-get update
sudo apt-get install sun-java6-jdk
- Python 2.4 -- 2.7
You can download from python.org. Or:
Code:
sudo apt-get install python
- Git 1.7 or newer
You can find it at git-scm.com. Or:
Code:
sudo apt-get install git-core
2) Install required packages:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev \
libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown \
libxml2-utils
On newer versions of Ubuntu such as 11.10 you may need to do the following:
Code:
sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
3) Configure your USB:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM==usb, SYSFS{idVendor}==0502, MODE=0666
#ASUS
SUBSYSTEM==usb, SYSFS{idVendor}==0b05, MODE=0666
#Dell
SUBSYSTEM==usb, SYSFS{idVendor}==413c, MODE=0666
#Foxconn
SUBSYSTEM==usb, SYSFS{idVendor}==0489, MODE=0666
#Garmin-Asus
SUBSYSTEM==usb, SYSFS{idVendor}==091E, MODE=0666
#Google
SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666
#HTC
SUBSYSTEM==usb, SYSFS{idVendor}==0bb4, MODE=0666
#Huawei
SUBSYSTEM==usb, SYSFS{idVendor}==12d1, MODE=0666
#K-Touch
SUBSYSTEM==usb, SYSFS{idVendor}==24e3, MODE=0666
#KT Tech
SUBSYSTEM==usb, SYSFS{idVendor}==2116, MODE=0666
#Kyocera
SUBSYSTEM==usb, SYSFS{idVendor}==0482, MODE=0666
#Lenevo
SUBSYSTEM==usb, SYSFS{idVendor}==17EF, MODE=0666
#LG
SUBSYSTEM==usb, SYSFS{idVendor}==1004, MODE=0666
#Motorola
SUBSYSTEM==usb, SYSFS{idVendor}==22b8, MODE=0666
#NEC
SUBSYSTEM==usb, SYSFS{idVendor}==0409, MODE=0666
#Nook
SUBSYSTEM==usb, SYSFS{idVendor}==2080, MODE=0666
#Nvidia
SUBSYSTEM==usb, SYSFS{idVendor}==0955, MODE=0666
#OTGV
SUBSYSTEM==usb, SYSFS{idVendor}==2257, MODE=0666
#Pantech
SUBSYSTEM==usb, SYSFS{idVendor}==10A9, MODE=0666
#Philips
SUBSYSTEM==usb, SYSFS{idVendor}==0471, MODE=0666
#PMC-Sierra
SUBSYSTEM==usb, SYSFS{idVendor}==04da, MODE=0666
#Qualcomm
SUBSYSTEM==usb, SYSFS{idVendor}==05c6, MODE=0666
#SK Telesys
SUBSYSTEM==usb, SYSFS{idVendor}==1f53, MODE=0666
#Samsung
SUBSYSTEM==usb, SYSFS{idVendor}==04e8, MODE=0666
#Sharp
SUBSYSTEM==usb, SYSFS{idVendor}==04dd, MODE=0666
#Sony Ericsson
SUBSYSTEM==usb, SYSFS{idVendor}==0fce, MODE=0666
#Toshiba
SUBSYSTEM==usb, SYSFS{idVendor}==0930, MODE=0666
#ZTE
SUBSYSTEM==usb, SYSFS{idVendor}==19D2, MODE=0666
4) Save the file and close it and then issue this command:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
6) Reboot PC:
7) Initialize the repo:
Code:
mkdir WORKING_DIRECTORY
cd WORKING_DIRECTORY
- For AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.3_r1
- For CM9
repo init -u git://github.com/CyanogenMod/android.git -b ics
- For AOKP
repo init -u git://github.com/AOKP/platform_manifest.git -b master
- For IceColdSandwitch
repo init -u git://github.com/IceColdSandwich/android.git -b ics
8) When prompted, enter your real name and email address.
9) Gather the files:
Code:
repo sync
10) Compiling:
Code:
source build/envsetup.sh
Or:
. build/envsetup.sh
11) Issue:
Code:
lunch
12) Pick your poison.
13) Now issue:
Code:
make -j4
Build for Sony Ericsson device
1) Download sources for ARMv6
Code:
cd ~/WORKING_DIRECTORY/
repo init -u git://github.com/MSM7x27-Xperia/android.git -b ics
repo sync -j4 or low if you have bad internet
2) Compile:
Code:
source build/envsetup.sh
Or:
. build/envsetup.sh
4) Get your list of devices:
Code:
lunch
5) Pick your poison.
6) Now compile:
Code:
make -j4
- Or for a flashable zip:
Code:
make -j4 otapackage
NOTE
If you are running into issues such as:
Code:
Which would you like? [full-eng] 5
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
Device shooter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for shooter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
** Don't have a product spec for: 'full_shooter'
** Do you have the right repo manifest?
What you need to do is to edit your blob to match the PRODUCT_NAME to the file name. For example with mine I have full_shooter.mk therefore in this file I need to have PRODUCT_NAME to match it. Whatever error it is looking for you just need to change the PRODUCT_NAME line to match what the error shows.
Supplement, if something is missing
Nice tutorial thanks.
Sent from my GT-N7000
Great for sharing this howto with us
MiKa
In future versions of udev, "SYSFS" will be deprecated and has to be replaced by "ATTR". So it depends on what version of udev is installed in your distribution.
Cheers,
ff0000.it
is this tutorial compatible with another Smartphones?
ocovarr112 said:
is this tutorial compatible with another Smartphones?
Click to expand...
Click to collapse
Yes, you just need propietary files, but is almost the same process
PD: Paul, im setting up my dev enviroment, soon ill help you a bit on framework, and maybe I learn C and help you on libs
PD2: Ubuntu 11.10 original unity interface sux.. i like Gnome
EDIT: 15 mins and after i thought it was ok, then
device/semc/msm7x27-common/libgralloc/mapper.cpp: In function 'int gralloc_perform(const gralloc_module_t*, int, ...)':
Freaking classic on android -.-, Ill try again 2morrow
Good Luck!
D4rKn3sSyS said:
Yes, you just need propietary files, but is almost the same process
PD: Paul, im setting up my dev enviroment, soon ill help you a bit on framework, and maybe I learn C and help you on libs
PD2: Ubuntu 11.10 original unity interface sux.. i like Gnome
EDIT: 15 mins and after i thought it was ok, then
device/semc/msm7x27-common/libgralloc/mapper.cpp: In function 'int gralloc_perform(const gralloc_module_t*, int, ...)':
Freaking classic on android -.-, Ill try again 2morrow
Click to expand...
Click to collapse
Great to see u man!! hope both of u get fully working ics soon All the best!
D4rKn3sSyS said:
Yes, you just need propietary files, but is almost the same process
PD: Paul, im setting up my dev enviroment, soon ill help you a bit on framework, and maybe I learn C and help you on libs
PD2: Ubuntu 11.10 original unity interface sux.. i like Gnome
EDIT: 15 mins and after i thought it was ok, then
device/semc/msm7x27-common/libgralloc/mapper.cpp: In function 'int gralloc_perform(const gralloc_module_t*, int, ...)':
Freaking classic on android -.-, Ill try again 2morrow
Click to expand...
Click to collapse
gralloc from 2.3 rom. remove he and contune.
D4rKn3sSyS
With new sources i have here error
Code:
target thumb C++: liboverlay <= hardware/qcom/display/liboverlay/overlayLib.cpp
target thumb C++: liboverlay <= hardware/qcom/display/liboverlay/overlayLibUI.cpp
hardware/qcom/display/liboverlay/overlayLib.cpp:122:1: warning: "LOG_TAG" redefined
In file included from hardware/qcom/display/liboverlay/overlayLib.h:21,
from hardware/qcom/display/liboverlay/overlayLib.cpp:18:
system/core/include/cutils/log.h:68:1: warning: this is the location of the previous definition
hardware/qcom/display/liboverlay/overlayLibUI.cpp:20:1: warning: "LOG_TAG" redefined
In file included from hardware/qcom/display/liboverlay/overlayLib.h:21,
from hardware/qcom/display/liboverlay/overlayLibUI.h:23,
from hardware/qcom/display/liboverlay/overlayLibUI.cpp:18:
system/core/include/cutils/log.h:68:1: warning: this is the location of the previous definition
host Java: android-mock-generatorlib (out/host/common/obj/JAVA_LIBRARIES/android-mock-generatorlib_intermediates/classes)
hardware/qcom/display/liboverlay/overlayLib.cpp: In function 'int overlay::get_mdp_format(int)':
hardware/qcom/display/liboverlay/overlayLib.cpp:57: error: 'MDP_Y_CRCB_H2V2_TILE' was not declared in this scope
hardware/qcom/display/liboverlay/overlayLib.cpp: In function 'int overlay::get_rot_output_format(int)':
hardware/qcom/display/liboverlay/overlayLib.cpp:90: error: 'MDP_Y_CRCB_H2V2_TILE' was not declared in this scope
hardware/qcom/display/liboverlay/overlayLibUI.h: In constructor 'overlay::OverlayUI::OverlayUI()':
hardware/qcom/display/liboverlay/overlayLibUI.h:101: warning: 'overlay::OverlayUI::mFBNum' will be initialized after
hardware/qcom/display/liboverlay/overlayLibUI.h:99: warning: 'int overlay::OverlayUI::mZorder'
hardware/qcom/display/liboverlay/overlayLibUI.cpp:226: warning: when initialized here
host C++: colladadom <= external/collada/src/dae/dae.cpp
host C++: colladadom <= external/collada/src/dae/daeArray.cpp
hardware/qcom/display/liboverlay/overlayLibUI.cpp: In member function 'overlay::status_t overlay::OverlayUI::closeOVSession()':
hardware/qcom/display/liboverlay/overlayLibUI.cpp:409: warning: suggest parentheses around assignment used as truth value
hardware/qcom/display/liboverlay/overlayLib.cpp: In member function 'bool overlay::OverlayControlChannel::setOverlayInformation(const overlay_buffer_info&, int, int, int, bool, int)':
hardware/qcom/display/liboverlay/overlayLib.cpp:958: error: 'MDP_Y_CRCB_H2V2_TILE' was not declared in this scope
hardware/qcom/display/liboverlay/overlayLib.cpp: In member function 'bool overlay::OverlayControlChannel::startOVRotatorSessions(const overlay_buffer_info&, int, int)':
hardware/qcom/display/liboverlay/overlayLib.cpp:1013: error: 'MDP_Y_CRCB_H2V2_TILE' was not declared in this scope
hardware/qcom/display/liboverlay/overlayLib.cpp: In member function 'bool overlay::OverlayControlChannel::setPosition(int, int, uint32_t, uint32_t)':
hardware/qcom/display/liboverlay/overlayLib.cpp:1165: warning: comparison between signed and unsigned integer expressions
hardware/qcom/display/liboverlay/overlayLib.cpp:1166: warning: comparison between signed and unsigned integer expressions
hardware/qcom/display/liboverlay/overlayLib.cpp:1172: warning: comparison between signed and unsigned integer expressions
hardware/qcom/display/liboverlay/overlayLib.cpp:1172: warning: comparison between signed and unsigned integer expressions
hardware/qcom/display/liboverlay/overlayLib.cpp: In member function 'bool overlay::OverlayControlChannel::setTransform(int, bool)':
hardware/qcom/display/liboverlay/overlayLib.cpp:1244: warning: comparison between signed and unsigned integer expressions
hardware/qcom/display/liboverlay/overlayLib.cpp: In member function 'bool overlay::OverlayDataChannel::mapRotatorMemory(int, bool, int)':
hardware/qcom/display/liboverlay/overlayLib.cpp:1512: error: 'struct msmfb_data' has no member named 'flags'
make: *** [out/target/product/mimmi/obj/SHARED_LIBRARIES/liboverlay_intermediates/overlayLib.o] Ошибка 1
make: *** Ожидание завершения заданий...
host C++: colladadom <= external/collada/src/dae/daeAtomicType.cpp
Note: external/android-mock/src/com/google/android/testing/mocking/AndroidMock.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
[email protected]:~/android/system$
You need to set:
TARGET_SPECIFIC_HEADER_PATH := device/semc/<device>/include
and populate this with include files you need, e.g:
include/linux/msm_mdp.h
added instruction for build with new mimmi source
hi
i got this error:
build/core/product_config.mk:205: *** No matches for product "full_p970". Stop.
** Don't have a product spec for: 'full_p970'
** Do you have the right repo manifest
any ideas?
donjamal said:
hi
i got this error:
build/core/product_config.mk:205: *** No matches for product "full_p970". Stop.
** Don't have a product spec for: 'full_p970'
** Do you have the right repo manifest
any ideas?
Click to expand...
Click to collapse
give me link to your repo i look here
paul-xxx said:
give me link to your repo i look here
Click to expand...
Click to collapse
https://github.com/koush/proprietary_vendor_lge/tree/ics/p970
https://github.com/CyanogenMod/android_device_lge_p970
its 2.3 we dont have any ics rom..so im trying it from zero
donjamal said:
https://github.com/koush/proprietary_vendor_lge/tree/ics/p970
https://github.com/CyanogenMod/android_device_lge_p970
its 2.3 we dont have any ics rom..so im trying it from zero
Click to expand...
Click to collapse
from proprietary remove camera libs
and in android_device_lge_p970
make cm.mk
and add here
Code:
## Specify phone tech before including full_phone
$(call inherit-product, vendor/cm/config/gsm.mk)
# Release name
PRODUCT_RELEASE_NAME := P970
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
# Inherit device configuration
$(call inherit-product, device/semc/mimmi/device_p970.mk)
# Setup device configuration
PRODUCT_DEVICE := p970
PRODUCT_NAME := cm_p970
PRODUCT_BRAND := lge
PRODUCT_MODEL := Optimus Black
PRODUCT_MANUFACTURER := LG
# Release name and versioning
PRODUCT_VERSION_DEVICE_SPECIFIC :=
TARGET_NO_LIVEWALLPAPERS := false
#Set build fingerprint / ID / Product Name ect.
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=p970 BUILD_ID=ITL41F BUILD_DISPLAY_ID=ITL41F BUILD_FINGERPRINT="google/yakju/maguro:4.0.1/ITL41F/228551:user/release-keys" PRIVATE_BUILD_DESC="yakju-user 4.0.1 ITL41F 228551 release-keys"
then rename p970.mk to device_p970.mk
and try
paul-xxx said:
from proprietary remove camera libs
and in android_device_lge_p970
make cm.mk
and add here
Code:
## Specify phone tech before including full_phone
$(call inherit-product, vendor/cm/config/gsm.mk)
# Release name
PRODUCT_RELEASE_NAME := P970
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
# Inherit device configuration
$(call inherit-product, device/semc/mimmi/device_p970.mk)
# Setup device configuration
PRODUCT_DEVICE := p970
PRODUCT_NAME := cm_p970
PRODUCT_BRAND := lge
PRODUCT_MODEL := Optimus Black
PRODUCT_MANUFACTURER := LG
# Release name and versioning
PRODUCT_VERSION_DEVICE_SPECIFIC :=
TARGET_NO_LIVEWALLPAPERS := false
#Set build fingerprint / ID / Product Name ect.
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=p970 BUILD_ID=ITL41F BUILD_DISPLAY_ID=ITL41F BUILD_FINGERPRINT="google/yakju/maguro:4.0.1/ITL41F/228551:user/release-keys" PRIVATE_BUILD_DESC="yakju-user 4.0.1 ITL41F 228551 release-keys"
then rename p970.mk to device_p970.mk
and try
Click to expand...
Click to collapse
got this
build/core/product_config.mk:193: *** _nic.PRODUCTS.[[device/lge/p970/p970.mk]]: "device/lge/p970/p970.mk" does not exist. Stop.
** Don't have a product spec for: 'p970'
** Do you have the right repo manifest?
---------- Post added at 10:39 AM ---------- Previous post was at 10:19 AM ----------
donjamal said:
got this
build/core/product_config.mk:193: *** _nic.PRODUCTS.[[device/lge/p970/p970.mk]]: "device/lge/p970/p970.mk" does not exist. Stop.
** Don't have a product spec for: 'p970'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
somehow after about million copy paste it worked
but with make -j1 otapackage run this
============================================
find: "omapmmlib/java": Nincs ilyen fájl vagy könyvtár
find: "omapmmlib/java": Nincs ilyen fájl vagy könyvtár
build/core/base_rules.mk:78: *** Module name: dspexec
build/core/base_rules.mk:79: *** Makefile location: hardware/ti/omap3/dspbridge/dspexec
build/core/base_rules.mk:80: *
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: *
build/core/base_rules.mk:84: * optional, debug, eng, tests, samples
build/core/base_rules.mk:85: *
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag:
build/core/base_rules.mk:89: *
build/core/base_rules.mk:90: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: * Android.mk for the affected module, and add
build/core/base_rules.mk:92: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: * makefile(s) where it's necessary, if
build/core/base_rules.mk:95: * appropriate.
build/core/base_rules.mk:96: *
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: *
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.
but if u are boring u could build one for me
but with make -j1 otapackage run this
Click to expand...
Click to collapse
im no tried
stuck
hey paul im stuck by
Build for mimmi with new sources
1) Download patched webrtc for ARMv6
but my device is a lg optimus black P970 so which files do i need=
kaassaus said:
hey paul im stuck by
Build for mimmi with new sources
1) Download patched webrtc for ARMv6
but my device is a lg optimus black P970 so which files do i need=
Click to expand...
Click to collapse
patched webrtc no need
only compatiable repo with ICS sources
Hello. I will teaching you how to build CM10 from source. You will need: a computer, lots of patience, and lots of time. I am writing this guide because I want more people to try and develop ROMs for the Droid RAZR and also so things will get fixed faster with more people working on them.
Step 1: Install Ubuntu (10.04 - 11.10 ONLY)
You will need a 64-bit version of Ubuntu for this. I think most computers should be compatible because I run 64-bit on my HP Mini netbook. I will be posting another thread later on how to do this. DO NOT INSTALL 12.04. It is only experimental.
Step 2: Install Android SDK
The next step is to install the Android SDK. Go here and install everything except MTP support for Galaxy Nexus. It will install the files to /usr/local/android-sdk.
Step 3: Install Java Developer Kit (JDK)
Next you will need to install the Java 6 JDK. To install it, open a terminal by pressing: Ctrl+Alt+T. Then enter this:
Code:
$ sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
$ sudo apt-get update
$ sudo apt-get install sun-java6-jdk
Remember to press enter after every line and if you encounter any errors please PM me.
Step 4: Install Python
Now, you will need to install Python. On some versions of Ubuntu it is already included, but it doesn't hurt to check. Enter this into a terminal:
Code:
$ sudo apt-get install python
Step 5: Install Git
Now it is time to install Git. It is one of the coolest, yet most confusing things, about Android/Linux. Think of it like this--it's a place where all of the revisions to the code go to be approved and get incorporated so that you have a solid piece of working software. To install enter this:
Code:
$ sudo apt-get install git-core
Step 6: Install Required Packages
It is time to install more "specific" packages to compiling android. If you are running Ubuntu 64-bit 10.04 - 11.10 (if you are running 11.10 skip to next set of packages) install:
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils xsltproc
If you are running 10.10 install these:
Code:
$ sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
If you are running 11.10 install these:
Code:
$ sudo apt-get install libx11-dev:i386
Step 7: Configure USB Access
Note- You may already have this step done by following the link for setting up the Android SDK, but if you have errors come back to this step. If it still does not help you, PM me.
In order for ADB to work properly, you need to have USB access configured. Type these commands:
Code:
gksudo gedit /etc/udev/rules.d/99-android.rules
Add these lines to the file:
Code:
#Acer
SUBSYSTEM==usb, SYSFS{idVendor}==0502, MODE=0666
#ASUS
SUBSYSTEM==usb, SYSFS{idVendor}==0b05, MODE=0666
#Dell
SUBSYSTEM==usb, SYSFS{idVendor}==413c, MODE=0666
#Foxconn
SUBSYSTEM==usb, SYSFS{idVendor}==0489, MODE=0666
#Garmin-Asus
SUBSYSTEM==usb, SYSFS{idVendor}==091E, MODE=0666
#Google
SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666
#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE=0666
#Huawei
SUBSYSTEM==usb, SYSFS{idVendor}==12d1, MODE=0666
#K-Touch
SUBSYSTEM==usb, SYSFS{idVendor}==24e3, MODE=0666
#KT Tech
SUBSYSTEM==usb, SYSFS{idVendor}==2116, MODE=0666
#Kyocera
SUBSYSTEM==usb, SYSFS{idVendor}==0482, MODE=0666
#Lenevo
SUBSYSTEM==usb, SYSFS{idVendor}==17EF, MODE=0666
#LG
SUBSYSTEM==usb, SYSFS{idVendor}==1004, MODE=0666
#Motorola
SUBSYSTEM==usb, SYSFS{idVendor}==22b8, MODE=0666
#NEC
SUBSYSTEM==usb, SYSFS{idVendor}==0409, MODE=0666
#Nook
SUBSYSTEM==usb, SYSFS{idVendor}==2080, MODE=0666
#Nvidia
SUBSYSTEM==usb, SYSFS{idVendor}==0955, MODE=0666
#OTGV
SUBSYSTEM==usb, SYSFS{idVendor}==2257, MODE=0666
#Pantech
SUBSYSTEM==usb, SYSFS{idVendor}==10A9, MODE=0666
#Philips
SUBSYSTEM==usb, SYSFS{idVendor}==0471, MODE=0666
#PMC-Sierra
SUBSYSTEM==usb, SYSFS{idVendor}==04da, MODE=0666
#Qualcomm
SUBSYSTEM==usb, SYSFS{idVendor}==05c6, MODE=0666
#SK Telesys
SUBSYSTEM==usb, SYSFS{idVendor}==1f53, MODE=0666
#Samsung
SUBSYSTEM==usb, SYSFS{idVendor}==04e8, MODE=0666
#Sharp
SUBSYSTEM==usb, SYSFS{idVendor}==04dd, MODE=0666
#Sony Ericsson
SUBSYSTEM==usb, SYSFS{idVendor}==0fce, MODE=0666
#Toshiba
SUBSYSTEM==usb, SYSFS{idVendor}==0930, MODE=0666
#ZTE
SUBSYSTEM==usb, SYSFS{idVendor}==19D2, MODE=0666
After that save and close the file. Then enter this:
Code:
$ sudo chmod a+r /etc/udev/rules.d/99-android.rules
Now you are done setting up the build environment and we can start downloading the source code.
Step 8: Downloading the source code and configuring repo
Create a /bin directory in the home directory using these commands:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
Download the Repo script and ensure it is executable (works):
Code:
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Now make a working directory:
Code:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
Note- WORKING_DIRECTORY can be anything you want it to be
Now we need to initialize repo into your WORKING_DIRECTORY:
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Note- If you exit the terminal aafter this you will need to repeat this step
That will initialize Cyanogenmod repo into your WORKING_DIRECTORY. Now we need to put the STS-Dev-Team's local_manifest.xml into our build directory so we can use their source. Enter these commands:
Code:
$ curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/STS-Dev-Team/android_local_STS/jellybean-cm-kexec/local_manifest.xml
Then you have to get prebuilts:
Code:
./vendor/cm/get-prebuilts
Last but not least, we need to sync with the repo:
Code:
repo sync
Note- This step could take a long time depending on your internet connection. Please plan wisely.
If there is an error syncing prebuilt just enter:
Code:
repo sync prebuilt
That should fix it and do another repo sync after to make sure you get all of the source downloaded.
Step 9: Verify GIT Tags
To verify the tags enter this:
Code:
gpg --import
After that copy and past this big 'ol list into the terminal and press Ctrl + D after you're done:
Code:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
mQGiBEnnWD4RBACt9/h4v9xnnGDou13y3dvOx6/t43LPPIxeJ8eX9WB+8LLuROSV
lFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw7
8tR1cXb197Ob8kOfQB3A9yk2XZ4ei4ZC3i6wVdqHLRxABdncwu5hOF9KXwCgkxMD
u4PVgChaAJzTYJ1EG+UYBIUEAJmfearb0qRAN7dEoff0FeXsEaUA6U90sEoVks0Z
wNj96SA8BL+a1OoEUUfpMhiHyLuQSftxisJxTh+2QclzDviDyaTrkANjdYY7p2cq
/HMdOY7LJlHaqtXmZxXjjtw5Uc2QG8UY8aziU3IE9nTjSwCXeJnuyvoizl9/I1S5
jU5SA/9WwIps4SC84ielIXiGWEqq6i6/sk4I9q1YemZF2XVVKnmI1F4iCMtNKsR4
MGSa1gA8s4iQbsKNWPgp7M3a51JCVCu6l/8zTpA+uUGapw4tWCp4o0dpIvDPBEa9
b/aF/ygcR8mh5hgUfpF9IpXdknOsbKCvM9lSSfRciETykZc4wrRCVGhlIEFuZHJv
aWQgT3BlbiBTb3VyY2UgUHJvamVjdCA8aW5pdGlhbC1jb250cmlidXRpb25AYW5k
cm9pZC5jb20+iGAEExECACAFAknnWD4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIX
gAAKCRDorT+BmrEOeNr+AJ42Xy6tEW7r3KzrJxnRX8mij9z8tgCdFfQYiHpYngkI
2t09Ed+9Bm4gmEO5Ag0ESedYRBAIAKVW1JcMBWvV/0Bo9WiByJ9WJ5swMN36/vAl
QN4mWRhfzDOk/Rosdb0csAO/l8Kz0gKQPOfObtyYjvI8JMC3rmi+LIvSUT9806Up
hisyEmmHv6U8gUb/xHLIanXGxwhYzjgeuAXVCsv+EvoPIHbY4L/KvP5x+oCJIDbk
C2b1TvVk9PryzmE4BPIQL/NtgR1oLWm/uWR9zRUFtBnE411aMAN3qnAHBBMZzKMX
LWBGWE0znfRrnczI5p49i2YZJAjyX1P2WzmScK49CV82dzLo71MnrF6fj+Udtb5+
OgTg7Cow+8PRaTkJEW5Y2JIZpnRUq0CYxAmHYX79EMKHDSThf/8AAwUIAJPWsB/M
pK+KMs/s3r6nJrnYLTfdZhtmQXimpoDMJg1zxmL8UfNUKiQZ6esoAWtDgpqt7Y7s
KZ8laHRARonte394hidZzM5nb6hQvpPjt2OlPRsyqVxw4c/KsjADtAuKW9/d8phb
N8bTyOJo856qg4oOEzKG9eeF7oaZTYBy33BTL0408sEBxiMior6b8LrZrAhkqDjA
vUXRwm/fFKgpsOysxC6xi553CxBUCH2omNV6Ka1LNMwzSp9ILz8jEGqmUtkBszwo
G1S8fXgE0Lq3cdDM/GJ4QXP/p6LiwNF99faDMTV3+2SAOGvytOX6KjKVzKOSsfJQ
hN0DlsIw8hqJc0WISQQYEQIACQUCSedYRAIbDAAKCRDorT+BmrEOeCUOAJ9qmR0l
EXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM=
=Wi5D
-----END PGP PUBLIC KEY BLOCK-----
To verify an individual tag enter:
Code:
$ git tag -v TAG_NAME
Step 10: Building CM10
The next step is to build it. If you know how to write Java for android you can modify the source code, but if you don't, then just enter this command and it will start building:
Code:
. build/envsetup.sh && brunch spyder
Then wait for it to finish building. On my machine it took me 15 hours for a single build, so it might be a while.
If you want to make it faster take the amount of cores you have and add 1 and replace that number with the "#" sign in the following command:
Code:
. build/envsetup.sh && brunch spyder -j#
If you are rebuilding, first switch into the root of your WORKING_DIRECTORY and type:
Code:
make clobber
Sorry, forgot to include this:
Code:
repo sync
Then type:
Code:
. build/envsetup && brunch spyder -j#
When it finishes you will have a .zip file in WORKING_DIRECTORY/out/target/product/spyder and you can flash it in recovery(preferably safestrap). Make sure you make a nandroid and do a full wipe. Wipe data, wipe cache partition, wipe dalvik cache, format /system. If you need to modify build.prop open the .zip and open it in a text editor and save it. Then update in the archive.
If you release it please credit the STS-Dev-Team for their source.
Thanks guys for reading this, please hit the thanks button and PM me if you have any questions. Have a good day
Credits: @dhacker29, @Hashcode0f, mattlgroff, and STS-Dev-Team
Sent from my CM10 ROM built using this guide.
***RESERVED***
RESERVED
Great article, I'm going to have to run through this ASAP.
i will try
Enviado desde mi XT910 usando Tapatalk 2
Thanks!
But basically what this guide explains is how to compile the latest razr build from sts source?
DanielMod said:
Thanks!
But basically what this guide explains is how to compile the latest razr build from sts source?
Click to expand...
Click to collapse
Yes, and after you download the source you can modify it, and I think you can compile full AOSP and AOKP, but I'll try that later. The advantage of doing this is that you get latest stuff For example when I did this a few days ago, Google had just released 4.1.2 source, so I did a repo sync and compiled and had 4.1.2 on my Razr since the 12th of October.
DROIDRAZ said:
Yes, and after you download the source you can modify it, and I think you can compile full AOSP and AOKP, but I'll try that later. The advantage of doing this is that you get latest stuff For example when I did this a few days ago, Google had just released 4.1.2 source, so I did a repo sync and compiled and had 4.1.2 on my Razr since the 12th of October.
Click to expand...
Click to collapse
Seems quiet nice but I for example know nothing about ROM development so I cant really customize anything
DanielMod said:
Seems quiet nice but I for example know nothing about ROM development so I cant really customize anything
Click to expand...
Click to collapse
You can modify the images and make it more custom
Sent from my own CM10 ROM built from source
Should this be Stickied?
Sent from my own CM10 ROM built from source
Thanks for this guide! Maybe a dumb question..but..If I want to modify the rom before compiling it I have to play with the source code, right? The advantage here is e.g. it will create me an working updater-script etc...? And can I just update the source to my rom with the rebuild command?
dtrail1 said:
Thanks for this guide! Maybe a dumb question..but..If I want to modify the rom before compiling it I have to play with the source code, right? The advantage here is e.g. it will create me an working updater-script etc...? And can I just update the source to my rom with the rebuild command?
Click to expand...
Click to collapse
Yes but I have not found a way to edit framework-res.apk so what I did is I extracted it from .zip and used apktool to modify it and replaced it in the archive. To update source first
Make clobber
Then
Repo sync
Then . build/envsetup.sh && brunch spyder
Sent from my own CM10 ROM built from source
Updated guide because I forgot a step
Sent from my own CM10 ROM built from source
Can you please describe how to make ZIP image from img files ?
I compiled AOSP and can't find way to flash it.
silentjet said:
Can you please describe how to make ZIP image from img files ?
I compiled AOSP and can't find way to flash it.
Click to expand...
Click to collapse
Do you mean like how to combine the whole thing into a .zip file? I'm not quite sure what you mean
Sent from my own CM10 ROM built from source
This guide is valid to umts_spyder?
Sent from my XT910 using xda premium
motopuk said:
This guide is valid to umts_spyder?
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
When compiling try:
. build/envsetup.sh && brunch umts_spyder
I don't have access to my computer so I can't check the name but I think that is it.
Sent from my own CM10 ROM built from source
repo sync take very long time, if you want to make it shorter, you can edit your local_manifest.xml to match only with the device you want to build.
it looks like (for umts_spyder):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="omapzoom"
fetch="git://git.omapzoom.org/" />
<!-- CM removals -->
<!-- <remove-project name="CyanogenMod/android_bionic" /> -->
<remove-project name="CyanogenMod/android_build" />
<remove-project name="CyanogenMod/android_development" />
<remove-project name="CyanogenMod/android_frameworks_av" />
<remove-project name="CyanogenMod/android_frameworks_base" />
<remove-project name="CyanogenMod/android_frameworks_native" />
<remove-project name="CyanogenMod/android_hardware_libhardware" />
<remove-project name="CyanogenMod/android_hardware_libhardware_legacy" />
<remove-project name="CyanogenMod/android_hardware_ril" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4xxx" />
<remove-project name="CyanogenMod/android_hardware_ti_wlan" />
<remove-project name="CyanogenMod/android_hardware_ti_wpan" />
<remove-project name="CyanogenMod/android_hardware_qcom_media" />
<remove-project name="CyanogenMod/android_packages_apps_Bluetooth" />
<remove-project name="CyanogenMod/android_packages_apps_Contacts" />
<remove-project name="CyanogenMod/android_packages_apps_Mms" />
<remove-project name="CyanogenMod/android_packages_apps_Phone" />
<remove-project name="CyanogenMod/android_packages_apps_Settings" />
<remove-project name="CyanogenMod/android_packages_apps_Stk" />
<remove-project name="CyanogenMod/android_packages_apps_VoiceDialer" />
<remove-project name="CyanogenMod/android_packages_apps_CMUpdater" />
<remove-project name="CyanogenMod/android_packages_providers_ContactsProvider" />
<remove-project name="CyanogenMod/android_packages_providers_DrmProvider" />
<remove-project name="CyanogenMod/android_packages_providers_TelephonyProvider" />
<remove-project name="CyanogenMod/android_system_core" />
<!-- CM replacements -->
<project path="build" name="STS-Dev-Team/android_build" >
<copyfile src="core/root.mk" dest="Makefile" />
</project>
<!-- <project path="bionic" name="STS-Dev-Team/android_bionic" /> -->
<project path="development" name="STS-Dev-Team/android_development" />
<project path="frameworks/av" name="STS-Dev-Team/android_frameworks_av" />
<project path="frameworks/base" name="STS-Dev-Team/android_frameworks_base" revision="jellybean-3way" />
<project path="frameworks/native" name="STS-Dev-Team/android_frameworks_native" />
<project path="hardware/libhardware" name="STS-Dev-Team/android_hardware_libhardware" />
<project path="hardware/libhardware_legacy" name="STS-Dev-Team/android_hardware_libhardware_legacy" />
<project path="hardware/ril" name="STS-Dev-Team/android_hardware_ril" />
<project path="hardware/ti/omap4xxx" name="STS-Dev-Team/android_hardware_ti_omap4xxx" revision="jellybean-stock" />
<project path="hardware/ti/wpan" name="Hashcode/android_hardware_ti_wpan" revision="jellybean" />
<project path="packages/apps/Bluetooth" name="STS-Dev-Team/android_packages_apps_Bluetooth" />
<project path="packages/apps/Contacts" name="STS-Dev-Team/android_packages_apps_Contacts" />
<project path="packages/apps/Mms" name="STS-Dev-Team/android_packages_apps_Mms" />
<project path="packages/apps/Phone" name="STS-Dev-Team/android_packages_apps_Phone" />
<project path="packages/apps/Settings" name="STS-Dev-Team/android_packages_apps_Settings" />
<project path="packages/apps/Stk" name="STS-Dev-Team/android_packages_apps_Stk" />
<project path="packages/apps/VoiceDialer" name="STS-Dev-Team/android_packages_apps_VoiceDialer" />
<project path="packages/providers/ContactsProvider" name="STS-Dev-Team/android_packages_providers_ContactsProvider" />
<project path="packages/providers/DrmProvider" name="STS-Dev-Team/android_packages_providers_DrmProvider" />
<project path="packages/providers/TelephonyProvider" name="STS-Dev-Team/android_packages_providers_TelephonyProvider" />
<project path="system/core" name="STS-Dev-Team/android_system_core" />
[COLOR="Red"] <!-- local devices -->
<project path="device/motorola/common" name="STS-Dev-Team/android_device_motorola_common" revision="jb" />
<project path="device/motorola/umts_spyder" name="STS-Dev-Team/android_device_motorola_umts_spyder" revision="jb" />
<!-- local vendor -->
<project path="vendor/motorola/common" name="STS-Dev-Team/android_vendor_motorola_common" revision="jb" />
<project path="vendor/motorola/umts_spyder" name="STS-Dev-Team/android_vendor_motorola_umts_spyder" revision="master" />[/COLOR]
<!-- local misc -->
<project path="frameworks/opt/telephony" name="STS-Dev-Team/android_frameworks_opt_telephony" revision="jellybean"/>
<project path="packages/apps/FileManager" name="STS-Dev-Team/android_packages_apps_FileManager" revision="ics" />
<project path="kernel/motorola/omap4_xt912" name="STS-Dev-Team/kernel_omap4_xt912" revision="master" />
<project path="prebuilt/linux-x86/toolchain/arm-eabi-4.7" name="STS-Dev-Team/arm-eabi-4.7" revision="master" />
<!-- TI addons -->
<project path="device/ti/common-open" name="device/ti/common-open" remote="omapzoom" revision="jb-release" />
<project path="device/ti/proprietary-open" name="device/ti/proprietary-open" remote="omapzoom" revision="jb-release" />
<project path="external/bltsville" name="platform/external/bltsville" remote="omapzoom" revision="master"/>
<project path="external/crda" name="platform/external/crda" remote="omapzoom" revision="p-ics-mr0" />
<project path="external/wpa_supplicant_8_ti" name="platform/external/wpa_supplicant_8_ti" remote="omapzoom" revision="jb-release" />
<project path="frameworks/opt/mms" name="platform/frameworks/opt/mms" remote="omapzoom" revision="master"/>
<!-- <project path="hardware/ti/domx" name="platform/hardware/ti/domx" remote="omapzoom" revision="jb-release" /> -->
<project path="hardware/ti/wlan" name="platform/hardware/ti/wlan" remote="omapzoom" revision="p-jb-release" />
<project path="packages/apps/OMAPCamera" name="platform/packages/apps/OMAPCamera" remote="omapzoom" revision="jb-release" />
<project path="packages/apps/otaupdater" name="STS-Dev-Team/ota-update-centre" revision="noicon" />
</manifest>
just keep "common" & "umts_spyder" in local device & local vendor, then you wont have whole source for all devices supported.
DROIDRAZ said:
Do you mean like how to combine the whole thing into a .zip file? I'm not quite sure what you mean
Sent from my own CM10 ROM built from source
Click to expand...
Click to collapse
Yeah, exactly.
I guess then that making:
Code:
build/envsetup.sh && brunch umts_spyder
Will compile the GSM version ?
firstly id like to thank project rookie over in the skyrocket section as i used their guide for this and changed it up for quincyatt, you guys are doing a great job promoting building keep it up! hope i can continue that here!
Instructions for building unofficial CM-10.1 and CM-10,2 for quincyatt
Disclaimer:
The releases, instructions, and extras posted here are to be used at your own risk. We work hard to provide good, workable knowledge and builds, and test our work before posting it up front. Nevertheless, no one is responsible if you lose your files, brick your device, or inadvertently cause a nuclear war. If you are seeking absolute perfection, RUN NOW WHILE YOU STILL CAN!!
READ ME THREE TIMES :
On one hand, it should go without saying that if you have no knowledge and/or experience with building, java, C++, and various other tools, you probably shouldn't begin here. At the same time, it is possible to learn to build, provided you can read, follow directions, and aren't too lazy to RESEARCH. OH YEAH, and you better have patience. It ain't easy. It will be work. The quickest way to get flamed is to show yourself to be lazy. If you think that with a couple clicks, you can have your own flashy ROM, forget it. But, if you do want to learn, this is a good place to get started. Nobody here has an ego about this, and we all want to help. But, we all struggled to get to a successful point, and lazy, unmotivated people just irritate those who have had to learn from scratch too. THIS link should be your absolute most used link. Have a nice day
GETTING STARTED
THIS GUIDE IS FOR 64BIT LINUX OS
recommended: quadcore cpu, 8gb+ ram
Setting up your environment (only needs to be done once) :
Tip: Allocate at least 75 gigs of space for the building of ONE ROM. If you install ccache, you will want 90. A complete build directory can use as much as 100 gigs, so make sure you have plenty of room. One of the ways to fail out a build is too use all of your partition before acquiring all the neccesary files.
Here are the steps for setting up build environment from those 2 tutorials in correct order:
1)You need the following:
-JDK 6 if you wish to build Jellybean.
Code:
$ sudo apt-get install openjdk-6-jdk
-Python 2.4 -- 2.7, which you can download from python.org. Or:
Code:
$ sudo apt-get install python
-Git 1.7 or newer. You can find it at git-scm.com. Or:
Code:
$ sudo apt-get install git-core
-Android SDK:
Download the SDK here: http://developer.android.com/sdk/index.html
Extract the SDK and place it in your home directory.
I renamed my SDK to android-sdk to make it easier to navigate to.
Go to your home folder, press Ctrl+H to show hidden files, and open up your .bashrc file.
Add these lines at the bottom of the file:
Code:
# Android tools
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin
Find your .profile file and add this at the bottom of the file:
Code:
PATH="$HOME/android-sdk/tools:$HOME/android-sdk/platform-tools:$PATH"
You have now successfully installed the Android SDK.
To check for updates issue this into your terminal:
Code:
$ android
2) Install required packages. 64-bit (recommended)
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
On older versions of Ubuntu such as 11.10 you may need to do the following:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master. with that said, i build on 12.04 without issue
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Configure your USB.
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
4) Save the file and close it and then issue this command:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
This is what you need to begin building. From here, CM-10.1 can be built with a few additions and commands.
BUILDING UNOFFICIAL CM10.2 :
Create your work directory:
Code:
mkdir ~/"your directory name here" For example: mkdir ~/cm102
cd ~/cm102
Initialize the work directory:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
Create and edit local_manifest.xml in .repo: /.repo/local_manifests/local_manifest.xml (hidden folder press CTRL+H to unhide)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_quincyatt" path="device/samsung/quincyatt" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_quincy-common" path="device/samsung/quincy-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
</manifest>
Code:
repo sync -j16 (this will take a few hours, use -j4 if you have slower internet)
To Build:
Code:
. build/envsetup.sh (notice the period and space)
vendor/cm/get-prebuilts
repo sync -j16 (again use -j4 for slower internet)
brunch quincyatt -j7 (lower for slower cpu's)
**After you build, your repo files will remain in place. This will cause your future builds to be based from that specific time of additions and merges. Wiping or 'cleaning' your files often will ensure that your builds are the most up-to-date. To be sure that you start with a fresh repo at the beginning of every build, you should 'make clean' often. For example:
Code:
$ cd ~/cm102
$ make clean (or 'make clobber' without quotes)
If you want to have your 'cleaning service' done as part of your process, this is a way to achieve it:
Code:
$ cd cm102
$ repo sync -j16
$ . build/envsetup.sh && make clobber && brunch quincyatt -j7 (lower if you have a slower cpu)
This will make the cleaning process automatic.
The Git can be found here:
GIT
The Gerrit can be found here:
GERRIT
again thanks goes out to project rookie and everyone that has helped them! visit their thread *linked at top* and shoot them a thanks!
i will fine-tune the look of the thread over time including adding different rom's to build but if you know what your doing this should be pretty straight forward but also informative enough to possibly start learning
Lastly, please be kind to other users, this is a thread for learning so if your not going to be helpful just continue being a reader of this thread rather than a poster also if you see someone asking a question you can answer please do so! this thread is here to learn from and hopefully help grow the dev section and future phone sections
Building CM-10.1
BUILDING UNOFFICIAL CM10.1 :
Create your work directory:
Code:
mkdir ~/"your directory name here" For example: mkdir ~/cm101
cd ~/cm101
Initialize the work directory:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Create and edit local_manifest.xml in .repo: /.repo/local_manifests/local_manifest.xml (hidden folder press CTRL+H to unhide)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_quincyatt" path="device/samsung/quincyatt" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_quincy-common" path="device/samsung/quincy-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
</manifest>
Code:
repo sync -j16 (this will take a few hours, use -j4 if you have slower internet)
To Build:
Code:
. build/envsetup.sh (notice the period and space)
vendor/cm/get-prebuilts
repo sync -j16 (again use -j4 for slower internet)
CM_EXTRAVERSION=mycustombuild CM_SNAPSHOT=1 brunch cm_quincyatt-userdebug
**After you build, your repo files will remain in place. This will cause your future builds to be based from that specific time of additions and merges. Wiping or 'cleaning' your files often will ensure that your builds are the most up-to-date. To be sure that you start with a fresh repo at the beginning of every build, you should 'make clean' often. For example:
Code:
$ cd ~/cm101
$ make clean (or 'make clobber' without quotes)
If you want to have your 'cleaning service' done as part of your process, this is a way to achieve it:
Code:
$ cd cm101
$ repo sync -j16
$ . build/envsetup.sh && make clobber && CM_EXTRAVERSION=-mycustombuild CM_SNAPSHOT=1 brunch cm_quincyatt-userdebug
This will make the cleaning process automatic.
The Git can be found here:
GIT
The Gerrit can be found here:
GERRIT
This by no means makes you a developer, this is a good first step.
If you build, flash, works and you want to share post it in this thread with a no responsibility warning
This is a great resource for us, Thank you for continuing to support the note community:good:
Thank you for this. Very nice write up.
Sent from my phone using xda premium app
Not only thank you for this guide, and sharing your builds. But thanks for your time and contributing to this community! I truly appreciate it.
Thanks for the write up! Awesome resource for me to read about how certain things work.
Sweet!
Many thanks Jamie.
Sent from my SAMSUNG-SGH-I717 using xda premium
I think you need to export the env variables.. at least thats how i do it.. though it could be just habit
Code:
export CM_EXTRAVERSION=mycustombuild CM_SNAPSHOT=1
and you need a linebreak before
Code:
brunch cm_quincyatt-userdebug
but you can also shorten it..
Code:
brunch quincyatt
thats a matter of preference though
Me thinks those that request a ROM to have certain features, Now have step 1 to creating the ROM of "Their" dreams...
RaiderWill said:
Me thinks those that request a ROM to have certain features, Now have step 1 to creating the ROM of "Their" dreams...
Click to expand...
Click to collapse
lol, step 1 in a 1 million step line
chris41g said:
I think you need to export the env variables.. at least thats how i do it.. though it could be just habit
Code:
export CM_EXTRAVERSION=mycustombuild CM_SNAPSHOT=1
and you need a linebreak before
Code:
brunch cm_quincyatt-userdebug
but you can also shorten it..
Code:
brunch quincyatt
thats a matter of preference though
Click to expand...
Click to collapse
their are a few different variations none of them wrong, when i built cm10.1 i built with
Code:
time brunch quincyatt
id update op but it will just start to confuse people if i put 4 ways to build the same rom hahaha
note: https://github.com/TheMuppets/propr...2ea796dc3/quincyatt/proprietary/lib/libakm.so
this commit fix's orientation i believe, have atter *thanks chris for pointing that out*
Jaimie thanks for this guide, and a place to ask questions about building.
After messing around with various apks for a while, I decided to sink my teeth into working on a whole ROM, with the release of JB for the note.
I used the kitchen to do all the standard things and a few experiments.. and it only took 3 builds to get my note running pretty good with JB. Lol - I know - nowhere close to a dev yet.. but it's a start. So, I figure, on to source stuff and actually trying to build things that boot myself.
My xubuntu build is pretty solid and I've double checked dependies across more guides that I've read, than I can count. Lol
My question right now, and what I'm trying to understand, revolves around the repos. I just want to understand before I start downloading gigs worth of stuff that I may not need.
Browsing around on github, I see folders and files updated at various times even before JB was released for the note. So I'm assuming that a lot of files carried over from ICS, with no changes needed for JB to run on the note.
Does that also mean that the source has already been updated in these repos, with what Samsung released a few days back?
So, I set up all the repos you have in this guide - do I need to download the source zips to copy any files over, to build something stable? Or do I just count on the repos for everything?
I just want to make sure I understand how to work with repos correctly. I don't want to build a ROM that ends up with crappy sound or some bluetooth connection issue because I didn't know I was supposed to grab a lib file or something from the source zip or the stock rom, and throw it in the build. Lol
i am trying to build rootbox, how do i know what kernel to use?
and after i get done syncing i do ". build/envsetup.sh" and it says no such directory
Bradl79 said:
i am trying to build rootbox, how do i know what kernel to use?
and after i get done syncing i do ". build/envsetup.sh" and it says no such directory
Click to expand...
Click to collapse
i have not built rootbox myself but
if you dont know what kernel to use, always stick with the cm kernel, which is in the OP
dont stagger off from the norm yet
and if you havent yet i would start with building cm
i get error
make: *** [/home/bradley/rootbox/out/target/product/quincyatt/obj/STATIC_LIBRARIES/librpc_intermediates/clnt.o] Error 1
Bradl79 said:
i get error
make: *** [/home/bradley/rootbox/out/target/product/quincyatt/obj/STATIC_LIBRARIES/librpc_intermediates/clnt.o] Error 1
Click to expand...
Click to collapse
librpc is in hardware/msm7k which I'm guessing is part of the missing qcom stuff I talked about
<project path="hardware/msm7k" name="android_hardware_msm7k" remote="cm" revision="cm-10.1" />
its in their repo
i need more of the error your getting because thats not the actual error
Sent from my SAMSUNG-SGH-I747 using xda premium
BlownFuze said:
Jaimie thanks for this guide, and a place to ask questions about building.
After messing around with various apks for a while, I decided to sink my teeth into working on a whole ROM, with the release of JB for the note.
I used the kitchen to do all the standard things and a few experiments.. and it only took 3 builds to get my note running pretty good with JB. Lol - I know - nowhere close to a dev yet.. but it's a start. So, I figure, on to source stuff and actually trying to build things that boot myself.
My xubuntu build is pretty solid and I've double checked dependies across more guides that I've read, than I can count. Lol
My question right now, and what I'm trying to understand, revolves around the repos. I just want to understand before I start downloading gigs worth of stuff that I may not need.
Browsing around on github, I see folders and files updated at various times even before JB was released for the note. So I'm assuming that a lot of files carried over from ICS, with no changes needed for JB to run on the note.
Does that also mean that the source has already been updated in these repos, with what Samsung released a few days back?
So, I set up all the repos you have in this guide - do I need to download the source zips to copy any files over, to build something stable? Or do I just count on the repos for everything?
I just want to make sure I understand how to work with repos correctly. I don't want to build a ROM that ends up with crappy sound or some bluetooth connection issue because I didn't know I was supposed to grab a lib file or something from the source zip or the stock rom, and throw it in the build. Lol
Click to expand...
Click to collapse
such is the way of the life of building android, there is no certain guarantee that your build will be perfect, i cant count how many failed builds and bootloops ive gotten *4 failed builds today actually *LOL its part of the fun debugging it
but no nothing from our source has been merged into cyanogenmod or themuppets, the msm8660-common kernel we use is already based off 4.1.2 full sources from hercules which is our phone minus the pen and hdpi instead of xhdpi, what we are missing are some of the jb blobs, we are still using some ics ones LOL
Hi Sorry if it's wrong section for this question.
I started to port UT to Sensation, based on CM11. I've synced all required repositories:
device_htc_sensation
device_htc_msm8660-common
kernel_htc_msm8660
+ pyramid vendor.
Then I run those commands:
Code:
$ . build/envsetup.sh
including device/generic/x86/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/lge/hammerhead/vendorsetup.sh
including device/htc/pyramid/vendorsetup.sh
including device/asus/flo/vendorsetup.sh
including device/asus/deb/vendorsetup.sh
including device/asus/tilapia/vendorsetup.sh
including device/asus/grouper/vendorsetup.sh
including device/samsung/manta/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. mini_x86-userdebug
6. mini_armv7a_neon-userdebug
7. aosp_mako-userdebug
8. aosp_hammerhead-userdebug
9. cm_pyramid-userdebug
[...]
Which would you like? [aosp_arm-eng] 9
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_pyramid". Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
I've checked AndroidProducts.mk etc. and everything looks fine. I have no idea what to do more to fix this.
Could someone help me?
Thanks in advance!
Hi, so i've tried to compile TWRP inside CM14 source and i've been struggling with linking error for a while
Code:
system/core/adb/adb_auth_client.cpp:94: error: undefined reference to 'android_pubkey_decode'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
[ 80% 4855/6059] target C: libminzip ...ootable/recovery-twrp/minzip/SysUtil.c
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
#### make failed to build some targets (04:34 (mm:ss)) ####
It's basicly CM14 not changed at all. What i discovered is that in OUT folder inside static libraries there is no libcrypto-utils build. In fact there is a folder but just with export-includes.txt
Here is part of system/core/adb/Android.mk
Code:
include $(CLEAR_VARS)
LOCAL_CLANG := true
LOCAL_MODULE := libadbd
LOCAL_CFLAGS := $(LIBADB_CFLAGS) -DADB_HOST=0
LOCAL_SRC_FILES := \
$(LIBADB_SRC_FILES) \
adb_auth_client.cpp \
jdwp_service.cpp \
usb_linux_client.cpp \
LOCAL_SANITIZE := $(adb_target_sanitize)
# Even though we're building a static library (and thus there's no link step for
# this to take effect), this adds the includes to our path.
LOCAL_STATIC_LIBRARIES := libcrypto_utils_static libcrypto_static libbase
include $(BUILD_STATIC_LIBRARY)
And part of libcrypto_utils/Android.mk
Code:
include $(CLEAR_VARS)
LOCAL_MODULE := libcrypto_utils_static
LOCAL_SRC_FILES := android_pubkey.c
LOCAL_CFLAGS := -Wall -Werror -Wextra -std=c99
LOCAL_C_INCLUDES := $(LOCAL_PATH)/include
LOCAL_EXPORT_C_INCLUDE_DIRS := $(LOCAL_PATH)/include
LOCAL_STATIC_LIBRARIES := libcrypto_static
include $(BUILD_STATIC_LIBRARY)
Also header file is included in adb_auth_client.cpp
Code:
#include <crypto_utils/android_pubkey.h>
What am i doing wrong?
Have you fixed this? I have same problem and i do not know how to fix it ..
_______________SOLVED____________________
https://github.com/discipuloosho/an...mmit/22801f5f78b5b996b163d54cf5c886a2d6db81c7
Anyone got a fix for this?
HaoZeke said:
Anyone got a fix for this?
Click to expand...
Click to collapse
Have you searched/posted this question within the the following thread that's a guide to performing this?
[GUIDE][NOOB FRIENDLY]How to compile TWRP from source step by step by Hacker432
Good Luck!
~~~~~~~~~~~~~~~
I Am The Egg Man,
They Are The Egg Men.
I Am The Walrus!
Coo Coo Cachoo!
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE