yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] nmyron:
So, DSP Manager still generates clipping, at least on my speaker. I'll have a quick test in my truck real fast to see if it does the same, or if the clipping was due to overpowering the phone's on board speaker.

Edit - when others reference "4/5", are you referring to build date (which on cm10.1-20130406 is 4/5) *or* are you meaning cm10.1-20130405????
[T-Mobile, Samsung Galaxy SIII] St0n3s:
Uh oh! I went to shoot some videos & it crashed everytime
[T-Mobile, Samsung Galaxy SIII] vvMINOvv:
Pretty sure it's date
[T-Mobile, Samsung Galaxy SIII] corkythetard:
Screen shots of battery stats? GPU/IO Scheduler settings? Stock Kernel? What apps are you using heavily?
[T-Mobile, Samsung Galaxy SIII] mdfritz:
The clipping is only when the virtual room enhancement is selected. Deselect that and you should be golden. From an audiophile perspective, that feature is a gimmick anyway. It ruins the stereo panning effects that are in the original studio mix of the songs.

The date refers to the nightly version that you see when you go to download it from cm updater, goo.im, cyan delta, etc.
[T-Mobile, Samsung Galaxy SIII] nmyron:
In my experience, on this fresh build, as soon as I turned on anything in DSP Manager, my tracks streaming in play music (all fairly high quality MP3 that play very well on my home HiFi system) started clipping. That goes for bass boost, or the equalizer. I never use that Room fill feature. Its kinda like those old Sound Blaster Live cards, how they "tried" to replicate a concert hall or studio with their "environment" settings, when all they did is make your hihats sound like mud.

But, otherwise, this build is super, super close to being the super-rom for this phone. Since purchase I have been rocking some flavor of CM, and i, in the last 12 or so hours, have not been happier with my choice. If only we could work out that clipping...
[T-Mobile, Samsung Galaxy SIII] ajm786:
To be honest, I started experiencing bad clipping even on 3/31. I suspect it has to do something with doing a nandroid restore, since it never did that before when I had 3/31. This is even with all DSP settings OFF.

Now, I just use Poweramp with DVC turned off, and it's solved all those problems. Using anything like Apollo, Android Music, or anything like that which uses the "default audio stack" (non-hardware accelerated audio) will cause clipping.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
I remember having the bad clipping issue on BT before March nightlies. Haven't had that since. I have used Google play music every day with no clipping whatsoever.
[T-Mobile, Samsung Galaxy SIII] sswb27:
My battery has been nice on 4/5 with some general use.
[T-Mobile, Samsung Galaxy SIII] nmyron:
I think I am going to try the GmusicFS and find a decent media player that works with either the DSP Manager or a different EQ. I just took a 4 hour drive with the family for a trip this Sunday afternoon, and for sure the glitches are gone. But as soon as I enable anything in DSP Manager, I get clipping and distortion. Which is sad, because this phone just doesn't seem to put out as much bass as is normally present on either my truck stereo or CD player. :confused:
[T-Mobile, Samsung Galaxy SIII] sswb27:
Try acid audio with awesome beats instead of dsp, It's been working great for me all day yesterday and today, been playing allot of music and it sound's great.
[T-Mobile, Samsung Galaxy SIII] nonmindo:
Random reboots after 3hrs stable on 4/7
[T-Mobile, Samsung Galaxy SIII] itzsmokey:
Everything running smooth since 4/5
[T-Mobile, Samsung Galaxy SIII] HarEllis:
looking to jump on cm10 for the updated kernel and my old rom is outdated is there a specific build that anyone would suggest? like mr2? or should i just get the latest nightly. thanks
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Newest.
[T-Mobile, Samsung Galaxy SIII] animefans:
I have seen more people commenting on 04/05 stability more than others

I don't jump to absolute latest nightly everyday, so I can't say how stable latest nightly is

As for myself, I am also on 04/05, and my previous one was 03/30
[T-Mobile, Samsung Galaxy SIII] darjama:
4/8 nightly is working nicely here. I did have a couple of in-pocket reboots with 4/5 and 4/7, and not right away, so we'll see how it goes with this one.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
4/8 has been stable and smooth all day today. Used for calls and BT audio on Play music pretty much all day long. Battery has been decent.
[T-Mobile, Samsung Galaxy SIII] zinite:
How can we get the dock audio fix pushed to our device?

https://github.com/cyanogenmod/andr...mmit/36c13a24f75a48265b79bec0a44017d1097edf7a
[T-Mobile, Samsung Galaxy SIII] Quiketaz:
4/8 Pretty Stable, I play ingress and no issues during the day.
[T-Mobile, Samsung Galaxy SIII] em2drvr03:
How is the Bluetooth audio streaming on the newer nightlies? Are all the problems fixed?
[T-Mobile, Samsung Galaxy SIII] zander21510:
4/7 is going nicely for me, only one reboot last night. I was typing a message on my eBay app and it locked up and rebooted
[T-Mobile, Samsung Galaxy SIII] ajm786:
Looks like M3 is coming soon.

https://github.com/cyanogenmod/android/commit/1d60f803f7dbc5b713abefe419efbe55851fbd9a
[T-Mobile, Samsung Galaxy SIII] cangri87:
Is anyone else having the jumpy screen issue also?

Ie: I'm on a page, phone scrolls to a diff position of where ever i am. Soon as i touch the screen it goes back to where i was at. :-/ hope I'm not sounding like a crazy person.
[T-Mobile, Samsung Galaxy SIII] gr4p3s:
You're not crazy, it happens to me on the Reddit Is Fun app a lot.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
This has been happening to me on Chrome and Tapatalk. Definitely thought I was going crazy :)
[T-Mobile, Samsung Galaxy SIII] stonew5082:
I've been getting that on my pdf reader too
[T-Mobile, Samsung Galaxy SIII] animefans:
same thing for me in 4/5 nightly as well
[T-Mobile, Samsung Galaxy SIII] meamgood:
I recently got a bluetooth speaker and went to the 4/5 update. So far, streaming bluetooth is perfect.

I have this issue too when using the BaconReader app, Google Reader and sometimes Chrome
[T-Mobile, Samsung Galaxy SIII] Batmensch:
From the 1st page:

"* 1 frame flicker when transitioning between overlay/gpu rendering."

I figured it was this problem. I'm seeing it with anything that does page-flipping type animations, like Kindle.
[T-Mobile, Samsung Galaxy SIII] munkyvirus:
I'm getting hardcore graphical glitches on 4/8. Ktoonz's latest, completely clean install. CPU overclocked lower than I what I had faux's kernel at.
[T-Mobile, Samsung Galaxy SIII] mulletcutter:
Also here, it will happen to me on wordon , the letter pieces will jump around.
[T-Mobile, Samsung Galaxy SIII] justin75:
Same here on chrome jumping around! Just thru on the 4/8 nightly.. Still doing it..
[T-Mobile, Samsung Galaxy SIII] ashokjadav:
4/8 nightly stable for past 24hrs now....
[T-Mobile, Samsung Galaxy SIII] zander21510:
I get it on 4/7 and ever since 4/3
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Dsp not working at all on 4/9

Edit: went back to 3/17 and it works but real wonky. I probably need to to a clean install to see what's really up with it.
[T-Mobile, Samsung Galaxy SIII] sswb27:
How about some logcat's for these wonky screens in case some of the dev's might need them.
[T-Mobile, Samsung Galaxy SIII] elesbb:
I just wanna comment that I went back to December 24th build

Couple build.prop tweaks, ktoonsez kernel. And not a single thing wrong. How did these nightly builds get so bad!?
[T-Mobile, Samsung Galaxy SIII] Batmensch:
Is a logcat worthwhile when there's no crash involved? I doubt that a low level graphics issue is going to generate much in the way of log entries.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
No need, think the Adreno revert fixed it.
[T-Mobile, Samsung Galaxy SIII] Batmensch:
I'm running 4/9, and I still have the page flickering problem. Is it something still to come?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
My post was in reference to the spazzing issue. Unsure of flickering problem.
[T-Mobile, Samsung Galaxy SIII] ajm786:
I just went back to 3/4. It's unbelievably bug free compared to any of the latest nightlies.
[T-Mobile, Samsung Galaxy SIII] munkyvirus:
The new kernel still has a lot of kinks to work out. A LOT. We're getting close to M3, so the bugs should be getting squashed pretty quick.
[T-Mobile, Samsung Galaxy SIII] eddylee09:
What kernel are you guys using on the 4/8 build? I just tried ktoonz but it got me trapped in a boot loop :(
[T-Mobile, Samsung Galaxy SIII] mdfritz:
They put out M1 and it was pretty buggy, I don't have my hopes up for m3. 3/1 thru 3/17 (including m2) was stellar in every respect until the kernel change. I was pulling 4 hours of screen time on each one of them with no glitches.
[T-Mobile, Samsung Galaxy SIII] bumsoil:
I have been on 3/6 since the night it came out. Tried a couple of nightlies since then and always go back. Been thinking about trying 4/8. But I may stick with this one.
[T-Mobile, Samsung Galaxy SIII] danielrod:
Does anybody know how to fix when sometimes the cLock widget says "no data" and never updates?
[T-Mobile, Samsung Galaxy SIII] ashokjadav:
i am on 4/8 for 2 days now...no issues yet....pretty stable..
[T-Mobile, Samsung Galaxy SIII] ajm786:
Ok, I've wracked my brains out over the past few days trying to figure this out. It's basically the same issue I've had since I got my phone on 3/5. I've tried every single nightly PAST M2, and it has this problem.

When you start playing music using an audio player (such as Apollo, Google Music, Android Music Player, Rocket Music Player) that uses the native audio stack thread, and then pause/play again, or simply browse away and click something else, like the app tray button, the audio horribly stutters. Any time anything else plays over audio, it will stutter. If you use an audio player that does NOT use the native audio stack thread, you don't get stutters (Poweramp, Winamp are perfect examples). The problem with that approach? You can't use CM's DSP; you have to use the respective app's internal equalizers.

What's got me worried is that the pops/stutters actually are so loud they sound/feel like they are going to damage the phone's speaker. If you put your finger up to it while it's doing this, you can actually feel it when the pops/stutters happen.

This does not happen on any nightly M2 or prior. Doing a brand spanking new clean install, straight off the bat, with no other apps installed (not even Google Apps), you can reproduce it; this rules out an app conflict issue. It's not an SD issue, because it does this even playing music off the internal SD.

Here's what I've done, all of which has made no difference. Clean install IN BETWEEN each step (full format and wipe of all internal storage, including data):

1. Clean install.

2. Removed DSP app.

3. Replaced DSP with Clear Audio.

4. Tried all sorts of different music players.

5. Tried all sorts of build.prop edits.

6. Tried all sorts of custom kernels.

Something is telling me that maybe it's the way TWRP formats the internal SD card? It uses EXT4SD or something like that. Maybe that's what's causing it?

I can post logcats if anyone likes, but I doubt that's going to catch anything, as it's not really an "error".

Can anyone help? I'd really appreciate it. Thanks.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
People have complained about audio problems for some time. Not sure why you suspect recovery could be the problem.

But your said it's fine with some media players. So use those. Sorry but no true fix exists yet.
[T-Mobile, Samsung Galaxy SIII] nmyron:
So, here's what I did. I backed up my SMS using Titanium Backup. I did a full wipe of EVERYTHING. System, Data, Data/Media, the works. I reinstalled cm10.1-20130406-NIGHTLY. After that, I no longer had audio glitches in Google Play Music or anything else when I tried to do something else while playing my tunes. But DSP Manager is still crap, and generates a ton of distortion when I try to setup an equalizer profile. So, again with Titanium Backup, I backed up and uninstalled Apollo, and DSP Manager. And I downloaded Equalizer from the market. On the onboard speaker and on my headset, it sounds much better. I have yet to test on my truck stereo yet though.

EDIT: a lot of the presets try to drive the low bass channels up WAYYYYYY to high in Equalizer. But that is easily adjustable in the graphical EQ. I'm testing now to see if I can create different EQ presets for different audio outputs (one for my headset, another for my truck where I have subs installed, etc).
[T-Mobile, Samsung Galaxy SIII] ajm786:
Well, looks like a logcat helped, after all.

What's happening is that while the audio is playing and you click something else which generates audio, this command is logged:

If you are on headphones:

D/ALSADevice( 251): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Headphones

I/ALSADevice( 251): a2220: txDevice=(null)rxDevice=Headphones

If you are playing over the speaker:

D/ALSADevice( 251): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Speaker

I/ALSADevice( 251): a2220: txDevice=(null)rxDevice=Speaker

These appear right when you hear the pops/clicks. Maybe someone can help us decode this.

Edit: Aha! And I see this error too! It shows up everytime you hear the errant pop/click/stutter.

E/ACDB-LOADER( 251): Error: ACDB AFE returned= -8

Thanks!

Edit 2: And this brings more light to the situation.

http://code.google.com/p/csipsimple/issues/detail?id=2126

As I stated previously regarding the audio threads, if you use an app like VLC which you can actively change what audio thread you are using (Java, Native, or OpenSL-ES), you will see what I mean. According to that thread, there is mention that Google changed something, which broke something the CM guys are probably not aware of (or maybe they are and we just don't know it).

I wish CM devs could read these posts, because it might be useful to help them hopefully debug/fix the issue. Unfortunately, they don't look at nightly bug reports. :(
[T-Mobile, Samsung Galaxy SIII] ganiman:
I was on stock/rooted. I tried the nightly from yesterday, and while I do love the features cyanogen provides over stock, stock is far more stable than this (I know it's a "nightly" but I figure this has been around for a long time). I've been running it for about 24 hours. Battery life is poor, some animations are stuttering, and I tried to use the camera once and it froze - now I get the "can't connect to the camera" message. I hate to go back to stock - touchwiz is ugly (however I do like a lot of the gestures it provides). These are a few things I've noticed so far. I've read back a few pages in this topic and I see a lot of people saying this rom has gotten more buggy than it was. Guess I will try out a couple others and see how they go, but I have to imagine anything based off cyanogen will inherit these things.
[T-Mobile, Samsung Galaxy SIII] Se7eN43:
Are you kidding me? If you are going to be running a nightly, do some reading first so you know what to expect and keep up with it. If you had, you would know that the new linux kernel (3.4) is quite buggy, which was merged a couple of months ago. Any bugs that are fixed CAN introduce new bugs. There's no need to rant about the rom in this thread. This is not a blog to review the rom either. So please, keep this thread clean by not giving your opinion on what you think of these nightlies. It does not contribute to anything.
[T-Mobile, Samsung Galaxy SIII] ganiman:
No, I am not kidding you. You cannot possibly expect each and every user to read through 1000+ pages of a topic to be kept up to date. It's actually quite useful to come in to a thread and have a "review" post once in a while, so people who might want to try out a rom know what to expect. I read through the last 10+ pages, and knew to expect some bugs, but none of what I described in my post. So get over your ego and don't take it personal. I've been running custom roms for many years and fully know what to expect from a nightly. This has been around for a looooooong time now, and no stable has been released for 10.1. There should be one by now. It's foolish of you to assume that I did no reading. Your post is more of a rant than mine was, and contributed even less to the overall development of this rom. If you want to help keep a topic clean, ignore the posts you don't agree with. Forums 101 man. If you wanted to reply and actually contribute anything, you could be polite and possibly even recommend a specific build or another rom which may have a better user experience, rather than being a douche. My thanks meter is 4 times that of yours, with half the posts. That should be some indicator I'm not a total retard.
[T-Mobile, Samsung Galaxy SIII] GenericAsianGuy:
Just to chime in and help you out (and others), CM 10.1 3/17 is a very stable build (I'm using it with BMS for 3.0.x kernels; Conservative/NOOP, 192 mHz and 1512 mHz).

In other news, CM 10.1 M3 was released today - http://get.cm/?device=d2tmo&type=snapshot
[T-Mobile, Samsung Galaxy SIII] effortless:
Has anyone been able to get M3 to boot? I get a black screen after the SIII Cid boot screen. Did an update first, then a clean install and same result.

*----> Got confirmation! I recommend against flashing the M3 release currently due to a bug with S3 phones, you'll end up with a black screen and you'll need to restore from recovery.

Repeat, do not flash M3 S3 release till they fix it.
[T-Mobile, Samsung Galaxy SIII] ashokjadav:
M3 not available to DL any more...may be after the fix it should be available...
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Animations are laggy with the 3.4 kernel that we first saw on 3/18. The camera has always seemed neglected to me, but I haven't had it freeze yet.

I'm most interested in your battery complaint. Battery life has been very good lately. Can I see some BBS stats?
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Delete
[T-Mobile, Samsung Galaxy SIII] javier180:
what a let down...Didnt even use it yet and I hear nothing but bad news. Well Hopefully they re upload it later today
[T-Mobile, Samsung Galaxy SIII] kaister:
Ever try Darth Stalker ROM? I'm currently running the X1 and so far it's been good since it's release. :) Still waiting for CM to get to a point where it is without bugs, seems it's going in the opposite direction lately! :(
[T-Mobile, Samsung Galaxy SIII] javier180:
and its back up!!
[T-Mobile, Samsung Galaxy SIII] darjama:
I've been having a pretty good time of it with the 4/10 nightly, disabling hw overlays in the dev settings seems to fix the flickering/scrolling display problems, although it seems to be at the cost of battery life. No crashes since flashing it over 24 hours ago.
[T-Mobile, Samsung Galaxy SIII] nmyron:
Have to agree here. I did a fresh build of 4/10, and have my phone all setup the way I always do, and have been up and stable for 14 hours thus far.

I've been off charger for over 6 hours and have dropped 40%. So battery consumption is a bit high, but, I have a ton of corporate email running through my phone.
[T-Mobile, Samsung Galaxy SIII] sabreful:
it's back up, and successfully flashed - no issues as of yet :)
[T-Mobile, Samsung Galaxy SIII] javier180:
so whats new in this build besides bug fixes? It feels really smooth!
[T-Mobile, Samsung Galaxy SIII] Se7eN43:
If you want to review, start it in the general discussion, not in development. What you wrote about was your opinion and bugs which have been known.The point is keeping threads clear of the clutter. This is why there are hundreds of pages to go through because of off-topic posts. Reviewing a nightly for others can be a good thing but keep in mind, device’s can behave differently. The best review would be for the user to try it themselves which is one reason why a back-up system exists. You can call this a rant but in all fairness, this needs to be clarified every so often because some members don’t know or just don't care.

On a side note, you have been here long enough to know name calling is uncalled for.
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Looks like a new experimental build
[T-Mobile, Samsung Galaxy SIII] sabreful:
sadly, a few hours later, I'm experiencing many random reboots on m3 :(

logcat linked to db if anyone is interested

http://db.tt/oDdPZBbG
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Just flashed m3, flashed lk 5.3.1-experimental kernel. This beast is BUTTER smooth! Doing my first full charge. KB seems a lot snappier.
[T-Mobile, Samsung Galaxy SIII] tropaios:
Installed M3, had 3 random reboots within 15 minutes.
[T-Mobile, Samsung Galaxy SIII] nicefella:
lol why did they change the kernel base in the first place? Things are way worse now :/
[T-Mobile, Samsung Galaxy SIII] c_brown93:
Installed M3 with full wipe and have zero issues so far. Running for two hours now. No audio skipping or issues. No RR or SOD at all. Butter smooth. Did you guys full wipe?
[T-Mobile, Samsung Galaxy SIII] javier180:
I didnt do a full wipe and only flash on top of nightly and its running smooth!

---------- Post added at 07:08 AM ---------- Previous post was at 07:03 AM ----------

I forgot to mention the audio issue still exist.
[T-Mobile, Samsung Galaxy SIII] c_brown93:
What audio issues are you getting?
[T-Mobile, Samsung Galaxy SIII] javier180:
The same one that everyone experiences.. When you touch anywhere or open an app the music stutters.
[T-Mobile, Samsung Galaxy SIII] mt3g:
not everyone...
[T-Mobile, Samsung Galaxy SIII] mulletcutter:
Yea, I'm not getting it either
[T-Mobile, Samsung Galaxy SIII] mofogx:
I hate to add to it, but I'm also getting the stuttering/clipping issues on M3. It seems to still be app specific, as spotify seems to be fine, but grooveshark and play music suffers. The issues were absent on 4/8 but returned on 4/12. Flashing to M3, and this ROM produces the same issues. I wonder what could be causing this.
[T-Mobile, Samsung Galaxy SIII] mulletcutter:
I only use Pandora And gmusic and either one of them doet
[T-Mobile, Samsung Galaxy SIII] mofogx:
That's cool, but more than one person is experiencing these issues. It's good that everyone reports whatever might be a problem, so that the devs can at least look into it.
[T-Mobile, Samsung Galaxy SIII] mulletcutter:
I'm not saying it's not a bug, I'm just saying that that is what I use with no problems.
[T-Mobile, Samsung Galaxy SIII] mofogx:
I think that what we should all do, rather than post "no problem here..." or "omg, it still happens," is to state the applications that are affected. At the very least, it will help developers narrow down the cause of some bugs. Just saying that there is or isn't a problem serves no one and does nothing to improve the software or the community.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Got a reboot on 4/12 while the phone was idle in it's holster.
[T-Mobile, Samsung Galaxy SIII] nmyron:
So, after playing around some today, I too experienced the audio glitch. I dumped a logcat to text, and tossed it up on Pastebin at the URL below.

http://pastebin.com/gSm0HQzZ

I did some prelim looking. And besides my Exchange service crashing pretty damn frequently (no big deal, it gets queued to restart), I noticed a METRIC TON of overlay glitches. These seem to happen every time I switch apps (long press home and pick different app) or when I pull down the notification tray. This is also when the bug is experienced.
[T-Mobile, Samsung Galaxy SIII] ajm786:
Guys, I did some extensive research on this. Look on this thread and see if you can match it up with the audio issues you're having (check your logcat).

http://xdaforums.com/showpost.php?p=40164970&postcount=10884
[T-Mobile, Samsung Galaxy SIII] mofogx:
Well, they're definitely going to look into it now, since this now affects the M3 builds.