So im a not so newbie here and have picked up a fair knowledge of all the basics etc for my sgs2. Now its time to learn how to create my own ROM. I have played with dsixda rom kitchen and feel reasonably comfortable with that, with sucess' and failures lol.
Can anyone guide me to the software, links to good threads that will help get me started. Self learning from there on.....
I take it you have checked out this thread?
http://forum.xda-developers.com/showthread.php?t=1272270
killall said:
I take it you have checked out this thread?
http://forum.xda-developers.com/showthread.php?t=1272270
Click to expand...
Click to collapse
yes ive use the kitchen and wouldnt say maximised its full potential but am looking to get more involved. Thankyou
I would suggest you download a public ROM repository to start working with, such as CM7 for example, to be able to touch any aspect of the ROM as well as learn the structure, compiling options, etc.
Check Cyanogen Wiki the page of Building from Source to get the full repo for it.
The source should build without problems, then once built, you can start tweaking and adding/removing things from it. This would be a port of CM7, but there are many other public repositories to start from, but CM7 has the most documentation about it.
If this is too hard for what you're looking for, I don't really know if there is an intermediate step between ROM Kitchen and this one...
AzureusPT said:
I would suggest you download a public ROM repository to start working with, such as CM7 for example, to be able to touch any aspect of the ROM as well as learn the structure, compiling options, etc.
Check Cyanogen Wiki the page of Building from Source to get the full repo for it.
The source should build without problems, then once built, you can start tweaking and adding/removing things from it. This would be a port of CM7, but there are many other public repositories to start from, but CM7 has the most documentation about it.
If this is too hard for what you're looking for, I don't really know if there is an intermediate step between ROM Kitchen and this one...
Click to expand...
Click to collapse
thanks for your reply, i will have a look into this and see how i get on.
thanks again
Pardon my ignorance. Just for fun and learning, I am willing to build a custom ROM from scratch for Sony Xperia-L from Android AOSP. But, even after going through a number of tutorials, following are the issues which are yet unclear to me:
How to obtain Xperia-L specific drivers to intergrate it into my build. Please note that unlike a few tutorials has suggested, I don't want to start from CM ROMS. I want to do it from 'scratch'
I have downloaded Open source archive for build 15.3.A.1.12, 15.3.A.1.14 and 15.3.A.1.16. It contains two top level directories: kernel and platform. What are these two for? Given the size of AOSP so large, I presume this archive does NOT contain full source for Xperia-L stock ROM. Am I correct to reason that?
Without using kiddie-approach, e.g. different ROM kitchen, what is the recommended approach to for a beginner to master the art?
Hi,
I wanted to ask this in other subforum, but this is my first post and I don't have permission there. Do you have a guide to recommend for creating custom roms?
I know a lot about Linux, I can compile kernels, patch, I know C a little. I programmed couple of Android apps, in Java and Go, so I guess I have some basic knowledge.
What do you guys do, with what source do you start? Is it a stock android source but you modify kernel and modules or you need first to find exact source for that phone?
For example, I own a Lenovo A560, and would like to try build custom rom for it. What would be the first steps?
Thanks,
Milan
Since Android is open source, I decided to learn code and make my own ROM as a fun project. I found a guide on Android Authority on this topic. But they said I need a nexus device to flash my rom to test. I have a spare Samsung device. Is it possible to use this device for testing?
0
Seppppx said:
You don't gave to had a nexus device. The guide is pretty old. Googles first Pixel phone was launched 10 days before the video, so they still recommended a nexus.
Google nexuses had a device tree made for them and all the tools needed to build Android for it were available. Google Pixels do the same developments wise.
I don't know if you want to learn how to build a ROM like AOSP or LineageOS or you want to make your own custom ROM.
But you can find a tutorial on a YouTube channel called AlaskaLinuxUser. I would with his "where do I start" video. He explains a lot about what you should learn first.
The Android authority guide is extremely oversimplified.
Click to expand...
Click to collapse
Thanks
You can use ANY device to test a rom, granted you have the device/kernel/vendor trees. Start off by building something like lineage, and then modifying stuff in the lineage source to make your own custom rom. The guide on androidauthority is way too simplified and only goes into the basics. Learn cherry-picking features using git
We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 - Sony Developer World
developer.sony.com
The one downside is Ubuntu...I would be down to start building roms...but the problem is I'm on windows 11...and prefer it...
Ainz_Ooal_Gown said:
The one downside is Ubuntu...I would be down to start building roms...but the problem is I'm on windows 11...and prefer it...
Click to expand...
Click to collapse
WSL?
unicastbg said:
WSL?
Click to expand...
Click to collapse
WSL??
What is Windows Subsystem for Linux
Learn about the Windows Subsystem for Linux, including the different versions and ways you can use them.
docs.microsoft.com
Code:
sudo apt-get purge ...
The instructions aren't off to a good start.
kevinmcmurtrie said:
Code:
sudo apt-get purge ...
The instructions aren't off to a good start.
Click to expand...
Click to collapse
To be blunt as a rock, you should be doing this on a clean install or inside a container anyways. I'm surprised Sony is not providing us with one.
UsernameNotRecognized said:
To be blunt as a rock, you should be doing this on a clean install or inside a container anyways. I'm surprised Sony is not providing us with one.
Click to expand...
Click to collapse
That's clear from step 1, but not necessary if Sony had created the build correctly. Modern build environments may coexist without issues.
Even apt-get is rather outdated.
kevinmcmurtrie said:
That's clear from step 1, but not necessary if Sony had created the build correctly. Modern build environments may coexist without issues.
Even apt-get is rather outdated.
Click to expand...
Click to collapse
The Guides are copy-paste since quite a time now. You basically just need to change the Tag each time You want to sync the Code. Anyways, sudo apt install works well on Ubuntu while some Parts cant be installed and need to be corrected like zlib1g-dev:i386 which is zlib1g-dev. WSL2 works fine on My W11 install. Just give this a go:
GitHub - bostrot/wsl2-distro-manager: A GUI to quickly manage your WSL2 instances
A GUI to quickly manage your WSL2 instances. Contribute to bostrot/wsl2-distro-manager development by creating an account on GitHub.
github.com
You will like it if You want to keep Windows...
what is the use of all these instructions if there are no developers who have made and supported at least a normal firmware based on android 12
Sakuma_Eitarou said:
what is the use of all these instructions if there are no developers who have made and supported at least a normal firmware based on android 12
Click to expand...
Click to collapse
There are many people involved working on it. It takes times and they need help with logs and testing since there are many supported devices. I am working myself on it with A13 and its a pain in the a** right now... Many small issues and missing stuff here and there. We are also talking about bugs like no Mobile Data + No Wifi and non working Cameras and such... It's a great Project but lacks Users and support...
Miustone said:
There are many people involved working on it. It takes times and they need help with logs and testing since there are many supported devices. I am working myself on it with A13 and its a pain in the a** right now... Many small issues and missing stuff here and there. We are also talking about bugs like no Mobile Data + No Wifi and non working Cameras and such... It's a great Project but lacks Users and support...
Click to expand...
Click to collapse
certainly lacks people and support because the community is too small due to the high cost and unpopularity of the phone. To begin with, I would like to see a completely completed firmware like this https://sourceforge.net/projects/ancientrom/files/gsi/V6.4/ and only then firmware based on a13
maybe one day there will be one fully working ROM with a fully programmable assistant button and a working Sony camera. as well as all the advantages of custom ROM
Sakuma_Eitarou said:
maybe one day there will be one fully working ROM with a fully programmable assistant button and a working Sony camera. as well as all the advantages of custom ROM
Click to expand...
Click to collapse
I can surely tease, there is Something comming this Year. Android 13 2019-2022 Xperias
Miustone said:
I can surely tease, there is Something comming this Year. Android 13 2019-2022 Xperias
Click to expand...
Click to collapse
in general, it doesn't matter, because official Google builds are 5 years behind amateur builds like crdroid and other teams. In my opinion, Android 12-13 looks gray, boring, not beautiful, sad, no transparency effects, colored notification icons. It feels like there are some idiots at Google who can't come up with anything worthwhile, or at least standardize what is already available in custom ROM. For example, it annoys me that the usual aosp assembly is empty, there you can't even adjust the height of swipes of control gestures
Miustone said:
The Guides are copy-paste since quite a time now. You basically just need to change the Tag each time You want to sync the Code. Anyways, sudo apt install works well on Ubuntu while some Parts cant be installed and need to be corrected like zlib1g-dev:i386 which is zlib1g-dev. WSL2 works fine on My W11 install. Just give this a go:
GitHub - bostrot/wsl2-distro-manager: A GUI to quickly manage your WSL2 instances
A GUI to quickly manage your WSL2 instances. Contribute to bostrot/wsl2-distro-manager development by creating an account on GitHub.
github.com
You will like it if You want to keep Windows...
Click to expand...
Click to collapse
would you want to update the aosp build guide as a how to do for xda?
i would certainly be interested in stock aosp build.
"Now you are ready to build AOSP images that can be flashed to a device. To do this, you have to point out your specific device and then start building the images."
this my current blocker. how would i point out the specific device? as i understand the command in the given step ( step5 ) it requires a source. that source is not specified in the builöd instructions or i didn't find them