android-source

问题 I've been going through the steps to build the Android Source code. After getting everything set up according to the instructions, I executed "make". The make process chugged along until the link where it ultimately failed with the following error: Undefined symbols for architecture x86_64: "_main", referenced from: start in crt1.10.6.o ld: symbol(s) not found for architecture x86_64 collect2: ld returned 1 exit status The other thing of note is that the link is generating a number of warning

问题 I am building AOSP and I want to sign the build with my own key. There is some official doc about this process here. But I wonder if I can simply turn around all of that process and instead do this things: Delete default android test-keys which are located at build/target/product/security put my keys (which are generated using official instructions at here) in that folder with same names. (Assume one key for all of shared,media,...) But this approach does not work. After burning the image,

问题 I am interested in building Android for Source for a Galaxy S3 (but just knowing how to do it in general will be quite helpful) I know how to do it for all the nexus devices in general, but I was wondering how to do it for some of the other phones. I know that it is possible because CyanogenMod and other modders do it. Usually when they announce them they include the source for the kernel. How do you put the pieces together? Getting the android source code and the custom kernel together in

问题 I am trying to build AOSP 4.3 (build: JSR78D; branch: android-4.3_r2) on Debian 7 (amd64). I followed the instructions listed in Google Android website and finished build steps successfully. At the end, I could test my newly built image with the Android emulator . Now, I have 3 image files in the out/target/product/generic directory: system.img , userdata.img , and ramdisk.img . However, boot.img is missing. I tried issuing the make bootimage command, but it did not help generating the

问题 I want to make some changes in one function in ViewGroup.java. I already had the sources compiled, so I am only compilling the part that I changed last, with the command make framework but when I start the emulator, it crashes with the error --------- beginning of crash 01-29 22:22:30.570 280 280 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main 01-29 22:22:30.570 280 280 E AndroidRuntime: java.lang.RuntimeException: Missing class when invoking static main com.android.server

问题 How to use custom RenderScript script in an application which is signed by system certificate? LogCat output: E/RenderScript: Failed loading RS driver: dlopen failed: cannot locate symbol "_ZN7android12renderscript15RsdCpuReference6createEPNS0_7ContextEjjPFPKNS1_9CpuSymbolES3_PKcEPFPNS1_9CpuScriptES3_PKNS0_6ScriptEEPFPN4llvm6ModuleEPN3bcc8RSScriptESK_SK_EPFS8_S8_jES8_" referenced by "/system/vendor/lib/libRSDriver_adreno.so"... E/RenderScript: Failed to load runtime libRSDriver_adreno.so,

问题 I've compile the android source source ./build/envsetup.sh lunch aosp_x86_64-eng when I run emulator64-x86 in terminal, error occur: emulator64-x86: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.7' not found (required by emulator64-x86) emulator64-x86: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5' not found (required by emulator64-x86) emulator64-x86: /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5: version `Qt_5' not found (required by emulator64-x86) emulator64-x86: /usr

问题 I'm trying to get a better understanding of the differences so I can evaluate if I should be implementing a System Service, or a Service. The differences that I have found from the docs are the following: System Service Started in SystemServer Added to ServiceManager Considered mandatory, and soft reboots the device on failure More permissions? (Not sure what it can do that a Service can't) Service Initialized and started using an intent? Is there anything else is different between the two? I

问题 I downloaded the source to spareparts here https://android.googlesource.com/platform/development/+/gingerbread-release/apps/SpareParts It includes Android.mk , AndroidManifest.xml , Notice , res and src folders. My question is how can I compile this source code in Eclipse? I see there is a make file ( Android.mk ) which I'm guessing I need to use but I can't figure out what to do to get this thing imported into Eclipse without having 500+ errors. 回答1: Brute force always works :) Create a new

问题 I'm trying to better understand the underlying logic of camera's native code, but I appear to be hitting a dead-end when looking for the method definition for Camera::connect() and other functions declared from Camera.h . The steps I've followed are these: In the master branch I located Camera.java, which contains the logic for resolving cameras, selecting CameraInfo.CAMERA_FACING_BACK when it is encountered: Camera.open() calls Camera.getCameraInfo(int, CameraInfo) for each int in Camera