Looking for someone to explaining how to use github and integrate the latest changes to code to a already current existing cm rom. Not completely sure how to do it since I am not doing it from the ground up
Related
i got it as a secondary device for cheap price. any ideas on playing around with the software or else?
On ROM development
Alvin Owen said:
i got it as a secondary device for cheap price. any ideas on playing around with the software or else?
Click to expand...
Click to collapse
Hello,
always a pleasure to have an enthusiast joining the ranks.
You may want to check out the ROM development (the whole platform OR a kernel alone). Some links for you to start with
[Sony Open Device Project](https://developer.sony.com/develop/open-devices/) - this would be the starting point for anyone wishing to deal with the Android software; provides the guides for building full fledged AOSP and mainline kernel
[Sony Xperia developers Github](https://github.com/sonyxperiadev) - the repository for all the code necessary for AOSP and kernel; it is a "wiki" for further development steps; issues are discussed in [https://github.com/sonyxperiadev/bug_tracker]
[Sony AOSP builds with some additions](https://github.com/SonyAosp) - the AOSP code repository with forked sources from XperiaDev Github and with some additions that make the builds more usable (TWRP as a default recovery, OpenGApps already included, etc.); a great resource for a deeper dive into the intricacies of the building-from-source flow; can be used to compare with the barebone AOSP from the official XperiaDev and learn some insights
[LineageOS Wiki](https://wiki.lineageos.org/) - an enthusiast may want to build a Lineage OS instance for the device on his own, the wiki is a great start.
You also might want to get familiar with the followings as a references:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763 - an XDA complete guide to AOSP building
https://forum.xda-developers.com/general/xda-university/literature-reading-getting-aosp-t3268211 - a collection of references for further insights
https://review.lineageos.org - LineageOS Gerrit platform for a better understanding of the build flow from the perspective of commits
https://github.com/omnirom/Docs/blob/master/Porting_Omni_To_Your_Device.md - a guide to porting an OmniROM to a given device; may be used as another reference to better understand the buidling flow
https://www.aicp-rom.com/ - AICP project home; another source of information for AOSP porting
https://github.com/AndroPlus-org - a reference for kernel development
Happy coding!
Hi, is there any chance to get ROM, that works with 10.3.4.0 PFGQUX and has source code available?
I would like to get manifest, kernel source and build instructions to get the published package. Even official releases often miss per-device sources. Downloading all the repos is impossible.
Background: I would like to make minor edits to ROM here-and-there, just for experimentation, maybe push it back if it improves stability. But it is completely broken nowadays.
Hi guys,
I'm trying to build an AOSP Custom ROM based on Android 10 and some cherry-picking for My Motorola one power(chef). For that, I need some answers.
Can I use the source tree from other ROM developers (like this one ) without making any changes. At the end of the linked thread, you can find the Device tree, Kernel tree, Vendor tree.
Can I use Motorola kernel found here
I'm new to ROM development btw new to programming too
I meant source tree means Device tree, Kernel tree, Vendor tree.
Help me in this I'm circling various thread for the last two days
Hello,
I am new to this, and this is my first post. I have tried finding the most suitable place to ask this, please tell me if there is a better place my questions.
I am currently trying to build lineageOS 17.1 for my Xperia Z. I have previously built lineage 15.1, which used to be officially supported, but this is my first time trying myself at an unsupported release.
I have followed the steps on the official build guide up to the the breakfast command step. I know I need to include manifests for the device tree and kernel, and thought I could simply use those made available by lineage from the 15.1 and 16.0 releases, and could add a revision="lineage-xx.x" tag accordingly. I am attaching the .repo/local_manifests/roomservice.xml which I am now using.
My problem: When running the breakfast yuga command I still get an error because it queries the lineage-17.1 branch of the LineageOS github repository. I don't understand why this is happening. isn't the explicit use of the revision="lineage-xx.x" tags in my manifest supposed to tell breakfast to not use the default lineage-17.1 branch? I am including the complete error log bellow (there are other errors there, but now I am more interested in finding a solution to this current problem).
As mentioned in the error log attached, one can set the ROOMSERVICE_BRANCHES environment variable to use other branches as backup, and this would solve the problem, but I don't understand why I should have to use this since I am explicitly mentioning which branch I want to use in my roomservice.xml.
Thank you in advance.
Hello, I work on a custom aosp rom for A21s based on android 13. Where I can put the magisk source code in the aosp code tree. I want to pre root that rom.
This question would be better asked in the Magisk forum. I'll move your post there.
However, I found this with a Google search, also this. However it's entirely possible that Magisk has outgrown this...