yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Good news! The bug where 3rd party apps causes a reboot when using the front camera seems to be gone in CM11!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Nice good cars and I ben through that blown clutch.. Were you able to solve your issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Anyone have tap to pay working on CM11 nightlies? I had it working on 10.2 with a modded wallet apk, but if I understand correctly, a play store install should get it working on CM11 without any fuss. I have NFC enabled, wallet appears under tap to pay settings, and wallet tells me tap to pay is a go. When I NFC the phone at the register though I get no response at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Black Adam:
Is there a bug list for the latest nightly releases?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joemommasfat:
I can confirm that tap to pay is not working on the latest CM11 nightly.

I also cannot get photosphere to work with the Banks standard gapps. It will not advance past "align to start". And then my camera app will FC whenever it is opened until I do a "clear data" on it. Does everyone have this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Is there save to SD card in latest nightly?

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Not yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diabolik711:
Installed cm11 12/9 nightly didn't restore my apps found that weird anyone else have that issue?

Sent from a phone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Yes, my apps didn't restore, had to do them manually from My Apps in Play.

Got CM11 working now. Had a problem off the bat with Launcher3 where it wouldn't show my desktop icons or anything, so I switched to Launcher (don't know what the difference is because they look about the same). I am using ART and it works fine so far (if you use TiBu it's not supposed to be playing nice with it right now). It does take 5-10 minutes to compile all your programs on reboot after you select ART.

Other issues:

Sound Search for Google Play crashes frequently, bringing up a dialog box

Can't find rotate 0, 90, 180, 270 options--I depend on these so I hope CM will be adding them back

Missing option to not press Enter after entering lock screen pin, and a few other little tweaks--maybe these are CM add-ons that haven't been added to KitKat yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I assure you this is "temporary". It's always like that when they switch from one version to another, it takes some time to merge all the tweaks back in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mts3:
I'm having issues connecting to wi-fi networks at work. Did a format /system and reflashed latest nightly, and I can at least see the networks. But I get "failed to connect to..." when I try to connect.

I suspect it will get ironed out over the next few days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Has it ever worked for you on any KitKat build? I just jumped over the other day, and it was working via secure element on CM10.2. I'm reading concerning things regarding kitkat's host card emulation (HCE) with regards to the AOSP stack, although I can't decipher enough of it to know whether or not it applies to the S3. Seems the S4 guys have it working just fine on CM11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joemommasfat:
No it never worked for me on kitkat. It used to work for me on 10.2 but that was by modifying my build.prop. As I understand it, modifying the build.prop in 10.2 tricked it into using the hardware secure element. In kitkat, it tries to emulate the secure element with software. The latter has never worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
I'm getting significant battery drain from the new Phone app (over 30% of battery use) even though I haven't made or received any calls, and also from the Sound Search, so I turned off the "always-listen" setting for sound search. OK Google, stop draining my battery. ;) Battery Stats Plus is not working; maybe because of ART runtime setting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diabolik711:
Cm11 12/9 nightly anyone else reporting Netflix issues, video won't play? App loads content then error when load video.

Sent from a phone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] k29er:
I like 11 a lot but very hard on battery. Worse than 4.1.2 stock for me. 4.3 stock was getting two days battery. Kk only made it 8 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
After fiddling around, It didn't really work. Thanks for the suggestion though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Also, reading a few pages back, there was talk about Canadian bootloaders and how downgrading back to a lower version of Android would brick your device. Is this still true?

I'm on 4.2.2 right now CM10.1 and have made a backup. If I do a clean flash of the new CM11 and need to downgrade/restore my CM10.1 for whatever reason, will it work; or will my device be bricked?

Thanks,

Elliott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No. It's about downgrading the bootloader by trying to Odin back to anything prior to 4.3 after flashing the new bootloader. If you're still on the older bootloaders you're just fine, and custom roms don't have to do with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Making and restoring a nandroid won't touch your bootloaders. Only if you flash back to a stock ROM via ODIN will your bootloader be overwritten. So you can revert back and forth from CM10, CM10.1, CM10.2 or CM11 without any issues.

Also just to clarify, both Canadian AND AT&T variant phones will brick if you try rolling back from the latest bootloader released with the 4.3 update that just rolled out from Samsung. If you have manually flashed or did the OTA 4.3 update you are stuck on that bootloader for now. Really there should never be a reason to downgrade your bootloader though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Great. Thanks guys.

Now just to wait for SD card saving in camera :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah I'm holding on the CM11 official nightlies for now. I'm perfectly happy with the state of CM10.2 latest nightly.

Can't you replace CM11 camera by CM10.2 camera though? Just a thought, have not tested myself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Just strip the gallery2.apk from 10.2 and replace it in they system folder on CM11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Also here's Gallery2.apk from latest CM10.2 nightly for d2att, while we're at it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Great thanks guys maybe I'll try that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You will need root explorer or a little more involved file explorer than the stock one to dump it in place. Just so you don't drive yourself nuts trying to get to the system folder.

Also note that flashing a new nightly will over write the gallery2.apk with the new one from the ROM and you will have to repeat the process again.

At one point in time buried in this thread I had a flashable zip to flash the CM10.1 camera after I flashed a CM10.2 nightly. If you can find that file you can just replace the gallery.apk with the one polo just gave you and you can flash it after every nightly update. It would make your life a little easier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
I have installed both the 12/7 and 12/9 nightlies, both clean installs, and am not able to access my extsdcard.

Has anyone else had issues? FYI, it's a SanDisk 64GB Class 10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Works fine for me.

I have noticed some bugs in the latest nightly (12/09).

I have chosen to use Launcher3 as my default launcher, yet, when I add some widgets such as the Vine recording widget, or What'sApp conversation shortcuts, they are added to the Google Experience Launcher, and NOT Launcher3...so I cannot see them unless I switch to the GEL...Major problem IMO...almost enough to warrant going back to CM10.1...:crying:

Elliott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
I have to see if it's a problem with the SD not being recognized at all or if it might be the size that's causing issues..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can anyone confirm if the network mode in latest CM 11 nightlies is causing FC's. This just makes my mobile stuck on the default settings. Things are working perfectly on Quantaum though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Why is it every night cm11 has updates why dont they fix the issues in one release like other roms. Idk I also wonder why there are so many updates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Just tried using Google Goggles with the latest nightly. Doesn't seem to be able to capture images for processing. Not sure if unique to CM11 though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
They're nightlies, so essentially they are beta in my eyes. They release release candidates and stable versions. If you run them you risk bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
lol I know flash at your own risk. But I havent seen a full complete rom as in its not a beta like you say the nightlies are. Or do they? if so where at?

Side note: I see some others talk running kitkat with ART what is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Nightlies are built automatically without any concern to open issues. Changes that are merged are built, and it goes out. Some issues take time to work out, but the nightly will [try] to be built every night regardless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galakanokis:
Nightlies are just builds that are auto-compiled by a bot. If commits get pushed the bot will compile them and kick out a ROM, some are stable and others are for testing. For me anyways nightlies are 99% stable and I have no issues. CM is not feature rich with dpi changer, status bar and navigation bar mods so you don't see big updates in that way.

It is also early for 4.4 and "full" ROM's take a good month or more before they start rolling out. I'm sure AOKP and Slim are just around the corner.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
They don't have a stable version for KitKat yet. Too early. 4.3 stables are on the download page.

As for art, it's a different compiler like dalvick. You'll need to do some research on this via Google and xda.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Thanks everyone.. I just always wonder why every night there were updates. All good information thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Furthermore some nights you might not see an update. This is usually because the bot compiling it threw an error because of a commit or because there were no relevant commits. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
http://wiki.cyanogenmod.org/w/D2att_Info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I'm pretty sure that's because they're updating every phone's ROM at once and its more generalized...could be wrong, though.

I've also noticed that the browser doesn't sync bookmarks anymore...by design or bug? And it crashes trying to open a new incognito tab.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
My sync works fine. Incognito crashes. I don't use the stock browser though. I opened it for the first time just to check these issues.

Everything works as it should in Chrome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Damn, okay, thanks.

I soooooo hate chrome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hey guys. Running CM11 here, when I take a screenshot (power+vol down) the animation is all garbled up. The actual image captured is fine but when u take the screenshot it looks like its smeared or something. Can someone try this. Im on CM11 dec10th nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Yup same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Same for me on every cm11 nightly so far. I haven't flashed 1210 yet but there were no commits that looked to fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cre4per:
Can anyone tell me what wisperpush is. Noticed it popped up in the latest nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://www.cyanogenmod.org/blog/whisperpush-secure-messaging-integration
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cre4per:
Thank you been looking for info on that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You can also read more directly at WhisperSystems blog.

https://whispersystems.org/blog/cyanogen-integration/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
Looks like CM11 doesn't like Sandisk 64GB Class 10 SD cards.

I installed the latest nightly, put a 2 gig card in, it read it just fine, put my 64GB back in, no dice, so I formatted it, still no dice..

Put all the files back on, booted back into recovery and am currently restoring a NANDROID backup from that very same SD Card.

It's definitely not the card that has the issue, and it's not the phone that has an issue. It works just fine in Stock 4.3 and all of the roms I had prior to installing the 4.3 OTA. Just doesn't play well with CM11..

Any other suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tokuzumi:
I wonder if this is a Kit Kat issue, rather than a CM issue? Do the Google Edition S4s handle 64GB cards with no issue? I know these are different phones, but there are so few phones with SD cards these days, that it might give a frame of reference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Play the waiting game and hope it gets fixed. Or fall back to cm10.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
My S3 running the 12/08 nightly works fine with my SanDisk 64GB card. For some reason I can't get the 12/10 nightly to do anything more than spin on the boot logo so haven't tried anything later than that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
You need to change your SELinux permission level to "Permissive" then remount the card using the "Uninstall" and "Install" that are in Parameters -> Storage.

The issue isn't with your SDCard itself, it's the filesystem thats on it. CM11 has issues mounting exFAT when SELinux isn't permissive.

Also, make sure /mnt/media_rw/sdcard1 is empty before you do "Install" as it will fail if it isnt. Some apps (see list bellow) likes to write to this directory, at boot (when the FS fails to mount). In my case, every phone reboot means i open up File Explorer, delete the newly created "Android" directory inside of /mnt/media_rw/sdcard1 and then remount the sdcard. Annoying but not the end of the world, i can live with that workaround for now.

Offending apps, for me, are Facebook, Google Music and Youtube.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dpwguenther:
Is anyone using ART? If so how are you able to make it stick after the reboot? Also if I deleted the libdvm.so (the lib for delvik runtime) will that cause a bootloop? Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
I'll try that.. How to I set SELinux to Permissive?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I use an app called SELinuxModeChanger. Im sure there are other ways too

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
I've used that.. I was curious if there was a builtin way with CM11

---------- Post added at 07:43 PM ---------- Previous post was at 07:18 PM ----------

I changed to permissive, and it's working fine..

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
I'm using ART. Switched it over from dalvik, rebooted, let it do its thing (takes way longer with ART than with dalvik; I think my flashing may be reduced to once every few days a result), and it sticks. No tricks.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
It sticks for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dpwguenther:
I just tried it again and it stilldalvik

Sent:confused: from my SAMSUNG-SGH-I747 using xda app-developers app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Xposed Framework reverts it back to dalvik if you have it installed. ART is not compatible with xposed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewd:
I've got a few issues on my phone. With the last few nightlies, I see random reboots two or three times a day. It hasn't happened when I'm using the phone - it's just sitting on my desk and I'll notice that the CM logo is spinning.

Also, ever since I flashed CM11 (after a factory reset), when I restore all of my text messages and conversation threads, the "new text" notification will not go away. It tells me that I have 235 new messages.

And I can't seem to get voice dialing to work with my bluetooth speakerphone. It worked with one of the early nightlies, I think, but now the speakerphone (a Blueant S4) says that the feature is not supported.

I'm running Nova Prime launcher if that makes any difference. Otherwise, nothing special. Mostly I've dirty flashed, but a couple of days ago I did a factory reset and flashed. That didn't change anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You aren't modifying the asserts in the updater scripts to allow you to flash with an unsupported bootloader are you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewd:
No, I updated CWM to the current version prior to CM11. It would probably be a recipe for disaster if I tried to change the scripts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
I also have the problem with the "new text" notifications. Do you happen to be using something other than the stock messaging app? I use chomp sms and noticed that if I switch back so the stock app is the default then it will mark those messages as read. I then switch the default back again

Of course I have to do this each time I reboot or I get notifications about the "new" ones that have arrived since the last time I did it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewd:
Yes, I'm using Handcent. It's something I can live with. Actually, I can live with all three of them since CM11 is so new. And the little Android notification is kind of a happy little guy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
But if you switch back to the default, open it once, then switch back to handcent then it should clear the fact that it thinks those messages are new
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewd:
Oh, OK, I get it...I misunderstood you. You're right, and now the icon is gone. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
Unfortunately it only works until the next reboot and then you'll have to do it again for any newer messages you have - but it's a step
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Would it help if you turned off the auto retrieve messages option in the stock messaging app?

Then the stock messaging app would never see any new messages thus never reporting that there are any new unread messages present on the system.

Your 3rd party app would then be the only one reporting new SMS.

---------- Post added at 01:44 PM ---------- Previous post was at 01:34 PM ----------

FYI.....Looks like there is a commit merged for the next nightly that fixes this.

http://review.cyanogenmod.org/#/c/55375/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
Yes, I am. I can't talk on the phone since 4.4

I can't possibly be the only one. I even formatted and reinstalled. The mic went all to crap with 4.4

Anyone else? Solution? Bandaid? Been using my bluetooth headset but that's not always easy when the phone rings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
I've been looking for a sound mod to increase the mic volume and so far no luck, this is a pretty annoying issue..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Might worth be looking at:

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

And more precisel:

http://xdaforums.com/showpost.php?p=48348001&postcount=18

If you want to set custom levels. It's the file that needs to be edited.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
I'ts the mic that's low, not the speaker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm very well aware, but this file controls all the gain for all the audio inputs/outputs of the msm soc, including the mic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
I had to enable the stock messaging app to turn it off, did so, and then switched back. I can't reboot to check right now, though, but I'll give it a shot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Anybody else getting wakelocks from Google Search? They stop if I wipe the app's data and force close it but it starts up again as soon as I open the app(and persists after a reboot). I also get a ton of FC's from Google Sound Search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I'd check your location settings. Google Search includes Google Now, which uses location data heavily.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I should have clarified. I don't have Google Now enabled and the wakelock is constant. It simply isn't released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
Just checked - nope, no difference. The old text messages still popped up until I enabled the old messenger and opened it up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Are you sure those weren't there from prior? It really sounds like your issue is just that you have 2 messaging apps receiving the sms. Leave it set up like that for a while and see how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewd:
It looks like the bluetooth phone issue may be related to Google text to speech force closing. I got the phone to respond to the Blueant hands free, but as soon as I pick a dialer, text to speech force close and it's game over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
To save everyone some time and headaches, the camera is broken in the 12/12 nightly. There were some camera commits last night that obviously did it in. Symptoms are you can take one picture but the view finder locks up and ultimately the process all together. Then when attempting to use another app instead the can't connect to camera error pops up and a reboot is required.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Just in case anyone was wondering, it seems CyanDelta isn't picking up CM11 builds later than 12/10. I had assumed builds were failing, but they indeed are available on download.cyanogenmod.org.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Anyone has an inside what the 2 experimental builds "DISABLESPC" are?

cm-10.2-20131212-EXPERIMENTAL-DISABLESPC-d2att.zip

cm-11-20131212-EXPERIMENTAL-DISABLESPC-d2att.zip

Probably not to be ran under normal circumstances, but I'm curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I noticed that to, I just been using the CM updater in settings until CyanDelta is working again.

---------- Post added at 01:38 PM ---------- Previous post was at 01:35 PM ----------

Disables PC? I have no clue what that means.