Database Users

[GUIDE]Compile CM7 AOSP (Kanged edition) For Speedy on Linux

Ok so I was searching and searching for a guide on how to compile CM7 source, and finally found a way to do it on the latest Ubuntu 11.10 oneiric
Updated info for non-debian based systems thanks to Vicodan:
If you want to use this on fedora or non-debian based systems you will need to replace every command that says apt-get to yum. Thanks to Vicodan for pointing this out as I do not use fedora myself.
Hardware Requirements:
- A minimum dual core pc, the more ram the better
- A working wifi connection
- Linux Operating System. Either 32-bit or 64-bit will work
NOTE: 64-bit will run faster
Optional Recommended Software:
Many of these can be found in the software center using the search box
If you find multiple versions it's ok to install them all, unless it says
otherwise
- Python
Alternatively open the terminal application and type
Code:
$ sudo app-get install python
Note: Enter your login password to install
- awk and gawk
- 7zip
- RAR
Code:
$ sudo apt-get install rar
Step 1 java:
Setting up java is one of the most important step to getting your pc prepared for a build environment. First check the java version that is installed on your pc
NOTE: On Ubuntu 11.10, and variants, you need to enable the
parter repository to install sun-java6-jdk:
Code:
$ sudo add-apt-repository "deb http://archive.canonical.com/ maverick partner"
Code:
$ java -version
The correct version is:
Code:
java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
You must have a 1.6.x to compile on the gingerbread branch of cyanogenmod. If you have the correct version skip down to Step 2.
1a - First install the correct version:
Code:
$ sudo apt-get install sun-java6-jdk sun-java6-jre
1b - Now you will need to manually remove the other java version
Code:
$ sudo nautilus
This will open up a root file explorer. Once it opens click on the "file
system" tab on the left and navigate to the /usr/lib/jvm
Once there you should see two types of java. If you see java open jdk
you need to delete it, along with it's associated bin folder. Close the
root file explorer window
1c - Edit .bashrc
Next navigate to your home folder and open up the .bashrc file. This is
a hidden file so you will have to press Ctrl + H to see it. Add the
following lines to the top section, and change accordingly to your path
Example:
Code:
#JavaDev PATH
export JAVA_HOME=/usr/lib/jvm/java-6-sun-1.6.0.24
export PATH=$PATH:$JAVA_HOME/bin
Save the file and exit, then changes will not take effect until reboot
Verify java version again
Code:
$ java -version
Step 2 - Install git
http://help.github.com/linux-set-up-git/
or
Code:
$ sudo apt-get install git
Step 3 - Prepare the Build Environment
NOTE: You only need to do these steps the first time you build.
If you previously prepared your build environment, skip to Copy
proprietary files.
3a - Install the ADB
Install the Android SDK. http://wiki.cyanogenmod.com/index.php?
title=Howto:_Install_the_Android_SDK
3b - Install the Build Packages
Install using the package manager of your choice:
For 32-bit & 64-bit systems:
Code:
$ [COLOR="red"]sudo apt-get install[/COLOR] git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
For 64-bit only systems:
Code:
$ [COLOR="red"]sudo apt-get install[/COLOR] g++-multilib lib32z1-dev lib32ncurses5-dev [COLOR="Red"]lib32readline-gplv2-dev[/COLOR] [COLOR="Red"]gcc-multilib g++-multilib[/COLOR]
3c - Create the Directories
You will need to set up some directories in your build environment.
To create them:
Code:
$ mkdir -p ~/bin
$ mkdir -p ~/android/system
3d - Install the Repository
Enter the following to download make executable the "repo" binary:
Code:
$ [COLOR="red"]curl https://raw.github.com/android/tools_repo/master/repo > ~/bin/repo[/COLOR]
$ chmod a+x ~/bin/repo
NOTE: You may need to reboot for these changes to take effect.
Now enter the following to initialize the repository:
Code:
$ cd ~/android/system/
$ [COLOR="red"]repo init -u git://github.com/CyanogenMod/android.git -b gingerbread --repo-url=git://github.com/android/tools_repo.git[/COLOR]
$ repo sync
3e - Copy proprietary files
NOTE: This only needs done the first time you build. If you have
already done these steps, you may skip to Download RomManager.
You will need to have a speedy with a working copy of CyanogenMod
install and ADB working on the computer. This script will copy the
proprietary files from the device.
Connect the device to the computer and ensure that ADB is working
properly.
Code:
$ cd ~/android/system/device/htc/speedy/
./extract-files.sh
3f - Download RomManager
NOTE: This only needs to be done when an update to
RomManager is released. If you are-up-to date, you may skip to Building
CyanogenMod. Download RomManager which is needed by the build:
Code:
$ ~/android/system/vendor/cyanogen/get-rommanager
3g - Building CyanogenMod
Check for updates
First, check for updates in the source:
Code:
$ cd ~/android/system/
$ repo sync
$ cp build/core/root.mk -f Makefile
3h - Set up your Compiler
This is optional but helpful for kernel compiling
There are a lot of things that need to be added to the .bashrc to let your
pc know about which type of compiler you want to use. The best way is
to use the one provided in the CM7 work tree.
Code:
[COLOR="red"]#Android[/COLOR]
export ARCH=arm
export CCOMPILE=$CROSS_COMPILE
export PATH=$PATH:~/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
3i - Configure Build & Compile
Now, the environment must be configured to build and the ROM
compiled, from code, for the Speedy.
Code:
$ . build/envsetup.sh && brunch speedy
3j - Install
Copy your .zip file from
~/android/system/out/target/product/speedy/update.cm-XXXXX-
signed.zip to the root of the SD card.
Optional: Download Google Apps for CyanogenMod 7 and place it on the
root of the SD card.
Flash both of these .zip files from recovery.

Nice write up. When I have time I'll see if it works for me.

riggsandroid said:
Nice write up. When I have time I'll see if it works for me.
Click to expand...
Click to collapse
Yeah this was a quick write up. The main thing is you have to reboot every time you edit your .bashrc, or copy and paste it into terminal
Also I'll be doing a how to compile kernel, hopefully soon

Or just when you change your bashrc, just source the bashrc script
. ~/.bashrc
Sent from my PG06100 using XDA App

Has anyone tried a swap file yet? I just set mine up and it seems to speed compiling up quite a bit. I went off of this guide but I made mine 1.6GB in size
https://help.ubuntu.com/community/SwapFaq

You are a savior... I have been trying to get this running on my natty tower, but have had little success... This write up will be very handy... Thank you for the excellent write up and the time for doing it...
Sent from my PG06100 using Tapatalk

New java update?
I noticed that my java was not all the way up to date. I went into recovery and selected fix broken packages and then it updated my java to this version:
~$ java -version
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
On a side note it also updated my python and some other things. Make sure you have internet that is not wifi

guide updated for korg workaround. Changes are labeled in red

Repo not found?
Followed Directions to the T, Currently Hung up on
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread --repo-url=git://github.com/android/tools_repo.git
Tells me repo command not Found
EDIT: I'm sorry hows about more info?, Ubuntu 11.10 64bit need anymore just ask

Nice guide. Can I do this on Fedora?

riggsandroid said:
Nice write up. When I have time I'll see if it works for me.
Click to expand...
Click to collapse
...6 months later.
Ya find any of that time yet, Riggs?

JaceAlvejetti said:
Followed Directions to the T, Currently Hung up on
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread --repo-url=git://github.com/android/tools_repo.git
Tells me repo command not Found
EDIT: I'm sorry hows about more info?, Ubuntu 11.10 64bit need anymore just ask
Click to expand...
Click to collapse
Did you set up ~/bin/repo yet? Never had that issue before. Probably need to reboot once for the repo to take effect. Just like it says on the OP.
Sent from my PG06100 using xda premium

VICODAN said:
Nice guide. Can I do this on Fedora?
Click to expand...
Click to collapse
I wish I knew more about fedora, but I just don't, sorry.
Sent from my PG06100 using xda premium

sparksco said:
I wish I knew more about fedora, but I just don't, sorry.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It works fine on fedora just change the apt-get to yum

Great guide, thanks sparksco
Sent from my PG06100 using Tapatalk

VICODAN said:
It works fine on fedora just change the apt-get to yum
Click to expand...
Click to collapse
Sweet thanks for pointing that out. I've been meaning to update this guide when I have time later when I get home I'll update more info on it. I've also been wanting to try fedora for quite some time.
Sent from my PG06100 using xda premium

jesusice said:
...6 months later.
Ya find any of that time yet, Riggs?
Click to expand...
Click to collapse
I was wondering about this too
Sent from my PG06100 using xda premium

OP updated
Updated OP to include Vicodan's instructions and this is to build kanged editions of Cyanogenmod. I will also start posting my own versions of the kanged builds here when I get a build that will include my own extra mods.

Awesome guide. I'll be trying this soon. Tonight, if the wife and kids cooperate. Which usually translates to 'a week from now' lol...
Sent from my SPH-D700 using Tapatalk

NawtyB78 said:
Awesome guide. I'll be trying this soon. Tonight, if the wife and kids cooperate. Which usually translates to 'a week from now' lol...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Its all good. me and sparksco use regular Ubuntu and it runs great

[TOOL] [14th Dec] | AIOlog - All in One Android Logger v0.5

AIOlog - All in One Android Logger​
{
"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"
}
Features:
Display and output Logcat
Last_kmsg
Dmesg
Kmsg
Kernel Version
Click to expand...
Click to collapse
Latest Version:
1. AIOlog for Windows: http://aiolog.googlecode.com/files/aiolog_win_v0.5.zip
2. AIOlog for Linux 32bit: http://aiolog.googlecode.com/files/aiolog_linux_32_v0.5.tar
3. AIOlog for Linux 64bit: http://aiolog.googlecode.com/files/aiolog_linux_64_v0.5.tar
4. AIOlog for Mac 32bit: http://aiolog.googlecode.com/files/aiolog_mac_32_v0.5.tar
5. AIOlog for Mac 64bit: http://aiolog.googlecode.com/files/aiolog_mac_64_v0.5.tar
Click to expand...
Click to collapse
NOTE: If you have this error "Cannot execute binary files" while using the AIOlog for linux, please download the 32bit version.
If you've downloaded the AIOlog v0.3 generic, please use the following file:
Either the aiolog_32bit or aiolog_generic_32bit
If this is your first time doing a log, you may need this file(Windows only):
http://code.google.com/p/aiolog/downloads/detail?name=aiolog_adb_fastboot_win_v0.1.zip
New features:
Added log push to phone and phone directory creation(log will be available at the computer, and the .aiolog, aiolog and root folder of your phone)
Added log archiving(unix)
Added log cid version
Added ADB files for Windows
Fixed a bug to auto detect device id when there is only one device
Click to expand...
Click to collapse
Full Changelog: https://github.com/wcypierre/AIOlog/commits/master​
Hi, I'm now in the look for users who can provide me with some data(non-private and non-confidential ones) in order to improve AIOlog as a big amount of data is needed for AIOlog in order to success.
If you're interested, please pm me and state your device name or you can email me via [email protected]
Basic Howto:
1. At your phone, go to Settings -> Developer Options
2. Tick the "Android Debugging"
3. Connect your phone to your computer(desktop/laptop)
Windows:
1. Navigate to the location where the aiolog is located
2. Extract it and place it to a folder
3. Open aiolog.exe by clicking at it
4. The menu will appear
5. Just enter the number(1,2,3 ...) of the function that you wanted to do
Linux:
NOTE: For AIOlog version 0.4 onwards, the binary file is called either aiolog_32bit or aiolog_64bit so please change it accordingly (The steps for the filename is used in Step #3)
1. Open your terminal
2. Navigate to where aiolog is located. Example, "cd ~/Downloads/" (Assuming that the file is saved at Downloads folder)
3. Type "./aiolog" and press enter
4. The menu will appear
5. Just enter the number(1,2,3 ...) of the function that you wanted to do
Click to expand...
Click to collapse
Advanced Howto:
1. At your phone, go to Settings -> Developer Options
2. Tick the "Android Debugging"
3. Connect your phone to your computer(desktop/laptop)
Windows:
1. Open the cmd
2. Navigate to the folder where aiolog is located
3. Type "aiolog -h" and press enter
4. Search for the functions that you wanted to do and type its command(refer to the examples below)
Examples:
1. To log all logs, type "aiolog.exe -a"
2. To get the logcat, type "aiolog.exe -l"
3. To get the last_kmsg, type "aiolog.exe -lk"
4. To specify a device that is to be used(use it when you have a lot of devices connected) and to get a dmesg, "aiolog.exe -id SH<yourdeviceid> -d"
Linux:
1. Open your terminal
2. Navigate to where aiolog is located. Example, "cd ~/Downloads/" (Assuming that the file is saved at Downloads folder)
3. Type "./aiolog -h" and press enter
4. Search for the functions that you wanted to do and type its command(refer to the examples below).
Examples:
1. To log all logs, type "aiolog.exe -a"
2. To get the logcat, type "./aiolog -l"
3. To get the last_kmsg, type "./aiolog -lk"
4. To specify a device that is to be used(use it when you have a lot of devices connected) and to get a dmesg, "./aiolog -id SH<yourdeviceid> -d"
Click to expand...
Click to collapse
Compatibility:
1. Full support on Windows
2. Partial support on Linux
3. Partial support on Mac(Version 0.5 onwards)
Issues:
1. May not work on mac yet(but it should be).
2. AIOlog will not work if the adb is not started for a 30 seconds to 1 minute in advance
Found a bug?
1. Go to here: http://code.google.com/p/aiolog/issues/list
2. Click New issue
3. Fill in the details
4. Report
5. Wait for it to be resolved :good:
Changelog:
Version 0.4
1. Added Auto Device Id detection
2. Logging support when there are more than 2 devices connected
3. Added logcat clear and dmesg clear
Version 0.3
1. Added logcat radio(to debug for radio issues)
2. Added log essential(logcat, dmesg, kmsg and last_kmsg)
3. Disable reprompt of device id after it has been entered
4. Misc Fixes
Version 0.2
1. Logcat, kmsg continuous(the normal logcat, kmsg way instead of log, stop and save method) added
2. Added additional checking on device id
3. Removed debug code
Version 0.1
1. Core functions(logcat, last_kmsg, dmesg, last_kmsg) implemented
2. Outputs the log to the current directory of AIOlog
3. kernel version output is implemented
Click to expand...
Click to collapse
To do list:
1. To archive the logs into an archive(zip, rar, tar)
2. To include mac support
3. To include log essential (Done )
4. To log other details
5. Fix any existing bugs

Building from Source
Prerequisite:
- Command Line Git(be it from any OS)
Instructions:
To clone the AIOlog(one time process):
git clone git://github.com/wcypierre/AIOlog.git
To update the existing AIOlog:
git remote update
git rebase origin/master
To compile AIOlog:
g++ main.cpp log.cpp -o aiolog.exe (for windows) / g++ main.cpp log.cpp -o aiolog (for mac/linux)

Miscellaneous:
If you want to log the logs using other methods, please refer to this thread by nitubhaskar:
http://forum.xda-developers.com/showthread.php?p=33716489

Nice. Will try it

Warren87 said:
Nice. Will try it
Click to expand...
Click to collapse
Please do try it and give any suggestions and how to improve the program

Nice tool, wcypierre!
Very helpfull for noob users.

icke said:
Nice tool, wcypierre!
Very helpfull for noob users.
Click to expand...
Click to collapse
Thanks . Please do provide some feedbacks after you've use it eh

Build from source instructions is added

For those who build from source, v0.3a is out(but the version number shows it as v0.2)

Version 0.2 is out!
1. AIOlog for Windows: http://aiolog.googlecode.com/files/aiolog_win_v0.2.zip
2. AIOlog for Linux: http://aiolog.googlecode.com/files/aiolog_linux_v0.2.tar
3. AIOlog for Mac: Coming soon.......
New features:
Version 0.2
1. Logcat, kmsg continuous(the normal logcat, kmsg way instead of log, stop and save method) added
2. Added additional checking on device id
3. Removed debug code

For those who build from source, please do a remote update as new commits has been committed to github

Ok, so I haven't played with it yet but I thought that I would provide some information to any other Ubuntu users who try to use the tool.
The download and compile of the executable occurs without any problems. If you have compiled nay other apps form source this is really easy.
In order to get the app to run you need to have adb installed and running.
I am not going to get into all the details for that. Google it.
But what you won't find in the instructions for when installing adb is the following:
a) You need to run adb under sudo, otherwise you get an error which says something along the lines of "no permissions", or "no permissions for this device" when you run aiolog.
b) If you have added adb to your path (Google it for instructions) then you run sudo with the -i argument. That is enter "sudo -i ad start-server"
Good luck

Nice gonna try soon

GaryWS said:
Ok, so I haven't played with it yet but I thought that I would provide some information to any other Ubuntu users who try to use the tool.
The download and compile of the executable occurs without any problems. If you have compiled nay other apps form source this is really easy.
In order to get the app to run you need to have adb installed and running.
I am not going to get into all the details for that. Google it.
But what you won't find in the instructions for when installing adb is the following:
a) You need to run adb under sudo, otherwise you get an error which says something along the lines of "no permissions", or "no permissions for this device" when you run aiolog.
b) If you have added adb to your path (Google it for instructions) then you run sudo with the -i argument. That is enter "sudo -i ad start-server"
Good luck
Click to expand...
Click to collapse
Thanks for the feedback . Was waiting for things like these(community feedback, so I can know new issues and write up on it) :good: .Provided that you know how to use git, usually compiling from source would not be a problem(especially when the project is only this small )
For the permission problem, I used to had that as well but I don't quite remember how I solved that. It can either be a permission problem at the adb file or the aiolog. anyway, just chmod the file to 755 with superuser permission(sudo) and you should be able to run it
Sample run of the command:
sudo chmod 755 aiolog
btw, would you mind to add a "b" after the "ad", because it should be "adb" instead of "ad"

Version 0.3 is out
New Features
Version 0.3
1. Added logcat radio(to debug for radio issues)
2. Added log essential(logcat, dmesg, kmsg and last_kmsg)
3. Disable reprompt of device id after it has been entered
4. Misc Fixes

Hey, i have added your tool to my all in one guide mate as we discussed.. and gave thread link to here..
Also congrats on hitting the portal news!! You got covered by POORCOLLEGEGUY.. he is awesome at covering these,..

nitubhaskar said:
Hey, i have added your tool to my all in one guide mate as we discussed.. and gave thread link to here..
Also congrats on hitting the portal news!! You got covered by POORCOLLEGEGUY.. he is awesome at covering these,..
Click to expand...
Click to collapse
hey, thanks for doing that :good: . I'll try and see what I can do for your thread
yeah, just noticed that, you're welcome

Hi, there!
Just downloaded aiolog_linux_v0.3.tar, extract and tried to execute, but had no succes ((
Can anybody help me?
Thanks!
Code:
[email protected]:~/Downloads/aiolog_v0.3$ uname -a
Linux vovs-pc 3.2.0-32-generic-pae #51-Ubuntu SMP Wed Sep 26 21:54:23 UTC 2012 i686 athlon i386 GNU/Linux
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file

v0vs said:
Hi, there!
Just downloaded aiolog_linux_v0.3.tar, extract and tried to execute, but had no succes ((
Can anybody help me?
Thanks!
Code:
[email protected]:~/Downloads/aiolog_v0.3$ uname -a
Linux vovs-pc 3.2.0-32-generic-pae #51-Ubuntu SMP Wed Sep 26 21:54:23 UTC 2012 i686 athlon i386 GNU/Linux
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file
Click to expand...
Click to collapse
Try to change the permissions and run it again
do the following:
sudo chmod 755 aiolog
Click to expand...
Click to collapse

same result
Code:
[email protected]:~/Downloads/aiolog_v0.3$ sudo chmod 755 aiolog
[sudo] password for vovs:
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file
[email protected]:~/Downloads/aiolog_v0.3$ ls -l
total 64
-rwxr-xr-x 1 vovs vovs 27133 Nov 4 14:54 aiolog
-rw-rw-r-- 1 vovs vovs 35147 Oct 16 16:47 COPYING
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file

[Guide] How to compile and install CM10 for Samsung i9300

{
"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"
}
LINKS
This guide is a Device-specific update of one of the following guides:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Compile_CyanogenMod_(Linux)
http://forum.xda-developers.com/showthread.php?t=1505006
http://forum.xda-developers.com/showthread.php?t=1533711
http://forum.xda-developers.com/showthread.php?t=1779426
DISCLAIMER
Although it's very good described I'm not responsible for any damage to you- or you phone
THANKS
PMOS69
stbenz
rycus86
kasper_h
gmhafiz
REQUIREMENTS:
Linux - Ubuntu/Linux Mint system - 64bit
i9300 with cm10 already installed (grab it from get.cm)
30 GB storage on HD/SSD (SSD is preferable in building speed)
__________________
1 - Install Debian Packages
1.1 - In terminal:
Code:
sudo apt-get install git-core gnupg flex bison python rar original-awk gawk p7zip-full gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool
sudo apt-get install libc6-dev x11proto-core-dev libx11-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils
sudo apt-get install g++-multilib lib32z1-dev ia32-libs lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib g++-multilib xsltproc
2 - Install JAVA
2.1 - Install Java JDK for Linux 64-bit (1.6)
Code:
sudo apt-get install openjdk-6-jdk
3 - Install Android SDK
3.1 - Setup directories:
Code:
cd ~
mkdir android
cd android
mkdir sdk
3.2 - Download Android SDK http://developer.android.com/sdk/index.html
3.3 - Extract SDK contents to ~/android/sdk
3.4 - Add Android SDK Path:
Code:
sudo gedit ~/.bashrc
Enter the Following:
Click to expand...
Click to collapse
Code:
#Android PATH
export PATH=$PATH:~/android/sdk
export PATH=$PATH:~/android/sdk/platform-tools
export PATH=$PATH:~/android/sdk/tools
3.5 - Add Extra Path For Device:
Code:
sudo gedit /etc/udev/rules.d/99-android.rules
Enter this:
Click to expand...
Click to collapse
Code:
#Samsung
SUBSYSTEM==usb, SYSFS{idVendor}==04e8, MODE=0666
SUBSYSTEM=="usb", ATTRS{idVendor}=="####:####", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Save/close file and run:
Click to expand...
Click to collapse
Code:
sudo chmod +x /etc/udev/rules.d/99-android.rules
3.6 - Close and open new terminal.
3.7 - Install Android SDK Tools
Code:
android
Check Android SDK Tools and Android SDK platform-tools and Install them
Click to expand...
Click to collapse
4 - Install Repository
4.1 - Download Repo:
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
4.2 - Add Repo Path:
Code:
sudo gedit ~/.bashrc
Enter the following:
Click to expand...
Click to collapse
Code:
export PATH=$PATH:~/bin
4.3 - Close and open new terminal.
4.4 - Initialize Repository & Sync:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
repo sync -j16
NOTE: If you have trouble syncing due to connection issues, try repo sync -j1. It's slower but some ISPs have issues with -j16. Want to make sure you didn't get any connection errors and have the complete repository? Just run the repo sync command again. It can't give you ANY errors.
Click to expand...
Click to collapse
4.5 - Get Device Specific Repos:
Code:
. build/envsetup.sh && breakfast i9300
4.6 - Extract files from phone:
Connect your phone (with CM10 installed) to your pc and in terminal type:
Click to expand...
Click to collapse
Code:
adb root
cd ~/android/system/device/samsung/i9300
./proprietary-files.sh
4.7 - Download Extra Files:
Code:
~/android/system/vendor/cm/get-prebuilts
4.8 - Add Toolchain PATH:
Code:
sudo gedit ~/.bashrc
Enter the following:
Click to expand...
Click to collapse
Code:
#Android Toolchain PATH
export ARCH=arm
export CCOMPILE=$CROSS_COMPILE
export CROSS_COMPILE=arm-eabi-
export PATH=$PATH:/home/YOUR-USERNAME/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
4.9 - Close and open new terminal
5 - Building Android
Code:
cd ~/android/system
. build/envsetup.sh && brunch i9300
6 - Install on Phone
6.1 - Copy your .zip file from ~/android/system/out/target/product/i9300/cm-10-XXXXXXXXX-UNOFFICIAL-i9300.zip to the root of the SD card.
6.2 - Optional: Download Google Apps for Jelly Bean from http://goo.im/gapps
6.3 - Flash both of these .zip files from recovery.
7 - Update
Code:
cd ~/android/system
repo sync -j16
make installclean
find ./out/ -name 'build.prop' | xargs rm
find ./out/ -name 'cm_i9300-target_files-eng.*.zip' | xargs rm
. build/envsetup.sh && brunch i9300
8 - CyanogenMod 10.1
8.1 - Backup and delete following folders:
Code:
~/android/system/vendor/samsung/i9300
~/android/system/vendor/samsung/smdk4412-common
~/android/system/device/samsung/i9300
8.2 - Initialize Repository & Sync:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
repo sync
8.3 - Edit local.manifest.xml
Code:
gedit ~/android/system/.repo/local_manifest.xml
Add this:
Click to expand...
Click to collapse
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" />
</manifest>
8.4 - Get Device Specific Repos:
Code:
. build/envsetup.sh && breakfast i9300
8.5 - Extract files from phone:
Connect your phone (with CM10.1 installed) to your pc and in terminal type:
Click to expand...
Click to collapse
Code:
adb root
cd ~/android/system/device/samsung/i9300
./proprietary-files.sh
or
Click to expand...
Click to collapse
8.5 - Download the following folders/files (and put in vendor/samsung):
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-10.1/i9300
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-10.1/smdk4412-common
8.6 - Building Android:
Code:
cd ~/android/system
. build/envsetup.sh && brunch i9300
9 - Armageddon
Only in emergency and nothing helps to get it back working
Click to expand...
Click to collapse
Code:
make clobber

Nice guide! Building now, hope I set up everything right and didn't forget anything. Couple notes/questions though.
1. You list Debian based system as a requirement, but I think you should make it more clear and change it to Ubuntu based. When installing the packages under Debian 6.0.6 very many didn't have installation candidate under that particular name. With Ubuntu 12.04 on the other hand everything installed smoothly.
2. Am I right in assuming that the step where the proprietary files are fetched from the phone is not needed during the update procedure?
Very happy about this. Had been thinking about learning to build myself but always crumbled in the device specific section and wasn't motivated enough to go on. This guide helped a lot! :good: Maybe now it's time to learn to apply some cherry picks to the rom for myself ^^

Dont need to be running CM10 on phone as long as you have root on stock. It is pulling certain files from the system.
You dont need to add the toolchain to your path. That is handled by the build script.
Dont need SDK either. Part of repo.
Thanks for the guide.
Sent from my GT-I9300 using xda premium

b-eock said:
Dont need to be running CM10 on phone as long as you have root on stock. It is pulling certain files from the system.
You dont need to add the toolchain to your path. That is handled by the build script.
Dont need SDK either. Part of repo.
Thanks for the guide.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ah really? Thanks! Tried to remember what steps I needed to take to build on my
SGSi9000 before, so I haven't done a clean build on a clean system. But if it's not
needed I will take it out of this guide :highfive:.
labbe- said:
Nice guide! Building now, hope I set up everything right and didn't forget anything. Couple notes/questions though.
1. You list Debian based system as a requirement, but I think you should make it more clear and change it to Ubuntu based. When installing the packages under Debian 6.0.6 very many didn't have installation candidate under that particular name. With Ubuntu 12.04 on the other hand everything installed smoothly.
2. Am I right in assuming that the step where the proprietary files are fetched from the phone is not needed during the update procedure?
Very happy about this. Had been thinking about learning to build myself but always crumbled in the device specific section and wasn't motivated enough to go on. This guide helped a lot! :good: Maybe now it's time to learn to apply some cherry picks to the rom for myself ^^
Click to expand...
Click to collapse
1. Sure, my fault. Thought Debian was a more handy and common name for
distro's mentioned (Ubuntu/Linux Mint etc), but I'll change it
2. Indeed, fetching the files from phone has to be done once, after that it's
not necessary anymore.
3. Good luck mate! Let me know if it worked

RATBORG said:
Ah really? Thanks! Tried to remember what steps I needed to take to build on my
SGSi9000 before, so I haven't done a clean build on a clean system. But if it's not
needed I will take it out of this guide :highfive:.
1. Sure, my fault. Thought Debian was a more handy and common name for
distro's mentioned (Ubuntu/Linux Mint etc), but I'll change it
2. Indeed, fetching the files from phone has to be done once, after that it's
not necessary anymore.
3. Good luck mate! Let me know if it worked
Click to expand...
Click to collapse
Left it to build overnight (tried first with VirtualBox on my laptop but it was slow as hell) but it failed. Didn't catch the error message because I was late for work. Going to install dualboot Ubuntu on my desktop machine tonight and try again and hope it goes better.

labbe- said:
Left it to build overnight (tried first with VirtualBox on my laptop but it was slow as hell) but it failed. Didn't catch the error message because I was late for work. Going to install dualboot Ubuntu on my desktop machine tonight and try again and hope it goes better.
Click to expand...
Click to collapse
That's better, I have a Acer laptop with a new SSD, made it single booted
with only Linux Mint x64. Note: you really need x64. VMware can be used
but I always had issue's with it. Maybe you can even try to use Archlinux
(check Codeworkx thread about it).

Nice guide. Been a long time since I seen one.

RATBORG said:
That's better, I have a Acer laptop with a new SSD, made it single booted
with only Linux Mint x64. Note: you really need x64. VMware can be used
but I always had issue's with it. Maybe you can even try to use Archlinux
(check Codeworkx thread about it).
Click to expand...
Click to collapse
Yeah i have 64bit no prob. Is there already a build of the BBQLinux available? I've tried searching but havent found it anywhere.
Unfortunately I don't have a SSD yet, planning to sell my MacBook Pro and buying an Ultrabook instead so with that building would be a little faster.

temasek said:
Nice guide. Been a long time since I seen one.
Click to expand...
Click to collapse
Thanks sir! You too for your efforts here
labbe- said:
Yeah i have 64bit no prob. Is there already a build of the BBQLinux available? I've tried searching but havent found it anywhere.
Unfortunately I don't have a SSD yet, planning to sell my MacBook Pro and buying an Ultrabook instead so with that building would be a little faster.
Click to expand...
Click to collapse
Yep, here: http://download.bbqlinux.org/
Tutorial: http://rootzwiki.com/topic/9287-how-to-setup-android-build-environment-on-arch-linux-64bit/
Ultrabooks are nice :highfive: aswell is the MacBook. But pretty pitty to
abuse a nice MacBook only for building haha

RATBORG said:
Ultrabooks are nice :highfive: aswell is the MacBook. But pretty pitty to
abuse a nice MacBook only for building haha
Click to expand...
Click to collapse
The MacBook is actually my main computer, the desktop tower is only for gaming. I'm planning the Ultrabook because I'm switching job soon which requires more traveling so the 17" MacBook is getting a bit too large.
I tried to build again and now it built succesfully in 30 minutes in virtualbox, so i guess there is no need for dualboot after all ^^ but going to install the BBQLinux anyway to test it.

Thanks for the guide!
Works as it should, but it overshoots a little. It is not necessary to install the complete android sdk. But it doesn't hurt, either

just noticed that the cm buildsystem reported that openjdk-6-jdk is an unsupported java version and it said in cm page that sun-java6-jdk is recommended. well, ubuntu has removed sun-java6-jdk from it's repository due to licencing issues with oracle, but i managed to get it installed with a guide i found while googling..
Code:
mkdir ~/src
cd ~/src
git clone https://github.com/flexiondotorg/oab-java6.git
cd ~/src/oab-java6
sudo ./oab-java.sh
sudo apt-get install sun-java6-plugin sun-java6-jre sun-java6-bin sun-java6-jdk
after that no messages anymore. thought i'd share :good:

Yeah thanks!
On the other hand it's just fine to use OpenJDK.
Sent from my GT-I9300 using xda premium

RATBORG said:
Yeah thanks!
On the other hand it's just fine to use OpenJDK.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
yeah i know it did it just fine, just an observation=)

After a time of extreme busy work schedule I finally found the time to continue my efforts in regards of building myself.
I was wondering, how do I include external sources to my builds? For example, I want to use temasek's kernel so that would save me the manual flash after every update. I read a little from CM wiki but it's too general for me :/
Also, the commands 'find ./out/ -name 'build.prop' | xargs rm' and 'find ./out/ -name 'cm_i9300-target_files-eng.*.zip' | xargs rm' does not seem to work so I've just skipped them and installed after make installclean, is that ok?

labbe- said:
After a time of extreme busy work schedule I finally found the time to continue my efforts in regards of building myself.
I was wondering, how do I include external sources to my builds? For example, I want to use temasek's kernel so that would save me the manual flash after every update. I read a little from CM wiki but it's too general for me :/
Also, the commands 'find ./out/ -name 'build.prop' | xargs rm' and 'find ./out/ -name 'cm_i9300-target_files-eng.*.zip' | xargs rm' does not seem to work so I've just skipped them and installed after make installclean, is that ok?
Click to expand...
Click to collapse
It is more troublesome to do that than flashing a separate kernel.
There will be commit conflicts and unless u can resolve that then its ok.
Read about git commands
Eg git pull ...git push ...git fetch..git commit ..git remote add xxxyyy github . etc

fixed

How about compiling cm10.1?

krille_java said:
How about compiling cm10.1?
Click to expand...
Click to collapse
repo init -b cm-10.1
repo sync

Aha thank you!

Guide for Compiling a kernel for the Tubuntu app by x3maniac and TF101

Guide for Compiling a kernel for use with the Tubuntu application by x3maniac and TF101.
These insturctions work with 64bit Linux laptop/PC's, version 4.5.4 for the armhf toolchain, and 2.6.36 kernel version. The toolchain and kernel from the github below is the direct source x3maniac makes the kernels we are currently using. Please understand a few things, if you add modules to this build you will need to add them to your Linux image you are using. I'll provide specifics as I work through the learning process as well. If you change compilers or upgrade the software components outside of this guide it may produce errors or problems.
If you are looking for making a version 3 kernel, hardware acceleration with nvidia and things like that you will either have to ask x3maniac or do your own research as this guide does NOT tell you how to do this.
******My directories reference my own username on my laptop, please substitute "thomas" with your username OR your /home directory, or whichever directories you wish to use. I used full paths on purpose for my own learning and to be specific for newcomers to Linux who wish to learn to compile.******
All credit goes to the time and consideration x3maniac took to assist me with doing this!
OP for Tubutnu by x3maniac
1. Open Terminal. Everything will be executed from Terminal.
2. Now type: sudo apt-get abootimg
3. Now type: mkdir /home/thomas/kernelbuild
3a. Now type: cd /home/thomas/kernelbuild
4. Now type: git clone https://github.com/novaspirit/tf101-linux-2.6.36
5. Now type: git clone https://github.com/novaspirit/Ubuntu_initrd-3.x.git
6. Now type: git clone https://github.com/novaspirit/config.git
6a. The config.git has a file called /config/boot.cfg, you could modify the last line called the command line and have it boot from alternate locations, the default is fine and set to /dev/mmcblk0p8. So let's not touch it, you can use nano to edit this file.
7. Now type: git clone https://github.com/novaspirit/android-toolchain-4.5.4.git
8. Now type: cd /home/thomas/kernelbuild/tf101-linux-2.6.36
9. Copy this into Terminal and hit enter: 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
10. Copy this into Terminal and hit enter: sudo apt-get install libgtk2.0-dev libglib2.0-dev libglade2-dev (this allows you to make a GUI of the config file)
11. Now type: make help (you should see a list of build targets. You are looking to see if you have tf101_gnulinux_defconf.)
12. Now type: export ARCH=arm
13. Now type: export CROSS_COMPILE=/home/thomas/kernelbuild/android-toolchain-4.5.4/bin/arm-eabi- (understand the arm-eabi- simply ends with the hypen to include sub components, it's not a typo)
14. Now type: make tf101_gnulinux_defconfig
15. Now type: make gconfig (the GUI pops up and this is where you can select options). Click on split, the options will be on the left. This is where you can select what you wish to add. For example, web cam and GPS functions. HOWEVER, it does not mean this will work nor is it all perfectly set up. There may be some additional research by YOU the reader to find out what will or won't work with this kernel. (NOTE: you must run make gconfig even if you don't change anything otherwise an error will occur when you run make -j2 modules command).
16. If you have made changes it will ask you to save. Go ahead and save it.
17. Now type: make -j2 zImage (j2 represents jobs that can be run concurrently, determined by the kernel build. This option only works if you have 2 cores and also you can use -j4 if you have a 4 core system and so on.)
18. Now type: make -j2 modules (If the github provided by x3maniac doesn't have a module you need, this is where YOU the reader must research what you need to add and place it in the appropriate location).
19. Now type: make modules_install INSTALL_MOD_PATH=/home/thomas/kernelbuild/Ubuntu_initrd-3.x/
20. Now type: cd /home/thomas/kernelbuild/Ubuntu_initrd-3.x/
21. Now type: find .|cpio -H newc -o | gzip -9 > /home/thomas/kernelbuild/initramfs.img
21b. The output should say something similar to 1111 blocks or 14582 blocks, doesn't matter the number. The number and blocks means it has been made successfully.
22. cd /home/thomas/kernelbuild
23. Now type: abootimg --create kernel.img -f /home/thomas/kernelbuild/config/boot.cfg -r initramfs.img -k /home/thomas/kernelbuild/tf101-linux-2.6.36/arch/arm/boot/zImage
23b. abootimg is very strict and will produce an error here if anything is wrong. You are looking for the output of some files created and you should see a kernel.img file in your directory with an ls command.
24. If you are going to flash the kernel using the Tubuntu application, rename kernel.img to linux.img and flash appropriately from the app.
25. If you are going to create another kernel you need to clean it up before repeating steps 12-24. So proceed to step 26.
26. Now type: cd /home/thomas/kernelbuild/tf101-linux-2.6.36
27. Now type: make clean
28. Now type: make mrproper
29. Delete kernel.img from /home/thomas/kernelbuild/
30. If you aren't modifying additional modules and parameters you can save the created initramfs.img file. Otherwise delete it and run through the steps, doesn't take long to do anyways.
31. Profit.

My guide is complete now. Please read everything thoroughly before diving in. It's not as difficult as it looks. I will make kernels and modify the guide to weed out any errors, typos, or wrong steps. Hope everyone enjoys! I do this as much for myself as the community.

Made some edits for consistency and clarity. Please remember to check the github to determine if X3, our dev, has made any changes possibly requiring you to git clone again. If changes have been made, it is my experience that the easiest way to get the newest is to just delete the directories and git clone again. There is probably a way to do this and only grab the changes but I really haven't looked into that.

Thanks for this, going to see if I can add some stability in there since mine is barely usable.
You should replace /home/thomas/ with $HOME/ instead, that way it won't error out for people that don't use mkdir -p or aren't using a thomas username

Lethe6 said:
Thanks for this, going to see if I can add some stability in there since mine is barely usable.
You should replace /home/thomas/ with $HOME/ instead, that way it won't error out for people that don't use mkdir -p or aren't using a thomas username
Click to expand...
Click to collapse
I thought about that but I specified it in the beginning of the post. The purpose was to not make assumptions on what people using Linux did or did not know. For example I didn't realize ~/ represented the home directory till x3 pointed it out to me.
Since the post had such little traction I left it as is to help me out as well.
*****lol, I didn't specify the directories and why they were named that way. Must have been my other guide. I'll fix it up soon.

I added this comment below into the OP to remove confusion on the directories I used.
******My directories reference my own username on my laptop, please substitute "thomas" with your username OR your /home directory, or whichever directories you wish to use. I used full paths on purpose for my own learning and to be specific for newcomers to Linux who wish to learn to compile.******

[GUIDE] How to build CM10.2 for the HTC One with OS X 10.8.X

This is a guide to build CyanogenMOD 10.2 (Android 4.3) for the HTC One. This guide is for OS X Mountain Lion (10.8.X).
[size=+1]Pre Requirements:[/size]
1) go to App Store on your OS X and Download Xcode 4. Once that is installed, open Xcode and go to preferences. There you find a tab “DOWNLOADS”, open it and there you can find “Command line tools” and next to it click INSTALL. It will take a few minutes to download and install
2) Make sure you have the android-sdk downloaded and setup adb and fastboot, so they work. It is recommended to place the android-sdk to /usr/local/
[size=+1]Initializing the build environment[/size]
First we need to set up our OS X to be able to build Android. This needs some extra things compared to for example, building in Linux, but the main stuff is pretty much the same. So let’s get started then, shall we?
Open up Terminal and type
Code:
java
If you don’t have java installed you will get a prompt to install it.
Next we will install homebrew (you can also use macports if you like)
Code:
ruby <(curl -fsSk https://raw.github.com/mxcl/homebrew/go)
Now make sure android-sdk and homebrew are in $PATH
Code:
touch ~/.bash_profile && echo "PATH=/usr/local/bin:/usr/local/sbin:$PATH:/usr/local/android-sdk/tools:/usr/local/android-sdk/platform-tools" >> ~/.bash_profile
I also recommend to add this edit to the .bash_profile file:
Code:
nano –w ~/.bash_profile
Code:
export BUILD_MAC_SDK_EXPERIMENTAL=1
Now run this and see if you need to update anything.
Code:
brew doctor
If you do (and you probably will once a day) type:
Code:
brew update
Now we need to get our dev packages
Code:
brew install git coreutils findutils gnu-sed gnupg pngcrush repo
Once that is done, run
Code:
brew outdated
if it shows anything, run
Code:
brew upgrade
Now run this the correct a few symlinks [Not sure if these are needed anymore]:
Code:
ln -s /usr/local/bin/gfind /usr/local/bin/find && ln -s /usr/local/bin/gsed /usr/local/bin/sed
Now to create our case sensitive image for our CM work [NOTE: the 60g can be changed to anything. It only takes up what it needs but I used 60GB]:
Code:
hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 60g -volname "android" -attach ~/Desktop/Android
Now to create our working directory
Code:
cd /Volumes/Android && mkdir cm10.2 && cd cm10.2
[size=+1]Getting the source[/size]
Now to initialize the git and to download it
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
Download the sources:
Code:
repo sync
Wait until it is finished. It will take a long time, depending on your internet connection.
[size=+1]Obtain the device build files and proprietary files:[/size]
To do this we will use CyanogenMods "tool" called roomservice. Roomservice is replacing the old local_manifest.xml file. Just run the code below to create the file directly into the folder.
Code:
nano -w /Volumes/android/cm10.2/.repo/local_manifests/roomservice.xml
Paste the following lines into the file:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_htc.git" path="vendor/htc" remote="github" revision="cm-10.2"/>
</manifest>
It seems that nowadays you only need to have the TheMuppets repo there, the roomservice process takes care of the rest and downloads the needed mako bits automatically. And actually it doesn't matter what you name the xml file under the local_manifests directory. The process loads every xml file from there in a alphabetical order. If you still have that local_manifest.xml file in your .repo directory, i suggest you remove that, because at that case that file will be read first and after that all the other from the local_manifests folder
Save the file. And rerun the code:
Code:
repo sync
Download the necessary pre-builts:
Code:
/Volumes/android/cm10.2/vendor/cm/get-prebuilts
That is all. The sources are now ready.
[size=+1]Building CyanogenMOD[/size]
If you build now, you're probably gonna get kernel build errors regarding the missing elf.h header (this error might be device specific). Fortunately, we already have this file downloaded, so we only need to copy it to /usr/local/include:
Code:
cp /Volumes/android/cm10.2/external/elfutils/libelf/elf.h /usr/local/include
FINALLY, we are ready to build:
Code:
cd /Volumes/android/cm10.2 && source build/envsetup.sh && brunch m7ul
The upper command will start the build for the international version for the HTC One (m7ul). Just change the m7ul part to the right codename (check it from f.ex www.get.cm webpage).
Then we just let the Mac do the rest. Remember that it will take a while to do the build, and meantime you Macs fans will scream for mercy while CM punishes your system ☺
After the build is finished successfully you can find your newly created flashable zip by typing:
Code:
cd $out
Look for .zip file with a tag UNOFFICIAL
Happy building!

donk

I just might give this a try. Thanks for the tutorial!
Sent from my One using Tapatalk 4

inffy said:
Hey there!
Only Thing that comes to mind is that you forgot to get the prebuilts. Or you flashed incompatible kernel
Click to expand...
Click to collapse
Not that I'm aware of, but I must've messed something up. I nuked it all and started over.
It works fine now (and more importantly I got myself a new "theme aware" aapt that doesn't think that drawable-xxhdpi is an invalid folder name )
Thanks again for a nice guide.

i can add packages of apk github
help
thanks

packhex said:
i can add packages of apk github
help
thanks
Click to expand...
Click to collapse
What do you mean, sry

Strange error
I get this error when I try to save the manifests xml file.
[ Error writing /Volumes/android/cm10.2/.repo/local_manifests/roomservice.xml: ]
Please help me figure this out...
Okay, I figured I hade the wrong directory..
now when I try to brunch, I get this error:
Don't have a product spec for: 'cm_m7ul'
Do you have the right repo manifest?
Please help!