Building an application against an SDK compiled from source

2,633 views
Skip to first unread message

Ron M

unread,
Feb 6, 2012, 2:45:09 AM2/6/12
to android-platform
Hi All,

I am trying to make a simple change in
frameworks/base/core/java/android/view/ViewRootImpl.java , which
adds a minor API change to class ViewRootImpl.
On the platform side - everything works great, and I can see the
changes I added, such as some logs to the LogCat.

However - I can't build an application with eclipse against this platform.
I tried a couple of methods:

(1) Including .class and .jar files from the AOSP build directory
out/target/common/obj/JAVA_LIBRARIES
I removed the default Android.jar, and then I tried about every
possible combination.
Just using the framework_intermediates .class files made my platform
changes visible from the eclipse app - however, it did not find
trivial Java includes - and no matter what I tried to do -
eclipse would crash on some GC stuff, and never build the APK
(although extremely high on all VM params)

This may be the way to go - but I'm not sure which .class/jar files I
should include at the first place. Could anyone please give an hand?
I don't mind ant building and avoiding eclipse - but I would have to
need the required jar/classes in advance.


(2) Buildiing SDK from AOSP source
lunch sdk-eng && make sdk

The sdk build succeeded.
I got an output zip file at
out/host/linux-x86/sdk/android-sdk_eng.ronubo_linux-x86.zip - which
I copied to another directory and extracted.
Now, I found the "Android.jar" file of this extracted archive, and
tried to "add external jar" to a simple eclipse project I made,
and the eclipse project could not import "android.view.ViewRootImpl".

The prebuilt arm emulator for the SDK I created works well - with my changes.

How can it be that the SDK is "missing"? Should I have included
anything other than "Android.jar" as an external jar?

I appreciate your help.
Thanks,
Ron

David Herges

unread,
Feb 6, 2012, 8:31:33 AM2/6/12
to android-...@googlegroups.com
see here: https://groups.google.com/d/msg/android-platform/ZCc6OfhNhNk/R8USGGDoYq0J

Ron M

unread,
Feb 6, 2012, 10:41:46 AM2/6/12
to android-platform
David,
I read the thread. However, it seems that "update-api" is no longer
neccesary (not sure about it) - I remember that when I
played around with gingerbread, an API modification would break the
build unless make update-api is called.

Anyway, I am linking the application with what I need with the method
that you suggested (which is method (2) in my original message) - but
I cannot
import "android.view.ViewRootImpl" and I don't understand why.

BTW - as for your method - it is not that trivial - because using an
SDK from the current AOSP - requires building the ADT, as the latest
released ADT version is 16, and current (4.03) AOSP SDK requires at
least v17, which can only be achieved by building the adt tools
( tools.android.com/ ).

I still need help on this one, unfortunately.

On Feb 6, 3:31 pm, David Herges <david.her...@googlemail.com> wrote:
> see
> here:https://groups.google.com/d/msg/android-platform/ZCc6OfhNhNk/R8USGGDo...

David Herges

unread,
Feb 6, 2012, 11:57:47 AM2/6/12
to android-...@googlegroups.com
Is the class annotated with '{@hidden}'? If so, the class is excluded from the API stubs (i.e. the .jar file that applications get linked against by the compiler).

An altogether different question is whether you actually need/want to modify the public API. The part of the framework you changed, is it public so that applications do call directly into that class/method?

Ron M

unread,
Feb 8, 2012, 8:05:05 AM2/8/12
to android-...@googlegroups.com
Yes David, the class was indeed annotated with "hidden". Your answer
was very helpful - I figured it out a couple of days ago and missed
the email.

I do want to modify the public API, OR - have the platform class
loader being aware of "Userspace" classes.

I will share what I want to accomplish, and you might be able to help
me on this one:

That is, I would like to be able to dynamically load/replace a class
which is packed as part of an APK, by using the Java dynamic loader. I
managed to do so from the application itself using
"class.Forname("com.mypackage.example" - and I guess that I could
somehow make it work, on a platform level by adding
"com.mypackage.example" to the some prebuilt loaded classes path.
This way, I would be able to extend platform functionality - without
having to rebuild it all the time (TONS of time - and impossible to
achieve by just replacing framework.jar /framework.odex AFAIK, because
it will break all ODEX dependencies everywhere, so I have to rebuild
all the platform for every single change I make - unless I manage to
build everything de-odexed - which I have no idea how to do (any idea
on this one also?)

I am sorry for deviating from the original topic, but any help will be
appreciated.

Ron

> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-platform/-/uOnYkpNu4J8J.
>
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platfo...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=en.

David Herges

unread,
Feb 9, 2012, 7:28:05 AM2/9/12
to android-...@googlegroups.com
Hi, here's what I think:


On Wednesday, 8 February 2012 14:05:05 UTC+1, Ron M wrote:
Yes David, the class was indeed annotated with "hidden". Your answer
was very helpful

thanks, man!
 


That is, I would like to be able to dynamically load/replace a class
which is packed as part of an APK, by using the Java dynamic loader.

 Don't know the details of Java class loaders and how it is used in Android.

 
 

This way, I would be able to extend platform functionality - without
having to rebuild it all the time (TONS of time - and impossible to
achieve by just replacing framework.jar /framework.odex AFAIK, because
it will break all ODEX dependencies everywhere, so I have to rebuild
all the platform for every single change I make -

You can use the single-shot make files (Android.mk included in the different projects) by using the 'mmm' command, examples:

To build framework.jar
mmm frameworks/base

To build services.jar
mmm frameworks/base/services/java

To build core.jar
mmm libcore

To assemble the emulator .img
make framework
make snod

snod stands for "system-image no dependencies". I commonly have to run 'make framework' before 'make snod' to get a working image, don't know the reason for it though. And the emulator shouldn't be running while building (since it has the .img file locked on my computer's filesystem).

If you don't want to quit the emulator, you can use adb to flash the image to the emulator. So instead of 'make snod' try
adb remount
adb shell stop
adb sync
adb shell start


I for one, prefer the first - quit the emulator, make snod, restart the emulator.


Cheers, David

Ron M

unread,
Feb 9, 2012, 12:07:53 PM2/9/12
to android-...@googlegroups.com
David,

I have tried both solutions before our writeup.
The second method did not work for me on ICS for any of the
framework/base/ modifications.
adb sync would "adb push" framework.jar and framework.odex - and
the system would unfortunately crash,
giving exceptions on one case, and the notorious "Zip is good, but no
classes.dex inside" or some other ODEX dependecies messages (please
see an example trace stack at the end of this message) - which sadly
caused me to workaround it by rebuilding everything every time (make
from $ANDROID_BUILD_TOP).

I am actually not 100% what make snod does , it seems that it just
takes the binaries and re-assembles system.img.

Unfortunately, I think that I have to go and build each and every
module, that is
make framework
make packages
make system
....
Which could end up in an entire make, given an arbitrary change.

I really hope that I am missing something. Since I just wanted to
modify something in framework/base/core I did:


# Kill all emulator instances
# from frameworks/base/core
mm # which is equivalent to mmm frameworks - please correct me if I
am wrong, because mmm frameworks yielded with the exact same results
cd $ANDROID_BUILD_TOP
make snod
# run emulator


The sad result is given below. The bottom line is the dreadful
dalvikvm error messages, which appeared for pretty much everything ran
by zygotte. Their summary is pretty much the vicious cycle of (DexOpt
, stale dependencies, Zip is good but no classes.dex inside, unable to
process claspath element ).

I hope that I am just missing something, but in the case I am not - is
it possible to avoid completely all Odexing procedure?
AFAIK it has something to do with java obfuscation and some dalvik
cache optimizations, and I read about ROM cookers "deodexing" - I just
don't know how to do it on the platform level.


D/AndroidRuntime( 1892): >>>>>> AndroidRuntime START
com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1892): CheckJNI is ON
I/dalvikvm( 1892): DexOpt: mismatch dep signature for
'/system/framework/framework.odex'
E/dalvikvm( 1892): /system/framework/android.policy.jar odex has stale
dependencies
I/dalvikvm( 1892): Zip is good, but no classes.dex inside, and no
valid .odex file in the same directory
D/dalvikvm( 1892): Unable to process classpath element
'/system/framework/android.policy.jar'
I/dalvikvm( 1892): DexOpt: mismatch dep signature for
'/system/framework/framework.odex'
E/dalvikvm( 1892): /system/framework/services.jar odex has stale dependencies
I/dalvikvm( 1892): Zip is good, but no classes.dex inside, and no
valid .odex file in the same directory
D/dalvikvm( 1892): Unable to process classpath element
'/system/framework/services.jar'
I/dalvikvm( 1892): DexOpt: mismatch dep signature for
'/system/framework/framework.odex'
E/dalvikvm( 1892): /system/framework/apache-xml.jar odex has stale dependencies
I/dalvikvm( 1892): Zip is good, but no classes.dex inside, and no
valid .odex file in the same directory
D/dalvikvm( 1892): Unable to process classpath element
'/system/framework/apache-xml.jar'
I/dalvikvm( 1892): DexOpt: mismatch dep signature for
'/system/framework/framework.odex'
E/dalvikvm( 1892): /system/framework/filterfw.jar odex has stale dependencies
I/dalvikvm( 1892): Zip is good, but no classes.dex inside, and no
valid .odex file in the same directory
D/dalvikvm( 1892): Unable to process classpath element
'/system/framework/filterfw.jar'
E/JNIHelp ( 1892): Native registration unable to find class
'com/android/server/Watchdog', aborting
F/libc ( 1892): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 788): *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** ***
I/DEBUG ( 788): Build fingerprint: 'unknown'
I/DEBUG ( 788): pid: 1892, tid: 1892 >>> zygote <<<
I/DEBUG ( 788): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault
addr deadbaad
I/DEBUG ( 788): eax 00000000 ebx b7f3b654 ecx 00000004 edx b7f3b7c8
I/DEBUG ( 788): esi b76ea000 edi bfd4d6fc
I/DEBUG ( 788): xcs 00000073 xds 0000007b xes 0000007b xfs
00000000 xss 0000007b
I/DEBUG ( 788): eip b7ede403 ebp bfd4d718 esp bfd4d6d0 flags 00000246
I/DEBUG ( 788): #00 eip: b7ede403 /system/lib/libc.so (abort)
I/DEBUG ( 788): #01 eip: b7c475fb
/system/lib/libnativehelper.so (jniRegisterNativeMethods)
I/DEBUG ( 788): #02 eip: b7d18f43
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime21registerNativeMethodsEP7_JNIEnvPKcPK15JNINativeMethodi)
I/DEBUG ( 788): #03 eip: b7d83f5a
/system/lib/libandroid_runtime.so
(_ZN7android32register_android_server_WatchdogEP7_JNIEnv)
I/DEBUG ( 788): #04 eip: b7d178c7
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 788): #05 eip: b7d18b50
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #06 eip: 080491d7 /system/bin/app_process (main)
I/DEBUG ( 788): #07 eip: b7edadcf /system/lib/libc.so (__libc_init)
I/DEBUG ( 788): stack:
I/DEBUG ( 788): #00 bfd4d6d0 00000002 (__libc_init)
I/DEBUG ( 788): #00 bfd4d6d4 bfd4d6fc [stack] (__libc_init)
I/DEBUG ( 788): #00 bfd4d6d8 00000000 (__libc_init)
I/DEBUG ( 788): #00 bfd4d6dc bfd4d6ec [stack] (__libc_init)
I/DEBUG ( 788): #00 bfd4d6e0 1d300181 (__libc_init)
I/DEBUG ( 788): #00 bfd4d6e4 00000000 (__libc_init)
I/DEBUG ( 788): #00 bfd4d6e8 b729113b /system/lib/libdvm.so
I/DEBUG ( 788): #00 bfd4d6ec 087a8500 [heap]
I/DEBUG ( 788): #00 bfd4d6f0 b72942eb /system/lib/libdvm.so
(_ZZL15Check_FindClassP7_JNIEnvPKcE12__FUNCTION__)
I/DEBUG ( 788): #00 bfd4d6f4 00000000
(_ZZL15Check_FindClassP7_JNIEnvPKcE12__FUNCTION__)
I/DEBUG ( 788): #00 bfd4d6f8 00000001
(_ZZL15Check_FindClassP7_JNIEnvPKcE12__FUNCTION__)
I/DEBUG ( 788): #00 bfd4d6fc fffffbdf
(_ZZL15Check_FindClassP7_JNIEnvPKcE12__FUNCTION__)
I/DEBUG ( 788): #00 bfd4d700 087a8500 [heap]
(_ZZL15Check_FindClassP7_JNIEnvPKcE12__FUNCTION__)
I/DEBUG ( 788): #00 bfd4d704 1d200181
(_ZZL15Check_FindClassP7_JNIEnvPKcE12__FUNCTION__)
I/DEBUG ( 788): #00 bfd4d708 b7ede38e /system/lib/libc.so (abort)
I/DEBUG ( 788): #00 bfd4d70c b7c9a5ec
/system/lib/libnativehelper.so (abort)
I/DEBUG ( 788): ...... ......
I/DEBUG ( 788): #01 bfd4d71c b7c475fb
/system/lib/libnativehelper.so (jniRegisterNativeMethods)
I/DEBUG ( 788): #01 bfd4d720 00000006 (jniRegisterNativeMethods)
I/DEBUG ( 788): #01 bfd4d724 b7c87ff6 /system/lib/libnativehelper.so
I/DEBUG ( 788): #01 bfd4d728 b7c8811c /system/lib/libnativehelper.so
I/DEBUG ( 788): #01 bfd4d72c b7d98b7d
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #01 bfd4d730 087a8500 [heap]
I/DEBUG ( 788): #01 bfd4d734 1d300181
I/DEBUG ( 788): #01 bfd4d738 bfd4d768 [stack]
I/DEBUG ( 788): #01 bfd4d73c b7dbee0c
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #01 bfd4d740 0000018c
I/DEBUG ( 788): #01 bfd4d744 087a8500 [heap]
I/DEBUG ( 788): #01 bfd4d748 bfd4d768 [stack]
I/DEBUG ( 788): #02 bfd4d74c b7d18f43
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime21registerNativeMethodsEP7_JNIEnvPKcPK15JNINativeMethodi)
I/DEBUG ( 788): #02 bfd4d750 087a8500 [heap]
(_ZN7android14AndroidRuntime21registerNativeMethodsEP7_JNIEnvPKcPK15JNINativeMethodi)
I/DEBUG ( 788): #02 bfd4d754 b7d98b7d
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #02 bfd4d758 b7dbd790
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #02 bfd4d75c 00000001
I/DEBUG ( 788): #02 bfd4d760 b7d18f19
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime21registerNativeMethodsEP7_JNIEnvPKcPK15JNINativeMethodi)
I/DEBUG ( 788): #02 bfd4d764 b7dbee0c
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime21registerNativeMethodsEP7_JNIEnvPKcPK15JNINativeMethodi)
I/DEBUG ( 788): #02 bfd4d768 bfd4d788 [stack]
(_ZN7android14AndroidRuntime21registerNativeMethodsEP7_JNIEnvPKcPK15JNINativeMethodi)
I/DEBUG ( 788): #03 bfd4d76c b7d83f5a
/system/lib/libandroid_runtime.so
(_ZN7android32register_android_server_WatchdogEP7_JNIEnv)
I/DEBUG ( 788): #03 bfd4d770 087a8500 [heap]
(_ZN7android32register_android_server_WatchdogEP7_JNIEnv)
I/DEBUG ( 788): #03 bfd4d774 b7d98b7d
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #03 bfd4d778 b7dbd790
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #03 bfd4d77c 00000001
I/DEBUG ( 788): #03 bfd4d780 b7d83f29
/system/lib/libandroid_runtime.so
(_ZN7android32register_android_server_WatchdogEP7_JNIEnv)
I/DEBUG ( 788): #03 bfd4d784 b7dbee0c
/system/lib/libandroid_runtime.so
(_ZN7android32register_android_server_WatchdogEP7_JNIEnv)
I/DEBUG ( 788): #03 bfd4d788 bfd4d7b8 [stack]
(_ZN7android32register_android_server_WatchdogEP7_JNIEnv)
I/DEBUG ( 788): #04 bfd4d78c b7d178c7
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 788): #04 bfd4d790 087a8500 [heap]
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 788): #04 bfd4d794 000000c8
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 788): #04 bfd4d798 b7d88663
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #04 bfd4d79c 00000000
I/DEBUG ( 788): #04 bfd4d7a0 bfd4d78c [stack]
I/DEBUG ( 788): #04 bfd4d7a4 00000001
I/DEBUG ( 788): #04 bfd4d7a8 b7d1787d
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 788): #04 bfd4d7ac b7dbee0c
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 788): #04 bfd4d7b0 b7d88314
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #04 bfd4d7b4 080493f4 /system/bin/app_process
I/DEBUG ( 788): #04 bfd4d7b8 bfd4d868 [stack]
I/DEBUG ( 788): #05 bfd4d7bc b7d18b50
/system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7c0 087a8500 [heap]
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7c4 087a8500 [heap]
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7c8 bfd4d84c [stack]
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7cc 00000008
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7d0 00000000
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7d4 087a83e8 [heap]
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7d8 bfd4d848 [stack]
(_ZN7android14AndroidRuntime5startEPKcS2_)
I/DEBUG ( 788): #05 bfd4d7dc b7d886f7
/system/lib/libandroid_runtime.so
I/DEBUG ( 788): #05 bfd4d7e0 000000b0
I/DEBUG ( 788): #05 bfd4d7e4 00080000
I/DEBUG ( 788): #05 bfd4d7e8 00000000
I/DEBUG ( 788): #05 bfd4d7ec 087a8f40 [heap]
I/DEBUG ( 788): #05 bfd4d7f0 00000001
I/DEBUG ( 788): #05 bfd4d7f4 bfd40031 [stack]
I/DEBUG ( 788): #05 bfd4d7f8 bfd4d818 [stack]
I/DEBUG ( 788): ...... ......
I/DEBUG ( 788): #06 bfd4d86c 080491d7 /system/bin/app_process (main)
I/DEBUG ( 788): #06 bfd4d870 bfd4d8c4 [stack] (main)
I/DEBUG ( 788): #06 bfd4d874 080493f4 /system/bin/app_process
I/DEBUG ( 788): #06 bfd4d878 080494af /system/bin/app_process
I/DEBUG ( 788): #06 bfd4d87c 00002000
I/DEBUG ( 788): #06 bfd4d880 00000005
I/DEBUG ( 788): #06 bfd4d884 00000000
I/DEBUG ( 788): #06 bfd4d888 00000000
I/DEBUG ( 788): #06 bfd4d88c bfd4dd27 [stack]
I/DEBUG ( 788): #06 bfd4d890 080494d1 /system/bin/app_process
I/DEBUG ( 788): #06 bfd4d894 bfd4d968 [stack]
I/DEBUG ( 788): #06 bfd4d898 00000004
I/DEBUG ( 788): #06 bfd4d89c 00000015
I/DEBUG ( 788): #06 bfd4d8a0 bfd4d8c4 [stack]
I/DEBUG ( 788): #06 bfd4d8a4 080494c3 /system/bin/app_process
I/DEBUG ( 788): #06 bfd4d8a8 0100000d
I/DEBUG ( 788): ...... ......
I/DEBUG ( 788): #07 bfd4d90c b7edadcf /system/lib/libc.so
(__libc_init)
I/DEBUG ( 788): #07 bfd4d910 00000005 (__libc_init)
I/DEBUG ( 788): #07 bfd4d914 bfd4d964 [stack] (__libc_init)
I/DEBUG ( 788): #07 bfd4d918 bfd4d97c [stack] (__libc_init)
I/DEBUG ( 788): #07 bfd4d91c 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d920 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d924 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d928 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d92c bfd4d97c [stack] (__libc_init)
I/DEBUG ( 788): #07 bfd4d930 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d934 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d938 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d93c 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d940 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d944 00000000 (__libc_init)
I/DEBUG ( 788): #07 bfd4d948 00000000 (__libc_init)
I/DEBUG ( 788): ...... ......
I/ServiceManager( 783): service 'media.audio_flinger' died
I/ServiceManager( 783): service 'media.player' died
I/ServiceManager( 783): service 'media.camera' died
I/ServiceManager( 783): service 'media.audio_policy' died

> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/android-platform/-/bc5LzdIPa4sJ.

David Herges

unread,
Feb 9, 2012, 2:58:02 PM2/9/12
to android-...@googlegroups.com
Fucking shite...yer don't wanna see these messages, don't yer? ^^

When I did my Android-based project, I branched it from gingerbread v2.3.7. For me, the following works perfectly fine. However, if there got *some*thing changed in the build system of gingerbread compared to ICS, that's likely the reason why it doesn't work for you. What I do is:

# quit the emulator
# make sure that emulator's process is killed
ps -a
cd $ANDROID_BUILD_TOP
mmm frameworks/base
mmm frameworks/base/services/java
mmm libcore
make framework
make snod
emulator
# bang bang, emulator spawns off with the up-to-date system.img


You can leave out any of the 'mmm' commands depending on what part you changed. 'mm' vs. 'mmm': you should be right with your assumption. Maybe the following links gives you further help: http://elinux.org/Android_Build_System

'make modules' and 'make droid' sound like it could help, you'll have to try. 'make snod', as you said, just re-assembles the system.img from all the partial builds that are located in '$ANDROID_BUILD_TOP/out/' folder. Another option, try asking in the android-building group. Maybe you'll find someone there who knows details of the ICS build system.


Cheers

Ron M

unread,
Feb 9, 2012, 4:30:12 PM2/9/12
to android-...@googlegroups.com, Android Building
I think this is the group for platform related issues, but just in
case, I am cross posting.

JBQ/anyone else - can you please assist on this one?

Thanks in advance.

Ron

> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/android-platform/-/ORRF3aAc6GwJ.

Ying Wang

unread,
Feb 13, 2012, 3:34:56 PM2/13/12
to android-...@googlegroups.com, Android Building
If dex-preopt is enabled (for example in user build) and the framework is changed, you have to rebuild everything, I believe.

ritter liu

unread,
Jan 21, 2013, 10:22:23 AM1/21/13
to android-...@googlegroups.com
Hi David

I have already find a solution. Do not just 'make snod', which means 'make (systemimage no dependence)', maybe you'd better make systemimage with dependence.
So,try this way:
1.after you edit the code in framework/base, do 'mm'
2.then back to the root dir, 'make droidcore'
3.then you'd better restart the AVD without just 'adb shell stop' && 'adb shell start'.(These cmds maybe not work).
Ps:If this way works,you can try to use 'make systemimage' instead of 'make droidcore', which will faster. :P
This is my blog about the solution: http://blog.csdn.net/ritterliu/article/details/7816004

2013/1/21 dima <hofma...@gmail.com>
Hi Liu,

do u solved this problem??? I get exactly the same error :(

Am Montag, 30. Juli 2012 08:59:21 UTC+2 schrieb ritter liu:
Hi David

I add some logs into frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java in android4.0.3.

And I do the follow steps just like you said:

mmm frameworks/base
mmm frameworks/base/services/java
mmm libcore
make framework
make snod

But when I try to start emulator,it dies in "android" words boot animation ,with ddms output:

07-30 06:50:52.762: I/ServiceManager(30): service 'media.audio_policy' died
07-30 06:50:52.762: I/ServiceManager(30): service 'media.audio_flinger' died
07-30 06:50:52.762: I/ServiceManager(30): service 'media.player' died
07-30 06:50:52.762: I/ServiceManager(30): service 'media.camera' died
07-30 06:50:52.822: I/Netd(383): Netd 1.0 starting
07-30 06:50:52.842: E/Netd(383): Unable to bind netlink socket: No such file or directory
07-30 06:50:52.842: E/Netd(383): Unable to open quota2 logging socket
07-30 06:50:53.253: I/(381): ServiceManager: 0xf958
07-30 06:50:53.253: I/AudioFlinger(381): Loaded primary audio interface from LEGACY Audio HW HAL (audio)
07-30 06:50:53.253: I/AudioFlinger(381): Using 'LEGACY Audio HW HAL' (audio.primary) as the primary audio interface
07-30 06:50:53.253: D/AudioHardwareInterface(381): setMode(NORMAL)
07-30 06:50:53.253: I/CameraService(381): CameraService started (pid=381)
07-30 06:50:53.262: D/EmulatedCamera_QemuClient(381): Emulated camera list: 
07-30 06:50:53.262: D/EmulatedCamera_FakeCamera(381): Initialize: Fake camera is facing back
07-30 06:50:53.262: V/EmulatedCamera_Factory(381): 1 cameras are being emulated. Fake camera ID is 0
07-30 06:50:53.272: I/AudioFlinger(381): AudioFlinger's thread 0x10fb0 ready to run
07-30 06:50:53.272: W/AudioFlinger(381): Thread AudioOut_1 cannot connect to the power manager service
07-30 06:50:53.272: I/AudioPolicyService(381): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
07-30 06:50:56.022: D/AndroidRuntime(393): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
07-30 06:50:56.022: D/AndroidRuntime(393): CheckJNI is ON
07-30 06:50:56.042: I/dalvikvm(393): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
07-30 06:50:56.042: E/dalvikvm(393): /system/framework/android.policy.jar odex has stale dependencies
07-30 06:50:56.042: I/dalvikvm(393): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
07-30 06:50:56.042: D/dalvikvm(393): Unable to process classpath element '/system/framework/android.policy.jar'
07-30 06:50:56.042: I/dalvikvm(393): DexOpt: Some deps went away
07-30 06:50:56.042: E/dalvikvm(393): /system/framework/services.jar odex has stale dependencies
07-30 06:50:56.042: I/dalvikvm(393): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
07-30 06:50:56.042: D/dalvikvm(393): Unable to process classpath element '/system/framework/services.jar'
07-30 06:50:56.042: I/dalvikvm(393): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
07-30 06:50:56.042: E/dalvikvm(393): /system/framework/apache-xml.jar odex has stale dependencies
07-30 06:50:56.042: I/dalvikvm(393): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
07-30 06:50:56.042: D/dalvikvm(393): Unable to process classpath element '/system/framework/apache-xml.jar'
07-30 06:50:56.042: I/dalvikvm(393): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
07-30 06:50:56.042: E/dalvikvm(393): /system/framework/filterfw.jar odex has stale dependencies
07-30 06:50:56.042: I/dalvikvm(393): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
07-30 06:50:56.042: D/dalvikvm(393): Unable to process classpath element '/system/framework/filterfw.jar'
07-30 06:50:56.682: E/JNIHelp(393): Native registration unable to find class 'com/android/server/Watchdog', aborting
07-30 06:50:56.682: A/libc(393): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

I also tried other method just like:

1.make framework

2. push framework.jar nad framework.odex into system/framework

It also doesn't work.

Do you have some idea about what to do can make framework's modify works?

Best regards
ritter liu

在 2012年2月9日星期四UTC+8下午8时28分05秒，David Herges写道：

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-platform/-/ZyDurjAiz4wJ.

Barath Seshadri

unread,
Apr 15, 2013, 8:46:27 AM4/15/13
to android-...@googlegroups.com
Hi,

I'm getting the same crash (fatal sigsegv) and I have a clean build with my local init.rc and some changes in framework/base/services. so, make built both ramdisk and system images that include my changes.

its posted here :
https://groups.google.com/forum/#!topic/android-platform/niYZPEVkA-M

Does anyone know how to fix this?

Thanks,
Bks
Reply all
Reply to author
Forward
0 new messages