yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] nmyron:
http://pastebin.com/YUJwW5eQ

I see some ALSA audio issues, it appears to lose its route momentarily to the audio output. But they coincide also with the HWoverlay logs, IE overlay changes, it loses audio destination route, comes back. I pasted a link to the ALSA logs above, and in my prior post is a full logcat.

I can re-run one with the time switch to get more logging. But, its gonna be a hard one to nail down, since I can't really identify at what second I switch apps or cause the glitch.

---------- Post added at 01:44 PM ---------- Previous post was at 01:30 PM ----------

Here's another logcat, verbose, with time, and all filters.

http://pastebin.com/2etqneD3

This is what I am using to dump these logs

logcat -v time filterspecs:* > /storage/sdcard1/filename.log

Dunno if I'm grabbing too much info, but the same issues cited above appear here. I attempt to switch apps, and it appears to momentarily lose route to the audio output destination.
[T-Mobile, Samsung Galaxy SIII] ajm786:
Good to see we're bringing to light what's causing this. Did you open an official bug report at Cyanogenmod's Jira?
[T-Mobile, Samsung Galaxy SIII] nmyron:
I, unfortunately, am not running the M3 build. I have been wary of updating since my 4/10 is stable, and others have complained of hot reboots.

Disable touch sound... Betcha your audio pop goes away until an alert plays... Just tested, and until my low battery alert played, I had no issues flipping from app to app and screen to screen. Turn touch sound back on and every screen tap/menu selection = pop through audio track playing
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Flashers, look M3 is smooth as butter. You need to to do a full wipe. That is NOT a factory reset. It means manually wiping the system partition (if your using cwm then dump it and use twrp its better), dalvick and cache, flash m3, flash gapps, and do NOT restore system apps/data from apps like TB. Either use the stock kernel or lk3.4.1 . This is my method and ive been using m3 since it dropped. No fc, no random reboots, hot boots, or audio skips. Dirty flashing, not doing a real full wipe, and restoring old system data then complaining the build is the problem annoying. Use this method and if you still have problems then its still your fault...jk but seriously if done right them m3 is gonna make you wet your jockies with joy.

---------- Post added at 09:59 PM ---------- Previous post was at 09:52 PM ----------

While that is helpful I will be honest and say that not a single Official CM Dev reads these forums for bug reports. If its not a bug submitted through the bug tracker with detail and a logcat then this all just chatter between end users (still helpful for each other). Now im not knocking your post or trolling etc. Im just saying these forums are for us flashers to help each other out but the official cm devs do not step one digital foot in here to look for bug reports. :beer:
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
1) /system is automatically formatted when you flash CM. Wiping it manually is not necessary.

2) System applications do not store their settings on the /system partition. They are stored on the /data partition, along with all other app settings.

3) Wrong on CWM/TWRP comparison.

I don't know about M3, because I didn't use it long enough to have problems. But 4/12 rebooted on me once today. And I haven't had any issues with the recent nightlies. Just this one.
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Lol, i have been flashing cm and others since my cliqXT. Ill stick to my experiance on the sgs3 though: i have dirty flashed roms with no issues with a version that supposedly has none and had issues persist. When i manually wipe then flash the new version they do not show up. SO i am inclined to believe that sometimes old data persists on a dirty flash.

My preference twrp over cwm is strictly that: preference. I have less issues when flashing anything 4.0+ in twrp than cwm.

Im not saying you do not have a valid point about the storage of settings. BUT search xda and look at the countless posts from users having issues when restoring system apps and data from TB. They are usually when going from one rom to a different but still valid.

My post was about MY experience in flashing roms and personal preference so thanks for replying but my way works for me chief :p
[T-Mobile, Samsung Galaxy SIII] nmyron:
We needed a Jira report. I submitted one. Here it is.

https://jira.cyanogenmod.org/browse/CYAN-830

If you are on M3. If you play music via the Play Music app, Pandora, or other audio apps, and tap the screen/hear a notification/etc and get a POP sound any time this happens, first do this in the terminal:

logcat -v time filterprocs:* > /storage/sdcard1/soundbug.log

Then replicate the popping sound, go back into the term and break the logcat (ctrl + c , in better term Ctrl is volume down) and email this to yourself. Open in Notepad+ or simulacrum and Ctrl+f for "alsa" (no quotes).

Go to the jira link above, up vote the bug, comment the bug, and paste in relevant data from your logcat. Let's get the devs sufficient data to fix the problem, instead of sitting on our laurels complaining.
[T-Mobile, Samsung Galaxy SIII] skyxliner:
Anyone try if 413 is better than m3?
[T-Mobile, Samsung Galaxy SIII] mt3g:
http://review.cyanogenmod.org/#/q/status:open,n,z
[T-Mobile, Samsung Galaxy SIII] nmyron:
I'm not sure what I'm looking at there. There are a WHOLE lot of items, which one in particular is of interest in regards to the bug post?

---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------

Dunno, I'm gonna stick with M3, can't submit bug reports for issues in a nightly.
[T-Mobile, Samsung Galaxy SIII] cangri87:
Latest nightly is a lot more stable than M3... And im sure most of the audio glitches are being fixed on the 04/14 nightly. Screen jumping to previous pages is fixed in latest nightly.
[T-Mobile, Samsung Galaxy SIII] mofogx:
I just looked at the changelog for the next nightly. This one is going to be huge... or so I hope.
[T-Mobile, Samsung Galaxy SIII] mt3g:
It's your guys' issue with music being looked at, someone posted a commit to fix it.

T-Mobile SGS III
[T-Mobile, Samsung Galaxy SIII] ajm786:
I looked all over and don't see it. Can you link the specific commit?
[T-Mobile, Samsung Galaxy SIII] mt3g:
Its the 4th commit down from open (not merged) fix static on speaker... Its still in the works and they're doing stuff at least. Not everyone has the issue (such as myself) but some do obviously. Hopefully they get it cause reading across all 4.2.2 ROMs about it is annoying lol.

T-Mobile SGS III

---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------

the M2: sound: fix static on speaker enable/disable
[T-Mobile, Samsung Galaxy SIII] nmyron:
Super schweet! Good eye there mt3g! While I know everyone doesn't see this in their build, its good to know that those of us that do suffer this issue have a possible fix coming in the future.

As a curiosity it would be interesting to know why its losing route to the audio output in the first place. Is that how it handles the music volume reduction to play notifications, or is that the bug in its entirety. Its not well explained, though they def cited CYAN-830 in the code review (the bug report).
[T-Mobile, Samsung Galaxy SIII] mt3g:
Ya I think its a bug overall (or a feature in their eye) but my notifications as of late have been coming out of external speaker instead of through the headset while plugged in. I'm pretty sure they were seeing if it'd be better this way or that way and things got screwy in the meantime.

Ya they definitely are paying attention to it since you posted things the proper way, instead of just saying "does this happen to any one else?" and "+1" then nothing following, kudos to you for doing stuff the right way sir :). If you follow that commit, on the bottom where "comments" are you can follow, although vague, some description of what's going on.
[T-Mobile, Samsung Galaxy SIII] ganiman:
And people havent posted audio bugs over and over and over. But thats cool right? Lets fill up pages on top of pages about that and bury any other useful information. Nothing about the camera though.

Sent using Tapatalk
[T-Mobile, Samsung Galaxy SIII] itzsmokey:
Have been flashing every 4 days and its running smooth since I started flashing in those increments
[T-Mobile, Samsung Galaxy SIII] Habs69M:
14/04/2013 Nightly rocks, should be renamed stable build if yo uask me :), loving it so far.
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Anybody see that commit to fix photosphere fc? I think ima try it and see if photosphere still has issues. Will report.

---------- Post added at 09:44 PM ---------- Previous post was at 09:16 PM ----------

Ok here is my report: Photosphere is working for me now! Always force close/freezed before causing me to have to reboot, etc.

I pulled the googlegallery.apk from a zip file from i believe the s3 international version thread on photosphere. Sorry there are to many photosphere threads for me to remember.

Anyway i think any gallery with photosphere should work.

Good luck!

---------- Post added at 09:50 PM ---------- Previous post was at 09:44 PM ----------

BAM! They fixed it! Photosphere working.

http://review.cyanogenmod.org/#/c/35048/
[T-Mobile, Samsung Galaxy SIII] tdizzle404:
Awesome news man thank you!

Can you confirm photosphere working?
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Working for me now.
[T-Mobile, Samsung Galaxy SIII] zinite:
For anyone following the dock audio fix, it's been assigned to cyanogen on the issue tracker.

https://jira.cyanogenmod.org/browse/CYAN-40
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Where is everyone? I thought photosphere working would be fairly big news with all the threads on trying to get it to running.
[T-Mobile, Samsung Galaxy SIII] mofogx:
I'm on the latest nightly now... how do you get Photosphere to work?
[T-Mobile, Samsung Galaxy SIII] mofogx:
Is there anything extra that I have to do? I have the panorama button on camera, but I don't see anything for photosphere on the latest nightly, not even a photosphere button.
[T-Mobile, Samsung Galaxy SIII] ashokjadav:
can you share the apk ??
[T-Mobile, Samsung Galaxy SIII] tdizzle404:
I've stayed away from cm for a while now, because of some instability issues,

But after flashing 14/4/2013 I am very pleased to report its very stable and battery life is great :) this build represents everything thing good that cm is known for.
[T-Mobile, Samsung Galaxy SIII] em2drvr03:
Is there a long press to kill an app feature?
[T-Mobile, Samsung Galaxy SIII] tdizzle404:
Its nice to have good data speeds again Lil I swear I couldn't get more the 12 Mbps since 4.2.2
[T-Mobile, Samsung Galaxy SIII] em2drvr03:
Anyone on 4/14 have fc on the theme changer and problems applying themes?
[T-Mobile, Samsung Galaxy SIII] mofogx:
I haven't tried that yet, but I did notice that the audio issues were gone after flashing, but came back after rebooting my phone an hour ago. I'm going to see what rebooting does again.
[T-Mobile, Samsung Galaxy SIII] inkling:
Unfortunately, I'm getting random reboots every half hour or so on 4/14. First flashed over 4/13, then tried again after wiping data (and system, dalvik and cache) first. Fixed permissions. I did restore data from some apps via rom toolbox. Any suggestions?
[T-Mobile, Samsung Galaxy SIII] neysito:
I had reboots on every nightly after 3/17, clean wipe or not, I tried the leankernel on 4/14 and 15 and problem solved. Great battery life and no reboots or freezing ups.

GS3 T999V
[T-Mobile, Samsung Galaxy SIII] mofogx:
Oh no, my device isn't rebooting by itself. I rebooted manually to test effects on battery, and upon booting back to the home screen, the audio issues came back. It seems to affect play, and apollo, but not Spotify or Pandora.
[T-Mobile, Samsung Galaxy SIII] Nabeel10:
Other than Ktoonez, what kernel are you guys running?
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
In Developer options. Its the very last checkbox in the list.

If you don't have the Developer options enabled you will need to go to System Settings -> About phone -> Tap the 'Build number' until the Developer options appear.
[T-Mobile, Samsung Galaxy SIII] silverton:
Interesting! Played with LiquidSmooth for about an hour and went back to CM. So a super fresh clean install of CM. no more jumpy browsing, and I notice on the notification bar, if I bring it down from farther to the right it brings down the quick tiles, if I bring it down with my thumb farther to the left it brings the notifications. I didn't notice that before...

Also, with a fresh install the whole ROM just seems smoother. Also noticed a different Scheduler, ROW...
[T-Mobile, Samsung Galaxy SIII] gen10:
Love this Rom with a burning passion but my ears aren't .If you guys could look into it I know its not the highest propriety ATM. Would it be possible for you guys to fix the safe headset volume and have it work. Thanks

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Never once had a single audio issue with Poweramp. Flash every nightly, been using it for six months. Not one time. Not one snap, crackle, or pop. Not one concert-level ear drum rupturing sound.

I had a long post typed out originally. I deleted it, but the jist is: get a better music app.
[T-Mobile, Samsung Galaxy SIII] ajm786:
Although this is true, it doesn't excuse the fact that default audio is broken or bugged. The good news is that it's currently being looked at by the devs; there is a commit in github regarding it.
[T-Mobile, Samsung Galaxy SIII] nmyron:
I think part of of the problem is DSP Manager. Whatever it installs (dunno, does it have a kernel module??) causes issues. I used Titanium Backup to uninstall DSP and Apollo and have had less issues. I have purchased Equalizer to replace DSP manager and it appears to be much more fully featured than DSP Manager anyways. You can create and save custom presets for different music types and output devices.

Either it truly is just a random kernel bug, or something in build buggers it up occasionally, but not always.
[T-Mobile, Samsung Galaxy SIII] ajm786:
On the flipside of that, during my midnight flashing madness to try and get to the bottom of the issue, I can confirm that DSP doesn't really make an iota of difference. If you replace DSP with something like Acid Audio or one of the other audio packs, it makes absolutely no difference. Additionally, having NO DSP at all doesn't help either.
[T-Mobile, Samsung Galaxy SIII] Spiyder:
http://xdaforums.com/showthread.php?p=36533817

Link to thread i got the zip from. Read the op.
[T-Mobile, Samsung Galaxy SIII] pvtbacon:
Ever since I switched from cm10 to cm10.1 nightlies, my phone has been randomly rebooting when idle. It isn't so much a boot loop as it is an occassional unannounced restart every 5-10 minutes with no regular pattern. I've tried undervolting, disabling nfc, changing governor from interactive to ondemand and nothing works. The only fix is to revert back to an older cm10 nightly. I thought i'd try flashing the 4/14 nightly to see if anything had improved over the past month but the same problem creeps up. Battery activity shows a black vertical line where it reboots and there is significant drain associated with it.

I've read about the issue elsewhere but no one has offered a solution. Anyway to troubleshoot the problem?
[T-Mobile, Samsung Galaxy SIII] stonew5082:
That sounds more severe than the majority of cm users. Your situation is particular and not universal it seems. Try a clean install.
[T-Mobile, Samsung Galaxy SIII] gen10:
I'm on the 04/14 clean install and I'm getting random reboots. Anyways to fix this?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
The last time I had random reboot issues in early April, I went back into recovery, wiped cache and dalvik, then fixed permissions and rebooted. Took care of it for me.
[T-Mobile, Samsung Galaxy SIII] Sergent D:
Things were great for me until about a week ago. I started having the rebooting problems in a really bad way, it would happen all the time. I tried everything. Clean installs, reverting to stock, switching to AOKP, etc. Other ROMS would work fine. I ended up switching to AOKP but I don't like that ROM nearly as much. I'll try again in a few weeks.
[T-Mobile, Samsung Galaxy SIII] em2drvr03:
I'm on a fresh install and I am getting no reboots at all. I couldn't be happier.
[T-Mobile, Samsung Galaxy SIII] tidewblch:
No issues

I must be very blessed. I only dirty flash and have been doing that since way back in 10.0 on the GS3. I dont wipe cache when flashing or do anything else to prep other than back up. My previous flash was 4/4 before I flashed 4/14 yesterday and have had no reboots or any other issues. I mainly use the phone for business and calls and some games. I dont play music on it often. I have never changed out the Kernel. Been using CM since version 7 and love it. My thanks to the developers who put their time into this OS and everyone else who contributes to its development in some form or other. Keep up the good work.
[T-Mobile, Samsung Galaxy SIII] zander21510:
I saw in the changelog on one of the recent nightlies that there is now an option to save pictures to external memory with the stock camera. Can anyone confirm?
[T-Mobile, Samsung Galaxy SIII] GenericAsianGuy:
I can confirm! Options are:

Internal Storage (default)

SD card

USB storage
[T-Mobile, Samsung Galaxy SIII] hurtz777:
I just tested the camera in 0416 and it saves properly to external sdcard! Thanks CM team!
[T-Mobile, Samsung Galaxy SIII] AllAboutAndroids:
I wiped it all...Formatted Internal SD card for the first time in months. Cleared Cache, Dalvik, Factory Reset, flashed a brand new clean Nightly followed by GAPPS then fixed permissions but unfortunately I still get the random reboots. No issues at all with the AOKP or LiquidSmooth alternatives though so I'm confused :S
[T-Mobile, Samsung Galaxy SIII] inkling:
I had a similar experience starting just with 4/14, but it all worked out. At first I had random reboots with a regular flash, then again random reboots with a full wipe and flash and fix permissions. Then it seemed to just settle down and stop rebooting after a half a day or so. No idea why. Later I installed leankernel, and haven't had any reboots since.
[T-Mobile, Samsung Galaxy SIII] em2drvr03:
I use Bluetooth streaming a lot...and I wish the streaming sound was as good as the stock touchwiz ROMs. Its really just a bass issue. It doesn't sound as clean. Anyone else notice this? Is this a common problem?
[T-Mobile, Samsung Galaxy SIII] cruise284:
Yes I've experienced the same issue. Hope this can be fixed.
[T-Mobile, Samsung Galaxy SIII] nmyron:
So, I dunno if anyone noticed yet. But, the change log for 20130417 Nightly has the kernel patch for the sound glitch. I am downloading now.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
It does have low end distortion over BT. Touch wiz has the apt-x codec which is an amazing wired-like sound feature for such enabled devices. Wishing we can get that somehow.

You might want to check this: at least for me, dsp speaker tab is controlling BT instead of the BT tab. So if speaker bass boost is set to extreme, BT bass will be distorted. It's real wonky, and I'm gonna try to wipe to see if it fixes it.

Other than that, 4/17 is totally stellar. I've used it all day listening to BT audio with occasional call interruptions and notifications, and absolutely 0 glitches. Been smooth as butter, and battery is decent so far too. I've stayed on 3/17 until today, but I see no reason to go back. Plus we have pics to ext and a non force-closing photosphere now.
[T-Mobile, Samsung Galaxy SIII] em2drvr03:
Just flashed 4/17 ..where is photosphere?
[T-Mobile, Samsung Galaxy SIII] mofogx:
I'm pretty sure that's for tomorrow's build.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
It's a separate apk. Google photosphere 4.2 galaxy s3 and flash it. The news it that it now doesn't force close on these nightlies.
[T-Mobile, Samsung Galaxy SIII] CodyRst:
4/17 still stutters, and occasional pop.

However, one of the Aokp's in the dev thread has the issue fixed. (The rom by synthetic).

I flashed it, and no stutters or pops what so ever. :good:
[T-Mobile, Samsung Galaxy SIII] nmyron:
Did you do a dirty flash or clean? I just got a chance to dirty flash, but, if you didn't do a clean, I am willing to try and see if it helps.

---------- Post added at 08:56 PM ---------- Previous post was at 08:44 PM ----------

I think you are right. It was merged on 2013-04-17 at 10:16, so it is most likely going to be the 2013-04-18 nightly since this 2013-04-17 build was run at 11:40:ish
[T-Mobile, Samsung Galaxy SIII] chrisneal:
DSPManager

For me, DSPManager works wonderfully well with Google Play Music, but makes no difference when enabled/disabled when listening to Pandora. Does that make any sense? I'm running the M3 release of 10.1.

Has anyone else had issues with DSPManager working/not working on various music apps?
[T-Mobile, Samsung Galaxy SIII] mdfritz:
4/17 went from stellar to horrendous in one day. All day today had issues like: broken microphone, several random reboots, bsod, call freeze, erratic home screen. This is on a dirty flash so take it with a grain of salt.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It is known.
[T-Mobile, Samsung Galaxy SIII] elesbb:
I read somewhere that an audio_config.conf file was incorrect and replacing it with a correct one would fix it but it doesnt for me.

Oh, and if anyone knows what the commit was to fix the long press button behavior (Where you press the home button once and it acts like you long pressed it) can you please PM me and link me to it? Thanks :)
[T-Mobile, Samsung Galaxy SIII] mt3g:
http://review.cyanogenmod.org/#/c/33383/
[T-Mobile, Samsung Galaxy SIII] chrisneal:
Thanks :) So it was a Cyanogen thing and not a Pandora thing? Anyone happen to have this corrected audio_config.conf file so I can give it a whirl?

Much thanks!
[T-Mobile, Samsung Galaxy SIII] elesbb:
You always knew i loved you right? xD no homo :P thanks bro
[T-Mobile, Samsung Galaxy SIII] mt3g:
Lol, I know the gerrit right now very well. Been stalking it since 3.4 kernel changes.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Yeah, ive stopped following the nightly builds. There so horrible i have no idea why. Things were so great in the beginning. Plus the whole mic issue for video and audio recordings.. i just dont know whats happening anymore :'( lol. Seems like things are falling apart. I went back to december 24th build and the only issues i can find is the long press issue, which im gonna try to smali out but i think it may be a kernel thing. and also the mic issue. battery is perfect, DSP is perfect. So long press issue is the only thing i saw wrong with it.

I miss these awesome builds :(
[T-Mobile, Samsung Galaxy SIII] mt3g:
Def a kernel thing flash a 3.0 kernel after the commit fix, and then implement the Faux Sound deal, that'll fix the low audio recording as well. It's tough to get a 100% good build but it's actually possible if you Frankenstein it...
[T-Mobile, Samsung Galaxy SIII] danielrod:
Are you guys still getting the laggy transition animations?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Yes. If laggy transition animations were the only problem, I could live with that. Not sure why everyone always complains about this one.
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
Still happy with 3/17 - no real bugs.
[T-Mobile, Samsung Galaxy SIII] Master Loon:
3-17 seems like a gem so far.....no issues to complain about....
[T-Mobile, Samsung Galaxy SIII] pgg285:
Just a heads-up: Latest nightly (4-18) seems to have changed more kernel stuff -- I got a black screen after flashing the latest Ktoonsez kernel over it. Reflashed without it and it booted normally.
[T-Mobile, Samsung Galaxy SIII] mofogx:
Where were you able to get 4/18? It's not showing up on updates or cmxlog
[T-Mobile, Samsung Galaxy SIII] pgg285:
I got it through CyanDelta.
[T-Mobile, Samsung Galaxy SIII] corkythetard:
I got it via ROM Manager. Went to look at the changelog before flashing and no list of a 4/18. It's running fine for me today.