yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
I dont really know what causes it. It seems to be an issue with the bluetooth app itself as people are able to force close it and have it work as expected again. The A2DP reverts dont have anything to do with the function of bluetooth.. only the audio that gets passed through it.. if that makes sense?

Personally I leave bluetooth on all the time. I get in and out of my car 3 times a day and rarely have a problem with it connecting to my car head unit. Have you tried just leaving bluetooth enabled all the time?
[Verizon Samsung Galaxy S III] s'pht:
Works fine on 1/23 too. Horray!
[Verizon Samsung Galaxy S III] RED ZMAN:
Yes Sir, makes sense.

The extra drain on the battery has always made me conscious of Bluetooth, but honestly, I've never left it on all day on this device. With the NFC tags I have laying around, it is super simple to toggle them, just wave the device over them ( it would be a lot simpler if NFC was allowed to be toggled to stay on at all times) after unlocking of course.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] ddggttff3:
hay mastamoon, having some graphical glitches here with my GS3 running your nightly from 1/22.

Here is my phone normally

http://i.imgur.com/9rRJgo2.jpg

Here is what it was doing every time there was an animation (getting a txt popup, screen movement,etc)

http://i.imgur.com/yRJyKPK.jpg

This started after playing a game that has laggy graphics (such as doodle jump), pressing home, locking, unlocking, starting game from the running app menu (holding home menu), pressing home again.

Hope this can help fix up the last few graphical problems.

Here is a somewhat trimmed logcat (sorry if its long)

http://pastebin.com/BJ6tLKt8

EDIT

Full logcat here

http://www.filedropper.com/fail
[Verizon Samsung Galaxy S III] mastamoon:
Thanks for the logcat. Hopefully somebody that can interpret that can do something with it. Way above my remedial set of skills :D
[Verizon Samsung Galaxy S III] sivarticus85:
So where is the coding for cam recording volume? There must be a way to boost it.

BTW, excellent work masta. This ROM is very nice!
[Verizon Samsung Galaxy S III] kyuubi08:
I thought NFC didn't work
[Verizon Samsung Galaxy S III] tducote:
So I got this notification recently after flashing masta's 1/22. I tried re flashing the gapps. No help. Any ideas?

Edit: I just edit wanted to mention that I am going to try the 1/23 build and see is this still happens. Also, I should note that the notification is persistent. I can swipe it away, but it comes right back.
[Verizon Samsung Galaxy S III] PerCompLLC:
NFC has been working since the early days of CM10.1
[Verizon Samsung Galaxy S III] RED ZMAN:
Yup, I use it multiple times a day. Just wish it wasn't so sluggish.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] goldsmitht:
Sorry this is a day late, but I'm behind on my crack-flashing schedule.

When you do the reverts to get a2dp working, what is changed, or reverted back to. I don't use a2dp, but do use Bluetooth, and want to know which is better for my usage
[Verizon Samsung Galaxy S III] arqbrulo:
The reverts are the last three listed. The only issue they fix is a2dp. Otherwise Bluetooth should work fine with any other build. I've placed calls over BT and no problems.
[Verizon Samsung Galaxy S III] fafinaf:
Does acid audio mod v5 work on the latest nightly/this rom in general? Searched but found no definitive answers to the question.. Thanks in advance
[Verizon Samsung Galaxy S III] masterxchief:
I've tried on every build do far but haven't gotten it to work. I tried flashing just v5.0, 4.0, 5.0 then 4.0, and 7.0. Nothing works. If anyone figures it out let me know. I hate dsp manager

Edit: just flashed the aroma version of 5.0 as universal and noozy. Looks like its working
[Verizon Samsung Galaxy S III] dbjr11:
Select universal instead of Samsung for the first two options. Then install the desired add on. Worked for me
[Verizon Samsung Galaxy S III] Stealth111:
At first I thought it was a placebo effect from always flashing nighties looking for the next big feature/fix. Unless it is just me, I noticed a VERY noticeable increase in battery life after dirty flashing last nights nightly. I normally start out the morning unplugging from the charger after I have downloaded and updated to latest nightly. By the time I run through nosing around the phone, checking emails and voicemails on my drive to work, I would notice that after about an hour I would be down 10% already. Today I did the norm and it took 3 additional hours to get down to 90% today! I am also noticing throughout the day I am still seeing it pulling less off my battery.

FYI...

Sent using Tapatalk
[Verizon Samsung Galaxy S III] d1ez3:
you mean unofficial 1/23 or 1/24?
[Verizon Samsung Galaxy S III] Stealth111:
Sorry, last nights 1/24 Official. Just noticed I posted in unofficial thread. I bounce around between official and unofficial builds quite a bit!

Sent using Tapatalk
[Verizon Samsung Galaxy S III] sparkerjc:
Still good info to look forward to, thanks.
[Verizon Samsung Galaxy S III] Amphibliam:
Yo dudes, been TWing for a while. Has data stabilized at all? I was getting ABSURD numbers of 0 dbm drops on 1/16.
[Verizon Samsung Galaxy S III] RED ZMAN:
Try the Q&A thread man, and also yes.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] dnoyeb:
Data drops are low but overall time with signal is still not so hot for fringe areas that I had a working signal on touch wiz
[Verizon Samsung Galaxy S III] devo1929:
I would have a data drop twice day on 1/16, once on each way to and from work. Since I've updated to 1/18, not a single data drop during my daily commute.

Unlocked Verizon GS3
[Verizon Samsung Galaxy S III] NegativeOne:
Did they fix a2dp in official yet? I wanna try the battery stuff a previous poster was commenting about, but I do like me my a2dp:)
[Verizon Samsung Galaxy S III] Stupifier:
Not fixed yet
[Verizon Samsung Galaxy S III] Neverender326:
On Masta's 1-18 unofficial i have llama turn off my data every time i turn the screen off. It's set to come back when I turn it back on and i never have any issues with it not coming back or getting stuck in 3G. goes right to 4G and good signal.

---------- Post added at 08:29 AM ---------- Previous post was at 08:19 AM ----------

Same!! I can't get it working. I will try the Aroma install...i'm now thinking the "Samsung Optimized" is only for TW Roms. Is noozx latest version crashing for you?
[Verizon Samsung Galaxy S III] eikoo:
Do these builds have working dock audio?
[Verizon Samsung Galaxy S III] mastamoon:
No :(
[Verizon Samsung Galaxy S III] ddggttff3:
Hay mastamoon any way I can request a new unofficial build with the RIL patches? I'm on the latest official nightly and no longer get ipv6 like I did in your last nightly. I want to see if the RIL patches are the reason for this.
[Verizon Samsung Galaxy S III] mastamoon:
Sorry not till Monday when I head back to work.

I'm having a good experience with my last build and imoysen's latest kernel.. v2.4rc2 I think it is.
[Verizon Samsung Galaxy S III] PerCompLLC:
^^This^^ Same setup here... Running GREAT!
[Verizon Samsung Galaxy S III] juancaperez2000:
I been running B17 with same kernel and is simply amazing thanks masta
[Verizon Samsung Galaxy S III] tcsheen:
I'm sorry imoysen v2.4rc2 what?? Where is that? I thought he was only to 1.7?
[Verizon Samsung Galaxy S III] mastamoon:
Believe its his experimental kernel.
[Verizon Samsung Galaxy S III] odub303:
2.4 went official recently and add a new cpu sleep state that seems to be having a noticeably positive effect on idle battery drain. Give it a shot.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] tcsheen:
Trying it now, ocd to 1.9... Super smooth combo so far, thanks for the tip!
[Verizon Samsung Galaxy S III] d1ez3:
1.7 is TW, 2.4 is AOSP 4.2
[Verizon Samsung Galaxy S III] goatman101:
Call echo

Masta, I flashed your 1-23 with cherry picks and reverts. I now have working A2dp streaming but gained the dreaded call echo (I know, you warned me). Does flashing a different kernel get rid of this or is there another fix?
[Verizon Samsung Galaxy S III] NedDasty:
Hi guys--

Quick question. Does anybody have a working photosphere camera? The recent CM10.1 builds have been coming with a photosphere-less version.

I remember using photosphere back in CM10. The only problem was that you had to manually touch to focus every shot, or the camera would lock up. I'm wondering if anyone has successfully installed a 4.2 photosphere camera with no issues on CM10.1.

Thanks
[Verizon Samsung Galaxy S III] odub303:
CM never included photosphere. It's a closed source Google app.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] mastamoon:
No, its not a kernel issues AFAIK.

Not sure. I thought it works with the work around you mentioned but really don't know for sure.
[Verizon Samsung Galaxy S III] sparkerjc:
You have to touch to focus still, or put it into action mode, then touch to focus once, reboot and leave it in action mode and you don't have to touch it again.
[Verizon Samsung Galaxy S III] mikejr83:
I use the photosphere camera with no problems. There is a flashable zip floating around of just the camera. Get that zip but don't flash it. Extract it to your sd card. In the extracted folder's system folder there should be two folders, one app and the other lib. Take the apk from the app folder and using a root capable file manager put it in your /system/app folder.

In the lib folder there should be two files. One will already in your /system/lib folder copy the other one (do not overwrite the lib that already exists).

After that boot into recovery clear cache and fix permissions and you should be set. You'll have two camera and gallery apps but that isn't a big deal. Also, the tap your screen for focus and then take a picture bug is gone.

All said I take no responsibility if you screw up your device using instructions that I typed from my phone while taking a BM. That said, I love the photosphere camera and gallery. My only grope is that I'm a crack flasher and I have to do those steps every time I flash a rom. One day I'll mod the script to take out the one unneeded lib.
[Verizon Samsung Galaxy S III] atc3030:
You are no the first, and nor will you be the last to help someone while helping yourself on the porcelain throne... :)

Just gonna leave this riiiiiiiiiight........ Here... :)
[Verizon Samsung Galaxy S III] lortay78:
I wish that photosphere trick worked for me. I must have the wrong zip. Mine has three libs. Two of which I already have. I get the same touch to focus bug. I'd pay good money for a working Google gallery app with photosphere on this device.
[Verizon Samsung Galaxy S III] sparkerjc:
You said grope. :) Also is leaving the unnecessary lib file out what fixes the touch to focus bug, or is there a new version of the camera floating around?
[Verizon Samsung Galaxy S III] mikejr83:
Here is the link to the zip I used:

http://db.tt/ooKMnFHD

I have both .so files from the lib in my /system/lib folder so I'm not sure which one it is. Normally I copy both and reject the one that's already there. I'm pretty sure libjni_mosaic.so is the one NOT to overwrite. Liblightcycle.so should not exist on a fresh install so you wouldn't get any notice to overwrite it.

BTW, I'm running matsa's 1/23 build and it works fine for me.
[Verizon Samsung Galaxy S III] Mean Sixteen:
For what it's worth I just flashed the zip with no problems. Works perfectly.

It actually gave me a separate camera app. Which is perfect for me since I use the modified camera to store on SD card for my daily camera. I just use photosphere camera for that feature only.

Edit: I should clarify that you still need to touch to focus on my photosphere camera. Other than that it's perfect. At least that I've experienced.

Sent through mental telepathy...or my unlocked SGS3
[Verizon Samsung Galaxy S III] mastamoon:
Here are my 1/28 afternoonlies. Repo Sync @ 2:45PM EST and 3:00PM EST respectively. I finally committed the magic to the CM Gerrit for review that makes the 3G/4G handoff of my builds rockzorzOMFG!!!111 No idea if/when CM will merge it into official, have never committed anything before so we will see.

One of the RIL commits I was CherryPicking got merged also, so 1 less in the list.

Download #1 - Just the CherryPicks so

NO

WORKING A2DP: http://d-h.st/cMt

Download #2 - CherryPicks and Reverts so WORKING A2DP: http://d-h.st/qNX * may cause echoing on calls *

Cherry Picks:

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

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

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

APN - http://review.cyanogenmod.org/#/c/31104/

Reverts:

Audio - http://review.cyanogenmod.org/#/c/29175/ - Fixes Bluetooth/A2DP Streaming *thanks mkasick

Audio - http://review.cyanogenmod.org/#/c/29174/ - Fixes Bluetooth/A2DP Streaming *thanks mkasick

Audio - http://review.cyanogenmod.org/#/c/29661/ - Fixes In Call Volume Adjustment *thanks termleech

As always check here to see what my repo sync may have missed: CM Gerrit - Merged

Enjoy!

NOTE: I haven't disabled LPA in either of these builds. I haven't had any wake-lock issues and its easy enough to do yourself with any root file manager. If your having battery/wakelock issues, disable LPA in your build.prop by editing the line lpa.decode=true to lpa.decode=false *thanks termleech
[Verizon Samsung Galaxy S III] landale:
I am wondering if it would be possible to look into a bug that has plagued 4.2 ROM's which is the stock email app not respecting when vibrate notifications are turned off. Basically if the phone is on vibrate mode no matter what this setting is set to the phone will vibrate when you receive an email. I had thought this effected all 4.2 ROM's but I tried out Phantom's AOKP ROM and it doesn't have this problem. It doesn't appear to be an APK issue but an Android one as there is a whole thread on it below and they mention having to patch services.odex. Was wondering if this could be looked into?

https://code.google.com/p/android/issues/detail?id=39592
[Verizon Samsung Galaxy S III] juancaperez2000:
Excuse me Masta this is the first time that you cherry pick your own IRL commit?
[Verizon Samsung Galaxy S III] mastamoon:
Looks like a toggle is in the works.. https://code.google.com/p/android/issues/detail?id=39592#c154 Shows you the 2 commits that are being reviewed. I can try a build tomorrow with them if you would like.. which version of my build do you use, though I would probably add them to both.
[Verizon Samsung Galaxy S III] mastamoon:
Indeed! If I tweak anything I generally just do for my own satisfaction but I figured this should be out there. I don't know if its the absolute fix for this issue.. but it certainly works better with my commit than without.

:good:
[Verizon Samsung Galaxy S III] landale:
That would be amazing. I typically use the non-revert one since I don't use A2DP. This has certainly been one of the most annoying bugs I have seen in a long while of using Android, even went back to CM10 because of it but would eagerly come back to CM10.1 with this getting fixed.
[Verizon Samsung Galaxy S III] gcutter:
Handcent

Anyone get Handcent MMS Pic sending / receiving working on 4.2.x? I have tried on LS and CM10.1 always have to go to stock MMS.apk to download or send MMS pictures.
[Verizon Samsung Galaxy S III] jackpot08:
Just curious what's wring with stock?its fast and now supports group messaging.
[Verizon Samsung Galaxy S III] V3TTOO:
That is a 4.2.1 bug.

And my signal just dropped down with 1/28. I am barely able to do anything before I lose signal.
[Verizon Samsung Galaxy S III] Stupifier:
Although stock is just as functional as handcent, it is not as customizable.
[Verizon Samsung Galaxy S III] Amphibliam:
Are the 0 dbm drops still an issue on this build?
[Verizon Samsung Galaxy S III] mastamoon:
Yep.
[Verizon Samsung Galaxy S III] Restola:
Reading through the comments in the commit I am grateful you are spending the time on this even if you do get slapped around a bit. I know CM has it's own goals and priorities with limited volunteers, but the reason people install unofficials sometimes is that stuff works that is broken or "barely works" in the official builds (or gets ignored entirely, which I know probably happens for a very good reason).

Keep up the good work and hopefully the official build gets a complete fix for the handoff issue soon (along with signal strength, which I'm finally starting to notice more :( )
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I'm not surprised a bit. But what can you do. Its my first commit ever and might not know all the terminology but I know this works and if it doesn't break anything else its better than the commit that broke it in the first place and got pushed right through.

Not even sure why a commit fixing something on Sprint had edits to the Verizon APN without testing. But at that point RIL was probably so broken it hid the effects.

:beer:
[Verizon Samsung Galaxy S III] mastamoon:
Hopefully this pans out and we can get back to a unified build.

https://twitter.com/BMc08GT/status/296042221881393152
[Verizon Samsung Galaxy S III] jspidah:
Do any of these have headset audio and inline mic working during calls?
[Verizon Samsung Galaxy S III] mastamoon:
The non revert build should.
[Verizon Samsung Galaxy S III] mikejr83:
I wonder if someone from AOKP figured out the reverts and they're going to include them in their official builds.

Hopefully they have a true fix. I switched over to the non revert build because I end up using my world headset more than streaming, but I still miss the opportunity.
[Verizon Samsung Galaxy S III] mastamoon:
Here is a 1/29 morningly. BT A2DP audio cherry pick that 'fixes' A2DP playback without audio reverts. Sound may not be as good as the revert build, so if you're an audiophile, stick with the revert build for now.

Download - http://d-h.st/BH8

FRAMEWORK PATCH - http://d-h.st/H2m *think this might be the 2nd commit that AOKP mentioned that might help with A2DP sound. If your running this build and can test A2DP.. flash this and see if it improves.

Cherry Picks:

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

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

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

APN - http://review.cyanogenmod.org/#/c/31104/

Audio - http://review.cyanogenmod.org/#/c/31127/

Enjoy!
[Verizon Samsung Galaxy S III] ddggttff3:
Thanks, and just to let you know, I flashed your 1/28 build, and IPv6 is back after a reboot! :) Thanks
[Verizon Samsung Galaxy S III] d1ez3:
He says it's a true fix on the thread on rootz
[Verizon Samsung Galaxy S III] NegativeOne:
Its a bs fix. He just puts the sample rate up to fix it. Depending on your audio it will still have problems I think
[Verizon Samsung Galaxy S III] termleech:
Actually looks at the commits he does more than just change the sample rate. The changing of the sample rates is the first step in the fix and is actually in cm as well.
[Verizon Samsung Galaxy S III] Stupifier:
So....we are still not sure if this is a "TRUE" A2DP bluetooth audio stream fix? Next question...if this DOES fix A2DP bluetooth audio stream, will the in-call echo issue be gone? Everyone was assuming the in-call echo issue was a result of the A2DP bluetooth audio stream Revert in Mastamoon's Unofficials
[Verizon Samsung Galaxy S III] NegativeOne:
What are you referring to?

BTW:

Yeah - sounds totally legit ;). I love hearing things like "for now" and "hardcode" - granted, it's just a comment, but they really do seem to just be scaling everything to the same sample rate.. I'm just not sure it will prove to be a good fix.
[Verizon Samsung Galaxy S III] termleech:
I love how people call it a BS fix and don't actually know what he's done to fix it. I assume you just saw the CM guy call is bs. CM is not the end all be all despite what people may think.

The commits I'm referring to (in addition the sampling rate for the bluetooth which BTW CM has also done in their gerrit http://review.cyanogenmod.org/#/c/31127/) are

https://github.com/AOKP/android_har...mmit/ade5f9e2ae4a10e436770e188a42f5e09cb831c8

https://github.com/AOKP/android_har...mmit/bf7e5998c7a40180688ed66a741532ecf7c9632a

https://github.com/AOKP/android_dev...mmit/fed37c57ee4379019af3fc95403002cddadb9db9

And for people who were wondering, in my initial tests, yes it does fix the bluetooth issue. However I don't have a very good bluetooth speaker to really test the lows and highs (which was a large part of the issue).

a2dp is broken in 4.2.1 in general and Google has said they have fixed it in 4.2.2 so this might be the best fix we get until 4.2.2 source drops and we can see what google did to fix it.
[Verizon Samsung Galaxy S III] ben999_:
Has anyone else noticed that DSP manager dynamic range compression and bass boost is not working properly on the official nightlies? By that I mean that enabling them completely distorts audio and clips like hell (depending on the amount of effect, eg slight, moderate, extreme). I've personally tested Mastamoon's 1/16 and 1/23 and it works as it's supposed to. It seems to me that the reverts are affecting more than just bluetooth audio.Occasionally DSP manager seems to get disabled, for lack of a better term, while I'm listening and the effects stop working. Pausing for a second and playing again re-enables them. I think it may have to do with a partial wakelock occuring or something of that sort.
[Verizon Samsung Galaxy S III] icon123:
@mastamoon

Maybe we can get an unofficial with the aokp a2dp fixes.
[Verizon Samsung Galaxy S III] mastamoon:
Here is a 1/29 afternoonly. BT A2DP audio cherry picks that 'fix' A2DP playback without audio reverts. Sound may not be as good as the revert build, so if you're an audiophile, stick with the revert build for now.

Download - http://d-h.st/TRj

Cherry Picks:

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

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

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

APN - http://review.cyanogenmod.org/#/c/31104/

Audio - http://review.cyanogenmod.org/#/c/31127/

Audio - http://review.cyanogenmod.org/#/c/31142/

Enjoy!

Let us know how the Bluetooth A2DP sounds, especially compared to the previous revert based builds.
[Verizon Samsung Galaxy S III] d1ez3:
can anyone get the changelog page for cm to load? I'm using 10.1.cmxlog.com/?device=d2vzw
[Verizon Samsung Galaxy S III] landale:
I know you have probably been busy with the a2dp fixes but have you had any time to look into trying this out? I'm not in a major rush for it but I can't be the only person who has been impacted by unwanted vibrating notifications. I am more than happy to try it out when time permits for you.
[Verizon Samsung Galaxy S III] mastamoon:
Whoops.. Ill give it a try tomorrow.
[Verizon Samsung Galaxy S III] landale:
Seriously no rush man, just glad you're even looking into it.
[Verizon Samsung Galaxy S III] mastamoon:
Looks like cyanogen just merged a d2 specific commit for the 48khz a2dp fix so Idk if my build has everything needed. But I'd guess the official nightly should have the entire fixed a2dp fix working.
[Verizon Samsung Galaxy S III] RED ZMAN:
Re: [Official] CM 10.1 Q&A Thread - OP updated 1/23

Looks like your first submitted fix is getting approved.

Congratulations!

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] V3TTOO:
I saw you had another for the 29th with a framework fix. Did that become unneeded?
[Verizon Samsung Galaxy S III] jackpot08:
I also noticed in the 28 nightly the game lag is gone.no more lag after playing a game
[Verizon Samsung Galaxy S III] masri1987:
anyone on the 1/19 build notice low in-call volume and ppl complaining that you sound low and or static?
[Verizon Samsung Galaxy S III] V3TTOO:
The low call volume has an in system option to increase the gain in the settings, under Advanced > Sound.
[Verizon Samsung Galaxy S III] bobby janow:
It was needed today but with the fixes merged on the official it might not be tomorrow. I for one will miss these builds if it all works in the morning. Thanks mastamoon for all your work on these reverts. I'm sure I speak for a lot of us.