yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jdubau55:
Are you using an older SD card from a different phone? I had the same problem. I had to go through folder by folder on my ext SD card and find the files. It will show the same file if in a different location. I only have a few the same now. Like hangout sound and facebook sound.
[Verizon Samsung Galaxy S III] henrys01:
Wipe and try again. Maybe you have some crap running in the background or something.
[Verizon Samsung Galaxy S III] imablackhat:
Seeing how I'm not the only one scoring it... Should I really have to? This is a fresh clean install. Format system. Wipe data. Cache. Dalvik. Install. Install gapps. Reboot.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] imablackhat:
Sent from my SCH-I535
[Verizon Samsung Galaxy S III] evandena:
Just flashed 8/30, first rom on this phone. Still setting it up, and everything was looking good, and then I got a phone call. Sweet baby Jesus was it loud, with no way to turn it down. Volume slider was all the way down. Had to smash the earpiece into my cheek.

:(
[Verizon Samsung Galaxy S III] eMpTy43:
Did you happen to try turning it up then back down again? Sometimes the volume may be all the way up but slider showing down. Same loud volume on an outgoing call for you? Friend of mine and I will be testing during our lunch in another hour.
[Verizon Samsung Galaxy S III] evandena:
Good idea, I'll give that a try.

I'm also running into data drops while sitting at my desk. Signal strength is alright, but it will just drop 3g all together. It's doing it frequently, once a minute or so. Stays out for 5-15 seconds. Tried rebooting, airplane, etc.
[Verizon Samsung Galaxy S III] Version_3:
Not a fix, but I've attempted to document the signal drops a bit better. It's on the previous page, but probably overlooked by all the posts regarding benchmarks.

http://xdaforums.com/showpost.php?p=30959676&postcount=1345
[Verizon Samsung Galaxy S III] Lastb0isct:
I had this issue the other day as well on the 8/29 release and noticed that I was able to fix it by turning the screen off/on and then adjusting the volume...weird issue, I know.
[Verizon Samsung Galaxy S III] Hilbe:
NFC looks working in xoomdev's new build...

http://blamexoomdev.com/?p=61
[Verizon Samsung Galaxy S III] eMpTy43:
Can't really comment myself on the data because I get such horrid signal in my office I just turn my data off altogether lol, during lunch (now) I'm going to turn stuff on and play so I'll post in a bit.
[Verizon Samsung Galaxy S III] alee:
Yes, but the change he posted does not appear to apply to CM10. I relocated the same lib and does not make any difference. There must be more going on in AOKP to get it working that CM10 doesn't have just yet.
[Verizon Samsung Galaxy S III] yznhmr:
Still having ECHO on Build 31, dirty flashed from 30..

30 was a clean install (wiped data and such)
[Verizon Samsung Galaxy S III] Hapex:
Anyone run into this issue? I think it may be a bug. I've attached my device to the company exchange server. No matter what I do it will not vibrate when I get a new email. I can get it to do different notifying sounds, but will not vibrate. Does the same with text messages.

I'm using the 8/31 nightly.
[Verizon Samsung Galaxy S III] henrys01:
CPU settings? My CPU score is a lot higher. Mines set to ONDEMAND, min:384 max:1512.
[Verizon Samsung Galaxy S III] WhammyDroid:
I know for a fact my music/mp3s only exist on one folder on my external SD card. I do not know why both winamp and apollo are showing duplicates. I also validated I do not have duplicate ringtones/notifications between the internal and external SD cards.
[Verizon Samsung Galaxy S III] Lastb0isct:
I've come to realize that most benchmarking software isn't that accurate. Stock I was seeing ~62XX score. Now w CM10 i'm getting 88XX?! That's a massive difference for no real reason other than software changes!
[Verizon Samsung Galaxy S III] softwarestealer0:
Is anyone else having issues with the camera on 8/31 I take a pic and it locks up as soon as it floats to the right.
[Verizon Samsung Galaxy S III] alee:
Yep it's a bug.

For now, download Sound Manager v2 (https://play.google.com/store/apps/details?id=com.roozen.SoundManagerv2). Hit menu, go to Vibrate Settings, and select "Vibrate Whenever Possible" for notifications.

Note that these settings will NOT survive a reboot (normally they would), so you have to do it on every fresh boot.
[Verizon Samsung Galaxy S III] schmaltzy:
Agree with that!

I can't post the articles or posts because it was a long time ago, but I've read that benchmark scores don't always communicate the true nature of how the phone is performing. It can be a good, simple judge of how your phone scores against other hardware, but I think that's about it. Whether you're scoring in the 8000's or the 6000's, just go off of how your phone is acting during your daily usage.

I myself scored just shy of 8000 with Antutu, but I only ran it to see how it compares to other devices.

Just some food for thought!
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Anyone else notice that when someone calls you after you answer it takes like 3 seconds for the other person to hear you
[Verizon Samsung Galaxy S III] Lastb0isct:
Has anyone noticed that UMS is inoperable on the latest build 8/31? I've never had the capability but in the 8/29 build it says that it is now included. Does anyone know where I go to turn this feature on? I loved the ability to have USB Media Storage as my connection setting on my Droid 2...
[Verizon Samsung Galaxy S III] psufan5:
YES!! I thought it was just me.
[Verizon Samsung Galaxy S III] manny108:
I just noticed that too.. I thought I was going crazy or something..
[Verizon Samsung Galaxy S III] schmaltzy:
Has anyone noticed that everyone keeps asking if "anyone has noticed"? I did notice that!
[Verizon Samsung Galaxy S III] eMpTy43:
Been playing around for an hour with data and then hooked up to WiFi, no drops on either signal.

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] jb_alphamale:
Same question here.
[Verizon Samsung Galaxy S III] psufan5:
I NOTICED!
[Verizon Samsung Galaxy S III] JCSIII:
Can somebody point me in the direction where I can find a way to get rid of these damn text messages? Lol
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
anyone notice how there is always a funny guy
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Is it the VZWsomething 001 texts that keep popping up from time to time? If so login to your my verizon page, an unsubscribe from the contact assistant. I had the same problem, an that was what it was
[Verizon Samsung Galaxy S III] JCSIII:
Yeah that's it.Thanks sir
[Verizon Samsung Galaxy S III] shadowwolfy:
anyone else having issues using the Tango app for video calls? It has me permanently flipped upside down regardless of screen rotation etc.
[Verizon Samsung Galaxy S III] wera750:
Contacts will stay aosp as is all cm10 Rom's.

Once again, Samsung keyboard isn't aosp. I would suggest downloading Swype. The newest beta works awesome and it gets themed with theme manager.

S-beam isn't aosp either. Use nfc (once it gets fixed). It works really well, normally.

S voice? Really? Try Google now. You will forget s voice ever existed.

I in no way speak for cm10 or cvpcs. I'm just speaking from experience with cm.

sent from locked bootloadrer SGS3 running a custom kernel :)
[Verizon Samsung Galaxy S III] wctaylor79:
Good news for the nightly followers.. Mms fix is merged. Next build should have in it..
[Verizon Samsung Galaxy S III] neyenlives:
This thread was in the regular Dev section originally and was moved here by the mods. I don't care where it is but this type of discussion is not only out of scope it is off topic for this thread. Please keep discussions relevant. This isn't a thread to complain about forum devs or a thread to complain about why [Insert App of Choice] doesn't work on CM10 Official Nightlies. This thread was simply taking what was made public by Cyanogenmod on G+ and making it available here on xda in a place where HOPEFULLY we can focus on how THIS ROM is running, what works, what doesn't, as far as the ROM is concerned.
[Verizon Samsung Galaxy S III] neyenlives:
I find it distracting and confusing for you to be making comments about how wonderful feature A or B works on a build that has it's own thread already. Take Alpha discussion to the Alpha thread. If you want to come to the Official ROM thread to tell someone how great a feature works in the Unofficial Alpha ROM, please send them a PM and kindly tell them where the Alpha Unofficial thread is.

It confuses people when you say "NFC works great on the alpha" when this thread has nothing to do with the alpha. People don't even read the entire OP here. They certainly aren't going to try to take into account you are talking about a completely different ROM.......so they get confused.

Try to be a part of the solution, not a part of the problem. No matter how you justify your off topic posts, they are off topic. Please be cool and avoid cluttering up the thread over your personal opinions of who what and where.
[Verizon Samsung Galaxy S III] Droosh:
Or just follow the clear directions of our official CM dev and use his Alpha 2 until the commit that fixes the problem gets merged and the new nightly is auto built and pushed out.

This is rather exasperating. Despite what the OP requests, I request that we follow Austen's (the actual CM rep) instructions since his build is the same, but with the commit already merged. This will keep us all on the same page and stop most of the noise. Why would anyone want to do otherwise? In a day or two this will be a non-issue.

Neyenlives, it's not like CVPS's build is a different ROM or a derivative Kang. I respectfully request that you don't dictate what we discuss when many of us consider this completely relevant to the "official" discussion. Hopefully it will be moot tomorrow.
[Verizon Samsung Galaxy S III] ka1z0ku:
Anyone running the latest nightly experiencing low signal strength, data drops, or slow mobile download speeds? My SGS3 is getting much worse reception /speed than my Moto RAZR ever since I installed CM10.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Yea I noticed that too..
[Verizon Samsung Galaxy S III] neyenlives:
The instructions in the OP work fine. If you want to run the Official Nightlies, follow the directions in the OP and MMS will work fine. If you want to run the Alpha build (like I am) from CVPCS (Austen) fine. But please take those discussions to the thread that has already been created for it as plainly explained in the OP.

If you are running the unofficial rom, keep the discussion in the unofficial thread. If you are running the official rom, keep the discussion in the official thread. That is as cut and dry as it gets. No confusion.

I understand, but many people that are coming here don't get all that. They don't understand the difference. That's why I updated the OP. In order to not confuse people it's best to keep separate threads for separate builds. If you come in this thread and start talking about how great a certain feature works in the alpha, you have created an entirely different discussion for the person who doesn't know the difference. Then someone comes along and reads your post and thinks you are talking about the official nightly....when you aren't. . .....I don't know why you can't just keep them separate.

cvpcs' build, and all the other unofficial alpha builds, are all pulling from the same code, but they are able to add in their own stuff as they see fit. Official Nightlies don't get that cherry picking action. That's the difference. As time goes on the official and unofficial builds can take very different paths.

Otherwise why don't we just have one giant thread with every AOSP based rom in it. AOKP, Paranoid Android, all alpha builds and all official nightlies.....because after all they are all Kangs of the same code......so to use your reasoning they should all be in the same thread.
[Verizon Samsung Galaxy S III] drbveb88:
Anybody using imo's kernel? I am running beta version .6 and everything is running really smooth and battery life seems to be better:thumbup:
[Verizon Samsung Galaxy S III] jdhas:
Yup. Loving Imo's work. Didn't realize v.6 was out. Thanks for the head's up!
[Verizon Samsung Galaxy S III] Droosh:
I wasn't even aware that you changed your OP based upon my post #30.

I do think that this debate is getting silly and I'm done posting until the commit is merged and you and I are on that nightly.
[Verizon Samsung Galaxy S III] TheBiles:
I'm using Sammy's kernel in the AT&T forum. It's pretty awesome. Great battery life, and I've only had one hot boot since switching.

Sent from my Nexus 7

---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------

Issue with first post: TWRP works perfectly. No idea why you can't get data wipe to work, but my external SD has been detected from day one. You shouldn't be spouting misinformation based on your personal opinion to other users.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] neyenlives:
Data wipe not working in TWRP has been confirmed by many people in IRC (irc.freenode.net #verizons3) as has not being able to access internal sd. That's got nothing to do with "spouting misinformation based on personal opinion". We have a dev actually working on the bugs. Come be a part of the solution and please keep the attitude out of the thread, thanks.
[Verizon Samsung Galaxy S III] TechSavvy2:
Okay, first - I've never mentioned NFC, I don't use it or care about it at all. Second, I agree with you about app posts except I stated the comment about Netflix because its not specific to Netflix, rather it is a cm10 "official" issue that is specific to ALL video playback. It effects everything, HBO, Netflix, hulu, cinemax, etc etc.
[Verizon Samsung Galaxy S III] neyenlives:
The NFC comment was an example, not a specific thing. Thanks for helping keep things on track.
[Verizon Samsung Galaxy S III] JFMFT:
8/19 build seems to break more than it fixes. going back to 8/17 build and trying imo's kernel.
[Verizon Samsung Galaxy S III] hopesrequiem:
Stop all this bs arguing guys. How does the new version run is all we want to know. Take your egos elsewhere. The op is right so just let it go jesus
[Verizon Samsung Galaxy S III] rossguy:
8/19 official isn't out yet. Unless you know something I don't?
[Verizon Samsung Galaxy S III] TechSavvy2:
This. Where did you find an 8/19?
[Verizon Samsung Galaxy S III] lxetuo:
Built from source about an hour back because I'm a crack flasher :) If anyone else is interested, here's the latest CM10 unofficial build. Unofficial as in the nightly CM bot didn't build it. Otherwise it's the same code-base as the nightlies.

CM10 unofficial build (3:18pm EST): http://dl.dropbox.com/u/5059462/cm-10-20120831-UNOFFICIAL-d2vzw.zip

MD5: 4c2aa96272836a4043f323177de7f541

So far running fine but it's only been a few hours. If posting "unofficial" builds is not appropriate, please let me know.
[Verizon Samsung Galaxy S III] imablackhat:
Disabling the hardware thing in developer options to make the screen not flicker. Anyone noticing they have to reclick it in as in its not saving.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] lxetuo:
It's not saving between reboots so if you mean that, then yes, have to re-check it.
[Verizon Samsung Galaxy S III] ExodusC:
I noticed this as well.

While checking that option does fix screen flicker, it noticeably degrades UI smoothness.

I could easily tell when pulling down my notification bar with the option unchecked that is was perfectly smooth- but with the option checked, it was quite a bit more "janky" as Google puts it- it was more akin to what you see on ICS, rather than a fluid, 60FPS, triple-buffered result.
[Verizon Samsung Galaxy S III] imablackhat:
I don't notice any difference of buttery smoothness. Stock cm kernel.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] lxetuo:
Haven't noticed the jerkiness with having 'Disable HW overlays' checked but maybe I wasn't attentive enough. Right now I have it unchecked and am not really noticing any screen flicker.
[Verizon Samsung Galaxy S III] boynamedstacy:
Dammit! You ruined it for me. Now that's all I notice! LOL

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Breezer23:
Others have reported it as well but adjusting the in call volume doesn't work. I'm on 8/31 and partially deaf.
[Verizon Samsung Galaxy S III] XDAholic:
[BEGIN SARCASM]The 3-5 sec voice delay on incoming calls was a pleasant surprise.[END SARCASM]

(Transcript of first in coming call on 8/31 Build)

hello!..:banghead:..Hello!...:banghead:...HELLO!:banghead:.. God Damn this POS phone and all its ****ing bugs. FU Samsung. FU Verizon....... OH! Hi Mrs.Grippo!:eek:.. No mam, I was talking to myself..:confused:

Literally how my 1st incoming call happened.

P.S. Mrs. Grippo is my sons soon to be 2nd grade teacher.......
[Verizon Samsung Galaxy S III] codyvance:
LMAO at this...
[Verizon Samsung Galaxy S III] softwarestealer0:
Does anyone have the gallery apk fix that syncs with picasa?
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
So is the latest k747 kernel not playing nice with the latest nightly?
[Verizon Samsung Galaxy S III] dlsolo:
By the power of searching google.com, I was able to quickly find this -- > http://xdaforums.com/showthread.php?t=1851259

....the power of searching....
[Verizon Samsung Galaxy S III] alee:
Bunch of NFC related work coming in the next nightly:

http://cm10log.appspot.com/?device=d2vzw

Could just be foundation work, or if we're lucky, we could have NFC this weekend.
[Verizon Samsung Galaxy S III] eMpTy43:
Snapped a few pics today and didn't have this issue...
[Verizon Samsung Galaxy S III] softwarestealer0:
Ya thats not how it should be. You shouldn't need duplicate gallery apps. It should sync to the JB one.
[Verizon Samsung Galaxy S III] eMpTy43:
Let me google that for you...

I will donate $$ if I get to buy stuff with my phone/NFC this weekend! Awesome feature!
[Verizon Samsung Galaxy S III] cd2573:
I'm on 8/31 and have 16gb left of storage but phone wont let me download or update says not enough space left any ideas how to fix?
[Verizon Samsung Galaxy S III] Breezer23:
Maybe you should have left it stock lol
[Verizon Samsung Galaxy S III] awmobjects:
I was having issues so I removed it
[Verizon Samsung Galaxy S III] eMpTy43:
What do you mean by "download" and "update"? Are you trying to download a file from the web or enter download mode for Odin? Are you trying to update an app or install an update.zip in recovery?
[Verizon Samsung Galaxy S III] cd2573:
just normal updating a file and say insufficient space but I have 17gb left
[Verizon Samsung Galaxy S III] eMpTy43:
Did you try wiping cache/dalvik already? If so, try pulling your battery, removing the SD card, booting up, then again pull the battery and re-install the SD card and boot up again. Assuming you are trying to write to an external SD ;) If you are trying to write to the internal SD then outside of a cache/dalvik wipe you may have to do a factory reset, format /system and re-install 8/31.

Personally I've copied, renamed, edited, and even Bluetooth transferred files on 8/31 so far today.
[Verizon Samsung Galaxy S III] cd2573:
thanks looks like im going to have to
[Verizon Samsung Galaxy S III] codyvance:
New kt747 kernel is up :good:
[Verizon Samsung Galaxy S III] evandena:
Question to you guys...

I'm new to using Cyanogen, as well as anything on a nightly release schedule. I'm well aware of the bleeding edge, and fully expect a good amount of bugs.

That being said, are obvious bugs, such as volume and delay while in calls, usually fixed in the next nightly, or do can they sometimes take days/weeks to get worked out?

Just curious if I can stick it out or of I should move to a more stable ROM while this fully bakes.

Thanks!
[Verizon Samsung Galaxy S III] ponyboy82:
Some stuff can take a while, it just depends. If there's a deal breaker issue for you it may be best to go with a stock based rom until it's fixed
[Verizon Samsung Galaxy S III] jgrimberg1979:
honestly, i am running aokp and i love it, but has made my phone very unreliable at times. Sometimes i cant hear people when they call and i pick up or call echo(not so much any more) and other things that really drive me nuts, but like i said i love aokp. Anyways it will take a while to get eveything sorted out. JB is still very new...
[Verizon Samsung Galaxy S III] imablackhat:
Anyone else's auto brightness not working. It worked on stock ICS.. stock cm kernel here.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Mystikalrush:
Is there a way to fix the alarm clock? Doesn't seem to want to play a ring tone, just vibrate.

Also noticed 9/1 is up, but I guess its still in the process of being uploaded since I cant download it.
[Verizon Samsung Galaxy S III] eMpTy43:
I feel like major issues are addressed promptly, take the call echo issue on the 8-29/30 nightlies for example... that was addressed same day and next day. Now for a less important feature like NFC, some have been griping about it since d2vzw nightlies started dropping and we're just now seeing development 14 days in.

To simply answer your question... I use nightlies on my phone everyday and don't worry about it. For me, it's a stable daily driver, but it is all determined by what you use your phone for. Make a Nandroid backup and try it out... worst thing hat happens is you restore and carry on with life :P

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)

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

I flashed up the 8-31 nightly this morning (was previously on 8-27), auto-brightness works for me if I move environments with the screen on and when turning it out from my pocket... seems to be functioning normally for me now.

My alarm vibrate and ring tones have been working on 8-27 and 8-31 all along. 9/1 is up but still named 8/31, strange... getting a 404 error though, hopefully September unveils NFC functionality! :angel:
[Verizon Samsung Galaxy S III] jgrimberg1979:
What happened to the change log? Half the time it says no changes?
[Verizon Samsung Galaxy S III] alee:
Pulled the most recent build off of Jenkins. NFC confirmed working.
[Verizon Samsung Galaxy S III] eMpTy43:
Flashing and headed to store! lol :rolleyes:

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] elude79:
Google Market & Group Text issue

Hi all,

My 1st time on this ROM and so far is nice and i can edit on Column n Row .. Love it.

Problem for me: ( I seen it somewhere and i can't seem to find it now )

No Google Market ( Needed )

No Group text ( Needed ) - Pic Text work without any problem .. but Group Text sent but not in the group.

Since I'm new to this ROM and seen lots of people on it. Can you guys please help me with above apps. ( a link to where would do it. )

Thanks... very much appreciate it.

Happy Friday All....
[Verizon Samsung Galaxy S III] Mystikalrush:
Hmm, very strange, i did a fresh install of 31, not sure why alarms dont work, even when selecting to pick which one i want - no sound. All other sounds are fine.
[Verizon Samsung Galaxy S III] jgrimberg1979:
Who is this jenkins you speak off and where can i find him>?
[Verizon Samsung Galaxy S III] Ratzinc:
New version is better than last one however battery life went down like crazy with small amount of use and playing podcast.
[Verizon Samsung Galaxy S III] codyvance:
Jenkins is the build bot for cyanogen
[Verizon Samsung Galaxy S III] eMpTy43:
You need to install Google Apps separately... not sure if that will fix your group text request or not though.

Would you mind posting a link? Don't have it in my phone favorites and away from the computer now...

Did you flash on battery? Even a reboot will suck up 5% of your battery. A flash is going to drain considerable juice as the processor cranks to install the update...

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)