I would like to pass along some of my knowledge that can be extremely helpful to know.
I would like to point out the value of the Official Lineage Wiki.
The link, below, has a list of All the links to the Content, within the Wiki, to include the various information for all the devices that, so far, has had any type of LineageOS releases:
All Content for LineageOS
Now I'll point out just some of the device specific information within that Wiki link specific to your issues.
First) Within that Wiki link, Just locate your device beginning with the words "Install Lineage on".
Second) Within the page that you had located, i would like to highlight a specific step with the words "(Optional): Root the device by installing the LineageOS su add-on or using any other method you prefer."
Finally) Just follow the instructions and be sure to pay attention to include that specific step i had pointed out above.
Locating Lineage Help and Support
---------------------------------------------------------
If you have any issues (and I'm sure that many may run into something) then go back to the Wiki All Content link above and you'll find many other links. Some of the titled include (but, not limited to) the following:
1) Logcat
2) LineageOS Contributors
(Highlighted below)
3) Frequently Asked Questions
4) How to submit a bug report
ETC... ETC... ETC...
Final (and important) highlight
--------------------------------------------------
A specific highlight I'd like to bring to your attention is the "LineageOS Contributors".
The Contributors link is a list of ALL the individuals that encompasses the Lineage's Development team.
The list is all broken down by categories and subcategories.
The Device specific developers, also known as "Device maintainers", are listed by their specific device they're responsible for the development of.
Lastly, i would also like to point out that the LineageOS Contributors link also lists individuals that are higher on the chain of responsibility.
Some are known/listed as:
1) Trusted Reviewers
2) Committers
3) Developer Relations Managers
4) Requesting LineageOS for your device
ETC... ETC... ETC...
Now I hope that passing this along was helpful to everyone and I do wish you all the best of luck!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
-----RESERVED-----
It looks like this thread is more of an FYI and doesn't seem to be active at all so I'll just close it...
Thank you for your time and understanding!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Related
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
Hi
I hope this is the correct area for this question?
I am having a go at building crackling for the Wileyfox Swift (1). I have set up a Unbuntu machine for this purpose as per the instructions on the Lineage website.
The problem I am having is downloading from git.
All goes well for a while, but then I start seeing -
Fatal: Not a git repository: /home/Ubuntu/android/lineage/.repo/projects/external/guice.git
The last folder and file in that string vary.
I have tried git init but that doesnt help.
What I am doing wrong?
Regards
Tubster
Tubster said:
Hi I hope this is the correct area for this question? I am having a go at building crackling for the Wileyfox Swift (1). I have set up a Unbuntu machine for this purpose as per the instructions on the Lineage website.
The problem I am having is downloading from git...
Click to expand...
Click to collapse
Here's just a handful of Guides available on the forum and I believe that one or more of them will be helpful for you. Don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=2814763
https://forum.xda-developers.com/showthread.php?t=1801690
https://forum.xda-developers.com/showthread.php?t=3179331
https://forum.xda-developers.com/showthread.php?t=2195858
https://forum.xda-developers.com/showthread.php?t=2320007
https://forum.xda-developers.com/showthread.php?t=3551484
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thank you for those links :good:
Unfortunately only one of them mentioned the problem I have, but it had a solution that didn't apply for me.
My problem isnt the setup (I think), as I have copied exactly the instructions on the lineage website.
Most of the source does download, but there's a few dozen areas where it fails with the above metioned error.
Regards
Tubster
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
Is there any way to add the ability for the developers (topic starters) to create a template for every post for members to respond with on their topics?
For instance, when members post to the topic 90% of the time it is a "this does not work", "this is broken", "I didn't read the install instructions but I still want to complain".
It would be incredibly helpful to everyone (to the members that constantly read that but want to still help anyway, ie. me and especially the actual developer for the ROM).
I've seen some devs post in the OP a "template" that members need to copy and paste into their post for a bug report. It's followed maybe 20% of the time. But many don't read the OP so it's still kinda useless there.
Something like github, most gits have a template when posting a bug report. Or something like this here:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
follow all OP instructions:
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (adb log/observations/frequency of problem/last version it worked on/etc) as needed:
Click to expand...
Click to collapse
I shamelessly copied that from the LOS topic here and added a few extras. But that template there (a template that any topic starter could make specific for their ROM) would be fantastic if it could be a template for every reply, basically forcing every poster to fill it in if they have a bug report. I know if I was developing ROMs that would make me muuuch happier to read replies.
Because as it is now, it's pretty depressing I would think for them (the devs) to constantly not see logs or any info other than "this don't work" and that's it (and guessing if they even followed 20% of the instructions). That is no help whatsoever. It would even help other members with the same problem, they could say to themselves "oh I'm using the same custom kernel and didn't wipe...hmm" then maybe they would be able to solve it without the dev wasting time looking into it when it's not even the ROM's bug (maybe it's the custom kernel, etc.).
Summary: a reply template the topic starters could make for their ROMs would go a long way for everyone involved on here.