yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
The OpenGApps stock package is what I used. You were able to boot after flashing the ROM followed by OpenGApps stock, right?

A broken camera is the only issue I'm left with, but I'll live with that until [MENTION=4551784]matrixzone[/MENTION] drops another build. I have my backup handy if I find myself headed for a situation where I must have the camera. Marshmallow idles so well that the percentage starts climbing, really just the battery settling in after some heavy use, but it's funny to see it climb without being on the charger.

Of course the other thing that is working but has room for improvement is the choice of VFAT format on the external SD. Before this, the CD was formatted exFAT, but so far this ROM could not handle it. It seems from reading that VFAT is not the best, but it will do for now. I wonder if I had formatted the external SD to F2FS manually, if this ROM would have recognized it. I may give that a whirl later, and that I know will work on CM12 also. Cannot be sure about VFAT.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yeah, for sure, but just like the camera, SuperSU was working in previous builds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GoughGhan:
Open gapps wouldn't even flash after flashing the ROM, just an error then it aborted. I'll try again in the next build matrix puts out but I'll try all of the ARM versions of 6.0 and see what happens and write down the error if I get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I'm going to try the beta, but first I had two question:

1. The Cyanogen C-Apps work with this beta?

2. Root Explorer if know work with this beta?

Thanks..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I'm in no position to confirm that but I don't see why those wouldn't work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Cyanogen C-Apps is for 12.1, so they will not work for CM 13.0

Try ES File manager, but still that is not stable enough. We have to wait for sometime, before any developer upgrade Root Explorer for 6.0, until then use ES
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsager33:
Does anyone have issues running Facebook? Both FB and Messenger will not run for me. Not sure if this is a FB issue with Marshmallow or a problem with CM13.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Stock Camera will be back in next build whenever it comes..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Thanks!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Google camera also seems to work on the new build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoitz:
This is awesome matrix! As soon as I get internet at home, my s3 (now my work phone) will join in the testing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Great news about the camera! I've been running the 11/19 build for 2 days now. With the camera fixed, the only problem I know of is the microphone use outside of a phone call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hw4ng3r:
I had one FC with Facebook and I can't seem to log in on my device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
What? How did you get the camera working on the 11/19 build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uncleswoop:
Yeah, Facebook and fb messenger won't seem to stay open for me either. Facebook stays open just long enough for me to enter the first 3 of my email address
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Think they have issues with MM, we have to wait until they make the app compatible
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Sorry about the poor wording...I did not mean to imply that I had gotten the camera working in 11/19. Just looking forward to the next build when it will be working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Upload in progress right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
OP updated with latest build.

Camera is back in this build, much more stable then the last build. 3+ days without any reboots, lag.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
Great news ? so now all is missing is the micro working outside of phone calls ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I'll test that right away and let you know
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Matrixzone, any update on exFAT SD support? Is that something that will be coming in some future build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Matrix, do you recommend wiping everything then flashing or just dirty flashing to update from the previous build you made?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Wipe everything for this update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
MIC not working for Google Now, and other app is known issue with CM 13.0. This will persist until the same is fixed by CM team. So we have to be patient on this please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
Roger that [emoji14]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JERW28:
Thank you [MENTION=4551784]matrixzone[/MENTION] and the others for all your hard work! I am wondering this as well. I'm hoping to get time to test this ROM soon
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Yeah, mic works for calls but nothing else

-camera for pictures works perfect (love the new google camera btw)

-when switching to video, google camera crashes

-but open camera can take video no problem, (w/o sound of course)

everything else is flawless as far as I know.... ? ???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Is there an ad blocking app that works with 13? Also, how do I remove system apps system tuner didn't remove them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
i hesitate to report this bug, because i have no logs. However, bluetooth connects with my stereo just fine but music plays from the phone, not the stereo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Adaway
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Yep, I use Adaway, but received this error.

Furthermore, how can I remove system apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GoughGhan:
Did you mean ads for everything or browser wise? adaway works so does adblockbrowser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
I'd like to block all ads like Adaway, but as the screenshot shows, the host file can't be edited. How did you get adaway to work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I jumped on this latest build right away, but before [MENTION=4551784]matrixzone[/MENTION] indicated that a clean install was recommended. I had already dirty flashed it over the previous build. That said, everything seems OK with the exception of the camera in video mode. As a camera it is fine, but dies when switched to video. If that's just me, that will probably be enough to justify a clean rebuild.

Is the video camera crash just me, or the same for all?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
I clean flashed and I have the same problem with Google camera, but sound doesn't work anyways (besides calls) so there is no point to take a video IMO. But if you download open camera from the play store video does work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hw4ng3r:
Anyone else notice that after a reboot, data (ie. LTE) is absent? This is fixed by a simple airplane mode toggle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Saves me a rebuild. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niphoet:
I experienced this also. I get no data at all until I toggle airplane mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chitown835:
Use Link2sd to remove system apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Thanks, but didn't work for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kereno:
Same here. It also happens when the connection switches from WiFi to Cellular. The mobile radio doesn't turn back on unless I force it. Personally, I use the Network app by Philipp Mangelow to turn the radio on and off at will.

Besides this issues, I have to say that this is one of the best ROM that I have tried in a while. It is more stable than CM 12.1 nightlies and faster. Thank you and keep up the good work Matrixzone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I'm not seeing that behavior. I can switch Wi-Fi off and LTE picks up instantly. FWIW, I am on AT&T, baseband NJ1, preferred network type is GSM/WCDMA/LTE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kereno:
I have a S3 i747m (Can version) running d2att rom, baseband NE6, preferred network type is GSM/WCDMA/LTE. The WiFi to Cellular issue is not constant. I just switched to mobile and it picked up the first time. I will have to test it thoroughly in order to reproduce the problem. Otherwise, I can confirm that the issue at boot up is constant and reproducible. I will have a look at radio updates...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Confirmed on the reboot here too. After reboot, no LTE. Toggle Wi-Fi, still no LTE. Toggle airplane mode, LTE is back. Interesting that I never noticed that before. Perhaps having it connect to Wi-Fi first, as it would at home where all my reboots happen, the problem is masked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
May have a fix for this in next build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I was about to post a new build, but during testing found that charging was broken in the phone. So enjoy with the old build until the issues are sorted out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uncleswoop:
Yesterday I noticed that my battery would drain within few hours and charging was painfully slow. That's also when I noticed if I have a completely drained phone and power it on while charging, the touchscreen will be unresponsive. It works again once restarting without being plugged in. But despite all this, I'm loving this rom. Been my daily driver since the first build! Thanks for all your hard work man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Very minor issue: I just discovered that the light sensor isn't working, therefore the phone won't automatically change brightness based on ambient light.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mario119:
I'm running the latest build (11/20) on my device as of now. It's actually running quite smoothly, dare I say smoother than CyanogenMod 12.1. However, there are still a ton of bugs that I've found. I'll list some here, so perhaps you guys can look into them:

- In the Settings Menu, there are a lot of duplicate options. An example is Ambient Display being listed in both Display and Gestures.

-Speaking of Gestures, the icon is missing in the Settings Menu. The description is also showing up where it isn't meant to be.

-The microphone isn't working for Google and other apps.

-Facebook and Messenger are both Force Closing on launch.

-The stock AOSP browser tends to crash on certain websites

-Google Camera is constantly crashing

-Google Now Launcher lags when you scroll to the bottom in the App Drawer. This bug is also present in CM 12.1

-Youtube's 60FPS mode is stuttering constantly. The bug is also present in CM 12.1 as well.

If anyone else could confirm these bugs, that'd be great. Other than that, amazing work Matrixzone ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kereno:
Regarding Facebook and Messenger force closing, the issue is CM 13 related and it has already been discussed elsewhere in the forum. To fix this issue until your next reboot, just delete or rename the libsslx.so in /data/app/com.facebook.katana-1/lib/arm and in /data/app/com.facebook.orca-1/lib/arm. You need to do this in root mode. [MENTION=4551784]matrixzone[/MENTION], as a temporary fix, could you hardcode this in your next build in order to force the ROM to delete the libsslx.so files at boot up? That would be helpful in order to avoid doing it manually. I'm just wondering if this would be possible in terms of credentials and file permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
if you know how, you can easily make a flashable zip that would delete that file and then place the rightly named one instead then flash that with every rom update. But that still makes it a temporary fix...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
The fact that this is a App file and their problem, inherently precludes Rom changes if anyone cares for my 2 cents. Besides,when rom is flashed, there are no apps so any such code in updater Script would fail anyway. But it is [MENTION=4551784]matrixzone[/MENTION]'s rom and his call.

Now this holds promise and such a zip should not be THAT difficult. If anyone is willing to experiment/code, the zip for flashing BBS is a good starting point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kereno:
I agree with you Arunscape and Perseus. There are other ways to do this. I'll work on a script to fix the FB FC issue at boot up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpeedsterPaul:
Currently trying this build out. Only issue I've run into so far is that my Bluetooth earbuds simply do not work with this ROM. It only plays music through the speaker, not the buds themselves.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kereno:
Follow up: I went the easy path and used Script Manager - SManager by devwom. I created a script named boot in my storage/emulated/0 path and added the following lines to it:

#!/system/bin/sh

rm data/app/com.facebook.katana-2/lib/arm/libsslx.so;

rm data/app/com.facebook.orca-2/lib/arm/libsslx.so;

(Depending on FB updates, the path suffix -2 might be something else like -1).

I configured the script to run silent at boot up in su mode. I also prevented FB and Messenger to start on boot with CM Privacy Guard in order to avoid a force close error before the script can execute.

For a temporary fix, it's pretty easy to do, almost risk free and it works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
All of the things you have reported has already been answered before. Most of these things will be there when CM team port the features into CM 13. So we have to wait for these features to be available in CM 13.0

Good News - CM 13.0 official nightlies are getting closer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mario119:
I wasn't sure if everything I listed was previously reported, so good to know. It's great news that the CM 13 nightlies are coming to the d2att soon, some other higher-profile devices actually already have them available. I'm just impressed that people are requesting Marshmallow for the Galaxy, despite it's age. It's more than capable of running Marshmallow too, as seen by your builds are running smoothly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I think even Samsung S2 will get MM, you never know :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
#offtopic does anyone have a fix for the lag of the Google now launcher app drawer ? Same lag exist on 12/12.1 builds ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Lots of fixes and battery improvement in next build.. That's what I can say right now :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Hate to say it, but my fix was to switch to Nova Launcher. In my case I was fixing a different problem, but as a result I'm not dealing with the lag. I really wanted to use Google Now, and did for a long time. I really liked the idea of running the "pure" google experience.

However, my personal requirement for a 5x5 icon arrangement on the home screens made me look elsewhere. With Google Now launcher I would have had to either run xposed or mess with the dpi in order to get a 5x5 icon arrangement. Both of those options came with their own issues. Instead, I moved to Nova Launcher. Nova is so configurable and smooth, I have never looked back.

The only thing I see missing from Nova are the Google Now cards. That said, you still have access to them, but you have to pick some way other than just swiping all the way to the left to access them. Due to Nova's highly configurable nature, you have a variety of choices.

---------- Post added at 08:18 AM ---------- Previous post was at 08:12 AM ----------

Such a tease. Is it just charging the battery out of thin air now? At least at idle, it is already awesome in my experience. I'm pretty sure that my S3 has never had such great battery life as it does now on CM13. And that's still with the original 3+ year old battery.

Edit: Looking at the change logs, it would seem that "doze" was not even enabled, but will be in your next release. Hard to believe.

Prior to all this CM 13 work, I had decided I would be getting a new phone real soon, probably a Moto X Pure when a good deal presented itself. Now I'm seriously putting that plan on the back burner. Aside from looking a little rough around the edges (stupid blue coating pealing off), the S3 continues to be a nice phone, a real workhorse. Thanks to [MENTION=4551784]matrixzone[/MENTION] and all the contributing developers for keeping the S3 viable all this time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
What did you mean by doze was not enabled ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
This merge from the change log says it is enabling doze for msm8960, which I believe is us. Perhaps I am jumping to conclusions, but if the change is to enable it, I'm assuming that it must not be enabled. Pretty surprising given the idle time I'm already seeing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
Well with the last build I had "7 days left" with 80% left in the battery with data and GPS on.

It's a great stand by time if you ask me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
[MENTION=4551784]matrixzone[/MENTION]: does 911 calling work on these builds? I saw you +1'd the change on gerrit, and this is going to be a blocker for official nightlies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
you can easily put the Google Now widget on any of your desktops ... Mine is 5x5 on first desktop to left of main .. full desktop is 6x5

since My home button is set to take Me to main (default) desktop, I can see the widget with two actions: home, then swipe left

you can also use Nova gestures .. I use swipe up to take Me into the Google app .. screenshot attached
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aha360:
Well if you think the OS would format microSD cards in F2FS format, think again, as I have went through the process and it would ONLY RECOGNISE AND FORMAT MICROSD CARDS IN FAT32 FORMAT, and this is regardless of what phone you're using, but I have to say that this needs fixing IMMEDIATELY (for those who need to have large files on the microSD card) and THAT is what's holding me back from using Android Marshmallow in the first place!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
For people having lag in the Google now launcher app drawer, I found an easy fix ; just reduce your DPI. I've set mine on 280 and it's smoother than ever. You can try it.

I'm also using the on screen nav bar buttons..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the Moderator

To all in this thread .......... Post Respectfully....... Post On Topic........... Or........

..........DO NOT POST ....... EASY .......... Stay on Topic

Do Not personalize your comments ... they will get deleted and get you into trouble

Remember ... this is development thread..... That means you post on development related issues.

Thanks ~~~ oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
are you saying that choosing the first option (to use sdcard as Portable storage) re-formats the card ??

is a factory reset and system wipe enough to come to cm13 from cm12.1 ... or have to wipe internal (/data/media) as well ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
Factory reset is enough. No need to wipe internal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vtails:
I could use some help,info on why I installed this rom. My AT&T had BattleFrontier and restored to stock 442 it wouldn't boot with out going back and wipe Del. cache so I tried many other TW rom's and some Lolipop but nothing would install, I formatted and wiped nothing worked until I installed this rom. What I need is all the preinstall app's that came with this I would like to get rid of. I don't use them but since this is working I'd like to keep it but get rid of play book's play movies without messing up the phone Which I have done in the past. I've been searching for program like Ashman's but haven't found anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Yes. Either option will format the external sd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
but this only pops up if it cannot read the sdcard in the first place ?

if it is able to read the card, then the Portable option should just leave the card as is ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
Can you be more clear so we can help you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I believe you are correct. The message that came with the options indicated that the card was in an unsupported format. Presumably if it was a supported format, it would have used it as was.

In my case the card was originally exFAT. I think the support for exFAT will be there eventually, in which case I would not have had to format.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] serstylz2:
I think I am going to flash this later this week. Going through the initial posts, it appears Camera/Wifi/GPS is stable, is that correct?

Also, I'm on MJB everything at the current moment, it says "latest bootloader" in the OP, does that mean i have some research ahead of me to figure out the latest bootloader?

Finally, for the Linux kernel listed in OP, do I have to find that and flash that separately, or is this included in the build? (Is the bootloader included in the build for that matter?)

Sorry, probably some NOOB questions in there but I left the flashing game a while back and do not assume or pretend I know enough to just start blind flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I have been following this thread since he first started building as an unofficial 12.x. I believe any of the 4.4.2 bootloader/modem combinations will work, but MJB will not. You could always try NE4 (AT&T) to start. If that doesn't work then go to NJ1 or on to NJ2 if necessary. The bootloader/modem files are not in the ROM build, you will need to get them elsewhere. enewman17 has recovery flashable zips in each of his 4.4.2 threads.

The kernel is included in the build, so no worries. At this time I would suggest staying with it and not one of the custom kernels. For the time being the stock kernel will probably include new fixes quicker than the custom ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
thanks for the info

unfortunately, I dont think there will be support for anything besides this 'vfat'

google has been pushing to remove external sdcards and the lack of them in nexus is the only reason I have stayed away

they want the "portable" option to be something that can be used in android/windoze/crapple .. one format .. they chose vfat

they want the "internal" option to be a second internal android ext4 drive

they dont want to have to support probs with extSdcard anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
Really? I just ordered a 128 GB SD card because I thought it would be a great thing to have... :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
that's fine ...

if the card is in format that MM can read .. it will handle it fine

if it is not, then you will get the popup and can choose to make it:

portable, in which case it would be formatted vfat

or internal, in which it would be formatted ext4 and only be usable in android/linux

however .. I dont know if the S3 can handle more than 64GB .. but most newer phones can