Related
Hhey anyone knows about cm for Mega 6.3?
Gesendet von meinem C6603
No one is coding?
Gesendet von meinem GT-I9205
In my years on this forum, I've seen more requests for CM to be supported on XX device than I could even begin to count. I want to clear up some common misconceptions.
The CyanogenMod developer team doesn't create CM from scratch. Rather, they take the code put out by Google, called AOSP (Android Open Source Project), and start adding all the awesome features we have come to love and enjoy.
Support for devices is handled by device maintainers. What does this mean? Well, let's back up a bit.
CM devs are consumers first. What this means is that they do not divide up devices among other developers, or assign devices like one would at a job. Developers work in their spare time without monetary compensation. Because of this, the developers are free to work on any device they choose to purchase.
Let's say a dev has bought fancy new device X. It is really sweet, but he wants CM on it, but there is no CM version currently available. He then goes through the trouble of taking the CM vendor and framework codebase (which in and of itself doesn't support ANY devices - that is what all the device trees are for) and then he goes and starts adding the code necessary to make CM work properly on his device. When it gets far enough along, he can then submit that code back to CM for inclusion into CM's github (where all the code for CM and devices are maintained). If that code passes the checks that the CM team has (minimal bugs and formatted properly) then the CM team will merge that code into its own device tree and add official support for that device. That developer has now become a "maintainer" for that device. For continued updates, that maintainer needs to maintain his code to make sure it works properly on his device when new CM code gets put out. If the maintainer's device breaks, or he/she upgrades, they may not be willing to maintain that device anymore, and if someone else doesn't step up, it could lose official support in CyanogenMod.
Now, what does this mean to you? First off, requesting anywhere in the CM forum, the CM Blog, or the Facebook/Google+/Twitter accounts for device XX to be supported is probably a waste of your time and anybody who reads said request. CyanogenMod does not work on device requests as there is no guaranteeing that a current CM maintainer is even interested in the device. Additionally, its not as simple as 'porting' code, the device trees must be coded from scratch and made to work with the AOSP sourced code and CM enhancements. This takes a large amount of time and effort, especially when the device's OEM fails to release the latest version of Android for it. Second, in hoping a worthy developer sees the post and decides to take up the project... well, that is probably just wishful thinking. Many developers do not like interacting with end users (too much finger pointing between both devs and users or anger directed at the devs for something working other than how the user expects - it happens far too often); because of that, many developers don't frequent the forum (or if they do, they only view the forums for the devices they maintain).
The best way to get a device official support is not requesting it from the CM team, but learning how to do it yourself or encouraging a maintainer of an unofficial build to submit their code for review. Many developers will work on unofficial ports on the xda-developers forum, so that would be the first place to check out. If there isn't any work currently being done, you can attempt it yourself. There is a pretty in-depth article in the wiki explaining a lot of the steps of porting a device (as the bottom of the wiki states, nothing can cover every single process of porting, but it is a really great start).
If you do feel so inclined to still post a device request, know that the CyanogenMod developer team is under no obligation to support your device. This is not a democracy and more replies/votes will not necessarily help get your device support. If you are going to submit a request, please submit them to the Device Requests forum to keep the clutter down in other forums
2SHAYNE
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
I found that...I don't want it to look like i said it cause I didn't... Just figured this is a good enough explanation. Thanx
2SHAYNE
Also if I had proper tools and spare devi e I'd try to build for us but that's hard to do. I hope it comes soon for the sake of our mega community
2SHAYNE
Also.... Pretty sure s4 mini has cm..... And our specs are the same.... Makes me sad
2SHAYNE
Yes, the S4 Mini does have CM 10.1 and 10.2. I've never heard of CM 10.3 though.
Help wanted:
Over the last few weeks we have been working feverishly at trying to make the switch from lollipop to Marshmallow. In addition, we have been trying to switch source from CM to Aosp. This has been a daunting task. We are working with a limited staff and are finding it to be a bit overwhelming. So why am I telling you this? Well frankly we have seen some great community builds of non supported devices being posted from all over the world. There are some talented folks porting our rom. Perhaps some of those folks may be willing to use their talents to help our cause? In the forums, we have seen some talented helpful users contributing to make OctOs better. Must be able and willing to develop and build for any/all devices we support. Don't worry about not having the device, we have plenty of awesome testers that will attempt to break whatever you throw at them lol. Also you must have your own build environment and stable internet. Serious inquiries only and please email us at [email protected].
Hey guys, we're looking for a jflteatt tester for 6.0MM . If anyone is interested email us at [email protected]. I'll get back to you asap as I'll be working today, or I'll have one of our devs respond if I can't. Serious inquiries only, must be willing to test builds as we post them & know how to restore your device & use hangouts. (Very rare you'll need to restore) but its a must you know how. We won't release or continue to build jflteatt w/o at least 1 tester. 2 would great. Thanks again. Team OctOS ?
Many of you are probably annoyed because OnePlus takes very long to release the nougat update. They took very long for the marshmallow update and they promised updates for 2 years from the release of the OnePlus Two. Nougat came out before the ending of this cycle. So a OnePlus Forums user (not me) started a petitionlike thunderclap campaign to show OnePlus and the world that this matter concerns many people. If you support this campaign that would be good for the future of our device and also for OnePlus' update behavior on future and current devices.
Link to the forum thread for further information:
https://forums.oneplus.net/threads/help-make-oneplus-care-about-its-older-customers-again.512493/
Link to the campaign:
https://www.thunderclap.it/projects/55301-promises-matter-oneplus?locale=en
I still doubt they'll do anything about 2 and X
MZO said:
I still doubt they'll do anything about 2 and X
Click to expand...
Click to collapse
I think the pressure could make them. Some well known android sites already wrote articles about this. And they actually said there will be nougat, but they refuse to publish the release date since a very very long time.
SUPPORTED :good: :good: :fingers-crossed: :fingers-crossed:
Once galactic stryder started to collected crowd funding to buy a new le max 2 and then also ordered it and then it now arrived because of some issues. Anybody can tell me what happened to the money of yours you donated? And why he is not developing? Just curious to know that!
Heyyo, he posted a while back that he has had stuff going on in life so it was delayed a few months for software development.
Tbh even once he starts it could be a few months before he has a properly working x2 build as he uses his own kernels with some stuff based on Darkobas (Oreo) and I haven't seen anything happening there either... So really who knows when we shall see some AOSPA x2 stuff.
Such is the way with crowdfunding anyways. We funded a device for him and it will take time for things to get done. I know I donated a bunch too but hey I am barely making progress on Oreo but I try with my limited software development skills and time.
He wrote to me that let max 2 "will be supported on our AOSPA 8 from April"
Let's wait for the guy solve his issues. Nobody forced us to donate. I am sure that he didn't run away with the LeMax2 :laugh: Any user should understand that developers are also people with jobs, family, etc. Heck, even to reply to xda Q&A takes time (thanks @ThE_MarD), so it's often to see that there's no answer from the dev to "why torch is not working" question or stuff like that.
Honestly speaking, even without him, the development of X2 is at a very good level by my standards.
I think we should also donate to infrag and all the others who worked really hard to fix the builds for this device.
Thanks to all for info
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
nope that's not correct bro recently he updated his profile and added le max2 and I can see some commits done in his lambda kernel so everyone cheers and hope for good
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
Forgive me, but it's a sad statement.
Actually, a passionate and skilled guy who did a good job with a very similar phone, offered to work on improving support for this device. I can't event think he needed another underpriced (because of lack of official support from manufacturer, bankrupt) smartphone
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
He is very active kernel dev for Le pro 3, so it wasnt like, hey lets give new phone to random guy.
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thanks for clearing situation
Nice to see you after long break, hope you like yours new device
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thank you galactic stryder!
https://forum.xda-developers.com/showpost.php?p=75925873&postcount=318
So I really don't know what's going on and what's happening behind the stage.
Obviously alonsoj636 decided to discontinue and abandon his greatly admired LineageOS builds from the past months.
I haven't found any notes or statements as to why he finally has decided to do so and I was not able to reach him on xda because he blocked PMs. If you read this, maybe you want to be so kind and give us some hints what's happened!
Anyway...
we, as the RM10 LineageOS community, have to face reality and that means: currently there is no LineageOS rom build and maintained by anybody. That either means sticking with old versions, changing ROMs/GSI or switching the phone completely.
While alonsoj636's versions are still working very well, they eventually become outdated sometime.
This thread should be used to coordinate discussions about future LineageOS development (if there is enough interest and people).
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Alright, so the cat is out of the bag on this one:
While I'm really happy that Alonso kept maintaining the ROM for a while, the reality is that he wasn't interested to go official anytime soon and kept being vague about it.
As for me, I'm building up the courage to do MPK99 recommendation and go with GSI. Apparently GSI works like old ROMs, and it doesn't nuke TWRP, so that seems nice.
Try GSI. It's perfect.
MPK99 said:
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Click to expand...
Click to collapse
I'm pretty aware of that, however all new ROMs are tagged as development on this xda forum so I used this wording.
I think all 3 mentioned options are valid.
I could build it myself, however the time is the problem. Finding someone else building lineage in the future seems to be difficult. The past showed there aren't as many people interested and even less have the time and skill to build it.
GSI sounds like a wonder bag to me. while it's great to always have the latest updates, it might lack of the features LineageOS had for years. (i think of things like os-level online permission per app (wifi/cell), permission center, etc.). you can workaround that with 3rd party tools maybe, but it's cumbersome again.
Also GSi still sounds like a bit of an unpolished OS for this specific phone, with some kind of bugs and lack of features (compared to LOS). it's everybodys own decision to put priority on either that or on latest updates, though.
I might as well give it a try sometime, but I'll need enough spare time for experiments, so it won't happen soon.
my hopes are low, but maybe someone will step up and also build new LOS roms in the future.
Zirila said:
however all new ROMs are tagged as development on this xda forum
Click to expand...
Click to collapse
They're all namesake
Zirila said:
it might lack of the features LineageOS had for years
Click to expand...
Click to collapse
Lineage is lineage whether it's a gsi or a cusrom
Zirila said:
still sounds like a bit of an unpolished OS
Click to expand...
Click to collapse
Those are false claims. You need to use it before committing on it.
Zirila said:
I'll need enough spare time for experiments, so it won't happen soon
Click to expand...
Click to collapse
There's nothing to experiment, as user's experiments are logged on my thread. You can follow them. I'm myself a gsi user for an year long btw. As for the time, it'll take not more than 10 minutes. And I've laid out post configuration & fixes on the thread which'll be another 5 minutes.
well what I meaned with unpolished is what I've red in your thread about bugs like -don't touch screen while booting- etc. I haven't installed it so I solely say that by reading these posts.
and experimenting is synonymous with taking time to clean flash and reinstall everything again while learning and fixing problems with new OS/roms/GSIs.
I'll have a look sometime and I'm grateful there is progress.
Atleast I was transparent about the bugs on it.
Zirila said:
bugs like -don't touch screen while booting
Click to expand...
Click to collapse
Not touching the screen 'while booting' is an easy fix & you won't often reboot your device while work in the first place.
Zirila said:
learning and fixing problems with new OS/roms/GSIs
Click to expand...
Click to collapse
Just the procedure would be new. Rest of it would be your same old preferred AOSP derivative (lineage).
you did well. nothing to complain.
the more I dip into the topic the more I think it might be worth a try. don't count the time till I can focus on it, it'll take a while. but it sounds more and more promissing and the overall experience might as well get even better with time.
regardless of the GSI option, let's still have this thread and discussion opened for the case of some future LineageOS-CustomROM progress.
I'm very sorry for my abrupt decision to kill Lineage.
some personal and family problems made me think that I couldn't continue with this (nothing too big, don't worry... typical family fights)
after some messages I decided to get back to the action.
I will upload a new build with improvements once I unlock my bootloader (not very soon) as my RN10 is my only source of internet and I can't use the Mi Unlock Tool.
Thread will remain locked until the new build is done.
Thank you for your understanding and sorry for my bad steps ....
Regards
Thanks for the informational update
no worry, we are all human. as software engineer and project maintainer in troubled times it's often better to just keep calm, step back for a while, let the projects delay or freeze, that won't really hurt anyone. and then check back later to make a judgement if the project(s) really have to end.
It wasn't that bad for us either, in the meanwhile some of us learned a bit more of the GSI option which might also be a viable way to run LOS in the future. But everything has up- and downsides.
I'm glad we get to see a few more updates for the LOS custom rom.
lineage is alive again
new update is up ... waiting for shadowstep to open the thread again
Changelog
* Switch to SkiaGL Threaded
* Optimize package manager dexopt properties
* Kernel upstreamed to v4.14.295
* Kernel built with Clang 15.0.2
* Enable config_avoidGfxAccel
* wifi: Disable TDLS offchannel
* Disable few debug services
* Don't enable iostats
these are only for LineageOS 19.1
No changes for 18.1
Lineage OS for Mojito - Browse /Lineage at SourceForge.net
LineageOS for Redmi Note 10 (mojito/sunny)
sourceforge.net
Deleted.