Petition: team up and ask samsung-mobile for sourcecode
Help us to get needed sourcecode from samsung-mobile to get all hardware bits working on aosp based roms like cyanogenmod.
http://www.change.org/petitions/sam...t-achieve-full-potential-of-purchased-devices
thanks
by this time, you may want to consider changing the caption / headline
Related
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
green2005 said:
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
Click to expand...
Click to collapse
It's actually fairly simple... an "official" ROM is one that is authorized, and often supported by, the development team of that ROM and the device is considered an "officially supported device".
But since the source code for these ROMs is open source, anyone can build or compile them for their device or another device that isn't officially supported. The ROM is not supported by the development team, but by the ROM maintainer/builder only. These types of builds that are either not officially supported devices, have modified the source code outside of the original developers guidelines, or not authorized by the development team are called "unofficial". They may even be by the same maintainer as the official version, but they modified (perhaps used a different toolchain) from the original guidelines for the ROM and it cannot be considered official any longer.
Really, it's boils down to: is the device supported and authorized by the core ROM development team... if yes, it's official... if no, it's unofficial.
Android Original Development is supposed to be for ROMs, kernels, and other projects that are completely original by the author, or authorized originals... Cyanogenmod/LineageOS is a good example of this... ROMs like Resurrection Remix are not considered "original" because they are based on Cyanogenmod, thus they just go into the Android Development section.
If in doubt about what the forum groups are for, read the sticky posts in each group.
Thanks now it's more clear
Hi all (sorry for my bad language , i'm french.),
I'm looking for members to modify LineageOS rom and make it a custom rom for our taste. I'm looking for developers who can add features in the rom
I have a Discord server to chat live.
available here:
https://discord.gg/w2ZD4gU
i need help, someone with android architecture to help me solve some problems please.
Hi Folks,
I'm trying to port B2G to my moto g3. I was referring to this doc (https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Porting_B2G_OS/basics). However some of the things mentioned in this doc are not clear to me. Could you please help me with the below issue.
I'd like to build the AndroidKernel from source. So where should I include the below lines? Is it in this file?
https://github.com/LineageOS/android_device_motorola_osprey/blob/cm-14.1/rootdir/etc/init.target.rc
HTML:
on early-init
start ueventd
import /init.b2g.rc
Also if I understood correctly. building the kernel from source doesn't require to unpack , edit the init.rc file and repack the kernel from the device. Could you please confirm this?
Thanks,
Arun
Hi Arun,
I totally understand your frustration with this. You'd like to contribute to the Servonk project but first you need to port B2G to your phone or buy a new phone. Since the only other supported phones are the Z3 compact and Nexus 5, both of which are still relatively expensive secondhand, you want to use your Moto G3 which means first porting B2G to it.
So, I think there are two options you have:
1. Port direct from the AOSP code
2. Port from the CM12 code.
As Gerard said in telegram, porting from CM to B2G was never finalised so may actually require more work. However there may actually be more people here who can help you since people seem more familiar with CM than AOSP (in general, I know some people are very knowledgeable in both).
I see you've posted in the AOSP 7.1.1 kernel thread. Unfortunately, for the Servonk project you currently need a Lollipop based build, so 5.x AOSP kernel or CM12.x.
It might be worth asking a mod to move this thread into one of the development sub-forums.
As you know, this is the limit of my knowledge, but I really hope you find some success, if would be great if you could contribute to the Servonk project.
Your last option is to use the desktop build of Servonk, based on Glutin instead of Gonk, but I understand that you really want to get Servonk working on your phone.
Best of luck
It would be great if any developer shares his/her work procedure about building any ROM for Oneplus 6 (enchilada).
A lot of new ROMS are there in the market and for people like me who want to learn custom ROM developement and have only this phone at the moment to test, not a lot of resources are present in the web market to help us.
Therefore, it's my humble request to any DEV who can share with us the procedure for building custom ROMS like from scratch. This can include, getting ROM sources, device tree, kernel tree or vendor tree to be used and other modifications. It will help the community a lot. Discussions can be made based on various issues people encounter and it would be appreciated a lot.
Closed at the OP's request.
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
(t.me) is a good place, they use SDK and Android Kitchen etc.
JaswanthTeja said:
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
Click to expand...
Click to collapse
Custom ROM sources require that the stock source code be made available to the public by the manufacturer/carrier of the device. If the stock source code for a specific device has not been made available to the public, developers can not create custom ROM source code for that specific device. Developers use the stock source code to create the custom ROM source code and then ROMs are built using the custom source they created. I think that is the answer you were really looking for. You want to know how the source code itself that the ROMs are built from is created. You aren't asking about the fruit that comes from the tree, you are asking where the tree that bears the fruit comes from. Am I right?
The only way to get custom ROMs on devices that do not have stock source code made available is to port custom ROMs from a similar device with the same architecture that does have available source code and custom ROMs made for it.
OldNoobOne said:
(t.me) is a good place, they use SDK and Android Kitchen etc.
Click to expand...
Click to collapse
I don't think that is what they are asking.
Droidriven said:
I don't think that is what they are asking.
Click to expand...
Click to collapse
Yeah, I Want To Know About Android Arc
JaswanthTeja said:
Yeah, I Want To Know About Android Arc
Click to expand...
Click to collapse
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Droidriven said:
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Click to expand...
Click to collapse
cool