yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Thats a fair and valid point however this is the original android dev section.. Dev being a key word this isnt a discuss zone... Thats what general is for and that's all im arguing.. Theres a place for everything and if there wasnt xda would be more chaotic than it already is and many users seem to have forgotten what goes where...

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
3/29 build clean install

still flickering sound when click on something (ie. app drawer, etc.) while playing music (no bt or anything)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Can you post a logcat I'd like to take a look at it in the morning

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
here you go

http://dl.dropbox.com/u/58538622/logcat.log
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
I can deal with that. I just don't want it rebooting on me mid-day. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
For being a non discuss zone you sure do a lot of discussing in it.

The fact of the matter is, if I flash a nightly and have a problem with it.. Clean flash or not... I am NOT supposed to report ANYTHING.. Why? Because its a nightly!

This forum would be the incorrect place to report a bug if I did manage to reproduce it on an M build. So unfortunately your entire argument has no purpose.

Now please stop posting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
So...I've been dirty flashing since CM9 and I've got this issue where my phone refuses to boot, douses itself in gasoline, and self-immolates. Is anyone else seeing this issue?

You guys need to lighten up. I feel like I may be the root cause of this particular argument, so I feel some responsibility to interject. I think it's reasonable to expect that users shouldn't be reporting every little bug if they've been dirty flashing (even though dirty flashing is a valid use case, people rarely wipe their phones when major upgrades come out), but it's also reasonable that during the course of development and beta testing and whatnot, that bugs will trickle out, and those should be reported. If this really isn't the best place to report them, then where is? I'd like to hear from a Recognized Developer or Forum Mod on this topic, because clear instruction from someone in a position to decide will likely reduce the amount of argument and actually streamline the entire development process because the Devs won't have to dig through all our bullsh*t.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elijahblake:
This is the only way I flash as well and I never have any bugs that aren't known. This is one of the many reasons I love CyanogenMod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Not much shows up on the logcat as far as i can see on my phone... Ill look deeper into it when i can get to a desktop :P

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Look up a couple posts and see who liked Zelendel's post. Then read it. I think it is quite clear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
Constant-crash fix (revert) by Cyanogen is merged:

http://review.cyanogenmod.org/#/c/34783/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yep. Missed that post. Clear indeed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
6+ hours and no crashing so far
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
LOL. Ok sorry to all for being worked up. Perhaps we lowly users can start an unofficial CM10.1 nightlies for i747 over at the "AT&T Galaxy S III Q&A, Help & Troubleshooting" http://xdaforums.com/forumdisplay.php?f=1713 where users are welcome to discuss issues after dirty flashing of nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
And your point would be? You would just be told to do a full wipe and see if the issue is still there and then post. Dirty flashing a nightly alpha build is a great way to have bugs and issues. No one takes bug reports from a dirty flash into consideration. The min they see dirty flash they tend to skip the post or reply with what I posted above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
This thread will be for the users who want nightlies but don't want to do full wipes. As spectrumfox pointed out, there is value for such users to find out what to expect after a dirty flashing of a nightly. They can also read about any possible solutions for issues such as a clearing the data of certain apps or selecting of certain options. This wouldn't be considered bug reports, more of users helping out users. I don't expect devs to hang out there if they feel dirty flashes are not useful in discovering new issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Well Good luck I think you will find out fast what the devs already know(and the reason for no bug reports on dirty flashs) That dirty flashing can bring random issues to different people. It may cause issues for me with say kernel panic or boot loops, but you dont get those issues but do get other issues that I dont see on my device. See what I mean.

Now while some are only here to make their phone cool and have no need to learn what is going on then I say this. If you dont follow the needed steps to run a custom OS then dont complain if you end up with a brick that has a voided warrenty.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Yes, we all do know the disclaimers that no one else is responsible for any problems except ourselves. Despite that, I can assure you I'm not the only one who still wish to do dirty flashes every single day of the latest nightlies. So for everyone like me, here is the thread http://xdaforums.com/showthread.php?p=39708178 I just created over in the other forum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
So let me get this right. You want to run a custom OS but don't want to follow the proper flashing steps? I never said you were alone in wanting to do this but as a development forum we are in the habit of trying to teach people the proper way to run a custom OS. And dirty flashing is the wrong way to do it. Its nice to see you offer to support all the dirty flashers in the thread you made. As I stated good luck.

Wayne Tech S-III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I disagree that it is wrong to do a dirty flash. Firstly, some devs have stated that a full wipe is not necessary most of the time when upgrading from CM10.1 to a newer version of CM10.1. Of course in between versions, like from CM9 to CM10, or when coming from another ROM, full wipe is highly recommended or required. Secondly, most users will understand that a dirty flash might introduce some strange bugs, but accept it as part of the deal in return for convenience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Ok you got this site very confused. This is not a Rom site, For users to come here and flash roms and then get support for said rom. This is a developers site made by developers for people that want to learn. If your not here for that reason then you are here for the wrong ones.

The same devs that say a full wipe is not needed are the same ones that will tell you to do a full wipe the min a bug shows up.

Now I will not argue this point any further. As my banner states. "The right way is never easy and the easy way is never right "
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Upgrade vs clean install

In product software, considering upgrades is typically a painful, yet meaningful exercise. Upgrades require the running code to take into consideration additional variables that are often, 'non-obvious'. In the end, the resulting code which supports both a clean install and an upgrade is often(if not always) more robust.

In this particular Android nightly flashing scenario, the situation is slightly different, as nightlies themselves may contain interim code and settings that are not found in "stable" releases. However, I think the result is still very similar, potentially even more beneficial. In this case, it may be something like 90/10 where the issues caused in upgrade are 90% likely to be seen in a full upgrade, 10% extraneous errata due to interim build items.

I would argue that in forcing development to consider upgrades vs clean will nearly always result in cleaner, more robust code, even in the case of the 10% extraneous above, as those can lead to back doors for security and other issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
The crash fix will be in the NEXT nightly (3/30), so you'll probably suffer at least one crash before then. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Dirty flashers, here's a thread that welcomes you and your discussion! ==> http://xdaforums.com/showthread.php?p=39715313 :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
I've had about 4 crashes today on the latest ROM and the last one rebooted into safe mode, got it back to normal but I had to reinstall a widget and the live paper. The cost of being on the. bleeding edge. W00t!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
The crash fix did not work for me. I had a few spontaneous reboots on a build that included the fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
The build with the crash fix will be 3/30. It was not included with 3/29.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
My build to share

https://www.dropbox.com/s/9up95uu4y3tata0/cm-10.1-20130329-UNOFFICIAL-d2att.zip

Here ya go, includes up to (Revert "Make using open-source drivers such as Freedreno possible." (android_kernel_samsung_d2))

Built it this morning, been using it all day. So far no problems. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
As I said, I was running a build that included the fix. So random reboots doesn't seem to be fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Stock kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
Ok i wipe my phone this morning now i have 2 issue.

1. My network icon on top that usually turn blue when i have connection to the internet always stay white but no connection issue.

2. Noting sync i have to manualy unclick and click sync then it sync that one time but do not automatically sync. I think could be cause by what cause the first issue. The phone think its not online and do not sync?

Also wifi or not wifi same scenario

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
Yep. Fresh build after sync, clobber and fresh extracts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
Maybe try and download again. I clean wiped this morning and have had none of those problems
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Thats a Q&A thread. The discussion does not belong there either.

---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------

Are you using ktoonzes kernel? If so go read that thread. Your problem sounds similar to problems some of them have been having.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
Not sure to see what kernel i use but here a screenshot or it

You can also see the wifi and data both grey but i still have internet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roughneckboren:
Have you flashed gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
Hi just did sames result

Also dont know if its related but my transformer prime do the same thing?

Dont get my email push at all?

Also a note i use titanium backup on both tablet and phone

---------- Post added 30th March 2013 at 12:02 AM ---------- Previous post was 29th March 2013 at 11:25 PM ----------

I think found the issue. Was cause by titanium backup.

To fix i had to clear google service framework data.

Fix now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
A question here related to sound that is annoying me a lot every time I put music It sounds really bad distorsionated and to Fix it I have to Open DSP manager and close it and it fix! that happens every time!!! Any idea? please

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubmusic:
Chrome meltdown with 3.4 kernel

One consistent observation is that Chrome is constantly crashing and at times causing the UI to completely freeze. If I use any other browser, everything is solid, but Chrome consistently fails, with the initial sign of disaster being the corruption of the UI graphics, particularly while inputing data (ie. a password). Easy solution, use another browser. Nevertheless, I will post a logcat when I get a chance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] etham3:
Check to see if your IMEI number is still intact.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
I turned off the volume rocker and it helped so guessing that somehow conflicting with others

However when playing some games like flying penguin, it's still there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jorgeszabo:
Photosphere?

I haven't heard or read anything in a while regarding photosphere on cm10.1 non nexus devices. Does anyone know if this is being worked on or is it a hardware limitation on the d2 devices?

Is there an alternative out there?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kennyaa:
Anyone know if Message Access Profile is working? Trying to get my car to receive and send text messages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corno1979:
Gapps install script only installs photosphere on nexus devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12th Planet:
hey, has anyone got PIE to work?

I installed the aroma navbar http://xdaforums.com/showthread.php?t=1918166

then I went into settings to enable PIE, but the gestures won't work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dagnus:
I've found that once you enable pie, you have to reboot the device. The gestures work after that. Try it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12th Planet:
Thanks for the help, dude, but unfortunately it didn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
I'm on the 3/17 build (so i cant confirm)...but I believe if you enable extended desktop, you get the pie controls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12th Planet:
Thanks for the info, but I've already done that. I still see no PIE. I think they removed pie from the d2att nightlies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
They pulled PIE from all phones with capacitive hardware buttons, thus all GS3's.. even if you enable Nav Bar it won't work. Someone with more knowledge may be able to correct me if I am wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Its a pretty useless feature. You can get it to install if you muck around with the installer script. I cant see anybody wasting any time trying to get it to work right though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
How's that 3.4 kernel coming along guys? I'm still on 3/17 with the old kernel and it seems like cm has made a bunch of improvements to the 3.4 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nyamoV2:
anyone having problems with the latest nightly link? i'm trying and all i get is a 404
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
I've been running the 03/31 nightly (includes 3.4 kernel) most of the day. Only problem was a single screen-of-death.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
I've been wondering as well. How's the battery life? 317 has been extremely stable and has great battery life. I might stick with it until a monthly or RC is out

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
CM has merged a bunch of code into the kernel. The commits have been merged with KT's kernel and its running very well now. I can't comment on the stock kernel because I dont use it but the code added to KT's from the CM kernel made a huge difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
+1. I have been on the 3/30, just received screen-of-death i.e. non responsive device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] romracer:
Photosphere is closed source. Unless that changes, it will only be officially available on Google devices.

Edit: Sorry didn't see the second question in your post. Samsung supposedly has Orb coming with SGS4. Who knows if it'll be portable to AOSP ROMs though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atmospher1c:
can anyone recommend a stable nightly? or do i need to go all the way back to a milestone build? too many restarts, crashes, etc lately for my tastes on the nightly builds :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
i've had no problems with the 3/17 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
3/30 and 3/31 seemed to run fairly well. 4/1 rebooted on me on my way to work this morning. Wasn't able to get a logcat either. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
I had lots of problems with the 3/20's but the 3/30 nightly seems to be working fine for me ... so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Me too. I've been using the 3-30 nightly since it came out & I haven't had any problems...Running great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Latest nightly no issues...

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastergrillo:
Unfortunately I'm getting the phantom back on some apps using the lastest

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Got one two however i realized it was setcpu messing me up

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Latest nightly is out, hope things are stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Anyone getting random lockups/crashes? I'm on the 3-29 nightly and this happens at least once a day. I'll get nova launcher crashing, system UI crashing and then nothing responds, phone reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Looks like media-based apps (Play Music, TuneIn) FC on the 0401 nightly. Or is it that I have to do a "fix permissions"?

Edit: tried fixing permissions, no workie. Updated to newest nightly (0402), no workie either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I get the nova launcher crash frequently. Play Store crashes as well. I've seen this on the 4-01 nightly and it persisted on 4-02.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
On 4/1, and a few builds before, I'll be on a phone call for about 1 minute and the phone freezes.

I reboot with power/press/hold and then I can make calls pretty reliably.

Flashing 4/2 now.

Dirty flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
4/2 appears to be pretty stable so far.

Decent battery life, no audio stuttering, no reboots (yet).

I can confirm the occasional Play Store crash. It's not very bothersome though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beng2k:
Installed 7/25...cannot confirm LTE for Canadian users however the option is there in mobile networks whereas it wasn't before. Won't be able to test until tomorrow when I'm back Downtown.

The default clock for the CPU is set @ 1.1. Had to manually set it at 1.5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
Audio (routing issues):

1. A2DP comes out the speaker

2. Back microphone doesn't work

Video:

1. Video can freeze when rotating

2. Memory allocation issues

Audio issues require that we adapt the QC ALSA driver to work on our devices, and video issues require IOMMU support in the kernel. I'm pretty far along with getting IOMMU working, except that it breaks the camera right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
nvm .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malaeum:
Cyanogen,

While you were away I have been trying to keep a decently organized bug list together in hopes it might be of use to the CM team. I'm no code monkey (sadly), but I hope its decently well put together. Let me know if something like this is of use to you so I can continue to maintain it. Its half been a project in procrastinating on my thesis (which is due Monday).

http://xdaforums.com/showpost.php?p=29253723&postcount=1205

Cheers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Igotsanevo4g:
Yes I know its probably been posted, but its buried and I'm late to the party. Yes I searched the thread (god xda search is bad)

Couldn't find CM10 gapps on the cm wiki where I get cm9 gapps, could anyone pass me a link to a solid gapps zip? Have googled and found some but they seem shady. Seem to remember a goo.im page with a list of gapps? Its been awhile...

Thanks :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
New GAPPS for JellyBean - Updated 7/26/2012

http://goo.im/gapps/gapps-jb-20120726-signed.zip

Changeloghttp://goo.im/gapps/gapps-jb-20120726-signed.zip MD5: c86d557ce575a223d39efbc27bdaeaa4

Add Jelly Bean Youtube (not available in Google Play Store)

Add TalkBack (Google Accessibility app)

Add Jelly Bean Gmail with Jelly Bean notification expansion compatibility

Add libpatts_engine_jni_api.so to fix Google Maps not announcing street names

Adjust install and update scripts to remove source-built QuickSearchBox.apk (Search) and replace with Velvet.apk (renamed as QuickSearchBox.apk). This prevents the user from ending up with two Search apps

Still no good way to fix Gallery not syncing to Picasa without ending up with a second gallery app

---------- Post added at 05:48 PM ---------- Previous post was at 05:41 PM ----------

did that work for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
I can confirm LTE works great on TELUS now :D

Awesome job Cyanogen!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Igotsanevo4g:
Couldn't have asked for more lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trincisor:
More detailed change log anyone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Someone should tell us what mdnie scenario and all that mumbo jumbo means in settings :)

And I just saw that post on updated gapps for jb and since I already flashed another version of gapps from like 3 weeks ago can I just reflash the nnew ones?

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Yay! Out to the Coast beach? I LOVE Ruby Beach and The Hoh

You sir, are a manly man, with manly sorts of ways! Thanks again for the work in this.

Loading right now. I'll report any issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alirulzz:
for some reason my android beam is not working.. tried sending files..pictures and what not between this and a gnex.. anyone know if it works here??? cant seem to find a definite answer on this thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Any word on the external speaker? The 7/20 build had pretty bad distortion at the upper volume levels, and I use the phone as a speaker phone often. Would someone be kind enough to let me know if the distortion is still an issue in this build and save a re-flash?

I'm a "latest ROM" addict.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] munchkers13:
ok i screwed up.. i didn't make a backup and now twrp doesnt recognize the internal card where the rom's zip is located... i realized this after wiping everything and now i dont have an os loaded... how do i recover from my **** up... ive looked and tried to push through adb but it says phone not connect...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scottyedmonds:
I just successfully sent a youtube video to my wife's stock s3 via beam, tried to send a picture and it said it doesn't support large file transfers (? 2.05mb)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JimmyStale:
Try download mode and flash with Odin?

Sent via raven from Winterfell