yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Casper34:
Clear the caches. Then try to flash.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] n3wt:
make sure you have newest version, for twrp it's 2.6.3.1 I believe
[Verizon Samsung Galaxy S III] spurnout:
I think I did do that but I'll try again.

Edit: Still not working. I see:

Finding update package...

Opening update package...

Installing update...

set_metadata_recursive: some changes failed

E: error in /external_sd/cm-11-20140199-NIGHTY-d2vzw.zip

(Status 7)

Installation aborted.
[Verizon Samsung Galaxy S III] jsmitty90:
Have you flashed a kit kat ROM before? If not you need the latest version of your choice of recovery
[Verizon Samsung Galaxy S III] spurnout:
I have not flashed one before. I just put CWM on my phone to replace TWRP. I'll install ROM Manager and try that to see if there's a newer version.
[Verizon Samsung Galaxy S III] jsmitty90:
OK keep us updated
[Verizon Samsung Galaxy S III] esjames:
This error is because of not using the latest version of CWM. You need at least v6.0.4.3
[Verizon Samsung Galaxy S III] spurnout:
Ok so there was a newer version and I supposedly flashed it but when I reboot to recovery it still has the older version. Any idea how to fix that? Been searching the web and not finding much.

Edit: Used Goo to go back to TWRP. Hopefully I have a newer version that works.\

Edit 2: Looks like they don't have a version that works with KK yet. Found a zip to flash the version of CWM I need and am going to try that and see if it works.
[Verizon Samsung Galaxy S III] lakingslayer:
No issues with WiFi on 1/19. I'm using the stock kernel.
[Verizon Samsung Galaxy S III] soondolee:
Can't hear anything when phone with someone. ..either through speaker nor norm way....
[Verizon Samsung Galaxy S III] jsmitty90:
http://d-h.st/Gb8 try that
[Verizon Samsung Galaxy S III] spurnout:
Thanks, I actually found the 6.0.0.45 version somewhere to flash as a zip and that worked. I'm just backing up my ROM, which takes forever, and then I suspect I will be able to flash CM. Yay!

Edit: No errors! Booting up now!
[Verizon Samsung Galaxy S III] jsmitty90:
You need atleast 6.0.4.3 cwm to flash kk. 6.0.0.45 won't work
[Verizon Samsung Galaxy S III] spurnout:
Oops, I meant 6.0.4.5! :-x
[Verizon Samsung Galaxy S III] jsmitty90:
Oh then yea you should be good to go
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I finally dove in after yesterday's nightly received positive feedback. Everything is smooth, but my battery seems to be draining fast. Looking at the battery stats it shows my display as being responsible for 60%. My Asus tablet which I'm running cm11 on is attributing 60% of battery usage to the display. I always use auto brightness on both. Are these stats typical with what you all have been seeing?

Along those lines, can anyone explain in detail how the different settings for auto brightness work?
[Verizon Samsung Galaxy S III] merdely:
It *feels* like my battery is draining faster since installing the 20140118 nightly. But, it's subjective and I try not to worry about battery drain until I've used a nightly for a few days (for things to stable out).

I installed 20140120 hoping that some of the camera fixes would fix the barcode scanner, but it didn't. But, that's the only thing I can think of that isn't working well for me.
[Verizon Samsung Galaxy S III] Defragger51:
I installed the 01/20 nightly because of all he d2 fixes and after reading your post, I just used the barcode scanner without any problems.As for battery life ever since they fixed the bluetooth the other day I am getting the Best battery life ever , at least since the unofficial builds . After updating to the 01/19 nightly and bring my phone back up to full charge, Took my phone off the charge yesterday around 12:30 noon, installed the 01/20 nightly almost and hour ago and still have 36% left on the battery. About to put it back on the charge now.
[Verizon Samsung Galaxy S III] foocankill:
If I install a different kernel like bms or lean is it possible that it might break how well bluetooth works right now? I am pretty sure kernels have bluetooth commits in them.
[Verizon Samsung Galaxy S III] Prack:
It depends on the kernel dev but yes it is a possibility. Most devs will post what date/commits are included. I know kt747 has his synced up to 1/18.
[Verizon Samsung Galaxy S III] thefuzz4:
Anyone know when the lock screen wallpaper settings will be back? I saw a post a few pages back that they were committed but I don't see them in the latest nightly. Thanks.
[Verizon Samsung Galaxy S III] ye1cee:
"insufficient storage available"

Up until the latest nightly (0120), I have gotten "insufficient storage available" when trying to install QuickPic, Google Zhuyin keyboard and Amazon Appstore. I have plenty of free space on both the internal (7.83G) and sd card (15G). Does anyone else have the same issue? Is there any workaround suggestions or solutions? I have tried factory wipe but didn't help. Thanks.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Navigate to /data/app-lib/ and delete the folder for that app. Then retry.
[Verizon Samsung Galaxy S III] ye1cee:
Thank you, JonnyTToxic, that solved the issue! :good:
[Verizon Samsung Galaxy S III] foocankill:
Thanks, I think I will build my own kernel using CM's guide, their latest code, and just add the governors and options I want. Good to know about KT's kernel though as I am running the 1-18 build.
[Verizon Samsung Galaxy S III] ryanstfl:
Please include faux sound in your kernel
[Verizon Samsung Galaxy S III] cheekoo:
i had posted some pages back about random reboots. Those were coz of xposed(or some frameworks I installed). As soon as I installed Xposed and some frameworks, it rebooted randomly in a couple of mins, and did that soon. After un-installing xposed, no random reboot since.

Just sharing here, if someone else is facing the same issue.
[Verizon Samsung Galaxy S III] Casper34:
What modules did you install? I have Xposed installed and have not had a reboot.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Yep... Had the same issue for awhile now... Gave up on mentioning stuff like that since it gets covered up by everyone constantly whining about bluetooth in their cars

---------- Post added at 06:29 AM ---------- Previous post was at 06:24 AM ----------

Same here only it seems to crash my phone when I try to do the birthday card thing... At least it did a few nightlies ago

---------- Post added at 06:34 AM ---------- Previous post was at 06:29 AM ----------

Are you using any type of ad blocker?

Yea they use their own version of as many apps as they can... Just sideload it or use PA GApps
[Verizon Samsung Galaxy S III] cheekoo:
I had xad - the ad blocker, youtue adaway n greenify. Without greenify, it was rebooting too.

BTW, what modules do you have installed?
[Verizon Samsung Galaxy S III] esjames:
Has anyone been experiencing force close on downloaded apps, for instance Tapped Out? I even tried a clean wipe (cashe, dalvic, sysem.) with no luck. Had to go back to the 1-18 build.
[Verizon Samsung Galaxy S III] foocankill:
https://www.facebook.com/HaxSync (see the top 12/6 post) They pulled the app from the appstore because of changes to facebook, it won't even work if you get the apk reinstalled via TiBackup, etc.

Here is his latest comment

"HaxSync: Unfortunately, I haven't made any progress on this front yet I will update this page as soon as I do, but in the meantime, constantly posting updates saying nothing has changed isn't helping anyone. I obviously want to see this fixed even more than you guys do.

January 13 at 12:37am "

---------- Post added at 07:55 PM ---------- Previous post was at 07:50 PM ----------

Has anyone had a problem with alarms not going off reliably using the stock clock app? There is just no sound (sometimes), it still shows the alarm going off screen. Running 1/18 nightly. Thanks.

My phone is also on a samsung dock with audio out I just realized..... maybe the audio for the alarm clock app is being routed through usb? Where can I go to disable that?
[Verizon Samsung Galaxy S III] annoyingduck:
[MENTION=339308]foocankill[/MENTION], nice find thank you
[Verizon Samsung Galaxy S III] Mtsprite:
So i was having a look over at cmxlogs to see what commits had been added to today's nightly build, and i was greeted with a bunch of commits that have not been included in any nightly. Now i don't exactly know whats gonna happen, but i think CM is getting ready to either make another snapshot or better yet, a release candidate. Like i said this is just me but you can see the increasingly long list of additions to the next build.

cmxlogs-d2vzw
[Verizon Samsung Galaxy S III] merdely:
I'm thinking that they just didn't have a successful build for us last night.
[Verizon Samsung Galaxy S III] Hellven:
I have been using Advanced Power Menu, All Notifications Expanded, Chrome new tab, Google search API, XBlast Tools, XuiMod, and Youtube AdAway. I have never had a random reboot with these modules installed. The issue I have seen is with floating notifications.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Any advice on how to bring sms messages over to this? I'm going to install it onI my wife's phone, but before when I tried a month or so ago, sms backup + wasn't working with the new kit Kat changes to sms
[Verizon Samsung Galaxy S III] Casper34:
I had one random reboot this morning.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] jager420:
I heard the cyanogen team was working on Samsung drivers to make the signal better? Have they implemented this in their new nightlies? The only thing keeping me away is the signal quality on the. Also what modem should I be on if I want to use this Rom? ATM I am running old and slows stock rooted rom with ML1 modem.

Thanks in advance
[Verizon Samsung Galaxy S III] caveritt:
Since so much has been fixed can anyone report if photo sphere is working now?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Damn there are a sh**load of changes in the upcoming nightly. Kinda getting impatient now... :p
[Verizon Samsung Galaxy S III] bdr9:
It's only because there was no 1/21 nightly.
[Verizon Samsung Galaxy S III] chowner:
What happened to google experience launcher ?
[Verizon Samsung Galaxy S III] cheekoo:
interesting.. thanks for responding. I will try again n put xad again :) cant live with all those ads.
[Verizon Samsung Galaxy S III] Hellven:
Check what gapps you have. I am using PA and it is included. I cannot confirm, but have heard that it may have been removed in one of the gapps packages on the CM website.
[Verizon Samsung Galaxy S III] ecooce:
Camera hasn't worked for me on the last 2 nightlies, anyone else confirm?
[Verizon Samsung Galaxy S III] im_on_fire:
Works fine for me on latest nightly
[Verizon Samsung Galaxy S III] GPS3:
Everything is working fine on 1/22. Including the camera.
[Verizon Samsung Galaxy S III] EatonZ:
Very unstable for me too! I have to reboot to get it to work, but it only works for a little while before it "stops detecting the camera".
[Verizon Samsung Galaxy S III] ecooce:
That's exactly the same as what I'm seeing!
[Verizon Samsung Galaxy S III] EatonZ:
Good to know our cameras aren't the problem.:)

Hopefully the devs fix it soon.
[Verizon Samsung Galaxy S III] merdely:
Camera is working well for me. Though the barcode scanner in MyFitnessPal is still not working.
[Verizon Samsung Galaxy S III] Rev. Voodoo:
1/22 update didn't go so well for me. I had problems with past nightlies around bluetooth and random lockups (seemed to be specifically when screen orientation would change)

1/20 nightly seemed to work a lot better. My bluetooth seemed to connect to devices reliably (my car and pebble watch specifically).

The 1/22 update seemed to introduce bluetooth unreliability again, couldn't get my watch to reconnect without cycling bluetooth. I also had several lockups that required battery pull, and a couple times where actions on the phone would take 30 seconds to actually happen - severe lag.

Reverted back to 1/20 and running smoothly again, just posting for info!
[Verizon Samsung Galaxy S III] Hellven:
So the two things that I see on the 1-22 is that I am also having camera issues, and massive battery drain. It is running hot (109 degrees) and am down to 19 percent left after only 4 hours off charger. Screen is most used but at only 40 min time on. Anyone else notice similar issues?
[Verizon Samsung Galaxy S III] foocankill:
Does anyone else need to turn GPS off and on again to get it to work? It works when you first turn it on, then if you stop using GPS for a while and go back to using it, it wont lock any satellites until you turn location services off and on again.

Also, is it fine to use CM's built in updater (with latest CWM), and not manually clear your caches?
[Verizon Samsung Galaxy S III] Hybridnoob:
I haven't noticed any GPS issues, but haven't tried it today. I very rarely clear caches and almost always upgrade using CM's Updater and the latest CWM recovery.
[Verizon Samsung Galaxy S III] jasoncallahan:
I'm on the 1/22. No issues so far with camera, gps or BT.

I still can't seem to get OTG to work though - I saw a post where it was reported to be included, but it is not working for me. Anyone else have luck with it? If so, what helper app if any are you using?
[Verizon Samsung Galaxy S III] foocankill:
Get wakelock detector or better battery stats and see if nlpprovider or any other gps things are keeping your phone awake. 1-22 build made my gps finicky and it'll keep the phone awake forever trying to find a gps signal for google location related services.

---------- Post added at 12:41 AM ---------- Previous post was at 12:39 AM ----------

I'm going back to 1-20 build fyi
[Verizon Samsung Galaxy S III] merdely:
Me too.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I heard that Better Battery Stats doesn't work on KitKat roms. How do you guys use it?
[Verizon Samsung Galaxy S III] mapatton82:
There is an Xposed module that enables battery stats on Kit Kat roms.

Sent from my Galaxy S3 running Official CM 11!
[Verizon Samsung Galaxy S III] bmeek:
I confirm that the proper Bluetooth connection behavior present on the 1/19 and 1/20 builds appeared to break again on the 1/22.

I quickly flashed back to the 1/20 build and it ran great all day.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
1. Camera probably won't be fixed anytime soon. I've been reporting camera problems since day one and it just for some reason can't be stable on AOSP.

2. Get better battery stats and its most likely "msm_camera". I usually get that wakelock and makes my phone very hot and drains fast. A reboot fixed it
[Verizon Samsung Galaxy S III] im_on_fire:
I believe it's because the Samsung camera drivers aren't openly available
[Verizon Samsung Galaxy S III] BrUhNiGGs:
On today's nightly I see there is a kernel update " Prima 3.2.7.27". Is that anything major? I'm worrying if I flash KT kernel it'll mess everything up
[Verizon Samsung Galaxy S III] mastamoon:
Prima is for the Apex... doesnt affect d2. We share a kernel.
[Verizon Samsung Galaxy S III] esjames:
Has anyone else have issues with the 1-23 build loading? Something went wrong for me updating from 1-18 build and i cannot get past the boot animation. When i tried to get into my recovery manager, it gets blocked by the update screen. Any thing i can do to get past this?
[Verizon Samsung Galaxy S III] chowner:
What do you mean? How are you trying to get into recovery?
[Verizon Samsung Galaxy S III] PSUFINN:
Yes I had that same problem a few times when using the cmupdater. Each time I had to use Odin back to stock. I think the path gets corrupted and something with the pip thing. You have to flash either the 16 or 32gb version
[Verizon Samsung Galaxy S III] esjames:
The usual method of pressing the vol-up+home+power buttons. Had to do a batter pull to do this. But however I worked a way around all this. I just odin'd back to stock firmware, used beanstown casual auto root+recovery. And!!!!!! the most important part, nandroid from my ext card and all is back to normal.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
What camera problem? My camera has been nearly flawless on all builds... The only issues I've run into are app specific such as snapchat
[Verizon Samsung Galaxy S III] xgujuplaya:
In on the latest nightly have any of you using Facebook messenger noticed that stickers are no longer transparent anymore they have a white box around them
[Verizon Samsung Galaxy S III] funkpod:
What do you guys think, 1/20 nightly pretty stable all around?
[Verizon Samsung Galaxy S III] merdely:
I'm happy with 1/20. The only thing that doesn't work for me is MyFitnessPal's barcode scanner. I think the battery is draining a bit faster than previous nightlies. But it's still pretty good.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
The "cannot connect to camera" issue comes occasionally and I have to reboot to get working camera. The front camera on snapchat has a condensed look for some reason and freezes up when trying to record
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
But that's not cm... That's snapchat... If it was cm then it would be the same way in the actual camera app... Snapchat is the one who needs to fix their app
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Regardless of that, any version of aosp whether it is pure, or cm has issues with rebooting/freezing on snapchat recording, at least from my experience. Works just fine if on touchwiz though.

I know if its such a problem I can go back to touchwiz, but too bad its terrible in terms of its interface.

I would still rather have some sort of fix for the connection to camera issue by now...
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
But again that's snap chats fault for not properly building their app... These things aren't happening with the default camera app...

Your basically blaming cm for not fixing snap chats problems... It's like blaming Eminem because you downloaded a low quality version of his latest cd or blaming the butcher because your mom burnt your steak
[Verizon Samsung Galaxy S III] ecooce:
My camera just went out, same error, "can't connect to camera". I'm on 1/23
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Correction. I get the same exact issue when I use the main camera app. When taking the 3rd video using the FFC It freezes/reboots right when I end the recording. Therefore it's not a snapchat problem.
[Verizon Samsung Galaxy S III] funkpod:
I am on a separate build of cm11, and I get that camera issue sometimes. I feel like it happens when I initialize the camera and rotate it at the same time. You guys?
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I just did what you described... No issue
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Weird. Been experiencing it since jellybean. But as you can see the camera isn't "flawless" since other people are getting the connection issue like me.

If you're not, good for you. Consider yourself lucky.

---------- Post added at 08:16 PM ---------- Previous post was at 08:09 PM ----------

I also would like to input, on betterbatterystats do you have a wakelock labeled "msm_camera" under "kernel wakelocks" that drains your battery? I found that whenever I get the "can't connect to camera" issue and the wakelock is there until I reboot.
[Verizon Samsung Galaxy S III] xs11e:
01/20 seems to be the last daily with working Bluetooth. Go back to that one and wait until a later one resolves the issues again.
[Verizon Samsung Galaxy S III] xs11e:
That should have been 01/20. You should have read what I meant instead of what I wrote! <G>

NOTE: I edited the post to fix it.

More importantly, BT didn't work until around 01/18 or so, it only worked for two or three nightlys and then it's broken again. You recall there was no nightly for 01/21 and 01/22 broke BT again.
[Verizon Samsung Galaxy S III] funkpod:
Hey, anybody's YouTube doesn't work while on lte? Mine just spins and spins. Works while on Wi-Fi not on lte, though. Doesn't work while on chrome, either.
[Verizon Samsung Galaxy S III] thorrules:
I am on official aokp, and I have this issue too. As a work around I start the video on wifi and then switch over to LTE (my LTE is faster than wifi and it is unlimited). But it is frustrating when I don't have wifi...

Sent from my Galaxy S3 (d2vzw) running Kitkat
[Verizon Samsung Galaxy S III] gt43aw:
I noticed that Google sound search was constantly trying to synch and never did. So I disabled it. Battery seems better now. I use art and the latest gapps on the cyanogen wiki.
[Verizon Samsung Galaxy S III] Audiorat1:
My speakerphone worked only once. I have to reboot for it to work again. None on the nightly fixed it. I'm on the 1/23 one now.
[Verizon Samsung Galaxy S III] funkpod:
WEIRD. this is a stupid issue. i use youtube a lot when not on wifi. any ideas?
[Verizon Samsung Galaxy S III] jkpair:
Yeah the youtube issue was the deal breaker. Other than that I love the rom. Just reverted back to CM10.2.
[Verizon Samsung Galaxy S III] funkpod:
i don't get why it would work fine and then stop working. and then when i go back to a previous rom where it worked, it doesn't work anymore.
[Verizon Samsung Galaxy S III] chowner:
clear data and reboot. I dunno works fine for me no issues
[Verizon Samsung Galaxy S III] funkpod:
as in clear youtube data? will try that.
[Verizon Samsung Galaxy S III] chowner:
yea
[Verizon Samsung Galaxy S III] funkpod:
thanks. here's what's frustrating. is that i wanted to test youtube before i cleared data, and it was working again! now, it was 3g, not lte. so, then i cleared data, and restarted.

right now, on lte, it doesn't work again. This is after the data was cleared.

so... does it work on 3g and not lte? or just randomly works and doesn't work? weird.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Are you using an ad blocker?
[Verizon Samsung Galaxy S III] funkpod:
No I am not, unfortunately.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I don't know then... That's the only time I've had any problems with YouTube
[Verizon Samsung Galaxy S III] Audiorat1:
I found some other post that if I toggle the volume down and up right away, it seems to work.
[Verizon Samsung Galaxy S III] xs11e:
BT still won't reconnect!

01/24 nightly, BT still FUBAR, back to 01/20 nightly!
[Verizon Samsung Galaxy S III] merdely:
There haven't been any recent BT-related commits (http://www.cmxlog.com/11/d2vzw/), so I wouldn't expect it to work until there are. The 01/20 nightly has been working well for me.
[Verizon Samsung Galaxy S III] rudedog830:
BT is working well for me on 1-20. However, I get many bluesleep wakelocks that drain my battery when BT is on. As a result, my phone never goes into deep sleep. Don't know if that is a rom issue or not.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I'm also having the same problem with YouTube. Works fine on wifi but just spins circles on Lte. I'm on the 1/18 nightly
[Verizon Samsung Galaxy S III] foocankill:
Is there any way to get the cLock lock screen widget to show weather on the 1-20 nightly? It works on newer builds but i want to stay on 1-20.

Edit: I just turned on custom widgets and it started showing the weather.
[Verizon Samsung Galaxy S III] kynibe:
I was having the same problem when ahead uninstalled the app and installed the one from the play store and that did the trick for me. Hope that can work for you.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I tried to uninstall it, but since it is a google app it only lets me uninstall the updates. Did you use titanium backup to force the uninstall?
[Verizon Samsung Galaxy S III] kynibe:
When I flash my gapp it didn't have the YouTube apk so I always installed it from the play store I guess that's why I was able to do a complete uninstall and not only the update. Sorry that it was of no help.
[Verizon Samsung Galaxy S III] funkpod:
That may have worked...I will see if it continues to work. I forgot test it before I uninstalled it.