yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] droidxuser123:
Aren't the cm devs on their own since Samsung went "lol no help for you"

Either way if, if you want a smooth experience with custom roms get a nexus device, ffs this device had a locked bootloader.
[Verizon Samsung Galaxy S III] seang:
exactly what im saying
[Verizon Samsung Galaxy S III] EGill42:
I see where you are coming from, but not everyone's problems are due to not knowing how to install CM10, or never wiping. For whatever reason, there is a decent amount of us who perpetually have problems. Clearly those of us who continue to use the ROM find it better than TW in spite of its flaws.

I think it would be more accurate for new people to note that for the majority of people it works exceptionally well, but there is a real chance certain issues will have seemingly no fixes for now. Hopefully they will not fall into that category. This issue does not need to painted in black or white; that CM10 is either perfrect, or a mess. I have issues, yet it still serves as a daily driver for me needs.
[Verizon Samsung Galaxy S III] Div033:
Only Exynos devices are on their own as Samsung cannot provide decent source code. Qualcomm based devices (US variants) are very well supported in the CM tree thanks to their great source control.

First make sure you have a custom kernel installed. I prefer leankernel.

Now, inside the app you'll find a tweaks button on the lower right. Tap that and then hit the presets button. I chose very light (Light could work as well). Also press the boot settings button and make sure Reapply Memory Limits is set to On boot completed. You should be good to go now.
[Verizon Samsung Galaxy S III] PureLife90:
Possible NFC fix... all credits go to inbisblek.

http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10

Post number 9.

MAKE a NANDROID BEFORE FLASHING!

Again, credit goes to inbisblek!

Edit* Please let me know if this worked for you. Flashing this DID fix my issue!
[Verizon Samsung Galaxy S III] funnyperson1:
This worked for me on liquidsmooth RC9, well at least it allowed me to turn nfc on. I'm still waiting for my tags to come in to see if NFC actually works :p
[Verizon Samsung Galaxy S III] AtLemacks:
And...... this is why we need an active maintainer, and/or active OP like I stated several times in this thread. We ALREADY HAVE AN NFC FIX! There has been a patch since the first time the issue arose. Nothing a new patch fixes isn't fixed using the original.
[Verizon Samsung Galaxy S III] AtLemacks:
Finally fed up. I have created a catch all thread for patches. If I am missing something you can think of, let me know! I am willing to add every and all patches available as a trouble shooting/trial and error type deal so they are always available build to build. http://xdaforums.com/showthread.php?p=34760470#post34760470
[Verizon Samsung Galaxy S III] toddley:
True but don't blame the OP he said he wasn't going to be active here long ago and nobody has created a new thread for this still
[Verizon Samsung Galaxy S III] gJon:
First off, let me say that when I'm at home on wifi this ROM has been exceptional for my needs. However, I'm still having data issues when not on wifi. I haven't seen anyone bring it up lately which makes me think that either I'm the only one experiencing this, or my problems are worse than that of everyone else.

There is no LTE where I live so I'm limited to 3g. Approximately every 90-120 seconds my data connection will drop completely and take about 20 seconds to reconnect. Reboots don't seem to fix the issue. I'm currently running the latest (K1) modem and RPM. I seem to have better connectivity with these drivers than the others (I've tried them all), but it's still pretty unusable. When I revert back to stock, I have no connectivity issues whatsoever.

Is it possible that trying a different kernel could fix this? Or do you guys have any other suggestions?
[Verizon Samsung Galaxy S III] AlexDeGruven:
Don't expect data to get as stable as TW at least until we get an official JB TW ROM. The RIL we're using is unofficial, and will be subject to issues that the official one won't because we don't have access to the sources.
[Verizon Samsung Galaxy S III] neyenlives:
added to OP with link to your post

also, in OP it says "If things change, let me know via PM, I'll try to update the OP."

nobody is PM'ing me and I am certainly not reading every post to try to pick out this or that, although I do visit this thread almost every day
[Verizon Samsung Galaxy S III] Restola:
So is there not an active d2vzw maintainer? Certainly I am owed nothing by anyone donating their time to the CM project, but my experience on the sprint epic 4g the CM developers were very vocal and open about what was going on. My experience with CM on the verizon gs3 has been quite different. I dont know anything about how the CM process works really, but it seems as though general CM changes get pushed out to all devices and are getting updated with the vzw gs3, but there aren't folks actively working on our device-specific bugs?
[Verizon Samsung Galaxy S III] neyenlives:
I am the same as all of you. Just a phone nerd that happened to take the time to create the thread, nothing more and surely less than some of you talented guys. The "maintainer" for the d2vzw has nothing to do with this thread.
[Verizon Samsung Galaxy S III] funnyperson1:
So really here is the problem, this thread is great for discussion of what works/doesn't work in a given cm 10 build. However, if nobody from cm reads this thread then there is no way that the bugs "reported" here will ever be fixed.

If you have a problem with cm 10, especially the "stable" release, then report the bug on their bug tracker. That's the only way these bugs will get fixed.

I read somewhere that the maintainer for our device is the original cyanogen, he probably doesn't have the time to troll 80 pages worth of posts for bugs.
[Verizon Samsung Galaxy S III] neyenlives:
This was my understanding from day one. This thread was never intended for the devs. Just for us phone nerds to share experience with builds, tweaks, etc...
[Verizon Samsung Galaxy S III] iofthestorm:
Last I checked our official maintainer is cvpcs but I haven't seen much of anything from him in a long while. Invisiblek does a lot of work for d2vzw and d2 in general though and cyanogen also does a lot of general d2 stuff but he doesn't have a d2vzw specifically.

There are a lot of other people who work on d2 devices in general too. Although data stuff is probably going to be specific to d2vzw so that stuff will take longer to fix. Also I am honestly not too hopeful about data problems getting better after a JB source release despite people here who keep saying like it'll be magically fixed once that happens. But I personally rarely have problems with data dying despite living in an area with crappy 4G reception.
[Verizon Samsung Galaxy S III] TechSavvy2:
Maintainer is cvpcs, correct. And I'd bet my car that data won't improve once jb tw source hits since.....wait for it.....we'll already be upgraded to cm10.1 by then in which case the tw jb source for 4.1 does absolutely no good, lol.
[Verizon Samsung Galaxy S III] abreeden:
The problem with this logic is that the first NFC Fix NEVER worked for me. Tried it constantly on varying nightlies. the one issued yesterday worked like a champ. Glad to have it back without the effort of flashing back to TW. Thanks to the dev who wrote that.
[Verizon Samsung Galaxy S III] iofthestorm:
Well, it's not like the RIL interfaces change all the time. I actually haven't looked too closely at RIL code recently but I did a couple years ago, and just logically speaking there isn't really any reason that new RIL code will be any better than the old RIL code inherently, or even necessarily different. RILs aren't *completely* magic and voodoo lol. But somehow people here think code is magic or something.
[Verizon Samsung Galaxy S III] NegativeOne:
We will be on 4.2 AOSP, but the Ril is proprietary from Samsung, so we still need their source code
[Verizon Samsung Galaxy S III] TheAnarchist1:
Not to throw blood in the water guys....but what "data issues" is it that everyone keeps whining about in this forum? I seriously have NEVER dropped data signal ONCE on this rom. To the contrary of you guys.....I actually get BETTER signal overall with CM10 LOL. I am using the latest modem and RPM from the last JB leak lol:D
[Verizon Samsung Galaxy S III] grin0048:
I don't think we get RIL source from Samsung since it's not in the kernel.
[Verizon Samsung Galaxy S III] Restola:
It seems to only happen in low signal areas. There are two small areas around Grand Rapids I have found where signal is consistently weak (even TW will lose signal entirely). Sometimes my phone on CM10 goes to complete loss of data and stays there, while my wife's stock GS3 still has a weak 3g signal.

On occasion my phone wont regain a signal until I get into a better signal area and cycle airplane mode (or reboot).

<<<<---- I think that underlined sentence is what people refer to when they talk about "data issues"
[Verizon Samsung Galaxy S III] tekhna:
There's no "blood in the water." There's only the simple fact that CM10 is buggy enough that everyone's experiences are different with this ROM; some people like TechSavvy2 are adament that the ROM is perfect because their experience is good. Which is cool, I've had good experiences with this ROM too, but I haven't always been so lucky. CM10 worked well for me for months, with a few weird quirks--my last install I had lots of data drops and no GPS lock, ever, but obviously it's not CM10, it's because I don't know how to install a ROM. :silly:

The fact is that it appears that no one is making D2VZW specific changes, so upstream changes break things and they never get fixed, if the commit log is to be believed.
[Verizon Samsung Galaxy S III] TechSavvy2:
Lol, I'd say that's a bit misinterpreted.

Does anyone remember where the cm10.1 merge, status, code was being put? I know they made an announcement of it but I can't find it. Wanted to dig through some code...:p
[Verizon Samsung Galaxy S III] Restola:
I agree in principle that could be happening as you outlined, but in the cases I mentioned I truly do not have data access while my wife is actively browsing facebook.
[Verizon Samsung Galaxy S III] dcowboys2184:
Cm biggest bug Is the random reboots... That's been a issue they haven't fixed since cm7 .. That's on all devices .. Becomes annoying after awhile
[Verizon Samsung Galaxy S III] jafterdark:
Does anybody else have this problem the home hard Key button doesn't do anything or does work if I return to stock the home button works
[Verizon Samsung Galaxy S III] Imatoasta:
Hmmm I haven't had a random reboot in forever even on cm7. Are you under volted, over clocked, different kernel?
[Verizon Samsung Galaxy S III] grin0048:
Yeah, same here, random reboots have been a complete non-issue for me.
[Verizon Samsung Galaxy S III] davidw2k4:
Same here no reboots
[Verizon Samsung Galaxy S III] Secretwar1:
Definitely a kernel issue, also as far as data drops go, they seem to be a very finnicky issue, ive had them, ive lost them, but what id recomend, is doing a full rebase to the latest Jellybean factory image, then doing a fully clean install of CM10, and restoring your apps
[Verizon Samsung Galaxy S III] d1ez3:
The issue I'm having is SOD, which I need to take out the battery sometimes more than once a day. The bad bluetooth and gps is something I can deal with but the phone just basically dying except for the soft keys is a pretty large issue, has anyone posted it to the bug tracker? I don't think you can get a log cat when you need to do a battery pull.
[Verizon Samsung Galaxy S III] Div033:
I'll have a reboot rarely, but they don't bother me as much as the audio/Google music bugs on Touchwiz based ROMs do. I'm using leankernel as-is, so that's probably the reason but idc. As long as aux routing works properly I'm a happy camper.
[Verizon Samsung Galaxy S III] dcowboys2184:
No I'm not.. Just running it as is .. My nexus reboots too.. So I know it's not just the phone itself
[Verizon Samsung Galaxy S III] JohnnyTToxic:
You can.

Either USB tether to a machine with ADB installed and run the logcat command so that it is stored real time on that machine

OR

Use an app like catlog that allows you to record the log to a txt file stored on the phone, untethered. I'm sure there are other apps that do this, but I like catlog. Just fire it up, hit record, name the file you want saved and it'll cache the logcat real time into the txt file you saved. When the phone crashes or loses power, the txt file will contain the log up to the point where it died (give or take some ms)
[Verizon Samsung Galaxy S III] iofthestorm:
There's also /proc/last_kmsg which might be more relevant in case of random reboots.
[Verizon Samsung Galaxy S III] anrichardson:
Is there a certain nightly people are sitting on? NFC is not that big of a deal to me nore is Bluetooth.
[Verizon Samsung Galaxy S III] antiseen:
Think the last nightly with unglitched bluetooth was nov 8 or 9. I know 8th is fine.

Anything after that means you have to place a call then hang up to get proper bt audio.
[Verizon Samsung Galaxy S III] Deevious88:
Nov 10th, 2012. Bluetooth was broken in the 11th's build.
[Verizon Samsung Galaxy S III] sivarticus85:
Is low cam volume bug in this build?

Edit: 11-10 build is not available on get.cm. Anyone like to share?
[Verizon Samsung Galaxy S III] jafterdark:
I use bluetooth everyday I'll give it a shot today running this rom if that'll help when tonight I'll give you feedback
[Verizon Samsung Galaxy S III] sobsmb:
Google search found it:

http://goo.im/devs/cm/d2vzw/nightly/cm-10-20121110-NIGHTLY-d2vzw.zip

EDIT: Nevermind getting a 0 byte file
[Verizon Samsung Galaxy S III] PerCompLLC:
NFC has been working perfectly on my device for the last 8 nightlies or so with no intervention. I haven't had to flash anything additional, it just worked out of the box. I know that others have had issues, and I did too for a little while, but CM merged the appropriate code and NFC has been working on my device ever since. Can't comment on Bluetooth as I don't use it at the moment.

I am on the 11/30 nightly with leankernel 1.10exp
[Verizon Samsung Galaxy S III] sivarticus85:
Lol I just tried this earlier... I found an unofficial 11-08 build but video playback is borked.
[Verizon Samsung Galaxy S III] sobsmb:
Ok found it, and can confirm it worked, I am now getting bass with bluetooth audio, and no phone calls (which only worked for me on incoming phone calls) (NOTE: I do not know the negative effects of this build)

http://oss.reflected.net/jenkins/12127/cm-10-20121110-NIGHTLY-d2vzw.zip
[Verizon Samsung Galaxy S III] addictedhacks:
I don't understand why it's so hard to find a download link to the official. All I see is a link to Alpha. I just went to get.cm to find it cause this post has everything but a Download link.
[Verizon Samsung Galaxy S III] jafterdark:
Bluetooth not working right

Okay bluetooth works but voice dialing does not sometimes I can't hang up the phone unless I use the button on the phone and not on the Bluetooth 4 voice dialing it'll say call and a name but doesn't pick up anything I say it's like the mic doesn't work anybody else can confirm
[Verizon Samsung Galaxy S III] sivarticus85:
Arguably the best build I've tried. Everything I've tried so far works great. NFC, Bluetooth audio, camera is fantastic, data is stable, WiFi, GPS locks fast, and battery life is awesome. Before i recharged i went a little over 2 hours screen on time with 56% left. Thanks for sharing this build with me.
[Verizon Samsung Galaxy S III] M Diddy:
Is low audio on video recording present on this one?
[Verizon Samsung Galaxy S III] sivarticus85:
I don't think so. It's not low to me. I did a few test videos to see, and the only thing i noticed is it records in mono i believe, which i don't care as long as audio is clear, which it very much is. I think you'll be satisfied.
[Verizon Samsung Galaxy S III] ekklesiaillusion:
Is there somewhere I can get the stable 10.0 from 11/13 stock kernel? Flashed leankernal and keep getting SOD'S and so I put the voltages back to stock but kind of defeats the purpose..

SIII on that Lean and Cyanogenmod
[Verizon Samsung Galaxy S III] solidunit:
Has anyone else noticed their headphone sound getting.....crappier?

To be more specific, my sound has gotten to the point where it feels like a hidden "pre-amp" setting is enabled that is artifically boosting the volume up to make everything louder; this is also causing distortion to present itself when i enable "slight" bass boost and modest bass/treble tweaks in the EQ. When I'm adjusting volume in general, by the fifth or sixth notch up, its just waaaay to loud. I don't know what could be causing this.
[Verizon Samsung Galaxy S III] masterxchief:
I've been noticing a lot of distortion too. I turned off compression in DSP and that helped a bit
[Verizon Samsung Galaxy S III] wctaylor79:
Reflash the build and it will overwrite the kernel
[Verizon Samsung Galaxy S III] WhammyDroid:
https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
[Verizon Samsung Galaxy S III] aeroevan:
You can turn off low power audio by making the build.prop edits linked in the report. That may help.
[Verizon Samsung Galaxy S III] ekklesiaillusion:
Anyone?

SIII on that Lean and Cyanogenmod
[Verizon Samsung Galaxy S III] solidunit:
Thanks Whammy, I just added a comment to that bug thread. Hopefully one of the devs takes a look at it soon!
[Verizon Samsung Galaxy S III] fafinaf:
have you considered trying out the Sony Acid Audio Mod that has been gaining popularity? I've been using it for a while and I must say it has made music much more enjoyable... it most definitely added a quality sound performance increase.

official website: http://m.chautemseric.wix.com/acidaudiotechnology

thread: http://xdaforums.com/showthread.php?t=1923630

hope it is of some value to you or at least benefits someone reading this.
[Verizon Samsung Galaxy S III] Brian Gove:
Should be able to dirty flash and get it back
[Verizon Samsung Galaxy S III] digitalsynner85:
ok does anyone know how to share via Wi-Fi direct? ive enabled it in the wifi settings yet it doesnt appear when trying to share something
[Verizon Samsung Galaxy S III] ekklesiaillusion:
I know I could but I was hoping someone had a flashable .zip

Thanks though.

SIII on that Lean and Cyanogenmod
[Verizon Samsung Galaxy S III] cgulliver:
Anyone figured out how to get the native LED to timeout? Its more reliable than LF but unfortunately it blinks until acknowledged.
[Verizon Samsung Galaxy S III] sobsmb:
Welcome man
[Verizon Samsung Galaxy S III] NegativeOne:
Question.. So is there a way to fix bluetooth on the latest builds other than the call workaround?
[Verizon Samsung Galaxy S III] EGill42:
Regarding the GPS

What I have noticed is that via a patch and a GPS fixing app my phone can get a lock quite fast, and within 30 feet. Huge improvement over the 900 foot radius Google Maps claims. Interestingly, even when a GPS fixing app has me located Google Maps still claims to locate me at best within 900 feet. Is this perhaps a problem with the app itself?
[Verizon Samsung Galaxy S III] Rixanu:
Am I the only person still having call volume issues? Because I never see anyone discussing it anymore. Ever since M2 (the first build I installed) I haven't been able to adjust the call volume with the rocker buttons properly. My calls always start out with maxed volume, even though the meter on the screen shows one level above the bottom. Using the rocker won't change this. If I actually manipulate the volume on the screen, it works fine. It's also the only way to get the volume to the lowest level-the rocker refuses to bring the call volume down past the second to lowest level. Is anyone else having this problem? I'm really confused as to how this problem has persisted for so long.
[Verizon Samsung Galaxy S III] NegativeOne:
Which app and patch?
[Verizon Samsung Galaxy S III] yznhmr:
I have been on cm since i got my GS3 VZ , and I cant remember rebooting unexpectedly .. only when i tell it to.. or very rarely if it locks up.. very rarely..

---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------

I am also interested.. sometimes have weird GPS issues..
[Verizon Samsung Galaxy S III] Div033:
Leave your call volume at level 3 and it won't reset to the highest volume level. It shouldn't be blastingly loud at that level either.
[Verizon Samsung Galaxy S III] techno_hippyGuy:
I seem to be having the opposite problem than most with call volume. It's really hard to hear people when in a call, even with volume maxed out. This is especially true when I have my phone running through the line out jack into my car's auxiliary port. I need to turn my car stereo to max volume just to hear people, and they get a horrible echo of themselves on their end. I live in a state where being on the phone while driving is illegal without hands free, and I'm always needing to make or take a call. Was there ever a fix/patch for these issues? I can't use blutooth headsets due to extreme pain on and around my ears after only a few minutes of use. Don't know why, but I've never been able to use them, and I've tried many. Any suggestions on how to fix?
[Verizon Samsung Galaxy S III] b3h3moth:
It could be. I'm not sure wheat fixed it, but outside of flashing the nightly normally, the only changes I made was the kernel and checking Noise suppression in call settings. ( open dialer> settings > noise suppression)
[Verizon Samsung Galaxy S III] fibofan:
Problems

Currently I'm no Synergy ROM

I'm Rooted, and used EZ unlock to unlock the bootloader. Running CWM v6.0.1.2

Put the Latest nightly on the SD card along with GAPPS and tried to install it. followed all instructions...

I keep getting this message in CWM

Symlink: some symlinks failed

E: Error in /"name of ROM"

(status 7)

Installation aborted

Then it goes in to a boot loop unless I Restore the last Nandroid

Any Idea's? never had this before and I would really like to run CM10
[Verizon Samsung Galaxy S III] tomyboombotz:
Try fresh downloads try putting them on either external mem then flash or internal then flahs
[Verizon Samsung Galaxy S III] hitman_dreams:
Data signal strength is worse than stock. I go miles with no connection at all now in an area I used to get at least slow 3g. This is sad. I know it's still early stages, but I need my data connection while driving. Anyone else notice this that isn't in a good 4g area?
[Verizon Samsung Galaxy S III] tomyboombotz:
Staten Island ny no issues at all with data or gps
[Verizon Samsung Galaxy S III] Merdinh:
I had the same issue, all you have to do is flash the latest build of CWM and you will be all set. Their should be a thread under the development section for the latest CWM
[Verizon Samsung Galaxy S III] Relentless D:
Everyone that is saying it is is saying that because it is gone for them...What would be the correct way to test it in your opinion?

fwiw, no echo for me on 3 calls today. Came from a clean wipe with imo's latest kernel.
[Verizon Samsung Galaxy S III] codyvance:
Isn't 6.0.1.2 the latest??
[Verizon Samsung Galaxy S III] fibofan:
Yeah I thought that CWM v6.0.1.2 was the latest version. At least I can't find any newer than that and it still won't install.

PS. I tried several downloads as well as putting it on the ex-sdcard and in-sdcard both gave me the failure error...

Any more idea's?
[Verizon Samsung Galaxy S III] bakaz:
No echoes here - just tested it with a few people. Noise Suppression is checked. 2012-08-21 nightly, stock kernel (dirty upgrade from previous nightlies).
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
where can i find imo kernel?
[Verizon Samsung Galaxy S III] opimpao:
When I try to install this via CWM recovery it goes through the process until installing the update... then it says assert failed: getprop("ro.product.device") ......

E:Error in /.../cm-10-20120822-NIGHTLY-d2vzw.zip

(Status 7)

Installation aborted.

Any ideas
[Verizon Samsung Galaxy S III] bieberhole69:
Rootzwiki