I know it's a bit too much to ask but considering the fact that we have an excellent development community is there a possibility of getting android o on Onyx? developers pls reply ...just a question
LineageOS sites listed yhat it will support OnePlus X by developing LineageOS 15 (Android 'O'). Which means developers are still supporting onyx and will support onyx.
http://www.lineageosrom.com/2017/03/los-15-list-of-devices-getting-lineage.html?m=1
sundhar88 said:
LineageOS sites listed yhat it will support OnePlus X by developing LineageOS 15 (Android 'O'). Which means developers are still supporting onyx and will support onyx.
http://www.lineageosrom.com/2017/03/los-15-list-of-devices-getting-lineage.html?m=1
Click to expand...
Click to collapse
Generally speaking, I wouldn't trust sites like that. There is no proof provided in that.
I will give you a short answer, no I do not believe you will see Android O on onyx or on any device using the 8974. Why? Google has been pushing aside legacy bits of code. As a matter of fact, the latest shift was with NetD, breaking WiFi on Onyx. It took us (PA) several days to isolate the issue, and begin a revert. That is only one case though. The thing is, this will continue to happen, and we will have to continue reverts so as to support legacy devices, or backport sketchy code that should not be shipped. Even getting N running was a struggle, and Paranoid was considering dropping the 8974 altogether because the source has been removed from AOSP for it entirely.
Proof:
https://github.com/AOSPA/android_system_netd/commit/1c2066bb498d0daee9e85d64e2a9afdad10d275d
Reverting that means that we do not pass CTS, and with O, CTS is a requirement from everything I have seen. We can bypass CTS through removing the checks from verifiedboot so ultimately reverting that is the route we took, but we wish we could have maintained CTS compliance. Again, there is a dire tradeoff for supporting legacy devices... But O introduces more ways for that check to be tripped outside of verifiedboot.
Now, with O we also see new APIs that require Vulkan and all of that good stuff. It is going to be really hard to support. Possible, but not optimal.
I am going to give a response for PA; we probably wont support O, but on the slight chance that it is possible without too many hacks, then I will do what I can to support it.
I'd assume the same response from Lineage, but they are Lineage. We keep modifications like that to an absolute minimum. Their aim is to support as many devices as possible.
CertifiedBlyndGuy said:
Generally speaking, I wouldn't trust sites like that. There is no proof provided in that.
I will give you a short answer, no I do not believe you will see Android O on onyx or on any device using the 8974. Why? Google has been pushing aside legacy bits of code. As a matter of fact, the latest shift was with NetD, breaking WiFi on Onyx. It took us (PA) several days to isolate the issue, and begin a revert. That is only one case though. The thing is, this will continue to happen, and we will have to continue reverts so as to support legacy devices, or backport sketchy code that should not be shipped. Even getting N running was a struggle, and Paranoid was considering dropping the 8974 altogether because the source has been removed from AOSP for it entirely.
Proof:
https://github.com/AOSPA/android_system_netd/commit/1c2066bb498d0daee9e85d64e2a9afdad10d275d
Reverting that means that we do not pass CTS, and with O, CTS is a requirement from everything I have seen. We can bypass CTS through removing the checks from verifiedboot so ultimately reverting that is the route we took, but we wish we could have maintained CTS compliance. Again, there is a dire tradeoff for supporting legacy devices... But O introduces more ways for that check to be tripped outside of verifiedboot.
Now, with O we also see new APIs that require Vulkan and all of that good stuff. It is going to be really hard to support. Possible, but not optimal.
I am going to give a response for PA; we probably wont support O, but on the slight chance that it is possible without too many hacks, then I will do what I can to support it.
I'd assume the same response from Lineage, but they are Lineage. We keep modifications like that to an absolute minimum. Their aim is to support as many devices as possible.
Click to expand...
Click to collapse
Wow, I'd never thought it was that hard supporting legacy devices... Thank you developers! If y'all don't update us to O, we completely understand.
Related
Why is there such alot more development and forum activity on for example the Xiaomi Redmi phones than on this one? The p9000 got excellent hardware for a great price but the community is really small somehow and the software is still buggy? How come? Do you think its still worth to wait for more activity and responses from developers for this phone or is it a "dead cow" already and better to swap to another brand to get support from developers on for example CM or RR?
furchtlos76 said:
Why is there such alot more development and forum activity on for example the Xiaomi Redmi phones than on this one? The p9000 got excellent hardware for a great price but the community is really small somehow and the software is still buggy? How come? Do you think its still worth to wait for more activity and responses from developers for this phone or is it a "dead cow" already and better to swap to another brand to get support from developers on for example CM or RR?
Click to expand...
Click to collapse
Development for this device is far from dead, we have a stable device tree for building custom ROM's, CM and RR ROM's already released, a fully source built TWRP and work on custom kernels is just beginning. That's a lot more development already than an awful lot of devices see in their entire lifetime.
I would rather say it has just begun. Development for this MTK chip is not a matter of course and the outcome so far is pretty exciting. This opens the way for other devs who work on other devices with the same chipset. It's just that many devs simply prefer Snapdragon which leads to higher dev count on those devices, faster bug fixing etc. I am pretty excited what the future brings not only for our P9000 but MTK devices in general as far as flashing and development goes.
Development is dead? What gave you that impression? For starter this phone already has a working twrp recovery. That is more then some Chinese phones get in their whole lifetime. Kernels is the area of development next and elephone has been kind to release the source code for the phone. Again more then most developers even bother with.
well, it got twrp,root and xposed working. More than some name brand phones that stop official updates after a year.
But i admit it is easier to update my old nexus 4 with cm downloader. Just click the update notification and latest cm gets installed.
It is also getting nougat in November hopefully
mangoman said:
well, it got twrp,root and xposed working. More than some name brand phones that stop official updates after a year.
But i admit it is easier to update my old nexus 4 with cm downloader. Just click the update notification and latest cm gets installed.
Click to expand...
Click to collapse
That's because Nexus 4 is an officially supported device by CM.
It's very difficult for MTK devices in general to get official CM support because we have to patch some things in the framework to make camera, RIL (mobile data) etc working.
The official stance is that these things should be done in device tree as no proprietary code is allowed in CM framework.
Initially when our patches were submitted to CM Gerrit they were rejected because of this, Leskal is working on minimising the patch work needed and getting more of the generic MTK code accepted on Gerrit.
Not helped by the fact that MTK themselves aren't helpful or willing to support developers as it doesn't suit their replace and force upgrade business model. Technically how they operate and their refusal to release official development tools or code is a violation of the open sources nature of Android. But google has yet to do anything serious about it. As far as I know, any code we have is from reverse engineering and leaks.
Android-UK said:
Not helped by the fact that MTK themselves aren't helpful or willing to support developers as it doesn't suit their replace and force upgrade business model. Technically how they operate and their refusal to release official development tools or code is a violation of the open sources nature of Android. But google has yet to do anything serious about it. As far as I know, any code we have is from reverse engineering and leaks.
Click to expand...
Click to collapse
Not true, I've met up with MTK engineers at DevCon and they do actually encourage development, they just seem to lately be wanting to protect their HAL's and drivers which as pointed out on the XDA portal article about this is sort of ridiculous. But then again it's proprietary code and not under the GPL so whilst we can say it's stupid we can't really contest it, it's their choice.
The code we have is completely official and not gotten from reverse engineering.
Jonny said:
Not true, I've met up with MTK engineers at DevCon and they do actually encourage development, they just seem to lately be wanting to protect their HAL's and drivers which as pointed out on the XDA portal article about this is sort of ridiculous. But then again it's proprietary code and not under the GPL so whilst we can say it's stupid we can't really contest ot, it's their choice.
The code we have is completely official and not gotten from reverse engineering.
Click to expand...
Click to collapse
I have seen many a leak before. But OK they support developing but at the same time they don't help provide any decent tools for troubleshooting or development.
Android-UK said:
I have seen many a leak before. But OK they support developing but at the same time they don't help provide any decent tools for troubleshooting or development.
Click to expand...
Click to collapse
Why do they need to? There's already great tools around for that, I know Qualcomm certainly used to provide a package for debugging the lower system levels but it wasn't widely available as the lower levels of the device booting process are not needed to be modified outside of OEM labs and manufacturing.
The lowest level we need is kernel debugging and the kernel already provides that via last_kmsg and desmsg etc, all other tools are already available as part of ADB, logcat etc. There are also a plethora of other tools readily available.
I would call it pretty dead now Well, if not dead then dying.
Let's hope for a Christmas special
Anyone else see this:
https://9to5google.com/2016/09/19/zte-is-working-to-bring-an-official-cyanogenmod-rom-to-the-axon-7/
Yes, it's been discussed in the CM dev topic.
xtermmin said:
Yes, it's been discussed in the CM dev topic.
Click to expand...
Click to collapse
What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed?
jim262 said:
What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/development/cyanogenmod-13-a2017u-t3457410/page10
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
jim262 said:
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
Click to expand...
Click to collapse
From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device.
Only for USA.
rikin93 said:
Only for USA.
Click to expand...
Click to collapse
Correction: Only for unlocked bootloaders, as it will not be officially signed by ZTE.
xtermmin said:
From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device.
Click to expand...
Click to collapse
Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different.
jim262 said:
Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different.
Click to expand...
Click to collapse
There's a huge difference between CyanogenOS and CyanogenMod behind the scenes though. Like you said, CyanogenOS is in-house, but most importantly it tends to include bloatware, especially now that Cyanogen the company is owned by Microsoft. And since it's closed source, people who want to develop custom ROMs will still have no access to the sources that would speed up development. Plus, if there are bugs or features that people want to implement, they can't, and have to wait for Cyanogen to release them. This also means that things such as security patches will have to wait for official rollout by Cyanogen.
Cyanogenmod, however, is open source, not controlled by Cyanogen the company at all, bug fixes / features can be added and addressed by the community, security patches can be applied to nightlies quickly, etc.
jim262 said:
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
Click to expand...
Click to collapse
It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source.
If they did offer open source at least it would alleviate concerns on the Chinese state-sponsored company reputation
Finally, the best hardware of 2016 and all it needs is aosp love... I hope this helps to spur more development or makes it easier for our fantastic developers at XDA.
From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way.
Do we have any ETA on this ?
I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/
rczrider said:
It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source.
Click to expand...
Click to collapse
Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released.
Araewuir said:
Do we have any ETA on this ?
I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/
Click to expand...
Click to collapse
The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support.
jim262 said:
Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released.
Click to expand...
Click to collapse
Okay.
xxBrun0xx said:
The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support.
Click to expand...
Click to collapse
I feel like the last phone I owned with that level of support was the Nexus 4.
rczrider said:
Okay.
I feel like the last phone I owned with that level of support was the Nexus 4.
Click to expand...
Click to collapse
One Plus released everything before the phone even hit the market, so there was development for the One Plus 3 from the beginning. The Axon, in my opinion, is a very good device, but ZTE has limited development of this product. It is almost as though they are perfectly happy being an iPhone/Apple wannabe.
japzone said:
From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way.
Click to expand...
Click to collapse
Which is never a good thing. Especially when they admit they don't care.
As a Sprint subscriber I'm locked out of the Axon7 until Sprint stop being dickbags about BYOD, which most likely will be never. If that changes, I'll probably buy an A7 if CM actually appears in a timely fashion since Shamu is being dropped by Google very shortly.
...but dumping code on the community and expecting them to make it right is massively annoying at best. It is exactly what Google does with AOSP....The Nougat AOSP is seriously broken and takes a ton of effort to fix enough just to get to compile. The stock AOSP GApps packages are all in varying stages of brokenness as of now. Sure they release the source, but what you get doesn't compile without a ton of forensic work.
Nougat has been on Nexus for over a month (minus Shamu)...and it is not going well.
Hey and first of all: I am not a coder or do know anything about android development.
Treble arrived with Android 8 and it was praised like it would be the holy solution. Essential said it got P running on Ph-1 within a day (weekend...?). When I read all the P GSI threads it seems like nothing has really matured. People still report ****loads of bugs and not working hardware.
Wasn't this the whole achievement with treble? To separate the hardware drivers from the software?
Could someone please explain to me in simple words why it seems (to me) that not much has changed?
thanks!
Wrong section
I guess it's because of few ****ty manufacturers closed sources for specific hardware and not including them in Treble vendor.
Treble only promised compatibility where Vendors comply with VTS. If they make closed source drivers with special cameras or special sensors, bugs are bound to happen.
However if you see the other side, a **** load of ROMs were able to boot without needing any dev assistance like in my case, Xiaomi mi6 was able to boot Android P GSI and other treble compatible GSIs by users WITHOUT any help from devs. This is HUGE.
The minor niggles regarding cameras or sensors or other things is NOT a huge deal. A relatively weak developer can even take up from there and try to fix up things.
Lastly, give treble some time. This was the first time it was tested and it worked. Not completely, but i would say better than expected. In time it will help us get Android 9.1 9.2 etc with minimum fuss.
You would understand if you tried porting roms or building them from source. It NOT easy.
OnePlus has numerous models (like my Nord N10) that are still waiting for Android 11. Other models have beta versions of Android 12, but OnePlus has wholly and completely botched their rollout of Android 11.
I'm sure that THOUSANDS of OnePlus users would gladly pay for a stable ROM.
Would love to see Pixel Experience or Lineage take the lead on this!
mkeaton1967 said:
OnePlus has numerous models (like my Nord N10) that are still waiting for Android 11. Other models have beta versions of Android 12, but OnePlus has wholly and completely botched their rollout of Android 11.
I'm sure that THOUSANDS of OnePlus users would gladly pay for a stable ROM.
Would love to see Pixel Experience or Lineage take the lead on this!
Click to expand...
Click to collapse
No doubt mate, I would definitely pay for a Lineage ROM...
I mean, I even contacted the OP support team showing them how pissed and disappointed I am due to the lack of OxygenOS support for the N10, but they answered with a completely generic and useless email...
However, there's already a Pixel Experience ROM for OP N10: https://download.pixelexperience.org/billie
But I dunno, isn't Pixel Experience way more Google-dependent than OxygenOS? I usually avoid Google stuff.
EDIT: Well yea, I just noticed that ROM was discontinued, my bad.
lbsilva said:
No doubt mate, I would definitely pay for a Lineage ROM...
I mean, I even contacted the OP support team showing them how pissed and disappointed I am due to the lack of OxygenOS support for the N10, but they answered with a completely generic and useless email...
However, there's already a Pixel Experience ROM for OP N10: https://download.pixelexperience.org/billie
But I dunno, isn't Pixel Experience way more Google-dependent than OxygenOS? I usually avoid Google stuff.
EDIT: Well yea, I just noticed that ROM was discontinued, my bad.
Click to expand...
Click to collapse
Appreciate your feedback. It’s a chicken or the egg conundrum.
I’ve shared feedback directly with both Lineage and Pixel Exp that there is an opportunity here. Some twerp moderating the Lineage forum (not a developer) sent me a grumpy reply saying “read the forum rules you can’t ask for a ROM for your phone”. I explained to the dummy that I’m not talking about just my phone, rather it is a huge opportunity for nearly every model of OnePlus phones.
We need to help folks at Lineage or Pixel Exp understand that yes these custom ROM projects are things they work on for fun — but that they are also supported thru DONATIONS. So, consider developing ROMs for models where there are known customer dissatisfaction issues. Maybe even require a minimum donation of $15 or $25 if you have published a stable ROM that you are committed to for ongoing support.
mkeaton1967 said:
Appreciate your feedback. It’s a chicken or the egg conundrum.
I’ve shared feedback directly with both Lineage and Pixel Exp that there is an opportunity here. Some twerp moderating the Lineage forum (not a developer) sent me a grumpy reply saying “read the forum rules you can’t ask for a ROM for your phone”. I explained to the dummy that I’m not talking about just my phone, rather it is a huge opportunity for nearly every model of OnePlus phones.
We need to help folks at Lineage or Pixel Exp understand that yes these custom ROM projects are things they work on for fun — but that they are also supported thru DONATIONS. So, consider developing ROMs for models where there are known customer dissatisfaction issues. Maybe even require a minimum donation of $15 or $25 if you have published a stable ROM that you are committed to for ongoing support.
Click to expand...
Click to collapse
I think many developers build and develop custom ROMs in order to practice or just to have fun, not for money. What I think you're proposing is turning what is a fun hobby for many of the developers into a sort of job, which I think is a little unreasonable. This is probably the point where most developers would stop having fun and cease development altogether. I think letting developers pick whatever devices they want to develop for would be for the best. The only thing we can do is wait or send a device their way in hopes that they pick up development. Also, there are already Pixel Experience and LineageOS ROMs for the N10(I'm using Pixel Experience right now and it's pretty stable). If you're feeling extra adventurous, there is a guide to flash GSIs from the GitHub Wiki here.
Generic123. said:
I think many developers build and develop custom ROMs in order to practice or just to have fun, not for money. What I think you're proposing is turning what is a fun hobby for many of the developers into a sort of job, which I think is a little unreasonable. This is probably the point where most developers would stop having fun and cease development altogether. I think letting developers pick whatever devices they want to develop for would be for the best. The only thing we can do is wait or send a device their way in hopes that they pick up development. Also, there are already Pixel Experience and LineageOS ROMs for the N10(I'm using Pixel Experience right now and it's pretty stable). If you're feeling extra adventurous, there is a guide to flash GSIs from the GitHub Wiki here.
Click to expand...
Click to collapse
Thanks for sharing your point of view. Agreed 100% that these are volunteers who don’t do it for money. Just pointing out that there’s an opportunity for both because of how OnePlus has handled the rollout of Android 11. The OnePlus 9 is part of the Android 12 Beta, but the N10 and other models are still waiting for Android 11.
My goal is just to create awareness of an issue. Given that most custom ROM developers focus on a couple of phone models, they might not be aware of the issues that OnePlus has had. Someone can still be a custom ROM developer on the side for the fun of it, but at the same time pick devices where there is a need. It might increase donations — a way to subsidize the fun.
I held off on installing Pixel or Lineage on my N10 because both mention issues with adaptive brightness — didn’t know if that meant that brightness was randomly changing or if that means it just doesn’t adapt and stays at whatever you have it set on.
mkeaton1967 said:
Thanks for sharing your point of view. Agreed 100% that these are volunteers who don’t do it for money. Just pointing out that there’s an opportunity for both because of how OnePlus has handled the rollout of Android 11. The OnePlus 9 is part of the Android 12 Beta, but the N10 and other models are still waiting for Android 11.
My goal is just to create awareness of an issue. Given that most custom ROM developers focus on a couple of phone models, they might not be aware of the issues that OnePlus has had. Someone can still be a custom ROM developer on the side for the fun of it, but at the same time pick devices where there is a need. It might increase donations — a way to subsidize the fun.
I held off on installing Pixel or Lineage on my N10 because both mention issues with adaptive brightness — didn’t know if that meant that brightness was randomly changing or if that means it just doesn’t adapt and stays at whatever you have it set on.
Click to expand...
Click to collapse
Thanks for the calm discussion. From your perspective, I can see how looking at all of these OnePlus devices and their lack of recent updates has created a huge void that could be easily filled with custom ROMs. The N10 is no exception; only 1 major android update and that's it, which is obviously a big bummer. I think some developers are aware, but might just be waiting for the "promised" updates to actually occur, slow as they are. I personally think the slow deveopment progress of the N10 relative to other OnePlus devices is most likely because this phone is on the more boring side, and most people have marked it off as budget garbage. Concerning Pixel and Lineage: auto brightness just doesn't work at all, and other than DT2W , both are pretty stable(as indicated by my last post).
I love you both
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.