Android compiled framework rack package Run Error

Source: Internet
Author: User

Android compiled framework rack package Run Error

http://blog.csdn.net/cqupt_chen/article/details/8163632


Recently in the frameworks to see the source code, preface, then want to change to see the effect, did not expect to change the end, the simulator is not running up.
First of all, I was using the Android 4.0.3 ICS source code, compiled well, using the compiled image to start the simulator, previously modified the inside of the launcher, will generate launcher.apk and Launcher.odex push after is successful.
Now I'm in
Frameworks/base/policy/src/com/android/internal/policy/impl/lockscreen.java
Frameworks/base/core/java/com/android/internal/widget/multiwaveview/multiwaveview.java
Added a bit of log, is actually unlocked when the corresponding output coordinates and other information,
Two methods were tried:
1. Make framework
Make Snod

2. In framework/base mm
ADB push Framework.jar and Framework.odex to system/framework/

As a result, when you start the emulator, the Android Word will not go in when the boot, DDMS printing the following information:
07-30 06:50:52.762:i/servicemanager (+): Service ' Media.audio_policy ' died
07-30 06:50:52.762:i/servicemanager (+): Service ' Media.audio_flinger ' died
07-30 06:50:52.762:i/servicemanager (+): Service ' Media.player ' died
07-30 06:50:52.762:i/servicemanager (+): 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 is 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 One (SIGSEGV) at 0xdeadbaad (code=1)
Later, according to the tips of the master, to see BUILD/CORE/MAIN.MK, found inside there is a droidcore command,
After attempting to compile with make Droidcore, the emulator runs successfully, prints the modified log, and then analyzes the Droidcore carefully:
755. Phony:droidcore
756 droidcore:files \
757 systemimage \
758 $ (installed_bootimage_target) \
759 $ (installed_recoveryimage_target) \
760 $ (installed_userdataimage_target) \
761 $ (Installed_files_file)
The discovery started with the execution of Systemimage, so I tried to compile with make Systemimage:
Modify the framework in the source code, in Framework/base mm, back to the source code root directory, make systemimage, start the simulator, modify the effect of successful display.
Ps:
1. Seemingly execute make Snod (systemimage no dependence) No, it seems to be made up of dependence.
2. Be sure to turn off the emulator after make systemimage, execute adb shell stop,adb shell start.
Is the time is longer, make up for about 10 minutes.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.