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
You're a power user. Can the Xiaomi Redmi 4X keep up? Rate this thread to express how "healthy" the development scene is for the Xiaomi Redmi 4X. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
XDA_RealLifeReview said:
You're a power user. Can the Xiaomi Redmi 4X keep up? Rate this thread to express how "healthy" the development scene is for the Xiaomi Redmi 4X. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
Click to expand...
Click to collapse
Release kernel source so we can update here status about development
Without Source Code, it's almost Impossible to Make Stable Custom ROMS, And Thus Santoni is getting a Delay in every aspect.
I am new to Xiaomi community. But the thing is I love exploring new tech stuff. I find this community in xda very helpful for the likes of me. I love exploring android stuff, like flashing custom roms, kernels, and stuff. It is also a challenge to me because I am new to MIUI environment. Wish me luck. Happy flashing.
Official source code is released now, coming from a Galaxy S3 and a HTC 10 is a bit disappointing seeing the development scene, Galaxy S3 had a kernel being maintained 5 years (Boeffla Kernel) yet I've seen too many developers ending their project very fast here, yet again the Galaxy S3 community is (or was) way bigger.. I'd love to use a plain and stable AOSP ROM that's maintained often but unfortunately I don't see that on Redmi 4X, so I'm just using a tweaked MIUI and Gabriel kernel which subjectively for me is the best; responsive developer, most customizeable (it has its own Stweaks!), and overall still maintained although slow recently
(No paid shill)
I am looking forward to trying some of the Lineage OS cooked ROMs. The MIUI Stock is kind of sluggish.
I've tried several AOSP based ROMs for about 6 months on this device and I can give my two cents about the development scene.
Mind that, of course, it's all volunteer work and I'm not bashing anyone. I'm just telling my experience as an end user.
1) Lately, most Santoni developers migrated their ROMs to Treble only. This means a couple of things.
- Instead of continuing to use official TWRP and plain Magisk, you'll now have to use an unofficial recovery (because TWRP official doesn't support treble for our device) and a modded version of Magisk.
I don't know about you, but I'd rather put something signed by a recognized developer on my phone, such as the people from TWRP and the Magisk dev, than a random "modded" ZIP from the web. Not only for security, but because it is less prone to bugs. Agree with me?
Yet, the former is now the installation process for most Santoni ROMs.
- If you were lucky enough to use one of those ROMs before the Treble migration, you now have to nuke everything on your phone just to update your system to the Treble version. Fun, right?
You found THE ROM for your phone, and now you're nuking everything again.
- Despite the above mess, I can't say any advantage of using Treble on this device, besides being able to flash GSIs. But flashing GSI means you didn't bother with the original ROM anyway. So why are most ROMs Treble only? It seems just a trendy thing with more inconveniences than benefits for our device.
- Also, some people report the treble ROMs are more buggy. Lose-lose situation?
2) Right now we have many ROMs for Santoni. But when you go choose, you see that many are abandoned and most of the rest are Treble, with the "hacky" installation method.
3) On that mess, you may still find a ROM that suits you and your Santoni. You'll settle, adapt to its bugs or even find some workarounds. Great, right? But after a couple of months the developer can (and most will) completely abandon it, leaving you having to find another ROM to keep updated.
Or he won't abandon it, but he'll decide to switch to Treble only. Oh boy.
So there you go, nuke your whole phone again and start from zero.
Both situations happened even to ROMs with official status.
4) Many ROMs updates will come with the suggestion of "clean flashing". Now, I know this isn't strictly necessary, but in some situations dirty flashing can really cause bugs.
So, good luck reinstalling everything just to update your system. Even with some tool such as TitaniumBackup, it's a tedious process. Even more when you're expected to do it every few weeks.
5) Many ROMs have an erratic update schedule. On Monday the dev ships an update, and you flash it. But on Tuesday he sees he screwed everything because of not testing properly before shipping, and there you are, having to flash a new update. (I hope you didn't do a clean flash yesterday!)
Even when the updates aren't so close to each other, most ROMs have an almost random release schedule.
6) Now this I think is not exclusive to this device, but most ROMs won't notify you when there is an update. You'll have to keep an eye on a Telegram channel or here in the forum, as if you didn't have a life.
Even when they notify you, the update process is manual.
7) There are some bugs I always find on most Santoni Oreo ROMs and after half a year they are still there.
For example, I found video recording to be terrible in every custom ROM I've tried (I've tried most). Bad auto-focus, bad audio, etc. It doesn't matter which camera app you use. Yet it is still there.
Also, voice recording can be extremely quiet on some ROMs (luckly I've found a way to fix it).
Not to mention the battery drain, present everywhere (for which I only found a workaround - not a solution).
So the impression is that the effort is going to the trendy things (Treble) instead of fixing the existing bugs. The months pass and we have the same bugs, or even new ones.
8) Feedback about bug reporting can be non-existent or dismissive.
You report the problem and some developers won't bother. Others will say the problem doesn't even exist.
In a nutshell, there are many AOSP based ROMs for Santoni, but the development isn't as reliable as it could be. The general feeling is that it's too erratic and amateurish. Old bugs are not solved; new ones are introduced; the installation process is made worse for no apparent reason; you are forced to lose many hours reconfiguring your device just to keep it up to date. Also, I have seen no intention to mimic/pre-load some features we have on MIUI.
However, despite all the negatives points I offered, I can't compare the dev scene to other devices. Does Santoni has a better dev scene than some other phones? Probably.
For me, right now, I don't find those ROMs to be worth it. Life is short, and I'm back to MIUI. I'm using Xiaomi.eu, and I'm very pleased in comparison.
Edit:
Every single ROM contains bugs, and/or different kinds of bugs, newer or older or same. Or if there are no bugs, there are issues. Someone posted up, also included.
Giving major features example: about battery backup, most/all custom ROMs has cutoff voltage(poweroff at set mV, aprox.) set to 3200mV, but in MIUI it's set to 3400mV. This makes huge differences in battery backup and health,(though it's changeable) and one of the reasons why custom ROMs are known to have much better battery life. Many many ROMs, but in stability, none. There were few errors running all the time in logs, while I tested. ROMs using effects, total stability, and months testing whole other things I can't explain easily here, I found none of the ROMs fully configured to keep pace with MIUI. Stable doesn't mean optimized. What daily users need, they are happy, need not to find out. What power users need, they can go through hard testing and debugging. Our custom ROMs are still in halfway to have real stability and other effects, comparison to stock MIUI. Though they have much newer and upgraded features, they lacks as well.
Stock MIUI, and all based on it, are the best ROMs for our R4X, believe it or not. I've wasted months testing and reporting. And now I'm back to MIUI(xiaomi.eu). Now I'm modifying it for my own needs.
shohabmsk said:
Every single ROM contains bugs, and/or different kinds of bugs, newer or older or same. Or if there are no bugs, there are issues. Someone posted up, also included. Many many ROMs, but in stability, none. Stock MIUI, and all based on it, are the best ROMs for our R4X, believe it or not. I've wasted months testing and reporting. And now I'm back to MIUI(xiaomi.eu). Now I'm modifying it for my own needs.
Click to expand...
Click to collapse
I am actually very happy with Havoc OS based on Oreo.
DoctorRzepa said:
I am actually very happy with Havoc OS based on Oreo.
Click to expand...
Click to collapse
Good for you.
Pretty good support and all considering it's pretty unpopular phone
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've got the Blackview BV9900Pro which as you probably know if you are reading this, is a wonderfully well priced, rugged phone with the Lepton FLIR camera built in. Being a Treble device, it is possible to install most GSI ROMs to it, however there is currently no build of TWRP, and thus far, nobody seems to have been able to get the FLIR working on the GSIs. This presents two problems. First, recovery is a wonderfully useful tool to have, and the stock recovery leaves a lot to be desired, Second, the FLIR is the main reason for buying the pro model of this phone, rendering custom ROMs virtually useless.
That being said, I love this phone, and want to start to work on both. This will be a major learning curve as a) I'm not a developer by trade (I'm a marine engineer and environmental officer on a cruise line) and b) My job takes 10+ hours a day, 7 days a week when I am on board leaving me with limited time to put into it. I've built Linux from scratch (LFS back a number of years ago) which gave me good experience with the build environment and with compiling code / troubleshooting issues so I am confident I can pull it off, but I'm intersted in gauging if there is interest in publishing my work for others ot use.
If you have the 9900Pro phone, and are intersted in either TWRP and/or custom ROMs that support the FLIR, drop me a reply here and let me know. If you have any experience with modifying custom ROMs to work with vendor hardware, I would LOVE to hear about it - it will perhaps help guide me in my efforts. One of my biggest peeves with the phone is the lack of support for basic features (ie, SIP calling is not natively supported in the vendor's ROM) and the bugginess of the OS (apps being closed int he background, widgets not loading on boot etc). The GSI I am running now (Lineage) solves these issues, but the lack of IR camera really devalues the phone, so I'm hopeful that I can resolve the issue, and make this phone worth having.
Also, if anyone knows how to go about adding a new device to the forum tree, please chime in. I'm completely new to this whole developer support thing but comitted to making it work!
Cheers everyone!
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.