yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] AyUaxe:
Now on 5/14, tried FFC in full, but not direct day light. Took 2 pix fine then locked on 3rd. Hard reboot required. Good news is reboot proceeded as normal, maybe a bit quicker than I've seen in a while. BT audio seems at least as goods as ever. Battery did seem worse on last couple of builds, so that's something I'll be watching for. Best to all!
[Verizon Samsung Galaxy S III] Jaws4God:
*note to everyone else* [MENTION=3056030]AyUaxe[/MENTION] has a special version phone where his camera works on builds and ours typically don't.. LOL :silly:
[Verizon Samsung Galaxy S III] YabbyYou:
I would be curious to know if anyone else reading this thread has the same rev as [MENTION=3056030]AyUaxe[/MENTION] , Samsung m2, CPU armv7 rev. 4 (7I). If you wouldn't mind checking and report back to the group, that'd be helpful. You can use an app called "Phone Tester" or the Kernel Adiutor app to get the info.
[Verizon Samsung Galaxy S III] Fenix2002:
Mine fits into that category. Haha. But it only marginally works better than what everyone else reports. It's not usually any better than anyone else's on most things. Very very rarely I can get the ffc to work better than others report. Although, if you're interested in selfie pictures, I have had great luck with Retrica. Almost never any force closes, but that's because it doesn't really attempt to focus or auto-contrast or whatever it is that the camera normally tries to do in bright light.
[Verizon Samsung Galaxy S III] Jaws4God:
I seemed to have had some issues with this APP.. freezes occasionally.. are you on 5.1 or 6.0 android?
[Verizon Samsung Galaxy S III] Fenix2002:
Latest AICP 6.0 nightlies. Haven't tested Retrica in a week or so, but last time I tried it it mostly worked. It's not 100%.
[Verizon Samsung Galaxy S III] Jaws4God:
well i installed it... and when i went to swipe finger on screen to switch the picture style, it froze up and then my phone seemed to stutter around until i un-installed it. anyone else experience this with Retica?
[Verizon Samsung Galaxy S III] jtnc:
So I too have a v4 CPU. Currently have flipped back to 12.1 as the Bluetooth isn't stable for me on 13 in any configuration. 13 has gotten a bit better now, but I want both phone and audio in the car which means back to 12.1. I keep saying I want to go look at the code, but not sure that'll ever happen.

But as to the front facing camera, when I have tested it, it's been fine on 13. Though I did switch to using OpenCamera a while back as it was behaving fine for the normal camera. I'll have to try it on a future 13 build again and see.

I miss the battery life 13 gave me, but 12.1 plus powernap isn't too bad and BT works.

FWIW DKP kernel has never been stable for me, so I always stuck with the stock CM kernel.

John
[Verizon Samsung Galaxy S III] Fenix2002:
That's unfortunate. It worked most of the time for me when I was using it. I could do as many shots as I wanted, even in full sunlight, but if I switched apps, my phone would lag and stutter until I force closed it through settings. I never had any luck with the stock camera or OpenCamera though. Keep in mind, I do have the v71 rev4 model, IF that makes a difference at all.

Sometimes it's a fluke, other times it just takes trial and error. Either way, happy flashing and good luck, all.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Apps that manage to weasel out of a crash from the camera just require a reboot to act normal again, uninstall shouldn't be necessary, and I'm honestly kind of surprised that works, since a force close of apps after an almost-hang doesn't seem to fix anything for me.

Edit: Maybe it does and I just don't notice, Fenix2002 says force closing makes things normal again
[Verizon Samsung Galaxy S III] dvschnk:
Hey Jaws, saw you poking around over on the AT&T S3 thread. Looks like they finally fixed the ffc problem on the d2att. Now from the last guy that responded to you, I wonder how hard it would be to push the fix upstream to official CM13 so that it fixes all d2 variants (which I would assume to suffer from this issue, just a guess...haven't poked around the tmobile or sprint threads). Anishs did say that the fix was easily implemented.
[Verizon Samsung Galaxy S III] Jaws4God:
yeah it sounds encouraging... so hopefully the incredible team of CM can see if it is an easy implemented fix and we can finally have a VZW working FFC for MM! :D (pssst [MENTION=2385005]invisiblek[/MENTION] ;) )
[Verizon Samsung Galaxy S III] ridzuan122:
Help me please. I flash this rom yesterday. (Cm13.0-20160520-NIGHTLY-i9300). I can't receive any phone call. Everytime incoming phone call my device will boot to cyanogenmod logo. What should i do? Im new here. Please help me. Thanks.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I was gonna wait for someone more experienced to chime in with a response, but here goes my explanation, haha...

This ROM is specifically for the SCH-i535 Verizon variant (some others work with modification) with the Snapdragon processor and north America APNs, your variant is the international version and has the Exynos processor.

Have you tried looking in the i9300 forums for a CyanogenMod build of CM13?

Maybe since it DOES work, just not for calls, its as simple as changing Settings -> Cellular Network -> preferred network type to something that includes GSM if it's not already selected.

My guess is it's more complicated than that though
[Verizon Samsung Galaxy S III] dvschnk:
Anybody tried the 5-30 nightly? From looking at the changelog and also whats been said over at the d2att forum, some of matrixzones camera edits have made it into CM13 official nightlies.
[Verizon Samsung Galaxy S III] Jaws4God:
well i have the 5/30 version of AICP 6.0 and the FFC looks like the proportions are incorrect.. plus it did FC when taking picture... downloading the 5/31 version right now... :fingers-crossed:
[Verizon Samsung Galaxy S III] adobeman:
Yeah, 5/30 FFC proportions wacky for sure in AICP and FCs when used. 5/31 wasn't there when I flashed this morning. I'll be eager to hear what you get with 5/31
[Verizon Samsung Galaxy S III] Jaws4God:
5/31 proportions are back correct.. still FC'ed :(

:(
[Verizon Samsung Galaxy S III] dvschnk:
Boo. But I may have jumped the gun a bit...seems like 531 is giving people over at d2att some trouble too with FFC FC....the wait continues
[Verizon Samsung Galaxy S III] atomicgarden:
Front Facing Camera

Front facing camera is working for me on 6/1. I've got CPU armv7 rev. 4 (7I), but wasn't working on 5/14 like it was for some.

Has anyone else been having trouble with mobile data / voice connection? The past several builds my phone has been having trouble with one or the other. I couldn't receive or make calls for a while, eventually realized that prefered network type had set itself to LTE only. Setting it to CDMA + LTE/EvDo got voice working but instead of LTE it only connects to 1X. So far seems like the same behavior on 6/1

Edit - welp, every camera app has been crashing/causing reboots. Snapchat was just working better than it did yesterday. I've heard that it doesn't really take a picture like a real camera app, just screenshots the viewfinder.
[Verizon Samsung Galaxy S III] Jaws4God:
so the stock FFC works for you but any apps using the camera crash and reboot?
[Verizon Samsung Galaxy S III] atomicgarden:
Apps meaning camera apps. Tested a little more today. Open Camera in medium light caused reboot. Google Camera force closed in dim light. CM Camera took one photo in dim light, force closed in medium light once and rebooted the second time. Snapchat worked last night pointed directly at a light bulp - it was freezing even in dim light on 5/30. So, things are better at least.
[Verizon Samsung Galaxy S III] Jaws4God:
does anyone know if the stock messaging app will get a signature option? Thanks!
[Verizon Samsung Galaxy S III] YabbyYou:
Is anyone else having data connectivity problems? I was going to make the jump to 6/1 but now I'm not so sure. I'm still sitting on 5/9.
[Verizon Samsung Galaxy S III] AyUaxe:
On 06/01, very smooth, quick, good battery life (though in WiFi only/airplane mode). FFC took 2 or 3 pix in outdoor daylight, then froze hard. How would one pull a crash log under those circumstances, i.e. where the crash locks up the device? Only hardware button that works is long press power to shut down. Otherwise, awesome, though I can't comment on 4g, since this d2 is no longer activated on VZW.
[Verizon Samsung Galaxy S III] Jaws4God:
Interesting.. hope its close to being fixed! :fingers-crossed::fingers-crossed::fingers-crossed:
[Verizon Samsung Galaxy S III] AyUaxe:
6/11, dirty flash (wiped caches)+dkp, FFC working perfectly in full outside morning light! Snapped about 10 pix without a hitch. All hail [MENTION=2385005]invisiblek[/MENTION]! Will edit as I try other things.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I'll give it a go tonight and try to report back tomorrow, I have a different HW revision.
[Verizon Samsung Galaxy S III] Jaws4God:
how exciting!! but i do remember it did work for you other times when it didn't for some of us with other hardware versions... :)
[Verizon Samsung Galaxy S III] AyUaxe:
Me and [MENTION=7430804]atomicgarden[/MENTION] have the same hw rev., it seems, but have only seen marginally different results from the majority of commenters on all the I535 threads. My money is on [MENTION=2385005]invisiblek[/MENTION] and awesome cm team having fixed the issue. BTW, still don't get the fascination with FFC. I'll never post any of the test pics I've taken-****e, I look awful.
[Verizon Samsung Galaxy S III] toosurreal01:
Because snapchat :laugh:
[Verizon Samsung Galaxy S III] Jaws4God:
has anyone else been able to check the FFC on this build? i'm curious to see if more people are seeing this fixed ? :fingers-crossed:
[Verizon Samsung Galaxy S III] Roger W:
Unfortunately, same FFC hang as ususal for me on 6/14 after 1 picture.
[Verizon Samsung Galaxy S III] AyUaxe:
Can you try 6/11 while it's available?
[Verizon Samsung Galaxy S III] Jaws4God:
are you thinking maybe the 6/11 works but 6/12 and 6/14 may have re broke it?

sent from Samsung S3
[Verizon Samsung Galaxy S III] YabbyYou:
I just flashed up to 6/14 (from 5/9 :cyclops: ), FFC hard crashed. I wish I saw your post earlier [MENTION=3056030]AyUaxe[/MENTION], I would have made a pit stop at 6/11 to test, then flashed up to 6/14. I'm reluctant to go backwards at this point. I'm downloading the 6/11 nightly anyway so I have it in case I feel adventurous.
[Verizon Samsung Galaxy S III] AyUaxe:
Sometimes it seems like we get a really solid build, then it's two more steps backward before the next steps forward. No dis to [MENTION=2385005]invisiblek[/MENTION] or the rest of the CM team--I get that they're basically working through a digital and hardware forest with no map.

Can't help but love having the "special" d2, but I'd rather all of y'all could enjoy having all of your stuff work. BTW, BT seems pretty solid on 6/11, battery life is good and I really like Gello, except it needs better tab and user agent management--as in it needs some, 'cause it seems to have almost none of that now--it does seem subjectively faster than Chrome, Opera, or YuBrowser, though YuBrowser (Chrome based, I think) seems close.
[Verizon Samsung Galaxy S III] XdrummerXboy:
6-13 FFC is still freezing and stuff.

I said I'd report yesterday, I'm a bit late, sorry!
[Verizon Samsung Galaxy S III] dvschnk:
Just put 6/11 on my S3 last night after reading through the page. FFC is still borked for me when using stock camera, open camera, and instagram. I have a rev 0 processor which is what most of the early adopters have, but just wanted to report my results. Also, I'm running stock CM kernal, not DKP...but I don't think that should make a difference.
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks for giving it a go. Could you give it a try with latest dkp? That's what works for me . Best to the whole dev and user community. And to Rufus Thomas, for the Memphis Train.
[Verizon Samsung Galaxy S III] dvschnk:
12/27 is the "latest" dkp right? Just want to make sure I'm grabbing the right file.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I know there were issues with Bluetooth phone calls several weeks ago. I thought they were fixed at one point but I could be totally wrong about that.

Anyways, last night I had a few instances of weird behavior, freezing/restarting, and being unable to hang up while connected to my car's BT head unit.

This is on 6-13 nightly
[Verizon Samsung Galaxy S III] AyUaxe:
I thought [MENTION=4932679]decimalman[/MENTION] had put out a minor update, but the latest downloads appear to still be from 12/27. Fingers crossed for good results!

BTW,wtf, nobody's picked up on the Memphis Train?https://m.youtube.com/watch?v=hYlSisv-VRU

Listen while you wait for that next build. FYI, Hulu is running Jarmusch's diamond in the delta rough, Mystery Train. Look for Rufus Thomas, Screamin' Jay Hawkins, and Joe Strummer, among other luminaries from the funky world before smart phones.
[Verizon Samsung Galaxy S III] dvschnk:
Just wanted to report back, 6/11 with dkp kernel still has problems with ffc. It works indoors with open camera, but is very jittery. Outdoors, open camera is way too sensitive with the light sensor and basically everything is white. If I mess with white balance, then the app freezes up. Any other camera app, the app force closes and then the camera is locked up until a reboot. At least most of the other apps don't cause a hard lockup and root...I guess that's progress.
[Verizon Samsung Galaxy S III] AyUaxe:
This is really weird. I've attached two of about ten test pix taken on 6/12 with FFC (not showing my ugly mug, tho). Very contrasty but functional. [MENTION=2385005]invisiblek[/MENTION], is the anything I can do to help get this result for all d2s? It's lonely out here!
[Verizon Samsung Galaxy S III] dvschnk:
I got my FFC to work consistently now! I've tested the results with build 6/11 with DKP kernel, and it also works with build 6/18 with stock kernel. But I'm not completely sure about 6/18 because I dirty flashed from 6/11. So before I get into the further detail, what I did was set SELinux to permissive. You will need root enabled, and this can be done through terminal emulator with the following command:

su
echo 0 > /sys/fs/selinux/enforce

(NOTE: This command is only temporary, and after a reboot, SELinux will be enabled again). Once SELinux is set to permissive, open up all your camera apps and test the FFC. From what I tested, stock CM camera, open camera, and CameraZoomFX works with the FFC and also video capture with the FFC works. Video chat with Hangouts also works. Even, after a reboot and SELinux is back to enabled, the FFC still works in all the camera apps. Instagram is the one app that doesn't work so far...and it causes a hard crash and reboot.

Now, I'm hoping others can give this a try, and report back whether FFC is working, and which nightly they're on, and what camera related apps do and don't work.

A bit of background of how I came about this solution. First setting SELinux to permissive or even disabled is a very brute force or scorched earth method to solving the camera issue. I knew there was an issue with SELinux regarding the camera from matrixzone (a big contributor over on the XDA At&T S3 forum) through his commits history on the CM Gerrit code review. What he's trying to do for the d2, and not just d2att is to properly write the correct camera access controls for SELinux. What makes it even harder is that the official CM code reviewers like all code projects want things to be done in a certain way. After reading over the code review comments, I get the bright idea to just say screw it, and open up SELinux and see what happens....and boom things work for the most part. What's even better is that the camera stays working even after a reboot, so that I'm not leaving SELinux off all the time still keep my phone relatively secure.

So if this fix works for everyone, all credit goes to matrixzone and i'm pretty sure soon down the line, he will have something submitted to the official repo where everything is correctly written, and we will not have to use this method anymore. One other thought, since I'm not much of a bluetooth user, I haven't experienced first hand all the bluetooth issues. I was wondering if people who set their phones on permissive could go through their bluetooth tests and see if they see an improvement there...just a thought.
[Verizon Samsung Galaxy S III] AyUaxe:
The audio mod I've been using, Viper DD+ 5.5 beats edition, includes a script to set permissive, so that's probably why FFC worked for me, too. With "stock" viper, I use an app from XDA called selinux mode changer. Easy toggle or set to run at start, if you're secure in your insecurity (not recommended).
[Verizon Samsung Galaxy S III] XdrummerXboy:
Thanks for looking into that, I'll definitely be giving this a try later today
[Verizon Samsung Galaxy S III] dvschnk:
Haha, I had a hunch that you probably used something like VIPER and had SELinux set to permissive because of it. Makes a lot of sense now why you had consistent luck with the camera now.
[Verizon Samsung Galaxy S III] invisiblek:
06-19 15:35:38.172 2072 2072 W mm-qcamera-daem: type=1400 audit(0.0:12): avc: denied { create } for name="RS_0.log" scontext=u:r:mm-qcamerad:s0 tcontext=u:object_r:radio_data_file:s0 tclass=file permissive=0

well would you look at at that

fixed: http://review.cyanogenmod.org/#/c/150211/
[Verizon Samsung Galaxy S III] dvschnk:
Awesome...there's the clean solution. I knew you guys would get it through soon...just didn't expect it to happen 1 day after I figured out what you guys were trying to do, and took the nuclear option of just opening up SELinux. Nice work!
[Verizon Samsung Galaxy S III] dvschnk:
One more comment....I actually looked through that commit...wow, can't believe the limiting factor was that selinux wouldn't let the camera create a specific log file...a freaking log file...and then the whole FFC would just die from that...it just seems so trivial.
[Verizon Samsung Galaxy S III] YabbyYou:
Yeah, that's selinux for you! When they say Security-Enhanced Linux, they mean it! Nice job tracking this down [MENTION=3316305]dvschnk[/MENTION] and it's always great to see [MENTION=2385005]invisiblek[/MENTION] check into the thread!
[Verizon Samsung Galaxy S III] XdrummerXboy:
That's awesome guys! Thanks!
[Verizon Samsung Galaxy S III] lepa71:
Does that mean we have a fully working both cameras? Thanks
[Verizon Samsung Galaxy S III] YabbyYou:
Lepa, I haven't installed the nightly from last night that supposedly includes the selinux fix (EDIT: it's actually the 6/20 nightly that contains it), I'm still running the 6/14 nightly. I'm sure someone else will install it and chime in shortly.
[Verizon Samsung Galaxy S III] Roger W:
Yep, 6/20 fixes it for me! Thanks [MENTION=2385005]invisiblek[/MENTION] !
[Verizon Samsung Galaxy S III] atomicgarden:
FFC actually not working for me on 6/21. Still force closing both CM camera and Google camera. I wonder if Xposed has an effect. After doing a clean install of 6/14 the other day CM camera hamburger menu caused force close only after installing Xposed..

Still having connectivity issues even after that clean install, about halfway through the day yesterday I stopped being able to connect any calls at all, even when set to CDMA only. Starting to suspect the radio is dying on my phone.
[Verizon Samsung Galaxy S III] Stealth111:
I started having connectivity issues yesterday as well. I have been flashing nightlies for years. I suspect something else is amiss, and not your radio. I have my old faithful S3 stop working after an update yesterday. I pulled my brand new spare out of the box for the first time ever yesterday, and got it all up and running on the latest CM13 Nightly and when it booted up it was on Verizon wireless for about 2 seconds and then went right to NO Service, rebooted a few times, reinstalled, and even brought over my backup, as well as tried new sim card, same effect, Verizon for a second, then right to no service. Airplane mode has same effect. I thought it was from the straighttalk APN, but deleting it didn't fix it either. I messed with it for 4 hours last night and somehow got it working. As soon as I flashed today's nightly and rebooted, I am back in the same boat. I even went back to a nandroid from last week. I thought it might have been an outage issue, so I decided to flash back to the original 4.1.2 rom that I backed up from when the phone was new. It immediately connected to the network and was fine. So I now know it was NOT an outage, and it must have been the ROM, or something got borked with the sim card (even though I tried a new one), because when I wiped, and flashed my nandroid from today, it booted and got right on the network like always... Strange.. Stay tuned! Tomorrow another nightly will be out and we shall see if it gets blown out again!

Stealth111
[Verizon Samsung Galaxy S III] XdrummerXboy:
Xposed doesn't seem to affect me. Haven't extensively tried the camera, but it seems like it's fixed.

It does seem like connectivity isn't as good lately for me too, needing to toggle airplane mode and stuff, but my phone could be dying too. It did have its 4th birthday like 2 days ago after all, haha!
[Verizon Samsung Galaxy S III] dvschnk:
Yeah, I get the connectivity problem too, but I think it has more to do with the code than the phone. Mine typically happens on crashes that forces a self reboot which I think half the time is really a soft reboot, and since cm12.1...soft reboots have always caused a connectivity problem for me. But like you said, a toggle of airplane mode usually brings it back or switching the mobile apn to something else then back to vzwinternet (interesting...just noticed the default was set to straighttalk_vzw and not the usual vzwinternet)

Now for [MENTION=7430804]atomicgarden[/MENTION] problem, that looks a bit more extreme. I wonder if you disable your xposed modules if you get more stability just as a check, and then slowly enable them 1 by 1. Also for your FFC problem, 6/21's been working for me...but I've dirty flashed all the way from 6/11....you could always manually but temporarily try setting your SELinux to permissive like I mentioned in my earlier post, and see if that fixes your problem.
[Verizon Samsung Galaxy S III] atomicgarden:
The connectivity was bad on 6/14 before I flashed Xposed. Other than the camera and CDMA, stability had been more solid that it has since CM11. Anyway, flashed back to CM12 last night and successfully made a call, so it would appear to be something software related after all. I'll see how long I can be content with Lollipop before I give CM13 another try...
[Verizon Samsung Galaxy S III] YabbyYou:
I'm on 6/14 still and I'm not experiencing any connectivity problems (yet?). 3G/LTE connects consistently. I'll probably hang on 6/14 until the connectivity issues clear up on the newer nightlies.
[Verizon Samsung Galaxy S III] toosurreal01:
I'm on the 6/21 build and am not experience any issues with connectivity. LTE and Wifi are fine and not getting any drops.

Can make calls, etc...

FFC working in all lighting I've tried so far.

Pretty solid!
[Verizon Samsung Galaxy S III] atomicgarden:
I'm back to being convinced that the issue is a hardware one. LTE briefly worked on CM12.1, and now I'm back to 1x only when phone signal is enabled. Better than the other day on CM13 when phone signal stopped entirely. Haven't found a way to toggle between LTE/no-voice and voice/no-LTE, but voice is more important.

My point being, I don't think anyone should be really worried about CM13 causing this issue.
[Verizon Samsung Galaxy S III] iwearthebelt:
I was having issues with my signal dropping out on me while on the last couple of nightlies. Wasn't sure why but a toggle of airplane mode usually fixed it. If not, a battery pull would. Anyway, since updating to the most recent nightly 6/24, I haven't had that issue anymore. Just thought I'd let you know in case you want to give that latest nightly a try.
[Verizon Samsung Galaxy S III] AyUaxe:
I love this community, man! And scotch!