Related
Just wondering if anyone knows on the cm 14.1 los builds . Does it included the latest security patches and important bits from nougat? Thanks in advance .
yes, it includes all the important bits from nougat, and i think , they are working on security patches
CM13 (still released unofficially, see Kernels & Roms Thread) and LineageOS 14.1 Pre-Official (and official once it's there) are both patched to the latest security patches (Jan 05) within the same month usually, the last few months it was patched within 1 or two weeks after release. I have to know that, I am doing it
BadDaemon said:
CM13 (still released unofficially, see Kernels & Roms Thread) and LineageOS 14.1 Pre-Official (and official once it's there) are both patched to the latest security patches (Jan 05) within the same month usually, the last few months it was patched within 1 or two weeks after release. I have to know that, I am doing it
Click to expand...
Click to collapse
Thanks for clarifying and the hard work. Definitely will have to root and give it a go. It's nice to see how far CM has come. Not to many roms always include latest patches alot of the time it's just ported eye candy features lol. CM 14.1 looks pretty awesome from what I've read up on even better that you included latest updates.
GrimReaper24 said:
Thanks for clarifying and the hard work. Definitely will have to root and give it a go. It's nice to see how far CM has come. Not to many roms always include latest patches alot of the time it's just ported eye candy features lol. CM 14.1 looks pretty awesome from what I've read up on even better that you included latest updates.
Click to expand...
Click to collapse
BadDaemon and crplamer are really dedicated with their work.
gopinaidu77 said:
BadDaemon and crplamer are really dedicated with their work.
Click to expand...
Click to collapse
I believe it lol. I've checked out the changelog and other bits since then. They are pretty good at squashing out bugs or finding a way to patch a lot of issues or playing with code to fix something. The layout works well tho gets reviewed approved then merged.
My favorite part of CM team from way back then which is now lineage was it generally was always updated and patched and never got stale.
Since the last one month there has been no update, no replies from the developer of lineage os 15 oreo build which has volte. Nor the trees are being released, so that others can implement. We users here are like sitting ducks. Is everything okay?
Grow up.
Well tbh abhisekh has not committed to you or me that he will update los 15 daily , weekly or monthly . So you cannot say why there is no update . Its been a month or two.. it doesn't matter how many days have passed. He or any other maintainer/developer builds rom in their free time xda doesn't pay them for building roms .
Regarding updating device tree its upto him ..when he wants to push the updated codes /commits .
The only thing you as an user can do is just enjoy whatever you are getting or roll back to previous android version or go back to stock miui or get a new device which you think has a great development in Oreo ..
Are there any Android Go ROMs available / underdevelopment for i9100? My phone has gone extremely slow and I think only something like Android Go could revive the old work horse.
Thanks for your time.
The unofficial LineageOS 15.1 builds by rINanDO (https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-lineageos-15-0-t3674567) are the first such ROMs currently, although, as of right now, it is in WIP phase, and although it is stable enough not to crash every few moments, a lot of things may be broken or not work at all.
I was wondering too. Thank you for the answer. I hope in 6months the bugs will be removed.
Cyanic Sword said:
The unofficial LineageOS 15.1 builds by rINanDO (https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-lineageos-15-0-t3674567) are the first such ROMs currently, although, as of right now, it is in WIP phase, and although it is stable enough not to crash every few moments, a lot of things may be broken or not work at all.
Click to expand...
Click to collapse
Are you sure those rINanDO's builds are based on Android Go and not full grown Android 8.1 ?
:fingers-crossed:
tnttrx said:
Are you sure those rINanDO's builds are based on Android Go and not full grown Android 8.1 ?
:fingers-crossed:
Click to expand...
Click to collapse
By nature, all Android Go builds are based on full grown Android 8.1, as they are built the same way, from the same source code, but the Android Go builds have an additional build flag attached at the very end.
So yes, they are based on Android Go, which in turn is based on Android 8.1.
and the flag is set !
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
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?