yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Roger W:
Just went to 3/15.:

Exchange is back!

My alarm app wasn't crashing on 3/14 so I can't clarify if that's better for those that had a problem. At least the UI buttons are the right color again.

Front camera is no better than usual

I won't be able to comment on BT audio until this evening.
[Verizon Samsung Galaxy S III] YabbyYou:
Is auto rotate working? Everything okay still with LTE?
[Verizon Samsung Galaxy S III] Roger W:
Both seem fine!

I just did a TWRP backup and will try encryption soon.

Edit: No apparent change with encryption, but I just tried what od4g posted last month and that works: only the very first boot can't use the SIM card. Each boot after that says a new SIM was found and a reboot is required to use it, but that's not true and just hitting Back makes the message go away and the phone works fine. The SIM is only found on the 2nd boot apparently, not the 1st or any after the 2nd. I'm going to have to give up on encryption again. Oh well.

Edit 2: Still no bluetooth Media profile function
[Verizon Samsung Galaxy S III] Fenix2002:
Thanks for the update Roger
[Verizon Samsung Galaxy S III] jonny30bass:
LTE doesn't work for me. Clean flashed the rom and nano open gapps, and I'm using the NE1 modem. This is on the 12/14 nightly.
[Verizon Samsung Galaxy S III] XdrummerXboy:
CM13 is pretty stable for me, after a couple minor hiccups during the first boot or two.

Back camera works for pictures. Video gets "cannot connect" even just for the preview.

Front camera preview works, but the picture doesn't save. Sometimes freezes the phone.

Main issues are app specific, such as Snapchat freezing the phone, weird issues with XDA mobile app listviews not showing the content until you scroll down, and Titanium Backup gets stuck while restoring apps/data.

Pretty sure TiBU was having issues for me on 5.1 though, so maybe that's a moot point
[Verizon Samsung Galaxy S III] matt_man:
When I updated to CM13 it said my sd card was corrupted so I went ahead and formatted it as internal and let it move everything from internal to the sd card. Note I can't access any backups or zip files on my sd card in TWRP.
[Verizon Samsung Galaxy S III] ioctlLR:
Need help debugging boot issues...

So my phone is still running 4/21. Sometime between then and 5/11, a change was made that stopped it from being able to run the newer builds. I tried 13.0 earlier today (12/14 build), and it's a little better, but still borked. Upgrade or clean install doesn't matter. Short version, I never get a responsive UI. Some builds bootloop, most just sit without a UI at all, and 13.0 showed me the setup wizard, but it was unresponsive. I've tried to enable adb / usb debugging via recovery, but adb never appears to start. At this point, I have no idea how to pull the necessary logs so I can figure out the issue...

Any ideas?
[Verizon Samsung Galaxy S III] bryank29:
Have you tried Open Camera?

---------- Post added at 04:56 AM ---------- Previous post was at 04:55 AM ----------

You pretty much screwed yourself doing that, I think.

6.0 does some fuggly stuff with the read/write of the external SD card, even if you put it in portable mode (during the setup process, that was the other option) and I found I couldn't write to it. I "think" it can be made writable via the Explorer app, but not sure.

---------- Post added at 04:57 AM ---------- Previous post was at 04:56 AM ----------

I am actually shocked this thread only has 3 pages thus far.
[Verizon Samsung Galaxy S III] Fenix2002:
I've tried OpenCamera on the last few builds, as well as a few others. They all behave pretty much the same way. The back camera works for photos and video, front camera works for video, but will completely crash with photos. Occasionally, it will completely lock the device; I've had to do battery pulls, force shutdowns, and actually had it self reboot when trying to take photos with the front camera. And when you get "can't connect to camera", most of the time I have to do at minimum a soft reboot.

I haven't had any issues with not being able to write to SD if you choose the portable option, so far. But the built-in CM File Explorer won't handle root functions (that I've tested so far), but ES File Explorer will.

As far as fixing the SD problem, [MENTION=5779024]matt_man[/MENTION], I think you'll probably either have to reformat it in terminal in TWRP (assuming it still reads it as a separate device. I haven't tested that aspect yet, for exactly this reason) or you MIGHT just resign yourself to doing a fresh flash of CM, shutdown, remove the SD, reformat it on your computer if you have an SD card reader, and then loading it back up with all your stuff and using TWRP. Idk.

First post was 4 days ago on the Official. There's actually quite a few pages in the Unofficial thread from before the 12/11 build. lol.

In other news, 12/17 build is up! Yasssss.
[Verizon Samsung Galaxy S III] bryank29:
hmmmm the first time I noticed the 'read only' issue was using QuickPic gallery and it needed me to confirm something and I did. But when I tried to move a photo I took to the SD card, it gave me the permission error. My research told me this was implemented on purpose in Android 6.0.
[Verizon Samsung Galaxy S III] Fenix2002:
That's odd. I haven't read anything about that specifically (I have read that MM is designed to make it incredibly difficult to write to /system partition, but that's a different beast entirely and seems like CM may have taken care of that already). So maybe it's actually a permission error with that app? I just successfully moved a picture from internal to external and back with CM File Manager, ES File Explorer, and the built in android Explorer (from the settings menu).
[Verizon Samsung Galaxy S III] bryank29:
This is where I read it https://www.reddit.com/r/Android/comments/3oz7eu/guidelines_for_marshmallow_users_formatting/
[Verizon Samsung Galaxy S III] XdrummerXboy:
What version of TWRP are you running? I *think* I'm on 2.8.7.0 or something like that. Chances are if you're on the right firmware and modem, and even clean installs don't fix it, you may have an outdated version of recovery that doesn't flash things correctly. Or you're just extremely unlucky and keep flashing borked builds! :D also, you may want to compare MD5 checksums, if you have a poor internet connection downloads may become corrupted or something.
[Verizon Samsung Galaxy S III] stevet86:
Just updated to the latest release with a delta. All went well except the wait for the optimizing. All of the functions I've been using so far have worked (hasn't been too many.) The only one thing that was weird is Bluetooth and ford sync. With 5.1.1 I could connect the phone and stream media. With 6.0 the phone connects but it will not stream the media. I haven't tried it with the latest update. Thanks again for all of the work put into this ROM.
[Verizon Samsung Galaxy S III] Master Cylinder:
Are you running Xposed? I've tried it with Gravity Box and that's what I get. It'll work for a little while, then complete meltdown.

I think you should be able reformat it through TWRP Wipe>Advanced Wipe> select a partition/device>Repair or Change Filesystem. As [MENTION=4652020]XdrummerXboy[/MENTION] said, that's if it recognizes your card as a separate card now. I have no idea how it's mounted within the operating system but that probably won't be true on recovery, which mounts things differently, so you should be able to do it. However, if there is any data that's been moved there, it'll be lost, as everything was when you chose to format it the first time.

However, there is also the fact that even if it is mounted portable, you have to set TiBu to look in a different path now to access the backup files - it won't know that it's mounted differently under MM.

[MENTION=978524]bryank[/MENTION] mentions the choice of mounting it as portable, but some people have been told that theirs was unreadable and had to be reformatted with no choice to mount it as portable. Sounds like that might have happened to you.

Also, I've had some conundrums with writing and reading to different places on the phone but it pretty much works now, except I have an empty zombie folder that I can't delete on the /sdcard, even though it says it's deleted and disappears. When I do a refresh, there it is again. And when I do a search for it, it shows to be mounted about 40 different ways. That was from 12/14.

Can't find much wrong with 12/17 yet, but love the new Live Display quicksettings tile. Had it in AICP and used it everyday since apparently "Automatic" won't work without GPS on all the time. I haven't tried it that way, but know I don't want to throw away battery life on that.
[Verizon Samsung Galaxy S III] Jaws4God:
so both camera's are completely functioning?

Do you know if they will bring navigation ring to CM13?

Thanks.
[Verizon Samsung Galaxy S III] Fenix2002:
Front camera still isn't functioning correctly for me on 12/17 (with stock camera, open camera, any camera). Videos work, photos are no go.
[Verizon Samsung Galaxy S III] ioctlLR:
I'm on TWRP 2.8.6.0, and have flashed the recommended firmware & modem multiple times (the old separate zips and the newer single zip). My internet connection is pretty solid, so I guess I'm down to flashing TWRP 2.8.7.0 and checking MD5's on *everything*. I'll probably try to flash firmware & modem again, while I'm at it.

Nope. :D

I'll post when I get a chance to try again... Might be a little while.
[Verizon Samsung Galaxy S III] Master Cylinder:
Camera: 12/17 A Better Camera works on back Camera and Video, but not on front camera. I forgot to check the stock one and I'm checkin' something else out at the moment.

Je ne sais pas on the nav ring.
[Verizon Samsung Galaxy S III] matrixzone:
Can you or someone else post log for the front face camera hang or fc?
[Verizon Samsung Galaxy S III] stevet86:
Not sure what happened. I dirty flashed the 19DEC build and I lost my SIM card. The then tried to clean flash and it still did not work. Ended up going back to the 18DEC build and all is working again.
[Verizon Samsung Galaxy S III] Fenix2002:
You're not alone. 12/19 build nuked my telephony. It wasn't reading IMEI, SIM, or anything. Was terrified that I'd lost it, but nandroid restore fixed my issue too.
[Verizon Samsung Galaxy S III] Jaws4God:
how do you do a nandroid?
[Verizon Samsung Galaxy S III] XdrummerXboy:
I don't know if it's still the case, but a while ago flashing with CWM caused either major bugs, or straight wouldn't get through the flashing process. At any rate we kind of HAD to flash with TWRP. I would suggest using that and reporting back. Good luck!
[Verizon Samsung Galaxy S III] YabbyYou:
Roger, thanks for the info. Bummer about the encryption still. Double bummer about the bluetooth media.
[Verizon Samsung Galaxy S III] YabbyYou:
This dead Bluetooth is really a drag. I've been rummaging the cm site, gerrit code review, cm open issues tracker and anywhere else I could find. I was trying to find a way to get a little more involved on the dev side of things but I haven't figured it out yet. CM really is a giant project!

Anyway, if anyone is interested, I think this link http://review.cyanogenmod.org/#/c/136368/ points to some action on resolving bt issues. It's not merged yet and looks to be somewhat broken. I'm not sure how I can get involved in the conversation so if someone has a suggestion please let me know. I hope these code changes yield something for us. I'll keep an eye on it.
[Verizon Samsung Galaxy S III] Fenix2002:
Decided to try 3/15 --

- Clock still crashing on alarm (when it tries to draw the snooze/dismiss swipey screen).

- Tried setting up extSD as internal, which worked. Migrated photos, etc., to it. Then Chrome wouldn't download anything, said I didn't have any photos, File manager wouldn't recognize it, terminal wouldn't recognize it, Play Store crashed. Big mess. Lost all my photos. *yikes*

- It ate my cat.

- All the typical fun bugs we see on a daily basis..
[Verizon Samsung Galaxy S III] YabbyYou:
I wanted to give your post a thumbs up but there is nothing thumbs up about it! Thanks for trying out 3/15, I guess we should avoid it for now? Or do you think it would be OK as long as we don't try the sdcard thing? I thought the clock thing was fixed.
[Verizon Samsung Galaxy S III] Fenix2002:
I thought the clock thing was probably fixed as well, so I gave it a shot. But every time I tested the alarm, it crashed. The alarm sounded, but when it tried to draw the screen where you dismiss/snooze it would crash, and you'd have to dismiss it from the notification. I sent a bug report to CM on it.

And yeah, the SDCard thing was a major bummer for me. Luckily I had just backed up my photos like.. A day ago. But I guess you can give it a shot, maybe I have a bad SD or it's going bad. But I definitely wouldn't try it without a rock solid backup.
[Verizon Samsung Galaxy S III] Master Cylinder:
Sorry to hear about your cat ... :crying:
[Verizon Samsung Galaxy S III] YabbyYou:
I installed the 3/17 build. Running it through the paces now.
[Verizon Samsung Galaxy S III] Fenix2002:
Would you mind trying the alarm to see if it crashes for you? Set an alarm and lock the screen. It should crash when it tries to draw over the lockscreen, or when you try to go to the alarm from the notification without hitting snooze/dismiss. That's what it does for me.

Thanks. :)
[Verizon Samsung Galaxy S III] YabbyYou:
Fenix - I was not able to get the alarm to crash. I set one up, locked the phone, waited. Alarm went off, I pulled down the shade and went to the alarm without a crash. Then dismissed. So maybe it's working now.

Auto rotate is working

Light sensor seems to be working still

Bluetooth phone calls work (as they have). Bluetooth media playback is still dead.

Front facing camera is still broke (seems more broke now then before, it crashes my phone completely now about 5 seconds after I switch it on)

Another weird thing, I had data working after the first boot. Then I crashed the phone using the front facing cam, rebooted, and then I never had data again, even after multiple reboots. I was about to restore my backup and decided to try clearing the cache again. I did that, rebooted and data returned. I have subsequently rebooted a few times and have not lost data again. Maybe it was a fluke.

I'll stay on 3/17 for now unless the data issue becomes a problem (or something else pops up).
[Verizon Samsung Galaxy S III] YabbyYou:
It looks like 4G/LTE is not working on 3/17. 3G data seems to work. I'll try a few more tests in between the St Patrick's Day festivities!

Edit: I cleared the cache again, rebooted and 4G/LTE seems to be back, for now.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I wonder if it needs to be in "doze" mode to get it to crash?
[Verizon Samsung Galaxy S III] YabbyYou:
Maybe. I think Fenix was able to get it to crash on demand, so I presume his phone wasn't dozing.
[Verizon Samsung Galaxy S III] Fenix2002:
Not Dozing. I can set an alarm for any amount of time, and it will crash.. doesn't matter if it's dozing or not (and doesn't actually matter if it's locked or not, I just discovered).

Just to recap, the alarm will sound like normal and the notification will appear. But if the screen is locked/turned off, it won't draw the screen that prompts you to swipe left to snooze, right to dismiss. If you unlock the phone, it will say that Clock has crashed. Hitting OK will silence the alarm, but the notification is still there. Tapping the notification will cause the same crash dialog. Sometimes it will show the swipey screen, but if you touch it, it will crash again. The only way to stop this cycle is to snooze/dismiss the alarm from the expanded notification.

The interesting thing is that this issue started on the 3/14 build, I think. Before that is fine, after that is junk. AICP after a certain point does the same. Clean flashing, dirty flashing, neither help.

*On a side note*: I tried to restore a stock nandroid so I could look at some network related stuff, but it won't boot all the way, saying "Encryption failed. Do a factory reset." But no matter how many I do, it doesn't fix it. I'm thinking there's something lingering on my partitions from when I tried encryption and it went bad.
[Verizon Samsung Galaxy S III] YabbyYou:
Even with a factory reset you are getting that error? That's a little scary!
[Verizon Samsung Galaxy S III] Roger W:
iirc, a Factory Reset doesn't format Data which you need to do after trying encryption and moving away from it. It's the option that makes you actually type "YES" in TWRP to continue. Let me know if it would help for me to dig into twrp and find the actual menu sequence.
[Verizon Samsung Galaxy S III] Fenix2002:
Yeah, it is pretty scary. But oddly enough, custom ROMs don't do this, only my stock nandroid that was never encrypted anyway.

And I've formatted my /data several times through TWRP where it requires you to type yes. And I've formatted manually, and done the "repair" option too. :/

so that might mean if I ever want to go back to stock I'll probably have to Odin it back. :( so that's pretty crazy.

I've had to go back to CM12.1 for now, because all the CM13 nightlies that were stable(ish) for me are gone now. Might try 3/18 later.

**EDIT**: I'm the king of off-topic conversation.. but I got the issue fixed that prevented me from booting my stock nandroid (and may help some of my other issues.. who knows?). Factory Reset and the format data button that required you to type yes didn't work. A regular wipe definitely didn't. I tried manually formatting the partition in the wipe menu, but that didn't work. Finally thought to format it to something different (did EXT3) and then format it back to the normal EXT4. Bingo, that did it for me.

EDIT2: Removed crashlog and YouTube link. Alarm clock issue is fixed in new build.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey Fenix, check out the comments here on gerrit for this fix, it mentions about force closing DeskClock: http://review.cyanogenmod.org/#/c/136674/

That fix is supposed to be in the 3/19 build, "v4: Assign mDrawable before calling setBounds". Maybe that'll help your alarm clock issue.
[Verizon Samsung Galaxy S III] Fenix2002:
It sounds like that might be the answer to my problems. I'm still curious why it happens to me and not anyone else here.

EDIT: 3/19 build fixed it for me. :) Good to go.
[Verizon Samsung Galaxy S III] beckx020:
03/19/2016 build. My alarm is ok. My camera is ok too. They have been for several builds that I've tested.

Right now, just the problem with bluetooth playing Pandora.
[Verizon Samsung Galaxy S III] Fenix2002:
I don't get why the alarm issue affected me and not others. But it obviously was an issue or they wouldn't have fixed it in the 3/19 build. Lol.

Your front camera is OK? It doesn't freeze or lock up your phone?
[Verizon Samsung Galaxy S III] razorloves:
The people without the issue may be using the google clock/alarm app. The bigger gapps packages replace the cm one with the google one. https://play.google.com/store/apps/details?id=com.google.android.deskclock
[Verizon Samsung Galaxy S III] Fenix2002:
Did not know that. That might be the explanation. I use the nano package. Thanks!
[Verizon Samsung Galaxy S III] beckx020:
I only had trouble with the first ROM I installed. 3/11? not quite sure. The camera locked up the first pic. Rebooted the phone and changed the pic size, then took pics with both cameras and they are ok. Changed pic size back to default and still never a problem with pics.

Alarm, I installed the mini gapps since I had trouble with the nano version. Phone would go in a boot loop. So I probably am using the gapps alarm.
[Verizon Samsung Galaxy S III] razorloves:
yep, you are https://github.com/opengapps/opengapps/wiki/Mini-Package
[Verizon Samsung Galaxy S III] YabbyYou:
Fenix, I think that might be it. I use the mini gapps, no alarm crash. Either way I guess the issue is fixed now.
[Verizon Samsung Galaxy S III] beckx020:
03/19/2016 build. Wow. They fixed the problem with my LTE radio using gobs of battery. I have 2 S3. One using the nightlies, one stock 4.4.2. Before the last build, I was getting the radio using 63% - 75% of my battery and the battery going dead before the day is over. I have the phones side by side and swap batteries to make sure it's not that. This new build the battery is only at 60% after all day and the radio is only at 10%. Looks normal compared to the other phone. So... now if the bluetooth gets fixed, I'm set to use it as a daily. Yay!

Thanks for all the hard work on this!
[Verizon Samsung Galaxy S III] YabbyYou:
Wow I might have to jump up to the 3/19 build and see how it behaves for me. Thanks for the update! I agree, we just need the bluetooth to be more stable and it's really going to rock! It looks like [MENTION=2044079]Nardholio[/MENTION] is working on it because I see all kinds of commits that have something to do with audio and bluetooth. Hopefully something in there gets cherry picked into our build and we can give it a test!
[Verizon Samsung Galaxy S III] Jaws4God:
anyone else able to take all kinds of pictures with front camera on the 3/19 version?

thanks.

via Samsung Galaxy S3

AICP 5.1.1 (Love Stable / Miss Doze)
[Verizon Samsung Galaxy S III] iwearthebelt:
I'm looking for some help with getting my ibolt docking station to work. It used to work fine before I updated to CM13, but now I don't have any audio output. Does anyone have a workaround for this? Any suggestions are appreciated!
[Verizon Samsung Galaxy S III] YabbyYou:
Hey iwearthebelt, are you running the latest CM13 nightly? If not, what nightly are you running? Does the ibolt docking station connect via the headphone jack or bluetooth? If bluetooth, then you're in the same boat as the rest of us. BT audio is not working at this time on the CM13 nightlies.
[Verizon Samsung Galaxy S III] iwearthebelt:
Yup I'm running the latest nightly. Funny thing is that Bluetooth is working for me. I can use the Bluetooth without any problems. The ibolt docking station uses a micro USB cable that splits on the other end to a USB connection and a headphone jack, using both at the same time. The USB for charging and the other for audio.
[Verizon Samsung Galaxy S III] YabbyYou:
Hang on a minute, you can play music over your Bluetooth to a speaker?
[Verizon Samsung Galaxy S III] iwearthebelt:
Sorry, my bad. Bluetooth is working on my S4, not my S3. Forgot i was in the S3 forum. It really should be working on the S3, they're basically the same other than the hardware. Didn't mean to get your hopes up.
[Verizon Samsung Galaxy S III] YabbyYou:
Haha, no problem. That sounds like a lot of phones you're juggling. There must be enough of a difference between the chipsets in the S3 and S4 since we seem to be having some major bt audio issues. I have faith in the devs.

As for your issue. Unfortunately I don't have any suggestions at this time since I don't have any similar hardware to try out. Did you ever have it working on a previous build of CM? Maybe on 12.1 or something? Does the charging work but not the audio? I wonder if there is some Samsung proprietary driver that allows the audio to go out over the USB that's not implemented in CM13?
[Verizon Samsung Galaxy S III] YabbyYou:
I was just looking through some of the battery numbers on my S3 in GSAM Battery Monitor and noticed that Doze was 0 minutes. That prompted me to wonder if doze was enabled on our S3. A little digging around and I think the answer to that question is No, because we don't have the correct type of motion sensor. Can anyone confirm this?

On a related note, it looks like there are some nice things waiting to go into our nightly, maybe even something BT related!
[Verizon Samsung Galaxy S III] charliepop:
Mine is showing the same thing.