This is an unofficial build for all those who want to stay with CM11. The build is based on the pure CM code and does include the stagefright patches and other patches up to July 30.
It does run perfectly on my wife's N7000. However, use at your own risk.
https://www.mediafire.com/folder/wqacsxdn42n15d2,z707vvgb63q4b74/shared
New version available:
https://www.mediafire.com/folder/ygkv6tryc7v7bgs,6ay7smbzruwxxrr/shared
Since - again - a severe security issue has been patched since the last time, I encourage everyone to upgrade.
NeuDLi said:
New version available:
https://www.mediafire.com/folder/ygkv6tryc7v7bgs,6ay7smbzruwxxrr/shared
Since - again - a severe security issue has been patched since the last time, I encourage everyone to upgrade.
Click to expand...
Click to collapse
Please tell us what is the changes applied to the official version of Cyanogemod. You only says to test it, with no description? No , thanks!
Jack4L_ said:
Please tell us what is the changes applied to the official version of Cyanogemod. You only says to test it, with no description? No , thanks!
Click to expand...
Click to collapse
Well it's up to you if you use my ROM or not (basically you always have to trust anyone providing a ROM, because you cannot confirm the actually used codebase anyway!). In the meantime there is another official version out, so you can readily stick to that. I did not wish to wait with a severe security issue until someone built another official version. Last time it was 2 weeks between builds... which is far too long with such severe issues as recently.
Apart from that, your accusation is incorrect! Did you read the initial post? Apparently not, because it clearly stated that "The build is based on the pure CM code". This is still the case and will be if not stated otherwise. So there are NO CHANGES APPLIED TO THE OFFICIAL CM CODE, period! I just build it when an important patch is out but no official build.
no thanks
New version available. This includes the - not yet merged - patches http://review.cyanogenmod.org/112044 and http://review.cyanogenmod.org/112043. According to stagefright detector app this has removed the vulnerability CVE-2015-6602 (also termed stagefright V2). Here you go:
https://www.mediafire.com/folder/0t8784a5at6h9z4,opbklzsle9igxfv/shared
Official version of November 22 available. As a number of bugs have been remedied, everyone should upgrade.
Only thing is that Xposed does not work due to some patches. I will try to compile a new version including a fix for that next week.
New version available. All patches up to and including the one of November 23, and also including a fix for Xposed (taken from here: https://gerrit.omnirom.org/#/c/15695/).
https://www.mediafire.com/folder/xy7zd919cv04ohf,b081a5orcm8et49/shared
Hi NeuDLi,
after many test with cm12 i am now back to cm11 because i think cm12 use to much rom and our old n7000 will work very slow.
I have had many break down and automatik restarts. cm12 has no advantages for me.
the official cm 11 builds -i agree with you- will not quick updated.
now i give your rom a chance to work for me and my n7000. Thanks.
New version available. Includes official patches including December 8. Unless stated otherwise all further version will include the Xposed patch as of the previous post.
https://www.mediafire.com/folder/h2bo3o5b7uqn4gw,40qmwwyfu2cb477/shared
Related
CyanogenMod was updated to version 10.1.1 yesterday which addressed several major Android security exploits. Is that something that gets into next touchpad nighlty build or does it wait for next version release. Just wondering.
poqonos said:
CyanogenMod was updated to version 10.1.1 yesterday which addressed several major Android security exploits. Is that something that gets into next touchpad nighlty build or does it wait for next version release. Just wondering.
Click to expand...
Click to collapse
It should be merged into the nighties as the various devs pull the latest cm code
Is anyone currently working on building CM 14 for the Turbo/Maxx?
DREWHAMM974 said:
Is anyone currently working on building CM 14 for the Turbo/Maxx?
Click to expand...
Click to collapse
Our official CM dev @Skrilax_CZ is working on CM14 -- just like he did CM12, CM12.1 and CM13. No device has official CM14 yet, just stuff thrown together. CM team has not released any CM14 ROMs yet.
Due to his kernel work, he's the only reason we have any custom ROMs at all -- they all use his CM kernel in their ROMs. Even BHM27 kernel is based on CM code @Skrilax_CZ wrote.
santi1993 said:
Will u develop CM14 from Moto X Style sources?
Click to expand...
Click to collapse
Moto X Style does not have official CM14 yet. Yes, somebody has thrown together an unofficial CM14 for that device but lots of stuff doesn't work.
@ Skrilax_CZ will release official CM14 when it's ready.
Skrilax_CZ said:
I usually start porting when CM14 official nightlies start. CM14 is just too unstable right now. Although since I have 2nd MAXX, I might look on it a bit earlier
Click to expand...
Click to collapse
Cobra04 said:
Nexus 6 STILL doesn't have stock Nougat so no rush.
Click to expand...
Click to collapse
This is just speculation as to when the first official CM14 nightlies for any device will begin, not necessarily our Quark.
http://www.theandroidsoul.com/cm14-release-date/
CM14 Release Date?
Expected on: October 2016 (2nd week). Read the below to know why we think so.
As said above, the work has started on the CM14 ROMs over at Github, the central station of the code. We already have ports of CM14 ROMs available for numerous devices, which we tried to list out in separate section below. Mind you, CyanogenMod has yet to release a ROM, as these ports are self-cooked (unofficial) ROM by users using the code available from CyanogenMod team.
Stable release of the CM14 would definitely take some time. When ROMs are stable enough to be used as daily driver, CM team will release them themselves. But let’s try to find out expected release date of that happening.
Let’s take an example. A real one. For Cyanogenmod 13, which was based on Android 6.0, it took nearly over one and a half month.
Google started rolling out the Android 6.0 Marshmallow update on October 5 last year, and uploaded it to AOSP the same day too. But it was only on November 24 that Cyanogen team released their first build of CM13. So, that’s 50 days, around 1 month and 20 days it took CM team to fork out their first CM13 build for selected devices, while most of the devices received CM13 support only later on.
We can expect similar release gap between AOSP release of Nougat and CM14’s release. As Google released the Android Nougat as an OTA to Nexus devices on August 22, to which we add the Marshmallow time gap calculated above of 50 days, our expected CM14 release date would come to October 11, that is, second week of October 2016.
Click to expand...
Click to collapse
Ok, I greatly appreciate it. I just got my Turbo a couple days ago and was just looking around. Once everything has been built I should be able to use the repos to port other CM based roms over to the quark devices. I'm in the middle of getting my build environment set back up since I havent done anything in quite a while. Please note though, I am not a developer. I'm just someone who knows how to build from source using other peoples work on device repos.
DREWHAMM974 said:
Ok, I greatly appreciate it. I just got my Turbo a couple days ago and was just looking around. Once everything has been built I should be able to use the repos to port other CM based roms over to the quark devices. I'm in the middle of getting my build environment set back up since I havent done anything in quite a while. Please note though, I am not a developer. I'm just someone who knows how to build from source using other peoples work on device repos.
Click to expand...
Click to collapse
These are the Marshmallow ROMs currently available for our Quark devices, so you can keep up with what's being done for our device. Just a repost of mine from another thread. Once CM14 (Nougat) comes out, these will probably be updated. But there's tons of other ROMs out there people would love to have! So, thank you.
___________
http://forum.xda-developers.com/showthread.php?p=68810980
Here's the current custom Marshmallow Quark ROMs to choose from:
[ROM][All Quark][6.x.x]Resurrection Remix
Bliss Rom 6.4 by Team Bliss
[ROM][6.0.1][OFFICIAL][QUARK] MoKee OpenSource Project
[Rom] NEXUS EXPERIENCE 10.4 [MotoMaxx] (recently updated to Marshmallow)
AOKP - Android Open Kang Project[6.0.1][Marshmallow]
[Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 13.0
[ROM][2016-09-17][Quarks][CM 13.0 Unofficial][6.0.1] (hybrid of CM13 and Resurrection Remix)
That list is in no particular order.
_________________________
You can also install a Marshmallow stock ROM released by Motorola for the Brazilian Quark. @iiWoodstocK adapted it so it runs on ANY Quark, including the XT1254 Droid Turbo or XT1250 U.S. Moto Maxx (clone of the XT1254). It will use YOUR radio, whatever you have installed.
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
Stock 6.0.1 MPG24.107-70.2 (Brazil) for Verizon XT1254
http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
I didn't include it in the list above, because while technically it is a custom ROM, the only "customization" was to allow it to be flashed via TWRP and to allow it to be used on ALL Quarks: XT1254/XT1250/XT1225. Otherwise, it's pure Motorola Marshmallow stock which was officially released for a Quark phone.
iiWoodstocK said:
this ROM is just factory Marshmallow with a modded build.prop. I didn't include any radio in the .zip, so it uses whatever is currently on the device. Aside from my build.prop tweaks, this ROM is even usable for Brazilian XT1225 users, but the device will say it's a Droid Turbo and contain useless CDMA build.prop lines.
Click to expand...
Click to collapse
iiWoodstocK said:
Major stock functionality that I have confirmed working as it should: Moto Display, Approach to wake, Wi-Fi, mobile data (LTE/3G), calls, etc. No Verizon VoLTE (yet). I have not tested Moto Voice as I do not use Moto Voice, but I see no reason why it wouldn't work.
Click to expand...
Click to collapse
Any questions go to those threads and ask.
Just flashed the November cyanogen mod update. Xposed isn't working. I'm assuming that it's the November android security patch causing the problem, because it stopped working on my phone Saturday after I flashed an updated rom. From what I've found, the cm team doesn't support xposed, so xposed developers will have to find a work around, and all we can do is wait.
hooks024 said:
Just flashed the November cyanogen mod update. Xposed isn't working. I'm assuming that it's the November android security patch causing the problem, because it stopped working on my phone Saturday after I flashed an updated rom. From what I've found, the cm team doesn't support xposed, so xposed developers will have to find a work around, and all we can do is wait.
Click to expand...
Click to collapse
Known issue with Nov 16th security patch impacting (at least) CM 12.1 and CM 13 on multiple (likely all) device types. CyanogenMod does not officially support Xposed; will be interesting to see how this plays out. For now stick with 20161021 build of CM 12.1 if you want to use Xposed.
hooks024 said:
Just flashed the November cyanogen mod update. Xposed isn't working. I'm assuming that it's the November android security patch causing the problem, because it stopped working on my phone Saturday after I flashed an updated rom. From what I've found, the cm team doesn't support xposed, so xposed developers will have to find a work around, and all we can do is wait.
Click to expand...
Click to collapse
Davey126 said:
Known issue with Nov 16th security patch impacting (at least) CM 12.1 and CM 13 on multiple (likely all) device types. CyanogenMod does not officially support Xposed; will be interesting to see how this plays out. For now stick with 20161021 build of CM 12.1 if you want to use Xposed.
Click to expand...
Click to collapse
Problem resolved w/latest CM build from @ggow (here). Confirmed working. Yey!
This is nothing big and I'm not a Developer.
This Thread is just for Unoffical LineageOS Builds that I do from time to time.
The Builds are done with Udev's Device Tree and Vendor Files and Offical LineageOS Sources.
I might make some changes at some point, but don't hold your breath.
So far all this is, is Udev's fixes and updated Lineage Sources (fixes) and monthly Security Patches.
I post updates whenever something interesting happens (which is now hardly ever with Lineage 15.1), or when there's a new security patch.
The only reason I'm making a new Thread for this, is because I don't want to post these updates in Ordenkrieger's/Udev's Official Thread.
Oh and the Disclaimer from the Original Thread.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Any failure in this process could lead to an unrecoverable bricked device.
Click to expand...
Click to collapse
With that out of the way, here is the Link to my latest Build:
https://mega.nz/file/eIEWFSAS#cmU62oG5IARruOPcYwAaSqnZKGvB3qdemJwnZt9SM_I
Thanks to:
OrdenKrieger, Unjustified Dev, king1990, DrakenFX, tdm and tprfd
ROM OS Version: 8.x Oreo
Based On: LineageOS ( Source ) ( Vendor )
Kernel version: 3.18.140-Baddar-RC1.2 ( Source )
Version Information
Status: Stable
Created: 12-04-2019
Last Updated: 03-08-2020
Changelog:
03.08.20
https://www.lineageoslog.com/15.1
20.04.19
Initial Release
Just in case...
Running great so far! Gcam FCing for me, but maybe it's just bad opengapps nightly. No battery stuck bug after changing battery.
Updated Version with latest LineageOS Fixes and latest Android Security Update, linked in the first Post.
The Build was made without Udev's latest Commits ( click ) as I don't know if he wants them in a public ROM yet ( and it says WIP anyway).
thanks!! you awesome. the previous April20 build has been great. -GA
[armitage] said:
Updated Version with latest LineageOS Fixes and latest Android Security Update, linked in the first Post.
The Build was made without Udev's latest Commits ( click ) as I don't know if he wants them in a public ROM yet ( and it says WIP anyway).
Click to expand...
Click to collapse
i am using this rom right now with baddar rc 1.1 kernel.Anyone got dolby atmos working?
I don't think that there is a way to get it working on newer non-stock Roms. I've given up on that quite a while ago.
i tried some zips,none works...i also give it up lol.The vendor really need updates also i think.Play store not certified even with fp props module.More heat on the phone,cpu load very high
Must be something on your side. No problems here whatsoever.
Play store works fine, no heat, low discharge rate, no high cpu usage.
I mean my battery is pretty much "trash", after two years of not treating it too kindly and I still get almost 5h SOT, which is not too bad I guess.
Oh and there's not really much I can do about the vendor and haven't tried that kernel yet. Using stock lineage kernel here.
i used it for some hours now,and i think i agree with you.Idle is really great,power consumption alsnly thing playstore not certified.
Thank you for these builds!!
Just uploaded the probably last update based on Lineage 15.1, as the the Axon 7 has been removed and (as you can read here) is no longer maintained.
Maybe it'll be back with Lineage 16 one day.
[armitage said:
;79596505]Just uploaded the probably last update based on Lineage 15.1, as the the Axon 7 has been removed and (as you can read here) is no longer maintained.
Maybe it'll be back with Lineage 16 one day.
Click to expand...
Click to collapse
It hasn't been maintained in months and months. I am pretty sure this only means that lineage will no longer provide an 'official' build. You can still build yours the way you're doing it.
So what you're saying is that there will still be some fixes and security patches added but I won't see a device specific changelog for the axon7 and there won't be any automated builds?
So I'd just have to check another device's changes to see when a for example a security patch was added and this will still be included when I check out and build for the axon?
[armitage] said:
So what you're saying is that there will still be some fixes and security patches added but I won't see a device specific changelog for the axon7 and there won't be any automated builds?
So I'd just have to check another device's changes to see when a for example a security patch was added and this will still be included when I check out and build for the axon?
Click to expand...
Click to collapse
No more automated builds for official. There hasn't been device specific changes for many months. The changelog you see on lineageoslog for axon7 includes the non-device specific changes and has the other device specific changes filtered out.
You can look here for the full changelog for 15.1 here:
https://www.lineageoslog.com/15.1
I can see the security bump was merged on the 17th.
It should be business as usual for your builds that you're providing here... I hope.
thanks for the ongoing efforts to update the builds!! much appreciated. do you have option to buy you a beer?? -GA
tprfd said:
No more automated builds for official. There hasn't been device specific changes for many months. The changelog you see on lineageoslog for axon7 includes the non-device specific changes and has the other device specific changes filtered out.
You can look here for the full changelog for 15.1 here:
https://www.lineageoslog.com/15.1
I can see the security bump was merged on the 17th.
It should be business as usual for your builds that you're providing here... I hope.
Click to expand...
Click to collapse
gads1 said:
thanks for the ongoing efforts to update the builds!! much appreciated. do you have option to buy you a beer?? -GA
Click to expand...
Click to collapse
Not me you should ask!
armitage is the one hosting/building these... and of course all of the work put in initially from the devs.
whoops!! thanks for correction. I wasn't paying attention... lazy! beers for everyone....
tprfd said:
Not me you should ask!
armitage is the one ....
Click to expand...
Click to collapse
I wasn't really thinking of that at all, as I don't really consider what I'm doing that important, but as I'm in the process of moving and a money will be tight over the next couple of months, sure... a beer would be appreciated.
But just to make sure... this will never be a necessity. I will probably build these as long as people need them, even if I don't have the device anymore, as it is not that hard to do and doesn't take a lot of time, once everything is set up.
Anyway, I added my paypal url to my profile.
It's not clear in this thread but is this build treble or not? Thanks
Hi.
LineageOS 20 is now officially released, but I can't find it for Sony Xperia XZ1c.
Does anyone know where it can be downloaded?
Thanks
There isn't official Los 20 for the XZ1c, but you have the unofficial version by derfelot. It works the same as the official versions for other devices, the only differences being the lack of OTA updates and the time between updates varies. I think we're getting an update to the Los20 rom soon, since I see commits submitted in github.
Hi,
I've installed the previous unofficial version on my XZ1c, and am looking forward to the mentionned unofficial LOS20 update before I install it (I didn't see it was already available at the time I installed 19 in december). I have a question, not too silly I hope :
I've read on LineageOS website that if some developers have a running and reliable LOS version developed for a device that is not yet officially supported, they can submit their version so that then the version becomes "official" and one can get it from LOS website. Is it planned with this unofficial LOS version ? why / why not ?
Thanks
I think It's not official because the devs don't want to involve/don't have the time to become official maintainers, instead releasing updates less frequently. Basically It's a responsibility. That's what I think and personally I'm fine with the unofficial builds, these devs do a lot already.
So in theory, If someone has the skills/time to maintain this device officially, It could become one without an issue.
Let me ask another question (since this is new post):
Which of available ROMs suits You all best and why?
I Was on Havoc 4, then 5, Lineage 17, now I'm back to Havoc 3.11 but this one gets random freezes and battery heats up. Only issue I have with new releases is lack of Android Auto support.
maarek7 said:
Let me ask another question (since this is new post):
Which of available ROMs suits You all best and why?
I Was on Havoc 4, then 5, Lineage 17, now I'm back to Havoc 3.11 but this one gets random freezes and battery heats up. Only issue I have with new releases is lack of Android Auto support.
Click to expand...
Click to collapse
Hi, I don't have an answer to your question since so far I've tested only lineage 19. But I'd like to ask you why you chose to go back to Havoc 3.11 even though it heats and freezes ? (Why not a more recent ?)
And what are the differences between Havoc and LOS in everyday use, what did you personnally notice / prefer ?
Arcline said:
I think It's not official because the devs don't want to involve/don't have the time to become official maintainers, instead releasing updates less frequently. Basically It's a responsibility. That's what I think and personally I'm fine with the unofficial builds, these devs do a lot already.
So in theory, If someone has the skills/time to maintain this device officially, It could become one without an issue.
Click to expand...
Click to collapse
Ok, indeed it would add more work/responsibility to the developpers.
eve1374 said:
Hi, I don't have an answer to your question since so far I've tested only lineage 19. But I'd like to ask you why you chose to go back to Havoc 3.11 even though it heats and freezes ? (Why not a more recent ?)
And what are the differences between Havoc and LOS in everyday use, what did you personnally notice / prefer ?
Click to expand...
Click to collapse
Hi,
I wanted to try and test Android Auto mostly to be honest.
As per differences - Havoc gives You way more options to customize whole phone (appearance), have more features (gestures, status bar, dock etc., you might even forget half of the settings after finishing configuring it), Lineage on the other hand I believe consumes less battery, appears to be quicker, is neat.
But I've tried either Havoc and Lineage on Android 12 and both works smooth. Testing Lineage 20 currently and can't say any bad word. But I'm kind of lucky with custom ROMs, never had any major issues, all worked fine always