Related
CONTENTS
Post #1 = General Info
Post #2 = [TUTORIAL] How to Compile AOKP for any Xperia phone
Post #3 = KangXperiaProject ROM threads list
================================================================================================
WHAT is KangXperiaProject ??
We (that is KangXperiaProject Team) have tried to create a buildable source tree from which anyone can build AOKP for the Xperia line of devices
This is a combined work of all team members. (Supervenom , Championswimmer, Stelios97, Daveee10, Pikpok)
CREDITS
It is very important to mention here that nothing, yes i repeat NOTHING was possible without the awesome work done by FreeXperia team for the community. For all 2011 devices we are using their device trees almost untouched. So all the hardware work (making camera, sensors, gralloc, hardware acceleration etc work flawlessly) is purely the credit of FreeXperiaTeam (FXP, bin4ry, defer and Kali- )
If there is anyone whom you really need to thank for Xperia devices being able to run CM9/AOSP/AOKP/MIUI or whatever non-stock ROMs it's the great people like :
ZdZihu, FXP, Bin4ry, defer, Kali-, KeiranFTW, DoomLord, Androxyde, Achotjan, Azuzu and many many more.
The only thing that KXP team has done is made the devices and vendor trees fit into the groove of AOKP source tree and manage a buildable environment. Our contribution in KXP ROMs is much much less as compared to the contribution of Team Kang and Team FreeXperia. (Ofcourse on older devices we had to work a lot becuase FXP does not support them anymore)
GET YOUR AOKP ROM FOR XPERIA
Scroll down to Post#3 to see a list of AOKP ROMs available for Xperia phones (that are compiled from KXP source tree).
STATUS OF REPOS
The platform_manifest and source trees we maintain are usually always up-to-date. We can guarantee that the sources are usually always 'buildable' (i.e. the compilation will always be error-free if our source tree is used) but we cannot always guarantee that the builds that you compile will be 'bootable'. This is mainly because we do not own all the devices and hence cannot test if builds are booting or not. Whenever bugs are reported, we try to fix them if our scope of knowledge allows us to.
As of 22 August 2012KXP-AOKP JB Repo : -
- repo can be synced
- buildable for all these devices
Code:
Arc/ArcS aokp_anzu-userdebug
Live with Walkman aokp_coconut-userdebug
Mini aokp_smultron-userdebug
Mini Pro aokp_mango-userdebug
Active aokp_satsuma-userdebug
S aokp_nozomi-userdebug
Acro S aokp_hikari-userdebug
Neo aokp_hallon-userdebug
Neo V aokp_haida-userdebug
Play aokp_zeus-userdebug
Play(CDMA) aokp_zeusc-userdebug
Ray aokp_urushi-userdebug
Pro aokp_iyokan-userdebug
- all builds shall be bootable, but there might be enough bugs to not make it usable dailyKXP-AOKP ICS Repo : -
not actively maintained anymore, repo may not be buildable. we are working ONLY on JB now
- repo can be synced
- buildable for all these devices
Code:
Arc/ArcS aokp_anzu-userdebug
Ray aokp_urushi-userdebug
Neo aokp_haida-userdebug
Neo(V) aokp_hallon-userdebug
Pro aokp_iyokan-userdebug
Play aokp_zeus-userdebug
Play(CDMA) aokp_zeusc-userdebug
Live with Walkman aokp_coconut-userdebug
Mini aokp_smultron-userdebug
Mini Pro aokp_mango-userdebug
Active aokp_satsuma-userdebug
X10 aokp_es-userdebug09ra-userdebug
X8 aokp_shakira-userdebug
X10 MiniPro aokp_robyn-userdebug
X10 Mini aokp_mimmi-userdebug
- all builds are bootable
I'd like to give a quick rundown on how to compile AOKP from sources for all Xperia devices.
The KangXperiaProject had been working for past few weeks to try to set up and maintain a buildable repo for AOKP on all Xperia phones.
The skeleton of this tutorial is taken largely from this thread
This tutorial assumes that you are using Ubuntu (prefer to use 64 bit). If you use some other Linux distro then there might be minor changes in the way the environment is setup. Figure that out yourself
Source code is about 10GB in size. One single build will take about 8GB (10+8=18). For a full set of builds and for building for multiple devices i HIGHLY recommend more than 100 GB of free space on your harddrive.
1) You need the following:
-JDK 6 if you wish to build Ice Cream Sandwich. You can download it from java.sun.com. Or:
Code:
$ sudo apt-get install sun-java6-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
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 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
if you wish to use adb for debugging or logging your builds you need to perform the steps hidden below.
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"
[COLOR=Red]#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"[/COLOR]
#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
the line in red is most important, the other lines are not important if you are using adb only for xperia phones
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
restart your PC or log off and log on
6) Choose work directory:
Code:
$ mkdir -p ~/android/kxp
$ cd ~/android/kxp
(the working directory could be anything you like. ~/android/kxp is an example)
7. Initialize the repo
Code:
$ repo init -u https://github.com/KangXperiaProject/platform_manifest.git -b jb
NOTE : to compile for ICS, use "-b ics" instead of "-b jb"
Only JB is maintained actively now. ICS repos are buildable but not anymore maintained.
7) When prompted, enter your real name and email address.
8) Gather the files:
Code:
Code:
$ repo sync -j1
if you have fast internet, you can use -j8 or -j16 for faster sync
total source will be around 10GB in size. please be patient
9) Compiling:
after complete sync
create the environment
Code:
$ . build/envsetup.sh
now choose your device
Code:
$ lunch
pick your device according to the following list
Code:
Arc/ArcS aokp_anzu-userdebug
Ray aokp_urushi-userdebug
Neo aokp_haida-userdebug
Neo(V) aokp_hallon-userdebug
Pro aokp_iyokan-userdebug
Play aokp_zeus-userdebug
Play(CDMA) aokp_zeusc-userdebug
Live with Walkman aokp_coconut-userdebug
Mini aokp_smultron-userdebug
Mini Pro aokp_mango-userdebug
Active aokp_satsuma-userdebug
X10 aokp_es-userdebug09ra-userdebug
X8 aokp_shakira-userdebug
X10 MiniPro aokp_robyn-userdebug
X10 Mini aokp_mimmi-userdebug
S aokp_nozomi-userdebug
Now start the build process
Code:
mka -j4 otapackage
yes it's "mka" not "make"
you can obviously use make instead of mka but mka is faster and optimized specially for android building.
NOTE: the -j# number should be double the number of cores of your CPU (the CPU of the PC on which you are building)
Thus if you are on a quad core build machine use -j8
If compilation (i.e. the last step) takes too much time for your comfort, you can see this article written by cyanogenmod devs Koush and aremcee to make compile time less
After everybuild, we need to clean the directory... do it like this
Code:
cd ~/android/kxp
make clobber
("make clean" also works)
Before next build, sync repo again to get latest changes
Code:
repo sync -j2
Now build again
Code:
. build/envsetup.sh
lunch
Code:
mka -j4 otapackage
AOKP(JB 4.1.1) ROMs for Xperia Phones
(which are maintined by KXP team members/friends)
Xperia Mini/MiniPro/Active/LiveWALKMAN
Xperia S
Xperia Acro S
Xperia Arc / Arc S
Xperia Ray
Xperia Play
Xperia Pro
Xperia Neo
Xperia Neo V
AOKP(ICS4.0.4) ROMs for Xperia Phones
(which are maintined by KXP team members/friends)
Xperia Arc / Arc S
Xperia Neo [cooked and optimized by kormatoes]
Xperia Neo(v) [cooked and optimized by kormatoes]
Xperia Ray
Xperia Pro
Xperia Play (GSM/CDMA)
Xperia Mini/MiniPro/Live/Active
Xperia X10
Xperia X8
Xperia X10 Mini
Xperia X10 MiniPro
On the last action, to build, isn't the make to use instead of mka ? typo ?
mekayzer said:
On the last action, to build, isn't the make to use instead of mka ? typo ?
Click to expand...
Click to collapse
nope buddy... it's mka only... you can use make too ... but mka is faster
Great thread
Sent from my Xperia neo using XDA Premium HD app
kormatoes said:
Great thread
Sent from my Xperia neo using XDA Premium HD app
Click to expand...
Click to collapse
you can also begin making native builds for neo/neov using this method if you want...
haida and hallon are already present in the working tree and are buildable (as of now we do not make builds for hallon/haida because we do not want two aokp threads for same device )... but you and your team can anytime start building aokp from source using our trees, and we would be very happy
can you push aplha build for JEllY BEAN from sorces ?
championswimmer said:
you can also begin making native builds for neo/neov using this method if you want...
haida and hallon are already present in the working tree and are buildable (as of now we do not make builds for hallon/haida because we do not want two aokp threads for same device )... but you and your team can anytime start building aokp from source using our trees, and we would be very happy
Click to expand...
Click to collapse
I need new pc bro ubunto it's not the best on it I will have a play tonight with it thanks for your great words much love Chris
Sent from my Xperia neo using XDA Premium HD app
n1kolaa said:
can you push aplha build for JEllY BEAN from sorces ?
Click to expand...
Click to collapse
maybe a week from now we can start doing that...
devices like Ray, Arc and Neo already have a stable milestone6 so next builds for these devices will be jellybean only
early builds MAY NOT be bootable, or have too many bugs to be usable...
also AOKP team have not properly set up a jb repo completely yet.
i myself have started the repo sync process for jb... it'll take me about 7-8 hours to complete the sync as i have slow internet...
jb repo is not buildable right now as it is pure aosp atm and to make xperia devices buildable many changes need to be committed
i also want to make it clear here that people like me, supervenom and pikpok are just "schoolboys" we are no major developers and cannot make hardware libraries from ground-up
we depend heavily on freexperia team's device and vendor source trees. the ics trees will provide a start but we will need some changes to that to make it 100% working and we do not know if our team of noobs can pull it off
and also it's hard to develop without devices... (supervenom owns an Xperia Play and I own an Xperia X10, while pikpok owns LiveWalkman... none of us own any hdpi 2011 device like ray, neo or arc)
On Ubuntu for 5 mins already want to smash it lol
{
"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"
}
Champ and me on talk so I can ask you ridiculous amount of questions jk lol
Sent from my Xperia neo using XDA Premium HD app
kormatoes said:
On Ubuntu for 5 mins already want to smash it lolView attachment 1193140View attachment 1193140
Champ and me on talk so I can ask you ridiculous amount of questions jk lol
Sent from my Xperia neo using XDA Premium HD app
Click to expand...
Click to collapse
look at your pm
btw i use an even older notebook than yours
1.6ghz dual core, 4gb ram and 4mbps download speed.... my environment is worse than yours ha ha ha... but well... i have to make do with it...
it put the repo sync all over night and put mka otapackage when i go for lunch/swimming practice/hanging out with friends ha ha ...
also my upload takes 2-3 hours...
but after first compilation, from next time time will be very less...
also repo sync takes long only first time.. from next time it'll only update and so it'll be only 5-10 minutes...
championswimmer said:
look at your pm
btw i use an even older notebook than yours
1.6ghz dual core, 4gb ram and 4mbps download speed.... my environment is worse than yours ha ha ha... but well... i have to make do with it...
it put the repo sync all over night and put mka otapackage when i go for lunch/swimming practice/hanging out with friends ha ha ...
also my upload takes 2-3 hours...
but after first compilation, from next time time will be very less...
also repo sync takes long only first time.. from next time it'll only update and so it'll be only 5-10 minutes...
Click to expand...
Click to collapse
Since I am going to have to set up a Ubuntu partition anyway...does it matter which version of ubuntu I install....I saw in some JellyBean threads that some versions are not "guaranteed" supported......
justmpm said:
Since I am going to have to set up a Ubuntu partition anyway...does it matter which version of ubuntu I install....I saw in some JellyBean threads that some versions are not "guaranteed" supported......
Click to expand...
Click to collapse
i am running 12.04 so i can "guarantee" that 12.04 at least will not fail to build this
jdk6 might be a pain in the a$$ but there are workarounds to install this found on google.... (this problem is common to all ubuntu distros)
Does the kernel compiled on the fly when the rom is builded, or does we compile separately a kernel.
Thanks for the thread.
mekayzer said:
Does the kernel compiled on the fly when the rom is builded, or does we compile separately a kernel.
Thanks for the thread.
Click to expand...
Click to collapse
for all 2011 devices (ray, arc, neo, lww, mini, pro, active) on the fly
for others, you need to compile separately (X10, X8, X10mini, X10minipro)
Thank you.
bloody brilliant thread champ! :victory:
shows the love when people are willing to share the knowledge, i will be messing with this very shortly! great stuff, thanks man! :highfive:
I am getting an error during the sync: Exited sync due to fetch errors
First I tried: repo sync -j8 and that failed after 3-4 hours
Then I deleted the working dir, made a new one and tried: repo sync -j16
That failed after about 1 hour....
Thinking back on it, I probably should have tried a slower and not a faster download....ehhhh, what
can I say...patience was all gone.....
Not sure what I should do...I looked in google for a fix and it didn't seem like there was a
more or less universal fix.....
justmpm said:
I am getting an error during the sync: Exited sync due to fetch errors
First I tried: repo sync -j8 and that failed after 3-4 hours
Then I deleted the working dir, made a new one and tried: repo sync -j16
That failed after about 1 hour....
Thinking back on it, I probably should have tried a slower and not a faster download....ehhhh, what
can I say...patience was all gone.....
Not sure what I should do...I looked in google for a fix and it didn't seem like there was a
more or less universal fix.....
Click to expand...
Click to collapse
do NOT delete your working directory on bad syncs
just kill the terminal window, restart terminal, cd to working directory and run "repo sync -j#" again it will resume from where it left
i personally use -j2 and that's what i would suggest you to use too
i often have sync errors, i just restart sync and it finishes
---------------------------------------------------------------
Easy Rooting toolkit (v17.0)
created by DooMLoRD
"pref_event exploit"
Credits go to all those involved in making this possible!
---------------------------------------------------------------
Special thanks to: the_laser, Bin4ry, fi01, hiikezoe, [NUT]
and to all those who are contributing to our git tree!
Sources:
---------------------------------------------------------------
[*] This script will:
(1) root ur device using the pref_event exploit
(2) install Busybox
(3) install SU files
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) connect USB cable to PHONE and then connect to PC
(5) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing files
63 KB/s (326 bytes in 0.004s)
223 KB/s (1578 bytes in 0.006s)
1311 KB/s (26268 bytes in 0.019s)
2493 KB/s (853044 bytes in 0.334s)
2112 KB/s (96260 bytes in 0.044s)
3295 KB/s (1858064 bytes in 0.550s)
--- DooMing device!
--- Correcting permissions
--- Running exploit
run_root_shell v6.2
Based on pref_event exploit
Modified for auto-rooting by DooMLoRD
Part of Easy Rooting Toolkit
Devices Supported:
Xperia Z (C6602/3) - 10.1.1.A.1.253/307
Xperia Z (C6602/3) - 10.3.A.0.423
Xperia Z (C6606) - 10.1.1.B.0.166
Xperia ZL (C6502/3/6) - 10.3.A.0.423
Tablet Z (SGP321) - 10.1.1.A.1.307
Tablet Z (SGP311/2) - 10.1.C.0.370
Xperia ZR (C5502/3/M36h) - 10.1.1.A.1.310
Xperia SP (C5302/3/6) - 12.0.A.1.211/257/284
Xperia L (C2104/5) - 15.0.A.1.31/36
Xperia T (LT30p) - 9.1.A.1.141/142
Xperia TX (LT29i) - 9.1.B.1.67
Xperia V (LT25i) - 9.1.A.1.140/142/145
Xperia S (LT26i) - 6.2.B.0.200/211
Xperia SL (LT26ii) - 6.2.B.0.211
Xperia Acro S (LT26w) - 6.2.B.0.200/211
Xperia Ion (LT28h) - 6.2.B.0.211
Xperia P (LT22i) - 6.2.A.1.100
Xperia Go (ST27i/a) - 6.2.A.1.100
Xperia J (ST26i/a) - 11.2.A.0.21/31
Xperia AX (SO-01E) - 10.1.D.0.343
Tablet Z (SO-03E) - 10.1.E.0.265/269
Xperia GX (SO-04D) - 7.0.D.1.137
Xperia A (SO-04E) - 10.1.1.D.0.179
Xperia A (SO-04E) - 10.1.1.D.2.26
Xperia SX (SO-05D) - 7.0.D.1.137
Xperia SX (SO-05D) - 9.1.C.0.475
Xperia VL (SOL21) - 9.0.F.0.226
Xperia VL (SOL21) - 9.1.D.0.395/401
Xperia UL (SOL22) - 10.2.F.3.43
Google Nexus 4 - JDQ39
Google Nexus - JOP40C/JZO54K
LG Optimus G E975 - v10e
Changelog is posted here:
Device detected: C6603 (10.3.1.A.0.244)
C6603 (10.3.1.A.0.244) is not supported.
You need to manage to get remap_pfn_range addresses.
--- cleaning
--- Please wait device is now rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Previously rooted and everything was fine, bricked during a reboot so factory reset it, can't root anymore. Suggestions on a similar thread were to flash a rom with flashtool but the Xperia Z cannot be brought into fastboot mode. What do?
Stock rom need flash mode not fastboot.
Volume down + connect the usb.
http://forum.xda-developers.com/showthread.php?t=2240614
Sent from my C6603 using xda premium
gm007 said:
Stock rom need flash mode not fastboot.
Volume down + connect the usb.
http://forum.xda-developers.com/showthread.php?t=2240614
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Thank you
Hi Guys, I tryed Root my Xperia SP using " Easy Rooting toolkit (v17.0)' but I didnt have sucess.
Could someone help me with it ?
---------------------------------------------------------------
Easy Rooting toolkit (v17.0)
created by DooMLoRD
"pref_event exploit"
Credits go to all those involved in making this possible!
---------------------------------------------------------------
Special thanks to: the_laser, Bin4ry, fi01, hiikezoe, [NUT]
and to all those who are contributing to our git tree!
Sources: https://github.com/android-rooting-tools
---------------------------------------------------------------
[*] This script will:
(1) root ur device using the pref_event exploit
(2) install Busybox
(3) install SU files
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) connect USB cable to PHONE and then connect to PC
(5) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Pressione qualquer tecla para continuar. . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing files
31 KB/s (326 bytes in 0.010s)
66 KB/s (1578 bytes in 0.023s)
1508 KB/s (26268 bytes in 0.017s)
2421 KB/s (853044 bytes in 0.344s)
1773 KB/s (96260 bytes in 0.053s)
2448 KB/s (1858064 bytes in 0.741s)
--- DooMing device!
--- Correcting permissions
--- Running exploit
run_root_shell v6.2
Based on pref_event exploit
Modified for auto-rooting by DooMLoRD
Part of Easy Rooting Toolkit
Devices Supported:
Xperia Z (C6602/3) - 10.1.1.A.1.253/307
Xperia Z (C6602/3) - 10.3.A.0.423
Xperia Z (C6606) - 10.1.1.B.0.166
Xperia ZL (C6502/3/6) - 10.3.A.0.423
Tablet Z (SGP321) - 10.1.1.A.1.307
Tablet Z (SGP311/2) - 10.1.C.0.370
Xperia ZR (C5502/3/M36h) - 10.1.1.A.1.310
Xperia SP (C5302/3/6) - 12.0.A.1.211/257/284
Xperia L (C2104/5) - 15.0.A.1.31/36
Xperia T (LT30p) - 9.1.A.1.141/142
Xperia TX (LT29i) - 9.1.B.1.67
Xperia V (LT25i) - 9.1.A.1.140/142/145
Xperia S (LT26i) - 6.2.B.0.200/211
Xperia SL (LT26ii) - 6.2.B.0.211
Xperia Acro S (LT26w) - 6.2.B.0.200/211
Xperia Ion (LT28h) - 6.2.B.0.211
Xperia P (LT22i) - 6.2.A.1.100
Xperia Go (ST27i/a) - 6.2.A.1.100
Xperia J (ST26i/a) - 11.2.A.0.21/31
Xperia AX (SO-01E) - 10.1.D.0.343
Tablet Z (SO-03E) - 10.1.E.0.265/269
Xperia GX (SO-04D) - 7.0.D.1.137
Xperia A (SO-04E) - 10.1.1.D.0.179
Xperia A (SO-04E) - 10.1.1.D.2.26
Xperia SX (SO-05D) - 7.0.D.1.137
Xperia SX (SO-05D) - 9.1.C.0.475
Xperia VL (SOL21) - 9.0.F.0.226
Xperia VL (SOL21) - 9.1.D.0.395/401
Xperia UL (SOL22) - 10.2.F.3.43
Google Nexus 4 - JDQ39
Google Nexus - JOP40C/JZO54K
LG Optimus G E975 - v10e
Changelog is posted here: http://bit.ly/ert_log
Device detected: C5303 (12.0.A.1.211)
Attempt perf_swevent exploit...
writing address is 8e49
Launching auto-root script!
---------------------------------------------------------------
Launching final rooting process...
---------------------------------------------------------------
--- Rooting!
--- Remounting rootfs
--- Killing RIC service (specific for new Xperia devices)
Unable to chmod /sbin/ric: No such file or directory
--- Installing busybox
--- Remounting /system
--- copying busybox to /system/xbin/
1666+1 records in
1666+1 records out
853044 bytes transferred in 0.032 secs (26657625 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
rm failed for /system/xbin/su, No such file or directory
188+1 records in
188+1 records out
96260 bytes transferred in 0.006 secs (16043333 bytes/sec)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
rm failed for /system/bin/su, No such file or directory
--- pushing Superuser app
3629+1 records in
3629+1 records out
1858064 bytes transferred in 0.070 secs (26543771 bytes/sec)
--- correcting permissions
--- DONE!
--- cleaning
--- Please wait device is now rebooting
ALL DONE!!!
Pressione qualquer tecla para continuar. . .
SOLVED !
Okay so there are several guides on XDA on how to compile Roms from source etc. Since the development for this device is growing... I want to encourage other members to contribute to development and teach those who don't know yet about compiling. This is an extremely indepth tutorial intended not only to teach basics...but also to clear up working of some stuff.
THIS IS A 5 PART TUTORIAL COVERED IN 5 POSTS.
So without further ado.......
################
THE BASIC STUFF
################
This will cover all the basics of android development...which is I think common to most other tutorials. This part will teach you how to compile a ROM from source.
First we select an OS. You can use gentoo or mint
But I prefer to use Ubuntu 12.04 64 bit.(OUTDATED)
Note: YOU CANNOT COMPILE ROMS ON 32 BIT ONLY KERNELS.
So let's download Ubuntu 16.04 (Xenial Xereus) image
http://releases.ubuntu.com/16.04/
Now that you have downloaded it.. You can set it up as a virtual machine in virtual box or dual boot it. You may also use it as primary os if you want.
Now let's set up the build environment.
Open up the terminal
Type this in the terminal window:
Code:
bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev
g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-dev lib32z1-dev
For Marshmallow and up replace openjdk7 with 8...
Now you need to install the android SDK
Get it here :http://developer.android.com/sdk/index.html
Extract this in the home directory
Now in the terminal window type this:
Code:
gedit .bashrc
A text editor will pop up. Add these lines at the very end:
Code:
# Android tools
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin
Now again in terminal window type:
Code:
gedit .profile
Add this:
Code:
PATH="$HOME/android-sdk/tools:$HOME/android-sdk/platform-tools:$PATH"
The SDK is now installed!
Now before we install the repo tool
Run this in terminal window
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
and add these lines:
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"
Save it and run:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
What we just did was Adding vendor id's for USB connectivity.
Whew ..... That was quite long.... Now let's be back to business.
Installing the repo tool:
To manage the git repos and to use them for our various needs like initializing them and syncing we use a tool made by Google called the repo tool.
Type this in terminal window:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Now you are all geared up for compiling roms !
For demonstration in this tut we will take the device as golfu and our source path as:
/home/user/android/system
So make the source folder by:
Code:
cd ~/
mkdir android
cd android
mkdir system
cd system
Now let's initialize the repo..... Let's decide which one to sync.... I'll use cm11 for this tutorial.
When you are in source folder type in terminal:
Code:
repo init -u *git link to source* -b *branch name*
The repo init link can generally be found in the manifest of the ROM on github.
So for cm 11 it should be like this :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11
Now you have successfully initialized cm11 source code in your directory!
Now you need to download the sources..... The android source code is very large and it may take a little to a looong time to download depending on your internet speed.
So when you are in your source directory:
Code:
repo sync -j#
# will be the no. Of jobs
A larger number will give better result if your internet is fast but entering an insane number won't help.
I use:
repo sync -j8
Now wait till your source is synced...long process.
After the source is downloaded you need to get the device specific parts.
You need to get the kernel source, device tree and vendor tree.
For this device you need not download the vendor tree
Download device tree as a zip from github
Extract CONTENTS to:
/home/user/android/system/device/htc/golfu
Create folders if not present.
Download the kernel source from github as a zip
Extract CONTENTS to:
/home/user/android/system/kernel/htc/golfu
Create folders if not present.
Now your source code is completely set up for compiling for our device !
Before building get the prebuilts:
Code:
cd /home/user/android/system/vendor/cm
. get-prebuilts.sh
Set up for building:
Type this in terminal
Code:
. build/envsetup.sh
Do this every time before building
And now finally start building!!
Type this in terminal to start building:
Code:
brunch cm_devicename-userdebug -jx+1
Where x is number of cores. My laptop has 4 cores.
So for golfu it should be :
Code:
brunch cm_golfu-userdebug -j5
Wait for it to complete building.
After it is done .... Your build can be found at
/home/user/android/system/out/target/product/golfu.
It will look like : cm-11-YYYYMMDD-UNOFFICIAL.zip
CONGRATULATIONS! You have built your very own ROM
Remember to make clean before every build!
This is the end of part one of series.
Please note, if by any chance there is a problem of java, python, maven, git etc.. not installed:
sudo apt-get install neededthing
Let's get on with part 2 of this series of 5!
########################
THE SOURCE CODE
########################
OKAY so if you followed the tutorial you theoretically speaking have created your own build.
BUUT ... Its not always like that practically.
You are bound to get errors especially if you are using your own device tree. So let's have a study of the source code so that you know what's wrong and what is what.
Let's get started!
So the source code in our folder has 2 parts:
a) Generic source code
b)Device-specific code
The generic source code is the ROM source code which is similar for all devices
The folders you should find there:
Bionic
Build
Bootable
Dalvik
Art
Device
Docs
External
Frameworks
Hardware
Kernel
Ndk
Out
Packages
Prebuilt
Prebuilts
System
Vendor
So let's see what goes in each folder:
Bionic: is the Android mobile-friendly version of libc.Lots of cpu-specific stuff present here. Better not to touch anything here and move along.
Build:The scripts and various files that are used for the actual build process are present here. You can see the various steps for compiling android
Bootable: The source of CWM is here
Dalvik: its the virtual machine that runs java apps.
You might recall in computer classes you were taught that java programs do not depend on the underlying architecture. This is why its so.
Art: art stands for android runtime. Its a replacement for dalvik in android 4.4
Device: it contains the device configurations for a particular device.
Docs: contain the source for Android Open Source website.
External: This is where non-android specific utilities go. Lots of the stuff in here are just regular open source projects that are used by Android.
Frameworks:This refers to the core Android frameworks. It's the stuff that makes Android, Android. The frameworks contain the Android user experience and the abstracted "hooks" that programmers use to build Android apps.
Hardware : specific libraries go in this folder.
The drivers for our WiFi chip ath6kl should be here.
Kernel: the kernel source code can be found here.
Ndk: Tools for allowing cross-platform C code to be included in Android apps.
Out: the output I.e the compiled ROM will be here.
Packages: the android apps are present here.
Prebuilts : contains the tool chains.
System: Lower-level linuxy system stuff such as netd, fastboot support, the shell
Vendor: it contains stuff particular to a vendor build such as CyanogenMod. It's also the place where proprietary blobs are extracted from the device.
That's it for generic sources.
Source: cyanogenmod docs
Now let's talk about the device specific code. You may already have guessed, its the code that contains all the configurations for our device...making the compiled ROM unique for our device.
Now let's have a closer look at it.
The device specific code contains 3 parts:
a)device tree
b)vendor tree
c)kernel source code.
Let's talk about the device tree.
Here is a perfect example of a great device tree.https://github.com/codexblack/golfu
Kidding. That one is for 4.3 and it barely works but it will do for demonstration.
In depth look time!
Files in the device tree *yawn* you guys still with me?
AndroidBoard.mk
AndroidProducts.Mk
BoardConfig
Device.Mk (for us: golfu.Mk)
Cm.Mk(for cyanogenmod. Will vary with different Roms)
Recovery.fstab
System.prop
Vendorsetup.sh
Now what each one does:
AndroidBoard: these files are present in our ramdisk in the kernel. You can decompile the kernel to see these files.
BoardConfig: you set up paths to some files and declare some stuff about architecture.
Device.Mk: define libs to be compiled along with other stuff. Take a look and you should understand
System.prop: build prop configuration
Vendorsetup.sh: self explanatory.
Let's move on to kernel
Its the source code of the kernel for our device.
After compilation it looks something like a boot.IMG..you might have seen in ROM folder . The kernel is very important. But what does it do? When software needs the hardware to do anything, it sends a request to the kernel.
That's it for kernel..... It handles all the instructions to put simply.
Vendor tree.....
It contains the proprietary blobs for our device.
We do not use it in golfu
Whew .... That's it for device specific code!
Move on to part 3.
Part 3 is here! Even if I move on to part 4... It won't mean this is over. I will keep on adding stuff here.
So now...........
###########################
TIPS,TRICKS AND MISC STUFF
###########################
Nightlies:
Okay so you have sources synced for a ROM say cm11.
Its complete and running with a proper device tree and kernel.
You want to do nightly or weekly builds for it.
So what IS a nightly/weekly?
These are build of the ROM done every night or week by pulling the latest source code of the ROM with all the new commits and build it to keep the ROM up to date.
How to do it? Sure compile every night. But that's not conventional eh?
So let's use this script for night lies!(please tell me if it didn't work).
Code:
#!/bin/bash
#navigate to source directory
cd ~/home/user/android/system
#clean out folder before building
make clobber
#sync source. Modyfy script to set -j flags accordingly
repo sync
#Set up for building
source build/envsetup.sh
#Start build process
brunch cm_golfu-userdebug
#rename to nightly
cd ~/home/user/android/system/out/target/product/golfu
mv cm-11*.zip cm-11-$(date +%Y%m%d)-golfu-NIGHTLY.zip
I've explained what the script does along the way.
Make changes accordingly for different Roms,devices and weeklies.
Save it as script.sh
Then navigate to folder of script and type
Code:
./script.sh
If some permission issue arises type
Code:
su chmod 755 script.sh
CCACHE:
Wanna cut down compilation time?? Use CCACHE!
Go to /home and open .baschrc by using gedit .basrc in terminal
Add these lines:
Code:
export USE_CCACHE=1
export CCACHE_DIR=/source-directory/prebuilts/misc/linux-x86/ccache
Navigate to source-directory and type this in terminal:
Code:
prebuilts/misc/linux-x86/ccache/ccache -M 50G
50G = 50gb of cache . Change it accordingly.
Cherry Picking:
Want to apply changes to your device tree by applying commits from github? Instead of manual copy-pasting its better to cherry pick those commits and apply in
your device tree!!
FIrstly, Navigate to your device tree.
Now that thats done:
Code:
git init
git pull [email protected]:username/android_device_htc_golfu.git
Now after that time to fetch the project from which we are cherry picking:
Code:
git fetch git://github.com/user/repo.git
Now time to cherry-pick the commit itself. You might have noticed that the commit has a particular id which looks like a long string.
eg: ab72e4ab36778474593ffce89150aece01d5f9c
so what we do now is:
Code:
git cherry-pick thecommitid
And you are done!!
Local Manifests:
There are many useless files in the source (for us) that we donot need. The vendor, kernel and device trees of official devices may be included. Why should we waste
data by downloading them? Lets remove them from our sync!
Code:
cd source/.repo
gedit local_manifest.xml
example of how to remove a project:
Code:
<remove-project name="CyanogenMod/android_hardware_qcom_fm" />
Using the reference flag:
Now that we have compiled CyanogenMod and want to compile another ROM , should we waste hours syncing again??
NO
We shall use the reference flag instead!!
So now navigate to the new folder created for the new source and then enter:
Code:
repo init --reference=~/rootofdownloadedsource -u git://url.com/ROM.git -b branch
What the reference flag does is it just simply transfers the common projects instead of re-downloading them saving time and data!
I was gonna put a kernel compiling guide here but i saw that there was already a good one.
So i shall link it here: http://forum.xda-developers.com/showthread.php?t=2246833
Now to the last part of the series..... Part 5
Thanks for sticking with me guys!
########################
F.A.Q'S and common build errors
########################
Q. What are ideal configurations for compiling?
:- You need to have at least 4gb ram and a dual core processor. Make sure you have at least 200gb free space.
Oh and have a decent internet of 2mbps+ to compile without headaches.
Q. I have less than 4gb of ram....what should I do?
:- Make a swap partition. Search how to make one.
Q. Help I have bugs in the build!
:- calm down. Take a logcat and study it. You can take logcats from phone itself by using aLogCat or CatLog app.
Q. I want to use this rom on my phone but its not there!
:- Ask someone to build it or even better... Build it yourself using your new knowledge. You will even earn some respect!
Q. Help I'm getting build errors!
:- Read the error statement properly goto the file associated with the error and see if there is a logical mistake like a missing semicolon or bracket. Search for similar errors on Google. No avail? Post it here. I'll try to solve and post the error with solution for everyone to see.
But please try first.
Q. My PC froze burning building.
:- you probably don't have enough ram. Use SWAP.
Q. It says permission denied while building.
:- Either use file explorer and right click the file in question and give it r/w access or cd to the directory and:
chmod 777 filename.extension
Q. How do I fix bugs in ROM?
:- take a log cat. Address the errors listed there.
Q. There is an error saying there is no way to define /xyz/kernel needed by /xyz/boot.img
:- Make sure the kernel source is in correct directory. Check in the boardconfig. Are you using prebuilt kernel? Then make sure its taken care of in the BoardConfig.
Q. Server connection failed with Jack
:- Kill server using jack-admin kill-server then enter:
sudo apt-get install libcurl4-openssl-dev nss-updatedb
Q. Jack froze, giving heap error.
:- Need to increase ram dump. For example try this:-
# Use 7GB RAM for Jack Server -1GB from 8GB
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx7000m"
# Killing...
out/host/linux-x86/bin/jack-admin kill-server
# Starting...
out/host/linux-x86/bin/jack-admin start-server
NOTE: IN LEGACY DEVICES YOU NEED TO ADD DISPLAY LEGACY AND MEDIA LEGACY DRIVERS!
Get it here https://github.com/androidarmv6/android_hardware_qcom_display-legacy/archive/cm-10.1.zip
And always remember...
.experience is the best teacher guys. These should clear basic doubt's. Learn as you go!
Le credits:
The cyanogenmod team
galaxyfreak, with whose tut I learnt to compile.
Fluoxetine , who helped me with some stuff
Same stuff if I'm using linuxmint 16?
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
Same stuff if I'm using linuxmint 16?
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Generally should be
Because I find Linux mint's ui better than Ubuntu
Sent from my HTC Desire C using XDA Premium 4 mobile app
NOTE: YOU CANNOT COMPILE ROMS ON 32BIT ONLY KERNELS
Click to expand...
Click to collapse
noobish confusion but what exactly does that mean?
Bashing away at my HTC Desire C
Antagonist42 said:
noobish confusion but what exactly does that mean?
Bashing away at my HTC Desire C
Click to expand...
Click to collapse
It means u can compile Kernels on 32-Bit OS but ROMs Require 64-Bit OS
Google It
Thanks
Sparky
That makes even less sense!
Not being able to make a 32bit ROM that uses Thumb2 and can use half-word requires you to build it on a 64bit system! :banghead:
Google says it's preferable to use 64bit for builds above Gingerbread, biggest thing it effects is build time using 32bit.
Bashing away at my HTC Desire C
Well I should say cyber you have done a wonderful job in making this guide specifically for golfu...we really appreciate your work for this device you don't even own...
Thanks a lot and I am sure this would help us make roms from source for this cute device...
Thanks once again mate !:good:
Part 2 finished
Part 5 done.
Expect part 3 and 4 today
Dude nnice work..Just visinting this section after some time cauz i dont have this device aymore..
One advice
For kernel link nikhil's kernel guide
It was great and i had compiled my kernel
just for the sake of knowing how to do it .. and is very good just some confusion which on reading whole thread can be solved
DELETED
Before building get the prebuilts:
Code:
cd /home/user/android/system/vendor/cm
. get-prebuilts.sh
It should be
Code:
./get-prebuilts
this gives error(. get-prebuilts.sh) no such directory found...
warrior1208 said:
Getting this by using this device tree...
Code:
Trying dependencies-only mode on a non-existing device tree?
Also, I noticed that this device tree is just 13 mb .zip whereas the kernel tree is itself 118mb
Then, maybe should I use cm10.1/10 device tree??? Anyone plz help asap...
Edit: alright, will today try with cm10/10.1/10.2 device trees...
Click to expand...
Click to collapse
Haha..... Late reply, but that's nothing to worry about. it's normal. Anyway, I'm trying to build too.... so we can try and get stuff fixed together.
rudi_j7 said:
Haha..... Late reply, but that's nothing to worry about. it's normal. Anyway, I'm trying to build too.... so we can try and get stuff fixed together.
Click to expand...
Click to collapse
After 20-25 days! Exams arriving soon!
Thanks
Thanks
This thread was created by @EnricoD, and everything except post #6 is his work. I took over this thread when he decided to discontinue support. All credit goes to him.
{
"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"
}
*****************************************
*****************************************
Build Your First CM11 Theme (or APP!!!)
- SETTING UP THE BUILD ENVIRONMENT -
WINDOWS INSTRUCTIONS
1) Download, Install and set up the Java JDK
- Download and install the JDK (32 or 64bit)
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
- Navigate to
System Properties --> Advanced system settings --> Evironmental variables
and create a new variable called "JAVA_HOME" where we'll add the JDK path:
2) Eclipse Setup
- Download Eclipse ADT and Extract to C:\
http://developer.android.com/sdk/index.html
LINUX INSTRUCTIONS
1) We need the JDK!
- Open the terminal! roftl
- Install the OpenJDK running:
Code:
sudo apt-get install openjdk-7-jre
Let's make sure the correct version of Java is running on our PC. To do this just run
Code:
java -version
2) SDK setup
- Download the Standalone SDK Package from here:
DOWNLOAD: http://dl.google.com/android/android-sdk_r23.0.2-linux.tgz
- Install the SDK Package
Let's create a folder in your Home called "development" (You can also call it pincopallino, gino, pippo, Giovanni, Lemonpie, Material, Mathias Duarte... if You want lol)
Code:
mkdir ~/development
Navigate to (your) downloads folder (cd Scaricati for example if You're Italian like Me xD or a custom one... you know!)
Code:
cd ~/Downloads
Extract the SDK package
Code:
tar -zxvf android-sdk_r23.0.2-linux.tgz
move the folder inside development's one. We are already inside the downloads folder! so just run:
Code:
mv android-sdk-linux ~/development/
LINUX & WINDOWS INSTRUCTIONS
3) Setup ADB/FASTBOOT in Linux and Update Developers Tools in Linux&Windows
- Linux [You can do this step after Eclipse installation also (like in Windows), it's the same]
cd to the Android SDK tools folder by running this command:
Code:
cd ~/development/android-sdk-linux/tools
Run the SDK Manager:
Code:
./android
- Windows
Open Eclipse ADT and Navigate to/Open
Window --> Android SDK Manager
At this point the SDK should come up
and .. and... you will need to download all the tools and all the extras files already selected by default.
1. Be sure to select at least Android 4.4.2 (API 19)!!!!!!!, so select them and install'em all \m/ \m/.
2. !!!! Avoid Android L (API 20, L preview) & Android 4.4W (API 20) installation. You don't need it for now! (but, if You want to start developing apps for Android L then install them .. your choice! )
Accept all licenses and click OK to all the prompts during installation
- Setting up ADB&FASTBOOT in Linux
When it finishes downloading everything you have to run this commands in terminal to return to Your Home folder:
Code:
cd
so let's edit the .bashrc!:
(You can also use gedit if in Ubuntu, leafpad for Lubuntu, etc etc)
Code:
nano .bashrc
and add your SDK paths at the end of it:
Code:
#Android PATHS
export PATH=$PATH:~/development/android-sdk-linux/tools
export PATH=$PATH:~/development/android-sdk-linux/platform-tools
Once done Save or press ctrl+x to exit, S and enter if You're using nano
Then Run:
Code:
source ./.bashrc
If you followed everything carefully adb and fastboot should work! To check this reopen a terminal and simply type:
Code:
fastboot
The output will look like this:
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall
... bla bli blu bla bli bli blu bla bla cit. Jake
Click to expand...
Click to collapse
if this method is not working, then install android-tools from ppa:
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Fixing ???????? No permissions errors (click to show)
To fix this error we need to create a file called android.rules:
Code:
cd /tmp/
and create android.rules by running:
Code:
sudo touch android.rules
Edit the file
Code:
sudo nano android.rules
and copy&paste the following lines:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
Save when finished.
Now we have to copy that file inside /etc/udev/rules.d/ and rename it to 51-android.rules. To do this just run:
Code:
sudo cp /tmp/android.rules /etc/udev/rules.d/51-android.rules
Now you have to set the right permissions to this file, just type:
Code:
sudo chmod 644 /etc/udev/rules.d/51-android.rules
Code:
sudo chown root. /etc/udev/rules.d/51-android.rules
and we restart udev and kill adb:
Code:
sudo service udev restart
Code:
sudo killall adb
4) Set up Eclipse IDE in Linux
- Dowload latest Eclipse IDE (I prefer the classical one instead of Google's one)
http://www.eclipse.org/downloads/?osType=linux&release=undefined
- Install Eclipse
cd to downloads folder
Code:
cd ~/Downloads
Extract Eclipse folder by running:
Code:
tar -zxvf eclipse-standard-luna-R-linux-gtk.tar.gz
Move this folder inside /opt folder
Code:
sudo mv eclipse /opt
Run the following command to make eclipse available for all users:
Code:
sudo ln -s /opt/eclipse/eclipse /usr/bin/eclipse
Now, we are going to add a Menu's shortcut, just create this file:
Code:
sudo nano /usr/share/applications/eclipse.desktop
and add the following content:
[Desktop Entry]
Version=4.3.2
Name=Eclipse
Comment=IDE for all seasons
Exec=env UBUNTU_MENUPROXY=0 /opt/eclipse/eclipse
Icon=/opt/eclipse/icon.xpm
Terminal=false
Type=Application
Categories=Utility;Application;Development;IDE
Click to expand...
Click to collapse
ctrl+x then Y to save.
- Now We can run Eclipse and choose the location of our workspace (we can leave the default one and tickmark «use this as the default and do not ask again»)
NOTE: You can also use directly Eclipse ADT + sdk instead of classical Eclipse IDE.
http://developer.android.com/sdk/index.html
5) ADT Plugin setup
FOLLOW THIS:
http://developer.android.com/sdk/installing/installing-adt.html
6) Android Studio
http://developer.android.com/sdk/installing/studio.html
- Linux
Code:
cd ~/Downloads
Code:
tar -zxvf android-studio-bundle-135.1245622-linux.tgz
mv android-studio ~/development/
To run it you just need to navigate to its bin folder and type
Code:
./studio.sh
also, check @blinqipa 's thread because I don't use Android Studio xd
http://forum.xda-developers.com/showthread.php?t=2780923
7) APKTOOL (in case You need it)
WINDOWS INSTRUCTIONS
- Download Apktool from here and extract where You want:
http://forum.xda-developers.com/showpost.php?p=50205159&postcount=90
LINUX INSTRUCTIONS
- Download it running this in a terminal:
Code:
wget https://www.dropbox.com/s/6s9bxszxjl7wclz/apktool.tar.gz
- Extract
Code:
tar -zxvf apktool.tar.gz
- cd to apktool folder
Code:
cd apktool
- Root permissions
Code:
sudo chown -R [COLOR="red"][B]yourusername[/B][/COLOR] aapt apktool apktool.jar
enricod[/COLOR @EnricoD-Aspire-5920G:~/Scrivania/apktool$
- Make them exec
Code:
sudo chmod +x aapt apktool apktool.jar
- Move to usr/local/bin
Code:
sudo cp aapt apktool apktool.jar /usr/local/bin
To see if it works just run
Code:
apktool
in a terminal. The output will look like this:
[email protected]:~/Scrivania/apktool$ apktool
Apktool v1.5.2 - a tool for reengineering Android apk files
Copyright 2010 Ryszard Wiśniewski <[email protected]>
with smali v1.4.1, and baksmali v1.4.1
Updated by @iBotPeaches <[email protected]>
Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0)
... bla bli blu bla bli bli blu bla bla cit. Jake
Click to expand...
Click to collapse
- You can now delete the package and the extracted folder
- Little guide on how to use apktool
http://forum.xda-developers.com/showpost.php?p=50181967&postcount=57
Import CM11 Template in Eclipse
IMPORT THE CYANOGENMOD TEMPLATE
1) FIRST! We open a logcat console! xD
In Eclipse navigate to
Window --> Show View --> Other... --> Android --> Logcat --> OK!
2) Download the Official Template from here and extract it where You want:
https://github.com/CyanogenMod/android_packages_themes_Template
3) Open Eclipse
File--> Import --> Android --> Existing Android Code Into Workspace
and select the root folder where the project is located, change its name, tickmark "Copy projects into workspace" and click Finish
DONE!
4) The first thing we'll do is to change the package name in AndroidManifest.xml.
- We're going to edit and add the following lines:
Code:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="[COLOR="Red"][B]com.your.theme.template[/B][/COLOR]">
<!-- Add build version number, #=number -->
[COLOR="SeaGreen"] [B]android:versionCode="#"
android:versionName="#" >[/B][/COLOR]
<!-- To avoid compatibility & permissions problems -->
[COLOR="SeaGreen"][B]<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="19" />[/B][/COLOR]
<!-- Add this and your theme won't ask for strange permissions -->
[COLOR="SeaGreen"][B]<uses-permission android:name="android.permission.SET_WALLPAPER" />[/B][/COLOR]
<uses-feature android:required="true" android:name="org.cyanogenmod.theme" />
<application android:hasCode="false" android:icon="@drawable/ic_launcher" android:label="[COLOR="red"][B]Theme name[/B][/COLOR]">
</application>
<meta-data android:name="org.cyanogenmod.theme.name" android:value="[B][COLOR="red"]Theme name[/COLOR][/B]"/>
<meta-data android:name="org.cyanogenmod.theme.author" android:value="[COLOR="red"][B]Your name[/B][/COLOR]" />
</manifest>
NOTE: Do not add comments (<!-- blablabla -->)
- Navigate to
Project and
1. Clean (build only the selected projects) (disable also "build automatically")
2. Build project
As Youu can see gen files got updated
5) Run and try the theme!
Connect Your device and grant ADB access, then Select Your project and just press ctrl+f11or or Navigate to Run -->Run and select Your device
6) Export a Signed APK for the Google Play Store
- Right-Click on Your project and navigate to
Android Tools --> Export a signed application package
We select Create new keystore, save keystore where You want and add a password. When finished click next.
- In next screen
We add:
Alias
password
validity (from 1 to 1000 years)
First and lastname
Click to expand...
Click to collapse
- Now choose a destination and a name for Your signed apk.
and click Finish
7) Oh s****! an Error during compilation process !!!!
1 - Open the LOGCAT console!
and search for the error!!
Fix it!!!!
F.A.Q.:
1 - " OMG that desktop wallpapers are awesome, can You share?? pls pls pls pls :fingers-crossed: "
Sure!
https://dribbble.com/shots/1355879-Meteor-Wallpaper
http://images8.alphacoders.com/393/393340.jpg
2 - "d***q!, dat theme/icons are too awesome "
I'm simply running Lubuntu + Numix candies:
sudo add-apt-repository ppa:numix/ppa
sudo apt-get update
sudo apt-get install numix-gtk-theme numix-icon-theme-circle
Click to expand...
Click to collapse
and my personal menu icon
https://www.dropbox.com/s/u0lo7zqn7f95q3o/Senza nome.png
Credits (listed randomly):
- @hoppermi (support)
- @CyanogenMod
- @blinqipa for Android studio thread
- @ivn888
- Cristian Giordano for Theme Debugger App
- @google (Eclipse ADT, SDK)
- @eclipse (Eclipse IDE)
- @iBotPeaches for apktool
- @iamareebjamal
- Ivan Botty
NOTE:
Please, don't use this guide to develop another Android L Theme! :silly::silly::silly:
Great places to start:
the Cyanogenmod Theme Template Github
Here you can find a detailed explanation of a CM11 Theme structure
https://github.com/CyanogenMod/android_packages_themes_Template
the Cyanogenmod Theme engine Google+ community
where You'll find lot of helpful people!
https://plus.google.com/communities/102878569352950531397
[GUIDE]Ultimate Guide to NinePatch PNG Files (9 PNG Discussion) by @iamareebjamal
http://forum.xda-developers.com/showthread.php?t=2326393
[CM11 Theme Manager] Tutorial (Android Studio) for theming beginners by @blinqipa
http://forum.xda-developers.com/showthread.php?t=2780923
Android Studio - Video Lessons by Ivan Botty
https://www.youtube.com/playlist?list=PLWB0Mwz_HN2QRJ0BVyKs3oQybdy7Qa399
Complete Your KitKat look (Holo light + CM KK UI) 33b5e5 genocide
A detailed (and featured) guide where I'll show You how to carefully change the look of Your android build from Holo Blue light to KitKat White
http://forum.xda-developers.com/showthread.php?t=2634743
Theme Debugger App
An app to test Your themed resources! by Giordano Cristian (the creator of Atomic Awesome Green theme)
https://play.google.com/store/apps/details?id=com.steel89ita.themedebugger
A collection of Stock Resources from CM and main Roms (PA and AOKP) that You can theme, by @22sl22
http://forum.xda-developers.com/showpost.php?p=53439701&postcount=38
Basic Theming w Screenshots
FRAMEWORK
SYSTEMUI
SETTINGS
KEYGUARD
Reserved
An Example: The Dialer
Github is Your Friend!
- Let's open Cyanogenmod Github and search for " Dialer ":
https://github.com/CyanogenMod/android_packages_apps_Dialer
- Navigate to Res --> Values --> Colors.xml
As You can see all values are commented/explained!!
- So, let's look at the Dialer from JellyRevenge theme
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
[COLOR="RoyalBlue"][B]<!-- 3 Color of dialpad digits 3 --> [/B][/COLOR]
<color name="dialpad_digits_text_color">#939393</color>
[COLOR="RoyalBlue"][B]<!-- 1 Background color of action bars. It's linked with dialpad digits colors!!!! Ensure this stays in sync with packages/Telephony actionbar_background_color. 1 -->[/B][/COLOR]
<color name="actionbar_background_color">#33b5e5</color>
[COLOR="RoyalBlue"][B]<!-- Primary color of dialpad text, including the call button -->[/B][/COLOR]
<color name="dialpad_primary_text_color">#33b5e5</color>
[COLOR="RoyalBlue"][B] <!-- Secondary color of dialpad text (used for the letters corresponding to each digit -->[/B][/COLOR]
<color name="dialpad_secondary_text_color">#8b8b8b</color>
[COLOR="RoyalBlue"][B]<!-- 4 Background color of dialpad 4 -->[/B][/COLOR]
<color name="background_dialpad">#000000</color>
[COLOR="RoyalBlue"][B]<!-- 2 Pressed color of dialpad buttons 2 -->[/B][/COLOR]
<color name="background_dialpad_pressed">#88939393</color>
</resources>
Obviously, You don't need to add these comments
UI repositories:
. Settings: https://github.com/CyanogenMod/android_packages_apps_Settings
. framework-res: https://github.com/CyanogenMod/android_frameworks_base/tree/cm-11.0/core
. "Oh s****, I can't find SystemUI, Keyguard ... etc ": You can find these UI repos inside the framework_base under "packages"
https://github.com/CyanogenMod/android_frameworks_base/tree/cm-11.0/packages
NOTE: Not all packages are commented! But all elements inside XMLs have evocative names! don't worry about that, I will show You how to make a basic theme!
Other Examples - Basic theming through XMLs
FRAMEWORK
THE THEME MAIN COLOR
When You design a new theme You will choose a default color for the theme. So, if We want to set up it overally we can simply tweak holo_blue_light value in framework so most of the elements will result themed (dialogs text, dividers etc etc)
assets/overlays/android/res/values/colors.xml
Code:
<!-- A light Holo shade of blue -->
<color name="holo_blue_light">#ff33b5e5</color>
<!-- A dark Holo shade of blue -->
<color name="holo_blue_dark">#ff0099cc</color>
<!-- A really bright Holo shade of blue -->
<color name="holo_blue_bright">#ff00ddff</color>
THE FRAMEWORK BACKGROUND FOR DARK/LIGHT LAYOUTS
Just place two images inside
assets/overlays/android/res/drawable-nodpi
https://raw.githubusercontent.com/e...d/res/drawable-nodpi/background_holo_dark.png
https://raw.githubusercontent.com/e.../res/drawable-nodpi/background_holo_light.png
DIALOG UPPER TEXT
assets/overlays/android/res/values/styles.xml
- Dialog light
Code:
<style name="TextAppearance.Holo.Light.DialogWindowTitle" parent="@*android:style/TextAppearance.Holo.Light">
<item name="android:textSize">22.0sp</item>
<item name="android:textColor">#ff[COLOR="Lime"][B]00ff00[/B][/COLOR]</item>
</style>
- Dialog dark
Code:
<style name="TextAppearance.Holo.DialogWindowTitle" parent="@*android:style/TextAppearance.Holo">
<item name="android:textSize">22.0sp</item>
<item name="android:textColor">#ff[COLOR="Magenta"][B]9f79ee[/B][/COLOR]</item>
</style>
NOTIFICATION TEMPLATE ICON BACKGROUND
assets/overlays/android/res/values/drawables.xml
Code:
<item type="drawable" name="notification_template_icon_bg">#3333B5E5</item>
ON TEXT COLOR
assets/overlays/android/res/values/styles.xml
Code:
<style name="Widget.CompoundButton.Switch" parent="@android:style/Widget.CompoundButton">
<item name="android:textOn"/>
<item name="android:textOff"/>
</style>
<style name="TextAppearance.Holo.Widget.Switch" parent="@android:style/TextAppearance.Holo.Small">
<item name="android:textColor">#ffffff</item>
</style>
note: You can also remove the text, just add trasparency:
Code:
<style name="Widget.CompoundButton.Switch" parent="@android:style/Widget.CompoundButton">
<item name="android:textOn"/>
<item name="android:textOff"/>
</style>
[COLOR="red"][B] <style name="TextAppearance.Holo.Widget.Switch" parent="@android:style/TextAppearance.Holo.Small">
<item name="android:textColor">#00000000</item>
</style>[/B][/COLOR]
SYSTEMUI
STATUS BAR BATTERY COLOR
assets/overlays/com.android.systemui/res/values/colors.xml
Code:
<color name="batterymeter_frame_color">#6633b5e5</color>
<color name="batterymeter_full">#ff33b5e5</color>
<color name="batterymeter_charge_color">#ff33b5e5</color>
STATUS BAR CLOCK COLOR
assets/overlays/com.android.systemui/res/values/colors.xml
Code:
<color name="status_bar_clock_color">#ff33b5e5</color>
NO RECENTS TEXT
assets/overlays/com.android.systemui/res/values/colors.xml
Code:
<color name="no_recent_apps">#80[COLOR="YellowGreen"][B]99cc00[/B][/COLOR]</color>
QS TILES BACKGROUND
1 = the background
2= background when pressed
Put an xml inside drawable folder:
assets/overlays/com.android.systemui/res/drawable/qs_tile_background.xml
with the following contents:
Code:
<?xml version="1.0" encoding="utf-8"?>
<selector
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:state_pressed="true">
[COLOR="Red"][B]<color android:color="#4033b5e5" />[/B][/COLOR]
</item>
<item>
[COLOR="Lime"][B]<color android:color="#00000000" />[/B][/COLOR]
</item>
</selector>
Reserved
Decompiled Resources for most densities
I case you don't know what this is or what I do here, these are decompiled resources for all the themers out there. So say you have limited internet (Only 30-40mb per file) or just don't have the time to trawl though dozens of apks, this is for you. I have decompiled 'core' apps for PA, CM and AOKP.
Core Apps are:
System-App:
DeskClock
Email
System-Priv App:
Contacts
Framework
Keyguard
Settings
SystemUI
Things included in Phone devices:
IncallUI
Dialer
MMS
If you want other apps, let me know and I will add them in a separate package :good:
I have done it for the following densities, I tried to be as broad as possible but if you want more densities/devices added, let me know :good:
XXHDPI- Hammerhead/Nexus 5
XHDPI- Mako/naxus 4
HDPI- I9100/Galaxy S2
Tablet-
Flo/Nexus 7 2013
Grouper/Nexus 7 2012
Download:
Now how I have structured it is one main folder that contains all the sub device folders with all the files you need inside compressed zips (decompiled of course ):
http://www.androidfilehost.com/?w=files&flid=17577
Enjoy and if I made any errors, let me know ASAP
If you want anything added, let me know.
Press the thanks button if you like my work :good:
My Free CM11 Themes:
AOKP Theme: https://play.google.com/store/apps/details?id=com.aokp.theme.swaggers
CHOCOUI (XDA Colors): https://play.google.com/store/apps/details?id=com.xda.theme.cyanogenmod&hl=it
JELLYREVENGE: https://play.google.com/store/apps/details?id=com.jelly.theme.revenge&hl=it
LOLLIDARK: https://play.google.com/store/apps/details?id=com.lolli.dark.enricod
AOKP SOURCES
https://github.com/enricodortenzio/packages_themes_AOKPtheme
LOLLIDARK SOURCES
https://github.com/enricodortenzio/lollidark
CHOCOUI SOURCES
https://github.com/enricocid/ChocoUI---XDA-Colors
JELLYREVENGE SOURCES
https://github.com/enricocid/JellyRevenge-CM11-theme
APKs Installer Sources (Read the readme carefully!)
https://github.com/enricocid/APKs-Installer
I also run Lubuntu?
---------- Post added at 03:27 PM ---------- Previous post was at 03:27 PM ----------
LuqmaanMathee said:
I also run Lubuntu?
Click to expand...
Click to collapse
And great guide.
Awesome guide, damn you reserved a lot of posts
If you need an updated version of the resources, let me know. I remember we were talking LDPI and some other resolutions in the other thread, let me know if you want those. They could probably do with an update any way :good: :good:
22sl22 said:
Awesome guide, damn you reserved a lot of posts
If you need an updated version of the resources, let me know. I remember we were talking LDPI and some other resolutions in the other thread, let me know if you want those. They could probably do with an update any way :good: :good:
Click to expand...
Click to collapse
I can reserve one of these threads.to You , You will post resources if You want
EnricoD said:
I can reserve one of these threads.to You , You will post resources if You want
Click to expand...
Click to collapse
Ok I'll download some more roms and post updated resources then
Sent from my Nexus 4 using Tapatalk
22sl22 said:
Ok I'll download some more roms and post updated resources then
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I asked moderator to reserve You the post #4
You will be able to edit asap
added some visual instructions
will add more next days, don't worry
i will also add tips to theme things by xml
e.g the dialer, the dialogs ... etc etc... and i will show You also how you can use github to know what to theme
commented cmlol will be update to the github
Subscribed! I will assist when I can answering questions.
Sent from my Nexus 5 using Tapatalk
Now preparing my setup. Hopefully something will succeed out of this.
Congratulations for your comprehensive tutorial.
Excellent tutorial, looking forward for more resources and tips. I don't have code experience on Android but I will definitively try to make a few themes for myself and then release them if everything works at the end
Why not add an Android Studio guide aswell? I believe it's far easier to set up and start building CM Themes, plus, users have the ability to use flavors. I can help you with that.
Koulis2000 said:
Why not add an Android Studio guide aswell? I believe it's far easier to set up and start building CM Themes, plus, users have the ability to use flavors. I can help you with that.
Click to expand...
Click to collapse
If You want I'll give You a post You're welcome