Related
Will community continue to develop to this phone after cyanogenmod is done in 6 days? As some of you may know Cyanogen inc had lots of issues so they decided to shutdown the company after 7 years of work. Some of the official devs started to tease a cyanogenmod reborn, named Lineage OS. You can find them on twitter, facebook, google+ and their new site lineageos.org . The site is still wip but i hope that Lineage OS will be developed for this phone and i dont have to throw my phone off the window just cause i dont have the latest update
As the source code will still available and the team is willing to continue, I see no reason for stopping, as long as our device maintainers support this device. But it may slow down a bit for a while, it's been a major transition after all. And rest of the custom ROMs might get affected too. Better to stay tuned in every thread possible, ours is not so big
Broadcasted from Zeta Reticuli
Gravemind2015 said:
As the source code will still available and the team is willing to continue, I see no reason for stopping, as long as our device maintainers support this device. But it may slow down a bit for a while, it's been a major transition after all. And rest of the custom ROMs might get affected too. Better to stay tuned in every thread possible, ours is not so big
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
youre right. i guess ill make sure im in the latest nightly in the next days if anything happens
The question is will CyanogenMod continue to live now that they have lost all support from Cyanogen, including build servers, monetary, and technical support... CyanogenMod will be renamed to LineageOS... The biggest problem is all development on Moto G 2015 (and many other Moto devices) is based on CyanogenMod, and there is no other source at this time. How will that play out? We don't know yet...
A well formed (and informed) answer from Stack Exchange's Android Enthusiast group:
CM's own blog is unreachable now, but XDA-Developers already summed it up and clarified some important bits:
All monetary and infrastructural support for CyanogenMod from Cyanogen Inc. will cease. -> CyanogenMod will no longer receive nightly builds after December 31st... unless the team finds another host to build nightlies.
The CyanogenMod team will not continue official development on the project.
CyanogenMod will rebrand as LineageOS.
Since it's clear that Cyngn is going in a new direction, Cyanogen OS will almost certainly have no future, since it's not community-driven in the first place. CyanogenMod, on the other hand, will live a bit longer, until Lineage dawns (or fails).
Click to expand...
Click to collapse
Wasn't Omnirom a fork of CM after the creation of Cyanogen Inc? As I recall all the developers were upset over going commercial and the future of cyanogenmod. Lineage OS would in essence be a fork of Cyanogenmod as well. I think it will really depend on whether they can find funding for some build infrastructure and how many developers jump on board.
acejavelin said:
The question is will CyanogenMod continue to live now that they have lost all support from Cyanogen, including build servers, monetary, and technical support... CyanogenMod will be renamed to LineageOS... The biggest problem is all development on Moto G 2015 (and many other Moto devices) is based on CyanogenMod, and there is no other source at this time. How will that play out? We don't know yet...
A well formed (and informed) answer from Stack Exchange's Android Enthusiast group:
Click to expand...
Click to collapse
The repositories are being mirrored (probably 'forked' is the correct term) into linageOS so I think we'll have a copy of our source code. And they said the source code for CM would still be available.
https://github.com/LineageOS?tab=repositories
Broadcasted from Zeta Reticuli
BTW, it isn't ending on Dec 31st like most people thought... it's ending prior to Dec 31st... They lost DNS and Jenkins yesterday, the blog is gone (so no reference to the official posts), official Cyanogen and CyanogenMod websites are down, and probably more that I haven't noticed mentioned yet are gone already.
But https://download.cyanogenmod.org is still live.
What would be the status of other custom roms that are based on cyanogenmod. Would they be affected ?
aa1010 said:
What would be the status of other custom roms that are based on cyanogenmod. Would they be affected ?
Click to expand...
Click to collapse
Of course...ALL ROMs for this device, except stock based ones, use the CM device tree and base code... Will LineageOS replace that? Right now it appears that way but time will tell.
To be honest, if CM/LineageOS doesn't make it... Probably 80℅ of all ROMs out there will disappear as we know them today, we really don't know the long-term effects this will have on the ROM community.
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
h0ttentot said:
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
Click to expand...
Click to collapse
1.2.3 i dunno but i hope everything will be fine
h0ttentot said:
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
Click to expand...
Click to collapse
1. Yes, to a point... for more information look at http://lineageos.org/Yes-this-is-us/
2. We don't know yet, they do not have build servers at the moment
3. I would wait, there is little chance of getting a working AOSP device tree at this time, but we will just have to wait and see.
The point is, right now we don't know exactly how this is all going to play out... we need to have patience and just see what happens.
---------- Post added at 01:29 PM ---------- Previous post was at 01:12 PM ----------
I would suggest everyone following this thread, look here: http://forum.xda-developers.com/2015-moto-g/general/cyanogenmod-to-lineageos-t3526944
The team behind CynanogenMod has declared the existing brand dead, and announced plans to fork the source code of the mobile OS.
Does this mean there will not be CyanogenMod version after 14.1? Or does it mean that they will not provide official builds for devices?
Yes to both, because what is left of CyanogenMod will be forked into LineageOS. No nightlies are to be developed after today. The OS will lose all Cyanogen-related branding as the brand could be sold. LineageOS will have zero affiliation whatsoever with Cyanogen.
deleted - wrong thread
SirSoviet said:
LineageOS will have zero affiliation whatsoever with Cyanogen.
Click to expand...
Click to collapse
LineageOS (or LOS) will be composed of several Cyanogenmod developers. Just want to remind that.
riahc3 said:
LineageOS (or LOS) will be composed of several Cyanogenmod developers. Just want to remind that.
Click to expand...
Click to collapse
That's basically what I said though. Cyanogen is not related to CyanogenMod, at all.
Wrong section, it should be to General talking not troubleshooting
P.S. Already mentioned from other posts
I looked through the threads and didn't see any post about this, so for anyone who isn't aware:
Im running CM 14 on my device and today I just realized there hasnt been any nightly updates since December. Well turns out there is no more CyanogenMod
But the good news is the developers decided to create their own fork if the project and continue the updates.
Here's a link to the blog post: http://lineageos.org/Yes-this-is-us/
Heres a link to the kltevzw downloads: https://download.lineageos.org/kltevzw
Introduction
A spinoff thread from the previously-supported-official thread by Atman.
This thread will contain my unofficial builds for violet. On the 16.0 version, the only real fix (so far...) have been the fingerprint scanner sepolicy denials. I aim to do monthly/bimonthly builds to keep up to date with security patches, as so far I haven't encountered any other issues (let me know).
On the 17.1 version, I have slowly figured out how to make it work, but it is highly experimental.
The 16.0 ROM is stable (I use it as my daily driver).
If you find any bugs, please do take screenshots, give a way for me to replicate it on my device, and send a logcat. If you're super smart, use a logcat and filter for the keyword so I don't have to do even more digging
Please don't tell me to use PE/Mokee commits.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Flash instructions
Same as usual:
Reboot to fastboot and flash recovery with fastboot (You have to use the TWRP linked below. Other versions likely won't boot.)
Reboot to recovery TWRP
Wipe to format data, wipe again to wipe system and cache (not necessary if you're updating, only if you're switching ROMs)
Flash firmware (ADB sideload) (this step is dated. The newer builds have a higher target firmware so you should try to flash without the firmware first, then flash the firmware if the ROM doesn't work.)
Flash the ROM (sideload)
Flash GApps, Magisk, etc. as necessary
Done
Downloads (16.0) (STABLE)
Firmware (Dated firwmare)
Recovery (TWRP)
11-Jun-2021 build (with 05-May-2021 security patch), and MD5 Digest
For previous builds see below
Downloads (17.1)
Here's the 17.1 ROM. Here's the md5 hash. It has the March security patch.
It currently does not boot. If you would like to try and help with development, flash the ROM, and then flash the Chinese Q firmware on top of it (this can be downloaded from xiaomifirmwareupdater). Be warned that there is a risk that the newest android keymaster may re-encrypt your device, which in the worst case may require you to format data and/or reflash recovery and/or flash a fastboot MIUI rom. So, it's a bit risky, but likely won't be an issue.
Credits, Sources, etc.
Too many to mention. Atman Shah for getting this device supported earlier last year. ThE_MarD (Marc Bougoin) for other help. Various other names I've seen - Bruno Martins, Weikai Kong, Wang Han... all of the Lineage dev team. I'm sure I'm missing many people who have been involved in the project. I am new, and very much a latecomer to all of this.
Device Tree: https://gitlab.com/mzha/android_device_xiaomi_violet
Kernel Tree: https://gitlab.com/mzha/android_kernel_xiaomi_violet
Other things see my gitlab: https://gitlab.com/mzha
A telegram group to discuss development for 16.0/17.1: t.me/lineageos_violet
Previous builds
07-Nov-2020 (incl. Oct-2020 security patch), with 07-Nov-2020 MD5 Hash
13-Jul-2020 (incl. Jul-2020 security patch), with 13-Jul-2020 MD5 Hash
11-May-2020 (incl. May-2020 security patch), with 11-May-2020 MD5 Hash
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
e2vinay said:
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
Click to expand...
Click to collapse
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
hcnulma said:
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
Click to expand...
Click to collapse
That's great
by any chance will you consider adding signature spoofing support? that would be really great. it would help many users go for microG instead of gapps
I completely understand you're starter.
great work. good luck.
Thank you
e2vinay said:
will you consider adding signature spoofing support?
Click to expand...
Click to collapse
No, but there are a few alternatives:
Merge the changes from this RFC and build it
Download the spoofer from https://download.lineage.microg.org/violet/, or get the (ed)Xposed module, or other possibilities...
Will be official Lineage Os?
Can we expect los 17 soon?
himanshu fulmali said:
Can we expect los 17 soon?
Click to expand...
Click to collapse
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Heyyo @hcnulma good to see you got your thread up and going!
As for 17.1? You can work with your current kernel and cherry-pick the fixes that other maintainers of violet are using and same for the device tree and vendor blobs.
As an example, LeEco msm8996 devives are using kernel source code from Marshmallow just rebased on a CAF Q Tag for our kernel since we never got anything newer...
Even once Xiaomi release their kernel source code for Android 10? It would probably take quite a bit of work to shave it down to what you specifically need and then importing it on top of a fresh CAF tag for the kernel or even more work to try and inplement it into uour current kernel.
To get official builds of LOS 16.0 going again for violet you would need to show that you are capable of fixing any major bugs that arise as well.
https://wiki.lineageos.org/submitting_device.html
anywho, hope this information helps bud!
hcnulma said:
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Click to expand...
Click to collapse
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Thank you. If he is stable enough I will use it to build RR PIE
Zjh0094 said:
Thank you. If he is stable enough I will use it to build RR PIE
Click to expand...
Click to collapse
It's definitely stable...
prajwal2001 said:
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Click to expand...
Click to collapse
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Request to create group for discussion in Telegram
hcnulma said:
It's definitely stable...
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
as every ROM uses the same device tree
and you won't be making pe instead of lineage as the same device tree and kernel are used in every Q ROM except EvoX which uses crimson kernel
hcnulma said:
It's definitely stable...
Click to expand...
Click to collapse
Thanks. I will use it as my benchmark to build RR pie.
---------- Post added 15th February 2020 at 12:03 AM ---------- Previous post was 14th February 2020 at 11:57 PM ----------
hcnulma said:
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
/quick/la/msm-4.14
prajwal2001 said:
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
Click to expand...
Click to collapse
It is precisely the device tree that I'm worried about. From experience, PE has a lot of platform-specific stuff that Lineage doesn't (and the same the other way), and also from trying to figure out the fix to 16.0 I realised there's a lot of context/definition differences between the two device trees. I'd still give it a look, but I suspect it might be easier to just modify the current 16.0 device tree.
RupeshRN said:
Request to create group for discussion in Telegram
Click to expand...
Click to collapse
https://t.me/lineageos_violet.
Zjh0094 said:
/quick/la/msm-4.14
Click to expand...
Click to collapse
Yeah I already figured it was msm-4.14. Have already cloned it but am also considering cherrypicking changes that other devs have done to their kernel trees from 16.0 -> 17.1 as opposed to starting with the CAF kernel. A work in progress.
Sir I'm noob but mokee dev released android 10 and i think mokee and los are pretty same, will he not help you if you contact him?
An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.
An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Here's the 17.1 ROM. Here's the md5 hash. Needless to say, it's very experimental, not stable in the least (expect to get past boot maybe 70% of the time) - I'm getting very mixed results when experimenting myself. Nevertheless, try it out, see what you get. Install it the same way as usual. Keen to get as many eyes on this as possible
Good morning, I have a Samsung Galaxy s5, I would like to change the ROM for carbonROM cr-9.0 (if I am not mistaken, it is the latest version), I currently have lineageOS 18.1, the problem is that there is currently no updated carbonROM support for my device So, I would like to know how I can adapt a ROM to be compatible with my device, I understand that it is something that requires work, but I want to know the steps that I should follow to be able to adapt a ROM, things to keep in mind, that programs to use, useful links, all the information you can give me, I would greatly appreciate it.
Martin19941994 said:
Good morning, I have a Samsung Galaxy s5, I would like to change the ROM for carbonROM cr-9.0 (if I am not mistaken, it is the latest version), I currently have lineageOS 18.1, the problem is that there is currently no updated carbonROM support for my device So, I would like to know how I can adapt a ROM to be compatible with my device, I understand that it is something that requires work, but I want to know the steps that I should follow to be able to adapt a ROM, things to keep in mind, that programs to use, useful links, all the information you can give me, I would greatly appreciate it.
Click to expand...
Click to collapse
You would have to build your own ROM using a mixture of the updated Lineage 18.1 ROM or the Lineage source code that it was built from and the carbonROM ROM or the carbonROM source code that was used to build your current carbonROM.
If you don't know how to build from source, you will have to try porting the carbonROM by mixing elements of the carbonROM and the LineageOS ROM. There are guides available that give a "rough" outline of how to port Samsung ROMs.
You can find guides and videos by doing a Google search for:
"How to port Samsung custom ROMs"
That should find some results but none of them are complete 100% start to finish guaranteed to work. It will require doing some research, reading, asking questions when you run into roadblocks along with a lot of trial and error testing and fixing mistakes along the way until you get a working generally bug free ROM.
All in all, you're probably better off just using the LineageOS 18.1 that you currently have.