yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] zxsix:
Clear cache on the maps app.
[Verizon Samsung Galaxy S III] TechSavvy2:
I think you should go ahead and flash it yourself and nandroid back if you're not happy with the results.
[Verizon Samsung Galaxy S III] dmbfan13:
Just flashed M1, says I have 3G, however I still cant seem to access the internet. Upon first boot, I wasnt able to get anything. So I restarted and like I said, it said I had 3G, but I cant access the internet.

hmm.....

UPDATE: Interesting...I was on 3G only, so I switched it to LTE / CDMA / EvDo, and everything works now...
[Verizon Samsung Galaxy S III] ynotbike:
This is driving me crazy, clean installs of 10 and 11.

Volume for media will be silent unless I hit volume up or down, netflix, music, web, anything. If I exit the app and go into another app with media I have to do it again.

In past comments I have only seen complaints about call volume so did I some how do something strange in my flash to cause this?
[Verizon Samsung Galaxy S III] EpicMangina:
Just throwing this out there

It seems that a lot of people are bit**ing in this thread, and then say, "that's why i'm not flashing from stock until .....". Please stop... this thread is supposed to be for people who have TRIED the builds to collaborate and report, not for people to just jump in and give their opinions that don't help anyone. I am no means an expert, nor am I an "OG" here, but I do have common sense and courtesy. Also, please don't bother posting issues if you did not clean flash. A dirty flash is KNOWN to cause issues in some cases... This just exasperates people.
[Verizon Samsung Galaxy S III] toddley:
Disagree. Lots of people are dirty flashing and their experiences are relevant and helpful to others who are doing the same. For instance I just dirty flashes M1 with no issues. It runs great. Just like I've been dirty flashing nightlies for 3 weeks with minimal issues.
[Verizon Samsung Galaxy S III] hopesrequiem:
To piggy back on this. Don't post about a build from a few days ago either. No one cares at this point. Its time to update. For the record, m1 is working great still. It seems flawless
[Verizon Samsung Galaxy S III] Zacharybinx34:
Are there any known real problems with M1?
[Verizon Samsung Galaxy S III] mustbepbs:
Yeah but it's not helpful to anyone but dirty flashers. We're not here to report bugs from incorrectly installing this ROM. We're here to follow the rules and report the bugs that are legitimate, not from user error. Just because you have no issues dirty flashing doesn't mean they don't exist. This thread is full of people having issues from dirty flashes.
[Verizon Samsung Galaxy S III] evertec:
I have had similar issued happen before when dirty flashing new roms and all I had to do to fix it is uninstall google maps and reinstall from the market.
[Verizon Samsung Galaxy S III] AlexDeGruven:
I think the dirty vs clean flash thing needs to be clarified. I can see importance for both.

I would word it: If an issue arises after a dirty flash, do a clean flash before reporting the issue so we can see both sides of it

That way, devs get details both on the fact that something is interacting poorly with the existing build pre-flash, and they know it resolves/doesn't manifest when done cleanly.
[Verizon Samsung Galaxy S III] EpicMangina:
yes, I agree. But there is a time and a place. I have done many dirty flashes of CM10 as well, but I never post about it here. If you are dirty flashing, the rest of have no idea where the issue originated from.... At that point it could have been caused by multiple things, and it does nothing but fill up THIS thread with irrelevant talk and posts. If its needed, just start a new thread titled "dirty flashing CM10" or something... It would sure help the rest of us who are clean flashing.

---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------

This i can agree with... Please only post after trying a clean flash as well.
[Verizon Samsung Galaxy S III] Travisimo:
I know this has been mentioned before, but for those of you getting the voice problems in GPS Navigation (where she repeats the same directions over and over), all you need to do is go into App Info for Maps, Force Close it and then clear data (just clearing cache didn't work for me every time). When you reopen the app, it'll say it "upgraded" and then the voice should work properly again. The only "data" you'll need to re-enter is your home address if you want to Navigate Home.

This has happened to me after a couple of builds, but not every time...
[Verizon Samsung Galaxy S III] toddley:
True I agree. Clean flash should certainly be first troubleshooting step before even posting here
[Verizon Samsung Galaxy S III] trbman:
any chance we could get the feature to record phone calls?
[Verizon Samsung Galaxy S III] EpicMangina:
I know there are some in the Play store, but i have not tested it. I think that this would be a sweet integration into CM10 as well though! But I also understand that the Devs got their hands packed full, so I am not expecting this one. :)

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

I'm running smooth still. just clean flashed. I got one random reboot when first powering on, (right before i could hit the next button to setup). 4G seems a bar or two better for me, but that could be anything from the wind outside. No 3G areas around here so I cant test that. Still great download speeds.

As for real issues, just follow this Doc. Or use the BBQ
[Verizon Samsung Galaxy S III] jdommer:
It should be, but if people keep coming down on the dirty flashers, they'll just keep posting here only they won't confess to having dirty flashed.

It's better that if they're going to post problems at least they stay honest about that... at least simpler for troubleshooting.

Personally, as a clean flasher, I just mostly ignore the posts about problems from a dirty flash. Sure, I have to read more, but I'd rather deal with that than attempts to cover it up.
[Verizon Samsung Galaxy S III] ballpoint:
clean flash 6 am been good all day :good:
[Verizon Samsung Galaxy S III] alexcolodner:
I have been dirty flashing nighties every few days since 8/24 build and have had no real issues other than issues know to particular builds (in which case I restore my backup and wait for the next build). I am sure I am just getting lucky but I don't think comments should be dismissed just because people have dirty flashed. Their issues could still be relevant (not mine, because I have a superS3 apparently!).

Edit:

I do however wipe cache and dalvik as well as fix permissions after each flash. Not doing so has lead me into some issues. Also, rebooting after initial boot is a must for me in order to fix no-data issues.
[Verizon Samsung Galaxy S III] codyvance:
I really don't understand the confusion here with clean/dirty flashes. It has been expressed many times, if you dirty flash, and have an issue, don't post about it until you clean flash and try to resolve yourself. I myself really don't care about how the ROM runs or issues it has if you dirty flashed, as I'm sure other feel the same.

My .02
[Verizon Samsung Galaxy S III] AlexDeGruven:
I'm interested in performance after dirty flashes, as this is the way most of us will be doing it once things stabilize.
[Verizon Samsung Galaxy S III] Seirÿu:
9/11 m-series clean flash having data issues. First flash for me i've experienced real data issues. there's hours at a time that the data won't reconnect. Wifi works fine though, it's just when i turn off wifi, I can't confirm I'm having a 4g problem although there was a few minutes i had greyed out 4g and data just wouldn't connect... In my office I rarely ever get 4g anyway so that's probably the reason for that. I'm going to try to reflash it and see how it goes... just found it odd, especially since there seemed to be a lot of people saying a lot of their data issues were resolved in this build.

If i'm still having issues I'm going to give the 9.11 nightly a try and see how that goes. I'm currently under the impression they are the same however??
[Verizon Samsung Galaxy S III] neyenlives:
Define dirty. Earlier in this very thread I mentioned my camera was locking up the phone. That was on the 9-8 and since. On 9-10 I decided to wipe just cache and Dalvik cache and reflashed the rom, and all of a sudden it works fine.

Honestly I have to agree with not reporting issues until a clean flash has occurred. Even though I routinely dirty flash (wiping nothing), I have since started wiping cache and Dalvik based on this.
[Verizon Samsung Galaxy S III] mustbepbs:
Dirty flashing to me has always been not wiping data/system, just cache and dalvik.
[Verizon Samsung Galaxy S III] AlexDeGruven:
Once we start approaching stability, most people are going to flash with nothing more than a cache and dalvik wipe. I would still consider that a dirty flash, as it leaves everything in /data intact.

In the early testing phases, stuff in /data can cause real problems with the rest of the system as libs and modules are changing rapidly. Once things settle down, this is not so much of an issue (hence why OTAs are able to be released while preserving /data).
[Verizon Samsung Galaxy S III] sullivan1985:
Clean flashed 9/11 build shows me connected to 3G/4G but some times I will randomly loose data (but icons still show connected). GPS is still shaky too.

Just about everything else seemed OK.

Currently back on the 9/8 build. While it has 3G drops, data is still more stable than 9/11.
[Verizon Samsung Galaxy S III] Byonik:
Basically, you should always attempt to troubleshoot problems yourself before reporting an issue. If I dirty flash and encounter a critical issue, then I either do a clean flash, or I restore a Nandroid backup (depending on what my schedule will allow for).

I agree that reporting issues without first attempting a clean flash is a bad practice and clogs up the thread. That said, I almost always try a dirty flash first, so I am interested in whether a clean flash resolved a particular issue that was initially present after a dirty flash.

I think it's reasonable to post about an issue that was resolved after a clean flash.
[Verizon Samsung Galaxy S III] codyvance:
Said perfectly!
[Verizon Samsung Galaxy S III] Brian Gove:
What a ****. He was just asking a simple question from anyone who had already flashed. It took you more effort to type that than it wouldve to answer the question, or not if you didn't feel like it.

This thread is full of petty bs and it's rediculous.
[Verizon Samsung Galaxy S III] Byonik:
And FWIW, the audio level on video recordings is still very low.
[Verizon Samsung Galaxy S III] Aali1011:
I would like if at all possible to see the original post updated with what is a clean install and what is a dirty install.And please feel free to chime in and correct anything i say as wrong otherwise please use this as a reference.

Clean:

Clean Install 1) Wipe Cache, Wipe Dalvik Cache & Wipe Data/Factory Reset. Install latest nightly & GAPPS

Clean Install 2) Wipe Cache, Wipe Dalvik Cache. Install latest nightly & GAPPS

Clean Install 2 is known forum wide as the most proper way to install a new rom & kernel or new nightly. It can be argued though for the sake of the nightlies that Clean Install 2) isn't required and that Clean Install 1) will suffice. Clean Install 2) is known to be used during major rom changes I.E Touchwiz to AOSP or CM9 to CM10 etc etc...

Dirty:

Dirty Install) Wipe nothing. Install latest nightly & GAPPS

Dirty Installs are taken as common knowledge forum wide as an IMPROPER INSTALL

This subject is getting beat to death and needs not be covered anymore or identified.

If you are having issues and did...

Clean Install 2 and have issues, then there is some sort of issue.

Clean Install 1 and have issues, try Clean Install 2 If the issue still persists after trying Clean Install 2 then there is a issue.

Dirty Install and have issues try Clean Install 1. If issues still persist try Clean Install 2. If issues persist, then there is a issue.

If Dirty Installs are working for you without a hitch then all the more power to you. BUT if and when something does go wrong before reporting said issue try either Clean Install 1 and or Clean Install 2

To further support this argument:

From a recognized forum developer and contributor to our platform
[Verizon Samsung Galaxy S III] jmaiman:
Please fix the initial data drop issue
[Verizon Samsung Galaxy S III] WhammyDroid:
Has anyone done this to fix their GPS issues?

http://xdaforums.com/showthread.php?t=1880411
[Verizon Samsung Galaxy S III] salas2324:
Also, you SHOULDNT send bug reports if you are over clocked or messed around in the performance settings, yet most of the people that complain about dirty flashes do that.

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] iofthestorm:
Right, you shouldn't ever post bug reports if you're overclocked or running a different kernel, but that's already been stated 1000x in this thread. Honestly, I think a new thread should be started with baseline steps to follow before submitting a bug report like I outlined, and any posts that don't follow that should just be deleted. Look at the bootloader unlock thread, that thread is pure 100% development, and that's because of strong moderation. Look at this thread, 0% development information, no code in sight, no one posts logs, steps to reproduce, or anything. Half the posts are *****ing about dirty flashing. Unfortunately that kind of moderation takes a lot of time so it's not always possible but if everyone polices themselves and thinks before they post we can have much better threads. And if someone else has already corrected someone, there is no need to chime in with your own echoes besides inflating your own ego, so don't do it.

Before you post, think: Does my post add concrete information to this thread, or is it restating things that have already been said, or providing vague information about possible bugs which may or may not be due to my own bad practices when flashing? If not, hit cancel, whistle a tune to yourself, and go on your merry way, or correct those flaws and compose another post.

(Honestly, I think the tapatalk app is the #1 reason that these threads are so goddamn useless, because no one knows how to search from that app, and people can't be arsed to read previous pages on their phones. If it's so urgent, don't flash when you're not in front of a computer and able to compose a proper post. Although my previous post was composed 90% on my phone and then edited a little for formatting on my computer, most people who post from mobile don't take that time to make relevant and useful posts).
[Verizon Samsung Galaxy S III] Travisimo:
Coming from other roms and other phones, a "dirty flash" has always been one where you wipe cache/dalvik but without doing a factory reset or full wipe. There is absolutely NO reason NOT to wipe the cache and dalvik before EVERY flash... it doesn't erase anything that needs to be recovered and it only adds some time to the initial bootup as it does the "Android is upgrading" mumbo-jumbo.

I too am interested in reports after a proper "dirty flash". Sure, it's possible for a dirty flash to be borked, but for the most part I'm reading the SAME exact issues from people who do dirty flashes OR clean flashes. In fact, one would think that a clean flash would result in the same exact experience between random users, but it does NOT: some clean flashes experience issues that other clean flashers do not. Same goes for dirty flashes. Now yes, I'm in total support of those who say you should clean flash if you are experiencing serious issues that weren't there before you dirty flashed. But I think many of us are still interested in hearing reports from those who do a proper dirty flash. Just don't be a dumbass and complain about the rom not working or "why isn't this fixed" unless you try a clean flash first. But even then, don't complain for complaining sake because we are on the bleeding edge and have no right to complain in that manner.
[Verizon Samsung Galaxy S III] cgulliver:
This was mentioned previously but key tones for a conference bridge don't work for me as a string. Somehow they don't get picked up properly. If I key them manually its ok.
[Verizon Samsung Galaxy S III] manywelps:
That's just a gps.conf mod.
[Verizon Samsung Galaxy S III] sullivan1985:
Less arguing and more nerding please. I've learned a lot from reading the information in this thread. Can we go back to that? Thanks...
[Verizon Samsung Galaxy S III] Brian Gove:
I agree... STOP the bs. If someone asks an f'n question and you don't got the answer, don't respond being a smart ass. If you dirty flashed, PLEASE do a clean flash before you post your problem see if that fixed it.

back to nerding...
[Verizon Samsung Galaxy S III] minmongoblin:
Uh-oh...anyone have Amazon Appstore working? I can't login on M1...keeps saying "Please use a valid email/password". They are both very valid...so am I alone on this?
[Verizon Samsung Galaxy S III] jmill75:
This used to happen to me on stock....I finally just got rid of Amazon
[Verizon Samsung Galaxy S III] minmongoblin:
Not really an option if I want to keep using Shazam and Quickoffice, lol
[Verizon Samsung Galaxy S III] tml478:
Go to the amazon appstore website on your computer. Every time you flash a new Rom it tells amazon you are using a new device. Just delete some of the saved devices and it will work again
[Verizon Samsung Galaxy S III] AtLemacks:
I don't know where all of you are having so many problems. I stayed on the 8/12 Kexec version until yesterday and dirty flashed 9/10. You habitual crack flashers are breaking code flashing your phone so much. Get on a stable build and wait more than a day or 2 before you flash again. Watch for key releases and flash those. Not everyone in the community needs to be a "bug" tester. Not to mention, everyone here is quick to complain, but never to troubleshoot! You know the risks, so take the time!
[Verizon Samsung Galaxy S III] TechSavvy2:
Okay, then I'll actually give you the response you're looking for. He posted the exact same question four days in a row on four different builds. All asking others to flash so said person can sit back and not do any work. We've all clearly seen how person 1's phone has different results than person 2. I have clean flashed every single build so far and report to cm bugtracker and debug the issues because posting it here just makes others complain about how this isn't a daily driver and how only stock tw works for them. I NEVER had call echo, I NEVER had data drops. I NEVER had GPS issues. Audio is the only issue i experience thus far by clean installs.. So my response is what you are asking others to do and also not to do. The answer is to clean flash your phone and try it out. It works fine. Quit crying when people assholes. Its part of life. I'm an asshole when it calls for it, no point in acting like this is a preschool forum.

To clarify clean flashing, everyone should do the following at least once:

Backup your ROM.

move backup to computer or external sd

Wipe data/factory reset

Wipe cache

Wipe dalvik

Format system

Format cache

Format ....everything.

FORMAT (internal) SD CARD

-this last one does make a noticeable difference. This may only need done once or twice here and there. Other than that, dirty usually works.

Here is where it sucks not having the device maintainer be active in the thread, we don't know when data needs fully wiped and when it doesn't. A lot of times, they are graceful enough to let you know but he's not on here. Dirty has many many meanings. You need to k ow specifically when the last clean install was done. That should be all that's needed (And kernel).
[Verizon Samsung Galaxy S III] CrzzyLegz:
Has anyone else noticed this thread has turned into Dirty flash vs Clean flash... move to a new thread? :silly:
[Verizon Samsung Galaxy S III] Brian Gove:
Amazon works fine for me, the app store.

Then don't answer him... plain and simple. IF you got an issue with the questions HE is asking PM him.... dont keep it in the thread... be the bigger person and stop the stupid BS.

Made new Thread for that here... Dirty vs Clean
[Verizon Samsung Galaxy S III] codyvance:
:::making popcorn:::
[Verizon Samsung Galaxy S III] tdperry:
All this almost makes me want to get an iPhone so I can feel the love. :rolleyes:

TAPPED in on my (now unlocked bootloader) Verizon S3
[Verizon Samsung Galaxy S III] Brian Gove:
Then get one, SCOOT!! and GO!!! GTFOOFH.
[Verizon Samsung Galaxy S III] hopesrequiem:
Just hit 16.5 hours on with 3.5 hours screen time on the m1 build clean flash stock kernel. Pretty amazing. Navigation worked flawless and talked the entire time, a little too much if anything haha. M1 is nice. Try it guys
[Verizon Samsung Galaxy S III] kennyho35:
Is there any future to seeing better 3g data support with this Rom?
[Verizon Samsung Galaxy S III] tdperry:
Apparently sarcasm is above your comprehension level. I've been playing with Android since the Eris/OG Droid days.

TAPPED in on my (now unlocked bootloader) Verizon S3
[Verizon Samsung Galaxy S III] codyvance:
On a positive note, next nightly has alot of changes.. And is next to build :)
[Verizon Samsung Galaxy S III] sullivan1985:
I did a full clean install on the 9/11 build using the method described in the quoted post with the exception of formatting the internal SD. Booted and the device stuck on the activation screen. Went back to recovery and cleared cache and dalvik again and fixed permissions. 3G data drops are now gone. GPS locks effortlessly. All other functions that I would use on a daily basis are functioning as well.

Previously I was only doing wipes and not doing any formatting. I'm not trying to add any fuel to the "Clean vs Dirty" thing, but it did make a major difference for me.

Anyways, it looks like a bunch of work is going into the next nightly!
[Verizon Samsung Galaxy S III] toddley:
I assume they were trying to stabilize it before the M1 in the past week so commits will probably pick up significantly for the next couple weeks.
[Verizon Samsung Galaxy S III] awmobjects:
Running m1 and loving it.
[Verizon Samsung Galaxy S III] TheBiles:
I'll let someone else dive on 9/12 first. So many commits.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] cgulliver:
There are a boatload of merges queued for tonight's build also. Gonna build an unofficial and roll the dice.
[Verizon Samsung Galaxy S III] alee:
9/12 running well this morning. Data seems to be better than 9/11. Nothing obvious that is broken.
[Verizon Samsung Galaxy S III] nsmal24:
Mind posting it again after you get it built? Do you use a VM to do your builds or do you have a dedicated Linux machine?
[Verizon Samsung Galaxy S III] cgulliver:
Ubuntu under Virtual Box. Here you go...

http://dl.dropbox.com/u/15319813/CM/cm-10-20120912-UNOFFICIAL-d2vzw.zip

md5: 0de7fc455b5b6c24989205bc9abcc432
[Verizon Samsung Galaxy S III] nsmal24:
Still uploading? How long does it take to build a nightly after you build machine is all set up?
[Verizon Samsung Galaxy S III] cgulliver:
Should be finished uploading. It takes me 20-30min to build on a 4x4 Ubuntu12 Instance. I have a quad core i7 processor.
[Verizon Samsung Galaxy S III] ddggttff3:
Link is bad, you need to put the file in your Public folder, then share a link.
[Verizon Samsung Galaxy S III] NegativeOne:
What app are you using to see those stats?
[Verizon Samsung Galaxy S III] lxetuo:
Does anyone else get the same text message 3 times or so sometimes?
[Verizon Samsung Galaxy S III] neyenlives:
yes, has always happened, randomly, since the beginning, long before official CM.....it's something I shrug off and it wont happen again for weeks, then it will happen all day one day, then go away...completely random
[Verizon Samsung Galaxy S III] nsmal24:
+1 on link not working. I may have to set up my own build box so I can crank out a quick build here and there. I have a server sitting around not doing anything. It is 2x quad core (Nehalem) with 16GB of RAM. Should do the job.
[Verizon Samsung Galaxy S III] cgulliver:
Sorry . Fixed... http://dl.dropbox.com/u/15319813/CM/cm-10-20120912-UNOFFICIAL-d2vzw.zip