yanglee110
commented
8 years ago Hi, haibo: So far I can trace the Frame Buffer and Camera activities、CPU/Memory accesses、raw instructions. However, the only problem is that the emulator's response time is very slow, even more than several minutes. Have you ever come across this problem and then how did you solve it? Please help me work out this problem. Thanks! Look forwards to your reply.
Hi, haibo: I've finished these steps:download the aosp4.4.4, compile the aosp, replace the qemu, compile the qemu. And so far everything is ok. However, i have come across two questions: (1)when i run the command "emulator -kernel ../../../prebuilts/qemu-kernel/arm/kernel-qemu-armv7 -sysdir ../../../out/target/product/generic -system system.img -data userdata.img -ramdisk ../../../out/target/product/generic/ramdisk.img", the android emulator is launched but the response time is very slow and much slower than the the emulator lanched by the sdk. So what's wrong with my problems? (2)when i successfully launched the emulator in the /objs directory, there are no physical keys compared with the emulator launched by the sdk. So how do i push the button 'Volume up' or 'Call' and how do i check the traces? Thanks!