yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] XdrummerXboy:
Following the instructions in that thread allowed me to boot the 9/15 nightly.

A little shaky at first which worried me, but seems perfectly fine now.

Thank you very much!

Edit: every so often I get a "system not responding" and "apex launcher not responding" message, but if I choose "wait" its fine. This happens every time after a reboot, and maybe every so often during normal use

Edit 2: I need to revert, 9-15 isn't stable at all for me. Could this be because I used Rovio89's official V74 Xposed instead of RomRacers unofficial V74? Or is this likely just the ROM being unstable?
[Verizon Samsung Galaxy S III] Master Cylinder:
I was testing something else on my phone so I didn't get any time with 9/15 today. But, it looks like you're guinea pigging Rovio89's to see if it works on our phone! Are your problems related to 9/15 or Rovio89's framework? I think there is an uninstaller for X;posed but you could just flash the ROM again along with RomRacer's framework and continue as the guinea pig. ;) My suspicion is that that'll fix you up.

EDIT: It's also possible that just flashing the unofficial framework might do the trick.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Does the Xposed Uninstaller cause the apps to re-optimize? If not, I'm willing to uninstall it and try it out for a bit. If not, I don't wanna go through the hassle more than I have to, and will likely just go back to what's most stable.

Edit: ehh I'll just give it a go
[Verizon Samsung Galaxy S III] Master Cylinder:
I don't know. Want to test it for us?

If you flash an earlier ROM you'll have to optimize again anyway, might as well do it with RomRacer's framework. It will work - me and others have been proving it. Then you'll be set going forward.

EDIT: Yeah man - go for it! I flashed Open GApps today to see how they work. Gotta take advantage of the opportunity we have with these unlocked phones, as long as they're still working and we're lucky enough to have [MENTION=2044079]Nardholio[/MENTION] pumping out nightlies for us.
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey! Why not just follow those same steps from that link again, but this time put RomRacer's on?
[Verizon Samsung Galaxy S III] XdrummerXboy:
That's essentially what I'm doing right now.

1) Used the uninstaller (pointless though, because #2)

2) reflashed 9-15 nightly

3) flashed RomRacer's Xposed v74

Hopefully that will confirm if it was Xposed or the nightly causing the issues

Worst case scenerio, I just flash back to what was stable for me with one of RomRacer's previous builds (v60 something I think).
[Verizon Samsung Galaxy S III] :
Send me the contents of /system/cameradata from your stock ROM
[Verizon Samsung Galaxy S III] msolaw:
My camera flash and my flashlight don't work at all. Could my light just have totally burnt out or something? Or is this a known issue with recent nightlys? I'm running 9/9 with the dkp kernel and just typical gapps.
[Verizon Samsung Galaxy S III] matt_man:
I managed to get it fixed yesterday by running dmesg from the terminal after trying to open the camera. I was able to find the file from /system/cameradata that the camera was looking for and added it to /data and edited permissions. The camera and flashlight now work properly.

Thanks for replying.
[Verizon Samsung Galaxy S III] Master Cylinder:
Awesome! Would you mind posting the file you changed and where you put it in /data? Is it a cam_socket# file in the root of /data? Others are having a problem and this could help them, too.

Thanks! :highfive:
[Verizon Samsung Galaxy S III] matt_man:
SlimISP_ZM.bin in the root of /data. I changed the permissions to 777 but more restrictive permissions would probably work. Running dmesg from the terminal should tell users the exact file they need to use. Also I used the SlimISP file that came with the ROM in the camera data folder not the stock one.
[Verizon Samsung Galaxy S III] :
Can you do me a favor? Can you delete the file from /data and send me a full set of logs? logcat, dmesg, and /data/misc/audit? I checked the kernel and it should be loading from /system/cameradata first, and /data second, something's going on here
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah, I don't have that file there.
[Verizon Samsung Galaxy S III] matt_man:
I can do that but I probably won't be able to get to it till tomorrow.

Thanks for looking into the problem.
[Verizon Samsung Galaxy S III] Master Cylinder:
Open GApps looks pretty sweet! I'm looking for a replacement for the CM12 OP because CGApps looks like it may have been dropped by the dev (used to put one out every month or 2. Still could get another one this month maybe.) But, Open GApps are modular AND have the option of Aroma Installer. Updated daily. Just flashed them yesterday to give 'em a try on this and another ROM. Everything works. Very interesting story with these GApps. They have a website and an XDA thread. They're in the OP now.

HOWEVER - WARNING!! The first time one installs Open GApps, you have to do it with a ROM update (or reinstall of current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally. After that, you can flash them anytime.
[Verizon Samsung Galaxy S III] phonetool:
9/17 wouldn't boot for me. :-/

I pulled the battery and re-flashed 9/15.
[Verizon Samsung Galaxy S III] :
Don't install the webview from opengapps. It's a beta version and for whatever reason Google doesn't have the workaround for the older version of Adreno we use in their beta version. Fortunately for us, enough people complained and they added it to the Play Store version, which was nice of them because as they said, no device with this Adreno has official Lollipop.

---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------

You must have been fast, I had 9/17 deleted from the server at like 2 AM eastern time. 9/18 will be ok.
[Verizon Samsung Galaxy S III] Master Cylinder:
Oh man!! I just was giving the Aroma installer a try and installed Webview. It's very unusual that I don't check my email early... but today .... I'll see how it boots and what happens. I'll find a way to get the other one on if I have to, plus have TiBu of everything always anyway.

I also had 9/17 on my computer screen last night and was looking forward to flashing it this morning. knew something was awry when my phone wouldn't get it and saw it was gone.:eek:

Here is a reply to a PM from Nardholio in response to how many are using CM on our phone. Others might like to see:

"CM does keep those stats, but I don't directly have access to them. I can safely say the Galaxy S III is the single most popular phone of all time and continues to be, so much so that Samsung is still making new ones for warranty replacements and for MVNOs. http://opensignal.com/reports/2015/08/android-fragmentation/"

PS - Those graphs from Open Signal don't take into account any US S3s but only one of the international versions. All together there are 15 versions! I would expect some non-US markets to hold to an older phone much longer. I expect that it might be harder to upgrade for many reasons in places like Africa, Estonia, Iran, Kazakhstan or Turkey. Central and South American countries?

Here it's the opposite! The pressure to upgrade is immense!

EDIT: Wikipedia reports 80 million sold world wide (July 2015) in 145 countries (that was in July 2012. They have come out with more S3 variants since then,) including 30 million sold in the last 2 years!! Lots of interesting info on there. https://en.wikipedia.org/wiki/Samsung_Galaxy_S_III
[Verizon Samsung Galaxy S III] phonetool:
I guess I was fast, but the is a delay between when the download is available from CM and when it's available via Cyandelta (which I am using).

Thanks for all your help and support!
[Verizon Samsung Galaxy S III] Master Cylinder:
Also builds seem to stay longer on cmxlog.com
[Verizon Samsung Galaxy S III] matt_man:
[MENTION=2044079]Nardholio[/MENTION] pm'd you the logs you wanted.
[Verizon Samsung Galaxy S III] phonetool:
Just flashed 9/18 and no problems so far.
[Verizon Samsung Galaxy S III] XdrummerXboy:
CM Resolver force closes when trying to open/download a PDF (and possibly other files) from Chrome.

Not sure if ROM or Chrome issue.

It is from a school site and requires authentication to download, if that changes things. I have to go to the stock browser and login to download it.
[Verizon Samsung Galaxy S III] Roger W:
For a month or two, any time I download a new build from the CM updater in Settings, and tell it to reboot to apply, it sits at the Rebooting screen forever after shutting down the various radios (based on the status bar). Normal reboots works, but in this case I have to hold the power button until it turns off. Then when I boot to Recovery, it starts the update automatically. Anyone else see this? It used to work fine.
[Verizon Samsung Galaxy S III] stevet86:
I had the same force close on September 15 with Nova launcher. Cleaned flashed September 18 and all was good. I haven't updated anything since.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Has anyone else been getting a LOT of "_____ launcher not responding" and "System not responding" messages when you wake your device?

This has been happening since the 30MB (or whatever) change, regardless of Xposed version. I haven't tried without Xposed though.

Stock kernel.
[Verizon Samsung Galaxy S III] Master Cylinder:
Not seen this. What recovery are you using? I have TWRP 2.7.8.0. I haven't tried the CM Recovery ...

I just tried it on my phone - works normally. (I hadn't been using it but TWRP Manager's Install function since I install more than one file at a time and it handles them all at once.)

None. Using Xposed Unofficial v74.

What is CM Resolver anyway? I just dloaded a PDF with Chrome, no problem. Of course I can't test that login thing - don't have something to do that with. It does seem like you're having launcher problems. Might clear data for it. When and where did you get that version of Chrome?

On 9/19. Been updating nightly at the moment. If anyone has 9/17 on, get something else on there - it was pulled.
[Verizon Samsung Galaxy S III] AyUaxe:
9/19 is butter. Delicious creamy butter.
[Verizon Samsung Galaxy S III] Coldblackice:
If we're stuck on 4.4.2 because of the whole Knox and locked bootloader business, is there anything we can do? Is it possible to update? Or at least update to protect against Stagefright?
[Verizon Samsung Galaxy S III] bryank29:
I am on 9/18 right now...for whatever reason, I am NOT affected by the Mobile Radio Active bug. I actually flashed the DKP kernel and when I rebooted, it was back. So I restored my 9/18 nandroid I did and I am back to no mobile radio active bug and good battery life. I haven't tried restarting yet which I heard "can' bring it right back...so maybe right combo of things going on, idk.
[Verizon Samsung Galaxy S III] :
Let me know what you think in terms of boot time, both first boot and subsequent. Also battery life. And any problems with delays in screen turning on when receiving a phone call. I recently did a major overhaul on the way CPU time is allocated. And actually I messed it up from the way I intended to set it up. From my own testing this might become permanent though lol
[Verizon Samsung Galaxy S III] bryank29:
like I mentioned above, I am running 9/18 with default kernel, default amplify settings, and greenify running. I am using 384mhz min, and 1296Mhz max.. Interactive governor.

best build I have used. The mobile radio active seems much more quiet. When I flashed the DKP kernel, my battery was getting eaten up and the mobile radio active was very active. So I don't know why any of this is going on.

might give 9/19 a try now.
[Verizon Samsung Galaxy S III] Master Cylinder:
I timed the boot of 9/21. From the time Mr. Boring shows up till he tumbles away was 1:58. (subsequent boot) Not abnormal?
[Verizon Samsung Galaxy S III] Jeremy.Stewart85:
I seem to be the victim of a common problem with in-call volume being stuck/too loud. The alarm volume also seems affected in the same way. I've made changes based on mastamoon's thread and another one I found using the same file but wasn't very successful: http://forum.cyanogenmod.org/topic/60699-in-call-volume-too-loud/ . The initial volume IS changed, but it still suffers from being stuck until you max the slider and move it back down again. At least my eardrums aren't getting punished right off the bat anymore.

Not sure when this started to become an issue for me for any build in particular, I barely make any calls so it's hard to remember. I am using dkp so I might try going back to stock next time I flash to see if that changes anything. The suggestion to turn off in-call volume boost doesn't seem to be an option for me on the default dialer, where can you even get to that option? I haven't seen other suggestions to get this working properly, has anyone had success in solving it?
[Verizon Samsung Galaxy S III] Roger W:
TWRP 2.8.7.0, which is the latest. Your version has the middle digits transposed - better version, or typo?

Anyway, it's probably some random one-off on my phone. Android OS is still active while it's stuck; I can use the power button to get to (but not use) the reboot menu, or the lock screen. So, it doesn't feel low-level. thanks.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Now on 9/22

CM Resolver got fixed somewhere in the last few days, which means no force closes when picking an app to open something with.

No lags or "system not responding" either that I've noticed.

But damn... The "Optimizing Apps" takes 70% of my battery, haha. I miss dalvik only for that reason.
[Verizon Samsung Galaxy S III] Jaws4God:
is anyone having issues with the volume toggle disappearing from quick settings shade?

ive noticed it on the last 2 or 3 nighties.. im on 9/21 right now.

thank you.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Master Cylinder:
Have you tried clearing the data?

Yeah, but I've figured out how to make that no impact. I use TWRP Manager which will automatically boot into recovery, flash the files I want in the order I want, and reboot. I set it before I go to bed and wake the next day with a new ROM! :p
[Verizon Samsung Galaxy S III] XdrummerXboy:
Yeah, that's what I used to do, but my phone doesn't charge any more. I rely on battery swaps, haha
[Verizon Samsung Galaxy S III] Master Cylinder:
Ouch! Well, I got no power button. We must really like these things to keep 'em going like this. :laugh:
[Verizon Samsung Galaxy S III] Master Cylinder:
Check this out: http://xdaforums.com/showthread.php?t=2639337
[Verizon Samsung Galaxy S III] phonetool:
Loving the straight - to - unlock option in 9/22!

Also tried in call volume and it seems to be working, too.

Sweet awesomesauce!
[Verizon Samsung Galaxy S III] XdrummerXboy:
What's the straight to unlock option?
[Verizon Samsung Galaxy S III] phonetool:
Avoids the "status screen" that you must swipe up and away before reaching the unlock pattern screen.
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh::laugh: I love these! It's making me hungry. :p
[Verizon Samsung Galaxy S III] Roger W:
The past 2-3 days/builds, I have a common app hang in email (com.android.email) and Chrome - navigating between email messages has about a 1 in 3 chance of hanging the app. Less often for web, but it happens. Anyone else seeing this?

I recently took the 9-15 update to Android System WebView, I don't know if email uses that.
[Verizon Samsung Galaxy S III] mav3rick478:
Stock messaging app keeps giving me a notification of can't send message when I open it, I tap it and it's a blank message. On build 9/22 but was happening on the 9/05 build since last week.
[Verizon Samsung Galaxy S III] AyUaxe:
Sorry for the long delay getting back--was out of the country. Still on 9/19. I don't use xposed, cyandelta, or CM updater. Just download the build from OP link, tee it up with DKP and 800vmin, flash with a reasonably current version of TWRP. Wiped cache/dalvik at the end on this one.

Start up was pretty fast comparatively, though the 127 apps optimization took the usual long time. Sorry, didn't time it. I did have one random reboot after streaming music about 2 hrs and the boot up was about 1.5 minutes.

Battery life seems somewhat better than prior builds--hard for me to quantify.

The answer screen for calls definitely comes on quicker--thought it was a change in CPU min [108], but checked and it had gone back to 54 mhz after the re-boot, so that's f'sure thanks to [MENTION=2044079]Nardholio[/MENTION].

Still have the manageable, but weird ineffective rocker switch for in-call volume (hit speaker, adjust, hit speaker again, seems to work). And speaker phone doesn't seem to work at all. The re-boot after streaming on wifi may be app (TuneIn Radio) related, but I still have to wonder if it's a cache management issue. BTW, everything worked well in UK via Verizon's deal with O2. Only problem was D2's known weak GPS, though all GPS ****es in London. Had intended to try a GifGaf sim with the gsm rilblobs linked in the OP, but wasn't there long enough to be bothered to do it.

All in all, [MENTION=2044079]Nardholio[/MENTION] is tops in the Beurre noisette ROM cooking category! Bon Appetit! And thanks!
[Verizon Samsung Galaxy S III] phonetool:
I've been through this once before, so I'll tell you what I found out. The stock app doesn't show a queue, nor is the queue cleared by an app cache wipe. The solution is to temporarily install a message app that does show the queue. Handsent (or whatever it's called) can do it. View the queue and delete whatever is stuck there. Then you can uninstall the app and go back to stock.

Hope that helps!
[Verizon Samsung Galaxy S III] AyUaxe:
It always surprises me that anyone still uses the stock msging app. I recommend Textra. Light, quick, nice layout, etc.
[Verizon Samsung Galaxy S III] mav3rick478:
I usually use Slide Messaging but every time I use it on an AOSP rom I never receive MMS. I'll take a look at Textra.
[Verizon Samsung Galaxy S III] AyUaxe:
1 caveat, I've never gotten MMS over WiFi with textra or any other app, for that matter. I've seen comments that some people do get them on WiFi. Maybe it's cause I'm on Verizon. Don't know. But if that's important to you, check early, so you'll know before critical fantasy football group messages pile up and break wireless.
[Verizon Samsung Galaxy S III] mav3rick478:
The problem was, I would get a notification, go to check it then it would disappear from my message list?! I could send them without any issues but being able to see them was the problem. On a TW Rom slide messaging worked fine because there is an option to have the stock messaging app handle mms.
[Verizon Samsung Galaxy S III] Roger W:
I've cleared data on the CM Updater app but that app still hangs at "rebooting" after putting the phone into airplane mode. No big deal, I can just manually Reboot Recovery and pick the file myself. I have a boot encryption password set so I can't automate my updates anyway.

Update - I downloaded a week-old Webview from an archive site and it works great. So the current one is broken for me. I'm back on 46.0.2490.23 now.
[Verizon Samsung Galaxy S III] :
Webview is going to be hit or miss for d2 as it demands more and more GPU capabilities. Google is aware of the problems with the older adreno in this chipset but doesn't test new features on it and only fixes them after the fact.
[Verizon Samsung Galaxy S III] msolaw:
I am on the latest nightly and open gapps. I get a constant Google play services app, so I can't use gmail. My flashlight and camera flash still don't work. Could it have just broken maybe? It's an old phone so who knows right? Any help is appreciated! Long live the s3!
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm sorry to hear this because putting the Open GApps in the OP has been a bit of a risk. Bleeding edge perhaps, (which is why I took banks off. They might be dead now anyway.)if that has something to do with your Google apps problem, which it might.

You could flash those CGApps that are in the OP. They're a couple of months old, but stuff will update and they work flawlessly just as a test, or something else you trust. If you have a backup, You could try just flashing those over your ROM. Hopefully Open GApps being installed won't screw it up. Or, second choice, you could wipe /system and dirty flash the latest nightly plus CGApps, or other GApps of your choosing, besides Open to see if it fixes it.

As far as your flash, did you clear your camera app's data? This hung my light up for awhile. Also, you could always put a TW ROM on there to see if the hardware is still working... or KitKat that you know works.
[Verizon Samsung Galaxy S III] Droidriven:
The S3 has been my favorite device to date, the locked bootloader can be a pain on the models that have the locked BL but other than that its generally a breeze
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Yes yes, but I have moved on to the LG G4. Though I like this device, it's not great on battery and though the screen is sick, the auto brightness is sad. If I knew all this about the G4 before I pre-ordered it, I would just be rocking my GS3 still on the 5.1 Nightlies. It finally got rooted, the G4 Vzw variant, but no unlocked booty or roms. There is actually a bounty out for the dev that unlocks it and makes a rom, something like that. Pretty damn crazy and cool. That's why #DroidDoes & #crAppleDoesnt!
[Verizon Samsung Galaxy S III] Droidriven:
Nope, thats why I'll never be an iDrone, android is just way too much fun. The android operating system is growing in spectrum, its being used on more and more devices every day whether mobile or cellular or not. It'll be in everything before we know it and just like in the 80's when Apple got crushed by Microsoft and IBM Apple and the iOS will get left behind, they try to stay ahead but android is just way too moldable across so many platforms its ridiculous.

Anyway, not trying to junk up the thread, sorry OP and Mods.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
AMEN! Took the words right outta my mouth!
[Verizon Samsung Galaxy S III] Master Cylinder:
I wondered what happened to you!:silly:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Lmao. Yeah, I moved on and it was a bad move at that. I still follow what's going on with the S3, I guess it's part of my therapy because of my G4 "buyers remorse." ? ? ?
[Verizon Samsung Galaxy S III] Droidriven:
I know, OT

But that's why I always research what I get before I get it to find what is available to it, then go straight from the box to flash.

I'll have all my files prepared before I ever get the device, lol.
[Verizon Samsung Galaxy S III] AyUaxe:
So, I guess the reason there are only a couple of ot comments in the last week is that the last few nightlies are perfect or so bad, everyone's off line? I'm still on 9/19 and it's still excellent, but some wierdness with switching bluetooth audio and switching off lte when in WiFi range, so would like to freshen things up. Thanks for any info. Happy Tues!
[Verizon Samsung Galaxy S III] XdrummerXboy:
Pretty dang stable for me (9/25).

Main issue now is switching from WiFi to data is sketchy. Sometimes I just need to turn off WiFi to get it to make the switch, sometimes it requires toggling airplane mode, and in the worst case it requires a reboot.

I can live with it though.

The support for this device continues to blow my mind. Many thanks to all involved.

Edit: also, I noticed the SD card issue was fixed! The one where you had to reboot the phone to get it to recognize the card if you didn't eject it "properly".
[Verizon Samsung Galaxy S III] vforaci:
I'm on the 9/28 nightly and I haven't had any issues yet. I'm still tweaking a few settings. Is this build going to have M builds or is it just nighties for this device?

BTW: I did a dirty flash coming from cm11.1
[Verizon Samsung Galaxy S III] phonetool:
Long-press back does not kill apps for me, even though it is activated in the developer settings. Hasn't worked for a long time.

Otherwise working well.