yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Update: my s3 broke, so I won't be posting new builds anymore...

Matrixzone's releases are probably of higher quality than mine, but I try to update nightly. Here's his thread if you're interested

[url]http://xdaforums.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854 [/url]

My builds for now are straight from CM source and have been unchanged because I haven't learned how to cherry pick yet. Honestly, it's a miracle that my builds are even working right now

Update: I'm compiling builds again!!! I'll try to do them nightly as always

Downloads:

If you're downloading on mobile, request the desktop version on mega.nz

That way, you don't need to download the megasync app :)

03/04 [url]https://mega.nz/#!YdNx2ZQQ!AnBDi09ldadvGIocvPPHVF2VgpO763xB8c_jZeiMdLw [/url]

03/03 [url]https://mega.nz/#!AJkQlLqL!lPkCRlUEaPB7YDuvpziMUHPKZpb4KUqWOLqaSRFj65I [/url]

**no 03/02 build**

03/01 [url]https://mega.nz/#!hAdT2KIT!sBR_xNymClhjBHHWFSwuBNlGXpHR_ZFYyMPnfcNfNh0[/url]

**no dowloads in between these dates**

01/16 [url]https://mega.nz/#!QcFzBQSQ!gxew9-wyBfulCVr5eejbMFU9Kk4zzpqsBydntCWHrqM [/url]

01/07 [url]https://mega.nz/#!lQVVjTyb!WEV98HcbfLGZ_wmS8LVJCuMpKRsiodXHkpOJyB0vMig [/url]

01/06 [url]https://mega.nz/#!5VchxYDT!hNDmqxP9-RauNPtW4MPufyz07JGkMx7wJQEg9oHFT88[/url]

01/05 [url]https://mega.nz/#!QdVRiK7T!0I-OoxA9r2q9EkDHJ43znAdjkvdPyZ6ge6Flp5mlsmk[/url]

01/04 https://mega.nz/#!kRdxGD4B!2-_kzo9mK3bJwzd-Om0P5h5LhTqV1IJ1IJU7xVnlg9o

01/03 [url]https://mega.nz/#!9dUiXL5J!z0DKXE1CvGvR5Fkwn7XTjECkW5-zCXGU-MZ9UzlDsFk[/url]

01/02 [url]https://mega.nz/#!IQkh2Zgb!NinrEa1o3dOAKpKZ3XNvNrcJpIEsDfS-y-HTghLOK8A[/url]

12/30 https://mega.nz/#!AU1iwTzA!k_3YZTaR...HJ43znAdjkvdPyZ6ge6Flp5mlsmkYWxsX_UMrAJ9bKtKs[/url]

12/29 https://mega.nz/#!9Q9AmY4J!mOWp4d8n7mjKCjKqzmBZWtnsRM7QwxhyaBaVF3qFXDY

12/28 [url]https://mega.nz/#!Ed8AxKhQ!xReR_gjgq5a8BQmAIn6WlJ7GSyioaGxTwnJOL-PiKu8 [/url]

Gapps (choose arm 6.0):

[url]http://opengapps.org/ [/url]

What's not working:

Network Issues fixed!!!

You tell me
​

Special thanks to these people for helping me figure things out:

[MENTION=5927992]jason2678[/MENTION] (for teaching me how to use themuppets)

XDA:DevDB Information

Unofficial cm13 by Arunscape, ROM for the AT&T Samsung Galaxy S III

Contributors

Arunscape

ROM OS Version: 6.0.x Marshmallow

Based On: Cyanogenmod

Version Information

Status: Testing

Created 2015-12-28

Last Updated 2016-01-02

XDA:DevDB Information

Unofficial cm13 by Arunscape, ROM for the AT&T Samsung Galaxy S III

Contributors

Arunscape

ROM OS Version: 6.0.x Marshmallow

Based On: Cyanogenmod

Version Information

Status: Testing

Current Beta Version: 6.0.1

Beta Release Date: 2016-01-05

Created 2015-12-28

Last Updated 2016-03-03
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
reserved
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
I'll try to help you figure out the sim issue. I'll be in touch soon ? gotta get to bed, work comes early.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I got the network issue fixed by setting up themuppets with an edit to roomservice.xml (before, I just used the extract-files.sh and connected my phone lol)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I just got a build error:

make: *** [/home/arunscape/cm13/out/target/product/d2att/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1

make: Leaving directory '/home/arunscape/cm13'

#### make failed to build some targets (01:39:11 (hh:mm:ss)) ####

It looks like something's wrong with the recovery?

update: my source code got all messed up after a power loss while compiling the rom, so I just deleted the source and redownloaded the entire source again..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
I am really excited to see another dev (even if you are a n00b) building cm13 for the s3. Thanks a bunch. I can't wait to try it ... Probably will flash tonight waiting for the ball to drop. Do you see flaky cellular data in your builds?

-J
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Hey man, I've been super duper slammed with work but I just wanted to drop in & say kudos! Glad you got the builds rolling & the sim issue fixed. I'll be following your progress. Oh, and Happy new year! ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Thanks for your support! Also I resolved the issue with the build errors that I was getting! Turns out that the entire source code gets messed up if you lose power in the middle of compiling a build...

I will post a build for January 2 soon! (though I haven't tested it yet.. I'll report back when I have flashed it.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I can't test data, because I don't have a data plan with my carrier, but SMS and calls work no problem :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
already uploading 01/04 build as I type right now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Sorry I haven't uploaded a new build yet. Exams are happening right now so my uploads will slow down a lot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] privatedoodle:
So for folks who are using this, how's it working? Anybody finding bugs/issues? Thinking about making the jump from CM12 but need something stable..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
so It's been a while since my last upload but I got one coming!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
If you want something more reliable, try matrixzone's ROM but I haven't seen any differences between our builds. Also, it's been a long time since he has updated his ROM http://xdaforums.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854

I am currently running the builds that I am building on my daily driver and they seem to be working fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] privatedoodle:
I'm coming back to the S3 after a year with a OnePlus, so there's a good chance I've missed something important.

The CM12 nightlies work just fine, but I can't get either this version of CM13 or the matrixzone version to boot. I wipe everything, install ROM, OpenGapps, and SuperSU, wipe cache/dalvik, and reboot. It hangs on the boot screen for over an hour before I give up and shut it down.

Am I missing something? A new bootloader maybe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] privatedoodle:
Nevermind, it seems SuperSU was the problem. Booting fine without SuperSU.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
SuperSU version. 2.66 works fine for me, but not the google play store version. You can get it here http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Anyone using their S3 with Marshmallow as a DAP/Transport. Does the USB Audio work? I moved my LG Pad 7.0 to Marshmallow and the USB Audio doesn't work. So I am looking for another alternative. Any information would be great on the USB Audio status
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kami Look:
baseband - IMEI - SN is missing with this rom...

SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XDAKeegan:
Does the camera work with this build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXshur1kenXx:
I would love to see this start getting builds again, even if only on a weekly basis. This rom has breathed new life into my S3. Thanks Dev, hope you build again soon :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbwarfield:
What are the known issues with the latest build?

XDAKeegan asked about the camera.

Kami Look says there's a problem with IMEI.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Alright, I'll start making builds again but I won't guarantee them being updated nightly..

As for bugs, I personally haven't encountered any but there's always the possibility... lol.

I'll download the source tomorrow, and maybe post a build on on the same day or on Tuesday!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Camera works fine, but Snapchat randomly crashes sometimes

And I have no clue about IMEI]

Update: the IMEI shows up correctly on my phone, so idk what's wrong. Wait until the first of February, I should have a new build up by then
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f4gww:
Here's what my SGH-I747 is doing with this build:

IMEI Information > IMEI = Unknown

IMEI Information > IMEI SV = 0

SIM status > Cellular network state = Disconnected (even though I have5 bars)

My phone also reboots every time someone tries to call me. I'm going to have to go back to Lollipop today. I can't have this unstable of a phone right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXshur1kenXx:
Thank you!!! This rom is my daily driver currently. I'll be more than happy to test any builds for you. I'll probably pair this with decimalmans kernel if it's compatible
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I downloaded source today. I'll build tomorrow and if there are no build errors I'll post it ASAP.

Also , thanks for offering to test builds for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Does front camera work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yes but I suggest waiting ~2-3 hours as I am compiling a new build right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Alright I have a new build uploaded for today!!! Feel free to test the build out. Fingers crossed that it's good lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
Installed the new 3/1 build tonight and have done some minimal testing so far....Other than the known light sensor and front camera issues (both bugs I've verified to still be present), the ROM overall is working very well...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
So no ability to take video with front camera?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
Unfortunately, front facing video does not work...As soon as I put any camera app in front facing video mode, the phone completely locks up (and I have to force a hardware reboot). Tried Google Camera and Open Camera and same thing happens as soon as I transition to video mode with the front facing camera in either app.

Front facing picture mode locks up the phone whenever I try to actually take a picture...transitioning into FF picture mode is no problem; phone only locks up when you attempt to actually take a picture in google camera. Oddly enough, Open camera is able to take front facing still pictures no problem..But again, front facing video in Open Camera is a no-go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
On matrizzone's 02/11 build the the front camera works flawlessly. :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsauser11:
Need some guidance.

Hi,

I recently installed the 01/16 build into my I747 which was previously on android 4.3. I really like this build, and most things seem to be working, but I have not been able to successfully complete a backup of my new system. I am using CWM with TWRP, and backups fail every time. From poking around in this forum, I am wondering if my backup failure is related to my bootloader and broadband versions (boot=I747UCUEMJ2, boradband=I747UCUEMJB) being too old? If that is true, what is my path forward to resolve the backup issue? Do I have to start from scratch, install a new (NE4) bootloader and broadband, and then flash CM13 and GAPPS? Can I do that without bricking the phone? Any guidance you could provide would be very welcome.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
How are you using "CWM with TWRP"? As far as I know you can only use one or the other, and if you made a backup with CWM and are trying to restore with TWRP, that won't work. You also can't restore a backup made with TWRP using CWM. Only TWRP backups can be restored by TWRP and only CWM backups can be restored by CWM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsauser11:
Sorry. Using Rom Manager V5 with TWRP. Tried with ROM Manager V5 and CWM, but no joy, so switched to Rom ManagerV5 with TWRP. Still no joy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Oh. Are you using TWRP 3.0? That version fixed a lot of stuff for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsauser11:
No. I just got a backup to complete a few minutes ago by booting into recovery bypassing Rom Manager. When I boot into recovery the recovery is CWM V 6. I don't know what is going on with Rom Manager. Maybe I should just scrap Rom Manager and figure out a way to install TWRP 3, but I don't know how to do that over the CWM 6 that is already there. Anyway, now that I have a backup, I feel much better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
stop using rom manager

once you have installed twrp .. use it directly for all recovery functions: backup, restore, flash, wipe, etc

custom roms like cm usually allow you to boot into recovery via power menu .. or you can use the volumeDown+homeButton+powerButton combo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsauser11:
So I should be able to uninstall Rom Manager, and then install TWRP, which will replace the CWM V6 which appears when booting into recovery with power menu or volumedown+home+power?

I was fearful that doing that might give me a brick. Of course, any CWM based backups will not be useable in TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yeah just use Odin to install twrp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
correct .. apps that flash recoveries flash the recovery.img

once you have twrp installed, you can use it to flash it's own updates (newer .img)

correct .. once twrp is installed, you can delete the cwm backup and make a twrp backup

like she said, use Odin to flash the recovery .tar file

the .tar version contains the .img and info for Odin so that it knows how/where to flash the recovery

links to twrp are in My sig .. make sure you get the proper img/tar for your device and flash method
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsauser11:
I installed from the Play Store, and seemed to go OK. Now, when I boot into recovery, it is TWRP, and TWRP Manager says the installed recovery is TWRP 3.0.0-0 when I set SELinux to permissive.

After install, I was able to successfully create a TWRP backup to my sd card.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Umm.. I'm a guy lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
why permissive??

umm .. oops .. apologies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
It's fine haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ocd_amp:
Hey cLogic, good to see you here!

[MENTION=5937595]Arunscape[/MENTION] : Good work man! Impressive you are now the "official unofficial supporter" Ha!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
What's new in this build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Nothing that I know of lol. I just push out builds as often as I can. All I do is update the source code so sometimes small fixes happen. (But that's because of cyanogenmod not because of me) For example, exFAT used to not work but now in the latest builds I think it does
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
sorry guys, I've been getting build errors lately and I need to figure out why, that's why I haven't been posting builds lately
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXshur1kenXx:
It's all good man! Doing dev work is not your day job and we all understand that. Take your time :) We'll all be here awaiting your next build regardless if its a day or a week later. I'm about to update to the 3/4/16 Build within the next 30 mins so I'll report back at the end of the week. Keep up the great work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I don't know how to fix this build error!

I tried deleting the source folder and repo syncing, and I also tried cleaning ccache and running make clean
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Looks like I won't be needing to post builds anymore!! according to matrixzone, official cm13 nightlies should be on the cyanogenmod website soon!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
(Forgive me for being late, I just saw this)I have the 3/18 build downloaded and ready to flash, just looking up any problems I may have. Thank you and [MENTION=4551784]matrixzone[/MENTION] for all your hard work! I've been dying to get on MM for a while, but it was way too messy. As soon as I have a little more spending money, you guys have a few beers(or whatever vice you choose :P) coming your way!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Tbh matrix did the hard work of fixing issues and it's because of him the nightlies are here, I was just posting vanilla builds ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Hey, give yourself more credit man, iirc, you helped him with one of his more recent releases as well. Had it not been for both of you putting so much momentum into this, we wouldn't be seeing these nightlies so early. Anytime I found anything for cm13, there was always someone wondering how to fix something with either your build, matrixzone's, or Oct-M, it wasn't just the Nexus owners.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yeah, I guess I did help with providing logs and saying which sensors weren't working...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ogichidaa:
Big thanks

Swamped with work but am super excited to start building. Also really happy to see other devs out there, I'm a complete n00b but I'll learn quick enough. Furthest I got is breakfast and I don't know how to switch to the unofficial streams very well, going to switch computers and try again, any pointers greatly appreciated. Big thanks to the devs who are working on the s iii. Happy building!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
When I get home, I'll make a mini guide for what worked for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Update: I'll do it on the weekend lol. Good luck building! ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harkavagrant:
keep having gps issues

any good new nightlies that are stable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
My s3 broke so I can't make new builds anymore
[Galaxy S6 Q&A, Help & Troubleshooting] Mekrel:
Most of you will be aware that a new "app optimization" feature was added to a recent 5.1.1 based firmware update.

I've been trying to research exactly what this does because Samsung have not updated their user manual (you can access this via the user manual widget) to cover this new feature. After searching online, I've come to the conclusion that I'm not the only one who isn't sure what this feature does and there's a lot of incorrect information out there.

Below is some examples of what I've read:

It's Samsung's implementation of doze - I think this is incorrect as doze is a system wide state that uses sensors and screen off information.

Someone on AC forums was told by a Samsung employee that for example, it will make taxing games black and white so they don't require so much processing power - I really don't think this is the case.

It's Samsung's implementation of app standby - I think this is the most likely.

Does anyone have any concrete evidence as to what this setting actually does?

Furthermore, I've noticed that the "app optimization" implementation will change depending on if you have Smart Manager enabled or disabled. Not only that, but the battery sub menu layout (settings > battery) is also different depending on Smart Manager running or not. Has anyone else noticed this?

From what I can gather, the "app optimization" feature is there regardless if Smart Manager is enabled or disabled, but you can only manually select wether an app is optimised or not. Smart Manager appears to only provide automation of the process by monitoring which apps have not been used for x number of days and then changing the optimisation setting for each app for you.
[Galaxy S6 Q&A, Help & Troubleshooting] Tricks25:
Based on your screenshots, system apps can now be optimized by default?
[Galaxy S6 Q&A, Help & Troubleshooting] bregan90:
Second screen is the 'Optimization Screen' under Setttings > Battery > Battery Usage > Battery Optimization. First one is from the 5.1.1 update, and the second is only present in Marshmallow Beta.

I don't think it's exactly an App Standby, as this keeps the apps 'unoptimized' if they have background services. Samsung's optimization only takes days since last usage for determining if an app should be optimized. Also, I think Samsung's optimization is more aggressive, like Greenify, an it shuts down apps shortly after user lefts them.

Oh, and it seems that you can't explicitly turn App Standby for an app, like you can do it with the Samsung alternative. Putting an app on/off on App Standby only activates App Standby for that app (If conditions are met) or disables it completely.
[Galaxy S6 Q&A, Help & Troubleshooting] Mekrel:
You're not quite correct on the screen shot front. All screenshots were taken from Android 6.0, the reason they're different is one was taken with Smart Manager running and the other was taken with Smart Manager disabled via Package Disabler.
[Galaxy S6 Q&A, Help & Troubleshooting] bubbleguuum:
What it does is that after an app has not been started for 3 days (this is configrable), it freezes (disables) it.

This is really problematic for small apps acting as unlocker of a main app and not supposed to be launched by user, as it prevents the main app to communicate with the unlocker app (bindServices() fails), preventing license verification to work.

This cancer acting in the back of apps used to only be possible on root devices, but Samsung generalized to mainstream devices.
[Other SmartWatches] damessiah13:
I have recently received a smartwatch m28 and have gotten everything to sync nicely with my htc one m9 using "fundo smartdevice" app, but need to know how to add watch faces and apps to further customize my new smartwatch. I've tried numerous play store watch face apps, but no success...please help...

thanks!

watch: http: // www .newegg. ca/Product/Product.aspx?Item=9SIA8WX3BW2784
[Fire Q&A, Help & Troubleshooting] KennBr:
Has anyone managed to get it working? I just tried to install via FlashFire and wound up getting an animation loop on the SlimLP boot logo. I applied the 5.1.1 firmware through the "apply update through adb" option in the recovery, can anyone confirm Xposed even working on SlimLP?
[Fire Q&A, Help & Troubleshooting] Hedied4me:
I'd like to know this also. Have not tried it yet.
[Fire Q&A, Help & Troubleshooting] Bib_x:
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
[Fire Q&A, Help & Troubleshooting] KennBr:
Thanks! Think I found an easier solution than installing Xposed for what zip needed though (just needed YouTube to play in the background). That will come in handy if I want it later for any reason though.
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
Yes, xposed works fine. Big thanks to csolanol!

You must use the xposed compatible SlimLP 0.13 build + the correct xposed version (see the howto xposed thread in Fire General forum).
[Fire Q&A, Help & Troubleshooting] kGe2007:
Anybody had success with getting .013 build running successfully with eXposed.. I've tried the ' Slim-ford-5.1.1.beta.0.13-UNOFFICIAL-20151221-0949.zip ' build from root junkies tutorial i think in section 4 or something if i remember vaguely, but with no luck... The Flash just proceeds as expected then reboots while opening/loading .zip.. But the standard release 'non-eXposed' runs without any problems.