I am posting to ask for the license of ROM(s) developed by all ROM guru.
I know from this forum that there are many people making customized ROM, either from stock or AOSP. As I have been getting the source thru AOSP and compiled a ROM for myself, I am planning to share the ROM.
However, if I really plan to include those customized MODs and/or kernels in my ROM, is it legal? Do I need to follow any rules or regulations when sharing my ROM?
I really learn a lot here. Thanks for all of your help
The code you take from AOSP is from the Android Open-Source Project and is under Apache 2 license.
It is quite similar to the GNU GPLv2, anyway it is Open-Source.
This part fo the source code, from AOSP, must be under Apache 2.
The changes your made should also be under Apache 2.
But technicaly your code can be under any license.
So, you can do what you want, just respect the Apache 2 license, and about Mods, give credits and respect any special author's instructions.
Codes are mainly OpenSource.
Related
hi guys,in the past i made a rom for my wm 6.5 device ,now i want to develop custom ROM's for my Mini,what are the sites/topics that i must see? what are the fundamental things that i must know?how hard it is?is there a Kitchen like in WM?there are REPOS like in WM for specific phone DPI?who is the rom structure?
I had already talked about this in another post so im just going to copy paste it out of laziness:
Some links
Start by going through source.android.com for the general basics if you havent already.
Also, even though Google removed the PDK (Platform Developer's Kit) from the site, it has been mirrored on kandroid here: http://www.kandroid.org/online-pdk/guide/index.html
The stuff in the the PDK, although inadequate, is still very important and explains how to create the necessary makefiles to add to the build, configuring for a new market, etc. etc.
Also,
watch these two videos over here. These were very helpful in my ROM development:
http://www.youtube.com/watch?v=1_H4AlQaNa0
http://www.youtube.com/watch?v=rFqELLB1Kk8
Learn to use github. It is helpful for you to keep track of your changes as well as incorporate others works into your own.
http://help.github.com/
Finally, Cyanogenmod repos are your BEST friend. Almost all major AOSP ROM devs owe some sort of thanks to those guys who have done so much. If you want to check out some of the code changes and patches that you want to incorporate look here on their gerrit:
review.cyanogenmod.com
If you want to look at the other changes that are actually in the cyanogenmod builds, best to look at their git repos here:
https://github.com/CyanogenMod
I am still learning right now while I create my ROM but your welcome to PM me if you have any questions
Click to expand...
Click to collapse
As for kitchens, there are a bunch of them.
For theming, there is UOT: http://uot.dakra.lt/
For HTC based phones (+ some others), there is dsxida: http://forum.xda-developers.com/showthread.php?t=633246
For others, just search the chef threads.
If you want to learn true ROM development, dont use kitchens. Study, study, study from the links above and the source code. Learn to make custom modifications in code. This will give you a much deeper understanding of how everything works.
If you want to just edit, add apps, and repackage them, then kitchen will be easy and clean.
As to how hard is it? If you're gonna work with source and do significant changes, then it will be difficult (as documentation is slim to none) but very satisfying. Like cyanogen said in the other sticky, learn how regular android apps interact with the system. Create a few test apps and go from there.
Hope I helped
Hi. I've been thinking about how the phone/tablet manufacturers manage the android platform source code. In my case, I have a SE MK16a "Xperia Pro", for which SE only releases the Kernel source code, as most manufacturers do.
What I think, as most of the android platform is licensed under the Apache license, should the manufacturers release the platform modifications they make? For me, it would be interesting if I could rebuild some framework parts to customize my stock ROM, and I think that's one of the reasons Android is open source.
The reason to post this here is, I would like to know other people's opinion or experiences about this.
Thanks.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I'm looking for a ROM that is proprietary-code free as possible.
I know Replicant, but unfortunately there is lack of development and devices support.
I know that Cyanogenmod for example contains proprietary code, like Google Analytics. In addition, as I understand OmniROM created because of this Cyanogenmod's proprietary code.
How is it in terms of FOSS?
Any other recommendations?
Thanks
UP
UP
UP
Hello friends, I am writing so that together we will achieve something that will benefit us all.
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Click to expand...
Click to collapse
Source: official website of "Mokee open source" in the section about
This ROM is very good, delivers great performance gains on our devices, I personally used in my previous smartphone (Galaxy S2 i9100) and if not for spoiling that I still continue to use thanks to Mokee.
So now, this group has developed a community Mokee google plus (which I can not give the link, and that despite much I visit this forum for years, recently dared to enroll today, and rules are rules) You can find this easily by typing in google "open source community Mokee google plus".
In the section "Device request" please discuss who want open source Mokee for Xiaomi Redmi Note 2 and maybe if we are many, we consider and develop this excellent ROM for the device.
I and several others already did, but the more the merrier.
Cheers
I think that to create an open source rom, you should have access to the full mtk sources and model drivers, which is not the case.
gnazio said:
I think that to create an open source rom, you should have access to the full mtk sources and model drivers, which is not the case.
Click to expand...
Click to collapse
but a lots of device very rigorous with his privacy code have mokee (like Sony), maybe with something port from other device or other method, but i'm not expert, thanks for comment
Obviously the more the better.
If they are fully working!
I remember using the Mokee ROM on my galaxy s2 skyrocket. Brilliant ROM i hope we can get one for the Redmi Note 2.
My question is really simple: How can I make an unofficial port of LineageOS? I've read this, which is based on an article from the (now death) CM Wiki, but some files (e.g. the mkvendor.sh script) are in older CM repos/branches. According to what I've read, there's not a full guide explaining the porting process since every device has its own tweaks (I imagine that it's due to ARM's nature)
What I want to do: Port LineageOS (the latest version) to the Samsung Galaxy Ace 4 Neo SM-G136ML (codenamed vivalto3mve3gltn). However there's not a LOS port at the latest version for a similar device which I could fork, so this would be "from scratch" in some way. I've seen Lineage's android repository at github but idk what are those xml files (they are definitively not the source code of a whole OS) EDIT: I realized that I had to clone it with `repo init`
What I've done so far: Documented myself as much as I could, read about how to get the vendor files, firmwares, kernel sources (in fact I requested the kernel source code for the device to the vendor), build.prop, recovery.fstab, and recovery/boot images.
My skills: I have a lot of experience with the GNU/Linux OS and I know some Linux kernel hacking, in fact I'm used to compile kernels for the x86_64, i686 and armv7h arch'es (not the vanilla kernel itself, but the Linux-libre kernel, which is basically vanilla but without binary blobs) and also patch them, and test them, etc. Besides kernel-stuff, I know shell scripting, advanced use of git (git clone, commit, add, push, remote, fetch, diff, apply, and more), use Heimdall, install custom recoveries and ROMs, and some advanced (non-noob ) Android hacking (Idk Java, C nor C++, however)
I know that here at XDA we've very talented developers who have experience with this, and much more. The only thing I need is some guidance to help me in my way to contribute the FLOSS community, I say this because when I asked in the LineageOS IRC channel if there was an official or well documented and updated guide, step-by-step, tutorial to port LOS that I could follow, someone answered me "it's impossible to have something like this", but I believe that there's ppl here who can demonstrate me the opposite
Thanks in advance
(...) I requested the kernel source code for the device to the vendor
Click to expand...
Click to collapse
Here it is https://gitlab.com/Megver83/android_kernel_samsung_vivalto3mve3gltn