yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] matthew4295:
Hey Google Now (voice) isn't working and neither is any other sort of mic dictation software. What's this "Mic Fix"? I can't find the actual fix anywhere.
[Verizon Samsung Galaxy S III] Restola:
Would a stock rom that is rooted not work?

http://xdaforums.com/showthread.php?t=1941334
[Verizon Samsung Galaxy S III] pinhead875:
I really want to try CM10.1, but I play Ingress so I need a super solid GPS lock. It looks like it's getting there, I'm definitely watching this thread.
[Verizon Samsung Galaxy S III] mastamoon:
Here is my 01/07 build.. http://d-h.st/lgo Repo Sync as of ~3pm EST.

CherryPicks:

http://review.cyanogenmod.org/#/c/28195/

http://review.cyanogenmod.org/#/c/29349/

http://review.cyanogenmod.org/#/c/29653/

http://review.cyanogenmod.org/#/c/29654/

Check out http://review.cyanogenmod.org/#/q/status:merged++branch:cm-10.1,n,z to see what my merges my repo sync may have missed!

Enjoy.
[Verizon Samsung Galaxy S III] iofthestorm:
Would anyone happen to know why /proc/last_kmsg does not seem to show up after hot reboots? It used to a while ago and now it doesn't, does that just mean my reboots are 'special' or is it disabled in the kernel?
[Verizon Samsung Galaxy S III] AkumaX55:
Video Chat

So i am currently on 1/6 and i was attempting to make a video call and i get an camera error when trying to use gtalk or google+ hangout. So wondering if others are having the same issue or if i am the only one.
[Verizon Samsung Galaxy S III] nh5:
Got a friend with a VZ GS3, put CM 10.1 on it. His video calling works but mic on his phone does not work in Google Talk. So no voice in voice or video call.
[Verizon Samsung Galaxy S III] tonu42:
For those wondering, I couldn't find it by searching here. But the built in wifi tether WORKS. ONLY if you set the security to open. I enjoyed unblocked sites on my tablet at work today, was rather enjoyable to see it working on 10.1 again.

(wifi-tether) (wifitether) [makes it easy to search thread now listing it differently]
[Verizon Samsung Galaxy S III] M Diddy:
Masta,

Here's some to add:

http://review.cyanogenmod.org/#/c/29661/

http://review.cyanogenmod.org/#/c/29660/

Sound fixes.

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

GPS is fine in 10.1. I've never had one issue and lock is instant. The radios are another story, but have gotten much better as of late.
[Verizon Samsung Galaxy S III] M Diddy:
W00t! Looks like these were merged today along with some other audio fixes.

Masta,

A repo sync with the for RIL patches would be baller right now! :D
[Verizon Samsung Galaxy S III] mastamoon:
It shall be done... :cyclops:
[Verizon Samsung Galaxy S III] Stupifier:
Bah, no Bluetooth audio fix
[Verizon Samsung Galaxy S III] mastamoon:
Here is my 01/08 build.. http://d-h.st/TMm Repo Sync as of ~2:55pm EST. In-call volume adjustment works!

CherryPicks:

GPS:

http://review.cyanogenmod.org/#/c/28195/

RIL:

http://review.cyanogenmod.org/#/c/29349/

http://review.cyanogenmod.org/#/c/29653/

http://review.cyanogenmod.org/#/c/29654/

http://review.cyanogenmod.org/#/c/29100/

Check out http://review.cyanogenmod.org/#/q/st...ch:cm-10.1,n,z to see what merges my repo sync may have missed!

Enjoy.
[Verizon Samsung Galaxy S III] trixnkix637:
Since the 1/6 nightly I've been experiencing screen flickering from hell. It's been almost constant. I found a fix by disabling the HW overlay but it works only temporarily. Any clues to what causes this or what I can do for a more permanent fix?
[Verizon Samsung Galaxy S III] mastamoon:
I see 0 flicker. I'd say it's time for a full wipe/reinstall.
[Verizon Samsung Galaxy S III] tpayne2345:
No flickers here also.. I have however experienced 4 random freeze+auto reboots in the past 24 hours, even after upgrading from 1/6 build to 1/8
[Verizon Samsung Galaxy S III] cvo515:
Mastamoon , after setting up your latest...all seems good. But after reboot the mobile network switches to NV away from SIM. Switching back and toggling airplane mode and alls good. Just a heads up. Haven't tried a call yet. Thanks for your work
[Verizon Samsung Galaxy S III] rampantandroid:
Is there any way to tweak the vibrate strength of the keyboard? I'm finding the default setting is far too weak for my taste.

Thanks!

EDIT: FOUND it. Vibrate duration. Win!
[Verizon Samsung Galaxy S III] osuron07:
I doubt it for stock.. do you need it to rock your world or something? lol
[Verizon Samsung Galaxy S III] rampantandroid:
Language and input, AOSP keyboard, advanced options, vibration duration. It was set to 5ms which I barely felt. I set it to 70 for now, which is about where Liquid Smooth felt like it was, and more like what my iPhone offered. Now if only my radio connection was more reliable.
[Verizon Samsung Galaxy S III] Lastb0isct:
I just flashed 10.1 over my 10 cm build. Everything works great, but I am getting flickering. Is mastamoon correct that a full wipe/flash will solve this problem?

Thanks
[Verizon Samsung Galaxy S III] Stupifier:
Yes
[Verizon Samsung Galaxy S III] yznhmr:
Any one know what was the last version that BT and call volume was working? (of 10.1) or if thee is a tweak to fix either.. thanks
[Verizon Samsung Galaxy S III] PVLMTREE:
20120109 is by far the best NIGHTLY yet. Up to this point, there was many fixes coming off the 01/05 build, so I decided to do a full wipe. I'm loving the new minor features and improvements the CM team implemented.
[Verizon Samsung Galaxy S III] NegativeOne:
How is Bluetooth audio in the latest build?
[Verizon Samsung Galaxy S III] BlazingGlory53:
Bluetooth may be broken. I think there's issues toggling on and off... it froze up on screen off and i had to do battery pull
[Verizon Samsung Galaxy S III] NegativeOne:
yes, that is one of the problems. also the actual playback has been broken for some time
[Verizon Samsung Galaxy S III] craigbailey1986:
After I did the battery pull from initially turning on Bluetooth it has been smooth sailing for me. Are you referring to music playback?
[Verizon Samsung Galaxy S III] NegativeOne:
Yeah. Have you tried that?
[Verizon Samsung Galaxy S III] jb_alphamale:
Yeah. Bluetooth playback is broken. I have no problems with toggling though.
[Verizon Samsung Galaxy S III] craigbailey1986:
Yeah its borked here as well...Lol... Guess I better break out the headphones..
[Verizon Samsung Galaxy S III] NegativeOne:
Ugh. This is for my car. For some reason my phone doesn't like my aux hook-up. I get crazy whistling noises. It's only my phone in my car. Other phones work fine, and my phone works fine in other cars. Seems like both the d2 and my car are poorly grounded. Switching to BT audio was the cheapest solution to fixing it, haha.
[Verizon Samsung Galaxy S III] mavness:
Is there an ETA for the com.android.phone crashing fix? Im sure it goes without saying that the phone working is a top priority since this is my...phone... hahaha :) Thanks!
[Verizon Samsung Galaxy S III] bobby janow:
Yes sir. The eta is as fast as you can go to the phone app, clear data and reboot.
[Verizon Samsung Galaxy S III] mavness:
As great as that is, I dont realize its not working until I have already missed a call due to the bug. So missing calls 10+ times a day is not really an option for some people. But thank you for the quick fix, I was rebooting into recovery and clearing things that way.
[Verizon Samsung Galaxy S III] bobby janow:
That happened to me a few builds ago. By clearing the data in the phone app there was no need to go into recovery, I merely needed a reboot. At that point it never happened again and no calls were missed. Am I missing something? What exactly happens?
[Verizon Samsung Galaxy S III] PerCompLLC:
When it happened to me, I didn't even need to reboot after clearing data on the phone app... Afterwards no missed calls and no FCs.
[Verizon Samsung Galaxy S III] soapinmouth:
Ive never had this issue, try a clean install.

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] lohp75:
Rule #1 never ask for an ETA

Rule#2 never ask for an ETA

Rule #3 never ask for an ETA
[Verizon Samsung Galaxy S III] rothnic:
Yeah bad timing for me trying these new builds. New to me car and was finally getting around to installing a bluetooth head unit last night after somehow living without it for a few months, and I run into these issues.

For me, it initially worked perfectly. Then I went to try a call with the voice command and it locked up solid. Pulled battery, and then afterwards it started the crackling noise that sounds like it is extremely low bandwidth. This morning I tried with the 1/08 unofficial nightly and got the crackling, low volume output. After switching between pandora and spotify a couple times, it worked "normally" for about 1 or 2 songs. The only thing was now my subwoofer (2 x 6.5" subs in a 2001 honda insight, woo woo) was getting very little to any low frequencies. When I leave the car the screen is non responsive, and required a battery pull.

So summary of issues are locking up when disconnecting or voice commands, intermittent crackling, and narrow bandwidth audio.

So, it looks like I'm going to downgrade back to 10 for now.
[Verizon Samsung Galaxy S III] NegativeOne:
Well I dunno if it's fixed now but CM10 had some bt audio problems too with "tinny" audio (no low frequencies). PM me when you try it and let me know if it's fixed now. I might downgrade as well.
[Verizon Samsung Galaxy S III] Restola:
Is there an ETA on when we'll be able to ask for an ETA?
[Verizon Samsung Galaxy S III] rothnic:
Will do. Been digging through gerrit to see what is going on with it. It looks like during MR1 staging that audio_policy.conf was changed substantially from the CM10 version. I assume this is because of some significant changes.

I'll add in any relevant commits in regard to bluetooth here:

Enabling bluetooth in MR1: http://review.cyanogenmod.org/#/c/27516/

10.1 audio_policy: http://review.cyanogenmod.org/#/c/27344/

Updated 10.1 audio_policy: http://review.cyanogenmod.org/#/c/29174/

It looks like something in regard to HAL audio. If it was working before in nightlies, I'd bet it stopped working on Dec 26th.

JB audio_policy abandoned in regard to bass:http://review.cyanogenmod.org/#/c/26614/

http://review.cyanogenmod.org/#/c/26615/

On another note, I came across this: http://review.cyanogenmod.org/#/c/29661/

Should of fixed the echo during speaker phone usage. No wonder my wife always complained.
[Verizon Samsung Galaxy S III] lohp75:
That's funny! ETA'S have been a rule not to ask for since cm's conception which I've been with lol.
[Verizon Samsung Galaxy S III] mastamoon:
Here is my 01/09 build.. http://d-h.st/c4N Repo Sync as of ~3:30pm EST. May have borked in-call volume adjustment by trying to increase in-call volume a bit. Dont install if this matters to you.. phone still works fine.

CherryPicks:

GPS:

http://review.cyanogenmod.org/#/c/29349/

RIL:

http://review.cyanogenmod.org/#/c/28195/

http://review.cyanogenmod.org/#/c/29653/

http://review.cyanogenmod.org/#/c/29654/

http://review.cyanogenmod.org/#/c/29100/

http://review.cyanogenmod.org/#/c/29669/

Bluetooth:

http://review.cyanogenmod.org/#/c/29952/

http://review.cyanogenmod.org/#/c/29951/

http://review.cyanogenmod.org/#/c/29950/

Check out http://review.cyanogenmod.org/#/q/st...ch:cm-10.1,n,z to see what merges my repo sync may have missed!

Enjoy.
[Verizon Samsung Galaxy S III] lxetuo:
Does this fix Bluetooth audio playback?
[Verizon Samsung Galaxy S III] pinhead875:
Try it and let us know?:confused:
[Verizon Samsung Galaxy S III] rothnic:
I'll try it out, but highly doubt it will fix the issues. The problems with bluetooth right now are with A2DP and decoding the audio. It seems to be selecting the wrong sample rate or something. I played with it some more on the way home. It seems to be playing at a low bitrate, but is decoded correctly for about 10-20 seconds. Then it seems to switch to the wrong sample rate and you get the distorted, low bitrate audio. If you pause the music for more than 5 seconds, then restart it, it does the same thing again.

MAP is for exchanging discrete messages. Setting up permission to exchange data, providing text messages, etc.
[Verizon Samsung Galaxy S III] NegativeOne:
it might, actually....
[Verizon Samsung Galaxy S III] bobby janow:
Actually what? Break in call volume or fix BT audio streaming?
[Verizon Samsung Galaxy S III] Restola:
In call volume still works for me on this build.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] mastamoon:
Good, I wasn't sure as I was only able to test by calling my work Voicemail lol.

Sound any louder?
[Verizon Samsung Galaxy S III] ming3r:
BT Streaming not fixed. Still static.
[Verizon Samsung Galaxy S III] pavigil:
Will this ROM work if I unlock my phone to work with AT&T?
[Verizon Samsung Galaxy S III] Restola:
Nope, no more than yesterday's.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] rampantandroid:
Can I just say thanks not only for the builds but also for telling us what's in them? :D
[Verizon Samsung Galaxy S III] kyuubi08:
The chronus app doesn't change when I tell it to display weather or calendar events
[Verizon Samsung Galaxy S III] mastamoon:
Delete and re add?
[Verizon Samsung Galaxy S III] masri1987:
mastamoon, running your 1/9 build, is low incall volume still prevalent, or am i the only one?
[Verizon Samsung Galaxy S III] mkasick:
The other relevant commit here is the switch to the caf audio hal from the AOSP/mako hal. The caf hal is more featureful (supports LPA) than the AOSP hal and is the closest to what we shipped in 10.0.

So the story here is that AOSP forked an earlier version of the caf hal we used in 10.0 in order to support the Nexus 4 (mako), which is the first Snapdragon-based Nexus device since the Nexus One. Code Aurora then rebased their hal on AOSP's fork, adding back in their features, but in doing so dropped other features we still require. Anyways we decided to switch to caf's hal so that we wouldn't have to modify the AOSP one used by mako and possibly introduce bugs on that device.

However, in reality the final hal is caf's + some parts ported from AOSP + other parts ported from CM 10.0. Needless to say it's been a bit of a messy transition but we're working things out as we can.
[Verizon Samsung Galaxy S III] theahlenius:
I'm on the latest nightly build, and it if I try to text it says "service not activated on network". Phone calls also just force close. I have data, and my network mode is on LTE/CDMA/EvDo, and my CDMA sub is set to RUIM/SIM.

This has been an issue on and off with different nightly builds. Any suggestions or just keep going back to ones that I know work? I see the dialer force close is a known issue (I think).

Update - After about a half an hour I tried again and both calls and sms are working. No idea what changed.
[Verizon Samsung Galaxy S III] Zacharybinx34:
In call low audio volume is fixed for me! Now just need the Pandora fix, and the 4g more stable/better signal, wpa for tethering, Skype feed back fixed, and this is solid! Keep up the good work.
[Verizon Samsung Galaxy S III] PerCompLLC:
Pandora fix? What's wrong with Pandora? Works perfectly for me on the current nightly...
[Verizon Samsung Galaxy S III] NegativeOne:
It was fixed but you sometimes need to clear data on pandora and on apollo to make it go.
[Verizon Samsung Galaxy S III] rockerrock:
Latest build 1/9/12 my Sandisk 64GB microsd reports "Sd card damaged". Tried formatting multiple times, CM10 simply fastboots. Works perfectly fine in my stock Note 2.
[Verizon Samsung Galaxy S III] NegativeOne:
Would it be at all possible to branch some builds with all of the latest things but the AOSP/mako hal? This would allow people who need the features that this change breaks to continue testing other things. For instance, I am still on old nightlies because I absolutely need the a2dp to work. I know it's a lot of effort to maintain two sets of builds like this, but I think there are a lot of people in the same boat.

edit: also, to clarify - The changes were applied on the 26th, so they would show up in builds no earlier than 12/27
[Verizon Samsung Galaxy S III] grin0048:
Perhaps Masta would like to tackle pulling that stuff out in his "afternoonlies" :) Just a thought...it certainly would add another bit of complexity over just building what's merged with a few cherry picks.
[Verizon Samsung Galaxy S III] mkasick:
Should be. One would have to revert these commits:

device/samsung/qcom-common: 22a9c684bf73187f07b740955a4d2c362e74f943

device/samsung/d2-common: e7ecaaac0b74dbb80a535f1d931c487b5989d1f6

and do a clean build. That should result in all "on device" audio working, but not USB, and I have no idea about A2DP.

Furthermore, while I don't think we're going to go out of our way to break support for the AOSP hal, we're not actively testing with it anymore (except when used for debugging regressions, which is why I know this much works). Inevitably we'll end up making commits that break compatibility with it further, but hopefully for the sake of resolving the remaining issues with the new hal.
[Verizon Samsung Galaxy S III] PerCompLLC:
I actually had to clear data on Apollo when I moved from the build prior to the LPA code being merged. But that was all that it took. And I've never had to do anything since. Just lucky I guess. :)
[Verizon Samsung Galaxy S III] mastamoon:
I'll give it a try today.

---------- Post added at 01:10 PM ---------- Previous post was at 01:00 PM ----------

also, USB dock audio doesnt work if that is what you are talking about, so seems like a no brainer.
[Verizon Samsung Galaxy S III] yznhmr:
Does Audio BT work in your build?
[Verizon Samsung Galaxy S III] mastamoon:
Here is my 01/10 build.. http://d-h.st/Xty Repo Sync as of ~1:20pm EST.

CherryPicks:

GPS:

http://review.cyanogenmod.org/#/c/29349/

RIL:

http://review.cyanogenmod.org/#/c/28195/

http://review.cyanogenmod.org/#/c/29653/

http://review.cyanogenmod.org/#/c/29654/

http://review.cyanogenmod.org/#/c/29100/

http://review.cyanogenmod.org/#/c/29669/

Bluetooth:

http://review.cyanogenmod.org/#/c/29952/

http://review.cyanogenmod.org/#/c/29951/

http://review.cyanogenmod.org/#/c/29950/

Reverted Commits:

as per this post: http://xdaforums.com/showpost.php?p=36540574&postcount=926 I reverted those 2 commits to see if this would fix bluetooth audio, or atleast get it back to where it was in mid-december.

Please test and post your results. I don't have any Bluetooth devices to test with so your info is key.

Check out http://review.cyanogenmod.org/#/q/st...ch:cm-10.1,n,z to see what merges my repo sync may have missed!

Enjoy.
[Verizon Samsung Galaxy S III] rmcomer:
Mastamoon, I just installed your 1/10 build and I can confirm that music is finally streaming over Bluetooth to my PC without glitching out after a few seconds. First build in a long time that has been able to do this. I've been streaming for over 10 minutes without any problems. I even received a call and music paused and resumed after I hung up. BTW there was no call delay when I answered the phone either!
[Verizon Samsung Galaxy S III] PerCompLLC:
Well that is certainly encouraging! Based on what you said, I just went out to where I get a better 4G signal and downloaded it. Installing now...
[Verizon Samsung Galaxy S III] soapinmouth:
Awesome!! Thanks masta, downloading now :)

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] eman3316@optonline.net:
Has the low video recording volume been fixed yet? Looks like that is all that's needed to make this my daily. Although multi-window is pretty cool on TW. I am itching for some AOSP though.

Also, which is the latest gapps?
[Verizon Samsung Galaxy S III] grin0048:
Issue with the A2DP static is gone for me as well. :good:

Still 12/12/12
[Verizon Samsung Galaxy S III] yznhmr:
mastamoon you ROCK>>>>> :good::good::good::good::good:

BT MUSIC WORKS!!!
[Verizon Samsung Galaxy S III] Chuckleb0ne:
Downloading now!
[Verizon Samsung Galaxy S III] landale:
I haven't been able to test BT yet as I am at work but after about 10 minutes of use this is the first CM10.1 build where I haven't experienced any screen flicker. Definitely the best CM10.1 build yet. Honestly with the exception of slightly weaker signal strength this build is better then the last CM10 builds I used. Now if we can just get that signal strength issue fixed and this ROM would be near perfect.
[Verizon Samsung Galaxy S III] Nightmare_24_7:
This is the only 4.1 rom that everything works great. Bluetooth is working for me as well as GPS. Got a lock within 5 seconds. Keep up the good work.
[Verizon Samsung Galaxy S III] MWFD:
BT audio working for me as well. I still think I hear a tiny bit of static, but could be just my ears having heard it for so long. Either way, 20x better than any previous 10.1 build. Thanks a bunch mastamoon!!
[Verizon Samsung Galaxy S III] mastamoon:
Thanks everybody! And thanks for the donations guys.. awesome!
[Verizon Samsung Galaxy S III] RED ZMAN:
So doesn't look like we'll see these changes in the official Or should I just start running yours? I reverted back to 10.0 a couple weeks ago because things were so unstable, but it's looking good now.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] jakereeves31:
That's weird, cause this is 4.2.1:P
[Verizon Samsung Galaxy S III] mastamoon:
Here is another build that fixes call volume adjustment and might have working BT audio.. its a hybrid of those commit/reverts.

http://d-h.st/BPD

Please test. Thanks!

BT audio NOT Working.. Do Not Flash if you like BT audio!
[Verizon Samsung Galaxy S III] BlazingGlory53:
Downloading now, will update with testing results
[Verizon Samsung Galaxy S III] jackpot08:
Thanks masta! Is it still a weak 4g signal though?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, signal remains an issue on all our CM10.1 builds.
[Verizon Samsung Galaxy S III] arqbrulo:
Hey Masta... Big fan of your work. I just tested a2dp and it's a no go. Static is back on this build. I didn't check the last one where it was fixed by yours, but this one it seems to be broken, at least for me.

EDIT: I'm sorry, I didn't see your edit that BT was NOT working. :-/
[Verizon Samsung Galaxy S III] AlexDeGruven:
Not to be a downer, but can we move the discussion for unofficial builds out of the "Official Nightlies..." thread?

I'm trying to watch the official channel stuff, and it's getting difficult to sort out the unofficial stuff.
[Verizon Samsung Galaxy S III] Lastb0isct:
Hi all,

I'm unable to turn USB Debugging on/off within the 10.1 settings. Does anyone know where it was moved/changed? This is not allowing me to restore from titanium backup.

-Lastb0isct
[Verizon Samsung Galaxy S III] termleech:
Nevermind I was looking at the wrong thing.
[Verizon Samsung Galaxy S III] PerCompLLC:
It's located in "developer settings".
[Verizon Samsung Galaxy S III] wctaylor79:
Masta great work. Much appreciated. 10/1 build. Wired headset doesn't work for phone calls. Official does. Just an FYI. Also any way you sound like to get an unofficial thread going? Your builds rock.. Just didn't want to clog this thread. Thanks again.
[Verizon Samsung Galaxy S III] pinhead875:
When dirty flashing, do you need to flash gapps again? TIA
[Verizon Samsung Galaxy S III] Lastb0isct:
I don't have a developer settings section within the settings menu.
[Verizon Samsung Galaxy S III] Nightmare_24_7:
Sorry typo. I was in a hurry. That's what I meant.
[Verizon Samsung Galaxy S III] RED ZMAN:
It is posted several times, you have to go down to your building number and tap on it 7 times to get that enabled. It'll always show after that.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] PerCompLLC:
No.