yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] lou1210:
Do you have GPS enabled?
[Verizon Samsung Galaxy S III] dpn982:
Anyone else having external sd card issues?
[Verizon Samsung Galaxy S III] wpbear:
Which clock app to add? Confirm same problem and also the bold selections do not take affect either.
[Verizon Samsung Galaxy S III] jhanford:
I'll be interested to see how tonight's nightly goes. I've been fighting all day doing my own build from the cm-11.0 branch (no cherries!) and the camera fails all the time (3rd party camera apps too)

The last build I built that works was started yesterday evening around the same time as this official build.
[Verizon Samsung Galaxy S III] jordannike:
This build has been working flawlessly only problem for me is battery life for now... BTW is there any good kernel I can install for this build?
[Verizon Samsung Galaxy S III] jhanford:
If you clean flashed, battery life will be worse as the rom settles in. Same happened with me on KitKang for the first couple of days. Now I think it's better than any previous version of Android on the d2vzw
[Verizon Samsung Galaxy S III] tykalx:
did everyone do this step in order to flash or is this optional? i went through each page didnt seen anyone having trouble with it, i did. i just want to avoid bricking.
[Verizon Samsung Galaxy S III] mastamoon:
Browse to /data/system and delete wpa _ supplicant and reboot.
[Verizon Samsung Galaxy S III] greaseman2:
Thank you. Worked perfect.
[Verizon Samsung Galaxy S III] annoyingduck:
I'll thank him for ya:p!
[Verizon Samsung Galaxy S III] biggins82786:
Just had my first random reboot after a full 24 hours on the 12/15 nightly. Only problem I've had thus far. Anyone else having this issue?
[Verizon Samsung Galaxy S III] Defragger51:
I have no idea how you can say Bluetooth works. I have tried every night since I started using the Official CM11 nightly's on 12/9 and Bluetooth has never worked correctly. I have to force my phone to connect with my ear piece every time, it has never done it on its own and usually the phone requires a reboot to get it to connect again that's not working correctly to me and I am on 12/17 now, Someone said in an earlier post that 12/11 had Bluetooth working , so I did another complete wipe /clean install only to find out that it was not true same problems persist on that one also. I have decide to go back to the last unofficial build I have, where I know fore sure Bluetooth and camera worked correctly, everything worked except Tap 2 Pay and I see in other recent post it still does not work. I really like and appreciate all the nice things the CM team has done to the rom and appreciate there hard work, but I'll have to stay with an working unofficial build until the basics get fixed. I wish they had never taken the wired ear piece jack's off phones.
[Verizon Samsung Galaxy S III] duarian:
Camera is still messed up in low light when using flash. Otherwise everything seems in working order
[Verizon Samsung Galaxy S III] Argent36:
Which unofficial build are you using that had working BT? I haven't had any 4.4 ROMs yet that worked....when I'm connected to my Jeep's radio BT just force closes after a minute or so...I understand the frustration (also it seems like about once an hour my pebble watch will also lose its connection to my phone) just dirty flashed 12/18 - we'll see how that works.
[Verizon Samsung Galaxy S III] lou1210:
I went from cm11 official nightly 12/14 that would never stay connected, back to cm10.2 (android 4.2.2) and then formatted everything and did a factory reset and installed 12/17 nightly. I tested for a while last night to verify that Bluetooth would stay connected. So far it has. I still have my backup of 4.2.2 so if it doesn't keep working I have something to go back to that I know works. And from what I'm seeing, no one phone does the same thing with each nightly build. Trial and error, but we always have other working versions to go back to, which is nice.
[Verizon Samsung Galaxy S III] lyricalsoul5:
RIL settings/update?

My data isn't working.
[Verizon Samsung Galaxy S III] korky0429:
Anyone else having wifi issues? Every build I've tried does. Dirty flash and clean flash. I can connect to wifi once but once I get disconnected, I can't connect to anything again or even find any.

I know there is at least 4 more wifi points in the but it doesn't find them.
[Verizon Samsung Galaxy S III] rfmodeler:
I flashed the official 12/13 that did not have Bluetooth working, but when I dirty flashed to 12/17 it was working again. I did a clean flash coming from CM10.2 and I formatted system when I dirty flashed.

Are you on stock kernel?

Did you clean flash to CM11?

What recovery are you using?
[Verizon Samsung Galaxy S III] Aquila76:
MiraCast / Cast Screen functionality working?

I noticed under the Display & lights setting there's an option for "Cast Screen." Does this actually work, or is it a placeholder for future functionality? I was gifted a MiraCast dongle, but the S3 running 12/15 nightly can't see it. I turned on "Enable wireless display", but nothing shows up in the list. Anyone have this working and can share settings?
[Verizon Samsung Galaxy S III] ugachris:
Did you try this from the previous page?

http://xdaforums.com/showpost.php?p=48591725&postcount=589
[Verizon Samsung Galaxy S III] Defragger51:
Sorry for the misunderstanding , the unofficial I was talking about is the 11/28 unofficial CM11
[Verizon Samsung Galaxy S III] korky0429:
I tried but I don't have that file
[Verizon Samsung Galaxy S III] Defragger51:
I am running the stock kernel, never really change that unless it really fixes something or improves battery life,don't care to over clock or anything like that. Yea I have done complete clean flashes, I am so tired of reloading everything on my phone to make sure it was not a dirty flash that causing the problem. I am using TWRP 2.3.6.1 without any issues and been using it since the 11/18 unofficial build, I like a touch recovery I can see on a touch screen phone, just my personal preference. I am also back on the 11/28 cm11 official build now and Bluetooth works flawlessly.
[Verizon Samsung Galaxy S III] chizler:
Any have a fix for the google service battery drain. I'm at 65% of my battery being used, I have turned the Google sync as mentioned in the earlier post.
[Verizon Samsung Galaxy S III] rfmodeler:
Many people have had problems using TWRP. Even on the newest version is not recommended.

If 11/28 works for you then I would stay there until you feel brave enough or impatient enough to go to a newer version.
[Verizon Samsung Galaxy S III] sidepocket:
This is still happening to me as well. I'm on the 12/18 nightly, clean install.
[Verizon Samsung Galaxy S III] WarER4X:
The latest version of TWRP worked just fine for me. I wonder if anyone out there has installed TWRP from the Play Store, but didn't actually use it to install the latest TWRP Recovery and, therefore, is still using the old Recovery. I flashed the 12/16 build with it yesterday and haven't had any problems (except the known camera thing with that build and I haven't had any cause to use BT at the moment). I would use CWM if I had to, but haven't needed to thus far.

-SR-
[Verizon Samsung Galaxy S III] merdely:
FWIW: I have an Acura ('05). When I get in the car, the phone does not automatically connect with the car. I have to manually connect them touching the car's entry in the bluetooth settings several times (sometimes as many as 10 times) before it actually connects. Then it works fine until I get out of the car.

While not ideal, this is useable for me.
[Verizon Samsung Galaxy S III] cehrl7:
Bluetooth works perfect on 12/7 build.
[Verizon Samsung Galaxy S III] titanshadow:
Do you have a link?
[Verizon Samsung Galaxy S III] AlphaXray:
Builds have been getting better, other than the obvious 12/16. But I'm still having front facing camera issues using certain apps.

And I know these builds are early, but it would be awesome if we could get the option to toggle brightness by sliding along the status bar back. I used that frequently.
[Verizon Samsung Galaxy S III] duarian:
Install xposed framework and gravity box. Has everything you will ever need.
[Verizon Samsung Galaxy S III] ned4spd8874:
I have the WiFi problem too. And also, that folder is not in the location on my phone. However, I performed a search and the "wpa_supplicant" folder is located in the following locations: /data/misc/wifi/ and /system/bin/.

Would I be correct in assuming that the first location would be the place to remove that folder from?
[Verizon Samsung Galaxy S III] harry_seaward:
Does Gravity Box work okay on CM11? I wanted to try it out but everyone says not to use it on custom ROMs.
[Verizon Samsung Galaxy S III] senorbuck:
Working great for me! Make sure you install the KK variant.
[Verizon Samsung Galaxy S III] xneuromancer:
I'm wishing I found out about Gravity Box sooner. This has all the mods I usually need in a ROM, which means I can stay with the constantly updated CM11 and not wait for custom ROM's to be updated. The other nice thing is that since GB is it's own app, all of my custom settings get saved through TB backups, so when I restore on a new build or dirty flash, I just re-install and all my settings come back.
[Verizon Samsung Galaxy S III] yhknq:
is the new firmware update out for us?
[Verizon Samsung Galaxy S III] lou1210:
Is there a mod or is it included somewhere in one of the menus? I'd like to download and try it too. Or is it in the play store?
[Verizon Samsung Galaxy S III] senorbuck:
You need to install the xposed framework and then the gravitybox module. Once you install the framework it'll show up as an app. You activate it, reboot, install gravitybox (via xposed app or apk), configure it, then do a final reboot/soft reboot.

Everything you need is in the main android apps forum on xda.
[Verizon Samsung Galaxy S III] lou1210:
I found it. I might give it a try sometime today or tomorrow.
[Verizon Samsung Galaxy S III] duarian:
New firmware?
[Verizon Samsung Galaxy S III] mastamoon:
Don't flash anything from the new Ota yet.. Its looking phones up and bricking others..
[Verizon Samsung Galaxy S III] duarian:
I didn't even know there was a new OTA...interesting. Is this the same one Samsung pulled a while ago for bricking phones or is this something new?
[Verizon Samsung Galaxy S III] ned4spd8874:
I took it upon myself to rename that folder as well as the .config file to see if that helped. It did not. Still broke.

Also, when I cycle the WiFi, it doesn't even show available networks. And also, I cannot connect or forget the current wifi connections (when I can get the phone to actually display them that is).
[Verizon Samsung Galaxy S III] harry_seaward:
Try going to Settings > Display & Lights > Cast Screen > Menu and turn "enable wireless display" on and back off. Then reboot.
[Verizon Samsung Galaxy S III] ned4spd8874:
That did it, thanks!
[Verizon Samsung Galaxy S III] yhknq:
Thanks
[Verizon Samsung Galaxy S III] senorbuck:
Awesome. Lots of nice modules to mess with :)
[Verizon Samsung Galaxy S III] korky0429:
I tried removing those files and made the wifi issue worse, had to dirty flashed 12.8 to get wifi to turn on again
[Verizon Samsung Galaxy S III] ned4spd8874:
I've got a new problem and it's a biggie! I've over slept now the last couple days since installing this. My alarm is no longer working!

I've done some troubleshooting tonight and have found that it's only when the phone is docked. I have the official Samsung dock BTW. I have checked every setting I can find and nothing points to what the problem could be.

One weird thing I noticed is that when the alarm is going off, the volume keys don't work. The phone will also vibrate, just no sound.

What gives?
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I'm using it just fine as well. The reason why ppl say not to use it on custom roms is because most custom roms have these options built in. But they are not inCM11 yet so u can use this for now.
[Verizon Samsung Galaxy S III] im_on_fire:
it's the verizon 4.3 update and from what i hear from stock users, it's working fine.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Anybody on the 18th build having SOD issues?

Edit: Updated to 12/19 and all seems well.
[Verizon Samsung Galaxy S III] StormFreak:
I am using the 12/19 build and am having no issues whatsoever with this as a DD. The only issues I am still having are with Instagram and Vine video recording. I would like if these would work, but I don't know if that will happen. From what I understand Instagram video recording wasn't working in any AOSP builds from 4.3 and up.
[Verizon Samsung Galaxy S III] mastamoon:
Thats because sounds are being routed through the dock for alarm notifications.. not good but hasnt been fixed over multiple versions.
[Verizon Samsung Galaxy S III] ericsdeadinside:
I can record video on Instagram, but somewhere in the upload process it's dying. Just like lately I can't upload pictures to Facebook. It's like the formatting is getting screwed up or something.
[Verizon Samsung Galaxy S III] StormFreak:
Mine crashes after applying filters multiple times to the video, or when selecting the cover image for the video. I haven't experienced the FB issue, but I haven't uploaded photos since several builds ago.
[Verizon Samsung Galaxy S III] ned4spd8874:
But the dock doesn't have a speaker. I'll have to look when I get home, but I don't think it even has a output jack.

I was on a CM10 nightly from back in September previous and didn't have this problem. This isn't good. I need an alarm. I can't keep waking up at the time I'm supposed to be leaving.

Any ideas out there? I'd hate to have to move away from CM for something so trivial, but I may have to if this doesn't work.
[Verizon Samsung Galaxy S III] soapinmouth:
Does anyone else have a problem with the camera creating and being unusable until reboot?
[Verizon Samsung Galaxy S III] xs11e:
Can the devs please fix the Blue Tooth? It's bothersome to have to connect manually every time I return to my car! CM10 didn't have this problem nor does CM11 on my old (now smashed) S4.
[Verizon Samsung Galaxy S III] StormFreak:
Which build are you on? From what I understand this was fixed in one of the recent nightlies.
[Verizon Samsung Galaxy S III] rfmodeler:
The 12/17 nightly connects automatically for me when I get in my vehicle. The only thing that doesn't happen is I have to manually push play on Google music. That could just be a setting though.
[Verizon Samsung Galaxy S III] dtcousineau:
The Bluetooth is killing me.
[Verizon Samsung Galaxy S III] sstenhjem:
(Status 7) Installation Aborted

I tried a lot of stuff today and could not get 12-19 nightly to load?!?!??! I formatted the internal SD. I did cleared all cache and did everything I could think of. I am on MF1. I am coming from Pac-Man ROM. Any ideas? :eek:
[Verizon Samsung Galaxy S III] Hybridnoob:
Are you on the latest recovery?
[Verizon Samsung Galaxy S III] sstenhjem:
That is what I am doing right now. I do take back my statement, "I have tried everything." I will update.

EDIT: Having the latest CWM worked for me. So much for assuming I was up to date.
[Verizon Samsung Galaxy S III] annoyingduck:
hey guys, having an issue I've never encountered...updated todays nightly from the cm updater and the recovery script must be broken..it flash fails, auto reboots, bootloops....a battery pull and rebooting to recovery auto engages the cm updater script...I cant do anything...tried to odin another version of twrp + same thing happens. I'm not up for a full stock odin tonight...any ideas? Anyone have a current cwm .tar file, all I can find are old ones...

---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------

can I shell command to tell twrp to stop its activity?? this is ridiculous!!
[Verizon Samsung Galaxy S III] Hybridnoob:
This should get you going...

http://www.clockworkmod.com/rommanager

http://android.stackexchange.com/qu...t-img-to-tar-to-flash-using-samsung-odin-tool

Can you intercept the boot process by hitting/holding volume up and home right after the Samsung logo goes away? That's how I've restored nandroid backups when I ran into bootloop situations (without having to pull the battery).
[Verizon Samsung Galaxy S III] kirkwoodlucas:
On 12/19 rebooted, and now WiFi will not work. Says saved, press connect, and then it just says save. No matter what I do wipe caches and factory reset won't work. Any fix?
[Verizon Samsung Galaxy S III] annoyingduck:
What I had to do was to Odin a non Kitkat compatible recovery - in this case an older cwm. When rebooting back into recovery that dam update script ran again, even with a different recovery! This time though the script failed because of the out of date recovery and I was able to actually access the recovery. Quick wipe of system/pulled battery/Odin twrp/restored backup... Wtf! Be careful with the cm updater!
[Verizon Samsung Galaxy S III] merdely:
I've observed this behavior with my Acura TL & CM 11. CM 10.2 didn't have this problem and neither did stock.

Basically I have to go into Bluetooth settings and tap the entry for my car a few times (3-7 times) before the phone will connect to the car. Then it works fine for the time I'm in the car.
[Verizon Samsung Galaxy S III] lexluthor:
I'm on 4.1.2 stock/rooted/cwm/unlocked bootloader. I'm thinking of taking the leap as I see people posting in other threads that everything is great on CM11 and they are thrilled with it, but then I come into this thread and it seems as if there are all sorts of dealbreaker type problems.

Sometimes the serial flasher has a very different definition of "working" as does someone who needs to use the phone of a wide variety of things.

So, what exactly isn't working here? When people say the camera is bad...does the camera work? I guess no more saying "cheese", but is the picture quality nearly as good as the TW camera? Is the front facing camera working with a wide variety of apps? What's not working with bluetooth at the moment? What other (even minor) issues are there still with this ROM?

Just trying to figure out if I really want to do this or just wait for a rooted 4.3 that I can flash.

Thanks!
[Verizon Samsung Galaxy S III] RayMcGrath:
Hey give it a try, you can always restore your current. Backups are great! :)
[Verizon Samsung Galaxy S III] rhcreed:
I can't speak to cm11, but I've been on cm10.2 for a while and there's nothing that "doesn't" work as far as I can tell. Very stable.
[Verizon Samsung Galaxy S III] lexluthor:
True, but I'd waste a few hours if there are known issues that would be a dealbreaker for me.

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

Yes, but I'd think that going to kitkat in cm11 would present a whole different set of things to deal with.
[Verizon Samsung Galaxy S III] titanshadow:
The major two things that I've had problems with are Bluetooth and the Camera. I haven't tried the camera though anything other than the camera app so it could be the app or not. I don't know. Bluetooth by far is the biggest issue in this ROM right now. People are having a variety of problems with devices not connecting automatically and having to go in and manually connect. Sometimes that doesn't even work and in some cases I've read about there are times when the Bluetooth stops cold until a reboot is done.

In the Camera app the things I've noticed are when trying to take a picture, it'll take a picture but then freeze up and I can't then use the camera again until I reboot. I don't take a lot of photos so your milage may vary I haven't tried it in several days.

If you need working BT and Camera then I'd recommend going to CM 10.2, which is a 4.3 ROM that works beautifully. Despite how much I like the GEL (Google Experience Launcher) and the built in option for Tap and Pay to the settings where I don't have to do a mod anymore to use Google Wallet. However, 10.2 is a great ROM and far better than the stock or even stock/rooted TW ROM. I highly recommend it if you really want a stable device you will very likely have better luck with 10.2 right now than with the 11 nightlies at this point.
[Verizon Samsung Galaxy S III] lexluthor:
I appreciate the detailed reply. I don't get how there are people telling others to go for CM11 and that everything is great, when things like you describe above exist.

If I'm not going to get a rock solid KitKat ROM, I'd probably just as well use TW 4.3 stock. I will sit back for a few days yet and hope someone can put together a TW 4.3 stock/rooted/odex flashable zip that I can dirty flash.
[Verizon Samsung Galaxy S III] senorbuck:
This (Instagram, Vine, etc.). What needs to be looked at to get this fixed? Not gonna happen or other things have priority at this point? Loving all the nightlies and run CM regardless. It would just be nice to use the video recording type apps.

:/
[Verizon Samsung Galaxy S III] titanshadow:
Well, a lot of devices aren't having the issues with Bluetooth and Camera that this phone is. I know my Note 8 is working beautifully and has no issues except the front facing camera which I hardly use. I will say as well that I would still recommend using CM in a 4.3 ROM than TW in a 4.3 ROM but that is just me.
[Verizon Samsung Galaxy S III] lexluthor:
And I might jump for that yet, especially if it starts taking more than a few days to get a TW 4.3 flashable out. Either way, I have my update check disabled on TW 4.1.2 so there's no chance I wind up with a locked bootloader and keep the option for CM10.2 and CM11 open.

As for CM10.2, you are recommending this, right?

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

No known bugs with camera, bluetooth, wifi, etc?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Try this: http://download.cyanogenmod.org/?device=d2vzw&type=stable
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Besides the Bluetooth and Camera issues, I've also noticed an issue beginning 12/17 up to latest build: some games, such as Samurai Siege (don't judge me), fail to load properly and just get stuck at a black screen.

I wouldn't expect any major fixes until after the holidays, but until then, the reported issues are pretty good for a nightly build that's essentially been around for two weeks on our device. Since nightly builds don't have any official bug reports, we just share stuff that we notice here to gauge everyone else's experiences/share fixes or workarounds/discuss changes/issues with flashing. If camera and bluetooth are deal breakers, then this isn't a daily driver for you. The camera issue has a temporary workaround which seems promising (since if an off the shelf app can work, hopefully it's just the matter of some small tweak to the code)

But, I'm just a user on this project, not a dev.
[Verizon Samsung Galaxy S III] rfmodeler:
Both camera and Bluetooth work fine for me. In on the 12/17 nightly and haven't had any functionality issues. Just follow the directions in the OP and you should be fine.
[Verizon Samsung Galaxy S III] duarian:
Have you tried taking low-light or pure dark pictures? Sometimes I get wavy red lines across the entire picture. More-so if there is an external light source in a dark room. Doesn't happen all the time, but then again sometimes it happens 5 times in a row before I get a good picture.
[Verizon Samsung Galaxy S III] WarER4X:
Interestingly enough, I've had lines like that in low light photos from this phone even before rooting (when I was still running the stock ROM). I always assumed it was a physical design problem that was exposing the flash to the image sensor.

In any case, I'm running the 12/19 build without any camera problems, stock app or otherwise. I still need to try out my bluetooth, though. The only issues I'm having with my phone are all universal problems with Google's apps:

Chrome's blanking screens

Map's inability to correctly shoe the direction I'm traveling

Now's lack of some of the card options in KitKat.

I'm grateful that the CM team does a much quicker job of fixing their bugs than does Google.

-SR-