yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Travisimo:
It's not that the Synergy rom needed a fix - it never had this problem to begin with because it's based off of stock (and stock doesn't have this problem). It's the AOSP roms that have had data problems from the very beginning. And while they have definitely gotten better, there is still more work to do. I am actually doubtful that the 3G/4G handoff and 3G performance itself will ever be as good as stock, but then again, the devs are amazing so maybe it will! When the cm10 previews first came out, 3G data was horrible - the signal was erratic and would lose data constantly. These newer builds still have some issues in marginal areas, but seem to do pretty well in stronger areas.
[Verizon Samsung Galaxy S III] hitman_dreams:
Haha, try living in an area with -100 when the wind blows the right way. Thank god I'm moving to a house with awesome 4g coverage. The bathroom gets the fastest speed at 39mbps :D
[Verizon Samsung Galaxy S III] b3h3moth:
Nice! Sitting on the john surfing xda :D

Sent from my mom's basement.
[Verizon Samsung Galaxy S III] azbobs:
very relaxing!

:p
[Verizon Samsung Galaxy S III] zxsix:
For me, I have only called verizon phones that are not samsung phones.

Bad echo at their end, not at mine.

My in-call volume is not adjustable at all and is stuck at very loud. Volume rocker and on screen slider both have no effect. I have run it low to high and back multiple times.

If I switch to wired headset that comes with the phone, echo goes away.
[Verizon Samsung Galaxy S III] wctaylor79:
Or just go to text settings and select split at 160

Edit. Maybe that will work for you.. Sorry forgot I'm using inverted g apps and the txt app was replaced so that might just be in this version of the app.
[Verizon Samsung Galaxy S III] alee:
Same problem here.
[Verizon Samsung Galaxy S III] ercDROID:
Echo is still present on 8/28 on my phone as well. When I call my Vonage land line there is no echo. Call to my wife's Verizon sg3 has been really bad on every cm 10 after 8/19. 8/19 had no echo. Flashed synergy in between and that has no echo. Call to Verizon iPhone had echo. My Buddy let me listen to it and its basically impossible to have a conversation from the other end. Hopefully they can find a fix soon.
[Verizon Samsung Galaxy S III] azbobs:
Just curious how the echo is doing now since you checked the noise suppression?
[Verizon Samsung Galaxy S III] jdubau55:
Should be able to. I think it's a check box to split (or not to) after 160 characters.
[Verizon Samsung Galaxy S III] alee:
8/28 was solid on CDMA roaming in Canada today. Tethering worked, and data was very reliable on 3G in Toronto. Way better than my GNex in Canada.
[Verizon Samsung Galaxy S III] softwarestealer0:
Hey so cm10 is great especially jumping from 7. Only thing Im wondering what kernals are you guys using. Rom is great but battery life was better on stock. Any better results with other Kernals?
[Verizon Samsung Galaxy S III] Deevious88:
Either I'm blind or the option isn't there.
[Verizon Samsung Galaxy S III] NedDasty:
I switch today to KT's kernel, found here. Ran it all day at moderate usage and I'm still at 57%.
[Verizon Samsung Galaxy S III] Snap Jackel Pop:
On 8/28 (w/ KT Kernel) I was having issues where sound would mute when the screen was off and I'd have to manually turn it back on. Flashing back to 8/23 as I need an alarm in the morning lol.
[Verizon Samsung Galaxy S III] revolt1:
that's one a kernel issue same thing happened to me stock cm10 been nice
[Verizon Samsung Galaxy S III] Dirty13ear:
http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v07-beta-82012/ I have been using imoseyan v .7 leankernel with build 8/26 and it is running really smooth for me...pretty good battery life as well...going to test with newer build probably tomorrow.
[Verizon Samsung Galaxy S III] TechSavvy2:
I'm on 28th and stock cm kernel and have no echo issues at all. But I also never have except on one build a week ago, but went away after next nightly.

Starting to wonder why it only effects some users and not others?

---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------

Also, they found what causes echo, its just a question of when it gets merged/fixed.
[Verizon Samsung Galaxy S III] Srambo217:
As of right now, what I think best build + kernel combo for cm10?
[Verizon Samsung Galaxy S III] cgulliver:
The next build. Lol
[Verizon Samsung Galaxy S III] sfetaz:
With the last two nightlys, the change log shows nothing new. Is there a different change log than whats in op? If not why release a build with no changes?

Also does anyone know how to backup profiles?
[Verizon Samsung Galaxy S III] TechSavvy2:
Settings - dev options - check disable hw overlays box
[Verizon Samsung Galaxy S III] 1ManWolfePack:
Long press menu. Set it in settings.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
I think that did it!

Wow I can't believe it was that simple of a solution

Thank you very much for pointing that out!

I've been mentioning in a few threads about this and no one ever helped me... Again thank you, the flickering was so annoying
[Verizon Samsung Galaxy S III] TheBiles:
No builds tonight? Aww.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] frankiedizzle87:
One thing I would suggest to anyone who is first flashing is dont restart after initial boot.that's when Vzw apps stopped working and couldn't MMS
[Verizon Samsung Galaxy S III] dexter35803:
The reason MMS stops working is because it reads the nv(stuff stored on the phone) phone instead of the ruim(the sim card). they are still working on a fix but I posted a permanent mms fix that has u edit the nv and put our phone number in. so that no matter how many times u reboot your phone number will still be there. plus the phone will still read from the sim card for actual service but when, about phone reads, it reads the nv thus the reason for no number.
[Verizon Samsung Galaxy S III] TheBiles:
The permanent fix has already been completed by CVPCS. He posted a build on Google+ that included the fix. We are currently waiting for the commit to be verified and merged with the source, which is why you don't see it on the nightly yet.
[Verizon Samsung Galaxy S III] juancaperez2000:
RIL had been merged :)
[Verizon Samsung Galaxy S III] idelgado782:
I haven't had any issues with the my Verizon widget. I don't click on the actual app but I have the widget on my hone screen and when I need to go into it, I do some from there.
[Verizon Samsung Galaxy S III] pyrostic:
Has the official nightly including this been built?
[Verizon Samsung Galaxy S III] frankiedizzle87:
I cant get it to merge and I need NFL mobile its a big part of my life :)
[Verizon Samsung Galaxy S III] zakth:
not as of the 8/18 build
[Verizon Samsung Galaxy S III] juancaperez2000:
Not yet, we dont even have new built, probably this night
[Verizon Samsung Galaxy S III] GrainOsand:
I don't think it's possible to get nfl mobile app working on cm10 yet. I hope someone figures out our soon.

Fantasy football is about to start and I use it daily during football season:cool:
[Verizon Samsung Galaxy S III] droidstyle:
Can somebody please explain why incubus's cm10 thread was moved to the dev section, but this thread is allowed here? I thought this section is for developers ONLY to share thier work. Its not for guides, how to's, or im just passing this info along. This forum is outta control...
[Verizon Samsung Galaxy S III] Marcismo55:
Not sure if you all knew about this but you can remap the the hardware keys under System settings. I currently have mine set for long press of home button to open voice search and menu for recent apps. Works much better IMO.
[Verizon Samsung Galaxy S III] rossguy:
That's awesome! I used a button remapper app to do this for my nexus. Glad to see it is built into the settings. Thanks for the info. If RIL and MMS are merged tonight I'm going to be all over it!
[Verizon Samsung Galaxy S III] tekhna:
Oh christ, it's "***** about NFL Mobile Not Working on CM" season. This hasn't gotten old after what, two years of NFL Mobile not working on CM? Use a different ROM.
[Verizon Samsung Galaxy S III] idelgado782:
I've also noticed that my WiFi connection has much more stable on cm10 than what it was in tw roms. In TW it would disconnect and I had to either do the *#0011# trick or turn WiFi off and on again. However with CM10 I haven't had to do anything of the sort.

I am curious though how do these guys find out about bugs with the builds. Is there a specific forum they follow or a place we can leave bug reports? Please don't kill me. I'm just being inquisitive.
[Verizon Samsung Galaxy S III] eersfanpilot:
First of all great work to all to contributed on this ROM. It is beautiful!

I was wondering if I could throw out a few questions.

1. Any way to get the stock contracts loaded? That grid looks like crap on the favorites and I could not find any way to change it back to list view.

2. Any way to get the swipe feature back into the android keyboard as in the stock ROM without having to download another keyboard?

I was reading through the many posts regarding CM10 and it seems they will not have the S-Beam feature? Is that not possible? S-Beam and S-Voice would be nice to get back.

Thanks
[Verizon Samsung Galaxy S III] alee:
http://cm10log.appspot.com/?device=d2vzw

Plenty of new stuff.

And since nightly builds are fully automated, if there are no changes, the app still gets rebuilt. These builds are for the testers (us) as well as the developers to validate build consistencies.
[Verizon Samsung Galaxy S III] cgulliver:
http://cm10log.appspot.com/?device=d2vzw
[Verizon Samsung Galaxy S III] alee:
8/29 running OK. No obvious issues that I can tell at the moment. Still no NFC.
[Verizon Samsung Galaxy S III] mikejr83:
Lol. No one calls me except my wife now. My dad's birthday is today so I'll ask him if he notices. It looks like someone else posted that the issue has been figured out and it's a matter of time before the fix is in the build. Hopefully the next time I make a call I'll be on a new build.
[Verizon Samsung Galaxy S III] jdubau55:
Noticed yesterday while on the john...if you are trying to re-arrange the notification toggles some of them don't retain their icon while moving. For example: You have wifi, gps, BT, sound, airplane toggles enabled. You go to change their order and you pick up airplane to move it. The icon might will change to the sound icon. Not sure which ones are messed up, but some their icons stayed what they were supposed to. Some changed to a different icon.

By all means not a deal killer. Just a very slight graphic bug.

---------- Post added at 07:57 AM ---------- Previous post was at 07:52 AM ----------

It's not. The split counter option is there. I want there used to be the option above or below that to split msg after 160 characters.
[Verizon Samsung Galaxy S III] awmobjects:
Build 8/29 factory reset cache/dalvik wipe :

I have No voice assistance with Google navigation.
[Verizon Samsung Galaxy S III] jl92880:
Updated to 8/29 Nightly.

So far....I'll say again so far no IMEI issues :p Will try nav later this afternoon.

Although...not sure if this is ROM or Kernel related, but when plugging the phone via USB to my pc it sees the phone and charges. I can't browse it as a Media Device. Media Device (MTP) is checked. I've tried both WinXP+Win7 boxes along with Samsung Drives.

Thoughts? or is this a known issue?

Thanks.
[Verizon Samsung Galaxy S III] Durthquake:
I have not heard anyone mention this in a while, and i know it used to be an issue... Do you still need microsd formatted as fat32 or can you use the regular formatting? :confused:
[Verizon Samsung Galaxy S III] jl92880:
I have a 16GB SD...but even when removed...it wont detect the phone as a media device.
[Verizon Samsung Galaxy S III] hotnvicious5:
Yes! The same thing happens to me when i want to move Going Quantum to my phone lol. I usually unplug and replug a few times while the screen is off, then unlock, then you can browse files.
[Verizon Samsung Galaxy S III] Nnyan:
Haven't fully tested yet but on 28 and no reported echo, battery life is decen (stock kernel, almost three hours on battery this morning and screen at 65%?) but it needs to bake a bit longer. I did notice this morning that there was some weirdness with the alarm clock. I typically set two alarms (in case I turn off the first and fall asleep and with two little ones disrupting my sleep it does happen). This morning one of my alarms would not turn off even though it was. It eventually stopped after repeated turning alarm on and off (not sure if that really did anything or if it did it on it's own.

Bluetooth reconnects fine, Wifi and Data doing well (particularly if you are in a high strength area) but is less "sensitive" then stock (get more bars in general with stock).
[Verizon Samsung Galaxy S III] seang:
those with echoes...

i was having terrible echo for the party on the other end of the call.

i switched back to a TW rom, and they are gone.

there is no way this is a VZW network issue.

all calls in my test were placed from my couch.

also, to narrow things down a little further, i was switching from a bluetooth headset, and back to the phone, and while on the headset there was no echo.

seems like an issue with the internal speaker/microphone issue or something.
[Verizon Samsung Galaxy S III] Durthquake:
Did you check the noise suppression (or noise canceling)? people were saying if you turn that off it gets rid of the echo. - oh, and you use your phone to talk? :cyclops: :cool:
[Verizon Samsung Galaxy S III] Dcox28:
I have tried it with Noise Suppression checked but the problem is, when I have that checked then the person I'm talking to says it sounds like i'm driving with the windows down while i'm in the living room on the couch. I tested it calling the wife and she gave me her phone and i could hear the echo and or the windows down sound also.

If I leave Noise Suppression UNCHECKED and NEVER use speaker phone, then the other person never complains of anything.
[Verizon Samsung Galaxy S III] kintwofan:
I've been reading but haven't noticed this mentioned yet, but us auto bright working for everyone? Mine isn't and I'm trying to decide if it's ROM it kernel related.
[Verizon Samsung Galaxy S III] grin0048:
Not working for me--running 8/28 with latest KT kernel.
[Verizon Samsung Galaxy S III] Mean Sixteen:
Mine wasn't either on 8-28.

Don't know what changed but it is now.
[Verizon Samsung Galaxy S III] kintwofan:
Are you app on 8_28?

Also I did find a work around, just use custom backlight from the play store
[Verizon Samsung Galaxy S III] Srambo217:
Oh... Cool... Thanks.
[Verizon Samsung Galaxy S III] Mean Sixteen:
Currently on 8-29 but I may have been mistaken. It seems like when I unlock the phone the brightness adjusts but doesn't seem to actually change while using the phone.

Sorry for the confusion.
[Verizon Samsung Galaxy S III] kintwofan:
No problem, it's s very, very minor problem I'm sure it'll get worked when this the actual stable release.
[Verizon Samsung Galaxy S III] yznhmr:
Sorry what is a TW rom?

I need to get rid of them.. how far back do i have to go to get rid of the echo 23?

Ok Touch wiz duh..lol Meaning ICS rom..?? or is there a JB TW rom?
[Verizon Samsung Galaxy S III] Mean Sixteen:
TW stands for TouchWiz. That's samsung's overlay. The way the phone came stock.

It is currently ICS but there are JB leaks as well.

Edit: missed the end of your post. You know what TouchWiz is.
[Verizon Samsung Galaxy S III] krbernier:
terrible echo on other end was running 8/28. a few other bugs as well display flickers and some FC issues. back to stock for now!
[Verizon Samsung Galaxy S III] ercDROID:
I last had no echo on 8/19
[Verizon Samsung Galaxy S III] b3h3moth:
The flickers can be stopped by selecting Disable HW overlays in Developer options. The echo, well it's hit and miss with kernel and nightly combination. I've had success with 8/26 and the Kt747 kernel, but it comes and goes.

Sent from my mom's basement.
[Verizon Samsung Galaxy S III] pyrodex:
There is a 8/29 experimental build on the site to fix the dual audio. Trying it out now.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Dual audio meaning echo?
[Verizon Samsung Galaxy S III] codyvance:
File says Experimental Echo Test and there is feature added to disable dual mic for speakerphone, possibly the cause for echo?
[Verizon Samsung Galaxy S III] mikejr83:
Any news on this? I've verified that I have the echo problem via both Verizon cell phone and landlines as well as Sprint wireless. I think it's an issue with the build as I did not have the issue with cvcps's alpha 2 build.
[Verizon Samsung Galaxy S III] TheBiles:
In-call volume is hella loud on 8/29! I love it! No problems hearing when talking on the phone with my car windows down.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] alee:
It is very loud but you can't adjust it lower right now. In-call volume adjustment is broken.
[Verizon Samsung Galaxy S III] dlsolo:
Have you tried cycling the volume all the way up and then back down, during your call?
[Verizon Samsung Galaxy S III] TechSavvy2:
I can turn it down during calls and whatnot. But on the next call, it starts back loud again.
[Verizon Samsung Galaxy S III] mikejr83:
Just did a quick test with my phone and my wife's with the latest experimental. It seems to have cured the echo.
[Verizon Samsung Galaxy S III] strung:
Speakerphone volume is not adjustable and too quiet on 8/26
[Verizon Samsung Galaxy S III] kuntri:
This worked thanks. I was thinking it was Nova launcher after I've hidden the notification status bar. Thanks!!!!

Posted from my Samsung Galaxy S3-i535 loaded with AOKP Xoom Jelly 4.1.1

http://blamexoomdev.com
[Verizon Samsung Galaxy S III] alee:
There are now 3 experimentals... which one worked? http://get.cm/?device=d2vzw&type=nightly

They may be all the same.
[Verizon Samsung Galaxy S III] wctaylor79:
On third experimental.. Haven't tried phone but system seems to be running just fine
[Verizon Samsung Galaxy S III] tv31284:
It also seems like the initial commit used to fix the echo is being reverted

http://review.cyanogenmod.com/#/c/22423/

So I wonder if that 3rd experimental build has something different.
[Verizon Samsung Galaxy S III] b3h3moth:
You're welcome man. Glad to help.

Sent from my mom's basement.
[Verizon Samsung Galaxy S III] juancaperez2000:
i just want to share this: for those like me that put more atention in battery life than speed, i would like to share this, i recomend Scary Governor and i/o BFQ with this undervold you probably gonna be like me, enjoying an amazing battery life and really good performance

1134Mhz: 1110mV

1080Mhz: 1105mv

1026Mhz: 1075mV

972Mhz: 1055mV

918Mhz: 1050mV

864Mhz: 1030mV

810Mhz: 1025mV

756Mhz: 975mV

702Mhz: 925mV

648Mhz: 925mV

594Mhz: 900mV

540Mhz: 900mV

486Mhz: 875mV

384Mhz: 865mV

192Mhz: 860mV

144Mhz: 855mV

96Mhz: 845mV

this is related to CM10 and ktoonz kernel, ;)
[Verizon Samsung Galaxy S III] Imatoasta:
No offense mang but using somebody elses voltages isn't a very good idea since chips vary so much.
[Verizon Samsung Galaxy S III] BlueCross:
1. How can we get the clock centered?

2. Is it possible to move the notification bar to the bottom similar to a tablet?
[Verizon Samsung Galaxy S III] ExodusC:
Anyone else have active background apps (such as a music player like PowerAmp) close after even a small amount of multitasking?

Running background apps on the stock ROMs were properly preserved and not killed, unlike on these CM10 nightlies.

So far this is the only thing close to a deal breaker for me. I'm dealing with it, but this seems like it would be a high priority bug.
[Verizon Samsung Galaxy S III] droidxuser123:
There should be an option under developer options to stop killing background tasks

also anyone on 8/30, is it stable
[Verizon Samsung Galaxy S III] PerCompLLC:
It appears that 8/30 has been pulled... I'm getting a 404 error. Oh well - perhaps tomorrow.
[Verizon Samsung Galaxy S III] droidxuser123:
Yea I just noticed it right now
[Verizon Samsung Galaxy S III] awmobjects:
Im downloading 8/30 experimental
[Verizon Samsung Galaxy S III] Kirkenjerk:
Whats the difference between the experimental and the regular nightly?
[Verizon Samsung Galaxy S III] pyrodex:
Looks like the merged the changes for the Audience 220 chip which is used by the Samsung for noise cancellation. This is due in the next nightly and should hopefully fix the issues with echo maybe...
[Verizon Samsung Galaxy S III] awmobjects:
I believe an attempt to fix echo on calls
[Verizon Samsung Galaxy S III] PerCompLLC:
Ya, just found it. I'm running it now without issue. :cyclops:
[Verizon Samsung Galaxy S III] psufan5:
Did they fix the long text message issue?
[Verizon Samsung Galaxy S III] jl92880:
8/29 pretty stable. WiFi+Bluetooth+Data working good....no echoes. USB mounting....I'm just gonna use AirDroid to transfer my files. Havent tried NAV yet.

---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------

I did see 8/30 is released on ROM Manager...hmmmm.
[Verizon Samsung Galaxy S III] schmaltzy:
I wiped everything and flashed the August 29th built last night. I then flashed inverted GAPPS and after that the KT747 kernel. Everything seemed to be running smooth for me this morning.....until someone tried calling me.

I got an incoming call twice and when I answered I couldn't hear anything and the person on the other end couldn't hear anything. When I would call them back though, they could hear me just as and I could hear them also. I then tested it with my wife's phone and same thing; when she called me, nothing. When I call her, perfect!

Anyone else know of this problem? Should I flash an older build or something? Is it the kernel?
[Verizon Samsung Galaxy S III] psufan5:
Can someone please test the long text message issue? 160+ characters wouldnt split and send in previous builds.
[Verizon Samsung Galaxy S III] Nnyan:
8.29 pretty solid but still have the regular echo issue (land lines, cell phones, various carriers, local and LD calls). As others have reported I have not had anyone complain about echo when I'm on BT. Echo seems a bit random sometimes it will start our really bad, get getter, go worse, disappear then come back as bad as ever even on the same call. Bluetooth solid but if you turn off your BT device overnight (like I do) it will not auto-reconnect when you turn it on (BT device says that it's waiting for phone to connect). At least a simple on/off of BT on the phone gets it to connect. NAV/GPS/WiFI/Data seem about as good as before.

Did download 8.30EXP did not have time to flash, unable to download 8.30 since it's giving various web server errors.
[Verizon Samsung Galaxy S III] wctaylor79:
I just ran into this.. Got a call this morning and all was silent. Called them back and yeah worked fine. But incoming was silent.. I am running the 8/30 build though. Even though it was taken down from the official page, I grabbed straight from Jenkins. Thought it was reason it was taken from official page.. guess not if you are on 8/29.. hmmm.. Anyone else? Guess I am going to try some things today and see what happens. Good for me nobody really calls me rather I call out a lot...
[Verizon Samsung Galaxy S III] schmaltzy:
Alright, I think I fixed mine but I have no idea how I did it so I will just tell you the steps I performed. I downloaded the 8-30 build, booted into recovery, wiped cache and dalvik, flashed 8-30, rebooted. I didn't put the KT747 kernel back on cause I wanted to see how it was first. I called my phone from my work desk and I could hear back and forth just fine (actually got made fun of a bit for having 2 phones up to me ears!).

I really want to try out the KT747 kernel so I booted back into recovery, flashed KT747, wiped cache and dalvik, fixed permissions (that what he says to do when flashing his kernel), and rebooted the phone. Just tried out an incoming call and it works just fine!

It doesn't seem to be a common problem on this thread so maybe it was just a "ghost in the machine!"
[Verizon Samsung Galaxy S III] psycho_asylum:
http://jenkins.cyanogenmod.com/job/android/7171/

You can download it there. I was also getting 404 on get.cm.