I have installed the ROM resurrection remix (7.1 nougat), I would like to know how to install or put a custom image in the header, already comes with some images and some apps add others, but not to add my own image, thank you who help!
I have the same question.
This is the starting point : https://github.com/omnirom/android_packages_apps_OmniStyle
This is being used to provide custom headers. There are apps to extend the list or you can try to add your own, but it's not like putting it into a folder and done. You need to add them to some xmls and what else...
Related
hello there,
i have a GT-I9100 phone best known as the Galaxy S II International, and i'm very fond of messing around with the custom firmwares and stuff. i like to test every nightly that comes out from CyanogenMod, so i'm almost always installing new firmwares, and i'd like to carry on some small updates that i do to each firmware.
however, there is a problem. an update.zip would be useful for static files such as replacing the bootanimation.zip and adding the init.d scripts i want. however, i also like to edit the build.prop files, that are changed each nightly, to show the correct date and other minimum details.
following that, i'd like to know if there's a way to not replace the build.prop file, but just edit/add some lines into it through some script that could go inside the update.zip.
thank you.
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
Anyone think it's possible to implement the manager system from nexus mod manager or something similar to a recovery. For example, have it keep track of the mods you install and the files it changes and put an option to remove it where it removes the files that were editing and replaces them with the files that were there prior to installing the file? If it help nexus mod manager is open source allowing to view the source code and I believe all that is handled under the NexusClient under ModManagement. If someone can implement this it will make it a lot easier to manage the mods we install on top of the roms since the only way to remove mods currently is making a backup prior to flashing the mod or by dirt flashing the Rom on top and reinstalling other mods.
Here's a link to the sourcehttp://goo.gl/PFnqI0
Sent from my HTCONE using Tapatalk
luigi311 said:
Anyone think it's possible to implement the manager system from nexus mod manager or something similar to a recovery. For example, have it keep track of the mods you install and the files it changes and put an option to remove it where it removes the files that were editing and replaces them with the files that were there prior to installing the file? If it help nexus mod manager is open source allowing to view the source code and I believe all that is handled under the NexusClient under ModManagement. If someone can implement this it will make it a lot easier to manage the mods we install on top of the roms since the only way to remove mods currently is making a backup prior to flashing the mod or by dirt flashing the Rom on top and reinstalling other mods.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
So you are simply stating having a program that automate a backup of the files yyou change? So instead of having to do it manually, as soon as you change something it makes a backup..
lacoursiere18 said:
So you are simply stating having a program that automate a backup of the files yyou change? So instead of having to do it manually, as soon as you change something it makes a backup..
Click to expand...
Click to collapse
Similar. The way I see this working is to create a class that adds this support and have it create a temp file of sorts with everything that was editing and a list of files that were created and allowing it to backup the files that were replace so it can put them back when u decide to remove the mod and delete the extra files that were created. Doing this would make it easier for developers to implement this into the scripts used to install the mods and possible having installations split between roms and mods, having the developers define it in the script and if undefined have it follow the default install which should be roms. Defining roms and mods could possibly be done through if-else statements such as adding InstallAsMod or InstallAsRom on the first line of a script and on the recovery have it check if it says InstallAsMod or InstallAsRom on the first line and if neither have it follow the InstallAsRom code which could be an exact copy of the way the recovery currently works. Though those are just my thoughts with my very basic java knowledge, maybe someone else with more insight can give a better method. Also having something like a extra menu in the recovery that displays the installed mods and having the uninstall/removal process there. The problem I see with this would be with rom updates, they will make changes to the files causing issues with the uninstall option if the files where changed through the rom update.
Sent from my HTCONE using Tapatalk
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..
I'd like to create a TWRP flashable ZIP of my phone meant for public release so I'd like to hide any information specific to my phone or self. As far as not installing a bunch of apps or backing up data that's obvious but what I'm unsure about is the process of creating a ZIP file instead of those folders that TWRP creates. How would I go about doing that?
This is basically what I'd like to do:
Backup my own stuff
Flash stock ROM and make customizations to the interface, possible minor debloat, installation of a few useful things, etc...
Release a flashable ZIP -- essentially just like flashing a custom ROM except it's just the stock ROM with customizations like ad blocking and interface changes, etc...
The idea is similar to @ChazzMatt posting images of his settings but involves more things and in a prepared format for flashing. It's sort of like a "lazy" version of creating a ROM.. where you're just modifying some things and doing all the work that would normally take a lot of discovery and time to do then releasing that.