Develop Bugs

[ROM] CyanogenMod 7 for the Samsung Galaxy S :: V7.1.0-RC1 (26 June 2011)

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
This version is a release candidate, but you will find it stable for everyday use.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Samsung Galaxy S, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official posthttp://forum.cyanogenmod.com/topic/...r-the-samsung-galaxy-s-v710-rc1-26-june-2011/​CyanogenMod:
Latest Version: update-cm-7.1.0-RC1-GalaxyS-signed.zip
Download: Link
Mirror: Link
MD5sum: c7e812d4c94de40176d463de7f720ffd​Google Apps addon:
Version: gapps-gb-20110613
Mirror: Link
Mirror: Link​The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

cool. just released

thank you all devs

We know. There is the oficial thread posted by codeworks. So why did you post this?
Sent from my GT-I9000 using XDA Premium App

sefuleo said:
We know. There is the oficial thread posted by codeworks. So why did you post this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
This is the official thread for the RC (and future RC's)... codeworkx's thread is for nightlies. the difference being is that the build flashed from this thread is allowed to report bugs to the issue tracker.

RC is too in codeworkx thread. But anyway.... Thanks for posting.
Sent from my GT-I9000 using XDA Premium App

sefuleo said:
RC is too in codeworkx thread. But anyway.... Thanks for posting.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
there is no information about the RC('s) in codeworkx's thread. his thread clearly says nightly at the top and is for nightlies and nightlies only. the "latest version" link does not count because following that no matter what will show you *all* options. this is the standard CM way of doing things. a thread for nightlies and a thread for stable(ish) version. feel free to check any other CM-supported device's section and you will see both as well.

so is RC1 > Nightly

tb5... said:
so is RC1 > Nightly
Click to expand...
Click to collapse
RC1 = stable(ish)
nightly = bleeding edge
RC will only be updated a few times over the next few weeks until the final build is released. nightlies will continue to be pumped out every night. benefit of RC is you can post issues to the issue tracker and actually contribute back to the community.

So whats the deal?
Used to run CM on my HTC Magic.
Have heard that there are issues with battery life etc. on SGS.
What are the cons of SGS CM71. Cant seem to find list of good/bad issues.
Also, the nightly "must be on froyo" is not listed on the CM7 webpage (and this thread). I can flash from sammy gingerbread now?

BatGnat said:
Used to run CM on my HTC Magic.
Have heard that there are issues with battery life etc. on SGS.
What are the cons of SGS CM71. Cant seem to find list of good/bad issues.
Also, the nightly "must be on froyo" is not listed on the CM7 webpage (and this thread). I can flash from sammy gingerbread now?
Click to expand...
Click to collapse
all the wiki instructions clearly say to flash from Froyo, and those are the instructions to follow.

Kaik541 said:
all the wiki instructions clearly say to flash from Froyo, and those are the instructions to follow.
Click to expand...
Click to collapse
Yes, but you had best add it to the install instructions here too, or the 15 questions you get about bootloaders a day will become 150 or more. No fun at all.
Also, it notes in the instructions on the OP that if you are updating a previous CM7 install, you do not need to flash Gapps again. This has not been true for around 15 nightlies now...has whatever issue that required reflashing Gapps along with a nightly been fixed?

Downloading it..
Finally a RC release ..good work Cyano's Team ..
I use Cyanogen 7 on my Galaxy S and also on my Htc Magic 32b
Cyanogen 7= The best rom of ever
Cheers

Perfectly and thx

rschenck said:
Yes, but you had best add it to the install instructions here too, or the 15 questions you get about bootloaders a day will become 150 or more. No fun at all.
Also, it notes in the instructions on the OP that if you are updating a previous CM7 install, you do not need to flash Gapps again. This has not been true for around 15 nightlies now...has whatever issue that required reflashing Gapps along with a nightly been fixed?
Click to expand...
Click to collapse
the ROM threads for RC releases are cookie-cutter, only replaced with proper links/md5sums. as for the gapps thing, I've been flashing updates every few days and have literally never once had to reinstall gapps =/
also, rschenck, please don't leave me to moderate this thread alone, you make the i9000 threads worth reading

And ANOTHER question....
If I opt not to install the RC1 release itself, but wait and install the next Nightly, which would be 40 for the i9000. Will that automatically update me to RC1?
Plus I am always ready to lend a hand and/or a stinging bon mot, you just seem more up on the RC1 situation than I so I defer to your wisdom.
Lastly, regarding reflashing Gapps, it has been advised as a precaution for ages now to avoid potential trouble. I see no harm in continuing to do it.

Kaik, thanks for the thread. Downloading the RC now (I've been running nightlies for months, if this is good enough I might have my dad run it!) Just wondering, are you a member of the CMSGS team? And if so, do you have any insight to headphone controls being fixed?

A little suggestion..
PLEASE CYANO'S TEAM READ THIS:
See at SuperAosp 8.6 camera..is similiar at Cyanogen camera but it is best in graphics..background black ..photo button better..see it please

rschenck said:
And ANOTHER question....
If I opt not to install the RC1 release itself, but wait and install the next Nightly, which would be 40 for the i9000. Will that automatically update me to RC1?
Plus I am always ready to lend a hand and/or a stinging bon mot, you just seem more up on the RC1 situation than I so I defer to your wisdom.
Lastly, regarding reflashing Gapps, it has been advised as a precaution for ages now to avoid potential trouble. I see no harm in continuing to do it.
Click to expand...
Click to collapse
personally, I always run under the assumption that each and every flash will horribly destroy my phone and make backups of apps with TiBu and nandroid every time while praying I never have to open heimdall again. I then keep the gapps zip and at least one earlier nightly on my SD card. RC1 is basically just a "nightly considered stable for the purpose of bug reports" for official means. nightlies will always surpass stable builds (and will always come with the risk that they are far more likely to break)
chambo622 said:
Kaik, thanks for the thread. Downloading the RC now (I've been running nightlies for months, if this is good enough I might have my dad run it!) Just wondering, are you a member of the CMSGS team? And if so, do you have any insight to headphone controls being fixed?
Click to expand...
Click to collapse
I'm an honorary member of teamhacksung as it were. I've been out of the i9000 group because coolya and codeworkx mostly have it under control and rschenck provides the right amount of help while being entertaining in a way that I couldn't possibly hope to be. as for headphone controls, atinm is aware of the issue and it's on the list of things to be fixed (including TV out at some point).

I didn't follow that much the Nighlies thread in the past month because i didn't have time to flash and reflash continously.
I'm wondering, on this RC1, if everything works, including all that didn't work perfectly in nightlies builds.
And what about battery life? I switched from JVH to JVP and i noticed a small reduction of battery life. Is CM7 RC1 overall better or worst than the aforementioned releases?
ANyway, thumbs up for the passage from nightlies to RC, i was looking forward for CM7 on my SGS since when i bought it in January. Coming from an HTC phone i really missed the speed and functions of CM.

[rom][cm9][4.0.3][cdma] cm9 semi-kang

CM9 NIGHTLY (UNOFFICIAL SEMI-KANG) FOR CDMA TORO
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.

Glad your making a Rom, but...
1) its in the wrong forum and
2) you dont have a link because of your "probation" status of < 10 posts
Good luck with your work though!

Also there's (unofficial) builds by a CM developer in the development section already:
http://forum.xda-developers.com/showthread.php?t=1397122

@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.

toroidal_loop said:
CM9 NIGHTLY (UNOFFICIAL SEMI-KANG)
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Click to expand...
Click to collapse
I love seeing new developers come here everyday
One small issue though, this is posted in the wrong section. This should be posted in the GSM Galaxy Nexus Android Development or CDMA Galaxy Nexus Android Development (depending whether its GSM or CDMA)

toroidal_loop said:
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
Click to expand...
Click to collapse
Did you ever ask the guys from cm team before you post the kang build?I dont think this allowed.
Sent from my Galaxy Nexus using Tapatalk

Getting your post count up and then posting in Development would have been the thing to do. This will get lost in General, and I can't see it being moved to Development or everyone and his mate would be using that loophole.

@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
@Kalavere I'm not trying to get this moved to the Dev. If there's enough interest in it, I'll repost the thread to Dev when I'm able. The problem I had was that there wasn't a vanilla build of CM that I could find anywhere for the CDMA/LTE toro.

toroidal_loop said:
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
Click to expand...
Click to collapse
Perfect .Just mention it because i dont want to see another locked thread

[Q] Official Cyanogen Mod rom. How soon?

Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!

kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
Don't know if there will be an official build, but unofficial build by crpalmer works great.

Rutr said:
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Click to expand...
Click to collapse
Yup, I saw that, just wondering if we will get official anytime soon.

kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.

crpalmer said:
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
Click to expand...
Click to collapse
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!

kortik9 said:
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
Click to expand...
Click to collapse
Not necessarily having visibility into any framework changes I've made is a pretty reasonable concern. There's only one change that I have already submitted for review so nothing too magical going on behind the scenes. Everything else is available in my public git repos for anyone to verify.

Most of the time official builds start out as unofficial builds. At least that's what I've noticed.

[ROM][6.0.1] UNOFFICIAL CyanogenMod 13.0

Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.​
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.​
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15

now with Marshmallow!

Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app

illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.

musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2

musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app

I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.

Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus

Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.

musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?

Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695

Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.

We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...

jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.

jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...

Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.

I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.

yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.

Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799

Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.

Older versions of LineageOS?

CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?

Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.

It goes back to 6.0.1 but no further.

It will do both, apparently.....

Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk

MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.

LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."

MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol

The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.

Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk

Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris

jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.