yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] tprophit:
OK....in any event, I learned there was a new radio. Thanks.
[Verizon Samsung Galaxy S III] aj8600:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Is anyone getting a mms error on this rom?
[Verizon Samsung Galaxy S III] Sean Hicks:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

I'm running the vrlg7 radio, do I *need* to upgrade my radio?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] mapatton82:
4/27 and todays build are working just fine. I haven't had any issues, although todays build has the PA functionality removed.

Sent from my Galaxy S3 with a Carbon footprint

---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------

The screen flicker issues comes from the display drivers and kernel changes. I am sure the Carbon team is looking into it.

In the meantime if you haven't tried this I would suggest a clean flash of the and see if it helps. I have not had any screen flicker and I clean flash weekly if not more if I have issues.

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] glman1:
On the 4/25 nightly, GPS is pretty much broken. After 2-3 minutes, no lock. Before that, I would get a lock in 5-8 seconds. Does the 4/28 nightly have working GPS, because I really need it for RunKeeper.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I've already experienced 2 random reboots with the 4/28 nightly ktk kernel 4/27. How are the majority of you guys managing to keep a stable 3.4 nightly? I may have to go back to 1.6.1 again....
[Verizon Samsung Galaxy S III] mapatton82:
Try increasing you frequency voltages, sometimes undervolting too low can cause reboots.

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Does 3.4 kernels react differently with voltage steps? Cause in 3.0 I was running the same exact setup with no problems despite the phone freezes sometimes.
[Verizon Samsung Galaxy S III] rhcp1253:
What kernel should I use for best battery life and stability? I've been rocking stock on 422
[Verizon Samsung Galaxy S III] cobija:
For screen flicker a temp fix is dev options > check "Disable HW overlays". Im on 4/26 atm and everything is well except for a random reboot here and there when using 8tracks.
[Verizon Samsung Galaxy S III] Rinkle McBally:
[MENTION=1100673]wbm[/MENTION]arty can you check your inbox
[Verizon Samsung Galaxy S III] rhcp1253:
Which yields better battery life, dark mode or normal?
[Verizon Samsung Galaxy S III] draexo:
Seems dark would use less screen display juice

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] rhcp1253:
Can anyone confirm?
[Verizon Samsung Galaxy S III] jamesino:
yes.
[Verizon Samsung Galaxy S III] tprophit:
I'm still on 4/11 nightly. Between the 3.4/3.0/3.4 changes, email, and GPS issues I've been reading about, have held off on flashing another nightly.

Can anyone advise which of the more recent 3.4 versions of this rom are the most stable?

Thank you.
[Verizon Samsung Galaxy S III] lucky13:
I had a few reboots as well, defaulted back to stock voltages to test, none since.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
How do you find out what may be causing your phone to be running warm/hot . I'm underclocked at 1.1 GHz with mw's ktoonz/zen setup. Before I switched to 4/28 from 1.6.1 my phone wasnt getting hot
[Verizon Samsung Galaxy S III] Dragery:
I would install something like BetteryBatteryStats to find out. I'd wager if your phone is getting warm, something is running. If the screen is off, then that process will probably keep the phone from sleeping, so check the wakelocks.
[Verizon Samsung Galaxy S III] sgs22012:
Could someone send me a link to a decent set of UV values for kt747 its been a super long time since I oc/UV a kernel (was running stock for awhile after bricking two phones in 6 months)
[Verizon Samsung Galaxy S III] PeakyBoo:
You can check here for many different set ups.

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

[Team Kernelizers][How To][VZW][TK Mod 1.0.2]KT747 Kernel Tweaks - Updated 4-15-13

As for which one works best, well, you'll just have to try 'em and see which one works the best for your Phone/Set-up/usage.

Everyone's phone acts a little different. Hope this helps ya.

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] buffal0b1ll:
I had issues getting GPS lock on 4/25. Restored 4/22 nandroid. Got a GPS lock on 4/22 and flashed 4/25 again with dirty wipes before and after and fix permissions after. GPS locking fine on 4/25 now. Tested working on fitness app but not extensively.

I'm liking everything about 4/25 still. Paranoid Per app settings are cool and I get no screen flicker on lk 5.5 with voltages I posted earlier in this thread.

Disabling Google now hot word recognition stops random reboots in 4/25.

Google Voice mail in dialer still broken in 4/25:(
[Verizon Samsung Galaxy S III] ckelly33:
I am on 4/8 and have the screen flicker only every 1-2 weeks and it is easily fixed with a reboot. GPS works. Phone doesn't get hot and I'm getting 12 hours of battery life with moderate use (1-1.5 hours screen time) and medium brightness (nothing like what you guys are getting for some reason).

I have two issues that remain: occasionally when I pull up gmail, I see a waiting for sync rather than the inbox ( happens once or twice a week) and when I am in an app or on the internet on screens with scrolling, occasionally it will snap around randomly - which is pretty annoying.

Have either of these issues been fixed in the latest nightlies? *Hopefully without breaking what works (better battery life would of course be welcome too):D!!
[Verizon Samsung Galaxy S III] draexo:
The screen flicker issue seems across all the CM based roms.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] lucky13:
I take that back, last night reboot, stuck on carbon loading screen, wouldn't boot. Got into recovery, flashed nightly again with no other kernel, hoping it's fixed.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] rhcp1253:
Which build has GPS working? I'm on 22 and its just wonky
[Verizon Samsung Galaxy S III] bamaredwingsfan:
"Disabling Google now hot word recognition stops random reboots in 4/25"

Where is the settings to disable it, I went all through the Google now settings an can't find it

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] buffal0b1ll:
Open Google Search and then open Settings

Uncheck Voice>Hotword Detection

---------- Post added at 03:20 PM ---------- Previous post was at 03:13 PM ----------

CARBON-JB-EXP-22APR2013-004407-d2vzw.zip GPS was working for me.

Then I dirty flashed CARBON-JB-EXP-20130425-050005-d2vzw.zip and GPS wouldn't lock.

To get GPS locking again in CARBON-JB-EXP-20130425-050005-d2vzw.zip I followed these steps.

1. Restored my 4/22 nandroid and rebooted

2. Got GPS to lock in 4/22

3. Reboot to recovery while GPS still locked on in 4/22

4. Wipe cache and dalvik

5. Flash 4/25

6. Wipe cache and dalvik

7. Fix permissions

8. Reboot

9. Open Maps and get a GPS lock;)

Not sure why but it worked for me
[Verizon Samsung Galaxy S III] Seanzle:
mms problems

Is anyone having trouble sending mms? mine just sits at sending
[Verizon Samsung Galaxy S III] rossida:
i cant get a gps lock on 4/29 build anyone else having a problem and might have a solution?
[Verizon Samsung Galaxy S III] WettbackMartyr:
See 2 posts above your's ^ that technique has worked for me.
[Verizon Samsung Galaxy S III] glman1:
Is 4/29 3.0 or 3.4, since it's not booting with the latest 3.4 KT747.
[Verizon Samsung Galaxy S III] PeakyBoo:
4/29 nightly is 3.4

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] glman1:
Carbon only boots if I don't flash KT747 or gapps. Does anybody else have this issue?
[Verizon Samsung Galaxy S III] jamesino:
I went to 4/8 to 4/27 and back to 4/20.

I also had the colorful lines flicker once every 1-2 weeks. My gmail works and worked fine. My screen did also jump around on the 4/8.

So far, on the 4/20, I haven't had any jumping or SODs or freezes or colorful lines yet, but I've only been on it for maybe 40 hours.

Combined with the 4/27 KT kernel, the 4/20 build is a bit faster than 4/8.
[Verizon Samsung Galaxy S III] rossida:
tried that. it didnt work for me.maybe a future nightly will have gps fixed
[Verizon Samsung Galaxy S III] Setco:
Try BMS's latest kernel. Seems to work pretty smooth for me.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
For some reason, that setting is missing for me

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] buffal0b1ll:
Not Google Voice settings.

Voice in Google Search settings.

If you haven't updated then you'll want go to Play Store and update your Google Search app also.
[Verizon Samsung Galaxy S III] draexo:
I had same issue a few days ago with KT kernel.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] rhcp1253:
What's this about updated camera features?
[Verizon Samsung Galaxy S III] hootyburra:
Are you force closing KTweaker and clearing data before flashing?

I was having issues a week or so ago with reboots as soon as KT gained SU permissions.

My method of flashing now.

Download Latest Carbon and KT747

Force stop KTweaker and clear data

Open your SU app and forget any KTweaker settings.

Reboot recovery

Wipe Cache

Wipe Dalvik Cache

Flash Latest Nightyl

Flash Latest Kernel

Wipe Cache

Wipe Dalvik

Fix Permissions

Reboot

Enjoy
[Verizon Samsung Galaxy S III] OMG_VTEC:
i was having some issues with kt as well( i think). would work fine for a while then a few games would throw the phone into a wicked bootloop. only fix was a battery pull and clear cach dalvik and fix permissions. kinda got fed up and tried decimalmans new one. no bootloops so far. still dont know if it was the kernels fault or not
[Verizon Samsung Galaxy S III] tprophit:
Continue to run 4/11....today, I restored ktweaker setting that worked fine yesterday. No other changes.

Carbon lockscreen all wrong, and won't accept any changes.

Won't switch from digital to analog and back. Won't NOT show next alarm, and the time shown is not centered. Wtf happened?

Signal is lousy too, going to drive around in a bit to test.

Suggestions appreciated.

Also, phone takes noticeably longer to reboot.

Thank you.

Ok, removed and re added lockscreen widget....all is good. Wonder what happened tho.

And signal still horrid....
[Verizon Samsung Galaxy S III] Setco:
Running carbon nightly 4/30 and BMS's latest 4/27 kernel. Pretty smooth and battery life seems good too. Running badass gov. w/ row scheduler. 1512 MHz and UV to 1200:)
[Verizon Samsung Galaxy S III] lucky13:
Getting a TON of reboots (every 15-20 minutes) on a fresh install of the 4/30 nightly, stock kernel, and voice hot word detection disabled. Anyone have any ideas?

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] jlokos:
I wish I could assist, but I've been running the 4/30 nightly with the LK.5.6exp all morning and have not had any reboots.
[Verizon Samsung Galaxy S III] lucky13:
Yeah I'm going to try LK and see if it improves.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] schmaltzy:
Anyone know how to change the color of the signal strength icons in the notification bar?

I can change the battery color, battery bar color, and clock color, but don't know how to change the signal status color!
[Verizon Samsung Galaxy S III] nuke235:
Just wanted to say thanks to Team Carbon for all the hard work.

Been running for weeks on CR v1.6.1 with Lean kernel v2.9 with almost no issues. Had to battery pull 2 times but after using a custom kernel all problems went away.

Switched to KT747 kernel this weekend and have had no issues so far. Using ktoonservative as governor and deadline for scheduler.

Rom is fast and stable. The only thing I could wish for is longer battery life while screen is on. Standby battery life is amazing though, under-volting in Lean kernel and KT747 was a breeze and offered some improvements to screen time battery life.

All in all excellent ROM, can't wait to see what the next stable release of carbonrom brings. Keep up the good work!

====

Sent from my "marble white, chocolate bar shaped electronic device that apparently looks so much like an iPhone that Apple had to whine about it." using the xda-dev app
[Verizon Samsung Galaxy S III] soapinmouth:
Stock kernel on nightly seems to be plagued with reboots.
[Verizon Samsung Galaxy S III] lucky13:
Yep. Loaded up LK, not one reboot since.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] bitemeoftn:
Clean install of latest nightly and stock kernel for about 10 hours now. No hiccups, no reboots, and best of all no crazy lines! About to install the newest KT kernel to see how that goes. I'll update if I run into any problems or not.
[Verizon Samsung Galaxy S III] PeakyBoo:
Running 4/30 and Latest LK for a couple of hrs now and no problems. No more checking off HW Overlays :thumbup:

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I've been running the 4/28 nightly for 2 days now, and I've been getting alot of errors where the sdcard gets mount an unmount errors. Mostly when you access a big file on the external sdcard. Anyone else have these errors? The sdcard is a SanDisk 64gb card.

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] PeakyBoo:
Quoted from TWRP thread!

Well there we go then. Explains it all.

http://xdaforums.com/showthread.php?p=40864861

[RECOVERY] TWRP 2.5.0.0 touch recovery [2013-04-09]

Thanks.

Was just talking about SanDisk today. That's how it started for me so MAKE A BACK UP NOW! To your computer. Don't want to scare you but that's exactly how it started with me and all three San Disks. See posts..

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] rhcp1253:
Would it be possible to post a flashable stock carbon kernel?
[Verizon Samsung Galaxy S III] bitemeoftn:
Reflashing the ROM will restore the stock kernel.
[Verizon Samsung Galaxy S III] rhcp1253:
No nightly?
[Verizon Samsung Galaxy S III] tprophit:
Just flashed 4/30. GPS won't acquire..its been 5 minutes...

Suggestions?

Thank you.
[Verizon Samsung Galaxy S III] lucky13:
Almost all the nightlys are posted about 3am, so... you are correct. No nightly, yet, patience.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Too late I lost a ton of pictures a week ago. I had chalked it up to a bad format job when I first set up the card. :mad:

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] buffal0b1ll:
Had the same problem when I flashed 4/25.

To fix it I followed these steps.

1. Restored a nandroid that had working GPS (4/22 in my case) and rebooted

2. Got GPS to lock in 4/22

3. Rebooted to recovery while GPS still locked on in 4/22

4. Wipe cache and dalvik

5. Flashed 4/25

6. Wipe cache and dalvik

7. Fix permissions

8. Reboot

9. Opened Maps and get a GPS lock:)

Not sure why but it worked for me
[Verizon Samsung Galaxy S III] tprophit:
Thanks, will try. Seems like a huge step backward tho...
[Verizon Samsung Galaxy S III] buffal0b1ll:
I didn't mean you have to go back to 4/25 and 4/22. Just use that technique with whatever Nightlies you're dealing with today:)

The technique is dirty so all your data and settings stay put. Takes about 10 or 15 minutes.

And just as an aside, I'm going to stop using goo manager to order and flash zips, backup, and wipes from the gui. I loved the convenience of setting it up and coming back in 10 minutes to a new Rom, but I don't like that it can't schedule the wipe caches or fix permissions after flashing rom.
[Verizon Samsung Galaxy S III] moparfreak426:
Are aosp ROMs with 3.4 kernels more battery effient than 3.0?

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] tprophit:
Thanks, and I understood you didn't mean those nightlys specifically. I just hate when standard stuff stops working.

Anyway, I did it, it worked. Rebooted again and it took close to a minute to lock.

Thanks for the tip!
[Verizon Samsung Galaxy S III] buffal0b1ll:
I have not noticed any difference. Used 3.0 in Carbon and Sons of Android. Using 3.4 in Carbon now. I've had great battery days on both 3.0 and 3.4 and I've had crappy battery days on both also. Too many variables in usage for me to notice a trend. Also, nightlies throw in more variables.

Will say that undervolting in LK and KT kernels made noticeable difference in battery life on both 3.0 and 3.4.

---------- Post added at 01:46 AM ---------- Previous post was at 01:44 AM ----------

Sweet!
[Verizon Samsung Galaxy S III] jamesino:
I'm on 4/20 with KT 4/30. Anyone have their alarm clock sometimes not ring? I would set the alarm before I go to bed, plug the phone in, confirm that the alarm is set.But in the morning, the alarm doesn't ring and when I go into the alarm time settings, it is shown that the alarm is turned "off."
[Verizon Samsung Galaxy S III] moparfreak426:
Latest pacman is supposedly pretty sweet

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] mapatton82:
Wrong thread, this is the CarbonRom thread!!
[Verizon Samsung Galaxy S III] moparfreak426:
They were next to each other on my participated tab :/ sorry

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] WettbackMartyr:
Haven't had this happen to me exactly but I have had the phone reboot in the middle of the night on a previous build thus disabling my alarm for some reason, launcher stopped I believe. I've been running 4/20 nightly since its release with lk 5.5.5...no issues with alarms or anything for that matter. Have made this my daily driver till the next Stable Carbon release. Give lk a try. It's a fire and forget type of kernel that can be tweaked if you so choose with the Carbon built in performance controls in settings.
[Verizon Samsung Galaxy S III] rossida:
cant boot on 5/01 stuck on splash screen
[Verizon Samsung Galaxy S III] Seanzle:
Is the 5/1 nightly 3.4 kernel?

---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------

Try a 3.0 kernel and let me know... I bet that's the problem... You are flashing kt 3.4 aren't you?
[Verizon Samsung Galaxy S III] jlokos:
there is nothing in the changelog about a change in the kernel.
[Verizon Samsung Galaxy S III] rossida:
i tried booting with the stock kernel and KT 3.4 kernel. none worked. i dont have the 3.0 dled on my phone so i didnt try it. i went to my backup
[Verizon Samsung Galaxy S III] Seanzle:
Has anyone successfully booted 5/1 and if so what version kernel. I would like to flash but dont feel like being the guinea pig this time since im at work and actually need my phone currently
[Verizon Samsung Galaxy S III] rossida:
i tried everything using kt 3.4 and 3.0 and stock. none booted. tried re downloading 5/1 hoping it was a faulty dl but still not booting
[Verizon Samsung Galaxy S III] Rev. Voodoo:
I'm on the 5/1.... stock kernal (which is listed as 3.4.41)

Running well for me for about 5 hours now.....
[Verizon Samsung Galaxy S III] Seanzle:
Maybe its an issue flashing from on of the PA builds??? Im really confused as to why this wont boot for some of us
[Verizon Samsung Galaxy S III] Rev. Voodoo:
This was a dirty flash over the 4/27 build, which did have the PA settings in it. I dirtied from 4/20 -> 4/27 ->5/1 as my last three ROMs
[Verizon Samsung Galaxy S III] draexo:
Does 5/1 have kernel fixes that take care of screen flicker

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] Rev. Voodoo:
I can't be sure as I haven't ever experienced screen flicker to begin with.... nothing I've noticed since v1.1 I believe is when I started on Carbon. One of the lucky ones.
[Verizon Samsung Galaxy S III] Seanzle:
I clean wiped and still cant get 5/1 to boot. I cant figure out why it would boot for some people and not others.. makes no sense..especially with a clean wipe
[Verizon Samsung Galaxy S III] lucky13:
Anyone figure out a fix for gps other than flashing a backup that had working GPS? I do not recall which one worked in my phone and don't want to flash x amount of nightlys just to find one that worked, then flash the current one, to get the latest build to work.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] moparfreak426:
4/22 everything works

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] WhiteAssBrent:
When people talk about 3.0 & 3.4 kernels... Do those numbers represent what version of Linux built them or something completely different?

Sorry for an off topic post.

Sent from my Verizon SGS3 Carbon 1.6.1
[Verizon Samsung Galaxy S III] jlokos:
Yes; they are referring to the Linux versions.
[Verizon Samsung Galaxy S III] draexo:
I should donate to the devs but there are so many!!!

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] head33:
Donate to the team as a whole
[Verizon Samsung Galaxy S III] Rick S:
I also had problems with no gps lock, flashing, etc, so here's what I did to have a fully working 5-1 build, with ktoons 4-30 3.4 kernel...

I wiped data, wiped cache, wiped dalvik, flashed carbon 1.6.1, booted up, set up phone the way I like, turned on gps, got instant lock, rebooted to recovery, flashed 5-1, rebooted, made sure gps worked, rebooted to recovery, wiped cache, wiped dalvik, flashed ktoons 4-30 3.4 build, wiped cache, wiped dalvik, fixed permissions, then rebooted. (sorry for the run on sentence!) everything now works perfectly!
[Verizon Samsung Galaxy S III] PeakyBoo:
Screen Flicker has been FIXED since , like, 4/27-28.! For those that had it.:good

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] soapinmouth:
Clean wipe with no custom kernel?
[Verizon Samsung Galaxy S III] draexo:
Wish there had been a change log about that!

Now GPS is broke!!!

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] bamaredwingsfan:
It's really weird, but after I updated the nightly to the 4/30 one then the setting to disable the Hotword appeared, very odd

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] mapatton82:
It was not in the changelog it was a facebook/twitter post on 4/25 stating they were making a change that should fix or reduce the flicker. If you are still having issues (and it sounds like you are) I would make a backup and do a clean flash of the rom.

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] Rinkle McBally:
What are you guys using to get oc values to stick with lk? I'm on carbon 1.6.1 and I'm using trickster mod and the values won't stick
[Verizon Samsung Galaxy S III] buffal0b1ll:
You only need to disable hot word if Google Now causes crash or random reboot. If you open Google search without crash or random reboot then leave this setting alone. Try searching with and without voice recognition before you even think about disabling.
[Verizon Samsung Galaxy S III] BattsNotIncld:
GPS is bad on 5/1 build. Very slow lock and drifts like crazy. Reverted to 4/30 and all is well. Need my GPS lol.
[Verizon Samsung Galaxy S III] draexo:
I'm going back to 4/30. GPS not working at all on 5/1

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] bitemeoftn:
I saw this asked earlier and thought it deserved mention again, but is there any chance we'll be seeing multi window like liquid smooth?
[Verizon Samsung Galaxy S III] slick_rick:
Multi window?
[Verizon Samsung Galaxy S III] draexo:
Ok now GPS broke on 4/30 build when I go back from 5/1??

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] mapatton82:
Try the latest build (20130501-234722)!! GPS is working for me. I opened maps and it found my location down to 20 meters in a snow storm. So if you are still having GPS problems, I would try a clean flash of the rom if you haven't already done that.
[Verizon Samsung Galaxy S III] bitemeoftn:
So we can run two apps at the same time. Like the note 2.
[Verizon Samsung Galaxy S III] pocii29:
How accurate would you guys say Gps is on 4/30? I'm on 4/22 and even tho it works. It's not very accurate