yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Finally...someone else notices this for once. This has been a problem for several months. And it doesn't even have to be in a row. I can take 2 videos and try to take the third at a later time of the day. Its like there is something in the system that literally counts down to 3 recordings for it to reboot
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Yea I have seen this as well on several roms including cm for months... I just held off from reporting it since it had been reported previously...
[Verizon Samsung Galaxy S III] mastamoon:
Fixes are up on gerrit for review, hopefully they will be merged soon.
[Verizon Samsung Galaxy S III] mastamoon:
Merged now! Next nightly is hopefully better.
[Verizon Samsung Galaxy S III] darkknight1812:
I am stuck on the 03/03 nightly because it is the latest nightly that works with my official Verizon NE. If you look back at some of my older posts (within the past week or two, just search network extender in this thread), you will get a sense of what I am having problems with. The data connection connects to the tower just fine and it is stable, but once my NE is running, my phone is useless since it is constantly "losing" connection along with the screen flashing frequently. I have read on the official CM forum that other users are having similar issues (http://forum.cyanogenmod.com/topic/90370-phone-unusable-from-latest-nightlies/ and http://forum.cyanogenmod.com/topic/90338-data-not-working-on-sprint-galaxy-s-iii/).
[Verizon Samsung Galaxy S III] WarER4X:
I've been running with ART for a long time, now, and didn't think much about battery life. Lately, though, it has been quite bad. The built in battery monitor and Better Battery Stats don't really point to any specific culprit, though. I'll switch to Dalvik tonight and see if it helps.

-SR-
[Verizon Samsung Galaxy S III] NegativeOne:
Just wanted to report that 3/17 is showing down to a stuttering halt for me after about 24 hours without a reboot. Anyone else?

Camera works fine. Seem to have more "no signal" time
[Verizon Samsung Galaxy S III] rhcreed:
Trying to do a full, clean wipe.. Copied ROM and gapps onto microsd from in the system. Boot into recovery, cwm, but clockwork won't mount the card. Getting error trying to mount /storage/sdcard1. Any trick to getting recovery to see the card so I can flash from it? Thx (latest recovery)
[Verizon Samsung Galaxy S III] Hybridnoob:
Fair warning - I dirty flashed 3/24 over 3/21 using CMUpdater and it bootlooped. Clean flashing may be Ok, but beware.

Update: Manually flashing (and wiping system, cache & dalvik / instilling ROM & gapps) worked fine.
[Verizon Samsung Galaxy S III] Defragger51:
I flashed back to 3/17 because I had no issues with it the first time I used it. After 39 hours on 3/21 with no problems my txt messaging just stop working.been back on 3/17 for 25 hours with no issues no slow downs . I did however get a message, just after 25 hours, that I have never seen before saying that I have changed my sim card, which I have not, but everything still seems to work as normal
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Any others tried 3/24 yet? Don't really want to risk it/lazy to make a backup and restore if something goes wrong
[Verizon Samsung Galaxy S III] soohyunk83:
I was about to install it, but the download was only 82MB each time. So I think the download file may not be dependable?
[Verizon Samsung Galaxy S III] Div033:
Just did a dirty flash (wipe cache/dalvik/system, flash gapps+ROM) and it worked fine.

Camera is now fixed. It no longer reboots when you take 3 videos with the front facing camera.

1080p video recording (back camera) is still broken though. Stick with 720p.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks! Flashing that way worked for me. I used CMUpdater before.
[Verizon Samsung Galaxy S III] chowner:
I did the same thing with no issues
[Verizon Samsung Galaxy S III] WarER4X:
After switching back to Dalvik, I have noticed absolutely no difference in battery drain. Both are equally high with no standout items in the battery reports that would indicate a clear cause. I have noticed that the drain from the screen usages has been quite high under both Dalvik and ART even with limited usage. I'm starting to think that my battery is just plain tired. It is nearly 2 years old, after all.

Since I'm not running any apps that are incompatible with ART, I'm going to switch back. The faster, smoother app startups and reduced homescreen lag are noticeable improvements I get from it.

-SR-
[Verizon Samsung Galaxy S III] chowner:
Battery life has been stellar on the last few builds
[Verizon Samsung Galaxy S III] colklink14:
324

Hi All

Thank you Devs for your incredible devoted work.

Not whining, but Lean Kernel 9.5 does not work with 324. It was working fine on 228 with fabulous battery life

IT was an absolutely clean install
[Verizon Samsung Galaxy S III] skytbest:
For some reason my phone is only recognized by my computer about 10% of the time I plug it in. I can't figure out why. It will charge just fine, but won't be recognized as a storage device, nor will USB debugging switch on. Some times it works (of course, only when I don't need it to) but I haven't noticed any difference in state from when it does or does not.

Is this a common problem? Anyone know how I might fix it?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Just flashed 2/24 nightly and still reboots after third video recording on FFC. Could it be because I installed an early version of KT kernel?

Here's a zip of all the logs after the reboot:

https://www.dropbox.com/s/37582gfko72f0ue/2014-03-24_07.44.zip
[Verizon Samsung Galaxy S III] mastamoon:
The camera fix was kernel related so likely thats causing your problem until KT resyncs with CM.
[Verizon Samsung Galaxy S III] nmh5001:
Maybe it's just an issue with my phone, but I swear every update fixes one issue and causes two more. Thinking of going back to a stable 4.3 build for now. Any issues with doing a downgrade?
[Verizon Samsung Galaxy S III] mastamoon:
Just wipe data/factory reset and you should be fine going back to CM10.2.
[Verizon Samsung Galaxy S III] KaLiBLeeK:
FWIW, just tested out the latest nightly (3/24, stock kernel, dirty flash over the 3/17 nightly) to see if the FFC video rec x3 reboot thing is still an issue. Recorded 3 videos without a reboot. Also tried out the rear camera video recording at 1080P and recorded 2 videos without any issues.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Yeah I figured that would be it. Hopes he syncs with cm soon
[Verizon Samsung Galaxy S III] Div033:
Interesting... I came from 3/17 myself and experienced issues with 1080p. As I described in a previous post, I wipe cache/dalvik/system each time I dirty flash.

I'd appreciate if more people could try recording multiple 1080p videos to see if it works or not. I do know that I had to switch from 720 to 1080 after boot, dunno if that had something to do with it.
[Verizon Samsung Galaxy S III] chowner:
2 recordings and then the screen went psychedelic
[Verizon Samsung Galaxy S III] mastamoon:
Stay with 720p videos right now and wait till its cleaned up some more. With 720p videos, camera should be working good for most.
[Verizon Samsung Galaxy S III] Defragger51:
Has the TXT message issue been fix in the 3/24 nightly ? After 40 hours of run time on 3/21 I could not respond to a txt get the txt did not send message. Went back to 3/17 and had the same thing happen .I originally ran 3/17 for several days with out issues until I went to 3/21.
[Verizon Samsung Galaxy S III] mastamoon:
You may have to follow the steps spelled out in this post in my thread... http://xdaforums.com/showthread.php?p=51312229

Please check it out.
[Verizon Samsung Galaxy S III] SDQB17:
Just flashed 3/24, Video problem is still there. First recording is fine,when you touch to stop recording the bottom of the screen pixelates green and red. When you start a second recording the whole screen does it....same as before. I can post a video if needed as it records the messed up screen.
[Verizon Samsung Galaxy S III] mastamoon:
Switch to 720p, it will get you by.
[Verizon Samsung Galaxy S III] SDQB17:
How do you do that? I have rebooted 2 x and cannot open camera even after a reboot. It FC's immediately. Never had that before..

Also when the camera FC's it also says sd card has been removed.
[Verizon Samsung Galaxy S III] mastamoon:
Hmm.. Try wiping camera data.

After your back in the camera, go into camera setting and change it from 1080p to 720p.

---------- Post added at 09:18 PM ---------- Previous post was at 09:13 PM ----------

From [MENTION=4193338]CyanogenMod[/MENTION] Twitter tonight:

Also... PSA: Galaxy S III users experiencing camera crash or "Cannot connect to camera" - Fix in the works. Affects current CM Installer builds only
[Verizon Samsung Galaxy S III] SDQB17:
Thanks for the info and link, I am patient I can wait for a fix. I checked video settings and I actually do not have an option for 1080. It was on 720 already. Like I said though I am patient...or I am a patient...lol I'll ask the DR. that just put the straight jacket on me :)

Edit: Ok weird...All I had was 480 and 720. So I rebooted 2 more times and now I get a menu with 480, 720 and 1080...and it was on 1080. Strange I wonder why it didnt show up the first time.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I love how CM has finally gave some attention to the camera [emoji106]
[Verizon Samsung Galaxy S III] Casper34:
Hesitant.......

I don't know if I should update to 3/24 from 3/1 or not. All this talk about not being able to text is what's stopping me. I don't record much video, so that is not even a factor.

I have started having a small issue with my data. When I type a link in chrome it will open the page, if I click on a link withing that page, it wont load. I have to enable wifi. Then refresh the page, it loads. Click another link, it wont load. Turn off wifi, refresh the page it loads. I have to do this for every click. This is why I want to update, but not having text is holding me back.

Do we know if text is 80% fixed? I use hangout if it matters.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] EatonZ:
If you aren't having problems now, I would hold off a little while longer.

I'm on the latest and I can only send picture messages. Data connection drops in/out and makes phone calls very hard, if not impossible.

There's also some occasional, unbearable lag.

Some of those may be specific to me, but I'd wait for the next stable version.
[Verizon Samsung Galaxy S III] joedajoester:
I'm on the 3-13 build, and if i'm in a weak signal area, my phone cycles through having no signal to having signal. Even in places where i could manage to get data to connect, this new issue makes it a whole lot more difficult. This makes it very hard to actually get any data to connect since it keeps dropping the signal every second. Texts are fine, calls seem fine too. I'm going to switch back to an earlier build(3-03) that didnt give me these issues. Also, are these issues persistent even after you flash another rom? I kinda dont want to odin just in case something goes wrong and i have to go to 4.3. Thanks
[Verizon Samsung Galaxy S III] EatonZ:
The signal in my area is very strong. It never dropped out like this before.

I was on CleanROM for like a year with no problems. I flashed CM around the end of December and updated every few nightlies. Was working well up till mid-Feb where the lag set in, then the MMS issues, and now the connection drops.

I should also note that downgrading to earlier CM versions did not fix the problems. So once something gets broken, it appears to stay broken.:(
[Verizon Samsung Galaxy S III] joedajoester:
I restored from a 3-03 nandroid i had. The problem seems to be gone, thank god :). On the 3-13, my phone on a desk in my basement make the signal keep dropping. Now i can death my phone in my basement, and it still hangs onto the signal for dear life but never drops it lol. If the signal does get too weak, data disconnects but it still has signal, just not data. I guess I just got lucky. Hopefully I wont get the issues if i clean flash the 3-03 build. I wish you and everyone else with the issues the best, and I hope this gets resolved asap.
[Verizon Samsung Galaxy S III] mastamoon:
Anybody having signal issues, would you try flashing this zip and let me know if it helps at all?

http://mastamoon.truelinux.net/other/d2vzwRILlibs.zip

Just flash in recovery, shouldn't need a cache wipe or anything.
[Verizon Samsung Galaxy S III] EatonZ:
I've been waiting for a long time, and not being able to text my friends/family is a little embarrassing. ):

I think I'll be switching to something more stable soon.
[Verizon Samsung Galaxy S III] rhcreed:
Had some big issues, battery and stability mostly. Have been dirty flashing for a while. So I did a full wipe (including format of /system) and a reflash of 3/24 cm11 and 3/24 pagapps.. Running WAY better now.. Very glad I did. Anyone having issues should try.
[Verizon Samsung Galaxy S III] darkknight1812:
Yeah I would stay on your 3/1 build. I nvrestored and reprovisioned this time and it seem to have help a little bit. However, my mobile connection is constantly dropping and flucuating. It will sometimes be stable and everything works (data,msm,sms) but then it will then drop and the screen will flash. I go back to my 3/02 nandroid and it works just fine. When I have time I will upload another logcat.
[Verizon Samsung Galaxy S III] ChuckFarley:
Took the leap and flashed. Initially, I'm now getting a signal where previously I wasn't. I'll update tomorrow after a days use.

Edit: tasker cell near shows me pinging off a gsm tower.

Edit: initially borked text, switched from home to auto back to home in mobile settings, got a flurry of text messages. Seems good now. What an adventure!
[Verizon Samsung Galaxy S III] ChuckFarley:
I'm having text send issues after flashing this. Nothing seems to be working. I flashed back to the mf1.aio, still no joy.

Edit: cleared cache and dalvik, reflashed 3/21, fixed permissions, reboot. I'm able to send text again.
[Verizon Samsung Galaxy S III] esjames:
lol wut?? CM doesnt want to see my face??
[Verizon Samsung Galaxy S III] Argent36:
Did the latest nightly update this morning

phone seemed to work fine for a few hours - randomly rebooted and stayed at the CM loading logo for about 5 minutes

when it finally came back up - dreaded UID inconsistant error and it appears to have hosed my homescreen/loader settings because it's like I fresh wiped it (along with a handful of force closed app messages)

rather frustrating because I'm probably going to have to ODIN back to stock and start over?
[Verizon Samsung Galaxy S III] merdely:
I installed 3/27 last night. So far everything seems to be working well except for the voice search from the home screen (didn't try anywhere else). "OK Google" goes into listen mode for a second and then stops.

To be fair, I don't use that feature TOO often, so it may have been broken for a while.

Anyone else?
[Verizon Samsung Galaxy S III] chowner:
I've had that happen a few times when first launching it. It's typically fine after the first launch though.
[Verizon Samsung Galaxy S III] TokedUp:
Phone calls do not stop music in Apollo when receiving a call. If I can't see the screen turn on I have no way to know I'm receiving a call. Thought this was fixed a few builds ago. Anyone know a fix?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I would appreciate if any of the devs could look into why taking a pic through FFC on the instagram camera causes a freeze/reboot? I've noticed this problem for as long as I did with the 3 consecutive video recordings. If this was fixed and 1080p recording, I think the camera will be perfectly stable.

Here's a log for the reboot: https://www.dropbox.com/s/320c1yea8bcottr/2014-03-27_13.27.zip
[Verizon Samsung Galaxy S III] NegativeOne:
I'm on 03/13 and my phone suddenly got a popup saying "SIM has been inserted", prompting me to reboot.

Right now I can no longer make calls, and my phone number displays as 000-000-4678, IMEI and MEID seem fine. Anyone else? any fixes?

Just to add, oddly enough data (3g/lte both) works fine. Just phone functionality is broken.

Edit: fixed! turns out when I got that message it set my phone into NV mode instead of RUIM/SIM. Switched back to RUIM/SIM and toggled airplane mode (not sure if that's necessary anymore). Instafix
[Verizon Samsung Galaxy S III] :
Face detect is broken in the ffc on aosp. We are issuing commands to apps that will listen that it's not supported. Instagram ignores them. There's nothing I can do about that. This problem has existed since cm 10.1.
[Verizon Samsung Galaxy S III] skrusrnmz:
Since we're talking cameras and we have our resident camera man Nardholio here, just had a problem pausing video recording.

I'm on 3/27, was taking video (in 720p) of my daughter attempting to crawl for the first time. Paused the video to get a better vantage point. Went to unpause and it had stopped recording. Didn't think anything of it and started recording again. Went to review what I got and realized all video recorded before pausing was gone.

Can reproduce this about 90% of the time.

I won't be using pause again soon but I am curious if there's a fix I can do.

Thanks
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm on the latest nightly and noticed opening the history within the dialer results in an immediate force close. Is anyone else seeing that? Everything else (other than SMS) is working great.
[Verizon Samsung Galaxy S III] chowner:
Dialer history and SMS are working fine for me on 0328
[Verizon Samsung Galaxy S III] xs11e:
It works OK for me, I'm on 3/28, I've fixed several issues with nightlies by either re-booting or, if that doesn't work, doing a battery pull*, give it a try and good luck!

Other things to try: re-download the nightly and/or try a clean install.

*I came to Android phones from Blackberries where a battery pull fixed almost everything and was always the very first trouble shooting technique to try, I've found that to be true for Android phones also and can't help wondering why it's not recommended more often?
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks, I already tried all of your suggestions (and then some), but I appreciate it. I guess I'm due for a clean install... I just wanted to make sure that portion of the nightly wasn't broken before I went through the trouble of a clean install. Such is the life of living on the bleeding edge of development!
[Verizon Samsung Galaxy S III] :
Quick question, I have the iBolt car dock, when I plug my S3 into it with the latest nightly...it correctly passes the audio through the jack in the dock...here's the issue though....I don't want it to do that. Where is/Is there an option to toggle this?
[Verizon Samsung Galaxy S III] mikejr83:
Been looking for information regarding host card emulation. I thought CM11 had this in source but I've never been able to get it to work on CM11 (had no problem in CM10 with secure element).

Does anyone have info on this? Is there something that needs to be done where we can help provide some info?

Thanks!
[Verizon Samsung Galaxy S III] SDQB17:
I am on 3/26 and while I have always had very good battery life on all CM roms on this phone, today at work I picked up my phone to make a call and was down to 4 %. That is after about 5 hrs. I usually get all day at work and then plug it in to charge at night, usually only down to around 40% by then. I noticed something unusual here though, the cLock and phone were each using over 40% of the battery. I had not even made a call today on it. Weird. Downloading 3/28 as I type.

Can't imagine why cLock app would use so much battery. Unless it is the weather part of it.

Well I am now on 3/28, Battery no longer shows those 2 apps using 80 some odd percent of the battery. It show now that Bluetooth is using 84%...and it isn't even on. Again...weird.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
3/29 was a non-starter on my phone, just a heads up. Downloaded thrice, wiped dalvik/cache, didn't factory reset though.

I couldn't get into the rotating cyanogenmod load screen. It would just freeze at the Samsung S3 boot logo. Getting into recovery was easy though, just home+volume up+power like usual.

Chime in if 3/29 works for anyone, I don't want to mislead anybody, just giving my experience and I'm just some guy from the internet.
[Verizon Samsung Galaxy S III] skrusrnmz:
+1 to this! I've been looking for this to get added forever. Thwre is a dock setting in TW ROMs but it's missing in CW.

It worked in 10.1.3, audio would come out the phone speaker. This stopped in 10.2 and hasn't worked since.

A few months ago I went on a bender trying to root out what changed. Looking at logcats from when trying to play audio while it was docked, it looked like it was a mistake in 10.1.3 that got "fixed" in future builds. I'd have to go back to my notes.

My "fix" has been to plug the power straight into the phone and manually launch CarHome Ultra.
[Verizon Samsung Galaxy S III] XdrummerXboy:
SAME HERE, NO GO ON 3/29 NIGHTLY EVERYONE!

sorry for all caps, I figure I'd try to grab peoples' attention :p
[Verizon Samsung Galaxy S III] Stealth111:
3/29 Worked just fine for me! I did, however, do a clean install and not a dirty flash over previous build. Using ART runtime as usual. The main issue I STILL have is the "No APN specified for this device" error that populates my screen when I am connected to my network extender and trying to send MMS or setup my VVM.

Sent using Tapatalk
[Verizon Samsung Galaxy S III] RedRumy3:
I updated to 3/29 last night and didn't have any problems. Everything is running great. I don't use ART though never tried it.
[Verizon Samsung Galaxy S III] xs11e:
3/29 dirty flashed, works fine for me. Not using ART.
[Verizon Samsung Galaxy S III] harry_seaward:
What was the latest stable nightly before all of this APN stuff?
[Verizon Samsung Galaxy S III] darkknight1812:
03/03 is the last nightly that seems to work fine for apn issues/sms/mms/data/etc....if you want camera fixes, I suggest flashing the latest ktoonez kernel since the camera fixes are kernel related. Every nightly past 03/03 for me has been a disaster because the mobile radio connection constantly drops every two to three seconds. However, I am able to boot them unlike some others here. I just can not use the latest nightly because it I can not use my phone without a solid connection to Verizon.
[Verizon Samsung Galaxy S III] harry_seaward:
Do you happen to have a copy of that nightly?
[Verizon Samsung Galaxy S III] Stealth111:
Why Certainly! :)

https://mega.co.nz/#!cpQ3SDpb!RAZIvhCwI83uLPKdie3BKDl7-X1FNR6xCm0gzkctpVk

Enjoy.
[Verizon Samsung Galaxy S III] esjames:
Just noticed the 3/29 build got pulled, anyone know why? I am currently on the 3/29 build and all seems to be fine.
[Verizon Samsung Galaxy S III] jhanford:
I had issues with GPS. Ran GPS Test and had 0 In View. Flashed back a day and 18 In View.
[Verizon Samsung Galaxy S III] mastamoon:
Toggle gps off the on again next time.
[Verizon Samsung Galaxy S III] althornin:
Yeah GPS works fine for me on the 3/29 build. The GPS problem you mention happens often on CM11 on a upgrade flash. Just reboot again and all is well. Though I didn't have to do that this time
[Verizon Samsung Galaxy S III] jhanford:
Hmm... did the toggle and the reboot (twice!) and couldn't get it to catch. I might try flashing again and see, but if the 3/29 has been pulled, there's probably a good (other) reason for it.
[Verizon Samsung Galaxy S III] mastamoon:
It was pulled due to nothing about gps.
[Verizon Samsung Galaxy S III] jhanford:
I agree. Hence my "there's probably a good (other) reason for it" comment. Do you happen to know the reason? I still have the zip, but might just wait until tomorrow's release now.
[Verizon Samsung Galaxy S III] mastamoon:
Some phones were having an issue with a new touchscreen / panel driver. Hit or miss.
[Verizon Samsung Galaxy S III] Mystikalrush:
I noticed 29 is gone. I've been dirty flashing every nightly and on 29 at the moment, no issues at all. I did a lot of video recording and picture taking as well, no issues.