Android 4.0 framework源码修改编译,模拟器运行不起来——解决
来源:互联网 发布:cdma类的网络 编辑:程序博客网 时间:2024/05/27 20:56
最近在看frameworks里的源码,手痒了,便想改改看看效果,没想到改完后,模拟器却运行不起来了。
首先声明,我是用的android 4.0.3 ICS的源码,编译好后,利用编译好的镜像启动的模拟器,以前修改过里面的Launcher,将生成的Launcher.apk和Launcher.odex push后是成功的。
现在我在frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
frameworks/base/core/java/com/android/internal/widget/multiwaveview/MultiWaveView.java中加了一点log,其实就是解锁时相应的输出坐标等信息,
试了两种方法:
1. make frameworkmake snod
2. 在framework/base中mm
adb push framework.jar 和 framework.odex 到 system/framework/
结果都是在启动模拟器时,在开机显示 android字样时进不去了,ddms中不停的打印如下信息:
07-30 06:50:52.762: I/ServiceManager(30): service 'media.audio_policy' died07-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)
后来根据高手的提示,去看 build/core/main.mk,发现里面有个droidcore命令,
尝试使用make droidcore编译后,模拟器成功运行,并打印出修改的log,后来仔细分析droidcore:
755 .PHONY: droidcore
756 droidcore: files \757 systemimage \
758 $(INSTALLED_BOOTIMAGE_TARGET) \
759 $(INSTALLED_RECOVERYIMAGE_TARGET) \
760 $(INSTALLED_USERDATAIMAGE_TARGET) \
761 $(INSTALLED_FILES_FILE)
发现一开始是执行systemimage,于是我又尝试用make systemimage来编译:
修改framework中源码,在framework/base 中mm,退至源码根目录,make systemimage后,启动模拟器,修改效果成功显示。
Ps:
1.貌似执行make snod(systemimage no dependence)不行,看来要编上dependence才行。
2.在make systemimage 之后一定要关闭模拟器重开才行,执行adb shell stop,adb shell start也不行。
就是时间比较长,编一下要10分钟左右。
这个解决方法貌似不错:http://blog.csdn.net/cqupt_chen/article/details/8166090
修复framework代码之后,push编译好的framework.jar和相应的odex文件,发现开机失败,一直在android界面循环
而且不停打dismatch dep :
- I/dalvikvm( 375): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
- E/dalvikvm( 375): /system/framework/android.policy.jar odex has stale dependencies
- I/dalvikvm( 375): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
- D/dalvikvm( 375): Unable to process classpath element '/system/framework/android.policy.jar'
- I/dalvikvm( 375): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
- E/dalvikvm( 375): /system/framework/services.jar odex has stale dependencies
- I/dalvikvm( 375): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
- D/dalvikvm( 375): Unable to process classpath element '/system/framework/services.jar'
- I/dalvikvm( 375): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
- E/dalvikvm( 375): /system/framework/apache-xml.jar odex has stale dependencies
- I/dalvikvm( 375): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
- D/dalvikvm( 375): Unable to process classpath element '/system/framework/apache-xml.jar'
- I/dalvikvm( 375): DexOpt: mismatch dep signature for '/system/framework/framework.odex'
- E/dalvikvm( 375): /system/framework/filterfw.jar odex has stale dependencies
- I/dalvikvm( 375): Zip is good, but no classes.dex inside, and no valid .odex file in the same directory
- D/dalvikvm( 375): Unable to process classpath element '/system/framework/filterfw.jar'
- E/JNIHelp ( 375): Native registration unable to find class 'com/android/server/Watchdog', aborting
- F/libc ( 375): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
- if (len != storedStrLen ||
- strcmp(cacheFileName, (const char*) ptr) != 0)
- {
- LOGI("DexOpt: mismatch dep name: '%s' vs. '%s'",
- cacheFileName, ptr);
- goto bail;
- }
- ptr += storedStrLen;
- if (memcmp(signature, ptr, kSHA1DigestLen) != 0) {
- LOGI("DexOpt: mismatch dep signature for '%s'", cacheFileName);
- goto bail;
- }
- ptr += kSHA1DigestLen;
- LOGV("DexOpt: dep match on '%s'", cacheFileName);
- numDeps--;
如此看来只有两种解决办法:
1.用make snod命令重新编译system.img,这样编译出来的system中的架包之间没有依赖
2.修改DexPrepare.cpp中的验证代码,直接跳过签名验证
- Android 4.0 framework源码修改编译,模拟器运行不起来——解决
- Android 4.0 framework源码修改编译,模拟器运行不起来——解决
- Android 4.0 framework源码修改编译,模拟器运行不起来——解决
- Android 4.0 framework源码修改编译,模拟器运行不起来
- 模拟器启动不起来怎么解决
- Android项目源码运行不起来的七种解决方法
- Android项目源码运行不起来的七种解决方法
- Android 4.0.1 源码下载,模拟器编译和运行
- Android源码编译及模拟器运行
- android adb运行不起来
- Android模拟器启动不起来的原因
- android 修改源码framework后如何编译
- android 修改源码framework后如何编译
- android 修改源码framework后如何编译
- android 修改源码framework后如何编译
- 编译运行Android模拟器
- 编译运行Android模拟器
- 编译运行Android模拟器
- 腾讯的一道面试题—不用除法求数字乘积
- SQL Server数据类型
- Telnet无法启动 的解决方法
- 浤济类-〉金额转换(数字=中文)互换(全)
- adb logcat 查看日志
- Android 4.0 framework源码修改编译,模拟器运行不起来——解决
- VS2010 继承目录编辑
- Oracle中批量删除数据
- 在Visual Studio 2010中配置VC++目录
- Oracle中大批量删除数据的方法(通过主键删除)
- C语言的const关键字与指针搭配使用
- 举例说明在android中用PhoneStateListener监听手机电话状态与用发送邮件来通知来电电话的号码
- windows文件夹不能在VMWARE共享的解决办法
- get_user_pages — 获取用户区进程使用内存的某个页