yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I'm really not sure man.. I have a feeling this is something like deep in framework and system files and has something to do with how the drivers are handling the hardware/software accessing the hardware. Because phone calls seem to work fine, its just media over A2DP bluetooth that isn't working fine. this is leading me to believe its some kind of change that got merged that affected the drivers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I figured as much. Just thought I would throw the idea out there. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Hey man definitely try it out if you want to. I'm certainly no authority on this subject or developing in general whatsoever. I just threw my personal opinion out there, hell i could be 180 degrees in the opposite direction wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
26th you say?

here is something for you guys to try out.. paste this into audio_policy.conf

http://pastebin.com/raw.php?i=SfAFth8v

then overwrite the file in /system/etc/ with the one here. set permissions to 644 and reboot. see if a2dp is fixed.

i'm reverting a commit made by cyanogen on the 26th that is likely the culprit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
yes 12/26 nightly. also, ive heard that Task's AOKP 12/23 had properly working A2DP as well.

I just looked into the commit merged here.. http://review.cyanogenmod.org/#/c/29174/

looks like we found the same one. i will try your suggestion once i get back to my car with Root Explorer.:good:

I also found this one http://review.cyanogenmod.org/#/c/29175/ but i think the first one is where the issue lies

edit: is there anything wrong with just copy/pasting that into the existing audio_policy.conf using Root Explorer on the device and rebooting?

Also, whats wrong with just adding this back in to the appropriate place, so it will have a2dp, lpa, voip, and usb in the audio_policy ?

lpa {	32
sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000	33
channel_masks AUDIO_CHANNEL_OUT_STEREO|AUDIO_CHANNEL_OUT_MONO	34
formats AUDIO_FORMAT_PCM_16_BIT	35
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AU
DIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_ALL_A2DP|AUDIO_DEVICE_OUT_A
UX_DIGITAL|AUDIO_DEVICE_OUT_PROXY|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_ALL_USB	36
flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_LPA	37
}	38
voip_rx {	39
sampling_rates 8000|16000	40
channel_masks AUDIO_CHANNEL_OUT_MONO	41
formats AUDIO_FORMAT_PCM_16_BIT|AUDIO_FORMAT_AMR_NB|AUDIO_FORMAT_AMR_WB|AUDIO_FORMAT_QCELP|A
UDIO_FORMAT_EVRC|AUDIO_FORMAT_EVRCB|AUDIO_FORMAT_EVRCWB	42
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AU
DIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_ALL_USB	43
flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_VOIP_RX	44
}	45
tunnel {	46
sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000	47
channel_masks AUDIO_CHANNEL_OUT_STEREO|AUDIO_CHANNEL_OUT_MONO	48
formats AUDIO_FORMAT_MP3|AUDIO_FORMAT_AAC|AUDIO_FORMAT_AMR_WB|AUDIO_FORMAT_AMR_WB_PLUS	49
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AU
DIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_ALL_A2DP|AUDIO_DEVICE_OUT_A
UX_DIGITAL|AUDIO_DEVICE_OUT_PROXY|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_ALL_USB	50
flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_TUNNEL	51
}	52
#fast {	53
# sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000	54
# channel_masks AUDIO_CHANNEL_OUT_STEREO	55
# formats AUDIO_FORMAT_PCM_16_BIT	56
# devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|A
UDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_ALL_A2DP|AUDIO_DEVICE_OUT_
AUX_DIGITAL|AUDIO_DEVICE_OUT_ALL_USB	57
# flags AUDIO_OUTPUT_FLAG_FAST	58
#}
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoachForLife:
I completely agree. Although I hope CM works this in.

On a related note, is there a feature request anywhere? Or do the CM guys monitor this thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Just tested it. This is worse: it completely breaks bluetooth streaming and the phone just locks up. That was the issue prior to the 26th which is probably why that commit was made to resolve that issue.

DO NOT revert that commit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
it seems it's either the audio policy or the switch to audio-caf that caused the break for our device.

root explorer? never used that for development but you're free to try. i just do stuff in cli with adb.

i didn't get your second question

what do you mean what's wrong? we're trying to figure that out :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
just saw your post. do you know which build A2DP worked on ? is it definitely the 12/26 ?

haha "whats wrong" meaning like, should i use what you provided or just copy/paste the code that was removed from the original audio_policy.conf from 12/26 (what i put in the code tags above)?

(i already copy/pasted that code and creatd a new audio_policy.conf file using TextWrangler on OS X)

i kind of asked the same question twice. I will be out of class soon and will be able to test.

what encoding do i want with TextWrangler (like the mac version of Notepad ++) for the new audio_policy.conf file unicode utf 8?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
i thought the build of the 26th worked fine? :eek: It's that time frame that I'm looking into.

just copy paste my file in. I already reverted that commit.

You might want to hold off though given that one user is reporting a lockup with my file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Disabling HW overlay makes this issue go away. This issue is specific to this device because I tested on CM10.1 nightly on my Nexus 7 and it works fine.

I know there were some HW overlay issues with CM10.1 on the i747. Is there a dev looking at this please? (Otherwise this so-called "development" thread is rendered moot)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Yes I saw that post after I responded to yours right before I applied your file. I was looking into 12/26 as well.

Over in tasks thread someone commented that Tasks 12/23 has properly functioning A2DP. Could we possibly look in that as well ?

Once I'm home from class in about 30 minutes I'll be able to hit this head on

If you'd like add me on gtalk maybe we can figure this thing out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
I only added in the a2dp output to audio_policy.conf and the streaming works. However it is bass-less still. I speculate the resolution to the lack of bass is in some underlying driver code. Again, all speculation without being able to build CM myself. Need to get my dev & build environment set up quickly... wish I had more time.

Here's my audio_policy.conf that works but is bass-less.

---------- Post added at 03:24 PM ---------- Previous post was at 03:20 PM ----------

Update: I then placed a call and got the following looping in my logcat:

I/audio_a2dp_hw( 246): start_audio_datapath: state 3
D/bt-btif ( 1286): btif_av_stream_ready : sm hdl 1936829912, state 2, flags 2
D/bt-btif ( 1286): btif_av_stream_started : sm hdl 1936829912, state 2, flags 2
D/bt-btif ( 1286): UIPC_Send : ch_id:0 1 bytes
E/audio_a2dp_hw( 246): start_audio_datapath: audiopath start failed

After that, audio streaming worked perfectly with bass and no distortion.

If you guys want to start a Google+ hangout then I can join and help troubleshoot this. Of course, I think one of us would need to be able to look at underlying framework/hardware code and be able to build CM. Does either of you have that capability at this time?

Update 2: Never mind. It still gets distorted after a while and speeds up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
There are no actual CM devs on this forum.. there has never been any type of "development" either. Closest we got to that was when the RIL issues were fixed. No matter if this can be fixed by the CM team, it is still an upstream issue within AOSP source. As multiple 4.2 devices have the exact same problem. If CM hasn't fixed it by now, than there must be something critically broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Well here's the controversy, it worked on 12/26 nightly and on tasks 12/23 release. So it isn't necessarily an upstream aosp issue. It could be something merged that broke it. We just can't figure out what
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
I'm not disputing that it can't be fixed without an Android update as a whole.. I just do not think it will be able to be fixed till that release happens. I don't use A2DP regularly so this does not affect me one bit. All my assumptions are just based off everything I have been reading on the issue. A2DP was pretty broken on CM 10 until pretty much 10.1 came out also..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
ding ding ding... we have a winner. ^^^^^^ (most important marked in BOLD)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
haha yea dude, that's why im setting up a build environment right now to look into this for real. i probably wont find anything but hey, it'll be a good learning experience right? :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Fact: Bluetooth worked on Dec. 26th... and did not work from the 27th on. So if you and I are smart enough to figure out the probability that something done on the 27th broke it.... don't you think that the guys that write the code are?

Obviously something was done that HAD TO BE to further the development of 4.2. Our choices are to live with that until its fixed, or use a ROM from before the 27th and live with that.

Edit: On the 28th on before were the data problems on CM10.1, or it would be a pretty easy call for those who need their Bluetooth. Illusion 12/27 (was built 1AM) works but data is a b!tch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
Your best bet might be to use a 12/26 and new build and start reverting audio and Bluetooth related items back to those from the 12/26 build and see if anything works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I think you guys are forgetting something. Working A2DP does not mean that Bluethooth was perfect before the 26th. Every 4.2 ROM had a problem with it upon disconnection. Bluetooth has never work 100% correctly on 4.1 or 4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
proof problem ain't from upstream:

http://www.mediafire.com/?915m3l58439zrz8

a2dp works on this one.

what did i do ? a lazy job of reverting both qcom-common and d2-common to the 26th (before the migration to the audio-caf mess). my headphones are blastin' with bass as we speak.

not sure if the 26th's copy has any device specific bugs.. they'll probably be here if there are any.

enjoy til we dissect and figure out the exact culprit is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
trying this out now man. did you use ubuntu or mac?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
arch

i have the entire thing setup already as I'm actively contributing to bring cm to the note 2 lte.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
This should be asked in Q&A.. General discussion is no longer allowed. Your question will not be answered here.. (No for me)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
The last few pages of this thread are the exact reason this thread exist. I love it guys. Jeep up the good work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
If I could give up all my thanks points on this post, I would. Works great for me. You just made my day better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
thanks man. comments like that make my day too :) Glad to help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
WOW, are you kidding!? So this is a Jan 15th build with your listed changes? Are you a god? (just saw the Avengers)

WORKS FOR ME!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
No, yes, and YES.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Where have you been?

Dude! Many Thanks. I am just wondering where have you been all this time? :highfive: I hope CM Team take your edits and incorporate them in all upcoming nightlies from now on :cowboy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
I haven't tested this yet, but great work! You still didn't answer the question: Ubuntu or Mac? I'm trying to set up a build environment myself...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I will give this a shot, I'm still on LH1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
He said he's using Arch Linux. https://www.archlinux.org
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
I am on M2 (4.1.2) build and, BT works perfect, so does AVRCP and Message profile, if you are a heavy BT user (like myself) M2 is the best built i think Everything works on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FlounderFX4:
Great work. Just saved me throwing the whole phone in the garbage. Downloaded the source myself to do this, but much happier that you completed it first. Many thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
So I went on the cyanogenmod website to see the change logs for my at&t and im not finding it I have checked the bbqlog. Where else can I see the change logs. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deamonix:
Try here: http://mobile.10.1.cmxlog.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Thanks man..:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Altaman:
Humm maybe you can get photosphere working too ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Just had to thank you and confirm for anyone wondering. I've been personally streaming music via a BT headset using Pandora for 20+ minutes and it sounds exactly as it does coming from TW. You sir have won the internet for today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
The sound quality however is not on par.

Edit: maybe I'm smoking crack :confused:. Sounded better on the way home
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drdingo21:
You sir. Are a god among men.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I'm not in my car, but using the same BT headset I listen to music every day with, it sounds about the same. This is 90% of how I use it so i'm just happy I can flash to a cm build with working bt music stream.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
Sound quality was great through Ford Sync. :confused: what a2dp device are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SomethingAwesome:
Just updated from the Jan 11th build to the Jan16 w/Bluetooth fix. Working perfectly so far.

Call quality improved drastically for me, and having working Bluetooth is awesome.

Thanks to everyone for their hard work!

Sent from my magical SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
GT-R and PowerAMP. Treble seems lower quality. Im confident this will be fixed and at least there are alternatives.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
At the same time when this happens Chrome is broken as well: try the tab button and see if you can get out of that tab listing mode (or whatever it's called)...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
Chrome tab listing works for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Thanks madmack! I don't suppose you could build a 0117 build with your BT fix, could you please?:o I'd love to see BT working again, but 'm already on 0117, and don't feel like flashing back to an earlier version...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
The changes are minimal between 1/16 and 1/17. It wouldn't be worth his time. It would be more reasonable for him to do one once a week if CM doesn't get it fixed. Just flash back. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Exactly. I have no idea the extent of things that were changed to make this work but IF it was some how possible, making a separate file to flash the changes made over the current nightly may be able to help. Again, I have 0 clue as to what was changed and this may not even be applicable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Miracast?

Does anyone know if we are ever going to get Miracast support? The System, Display, Wi-Fi option is there, and I can start a pairing with my PTV3000 but it does not work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerojay:
A .diff of the changes from the guy that made that build with all his changes would be appreciated so that if he can't maintain it, someone here in the community can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ouija147:
that did it

Thank you sir!

and thanks button hit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
I'm working on syncing the CM Repo today. Once I get my setup going, I will attempt to duplicate his fix and will maintain the fix once per week unless there is a large change if I succeed. Or I will make a flashable package if possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I'm still using the 9th. Is it worth updating it to the most recent one? What are some differences/improvements that I will notice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
He said exactly what he did. He's using the old d2-common and qcom-common repos to build instead of the newer ones where the audio-caf came into play. You can just compare the two of each of those repos as your diff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Many thanks! Please let us freeloader bums know when your patch/ROM is ready...:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
The changes are known to those who know what he did. And he has already noted what that was. So your post was taken care of before you posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Madmack build - best battery life I've seen

Ok, this makes no real sense that I can think of but on this build, I'm getting the best battery life I think I've ever seen.

Today on idle, I'm getting 3-4 percent/hour drain vs. 5-6 percent which was the best I ever saw before. This is despite the fact that "Google Services" is still chewing up 50% of the drain.

So weird.

Madmack, can you just post about 10 posts here so I can thanks them all? :) Maybe I'll just start digging through the history.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
haha. ok, you can thank this one :)

No special magic went into that build but happy you got good battery life.

Just to shed some light on what is happening here: Being a nightly really means bleeding edge. The devs moved to the new audio drivers on the 26th even though they're really unstable compared to what we had running before. My copy simply reverts and uses the old stable drivers. You should really expect hiccups like that as the nightlies evolve.

I'm not going to bother to try to fix the audio-caf drivers mainly because I'm no audio driver expert and I don't have that much time :( I'm sure some talented minds are already working on it. I'm pretty happy with the build I posted earlier personally :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah, I completely understand about the battery, and it makes sense that you weren't looking at that at all, which just makes it weirder that it's the first time I've seen an improvement. I also understand about the nightlies. I've been a nightly flasher (ha) since Galaxy S Captivate had a build available.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Out of curiosity, what exactly was "broken" by reverting back to the old drivers with working A2DP? I'm setting up a build environment now, I want to look into this pretty heavily tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
How can I stop Google Services from using this battery?

Screenshots taken after 2 hours of non-use. Idle on wi-fi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
If I know what was broken, I would've fixed the new drivers instead of reverting back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Turn off Google now. Go to maps disable location reporting and location history. This maybe your problem. Also get the app Autostarts from play store and disable everything under maps including hidden entries.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
35+ minutes of wakelock in two hours, 25minutes for Network locator. I've never really looked into it, but does Google Now really check the location of the phone that often while idle, or are you running something else that is checking your location?

Either way, 25minutes of wakelock in two hours for checking location seems very excessive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
"Google Now" was already set to off. I'm a huge fan of autostarts. Been so for a long time. Thanks. I'll dig around for anything I can find in there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nyamoV2:
i asked in the Q&A but not getting an answer so i'm asking here as well. is the random lag after exiting apps (mostly games) gone? it used to require a reboot to fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
No, it's not gone. Still here. But it doesn't require a reboot to fix it, a simple screen lock & unlock does the trick just fine.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
If u have mac osx i can help you out.. I personally havent synced 10.1 but i do have working 10.0 with osx lion... And when i have time sync 10.1 is it not compiling?

trolol and awayyy!! Expect typos this is my phone.

running ultimatum, cm built by me, other cm if im lazy, or task if im adventurous and bored. also hit the thanks because u can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RazKidd:
All you gotta do is flash the rom and your fine right? Or is there something you can do wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
What are you coming from? Full wipe (Data, System, Cache, and Dalvik Cache). Flash ROM (Make for sure its the d2att one), flash GApps (12/12/12). Good to go. Search before you ask if you run into issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Post your question here or in the Q&A forum please

---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------

Get a logcat and post it here. See my post regarding a similar issue which might be what you're experiencing. Also, in Developer options is HW overlays disabled?

BTW, I also replied to your question in the Q&A thread. But if you can get a logcat then this thread is the right place to post this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoked:
Dirty flashed from the CM10 Dec 16th to madmack's BT fixed build but think I flashed the wrong gapps. Anyhow, a few uninstall and reinstalls of google apps and things seem to be good now. My Handsfree BT issues seem to have been solved but I was only in the car for 10min so it may be too early to tell.

I don't know if it's me, but for some reason it seems like the widgets seem to fit smaller on the homescreens than CM10 did.