I have modified the android system source file audiomanager.java for my own purposes and compiled the whole ROM. However, i dont want to flash the whole ROM. Which file is audiomanager.java compiled to?
Its location in the source is /frameworks/base/media/java/android/media/audiomanager.java
Thanks!
Related
I already have the source file for my phone (Samsung Conquer 4g) from http://opensource.samsung.com/ but I want to know how to build it. I want to get some things straight first. When I unzipped it I get two other zips, one named platform and the other named kernel. The file system would be the one named platform correct? After that I am wondering how I can build a flashable, bootable rom. I am on ubuntu 12.04. I am not trying to port, I am trying to update than mod it with root and etc. Coding would be useful. Thanks.
itzdarockz said:
I already have the source file for my phone (Samsung Conquer 4g) from http://opensource.samsung.com/ but I want to know how to build it. I want to get some things straight first. When I unzipped it I get two other zips, one named platform and the other named kernel. The file system would be the one named platform correct? After that I am wondering how I can build a flashable, bootable rom. I am on ubuntu 12.04. I am not trying to port, I am trying to update than mod it with root and etc. Coding would be useful. Thanks.
Click to expand...
Click to collapse
Tutorial in my signature. You downloaded kernel source, not device repo source. Platform just contains files that have been modified from the android source to build the kernel for your device.
私のEVO 3Dから送信される。
So i've compiled my first build from source (NS4G) and have a few questions.
1. after its completed compilation what is the directory/path that i can find the files i need. Ive uploaded a screenshot of the path i think it is however it doesnt contain a system.img file why is that and do i need it?
2.Once i have the correct files how to i place them for use in the emulator?
thank you for any help.
I'm working on learning how to build AOSP. And I have it working for the most part... I have built it and have been able to get the superuser.apk and proprietary binaries in... however, it compiles the su-binary from the source code it seems, so I haven't been able to include the most recent su-binary in my build. I've tried pasting in the chainsDD source, but I know that must not be the correct way to do it as I got errors (manually replacing the source code in WORKING_DIRECTORY/system/extras/su with the source from chainsDD git repository).
Does anyone know any tricks to get the most recent su-binary compiled into AOSP builds?
I've tried all sorts of things replacing 'su' in various places with the one I want, unpacking, mounting, modifying, and re-packing system.img from the out directory and the su-binary always gets built from source when I do a make otapackage.
I'm sure I am going about this is a roundabout and inneficient way... maybe someone can enlighten me.
I know it probably doesn't matter what version of su-binary is in there, as the superuser app will just be able to update it, but I'd like to have it there without needing to update after flashing. I'm trying to get my local aosp code so that I run the make command and it generates the ota package that I want rather than having to manually put things in the zip after it is created.
Hello everyone,
I am currently developing with AOSP 5.1 for a FriendlyARM s5p4418 (NanoPi2).
Our special firmware is working nice, building it creates all the necessary img files (boot.img, system.img, userdata.img, ...).
But when I do a "make dist", it is not copying the boot.img into the IMAGES/ folder in out/dist/ folder. So when I try to continue, I cannot create a ota-package because the releasetools/ota_from_target_files crashes when trying to calculate the Difference of recovery-Image and boot-Image. Both are of type NONE because they are not existing.
Why is it creating the boot.img when using just make, but not creating or using it with make disk.
Is it because I am using the prebuilt kernel zImage?
Is there a way to fix this? Or to create an OTA package from the files that make creates?
Greetings
Tobi
Well it seems I found the problem.
The device tree is setting TARGET_NO_KERNEL to true, because it is using a prebuilt kernel uImage.
I did now set this to false and copied the uImage to $(PRODUCT_OUT)/kernel and now it is compiliing a recovery and the boot also.
But I do not know if this is the correct way to do it?
Is it possible to extract device sources files from stock rom like vendor blobs with extract-files.sh ?
I have system / boot and all other images available on my linux system.