Develop Bugs

[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.

[ROM][SGH-T889 / T0LTETMO][4.4.4][UNOFFICIAL] OmniRom 4.4.4 - Builds of opportunity

As many of you know the GSM Note 2 is supported by Team OmniROM in a unified build format. This work is inspiring to me as the team split from CM for altruistic reasons. I have come to consider OmniROM my AOSP branch of choice due to their philosophy toward security and development.
I see a niche for our community where some of our members may be uncomfortable utilizing the unified build for any number of reasons.
My product is no more than a straight source built t0ltetmo build as the OmniROM spec is drawn up for the t0lte and adapted by the t0ltetmo spec on the OmniROM github. All source is available at the OmniROM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-Omni commits or "fixes" with very few exceptions. If it is broken in the unified build it will be broken in this one as well.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in OmniROM commits that looks promising I expect that I would post a new build. Getting to the point where stuff wasn't broken took some serious banging of the head.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial OmniRom .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
omni-4.4.4-20150322-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150313-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150223-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150206-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150107-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150101-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141220-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141216-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141208-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141014-t0ltetmo-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0ltetmo git
DonkeyCoyote Samsung Vendor git
Props and credit to:
The OmniROM team.
UtkarshGupta for providing advice in working through build issues on compiling OmniROM and maintaining for t0lte.
Rmanne for assistance in getting my previous efforts in getting the unofficial CM ROM running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.

Mine
10/14/14 - I know the camera is a bit weird with how it won't connect after a while. This is present in the unified build as well.

1st!! Yeah! Thanks for another great rom amd contribution to our community!

Coug is definitely one of the greats in our GN2 community. Total warrior in my book. Grateful for his time and talent.

Awesome build, but I am not getting any mobile data. I used Philz recovery. Anything I am missing here?
EDIT: Just tried with the latest TWRP also, still no mobile networks.

Mrzoops said:
Awesome build, but I am not getting any mobile data. I used Philz recovery. Anything I am missing here?
EDIT: Just tried with the latest TWRP also, still no mobile networks.
Click to expand...
Click to collapse
What does your APN show?

Nice.

Great Job
This instal went smooth and all seems to be working great. Nice rom TY

After a short sabbatical, T889 OmniRom is back. Still 4.4.4 KK.

What happened to the other omnirom thread?

Coug76 said:
As many of you know the GSM Note 2 is supported by Team OmniROM in a unified build format. This work is inspiring to me as the team split from CM for altruistic reasons. I have come to consider OmniROM my AOSP branch of choice due to their philosophy toward security and development.
I see a niche for our community where some of our members may be uncomfortable utilizing the unified build for any number of reasons.
My product is no more than a straight source built t0ltetmo build as the OmniROM spec is drawn up for the t0lte and adapted by the t0ltetmo spec on the OmniROM github. All source is available at the OmniROM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-Omni commits or "fixes" with very few exceptions. If it is broken in the unified build it will be broken in this one as well.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in OmniROM commits that looks promising I expect that I would post a new build. Getting to the point where stuff wasn't broken took some serious banging of the head.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial OmniRom .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
omni-4.4.4-20141208-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141014-t0ltetmo-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0ltetmo git
DonkeyCoyote Samsung Vendor git
Props and credit to:
The OmniROM team.
UtkarshGupta for providing advice in working through build issues on compiling OmniROM and maintaining for t0lte.
Rmanne for assistance in getting my previous efforts in getting the unofficial CM ROM running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Click to expand...
Click to collapse
Just a Heads up. Your file link is sending us to the att version...i didnt realize it until i tried to flash it and recovery advised it as such. I found th file by looking up your profile there it listed the correct t889 file. Downloading now.

butwhydoitalk2u said:
Just a Heads up. Your file link is sending us to the att version...i didnt realize it until i tried to flash it and recovery advised it as such. I found th file by looking up your profile there it listed the correct t889 file. Downloading now.
Click to expand...
Click to collapse
So it is. Did you DL the version from October then? I'll upload the correct version in a minute. I'll also do a clean build after the I walk the kids to school.
Coug

AngryDinosaur said:
What happened to the other omnirom thread?
Click to expand...
Click to collapse
UtkarshGupta is taking a step back to focus on more important things in life. He is working to hand off Omni for Note 2 to a new maintainer if one can be found.

Coug76 said:
So it is. Did you DL the version from October then? I'll upload the correct version in a minute. I'll also do a clean build after the I walk the kids to school.
Coug
Click to expand...
Click to collapse
I was able to find the file in your profile. So i downloaded it. I am currently running it and so far so good. Thanks.

butwhydoitalk2u said:
I was able to find the file in your profile. So i downloaded it. I am currently running it and so far so good. Thanks.
Click to expand...
Click to collapse
Thanks for the heads up. I have corrected the link and it is the 12/08/14 build. I just synced the repo for both Omni and CM and will run a build for both this morning. I should be able to post new builds this afternoon or evening depending on what the afternoon allows.

New build is up
EDIT: I pulled the DL link as the build was broken.

New build is up.

Coug76 said:
New build is up.
Click to expand...
Click to collapse
Could that new maintainer be you? Because cougmade omni is pretty slick, smooth sailing. ?
Thanks for the build.
Coug76 said:
UtkarshGupta is taking a step back to focus on more important things in life. He is working to hand off Omni for Note 2 to a new maintainer if one can be found.
Click to expand...
Click to collapse

I'm too much of a novice to take that role. That and my wife would invite me to find other living arrangements.

New build is up.

[ROM][SGH-I317 / T0LTEATT[4.4.4][UNOFFICIAL] OmniRom 4.4.4 - Builds of opportunity

As many of you know the GSM Note 2 is supported by Team OmniROM in a unified build format. This work is inspiring to me as the team split from CM for altruistic reasons. I have come to consider OmniROM my AOSP branch of choice due to their philosophy toward security and development.
I see a niche for our community where some of our members may be uncomfortable utilizing the unified build for any number of reasons.
My product is no more than a straight source built t0lteatt build as the OmniROM spec is drawn up for the t0lte and adapted by the t0lteatt spec on the OmniROM github. All source is available at the OmniROM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-Omni commits or "fixes" with very few exceptions. If it is broken in the unified build it will be broken in this one as well.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in OmniROM commits that looks promising I expect that I would post a new build. Getting to the point where stuff wasn't broken took some serious banging of the head.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial OmniRom .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
omni-4.4.4-20150323-t0lteatt-COUGMADE.zip
omni-4.4.4-20150313-t0lteatt-COUGMADE.zip
omni-4.4.4-20150224-t0lteatt-COUGMADE.zip
omni-4.4.4-20150206-t0lteatt-COUGMADE.zip
omni-4.4.4-20150107-t0lteatt-COUGMADE.zip
omni-4.4.4-20150101-t0lteatt-COUGMADE.zip
omni-4.4.4-20141220-t0lteatt-COUGMADE.zip
omni-4.4.4-20141216-t0lteatt-COUGMADE.zip
omni-4.4.4-20141208-t0lteatt-COUGMADE.zip
omni-4.4.4-20141014-t0lteatt-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0lteatt git
DonkeyCoyote Samsung Vendor git
Props and credit to:
The OmniROM team.
UtkarshGupta for providing advice in working through build issues on compiling OmniROM and maintaining for t0lte.
Rmanne for assistance in getting my previous efforts in getting the unofficial CM ROM running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.

Mine
10/14/14 - I know the camera is a bit weird with how it won't connect after a while. This is present in the unified build as well.

Thank you for this! my Att Note 2 is far from dead and the way Att and the other "Providers" want to charge for every single little stinkin' thing.. (A 40$ SmartPhone charge from ATT? NO WAY) is ridiculous I plan to make this phone last quite a while if possible and folks like YOU and stuff like THIS make that possible! Thank you sir!

This type of thing is my way of giving back to the community and developing my understanding of the software we rely on.

does tethering work with this rom?

Main Difference From OmniROM
I have installed both OmniROM and this variant but I can't tell the difference. Can you explain?
Thank you very much in advance.

fresnogamer said:
I have installed both OmniROM and this variant but I can't tell the difference. Can you explain?
Thank you very much in advance.
Click to expand...
Click to collapse
The only difference is this is built from source with the I317 build prop baked in from the start. It is nothing earth shattering. Some folks really prefer a ROM built for the specific model they use.

New build is up. Still KK.

i cant install it... Status 7 , installation aborted
Edit: I installed the newest TWRP recovery and it worked ... thanks a lot, i'll be trying this ROM
Edit 2: Lost root access?

New build is up.
EDIT: I pulled the DL link as the build was broken.

New build is up.

New build is up.

Change log?
Coug76 said:
New build is up.
Click to expand...
Click to collapse
Forgive my ignorance if I am missing it.
Is there a change log indicating updates between releases?
Awesome Rom BTW.

parakleet said:
Forgive my ignorance if I am missing it.
Is there a change log indicating updates between releases?
Awesome Rom BTW.
Click to expand...
Click to collapse
omni.cmxlog.com/4.4/t0lte/

Coug76 said:
omni.cmxlog.com/4.4/t0lte/
Click to expand...
Click to collapse
Cold Blooded
THanks

Happy New Build!

Coug76 said:
Happy New Build!
Click to expand...
Click to collapse
This one did not like a dirty flash.
Clean flash worked well though.

parakleet said:
This one did not like a dirty flash.
Clean flash worked well though.
Click to expand...
Click to collapse
Thanks for the feedback.

New build is up.

New build is up.

[ROM][6.0.1] UNOFFICIAL CyanogenMod 13.0 (DDK 1.9)

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 toro (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=24588232905721322
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970093
All builds: https://www.androidfilehost.com/?w=files&flid=23530
Unofficial TWRP build: https://www.androidfilehost.com/?fid=24459283995311442
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (required due to system partition restraints)
Bugs
- No mobile data out of airplane mode - reboot to fix.
XDA:DevDB Information
UNOFFICIAL CM13, ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-12-30
Last Updated 2016-07-16

Sources and such
https://github.com/CyanogenMod/
https://github.com/musical-chairs
This would not be possible without @Ziyan and @MWisBest. @zzpianoman has also been a tremendous help. Be sure to visit their threads, thank them, and support their work.

Sweet... can't wait to try this out! There is no download tab btw.

TheYoz said:
Sweet... can't wait to try this out! There is no download tab btw.
Click to expand...
Click to collapse
Yeah sorry about that, my upload failed, trying again...
Edit: I'm having problems uploading to xda, trying another option...

There is no download for this. Cannot wait to try this out.

I might give this a try while I wait for my GNexus to die. I want to get my hands on Lollipop and can't wait for my N6.

rippedwarrior69 said:
There is no download for this. Cannot wait to try this out.
Click to expand...
Click to collapse
XDA keeps giving me a server IO error, after uploading the whole file. I'm still trying to get a good upload either to xda or to another hosting site.

Finally a successful upload!
https://www.androidfilehost.com/?fid=95864024717073147
Now I can start working on the next build!

New build up:
https://www.androidfilehost.com/?fid=95864024717073317
Synced with cm's latest sources as of 12-31-2014. I'll be working on toroplus for a bit, trying to get ril to behave properly there, so toro will be waiting for a maybe a week, unless there are any exciting new features or bug fixes.

@musical_chairs, I'm the gnex maintainer for LiquidSmooth. I have LP maguro builds that are all good, but my toro builds don't have data, and my toroplus builds don't have voice or data. I think I have toroplus figured out and I'll know with a test build that'll be done in a few hours. With toro, though, MW and I are stumped. Would you mind sharing details on how you got CM12 toro data working?
[poo]

poo706 said:
@musical_chairs, I'm the gnex maintainer for LiquidSmooth. I have LP maguro builds that are all good, but my toro builds don't have data, and my toroplus builds don't have voice or data. I think I have toroplus figured out and I'll know with a test build that'll be done in a few hours. With toro, though, MW and I are stumped. Would you mind sharing details on how you got CM12 toro data working?
[poo]
Click to expand...
Click to collapse
Sure! I'm currently stuck with toroplus, ril is completely broken, no service of any kind. I'd be interested in knowing how you got that working.
For data on toro, I picked these commits from MWisBest's github:
https://github.com/MWisBest/android...mmit/7611a40b233517384d56d1f93caa7fd836c376af
https://github.com/MWisBest/proprie...mmit/5d70b4a8d019d60102432ca29f738e6e7c39a978
I also added some stuff to system.prop, patch is attached to this post. Again, I take no credit for it, it's copied from MWisBest.

musical_chairs said:
Sure! I'm currently stuck with toroplus, ril is completely broken, no service of any kind. I'd be interested in knowing how you got that working.
For data on toro, I picked these commits from MWisBest's github:
https://github.com/MWisBest/android...mmit/7611a40b233517384d56d1f93caa7fd836c376af
https://github.com/MWisBest/proprie...mmit/5d70b4a8d019d60102432ca29f738e6e7c39a978
I also added some stuff to system.prop, patch is attached to this post. Again, I take no credit for it, it's copied from MWisBest.
Click to expand...
Click to collapse
If I manage to get toroplus going, I'll certainly relay that back to you.
I've also applied those same commits from MW, and I'm pretty sure I'm using all the same build.prop entries. What was your starting point? device_samsung_toro from CM? What I did (at ziyan's advice) was start with the latest JB-era repo from google, apply like 5 commits from Ziyan's maguro repo, then the MW stuff.
[poo]

poo706 said:
If I manage to get toroplus going, I'll certainly relay that back to you.
I've also applied those same commits from MW, and I'm pretty sure I'm using all the same build.prop entries. What was your starting point? device_samsung_toro from CM? What I did (at ziyan's advice) was start with the latest JB-era repo from google, apply like 5 commits from Ziyan's maguro repo, then the MW stuff.
[poo]
Click to expand...
Click to collapse
device_samsung_toro is from cm, cm-11.0 branch. device_samsung_tuna and proprietary_vendor_samsung are from Ziyan, cm-12.0 branch.

musical_chairs said:
device_samsung_toro is from cm, cm-11.0 branch. device_samsung_tuna and proprietary_vendor_samsung are from Ziyan, cm-12.0 branch.
Click to expand...
Click to collapse
Ok, that gives me something to try then. I'm also using the same tuna and samsung vendor repos. Are you using ziyan's omap kernel repo?
[poo]

poo706 said:
Ok, that gives me something to try then. I'm also using the same tuna and samsung vendor repos. Are you using ziyan's omap kernel repo?
[poo]
Click to expand...
Click to collapse
Yes.

waitin to see how this turns out...appreciate your work here...

I flashed this just to try it out. It looks amazing. Is there no mobile data on this rom? I am on verizon i515. I flashed it had the signal bars but said disconneted. I did have a imei number. I flashed with cwm touch 6.0.4.3

rippedwarrior69 said:
I flashed this just to try it out. It looks amazing. Is there no mobile data on this rom? I am on verizon i515. I flashed it had the signal bars but said disconneted. I did have a imei number. I flashed with cwm touch 6.0.4.3
Click to expand...
Click to collapse
There is supposed to be mobile data, it works here. I don't think I did anything special to get it working, though I did mess around a bit with some settings (Testing menu settings, APN settings) on my first few builds and haven't done a clean flash real recently.

I'm new to this phone. I thought you could just flash like I did on my note 2 i605. If mobile data works I want some 5.0

It looks like I had the same issue as zzpianoman on his cm12 build. If you flash his APN fix, you should get working data:
http://forum.xda-developers.com/showpost.php?p=57890624&postcount=17

What to flash in case of update Lineage OS?

Hello,
I am currently running a nighly build of Lineage OS 14.1 on my LG G2.
I was wondering:
- when a new 14.1 nighly comes out: Do I have to flash the Gapps and root zip also after (dirty) flashing the new nightly?
- and what in case of a 14.2 build or even a 15 build? Do I have to do a clean install in that case?
Thank you in advance!

Don't know about 14.2 or 15 because they are still no where.
But for new 14.1 no need to flash g apps and root zip again.

FrankFrank456 said:
Hello,
I am currently running a nighly build of Lineage OS 14.1 on my LG G2.
I was wondering:
- when a new 14.1 nighly comes out: Do I have to flash the Gapps and root zip also after (dirty) flashing the new nightly?
- and what in case of a 14.2 build or even a 15 build? Do I have to do a clean install in that case?
Thank you in advance!
Click to expand...
Click to collapse
It doesn't hurt to flash an updated GApps package along with the Nightly update.
If you have SuperSU, then you should flash it again along with the Nightly update. This is because updating the Nightly also affects the SuperSU modifications and binaries. Re-flashing the SuperSU will reinstate the SuperSU modifications and binary installation.
If you don't re-flash SuperSU, then you'll get a notification from the SuperSU app that the binaries need to be installed.
So the GApps is up to you and the SuperSU is a yes.
I wish you the best of luck!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************

FrankFrank456 said:
Hello,
I am currently running a nighly build of Lineage OS 14.1 on my LG G2.
I was wondering:
- when a new 14.1 nighly comes out: Do I have to flash the Gapps and root zip also after (dirty) flashing the new nightly?
- and what in case of a 14.2 build or even a 15 build? Do I have to do a clean install in that case?
Thank you in advance!
Click to expand...
Click to collapse
To add on to what @Ibuprophen said...
Historically speaking, dirty flashes are usually fine within the same major version number, while clean flashes are often required when the major version number changes.
The ROM maintainer will provide instructions for any exception to this general rule.

Thank you for your replies!
Is 14.1 --> 14.2 a major version number jhedfors? I mean: when there is 14.2, can I flash it dirty?
I flashed my phone yesterday, and I got a lot of errors. After flashing Gapps and the root-zip from Lineage, it was all solved. So in my case I have to flash them all again everty time.

FrankFrank456 said:
Thank you for your replies!
Is 14.1 --> 14.2 a major version number jhedfors? I mean: when there is 14.2, can I flash it dirty?
I flashed my phone yesterday, and I got a lot of errors. After flashing Gapps and the root-zip from Lineage, it was all solved. So in my case I have to flash them all again everty time.
Click to expand...
Click to collapse
Current versioning is as follows: Major.Minor.Patch
That would be considered a minor change. But as I mentioned, it all depends on the advice from the maintainer.
You should not need to flash either Gapps or official Lineage superuser after nightly update. You might want to post logs of you have any issues next nightly update.

jhedfors said:
Current versioning is as follows: Major.Minor.Patch
That would be considered a minor change. But as I mentioned, it all depends on the advice from the maintainer.
You should not need to flash either Gapps or official Lineage superuser after nightly update. You might want to post logs of you have any issues next nightly update.
Click to expand...
Click to collapse
Ok I will, thanks!