Hi,
I am looking for some guy in order to speedup the develop my project.
It consist of port most usefull features of CM, Omni, etc to AOSP.
The goal is create a stable, optimizied and maintainable ROM for daily use.
Minimum skills:
- Have a brain and know how use it
- Git
- Linux
- Java
- C/C++
Related
Let's say that I wanted to get into android rom development, what would be a good place to start to learn. I've downloaded several e-books about android development, but they all pertain to writing applications for android OS, not really getting into modding the OS itself. I suspect I'd need to learn about linux then translate that knowledge to android?
Anybody have any good places to start or good reference materials?
It appears that none of the cyanogenmod team is even going to do anything with the Captivate, they're all working on I9000 and Vibrant, totally ignoring the Captivate. So, I thought I'd get in there and try and learn.
Building Android from source - their own site is the best for instructions on how to build android: http://source.android.com/
Building Captivate requires downloading the sources, building the kernel using the build_kernel.sh after you've fixed the toolchain paths. Or you can just use the usual linux kernel building method that the script actually does underneath.
Then you need to build eclair (or froyo). Samsung has opensourced most of the code but not all so you need to figure out how to merge vanilla eclair source into Samsung's tree, and build it. There is a readme in the source from Samsung about what to change in the build files.
You're going to be doing a lot of googling . . . I haven't figured out all the details of the Samsung eclair build so you're on your own there. Maybe others can chime in.
-Atin
atinm said:
Building Android from source - their own site is the best for instructions on how to build android: http://source.android.com/
Building Captivate requires downloading the sources, building the kernel using the build_kernel.sh after you've fixed the toolchain paths. Or you can just use the usual linux kernel building method that the script actually does underneath.
Then you need to build eclair (or froyo). Samsung has opensourced most of the code but not all so you need to figure out how to merge vanilla eclair source into Samsung's tree, and build it. There is a readme in the source from Samsung about what to change in the build files.
You're going to be doing a lot of googling . . . I haven't figured out all the details of the Samsung eclair build so you're on your own there. Maybe others can chime in.
-Atin
Click to expand...
Click to collapse
Thanks. Thats what I'm talking about, a lot of what you said seems Greek to me. I'd like to learn how to do all that. I guess, just read a lot from the google source website?
My advice would be to first learn how to go muck in the linux kernel and the Android sources in general. The Captivate code has been hacked some by Samsung so it doesn't quite follow all the rules about where files are supposed to go (there is no vendor tree for example) but at least it is a start. The google source site is the best for instructions on how to do vanilla stuff that's not hardware specific. Google around for more specific instructions related to the particular problem you are trying to solve after that.
Building working stuff at this level isn't easy. Unless you are somewhat experienced or willing to spend a lot of time learning and making mistakes, I'd say leave this to people who have some experience at this level and come back to it when building for the Captivate is well understood and the knowledge has been distributed enough so lots of people can help you when you have specific questions (no one likes answering general "how to" stuff on a device specific thread).
-Atin
Hey guys, I wanna start a new "little" project and hope for some help from the one or the other.
I just realized, that noone until now really compiled a stock ROM for our device.
That means, we can't get a fully customized ROM. I mean Zeus ROM is close to it, but it's pretty restriced, to the typical "tweaks" like kernel, theming and so on.
So I thought of trying to compile the sourcecode. It's still compiling, but if I already look at the build.prop, it looks like it's not building for our device, although I followed LG's advices that are:
Code:
How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code (Android 2.3.4 gingerbread) from http://android.googlesource.com
(2) Overwrite modules that you want to build.
- Untar opensource packages of P970_BDop_GingerBread_v20s.tar.gz into downloaded android source directory
- And, merge the source into the android source code(gingerbread)
(3) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
$ ./build/envsetup.sh
$ make -j4
into the android folder
- If the android is built sucessfully, you will find the outputs in this directory,
"out/target/product/generic".
So far it looks and is pretty simple. But like I said, with the commands mentioned, I think it doesnt build for our device.
Had to bypass some errors, since I am using a more recent toolchains as LG seems to have used, but since goolge is my best friend, he told me what to do
Now how can we get this sourcecode compiled?
Do I have to start like rmcc did? And add these files/add the content he added?
https://github.com/CyanogenMod/andr...mmit/04b8b02f13c62239dad2884530ad07b9fe3ebd60
Dont wanna mess up my building environment and start over again, that's why I am asking.
When typing lunch, it only shows:
1. Emulator
2. crespo (I think)
3. some HTC device
4. one more
at least I cant pick p970.
Would be nice, if we could get that done, since it would probably also work for our hopefully soon coming ICS!
Then we could get a VEEERY good ROM for our already lil bit old device
Hope we can make it and I am sure we can
All recommendations are welcome.
About that, you need to setup the proprietary binaries for LGE to be able to setup P970 for lunch. Beside that, the prebuilt must be of the similar version.
Sent from my LG-P970 using Tapatalk 2
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Huexxx said:
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Click to expand...
Click to collapse
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
N00BY0815 said:
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
It would be CM7...
LG's ROM source code is close to nothing... only mods to non-proprietary stuff... there is NOTHING more. so CM7 sources + LG's source = CM7 source... CM7 has used LG's stuff for its project...
The way IMHO is:
- Take latest Gingerbread AOSP sources.
- Take a existent target (as Crespo) and duplicate all the needed stuff with a different name... as P970.
- Once you can build P970 (a Crespo ROM will be generated), modify all the stuff with vendor blobs from CM7 and proprietary files from LG's GB.
- A way to understand what you are doing is to take AOSP complete code... CM7 complete code, and compare the way both sources compile the same target, (Crespo...) to obtain the differences... Once you understand how change from AOSP to CM7 for Crespo, you will try to make the opposite from CM7 to AOSP for P970...
Regards.
have good luck
:fingers-crossed:
Good luck for your project...:good:
I've done some searching and found many dated and non-specific references on building AOSP for your device. I didn't even find anything referencing lollipop. I was wondering if somebody had written up some device specific instructions for the m7. I'm looking for information like pulling in the correct binaries and kernel source.
91ludesit said:
I've done some searching and found many dated and non-specific references on building AOSP for your device. I didn't even find anything referencing lollipop. I was wondering if somebody had written up some device specific instructions for the m7. I'm looking for information like pulling in the correct binaries and kernel source.
Click to expand...
Click to collapse
Which ROM are you looking for? I found the instructions for building CyanogenMod for the Nexus 6 to be helpful when I rebuilt CM7 for the original Droid Incredible. I don't see any reason it can't be extended to the M7 and lollipop--I can indicate the appropriate changes, if that's helpful.
wiki.cyanogenmod.org/w/Build_for_shamu
I'm just wanting to build straight from aosp with maybe a custom kernel source.
91ludesit said:
I'm just wanting to build straight from aosp with maybe a custom kernel source.
Click to expand...
Click to collapse
Ah. Well, I'm not an expert by any means, but I don't think it's quite that straightforward. The Android source released by Google has no support for any devices except Nexus devices. Various ROMs, CyanogenMod being the biggest, have created open-source device trees to support additional devices. In the source tree for the device that I built for (Droid Incredible), for example, there is code for "liblights", "libsensors", a kernel module, some firmware, some configuration tweaks for various system apps like Camera and Torch--and a configuration file for the kernel. So if you want to compile AOSP for your m7, you'll have to port all that code over to the AOSP tree.
You might find it valuable to try building CM12 for your device. If you can do that successfully, then you can start tweaking with the kernel config that CM provides to suit your needs. Building CM is also very well documented, and once you've done that, it's more clear how you'd go about trying to build AOSP, and you can use the stuff that CM has done to help you port to AOSP if you want.
Here's Google's information on building straight AOSP:
https://source.android.com/source/building-devices.html
Here are CyanogenMod's guides on building for m7 and tweaking the kernel config:
http://wiki.cyanogenmod.org/w/Build_for_m7
http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
Here is an XDA Developer guide to porting a device from one AOSP-based ROM to another:
http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code
Thanks for the info, that's what I was afraid of. I was wanting to build something like the Google play edition, but with all the latest security updates.
Hey fellas,
Currently I have CM13 compiled from source and its up and running for trltetmo (love it). I am just trying to see how other people are compiling toolchains and making them work. I have spent way too much time banging my head against the wall trying to get things running but I'm stuck using outdated sources and very buggy code...
Curious if:
- People have experience using SM and how they are updating it from source (osl from their manifest is non existent). Currently I can only find an outdated precompiled zip for SM found here.
- People have any experience using UBER and where is their source directory to pull updated code.
Currently I have several things where they need to be and if I can get some help applying a custom TC I may start to release optimized, minimalist, true (not jimmy rigged vzw files) CM13 zips.
NOTE: if it weren't for @fattire, @ZION959, @BotsOne none of this would be possible.
Hello! I've taken an interest in kernel and rom development, so I'd appreciate it if someone could give me tips and/or link/write tutorials that explains things about kernel modification (overclocking, bug fixing etc), custom rom making (how to add features, bug fixing etc).
Also is it possible to update/make a newer kernel from the source, like source is available for 4.5, would it be possible to update it to 4.6?
Any help/tip/tutorial is appreciated.
Ps: I don't know if this thread belongs here, as I'm new here.
Thanks, .