yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] dltccf:
Only issues I have with this is com.android.clock stops randomly and com.android.phone stops when I try to send a text. Also seems to be related to having mobile data disconnect most of the time. Everything looks fine, but mobile data just goes disconnected. Anyone else having these problems? Or has everyone moved on to the CM13 nightlys? I'm trying to decide if moving to CM13 might solve my issues or not be worth it.

Thanks
[Verizon Samsung Galaxy S III] matt_man:
I'm having far fewer issues with data connection on CM13 than I did on CM12. Battery life has been much better for me also.
[Verizon Samsung Galaxy S III] dltccf:
well, I've upgrade to CM13, we will see how it goes. It took several attempts but I am now on the 1/8 nightly
[Verizon Samsung Galaxy S III] Jaws4God:
what are your impressions so far?
[Verizon Samsung Galaxy S III] Jaws4God:
are you having camera issues? im back on 12.1 because i need a stable camera [emoji1]
[Verizon Samsung Galaxy S III] justinnotjason:
Edited because I've discovered that reading are hard. :o:laugh:

Don't mind this post. Changing it to say thanks to everyone for maintaining my DD ROM!
[Verizon Samsung Galaxy S III] dltccf:
Impression is good, it solved the data connection problem and the clock has stopped error. Camera works fine although I haven't tried using the front camera as I just never use it.
[Verizon Samsung Galaxy S III] Jaws4God:
How stable is the back camera?
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey! I guess this is redundant since you've moved on to MM. I'm wondering where you came from before getting this on your phone. I've seen those problems here and on my phone but not on the builds for the last months ending on 12/10. Really cm12 at the end is the most reliable ROM for our phone so far, in my experience. AICP has continued to put out Lollipop builds for our phone based on cm12 until sometime this month I think? So there is still some final refinements out there but we got abandoned by our maintainer and the builds all disappeared. Even the cm13 build links are there for every build but only the last 6 or so work. Used to always have access to builds past and present. Maybe someone did the numbers on d2vzw users out there. We're lucky to have 2 ROMs based on cm13 - other d2 devices have been abandoned for MM.

Enough of a rant. I've had to go back to my 12/10 nandroid from cm13 numerous times when I needed everything to work and I couldn't effe around, but dang if that nandroid ain't 4.5GB!! I've been having problems in cm13 with Bluetooth but I finally figured out to disable "Media" and my earpiece works now. No one else has been having issues it seems.

LOL!:laugh:
[Verizon Samsung Galaxy S III] Master Cylinder:
Back camera works fine - they just put in a new camera app "Snap" but it's been working for me for awhile using "A Better Camera". Front camera is still hosed.
[Verizon Samsung Galaxy S III] Jaws4God:
which version has "Snap"? im trying to decide if back camera is stable.. i may try to use CM13 as DD.. [emoji102]
[Verizon Samsung Galaxy S III] Master Cylinder:
It looks like it's called SnapDragon Camera. I'm not sure when it started in the build but 1/15 and up for sure. MAN! They already pruned the 6th build off the list and only the last 5 builds are available for our phone at any given time. The links are there but all you get for your trouble is "404."
[Verizon Samsung Galaxy S III] Jaws4God:
cool thanks! do you think they can incorporate snapdragon camera for the front to make it stable?

are you able to use all features on back camera? video also?

thank you.
[Verizon Samsung Galaxy S III] Master Cylinder:
Je n'est pas. But, ask over at invisiblek's Official CM13 thread. That's where it's at.:good:

EDIT: Ooops! Forgot you already been over there.
[Verizon Samsung Galaxy S III] justinnotjason:
My LTE data connection isn't working. I'm on CM12.1 and the December 12th build (20151210). I'm investigating and I'll keep you up to date.
[Verizon Samsung Galaxy S III] mav3rick478:
change your access point and it well correct itself.
[Verizon Samsung Galaxy S III] justinnotjason:
Thank you. That worked....literally immediately.
[Verizon Samsung Galaxy S III] Master Cylinder:
Dang! I posted 1 minute after you did!

Well, there are some other pointers in the OP in the "Notes - Bugs" section.
[Verizon Samsung Galaxy S III] mav3rick478:
Learned it from you guys! [emoji106]
[Verizon Samsung Galaxy S III] justinnotjason:
I saw it but my issue was that it hadn't happened on reboot. It just randomly stopped working. Should've tried it anyway though :silly:
[Verizon Samsung Galaxy S III] Master Cylinder:
If you're using the NE1 modem you'll probably have occasional problems that the APN trick will solve. Switching to the ML1 modem should fix it more permanently but I haven't tried it on cm13 and I know you are using that one, too. Probably would work fine. Now that I mention it, I'll probably try ML1 myself on cm13.
[Verizon Samsung Galaxy S III] John877:
Hi Im new here and I will admit that I didnt scan all the pages of this thread so if its been covered, I apologize for bringing this up again.

I just got a used Samsung Galaxy SIII Verizon SCH-I535 (d2vzw) and its not my main phone, I use a non-smart phone as my main so if something bad happened Im not out of communication. Of course Id prefer not to brick it though.

So my question is, seeing the main headline saying Cyanogen and d2vzw are together again, does that mean even if it currently has stock Android OS on it from Verizon? Currently it has AOS 4.4.2 (KitKat) installed and I understand that with the 4.3 update they introduced a heavily locked bootloader, so Im wondering if this thread means that something has been done to bypass that bootloader to be able to install Cyanogen on it? Id really like to properly root the phone as right now Ive just used towelroot and some apps like LuckyPatcher tell me that root is unstable or something to that effect and cant do some things.

If this is possible to do I would love a step by step procedure. I am fairly familiar with Odin and some recovery steps so I would like to consider myself not a complete newb :D but when it comes to coding I am clueless. I did try to play with some things when I first got it though and ended up getting the yellow triangle and it only booting to the screen saying that it detected unauthorized software etc which I managed to fix by googling and finding a debrick file.

Id appreciate if theres some way to help with getting Cyanogen on this phone.

Thanks
[Verizon Samsung Galaxy S III] phonetool:
Short answer, no cm for you.

"together again " refers to the cm branch especially for the vzw device forking off again after a brief time of being muddled together with other devices.

Your best bet is mohamedafneh's superlite rom. Stock, but cleaned up and rooted.
[Verizon Samsung Galaxy S III] John877:
What about the bootloader? Wont installing that cause an issue with the bootloader?
[Verizon Samsung Galaxy S III] Master Cylinder:
We are all into hacking and getting away with stuff here, but Lucky Patcher is frowned upon since it directly takes money away from devs.

You should go to look at the first few threads in the And. Dev. section instead of the Orig And. Dev. section since all your answers are there.
[Verizon Samsung Galaxy S III] John877:
I understand that and I apologize if I overstepped. To be honest Lucky Patcher isnt really my concern I was just mentioning a message I got in that program about root being unstable. My bigger concern or rather desire was wondering about the bootloader and whether I can ut a different ROM on such as Cyanogen but I guess theres still no way around it which sucks. I looked into what the other guy above mentioned with that SuperSlim ROM so My guess is that that is likely one of my only options.
[Verizon Samsung Galaxy S III] Master Cylinder:
There might be a way around it, but I can't vouch for it. Best thing to do is follow the advice from my previous post.
[Verizon Samsung Galaxy S III] John877:
This section? http://xdaforums.com/android

Theres so many sections and subsections lol

As for that possible way, could you give more info and maybe I can look into it more or try it myself?
[Verizon Samsung Galaxy S III] Master Cylinder:
No, and ya!

Go to the top of this page and just underneath the banner you'll see the live links indicating where you are in the hierarchy of site. The first one to the right of the house (home) symbol is the top level for our device. If you click on it, you'll see the subforums for our device. Look at the And. Dev. forum and you'll see information in the sticky roll-up thread and there is another one about flashing partially a different bootloader that could open the door to Cyanogenmod. Best to go to that thread and read all through it and even ask your question in it. :good:

However! I don't know if this works or not! Or what you'll end up with after. One guy did get it to work I think, but then, without knowing this (which was a new technique at the time - just a few weeks) existed or him communicating it, he posted a problem and I suggested to flash the standard unlocked bootloaders package for our device which was the main solution for his problem and he permanently bricked his phone.

EDIT: Actually, I think he made a reference to it but I didn't know what the issues were. Now I do!
[Verizon Samsung Galaxy S III] Droidriven:
Yeah, I remember that one. As I recall it didn't go so well.

It would still be nice for someone that understands it well to tear that method apart and see what is actually possible or not possible with it. There may be a way to get more benefit out of if that road can be followed a little further, I just don't understand it well enough to know if its "downgrading" enough of the right stuff to actually do anything productive with it.
[Verizon Samsung Galaxy S III] Jaws4God:
is anyone having speaker phone issues?? either turning off or not loud ?
[Verizon Samsung Galaxy S III] Master Cylinder:
I never saw this when I was on it. What date are you on? Did you find your answer already? Are you using Xposed or any other apps that might be farting around with the phone/volume?
[Verizon Samsung Galaxy S III] Jaws4God:
im on the 12/10 version (last CM12.1)

i am using Xposed.. but dont think im using any of the audio tweeks..
[Verizon Samsung Galaxy S III] adobeman:
Ah.. Didn't realize you were on LP when you first posted. Last LP build for d2vzw was 12/27 and on that I have one speakerphone volume. Full volume! Volume slider does nothing.
[Verizon Samsung Galaxy S III] Jaws4God:
do you have that link? I don't see it on their site...
[Verizon Samsung Galaxy S III] adobeman:
Ugh! I'm a dope. Never mind. I was thinking you were looking for AICP ROM. I got my threads mixed up.
[Verizon Samsung Galaxy S III] wadhwaa:
[MENTION=4908029]ItsMeSri[/MENTION] Can you please share this file I am unable to find it on given URLS

Thanks!
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey friend! Well, I know it's still there because someone just downloaded it a couple of days ago and got their phone to work in India! He's on CM13, too. Plus, I just checked. It's in the OP.

But, here is that link directly: d2vzw ROM Extras
[Verizon Samsung Galaxy S III] Jaws4God:
can someone tell me how to disable incoming calls as heads up ? Thank you.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I know there's a setting for all heads up notifications, but unsure if you can disable JUST the incoming calls. Settings -> Notifications -> Heads Up

Maybe try disabling "peeking" in the notifications, Settings -> Notifications -> App Notifications -> Phone -> Allow Peeking. That is totally a guess though.

I'm sure someone knows better than I, however

Edit: didn't realize I was in the 12.1 forum, I think it's the same as on 13 though
[Verizon Samsung Galaxy S III] Jaws4God:
yeah thats what I ended up doing.. I don't think she minds not having the other heads up notifications..

I was curious what "peeking" was.. maybe i could try that if she says she wants the notifications back for other apps..

LOL, yep, Wife was getting frustrated with her phone not being able to download some of the newer apps.. so I rooted her phone and tried to figure out which Rom is the most stable... I went with CM12.1 because it seems to have all working features and the CM team does a great job at stability..

I know my AICP MM is running buttery smoothe with barely any hiccups... of course the major issue is the FFC and I know my wife would want to make sure that works..
[Verizon Samsung Galaxy S III] Ibuprophen:
Just an FYI...

I just completed the uploading of "cm-12.1-20151210-NIGHTLY-d2vzw" to the Dropbox link provided in this thread.

I wasn't sure if it was available and that was the last cm12.1 nightly for the d2vzw.

I hope it becomes available for those who need the final one from 12/10/2015.

Enjoy!!!
[Verizon Samsung Galaxy S III] bmeek:
Is there any advantage to this last nightly over the snapshot release? I'm running "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw.zip". It's a month older, but it's a snapshot...
[Verizon Samsung Galaxy S III] phonetool:
Hi gang, I searched around a bit, but can't find an answer.

I've been suffering with an issue where apps on the sd card won't load up after boot.... sometimes they will, sometimes they won't. I just did the sd write permission fix on the platform.xml file, but no joy.

My Amazon app, apps from Amazon, and a couple side-loaded apps are affected.

It's a b*tch when I have to reboot my phone 3 or 4 times to get Amazon to work.

Sometimes I can get Amazon to work just after boot up, before the desktop app link goes grey. Other times it just says "App isn't available".

Any suggestions are welcome!

This is the only daily problem I have on this phone. Great ROM! Although, I'm tempted to jump onto the Marshmallow builds now that most of that is working. Been very patient with that effort.

Anyway, thanks in advance for any advice.

--edit--

Oh, thought I'd mention that I've also run a few basic cleanups, like dalvik wipe (from TWRP) and a bunch of cleaning scripts from SD Maid Pro. None help or hurt the situation.
[Verizon Samsung Galaxy S III] Droidriven:
Are you using a native feature of the ROM to have apps on SD or are you using a partition mod or app to do it?

You said you've done the wipes and scripts but have you tried doing a full wipe of system and data partitions and then flashing your ROM and Gapps then setting up apps on SD again after getting the device setup. If you do a clean flash then you might need to reverse the process on your moved apps and put them back on the device to completely undo everything like it was never done, then Titanium Backup to preserve data then doing the clean flash after that is completed just to avoid any possible issues with everything at a clean start then restore data from Titanium Backup(some things don't restore properly and cause bugs, choose wisely what to keep and restore), reboot after restoring from Titanium Backup then set apps to SD again then for good measure after setting everything up, boot to recovery and wipe cache and dalvik only then reboot.
[Verizon Samsung Galaxy S III] Ibuprophen:
Sorry for the delay...

Was kinda out of the loop.

I didn't think of that (went over my head LOL!).

I wonder why there was 1 last CM12 Nightly right after the Snapshot release then switch to the CM13 Nightly's....

Can anyone answer these:

1) Is it necessary to apply the last CM12 Nightly that was released right after the Snapshot?

1a) If so, then what does that single nightly offer the CM12's final Snapshot?

2) Does anyone know if the Cyanogen team has any plans to release a Snapshot of the CM13 for the d2vzw? I'm only asking because I'm assuming that if the Cyanogen team distributes nightly's of CM13, then i would assume (again) that they have intentions of releasing a Snapshot. Am i wrong?

Thank you all for your understanding...

Peace!
[Verizon Samsung Galaxy S III] phonetool:
I was flashing the 12.1 nightlies all the way up to the end. I am still on the last one from 12-10-2015.

When I look at the download page I only see the snapshot from November 15 as the most recent 12.1 file.
[Verizon Samsung Galaxy S III] kls629:
i installed 12.1 snapshot and now cannot receive mms messages. i tried different applications also still doesnt work.

under APN settings it states APN settings are not available for this user

anyone have a solution? i do receive sms

i installed NE1 modem and now cannot receive LTE
[Verizon Samsung Galaxy S III] Ibuprophen:
I had the same issue and, once or twice a month, had to get my carrier to push a refresh in their system.

Now, with CM13, i no longer have to deal with that. I have no problems with my mms nor my lte data.

There's something about CM12.1 that isn't right.
[Verizon Samsung Galaxy S III] kls629:
Thanks for the reply,

i did a clean install and the phone seemed to like it

it shows APN settings and i can send and receive mms now

also i get mobile data now too
[Verizon Samsung Galaxy S III] Master Cylinder:
I never had any problems with 12.1, or 13, at least on call/data issues. But, I'm having the same problem Ibuprophen mentions with, uh, CM14? Invisiblek's 2 unofficial builds anyway. The last one, 10/11, I just installed and it can't read my extsd without formatting it. I dirty flashed over the first one. Maybe I'll try a clean install again but I'll need to still find out what we had to do when invisiblek put out the unofficial 13 to get the phone to work. (I'm gonna post this over on 13, too.)
[Verizon Samsung Galaxy S III] kls629:
yeah most problems can be fixed if a clean install is done, but with nightlies you never know

also i switched from CWM to TWRP not sure if that mattered either
[Verizon Samsung Galaxy S III] phonetool:
You must be on TWRP. Step number one.
[Verizon Samsung Galaxy S III] kls629:
i was on CM10 and the TWRP manager would not install over CWM for some reason

once i upgraded to CM12, TWRP manager was able to install over CWM and i did a clean install
[Verizon Samsung Galaxy S III] Ibuprophen:
Just spreading the word that LineageOS just released an Official LOS14.1 for the d2vzw here:

https://download.lineageos.org/d2vzw
[Verizon Samsung Galaxy S III] Ibuprophen:
Just an FYI for those who may have missed it...

Rovo89 just posted a status update regarding the Framework for Nougat here:

http://xdaforums.com/showthread.php?p=70773752
[Verizon Samsung Galaxy S III] mastamoon:
Try deleting data/misc/wifi folder.

Also wifi drivers are in the kernel, so flashing a 3rd party kernel and complaining about wifi issues is bad juju.
[Verizon Samsung Galaxy S III] AyUaxe:
WiFi issue

Thanks, MM & MC for your suggestions. Haven't had the chance or need to try them out yet, as WiFi has been very stable on 5/23 build. I think MC's static ip suggestion may be the fix for home anyway.

Been waiting for some grief for using dkp. Concern is understood, but decimalman seems to base his on CM and syncs his with CM fairly regularly. I think it's just got or unlocks additional features, so drivers and such should be the same. Best regards and honor to all vets this memorial day.
[Verizon Samsung Galaxy S III] mastamoon:
Understood about decimalman keeping his stuff syncd... But if you come here looking for support you should be as "stock" as possible. Most devs/ops require this.. Thats the only reason I mentioned it.

Glad your having better luck with the last build though.

Happy MD to all ya'll vets out there! Thanks for everything, literally everything! [emoji1]
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I'm on the 5/25 build. Not having any WiFi issues and really never did with any of the others. It might be the kernel change that's causing the issue. Hopefully you get it resolved. :)
[Verizon Samsung Galaxy S III] brandonb0013:
Pretty disappointed, I flashed 5/26 and yet again had BT share stop after finally strong my phone back up... An hour later. I really want to sort this out so I took some screenshots of the report.

http://imgur.com/wvb4uEq

http://imgur.com/jVyJp1I

http://imgur.com/U1MVzHc

I hope to someday soon fix this issue
[Verizon Samsung Galaxy S III] Stealth111:
A bit off topic, but how did you get your signal strength meter to look like that? I love it! I needz it! :)
[Verizon Samsung Galaxy S III] brandonb0013:
Nicholas Dark Material Theme. I think it's pretty good. I life everything dark for battery life.
[Verizon Samsung Galaxy S III] phonetool:
When I follow the cyanogenmod gapps link in the OP there is only one option. It looks like they merged ARM, ARM64, and x86 versions on the 24th.

I haven't tried it out yet.

Edit

The download has failed me twice at 201/211MB.
[Verizon Samsung Galaxy S III] Master Cylinder:
Cool, I'll make a slight edit on that. I'm gonna try to dload one too to see if I can.

Looks like the nightly build machine is up to full speed ... :cool:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Guys, I downloaded the gapps last night no problem. I am using them now. I was using other gapps though, these seem to be better though. Just an fyi. GL :)
[Verizon Samsung Galaxy S III] Master Cylinder:
I was able to dload the latest GApps okay... Also the 5/27 build!
[Verizon Samsung Galaxy S III] NoCrAppleHere:
[MENTION=4602329]phonetool[/MENTION] maybe try it on your computer? I'm assuming you're using your phone.
[Verizon Samsung Galaxy S III] brandonb0013:
I see in the 5/27 changleog there's a revert for bluedroid according to A2DP. Could that have an effect on us with the random BT issues? I guess idk what bluedroid is but I thought it is for BT things
[Verizon Samsung Galaxy S III] Master Cylinder:
From https://source.android.com

Android provides a default Bluetooth stack, BlueDroid, that is divided into two layers: The Bluetooth Embedded System (BTE), which implements the core Bluetooth functionality and the Bluetooth Application Layer (BTA), which communicates with Android framework applications.

From Mobile Burn Glossary

"What is "A2DP"?

The Advanced Audio Distribution Profile is a Bluetooth profile that allows for the wireless transmission of stereo audio from an A2DP source (typically a phone or computer) to an A2DP receiver (a set of Bluetooth headphones or stereo system). Such devices typically also support the AVRCP profile as well in order to allow for track selection and such. A common misconception is that A2DP support is available on all Bluetooth 2.0 devices, which is not the case, and that A2DP is only available on Bluetooth 2.0 devices, which is also not true. A2DP support can exist in older versions of Bluetooth, it just was not commonly supported.

Also known as: "Advanced Audio Distribution Profile"

<Google is my brain>:cyclops:
[Verizon Samsung Galaxy S III] phonetool:
Yah, on the phone. I try to do most everything with it. Hardly ever hook up with a pc. Guess I'll have to try that.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Yes yes, me too, but if all else fails, we must try old faithful. Lol. Good luck
[Verizon Samsung Galaxy S III] Master Cylinder:
After reading this again, I'm still a little confused about what devices support A2DP. I guess what they're saying is it's either specifically supported by a device or it's not, regardless if it's Bluetooth 2.0.

Do you have a ROM you've used that the device you're having problems with works perfectly? Which device is that again?
[Verizon Samsung Galaxy S III] mastamoon:
My old head unit in my car was bluetooth capable.. but only did hands free calling.. So I guess they are saying that even though your device is bluetooth 2.0, it doesnt mean that a2dp is a guarantee.
[Verizon Samsung Galaxy S III] brandonb0013:
Quoting myself, but hopefully it helps people. From the changelog,

"This seems to have resolved 90-95% of my Bluetooth Share crashes. I'm using a jfltevzw and primarily connecting to a 2015 Honda head unit. I still get an occasional force close, but not nearly as much as before."

They're pretty much all talking about using a2dp on vehicle head units but if it solves bt share crashes that might also fix my issue with it being connected to my pebble. I plan on flashing in an hour or two and will report back.