yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Div033:
The attitude here toward the CM devs is incorrigible.

How about you spend hours trying to fix a problem you didn't create only to be yelled at by the very community you're trying to serve?

Reality is that this stuff is HARD. It would take years of research and practice to get on the level these guys are at, so try and have a little bit of patience when a volunteer developer doesn't immediately respond.

I think many people are confusing their vented frustration as elitist attitude. They're trying and they want the people who are complaining to give them logs so they can fix it. That's it.

[MENTION=2044079]Nardholio[/MENTION] (if you ever come back) I just experienced some camera issues so I'm going to try and take a logcat/last kmsg later in the day and I'll post it here and on the official issue tracker.
[Verizon Samsung Galaxy S III] Naddict:
Thread cleaned...honor the wishes of the OP and provide log cats. Do not grumble if things do not get fixed...you are here to learn. XDA is not a support site, so, either try the stuff, learn how to fix it yourself and/or provide said logcats to help in getting things fixed, or get out.

Another thing, there are about a hundred ways to be nice to each other too...so some of the trash/disrespectful-tone posts have also been cleaned.

Get back to development in here, final warning.
[Verizon Samsung Galaxy S III] Div033:
Alright here is my bug report and related logs. I can reproduce this 100%.

I'm running stock kernel on the 03/13 nightly build.

This was 1080p video recording.

1. Open camera, take a picture.

2. Switch to camcorder, record a video and stop.

3. Now the camera preview appears garbled, with major artifacting appearing near the bottom of the screen.

4. Take video, colors are whack.

5. Stop video.

7. Take another video, colors still whack.

8. Switch back to camera, artifacting remains.

9. Take picture, camera never shutters.

10. Try to take another picture.

11. Shortly after, camera crashes.

This is where I stopped the logcat.

After this, the phone will shortly reboot. I cannot consistently get the reboot to occur, but my guess is that since so many things get worked from the camera crash a number of things cause the reboot. Regardless, I have a last kmsg that might shed some light on the matter.

Hope this helps.

Edit: Logs have been attached.

Edit 2: Looks like I won't put these on the official issue tracker seeing as they don't collect reports from nightlies... Guess I'll wait for a M build to do that.
[Verizon Samsung Galaxy S III] skrusrnmz:
With 3/17 nightly, when launching stock camera, was getting Cannot connect to camera error. Cleared data in camera App info section and it seems to be working now.

Just a heads up for flashers.

Edit: Also (and this is huge for me!) the crazy stuff that was going on for some of us while taking videos seems to be gone. Where when you stop taking video the screen goes crazy and it breaks the camera until a reboot or it forces a reboot. I read lowering the setting to 720p fixed it before and it did. But after clearing data earlier and testing video I realized it was at the default of 1080p and was working flawlessly!

So, thanks Nardholio? Thanks whoever fixed it!
[Verizon Samsung Galaxy S III] darkknight1812:
Network Extender Problem

I have narrowed my mobile connection problem down to my network extender. I have a Verizon extender and it has been working fine with the 03/02 build. However, the latest nightlies are causing problems. It does not matter if I dirty flash or clean flash, I still get the same results. When the phone boots, the mobile connection status icon will fluctuate between full signal to no service. Trebuchet will also flash while I am on my home screen. When I unplug my network extender and force my phone to find a tower, the problems go away. The mobile connection is stable and trebuchet is also stable. I am attaching my logcat of when I had my extender on and then unplugged it. If anyone needs further information, please let me know.
[Verizon Samsung Galaxy S III] tv31284:
I posted this on the unofficial thread but I've been having trouble logging on and using certain apps such as Bank of America and Time Warner Cable Sportsnet. I can access the apps just fine but can't log onto them when I'm on LTE. If I'm on Wi-Fi or 3g however it works just fine. This is on the latest nightly. I've included a log of me trying to log on to the Bank of America app on LTE and then Wi-Fi, which hopefully helps. On Touchwiz I don't have this problem. I've tried uninstalling the app and reinstalling, messing around with the APNs, clean flashing, and probably a ton of other things. Love the ROM and this is my only issue with it. I'm open to any suggestions. And if there's anyway i can provide more info I'll gladly do it. Thanks for reading.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I apologize for my rude behavior. My reply came out of frustration of camera issues that seems to be exclusively for me ever since the beginning of JB AOSP for the d2. Every time I've reported the issue I get, I either get ignored and its funny because I can reproduce it without a hitch every single time. I've done multiple Odin flashes, full wipes, and it can't be specific to my device itself since I've been through 2 replacements encountering the same exact thing.

Now onto the actual problem. I'm going to lay it out exactly as you've had with yours:

1. Open Camera, take a video using the FFC and stop the recording

2. Take another one and stop the recording

3. Take the third one and stop the recording

4. As soon as you press stop on the 3rd video the phone will freeze and automatically reboot

Obviously, this is a very frustrating issue if you are someone that records several videos using FFC.

So here's a dropbox link to a full zip of the main log, dmesg, last_kmsg, and modem log using the SysLog app as appointed to use by the OP: https://www.dropbox.com/s/9r49a6iutsc3t2d/2014-03-17_00.03.zip

I'd imagine the only thing that would help is the last_kmsg. But I'm no expert and some help would be greatly appreciated. Again, I apologize for my ignorance and impatient behavior but it would be nice to get a justification about this particular issue that I've experienced for a very, very long time.
[Verizon Samsung Galaxy S III] Div033:
I too have fell victim to that frustration. Not specifically with camera, but with other issues. It's easy to blame the CM devs since they're the ones releasing the builds, but I'll bet the ones to blame would be Google or Samsung for unreleased material. Can't say with certainty though.

It wasn't just you I was targeting with my post so don't feel singled out. There was lots of negativity spreading around but it seems to have been quelled by our local moderator.

Time to try out 3/17.

Edit - Even on 3/17 I can reproduce the issue you listed above. I can also reproduce the 1080p camcorder issues. Hopefully our logs can assist the devs in fixing it.
[Verizon Samsung Galaxy S III] tv31284:
I guess because I usually only do my banking at home on Wi-Fi but I clean flashed the m3 release and had the same problem.
[Verizon Samsung Galaxy S III] SDQB17:
Running 3/16 and I get the same problem once I start a second video recording. The wack colors actually look like the same thing you see when you have a bad video driver on a PC GPU. Or a overheating GPU. IT is all pixelated and predominantly green.

Edit update: Running 3/18 now and video problem mentioned above still persists. 1st video works fine, after that it gets all screwed up, etc...

Update: 3/19 and video is still the same.
[Verizon Samsung Galaxy S III] darkknight1812:
So if anyone is interested, I have more information for my problem. It appears to be switching back and forth from the Network Extender to the tower signal. I am guessing that because the Network Extender is considered "roaming" the phone will give the cell tower signal a higher priority. However, since my cell connection is either non-existent or very weak, this could be the reason for the constant switching.
[Verizon Samsung Galaxy S III] bmeek:
That's too bad. Are you saying that older builds (or a current stock TW ROM) will automatically put your extender at a higher priority?
[Verizon Samsung Galaxy S III] darkknight1812:
Yeah, I am on the 03/02/14 CM11 nightly and I have not had any problems with my extender. However, when I was on CM 10.2 (latest stable) the extender was not considered "roaming". When I moved to CM 11, it it now listed as "roaming" and I have to enable "Data Roaming" to send and receive MMS. The stock TW rom never listed the extender as roaming. I have been going through the changelogs and commits but I have not found anything as of yet. If I can get a hold of some nightlies between 03/02 and 03/15, I can try to find when the problem starts to occur and go from there.
[Verizon Samsung Galaxy S III] tpearsall:
Recover from text issue

I was having the common texting issue where after reboot only one message would go out. From my reading it appears the issue has been fixed, but you needed to go back to TW and then come back to CM11.

I had a recent nandroid backup for CleanROM 8.1 (TW JB4.3) so I restored it , confirmed messaging was OK, wipe/factory reset, format system, davlik and installed the latest nightly CM11 and lastest KK gapps. As soon as it booted and did the initial config I confirmed the mobile network was CDMA/LTE/EvDO

Unfortunately, the messaging issues still exists.

I assume I really should have:

- ODIN back to a stock with MF1

- Root, install recovery

- wipe/factory reset, format system, davlik

- latest nightly CM11 and lastest KK gapps

- Check the mobile network

Is that the correct procedure? I didn't see it documented and was trying to avoid screwing it up a 2nd time. A day back in TW was painful...

Thanks.
[Verizon Samsung Galaxy S III] bmeek:
Fortunately for me I haven't experienced any of these SMS or MMS issues (knock wood).

I've read heresy that it's network-related. There's speculation that regional network changes (or glitches?) are sensitive to differences between the way aosp ROMs handle SMS vs. stock ROMs.

Anyone know the actual scoop?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I'm just wondering, how is ART running for all you guys? I've been on dalvik for a while because of stability purposes. Is it worth switching back? Any problems with it?
[Verizon Samsung Galaxy S III] NegativeOne:
Has anyone else noticed the annoying delay on the home button now? Seems to be due to the "double press" detection capability, but it happens even if you don't use double press.
[Verizon Samsung Galaxy S III] chowner:
Bluetooth was great yesterday, not so much today. I should stay put.

Not complaining I swear, keep up the good work guys.
[Verizon Samsung Galaxy S III] merdely:
Yes. I've seen that for a few days. I thought it was me (or that my home button was going).
[Verizon Samsung Galaxy S III] alershka:
I've been on ART for the past few weeks. No issues other than the first reboot after a flash taking much longer. I switched back to Dalvik this week for a day and my battery life took such a hit, I switched back that night.

Just because of the slow first boot, I only flash weekly now instead of every three days.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Weird I just tried switching to ART and rebooted but it didn't optimize any apps and I checked under dev options and was still at dalvik. Any ideas? I tried twice and I'm on 3/19 nightly
[Verizon Samsung Galaxy S III] Jaegermeiste:
Make sure that you aren't running Xposed. Xposed isn't compatible, so it forces you back to Dalvik. Make sure you are using some ART compatible Gapps like the latest PA too.
[Verizon Samsung Galaxy S III] Hellven:
Make a nandroid backup, then if you do have issues, you can just flash back to what is more stable for you.
[Verizon Samsung Galaxy S III] drake90001:
I don't think dirty flashing ever really help the situations. Does that include using the OTA updater?
[Verizon Samsung Galaxy S III] annoyingduck:
Here:

http://xdaforums.com/showthread.php?t=2457569
[Verizon Samsung Galaxy S III] headcheese:
Don't dirty flash then :duh: how do you expect to upgrade to a new version of android without wiping?

I restored all my user apps+data and text messages with titanium.

Cm11 has been pretty solid for me. Got a few keyboard fc but that's about it. No lte toggle either.
[Verizon Samsung Galaxy S III] LudicrousPeed:
Is that MF1?
[Verizon Samsung Galaxy S III] harry_seaward:
Yep.
[Verizon Samsung Galaxy S III] drake90001:
I've had no issues with CM11 other then the menu key bypassing the lock screen and incognito mode crashes the browser (but I'm using ART so I'm not going to pin the issue on CM). Also, sound search FC's on my randomly but I assume that too may be ART's fault.
[Verizon Samsung Galaxy S III] FroyoBaggins:
Anyone else use Waze with the nightly? I can't shut it down. It stays running in the notification bar, and when I click on shut down from there it fc's, but remains running.
[Verizon Samsung Galaxy S III] rootofalldroid:
Your right I should just back everything up and give it a spin...Thanks
[Verizon Samsung Galaxy S III] dewhashish:
My phone vibrates for all notifications, how can I shut that off so only the apps I want will vibrate?
[Verizon Samsung Galaxy S III] 0331:
For the ones you don't want, go to settings, apps, and turn off notifications for that app? Might not be what your looking for though.

sent from my I535 on CM11 KitKat
[Verizon Samsung Galaxy S III] mbarry55:
I had search FC, as well as the dialer until I switched back to dalvik. Since then no FC at all.
[Verizon Samsung Galaxy S III] 0331:
So is ART just for Dev use?

sent from my I535 on CM11 KitKat
[Verizon Samsung Galaxy S III] drake90001:
Yeah, I assumed so.

Not really. I mean it's pretty stable for the most part, some apps don't like it but I haven't really installed a lot of apps so I have no problem with it.
[Verizon Samsung Galaxy S III] annoyingduck:
No, not at all. Just don't expect support if using it. Some things work better, some worse. It'll take a fair amount of time before it becomes fully user useable...
[Verizon Samsung Galaxy S III] 0331:
I should have searched before asking. Apparently it is experimental and for gaining developer and partner feed back. (News to me, probably not for most of you)

http://source.android.com/devices/tech/dalvik/art.html

sent from my I535 on CM11 KitKat
[Verizon Samsung Galaxy S III] mbarry55:
It's theoretically faster as it pre-compiles your apps(hence the long boot when you switch to ART) instead of in real time when you launch them, as is the case with dalvik. So in theory your apps run quicker, and potentially use less battery but until all apps play nice with it i can live with dalvik and no FCs.
[Verizon Samsung Galaxy S III] fonixmunkee:
I'm noticing a lot of stability with the nightlies...wow.

Bluetooth audio works good, but meta data like artist/track info doesn't get transmitted to my car. Oddly enough, my wireless headset's controls work to skip/pause, though.

Going to keep it as my daily driver for right meow.
[Verizon Samsung Galaxy S III] CKyl22:
You don't have to reflash gapps with every upgrade right? I'm just updating the ROM via the built in updater.
[Verizon Samsung Galaxy S III] LudicrousPeed:
Made sure latest CWM (6.0.4.3) was installed, did a factory reset, flashed the 12/8 nightly, and when it finishes booting, I get a popup saying "com.google.process.location has stopped" as well as the Android Keyboard (AOSP) has stopped. Tried a wipe and reflash. Same thing. Tried a wipe and 12/9, then another wipe and 12/8 again. Same results. I wiped dalvik in recovery after each flash of course.

Stumped. The far bigger issue is the keyboard. I obviously can't even sign in. Any thoughts?
[Verizon Samsung Galaxy S III] NedDasty:
This might be my phone getting old/breaking, but my phone's been randomly turning off/rebooting all the time for the last week's worth of nightlies.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Oh yeah I totally forgot xposed isn't compatible. Looks like I'll stick with dalvik :P

No worries your not alone, I've been experiencing that too. Not sure if its kernel related but switching to a different kernel setup fixed apps from restarting/force closing on me, as well as the random reboots. It still comes occasionally when I play Clash of Clans or something. Not sure of a way to reproduce it but it happens out of nowhere
[Verizon Samsung Galaxy S III] alershka:
I am not sure how you get such great battery life. I work in an area with very poor reception. I have a Tasker script that turns off data when the screen is off. After 10 hours on LTE with Dalvik, I was at 42%. On ART under the same conditions, I'm usually in the mid 60% range. Screen time and android system are the one / two usages for me. On Dalvik, the android system usage was much higher.

Running the 3/13 version of CM 11 for both.
[Verizon Samsung Galaxy S III] rmg88888888:
This is a minor annoyance, but has anyone else noticed that if you receive an sms and you open your phone and it is already in the thread of the person who sent you a message, the notification won't clear until you go back to the main screen with all of the threads.

For example, let's say I send a text to John and put my phone to sleep. John sends a reply, I turn on the screen and I send a reply. If I then hit the home button to go to another app, the notification for the message will still be there until I go to the main screen of the messaging app. This is all on the stock messaging app. Does anyone else have this?
[Verizon Samsung Galaxy S III] DGolom:
I can confirm that this happens for me, too. I don't remember it always being like this. I think it popped up for me about a week ago. I typically flash every nightly that is released.
[Verizon Samsung Galaxy S III] satadru:
Low or muffled call audio?

So I did a full wipe several weeks back.

I've been running d2lte nightlies since then. Everything's been fine up to about a week ago.

Now I'm getting muffled audio when calling. (The person on the other end has trouble hearing me.)

I've tried toggling all the voice call options I can see, but nothing seems to change anything.

I've also tried recording a video from the front camera, assuming that also uses the front mic... and the sound seems fine.

Any ideas on what I should try next?
[Verizon Samsung Galaxy S III] NedDasty:
FYI, I switched to leankernel 9.5.1 and it's cleared up my 95% of my reboot issues.
[Verizon Samsung Galaxy S III] jehelmer:
Looks like the dialer with caller ID is coming in next nightly? :)
[Verizon Samsung Galaxy S III] eaglesfan398:
Not been able to send a text

Has anyone not been able to send a text message. I am on the most recent rom and I did a full flash and wiped everything and I still can't send a text message. Any ideas?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
From what I've read, you have to ODIN back to stock firmware and reflash in order to fix it.
[Verizon Samsung Galaxy S III] mastamoon:
Have to go back to stock, nvrestore, reprovision then go back to CM. So far this is the only fix.
[Verizon Samsung Galaxy S III] smelkus:
I ran into the texting issue yesterday and just restored a CM11 nightly backup from Feb 28 that I still had and texting works fine again for me. MMS and SMS, send and receive. Might at least try that before the go back to stock, etc etc approach. I'm too lazy for that. Don't think there is anything magic about that date, it just happened to be the only other older one I had before Mar 18.
[Verizon Samsung Galaxy S III] eaglesfan398:
It seems like only certain roms have that issue. Or it could be because I have 26k messages on my phone.
[Verizon Samsung Galaxy S III] esjames:
I been rocking the last M-release since i had to odin back, today I decided to move away from the LK3 baseband and flashed the MF1 baseband and ML1 modem and my texting broke like before. I'm gonna install the latest D2 variant nightly and see what happens, hope it doesn't break:eek:
[Verizon Samsung Galaxy S III] jhanford:
I'm currently staying on the 3/13 nightly as that's the only one where sending SMS works for me.

I'd be interested to see if anyone else who has experienced this can confirm that date.
[Verizon Samsung Galaxy S III] darkknight1812:
I am stuck on 3/03 due to network extender issues. I have narrowed the date down though. I have the 3/03 and 3/06 nightlies and when I go to 3/06 my mobile data connection freaks out. If any one has 03/04 and/or 03/05 that would help me pinpoint the time frame. I even tried odin stock flash, and still same issue. Is there an archive of the changelogs?
[Verizon Samsung Galaxy S III] cheekoo:
---------- Post added at 05:45 AM ---------- Previous post was at 05:44 AM ----------

[/COLOR]
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Anybody got force close issues on AOSP keyboard upon boot up of tonight's nightly? (3/21) I had to freeze and download the Google Keyboard from the playstore instead.
[Verizon Samsung Galaxy S III] boricua1213:
I had the same issues when updating via CMUpdater. I had to use ODIN to put on Samsung ROM on it then update it was painful. Now I download via CMUpdater and reboot into Recovery and backup/update. That works for me.
[Verizon Samsung Galaxy S III] PerCompLLC:
The key component here is reprovision... Just my two cents as I am experiencing the SMS bug as well.
[Verizon Samsung Galaxy S III] xyrcncp:
I'm having the SMS issues as well and trying any avenue to fix this. I saw your post mention the Network Extender. What do you mean you're stuck on the 3/3 due to NE issues? I have an NE as well, was this the last nightly that worked for you?
[Verizon Samsung Galaxy S III] rhcreed:
I'm getting terrible battery life after switching to art (3/18 and latest pa gapps) any suggestions? What other useful info can I provide to help?
[Verizon Samsung Galaxy S III] open1your1eyes0:
So what's the current status on the video recording issue? Seems as of 3/21 nightly still not resolved.

Recap:

1. Open Camera app

2. Take a video (few seconds is enough)

3. Stop recording and don't close the camera app yet

4. Just start recording another video and then stop it again after few seconds

5. Distorted image on the camera screen, eventually if you reload it will force close and reboot the phone even.

I confirmed this issue exists on third party camera apps as well.
[Verizon Samsung Galaxy S III] mastamoon:
It's broke, devs know its broke, it's being looked at but no ETAs on a fix.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Great, thanks for the confirmation.

Just wanted to be sure it wasn't marked as resolved yet.
[Verizon Samsung Galaxy S III] mastamoon:
No, far from. We all know the camera is an ongoing fail.
[Verizon Samsung Galaxy S III] open1your1eyes0:
For the record, I tried the same exact nightly build on a T-Mobile Galaxy S3 (non-LTE version) yesterday and it works completely fine there.
[Verizon Samsung Galaxy S III] mastamoon:
So the same d2lte build on a tmo s3 works fine?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Yep. I got it because, as I understand, all Snapdragon-based S3's are now merged into d2lte (even the non-LTE version of T-Mobile's S3).

Camera working completely fine on that one.
[Verizon Samsung Galaxy S III] mastamoon:
We believe that's possibly due to the tmo s3 having newer firmware, as your 4.3 Ota was unlockable. D2vzw isn't that lucky and makes me a sad panda.
[Verizon Samsung Galaxy S III] LudicrousPeed:
Do you know what causes this issue? Makes me want to be careful how often I flash if it just comes up without warning.
[Verizon Samsung Galaxy S III] mastamoon:
Oh camera... Cm updates **** that fixes some devices and breaks others.. Its a game of cat and mouse.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I love the way this is worded ... an ongoing fail lol

---------- Post added at 07:26 PM ---------- Previous post was at 07:17 PM ----------

I'm not on cm but on pacman and just thought I'd add since they also use cm... if I make 3 video recordings in a row using ffc then it will reboot the phone as soon as I hit stop but I don't get any distortions or anything... Just offering some insight