Originally Posted by CYANOGENMOD
in facebook
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, David van Tonder (dvtonder) decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
Click to expand...
Click to collapse
Let's wait for further announcements
thanks but no CM10.1 for Neo and Neo V
mido_fedo said:
thanks but no CM10.1 for Neo and Neo V
Click to expand...
Click to collapse
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Abhiheart said:
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Click to expand...
Click to collapse
Even if we get a stable Cm 10 ,it would be worth it and I think Fxp would do that!
As for Cm 10.1,it's been answered already ,it's not just worth the efforts n hassles!
Sent from my MT11i using xda premium
---------- Post added at 09:42 AM ---------- Previous post was at 09:41 AM ----------
FXP said:
HY All
We said it already several pages back CM10 is last release for 2011 devices
Those devices use an old kernel (2.6.32) and old blobs for camera (ICS)
So even making those work with cm10 (jellybean) was an real pain
To update kernel to 3.0 we will require 6+ months (not worth for an 2 year old SOC) limited in hardware and memory
Even if we take this effort this device will not be able to handle next version of android after 4.2 because it simply lacks RAM
Even for Jellybean we had to use legacy camera to be able to use camera in an proper way (with broken panorama)
What's the benefit of having latest android if your device is not able to use new features?
We will continue fixing cm10 and releasing weekly updates with latest JB progress
Jerpelea
FreeXperiaTeam
Click to expand...
Click to collapse
Sent from my MT11i using xda premium
How many days which have a release for cm-13 SNAPSHOT ROM
You can check their blog for new information -> http://www.cyanogenmod.org/blog. They write around 1 post a month on their blog, so the february post may come in the next days. Communication could be better (what is a blog for?).
The fact that they did not release a snasphot gives you a hint on what to expect from current nighlies. You can have a look at the cm13-stable branch here -> http://review.cyanogenmod.org/#/q/status:merged+branch:stable/cm-13.0-ZNH0E. There are still so many changes getting merged every day, I would not expect a snapshot before march.
Unfortunately they quietly dropped support for cm12.1, no snapshot with security updates since november. There is still a stable branch for cm12.1 with security updates (http://review.cyanogenmod.org/#/q/status:merged+branch:stable/cm-12.1-YOG7D). Hard to understand why they don't update at least the snapshots for cm12.1.
Hello,
@sir_bazz mentioned that this needed its own thread, thus I'm creating one.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
Deb is at https://lineageos.disavowed.jp/deb/. Flo is at https://lineageos.disavowed.jp/flo/. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Have been testing the latest weekly for a couple of days now, and no issues to report.
My Deb device is relegated to a dedicated Pogo tablet and I think Lineage 14.1 is a better match for my use as there's noteably more memory available after system startup than with the Pie ROMs I've tested.
It just feels much smoother.
Would've been more than happy with monthly updates but thanks for building the ROM and also making weeklies available for us Nexus 7 diehards.
sir_bazz said:
Have been testing the latest weekly for a couple of days now, and no issues to report.
My Deb device is relegated to a dedicated Pogo tablet and I think Lineage 14.1 is a better match for my use as there's noteably more memory available after system startup than with the Pie ROMs I've tested.
It just feels much smoother.
Would've been more than happy with monthly updates but thanks for building the ROM and also making weeklies available for us Nexus 7 diehards.
Click to expand...
Click to collapse
Likewise. I was just about to junk a (relatively) new N7 (flo) on stock MM. but wanted to give a newer ROM a try (Oreo). I didn't like my O options and stumbled upon these N builds on the backend of another thread. Flashed/Magisk couple Mods. Been up a week now and not one problem whatsoever!
Really appreciate the work as this ROM (I had never used a LinOS rom before) is running so well the N7 is almost my daily house driver again. The N7 FF really has never been matched/surpassed and once you've become accustomed to it its just hard to give up that "sweet spot".
wileyc said:
Hello,
@sir_bazz mentioned that this needed its own thread, thus I'm creating one.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
Deb is at https://lineageos.disavowed.jp/deb/. Flo is at https://lineageos.disavowed.jp/flo/. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Click to expand...
Click to collapse
Hi, I've just updated both my Hammerhead 15.1 and Flo 14.1. Everything has gone smoothly and all is working. I was just hoping you could clarify something that occurred to me regarding the builds.
When you say there are no modifications, does that mean that the basic ROM is frozen at the point when LineageOS stopped releasing official builds, and does that also mean that builds in between the monthly security updates are all the same or can there be other security/bug fixing updates from LineageOS? Also Lineage 15 was never official for the Nexus 5 or 7? I'm a bit in the dark as to how these things work.
Thanks in advance.
anivegmin said:
Hi, I've just updated both my Hammerhead 15.1 and Flo 14.1. Everything has gone smoothly and all is working. I was just hoping you could clarify something that occurred to me regarding the builds.
When you say there are no modifications, does that mean that the basic ROM is frozen at the point when LineageOS stopped releasing official builds, and does that also mean that builds in between the monthly security updates are all the same or can there be other security/bug fixing updates from LineageOS? Also Lineage 15 was never official for the Nexus 5 or 7? I'm a bit in the dark as to how these things work.
Thanks in advance.
Click to expand...
Click to collapse
No worries. By "no modifications", I mean that these are built directly from a clone of the LineageOS repository. I've made absolutely no changes to the source code. No kernel tweaks, no new features, no hidden spyware, no bugfixes (no matter how much I am tempted to do so!).
The LineageOS folks merge the monthly Google security patches into the 14.1 and 15.1 trees, but they don't make official builds for devices that no longer have a maintainer. Their official recommendation is to build it yourself if you want to keep your devices patched, but a non-trivial number of users can't make their own builds, so ...
... since I'm doing builds for my own devices anyway, it would be a good thing to make them available to others. Thus I have done so
Edit: argh, rereading I realize I didn't directly answer your exact question. From an end-user perspective, these builds are indeed frozen in time compared to the last official LineageOS build. Security patches happen as described above.
The Nexus 7 never received an official 15.1 build as far as I can tell, so I'm generating 14.1 for it.
The Nexus 5 is a bit of a grey area, in that builds generated from the 15.1 branch work fine with the exception of Bluetooth (from what I hear, as I don't use Bluetooth on my device). It appears to require a device repartition if you want to use Google apps, though, so I'm building both 14.1 and 15.1 to keep options option.
wileyc said:
No worries. By "no modifications", I mean that these are built directly from a clone of the LineageOS repository. I've made absolutely no changes to the source code. No kernel tweaks, no new features, no hidden spyware, no bugfixes (no matter how much I am tempted to do so!).
The LineageOS folks merge the monthly Google security patches into the 14.1 and 15.1 trees, but they don't make official builds for devices that no longer have a maintainer. Their official recommendation is to build it yourself if you want to keep your devices patched, but a non-trivial number of users can't make their own builds, so ...
... since I'm doing builds for my own devices anyway, it would be a good thing to make them available to others. Thus I have done so
Edit: argh, rereading I realize I didn't directly answer your exact question. From an end-user perspective, these builds are indeed frozen in time compared to the last official LineageOS build. Security patches happen as described above.
The Nexus 7 never received an official 15.1 build as far as I can tell, so I'm generating 14.1 for it.
The Nexus 5 is a bit of a grey area, in that builds generated from the 15.1 branch work fine with the exception of Bluetooth (from what I hear, as I don't use Bluetooth on my device). It appears to require a device repartition if you want to use Google apps, though, so I'm building both 14.1 and 15.1 to keep options option.
Click to expand...
Click to collapse
OK. Thanks for the explanation. Sorry to ask again, but does that mean that I only have to update once a month for the security updates, and that the other weekly builds are basically just repeats? Or am I misunderstanding?
anivegmin said:
OK. Thanks for the explanation. Sorry to ask again, but does that mean that I only have to update once a month for the security updates, and that the other weekly builds are basically just repeats? Or am I misunderstanding?
Click to expand...
Click to collapse
They're repeats. I'm doing them weekly to reduce the amount of time between the security patch hitting the tree and having a patched build available.
wileyc said:
They're repeats. I'm doing them weekly to reduce the amount of time between the security patch hitting the tree and having a patched build available.
Click to expand...
Click to collapse
OK. That's clear now. Thanks for your time.
smw6230 said:
I was just about to junk a (relatively) new N7 (flo) on stock MM
(...)
the N7 is almost my daily house driver again. The N7 FF really has never been matched/surpassed and once you've become accustomed to it its just hard to give up that "sweet spot".
Click to expand...
Click to collapse
Outstanding. That is exactly the reason why I'm making these builds. There's no reason to trash perfectly good hardware. Kudos to the LineageOS folks for keeping the tree patched -- the only thing missing were, um, actual builds.
Hi !
Thank you for your LOS 14.1 updating release, but I have error 7 with TWRP when I try flash it.
arkansis said:
Hi !
Thank you for your LOS 14.1 updating release, but I have error 7 with TWRP when I try flash it.
Click to expand...
Click to collapse
Make certain you're flashing the correct image. Boot into the bootloader and verify that the platform is the same as the build variant you are flashing. Good luck.
Thank you so much for this @wileyc , is possible to add 15.1 for flo?
Enviado desde mi Nexus 7 mediante Tapatalk
Thank you so much for keeping 14.1 alive!!!
DorianX said:
Thank you so much for this @wileyc , is possible to add 15.1 for flo?
Click to expand...
Click to collapse
I'm afraid not. These are built from unmodified LineageOS source repo; I'm just providing sustaining builds, not doing new development/porting.
Thank you for these!! This rom runs perfect on the FLO. I hope you continue the updates for a long time!!
wileyc said:
There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
Click to expand...
Click to collapse
Good day sir, would you consider adding to the roster and doing sustaining builds for the Moto Z Play, https://wiki.lineageos.org/devices/addison?
Many thanks for providing these builds for the Nexus 7 2013.
braveheartleo said:
Good day sir, would you consider adding to the roster and doing sustaining builds for the Moto Z Play, https://wiki.lineageos.org/devices/addison?
Click to expand...
Click to collapse
No problem at all. I've added it to the weekly roster, and a one-off build is at https://lineageos.disavowed.jp/addison/.
wileyc said:
No problem at all. I've added it to the weekly roster, and a one-off build is at https://lineageos.disavowed.jp/addison/.
Click to expand...
Click to collapse
Awesome turnaround sir. And thank you very much. ?
Thanks for running these builds! Out of curiosity what's the monthly cost like? You running these on a home machine or something like DigitalOcean?
Hi. One Question, can i update over last zeelogs LOS Build?