yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] PerCompLLC:
Honestly I'm beginning to wonder if the echo is something within the VZW network...
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Can't be because my wife and my brother both have the sg3 and they are stock not rooted and they don't have that problem
[Verizon Samsung Galaxy S III] Nopi45:
I posted a fix for the echo in Q&A section.
[Verizon Samsung Galaxy S III] manny108:
MMS Force Closing

Is anybody having problems with MMS force closing? Is there a fix for this?
[Verizon Samsung Galaxy S III] jmill75:
Back to 8/23, which isn't a bad thing. Really digging the ROM. Funny thing is I had screen flicker on 23 before but it's gone now.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Don't see it.. Why not just tell us the fix here? Or link us to the fix

Edit - I've tried that already and didn't help but thanks for trying
[Verizon Samsung Galaxy S III] Nopi45:
I'm out in the field (army) and its kinda hard to post links on the app.
[Verizon Samsung Galaxy S III] sfetaz:
Would love to know what people are doing different that has their nfc working, myself and others have never gotten nfc to work using cm10, while others have. Maybe the people who get it to work are doing something different immediately after flashing?

Also my speaker sounds are muffled due to being too loud, i have expanded volume control selected and choose the 2nd one, the one with the speaker icon, i lower it and it helps with some sounds, one in particular text to speech voice.
[Verizon Samsung Galaxy S III] zxsix:
http://xdaforums.com/showthread.php?t=1855271

Though it didnt fix mine.
[Verizon Samsung Galaxy S III] yukonhijack:
Your not alone. I couldnt get it to work either. Back on TW Stock Clean Rom 2.0 for now. Hope this all gets worked out so I can go full stock Android experience.
[Verizon Samsung Galaxy S III] rbellis:
I have been going back and forth on using something like CM10 and just going back to Stock. With CM10, can you use some of the things like the "video while texting" or the S Voice? I know there is no NFC.
[Verizon Samsung Galaxy S III] rossguy:
Once you experience Jelly Bean voice search and commands you will never think about S Voice again. I don't think you can video while texting though but the pros of CM10 / Jelly Bean faaaar outweigh the little Samsung things you give up.
[Verizon Samsung Galaxy S III] codyvance:
Agree, i think you will forget alll about those features you thought you would miss :)
[Verizon Samsung Galaxy S III] Seirÿu:
Loving JB, but i do miss the motion options Samsung provided as well as the swipe to call/text gestures. - you know the gimmicky stuff that were fun but overall, CM10 JB > Stock by far
[Verizon Samsung Galaxy S III] rbellis:
y only real problem is that I dont have any volume control in call with CM10. I press the volume keys and the volume bar slides up and down but the actual volume does not change
[Verizon Samsung Galaxy S III] strung:
How does the JB camera compare with the TouchWiz camera?
[Verizon Samsung Galaxy S III] wera750:
Less features but same quality imo
[Verizon Samsung Galaxy S III] Dirty13ear:
UPDATE:

okay so I tested the fast charge by seeing how much it went up in a half hour with and without fast charge enabled...btw I am using a third party app to enable fast charge...the app prompted me saying fast charge was enabled and data transfer disabled (which normally you can't get prompt if the kernel doesn't allow fast charge...at least for what I've noticed). Even though I was prompted about fast charge it didn't seem to make a difference, my phone seemed to charge 1% every 2 or 3 minutes with fast charge on and off... just my results with imo .7 and CM 8/26....anyone else happen to test out fast charge on imo .7 with CM10 builds?
[Verizon Samsung Galaxy S III] drbveb88:
+1000
[Verizon Samsung Galaxy S III] codyvance:
Hey everyone new Kt747 kernel is out.. Lots of audio fixes.. Just installed and super smooth so far
[Verizon Samsung Galaxy S III] b3h3moth:
I was experiencing the same thing, installed the Kt747 kernel and the sound problems seemed to disappear. Are you on the stock kernel?
[Verizon Samsung Galaxy S III] codyvance:
If you have audio issues, install new KT747 kernel just posted and see if it fixes.. It specifically states CM10 audio patches
[Verizon Samsung Galaxy S III] xCHPx:
How stable is the latest nightly, and CM10 in general? Trying to decide if it's good enough to switch to yet...
[Verizon Samsung Galaxy S III] Deathbynukes:
I would wait a couple more days if you're looking for something as stable as Synergy or Beans.
[Verizon Samsung Galaxy S III] awmobjects:
8//26 build has been very good for me!...

Everything I use appears to work.
[Verizon Samsung Galaxy S III] juancaperez2000:
8/28 is up
[Verizon Samsung Galaxy S III] manny108:
Change Logs

Where can I find the change logs for CM10 nightlies?
[Verizon Samsung Galaxy S III] mustbepbs:
Serious? It's right on the OP. Bottom of first post.
[Verizon Samsung Galaxy S III] alee:
28 running really good for me. Looks like lots of display improvements. Flicker is gone and screens are all running very smooth. 4G seems steady on this cab ride to the airport. Will be roaming into Canada for a bit today so we'll see how well 3G works up there.
[Verizon Samsung Galaxy S III] manny108:
Nightlies

Sorry, I am new to this.[

QUOTE=mustbepbs;30813324]Serious? It's right on the OP. Bottom of first post.
[Verizon Samsung Galaxy S III] hitman_dreams:
Haven't checked out 8/28 yet but 8/27 has been great so far. Haven't found anything that doesn't work yet. Was surprised to see Netflix working too! BT works fine attached to my cars head unit, despite showing the name of my phone on the display. Haven't had issues with calls or volume. Haven't tried GPS yet...strike that, just tried it...works fine
[Verizon Samsung Galaxy S III] sfetaz:
Ignoring the risks involved, is there a way to fully backup settings and profiles in CM10? I have tried titanium backup and mybackuproot, and had limited success with settings and zero success with profiles. I am mainly concerned with the profiles at this point, anyone have any insight?
[Verizon Samsung Galaxy S III] awmobjects:
Did you factory reset?
[Verizon Samsung Galaxy S III] alee:
No, flashed over 27, wipe cache and Dalvik.
[Verizon Samsung Galaxy S III] psufan5:
Doesnt look like any changes in 8/28, but the file sizes are different... had to be something!
[Verizon Samsung Galaxy S III] alee:
http://cm10log.appspot.com/?device=d2vzw

Lots of display related changes.
[Verizon Samsung Galaxy S III] hotnvicious5:
If Project Butter wasn't in the other builds, then it's DEFINITELY in this build! I can just taste the smoothness... :laugh:
[Verizon Samsung Galaxy S III] FryDay444:
Is the alarm stable?
[Verizon Samsung Galaxy S III] rbellis:
I am running B8/23 with clean kernal but think I might flash this new kernal and b28
[Verizon Samsung Galaxy S III] PerCompLLC:
Yeah, for some reason the BBQLog seems to show changes after the fact sometimes (at least it appears that way to me)... There are DEFINITELY changes though.
[Verizon Samsung Galaxy S III] hitman_dreams:
Alarm is stable. I've been using it since the 8/22 build and have had no issues.
[Verizon Samsung Galaxy S III] psufan5:
There seems to be an issue sending texts over 160 characters. Any way to fix it? It will fail to send each time.
[Verizon Samsung Galaxy S III] Metalhead520:
I'm unrooted, locked bootloader, completely back to stock like when I first got the phone from the store and the GPS is still not locking on. Ive tried gps toolbox, and gps status....and another one which I can't think of right now but.....yeah none of them work at all. If a fix isnt found soon, im going to verizon and seeing about getting a warranty replacement since its stock and all that good stuff. So if you have anymore tips on what I could do to get it working again it would be greatly appreciated.
[Verizon Samsung Galaxy S III] alexcolodner:
I had the same problem a couple weeks ago. GPS stopped locking completely (I was on a road trip too...) When I got back I tried everything I could think of. I flashed back to stock with ODIN and it did not help. Tried all the different modems as well as multiple roms and configuration - no juice. Tried all of the GPS test/toolbox apps and they didn't fix it. I set everything back to stock again and went to Verizon. They ran into the same issue when testing my phone and shipped me a replacement. Turns out I had the same issue on the replacement that I had on the original phone. A few days later after flashing the official CM10 8/22 build, it started working again out of nowhere. I did not test right away on that build but I am still on that now and it works fine. I don't know what the issue was or what fixed it (maybe try 8/22?), but I don't know if getting a warranty replacement would do the trick. Might just be more of a hassle. I had a scratch on my screen so didn't mind the replacement ether way.
[Verizon Samsung Galaxy S III] rbellis:
I am trying to find the KT747 and I do not see it! Some someone please tell me where it is to give me a link
[Verizon Samsung Galaxy S III] Dcox28:
http://xdaforums.com/showthread.php?t=1853816
[Verizon Samsung Galaxy S III] Metalhead520:
Point me in the direction of the 8/22 build please cause on goo.im it skips builds between uploads from 8/21/ 8/26 i believe but no 8/22, and the actual CM site doesnt have the 8/22 build on it anywhere. Ill give that one a try for a day to see if it fixes my gps. If not I hope they don't give me a hassle on getting a warrany replacement phone.
[Verizon Samsung Galaxy S III] patt2k:
so I am also having problem with the gps first when I had the phone on stock it worked now I am on the 8/28 nightly and it won't lock at all , I don't have backup of the TW rom any other fixes?
[Verizon Samsung Galaxy S III] wctaylor79:
I am not sure what else I could suggest. I know this method has worked for me time and again. It could be faulty hardware, but as noted in the posts before this it may or may not help to get replacement. I typically have best results with "gps fix" as it leaves the gps on until locked. gps status I use to confirm the lock is solid, but sounds like you have been through them all. Wish you luck in finding the answer. :)
[Verizon Samsung Galaxy S III] AlexR666:
This is where i found the 8/22 build im about to flash. Coming back from Synergy.

http://goo.im/devs/cm/d2vzw/nightly
[Verizon Samsung Galaxy S III] detta123:
Anyone know if NFC is working in this build? It is the only thing holding me back.
[Verizon Samsung Galaxy S III] Metalhead520:
Im using the gps toolbox app, its blinking in the top left and says 0/29 Fix/Sats....so obviously meaning no fixed location for it but it sees 29 satellites in space. Ive cleared the agps and redownloaded it to no avail. Im gonna try messing with it for a few more hours then go to my verizon store to see about getting a replacement
[Verizon Samsung Galaxy S III] Mean Sixteen:
Not for me on 8/28
[Verizon Samsung Galaxy S III] dtoye:
New to the gs3 and cm10 and nightly scene, I have cm10 flashed now but to flash the newest update should I wipe data cache and dalvik? Do I have to wipe data each time I update?
[Verizon Samsung Galaxy S III] Mean Sixteen:
This is my order every time.

Wipe cache

Wipe dalvik

Flash rom

Flash gapps

Wipe cache

Wipe dalvik

Fix permissions

reboot

No problems
[Verizon Samsung Galaxy S III] seang:
8/27 woke me up this morning.
[Verizon Samsung Galaxy S III] scarroll825:
I've read through virtually this entire thread and haven't been able to find anyone with the same problem as me. I posted this in Q&A, but I didn't get any solid answers. Every single JB ROM that I flash gives me the same problem: It will work great for several hours (just long enough to get me hooked) and then it will go into constant, one-after-the-next reboots (just the bootscreen though not a full reboot). Also not exactly a bootloop because it will bring up the lock screen and work for a second or two before it does it again. I will also get multiple FC errors. I've tried wiping cache and dalvic then rebooting, tried fixing permissions, tried reflashing gapps, nothing works. This messed up this is that this happens no matter what JB ROM/Kernel combo I am using (tried AOKP, at least four CM10 builds, and the two available kernels). Every time it doesn't work I usually end up ODINing back to stock, rerooting, reinstalling CWM, and unlocking before attempting to flash again. Does anyone have any idea what could be causing this problem? It seems like by now CM10 is functioning (i.e. not constantly rebooting) for everyone else and it's making me extremely jealous lol. Thanks in advance for anyone who might be able to help a brother out.
[Verizon Samsung Galaxy S III] seang:
i dont flash gapps every time.

i just wipe cache, and dalvic.

flash rom.

done.

been doing that method since the first unlocked bootloader version.

did it like that on my old D1 too. once gapps is there, its there.
[Verizon Samsung Galaxy S III] psycho_asylum:
Have you wiped data and cache after flashing? Forgetting to wipe the cache can cause this.
[Verizon Samsung Galaxy S III] seang:
did you do a factory reset prior to installing the ROM?

---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------

I use handcent, and there is an option to auto split at 160 characters. i used that option, and it fixed the issue.
[Verizon Samsung Galaxy S III] scarroll825:
Yeah factory reset/data, cache, and dalvic each time. Is it possible that this is a problem with recovery not wiping properly? I've been using 6.0.1.0 each time. Even tried flashing from both the ex-recovery app and rom manager.
[Verizon Samsung Galaxy S III] seang:
i havent used CWM in a long time. i use TWRP.

on my first install, i did a factory reset, wiped cache, then dalvic cache.

installed rom, then gapps, reboot. done.

from the OP... just for grins, i would use an updated recovery as a first step in troubleshooting.

also, make sure all of these steps are done.

YOU MUST BE ROOTED:

I recommend using the Casual app from Adam in THIS THREAD.

YOU MUST BE UNLOCKED:

As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.

YOU MUST BE RUNNING A CUSTOM RECOVERY:

Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want.

Originally Posted by blade7840	Can I use TWRP recovery to flash this Rom?
​

Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing.

BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC

* CWM 6.0.1.0 is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
[Verizon Samsung Galaxy S III] codyvance:
I would try newest version of CWM 6.0.1.2 install from rom manager then try again..
[Verizon Samsung Galaxy S III] scarroll825:
Thanks I'll try that, also I ran a log in recovery after wiping cache . I don't know if any of these lines are red-flags, but here they are just in case they are.

I:Can't partition non-vfat: datamedia
I:Can't partition unsafe device: dev/block/mmcblk1p1
I:Can't format unknown volume: /emmc
[Verizon Samsung Galaxy S III] jgrimberg1979:
I apologize on advance if this has already been addressed. I am Tapatalk so the search blows. Anyways is there a fix for the camera storage issue. It defaults to internal storage and my dcim folder is on external SD. Thanks
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
when i do clean install i wipe system,data, and cache and factory reset and dalvik..

is that too much?
[Verizon Samsung Galaxy S III] Ignite023:
Not sure if this was already answered.. Can I do dirty updates nightly, or is a wipe recommended?

Thanks.
[Verizon Samsung Galaxy S III] 1ManWolfePack:
I'll give you the same answer you'll always get:

Try it. If you have errors, don't come here and talk about them until you've done a clean flash. You'll probably be fine.
[Verizon Samsung Galaxy S III] Deathbynukes:
Wipe is recommended, but some people have reported that dirty flashing works. Proceed at your own risk.
[Verizon Samsung Galaxy S III] codyvance:
That is considered a clean install, i dirty install most times by wiping cache and dalvik, install rom, install kernel, wipe cache and dalvik again, fix permissions, reboot

Never had issues with this rom..
[Verizon Samsung Galaxy S III] jdubau55:
Went with Synergy for about 3 hours. Didn't like it. TouchWiz just has too much crap going on still.

I re-flashed the CVCPS 8/16 build which has been pretty solid for me.

---------- Post added at 01:02 PM ---------- Previous post was at 12:53 PM ----------

Is it just me or does holding Menu to get Google Now not work? Google Now works if you use the icon, but even after running it, going to home, and trying to shortcut using the menu key doesn't open it.
[Verizon Samsung Galaxy S III] codyvance:
Did you reconfigure the hardware keys?
[Verizon Samsung Galaxy S III] SightSeeker:
How is batter life lately? Last time I had this on it was getting killed in standby overnight. No different apps then on TW roms.
[Verizon Samsung Galaxy S III] ruben8448:
I ran 8-25 for about an hour and my data dropped 8 times. I saw more grey bars over blue. Could it be the kernel? I'm using Imo v. 7
[Verizon Samsung Galaxy S III] Dirty13ear:
I am using the same kernel with 8/26 and haven't noticed any data issues... I have heard that the earlier versions of the kernel or CM10 didn't play well together but so far with 8/26 and imo v. 7 it seems to be in order.
[Verizon Samsung Galaxy S III] alexcolodner:
Hope it works for you guys. Let us know the verdict.
[Verizon Samsung Galaxy S III] scarroll825:
I tired flashing with TWRP, same story. To me the interesting thing is that if I start from scratch (ODID stock,root, recovery, unlock, wipe, flash) CM10 will work for a while, but it will eventually fall back into the reboots and FCs. From that point if I try to wipe and reflash the rom or a different JB rom (or even restore stock), it will be the same thing. When I try to restore from a nandroid it is constantly freezing up (tried ODINing stock kernel to make sure that wasn't it and same deal). Eventually I am forced to ODIN stock to get it to function properly. I would think that it is just a faulty device but it functions fine stock so I can't really bring it in to verizon.
[Verizon Samsung Galaxy S III] henrys01:
I just did a little test here at work. When I call another stock VZ sgs3 it echo's. However, when I call an ATT or land line there's no echo. I've tried the settings in the dialer and they have no effect. I think the problem only happens when you call another phone in the VZ network..
[Verizon Samsung Galaxy S III] PerCompLLC:
And occasionally it happens when my wife calls me from her gnex. But then I'll call her back and there is no echo. That is why I'm thinking that it just "might" be the VZW network.
[Verizon Samsung Galaxy S III] ugachris:
Why don't you do like the original poster said and try flashing with CWM instead of TWRP? Use the EZ-Recovery app from the market to flash CWM and then flash CM10.
[Verizon Samsung Galaxy S III] krbernier:
video player

what video player are you using on this. i was using mobo pro but it keep FC on this rom.
[Verizon Samsung Galaxy S III] henrys01:
NM, just called another ATT phone and it echo's. It definitely doesn't echo when calling land lines though.
[Verizon Samsung Galaxy S III] jdubau55:
Found that while on the crapper.
[Verizon Samsung Galaxy S III] zachtannehill:
I call my wife's razr and she says it constantly echos too (on vzw)
[Verizon Samsung Galaxy S III] Version_3:
Stock kernel, data drops on 3G in low signal areas. I've not noticed the issue in higher signal areas or on 4G.

I've tried VRLF2 and VRLG1.

Edit: I had a drop on 4G just now.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
How many different Verizon phones did you test with? Because I'm beginning to think it has something to do with the call eq that the sg3 has.. Idk why I think that if I flashed back into stock then turned off the eq and then flashed back to cm10 it would help.. But I honestly don't feel like testing that theory.. Also the other Verizon phone you call make sure they have the eq off.. I will test that theory later with my wife because she has a stock sg3
[Verizon Samsung Galaxy S III] keatond:
Im in a poor reception zone so my 3G is usually around 86-83 in strength. It drops every 3-4 minutes for about 15 seconds then comes back. I switched to synergy and it doesnt happen....I wonder what fix they have...
[Verizon Samsung Galaxy S III] alexcolodner:
BSPlayer has been working for me flawlessly, even with large HD files.
[Verizon Samsung Galaxy S III] tomyboombotz:
Take mms. Apk from 23 and install it it will reactivate split txt messaging feature for some reason they took it out in the latest nightly
[Verizon Samsung Galaxy S III] lxetuo:
Can you turn off the splitting?
[Verizon Samsung Galaxy S III] yznhmr:
horrible echo,,ouch..
[Verizon Samsung Galaxy S III] strung:
8/26 is the best build so far

No echo

/edit Just got sleep of death. =[
[Verizon Samsung Galaxy S III] XooLoo:
What kind of speeds are you getting on your tethered device when in full 4G coverage? I used to get 23+ Mbps on the very first nightly, but after flashing the 2nd one (sorry, can't remember the dates) I can't get anything higher than 6-7 both on the phone and my laptop, Nexus 7, etc. Anyone else having similar issues?
[Verizon Samsung Galaxy S III] ercDROID:
8/26 still have terrible echo. Workaround also didn't work. Full wipe. Used both stock and KT kernel.
[Verizon Samsung Galaxy S III] strung:
People having echo issues, it might be helpful to know:

1) What network (and phone) is on the other end? E.g. landline, AT&T

2) Does the echo go away or get reduced when you turn down your in-call volume (in order to limit as much sound being echoed back from the earpiece to the mic)?

(Also, if you are flashing another kernel after flashing a latest nightly, you won't get all the changes unless that kernel is pulling in the latest CM code.)
[Verizon Samsung Galaxy S III] xsteven77x:
Sounds like the cpu is clocked too high.
[Verizon Samsung Galaxy S III] yznhmr:
1 MY VZ to land line

2 I tried it with the volume all the way up and each segment down.. still echo

IM on 28 with the KT747-Kernel-AOSP-JB-VERIZON-8-27.zip (tried it without and then with the kernel)
[Verizon Samsung Galaxy S III] scarroll825:
I haven't changed any of the performance settings in the ROMs, is there any reason this would happen by itself?
[Verizon Samsung Galaxy S III] mikejr83:
Confirmed echo issue with SGS3 to both a VZW wireless and VZW land line. I tried to adjust volume but didn't get a response that it helped.

I'm on 8/28 cm10 and 8/27 KT747 kernel.

After my last call I went to dialer->settings and checked Noise Suppression. It wasn't checked so maybe that will help.