yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ups2525:
got locked GPS?? Yes I do!!!!!!!!!

I did a clean install of 12/08/12, while still in recovery I then flashed LK3, KT747 11/13, & last flashed Beats w/Dolby audio and rebooted system. Setup the bare minimum (no FasterFix, GPS status toolbox, none of the usual extra apps I DL) to get to the point that I could attemp to get a gps lock & within about 3 seconds time MAPS GAINED A LOCK ON MY LOCATION VIA GPS within 2 meters!!!!!!!!!!!!!!! I have flashed every rom multiple times over and excluding Clean Rom I have never been able to get a lock on gps. I always get, at best, within 20 meters. I'm a coverage driver for UPS and the abilty to get a lock in Google Maps is a big part of my job. No more worries now...haa ha haaaa...holy s!@t!!!!!

Great work devs!!!

I'm so thankful to be back on CM10...by far my "all time favorite rom".
[Verizon Samsung Galaxy S III] BlueCross:
Do a double tap.
[Verizon Samsung Galaxy S III] fafinaf:
Mind sharing the beats mod you're using? Congrats on your gps situation
[Verizon Samsung Galaxy S III] cgulliver:
CM10 commits are barely trickling in which makes sense with dev effort shifting to 10.1. Even though it's not ready, there a change log site for 10.1?
[Verizon Samsung Galaxy S III] dpaine88:
Hello Fellas, I hope one of you can help me out here.

I have not been on CM since CM5/6 on my Droid.

I have been using Liquid ROMs for quite some time now but the issues with AOSP are really getting to me.

Namely: Random SystemUI Force close, Messaging Force Close during heavy texting, Very poor GPS location(too far from my location for Navigation) and also annoying data drops.

I know Liquid ROM is based somewhat off CM10 but I am hoping some of you can confirm if these issues are present n CM10 as well.

Also, are there any issues in CM10 stable?
[Verizon Samsung Galaxy S III] grin0048:
You can see merges to the 10.1 branch here:

http://review.cyanogenmod.org/#/q/status:merged+branch:mr1-staging,n,z

This one looks interesting:

http://review.cyanogenmod.org/#/c/28047/
[Verizon Samsung Galaxy S III] cvo515:
I've been running cm10 right along with none of these. I recommend a full wipe or everything and a fresh download. I have a GPS lock in seconds right from the start. Maybe try a tw Rom and get a lock before trying cm. Other than that I'm not sure what to tell you
[Verizon Samsung Galaxy S III] sweeds:
Is there any way to mod or add options to the notification drawer?

In my case, I'm thinking a toggle for the Wifi/Mobile network location. Or, itd be great to toggle all Location Services rather than just the GPS.

Any ideas where to go for further research or to implement?
[Verizon Samsung Galaxy S III] grin0048:
In settings, go to System > Notification drawer > Widget buttons. There are a bunch more that can be added. edit: probably not what you were asking :p

If you long press the GPS widget button, it will take you to location settings, where you can enable/disable things there--don't think there is a specific widget button to toggle them all.
[Verizon Samsung Galaxy S III] vdefender:
I can't get a GPS signal for the life of me :(

I've been using CM10 nightlies from day 1, at the beginning I was getting a weak signal (like 4 sats locked), that lasted until the 10-27 nightly which was so stable and awesome for me I just kept it until this week. I am now on 12-7 and I have zero GPS reception. If I'm out in the open with it on I can sometimes get one sat to lock for a minute, then it will just drop back to 0. So far I've tried wiping and reflashing cm10 twice. I've wiped and flashed TW ROM cleanROM lite. And I got zero SATs there. I attempted that GPS fix patch to no avail. I'm back on cm10 12-7 nightly. My friend also has a Sprint S3 and I maintain it for him and I put 10-7 nightly on his. First boot up, opened GPS status and his instantly locked on to 8 sats.

At this point I think my phones hardware GPS is just shot :( does Samsung warrantee their phones for a year? I bought this new on Craig's list. It was purchased from Verizon by the original owner.
[Verizon Samsung Galaxy S III] lohp75:
In your settings /location access make sure that your gps source is turned to internal. Might help.
[Verizon Samsung Galaxy S III] sweeds:
News to me. And it's essentially what I wanted. Thanks!
[Verizon Samsung Galaxy S III] NegativeOne:
I forget, why can't they back out the qcom code responsible for the messed up bluetooth from the d2 branch?
[Verizon Samsung Galaxy S III] jasonfreeland:
Can you restore a nandroid to a replacement phone from a previous one? It's nightly 1207 if it makes a difference. I had to do an insurance replacement for a broken screen and would really love to not have to re install everything.
[Verizon Samsung Galaxy S III] grin0048:
I've never done it, but I've seen this question asked before and the answer you'll usually get is that there really isn't any reason why this wouldn't work.
[Verizon Samsung Galaxy S III] jasonfreeland:
I'd seen some stuff in a search, but none of it was for CM. I figured it wouldn't hurt to ask. Here goes (cross fingers).

Edit: Appears to have worked.
[Verizon Samsung Galaxy S III] dtraini7:
Don't hate, but I am on CleanRom right now, waiting for something stable to come out of this thread. I know everyone's phone is different, but my experience with CM10 has been about 90% AWESOME. The only complaints I have are that sending picture messages result in awful photos, data drops on data droos on data drops, and that I basically got a dropped call about every day. I KNOW these have been covered but I am asking if there is hope. JB TW is slow as hell and buggy, the only reason I like it is because the bugs above are not present. Will the next versions of CM10 or CM10.1 fix these issues? I am thinking I have no doubt CM can fix these, but I am waiting for a while. Thanks for the thoughts in advance. :)
[Verizon Samsung Galaxy S III] Maroon Mushroom:
(Just because I've shared this on other CM threads)

https://play.google.com/store/search?q=cyandelta..

If you guys are flashing nightlies, I HIGHLY recommend using this app instead.

Rather than redownloading the entire ROM, it downloads a tiny delta file and flashes it.

This way, you download a 4mb update to upgrade your nightly rather than a 150+mb update.
[Verizon Samsung Galaxy S III] ekklesiaillusion:
I'm in a month old stable build from 11-13 and can tell you for sure that there are rarely data drops(as many as any touchwiz I've used), and I've never once had a dropped call. The photo resolution is still bad on MMS but I read somewhere there's a fix, I just don't remember where.

Sent from my Galaxy SIII
[Verizon Samsung Galaxy S III] dtraini7:
Hmm.. I mean like I said, all phones are different lol. And I have not seen that fix, it could be buried in here somewhere! But I am just wondering if anyone else has had these problems and thinks that they'll get fixed soon ;)
[Verizon Samsung Galaxy S III] bluezr1:
That app's the bomb. Thanks
[Verizon Samsung Galaxy S III] funnyperson1:
The December 6th nightly supposedly helped a lot of people with data drops. You would probably want to run one of the jelly bean modems /rpms with one of the most recent nightlies.
[Verizon Samsung Galaxy S III] ups2525:
Beats you asked for...

Absolutely...just walked in the door so give me some time to get the info collected and I'll chime back in. Here ya go...I use 0917...BUT I just noticed the 11/15 updateand I'm gonna give it a go...http://xdaforums.com/showthread.php?p=30596259#post30596259...Now I get good results from the 0917 but this was recommended for CM10...http://xdaforums.com/showthread.php?t=1728391
[Verizon Samsung Galaxy S III] vdefender:
Good thinking, but I do have that set correctly, still getting nothing for GPS.
[Verizon Samsung Galaxy S III] bigjobber69:
Question for people on the newer nightlies i'm running the stable build from 11/13/12 and couldnt be happier with the build/phone. To those running nightlies or a newer build know if they pulled the group messaging from 4.2 and got it working, or was this even merged, I heard talk about it awhile back and it was never confirmed. Thanks
[Verizon Samsung Galaxy S III] mastamoon:
no group messaging in CM10 nightlies yet/ever.
[Verizon Samsung Galaxy S III] kimsj756:
Does anyone know how to change the location where the camera is saving the pictures?

I recently purchased a new sd card, and I want the camera to save new pictures on to the sd card, not the phone.

Thanks!
[Verizon Samsung Galaxy S III] RED ZMAN:
I asked the same question a couple weeks ago myself, in this thread. It is currently not available to change to the s_d card.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] ups2525:
DL'd the app, DL'd the file, watched it install, rebooted to recovery and got an error & failed install. Excited about the app and hoping someone can help me get things goin...

---------- Post added at 02:36 PM ---------- Previous post was at 01:55 PM ----------

1. Do a nandriod

2. uninstall all downloaded apps that assist gps or clear data

3. uninstall Google Maps

4. leave all location srvcs on & internal gps selected

5. reboot to cwm & wipe cache/dalvik.

DO NOT WIPE DATA

6. reflash rom, gaaps, fix permissions & reboot

7. confirm that Wifi, data, & all location services are turned on

8. confirm internal gps is selected

9. download Google Maps, take updates, while in maps click the compass on the top right

If you get a lock on your location the first thing I would do is a nandroid...immediately. If this doesnt work I would repeat the same steps but add flashing the LK3 radio in the process and I mention this because I NEVER EVER could get a lock on gps til' I clean installed 12/8 build along with the LK3 radio.

I'm a rookie and still learnig so if this works/doesnt work and or blows up your phone Im not responsible. Good luck...
[Verizon Samsung Galaxy S III] toddley:
Correct. I wonder why though doesn't seem like it would be terribly difficult to implement. The new update to Verizon messages is quite good though btw
[Verizon Samsung Galaxy S III] mastamoon:
The code was done for it, but I believe 4.2/CM10.1 has this in it by default so they decided to work on other things I suppose.
[Verizon Samsung Galaxy S III] blade7840:
I would like to try CM10 again. But I want to be sure it is stable. Last one I tried; the radio signal wasn't working right. Kept cutting on and off in areas. Where I live; I have strong 4g LTE signal.
[Verizon Samsung Galaxy S III] hopesrequiem:
Stock kernel?
[Verizon Samsung Galaxy S III] yamaha_wins:
While I've been running cm9 on my touchpad for awhile now, and it runs pretty smooth... I only wish I could say the same for cm10.

Random reboot, glitching app drawer, problems getting my backups to reflash (I'm sure this is due to cwm touch) had my battery drain completely and couldn't get phone to build a charge with OEM charger, I used the HP touchpad charger... I think I'll redownload and flash synergy until somethings are worked out a little more.

Thanks you all involved with cm10 and I'm looking forward to future improvements!

---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------

I had the same issue. It was due to the recovery I was using, I just flashed cwm 6.0.10 then flashed cm10..ml
[Verizon Samsung Galaxy S III] Dcox28:
Just confirmed with wife that when I DO have her on speaker phone she echoes when talking. Took her off speaker and echo was gone
[Verizon Samsung Galaxy S III] goatman101:
Audio probs

So the 8-21 build was fine and then I flashed the 8-22 build and now I have very little volume through the headphone jack. The volume level is extremely low, even though I have the volume up all the way. I flashed back to the 8-21 build and it is now back to normal. I hope this gets fixed in the 8-23 build because I was having fairly decent battery level with the 8-22 build.
[Verizon Samsung Galaxy S III] Relentless D:
He keeps it up to date over at Rootz:

http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v07-beta-82012/
[Verizon Samsung Galaxy S III] TechSavvy2:
I don't have any echo at all, nor do the people i speak with, and I'm completely stock cm10. Cm kernel and all. Been using for phone calls all day too and speaker phone both. I even asked my brothers and wife if they heard echo still and nobody does anymore.

If you're interested in my steps for clean install:

ROM manager - install touch recovery from within the app (6.0.1.2) - reboot recovery

Cwm - wipe data, wipe cache, wipe dalvik - I do that 3 times over (I know, I know, you don't need to say it)

Then mounts & storage - format /system. Then obviously flash ROM followed by gapps here.

Boot, let all apps restore naturally from play store on there own- then I use tibu for app data ONLY just in case, and NEVER any system apps.

That's it, and I usually don't experience the issues others report here. Never had the camera issues, but I did have echo two builds ago but not since then.

I also am always running most recent build the moment it drops for all my posts on here.
[Verizon Samsung Galaxy S III] Travisimo:
I've been running the 8/22 nightly since it appeared last night. Using the phone extensively all day, I have not had a single random reboot! I don't know if my phone has just settled down, or if the reboot problem has been fixed in the latest nightly?

I cannot comment on call echo because I only made one phone call since installing it, and that was with a CSR from Google for exchanging my Nexus 7 (screen problems). The CSR did not mention any echo.

The only problem I've run into all day is that the camera broke one time. I took a photo and it locked up. When trying to open the camera again, it gave me an error message. I had to go in an force close the Gallery, clear data, and then it was working again. (And yes, I had already done this on the previous build when the camera would cause random reboots). At any rate, I think there's still a bit of work to be done with the camera/gallery.

Data has been pretty solid. Every once in a while, the handoff will be borked a bit... meaning, it takes a little longer than expected to switch and there is a short data blackout for a second or two.

Battery life has still been phenomenal. I'm at 50% after 8 hours with quite a bit of use (about half on wifi and half on 4G). When my phone is in my pocket, it's only dropping about 2-3% an hour. I'm running Battery Monitor Widget from the Play Store that tracks my battery use, has graphs, and is an excellent program. I can see when my battery is draining faster and is gives me estimates and data on how long the battery has lasted on the current charge, as well as predictions of how long it will last based on global usage, current usage, etc.

At any rate, I'm loving these cm10 nightlies! It can only get better from here on out, right? :)
[Verizon Samsung Galaxy S III] Tbenson:
No echo for me. 8/21 build. Stock cm kernel. Use Bluetooth in my car and headset as well as just a regular phone, never tried speaker phone.
[Verizon Samsung Galaxy S III] rednukleus:
hopesrequiem, yes, stock kernel and default performance settings. I hope I haven't suddenly developed a hardware bug.

opimpao, I had this error and the zip file was somehow bad, it turned out. I just downloaded the same file again from the same source and the second copy worked. I hope your problem is that simple.
[Verizon Samsung Galaxy S III] tdperry:
You're not going to get "stable" with the early builds so you might as well go back to the TW ROM's.

TAPPED in on my (now unlocked bootloader) Verizon S3
[Verizon Samsung Galaxy S III] lackskill:
I've been in rural western colorado for the last couple weeks. During that time I've been on synergy and cvpcs' 8/16 alpha build. No noticeable change in signal strength. I was already on the cusp of unusable signal in my hotel, so any worse would have been noticed.
[Verizon Samsung Galaxy S III] saintsdarkness:
I got the same problem. Nice to know I'm not alone, but I am running a different kernel.

I'm talking about the sleep of death btw
[Verizon Samsung Galaxy S III] drbveb88:
Thanks for the insight. I also went back to stock today. And basically started from scratch. I also went to 6.012 (not the touch version)

0822 build, .7 imo lean kernel is working terrific for me.

I also had about a 500 point increase in my benchmark scores. :good:

Thanks again.

---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------

I am loving this rom. Even with its minor flaws (and what rom doesn't have its issues) It really is light years beyond stock.

And the panoramic camera is so perfect for the business I am in. I could never show off my houses like this with the stock camera!

Although I do miss my burst shots, anyway to incorporate that into the current camera?
[Verizon Samsung Galaxy S III] rbellis:
i just flashed the new CM10 and right off the bat I got a SOD. Is this normal? I did a battery pull and the screen is up but I dont know if this is going to happen again
[Verizon Samsung Galaxy S III] drbveb88:
​

What are the proper testing steps?

I spoke to about 30-40 people today, some of them were the same ones that experienced the echoing yesterday and all them confirmed that there was no echoing issues today. However, on speaker phone was a different story. About 50% of the time I experienced echoing on speaker.

Easy solution, I switched to my bluetooth and the echoing is gone for me.

I hope it gets fixed for you soon.

---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------

I cannot speak for everyone, but I have not had a single SOD all day long. (knock on wood)
[Verizon Samsung Galaxy S III] saintsdarkness:
Looks like SOD is a problem. okay i'm running 10-20120820, imos 06 kernel, and BOSS theme. also I came from Synergy rom
[Verizon Samsung Galaxy S III] drbveb88:
Have you tried to enable noise suppression under the phone settings? I saw this in an earlier post.
[Verizon Samsung Galaxy S III] rbellis:
has anyone been able to get HBO GO working on this ROM
[Verizon Samsung Galaxy S III] codyvance:
I have never had one either, ever since first build. Maybe because I have always ran imo kernel? I actually have had zero issues except for the flicker and mms, which were ez fixes.. Love this rom..
[Verizon Samsung Galaxy S III] kimsj756:
Is it same with 3rd party messaging app?
[Verizon Samsung Galaxy S III] Neverender326:
Invisiblek's unofficial build over on Rootz has group messaging with the stock aosp app. Its great. Works perfectly.
[Verizon Samsung Galaxy S III] Chris123NT:
Interesting issue I've run into. It seems that I cannot send MMS messages when I have wifi enabled in any way shape or form. I have mobile data still enabled when wifi is on so it SHOULD work but it doesn't. As soon as I turn Wifi off MMS messages send perfectly normal. Anybody else noticing this or should I try to re-flash from scratch?
[Verizon Samsung Galaxy S III] VinBertinelli:
What happened to NFC? I thought this issue was fixed
[Verizon Samsung Galaxy S III] vdefender:
Bingo!!! GPS is working. I didn't follow your instructions exactly, here is what I did. I grabbed the newest nightly (12/10) I wiped everything. I flashed. I wiped delvik and cache. I flashed gapps. Then the lk3 radio. Then booted. As soon as I was booted I clicked through intro and didnt add any accounts. Then I rebooted to recovery and fixed permissions. Then I rebooted, then turned on gps wifi and BT THEN added my gmail account and installed maps, opened it and it locked instantly. Done!! So it has something to do with either the new radio (doubtful) or fixing permissions after first boot, or installing maps and opening first thing before using gpsstatus

Edit: Now my NFC is broken :( I've never had an issue with that before. Hmmm
[Verizon Samsung Galaxy S III] Restola:
If yours won't turn on then make a backup, flash to a ICS TW rom, enable NFC, then restore your CM10 nandroid.

VZW Galaxy S3 via Tapatalk

---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------

I sent a mms with wifi on yesterday with no issues. May be intermittent or only some devices? I haven't had any problems in as long as I can remember.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] kimsj756:
Where did you get lk3?
[Verizon Samsung Galaxy S III] vdefender:
http://rootzwiki.com/topic/34053-of...zon-sgs3-sch-i535-odin-or-recovery-flashable/
[Verizon Samsung Galaxy S III] PerCompLLC:
NFC is fixed again on 12/11...
[Verizon Samsung Galaxy S III] sivarticus85:
I thought data drops were fixed as of the 12-8 build? Had a few drops today where service is strong. Using the latest LK3 modem/rpm.
[Verizon Samsung Galaxy S III] ups2525:
I have paid for every app there is for assisting in gps as well as used all the free ones. The way I described setting up the 12/8 build with the LK3 radio and doing a bare basic setup and keeping everything turned on and going straight to downloading Maps and nothing else is EXACLTLY how I got a lock. The moment I got a lock, still very early in my setup, I immediately did a nandroid. I continued doing nandroids as I went along with my usual setup and now I'm fully setup with a couple nandroids that all achieve a gps lock within a few seconds.

It was fu!@#ng halarious the first time I achieved a lock on the 12/8 build. I jumped up and did a lap around the house screaming whoo hooo the whole way!!!! I have been to hell & back trying to get a lock on CM10.

I think all the gps assist apps I was using did more harm than good.

*vdefender...Im super stocked about your achieving a lock...CONGRATS!
[Verizon Samsung Galaxy S III] patt2k:
I thought I was the only one with GPS issues any idea how to fix it or what is causing it?
[Verizon Samsung Galaxy S III] ups2525:
I responded to vdefender in post #6378 on page 638 about his concerns with gps and you can find vdefender's outcome that has how he achieved a gps lock as well in post #6385 on page 639. Good luck...let us know the outcome.
[Verizon Samsung Galaxy S III] vdefender:
Yeah! When I got my lock I jumped up in my cubical at work and shouted "I got a lock!" hahaha I got funny looks.

But now I can't get NFC working on CM again for the life of me! Argh! I flashed back to TW rom, turned on NFC, then flashed to CM and still no NFC... GPS is still good though hah. I've got the process down to get it to work.
[Verizon Samsung Galaxy S III] URPREY:
There is a flashable zip in this thread to fix NFC. Flash that and you'll be good.
[Verizon Samsung Galaxy S III] ups2525:
Did a search...Is this it? http://xdaforums.com/showthread.php?p=34758839&highlight=flash+to+fix+nfc#post34758839 page 612 post #6111??
[Verizon Samsung Galaxy S III] URPREY:
Post 6113 is the one I use

Sent from my VZW Note II
[Verizon Samsung Galaxy S III] ups2525:
Thx for sharing URPREY!!!

Go to page 612 and down to post 6113.

http://xdaforums.com/showthread.php?t=1840414&highlight=flash+to+fix+nfc&page=612
[Verizon Samsung Galaxy S III] Chris123NT:
Just a suggestion for all the people with GPS lock issues on CM10. I just noticed I had the issue, couldn't get navigation to lock for anything, gps status showed NIL. Searching for a fix I found this thread:

http://xdaforums.com/showthread.php?t=1881655

I Flashed the S3 Test 3 fix via CWM, rebooted, fired up nav and within a minute had a lock. Fired up GPS status and within seconds I got a lock on 6/18 standing near my window, so it will definitely be better in the open, and to think 20 minutes ago I was getting 0 hanging out the window (neighbors probably think I've lost it LOL)
[Verizon Samsung Galaxy S III] vdefender:
Congrats on getting that to work. I've tried it a few times and still got nothing.

But as mentioned above I now have instant GPS locks just by starting Maps as the very first thing I do on a fresh flash.

---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------

Ah shoooot. I'm having no luck with that. I tried flashing 12/11, then flashing gapps, then flashing the nfc fix. Booted and it's still broken. So then I tried going back to recovery and flashing the fix again now that I had booted the rom once, and then it still didn't work.

Any suggestions?