yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] YabbyYou:
I flashed the 6/28 nightly. FFC works! Amazing. Much thanks to the devs ( [MENTION=2385005]invisiblek[/MENTION], DMD and matrixzone) for brow beating this cam into submission! Bluetooth media audio still working. I need to check bluetooth phone audio as I read that might not be working when media is also enabled, might not big a huge problem if you have one bluetooth device for phone and one for audio, but I need to check it out.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Yeah, I've been getting restarts when I get a phone call while listening to music over BT. A couple music "glitches" during normal BT playback, but nothing as bad as it used to be. Could be from network issues too.

So close to being perfect. My wife just upgraded from her S3 today to an S7, and we were talking about how many versions of Android my phone has seen. It's truly amazing what the devs have done! And it's the only reason I've been able (willing) to keep my phone for such a long time
[Verizon Samsung Galaxy S III] killua#:
hi

when I install , I obtain ERROR 7

and l have a Samsung s3 Verizon sch i535 (4.4.2/ I535VRUDNE1)

I installed with safetrap twrp

Please help me
[Verizon Samsung Galaxy S III] AyUaxe:
6/28 has been good for me. Cams work, BT audio works, but with some stutter I don't think was present with 6/21 or 6/11 (the last ones I flashed). Haven't had any WiFi connectivity issues. A very happy and safe 4th of July holiday to all!
[Verizon Samsung Galaxy S III] phonetool:
If your phone was on 442, you have a locked bootloader. You can only flash 442 locked bootloader roms, like SuperLiteROM. Sorry, you can not flash cyanogenmod.
[Verizon Samsung Galaxy S III] killua#:
Ok ok but if I install 4.3 or other version , could I install cm13 ??
[Verizon Samsung Galaxy S III] lepa71:
You can't. Your bootloader is locked.

No soup for you.;)
[Verizon Samsung Galaxy S III] killua#:
Ok

I can !!! I can change my firmware via Odin

so I must put what version on my phone for installed cm 13 ??
[Verizon Samsung Galaxy S III] phonetool:
Go and look up "Q-fuse" on Wikipedia.
[Verizon Samsung Galaxy S III] lepa71:
You don't get it, do you. You are done, finished. This is it for you. Odin does not overwrite locked bootloader. Search and read this forum.:rolleyes:
[Verizon Samsung Galaxy S III] killua#:
Ok ok how do I can do to install 6.0 on my phone ?
[Verizon Samsung Galaxy S III] phonetool:
You must read more before you make any more posts. Go. Read.
[Verizon Samsung Galaxy S III] killua#:
I've installed SUPERELITEROM and when i install cm 13 on supereliterom , I obtain : success !!! But when I reboot my phone , I have not access to my phone but i have access to recovery !!!

Plz help me
[Verizon Samsung Galaxy S III] rwilco12:
As an XDA member and developer, rather than as a XDA moderator, I would advise you to spend more time reading and less time flashing. Almost every post that you have made in this thread has been answered, either in the first post or in reply to your previous posts. XDA is a community of people that love our phones and love to tweak them and mess with them. We love to share the experience with others but we can't do that if you're not going to read what is being said.

Please go back through the various posts that were made in reply to your many previous posts and also read the first few posts in the thread in order to find the solution to your issues.

Thank you,

Rwilco12
[Verizon Samsung Galaxy S III] killua#:
Ok
[Verizon Samsung Galaxy S III] YabbyYou:
Hello fellow SGS3'ers, I'm going to try and get us back on topic here. I just flashed the 7/11 nightly onto my sgs3. Running it through the paces now. Anyone else on this nightly? Hoping to see a little improvement in the BT audio since it was a little choppy at times on the 6/28 build I was running. I also noticed a another weird thing on the 6/28 build, when the phone would reboot, it would take at least two reboots before it would stay booted up, it was very strange, hopefully that issue is gone now the 7/11 nightly.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Ive had many issues with my phone rebooting anywhere from 1-3 extra times before a boot would stick. I chopped it up to be my hardware failing, as I was also having issues with what I think was the power button too... the power menu would pop up seemingly out of nowhere, and the camera of all things would come up, and then my phone would freeze and reboot because of it sometimes.

My wife's S3 (stock) had something similar before it crapped out, so I figured mine was on its way out. But then I flashed a newer nightly, and the issue has either severely decreased, or possibly completely gone away....

In the meantime I bought a Nexus 5X (coming Thursday) so I wouldn't be without a phone for a trip coming up. So I'll be saying farewell to you guys soon ???? I was gonna wait for the 2016 round of nexii, but didn't think my phone would make it!
[Verizon Samsung Galaxy S III] YabbyYou:
Oh no! Queue up some Queen... Another one bites the dust.... Keep that S3 around on wifi as an alarm clock or for playing Pokemon Go without giving up all access to everything on your main phone... haha #pokemongopsyop

7/11 build is running very well so far. BT still stutters a bit at times. Battery life seems good, performance seems good. I haven't experienced the reboot weirdness yet.
[Verizon Samsung Galaxy S III] Roger W:
I've been on 7/8 and now 7/11 with no new problems. Never had problems with random or multi-reboots. Only CM13-era new problem I regret not seeing a fix for yet is when BT phone and media profiles are both active and a call crashes the device.
[Verizon Samsung Galaxy S III] AyUaxe:
On 7/10 and I think this is the best build yet. Very snappy, quick boot, good WiFi and BT connectivity. I had problems for a while with reboots getting stuck on the animation. Had to get into recovery and reflash to reboot successfully. I thought it might be corruption or something, BC I run dkp w/ cpu oc'd to 1782. Rolled it back a notch to 1728, but no difference. However, the reboot issue seems to be resolved in the 7/10 and later builds. Many thanks [MENTION=2385005]invisiblek[/MENTION] !
[Verizon Samsung Galaxy S III] dltccf:
I loaded the 7/16 nightly and I am seeing two issues with audio for phone calls. I actually use the phone to make calls, I realize that isn't the norm these days, but it is for me. First issue is when making a call with earbuds plugged in, the sound is extremely loud and changing the volume doesn't work. moving the slider works as though it were changing the volume, but the volume doesn't change.

Second bluetooth is still not working, it pairs and connects, but sound still come out the speakers rather than the bluetooth headset.

---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------

The previous nightly I was on was 6/25
[Verizon Samsung Galaxy S III] AyUaxe:
If you can still get it, try 7/10 or 11 and see if your volume issue resolves. I flashed from 7/10 to 7/14, but got the never-boots again, so restored backup of 7/10. Volume works well on all out puts (haven't tried phone) for me on this build.
[Verizon Samsung Galaxy S III] dltccf:
Thanks, I ended up going back to the 6/25 nightly.
[Verizon Samsung Galaxy S III] L4zyD0g:
What are the bugs in this rom ?

Can I use it daily ?
[Verizon Samsung Galaxy S III] AyUaxe:
Srsly?

Srsly?

[IMG="owl"]http://media.riffsy.com/images/661ab37ebe9d7352eba2edb4ea4838fa/raw[/IMG]

Read comments #712 and #713 for solid advice.
[Verizon Samsung Galaxy S III] JurKZ:
I just installed this in my phone and it would bootloop. It would update android apps and then go back to the animated cm logo. Anyone else have luck with the 0731 build?
[Verizon Samsung Galaxy S III] toosurreal01:
Make sure you delete cache/data, flash the ROM then flash GAPPS right after.

Once they are both done then reboot.
[Verizon Samsung Galaxy S III] JurKZ:
Thanks for the heads up. I just noticed I had a very old version of TWRP. I updated to the most recent version and it worked like a charm. Now I just flashed xposed so I hope all goes well after it optimizes all the apps.
[Verizon Samsung Galaxy S III] Fenix2002:
Xposed is hit or miss. I've seen some have luck with it and some not. I think a lot has to do with which modules you use. GravityBox has had a decent success rate on the S3.
[Verizon Samsung Galaxy S III] Roger W:
8/3 build has problems -- possibly with NovaLauncher -- for me. I just installed it for the August Google patch, but it soft-reboots almost every time I go back to the home screen from an app, and this has never happened before.

I'm coming from a build from about 10-15 days ago, which was fine.

I usually use Nova Launcher but switched back to Trebuchet to test, and when I hit Home, it rebooted one last time, but on the next boot when Nova isn't running, it now seems stable.. But, oddly, I'm now switching *back* to Nova and it hasn't rebooted yet. After about 6 easy-to-reproduce reboots in a row.

I'm not using a custom kernel, xposed, or anything similar.

I'll investigate more tomorrow.

Edit2: after a full day of use, no more reboots. The "fix", if it was one, was to switch from Nova to Trebuchet and back. I also had Nova "Backup" its settings to local storage; I was about to clear its data but found that it stopped rebooting so I didn't have to. so, probably a weird quirk of my system, and not a broken build.

Edit3: Yeah, that build, or my install of it, is bad. Reboots have come back, and today there's no mobile data. Tried switching APNs, toggling data and airplane mode, no luck. I'll try the current build, and if it's still bad, I'll restore a backup from a couple weeks ago.
[Verizon Samsung Galaxy S III] AyUaxe:
New dkp kernel build and great guidance from [MENTION=4932679]decimalman[/MENTION] over at his playground. Lil d2 that could now max'd @ 1944 MHz , 1280 MV, stable and crazy fast for all routine tasks. Play updates a little janky, but the last 5mV bump seems to have fixed that, too. Temps in low 30s while streaming audio, browsing. Will try more demanding video and report. BTW, I'm on cm13.1, 7/10 build. Tried 7/28 and 8/3, but got random reboots and neverboot syndrome. In hindsight, 7/10-11 were snapshot quality builds. Glad I had back ups. Wish they were still available for download (any possibility of that, oh great [MENTION=2385005]invisiblek[/MENTION]?)
[Verizon Samsung Galaxy S III] Roger W:
I gave up on my bad 8/3 install- no data on any band was a killer - and restored from mid-July, then flashed to 8/6. That's working fine for me now. Note if you use the CM Updater app, the builds are out of order because they reverted a version name change from 13.0.1 back to 13.0, so look at the dates, don't just grab the top one.
[Verizon Samsung Galaxy S III] AyUaxe:
8/14 is buttah! Like the new optimizing apps info during boot. BTW, still running 8/1 dkp kernel, but rolled back CPU oc to 1782 again. Higher speeds worked, but downloads were corrupt.
[Verizon Samsung Galaxy S III] YabbyYou:
I may make a move up to a newer build based on this review! I'm still running 7/11 (with that 8/1 dkp kernel).
[Verizon Samsung Galaxy S III] AyUaxe:
Be sure to keep a backup and a copy of the 7/11 build, if you've still got it. I used my copy of 7/10 several times to fix no boot problems and such. Still liking 8/14, though. Haven't seen any glitches.
[Verizon Samsung Galaxy S III] YabbyYou:
I just flashed the 8/15 build. The battery percentage is all messed up. Not sure what is going on but it thinks the battery has -1,095,328,212% remaining. What!?!? Is my phone suddenly running on negative energy? Maybe it's powered by a black hole?
[Verizon Samsung Galaxy S III] razorloves:
See comments here https://review.cyanogenmod.org/155639
[Verizon Samsung Galaxy S III] YabbyYou:
Thanks for the link [MENTION=614507]razorloves[/MENTION], that's a good read. Looks like the problem is being worked on. I went back to the 8/14 build since [MENTION=3056030]AyUaxe[/MENTION] has given it such a glowing review. It's working much better, I'll stay on it for now until the battery issues are fixed. I didn't flash the dkp kernel yet since I want to make sure 8/14 was stable on my d2vzw. I'll probably flash it sometime tomorrow. For now, I will second AyUaxe's review of 8/14 as being stable and fast, worth the update for anyone else reading this. As always, if I run into any other issues I'll report back.
[Verizon Samsung Galaxy S III] zwliew:
This issue has been fixed and the fix will be in the next nightly (20160818).

Here's the actual fix for those who are curious:

http://review.cyanogenmod.org/#/c/156679
[Verizon Samsung Galaxy S III] YabbyYou:
Thanks for the updated info on this fix [MENTION=5604178]zwliew[/MENTION] . I am running the 8/14 build at the moment and it's been running very well. Glad to see a few other people commenting in this thread. I wonder how many people are out there running CM13 on their d2vzws!
[Verizon Samsung Galaxy S III] bmeek:
My more modern smartphone died this week, so I swapped the sim over to my old dusty d2vzw and flashed the 8/14 build. So far so good!

I'm very grateful and impressed that there are cm13 nightlies for this!

I also can't believe my old phone is still running - the power button had died, so I scraped it off and I'm running fine with button savior. Even the original battery has held a charge pretty well today
[Verizon Samsung Galaxy S III] J-Lindo:
First off, this is my first post on XDA. Hi!

Second, on the recommendations of everyone above, I gave 8/14 a go, and I can also verify that it's working quite splendidly! No noticeable bugs/glitches so far, everything's running smoothly, and I'm a happy camper. I don't suppose this indicates a snapshot release in the near future?
[Verizon Samsung Galaxy S III] YabbyYou:
Welcome J-Lindo! Glad you were able to successfully flash 8/14 and are enjoying it. I'm not sure if there will be any snapshot releases for our d2vzw, might just be nightlies. As you can see from the length of this thread, a bunch of us have been running the nightlies for a while now and have had good success with many of the builds. If you have any questions or run into any problems let us know and we'll try to help.

---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------

The d2vzw is a pretty amazing piece of hardware and still holds up well despite it's age. I still use mine as a daily driver! I am keeping an eye out for the new nexus phones as I think it might be time to make a jump to new hardware. The thing that annoys me the most about the d2vzw is the crappy GPS chip. Everything else I can deal with, but that slow GPS makes me nuts sometimes!
[Verizon Samsung Galaxy S III] bmeek:
Has anyone else had trouble with Bluetooth on the 8/14 build? I can successfully pair my Plantronics Voyager Edge, but using it for phone calls seems to turn the phone sluggish and ultimately leads to a crash/reboot (not to mention a failed phone call).

---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------

FYI, I loaded the 8/18 build and the battery status problem persists. Maybe tomorrow's build...
[Verizon Samsung Galaxy S III] YabbyYou:
I haven't tried using my bt headset on a call yet with this build. I have successfully used my bt headphones for listening to music, that worked without any major issues though it does get a little sluggish at times, not uncommon with these builds.

---------- Post added at 10:27 AM ---------- Previous post was at 10:24 AM ----------

Interesting. I see the 8/18 changelog has the code in it that's supposed to fix this, in particular "power: max17040_battery: Set type to UNKNOWN (android_kernel_samsung_d2)".
[Verizon Samsung Galaxy S III] Roger W:
As far as I know, using BT "Phone" and "Media" profiles on the same device has been broken since January. (Lots of us have seen it, and I haven't seen anyone report it to work.). The workaround is to disable one or the other profile for each BT device so that making/receiving a call doesn't crash the device.
[Verizon Samsung Galaxy S III] bmeek:
Ah... Thank you. Good to know.

Almost a showstopper for my daily driver usage that is, but at least I know the workaround.
[Verizon Samsung Galaxy S III] bmeek:
I just confirmed that my headset works fine for calls provided that I disable the media profile. After a call was completed successfully using a Bluetooth headset with it's media profile disabled, I disabled the phone profile and enabled the media profile for it and listened to a newscast using the same headset. Unfortunately, even though the newscast had ended and the Bluetooth phone profile was disabled, I was unable to answer an incoming call - the phone became unresponsive until after the call was logged as "missed".

So there you have my long-winded description of a caveat to the Bluetooth issue workaround.

I gather this issue is common to all marshmallow ROMs on this device (not just this cm13 ROM)?

If so, what's the most solid lollipop ROM for the d2vzw? I'd prefer aosp over TouchWiz unless the latter gets substantially better battery life (assuming there are any lollipop-based TouchWiz ROMs for this device).

Thanks!
[Verizon Samsung Galaxy S III] Fenix2002:
Fairly certain it's an issue on all d2vzw MM ROMs. My personal favorite is AICP, but OctOS is fairly enjoyable also. Those are the big ones I know of that are still going.

(In the interest of transparency, I haven't used my S3 in about 2 months, hasn't been on the network in 3 months. I just kick around on here to see how things are going. Lol)
[Verizon Samsung Galaxy S III] J-Lindo:
Why, thank you! I couldn't've asked for a kinder welcome.

Now, to be somewhat useful (or make myself look dumb, we'll see), I've found an issue to report. To begin, I updated to build 8/20 to see if it resolved the issue, but it persisted. My screen-side camera will not record videos for any third-party apps. For example, my parents like communicating with Glide, a video messaging app, and if I attempt recording a video with my front camera, it gives an error saying, "Unable to load camera. Please close any apps that may be using the camera and try again." Also, I'm on Snapchat (ladies), and, rather than giving an error message, it appears to work fine, but the recipient only gets audio and a black screen. Snapchat will, however, take still photos with said camera. In both apps, the rear camera works fine. Interestingly, both CM's camera app and Google Camera record video on the front camera just fine.

Also, I haven't tested this extensively, but it seems like sometimes the wifi disconnects and I have to manually reconnect it myself (especially with 5ghz). Anyone else seeing that, or is it just me?
[Verizon Samsung Galaxy S III] YabbyYou:
Well, the FFC has always been a bit unstable. I don't really use mine so I never notice it. I'm actually not sure of it's status on the latest builds, someone else in this thread may be able to comment further. As for the wifi disconnects, I am not having that problem when on wifi, stays connected all the time for me. I wonder if it's a wifi router issue, do you have that issue with any other devices that use the same wifi router?
[Verizon Samsung Galaxy S III] J-Lindo:
I gotcha. I suppose I'll wait and see and just work around it in the meantime.

As for the wifi, I think it's just me. None of my other devices have issues like this with my router. I connected to my apartment's 2.4Ghz wifi and it's been holding just fine, so I think it may just be that my 5Ghz isn't reaching my living room too well.
[Verizon Samsung Galaxy S III] vforaci:
I flashed 8/14 several days ago and I'm happy to report no visible issues. Last time a tried back in April the upgrade was a disaster and I was force to revert back to CM12 and even flash to TWRP since it's required now-a-days.

I'm tempted to flash DKP kernel to see if I can further improve the experience but don't want to rock the boat. Anyone have a feedback on DPK, neg or pos?
[Verizon Samsung Galaxy S III] YabbyYou:
Yeah 8/14 is still working well for me. I haven't moved up from it yet, waiting to hear back from someone on here that the weird battery display issues are resolved. You can give dkp a shot. It works fairly well with my phone and it works amazingly well with [MENTION=3056030]AyUaxe[/MENTION]'s super-duper-d2vzw. Take a read back thru this thread for more details or head over to the dkp thread for even MORE details. Report back here either way, let us know your experience with it.
[Verizon Samsung Galaxy S III] AyUaxe:
Highly recommend dkp kernel whether you're rockin a John Clare or Proteus Frankenstein CPU (gratuitous Penny Dreadful reference). Use kernel adiutor to tweak. I've posted lots about my settings over the last 18 months or so, as we've blown through K, L, and M. Have used dkp throughout with great results. D2vzw was my dd until just a few months ago. Still use her constantly as media device and reserve phone, since she can also do gsm.
[Verizon Samsung Galaxy S III] J-Lindo:
I'm on 8/20 and my battery display seems perfectly fine. None of that weird, negative black hole charge status here! (I am, of course, assuming you mean the battery icon in the notification bar.)
[Verizon Samsung Galaxy S III] dltccf:
Anyone else noticing that over the last two months the phone gets very hot when using location services. The hottest spot seems centered about 2/3 of the way down in the center of the screen. Using an app like maps or swing by swing gets if very hot and it doesn't cool down even if you kill the app. the only way is to reboot. I'm not talking about the old "the phone gets pretty warm when running maps" I mean considerably hotter than that. I have gotten so that I turn off location unless I need it on and then turn it back off as soon as I can.
[Verizon Samsung Galaxy S III] dvschnk:
I haven't ran into that problem. Something is pegging your cpu to max when your location is on. The CPU and battery are roughly located 2/3 of the way down the phone. Does it get really hot with location services is on but you're not using an app like Maps?

Have you looked under settings and location to see what had recently used the location service. Something like GSAM battery monitor might be helpful too, because it shows what uses your battery heavily in time intervals (and usually heavy battery usage in short amount of time = heat). If you go with the GSAM route, be sure to take it off once you've diagnosed your problem. The way it monitors everything uses battery and cpu power too.
[Verizon Samsung Galaxy S III] herbby:
Pandora

Guys will Pandora ever work with CM? Still can't get it to work, only on wifi connection. Even my brother and his Note 2 with CM just won't work. Anybody?
[Verizon Samsung Galaxy S III] jtnc:
I haven't had any issues over LTE with it. Just tried it again on the 8/26 build and works fine.

Even better (for me), 8/26 appears to have working Bluetooth! I saw a note on it in the ATT forum, and sure enough, I can use MM with my car's Bluetooth. So far seems to allow me to call and switch between music and phone without a lockup/hang! I need to give it a few more days of testing before I'm totally convinced, but looks promising.
[Verizon Samsung Galaxy S III] herbby:
Thx for replying, weird. The bluetooth has worked for me for quite some time. It's just that darn Pandora. It is hacked version tho, that used to work on earlier builds. Tried several hacked versions with no commercials and nada. Is that it? Are you using the untouched version? Both of us with different phone no go.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey everyone, just a quick off topic question if you don't mind. Has anyone used a non-verizon SIM in there CM powered d2vzw? Just curious if it would work, I may be taking a trip down to the British Virgin Islands, curious if a local SIM would be a better option then TravelPass (though the TravelPass option really looks like a good way to go).
[Verizon Samsung Galaxy S III] invisiblek:
I'll just leave this......here.......

Its super buggy, pretty much nothing works, it may be a very long time before its ready to use as a daily driver, but hey it boots :silly: