yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] invisiblek:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we 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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review.

Download Links

CyanogenMod:

Nightly: http://download.cyanogenmod.org/?device=d2vzw&type=nightly

Google apps addon:

OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 6.0)

HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.

Firmware:

Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip

Misc Links

Unoffical changelog:

Link: http://www.cmxlog.com/13/d2vzw/

Learn to build yourself:

Link: https://wiki.cyanogenmod.org/w/Build_for_d2vzw

The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

XDA:DevDB Information

[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III

Contributors

invisiblek

Source Code: http://github.com/CyanogenMod/

ROM OS Version: 6.0.x Marshmallow

Version Information

Status: Nightlies

Created 2015-12-12

Last Updated 2015-12-12
[Verizon Samsung Galaxy S III] jdiamond7:
Clean flashed earlier today and seems to be running great. Haven't found anything that doesn't work yet, camera, video, phone calls, GPS all seem to be working fine. Might be the best first nightly for any CM release on this device.
[Verizon Samsung Galaxy S III] bryank29:
So installed Stock Gapps and the 1st nightly. So far so good, though I didn't get any of the stock CM software like messaging and the browser.

The default google camera gave me the typical "camera has failed" error that I got non stop on 12.1. My solution was always going with Open Camera. Never had issues but in a blue moon.

Any clue why?
[Verizon Samsung Galaxy S III] Shakes The AssClown:
So if we are on 12.1, do we need to use the nuke it wiper that was mentioned in the unofficial nightlies?
[Verizon Samsung Galaxy S III] yorkwar:
I remember CyanogenMod said a dirty flash from 12.1 is possible, but just not tried it yet:)
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Do we need any special version of TWRP to flash this for 6.0?
[Verizon Samsung Galaxy S III] 65vdub:
Nope, flashed it with the latest twrp image from their site on my old s3 and it booted up just fine
[Verizon Samsung Galaxy S III] Shakes The AssClown:
So what exactly is working right and what still needs tweaking? Is this a daily driver at this point?
[Verizon Samsung Galaxy S III] pogeymanz:
I'm getting a no SIM error. I tried using the Nuke_it.zip from Invisiblek's unofficial builds thread and it didn't work.
[Verizon Samsung Galaxy S III] Master Cylinder:
All Hail to [MENTION=2385005]invisiblek[/MENTION]!

Hmmm... I've had this before but not on the last 4 builds or so. Dirty flashed originally over the 12/10 unofficial, and have been going on - now on 12/14. If you flash from 12.1 it seems you'd have to use the nuke_it.zip. I tried it on the other MM ROM out there without success, too. Started from scratch here, as baaaaaaaaaad as I hate to clean flash.
[Verizon Samsung Galaxy S III] pogeymanz:
Yeah, I hate to clean flash, too. It's almost never actually necessary.

However this time it doesn't seem to matter if I clean or dirty flash, or whether I use the nuke_it.zip or not. I've tried the 12/13 and 12/14 builds with no luck. I've not tried any others.

I doubt it's possible, but I wonder if it has to do with either the fact that I've encrypted my storage or if it matters that I'm using f2fs on my cache and data partitions. Neither of those obviously mattered for 12.1 and neither *should* have anything to do with reading from the SIM...
[Verizon Samsung Galaxy S III] Master Cylinder:
Don't use nuke-it.zip if you're clean flashing. They changed the database files for the phone, etc , from [MENTION=1782878]Stealth111[/MENTION]'s thread "nuking your old telephony and settings databases." on 11/21 cm13 or so. Everything after that is the new ones.

This has been a strange gremlin popping up - I'm surprised to see it still rear it's ugly head. You could use one of the last unofficial builds and then update on that - that's what I've done just out of laziness. Got Xposed and Gravity Box running.

Front facing camera will lock the app when clicked. Logcat to come.
[Verizon Samsung Galaxy S III] pogeymanz:
Thanks for the reply. I do understand what the nuke_it.zip was for and why it's unnecessary on a clean flash. I didn't articulate that.

I think I will try your suggestion of trying out an unofficial build and see if that works. Do you have any suggestions for which build to try? I'm wondering if I should try one before 11/21, then run the nuke_it.zip on upgrade, or if I should try one after the database change over.

I'll probably end up doing both strategies because neither will work...
[Verizon Samsung Galaxy S III] Master Cylinder:
I used 11/25 which didn't need the zip and have just kept going.
[Verizon Samsung Galaxy S III] Deliquified:
Here's the new changelogs for CM13 builds: http://www.cmxlog.com/13/d2vzw/

Thanks to invisiblek and CM Team for keeping us current!
[Verizon Samsung Galaxy S III] toosurreal01:
Great work!
[Verizon Samsung Galaxy S III] AyUaxe:
Anyone try navigation with this rom and 6.0 gapps? Btw, glad to see [MENTION=2385005]invisiblek[/MENTION] back in the d2 saddle. Thanks!
[Verizon Samsung Galaxy S III] Master Cylinder:
The d2vzw must have 9 lives because this is gonna make it last quite awhile longer!!

Let's give it up for [MENTION=2385005]invisiblek[/MENTION] once more!

Darn! Gif animation doesn't work on the XDA phone app.

Mine seems to do better in battery saving mode than the other 2 - puts my address across the street but the dot is next door.
[Verizon Samsung Galaxy S III] Fenix2002:
I haven't tried it while driving, but I've used it while walking, biking, and hiking. I have no idea what the difference is, but GPS is flawless on MM whereas I couldn't get a lock since KK. I usually get GPS fix in ~30-40s to ~5m accuracy. [[EDIT: That's actually in GPS only mode.]] My experience is that Mapquest is better for handling navigation purposes than Maps. Idk. Personal preference.

I follow in the footsteps of those before me, and hail the mighty invisiblek!
[Verizon Samsung Galaxy S III] Jaws4God:
does anyone have a list of what currently doesn't work? I accidently flashed this when doing the weekly updates..

From what i noticed when just quickly messing with it..

Video Camera did not work (said couldn't access camera)

Front Facing camera froze (took picture but then would not let me click anything)
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks for the clarification. That's what i thought and tried first, but nothing happened. I saw that touches on build date did have an effect and that's how i found demo mode. Yet to discover of it means demonstration or demolition. Evidently, my cm 13 install is just borked, so it's restore the back up and start over.
[Verizon Samsung Galaxy S III] Jaws4God:
just flashed 1/26 .....

camera app had some slight changes.. (blue ring around snap button)

front camera still force closes :(
[Verizon Samsung Galaxy S III] static.chaos73:
I installed the 1/26 update and Xposed modules aren't working anymore. I have uninstalled/reinstalled everything. I only have two - adblock and disable root notification on status bar. Anyone else have issues with Xposed in the latest build?
[Verizon Samsung Galaxy S III] Jaws4God:
i do like on the 1/26 build you can hide brightness slider

[emoji106]
[Verizon Samsung Galaxy S III] Master Cylinder:
Mine are all working. However, I DID just also install the latest Xposedinstaller_3.0-alpha4.apk from rovo89's official thread, whereas I had alpha2 before. Maybe that'll help ya?
[Verizon Samsung Galaxy S III] a11m1ghty:
Anyway I can upgrade my S3 VZW with 4.4.2 to this?
[Verizon Samsung Galaxy S III] phonetool:
Nope, sorry.
[Verizon Samsung Galaxy S III] Jaws4God:
just flashed the 1/29 build.. front camera still Force Closes..
[Verizon Samsung Galaxy S III] Jaws4God:
what are the soft key ways to take a screenshot? all i know of right now is hard keys (hold power button menu) or power and home down volume...

thanks!
[Verizon Samsung Galaxy S III] Master Cylinder:
There are none built into the ROM. I use the Xposed module Gravity Box to accomplish this, though there are also apps on Play that are supposed to do it. Had trouble getting any of those to work.
[Verizon Samsung Galaxy S III] Jaws4God:
i downloaded xposed.. but it showed a warning before i could install that my structure wasnt compatible yet.. anyone else see that?
[Verizon Samsung Galaxy S III] Roger W:
Here's a recap of things I've encountered that don't yet work as well on CM13 as on 12.1. Most have already been covered earlier in the thread, but I'm just curious if anyone has found a workaround or if a clean install fixes anything since my last one a month ago.

1. Bluetooth call problems when Phone and Media profile are both active

2. SIM not recognized on encrypted device (haven't tried for weeks because it requires a full wipe)

3. Wifi Hotspot 5GHz mode doesn't work

4. Some apps can't use light sensor (but google maps goes into night mode when I drive through tunnels, so either something works or Google crowdsources brightness data to toggle tunnel mode by GPS (?))

5. Front camera problems

6. Bluetooth connection to car keeps phone Awake and draining battery even without anything playing. I think this used to be better.

Anyone know anything to the contrary? Thanks!
[Verizon Samsung Galaxy S III] Master Cylinder:
...

You got to get the right one: v79sdk23. there's a v79sdk21, 22 and 23 all one after the other on that thread. KitKat, LP and MM.
[Verizon Samsung Galaxy S III] Jaws4God:
i went to the forum.. several listed there.. would u be able to provide the link to the exact file? thanks so much!

i see......

v79sdk23 arm

v79sdk23 arm64

v79sdk23 x86

i think we have arm right?
[Verizon Samsung Galaxy S III] Jaws4God:
Got It! I used xposed (arm) to install gravity box.. they have a setting for navigation keys.. so now my onscreen back button can...

hold: for screenshot

double tap: to turn of screen.

Thank You!!!! [emoji106] [emoji1] [emoji2] [emoji3]
[Verizon Samsung Galaxy S III] Master Cylinder:
Awesome! Yeah, I have no power button, so I need a way to take a screen shot plus turn the screen off. (I have a widget to reboot/power down, etc ....) I also install a flash file for Omniswitch, plus a toggle apk and I can use Omniswitch for recents by remapping the home key as well! :cyclops:Plus, Gravity Box has many other great features. It's a play ground! I've been using it since LP first came out. Love to have an image on the notification pulldown background!

He's always reminding me: if you ain't laughin', (and getting away with something) you ain't livin'!
[Verizon Samsung Galaxy S III] Fenix2002:
02/03 build

Most stuff seems to be pretty good.

New LiveLockScreen re-enables on every boot for me, which is a nuisance.

Light sensor still not working.

Front camera still not working.

New issue that I've encountered is that sometimes the screen orientation won't change, even though it's set to auto.

Any ideas why?
[Verizon Samsung Galaxy S III] Master Cylinder:
No, but I'm seeing the same thing. Kinda need that with these things. I haven't been paying attention to the commit history or anything... You get that Gravity Box to work? By the way, there might be a problem where it takes a trick to get it to actually work.

(Dang! Thought I posted this last night!)

:eek:
[Verizon Samsung Galaxy S III] Jaws4God:
yeah im back on 12.1 since the camera issues on CM13 pissed me off.. LOL I hope to keep hearing from you all on big fixes..

how is the 2/5 build? i didn't see any build notes about camera... :-/

i did use GB on both CM13 and CM12.1 .. only was able to use back button to do screen record and power menu. I asked on their thread, but they are clear that CM is not supported by GB.. so any glitches or issues cannot be addressed..
[Verizon Samsung Galaxy S III] Fenix2002:
2/7 build

Lots of CM kernel changes. Not sure what everything did, but it happened. Lol.

Front camera still not working right.

Light sensor still not working.

Auto-rotate still hit or miss.

Personal note: my battery life is ****e on CM13, compared to 12.1. When inactive and doze takes over, I see good savings. When I use it with screen at lowest brightness, powersave, etc., just casually surfing the web or reading the news, I'm seeing like 1% drop every minute or 2. Much more than used to, especially on non-intense use, completely negates doze benefits. (typing this, I lost 5%)
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey that's out of control! Something must be going on. My b-life is fine. You could use OS Monitor to see what's eating so many cycles on your cpu, if something is. I've looked in there and said "Hey! who told you to start and run all the time and eat so many cycles!! Huh?"

I was going to say that you can go to Settings>Privacy>Privacy Guard and then select 3 dots and touch 'Advanced.' You can stop things from starting automatically here or using wakelocks, with stats there about how much and when they've been doing it. I've found apps obnoxiously launching themselves at startup that I never or rarely use. However I just tried to access it and I'm getting a settings fc on 2/7.

Getting a battery stats app going is probably a good idea. Gsam is one that I've used and Better Battery Stats is one everyone likes but I think you gotta pay on that one.

I also use Greenify to automatically put things to sleep.

:good:
[Verizon Samsung Galaxy S III] Jaws4God:
i got excited when i saw some camera (Snap) updates on 2/12 build... no luck.. front camera froze with first try.. oh well. lol
[Verizon Samsung Galaxy S III] Fenix2002:
Bummer. :( Light sensor or orientation working?
[Verizon Samsung Galaxy S III] Jaws4God:
to be honest.. not sure what light sensor is for.. or how to test..

didn't know about orientation
[Verizon Samsung Galaxy S III] tofa655:
How to more battery life with this rom?
[Verizon Samsung Galaxy S III] Fenix2002:
Light sensor works for a few things, primarily auto-brightness. I have a sensor app, "Phone Tester" from the play store that has readouts of all the sensors, and other information. Pretty cool.

Settings>Battery>Battery Mode and change to a less aggressive mode. Or install Decimalman's dkp kernel, which you can find in this forum. It has some good CPU governors that you'll have to tweak by downloading the "Kernel Adiutor" app from the play store.

Lowering screen brightness, turning off mobile data or WiFi when not needed, turning off background data, etc., are all options to save battery as well.
[Verizon Samsung Galaxy S III] Jaws4God:
i haven't been on the ROM for very long due to the camera issues . but the times i was i was VERY impressed with battery life.. doze and the other battery savers work well. I felt like it was much better than Lollipop.
[Verizon Samsung Galaxy S III] XdrummerXboy:
On 2-12 right now. Either there were a lot of Bluetooth fixes in the last 2 weeks or wiping the cache after updating fixed my issues.

BT audio was borked for a while, half the playtime was spent glitching out. Now it's actually usable, however it still has minor issues like skipping a split second (1/10 of a second maybe?) Every 30-45 seconds.
[Verizon Samsung Galaxy S III] Roger W:
For anyone wondering, the 2/17 nightly still has the encryption problem that CM13 has always had for this device (no SIM found)
[Verizon Samsung Galaxy S III] Jaws4God:
i guess i don't see that error since i have an old Verizon sim card in mine. thought it was needed to get data after going to 4.4+.

any front camera fix? light sensor?
[Verizon Samsung Galaxy S III] Deliquified:
Bunch of camera fixes for tonight's nightly.. Let's hope one of them fixes the ffc
[Verizon Samsung Galaxy S III] charliepop:
Front camera is working for me on 2/17.
[Verizon Samsung Galaxy S III] Deliquified:
Does Skype work? FFC video and the ability to Skype was the last thing keeping me from upgrading to MM
[Verizon Samsung Galaxy S III] charliepop:
I have taken pictures and video with the front facing camera with no problems. I would think Skype would work , but can't say for certain.

Edit : I dug up my old Skype account and downloaded the app. I don't have any contacts online , but when I tried to make a video call it brought up the front facing camera and seemed to be working like it should.
[Verizon Samsung Galaxy S III] Roger W:
Are you saying that you can use the "Encrypt Phone" feature without SIM problems after it finishes encrypting? I and others have had that always fail since the switch to CM13, and I also have an old Verizon SIM (well, 3-4 years).

Front camera still doesn't work for me, and this is a clean install. I can take one front shot (using stock app or OpenCamera) then the phone grinds to a halt and I have to reboot.

Light sensor still registers 0.0.

Bluetooth still doesn't work correctly when the Media and Phone profiles are both active on a device like my car.
[Verizon Samsung Galaxy S III] Jaws4God:
anyone else it working?
[Verizon Samsung Galaxy S III] charliepop:
Guess I should have noted my phone is the sch-s968c straight talk variant. Thought it was in my signature.
[Verizon Samsung Galaxy S III] Jaws4God:
2/17 front camera did not work for me...
[Verizon Samsung Galaxy S III] Jaws4God:
2/18 had some snap updates.. none fixed the front camera
[Verizon Samsung Galaxy S III] Roger W:
Dumb question - today's change notes mention bugfixes in the LockClock calendar. Is that exposed in our ROM in a way that I'm missing, or is that not available on our device? In KitKat I really liked having the "cLock" widget on the lock screen so I could see my upcoming calendar without typing my PIN. In LP and M, I am using WidgetPager to provide a button that pops up a page of Chronus widgets to replace that, but it's an extra tap and a little hacky. Am I missing something?
[Verizon Samsung Galaxy S III] Fenix2002:
Idk, but that would be nice. It's one of the things I'd like to see in a stable version of CM13 along with stable front camera, and I hope the encryption thing gets taken care of.
[Verizon Samsung Galaxy S III] Jaws4God:
how is it working for ya? what gapps? clean install?

thanks!

Edit, I tried installing CM13 2/20 with no gapps.. front camera still failed...
[Verizon Samsung Galaxy S III] dvschnk:
Thanks, for the edit. Still waiting for the front camera to be completely fixed before I hop into this. Waiting patiently on CM12.1
[Verizon Samsung Galaxy S III] Jaws4God:
well the CM12.1 video froze on me.. so i said screw it.. ill go with CM13.. just fyi the 2/21 version front camera hard freezes and reboots. lol
[Verizon Samsung Galaxy S III] Jaws4God:
2/22 update. Front camera FC with too much light.. (low light works)
[Verizon Samsung Galaxy S III] Fenix2002:
Dang, got my hopes up.

I don't understand (and maybe someone could enlighten me) why the camera can work in one android version and not the next. I understand that the proprietary camera code can't be used, and so custom code has to be written to replace that. What I don't get is why that has to happen with each OS update. I would assume once you had the code in one, it would *just work*. I guess there are too many standard library changes with each android version and so those changes have to be accommodated?
[Verizon Samsung Galaxy S III] Jaws4God:
is anyone using exchange email on CM13? the stock email doesn't list the option and gmail says security update but then hangs up..

thanks.
[Verizon Samsung Galaxy S III] Deliquified:
You pretty much already answered yourself. With every version of Android there's different code, libs, and proprietary code. It's like a puzzle.. Someone has to figure out what's going on, what's been changed, and how to hack around it to make things work without being able to see Samsung's code. It's equivalent to feeling around in the dark to find something you dropped. There's hundreds to thousands of lines of code that change with each version of Android.. Not nearly as simple as changing one or two things and calling it a day. Things take longer and longer to fix in time as people migrate to new phones