yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] annoyingduck:
FYI - this was asked a few pages ago and I just tested the answer I gave.

Yes - adding: qemu.hw.mainkeys=0 to the build.prop adds full nav bar capabilities in cm11 the same way it did in cm10 with the settings customization options.
[Verizon Samsung Galaxy S III] bmeek:
As far as I know, the cm download site only keeps a few days worth of nightlies...

I just uploaded a copy to my public dropbox folder https://www.dropbox.com/s/9g2u9gbmk934p5q/cm-11-20140120-NIGHTLY-d2vzw.zip
[Verizon Samsung Galaxy S III] muscal:
I know this is a temporary workaround but only for a little while. It seems to come back after some time. Does anyone know if this has been submitted to CM bugtracker (ie. is it a work in progress and that they at least know this is an issue). Thanks for any info you guys can provide!

---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------

Not quite fixed yet, here is what happens to me. If i finally am able to get my bluetooth connected to my car i am unable to answer the phone via the controls on my steering wheel. When i was back on stock, i would be able to do this no problem by pressing the answer button, now it's a no-go. Any suggestions? Is this something to do with the call screen itself? Thanks!
[Verizon Samsung Galaxy S III] Omega Ra:
On the 1/29 build and having issues pairing my Basis Band to my phone via Bluetooth. This is the first nightly I have installed, was running KitKang previous and it worked. Hopefully it gets fixed in the new nightly
[Verizon Samsung Galaxy S III] Zacharybinx34:
Two issues:

1. Skype doesn't work correctly. My video does not show up on the other person's screen, it just sits there with that loading animation for them forever.

2. Google Hangouts has major delays still. I'm not sure what the problem is with this, but it did it on CM 10 and 11 and I even clean installed, wiped data, uninstalled, reinstalled, etc. etc.
[Verizon Samsung Galaxy S III] ned4spd8874:
I went ahead and reverted back to an older build (20131217) and it's working again. So something has changed recently to stop this game from working. I tried the latest and greatest nightly before reverting and that didn't fix it either. Weird.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I may be assuming the role of Captain Obvious here, but it would seem that as of right now we have a choice between working bluetooth (auto-connect) or excellent battery life. Any chance these two trade-offs are somehow working against each other in the code?
[Verizon Samsung Galaxy S III] NeoMagus:
Bluesleep wakelock is what drains it when the Bluetooth is turned on. Rudedog posted this earlier and I can confirm with cpuspy I've got no issues on 1-20 deep sleeping with BT turned off, however once its turned on no longer deep sleeps. Goes back to normal once I turn it back off with the Power control widget. Just turn it off when you're not using it until they figure it out
[Verizon Samsung Galaxy S III] mastamoon:
If you guys want to try a build that has fixed camera and possible bluetooth fix, check out my unofficial build from today...

Rom: http://mastamoon.truelinux.net/ROMs...cm-11-20140130-UNOFFICIAL-mastamoon-d2vzw.zip

MD5: dd94de17cc63af36fc07543706efed4c
[Verizon Samsung Galaxy S III] bdr9:
Finally, someone else that has the same issue as me! Did you dirty flash from CM 10.1/10.2 or did you wipe data first?
[Verizon Samsung Galaxy S III] NITRO_2:
I actually have the same exact problem and I did a clean flash. I just thought it was the app
[Verizon Samsung Galaxy S III] bdr9:
Well, that's reassuring then. I was about to try wiping all of my data to see if it fixes the issue.

Is there anyone who uses Skype and does NOT have this issue?
[Verizon Samsung Galaxy S III] funkpod:
Thanks! Do you know why YouTube is messed up on LTE? Is yours fixed for that?
[Verizon Samsung Galaxy S III] Omega Ra:
my Wifi doesn't work. It connects to the network, but it shows Orange like there is not internet, and I cannot connect to the play store...yet google now updates...
[Verizon Samsung Galaxy S III] Hybridnoob:
What gapps are you using?
[Verizon Samsung Galaxy S III] bmeek:
Thanks, but no luck here. I dirty flashed over the cm11 1/20 build, as I usually do with your builds, and not only would my headset not auto-connect, it wouldn't connect when I tapped the device name in Bluetooth settings (this has usually worked fine for me with the various nightlies). I then tried re-pairing and it wouldn't see the headset while it was in pairing mode.

I also noticed that 1.) When I tried searching for Bluetooth devices, it would immediately report that no devices were found; and 2.) As i repeatedly tried tapping on search-for-devices and otherwise get my headset connected, it kept reporting that Bluetooth was being turned on (when it was presumably on already).

IOW, Bluetooth is pretty much FUBAR for me. If a logcat would help, here you go: https://www.dropbox.com/s/8143azywg8v6es3/cat.log
[Verizon Samsung Galaxy S III] Zacharybinx34:
What in the world happened to launcher 3...? It's just gone now....
[Verizon Samsung Galaxy S III] chowner:
I have both now
[Verizon Samsung Galaxy S III] Zacharybinx34:
What do you mean that you have both now? I see launcher, but no launcher 3 anymore. Did I lose my setup?
[Verizon Samsung Galaxy S III] Zacharybinx34:
Also, I can't edit any of the settings for trebuchet
[Verizon Samsung Galaxy S III] Hybridnoob:
I know most everyone is having bluetooth problems on the most recent nightlies (S3), but has anyone had success connecting a Pebble Watch on CM11 with this phone? I had no problems doing so with my N7 CM11. Everything else is perfect for me on the latest nightly.
[Verizon Samsung Galaxy S III] Omega Ra:
I was using the full PAGapps for 4.4 from 11/26, but changed over to the same from Jan something. I am flashing the stock rooted deodexed ROM for now with the PAGapps for 4.3 as this is my work phone and I need to make sure all is working. I tried flashing back to a nandroid but was still having the same issue.
[Verizon Samsung Galaxy S III] xgujuplaya:
Is there anyway to get the Google launcher back? I even went back to 1/26 nightly and its gone now
[Verizon Samsung Galaxy S III] Hybridnoob:
Flash PA gapps.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Can someone please tell me what happened to Launcher 3. Trebuchet doesn't even let me edit any options.
[Verizon Samsung Galaxy S III] Omega Ra:
So the intermittent Wi-Fi I was having may have something to do with my router here at home. I can't remember offhand if it was happening at work or not. But the Bluetooth issue is still annoying as I can't sync with my fitness tracker watch. So for now I am on the stock rooted 4.3 ROM
[Verizon Samsung Galaxy S III] Imacellist:
So if someone would be so kind as to state where this ROM is at in terms of stability I would be most grateful. I'm looking to upgrade my wife's s3 but I like to only do it when things are stable. What are the major hiccups with this ROM now? Do they exist in the snapshots? Any info will help. Thanks in advance.
[Verizon Samsung Galaxy S III] Hybridnoob:
Is she running stock 4.3? If so, she's stuck. CM11 is good and stable as long as you don't depend on bluetooth. CM10.2 is the latest 4.3 stable. A new CM11 snapshot should be released in a week or so.
[Verizon Samsung Galaxy S III] Imacellist:
No she is on cm 10 still haha. 4.2 has been good for her but its starting to have issues and that why I'm gonna upgrade her. She never uses Bluetooth so I'll give cm11 a shot. Thanks for the info.
[Verizon Samsung Galaxy S III] Hybridnoob:
Good to hear. One last thing - CM10.2.1 (stable) was just released today if you want to go that route.
[Verizon Samsung Galaxy S III] Imacellist:
Thanks. Its hard to keep up to date with Roms on phones I don't use haha. Appreciate it.
[Verizon Samsung Galaxy S III] Hybridnoob:
You're welcome. One last thing (for real), don't forget to check/update her modem/firmware. You'll have problems if she's not up to date.
[Verizon Samsung Galaxy S III] Casper34:
I noticed when I updated this morning to 2/1 that I had GEM (launcher), trebuchet, and sslauncher. I have liked ssl since I tried it.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Zacharybinx34:
Yes, very annoying. I want to know what happened.
[Verizon Samsung Galaxy S III] Casper34:
OK I know was reported before.... not all the time, but most of the time, and it wont do it while the screen record is on, but when I hit the back button to close an app, another app will show for a second and close. When I go to my recent apps, it will show the app that showed for a second as being the last one opened.

Has anyone else seen this? How can I fix it?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] esjames:
This has happened on multiple devices. My wife's gnex did the same thing on today's build. We got reverted back to the original kitkat UI.
[Verizon Samsung Galaxy S III] esjames:
I am pretty sure it's by design.
[Verizon Samsung Galaxy S III] mastamoon:
They are working on rolling out the new trebuchet and something obviously went wrong with the data conversion/migration.

Not sure what's up with the wrong layout. I'd install a 3rd party launcher like Nova if you want to make you stay out of the mess.
[Verizon Samsung Galaxy S III] joedajoester:
Can anyone comment on the status of the 2014/02/01 build? I realize that gpe launcher is missing, and has been missing since when? It shouldn't be a problem to sideload by placing it in /system/apps. Overall, how stable is it compared to older nightlies? Also, anyone know why ge launcher is gone? Was it a mistake or something legal involved? thanks
[Verizon Samsung Galaxy S III] Zacharybinx34:
We need launcher 3 reverted back. This Trebuchet stuff needs to go immediately.
[Verizon Samsung Galaxy S III] gt43aw:
Joedajoester 02 01 works awesome besides bluetooth. Its pick your poison. No Bluetooth and everything works and battery is kick butt or older daily that sucks battery like no ones business. I confirmed the awful battery performance on earlier builds in Jan on my nexus 7 as well. Oh and it isn't cm that doesn't have gel but the latest gapps from the cm wiki site. If you want it, sideload or use another gapps like PAC which has been suggested a few times here.
[Verizon Samsung Galaxy S III] bmeek:
I've been missing Trebuchet since CM10.2 and I'm happy to see it coming back into cm11 - I like the deeper integration between the ROM and launcher. OTOH, a nice thing about android is your range of ui options with all the different launchers available.

GEL seems ok as far as it goes, but last I checked it was pretty limited option-wise, and I've never felt that Google search is too far away...

I've been running holo launcher recently on cm11 and CL8, and I must say it's nice to be able to backup & restore launcher configurations independently of ROMs...

---------- Post added at 04:47 PM ---------- Previous post was at 04:37 PM ----------

No kidding? I don't see it on the cm download site yet (nor any recent 10.2.? nightlies or release candidates). Are we really expecting a build for the d2vzw?
[Verizon Samsung Galaxy S III] Hybridnoob:
I haven't seen it yet either. Was basing my comment on this (http://www.cyanogenmod.org/blog/cm-10-2-1-maintenance-release). Should be posted soon...
[Verizon Samsung Galaxy S III] joedajoester:
Did you do a clean flash? Dirty flash might of broke Bluetooth for you. The better battery your saying excites me, but I'm kinda skeptical. Thanks
[Verizon Samsung Galaxy S III] Durhammer:
How does the 2/01 battery life compare to Snapshot M2 (1/02)? That was the last rom I was on

Are there any major non-bluetooth related changes between the Snapshot on the 2/01 rom?
[Verizon Samsung Galaxy S III] dmginc:
Way better.
[Verizon Samsung Galaxy S III] ned4spd8874:
Any word on if The Simpsons: Tapped Out crashing will be fixed anytime soon? It works fine with older versions of the Rom, but anything from the past few weeks causes the game to crash for some reason. Myself and a lot of other people are stuck in update limbo because we just don't want to be unable to play this game. I know this is a very specific bug and probably not very high on the to-do list. But it doesn't hurt to mention and ask about it.
[Verizon Samsung Galaxy S III] dandaman96:
CM11 20140202 nightly - not usable

Just a heads up. I just installed the most recent nightly (cm-11-20140202-NIGHTLY-d2vzw.zip) and it didn't go well.

Phone booted, brought me to the lock screen and allowed me to unlock the phone. That worked fine.

Once the launcher was showing, I attempted to launch an app. With a single short press on an app on the home screen, it acted as if I had long pressed (as you would to preposition or delete an app icon from the screen). It then locked up. I had to pull the battery. Booted a second time and repeated. I found that as soon as I touched the screen or any button once, the UI froze. It would not recognize any additional touches or button presses. All I could do was pull the battery. During all of this, I had no access via adb. The phone did continue to function though (it just wouldn't accept any user inputs). When I connected my USB cable, the top ribbon displayed a notification that it has been connected as a media device. But no debugging.

Something else I'll mention - I'm not sure if it is related or even an issue at all - but I noticed it while attempting to resolve the above issue. I had thought to enter recovery, all you had to do was hold the volume key while pressing power. But I find now that I need to hold volume+home key+power to get into recovery. I'm not sure if this is a change or if I'm just off my rocker here.
[Verizon Samsung Galaxy S III] DGolom:
Yeah, newest nightly is definitely booked. But you have always needed to hold the home key to boot into recovery.
[Verizon Samsung Galaxy S III] ericsdeadinside:
Same here. Wtf did they do?
[Verizon Samsung Galaxy S III] dandaman96:
I would say 75% of the time that I boot into recovery, I do so through the reboot menu in the software. So the key sequence isn't something I use that often. And I didn't see how that could have been effected with the flash, but man... I don't remember having to hold the home key. Old age I guess.

I'll admit, I was getting a little panicked at first when the phone was unusable and I couldn't get into recovery.

---------- Post added at 11:41 AM ---------- Previous post was at 11:33 AM ----------

Is this to say that if I were to go purchase a new S3 today, that I would not be able to install CM?
[Verizon Samsung Galaxy S III] NegativeOne:
How's BT today? And how's battery life?
[Verizon Samsung Galaxy S III] Aquila76:
If it has the ML1 firmware on it, you are correct. Verizon made Samsung change the bootloader and add KNOX to the latest firmware, so no ROMs with custom kernels like CM11. If it has MF1 or older, you're good to go.
[Verizon Samsung Galaxy S III] Durhammer:
Damn, now I'm tempted to return from TW 4.3...argh.. Thanks :)
[Verizon Samsung Galaxy S III] xs11e:
Yup, totally borked.

You might not be totally off your rocker. Have you ever messed around with a Galaxy S4? Volume up + Power boots the S4 into recovery. If you've never booted an S4 into recovery maybe there's some other phone that works that way? The S3 has always required volume up + home + power.
[Verizon Samsung Galaxy S III] lakingslayer:
As far as launchers go I like the 'Launcher' launcher. I can Swype to the left of my home screen and have a my Google now screen all set and ready. I think that's cool. Not sure how to do that with any other launcher
[Verizon Samsung Galaxy S III] xneuromancer:
4.4.2 is nice but I'm getting sick of the Android System battery drain. I only get ~12h out of my battery and this is barely using it, just having it sit on my desk while I work.

I've been looking at trying 4.3 TW, but there seem be all sorts of issues with Lock Screen wake-up lag. I definitely don't want that. I understand there's some tweaks and custom kernels that will help, but I haven't seen anything definitive that completely gets rid of it (without removing the lock screen or deep sleep entirely). Not sure where to go from here :|
[Verizon Samsung Galaxy S III] XdrummerXboy:
Latest Nightly (2-2-14) is messed up. I wish I had visited the forum before installing it.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Not even sure what you guys are taking about. 2-2 is running fine for me
[Verizon Samsung Galaxy S III] NeoMagus:
Battery is fine on 1-20 with the working bluetooth just turn it off when not in use, its the wakelock that keeps it from deepsleeping and drains it. Cpuspy is great for making sure the phone is getting deep sleep.

Haven't had any problem making it a full day here and using it in the car on my drive to work I just turn it completely off from the power settings widget after it disconnects from the navi
[Verizon Samsung Galaxy S III] mjb32803:
Feb 2nd nightly locks up after booting. Installed via the CM updater, coming from the Feb 01 nightly. The first boot after flash, the phone rebooted in the middle of the boot animation. 2nd boot attempt, I get to the pin screen, enter the pin, and home screen comes up. If I do anything, the phone locks up. Have to pull battery. Reflashed back to Feb 01 and all is fine again.
[Verizon Samsung Galaxy S III] dpn982:
Same here had trouble with Feb 2nd nightly had to go back to Feb 1st
[Verizon Samsung Galaxy S III] Zacharybinx34:
Feb 2nd build locks up, and going back has jacked up trebuchet with never ending crash errors.

Where is Launcher 3? Just put it back.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I set up a Tasker profile to shut off the Bluetooth as soon as I disconnect from my car's hands free.

Does anyone know if cm11 builds for other devices are having the same issues?
[Verizon Samsung Galaxy S III] tv31284:
The m2 build rebooted quite often for me. The more recent nightlies have done better but still reboot every so often. Here's a log from the 1/27 nightly. Phone was in my pocket and I didn't realize it had rebooted until bootlog notified me. Thanks for the all work all of you put in.
[Verizon Samsung Galaxy S III] NegativeOne:
How's bluetooth now?
[Verizon Samsung Galaxy S III] bmeek:
Today's build was too messed up to be able to gauge progress on Bluetooth...
[Verizon Samsung Galaxy S III] xbiker321:
Feb 2nd caused signal not to work. Went back to Feb 1st and all is good again.
[Verizon Samsung Galaxy S III] RoboJoe:
Anyone tried the 02/03 build? I just got the boot animation for about 10 minutes before I gave up and flashed back to my previous build.
[Verizon Samsung Galaxy S III] Omega Ra:
I am downloading it now. Will probably try it out, but I did a complete backup from TWRP of my existing ROM first LOL
[Verizon Samsung Galaxy S III] iwearthebelt:
Booted OK for me. Launcher was a little unstable at first and it switched my wallpaper back to the stock wallpaper. Did a reboot and it seems stable now.
[Verizon Samsung Galaxy S III] merdely:
Do you mind sharing how you set this up?

I don't think so. I have a friend on an AT&T S3 who doesn't have this problem. And, I looked at Paranoid Rom's forum last week and they ARE having the same camera and bluetooth problems. So, I think they're specific to our hardware and Kitkat.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Feb 3 works for me, aside from Trebuchet not letting me edit the Drawer settings - anyone know why that is?
[Verizon Samsung Galaxy S III] Omega Ra:
I prefer the regular launcher (though I haven't tried trebuchet) so I don't know anything about that. But with a full wipe everything seems ok so far. Waiting on apps to install before testing BT and such.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I set up an exit task for my Bluetooth connection profile. The exit task shuts off the Bluetooth. Let me know if you need more details than that
[Verizon Samsung Galaxy S III] NegativeOne:
Does bluetooth seem to be working okay today?
[Verizon Samsung Galaxy S III] Zacharybinx34:
Seems fine to me
[Verizon Samsung Galaxy S III] NegativeOne:
Weird isn't it? I didn't see any commits for it today.
[Verizon Samsung Galaxy S III] merdely:
Nope. Your hint was exactly what I needed. I'm a Tasker newbie and "Exit Task" was enough info. Thanks!
[Verizon Samsung Galaxy S III] Omega Ra:
So my BT still isn't working correctly. I can get my Basis watch to pair and sync, but then it can't connect again. I always have to go back into the app and reconnect it to the phone...
[Verizon Samsung Galaxy S III] Zacharybinx34:
It's not prefect yet, some long connect times still
[Verizon Samsung Galaxy S III] merdely:
So, you motivated me to install the latest nightly (0203) and go try it in my car. It took me several attempts to connect, but I was able to connect manually and I was able to make a call. At this point, I'm finding this preferable to an automatic BT connection and HUGE battery drain.

I went for an two hour drive this weekend with my BT connected, I didn't make a call, and my battery was down to 50% from 100%. So, manual connect BT for me!
[Verizon Samsung Galaxy S III] thefuzz4:
So decided to give today's build a go. Does anyone know how to add the google now as a home screen? I really liked it just being a swipe away. I'll test out the bluetooth with my truck later on today. I'll take a manual connect over battery drain.

Also this is happening on both mine and my wifes S4 on Tmobile. When you tell CM to always use this app it just keeps prompting you each and every time. Does this happen to anyone else? Do you know a way to make it stop?
[Verizon Samsung Galaxy S III] bmeek:
I think it's more likely that your drive took you through some low coverage areas and your battery was spent trying to maintain a signal.

I've used the 1/20 build and don't see anything like that while leaving Bluetooth on. Presumably the higher battery drain is associated with Bluetooth listening for the presence of a paired device looking to connect. When connected to a device, I don't see noticeable battery drain simply maintaining the connection. Were you streaming Pandora or something that you were playing through the car stereo?
[Verizon Samsung Galaxy S III] NegativeOne:
It's also something that is present in only some of the newer nightly builds I think
[Verizon Samsung Galaxy S III] Casper34:
OK, sorry for sounding so naive, but why can't you just add the widget? I can add the Google widget and see my cards.

BTW, in case it matters, I am using SSLauncher.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] lakingslayer:
This is so much nicer than a widget
[Verizon Samsung Galaxy S III] harry_seaward:
Don't you need to be using the Google Experience Launcher for this effect?
[Verizon Samsung Galaxy S III] merdely:
No. Bluetooth is keeping the phone awake the WHOLE time it's enabled. Not about the signal. I've done that drive before and have never had that problem.
[Verizon Samsung Galaxy S III] LudicrousPeed:
Deleted
[Verizon Samsung Galaxy S III] WarER4X:
You should drop that Feb 2 nightly like it's radioactive! It's full of problems. Go with Feb 1 or 3 (though, I haven't tried 3 yet).

-SR-
[Verizon Samsung Galaxy S III] KevTN:
I have a question do I need to flash pa-gapps or ?. Reading the OP is sounds optional. Coming from stock.

Thx
[Verizon Samsung Galaxy S III] xs11e:
Yes, the pa-gapps will work fine.
[Verizon Samsung Galaxy S III] NeoMagus:
fwiw my Galaxy Nexus Toro on CM11 same day nightly before bluetooth was "fixed" exhibited the same behavior trying to connect to my car, com.android.bluetooth or whatever it was would crash on pair and connect , reconnect then crash again over and over- nothing worked with my unit until 1-18 /19 whatever it was when it was fixed before it broke again, I have both my S3 and Toro now still on 1-20 as they are both working fine in the car auto connects and works just like CM 10.2 did.

As for huge battery drain while in the car I dont see anything crazy I have a 45 min drive to and from work and I play pandora the whole way and havent had a problem yet, watching it with cpuspy it just hangs at lowest frequency and doesnt deep sleep while on just switching it off soon as im done with it and it starts sleeping fine again