yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] YabbyYou:
Morning XDA, just wanted to give some input on this excellent CM13 build for our SGS3. I've been running the 2/10 build of this as my daily driver since it came out. Quick side bar, I was running CM12.1 for the longest time, I downloaded the 2/10 nightly as well as the corresponding opengapps mini package and flashed both onto my SGS3 using TWRP. I did not factory wipe my phone, just cleared the cache partitions after I completed the flash. Updating apps took a long time to run, but I just let it go. It's been working great. Very stable for me, battery life is acceptable and almost everything is working great. As stated many times in this thread, the front facing camera is not working well. Also, the bluetooth is a little unstable, but it seems to depend on the device I connect it too. I mostly use it for listening to music on a bluetooth speaker or connected to my headset for hands free phone calls. I have a few different bluetooth speakers, some work better then others on this build. I've been using TiBu to backup my apps without any problems. Wifi seems stable and fast, LTE/3G working well too. GPS works ok, but I've always had issues with the GPS on my SGS3. I've done all the fixes out there and sometimes it works perfectly, sometimes, not so much. Overall though, I have found Google Maps and Navigation to be better on my phone running CM13 then when I was running CM12.1. I use my phone a lot on my commute to listen to music, using poweramp, (locally stored on external sdcard) and podcasts using Pocket Casts. Both apps work great. Regular camera works good, I use CameraZoomFX as my main camera app. I haven't tried taking a video. Casting to Chromecast works, Google Fit works, SomaFM works. SMS/MMS, group texting all work using Textra.

Onto a few questions:

I noticed that when connected to Wifi and/or LTE, the send/receive indicators on the status bar don't show. I seem to remember that working in CM12.1, could this be a bug or did something change?

The volume control is behaving a little differently to me. CM used to remember the volume level I had set for BT devices, or when I plug something into a headphone jack. Now it seems to just keep whatever volume level is set, instead of adjusting per device.

The light sensor is not working completely for me. My screen does not adjust it's brightness. I have the "Phone Tester" app installed and it's reporting 0.0 lx for the Light sensor. Hopefully this gets fixed as well.

I'll probably make the jump to one of the new nightly builds sometime this week. Looking to see improvements in the BT and front facing cam. I may also give dkp's custom kernel another try. Big thanks to the CM contributors and to the devs specifically working on our build. I've been a long time lurker on XDA (back to the days of the OG Droid). This really is a great community and has some of the most talented devs I've ever seen.

Hopefully this wasn't too long but I wanted to convey just how good this build is as a daily driver. I look forward to more excellent builds of CM13 for our SGS3.

Thanks!
[Verizon Samsung Galaxy S III] Omega Ra:
Do any of these builds have the Microsoft Cortana integration and such?
[Verizon Samsung Galaxy S III] Roger W:
Yep, works fine for me. In the stock mail app, I go to Add Account, type my company email address, and hit Manual Setup at the bottom of the screen. Then it asks if it's POP3, IMAP, or Exchange.
[Verizon Samsung Galaxy S III] Jaws4God:
weird... heres mine...

version.. with services...
[Verizon Samsung Galaxy S III] YabbyYou:
Jaws,

I don't use Exchange but I tried adding an account to see what happens and my stock email is behaving like yours, no Exchange option, just IMAP and POP3.

As I stated in my previous post, I'm running the 2/10 build of CM13.
[Verizon Samsung Galaxy S III] Jaws4God:
2/23

I got excited when i took a 2nd picture with the front camera.. however when i moved to the brighter kitchen light.. it hard froze..
[Verizon Samsung Galaxy S III] Roger W:
I have Exchange Services 6.0.1, not 5.0.1, see attached.. Maybe my gapps? I flashed open_gapps-arm-6.0-pico-20160217.zip. I'm on the 2/17 nightly as well, but Exchange has worked for me all along and I update almost weekly.

This install was a clean install because I tested encryption again (unsuccessfully), though I did do a bulk restore of TiBu apps and data onto the new install, so I might have some cruft from a month ago, but I didn't let it overwrite system APKs.
[Verizon Samsung Galaxy S III] Jaws4God:
thanks! maybe ill try the newer gapps
[Verizon Samsung Galaxy S III] Jaws4God:
well i downloaded the open gapps 2/23 (mini) ... then flashed. still has services 5.0 and front camera does not work.

if anyone has a full functional CM13.. please let me know what gapps and version you are on.

thank you.
[Verizon Samsung Galaxy S III] Jaws4God:
is there any way you can send me that file? :confused:

It still bugs me why mine is the 5.0.1 version when I flash the Open Gapps Mini . Makes me wonder if i'm doing something wrong..

*********************************

2/24 Update - Front camera hard freeze and reboots.

*********************************

( EDIT )... did a test. installed Nano Gapps.. it removed the services.. then installed Micro Gapps, that installed 5.0 exchange services.. going to do a clean install with Nano Gapps to see if and version of exchange is installed from CM13.
[Verizon Samsung Galaxy S III] YabbyYou:
Maybe RogerW can tell us what specific version of opengapps he installed? (EDIT: he did, my mistake - open_gapps-arm-6.0-pico-20160217.zip) I think you're on the right testing path Jaws, to me, it sounds like something funky with the opengapps install. For what it's worth, I have version 5.0.106634657 of Exchange Services and I used open_gapps-arm-6.0-mini-20160210.zip .
[Verizon Samsung Galaxy S III] Jaws4God:
******************** Completed TEST **********************************************

After a clean install with CM 13 (02/24 version) and Nano Gapps... it

did not

install an exchange service. So I am not sure where some of the guys are getting the Exchange Services 6.0.1 .... so right now i'm not sure the best way to get my work email on my phone without a 3rd party app..
[Verizon Samsung Galaxy S III] YabbyYou:
Jaws - I found this little tidbit in another thread:

Open Gmail -> Side menu -> Little down arrow next to your Gmail account -> Add account -> Exchange

It's available for me following that path. I don't have Exchange so I can't test if it actually works.
[Verizon Samsung Galaxy S III] Fenix2002:
Not sure either. I don't use exchange, but I tried CM13 2/24 with OpenGApps nano 2/24 and the email app is version 6.0.1 and I have access to exchange.
[Verizon Samsung Galaxy S III] Roger W:
Weird! I just PMed you a link to the 6.0.1 apk from my phone.

I haven't done anything unusual with my installs. Open Gapps does note that bad things can happen if you don't install it immediately after flashing the ROM (i.e. don't reboot system in between) but since you just did a fresh install you're probably safe there.
[Verizon Samsung Galaxy S III] Jaws4God:
got the file, but no luck on install.. it did open up the option for exchange on the default email app.. however i would continue to get " Exchange Services has unexpectedly stopped " [emoji22] [emoji30]
[Verizon Samsung Galaxy S III] Fenix2002:
For late night giggles while I couldn't sleep, I encrypted my phone. I'm on the 2/24 build, and not having any issues with my SIM. Able to call, text, use data.

To be fair, I'm on the Straight Talk variant (SCH-S968C/d2tfnvzw) and it's 3G only. We have to have a deactivated SIM in newer ROMs to get any data service at all, but we don't actually get 4G service (although mine has shown connected to 4G service before! [emoji13] )

Anyway, thought I'd share that tidbit, because this is the first time I've tried encryption.
[Verizon Samsung Galaxy S III] pogeymanz:
Interesting! Thank you for trying that out and reporting. I've been stalking the thread ever since I first tried the new CM 13 nightlies waiting for anyone else to try encryption. I can't run the ROM unless I'm able to encrypt, but not being able to make phone calls was kind of a deal breaker...

I'll give this a go again tomorrow and see!
[Verizon Samsung Galaxy S III] Fenix2002:
It may not work, so definitely make sure you back everything to before you try. Lol. It may be something unique to the ST variant that let's this work, since it doesn't rely on the SIM for service
[Verizon Samsung Galaxy S III] Jaws4God:
can you tell me details on what this is? purpose?

how do you do it?

thanks!
[Verizon Samsung Galaxy S III] Fenix2002:
It encrypts any and all user information on your device (apps, files, media, calls, texts, etc.) with a "cryptographic key".. Basically it scrambles your data unless someone has the right key. When you boot your phone, it'll ask you for your password/pin/pattern/whatever you set up, and it'll decrypt your information using your special key. As soon as the phone turns off again, data is re-encrypted, and inaccessible.

If you've heard or read anything about the Apple&FBI issue going on right now, this is the root of what they're arguing over, except iOS has mandatory encryption on newer devices.

How-to:

Settings>security>encrypt

But you have to have a full battery and be on the charger and willing to wait as long as possible to encrypt without unplugging. It took me ~10 minutes.. It warns it could take up to a couple of hours.
[Verizon Samsung Galaxy S III] Jaws4God:
thank you!

so does it only require pin when booting or each time screen comes on?

what is the issue with encrypting?
[Verizon Samsung Galaxy S III] Fenix2002:
Your pin or pattern is required each boot to decrypt your device. After that, it's just required as your normal lock screen. Until a reboot.. Wash, rinse, repeat.

The issue with encryption is that if you don't have the key, you can't access the data. FBI is mad they can't access the San Bernardino terrorist's work iPhone because of encryption, is requesting Apple to go out of their way to build a way to bypass or try to crack it with brute force attacks. It has some serious consequences for EVERYONE'S personal privacy rights, and that's why Apple has taken a stand and Google is supporting them in this case.
[Verizon Samsung Galaxy S III] Fenix2002:
Update on encryption:

I can't send MMS on the Straight Talk variant which means there's probably an error in the SIM department because of encryption.

Probably better not.. Verizon variants would probably lose service.
[Verizon Samsung Galaxy S III] Jaws4God:
well it was a nightmare to get rid of the encryption.. but after several formats and completely fresh clean install.. i have Exchange 6.0.1 ! [emoji1]
[Verizon Samsung Galaxy S III] od4g:
While it's no fix, it seems every other time I reboot I get a popup saying "SIM Card Added - Restart to use" or something similar. If I reboot, then I get the No SIM Card error again. If I just press back to make that popup (SIM Added) go away, the phone is good to go, LTE and all. Again, it's just a bandaid, but may be useful to someone who doesn't want to reformat. Aside from encryption issues it's been great. Been using CM12 and now CM13 for awhile as a DD. SIM Issue after encryption still exists on 2/24 fwiw.

Edit: Well, sometimes it just won't work after a bunch of reboots.. Nevermind.
[Verizon Samsung Galaxy S III] Jaws4God:
has anyone had any issues with the stock messaging app hanging up and rebooting the phone? It has happened to me 2 or 3 times.. I believe its related to starting a group message.. after I add the names, I click the check mark and then when I go to start typing the message.. screen will go black.. then after 30 secs.. reboot.

also, now that I have Exchange 6.0.1 , I added my work email.. and noticed right away it was draining my battery much faster than it should.. anyone else experience this with exchange services?

Thank you.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey Jaws, I just tried a test of the Group MMS. I normally don't use the stock messaging app, I use Textra. In any case, I fired up the stock app, created a group MMS, added some people following the steps you took. No crash. I then sent the message to make sure, also no crash. EDIT: I also am not using the stock keyboard, I use Swiftkey. I'm still on the 2/10 build of CM13.
[Verizon Samsung Galaxy S III] Fenix2002:
I don't typically MMS, but I do use the stock app. I fired it up, did a group message, checked the group contents, but didn't send the actual message. No crash. 2/26 build.
[Verizon Samsung Galaxy S III] Jaws4God:
yeah it doesn't happen every time.. so still trying to find out the factors.. just curious if anyone else has had any reboots because of it. [emoji12]
[Verizon Samsung Galaxy S III] Roger W:
My battery time seems ok with Exchange push enabled, but if you're used to doze/deep-sleep mode I could imagine this being worse. I think doze is working for me, though, because I also have an IMAP account that polls every 15 minutes and alerts if a folder gets mail, and that doesn't alert on time when the phone isn't plugged in. So that's doze at work.

I'd guess my trend would be about 30-40 hours on a charge if I didn't actively use it. (New battery as of November)

Also, no problems with group MMS using swype.
[Verizon Samsung Galaxy S III] YabbyYou:
Is the light sensor working any better on the newer builds? I'm missing the auto brightness feature on the 2/10 build.
[Verizon Samsung Galaxy S III] Fenix2002:
2/26 build -- no, light sensor still not registering (tested with Phone Tester app)

Edit::Update:

2/27 -- no different. Light sensor and front camera not working. On the bright side, auto-orientation seems to be working.

Also, if you notice an app not syncing (like gmail, in my case), doze is usually the culprit. You can turn off individual app optimization in settings>battery>battery optimization (in menu). That worked for me.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Don't know if it's related, but lately I've gotten Textra hanging my phone and causing reboots sometimes too.
[Verizon Samsung Galaxy S III] YabbyYou:
I use Tetra exclusively as my messaging app and I haven't had any crash or reboot problems. Maybe delete and reinstall it?
[Verizon Samsung Galaxy S III] YabbyYou:
I found one of the odd volume problems is being caused by Camerazoom FX. If I have the phone in Do Not Disturb, then open Camerazoom, it switches off do not disturb, I'm not sure why but that's a little annoying. I like my phone to pretty much be silent at all times.
[Verizon Samsung Galaxy S III] Jaws4God:
2/28 Front Camera still freezes.
[Verizon Samsung Galaxy S III] Fenix2002:
Anyone having issues with phone quality? Starting on last Monday, 2/22, I started getting complaints of bad connections. Some people I talked to said that I was cutting in and out every 10 seconds or so, and that I had a "robot voice" occasionally. No issues on my end, though, and if I called someone back they said the call was better. I've also started not getting all of my calls, even with solid service.

Anyone else seeing these sorts of issues with recent builds?
[Verizon Samsung Galaxy S III] Jaws4God:
i haven't noticed anyone saying anything about my call quality...

anyone install the 3/1 version ? it wont let me see the change log and that has me nervous.. lol

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.
[Verizon Samsung Galaxy S III] Fenix2002:
OK. Maybe it was just a fluke, or probably the weird weather my area has been getting recently.

When you can't see the changelog through the built-in updater, you can check it on the website at www.cmxlog.com/13/d2vzw/
[Verizon Samsung Galaxy S III] YabbyYou:
I am seeing the 3/1 change log using the link from the OP. I also see the list of changes targeted for the next build.

I was going to pull the trigger on the 3/1 build but pesky work got in the way. Maybe the 3/2 build tomorrow.
[Verizon Samsung Galaxy S III] Jaws4God:
well I'm on it (3/2).. no fix for front camera yet.. and I think light sensor is still having issues.. its almost impossible to see screen in daylight..

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.
[Verizon Samsung Galaxy S III] YabbyYou:
Jaws, thanks for the info. I agree, the screen is just about impossible to see in daylight when the auto brightness is on. I'm not sure if we can submit a bug report anywhere on this. We should probably feel amazingly lucky there is even a working build for our phone! In any case, if there is someplace I can submit a bug report, let me know.
[Verizon Samsung Galaxy S III] Jaws4God:
3/3 Front Camera no luck.. :-/

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.

---------- Post added at 02:57 PM ---------- Previous post was at 02:32 PM ----------

anyone having issues with themes? i don't think i had tried them on the last few versions either..

*edit - reboot seems to have fixed it *

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
CM: 03/04 Nightly

Anyone running into rebooting issues? I've been stuck in reboot mode for over 10 minutes. It's not looping. It's stuck in the process where the device is powering down. I've been seeing this in the past 3 builds on my device. Not sure if it's tied to any of the builds but just curious.
[Verizon Samsung Galaxy S III] Fenix2002:
Nope. I just updated to 03/04 about an hour ago and it works just fine for me in that regard.
[Verizon Samsung Galaxy S III] YabbyYou:
I just updated to the 3/4 build. Not having any reboot problems.

Light sensor still isn't working.

Front Camera still not working.

Bluetooth is a little better but not much. Still skipping when playing music every 30-45 seconds when I use my SuperTooth speaker. I'll do some more testing with other bluetooth devices to see if things are different.

Also, I still don't see the wifi activity in the wifi icon on the status bar. I know this used to show activity on CM12.1, but on CM13 I'm not seeing it.
[Verizon Samsung Galaxy S III] Jaws4God:
i did have 2 random reboots.. one i was changing a theme and the second was when i had selected several people for a group MMS

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Have any of you noticed Bluetooth "forgetting" devices?

I have to reconnect it to my car stereo every other day or so, and it goes through the "would you like to grant access to messages and call info" type dialogs each time.

Also, and much more frustrating, I have to factory reset my Moto360 every couple days if I want it to reconnect, since they can only be connected to one device, and disconnecting / "forgetting" a device trips that. In the Android Wear app on my phone it's stuck in a state of "connecting" when it forgets the watch.

This has been going on for 2-4 weeks or so as a guess.
[Verizon Samsung Galaxy S III] YabbyYou:
I have not noticed that. I was running the 2/10 CM13 up until today. I had a bunch of bluetooth device profiles saved. They all connected each time, no problem. Now, I cleared all the profiles out before I updated to 3/4 because I'm trying to figure out why I am getting skipping on music playback with one of my bluetooth speakers. So far, the profile is not being forgotten.

---------- Post added at 11:31 PM ---------- Previous post was at 11:26 PM ----------

Jaws,

If you are still having some weird theme issues, I noticed a bunch of commits that seem to be related to themes in the 3/5 build. Maybe something in there will tame the themes on your phone.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well, I'm back over here with y'all again after holding tight to AICP for awhile - a couple of things not ready for prime time there. Also don't think too many d2vzw's are using that ROM, if any! At least we have 2 ROMs currently developed for our phone, though we ain't being taken care of great here with the builds disappearing right quick, though the links remain. (Not sure what the benefit would be to have them, except for some 12.1 builds, which should be kept available.) Still, [MENTION=2385005]invisiblek[/MENTION] deserves $500 of my money (if I had it to give away ...)

You'll be glad to know that I'm able to take pictures easily with the front camera on 3/5. I can even take videos! However, the transition from stills to video on the front camera is far from clean - it'll probably lock up and/or force to be closed. Open the next time and you're ready to go. Going back the other way the same thing, on the front one. (I forgot to test the rear camera!!) Guess I'll get a logcat before long.

I also have not been seeing any Wifi drops on the last 1 or 2 builds using the native DHCP client.

:cyclops:
[Verizon Samsung Galaxy S III] Fenix2002:
Welcome back, Master Cylinder! I was wondering what dark corner of the forums you were hiding in. Lol.

Holy snot rockets, he's right! I've been able to take front facing pictures for awhile, as long as it was in low light.. But for the first time, it seems OK with full light! ?

The light sensor is still not functioning for me, according to Phone Tester app. Idk.

Without a doubt. If/When I have it, I plan on kicking some his way. ?
[Verizon Samsung Galaxy S III] Jaws4God:
yeah i was starting to give up on Cyanogenmod and front camera.. tried to see what other MM ROMs were out there.. only ones i found were AICP and Oct OS.. both built on CM.. so cameras don't work.. just dont know why some people says it does. ?

downloading v3/5 now! [emoji1]

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.
[Verizon Samsung Galaxy S III] Jaws4God:
did you do a clean install? my 3/5 version still fc on front camera :-/

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well Blimey! It was late but I was straight last night I swear!! ;) Feenix2002 was right, all of the pictures I popped off with the front camera last night were in very low light. Today with the New Mexico sun out - nada. Same as before. (A really long bronx cheer goes right here...)
[Verizon Samsung Galaxy S III] AyUaxe:
[MENTION=2334309]ibnarabi[/MENTION] said front camera worked with Open Camera, over at AICP's place. He confirmed he's on d2vzw. YMMV. I recently uninstalled open camera, bc horrible lag and wouldn't auto focus. Guess I'll give it another go.
[Verizon Samsung Galaxy S III] Jaws4God:
ive been in same boat.. a few tines id take a pic with what i thought was bright enough light.. but right before id go tell you all, id try with more lights on and BOOM .. FC :(

hope the CM team can get it! I think Android N is coming soon ;)

sent from Samsung Galaxy S3 via Tapatalk powered by Cyanogenmod 13.
[Verizon Samsung Galaxy S III] Fenix2002:
Yeah, it doesn't make a whole lot of sense. It's getting better, though. I was able to capture a lamp in one last night. (Sounds funny, but there it is.)

From what I can tell and have tried while briefly messing around is that if the camera tries to focus because of the difference in brightness, it FC's. I was able to quickly turn it towards a light and snap one before it tried to adjust. Lol. You can also try to play peekaboo with your phone. Hold your hand over the camera, then pull it away real quick and snap the picture as soon as you can.

I'm having the same issue with OpenCamera, and Google Camera. Biggest thing with OpenCamera is that it won't close when the camera goes off the rails. The preview will freeze, and the app will still be chilling.

Edit:

Not sure how I feel about android N from the rumors so far. No app drawer? Redesigning the QuickSettings shade, and making the notifications into Google Now cards? Ehh.
[Verizon Samsung Galaxy S III] YabbyYou:
Just flashed decimalman's dkp kernel onto my 3/4 CM13 build. Running good so far. Bluetooth seems to be behaving better but I have upped the CPU freq to 1620mhz and I set the governor to "performance". I'm sure my battery life will suffer.
[Verizon Samsung Galaxy S III] AyUaxe:
dkp

I have had stability at 1782 but not higher mhz. Tierservative has been best compromise gov. Also, try deadline for internal i/o, sio for sd. Let us know results.