[DEV + HOWTO] KangXperiaProject - AOKP for Xperia (tutorial to compile from source)

justmpm · Jul 13, 2012

championswimmer said:
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

Thanks....alot!!! Having to restart from scratch really sucks! I figured since it was a sync that I could restart, but the repo sync threads I found in
cyanogenmod said to delete and restart.....

Tenacious · Jul 13, 2012

Thanks for the guide everything goes fine but when I tray to build I heave a lot of errors so can't build it I'm missing some dependent files for building cud you help out what packages I need to get to build successfully.

I'm on Ubuntu 12.04 x64 and I'm building hallon.

Sent from my Xperia Neo using Tapatalk 2

championswimmer · Jul 13, 2012

Tenacius D said:
Thanks for the guide everything goes fine but when I tray to build I heave a lot of errors so can't build it I'm missing some dependent files for building cud you help out what packages I need to get to build successfully.

I'm on Ubuntu 12.04 x64 and I'm building hallon.

Sent from my Xperia Neo using Tapatalk 2

could you post a terminal output of the errors you are facing ???

szl.kiev · Jul 13, 2012

justmpm said:
Thanks....alot!!! Having to restart from scratch really sucks! I figured since it was a sync that I could restart, but the repo sync threads I found in
cyanogenmod said to delete and restart.....

When you do a repo sync and downloading projects, a compressed tmp file is stored inside your working dir for each project (around 200 projects for ics, 300 for jb)
They are inside .repo/projects/ folder (its a hidden folder, ctrl-h for view hidden files/folder under linux)
once each completely downloaded, it'll deflated and deleted,
if you sync from google's server (aosp) and failed, just re-sync again and it'll resume those tmp files.
But if they are from github site, when failed and re-sync, it'll create a new tmp file (different method and different file extention with aosp). Just imagine if your failed tmp files are over 500mb and will grow every time it failed, that would be a wasted hdd space.
I usually delete those failed tmp files after everything is 100% synced, by search "tmp" under .repo folder

[edit]
By default it sync with -j4 , it's stated in the manifest. If you have fast internet connection, you can increase it like 8 or 16, but if yours is slow that would give you more download errors, stick with j4 or less.
Mostly I use "repo sync j1" or j2 when it comes to the big project ones like framework/base or prebuilt

Sent from my ST18i using xda app-developers app

Tenacious · Jul 13, 2012

championswimmer said:
could you post a terminal output of the errors you are facing ???

That error was because of my stupidity sorry for that
But now im heaving real error right now i was about thee hours in to building and then this pops out

Code:

Finding NOTICE files: out/target/product/hallon/obj/NOTICE_FILES/hash-timestamp
Combining NOTICE files: out/target/product/hallon/obj/NOTICE.html
Installed file list: out/target/product/hallon/installed-files.txt
Target system fs image: out/target/product/hallon/obj/PACKAGING/systemimage_intermediates/system.img
Install system fs image: out/target/product/hallon/system.img
Package target files: out/target/product/hallon/obj/PACKAGING/target_files_intermediates/aokp_hallon-target_files-eng.tenacious.zip
Package OTA: out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip
device/semc/msm7x30-common/releasetools/semc_ota_from_target_files -v \
	   -p out/host/linux-x86 \
	   -k build/target/product/security/testkey \
	   --no_assert=false \
	   --backup=true \
	   --override_device=MT15i,MT15a,hallon \
	   out/target/product/hallon/obj/PACKAGING/target_files_intermediates/aokp_hallon-target_files-eng.tenacious.zip out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip

Given a target-files zipfile, produces an OTA package that installs
that build.  An incremental OTA is produced if -i is given, otherwise
a full OTA is produced.

Usage:  ota_from_target_files [flags] input_target_files output_ota_package

  -b  (--board_config)  <file>
      Deprecated.

  -k (--package_key) <key> Key to use to sign the package (default is
      the value of default_system_dev_certificate from the input
      target-files's META/misc_info.txt, or
      "build/target/product/security/testkey" if that value is not
      specified).

      For incremental OTAs, the default value is based on the source
      target-file, not the target build.

  -i  (--incremental_from)  <file>
      Generate an incremental OTA using the given target-files zip as
      the starting build.

  -w  (--wipe_user_data)
      Generate an OTA package that will wipe the user data partition
      when installed.

  -n  (--no_prereq)
      Omit the timestamp prereq check normally included at the top of
      the build scripts (used for developer OTA packages which
      legitimately need to go back and forth).

  -e  (--extra_script)  <file>
      Insert the contents of file at the end of the update script.

  -a  (--aslr_mode)  <on|off>
      Specify whether to turn on ASLR for the package (on by default).

  --backup <boolean>
      Enable or disable the execution of backuptool.sh.
      Disabled by default.

  --override_device <device>
      Override device-specific asserts. Can be a comma-separated list.

  -p  (--path)  <dir>
      Prepend <dir>/bin to the list of places to search for binaries
      run by this script, and expect to find jars in <dir>/framework.

  -s  (--device_specific) <file>
      Path to the python module containing device-specific
      releasetools code.

  -x  (--extra)  <key=value>
      Add a key/value pair to the 'extras' dict, which device-specific
      extension code may look at.

  -v  (--verbose)
      Show command lines being executed.

  -h  (--help)
      Display this usage message and exit.

** option --no_assert not recognized **
make: *** [out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip] Error 2

Tenacious · Jul 14, 2012

Any one knows at what i need to look for above error.

Thanks in advance.

championswimmer · Jul 14, 2012

Tenacius D said:
Any one knows at what i need to look for above error.

Thanks in advance.

you have all but done it

even we face these errors.. not a bad thing really.. this was too low in our priorities to fix ... lol there is a simple workaround

Code:

device/semc/msm7x30-common/releasetools/semc_ota_from_target_files -v \
	   -p out/host/linux-x86 \
	   -k build/target/product/security/testkey \
           --backup=true \
	   --override_device=MT15i,MT15a,hallon \
	   out/target/product/hallon/obj/PACKAGING/target_files_intermediates/aokp_hallon-target_files-eng.tenacious.zip out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip

pass on that command to terminal just right after your build stops
you'll find your otapackage in out directory then

just the script that creates the zip is not fixed.. you have in fact completed your build you only got stuck at packaging

Tenacious · Jul 14, 2012

]

championswimmer said:
you have all but done it

even we face these errors.. not a bad thing really.. this was too low in our priorities to fix ... lol there is a simple workaround

Code:

device/semc/msm7x30-common/releasetools/semc_ota_from_target_files -v \ -p out/host/linux-x86 \ -k build/target/product/security/testkey \ --backup=true \ --override_device=MT15i,MT15a,hallon \ out/target/product/hallon/obj/PACKAGING/target_files_intermediates/aokp_hallon-target_files-eng.tenacious.zip out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip

pass on that command to terminal just right after your build stops
you'll find your otapackage in out directory then
just the script that creates the zip is not fixed.. you have in fact completed your build you only got stuck at packaging

Thanks that did the trick also thanks for the guide.

Code:

out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip
done.

kormatoes · Jul 14, 2012

Tenacius D said:
]

Thanks that did the trick also thanks for the guide.

Code:

out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip done.

Win bro win

Sent from my Xperia neo using XDA Premium HD app

szl.kiev · Jul 16, 2012

Tenacius D said:

That error was because of my stupidity sorry for that
But now im heaving real error right now i was about thee hours in to building and then this pops out

Code:

Finding NOTICE files: out/target/product/hallon/obj/NOTICE_FILES/hash-timestamp
Combining NOTICE files: out/target/product/hallon/obj/NOTICE.html
Installed file list: out/target/product/hallon/installed-files.txt
Target system fs image: out/target/product/hallon/obj/PACKAGING/systemimage_intermediates/system.img
Install system fs image: out/target/product/hallon/system.img
Package target files: out/target/product/hallon/obj/PACKAGING/target_files_intermediates/aokp_hallon-target_files-eng.tenacious.zip
Package OTA: out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip
device/semc/msm7x30-common/releasetools/semc_ota_from_target_files -v \
	   -p out/host/linux-x86 \
	   -k build/target/product/security/testkey \
	   --no_assert=false \
	   --backup=true \
	   --override_device=MT15i,MT15a,hallon \
	   out/target/product/hallon/obj/PACKAGING/target_files_intermediates/aokp_hallon-target_files-eng.tenacious.zip out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip

Given a target-files zipfile, produces an OTA package that installs
that build.  An incremental OTA is produced if -i is given, otherwise
a full OTA is produced.

Usage:  ota_from_target_files [flags] input_target_files output_ota_package

  -b  (--board_config)  <file>
      Deprecated.

  -k (--package_key) <key> Key to use to sign the package (default is
      the value of default_system_dev_certificate from the input
      target-files's META/misc_info.txt, or
      "build/target/product/security/testkey" if that value is not
      specified).

      For incremental OTAs, the default value is based on the source
      target-file, not the target build.

  -i  (--incremental_from)  <file>
      Generate an incremental OTA using the given target-files zip as
      the starting build.

  -w  (--wipe_user_data)
      Generate an OTA package that will wipe the user data partition
      when installed.

  -n  (--no_prereq)
      Omit the timestamp prereq check normally included at the top of
      the build scripts (used for developer OTA packages which
      legitimately need to go back and forth).

  -e  (--extra_script)  <file>
      Insert the contents of file at the end of the update script.

  -a  (--aslr_mode)  <on|off>
      Specify whether to turn on ASLR for the package (on by default).

  --backup <boolean>
      Enable or disable the execution of backuptool.sh.
      Disabled by default.

  --override_device <device>
      Override device-specific asserts. Can be a comma-separated list.

  -p  (--path)  <dir>
      Prepend <dir>/bin to the list of places to search for binaries
      run by this script, and expect to find jars in <dir>/framework.

  -s  (--device_specific) <file>
      Path to the python module containing device-specific
      releasetools code.

  -x  (--extra)  <key=value>
      Add a key/value pair to the 'extras' dict, which device-specific
      extension code may look at.

  -v  (--verbose)
      Show command lines being executed.

  -h  (--help)
      Display this usage message and exit.

** option --no_assert not recognized **
make: *** [out/target/product/hallon/aokp_hallon-ota-eng.tenacious.zip] Error 2

to make it permanent fix, just comment
# --no_assert=false \

it's in /build/core/MakeFile at line around 1200

championswimmer · Jul 16, 2012

szl.kiev said:
to make it permanent fix, just comment
# --no_assert=false \

it's in /build/core/MakeFile at line around 1200

i though prefer this sort of a fix

just have to do it on msm7x30 too, didn't have time for it

https://github.com/KangXperiaProjec...mmit/48b600885f97e42bfed70f06856997612e3199c3

n1kolaa · Jul 16, 2012

dasdasda
moderator plz delate it

justmpm · Jul 16, 2012

I have a build for Urushi...it is hopelessly small: 107 Mb vs 190 for ChampionSwimmers M6 build...and no surprise, it didn't boot. I have done a quick sweep of what is in my build and some of the smallness is due to /app (not worried about this), there are a lot of files that have different
sizes between the two builds, but I found one that is wee little in my build and big in the "official" M6 build: /system/etc/security/cacerts....

I will try the build again....any suggestions, hints, tricks?????

championswimmer · Jul 16, 2012

justmpm said:
I have a build for Urushi...it is hopelessly small: 107 Mb vs 190 for ChampionSwimmers M6 build...and no surprise, it didn't boot. I have done a quick sweep of what is in my build and some of the smallness is due to /app (not worried about this), there are a lot of files that have different
sizes between the two builds, but I found one that is wee little in my build and big in the "official" M6 build: /system/etc/security/cacerts....

I will try the build again....any suggestions, hints, tricks?????

run the make command like this

mka -j4 otapackage 1>./build.log 2>./error.log

when building is finished, send me the error.log file (it should be present on the root of the directory where you are building)

EDIT :
there was problem in makefiles
just sync your repo again and try again

Tenacious · Jul 16, 2012

Same thing for my hallon build size is 102mbps and I just took a look my system folder and lot of files are missing in android system apps libs

championswimmer · Jul 16, 2012

Tenacius D said:
Same thing for my hallon build size is 102mbps and I just took a look my system folder and lot of files are missing in android system apps libs

fixed it

sync repo and build again

Tenacious · Jul 16, 2012

championswimmer said:
fixed it

sync repo and build again

Thank man I'm rebuilding and I can see that missing files are getting build now

Also I forgot to mention in build.prop it says ray while I'm building neo (hallon)

championswimmer · Jul 16, 2012

Tenacius D said:
Thank man I'm rebuilding and I can see that missing files are getting build now

Also I forgot to mention in build.prop it says ray while I'm building neo (hallon)

see the file
vendor/kxp/products/hallon.mk

change ray to neo

festa20 · Jul 16, 2012

Syncing work tree: 91% (257/282) fatal: Unable to create '/home/festa/android/kxp/sdk/.git/index.lock': File exists.

If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.
Syncing work tree: 100% (282/282), done.

bootable/recovery/: discarding 13 commits
error: sdk/: platform/sdk checkout 7f1c3fd5754369ed32d34a9466594093c15927db
festa@ubuntu:~/android/kxp$

whats this all about plus getting errors while compiling

championswimmer · Jul 16, 2012

festa20 said:
Syncing work tree: 91% (257/282) fatal: Unable to create '/home/festa/android/kxp/sdk/.git/index.lock': File exists.

If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.
Syncing work tree: 100% (282/282), done.

bootable/recovery/: discarding 13 commits
error: sdk/: platform/sdk checkout 7f1c3fd5754369ed32d34a9466594093c15927db
festa@ubuntu:~/android/kxp$

whats this all about plus getting errors while compiling

Code:

$ rm -f -r /home/festa/android/kxp/sdk/.git/index.lock

[DEV + HOWTO] KangXperiaProject - AOKP for Xperia (tutorial to compile from source)

Which phone you own

Arc / Arc S

Neo / Neo V

Ray

Mini / MiniPro

Active

Live with WALKMAN

X10

X10 Mini / MiniPro

X8

Retired Senior Moderator

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Inactive Recognized Developer

Retired Senior Moderator

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Similar threads

Top Liked Posts