yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] tombepa:
No go. Rebooted. MMS broke. Now phone number shows unknown. Been looking around for a few to find an answer, but how do I get my number back?
[Verizon Samsung Galaxy S III] THE SKATER DUDE:
When I first boot this up do I need to skip activating by using the counter clockwise method on the welcome screen?
[Verizon Samsung Galaxy S III] frankiedizzle87:
I am going to keep an eye on this nightly. Once that's fixed ill root. Coming from gal nexus its hard to not root and mod but mms is a major part of my day to day
[Verizon Samsung Galaxy S III] tombepa:
Nevermind. I did restore on cleanrom. Think I'll wait a couple weeks before doing cm10 again
[Verizon Samsung Galaxy S III] TechSavvy2:
Been running official since it dropped last night. Haven't had a single reboot yet. Don't let this get buried....lol.

Aside from that, its like people in here don't read. Its only on page 6 and all of those 6 pages are literally already the same thing over and over and over. How many times does cvpcs / Austins g+ post need to be iterated here? MMS ril and whatnot will be in tonights or tomorrows build.

READ THE OP BEFORE POSTING!!!!!!!
[Verizon Samsung Galaxy S III] neyenlives:
If you root first and purchase an app like Titanium Backup it will backup your app data and allow you to restore it later after you install.

The instructions are in the OP, do what it says, nothing else, and it will come back.

I've never seen an activating screen at boot. I also don't wipe when i flash each one, so that's probably it. Someone more familiar with CM fresh boots will have to answer that one.
[Verizon Samsung Galaxy S III] psycho_asylum:
Does anyone have any problems with screen rotation? I just noticed the YouTube app didn't rotate and tried a few other apps. Rotation is enabled, it just doesn't work.
[Verizon Samsung Galaxy S III] codyvance:
My GPS wont lock, anyone else?
[Verizon Samsung Galaxy S III] TheBiles:
Because that commit hasn't been made to official CM yet. This has been covered many times.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] idelgado782:
I can definitely confirm that completely steps as described in the op, I have successfully gotten MMS working not once but after two reboots. It is a bit tedious but worth it you want to use cm10 and need MMS working. I did lose my phone number however in settings but that's not a deal breaker for me right now. I'm enjoying being on CM10 and look forward to flashing the nightlies. :thumbup:
[Verizon Samsung Galaxy S III] prenedo:
Anyone working on a flashable nav bar? I know there was one in mods section but it doesn't work with newer releases....
[Verizon Samsung Galaxy S III] Hilbe:
Did you copy this off the wiki? :)
[Verizon Samsung Galaxy S III] TheBiles:
Or you could flash the build CVPCS posted and wait for the commit... /facepalm

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] PerCompLLC:
No expiration.
[Verizon Samsung Galaxy S III] BosCeltics18:
I was so close to flashing this Rom, but I realized I am better off waiting for the official build to release. I can't stand bugs and dislike flashing new builds daily. Touch Wiz is pretty cool rooted. I will be sticking with this till CM10 is official.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] skinnytoo2:
I flashed last night and my exchange email kept crashing. I uninstalled account and reinstalled with same result. So I tried touchdown and it works, but the calendar is terrible. The stock TW calendar is so much better. Anyone have same issue or any ideas?

Thanks!
[Verizon Samsung Galaxy S III] yankzfan007:
Also the disable HW Button Backlight doesnt stick.. :confused:
[Verizon Samsung Galaxy S III] codyvance:
Im pretty sure this is normal functionality.. Some dev options don't stick on reboot..
[Verizon Samsung Galaxy S III] irtehun:
Is the call echo fixed on latest nightly
[Verizon Samsung Galaxy S III] allareconnected:
Anybody got foxfi working on CM10? It's not working for me.
[Verizon Samsung Galaxy S III] b3h3moth:
I don't know if it was fixed in the nightly, but I installed the latest nightly, along with a cache wipe and davlik wipe. I followed that up with imoseyon's leankernel beta install, and checked the 'Noise Suppression' under call settings. (open phone>menu button> settings) I was told from two separate people that echo was gone. They both commented on it before...so, not sure what fixed it, but it seems to not be an issue with mine anymore.

There's a link to imoseyon's kernel on rootzwiki.. couldn't find a xda link.
[Verizon Samsung Galaxy S III] irtehun:
Thanks. I'll flash and find out
[Verizon Samsung Galaxy S III] b3h3moth:
Good luck man. Keep us posted, maybe we can figure out a workaround.
[Verizon Samsung Galaxy S III] FormeriPhoney:
Foxfi is not working but native tethering works great

SGS3 production
[Verizon Samsung Galaxy S III] TechSavvy2:
Ability to save to extSD haven't been implemented/fixed yet. And disable hw overlay may never stick, just have to wait out the screen flicker fix.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
ECHO IS STILL NOT FIXED ON LATEST NIGHTLY!!

everyone saying that it is can you please test right...it is sooo misleading
[Verizon Samsung Galaxy S III] strung:
Can someone explain the echo problem? Where do you hear it? On the GSIII end or on the other end?
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
the other person hears a really bad echo.

so many people dont use the phone app i guess...lol

as soon as i flash the latest nightly i call three people to test

i call landline as well to make sure and they all said the same thing
[Verizon Samsung Galaxy S III] andreiantal:
The other end hear them selves. You don't detect the echo on your end.
[Verizon Samsung Galaxy S III] b3h3moth:
Ive been told by two or three people that had experienced the echo previously that they did not hear it anymore. Its kind of hard to test yourself. I posted what steps I took a page back.

It is coming from the other end. The caller will hear an echo when speaking.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
i see on your sig that you are using a custom kernel

maybe that could be the reason you are not having that issue??
[Verizon Samsung Galaxy S III] TheBiles:
Native tether works.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] tdperry:
Have LTE here, but will be able to check later today as I'm driving to pick up my wife from work. LTE doesn't work out that far.

TAPPED in on my (now unlocked bootloader) Verizon S3
[Verizon Samsung Galaxy S III] cynikalJ:
I am assuming the low video sound recording bug is still present..
[Verizon Samsung Galaxy S III] AtLemacks:
What do you need me to elaborate on? All info is right there.
[Verizon Samsung Galaxy S III] M Diddy:
How does editing you build prop fix the issues with BT, NFC, etc?
[Verizon Samsung Galaxy S III] tcsac:
I can also confirm that sound is AM-ish over bluetooth. However if I make a call and hang up, bluetooth sound is normal until the phone disconnects and reconnects.
[Verizon Samsung Galaxy S III] funkdoctor:
3g data drops are improved with new radio - but still there, low video recording volume, bluetooth sounds tinny...
[Verizon Samsung Galaxy S III] jackpot08:
For some reason on the last 2 nite lease my phone microphone has not been working. People on the other line cannot hear my voice
[Verizon Samsung Galaxy S III] hopesrequiem:
Clean or dirty flash? If not clean, please try a clean install first. Then report if that issue is still there. Not trying to preach, just narrow it down for us
[Verizon Samsung Galaxy S III] jackpot08:
Sorry I forgot to mention.i tried twi clean flashes from the last two nightlies. very weird.its like the main function for my phone which is phone calls doesn't work lol
[Verizon Samsung Galaxy S III] sweeds:
Confirmation, flashing Gmail 4.2 apk works as intended. Great feature upgrades! :)
[Verizon Samsung Galaxy S III] mangler1055:
hoping someone can help me with a problem i'm having.

i've been happily running 10.0.0 essentially since it came out. it was a clean install.

all of the sudden today i could only get 3g even though everyone i was with was getting 4g. then all of the sudden it was only showing Roaming. i still have my IMEI and other vital information in About. i've tried a few different modems, but nothing changes.

i got it back temporarily by flashing a TW rom and then pulling/reinserting the SIM card. it was even 4g for a bit when i restored my CM10 nandroid. but after a reboot it went away. i've tried a few different radios, but no luck.

any ideas? thanks!

Edit: HE radio seems to be working now. which is strange because that is what i had been running in the first place. all of the newer ones have me roaming.
[Verizon Samsung Galaxy S III] tekhna:
I hate to be that guy, but after running CM10 since the kexec days, I'm going back to TW until this ROM gets sorted out. It seems to be backsliding in a lot of ways, and I need stuff like a functioning GPS and clock on my phone (yeah, that's a weird new bug).
[Verizon Samsung Galaxy S III] bby144:
Yep. I come back to cm10 after weeks and it seems there are new problems Coming up
[Verizon Samsung Galaxy S III] PerCompLLC:
Used my GPS yesterday without issue to deliver something for my wife. I'm not aware of any clock issues... I'm not saying that your issues don't exist, but I have yet to experience them. This (CM10) has been a great daily driver for me.

I'm just saying - to those that are thinking about trying CM10 - try it before you judge. It is certainly not for everyone, but don't judge just by what you read here...

-CM10 Nightly (11/24) w/ lean kernel 1.10
[Verizon Samsung Galaxy S III] gregurbo:
I agree with you. You can't go by what you read here. I'm on CM10 Stable build and its been great for me. I don't have any problems with GPS,data, clock....The only thing that I have experienced is sometimes when waking the phone with the power button it will give me a blank screen but with a second tap of the power button it always wakes fine and screen comes back. It all just depends on your device or how you installed everything... For me this has been a great daily driver and I have no real complaints.:D

Sent from my SCH-I535 running CM10 :)
[Verizon Samsung Galaxy S III] mangler1055:
So no one else has gone roaming without having any IMEI issues?
[Verizon Samsung Galaxy S III] blu3poptart:
I don't know if this has been discussed before but I can't get gif images to work. They are displayed as a static image. Is there any way to fix this?
[Verizon Samsung Galaxy S III] PerCompLLC:
I assume that you mean animated gifs (as opposed to static gifs). What application are you referring to that they are not animating in?
[Verizon Samsung Galaxy S III] TechSavvy2:
Agreed. Its why I usually don't follow the thread anymore. I don't have any of the issues people have in here. And then when I say I don't have the issues, someone jumps in jaggin about how I'm not helping anyone blah blah blah. I just don't see the point of "I'm going back to tw, this ROM doesn't work" comments. What's the point? So everyone knows which ROM youre running all the time? We were all waiting to find out....now I can sleep better, lol. It sucks for new people to come in and see those comments cuz then they avoid flashing it all because some guy can't get stuff working right. Kinda cripples the process.
[Verizon Samsung Galaxy S III] droidxuser123:
The stock gallery display them as stills. I use quickpic anyway
[Verizon Samsung Galaxy S III] TechSavvy2:
#6000!!!!
[Verizon Samsung Galaxy S III] zipkicker:
Haxsync is a fantastic app for this
[Verizon Samsung Galaxy S III] drdagreenphd:
I couldn't agree more. CMX is like wine: Gets better over time, not everyone likes it, and it's not perfect but does the job.
[Verizon Samsung Galaxy S III] RED ZMAN:
Can anyone help me here?

I go to any video site, go fullscreen, and cannot get video controls. Dolphin and stock browser. This used to not be a problem. I'm on 10.0.0, but this didn't happen on m1.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] TechSavvy2:
Advice for people with GPS issues...go to settings -apps - all - clear data in Google services framework. Has worked like a charm on every build so far. But you need to reboot to have play store work after that. GPS works flawless if you clean install every build though (but who wants to do that, lol).
[Verizon Samsung Galaxy S III] tekhna:
lol wut? I've been flashing ROMs for god knows how long. See the registration date next to my name? I know how this is done. I've had stable CM10 installs, and I've had total garbage CM10 installs. The current iteration is garbage. It's total hit or miss, and frankly it's either dumb lock or the vagaries of phones that seem to be the predictors of success; I've never in my time using Android seen a ROM as inconsistent as CM10 on the D2VZW. That's just the facts. I hate TW, but I also hate the fact that my phone SODs, can't lock onto the GPS (except certain builds, when it can), and now seemingly can't keep time. The ROM was more stable in August than it is November. Period.
[Verizon Samsung Galaxy S III] Brian Gove:
AOKP milestone is damn solid, if you wanna stick with an AOSP based ROM anyways. It's 'old' but I've used it for a dd since it dropped with relatively no issues.
[Verizon Samsung Galaxy S III] AtLemacks:
CM is built first based off AOSP builds stripped from Nexus devices and source/etc. When you used to install Wallet (before the newest build at least), you had to change the build.prop to some Nexus values, then you could revert back and use it without issue. Well, There have been 2 or 3 occasions that I have not reverted back to d2vzw values and noticed I did not have half the issues I had when running it on those values. BT was one instance, NFC was the other.
[Verizon Samsung Galaxy S III] Imatoasta:
Lol if you've read the thread you would get the impression that nothing works on cm10 but here I am on the stable build with everything working. Crazy, I know. All of this without source. Imagine when the source is released?
[Verizon Samsung Galaxy S III] EGill42:
Thanks for the advice, but it does not seem to be working for me. I have even used odin back to a stock TW rom before reloading CM10 to get my GPS working. No luck. Although, using GPS Test I have gotten it to claim I have a fixed location, yet Google Maps still wouldn't locate me.
[Verizon Samsung Galaxy S III] TechSavvy2:
Lol, I COMPLETELY apologize, I forgot that the registration date of a user is the implication of how much someone knows about flashing roms. I'm with Imatoasta on this one. Haven't had any "inconsistancy" since the september builds. I can, with 99% confidence interval, say that every build pumped out lately has had all the things you complained about working for me. I use GPS for about 4-5 hours a day. NEVER had a SOD since about august, and no idea what time issues you are speaking of. THe only issue I've experienced is the BT bass issue lately.

I guess what's so annoying about the thread is that its always negatively focused on what's not working. Angry people basically stating how nothing works correctly. Almost like a bash-fest of cm maintenance. VERY glass half empty. People wonder why our maintainer isn't in here helping out. He said on twitter that he gets really pissed off everytime he pokes his head in and reads. Understandably too. Devs have stated this is the exact reason you usually don't see them around anymore except pumping out builds.

I am sorry though that you took offense to what I said. I did quote you, but was actually referring to the entire thread as a whole.

I love and appreciate CM. I accept it for what it is. They're nightlies. People have problems with nightlies, run M-builds. Have a problem with those, run stable. Problems with that, run TW. Problems with that, buy another phone.
[Verizon Samsung Galaxy S III] iofthestorm:
Err are you talking about cvpcs? Or is it invisiblek I can't actually tell who is our maintainer. Either way I kind of agree that most of the issues seem to happen to a small number of users but at the same time I haven't seen hardly anything device specific for us in ages. Thus I pretty much only flash an update when I'm bored or something interesting gets added to CM. I think I'm on a build at least 2 or 3 weeks old and I really have not had many issues at all since flashing CM10 the first time in august and I've only done one clean install in that time. GPS, NFC, data, everything is fine for me. But clearly some people have problems so I don't know what to say to those people other than try to get some logs pertaining to the issue. I think GPS and data are probably also affected by where you live so it's hard to debug these issues. App crashes are actually pretty easy to debug IMO, logcat will usually tell you everything you need to know and its usually not the ROM's fault but the hardware specific stuff is undoubtedly quite tricky otherwise it would be more consistent and reliable and easily fixed. Also I feel like these days Touchwiz is not half bad, just ugly so I don't feel too bad for those moving back to TW.
[Verizon Samsung Galaxy S III] Div033:
I agree with you, but I checked cvpcs' twitter and was unable to find any such posts. Could you show me what you're talking about?
[Verizon Samsung Galaxy S III] eppo12-:
I've been running CM10 stable for a few days now. Works flawlessly, not one issue so far. I was scared to try it due to the negative posts, but had switched to a new synergy Rom, so figured why not. Glad I made the switch!
[Verizon Samsung Galaxy S III] yddot:
I've been following this thread for a lllllong time and I thought I'd add my two cents...

This ROM does work wonderfully. It's extremely smooth and for the most part fully functional. There are a few bugs whose resolution I'm still awaiting, however:

In-call volume bug (already mentioned)... if I set the earpiece volume lower than the absolute middle level, the volume on the next phone call is PIERCINGLY loud, even though it shows the volume set at the lower level. Or sometimes I can't adjust the volume while the phone is at my ear.

Low quality MMS pictures (already mentioned)

Equalizer... if I listen to music from any app for 20 minutes or so, the equalizer stops equalizing--i.e. the music goes back to playing as recorded, without the effect from the equalizer. I have to stop the music and restart for the equalizer settings to take effect again.

Battery life seems to have taken a dive since (approximately) the latest experimental build.

I'm on the 11-24 nightly, flashed directly from the stock Verizon/Samsung cheez-wiz ROM.

Like I said, the ROM works excellently for the most part. Just a few GS3-specific bugs that need to be worked out (my Galaxy Nexus didn't have any of the above issues, except terrible battery life, which was most likely just due to older hardware).
[Verizon Samsung Galaxy S III] hopesrequiem:
Personally cm10 or synergys cm10x ROM run better for me then stock. Battery life blows tw away now. I always have GPS working too. Cm is the best ROM out tbh. It may not work for all but it is killer on my phone
[Verizon Samsung Galaxy S III] Desertburn:
nightlies 112512

new nightlies broken again. seems to have quite a few broken links past few weeks.otherwise this is the ROM i use all the time works great!
[Verizon Samsung Galaxy S III] TechSavvy2:
I think it was like a month ago. I'll find it.

Broken links? I'm on last nights and only bug still is BT bass.
[Verizon Samsung Galaxy S III] aeroevan:
Does the latest nightly have http://review.cyanogenmod.org/#/c/26891/ merged in?

My latest CM10+linaro unofficial build has it merged in already if you want to give that a shot (http://goo.im/devs/aeroevan/cm10/cm-10-20121124-UNOFFICIAL-d2vzw.zip).

EDIT: that build also has all of the recent msm_fb and qcom/display patches submitted by cyanogen and all of the linaro patches and is built with latest linaro toolchain.
[Verizon Samsung Galaxy S III] cvo515:
What's the deal with the gallery turning portrait pics side ways in mms? Lol drives me nuts because I can't get my muscle memory to turn my phone landscape for pictures! Haha
[Verizon Samsung Galaxy S III] TechSavvy2:
Yes, was merged in 11/24 build.

Your linaro builds are pretty exciting, thank you!
[Verizon Samsung Galaxy S III] PerCompLLC:
Nope, they're up...
[Verizon Samsung Galaxy S III] anidamo:
Anyone else have DNS problems when on 3G? I tried a nightly back in August and I had to revert to stock because 3G had issues with DNS resolution. WiFi worked fine, but as soon as I disabled it and dropped down to 3G (no 4G in my city) many sites would refuse to load. Google services like search, youtube, android.com, etc., seemed to be fine, but non-Google sites wouldn't load in the browser and all apps throw an UnknownHostException, with the message (for example, my app gives this message when attempting to connect to my server) "Unable to resolve host "www.leetsoft.net": No address associated with hostname".

Curiously, the Play Store doesn't connect either, complaining of hostname resolution problems as well, though I can load play.google.com in the browser.

EDIT: Running getprop | grep dns displays the following:

getprop | grep dns
[net.change]: [net.dnschange]
[net.dns1]: [2001:4888:3:fffe:c0:d:0:3]
[net.dns2]: [2001:4888:2:fffe:a0:d:0:3]
[net.dnschange]: [1]
[net.rmnet0.dns1]: []
[net.rmnet0.dns2]: []
[net.rmnet1.dns1]: [2001:4888:3:fffe:c0:d:0:3]
[net.rmnet1.dns2]: [2001:4888:2:fffe:a0:d:0:3]

Is there any way I can manually set the DNS to 8.8.8.8 and 8.8.4.4 and have it persist after reboot? I tried using setprop net.dns1 8.8.8.8 but it was reverted after a reboot.
[Verizon Samsung Galaxy S III] VinBertinelli:
youtubes a little laggy
[Verizon Samsung Galaxy S III] aeroevan:
Just set it in your built.prop, that should work
[Verizon Samsung Galaxy S III] WhammyDroid:
All,

I reported an issue a while back with having issues disconnecting BT from the BT device. I need some help in getting this issue justified because the CM10 issue manager thinks this issue is not important.

https://code.google.com/p/cyanogenmod/issues/detail?id=6659

Any help would be greatly appreciated! Thanks!
[Verizon Samsung Galaxy S III] aeroevan:
It looks like you forgot to complete the bug report form. Like did you wipe data, have a task killer etc.
[Verizon Samsung Galaxy S III] peaceofpi:
Installed this morning's release and I can happily report that Bluetooth is back. Battery seems better and much fewer data drops from 11/9 (the only build i used for it had the better bt)
[Verizon Samsung Galaxy S III] pschatz12:
Bluetooth audio? I never had a problem with any Bluetooth except tinny bass
[Verizon Samsung Galaxy S III] peaceofpi:
That was the major issue. That and the random clipping I would experience. And Apollo would freeze a lot.

But since this build all of that have been resolved.

There were people that this was bothering so I figured I would share.
[Verizon Samsung Galaxy S III] pschatz12:
So your saying Bluetooth audio does not sound tinny in the newest nightly?
[Verizon Samsung Galaxy S III] TechSavvy2:
Its still tiny, I was using it this morning.
[Verizon Samsung Galaxy S III] EGill42:
So I am one of those people having the black screens and needing to hit the power button to get it back, GPS problems, and echo problems still. Not long ago I used ODIN to revert back to a stock rooted rom. When I did this the echo was gone, and the GPS worked on the stock rom. After that I installed CM10, and I went right back to having the same problems. I have been using CM10 since the kexe days, could this be part of the problem?

Does anyone have any other methods that might be viable to get everything working? And to all those who think those of us are ungrateful for CM10, I highly doubt that is the case. These forums are full of people willing to help, and we are just looking to get the same great experience those of you without problems are having. These forums have helped me get much more out of my phone that I would have otherwise.
[Verizon Samsung Galaxy S III] peaceofpi:
It's not "holy bass" but it's there. Also doesn't distort as badly. And the clipping has ceased.

I wish the DSP manager worked. When it did it was awesome.