FORUMS
Remove All Ads from XDA

[Question] post #4: Include Stk.apk in full_passion_eng make...

1,359 posts
Thanks Meter: 207
 
By lpasq, Senior Member on 13th July 2010, 05:40 AM
Post Reply Email Thread
question #1 regarding if "make -jx otapackage" update.zip flashes new recovery over custom recovery...

when building froyo from aosp for passion, i have been taking the out/target/product/passion boot.img and system.img and using dsixda kitchen to output a flashable update.zip... no issues. i just started also ending the compile with "make -jx otapackage". pulling apart the .zip i see there is a "recovery" file folder. does this flash a new recovery that would replace any custom recovery already on device???

thanks to anyone willing to throw me an answer.
 
 
13th July 2010, 11:47 AM |#2  
gnarlyc's Avatar
Retired Recognized Developer
Flag Raleigh, NC
Thanks Meter: 57
 
More
Quote:
Originally Posted by lpasq

when building froyo from aosp for passion, i have been taking the out/target/product/passion boot.img and system.img and using dsixda kitchen to output a flashable update.zip... no issues. i just started also ending the compile with "make -jx otapackage". pulling apart the .zip i see there is a "recovery" file folder. does this flash a new recovery that would replace any custom recovery already one device???

thanks to anyone willing to throw me an answer.

It's my understanding that as long as there's nothing in the update-script that will flash the recovery image, then you are ok. I've encountered this once, and I just deleted the recovery folder and anything in the update-script. (And then zipped and resigned the ROM.) When I flashed the ROM, there was no recovery image flashed. Just double-check everything.
13th July 2010, 02:38 PM |#3  
lpasq's Avatar
OP Senior Member
Flag SoCal
Thanks Meter: 207
 
More
Quote:
Originally Posted by gnarlyc

It's my understanding that as long as there's nothing in the update-script that will flash the recovery image, then you are ok. I've encountered this once, and I just deleted the recovery folder and anything in the update-script. (And then zipped and resigned the ROM.) When I flashed the ROM, there was no recovery image flashed. Just double-check everything.

Understood and appreciated.

Sent from my Nexus One using XDA App
13th July 2010, 07:51 PM |#4  
lpasq's Avatar
OP Senior Member
Flag SoCal
Thanks Meter: 207
 
More
[Question] Including Stk.apk in full_passion_eng make...
When I lunch full_passion_eng, the Stk.apk is not included in my compiled build. How do I add it for inclusion in the build?

My build.sh is as follows:

PHP Code:
#!/bin/bash

#clean out prior compiled files
make installclean
make clean

#update AOSP froyo source files
repo init -u git://android.git.kernel.org/platform/manifest.git -b froyo
cd ~
repo sync

#setup compiling environment and build
cd ~
build/envsetup.sh
lunch

#USB connect N1 and initiate ADB
cd ~
adb devices

#ADB pull needed device files
cd ~
cd device
cd htc
cd passion
./extract-files.sh

#build the Passion *.img's
cd ~
make -j3

#view compiled folder's new boot.img/system.img/userdata.img
cd ~
cd out
cd target
cd product
cd passion
echo 'see flashable files:'
ls *.img

#create update.zip
cd ~
make -j3 otapackage 
This is the Android.mk in /packages/apps/Stk. Am I to modify this or am I really off?

PHP Code:
# Copyright 2007-2008 The Android Open Source Project

LOCAL_PATH:= $(call my-dir)
include $(
CLEAR_VARS)

LOCAL_MODULE_TAGS := optional

LOCAL_SRC_FILES 
:= $(call all-subdir-java-files)

LOCAL_PACKAGE_NAME := Stk
LOCAL_CERTIFICATE 
:= platform

include $(BUILD_PACKAGE
Thank you.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes