yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Jaws4God:
has there been any updates on the FFC ? [IMG="https://i2.wp.com/img.android-apk.org/imgs/3/4/0/3402432e228cc87ad21d5749b1688bbe.png?resize=36,36"]https://i2.wp.com/img.android-apk.org/imgs/3/4/0/3402432e228cc87ad21d5749b1688bbe.png?resize=36,36[/IMG] :)
[Verizon Samsung Galaxy S III] Master Cylinder:
Yo - this phone still has quite respectable specs, removable and upgradeable memory and battery, and is in use throughout the world in VAST numbers! (not d2, of course. Though people are taking it to places like England India and such, flashing your gsm rilblobs, even on MM, and goin' to town!)

And, with MM, performs really well! There are even 2 other cutomized ROMs for it, though they are based on CM too, so problems tend to proliferate to them, but you might ask over on the OctOS thread and see what someone has to say over there since they have developed their own kernel and are working directly to patch the few issues left.

:good:

EDIT: And it's unlocked!
[Verizon Samsung Galaxy S III] Fenix2002:
I guess my terminology is right.. It's just a backup/restore from recovery. Lol. Nand is basically just 'permanent' flash memory, like the internal memory the phone uses, as I understand it anyway. Lol
[Verizon Samsung Galaxy S III] matt_man:
I clean installed the 12/18 build today along with opengapps nano and I can't get the Google+ app to install. Has anyone else had trouble installing G+?
[Verizon Samsung Galaxy S III] invisiblek:
Oops, sorry about the latest build not having data. Should be fixed in the next one =)
[Verizon Samsung Galaxy S III] static.chaos73:
I lost telephony as well as USB mounting with the 12/19 update...the computer doesn't recognize my phone anymore.
[Verizon Samsung Galaxy S III] static.chaos73:
After losing the SIM on the 12/19 build, I tried to go back to 12/18 and still can't get my SIM recognized. I tried restoring a prior backup and still no luck. Any ideas on how to restore functionality? I use a T-Mobile SIM, so usually have to go into cell settings and choose a GSM or Global, but all options are greyed out and I can't make the changes. I tried installing the Network app from the Play store and it won't let me make changes there either. However, in the Network app it recognizes that I am on the T-Mobile network, the signal strength is normal, but not reading the phone number etc.

I'm going to try installing CM12 and see if that will put things right again, but in the meantime if anybody has any ideas, it would be greatly appreciated!
[Verizon Samsung Galaxy S III] Fenix2002:
I had the exact same issue you describe where everything is greyed out. Going back to CM12.1 fixed the issue for me (I went back from a nandroid backup. I suggest always keeping a recent nandroid if you don't already.) It sounds like invisiblek knows what the issue is and will have it fixed soon!
[Verizon Samsung Galaxy S III] static.chaos73:
I still haven't been able to fix it...I'm on 12.1 now and having the same issue. I even tried going back to the MIUI 4.2 lol . . . I'm worried I might have permanently broken something that even the new update won't fix! I do the backups through TWRP, the same issue showed up on the backup too.
[Verizon Samsung Galaxy S III] Fenix2002:
Oh man, that's not good. Might've nuked your IMEI or something. *shrug* a little out of my depth on that one. :/ I guess I was lucky getting mine to work. When you restored from TWRP, was everything still greyed out and not available?
[Verizon Samsung Galaxy S III] static.chaos73:
That's the weird part...the IMEI shows up and now I can make phone calls even though it shows 'no sim' message. but can't change APN or turn data on etc. Yeah after the backup was restored it was all fine except for the mobile networks settings. I put a Verizon SIM in and it detected it just fine, so I'm thinking it might have been something that disabled GSM/global settings somehow. Luckily I have a backup phone!
[Verizon Samsung Galaxy S III] static.chaos73:
Apparently my SIM problem is with any non-Verizon SIM now. I threw an old Verizon card in the phone and it got a signal and no errors. I tried putting the T-mobile sim back in and it still gave me the 'no sim' error. I tried another SIM that worked in my phone last week from Tracfone and it did the same thing - 'no sim'.

Could there be some glitch in the last update that made my phone lock out any non-verizon SIM cards? Is that even a thing that happens?
[Verizon Samsung Galaxy S III] static.chaos73:
woohoo...12/20 update fixed it! Thanks!
[Verizon Samsung Galaxy S III] Jaws4God:
how are the cameras?

overall considered stable?
[Verizon Samsung Galaxy S III] Roger W:
I'll upvote your encrypted storage theory. I've just tried a dozen combinations of getting to CM13 including upgrades from 12.1, and clean installs of various nightlies (excluding 12/19 which apparently had other problems), and none of them could find my SIM until I formatted my encrypted data partition.
[Verizon Samsung Galaxy S III] pogeymanz:
Can you clarify whether you re-encrypted your data partition after you formatted it?

I did have it find my SIM card a couple of times, but then as soon as I would reboot, it wouldn't see it anymore- it was very strange. I had to do a specific ritual of installing, running the nuke_it.zip, and wiping in a certain order. I'm still on 12.1 for now...
[Verizon Samsung Galaxy S III] Roger W:
I'm currently installing my apps, then I'll do a backup and encrypt before setting up any sensitive data again. I'll edit this post with results later today.

Edit: Unfortunately, encrypting the clean install of today's nightly brought me right back to the no-SIM error.
[Verizon Samsung Galaxy S III] static.chaos73:
I haven't run into any other bugs. The stock camera works front and camcorder, but I still can't get front-facing photos to work, it just doesn't take the picture.
[Verizon Samsung Galaxy S III] XdrummerXboy:
If all else fails, I have a stock 4.3 unlocked bootloader image from scottsroms that includes drivers and all that good stuff if you want to try flashing it. Probably overkill, but whatever :D

Coming back to CM13 you'd possibly need to reflash the MF1 firmware, but pretty certainly the NE1 modem.
[Verizon Samsung Galaxy S III] Jaws4God:
is the CM team still releasing updates? i haven't heard much on here of recent nightlies
[Verizon Samsung Galaxy S III] YabbyYou:
Hey Jaws, releases still seem to be flowing. I was sitting on the 4/12 nightly for a bit since Bluetooth started working and I was so happy about that. I *just* finished flashing the 4/22 nightly. Running it through the paces now.
[Verizon Samsung Galaxy S III] beckx020:
I think everyone is waiting for BT to work properly. Which, I'm going to try the 4/22 build this afternoon also.
[Verizon Samsung Galaxy S III] YabbyYou:
Damnit! Now that you pointed this out Roger I do notice the compass is misbehaving. It's not something I've been actively checking on my nightly installs so I don't know if it worked at all on a past build. If anyone is running any builds prior to 4/12, please check your compass and let us know if it's working or not. I can open a regression bug report but I need to know a Last Known Good build date. Hopefully someone can locate it. I know it's not working on the 4/22 or 4/12 builds.
[Verizon Samsung Galaxy S III] Fenix2002:
I don't think compass has worked properly at all on CM13. I think the last time it was mostly accurate was at the end of CM12.1.

When I get home tonight (or maybe tomorrow), I'll test it on 3/31 if nobody gets to it before me.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I can semi-confirm. Compass has pretty much always (at least as far as I can remember on MM) shown the wrong direction, nearly 180 degrees off.
[Verizon Samsung Galaxy S III] YabbyYou:
OK. Consensus seems to be that as of CM13 we have not had an accurate compass. So I can't open a bug report on the nightlies tracker because it's not a regression. Is anyone running the CM13 stable build? We could potentially open a bug report on that tracker.

Or, if it's not a big deal we can just be all whatever about it. I have grown accustomed to the poor gps/navigation on the S3. That will definitely be one of the great perks of getting a new phone, proper, consistent navigation.

Just a quick update on the 4/22 nightly. It's been running great. No reboots, Bluetooth is working well (barring any misbehaving apps), sensors seem good (minus the compass), GPS locked on though I did not navigate yet. I'm not running the dkp kernel yet, just the delivered cm kernel.

OK, back to watching the late, great Prince shred While My Guitar Gently Weeps during the Rock and Roll Hall of Fame Induction ceremony.
[Verizon Samsung Galaxy S III] phonetool:
Don't know about 13.0, but my compas on 12.1 is pretty flakey. GPS and Maps works ok, but my compas app and ISS detector app both are 180 out. So, maybe not a bug that is special to 13.
[Verizon Samsung Galaxy S III] beckx020:
Compass on 4.4.2 is at 306 degrees NW (correct I believe) On 4/22 build it's at 7 degrees N. Those two S3 phones are about 1 foot apart.

But Google maps cannot find my location either. (sigh) GPS status shows a lock within 30 feet. Don't know what the problem is.

BT on 4.22 build still crashes the whole phone when getting a call. But it works otherwise for me. Camera in low or high light, front or back works ok too.
[Verizon Samsung Galaxy S III] Deliquified:
Can anyone confirm if the FFC works and Skype video calls work on latest builds?
[Verizon Samsung Galaxy S III] AyUaxe:
4/23 performs well except FFC freezes system in full office light. Have to dig or a speaker to test BT. Decided it was my ear piece, rather than d2 that's f'd, since it's same for my stock xt1254.
[Verizon Samsung Galaxy S III] Jaws4God:
this may be a silly question, but why does the FFC have all of these issues when they were able to get the rear camera to work so well? I would think the code would be the same / very similar ? I have very little understanding of Android code.. so this is an honest question.
[Verizon Samsung Galaxy S III] AyUaxe:
I think that's a reasonable question. My thought is if it worked in L, why's it so hard to get it working in M? Is there an app that automates comparison of one batch of code to another, so one could see what's the same and different between a last known good L build and a current/proposed M build?
[Verizon Samsung Galaxy S III] YabbyYou:
I'm going to go out on a limb here and say it's probably much more complicated then we can imagine. While it may seem like a simple thing on the surface, there must be all kinds of changes under the hood that cause this problem. Also, I believe the front and back camera modules are both different, so there's a pretty good chance the code is completely different to interact with them. The other reason I think it's very complex is because you can see there are camera issues with all different phones running all different versions of CM. This suggests there are a lot of permutations of code to handle your finger pressing the the 'Take Picture' button on a multitude of devices. I'm amazed it works at all! The devs that take time to work on the CM code have got to be some of the best out there. I can't even imagine trying to figure some of this stuff out having ZERO documentation!

That being said, our issue with the front facing cam crashing in bright light is interesting. To me, that suggests a problem with the focusing code. It could also be something where the dev borrowed some code from the rear facing cam that doesn't quite behave properly with the ffc, that sorta thing.

Not sure if that answered you, but I just thought I'd jump in on the question. I have been on the 4/22 build for a few days now and it's been running great. I'm not on the dkp kernel, just the stock kernel. Bluetooth has been working well (as long as I force close the WeatherBug app).
[Verizon Samsung Galaxy S III] Jaws4God:
thanks so much for letting taking the time to respond.. I do figure its more complicated than it appears.. I hope i didn't offend any DEVs because that was not my intention.. im amazed and so grateful for all the work they do and how my old phone can be on one of the newest versions of android.

I guess I'm more curious if the FFC has the potential of being fixed or is close or is there a reason it isn't fixed.. I also wonder if "N" development has started so will the MM FFC never get resolved.. LOL

via Tapatalk (AICP 6.0.1)
[Verizon Samsung Galaxy S III] dvschnk:
I've been lurking over on the AT&T S3 forum, and like someone else stated a few pages back, it looks like matrixzone over there has a lead on the problem and he was pushing out test builds over there. But then the VM (Virtual Machine) that he does his testing or compiling (he didn't state) wouldn't boot up (not because of modifying android code, but just a software bug of the VM...this has been happening to me in VirtualBox too). So what seemed like quick progress is now delayed. He's been silent for a week I think, so I'm hoping he's making progress. Whenever he gets it going and working, it'll be pushed upstream to the CM13 codebase, which will hopefully then fix all d2 devices with the ffc problem.
[Verizon Samsung Galaxy S III] AyUaxe:
4/29 seems a bit faster than 4/23 (both with DKP) and BT is streaming Mozart Milanese string quartets to an external speaker very well. Since this phone no longer has cell service, can't check to see if BT will hand off between calls and music. Battery life has been very good.
[Verizon Samsung Galaxy S III] XdrummerXboy:
4/30 is borked for me.

Google Play Services keeps force closing. Could be the way I flashed it (using multiple zips at once in TWRP) or maybe I forgot to clear cache. It was a long night/morning, so who knows.

I'll try reflashing the normal way and report back

Edit: same result!

Edit 2: well shoot, 4/29 is giving the same result. Time to clean flash I think :/ or just reflash GApps maybe?
[Verizon Samsung Galaxy S III] YabbyYou:
Do you check the checksums on your downloads? Maybe it's a bad download. Reflashing gapps could help too. What gapps build date are you using?
[Verizon Samsung Galaxy S III] XdrummerXboy:
Certainly could have been a bad download. It was GApps from long ago, I dirty flashed today's nightly over the 27th or something like that. My last clean install was somewhere in early January. The GApps worked well for previous builds, so the zip itself was fine, but the install may have gotten corrupt somehow.

Anyways, a clean flash of the 30th with today's GApps worked for me, but when I get a call the phone app force closes, but the call still goes through, so I just can't "end" it. This has only been a problem with bluetooth calls in the past I thought... Has it been an issue with all calls for you guys? I rarely get a phone call, so I wouldn't know.

Edit: some other weird things happened, namely an installed app completely disappeared from the stock launcher, and didn't show up in Play Store as being installed, and couldn't re-install it, yet still had the apk and such in /data/app/. I did a clean flash of 5/1 and things seem to be better, only time will tell. Also, could 100% be an error on my part or gapps or something unrelated to the ROM.
[Verizon Samsung Galaxy S III] YabbyYou:
I just flashed the 5/2 nightly. Running it through the paces now. I'm not seeing any of the weirdness that you saw [MENTION=4652020]XdrummerXboy[/MENTION] . I will try to test the situations you had problems with and see if I run into any of them. BT is still working, listening to music as I type this. FFC still wonky.
[Verizon Samsung Galaxy S III] XdrummerXboy:
5/1 notes:

BT works MUCH better than the previous nightlies I've been on. A couple very minor hiccups, but no "glitches" every ~45 seconds like on other nightlies.

My phone froze when I got a call while listening to BT audio, but that's been an issue for a while.
[Verizon Samsung Galaxy S III] YabbyYou:
I'm going to try and test a bunch of phone call scenarios tomorrow if I have some time. I'll call my mobile from my work phone and see what situations crash what.

BT working well for me too. GPS was OK, not good or great, just OK. Compass is still funked. Other things working well. Speed and battery life are acceptable so far.
[Verizon Samsung Galaxy S III] Jaws4God:
I am starting to realize now how much GOOGLE apps take up battery life... for they past month or so i've been using the

PICO GAPPS

(bare minimum).. and noticed amazing battery life.. in the last few days, i went to the

NANO GAPPS

(minimal Google apps) and now already seen a noticeable dip in battery life.
[Verizon Samsung Galaxy S III] YabbyYou:
Absolutely! More apps = more battery! Or is it Mo' Money, Mo' Problems? :)

You'd think the Google apps would manage their resources better, but I guess not.
[Verizon Samsung Galaxy S III] Jaws4God:
I guess i always assumed as long as you weren't using the app itself, it wouldn't take much battery.. but that appears to be flawed thinking.. I think i always put to much credence into the ROM and KERNELS way of managing resources and thus was the reason for more of the "battery draining issues"... looking like i may have to go back to PICO.. lol

You would think that since Android does great with DOZE to manage battery life, that its apps would do likewise.. guess not.. LOL :eek:
[Verizon Samsung Galaxy S III] adobeman:
Interesting since I think going from pico to nano only adds Google Search and Hotword. So if you enabled "OK Google" detection for from any screen that will use battery. I believe you, just surprised. I figured play services was the major hog and it's in all gapps.
[Verizon Samsung Galaxy S III] Jaws4God:
Yeah, that was the main reason i went from Pico to Nano (Google Search / Google Now on Tap).. but for the loss in battery, i may go back to the
[Verizon Samsung Galaxy S III] Roger W:
Just installed 5/4 to get the monthly security rollup. Haven't seen any new problems; fc still hangs. But it seems safe to install.
[Verizon Samsung Galaxy S III] Jaws4God:
I am installing the 5/6 AICP right now... did CM have a 5/6 version? how is FFC :confused:
[Verizon Samsung Galaxy S III] YabbyYou:
The rear camera in 5/2 is being a little....... testy. I can take a few pics then it seems to crash. A little while ago I just took 1 pic, then it crashed. Not sure what's going on yet.
[Verizon Samsung Galaxy S III] AyUaxe:
5/7 and both cams work! At least FFC worked for 3 pics under a 13 watt cfl light-so not very bright, but not dark either. Took one pic pointed right at light but it didn't freeze. A week ago, I think it would've. Haven't tried anything other than WiFi net browsing and file browsing with es. All stable, snappy, and smooth. I'll update when I get a chance to try BT.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Thanks! Dirty or clean flash?
[Verizon Samsung Galaxy S III] AyUaxe:
Down and dirty. Just wiped caches after flashes. Also my usual dkp and dkpvmin800. No other changes at this time. Will be interested to hear how phone functions work for those who still have d2 DDs.
[Verizon Samsung Galaxy S III] Jaws4God:
encouraging!! anyone else confirm their FFC is working as well?

:good:
[Verizon Samsung Galaxy S III] YabbyYou:
I jumped to 5/9. FFC is still not working for me under normal light conditions, I'll try a low light pic later and see what happens. Rear camera seems better then 5/2, haven't crashed it yet. BT is working well, still stutters a bit if you have an offending app installed (in my case Weatherbug), but as soon as you Force Stop that app, BT runs great. Haven't received any calls yet so I don't know if there are any dialer issues.
[Verizon Samsung Galaxy S III] Jaws4God:
Thanks [MENTION=7295238]YabbyYou[/MENTION] , I was afraid that may have been the case... :(:eek:
[Verizon Samsung Galaxy S III] YabbyYou:
To be fair, I don't doubt that [MENTION=3056030]AyUaxe[/MENTION] has had better luck with the FFC. For some reason, the specific phone that [MENTION=3056030]AyUaxe[/MENTION] has seems to respond really well the these CM builds with dkp kernels. I can not reach the level of stability that [MENTION=3056030]AyUaxe[/MENTION] reaches with the dkp kernel on my particular S3. I'm jealous!
[Verizon Samsung Galaxy S III] Jaws4God:
yeah me too!! what version does he have?
[Verizon Samsung Galaxy S III] AyUaxe:
Sorry for creating undue optimism. I have the schi535, direct from vzw-the "bronze" model that was exclusive to vzw. In kernel adiutor it reports hardware as Samsung m2, CPU armv7 rev. 4 (7I). Not sure if that helps or if it's just my wicked enabling, ethanol fueled aura that makes her go. BTW dialed back Max cpu to old reliable 1782 BC app updates were failing. Guess there are too many errors introduced at higher speeds.
[Verizon Samsung Galaxy S III] YabbyYou:
And there it is! I checked my versions in kernel adiutor and here's what I have: Samsung m2, CPU ARMv7 Processor rev 0 (v7l) . That's the difference right there. You have a newer revision CPU then me. That's what I get for jumping on the bandwagon so early!
[Verizon Samsung Galaxy S III] XdrummerXboy:
Rev0 here as well, that's what I get for pre-ordering to keep unlimited data :/ haha
[Verizon Samsung Galaxy S III] Roger W:
Heh, I got mine new from Verizon about 11 months after launch - rev 0, v 71. :-|

so you guys didn't "just miss" the newer rev.
[Verizon Samsung Galaxy S III] Fenix2002:
Straight Talk S3, bought a long time after the S3's original run. Rev4 (v71). But mine has never really performed better than any other, and I saw a lot of instability with dkp versus stock or CM kernel, even without doing much tweaking.
[Verizon Samsung Galaxy S III] AyUaxe:
So it's the ethanol. Eagle Rare works wonders-don't even care about ffcs. Drink up (responsibly), friends!
[Verizon Samsung Galaxy S III] YabbyYou:
I'm seeing some call pickup/hangup problems when BT is connected. I can't seem to pickup a call properly when BT is connected, I also can't seem to hang up a call properly when BT is connected. This is on the 5/9 build, but it sounds like this may have been a problem for a few nightlies already.
[Verizon Samsung Galaxy S III] Jaws4God:
so does that difference mean the camera can work for some and not others? :confused:
[Verizon Samsung Galaxy S III] Roger W:
There's been a problem since around January, but not all the way back to the first CM13 builds, where when bluetooth *media* and *phone* profiles are both connected to the same device, the phone doesn't hangup properly and it can reboot the device. The workaround is to disable one or the other for each device, unfortunately.. So for my car, where I want the option to have hands-free phone, I leave media off and use the car's SD card for music and the phone's speakers for nav directions.
[Verizon Samsung Galaxy S III] YabbyYou:
The difference could be everything, or, it could be nothing! I have just been struck by how stable [MENTION=3056030]AyUaxe[/MENTION] gets his S3 running the dkp kernel at some pretty high clock rates.
[Verizon Samsung Galaxy S III] kmoore11:
Can somebody help me get an exchange account set up? Since Sunrise is about to die, I'm trying to get my work Office365 calendar set up in Google or Today Calendar. I've tried installing a bunch of versions of exchange services, but exchange never shows up in the "add account" menu. I feel like it shouldn't be this difficult, so is there something I'm missing?

FYI 5/13 still has FFC issues for us with an old CPU.
[Verizon Samsung Galaxy S III] AyUaxe:
Been on 5/11 for a couple of days and FFC seems slightly better than 5/7. 5/7 FFC worked, but with some stutter and light sensitivity. 5/11 is smooth in full office florescent light. Hopefully tomorrow I'll remember to try it in full daylight.

BT works OK, too. I may be wrong, but it seems most audio stutter in bt is actually streaming/WiFi stutter.

One oddity for the last 3 or 4 builds, reboots take ridiculously long and often it just stays on the boot animation. Only solution I've found is hard power off or battery pull, engage recovery key sequence, reflash ROM etc. Then she boots as normal. Happy Saturday flashers!