yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Excessiveidling:
Had been on cleanrom 6.2 with aosp messaging stock kernel but figured I'd try this release candidate (even did the newest nightly) and all in all it looks and seemed to run smooth. The only complaint I had (which I've had since the first time I tried cm) was the video audio recording is still ultra low at best. While I know the phone is a phone....not a video camera...that was sadly a deal breaker for me (18 month girl...gotta make sure I get all the vids and audio ya know!)...is it still an issue with it not using both microphones when recording? Is it just a low receive gain? Figured it would have been fixed by now...hmm....maybe by rc3 I can only hope!

E|
[Verizon Samsung Galaxy S III] Div033:
I too had this issue when I was recently using CM10.1. I've never seen anyone from the CM team comment on the issue but its definitely been around for a while.

The popular speculative reason for the issue is Samsung's RIL code is closed source and the CM team can't replicate it completely.

I dunno. Hopefully one day.
[Verizon Samsung Galaxy S III] Restola:
The audio recording volume hasn't been changed in months. I have a feeling it won't be. It is still lower than stock but it does record in stereo. I haven't had a chance to do a side by side in a long time. Maybe I'll borrow my wife's gs3 and see just how big of a difference it still is.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] titanshadow:
So as suggested I did a factory reset after updating to the latest nightly ROM, 5/21, and then went in. My headset paired alright, but after a good 2-3 minutes of not being connected, it again won't reconnect at all. I'm going to try it once more, factory reset, then I'm going to cancel the restoration of any of my apps from Google Play, just upgrade the ones that come with the ROM, and see if that makes a difference.

Lucky for me I have a full titanium backup of everything on my device - at least I won't have to spend hours reconfiguring everything - that always sucks.

I'm open to any more suggestions. I guess I'll wait for the next RC (assuming this doesn't work), if it still has this issue then I can submit a bug report via Jira. I made sure to flash the latest in TZ, Modem, and all of that after we were all notified about the problems with NOT doing that.

---------- Post added at 01:59 PM ---------- Previous post was at 01:22 PM ----------

Well that settles it. It isn't some errant configuration file or something... Did two complete wipes, this last one I simply ran updates on the apps that come with the ROM and were in my GApps package from when I originally installed CM 10.1 and after 4 minutes of being disconnected, the headset will not reconnect. Same result if I re-pair the device after, go 3-4 minutes without it being connected and the reconnection fails.

Meh.

Suggestions are welcome! :)
[Verizon Samsung Galaxy S III] mastamoon:
Try my unofficial. And/or install a different kernel maybe?

And this all works fine with a build from a few days ago?
[Verizon Samsung Galaxy S III] sivarticus85:
Several posts back I did a side by side comparison of the camcorders with my wife's GS3 running CM 10.1 and a stock Gnex. That's just how it is bud. Granted it may sound quiet on the phone speaker, but it's very audible when playing on a PC or using headphones. Sorry bro.
[Verizon Samsung Galaxy S III] dvaderx:
I did a side by side - stock vs. aosp

cleanrom6.2 laying on my sofa, recording both tv and my voice.

did a full wipe installed latest CM and recorded same tv and my voice.

with the CM I can't hear the TV unless i put the phone right to my ear and listen close and it's still barely audible.

with the stock/cleanrom I can hear the TV in play back by just holding the phone in front of me, don't need to hold it up to my ear.

so aosp/cm is still very low.

If you test it on CM just by talking right into it and play it back, then yeah it will appear to work fine, but if you do further test, you'll see it's not up to stock levels.
[Verizon Samsung Galaxy S III] rockingrubberducky:
is it okay to back up my apps from the stock rom and restore them on aosp?
[Verizon Samsung Galaxy S III] mastamoon:
Apps yes.. App data, maybe.. System data.. Noo
[Verizon Samsung Galaxy S III] jackh0lt:
However if you plan on restoring those apps, Samsung/touchwiz tied apps will cause apps like Titanium Back up to stall. Happened many a times.
[Verizon Samsung Galaxy S III] titanshadow:
It does, which is odd. I haven't tested the latest builds on my tablet yet, I'm going to do that tonight. What is your build?
[Verizon Samsung Galaxy S III] soohyunk83:
pie controls?

Is pie controls actually enabled on the latest nightly?

Maybe I'm just not finding the option in settings?
[Verizon Samsung Galaxy S III] toddrosenberger:
Is it still necessary to flash Gapps every time you install a new nightly?
[Verizon Samsung Galaxy S III] airmaxx23:
I'd like to report this but can't seem to get a response from anyone on how to do so, could someone please give me some assistance?
[Verizon Samsung Galaxy S III] invisiblek:
https://jira.cyanogenmod.org/
[Verizon Samsung Galaxy S III] airmaxx23:
Thank you, how do I go about getting a logcat?
[Verizon Samsung Galaxy S III] ugachris:
A quick Google search would really help you out.

http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat

http://xdaforums.com/showthread.php?t=1378491

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en
[Verizon Samsung Galaxy S III] jwoytk01:
Me too. Had it since day one. Never gone away. Settings are all good.

Sent from my Sick-Ass GS3
[Verizon Samsung Galaxy S III] jackh0lt:
Forgive me if this is a solved issue but I get this random bug after a day where the screen (wallpaper as the icons never were affected) looks like static images like on tv channels that don't come in. Not a deal breaker but it's frequent.
[Verizon Samsung Galaxy S III] coldconfession13:
Bluetooth has been really buggy past few nightlies. My peblle would stop working so I turn off Bluetooth and turn it back on which it never turns on. A reboot fixes this for a while. When my radio wants to connect it can't find it. Its like it says Bluetooth is on but it really just stopped working.
[Verizon Samsung Galaxy S III] VinBertinelli:
Anyone know if mic is working on hangouts in the latest nightly?
[Verizon Samsung Galaxy S III] mastamoon:
Was this the issue?

http://review.cyanogenmod.org/#/c/38204/
[Verizon Samsung Galaxy S III] titanshadow:
Just a note for developers, the latest nightly presents better bluetooth reliability for me, but still not very good. Usually it'll connect by the third of fourth try, where as before it was damn near impossible.

I'd still like some help in trying to get a log from my tablet on what error it is getting when trying connect to the phone for tethering. I would do this for the headset too but obviously I can't get an error log from a headset.

Any help would be appreciated.
[Verizon Samsung Galaxy S III] titanshadow:
I was reading a bit about logcat, and would bluetooth errors be included int he radio buffer or is that only the cell phone radio?
[Verizon Samsung Galaxy S III] titanshadow:
Well after some research and experimenting with logcat, I finally got an error message not on the phone but on the tablet that is trying to connect to the phone. Logcat on the phone shows nothing at all (which I think is especially strange) when I try to connect to it via Bluetooth from the tablet.

The tablet is a Galaxy Tab 2 7" also running CM 10.1. When trying to tether to the phone, I saw this error:

W/bt-bnep ( 1387) BNEP - Rcvd conn cnf with error: 0x10 CID 0x48

That is between the messages that basically say the device is trying to connect to the phone and the device fails to connect to the phon.e

I've tried searching for that error code 0x10, but I can't find anything but a reference to linux error codes when reading hard disks, which reference a CRC error, given that this isn't a hard disk problem I have my doubts about how related the two errors might be. That being said, I have actually seen error codes be somewhat consistant at times in linux.

I don't know, I'd really like some help from someone who is more experienced than I.
[Verizon Samsung Galaxy S III] buschbarber:
Bluetooth and Audio

I recently updated to 05/23. The Bluetooth was working fine with my car radio, but for some reason, it mutes my Notification sounds. I turned it off and the Notification sounds returned. I tried to turn it on again and I could not until I rebooted the phone.
[Verizon Samsung Galaxy S III] Defragger51:
Just stated on the Q&A form how great RC2 has been running for me after 324 hours and was going to give the latest 3/24 nightly a try , but after reading this form and all the issues people are having with Bluetooth and the mic I think I going to stay on RC2 for awhile longer. See reading does help.
[Verizon Samsung Galaxy S III] nickjensz:
Is there a way to get an option in the power menu to reboot into recover?
[Verizon Samsung Galaxy S III] titanshadow:
More on the bluetooth front... I'm having trouble deciphering the verbose log I'm getting and would like some help. For the test the Tablet and Phone both have wifi disabled, I checked the verified that pairing is good between devices and that the phone has tethering enabled. This is the log from the tablet when it tries to connect.

This is the log from the phone during the attempt.

In particular, finally realizing I was using logcat wrong previously, I notice that there are some lines on the phone log about trying to call a system process without a qualified user. I fixed permissions right before trying this, so, I know that isn't an issue. Another oddity is that the log states that the proxy is connected but, obviously, the connection fails or doesn't stick but I can't find the particular error that goes with that.

Any help, again, would be appreciated.
[Verizon Samsung Galaxy S III] rockingondrums:
Settings > developer options > advanced reboot.

to enable developer options, tap on build number 7 times.
[Verizon Samsung Galaxy S III] mastamoon:
Hey, please flash one of my builds here http://xdaforums.com/showthread.php?p=36583200 and let me know if bluetooth gets better. Please delete the device then re add it.

Thanks.
[Verizon Samsung Galaxy S III] titanshadow:
Thanks, I've got to work soon and so I can't try them right now but hopefully I'll be able to flash them tomorrow. I've got a 13 hour shift today so, yeah, probably won't get to it tonight. But thank you! :)

I've downloaded both the "new" and "current" RIL, not sure what that is so... Which one would you suggest?
[Verizon Samsung Galaxy S III] mastamoon:
Either is fine really. I run the new ril version, works fine but I put up 2 versions just in case somebody has an issue.

Thanks for testing, let us know what you find.
[Verizon Samsung Galaxy S III] airmaxx23:
I just flashed one of the newest builds and even though my bluetooth has been off for days under battery stats my bluetooth usage shows 49 days and 51%. This happens on the 5/24 and 5/25 builds, both official and unofficial.
[Verizon Samsung Galaxy S III] titanshadow:
I ran yours and god damn it worked!

Out of curiosity, do you know what difference between the two made yours work vs. the other not work?

Also, a side note, usually the little popup message for my auto-bluetooth connection fades in and out too quickly, however I actually saw it do its thing last night (I have tasker setup on the tablet to find my phone in the event the wifi is a lost cause) and event hough on the 5/16 build it connected, it gave me an error, it just connected anyway. Usually when testing I have tasker turned off and regular bluetooth connections don't report errors as well as I'd hope.

Thanks though, seriously!

Do your changes ever get integrated into the main branch?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah looks like its actually a recent kernel merge that caused it. We'll get that reverted for the time being and remerge when we know what borked it.
[Verizon Samsung Galaxy S III] stefilini:
FYI - I started getting a lot of wallpaper screen flickering issues from the last two nightlies. Clean install seemed to fix it.
[Verizon Samsung Galaxy S III] NITRO_2:
I feel bad for asking but I wanted to try out CM10.1 and installed the latest nightly. Is there anyway to change the quick settings tiles to have 5 tiles across the board instead of 3 in each row? Sorry, it was something I liked about Liquid rom. Thanks

Edit: Also, is there a trick to get facebook contacts to sync? Can't get mine to sync.
[Verizon Samsung Galaxy S III] sivarticus85:
They don't unfortunately. I use Haxsync.
[Verizon Samsung Galaxy S III] NITRO_2:
Ok sweet, thank you. Does your haxsync sync phone numbers also? Mine won't
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Ubersync works well too, I use it cause I couldn't get haxsync to work for me

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] sivarticus85:
No I don't think so. Just FB contacts.
[Verizon Samsung Galaxy S III] toddley:
I use ubersync as well. I believe Facebook doesn't allow numbers to be synced along with profiles.
[Verizon Samsung Galaxy S III] RED ZMAN:
I've found conflicting reports, is USB Tethering working over here okay? I'm on the Unofficial and trying to help work out some bugs with a custom Nexus 7 ROM that I have when trying to USB Tether with my SG3.
[Verizon Samsung Galaxy S III] TheDigitalSlacker:
First of all let me say: I love CM10.1, I have it on 3 other devices. Thanks to all the developers that are helping with you, I really do appreciate it.

Now my question: Is there a fix for the terrible signal with CM10.1? I am talking half *or less* signal from the stock rom. I've gotten addicted to the speed and battery of CM but the signal is killing me. I have the latest radio's flashed and have the stock CM kernel.

Any help?

thank you!
[Verizon Samsung Galaxy S III] yznhmr:
+1
[Verizon Samsung Galaxy S III] rockingondrums:
What metric are you judging this on? dBm or bars? Because bars don't mean ****.
[Verizon Samsung Galaxy S III] TheDigitalSlacker:
Totally fair question.

I'm using a combination of the bars (even though they they arn't the end-all be all but they give me a quick look), going to Phone Status and looking at db and honestly just general usage.

I was at a client yesterday and my phone was going between 1x and one bar of 3g and when i was there last week on stock rom i was bouncing between 3g/4g. Just this morning, when i posted, i was also at 1x whereas i was on 3g before.
[Verizon Samsung Galaxy S III] shadrach47:
I honestly thought my bad reception was due to me moving to where Verizon is terrible just around when I switched to CM10. Work also seems to be weaker from when I was on TW but never really bother to investigate since many weren't reporting it. Now I can see when I'm in low reception the service switching from 1x to 3g isn't so great and when I'm home my battery drains from RILJ wakelock. I also notice I have to toggle 4g sometimes to get it when on 3g. I think I'm going to try TW out and see if there is any difference or if I'm just stuck in a ****ty service area.
[Verizon Samsung Galaxy S III] TheDigitalSlacker:
I've had degraded signal with other custom roms and I think the answer that I got was 'its samsungs drivers' that keep us from getting full signal. For the life of me I can't remember where I say it so I just figured I would ask here. If anyone can get it working its the CM team, I got faith.
[Verizon Samsung Galaxy S III] Div033:
I'm fairly certain there's only two RIL drivers. Samsung's and CyanogenMod's. You're always using one or the other no matter which ROM you're on... With this phone at least.

The signal issue occurs primarily in low reception areas. Right now my 4G is reporting 0 dBm but I still get data just fine. There are some weird signal bugs that have existed since they got data working on this phone... I'd think if it was something they could fix, it would've happened by now. I'd be ecstatic if someone could say otherwise.

At any rate, the GS4 already has working data on AOSP so I've been thinking about upgrading to that if it doesn't have the same signal issues.
[Verizon Samsung Galaxy S III] titanshadow:
Anyone here know what encryption algorithm CM 10.1 uses for its device encryption?
[Verizon Samsung Galaxy S III] Lrr_r:
http://source.android.com/tech/encryption/android_crypto_implementation.html
[Verizon Samsung Galaxy S III] razortaz18:
RC3 is available for download.

http://get.cm/?device=d2vzw
[Verizon Samsung Galaxy S III] Worm1996:
RC3 no problem
[Verizon Samsung Galaxy S III] VinBertinelli:
Not seeing anything different in RC3, hopefully screen flickering is a thing of the past
[Verizon Samsung Galaxy S III] titanshadow:
Loading it now, hopefully my Bluetooth issues are also a thing of the past.
[Verizon Samsung Galaxy S III] VinBertinelli:
Yeah those were annoying, I'll test it tomorrow
[Verizon Samsung Galaxy S III] titanshadow:
Nope, Bluetooth still doesn't work on RC3 or 5/30 nightly. I'll post a bug report for RC3 tomorrow with a log cat and everything.
[Verizon Samsung Galaxy S III] NeoMagus:
Bluetooth is working fine for me between my Rocketfish headset and in my 2013 Altima on RC3 with Play Music and Pandora. I haven't had any issues yet coming from RC2
[Verizon Samsung Galaxy S III] titanshadow:
The issues are not constant, no idea what happens but for me the phone just stops accepting bluetooth connections.
[Verizon Samsung Galaxy S III] NeoMagus:
Try changing lpa.decode in the build.prop from true to false, might help

Honestly haven't had an issue with it at all doesn't drop, no static works like it should.
[Verizon Samsung Galaxy S III] dtraini7:
I haven't had my s3 for a while but my brother has it and is running CM10.1 on it and we have one bug to really report. Has anyone else experienced the microphone not working in a hangouts video call? It is very odd. Thanks to those who help!
[Verizon Samsung Galaxy S III] rockingondrums:
Dammit, I saw something about it being added to the manifest on BBQ log as I was prepping to flash the nightly haha. I know what I'm doing when I get home.

I also want to mention that flickering for me has been practically non-existent until recently. It came roaring out of nowhere as I watched the red wings v blackhawks recap.
[Verizon Samsung Galaxy S III] NeoMagus:
Are you running a nightly 5-27 or older. This commit was merged 5-28, and it is working for me on RC3.
[Verizon Samsung Galaxy S III] anubis1127:
I haven't had any screen flicker on RC3 yet, knocks on wood. I was running the nightly from 5/25 before and was getting a little flicker, but it was very intermittent.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Does 5-31-13 build have all the merges from the RC3?
[Verizon Samsung Galaxy S III] dtraini7:
Thank you! I will update him to RC3.
[Verizon Samsung Galaxy S III] byproxy:
anyone figure out how to swap internal and external storage yet? i really want to use this rom but have to have that swap ability.
[Verizon Samsung Galaxy S III] Div033:
Anyone notice how the kernel commits from 5/29 substantially improved benchmark scores? I know benchmarks mean nothing... But they're kinda fun :P

Specifically quadrant.
[Verizon Samsung Galaxy S III] Argent36:
Just clean flashed RC3 and I've encountered the dreaded camera not working.... Is it just me?
[Verizon Samsung Galaxy S III] cybertec69:
Just noticed that my GPS locks on instantly with the new RC3 build, fantastic.:good:

---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------

Same issue here, it says "Can't connect to the camera", I am sure they will fix it in due time.
[Verizon Samsung Galaxy S III] Hybridnoob:
Which modem, tz are you using?
[Verizon Samsung Galaxy S III] cybertec69:
The way I FIXED the camera issue was to flash the VRBM1.aio.zip Radios separately. I have a feeling they are running the latest VRBMD3 Radios in build RC3 that where just released by Verizon and the latest 4.1.2 stock ROM, which has had issues with 4.2.2 ROMS.
[Verizon Samsung Galaxy S III] Argent36:
Yeah I flashed VRBMD3.....going to try VRBMB1...see if that fixes it

(also it doesn't appear that I can access the storage when plugged in to a computer? media device is checked in USB settings)

EDIT: Yes ok - so the fix for the camera is to reflash the VRBMB1 all in one firmware from invisible

at least that's what got my camera back :)

Thanks cybertec69 for the clue!
[Verizon Samsung Galaxy S III] mastamoon:
You guys should flash this..

http://bit.ly/18Btjwc

Its the D3 radio, sbl's and rpm plus the B1 TZ file. The D3 TZ file is what is causing the camera breakage. This zip makes you as up to date as you can be right now.
[Verizon Samsung Galaxy S III] titanshadow:
Mastamoon released a version of VRBMD3 firmware that had the older TZ, which seems to fix the camera issue.
[Verizon Samsung Galaxy S III] cybertec69:
My Virus software won't let me go to the site.
[Verizon Samsung Galaxy S III] mastamoon:
I can assure you the site isn't dangerous.. but here is a direct link.. http://truelinux.net/sch-i535/mastamoon/other/I535VRBMD3_firmware-MB1Tz.zip
[Verizon Samsung Galaxy S III] Lrr_r:
Why? Not long ago there've been issues thought to be linked to modem and tz versions mismatch. If current CM isn't fully compatible with some old firmwares, what makes it compatible with the latest one?
[Verizon Samsung Galaxy S III] cybertec69:
Fixed it, changes the security exceptions in my Antivirus. Flashed them, all is well, thanks again.
[Verizon Samsung Galaxy S III] mastamoon:
It is most likely a change in the kernel and tz together that allow full functionality. Right now there is a link in the chain missing. From what we can tell the kernel is trying to load the camera firmware, but there is some communication issue with the Tz file from the latest update that is causing this failure. Using the old tz allows this firmware update/initialization to take place and you have working camera.

If you dont feel comfortable running this mismatch, thats fine.. run the straight MB1 package until its figured out in source. Shouldnt be soon after the kernel source for D3 is released which hopefully should be early next week.

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

Yeah was probably the website redirect that was causing it to yell at you. Glad its working for you.
[Verizon Samsung Galaxy S III] titanshadow:
I officially added my bluetooth connection issue to Jira on the RC3 ROM. Gave them the logcat and also pointed them to the custom ROM from [MENTION=2963287]mastamoon[/MENTION] as to a CM ROM that works.

We'll see what happens.

On an unrelated note, thanks to the CM guys for the encryption capabilities but, is there a decrypt option - I mean, I haven't lost the password or anything so, if I wanted to decrypt my phone I wouldn't need to factory reset would I?
[Verizon Samsung Galaxy S III] Argent36:
Thanks mastamoon for the fix to....uh fix the camera :)

worked like a charm!
[Verizon Samsung Galaxy S III] Lrr_r:
You'll have to reformat the /data partition which contains app data and internal SD. All of your data and files will be gone. Note that nandroid backup doesn't back up the internal SD.
[Verizon Samsung Galaxy S III] titanshadow:
Thanks, did not expect that. But it's fine. :)
[Verizon Samsung Galaxy S III] rockingondrums:
I updated a few hours ago to RC3 and suddenly my phone thinks I've used 30 GB of data, even though the top app isn't anywhere near that. As you can see in the screenshot, I just started the new billing cycle:
[Verizon Samsung Galaxy S III] cybertec69:
RC4 is ready for flashing.
[Verizon Samsung Galaxy S III] VinBertinelli:
**edit** I think I just made an android pun >_<

Man these RC builds are like clockwork.
[Verizon Samsung Galaxy S III] Snakehn:
yeah mine was showing 8GB used after just a few hours of usage, also what's up with the camera on these RC3, RC4? its the basic one and freezes when trying to take a picture.