Hello,
I want to become maintainer for Lineage OS for specific device (I will buy the device to maintain).
Could someone plz explain me the process of becoming the maintainer and pre-requisites for it?
I had a look at teamoctos/join-our-team/ but it will be helpful if someone explains all those steps in it.
--
Thanks
I'm not sure about this but however:
First of all you will have to build device tree for that device (I guess that device isn't supported at the moment, if is than you can contribute to that repo on github via pull requests and wait for them to approve change) and that device tree works without lethal bugs. Also you'll need kernel that won't make you much troubles because manufacturer probably published sources (they had to). And when you make it work than you can try to conntact them about joining team, if they accept new devs, because I read somwhere about how to make CM support device officialy they mention only they support devices they own, they not mention anything about joining team if I remember well. It's best that you conntact them and ask I'm sure there is way for that.
alpesh.valia said:
Hello,
I want to become maintainer for Lineage OS for specific device (I will buy the device to maintain).
Could someone plz explain me the process of becoming the maintainer and pre-requisites for it?
I had a look at teamoctos/join-our-team/ but it will be helpful if someone explains all those steps in it.
--
Thanks
Click to expand...
Click to collapse
Unless a specific thread states otherwise (which will provide you with the individual or location to do so), the XDA Forums isn't where you request this.
Regarding the Official LineageOS, though, the XDA Forums isn't where you request this either, here's the only location (at this time) to where you can find what you're looking for.
1) Go to the following link:
http://wiki.lineageos.org/faq.html
2) Scroll down to the following question (without quotes):
"My device is not officially supported, but I’d really like to give LineageOS a try. Can you support my device?"
3) It is there that you'll find the information you're looking for as well as the E-Mail address to where you can send them the information.
Good Luck!
Sent from my SCH-I535 using XDA Free mobile app
Related
Hi all Desirian Guru,
I am not sure this is the right place to bring this stupid question, but if you, the operator, found it is wrong, please move to where it should be. I would like to create or develop, if I can, my own custom ROM for fun and share. Could anyone here kindly point me what steps I should take, what the prerequisites I should have.
Appreciate you guys so much if those tools are supported on my Ubuntu.
and on windows too!
Same sort of thread made before: http://forum.xda-developers.com/showthread.php?t=817699
Might help
Start here, if you are intending to build from the AOSP source:
http://source.android.com/porting/index.html
http://source.android.com/source/git-repo.html
Get the source code from here:
http://android.git.kernel.org/
There is an unofficial "vendor" from devoferreria for the htc bravo board here:
https://github.com/defer/android_device_htc_bravo
The cyanogenmod wiki has a load of excellent info on it, including compiling your kernel:
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
If you are looking to mod a SenseUI rom there are guides around here that explain how to change the framework. That is a different art ... use a wider forum search and you should find them.
TheGost1233, stOkes,
thanks for your advise.
You guys rock.
Dharam's Kernel Development Tutorials
Since many of the S2 Kernel Developers have moved on or will be moving on to the Galaxy S3, I feel we need more developers for the S2. No offence to those who have moved on, even I would have done the same if I could afford one
Anyways, there will be many people who will have the knowledge of coding and stuff, just wont know how to build kernel's and all...
So here I present the Kernel Development Tutorials for the Galaxy S2. It will be similar for many other devices and so you can refer the same also if you are developing for any other device
The thread will be similar to my previous tutorials for the Galaxy 3, but based on MOD's for the S2.
I do not present myself as an expert of things, there are many great developers for the device including codeworkx, chainfire, gokhanmoral, simone201 and many many others which I am just skipping for the time being. Credits for their work will be provided as and when refered to.
I am also learning stuff myself, and so I maybe wrong at many places. I would request other developer's to keep a look on this thread and help out me and others whenever required. You guys have better knowledge, and it is a great thing to share the knowledge.
I will explain everything Step by Step.
If you got time to learn/develop join in.
If you get some step working and a fellow developer cant get it, please help each other by answering everyone's doubts.I cant reply to each and every query always.
Most of the code is to be run in the terminal. So I wont be mentioning to Open terminal every time.
I would like to thank marcellusbe who was the first one to make a proper custom Kernel for Galaxy 3, who taught me how to build a kernel, and also lot of other help
Note:
Please do not post useless messages.
If you dont know coding, please learn that first.
Do not flood my inbox with PM's. I will not respond to PM's regarding Kernel Development. Please post in the thread, so that everyone can learn.
[*]I AM NOT RESPONSIBLE IF YOU HARDBRICK YOUR PHONE, DOING ANY OF THE FOLLOWING STEPS
A request to all the people, please do not vote down this thread directly. It will take some time to build the tutorials step by step. If you have any doubts, then this thread will be similar to http://forum.xda-developers.com/showthread.php?t=1186409
I have got many requests to do a similar series for the S2, and so I am doing it.
This series will also be posted at www.androidnova.org - Checkout the website for latest Android News, Reviews and other cool stuff
Step 1: Setting Up The Build Environment
Installing Ubuntu.
1. Download Ubuntu x64 from http://www.ubuntu.com/download/desktop
2. Install Ubuntu directly or as a Virtual Machine ( I prefer direct installation)
3. If setup is Virtual Machine, Please dedicate enough RAM and processor for the Kernel to build fast, else it will take ages
Logging In As Root
1. When Ubuntu first boots, login with the username and password you mentioned while installing.
2. Open Terminal
3. Use following command.(Always the code after $/# is the one to be used. The one before that just specifies [email protected]:~)
## Anything after ## is a comment by me.
Code:
[email protected]:~$ sudo passwd
[sudo] password for dharammaniar: ## Enter password which you used to login.
Enter new UNIX password: ## Enter Password for root(it can be same as your prev password)
Retype new UNIX password: ## Re-Enter Password for root
passwd: password updated successfully
[email protected]:~$ su
Password: ## Enter the root password
[email protected]:/home/dharammaniar#
4. Once you get the last line as above means you now have root access.
5. Now logout from this user and login with username as root
6. On starting Terminal now, you should get
Code:
[email protected]:~#
Setting Up Build Environment
1. You should always be running as root.
2. Go To System->Administration->Synaptic Package Manager
3. Search for ncurses-devel
4. Install libncurses5-dev.
5. Download the toolchain. You can find it in the AOSP Source. I will also upload it soon enough.
Downloading Source
Downloading The Source
1. Download the Update4 Source from http://opensource.samsung.com/ or https://github.com/CheckROM/DK_S2_ICS_KERNEL/tree/5ec9752c34cedf3e8df9e887ecad6db9337de927
2. Download the initramfs from https://github.com/CheckROM/DK_S2_ICS_INITRAMFS/tree/d85b2201b79588e70387d3df0ffd2f83d741c4ac or maybe request some developer to post how to extract initramfs from stock samsung kernel. Even I am trying to figure that out...
(If any developer is reading this, and can help out, We would be grateful)
3. Create a folder named S2.
4. Inside that have 2 folders, 1) Kernel 2) initramfs
5. Kernel folder should have the source e.g. arch, drivers and all
6. initramfs folder should have the files init.rc and stuff
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Last Reserved... I will make use of these posts as and when required, so request the MOD's not to delete any of the above posts
Sure thing i got all the time i need. I was waiting for someone explain this xD
Nice to see this post. .Sir,I have send you PM if you don't mind please see it .
Really nice iniciative
Good luck !
Setting Up The Build Environment is done...
Checkout first page...
Awesome mate that is what i was looking for!
I really appreciate this
this will be the hugest tutorial in know.
but very helpfull for some peoples.
rly nice
Can I follow this tutorial (codes and everything) with mint 13?
Cristiano Matos said:
Can I follow this tutorial (codes and everything) with mint 13?
Click to expand...
Click to collapse
I think it should work, but cant guarantee...Try it and let me know
Dude, it's really nice. But one question. After that, are we going to have a brick wave? I think that unexperienced people like me will have some trouble when trying to build. Your tutorial will be brick safe if we follow all steps? If yes, I will try to do something.
Ics opensource update 4. is believed to be safe,so people will be "brick-safe".
This thread will be handy for disscussions when we get ICs successor,and samsung presents us a new "virgin" kernel source.
Also,u can find 6 toolchains in this repository- https://github.com/sakindia123/Android_Toolchains
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
madde on Fairphone Forum said:
Well there already is a recovery file for the fp1 + fp1u by chrmhoffmann up and running. The MTK6589 source code is kind of released and there has been a lot of work on the android code by the omnirom project, which might come in handy.
Should be definitely manageable to build and try out Firefox OS on the FP1. UnfortunatelyI'll just don't have the time to really dig into that. Maybe someone with a bit more experience can give it a shot. I'd love to see and try out the result...
Click to expand...
Click to collapse
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
I'm very interested by a portage of Firefox OS to the Fairphone
Don't have enought time to test for now, but I stay connected
Newluck77 said:
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
Click to expand...
Click to collapse
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
madde- said:
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
Click to expand...
Click to collapse
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Porting#Create_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Newluck77 said:
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US...reate_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Click to expand...
Click to collapse
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
madde- said:
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
Click to expand...
Click to collapse
No haven't been able to work on this.
I still have no idea, where and how to build this configuration tree. Do you have advice on this?
Thank you, Stefan
Fyi, a build is now available. As a new user on XDA, I can not post link here (what a ****ty rule), but check bug 1139642 on bugzilla and search Fairphone on the Mozilla Developer Network (MDN) to have more info.
Wrong phone (FP1(U) vs FP2)
The build, you are referring to, is for FP2, not for FP1.
A Firefox OS for FP1 could possibly be built using the source by @chrmhoffmann: http://forum.xda-developers.com/fairphone/orig-development/rom-fairphone-fp1-kitkat-4-4-2-t3243623
What is the proper way to request features or report bugs for a given ROM (e.g. Xiaomi Mix 2). I saw a maintainer name was listed but there's no way to contact him.
olalonde said:
What is the proper way to request features or report bugs for a given ROM (e.g. Xiaomi Mix 2). I saw a maintainer name was listed but there's no way to contact him.
Click to expand...
Click to collapse
If you go to the following LineageOS link...
https://download.lineageos.org/chiron
... at the top of the page (under the words "Builds for chiron"), select the "Device info" and it takes you to the following link...
https://wiki.lineageos.org/devices/chiron
... scroll to the bottom portion of that page and the listed "Maintainers" reflects "@mikeioannina" as the Official Lineage Team Maintainer for your device.
Fortunately, this individual has the same member name, as follows, on XDA as well.
https://forum.xda-developers.com/member.php?u=3839575
With that stated...
The only thing that I can guide you to is the following Official Lineage Link that reflects a way to either Contribute and where to ask for support.
https://www.lineageos.org/community/
You now have all the information on where/how to contact the Lineage Team and the individual via XDA and the above link.
I hope that I had explained this okay via text...
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Ibuprophen said:
If you go to the following LineageOS link...
https://download.lineageos.org/chiron
... at the top of the page (under the words "Builds for chiron"), select the "Device info" and it takes you to the following link...
https://wiki.lineageos.org/devices/chiron
... scroll to the bottom portion of that page and the listed "Maintainers" reflects " @mikeioannina" as the Official Lineage Team Maintainer for your device.
Fortunately, this individual has the same member name, as follows, on XDA as well.
https://forum.xda-developers.com/member.php?u=3839575
With that stated...
The only thing that I can guide you to is the following Official Lineage Link that reflects a way to either Contribute and where to ask for support.
https://www.lineageos.org/community/
You now have all the information on where/how to contact the Lineage Team and the individual via XDA and the above link.
I hope that I had explained this okay via text...
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Thanks, it did help a lot. I'll try to create a forum post here and @ mikeioannina.
How to install twrp from official TWRP App
after rebooting just wait for the black screen, don't panic, it's the boot process
The TWRP.img You gave is Compiled By me for realme C11/12, Since realme C11/12/15 ( mtk Edition ) are same it worked in C15 & I know About that, Please try to Give Credits to original Owner of the Compiled ROM/Recovery, I've verified md5 checksum too, its same, Edit The post with proper credits, Thanks
@bass_deso THREAD CLOSED and the formerly attached twrp.img removed.
It seems you haven't credited the original developer of the recovery that you posted. Even if it had been your development TWRP is licensed under GPLv3 i.e. you were required to provide a link to your source.
Please advise the moderaors team (best via the report function) to re-open the thread when ready to credit the devloper of the TWRP and to mention where you obtained it from. If the original location does not obtain a link to source you'd be required to provide that link.
XDA Forum Rules (excerpt):
...
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or to a Moderator. We are here to help!
...
Click to expand...
Click to collapse