I would prefer not mixing the SDK build and the opensource build. The following should work: <android-root>$ source build/envsetup.sh <android-root>$ lunch 1 <android-root>$ make clean <android-root>$ make -j ENABLE_PV_LOGGING=1 <android-root>$ emulator & adb logcat
-Ravi On Feb 3, 7:11 pm, RCP2278 <rcp2...@gmail.com> wrote: > Hi Ravi, > > Thanks again for your response and patience. > > So I've confirmed that the emulator is still loading the old images > after I've compiled the android code, but I'm now running into issues > (not necessarily logging issues) when I launch the emulator or try to > run the ApiDemos application. It turns out that the emulator that I'm > launching is looking at the emulator located in the android-sdk tools > folder. So here's what I've done: > > 1) Ended up building the entire android codebase (just to be safe, > plus I had some time in my hands :)). Basically, from <android-root>: > > make clean > make -j ENABLE_PV_LOGGING=1 > > 2) After building, I saw that the new images are built under <android- > root>/out/target/product/generic. The three images that I need I'm > assuming are ramdisk.img, system.img, and userdata.img > > 3) Launched the emulator from Eclipse with option -system <android- > root>/out/target/product/generic. Unfortunately it prompted me saying > that it could not find the kernel-qemu and that I should use -kernel > option. Couldn't find the kernel-qemu file in the same directory, so > I did an alternative approach instead (see (4) below) > > 4) Since my default emulator is being launched from the android-sdk > tools folder, I copied those three built images to <android-sdk- > folder>/tools/lib/images instead. Coincidentally, there is a kernel- > qemu file in that directory as well. > > 5) Relaunched the emulator again from Eclipse (this time with -wipe- > data option included but removed the -system option I added earlier). > When it came time to install the ApiDemos.apk, the following DDMS > console error appeared: > > ApiDemos] Installation error: INSTALL_FAILED_MISSING_SHARED_LIBRARY > ApiDemos] Please check logcat output for more details > > Not suprisingly, the ApiDemos app is not there and the logcat messages > show a lot of errors indicating that it couldn't find any libraries, > etc > > Now, I thought maybe the only image that I need is userdata.img??? So > once more I followed the same steps as above, except this time I'm > only using the built userdata.img and kept the ramdisk.img and > system.img as is. Everything loaded fine, but when it came time to > play a streaming file, I continue to see the VERBOSE log of tag > ProtocolEngine (argh!) > > Can you help me point out what step I did wrong here? Did I copy the > wrong images? Did I build it incorrectly? > > -R --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
