yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Travisimo:
Regarding "newbs" vs "experienced crackers":

I am neither a newb nor a pro, but I do have something to say. No matter how many times you guys repeat it, I am not going to do a clean install every night. But know too that I am not going to simply complain about issues after doing a dirty flash. We have two extremes here that can be reconciled by some common sense:

1) If you are doing "dirty flashes" of these nightly builds (and I think it's perfectly reasonable to do so), then you should spend some time testing your phone before posting problems. Sometimes issues that occur immediately after a dirty flash are corrected after the phone settles or after a reboot. Also makes sure you have followed the steps correctly; that you have indeed cleared both the cache and dalvik cache, and tried a few basic troubleshooting tips like fixing permissions, rebooting, checking your settings, etc. Also make sure you troubleshoot using the stock cm10 kernel since flashing a custom kernel can cause problems that are unique to that flash.

2) Once you have done that and still encounter problems, I think it's perfectly reasonable to post your experience after a "dirty flash", makings ure to note that you have dirty flashed. Without complaining and asking why something isn't fixed, it seems reasonable to place a feeler out there for others who have dirty flashed. If no one else is experiencing the issue, then you'll be advised to do a clean flash. If everyone is experiencing the issue, then we can bounce off of each other to see if it's cleared up by doing a clean flash.

I realize there are purists who will not accept anything other than a clean flash every time. And while that's fine for you, I don't think it's fair to expect everyone to do this every night (or every time they flash). I *do* think it's fair to ask those who dirty flash to try a clean flash before complaining about issues and problems. But I don't think that means they shouldn't post at all before trying a clean flash; I think posting experiences after a dirty flash are perfectly reasonable as long as they are qualified and cordial.

As always, this is my opinion on the matter and not the last word. :cowboy:
[Verizon Samsung Galaxy S III] Zalithian:
I think this post is reasonable, but I think there's something even more important to consider.

Nightly builds are test builds. Their whole purpose is essentially to find out what works/doesn't work. This is best accomplished by having people do a full wipe and test the new build to make sure nothing could have messed with it.

I think a big part of the problem is people go into these nightly builds without an actual testing mindset. Like, oh no NFC broke on my new nightly! When you gaiz gonna fix it? This of course does not mean that people shouldn't post what's wrong with the new nightly. They should, especially if they did a clean flash.

So, back to the main point.

NIGHTLY BUILDS ARE TEST BUILDS

If people want to test the nightly builds, great! More testers is always good, but if having something broken is going to be a big problem for you, go with something stable. Don't flash nightly builds. Wait until a stable milestone of JB comes out for the VZW S3.

To add something on topic, my IMEI/etc was all missing when I flashed 9/8. Rebooted and it was back, but I still had activation problems even after another full wipe. Phone number was wrong on initial boot again. Pretty common. After a couple reboots it's all working normally now, and I haven't noticed any bugs besides the volume before sound one?
[Verizon Samsung Galaxy S III] wctaylor79:
I thank you and I'm downloading. The reason the bot hasn't built yet is cause this is the cm9 weekly day. Once they clear the bot moves to cm10 . Still thank you for the early build.
[Verizon Samsung Galaxy S III] jmill75:
I can't believe you took the time to post all that....jeezzzzz

Anyway I believe you must do a fresh install every time to have a legit run with the OS.

Thread derailed enough. Back on topic :)
[Verizon Samsung Galaxy S III] cgulliver:
I built an unofficial today as well and have had zero issues so far. Are there any commits in there that would help with battery? Because I could swear it's better than 9/8. Haven't officially measured but getting ~3%/hr with moderate use. Running Imo 11 and yes I Dun... Dun... Dunnnn.... dirty flashed. : /
[Verizon Samsung Galaxy S III] trbman:
would the CRT mod listed below work? i flashed it on a previous synergy build and it caused me to hang on boot screen. don't wanna risk that again without asking first. plus i saw some folks who had asked in this thread previously but never received an answer.

http://xdaforums.com/showthread.php?t=1841802
[Verizon Samsung Galaxy S III] cgulliver:
States only for tw roms and specifically not CM so wouldn't do it.
[Verizon Samsung Galaxy S III] Ratzinc:
I've been flashing since the HTC Evo days and it's funny how many backseat mods or cm dev cheerleaders there are here. Clean flashes have never been considered the ONLY way to flash and post about bugs. It should be noted if there are bugs and through what type of flashing method you used, since it's a given you should be able to flash either way. The cm team has no hard rules about how you flash and post about bugs.
[Verizon Samsung Galaxy S III] jmill75:
But....with as many changes there could be on a lightly build, the only way to truly help squash bugs is with a clean slate. why should developers have to worry about what build you are running.
[Verizon Samsung Galaxy S III] kennyho35:
I agree somewhat...... that's fine but these people are getting on here and complaing about the bugs. They should at least first do a clean install and then post if there problem was resolved or not.

cyanogenly ported from a galaxy far...far....... away ;)
[Verizon Samsung Galaxy S III] trbman:
i was taking videos with my S3 today and the volume during playback was super low. after playing the video back twice, my screen went black and would not come back on. I've taken the battery out and tried to turn it back on but all it does is vibrate once quickly without turning back on. what can i do? i hope i didn't brick this thing

EDIT----

i panicked and fled to the forums before troubleshooting. turns out the battery died. it said 20% while i was using it and than it just turned off. after plugging it back in it was at 0%. not sure what may have happened.
[Verizon Samsung Galaxy S III] kennyho35:
Reboot recovery and wipe battery stats

cyanogenly ported from a galaxy far...far....... away ;)
[Verizon Samsung Galaxy S III] badseed767:
Correct. If we do get a build, it'll be late this evening. At that point, we may as well wait for tomorrow's nightly.
[Verizon Samsung Galaxy S III] trbman:
I was thinking that. Is it best to do it once the phone is fully charged or can I do it during the charge?

Sent from my Galaxy S3 using the XDA App
[Verizon Samsung Galaxy S III] alee:
Thx. Looks like d2vzw is next in line for a build as of right now.

Edit: Building now http://jenkins.cyanogenmod.com/job/android/7815/
[Verizon Samsung Galaxy S III] twolfekc:
Fully charged for sure
[Verizon Samsung Galaxy S III] wctaylor79:
Build is live and done on Jenkins.. :)
[Verizon Samsung Galaxy S III] kennyho35:
Just to clear this up did the 20120908 build lastnight have the ril code merge in it or not?

cyanogenly ported from a galaxy far...far....... away ;)
[Verizon Samsung Galaxy S III] wctaylor79:
Yes and the new one that just went live for download too...
[Verizon Samsung Galaxy S III] wera750:
The ril change wasn't for our device
[Verizon Samsung Galaxy S III] qqhorus:
So far been running 9/8 for a day and it's been absolutely awesome. Battery life is phenomenal and everything seems to be working.
[Verizon Samsung Galaxy S III] saintirish:
Question for the CM10 official nightly DZVZW for GS3. I am by no means a noob to flashing ROMs and such, but I am a noob when it comes to doing it using the ROM manager. I just wanted to verify that the nightly cyanogen build that I find on the ROM manager is the same as the DZVZW one that I find thru here?
[Verizon Samsung Galaxy S III] twolfekc:
Correct
[Verizon Samsung Galaxy S III] NeoMagus:
just flashed 9-10 coming from 9-5 , wiped cache/dalvik only , everything in status is fine , data/4g working no issues to report yet
[Verizon Samsung Galaxy S III] juancaperez2000:
hello, i just did a clean installation on last nightly and noticed a bug in activation proces by some reason is not working like in the past, also i read that a lot of ppl are suffering same issues, i just want to know if its bug on rom or phones are getting corrupted and need go back stock and then reflash?
[Verizon Samsung Galaxy S III] Recon0212:
What does 9/10 fix?
[Verizon Samsung Galaxy S III] NeoMagus:
Changelog
[Verizon Samsung Galaxy S III] trbman:
i just did a clean flash to 9/10. is your call volume super loud? even when i turn the call volume all the way down it's loud enough for anyone near me to here. practically speaker phone.

i had some issues activating as well. first time around, i got stuck at the activation screen. so i went back into recovery, wiped everything, reflashed one more time. after it booted up the second time, i skipped the activation screen by tapping on the four corners of the screen (start at top left and go clockwise). after that, it brought me to the home screen. i gave it a few minutes to activate and nothing happened. i thought i lost me IMEI. than i rebooted one last time and everything worked. give that a shot
[Verizon Samsung Galaxy S III] alee:
Been like that for a few builds now. If you use the screen slider you can get it to go a little quieter but it's definitely way louder than it should be.
[Verizon Samsung Galaxy S III] juancaperez2000:
thats how i make it work but is kind of weird, i never have this kind of issues in the past, i even running cm since kexec time
[Verizon Samsung Galaxy S III] Zalithian:
Yeah the activating/phone number thing is a little strange. Hopefully they'll get around to fixing it soon. I've had it on pretty much all of them and not on AOKP. I just flashed 9/10 which went smooth and no issues so far, but obviously it's brand new. :P.
[Verizon Samsung Galaxy S III] trbman:
are you sure? i had 9.8 earlier today and call volume seemed alright. i noticed something in the change log for 9.10 that mentioned audio too. i may have not realized it during 9.8 while on calls, but its so loud that its almost hard to overlook.
[Verizon Samsung Galaxy S III] alee:
9/10 nightly running smooth. Last 2 nightly installs seem to be a bit harder on the battery during the upgrade process. Between the ROM install and the reboot, I am losing about 10% of my battery for these activities. Going to reset my battery stats just in case something got thrown out of whack.

---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------

9/8 was also very loud. Have not made a call on 9/10 yet, but did a dozen or so calls on 9/8 and the volume was definitely blaring.
[Verizon Samsung Galaxy S III] NeoMagus:
just tried, it seems fine to me but I always have it at maximum anyway
[Verizon Samsung Galaxy S III] juancaperez2000:
agree with you just instal BMC aokp and no problems with that, like you said i hope the fix this tho, at least is not my phone lol
[Verizon Samsung Galaxy S III] evandena:
There is something seriously wrong with every single nightly thus far.

I've tried wiping 10 different ways from Tuesday, and I always get data drops. Every minute, my data will drop and take 20 seconds to reconnect.

I hope this gets addressed.
[Verizon Samsung Galaxy S III] yiannit:
Does anyone's led notification colors work besides blue
[Verizon Samsung Galaxy S III] Droosh:
Camera-MOD FYI

FYI- I've been wanting to try this camera mod for a while, but didn't want to go through all of the manual steps to make it work on our device. Fortunately someone put the fixes in a zip for us. I'm trying it now with the new nightly and LeanKernel v.11.

In case you want to give it a go:

http://rootzwiki.com/topic/33633-mod-aosp-camera-mod-for-jb/

Original Work is here on XDA:

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

Edit: Ok, I just tested it and it works perfectly!!!! IMHO this is a must have.
[Verizon Samsung Galaxy S III] trbman:
yeah i've tested out a bunch of colors in the menu. they all worked. my phone lights up for notifications, but not when its plugged in charging.
[Verizon Samsung Galaxy S III] neyenlives:
9-10 build camera is still broken, taking a picture turns phone off abruptly....this has been the case for me since the 9-8 build came out
[Verizon Samsung Galaxy S III] Droosh:
Try the mod I linked to two posts above yours. It's sweet. Hopefully Austen gets some of this goodness built into CM for us.
[Verizon Samsung Galaxy S III] asenduk:
Still getting slight random skipping/stutter from playing music using Apollo on the 9/10 build

Auto brightness also still borked

But everything else works
[Verizon Samsung Galaxy S III] NeoMagus:
camera is working fine for me on 9-10 doesn't reboot no data drops either

** originally started on 8-16 alpha clean. wiped cache/dalvik to 9-5, tonight wiped cache/dalvik to 9-10
[Verizon Samsung Galaxy S III] mwep:
Data Arrows

Anyone else seeing there send/receive arrows on WIFI and 3G/4G constantly showing ? Appears that data is constantly sending and receiving but looking at Data Usage under settings, nothing is out of whack.

This is on 09/10 nightlies with squeaky clean install. Also noticed this on 09/08. Its been settling in for a couple hours already and still wonky.
[Verizon Samsung Galaxy S III] TechSavvy2:
Yet you're the only person reporting this......and its on every single build you try......
[Verizon Samsung Galaxy S III] grin0048:
Yep, same here.
[Verizon Samsung Galaxy S III] mwep:
Anyone know what could cause it ? Perhaps an app ? Will try uninstalling tomorrow to see it that makes difference.

Update

---------

No deep sleep either... Tried Stock which only runs at 2 speeds and LeanKernel which runs multiple speeds but neither deep sleep. AC/USB is not plugged in.
[Verizon Samsung Galaxy S III] Nightwind Hawk:
Just out of curiosity (since I know nothing), does anybody have an *idea* when you *think* a stable build of CM10 will be released? Instead of nightlies?

I am trying to phrase this as cautious possible to avoid any angry responses! :P
[Verizon Samsung Galaxy S III] toddley:
I've also been wondering this. If you take a look at the version history of each, the quickest they've ever gone from release of android version to stable is cm is 4 months (gingerbread). Most of them are around 8 to 10 months though. I didn't go back all the way so someone correct me if I missed something. Jelly bean came out in July and they've said many changes were anticipated but I'd imagine we're looking at a couple more months at least for an official release. However a release candidate could be much sooner and they're usually more than adequate for daily use. I'm interested in more knowledgeable users' opinions
[Verizon Samsung Galaxy S III] kennyho35:
**** that suxks I was hoping to get rid of the 3g data issue ahhhhhhhhhh lol

cyanogenly ported from a galaxy far...far....... away ;)
[Verizon Samsung Galaxy S III] TechSavvy2:
We got a while still. Only thing that makes me hesitant about the answer is that many phones are much more up to date with fixes than our phone as how its so new(ly unlocked). I guess it basically depends on the status of other devices as a whole. They are probably much more stable than we are so who knows when a code-freeze gets implemented. One thing for sure, I guarentee you cvpcs is gonna freak when they announce the freeze. It basically means he has one week from then to fix all reported and known major bugs. Which for us is still significant.
[Verizon Samsung Galaxy S III] Droosh:
Not for quite a while. I wouldn't even hold my breath for a release candidate anytime soon. The CM team doesn't like to release these until the ROM is about as good as it is going to get on the majority of devices. Also worth noting that CM nightlies for popular devices like the Nexus and GS3 are usually more stable than most custom ROMs and even OEM's skinned ROMs.

What value does slapping the label "stable" really add? It doesn't mean it's any better than the "nightly" that was release just before it.

FWIW, the bugs in this are minimal enough that I recommend it over any TW ROM as a daily driver.
[Verizon Samsung Galaxy S III] kichard:
Is there any way to enable screen off animations in these nightlys? I miss it..
[Verizon Samsung Galaxy S III] xdstx:
Just clean installed 9/10, is anybody else's Google voice search not working? When I click the mic and talk, it will not recognize voice input.

Edit: apparently when I speak two inches away from the top of the phone it will recognize it. But when I speak towards the bottom of the phone with the mic it does not.
[Verizon Samsung Galaxy S III] loveubuntu:
SwiftKey 3 keyboard does not work, back to bean 11.
[Verizon Samsung Galaxy S III] nnnnr14:
I was going to flash this until I saw this

I got 99 problems but bamf ROMs ain't one! -nnnnr12

-tapped from my Galaxy s3
[Verizon Samsung Galaxy S III] droidxuser123:
I have more of an issue with people on custom kernels complaining about bugs

just my 2cents
[Verizon Samsung Galaxy S III] Travisimo:
There are definitely others reporting issues with data drops, though not "every minute". Up until a few nights ago, I hadn't been getting any data drops since the initial alpha builds of cm10 came out a long time ago. Now I get random drops where the signal bars go gray and there is no data connection. It has happened on 4G and 3G, whereas in the past I only had problems when in 3G areas. Anyway, sometimes the bars will turn back blue on their own but sometimes it takes an airplane mode toggle or a reboot to get it back. And yes, this was with both a dirty flash and after a clean flash. It's not every minute, by any means. And of course, when I'm on WIFI everything is fine. But when I leave my house, I do notice the drops, and it's not just when it's switching from 4G to 3G or visa-versa.
[Verizon Samsung Galaxy S III] salas2324:
Appears its using the Second Mic located at the top.

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] PerCompLLC:
Yup, camera freezes for me after several pics. Switching over to the AOSP camera posted by TheUnkn0wn which is just awesome...
[Verizon Samsung Galaxy S III] TheBiles:
Just dirty flashed 9/10, and NFL Mobile started magically working. I've got some logcats of starting it up in case it could help. Any idea who to send them to?

Edit: And it is not working after a reboot. Whatever causes data to start working again also breaks NFL Mobile.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] softwarestealer0:
My swift key works perfectly.. Like it's been said clean flash.
[Verizon Samsung Galaxy S III] deanrobbins:
Maybe someone can help me out. Haven't had any issues w/ various roms and used several CM10 nightlies starting at 8/29. I was on the 9/4 nightly last week at a conference. No wifi and the 4g/3g service was poor. No outlet and the phone needed to last all day. Figured I would save some battery by sitting on 3g all day versus 4g. I changed the notification screen toggles in the settings to include the LTE toggle. Hit the LTE toggle button to turn off 4g and the phone reverted to 3g without a problem.

The problem arose later. No 4g service at all. Normally I have full 4g bars everywhere I go. Haven’t seen it since I toggled off several days ago. Tried toggling it back on, obviously.

Reloaded the rom. Tried different nightlies. Tried different roms. Cleared cache/data wipe/dalvik every time. Now when I load a CM10 rom, I get the “Your Phone is Activating” screen until it eventually fails, even though I see 3g bars. Other roms work, but they’re only 3g. Before CM10 wouldn’t activate for me, I would get 3g bars (and the 3g notation) and could make calls no problem, but zero data unless I disabled mobile data and reenabled. Then I get 3g service until I reboot.

It’s weird. Have no idea what’s going on.

Last night I followed the Soft Brick sticky thread and reloaded everything to factory stock via ODIN. Still, no 4g though the 3g seems to work reliably now.

Any ideas on what could have happened or steps I need to take?

Additionally, tried nandroid restores, but both of my nandroid files were corrupted I guess. Now that I'm home and have a couple spare nandroid backups (with working 4g) on my computer that I could move to the phone and restore to. Would this fix the issues?
[Verizon Samsung Galaxy S III] kman79:
Is anyone else still having issues with GPS on the 9/10 build? I've had no GPS since the 9/6 build, just inquiring.
[Verizon Samsung Galaxy S III] trbman:
i couldn't get a lock last night at all. on other ROMs i've tried it has just taken some time. i'll probably try again today later when i'm out of class. i'll report back.
[Verizon Samsung Galaxy S III] cgulliver:
Working fine here.
[Verizon Samsung Galaxy S III] Version_3:
No he's not. I have the same issues. I just stopped trying nightlies because of it.

Right. Same here, except I've timed my drops and they happen exactly every 2 minutes - clean flashed different versions, and I also tried restoring what I thought was a good working version.
[Verizon Samsung Galaxy S III] Byonik:
Working for me as well, and I've dirty flashed the last 4 or 5 nightlies..
[Verizon Samsung Galaxy S III] ssmaster:
Are there any apps that log data drops? I've tried searching the market but the term makes it hard to search for.
[Verizon Samsung Galaxy S III] Byonik:
From what I've read elsewhere, it sounds like this issue is related to the same mic gain issue that is causing low volume in video recording.
[Verizon Samsung Galaxy S III] nohbdyshero:
Swiftkey is working on 9-9 for me

---------- Post added at 08:28 AM ---------- Previous post was at 08:24 AM ----------

9-9 gets a quick full lock for me on Maps and weather
[Verizon Samsung Galaxy S III] yiannit:
Hmm mine don't seem to work right. Blue is pretty much the only one spot on
[Verizon Samsung Galaxy S III] Version_3:
Logcat shows them, which I've attached to a previous post of mine.

I should note that on stock rooted, I have no data drops. On CM10 nightlies, I've tried both shipped modem and the OTA modem.
[Verizon Samsung Galaxy S III] trbman:
any chance of getting more toggles? thats one thing i miss from syngery. 15 toggles was nice.
[Verizon Samsung Galaxy S III] coldhardtruth:
I'm on a clean install of 9/8 & when I go to connect my phone to my laptop it says, "Hardware ID Missing".

Anyone know how to fix. Everything else works great on this build tho

Thanks!
[Verizon Samsung Galaxy S III] MichaelTheCrum:
Settings -system- notifications drawer
[Verizon Samsung Galaxy S III] minmongoblin:
Just did a clean install of 9/10. Anyone else getting "Activating, may take some time" message EVERY TIME you boot up? And it never seems to finish? I can hit Home and it doesn't seem to affect anything. My phone number is 000-000-(four random numbers) but people say my correct number comes up when I call/text. Just annoying to have that happen with every reboot.
[Verizon Samsung Galaxy S III] jsb5388:
Try changing CDMA subscription to ruim/sim and reboot your number should come back.
[Verizon Samsung Galaxy S III] AtLemacks:
Go to settings and change CDMA subscription from NV to RUIM.
[Verizon Samsung Galaxy S III] niv3d:
I have not been keeping up with CM10 very well. Have the data dropout issues been fixed yet?
[Verizon Samsung Galaxy S III] minmongoblin:
Thanks guys!
[Verizon Samsung Galaxy S III] vaffanculo403:
So far mine has been stable on the most recent one. 9/7 was a train wreck for me with the data drops...
[Verizon Samsung Galaxy S III] coldhardtruth:
Uninstalling, rebooting and reinstalling the Samsung drivers fixed it. Super pleasen!
[Verizon Samsung Galaxy S III] kls629:
did 9-10 fix the volume in the camcorder? the camcorder on 9-8 was working but the recorded volume recorder seems messed up