yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] joedajoester:
The google camera app still doesn't have the option to save to external SD card. Also it would be nice to have HDR, which has never been included/working correctly. Is there any replica of the aosp camera that can do all this? Thanks

Also, is there a way to set the transition animation scale to .75?
[Verizon Samsung Galaxy S III] Schaweet:
I think you are out of luck on the animation scale but here you go for the camera.

[APP] AOSP Camera mod for 4.3/4.4

http://xdaforums.com/showthread.php?t=2408345

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] joedajoester:
Thanks for the link. The HDR takes its time and if you slightly move, your picture is ruined. Nut sure what to do now, since it seems HDR is broke on cm
[Verizon Samsung Galaxy S III] lexluthor:
I see that I currently have the MF1 baseband with my CM11 installation. Can I flash the ML1 modem found here or will that cause issues (or worse)?

http://xdaforums.com/showthread.php?t=1788313

Anyone done that?
[Verizon Samsung Galaxy S III] Prack:
Yes I've uninstalled/reinstalled many times. I tried restoring a titanium backup of it, nothing works. For whatever reason the version of the rom that the app runs on is the one with the broken camera (camera is just black) The nightly after they fixed the camera the app stopped running.
[Verizon Samsung Galaxy S III] Hybridnoob:
From the linked post, "You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick." So... no :) I haven't tried updating the ML1 baseband yet, but don't have any issues with MF!.
[Verizon Samsung Galaxy S III] lexluthor:
I was asking specifically about flashing the ML1 modem only. I guess can't flash that either?
[Verizon Samsung Galaxy S III] Hybridnoob:
I edited my post just before you responded. You should be able to update the baseband without any issues. Just also download the MF1 firmware to flash if you aren't happy with the new baseband.
[Verizon Samsung Galaxy S III] Blaiser47:
Modem is fine, just nothing else. Follow invisibleks instructions in the firmware op.
[Verizon Samsung Galaxy S III] joedajoester:
What benefit is there from MF1 over ML1 modem?
[Verizon Samsung Galaxy S III] lexluthor:
Ok, I'm on the ML1 modem with CM11. I couldn't easily find the MF1 modem alone (I found an MF1 firmware file that was around the same size), so hopefully I won't want to go back to MF1.
[Verizon Samsung Galaxy S III] rgraville:
I just updated my phone from CM 10.2 to CM 11 via the "About Phone" > "CyanogenMod Updates"

I was on cm-10.2-20131114-NIGHTLY

I upgraded to cm-11-20131230-NIGHTLY

Before upgrading, I checked my firmware. Baseband version was I535VRBMF1 so no change was necessary.

I created a nandroid backup, and once complete proceeded with the update.

Update appeared to go fine. I don't really care for the new launcher so much but that is beside the point.

I played around with the phone a bit, and noticed that I did not have WiFi. I checked, and WiFi was turned on, but it said my SSID was "not in range." I turned WiFi off and back on, no joy. Rebooted the phone again, no joy. I then ran the app "WiFi Analyzer," which btw is a pretty awesome app for checking nearby access points, and it could not see any access points nearby.

I then checked the "About Phone" information to review the firmware version again, just to double check, and the Baseband version said "Unknown" as the version number. I found that odd. In my experience flashing a ROM does not touch the modem or firmware, so the fact that it said Unknown took me back a little.

I went ahead and re-flashed the MF1 firmware. Once complete the About Phone > Baseband Version showed the correct information, but WiFi was still not functioning.

At this point I made a new nandroid backup, and then restored the CM 10.2 backup i created earlier. Once 10.2 came back up, WiFi works fine, and the Baseband version still shows the correct information.

I have both ROMs as nandroids. I can restore between them and create whatever logs you believe you might need, as long as you can give me direction on how and when to create the syslog files. Let me know what you want me to do.
[Verizon Samsung Galaxy S III] lexluthor:
I think a couple of days ago there was a post from someone who fixed wifi by deleting a specific folder and then rebooting. See if you can find that post.
[Verizon Samsung Galaxy S III] Hybridnoob:
I had WiFI problems on the 12/30 CM11 Nightly. I restored my 12/29 nandroid and WiFi now works as expected. Maybe try restoring your CM11 nandroid, then download 12/29, wipe system (not data), install 12/29 and see if WiFi works for you.
[Verizon Samsung Galaxy S III] titanshadow:
Nevermind. Derp
[Verizon Samsung Galaxy S III] joedajoester:
Anyone experiencing camera issues on the 12-30 build? In snapchat, the front camera is all squished looking, and in hangouts the front camera is upside down.
[Verizon Samsung Galaxy S III] bdr9:
That was me. I fixed WiFi by following the instructions here: http://forum.cyanogenmod.com/topic/83591-wifi-not-turning-on-after-upgrade-to-cm11/#entry428747

This is a known issue that many people are having. Hopefully it will be fixed soon but we don't know.
[Verizon Samsung Galaxy S III] rgraville:
Cool! So i restored the 12/30 nightly, WiFi failed again as expected. Updated to 12/31, wifi still down. I followed the instructions in the link you shared, and BAM! Wifi works. Thank you so much!

FYI, here are the steps I used from the link:

Download SQLite Debugger. Open the app, then open Setting Storage, then setttings.db, then Global, then look for wifi_display_on (was ID 1169 for me) and edit the value, change it from 1 to 0. Reboot and wifi worked again.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Constant random freezes and reboots on 12/31... Even had it boot up and tell me that encryption failed and that I had to factory reset my phone... I've never encrypted my phone and never tried to either... It's even rebooted while I'm in recovery trying to flash a file or wipe cache
[Verizon Samsung Galaxy S III] titanshadow:
Alright guys, I've got a huge problem. I did a nandroid backup of my phone and then restored it to stock so I could loan it to my sister. She knows the stock OS pretty well and we couldn't get bluetooth to work with her car. Anyway, while she had it she said OK to the update to 4.3 from Verizon and now I'm stuck with Stock 4.3 and I managed to get the device rooted (thank god) but for the life of me I can't unlock the bootloader so I can get CWM on it and restore my backup.

Any ideas? I could really use some help here. I've been searching all day and night and have only found one entry by one person who said they managed to flash back to 4.2 but never says if he just wanted 4.2 of it he could get the bootloader unlocked from there. I'm downloading the files to try it now since the phone is bricked nicely after trying to get it working myself.

Any help would be appreciated.
[Verizon Samsung Galaxy S III] mastamoon:
You're stuck dude. :(
[Verizon Samsung Galaxy S III] titanshadow:
Any thoughts on at least how to get the tar.md5 file for 4.3 so I can get it going again?
[Verizon Samsung Galaxy S III] mastamoon:
I haven't seen one yet. Probably easiest to play dumb with vzw and try to get a new phone.
[Verizon Samsung Galaxy S III] Hybridnoob:
http://xdaforums.com/showthread.php?p=48922590

And

http://xdaforums.com/showthread.php?p=48859410
[Verizon Samsung Galaxy S III] mastamoon:
Nice man. Thanks! Last I looked there was no tar or system dumps yet.
[Verizon Samsung Galaxy S III] titanshadow:
Thanks man, seriously saved my a$$! If this doesn't get fixed before my contract is up, I'll be buying a new phone that I can put CM on properly. :)
[Verizon Samsung Galaxy S III] lexluthor:
Anyone seeing the same thing? Wonder what's causing it.
[Verizon Samsung Galaxy S III] cehrl7:
I have been running 12/27 nightly. No problems until this morning. The phone does not lock. The power button does not work. I have pulled battery. It only reboots automatically. I tried getting in to recovery.. but can't. Any ideas??
[Verizon Samsung Galaxy S III] lexluthor:
That almost sounds like you have a broken power button.
[Verizon Samsung Galaxy S III] lexluthor:
Think I might have found a bug.

I have a saved contact number to check my voicemail. It looks like 2125555555,1,*,1234#

The sting works to automatically get me into my voicemail. But, once the string is done dialing, I am unable to make any extra selections on my keypad.

If I manually dial the string (leaving out the commas when I do it manually), I can still enter digits after the #.

Can anyone confirm?

If it is a bug, how do I get a CM11 developer's attention? I did post this in their forums too, but they are pretty slow forums.
[Verizon Samsung Galaxy S III] zacdroidfan:
I'm from another device Galaxy W, using CM11 unofficial build ROM, that Force Close occur after I took a video using Instagram or Stock Camera, maybe it's because Instagram doesn't support 4.4.2, yet:)
[Verizon Samsung Galaxy S III] dvaderx:
Hangouts camera is fixed on 1/1/2014
[Verizon Samsung Galaxy S III] cehrl7:
Power button not working. Now I can't get into recovery. Phone is not locking. I have pulled battery. Any suggestions?? I have never had a phone do this!!
[Verizon Samsung Galaxy S III] Bamdroid:
If your you're using CWM recovery, you can try downloading ROM Manager from the play store. It has an option to boot you into recovery. Maybe try a full wipe and flash a different build and see if it continues...

*edit* didn't see you already pulled battery..sorry about that.
[Verizon Samsung Galaxy S III] iwearthebelt:
Anyone else lose their IMEI & MEID on 01/01 build? I tried rebooting & a battery pull but no luck. Restored 12/31 backup and they came back.
[Verizon Samsung Galaxy S III] lexluthor:
Still there for me on 1/01
[Verizon Samsung Galaxy S III] iwearthebelt:
Thanks for the input. Tried redownloading and reinstalling with same results. I'll just stay on my 12/31 backup and try again tomorrow.
[Verizon Samsung Galaxy S III] xs11e:
How about Blue Tooth? Any fix so far?
[Verizon Samsung Galaxy S III] cheekoo:
speakerphone volume is fixed too in 1/1 build. in few previous builds, it was way too low. even lower than the earphone. :)
[Verizon Samsung Galaxy S III] e30bimmer89:
Downloading the newest nightly. Will report any bugs when I find them.
[Verizon Samsung Galaxy S III] dvaderx:
I'll check when i can and let you know

---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------

The work around is turn down the volume all the way and then back up and it would work normally. Hope its fixed though
[Verizon Samsung Galaxy S III] anonymity:
Bluetooth Issues Continue

I'm using the 12/31 nightly and am still having the same issues with bluetooth in my car. I know many posts have been made about this issue, I'm just wondering what kind of progress has been or is being made. I had the same problem with another KK ROM so I'm assuming it's specific to KK, not CyanogenMod.

My problem is a little different from what others have reported. I have been able to get it to connect by manually connecting from the phone to the car, rather than the other way around. I have been able to receive calls and can speak and hear just fine while in the call. I can't make calls though or hang up after receiving calls. I have to wait for the connection to kind of die to the phone after the caller disconnects. Then I get a message on my car saying "No response from phone" and it lets it go. The bluetooth connection is still good though. I haven't tried to play media through it.

If it's any help, this happens while connecting to a 2013 VW Jetta GLI with the Fender Audio system (no nav). I'm not sure what version Bluetooth comes equipped on this particular radio. My Google searches haven't turned up much.
[Verizon Samsung Galaxy S III] gt43aw:
Anonymity,

That's the same Bluetooth problems others are reporting. Including the issue with hang ups (though I see that reported less often ). No fix. Just need to sit tight I guess.......
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
is netflix working in recent nightlies?? i am on the 21st or 23rd and it crashes every time . :(
[Verizon Samsung Galaxy S III] Hybridnoob:
It works for me on 1/1
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
thanks sir, ill check it out. ! :good:
[Verizon Samsung Galaxy S III] wpbear:
Does slimport/HDMI work on CM11 yet?
[Verizon Samsung Galaxy S III] lexluthor:
I'm ok switching from cwm to twrp 2.6.3.1, right? The nightly updates will still flash fine via the auto updater?

I see that it's noted in the changelog that tonight's update will have an updated recovery. But the recovery isn't part of the Rom so that's confusing me.
[Verizon Samsung Galaxy S III] SDQB17:
Well, my Rom manager just updated my recovery, CWM to a new one , 6.0.4.5. from 6.0.4.3, perhaps it has to do with that?
[Verizon Samsung Galaxy S III] lexluthor:
I saw there was a cwm update today, but not sure why cm11 would note that as the recovery isn't part of the Rom, right?

Either way, I'm ok switching to twrp? The auto updater will work? Many of you are doing that on twrp, right?
[Verizon Samsung Galaxy S III] bdr9:
I'm also confused by this. The recovery isn't part of the ROM, so why is it updated with the ROM? Can anyone explain this?
[Verizon Samsung Galaxy S III] mastamoon:
Recovery is built with every rom build but isn't included in the rom zip.
[Verizon Samsung Galaxy S III] bdr9:
Thanks for the answer. So if it's not included with the zip then why is it built at all? Where does it end up after it's built? I just don't understand why CM and CWM recovery are built together at all.
[Verizon Samsung Galaxy S III] mastamoon:
Not sure the specifics on why, just know it is and that's why you see it on the change log. The recovery.img ends up in the same output directory as the rom zip and a bunch of other stuff.
[Verizon Samsung Galaxy S III] lexluthor:
Back to my question then. Am I ok with replacing CWM with the latest TWRP and updating via the internal auto updater? I presume many of you are already doing that on TWRP?
[Verizon Samsung Galaxy S III] Bramton1:
So I'm debating if I want to stick with CM11 or jump to the new TW 4.3 ROM (not the OTA). I really love my current rom (12/30 nightly) but the wi-fi issues are driving me insane. When I boot up, I connect (let's call this Hotspot A). When I go to a new location with wi-f (hotspot B), the phone is still showing me hotspot A and its' surrounding hotspots. A reboot or cycle airplane mode fixes it, although sometimes it instead shows hotspot B as too weak of a signal to connect. Another reboot or airplane mode cycle clears that up.

Anyway, I tried the above fix, and wifi_display_on (what is that, btw) is already set to 0.

Suggestions?
[Verizon Samsung Galaxy S III] metalcated:
I go back and forth as long as you at using KK supported versions you should be fine with either CWM or TWRP.
[Verizon Samsung Galaxy S III] Hellven:
Many thanks! I don't why I did not think of that before. Works great again.
[Verizon Samsung Galaxy S III] cammykool:
Did a dirty flash from my own build with no issues.
[Verizon Samsung Galaxy S III] cammykool:
Also does art break root?
[Verizon Samsung Galaxy S III] RayMcGrath:
Yes, it did for me. I had to flash superSU update to regain root. Then, after boot update the SU binaries, turn SU off in its settings then back on, another reboot and VOILA, ROOT! Personally, I dont think that it's worth the extra time and effort. When updating I had to set it back to dalvik before flashing the update.

:good:

Have fun Man!
[Verizon Samsung Galaxy S III] xyrcncp:
Yeah, Goo is not working.

It's been a while since I've flashed a recovery img manually, are these still the correct commands via terminal?

su (press enter)

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (press enter)
[Verizon Samsung Galaxy S III] wpbear:
Nightly 12-8 wont boot. Need to re-flash 12-7.
[Verizon Samsung Galaxy S III] billquinn1:
Booted fine for me. Clean flash though.
[Verizon Samsung Galaxy S III] RayMcGrath:
sorry you're having trouble, mine did. I just wiped cache and dalvik and flashed the update then gapps. everything seems good.

:fingers-crossed:

---------- Post added at 06:55 AM ---------- Previous post was at 06:51 AM ----------

you can use the app flashify, from the play store. I used it when I flash a new recovery with no problem. good luck!

---------- Post added at 07:07 AM ---------- Previous post was at 06:55 AM ----------

Does anyone know why google keyboard is sucking up so much battery? From a fully charged battery (I only used it once for an sms) and it shows 21% of battery use. Under use details: 7m cpu total, keep awake - 7m, wi-fi data recieved - 20.87mb.

I've never had the keyboard show up under battery usage until cm11 official builds??
[Verizon Samsung Galaxy S III] xyrcncp:
Weird. I tried it, it said it flashed, but when I rebooted into recovery TWRP still showed 2.6.3.0 instead of .1
[Verizon Samsung Galaxy S III] Restola:
FYI on some of the earlier builds mute didn't work at all (on a call, speaker, headset, or BT headset). I'm not on cm11 right now but someone might want to check that out.
[Verizon Samsung Galaxy S III] RayMcGrath:
I just checked and mine says 2.3.1. Maybe double check the download? Hmmm.?
[Verizon Samsung Galaxy S III] jhanford:
[ROM][Official][4.4.1] CyanogenMod 11.0 Nightlies for the Verizon Galaxy S3

Just downloading 12/8 now. Does the camera work?

EDIT: Camera works. Going to build my own from source and see if it still does.
[Verizon Samsung Galaxy S III] xyrcncp:
Downloaded the file twice, tried it again, same thing. Tried it again, says I reached the limit of 3 flashes on the free version.

Tried an app called EZ-Recovery, same thing. Reboot into recovery, TWRP still shows 2.6.3.0 :confused:
[Verizon Samsung Galaxy S III] jhanford:
What if you try flashing the latest CWM? Does it still boot TWRP? What if you THEN flash latest TWRP?
[Verizon Samsung Galaxy S III] Wisiwyg:
Just DL Flashify from Play, then use it to flash the .IMG file from the twrp site. Works perfectly.
[Verizon Samsung Galaxy S III] wpbear:
Had to do a clean install to get 12/8 to boot after CM11 worked fine yesterday on 12/7.
[Verizon Samsung Galaxy S III] rhamorsky:
i looked up twrp in these forums and found one that i believe was a nexus forum, however, someone had created a flashable zip which is what i used and it worked great

edit: just tried again using the goo manager that comes with Rom Installer and it worked.
[Verizon Samsung Galaxy S III] rootofalldroid:
So far so good!
[Verizon Samsung Galaxy S III] TokedUp:
Can someone test to see if Auto Retrieve MMS is working on this rom? and what I mean by that is turn of mobile data and see if u get any notifications an MMS has come thru while its off. I cannot receive MMS until I have the Mobile Network on and I dont get a notification to let me know I even have one. Only until I turn on data will the messages show up. On most 4.3 builds this feature worked great and not only did it work, it actually turned data on/off when I would send/receive MMS automatically. I leave my data off most of the time to save battery and lately when turn it on I get all these MMS that never went thru so I dont know when they were sent. Stupid iPhone user friends all send group messages thru MMS and I never get them. Missed a good poker game last night :(
[Verizon Samsung Galaxy S III] xyrcncp:
Tried, see above. I'll try another way, I'm not paying for the app just to flash one file.

edit: finally, got it with EZ Recovery. 3rd download was the charm.
[Verizon Samsung Galaxy S III] echodeluxe:
so, if im updated OTA 4.3 but rooted, can i flash cm 11? or is this gonna brick the device even thought its technically an upgrade?
[Verizon Samsung Galaxy S III] lexluthor:
You'd need an unlocked bootloader and trying to unlock would brick you.
[Verizon Samsung Galaxy S III] dvaderx:
still seems broken
[Verizon Samsung Galaxy S III] hoodieNation:
Yep, that will brick your phone.
[Verizon Samsung Galaxy S III] Schaweet:
Well I took the plunge today and picked up a Moto X Dev Edition. I'll be Odining this baby back to stock and getting some cash back from VZW as soon as it arrives.

Thanks for getting CM11 on this phone so quickly. It's been fun testing it.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Two suggestions gathered from previous posters about 80 pages back in this thread:

Did you try renaming/deleting /data/misc/wifi/wpa_supplicant.conf and then rebooting? It gets regenerated each boot (if it's missing or named to something not wpa_supplicant.conf)

Also, you should try manually going to Settings > Display & lights > Cast Screen and then click the menu button (lower left) and then toggle "Enable wireless display" on, reboot, go back in and toggle it off, then reboot. You should only have to do this once and from that point forward, your WiFi should be working like everyone else's.

That fixed my WiFi issues back a couple weeks ago when they started. You may need to dirty flash whatever nightly you're currently on over it if it doesn't connect to WiFi afterwards, but from that point on, you shouldn't have any issues.
[Verizon Samsung Galaxy S III] joedajoester:
Is chromecast working in the latest builds? Think I'm gonna pick one up in a little
[Verizon Samsung Galaxy S III] Hybridnoob:
1/1 works with Chromecast for me. You'll love it!
[Verizon Samsung Galaxy S III] lexluthor:
Was chromecast not working at some point? I guess I haven't tried it since CM11.
[Verizon Samsung Galaxy S III] joedajoester:
I'm sspencer's old builds, some said it wasn't working I believe. I just can't wait to set it up!
[Verizon Samsung Galaxy S III] lexluthor:
Actually, now that I think about it, I'm pretty sure I did chromcast from Pandora a few days ago and it worked just fine.
[Verizon Samsung Galaxy S III] titanshadow:
I'm stuck on TW 4.3 - and it's ok, I'm finding comparable battery life to what I was getting with CM 12/30 nightly. But as long as you don't do the OTA, you might as well do a nandroid of things right now, keep your recovery the way it is, and then try 4.3 out for a while with TW. If you don't like it, you can always go back.
[Verizon Samsung Galaxy S III] merdely:
Wow. Lots of commits today. Can't wait for tomorrow's update!
[Verizon Samsung Galaxy S III] merdely:
Does anyone use MyFitnessPal with CM11? Ever since one of their updates a month or so ago, the barcode scanner doesn't work anymore. I can't tell if it's due to their changes or CM changes.
[Verizon Samsung Galaxy S III] Stump909:
Where is that located?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
What is the default font being used called?
[Verizon Samsung Galaxy S III] iwearthebelt:
Just did a clean install of today's build and for some reason Google voice search won't initialize. Anyone else experiencing this issue?
[Verizon Samsung Galaxy S III] Stump909:
Same. "Ok Google" does nothing, and voice to text says "Google is unavailable".
[Verizon Samsung Galaxy S III] iwearthebelt:
Thanks, at least I know its not just me. I've tried everything I could to get it to work but no luck. Must be something in last nights update because if I restore my last backup it works fine.
[Verizon Samsung Galaxy S III] dmginc:
Under the lock screen menu in settings.
[Verizon Samsung Galaxy S III] Stump909:
Just flashed this Qualcomm Optimized Dalvik Patch: http://xdaforums.com/showthread.php?t=2546120

Can't say I see a significant performance boost, but the CPU allegedly is used less (aka better battery).
[Verizon Samsung Galaxy S III] AlphaXray:
Just wondering. Did your front camera ever work properly on snapchat on CM11. I have had huge problems with it from day one. Not sure if there's something on my phone that's screwing me up alone, or if its the ROM itself. My issue is that the front camera constantly freezes. Sometimes it stays frozen and I have to leave the app. Sometimes it only freezes for about 2 or 3 seconds at a time.