im wondering if it it would be possible to find where they are booted and change the file path location to read another type of file, say a .zip like everyother phone?
I am wondering the same thing. I understand that you can replace the kernel to achieve the same effect. But is there an other way that would not depend on kernel modification...
system/media/bootani.qmg
Which is utterly useless since no one can compile or decompile a .qmg file.
well the net is jam packed with tuts and how tos on setting up build environments, and building/ compiling or just plain cooking roms/ kernels.
and everyone is different in its own way, but everyone of them is the same when it comes to putting in device prop files,binaries.
a little vague, and assumes you have them. lol
so i have a sudo supported device, lgp505. i am trying to obtain prop files for it so i can build GB. i do not have an extract-files.sh that works, i have ics,jb prop files and the extract script from that git tries to cd to a folder that is not there.
how do i go about getting GB prop files. what files do i need, and how do i get them and the .mk files into source in order to compile?
thanks abunch.
Hello all,
I am working on a custom CyanogenMod ROM (10.2) for my own use. I've managed to accomplish most of my goals. One thing remains: removing packages that I don't want/need from the build. Technically, I am able to do so already by modifying the Android.mk file of the package so that it produces errors during the build procedure, skips building the package, but doesn't stop the entire build process. However, that is just a lousy hack.
Can anyone point me to the correct .mk/.sh/.whatever files in the repository I would need to edit (there are probably several) so that I can skip building the packages I don't want included in my ROM? I want to avoid using a "kitchen" if I can. I won't actually learn anything if I use a kitchen.
Files to look at
After laboriously looking through the repository, I came accross several files/directories you may need to look through/edit to remove packages from the build:
This directory (replace cm102 with your path to your Cyanogen repo):
/cm102/vendor/cm/config
This file:
/cm102/android/cm-10.2-M1.xml (<- This is a long file, dig through it. I edited this to help me remove some prepackaged live wallpapers, but there is a lot more in here.)
Device specific CM makefile that may specify additional packages to include (replace the all caps with whatever seems logical in your directory at each step):
/cm102/device/YOUR_MANUFACTURER/CODENAME-COMMON/CODENAME-COMMON.mk
Hi! I am trying to build a device tree for my device. I am wondering which files are required in a device tree. I know you need certain files that are mandatory, like BoardConfig.mk, system.prop etc. but how do I know which other files and folders I need. For example, the 1+1 device tree has audio, bluetooth, gps, camera and other folders, but certain device trees don't have a GPS folder. It varies between device. So, how do I know which files are needed in my device tree? Thanks
Looking forward to see answer to this. I also need to know this
NateDev473 said:
Hi! I am trying to build a device tree for my device. I am wondering which files are required in a device tree. I know you need certain files that are mandatory, like BoardConfig.mk, system.prop etc. but how do I know which other files and folders I need. For example, the 1+1 device tree has audio, bluetooth, gps, camera and other folders, but certain device trees don't have a GPS folder. It varies between device. So, how do I know which files are needed in my device tree? Thanks
Click to expand...
Click to collapse
I would start by checking out this guide for some better information about the required files and what is involved https://docs.omnirom.org/Porting_Omni_To_Your_Device. But I personally before I even started would find a device as close to yours as possible and look at its device tree and the files it has. What device are you building for?
shimp208 said:
I would start by checking out this guide for some better information about the required files and what is involved https://docs.omnirom.org/Porting_Omni_To_Your_Device. But I personally before I even started would find a device as close to yours as possible and look at its device tree and the files it has. What device are you building for?
Click to expand...
Click to collapse
I am porting for the BLU Energy X 2, and as a reference, I am using the device tree from the Infinix Hot 2. They are very similar.
NateDev473 said:
I am porting for the BLU Energy X 2, and as a reference, I am using the device tree from the Infinix Hot 2. They are very similar.
Click to expand...
Click to collapse
Since you found a starting point setup your device tree similar to the device tree of the Hot 2 you found.
shimp208 said:
Since you found a starting point setup your device tree similar to the device tree of the Hot 2 you found.
Click to expand...
Click to collapse
OK, I will do that and see how everything goes.
NateDev473 said:
OK, I will do that and see how everything goes.
Click to expand...
Click to collapse
Great! Best of luck let me know if you still have questions!
OK, so I've completed all the files and folders from the Infinix device tree, but I still am wondering a couple things. Since the Infinix device tree didn't have files like proprietary-files.txt, do I need that in my device tree, as mentioned by some guides? Also, since I'm making the vendor files as well, do I put all the lib files from my device, or just the files that are in the Infinix vendor files? I am also facing an error that says: No rule to make target device/.../kernel. Sorry for all the questions, I'm a bit of a noob Thanks!
NateDev473 said:
OK, so I've completed all the files and folders from the Infinix device tree, but I still am wondering a couple things. Since the Infinix device tree didn't have files like proprietary-files.txt, do I need that in my device tree, as mentioned by some guides? Also, since I'm making the vendor files as well, do I put all the lib files from my device, or just the files that are in the Infinix vendor files? I am also facing an error that says: No rule to make target device/.../kernel. Sorry for all the questions, I'm a bit of a noob Thanks!
Click to expand...
Click to collapse
Where did you find the files which has to be in folders like gps, camera etc. Did you find that folders in phone or kernel source or what?
Professor Woland said:
Where did you find the files which has to be in folders like gps, camera etc. Did you find that folders in phone or kernel source or what?
Click to expand...
Click to collapse
I'm currently using the files from the Infinix Hot 2, to see which will work and which need changing. Some of the files are on the device but they're not in the kernel source code, as far as I can tell. I'm currrently using the prebuilt kernel, but I've looked at other source code.
However, I get an error when running make. It will tell me I need an audio.cpp file.
That doesn't make sense though, because that audio.cpp file isn't needed if I don't make any changes to the device tree (so the straight Infinix device tree).
EDIT: Ok, so I used just the sepolicy file, and I got a different error around 9 mins in, about a twrp.fstab, so I will work to correct that, but atleast I don't have have the audio.cpp file anymore.
EDIT: I just added the rootdir folder, and it got past that error, so I won't be posting anymore updates until I find which folder gives me the audio.cpp error, and then I will not include that folder in the build.
After that, with all the other folders in, I will built it, and flash it on my device.
OK, so in the device tree, I have included the Bluetooth folder, the rootdir folder, the sepolicy folder and the wpa_supplicant folder. For the files I have included AndroidBoard.mk, AndroidProducts.mk, BoardConfig.mk, cm.mk, device_e050u_blu.mk, kernel, system.prop, vendorsetup.sh.
I ran make, and it completed successfully. I didn't make the flashable zip however, so the images are separate, but I can flash them through adb to test. But, if I want a flashable ZIP, is there a way to turn those .img files into a zip? Will the building of the flashable zip take less time if I already have built it once? Because I don't want to have to sit through 2 and a half hours again. I am assuming that from here, I put in the other folders 1 by 1 until I find which folder gives the audio.cpp error, I remove that, and then I build the ROM again. Am I correct on this process? Because the rest of the folders are asec_helper, audio, gralloc_extra, include, libbt-vendor-mtk, libxlog and overlay. Could someone explain to me what these folders do/enable?
EDIT: I ran make bacon and I am getting an error saying:
build/core/Makefile:1498: recipe for target '/home/nate/cm12.1/out/target/product/e050u_blu/obj/PACKAGING/target_files_intermediates/cm_e050u_blu-target_files-f63afd6f51.zip' failed
make: *** [/home/nate/cm12.1/out/target/product/e050u_blu/obj/PACKAGING/target_files_intermediates/cm_e050u_blu-target_files-f63afd6f51.zip] Error 1
#### make failed to build some targets (05:53 (mm:ss)) ####
Thanks
OK, so I solved the make error, but I get error 1 when I run make bacon. It says error 1 relating to a zip file, the name of the finished zip.
I built a rom for my device based on lineage oreo. So far it looks good. I want to do the following things and not sure how to achieve this, will keep working on it, but any tips are appreciated.
1. change the name etc of the ROM. Different generated name for the rom zip file. different name in settings->About phone after the install.
2. Add an existing apk to the code base so that its automatically installed. How do I make it removable (pre installed app, can be removed) or not-removable (pre installed app, can't be deleted.
3. Add sources for an apk to the code base so that it gets compiled and installed. Same question with removable/non-removable. I tried this with f-droid sources. Added a line for this to the local manifests. Sources get downloaded, but dont get compiled. I added a line for this to the PRODUCT_PACKAGES in common.mk (for the vendor tree) but I dont see anything related to f-droid in the build log or the out folder related to f-droid. App does not get installed on the phone.
4. Change settings for an app. i guess this would require modifying the contents of some file where the settings are stored. Is there a concept of a post install script where it can be taken care of.
Thats all I can think of now, more later. Thanx guys..