yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] caveritt:
Using 2/21 and my car connects with no problem on Bluetooth and photosphere is working again. Can find no issues at all with it.
[Verizon Samsung Galaxy S III] hoodieNation:
No camera issues to report? I'm itching to get back on an AOSP rom.
[Verizon Samsung Galaxy S III] caveritt:
Spoke too soon. No front facing camera on 2/21. Causes phone to reboot.
[Verizon Samsung Galaxy S III] merdely:
I can confirm. I just tried the front facing camera after seeing your post. The preview works, but as soon as I took a picture, the screen turned black and then it rebooted.

Sent from my Verizon GS3 running CM11
[Verizon Samsung Galaxy S III] hoodieNation:
Same here. I flashed as soon as I post above lol. Should have waited for a reply.
[Verizon Samsung Galaxy S III] brockkk:
My regular camera isn't even working. Locks up after one pic. Anyone else?
[Verizon Samsung Galaxy S III] merdely:
I was able to take multiple pictures from the rear camera from both the Camera App and the lock screen widget.

Sent from my Verizon GS3 running CM11
[Verizon Samsung Galaxy S III] brockkk:
Might just have to do a clean flash then. I've been riding dirty for a while. Lol

---------- Post added at 09:44 AM ---------- Previous post was at 09:43 AM ----------

Nvm. After a reboot it's magically fixed.
[Verizon Samsung Galaxy S III] CCivale:
Yup, same happens to me. I clean flashed the 0221 nightly. Only takes one pic and then freezes. Rebooted and it happened again.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Not sure but it seems like the latest nightlies are battery drainers. 2/18 seemed great but since it drops like a rock for me.
[Verizon Samsung Galaxy S III] rhcreed:
Agreed, very poor battery life suddenly.. Otherwise great!
[Verizon Samsung Galaxy S III] NedDasty:
2/22 nightly here. It took a LONG time for this build to "settle in," and it's still crap compared to others.

I've mostly been having problems with the Phone app hogging battery (it's the vast majority of my CPU usage)--was something like 28 mins of CPU time after phone had been turned on for only 30 mins, and I was down from 100% to 20% battery in that short timespan.

The camera locks up at every picture.

I dirty flashed, but based on the reviews here it might be a good idea to flip back to an earlier build. Might give the 2/23 a shot first whenever it pops up.
[Verizon Samsung Galaxy S III] merdely:
I'm still on 2/21. The only difference between 2/21 and 2/22 is a copyright notice update.

The only thing that isn't working for me on 2/21 is the front facing camera. Battery life, the barcode scanner in MyFitnessPal, Bluetooth are all working well.
[Verizon Samsung Galaxy S III] NegativeOne:
How well does voice+ work for you guys? Anyone using it?

I get all sorts of missed notifications
[Verizon Samsung Galaxy S III] LudicrousPeed:
I get a delayed or missed notification every once in a while. But it is more of an erased notification. My phone buzzes and there is a brief popup in the notification bar but it disappears. I enjoy keeping all my messaging in one app, so it is worth the occasional need to open the Voice app to retrieve the missed text.
[Verizon Samsung Galaxy S III] Uncleheff:
New to this phone. Just got it for straight talk using Verizon 3g. Will this rom work on it?

Devices: Nexus 7 (2012) stock , HTC Rezound unlocked, rooted, S-off, custom rom cm 11 kitkat 4.4, Droid DNA stock, HTC One stock, HTC windows 8x, LG Lucid rooted, Droid x2 rooted custom rom cm 10.1 jellybean 4.1
[Verizon Samsung Galaxy S III] bmeek:
I use Google Voice, and see inconsistent notifications on voice mail... I don't use voice+ (I don't want to train people to use my Google Voice phone #for texting or port my actual mobile number to Google Voice).
[Verizon Samsung Galaxy S III] NegativeOne:
Hmm. I don't have hope that they will ever get this perfect hehe.

Anyone else experiencing trouble with Netflix on these builds? Mine just won't go at all. Either crashes the phone or just gives me a black screen
[Verizon Samsung Galaxy S III] RoboJoe:
FYI, 02/24 nightly doesn't fix the front facing camera. :-/

Edit: By the way, I dirty flashed. There's always a chance that a clean install might work, but I'm not going to go through that at work.

Edit2: And Netflix has audio but a black screen for video.
[Verizon Samsung Galaxy S III] merdely:
I get audio but no video on 2/21.

Sent from my Verizon GS3 running CM11
[Verizon Samsung Galaxy S III] skytbest:
Is it a Verizon branded Galaxy S3? If so, yes it should.
[Verizon Samsung Galaxy S III] WarER4X:
I'm a little sad that I can't use ART anymore since the 2/21 build. I know it's not officially supported by CM, but is has worked so well all this time and was noticeably better for performance. Oh well. Time to switch back to Dalvik for a while. At least installing new nightlies will go quicker.
[Verizon Samsung Galaxy S III] Jaegermeiste:
This ART boot issue may be fixed in the next nightly: http://review.cyanogenmod.org/#/c/60044/
[Verizon Samsung Galaxy S III] Hybridnoob:
Which firmware are you running? Are you running the latest 4.3 with a little locked bootloader? If so, you're stuck unless you can convince Verizon to unlock it.

If your bootloader is unlocked or unlockable, this ROM will work.
[Verizon Samsung Galaxy S III] pcwizkid1994:
So this will not work on it even if it has SS installed and it shows a unlock icon wheb I boot up?
[Verizon Samsung Galaxy S III] Hybridnoob:
This thread should help. In short (from what I've read), safe strap isn't enough to keep your phone from hard bricking when attempting to flash a custom ROM from stock 4.3.

http://xdaforums.com/showthread.php?t=1788313
[Verizon Samsung Galaxy S III] pcwizkid1994:
The reason I asked is bc I flashed another 4.3 Rom and that worked but none of the 4.4.x do
[Verizon Samsung Galaxy S III] NedDasty:
Flashed 2/24. Phone won't boot--gets stuck on Cyanogenmod animation. Can't boot into recovery either. Might have to ODIN back :-\
[Verizon Samsung Galaxy S III] merdely:
Odd. Which recovery were you using? Were you set to use ART?

I'm using CWM Touch (latest) with dalvik. 2/24 installed like all of the others: download, reboot, backup, install, boot, power off, boot, no issues so far.

Edit: Front-facing camera still causing a reboot, though. And Netflix has audio with no video still.
[Verizon Samsung Galaxy S III] NedDasty:
To be fair, I did what I usually do, which was flash it along with a bunch of other stuff that I probably shouldn't: leankernel 9.4, qualcomm dalvik optimations for 4.4, and operation killjoy.

I managed to get back into recovery (my inability was probably due to my totally messed up power button, which constantly goes on/off by itself) and flashed the new CM11 alone. Looks like the boot is finishing up as I write this...and we're up!

Quick edit: taking a picture still freezes camera, requires reboot. Back to 2/18...
[Verizon Samsung Galaxy S III] merdely:
PHEW!

Does the camera problem happen when you don't install the other stuff too? I can take many pictures with the rear-facing camera. I can't even take one with the front-facing camera.
[Verizon Samsung Galaxy S III] NedDasty:
Yeah, it does--I did a lone-flash. The last few nightlies have all had that problem for me: 2/21, 2/22, and 2/24.

2/18 appears to be the best for me, although it's not without problems: switching to video camera introduces a weird jittery-effect that persists and increases as time goes by. Flipping back to regular camera then crashes. So in short: can't really get video, but regular pictures works ok.
[Verizon Samsung Galaxy S III] merdely:
Gotcha.

I took two photos, one after the other, with the rear-facing camera (no problems), switched to video and took one video that looked good. Then I tried to take a second video and my screen (and the video) were all messed up with what kind of looked like reversed colors and jagged lines at the bottom. I tried switching back to photos and I couldn't connect to the camera anymore with the Camera App or A Better Camera. A few minutes later my phone rebooted.
[Verizon Samsung Galaxy S III] Uncleheff:
It's a straight talk branded phone using Verizon towers on straight talk. When I called to activate it said welcome to Verizon wireless.
[Verizon Samsung Galaxy S III] soohyunk83:
Anybody notice their phone do a lot of reboots when using Google maps for an extended period of time? Was driving to Irvine, and my phone reboots every hour or two hours on Google maps. Didn't reboot all day today when not using it. Happened on the past three nightlies.
[Verizon Samsung Galaxy S III] RoboJoe:
02/25 still has the borked FFC, but Netflix appears to work again.

Anyone have a link to the last nightly with a working camera and Bluetooth? (02/18?)

As with last time, this is a dirty flash. There's a chance a clean flash will fix the camera, if someone is feeling adventurous.

Edit: Nevermind, I have it; it was the first lte combined build, so it wasn't in my cmupdater directory. If anyone needs it I'll upload it somewhere and share it.
[Verizon Samsung Galaxy S III] Jaegermeiste:
Infinite Boot issue when using ART is resolved on 2/25/14 nightly.
[Verizon Samsung Galaxy S III] WarER4X:
I have seen this when using navigation. It will sometimes reboot once. I haven't travelled long enough to see if it reboots more than that as I often reach my destination or quit navigation shortly thereafter. I have also seen reboots when I have wifi hotspot turned on. Other than those two situations, I don't really experience reboots, that I have noticed.

-SR-
[Verizon Samsung Galaxy S III] bmeek:
Yes. After deleting data for the camera app, I took a standard photo, then tried switching to the FFC... Boom - the screen immediately went black and the phone rebooted!

FWIW, I've started using the facial recognition unlock feature, and it (with the front-facing camera) continues to work just fine on the 02/25 build.
[Verizon Samsung Galaxy S III] mastamoon:
Stock camera should be working better on the next build.

May break 3rd party apps like snapchat and such though. :-/
[Verizon Samsung Galaxy S III] joedajoester:
Thanks for the confirmation. How's there overall stability of it? I'm running the 2/20 build and it keeps rebooting when charging while powered off over time, battery is okay, but not as great as previously. I'm just dying for a stable lol.
[Verizon Samsung Galaxy S III] rhcreed:
Getting awful battery life, "Google play services" is showing as the culprit.. Any suggestions?
[Verizon Samsung Galaxy S III] skrusrnmz:
I love the new unified build system. I can get tomorrow's nightly about 6 hours earlier. I used to have to wait until the morning to see it. Now it's here by like 9pm.

So with that being said, the camera is still bad on the 2/26 nightly. The front facing camera works now but there are still some major issues and reboots.

Pictures take fine from front and back. Took a video once no problem. Second time when I stopped recording the screen went crazy. It was still showing the video "viewfinder" but the screen went nuts. You can see in the screenshot.

I was able to back out of the camera but when I went back in it rebooted. I repeated to see if I could get a screenshot of the craziness. It took the screenshot and let me back out. I was able to open the gallery but when I tried to open the screenshot it rebooted.

Other than that I'm having a hard time finding flaws with the latest nightlies. I can take pictures at least so that's cool for now.
[Verizon Samsung Galaxy S III] merdely:
Yeah. Awesome benefit, eh?

I tested taking a couple front-facing pictures, switched to rear, took two videos. No issues. In typing this I just tried taking a third video and upon stopping recording, the screen froze and the phone rebooted. :( It's still better and I don't take lots of pictures and hardly any video.

Yeah. It's working really well for me for what I used on a daily basis.
[Verizon Samsung Galaxy S III] Casper34:
With all these camera issues, has anyone tried a 3rd party camera to see what happens? I would like to update, but seeing all these stock camera issues I am hesitant. I use snap camera.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] RoboJoe:
I also use snap camera, and for the 2/26 nightly, FFC still doesn't work. Stock CM camera FFC worked for at least one FFC picture. (I didn't try more than one.)

It's nice to know it's there, and that progress is being made on this front.

I didn't check anything else, because there are no other known issues to check.
[Verizon Samsung Galaxy S III] esjames:
Not sure why everyone is having camera issues, mine has worked fine including FFC. I even played around with some 3rd party apps like paper artist and such and no issues. After toying around with kernels, that's when things got a little wonky like apps stop working and battery performance not meeting expectations. I tried to break my phone on most builds and only had issues with custom kernels, and I determined with my device its not just CM i had these issues, but with TW roms as well.

Just my experience so far. :)
[Verizon Samsung Galaxy S III] Prack:
My front camera didn't work for face unlock but everything else about the camera has been working fine for me. Just flashed 2/26 and it still works etc.
[Verizon Samsung Galaxy S III] rhcreed:
What Kernel should we be using for this? My battery was great on cm10.2, but lately it's been dead by lunchtime.
[Verizon Samsung Galaxy S III] esjames:
I don't use a custom kernel. I just let the CM installer perform its magic!
[Verizon Samsung Galaxy S III] Zacharybinx34:
Any status on changing trebuchet grid size?
[Verizon Samsung Galaxy S III] merdely:
Same here. I use CM's kernel (though I manually install after a CM Updater download so that I can do a nandroid backup first). My battery life has been better than it ever was pre-CM.
[Verizon Samsung Galaxy S III] Defragger51:
I notice a lot of Bluetooth changes in the 2/26 nightly change log, Is Bluetooth still working or has it been broken again. I see a lot of changes for the camera coming in the next nightly, at least they in the change log for tomorrow
[Verizon Samsung Galaxy S III] rudedog830:
Bluetooth has still been a problem for me on the recent integrated builds. I haven't yet seen a recent build where the wakelock issue is absent and where bt auto-connect works reliably. The more recent builds fixed the auto-connect, but seems to have reintroduced the wakelocks, at least for me.
[Verizon Samsung Galaxy S III] merdely:
I haven't had any bluetooth issues over the last few builds (since before the integrated builds). Autoconnect with my car works and there is no wakelock-related battery drain for me.
[Verizon Samsung Galaxy S III] pilotbob3:
AVRCP Bluetooth metadata issue?

My current Bluetooth issue, although this appears for all the CWM 11 devices I have, is that Metadata over AVRCP is spotty. It works with some of my car audio receivers, but with others no track information appears. Skip, pause all works, just no track information. I see in other device threads that this is problematic in general with KitKat. Does anyone have info about this issue?
[Verizon Samsung Galaxy S III] chowner:
Anyone using this with a Chrysler uconnect system?
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I'm still running the 2/13 nightly since it was the first build that fixed the autoconnect and didn't have the wakelock issue for me. The only bt issue I've noticed is when I'm already on a phone call and enter my car, the phone doesn't instantly connect to the car and transfer the audio to the speakers like it used to pre cm11. Can anyone confirm if this is an issue on the latest builds?
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm running 2/27 now and everything seems to work perfectly so far. Camera is much improved (even from 2/26) and being able to pause during video recording is a really nice addition. Bluetooth is still working for me too. Well done, CM team! This will likely be my new DD for a little while.
[Verizon Samsung Galaxy S III] caveritt:
Are 3rd party camera apps working? Does photosphere work?
[Verizon Samsung Galaxy S III] RoboJoe:
Snap Camera FFC still causes a reboot on 2/27; dirty flash. Don't know about photosphere.
[Verizon Samsung Galaxy S III] skrusrnmz:
Flashed 2/27 last night. Tested video. Started recording, hit stop, screen looked like it did in my last post with the screenshot.

It looked like the camera was still working even though the screen looked crazy so I started recording again and then hit stop. Then my screen looked like this.
[Verizon Samsung Galaxy S III] KaLiBLeeK:
Did a clean flash of 2/27 last night. Haven't tested the FFC, but I ran into this same issue with the video recording. Standard camera and HDR Camera+ both worked for me tho, which is a huge improvement over the previous nightlies, so I think I'm going to stick with this version for a while unless the nightly changelogs indicate video recording fixes.
[Verizon Samsung Galaxy S III] gt43aw:
The last couple of builds use the car speaker for Google voice search and text to speech (it looks like you're making a call from the car interface). Previous builds and 10.2 used the phone speaker to do this. I thought that behavior to be better. Anybody else experience this?
[Verizon Samsung Galaxy S III] Jaegermeiste:
Lol I'm trying to
[Verizon Samsung Galaxy S III] Defragger51:
Just read and article on how Tap to Pay is working on updated Kit Kat Roms on Verizon. Does anyone know why Tap to Pay does not work on the CM-11 Kit Kat Rom or what if any custom Kit Kat Roms does Tap to Pay actually work on?
[Verizon Samsung Galaxy S III] xneuromancer:
Build: 2014-02-16

Noticed the following issues thus far:

1. After each boot up, GPS will not lock unless I toggle Location off, and then on.

2. Phone crashed and rebooted while I was 30 minutes into a trip using Google Maps Navigation. Not a great time to have a phone crash :/
[Verizon Samsung Galaxy S III] Defragger51:
A problem that seems to be happening more often now is,When I am on the phone on a call and another call comes in I get a constant loud buzzing, so loud that I have to hang up because I can not hear the other person. Is anyone else having this problem, is there a fix for it ,is it only related to CM Roms ? this is very annoying to have to keep hanging up in mid conversation because someone else is trying to get through.
[Verizon Samsung Galaxy S III] 3thereal:
Same exact problem I've had for a while with GPS. I'm glad I read this though, didn't realize I could fix it by toggling. That works
[Verizon Samsung Galaxy S III] rudedog830:
How's the battery life on the last few nightlies?
[Verizon Samsung Galaxy S III] brockkk:
2/27 has great battery life for me. Camera works awesome every time GPS locks perfect call volume and sound is great and Bluetooth is working very well best it ever has. It even pauses the Bluetooth audio music when I switch over to FM then resumes when I turn it back.
[Verizon Samsung Galaxy S III] hoodieNation:
Haha. :thumbup:
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Is snapchat FFC still distorted?
[Verizon Samsung Galaxy S III] NedDasty:
LTE recent versions and compatibility with common zips

Hi all,

Did a few experiments on the 2/28 version. I didn't test this out with other versions, but my experience with the last few flashes have been consistent with what I did today:

LeanKernel 9.4 breaks video camera (causes weird green-stripey artifacts that progressively get worse with time)

Qualcomm Dalvik 4.4 optimization zip causes infinite bootup.

I've tested this out a few times and gotten consistent results every time.
[Verizon Samsung Galaxy S III] chowner:
common eh?
[Verizon Samsung Galaxy S III] Jdelta9889:
Works great with stock kernel.. Everything works great so far.. Will update as time goes by ( just installed today)
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Anybody? Quantum Rom has this working
[Verizon Samsung Galaxy S III] Casper34:
2-26 ffc rebooted phone. Don't know about anything later. I will update tomorrow morning with the latest.

Update: 3-1 ffc forces reboot. Snap camera.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] hazard666:
Anyone else having bootloop problems with the latest nightly?
[Verizon Samsung Galaxy S III] jasonbtx:
Not yet Hazard. I did clean flash though.
[Verizon Samsung Galaxy S III] bmeek:
Working fine for me. Installed 03/01 via cmupdater from the previous build.
[Verizon Samsung Galaxy S III] joedajoester:
I dont know about you guys, but ever since the 4.3 nightlies a while back, it introduced notification shader lag (not sure of its name). In 4.2, google play music app was fine, then 4.3 nightly the app became unbearably laggy and slow to the point where i cannot use it. It also had lag when tapping the quick settings panel button, the flipping animation was jumpy. Now were at 4.4 nightlies and the lag is there still! The quick settings panel toggle animation lags, flip your phone sideways and the entire shader/dropdown is really laggy. Google play music is so laggy its impossible to use. I was so sick of this lag that i flashed cm10.2/4.3.1 stable. All the lag was gone. All of it. It was so great seeing android back to its full non lag glory. My question is why are the nightlies getting this huge problem, and how can we fix it
[Verizon Samsung Galaxy S III] bmeek:
? So all I got from your post is that you're experiencing lag in Google Play Music and somewhere around the notification pulldown... I see neither of these things.

I assume you didn't dirty-flash from cm11 back to CM10.2.1 to test this, so I would guess you've got something else going on...

Do you experience this in the current cm11 nightly after a clean flash AND after any automatic restoration of apps/data (IOW when your phone isn't otherwise busy)?
[Verizon Samsung Galaxy S III] joedajoester:
I always had this lag issue on every KitKat build I've been on. I always clean flash, so that's not the issue. Even right after a clean flash its still laggy I believe. Have you tried rotating your phone sideways and tried to pull down the shader? I think your missing it lol. I can make a video demonstrating it all of needed. This lag is just really really bugging me. Can you also try play music and see if that's laggy for you?
[Verizon Samsung Galaxy S III] bmeek:
As i said, no such lag for me (landscape notification pulldown or in play music).
[Verizon Samsung Galaxy S III] Hybridnoob:
Same here on 2/27 (haven't had it on any prior CM11 build).
[Verizon Samsung Galaxy S III] joedajoester:
EDIT*

I freshly clean-flashed 2-27, and the lag is STILL THERE! After some more fustration, i found that when my phone is in vibrate mode(which it is 90% of the time) it adds to the lag. Not being in vibrate mode fixes sideways lag, and lag when some notifications are not maximized. Play music is still very laggy, especially when there are songs with album covers. I think its the fault of cm, because it doesnt make sense how there is literally no lag on stable cm10.2, while nightly kitkat has it, and its my phones fault for the lag.

*before ^ happened*

I must be doing something wrong, what build are you running and what modifications? I'm on 2-27 stock kernel, and viper4android audio mod. Same lag on dalvik or art. Also, can you go to settings>interface>notification drawer, and enable it and see if the entire shader lags and it jumpy. It makes mine crazy laggy. Also, thanks for your response
[Verizon Samsung Galaxy S III] bmeek:
"enable it"? The quick access ribbon? Anyway, it's all enabled - landscape or otherwise - no lag.

Running the current 03/01 build with stock kernel mostly (although playing with the 2/26 build of dkp kernel from time to time).
[Verizon Samsung Galaxy S III] Zacharybinx34:
Still wondering about trebuchet grid size and when that's going to be fixed, thanks
[Verizon Samsung Galaxy S III] jasonbtx:
Hey Zachary try Nova Launcher. It's adjustable
[Verizon Samsung Galaxy S III] ecooce:
Running 3/01 and when I switch to PowerSave, then restart, I get bootloops, can anyone confirm?
[Verizon Samsung Galaxy S III] chowner:
PowerSave?