yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] EGill42:
Like the other person who had the internal GPS selected, my phone continues to say location not found.

But thank you for everyone who was trying to help solve the problem. And especially thanks to those who build these roms. I would rather use them with their flaws than not. Plus I just have fun watching the bugs slowly get squashed it.
[Verizon Samsung Galaxy S III] khaoskosmos:
NFL mobile works for me now. It think it did a few nightlies ago actually
[Verizon Samsung Galaxy S III] Mexi7:
NFC

Anyone still having NFC issues, even after trying the fix?
[Verizon Samsung Galaxy S III] abreeden:
I didn't flash the 11/15 because it came out pretty late so i cant speak for it. but on the 11/14 i had NFC. i flashed the 11/16 this morning and have lost NFC. The CWM NFC Fix zip has failed to remedy it for me as well. doing what i did last time and flashing to TW and then back following a nandroid. i will report back in a moment

Ok. I made a backup, flashed to Synergy TW Rom and turned on NFC and SBeam, and then restored from my backup. this has worked for me in the past (2 previous instances) but has not fixed the problem this time. Going to flash back to TW again, re enable them, and then flash the stable build from a few days ago

That worked. Currently on the stable 10.0.0 build. NFC has come back for me. Restoring apps from TB now.
[Verizon Samsung Galaxy S III] nbaj2k:
Flashed the stable build, somehow my GPS is totally shot, can't get a fixed lock at all now. I tried the agps patch on the xda forum, might have made it worse. Even Clean ROM doesn't get a GPS lock now. Would flashing back to stock first before trying to reflash CM10 help at all?
[Verizon Samsung Galaxy S III] mastamoon:
Looks like the reverted the driver change that caused NFC issues finally.. so any build from today on shouldnt need the NFC zip fix.

Other than that, changes are few and far between right now. Everybody must be working on 4.2! :D
[Verizon Samsung Galaxy S III] ugachris:
What reverted driver change are you referring to? I'm not seeing anything in the changelog.
[Verizon Samsung Galaxy S III] mastamoon:
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/jellybean

Look at D2VZW.. Revert "d2vzw: update nfc props from VRBLI5"

The update nfc props from VRBLI5 is what killed NFC.
[Verizon Samsung Galaxy S III] abreeden:
I lost NFC on todays build. Mentioned not even 3 comments ago. it most certainly didnt work for me.
[Verizon Samsung Galaxy S III] mastamoon:
Well excuuuuusee me :D

Looks like todays build was built around 3 hours ago, and the revert happened 10 hours ago so it 'should' have fixed the issue. Maybe there is more to it.. or maybe the build bot didnt update its hardware repo.

Ill run a build now and see what happens.
[Verizon Samsung Galaxy S III] abreeden:
Thank you... i got mine back, but it took some work (outlined in comment)

Not too worried about it. its nothing but a minor inconvenience

Excited to try that build out
[Verizon Samsung Galaxy S III] Argent36:
Is there some way to test NFC? I must be missing something - I never use it

EDIT: nevermind - I tested it with someones N7 and was able to push stuff :)
[Verizon Samsung Galaxy S III] mastamoon:
Here is my build. http://bit.ly/RYTczz NFC works without flashing the NFC-fix zip on my phone where previous builds did not.

Hope it works for you guys.
[Verizon Samsung Galaxy S III] Defragger51:
Had a very od thing happen, been running CM10.0.0 stable with cm10 nfc fix since it cam out with out issue and the most important thing for me GPS worked perfectly up until late last night when it stopped getting a GPS lock at all, rebooted several times and everything is set that should be set. Any ideas? Also I get a very loud buzzing in my ear while on a call and another call comes in, I have to hang up to stop it . did not have this issues on 10/27 but have had it on 11/04 and the Stable build. Any ideas or fixes, its very annoying
[Verizon Samsung Galaxy S III] abreeden:
Lost NFC again with this build..... :(

NFCFIXzip didnt fix
[Verizon Samsung Galaxy S III] mastamoon:
I bet your agps data is stale and it is failing to update it.

Ive had no issues with the GPS on my phone running my build that has the AGPS patch 3 built in. Just last night got instalock from inside a school gym.

Give it a go. http://bit.ly/RYTczz
[Verizon Samsung Galaxy S III] ugachris:
Does this get rolled in to the official CM builds? I apologize for the continued questions, but I'm not seeing it show up on the CM changelogs yet:

http://cm10log.appspot.com/?device=d2vzw

http://changelog.bbqdroid.org/#d2vzw/cm10/next
[Verizon Samsung Galaxy S III] docdockstader:
CM10 stable released without an announcement?? Skipped release candidates?? Is this real? (reference: get.cm)
[Verizon Samsung Galaxy S III] mastamoon:
I guess you are just one of those unlucky people that have had their NFC go bonkers for no reason.

Sorry man.

Just curious, what are your steps of flashing a rom and what recovery are you using?

---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------

You wont see a gerrit entry for changes in that hardware repo usually. They are 2 separate entities.

The timing of the revert and the official build would indicate that the changes were in the build. So no need to flash my build as the guy with the NFC issue seems to be having another issue separate from the driver.
[Verizon Samsung Galaxy S III] abreeden:
CWM is recovery. Clean install and TBackup user app restore. Only way i get back is to flash TW, turn on nfc and sbeam and then flash back to CM10.
[Verizon Samsung Galaxy S III] nbaj2k:
I tried loading your build and I seem to get GPS lock pretty fast.When I go into Google Navigation though, it says searching for GPS. I have GPS satellites, Wi-Fi mobile network location,and internal GPS all checked. I downloaded GPS status, and although it finds satellites pretty fast, none of them are fixed.

Any suggestions for something else to try? According to the AGPS thread, that patch is not supposed to help users with Cyanogen.

I'm debating reverting back to the factory stock image and starting over, but I'd rather not have to go through the hassle of that if I don't need to.

Any assistance would be greatly appreciated,

~J
[Verizon Samsung Galaxy S III] mastamoon:
in my build, I have the build.prop edit that is needed for it to 'work' that is outlined in the notes section.

The only thing I have ever had to do to make my gps function correctly is turn it on, then reboot. If I dont do this, sometimes when I try and turn on and use GPS + Maps, the little gps icon flashing thingy doesnt show up and ill never get a lock. Rebooting with GPS turned on seems to fix this.
[Verizon Samsung Galaxy S III] hopesrequiem:
I would assume the "m" series ones were what other ROMs would call an RC
[Verizon Samsung Galaxy S III] FingersMcGee7:
"M" stands for monthly or milestone. Those are the stable builds of cm10. Someone correct me if I'm wrong.
[Verizon Samsung Galaxy S III] Brian Gove:
You're wrong. Those were basically just the best build at the time so CM10 decided to mark them with the m. They're the same as one of the nightlies released around the same time.
[Verizon Samsung Galaxy S III] beaups:
You're wrong too. The monthly or m builds are basically just that day's nightly, once per month. Nothing special about them.
[Verizon Samsung Galaxy S III] Brian Gove:
Which is pretty much exactly what I said...
[Verizon Samsung Galaxy S III] glensta:
FWIW

http://www.engadget.com/2012/09/11/cyanogenmod-10-now-available-in-m-series-monthly-builds/
[Verizon Samsung Galaxy S III] beaups:
Its not the "best". Just that day's build.
[Verizon Samsung Galaxy S III] nbaj2k:
Unfortunately I don't have that kind of luck. I tried to reboot the phone with GPS on and although I'm getting the GPS lock icon in the status bar, when I go to my GPS status application, it is still finding 19 satellites, but no fixed location from any of them. Not sure exactly how to go about trying to fix this. I rely on using Google Navigation a lot in the car. Not sure if even reflashing stock will help.

~J
[Verizon Samsung Galaxy S III] mastamoon:
This is me standing next to a window in a brick/steel 2 story building. The app is GPS test. Also, if you are letting GPS Status download agps data when you open it, you are overwriting stuff that the gps patch does. Maps and Navigation pegged me within 3 meters also.
[Verizon Samsung Galaxy S III] Defragger51:
I am running CM10 stable and I get a very loud buzzing in my ear while on a call and another call comes in, I have to hang up to stop it. Did not have this issues on 10/27 but have had it on the only two roms I have used since then, 11/04 and the CM10 Stable build. Any ideas or fixes? Its very annoying. :confused:
[Verizon Samsung Galaxy S III] Brian Gove:
Way to knit pick... you do realize they hold the commits for the m series so as to make sure they're the best (relatively speaking since I know you're taking everything literally)
[Verizon Samsung Galaxy S III] NeoMagus:
There was an announcement, guess you missed it.
[Verizon Samsung Galaxy S III] rfmodeler:
You are wrong too. CM said there is a code freeze for a few days before each m release. That makes them a bit different than the standard nightlies.
[Verizon Samsung Galaxy S III] grin0048:
I do remember them saying that, but I am puzzled by what they meant...if you freeze the code for a few days, all you're doing is releasing a nightly a few days later than it otherwise would have been--it's not like the code becomes more stable just by "sitting" for a few days. I'm wondering if they freeze new development while still allowing bug fix commits. :confused:
[Verizon Samsung Galaxy S III] Mercuie:
For the most part, it means that you don't add any new features or code. You just fix the features and code you have already put in.
[Verizon Samsung Galaxy S III] jackpot08:
How come in the latest versions including this nightly we can no longer record 1080p video?

Grrrr haha
[Verizon Samsung Galaxy S III] Imatoasta:
Works fine for me.
[Verizon Samsung Galaxy S III] Aali1011:
I got no 1080p recording, No sound during recording, and obviously NFC is broken. I haven't read anything about the video issues untill recently anyone care to chime in?
[Verizon Samsung Galaxy S III] beaups:
Great. So its a nightly 3 days late. My bad.
[Verizon Samsung Galaxy S III] Brian Gove:
It's exactly as I inferred, they hold a build making sure there isn't any huge problems with the commits then release it as milestone. Just admit you're wrong lol. You're the only one who really cares.

The sound during video recording has always been an issue.
[Verizon Samsung Galaxy S III] jackpot08:
But the no 1080p is a new problem? Now we can only record 720p.....
[Verizon Samsung Galaxy S III] Imatoasta:
I'm on the stable 10.0 build and it works fine and I don't see any commits that would of broke it?
[Verizon Samsung Galaxy S III] Brian Gove:
I wouldn't know. I'm on AOKP milestone and enjoying everything except the volume during video recording. Is stable and battery is wonderful for an AOSP based ROM. (dual panel is pretty sweet to)
[Verizon Samsung Galaxy S III] bL33d:
so does every gs3 on every carrier have low video recording? or just vzw...
[Verizon Samsung Galaxy S III] J913B:
Am I the only one that is experiencing an issue where if I'm watching Youtube or Twitch my phone will randomly reboot? I don't see anything on the bug tracker about it. It's a very fast reboot and I don't have to enter my SIM password. So it's not even a reboot, it's a crash of something important?
[Verizon Samsung Galaxy S III] Defragger51:
Am I the only one having this issue. Have posted 2x and No on has said anything. Running CM10 stable and I get a very loud buzzing in my ear while on a call and another call comes in, I have to hang up to stop it.
[Verizon Samsung Galaxy S III] mastamoon:
Just made 2 calls on 11/16 with no buzzing to be heard.

Edit, didn't see the part about when another call comes in, sorry.

---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------

I watched about 10 minutes of YouTube video today and had no reboots. On 11/16.
[Verizon Samsung Galaxy S III] Restola:
My sprint gs3 did as well
[Verizon Samsung Galaxy S III] Desertburn:
CM-10 20121117-NIGHTLY-d2vzw-1.zip

this file keeps downloading at 15 mb,it should be 163.9 mb. anybody to help fix this?anyone having same issue?
[Verizon Samsung Galaxy S III] badseed767:
I'm on the 11/16 nightly and I have 1080p video recording. Which gapps package are you using? If you're using the one with Picasa support, that limits the camera to 3mp and video to 720p I believe.
[Verizon Samsung Galaxy S III] jackpot08:
Weird.latest nightly just fixed it. Thanks guys I thought I was going crazy lol
[Verizon Samsung Galaxy S III] goldsmitht:
Did the same for me the two times I tried this morning
[Verizon Samsung Galaxy S III] Desertburn:
THANKS

OK, I thought it was me.
[Verizon Samsung Galaxy S III] Jaegermeiste:
For anyone still interested in the Clear All button check out this commit: https://github.com/cyanogenmod/andr...mmit/dd00b33b152e440a573bec4aa206e2bed9da4c1f
[Verizon Samsung Galaxy S III] locozildjiangodx:
How do you apply that commit to cm? It says it's for tablet, but will it work on gs3 too? I've been waiting for that feature; only thing I've missed from tw!
[Verizon Samsung Galaxy S III] Imatoasta:
I think there is a flashable zip somewhere in the thread. I don't remember what page though but I could of sworn somebody made one?
[Verizon Samsung Galaxy S III] bby144:
Does mms not work on the 11-16 build?
[Verizon Samsung Galaxy S III] RED ZMAN:
I'm on the 10.0.0.0 build, only problem is I have is NFC is now broken, messages still send really low quality images, and the previously mentioned is USB storage mounting.

Oh, and I have no option to store photos on my sd card instead of the internal. Annoying.

Anyone else having this last problem?

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] Restola:
Since CM10 was released.
[Verizon Samsung Galaxy S III] peaceofpi:
I'm back on 11/9 still the only build that doesn't make blue tooth sound all tinny. And Apollo works more stable. Data drops are infrequent. My headphones are bt so that's important for me. Also the DSP hasn't worked for some time now.

---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------

Somewhere in this thread there is a post for the NFC fix flash. With every update I run it and it works. Also still have to edit the build.prop as you can see from my sig.
[Verizon Samsung Galaxy S III] Crennie:
Thanks for the build info.

I wondered when the BT went bad. I thought it was just volume (in car BT)until I plugged in my headphones and realized it's really bad now.

I tried different kernels hoping to fix it, but no use. I rely on BT too much to ignore this bug.
[Verizon Samsung Galaxy S III] locozildjiangodx:
Found it, thanks! Works great!
[Verizon Samsung Galaxy S III] RED ZMAN:
Really? I wonder how I took all those photos later on my sd card a couple weeks ago. Now I'm perplexed.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] levilib:
Would there be any issue if i was to flash the 4.2 Gapps package found here:

on the stable CM10 instead of the regular Gapps package for JB?
[Verizon Samsung Galaxy S III] alee:
Looks like an experimental was just posted called d2vzw-bass-bluetooth-test
[Verizon Samsung Galaxy S III] bL33d:
dang keep checking this thread hoping to see these little bugs squashed. this rom really is snappy and smooth but bt and low volume camcorder kill it for me :(
[Verizon Samsung Galaxy S III] masri1987:
11/17 nightly is only 16 mb --- just fyi there's a 11\18 experimental nightly as previously stated
[Verizon Samsung Galaxy S III] OneNutShort:
Im running that same 4.2 package on the latest nightly, and also tried it on the most recent stable build. Everything is running great with the exception of the camera. It functions, but has the same lockup issue as others have mentioned. tapping the screen to focus just prior to snapping the shot prevents this. Hoping cm10.1 comes out soon and remedies this.
[Verizon Samsung Galaxy S III] glensta:
Well I just downloaded and tested the experimental ROM that supposed to fix the bass. I paired my phone with my car stereo and when I try to play music through my car stereo....it only plays through the phone speaker. I tried rebooting and clearing the cache is but nothing help

Sent from my Obsession
[Verizon Samsung Galaxy S III] Crennie:
+1 same here.
[Verizon Samsung Galaxy S III] DangerIsGo:
I don't know if anyone else had an issue with CM10 and Gapps 4.2, but after doing all the formats and clears, I then installed CM10 then Gapps 4.2 but everytime I went to start google (say google search or google now), it would crash. After flashing and flashing and flashing of various Gapps and the different nightlys of CM10, I did some more digging as to what could it be and found out that when I removed Velvet.apk an Velvet.odex from \system\app, the Google stuff that were previously crashing, no longer crashes and works great. Could help someone else if they are experiencing the same issue.
[Verizon Samsung Galaxy S III] NeoMagus:
I'll third this on 11-18 experimental. Where as it was tin sounding and no bass coming from the stable build, it will pair to my headphones but plays through the phone speaker, flashed back. Looking in the build.prop they changed the lpa audio strings back to false again but doesn't look like it helped
[Verizon Samsung Galaxy S III] nbaj2k:
I apologize if this is a dumb question, but does anyone know which nightly/gapps combination will auto restore apps from the Play store? I was backing everything up with Titanium but I screwed up when restoring my phone and wiped it.

I tried a few but haven't had any luck. Is it based just on the gapps package? I tried 7/26 and the one from October and I can't get them to restore now for some reason
[Verizon Samsung Galaxy S III] mastamoon:
Anybody else having issues repo syncing?

Nvm.
[Verizon Samsung Galaxy S III] Deevious88:
2012-11-10 is the last build that has working bluetooth audio (with bass) for me... Does anyone have the changelog from 2012-11-10 to 2012-11-11 handy?
[Verizon Samsung Galaxy S III] AtLemacks:
When I was running 11-14 Bluetooth worked well for me. Just a wild guess but with normal plug-in streaming and playing thru the speaker it sounds and works fine. So, it could either be a problem with libs, or possibly they updated DSP and broke it?
[Verizon Samsung Galaxy S III] Seirÿu:
I have a feeling I know the answer to this, but low audio recording is both inside and outside of video recording right? It's not just me going crazy? Am I the only one who uses their phone as a voice recorder?? lol I only see low audio in video recording references.
[Verizon Samsung Galaxy S III] Restola:
It's probably both but im not sure. The issue is the phone tries to use the noise canceling mic as the mic to record from, it probably does that everywhere (except when on a call).
[Verizon Samsung Galaxy S III] spaz mk will:
Clear All zip

Where did you find it?
[Verizon Samsung Galaxy S III] Deevious88:
Were you streaming music with an A2DP bluetooth headset, or just using it for phone calls?
[Verizon Samsung Galaxy S III] nbaj2k:
I ended up just installing them all one by one from the play store on my desktop computer, luckily didn't take as long as i thought
[Verizon Samsung Galaxy S III] WhammyDroid:
Reported another Bluetooth issue. I am experiencing issues where I cannot the bluetooth headset to hang up a phone call. I always have to go to the headset to get it fixed.

Link to issue: https://code.google.com/p/cyanogenmod/issues/detail?id=6659
[Verizon Samsung Galaxy S III] imaverik:
GUI placement issues 240dpi

So i like hi-res. this phones screen looks awesome set to 240 instead of 320 (factory) DPI.

I have noticed a few things that work but the layout overlaps some things when in 240dpi mode.

The phone -> contacts screen. In the top right corner the seperator line is in the way of anything towards the top of the menu.

Oddly enough it's mostly the gapps programs that have overlay issues.

The promlems dont make it unusable but they can be annoying when fast touching around the sreen becuase theres only 2 pixels or so to get it to register what you selected.

It would be AWESOME if the lockscreen displayed correctly in landscape mode. the lockscreen slider buttons stay in portrait mode even thought the lockscreen is in landscape.

I use widget locker to fix the issue but i hate using programs for features that are already included.

i think its jsut some framework tweaks to fix all of these but i am not a programmer and not sure what the correct terminology to use.
[Verizon Samsung Galaxy S III] sydewayz:
Nope. I tried it and it gave me an endless boot animation...had to nandroid restore.

I think thats for the Nexus only...
[Verizon Samsung Galaxy S III] Crennie:
Btw: http://changelog.bbqdroid.org/#d2vzw/cm10/1352648489
[Verizon Samsung Galaxy S III] dtraini7:
So over the past couple of days I have been noticing more and more lag and problems than I have ever seen before with CM10 on my S3. I actuall just had my first random reboot ever just before writing this. I have noticed increased lag in things like opening and closing apps, typing on the keyboard, even unlocking the phone. It seems like for some reason it is being slowed down and even changing the animation settings don't really help. Has anyone else been having these problems? I can't remember the last time it was "lag-free" but I am currently on the 11-16 nightly. Thanks for any help or advice!
[Verizon Samsung Galaxy S III] Zacharybinx34:
I'm having the same problems.
[Verizon Samsung Galaxy S III] mike216:
I'm using imoseys 1.10 kernel and everything is butter!
[Verizon Samsung Galaxy S III] dtraini7:
Well at least I am not the only one! I'm sure it'll get fixed in the next couple of days if others are having the same problem.
[Verizon Samsung Galaxy S III] digitalsynner85:
i'm on 11-16 that everyone on rom manager says is more stable than the stable release was and i have no issues at all.....my phone is snappy, even with the stock kernel...only thing i did was odin to the ICS stock rom and then flash immediately over to CM10
[Verizon Samsung Galaxy S III] Desertburn:
cm-10-20121119-NIGHTLY

so i have the second problem in three days.can not download nightly.either from website or cmupdater
[Verizon Samsung Galaxy S III] NegativeOne:
Please don't say that you have "no issues at all", because it doesn't actually convey which functionality you've used. For instance, if all you have used your phone for is the Facebook app, then you'll have probably never experienced a single issue since July or August.

When making these posts, it would be more helpful if you said: "I am on 11-16, and audio works, battery is fine, etc"

Thanks.
[Verizon Samsung Galaxy S III] Argent36:
its not just you - I can't download today's nightly either via the phones built in updater...

had the same problem yesterday too
[Verizon Samsung Galaxy S III] PerCompLLC:
Should be the same problem for everyone. The nightly file was removed... Probably an unsuccessful overnight build.
[Verizon Samsung Galaxy S III] majmuni:
Build 11/18/2012. Bluetooth works good. Just an update fpr those who care
[Verizon Samsung Galaxy S III] peaceofpi:
Is it still tinny? Is Apollo still slow to respond?
[Verizon Samsung Galaxy S III] alee:
For A2DP audio, are you getting any bass, or is it still thin sounding?
[Verizon Samsung Galaxy S III] locozildjiangodx:
http://xdaforums.com/showpost.php?p=33919415&postcount=5499
[Verizon Samsung Galaxy S III] glensta:
+1 I'd like to know this too

Sent from my Obsession
[Verizon Samsung Galaxy S III] Trumps:
Amen. I had to stop using Rom Manager to download nightlies because I was just infuriated by the fact every build had hundreds of 5 star ratings from every heartthrob cyanogenmod loving, "i just use my phone for facebook and instagram" superstar.

OH HAY GUYS!!! Five stars!!! It's Cyanogen!!! :eek:

With that out of the way, I can't get a GPS lock on 11/18.