yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] sammymcalaxy:
Anyone else having difficulty with Wi-Fi? Started a week ago for me, I was able to see my ssid, but after typing my password (correctly), I'd get a toast saying "Failed to Connect to Network". I could connect to a public network though, so I figured something was jazzy with my config. Fixed it by going into data/misc/wifi/wpa_supplicant.conf and deleting all the stored network { } junk. It worked, and for the past 3 days, I've been humming along on my normal ssid.

Last night, while using my phone, it bounced me from my network, and again " failed to connect to network "; except this time, juking my WPA_supplicant.conf doesn't work. I'm confused, it's not a firmware issue, it couldn't be a kernel issue, could it? Am I alone here, is this something I screwed up inadvertantly, or is this something others have dealt with?

Research has born no new fruit....gracias por su ayuda

Sent from my SCH-I535 using weak and spotty LTE because the wifi is currently unattainable.
[Verizon Samsung Galaxy S III] Omegapsy:
I had that happen to me but it worked itself out with no interaction from me. You are not alone on getting the problem but I am unsure on how to fix it
[Verizon Samsung Galaxy S III] sammymcalaxy:
Thanks, makes me feel a little better. I finally just got it to connect, albeit for only about 30 seconds; and much like you said, it wasn't due to anything in particular. As I've written this, it's disconnected and reconnected. What the hell?
[Verizon Samsung Galaxy S III] kidhudi:
Deep sleep seems to be activating now.
[Verizon Samsung Galaxy S III] Reznor7:
The WiFi issue is driving me insane. Might have to go back to CM11 if I can't get it to settle in. Sometimes on a fresh install, on the initial WiFi connection, I get the failed error. Other times it works. When turning WiFi on/off, it frequently fails to turn on the first time and toggles back/forth multiple times on/off. Sometimes it eventually sticks on, other times it doesn't and even erases all of my saved networks! Nobody else seems to have this issue, and I can't figure out what the heck could be causing it. I ODIN'ed back to stock yesterday and started from scratch. Still got the same symptoms. No idea what it could be other than a CM12 problem.
[Verizon Samsung Galaxy S III] kidhudi:
did you try to reboot your router turning it off for like 30-45 seconds?

i have to do that often to connect my network extender.

i have 0 issues with wifi on my phone
[Verizon Samsung Galaxy S III] sammymcalaxy:
(At the risk of jinxing this)I managed to flash today's update, and so far so good with both Wi-Fi and battery life although colors seem a little 'washed' despite live display being off.... No biggie but odd.

Did you try going in and clearing out WiFi_supplicant.conf?
[Verizon Samsung Galaxy S III] slick_shoes:
flashed the latest nightly and after a reboot, it went to deep sleep in a few mins. So far it looks like it's working as intended.
[Verizon Samsung Galaxy S III] Omegapsy:
So I an unsure if anyone else is having this issue but, I dirty flashed today's build over a fresh flag of yesterday's build and my camera is back to the old problems that were in earlier builds.
[Verizon Samsung Galaxy S III] puffingonj:
Anyone having alarm sound not playing/ settings fc when trying to change alarm sound?
[Verizon Samsung Galaxy S III] Deliquified:
I have this issue at times when first joining a network. It'll say failed to join network 5-10 times of trying, finally work, and then once it works it sticks.
[Verizon Samsung Galaxy S III] Reznor7:
Hearing this at least makes me feel a little less crazy. I'm still the only one I know of that has my wpa_supplicant file get wiped by the system from time to time, though. ?
[Verizon Samsung Galaxy S III] mastamoon:
I wonder why these WIFI issues only hit certain people though.. I havent had one issue with it.

Are you guys with wifi issues flashing a different kernel or any other mods? Somebody send me some logs of the fail happening.
[Verizon Samsung Galaxy S III] kidhudi:
I had WiFi issues a few builds ago where I had to toggle airplane mode in order for it to connect. But the recent builds seemed to have fixed it for me.

The problem I am having not is deep sleep seems to be activating but the battery life is still pretty bad

Should be getting my new phone today. Thanks masta for all you do bro.
[Verizon Samsung Galaxy S III] mastamoon:
Good luck with the new phone! Im still trying to get mine without losing unlimited. Every method I have come up with ends up costing me more money a month.. nothing is easy! lol :crying:
[Verizon Samsung Galaxy S III] kidhudi:
thanks bro... did you see the 200 dollar incentive i showed you a few pages back?

i hope it helps

maybe 1 day i will see you in the nexus forum

peace
[Verizon Samsung Galaxy S III] mastamoon:
Yeah.. going through the comcast link will kill my unlimited data.. "Your current unlimited data offering is no longer available. By Default 76375 - DATA PACKAGE 2GB/$30 offering is selected"
[Verizon Samsung Galaxy S III] sammymcalaxy:
I've spent more time than I'll ever admit trying to figure it out, and while yesterday's build seems to have cleared it up, I'd still like to know what in tarnation was confounding my doohickey. If it happens again, I'll run another log. (thought I had one, can't find it..?)

Didn't flash anything extra like a kernel, only gapps 7.xxx.

Airplane mode didn't help fix it for me, it was only in clearing out the network jazz in the wpa_supplicant.conf.... Wonder if it had anything to do with only effecting certain make/model/frequency/etc of routers/modems? It picked up the signal, just wouldn't authenticate anything with a password.
[Verizon Samsung Galaxy S III] kidhudi:
Dude what if you activate another phone with limited data. Upgrade that to a nexus or whatever you want. Then transfer the nexus 2 your number and delete the new line.

You can use my phone if you need one. I can't be more than 1/2 from you.
[Verizon Samsung Galaxy S III] mastamoon:
If you order a smartphone on a dumbphone line, you are locked into smartphone data for 2 years. Another loophole vzw smashed awhile back.
[Verizon Samsung Galaxy S III] ugachris:
Did you see this?

http://www.droid-life.com/2015/03/18/awesome-deal-verizon-moto-x-2nd-gen-in-bamboo-for-just-259/

I'm in the same boat you are.
[Verizon Samsung Galaxy S III] mastamoon:
250 for a locked phone isnt a good deal if you hang around these parts =P
[Verizon Samsung Galaxy S III] Reznor7:
I've tried only clean flashing the CM12 ROM without Gapps in case it was causing the problem, and I get the same symptoms. I don't flash anything else. I'll try and grab a log tonight.
[Verizon Samsung Galaxy S III] defTwitch:
No... no it isn't... but I'm thinking more and more I might just go that route.

Get a dev edition of something.

I TOTALLY get your wanting the newest and greatest but I refuse to give up unlimited. And I still think that nexus is just redic huge :P

Every time I try to google upcoming unlocked phones or a nice list of the newest unlocked out now that work on verizon I find the worst friggin info. Anyone got something clean and often updated with that info?
[Verizon Samsung Galaxy S III] mastamoon:
Even the dev editions of locked phones really dont get the support you would think they would. They are just different enough from the unlocked versions to not be just a quick port.

For verizon, the only phone you will always be able to unlock, guaranteed is a Nexus. No other phones, especially on VZW will be a no question unlock. Every phone release is a harder and harder root/unlock for the awesome guys who do these wonderful things. There is no saying that just because the M8 is unlockable, so will the M9.. Its really switch carriers or go nexus.. or wait until a phone has been released for a bit and see if it ever gets unlocked.

Called a VZW store nearby and asked if they would have a N6 on display tomorrow. Ill be heading there after work to check it out. Even if its big, ill probably still get it.
[Verizon Samsung Galaxy S III] defTwitch:
Yea I work right next to one... I guess I really gotta go pick (as in "heft") one up myself.

IF... I do end up buying it... it's COMPLETELY your fault and that is what I will tell my wife.
[Verizon Samsung Galaxy S III] mastamoon:
Guy at work has an iphone 6 plus... its not that big even with a stupid case on it.. with the case I would guess its the same size as the nexus6.

http://www.phonearena.com/phones/size/Google-Nexus-6,Samsung-Galaxy-S-III/phones/8626,6330

from what I can tell, its .5 mm wider and about .25 taller and thicker (than an iphone6plus).. I know you can look up the exact numbers lol. but having one on screen in front of you really shows you how big. Jujst calibrate your screen first lol.
[Verizon Samsung Galaxy S III] defTwitch:
Oh I've done that a few times already... still looks huge.

That 6plus is big and nexus isn't WAY bigger but is noticeable larger. Mostly I hate that Nexus6 is a thicker phone... I like em slim like my frappuccinos (you all thought I was gonna say women you pigs =)
[Verizon Samsung Galaxy S III] Flowah:
Just curious but are these builds on 5.1 now or not yet? I moved back to CM11 and was hoping to see if 5.1 made a big performance difference with the supposed memory leak fix and other improvements.
[Verizon Samsung Galaxy S III] MrBrady:
Just curious, if you buy a Nexus 6 at full retail, does it matter where you buy it (Google, Moto, VZW, etc)? I'm on VZW with unlimited data and will be paying retail for the N6, but I need to make sure it works with VZW.
[Verizon Samsung Galaxy S III] mastamoon:
No 5.1 yet.

Doesn't matter, all the same phone.
[Verizon Samsung Galaxy S III] Blaiser47:
Not entirely true. Phones bought elsewhere will not be on verizons white list so it may be a little tougher to activate. Google around, some people has a little trouble with purchasing elsewhere at first. Nothing you can't solve but....
[Verizon Samsung Galaxy S III] kidhudi:
just got my nexus 6

it's big.... but not overwhelming.a hair bigger then my bro's lg g3

i havent turned it on yet still have it on the charger.

cant wait to crrank it up though.
[Verizon Samsung Galaxy S III] mastamoon:
Now that it's released on Verizon, all you need to do is either request a sim or cut yours down. I you couldn't request a sim from them for it before it was released.. No it shouldn't be a big deal.

I know quite a few people with Google play or Motorola.com phones that have been on VZW for months.
[Verizon Samsung Galaxy S III] DubleJayJ:
Not sure what happened but out of nowhere Google Play Services just stopped working. I'd go into Google Play Store and I'd get the "Install Google Play Services!" or I'd swipe left on GEL and get that same message. Well I went to update it and the message disappeared but it seems as if it broke my custom font. Battery is coming up in the font and so is GEL but clock, keyboard, and settings are coming up in normal Lollipop font.
[Verizon Samsung Galaxy S III] Reznor7:
So I sat down last night with the intention of grabbing a log of my WiFi issue. I decided to manually delete the saved networks in my WPA file first. Lo and behold, I couldn't replicate the error from that point forward. I've even restored my saved ones using Titanium to see if it would start again. I've rebooted and toggled WiFi at least 50 times, and it's worked without a hitch every time. I still have no idea why, but I'm not complaining at this point. ☺
[Verizon Samsung Galaxy S III] sammymcalaxy:
It's a beautiful, confounded thing.
[Verizon Samsung Galaxy S III] mastamoon:
Check out stock camera on today's build. Thanks
[Verizon Samsung Galaxy S III] Omega Ra:
Okay, I feel dumb but, How do I get the ROMdb Dev Tool to actually update my phone. I click download, but I can't find where it downloads it to when I am in TWRP...

EDIT: nevermind, I think I found it
[Verizon Samsung Galaxy S III] kidhudi:
No love for the camera for me bro. Force closed
[Verizon Samsung Galaxy S III] Master Cylinder:
It puked! (Or maybe it farted? It made some kinda weird noise before it crapped out. :silly:)
[Verizon Samsung Galaxy S III] mastamoon:
Damn it! Lol.. I was able to take about 20 rear cam pics, 5 front cam pics and a video with stock cam today.. I dont understand what the difference in my phone and the phones that are really having a problem.

3rd party cams all work for me also.
[Verizon Samsung Galaxy S III] MrBrady:
Maybe it's the Gapps package?

When I was having camera issues with Google Camera 2.3 vs 2.4 on 4.4.4 ROMs, I had to delete the entire sdcard/DCIM folder before it would work properly.
[Verizon Samsung Galaxy S III] mastamoon:
Could be.. It looks like if you use the PA gapps.. the micro package is missing a few camera2 related files that the larger versions have. Also the gapps listed on CM's wiki is also missing these.

For you guys with busted camera2(stock cam).. can you see if your phone has /system/etc/permissions/com.google.android.camera2.xml and /system/framework/com.google.android.camera2.jar?

If they are missing... flash http://mastamoon.truelinux.net/other/camera2files_flashable.zip .. even if they are there, maybe try to flash this and see if it helps.

LMK
[Verizon Samsung Galaxy S III] bamaredwingsfan:
My camera has never worked, I'll try it. My camera will flash, but won't save the pic. I'm guessing just flash this in recovery right?
[Verizon Samsung Galaxy S III] mastamoon:
yes recovery. Can you check to see if those files exist already though.. might help in the cause.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Xml was jar wasn't, I'm flashing now.
[Verizon Samsung Galaxy S III] mastamoon:
Awesome, cant wait to hear the results!
[Verizon Samsung Galaxy S III] mastamoon:
Just ordered my Nexus 6! Tonights build mayyyyy be my last one for d2.. but really I wont have the phone till tuesday probably so maybe that will be my last one.

Invisiblek says he will provide nightly builds and zachf714 might do some also. Not sure how official nightlies are gonna work out. With invisiblek's builds, youll have to go out and grab the builds manually... I think zachf714 has a romdb account, so he might be able to use that so much of your normal routine wouldnt change.

Guess we will see!
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Jar file still not showing up, let me flash again
[Verizon Samsung Galaxy S III] mastamoon:
Hmm.. if it doesnt work, please manually extract the jar and place it in /system/frameworks.. ill check my zip. Not getting any errors when flashing right?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah it was my zip.. sorry about that.. i put frameworks instead of framework... I uploaded the FIXed version, please redownload and reinstall. You can also safely delete /system/frameworks if you want....

Sorry bout that!
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Bingo, it worked
[Verizon Samsung Galaxy S III] mastamoon:
And camera? May have to wipe camera2 data... maybe.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Took 1 pic fine, then a wide angle pic crashed the camera, but I took another vertical pic an it took, but crashed the camera
[Verizon Samsung Galaxy S III] mastamoon:
Did you wipe camera data?

Try goign into settings and setting picture size to 6.0mp widescreen... also , try touch 2 focus between pictures.
[Verizon Samsung Galaxy S III] mastamoon:
Also, was this better than previous tries to use the camera?
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Was better than previous, cause it actually works. I'll do those other things you requested in a few.
[Verizon Samsung Galaxy S III] mastamoon:
Thats good news I guess. =) Thanks for your help!
[Verizon Samsung Galaxy S III] Master Cylinder:
NOOOOOOOOOOoooooooooo!!!!!! :crying:
[Verizon Samsung Galaxy S III] mastamoon:
Haha, thanks!

Sorry, but it's time. Been sitting on this upgrade for 9 months.. Its time to burn it.
[Verizon Samsung Galaxy S III] Reznor7:
Mobile networks won't turn on for me in today's build. ?

Edit: Never mind. A reset of the APNs fixed it!
[Verizon Samsung Galaxy S III] mastamoon:
Do what I did.. Edit your addon.d/gapps script to automatically backup and restore apns-conf.xml file and flash my apns zip... If you are on VZW anyway.
[Verizon Samsung Galaxy S III] Reznor7:
Grr, the new build crashes Snap Camera on startup. It used to only crash when I had GPS tagging on.
[Verizon Samsung Galaxy S III] Prack:
Hey Masta did you get your nexus 6 yet? I've had mine for 2-3 days now and the difference between 1440p amoled from 720p pentile is insane lol. The quad core cpu and extra gig of ram ain't bad either :) Thanks again for all you did on the S3, hopefully I will see you on the nexus 6 forums soon. I still play around with my s3 so i'll be sure to follow invisblek's stuff.
[Verizon Samsung Galaxy S III] mastamoon:
Ordered today.. Will have it Tuesday! Thought the day would never come. Even though I cut my dev teeth on this phone and learned a whole lot, I'm happy to move on.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Thanks for your work Mastamoon!

Its been much appreciated by everyone here. Enjoy the N6!
[Verizon Samsung Galaxy S III] mastamoon:
Thanks man :)
[Verizon Samsung Galaxy S III] kidhudi:
dude your going to love it.

congrats
[Verizon Samsung Galaxy S III] bgorrell:
Camera status

Mastamoon, I'm loving CM12 and thank you for your efforts! It's my daily driver.

However, I lost all camera functionality with the 3/20 nightly. All camera apps are failing from the first attempt (Google, AOSP, Camera FX, etc). So, I started working backwards through the builds because I thought I had a completely successful camera in the past. As I worked back through the daily's, I found 3/16, 3/17, 3/18, and 3/19th all worked but would crash after the first "session". All builds worked the first time I took a series of pictures, but if I exited any camera and re-entered it, it would not connect. "Restart Camera" app would not work to reset it, BTW. It required a reboot.

So, I went back to the 3/12 build and all cameras are working perfectly again. I can exit and re-enter cameras at will and everything keeps working. I remember when I first installed this build and was elated. Everything since has crashed after the first use and the latest doesn't work at all. I do remember a crash or two on the 3/12 build, but "Restart Camera" also worked on that build.

Aside from that, I did check for the files you mentioned and I do not have the XML, but do have the JAR. I have not tried flashing the file you supplied yet with a newer build. Should I re-install a newer build and see if your file adds the XML, or just stick with the older build which seems to work?

FYI, since originally installing the 3/12th build, everything has been a "semi-dirty" flash. Going forward and backward for troubleshooting I only flashed the ROM and wiped dalvik/cache each time.

I see you are moving on, but hopefully the camera issues can be nailed down. Given that, I will stick with the S3 a bit longer. I'm actually overseas and this works great in Europe. No LTE, of course, but that's the whole reason I'm trying to stick it out with this phone. I'll get an upgrade when I return to the states and pick a carrier there. Wish there was an international standard for LTE.
[Verizon Samsung Galaxy S III] Master Cylinder:
Oopsie! Me too. Gonna flash 3/19 on it and see what happens, which I think worked fine. Or was it 3/18? Flashed a lot this week so now I don't remember.

---

EDIT: 3/19 works so far.
[Verizon Samsung Galaxy S III] timedroid:
What changed with the camera to fix it? Can you point to the commits?

Thanks.
[Verizon Samsung Galaxy S III] Reznor7:
Yup, 3/20 completely borked the camera for me. 3/19 is like butter. ☺
[Verizon Samsung Galaxy S III] bgorrell:
I tried 3/19, 3/18, and 3/17 and the camera only works for one "session". If I exit it and go back in it can't connect. So, I went back to 3/12 and it works perfect every time. However, 3/12 is giving me a wicked wakelock issue. It simply will not hit deep sleep. I'll try going forward to 3/19 again and report results.

EDIT: 3/19 is working perfectly now. So, a flash back to 3/12 then forward to 3/19 fixed it for me. Also, no wakelock/deep sleep issue in 3/19.
[Verizon Samsung Galaxy S III] stevet86:
I've had good luck with the 3/16 build. I cannot get any camera to work on builds after that. The battery seems to last for a good while aslo.
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=2963287]mastamoon[/MENTION], I'm just checking to see if you got the pm I sent you? I was hoping you got a chance to read it and see what you think?
[Verizon Samsung Galaxy S III] bgorrell:
Well, I spoke too soon. The 3/19 build's camera is back to only working for one "session". After exiting the camera it won't connect again. The only way to get it to work is a reboot. I guess I'll try the 3/16 build next.

EDIT: 3/16 has same camera issue as 3/19 for me. I'm going back to 3/12 one more time to validate if it has the issue or not.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Off a clean install: my first time trying this ROM (03/20/2015 build). A few thoughts.

1. Camera is broken for me. Camera [built-in] doesn't work at all ("Unfortunately, Camera has stopped").

2. Flashlight not working properly. Flashlight would come on but turn off instantly.

3. Trying to add a new WiFi connection had some difficulty. It says that it failed to save the connection. I had to keep trying multiple times to get it to save.

Other than that, everything else seems to work just fine at the moment. Thanks for a great looking ROM.
[Verizon Samsung Galaxy S III] mastamoon:
Hey guys.. not sure whats going on with the camera.. Im hoping its not something outside of our device branches cuz those are much harder to figure out.

I see the fail in the logs.. trying to get it cleaned up with the other guys..
[Verizon Samsung Galaxy S III] mastamoon:
Think I figured out the issue.. today's build should be back to only a half derpy camera vs. a full derpy camera! =P
[Verizon Samsung Galaxy S III] bgorrell:
I decided to do a little more troubleshooting. I tested all the way back to 3/12 and I consistently get one issue. The cameras (Google Camera and stock) work great after the first boot, but exiting and restarting the camera gives the "cannot connect" message after a few uses. It takes anywhere from 1 to 5 exits of the camera, but is repeatable every time on every build I tried (3/12 to 3/19). I don't know if this is the same as others experience, but it is definitely repeatable for me.

So, I found something that may be helpful! I enabled "Kill app back button" in "Developer options". This causes a long press of the back button to "kill" an app on exit. So, I tested long-pressing to exit the camera it gives the "App Killed" message. I am then able to re-enter and use the camera as many times as I like. I did it 20 times in a row. Then, I tried the regular short-press of the back button to exit and it failed to connect on the very next attempt.

So, it seems something about the camera being put in the background vs. being killed is causing it to not close cleanly and when it attempts to re-connect it gets the error. Forcing a Kill on exit fixes the behavior. I don't know if there is a way to automate this or manually kill the camera if accidentally exited without a long press. The camera does not show up as a running process (that I can tell). I had used the "Restart Camera" APK in the past, but it doesn't seem to work in recent builds. I suspect it is not the camera app, but rather something lower level that is being left in the "wrong" state when in the background vs. being killed.

The long-press to kill will make the camera more usable, but I would love to see a more permanent solution. Is there anything that can be done to automate this (pending a proper fix of course)?

EDIT: Additional info that may be needed. Freezing the stock camera makes no difference. Google Camera still loses connection after a few exits. I use PA GAPPS Stock.