yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SDQB17:
Same..I have have had good nightlies for 2 mos now....everything is working. There were a few at the beginning of the month where the battery drain was double what it should be. I am on the 7/12 and it is outstanding. I did my pool route today ( 31 pools ), I call customers during the day ( a few) and constantly check messages and facebook lol, my phone has been on since 530 am, it is now 230 in the afternoon and I am at 70%. :) Not changing this one for awhile....
[Verizon Samsung Galaxy S III] Annon2255:
Which gapps are people using? And any suggestions as to what kernel I should use?
[Verizon Samsung Galaxy S III] bill3508:
Are you guys having MMS problems. I switched to m8 no MMS, and now 7/14 and still doesn't work. Was on an older 4.4.2 version I think from June that worked.

Thanks

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] mastamoon:
Check for and disable VoicePlus
[Verizon Samsung Galaxy S III] bill3508:
Just did that and still no go.

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] bill3508:
If I use hangouts the MMS go through. Regular messaging they don't.

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] mastamoon:
Maybe you have to wipe messaging data?
[Verizon Samsung Galaxy S III] ChuckFarley:
There's a new gapps update flooding around. Has anyone updated and seen better wakelock/battery life?

http://www.theandroidsoul.com/downl...tm_source=plus.google.com&utm_campaign=buffer
[Verizon Samsung Galaxy S III] ChuckFarley:
Wow, things got quiet here! Is that a good or bad sign? I stepped away from cm for a moment for the 4.4.4 bugs to work out, but I'm missing it already...
[Verizon Samsung Galaxy S III] sanjsrik:
on the 12/10 nightly, is anyone having an issue with the wifi just simply not working? I've restarted, pulled battery, turned off/on wifi, airplane mode off/on, nothing seems to get the wifi to work.

Any help/ideas would be most appreciated.

Is it a matter of flashing the 12/11 nightly?
[Verizon Samsung Galaxy S III] Defragger51:
I am on the 12/11 build ,Just checked mine and its working fine, blue tooth is acting wonky. did not see any wifi changes in 12/10 change log but did find this one for blue tooth, " 32 bit int shifted by an amount not in the range -31..31 (FindBugs) "no idea why they did not take it out in the 12/11 build
[Verizon Samsung Galaxy S III] sanjsrik:
thanks, dumb question. has everyone been clean flashing the nightlys or are they dirty flashing (wiping cache and dalvik only) when installing nightlys? The last few nightlys after the initial one I've been doing the dirty flash through the CMupdater within the phone.

I have read some say clean flash and wipe complete but on previous builds for 10.1, I just did dirty flashes.

Thanks in advance.
[Verizon Samsung Galaxy S III] Defragger51:
I did a dirty flash from 12/9 to 12/10 and that solved the horrible battery life I was getting on a clean install of 12/9. I did a dirty flash this morning to 12/11 with out issue , still have great battery life but it did not solve the blue tooth problems from 12/10.
[Verizon Samsung Galaxy S III] lou1210:
Dirty flash is just clearing system and dalvik. Right?
[Verizon Samsung Galaxy S III] p2kmafia:
you are correct
[Verizon Samsung Galaxy S III] annoyingduck:
Sorry, free thanks for you! But yes that is a dirty flash. A clean flash adds wiping data + technically wiping system as well. If you update through the cm updater, the correct wipes are built into the script. You don't have to do anything! But I like to use the updater to download the nightly and manually flash so I can add back supersu, which I prefer over the open source su.
[Verizon Samsung Galaxy S III] lou1210:
OK so clear system and dlavik cache, flash new ROM and su zip file and I should be good?

I came from an unofficial copy of 4.4 and went to the 12-8 nightly and in the process lost my imei info. If I dirty flash, I won't have that problem right?
[Verizon Samsung Galaxy S III] annoyingduck:
No! Dirty is dalvik + cache only. Clean is data + dalvik + cache + system. If your coming from an unofficial I'd clean flash it. Once you've clean flashed the official, you can then dirty all the nightlies.
[Verizon Samsung Galaxy S III] lou1210:
Yes. I'm sorry. I meant system cache and dalvik cache. I'm currently on cm11 nightly 12-8 and read that 12-11 battery life is better. So I was going to dirty flash. Wanted to be sure I had it right. So I should not have to reflash gapps and the su update or will I have to re-add the update? Thank you very much for your time and help. I just want to make sure I don't mess up my imei, I won't be near a computer I can Odin with for several hours, should it happen.
[Verizon Samsung Galaxy S III] annoyingduck:
Supersu you'll need to flash again, as the initial flash of the ROM will wipe the system. Gapps however, do not need to be reflashed as the rom/gapps packages include updater scripts that prevent them from being wiped on a dirty flash
[Verizon Samsung Galaxy S III] senorbuck:
Ya, it's annoying. Wonder if it's an Instagram thing or something that needs looked at. I'd assume Instagram supports Android 4.4...?
[Verizon Samsung Galaxy S III] muiriddin:
On mine wifi will not turn off. Basically it will toggle off, but the battery info shows that it is still running and analyzing things with BetterBatteryStats shows that it is still draining battery. So yes, you are not the only one who has noticed some strange behavior with wifi on the 12/10 nightly. I am going to try bringing down the 12/11 one to see if it resolves things.
[Verizon Samsung Galaxy S III] tekhna:
Anyone's LTE unusably slow in the newest nightly? Wiped coming from an older unofficial nightly and everything was normal, now it's more or less unusable.
[Verizon Samsung Galaxy S III] AlphaXray:
Sorry to ask a dumb question, because I know it's been answered. But in order for us to get the dialer that actually performs local searches we do have to load a GAPPS other than the one that was provided in the original post of this thread correct? Any suggestions on which GAPPS is the best one to load for this?
[Verizon Samsung Galaxy S III] titanshadow:
Mine seems perfectly usable but I'll do some testing tonight and post again. Can you describe what kind of bit rates you're getting?

---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------

Does anyone know an app that integrates with Tasker and can turn the menu and back buttons off? I know this is a bit off topic but I can't seem to find one so, I hope no one minds.
[Verizon Samsung Galaxy S III] lou1210:
Download the paranoid android gapps zip file. You can search the forum for it.
[Verizon Samsung Galaxy S III] jhanford:
Is your wifi working now? Mine shows nothing
[Verizon Samsung Galaxy S III] tn_volfan:
Not sure if this will help, but I noticed in the battery stats that my wi-fi showed it was always on even when it was supposed to be off. Then I noticed in the wi-fi menu there is an advanced setting to "Let Google's location service and other apps scan for networks, even when Wi-Fi is off". After unchecking the box I no longer have the issue. Hope this helps.
[Verizon Samsung Galaxy S III] muiriddin:
That was what I just found and was the source of my issue. The 12/11 nightly also had the issue was my first clue... Thanks for posting, even if I had just found the same setting myself.
[Verizon Samsung Galaxy S III] Hybridnoob:
Everything's fine here! Latest nightly and no complaints.
[Verizon Samsung Galaxy S III] Tbenson:
Just a quick question. Just replaced my wife's phone with a new sg3 since the last one broke. She got it and updated before I was able to get home and do what I do with all the phones and flash cm.

Is it possible to install CM on it with the updated i535vrucnc1 firmware?

On CM's wiki the warning explicitly states that it must be on 4.2.2 or older. Does anyone know?

#CM WARNING ON WIKI#

Additionally, you must be a 4.2.2 or older build or this will not work. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.

Thanks for anyone's help.
[Verizon Samsung Galaxy S III] Hybridnoob:
Sorry, she's stuck with a locked bootloader.
[Verizon Samsung Galaxy S III] Tbenson:
Booo. Thanks for the reply. I just was looking on this thread (http://xdaforums.com/showthread.php?t=1788313&page=134) and saw the same response.
[Verizon Samsung Galaxy S III] funkpod:
Hey, ever have any problem recording video during a live concert? My phone on AOKP gets CRAZY distorted. I'm not up super close, either. Don't know if it's my ROM or my phone. Thanks!
[Verizon Samsung Galaxy S III] MartyMacGyver:
So I'm running 7/14 and this is getting ridiculous. Phone was fully charged. I take a few flash photos (maybe 10-20 total) and it just... dies. doesn't reboot, just dies. Hold the power button and it comes back with... 41% battery left (battery stats conveniently went missing too - WTH?

Earlier today it was at around 70%. Took some photos outside (no flash), wandered a bit and it suddenly dies. Reboot and in the span of those 3 minutes the battery is at... 10%. Battery stats show the precipitous drop from around 45% to 10% in those 3 minutes.

I don't think it's me here, and for the battery to tank during a quick reboot is kinda ridiculous. Bad battery? Bad build? It doesn't make sense, nor do the random reboots.

And no, it's not wakelocks at this point... it's just plain weird.

Update: I used it for a bit more unplugged and it barely drained at all (got down to around 40%). Then, figuring I'd throw the old battery in it (maybe the new one is bad?) I shut it down... then deciding I wanted the battery topped off before pulling it I plugged it in to charge it while it was "off". Lo and behold the boot-time animated charging screen says it has 64% charge! So now I'm thinking something is going hella wrong with the battery monitoring and stats code in normal operation and that the battery itself is fine (a normal full reboot will show some drop in battery life - while this abnormal shutdown thing comes back with weirdly low battery levels).

Update 2: Updated to the 7/18 build and things seemed fine all night in airplane mode starting at 75% charge. Woke up, used the phone for a while and it was down to ~20% when it suddenly powered off. Plugged it in and it claims 0% battery (pre-boot charge screen as above). Noticed that for 7 hours the battery level was virtually flat... that should've dropped overnight.

Is this happening to anyone else? Is there a stable version of CM11 around?
[Verizon Samsung Galaxy S III] bmeek:
CMupdater won't run for me on the 07/16 build. Anyone else seeing this?
[Verizon Samsung Galaxy S III] thelangosta:
How old is your battery? When these batteries get old they sometimes have huge percentage drops for no reason.
[Verizon Samsung Galaxy S III] MartyMacGyver:
It's a couple of months old actually, and it is OEM, but yeah, it's a suspect too. But the lack of any appreciable battery level change over some 7 hours idle suggests a software issue (since the voltage sensors are on the phone side). Not sure what to make of it - about ready to kick it to the curb.
[Verizon Samsung Galaxy S III] thelangosta:
Sounds like it's time to wipe everything and start over.
[Verizon Samsung Galaxy S III] MartyMacGyver:
Spending hours wiping and then re-configuring every single app, login and password is great, if it's actually effective, but it doesn't appear to be helping others who have come across this kind of problem. This isn't about some random app drinking battery (except apparently the wakelock bug baked into Play Services, since nerfed to prevent wake-and-bake-the-CPU problems). This is about the battery stats not being read or tracked properly, and while I'm going through the "calibration" process now FWIW I don't expect much from it.

Perhaps it's bad build(s)... which begs the question, what recent build of CM11 is objectively considered "good" (the recent snapshots/milestones have tended to be worse than the nightlies immediately surrounding them)? It'd be great to be able to say, no, it's not the build, or yes, file a bug, but it's nightlies and so that's not an option either. I'd roll back to 10.2 if not for the fact it's dead and had a habit of rebooting randomly (among other bugs).

I'd even consider going back to the stock ROM but... I tried that back when I tried CM10.x for a short time, then tried to roll back, full wipe and all, and the camera refused to work with the stock rom anymore. Now it only works with CM (moving to CM10.2 appears to have altered my camera firmware, because it works with CM but stock will *not* detect the camera - thoughts?)

I'd look forward to a stable CM11, but will CM11 ever stabilize? CM10.2 started to stabilize and then was dropped in favor of CM11, and that's been the pattern since CM7. Are there better alternatives?

I'll play the full wipe game at some point, but again, I'm trying to see if this is a known issue. I wasn't alone with the Play wakelock bug, and this battery stats thing (leading to sudden shutdowns) doesn't seem to be entirely novel either.

Update: It took about 5 hours of monkeying around (mainly ensuring complete backups, reauthenticating to dozens of accounts, restoring lots and lots of settings, and as usual the launcher is in some random new configuration) but it's right back were it was. Remains to be seen if this will have any effect on the battery stats problem though.
[Verizon Samsung Galaxy S III] bmeek:
fyi, I manually updated to the 07/19 nightly and cmupdater is functional again.
[Verizon Samsung Galaxy S III] MartyMacGyver:
So... once everything was reinstalled the battery life seems to be better, but the "cliff" around 10% is still there (it might be a calibration thing or a bad battery).

Learnings:

My relatively new OEM battery may be flakey - or phone battery stats are somewhat buggy. [Update: I ordered an OEM EB-L1G6LL battery shipped & sold by Amazon... might help.]

Google Play Services seems to be wakelock-happy lately. Disabling those wakelocks in the Privacy Manager seems to help.

Bejeweled Blitz - which I don't use that often lately - likes to keep an audio wakelock going (background hiss even when it's not in the foreground). Uninstalled... oddly, this wasn't a problem on this phone til recently, and perhaps only since I moved from CM10.2 to CM11 (while another phone - rooted HTC X with stock Android 4.0.3 - routinely experiences this problem).

Reimaging the phone (wiped system, cache, and data first) seems to have stabilized a couple of unrelated things but had little effect on this issue.

BetterBatteryStats is handy but would be much handier if it periodically saved *all* its logs... not much help if the phone shuts down in the middle of the night because something wakes up and drains the battery.

GSam Battery Monitor helped narrow things down more exactly, and I could quickly see the audio out wakelock. Not saying either is amazing as-is, but the sum total of information was useful.
[Verizon Samsung Galaxy S III] bill3508:
On 7/14 not having any problems. Nearly 5 hrs sot yesterday but I'm running kt747.

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] althornin:
For what it is worth I doubt it's your battery. I have the same problems. Seem to be ok on the 7/19 nightly. I can go back to the 6/8 nightly and have no issues so I know it isn't my battery.
[Verizon Samsung Galaxy S III] MartyMacGyver:
Yeah... it's not drinking it as heavily but it's still drinking, and I think it's at the OS level now (having removed the other offenders). I'll update to 7/19... couldn't hurt if it's working for you.

It's odd that Bejeweled did what it did... that was never a problem for me on this phone before and that app may have been working fine until I went and reimaged it.
[Verizon Samsung Galaxy S III] rhcreed:
screen mirror to chromecast?

anyone have any luck making this work for us?
[Verizon Samsung Galaxy S III] dmginc:
Make what work for who?
[Verizon Samsung Galaxy S III] cobija:
I have had this issue in the past but finally thought about asking it here. In older builds of CM, there was a way to change the location of the clear recents button. I know i could use gravity box and have one somewhere else, but then there would be two clear recents buttons. Does anyone have any insight on this? I looked through every menu option.
[Verizon Samsung Galaxy S III] thefuzz4:
Just quick question for Colorado what modern should I be on having terrible signal issues. Thanks
[Verizon Samsung Galaxy S III] rhcreed:
Screen mirroring to chromecast from s3 running cm11..
[Verizon Samsung Galaxy S III] esjames:
Has anyone tried the latest nightly? Is it pretty solid?
[Verizon Samsung Galaxy S III] sbenson1226:
I'm wondering the same. I haven't checked in on CM11 for the S3 in a while. Are there still the usual issues with the front facing camera and third party camera apps?
[Verizon Samsung Galaxy S III] bill3508:
On 7/20, no problem so far.

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] rhcreed:
screen mirroring

http://xdaforums.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193

would love to see this feature integrated into the base rom.. anyone know how to contact the devs??

thx!

http://xdaforums.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193

(see red text in 1st post)
[Verizon Samsung Galaxy S III] MartyMacGyver:
A bit of a followup: I ended up getting yet another battery from Amazon (appears to be OEM with the correct NFC antenna and all) and will be swapping that in. My original battery is still decent and I had to swap it in today because, at around 50%, the phone started just dying randomly. I learned to spot a fake and as far as I can tell (including entirely removing the label on the one that keeps acting up) they are all OEM. The one that's been acting up, though, turned out to be a wee bit "bulgey"... so that one will be going bye-bye.

Thanks to everyone for the responses to my posts! I managed to learn a lot more than I expected to and may have saved myself from a major battery failure.
[Verizon Samsung Galaxy S III] Akagami:
For anyone having navigation issues try mf1 firmware flash from Mastamoon's page and updating past 16th nightly. Seems to have fixed it for me.
[Verizon Samsung Galaxy S III] mastamoon:
This file already exists in the build.
[Verizon Samsung Galaxy S III] chowner:
linky link?
[Verizon Samsung Galaxy S III] althornin:
Anyone else still having no notification sounds after you connect to a Bluetooth headset and then disconnect?

I ride my motorcycle to work and every morning notification sounds won't work after I listen to music via Bluetooth on the way to work. Same with the way home.

I have to restart to get sounds back.
[Verizon Samsung Galaxy S III] mastamoon:
Do you use any sort app to kill notification sounds while streaming? An app like "don't pause"??

I have this happen often when using the app, but when I don't use it, I never have the problem.
[Verizon Samsung Galaxy S III] althornin:
Hrm. I am using Tasker to set the phone to" silent" and start the music automatically when it connects to the Bluetooth headset, and does the reverse on a disconnect. This has always worked before (by that I mean since Gingerbread version of Carriage across various phones). . The notification sounds problem has been happening for a couple months iirc.

What else can I use so that my ride is uninterrupted?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah that's it then.

Something weird is up with kitkat where it doesn't realize the stream has ended or something. Same reason why the lock screen music controls don't go away on disconnect like they used to.

Maybe you can use tasker to do like a hot reboot or something. I actually installed tasker last night because I thought it might be the don't pause app I use to automatically kill notification sounds when a stream starts.
[Verizon Samsung Galaxy S III] bmeek:
My big gripe along these lines remains the lack of an option to hear regular volume notifications and ringtones from the handset while a Bluetooth A2DP device is connected with media audio routed to the device.

By default, TouchWiz ROMs let you hear your phone ring if you take off your headset without turning it off....
[Verizon Samsung Galaxy S III] bill3508:
Kt747. 5 hrs sot running smartassh3 and sio.

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] aromig:
Wifi gets stuck turning on with the 7/24 nightly. Reverted to 7/23 and works fine again.

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] Hybridnoob:
WiFi works fine here on 7/24.
[Verizon Samsung Galaxy S III] aromig:
Good to hear, might try a clean flash tomorrow then.

Sent from my GS3 running CM11, via FapDaCock
[Verizon Samsung Galaxy S III] althornin:
So I tried using Tasker to set the notification volume to zero and then back up to 15 when bluetooth disconnects - same problem.

This is just stupid.

---------- Post added at 06:45 AM ---------- Previous post was at 06:43 AM ----------

Using stock Kernel?

I'm curious because if you read the changelogs, it looks like some major kernel changes have happened regarding modules. I typically use Lean Kernel, but I am wondering if it will have issues with the 7/24 nightly.
[Verizon Samsung Galaxy S III] mastamoon:
This^... 3rd party kernels will have to play catch up due to the wifi changes tha were pushed.

Does your phone also become super laggy when the no volume thing happens? Mine does. Also, have you tried just manually lowering the volume before streaming and seeing if that also breaks?
[Verizon Samsung Galaxy S III] althornin:
Most things on the phone run fine when the no notification/volume thing happens, but some things are intensely slow. Like trying to change the volume - it takes multiple seconds for each movement of the volume slider. Basically, anything that has to do with audio gets very bad.

Hear is the interesting part: I have Tasker set up to make my phone silent when I set it down face down (an undo it when it is no longer face down). This causes no problems (showing the silence issue is linked to Bluetooth). However, if I experience the above problem, sometimes, setting the phone face down for a while (5+ minutes) will fix the issue.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I have noticed the slowness on volumechange also. Im guessing its the combo of bluetooth and audiostream and volume that is the issue. I wonder if its a timing issue... maybe if the trigger lowered the volume before bluetooth connected would work, or lowered the volume after. So if you base the trigger on launching of an app.. have it do one before the other?
[Verizon Samsung Galaxy S III] althornin:
Well, that would require actual effort on my part... :)

The whole point of using Tasker is to automate things so I don't have to do them. I turn on bluetooth on my motorcycle helmet, and Tasker does the rest - silences notifications, starts the audio application, auto replies to text messages, reads text messages from my wife to me, etc.

I take the helmet off and turn off its bluetooth, and Tasker stops the music, turns the volume back up.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I totally agree. But sadly, some things require a work around especially when the phone ages and you dont have a full team working on the device anymore to tackle weird issues like this.

So if you could deal with basing the task on launching an app instead of the bluetooth connection, maybe a fix can be had with very little additional effort. Im basically thinking out loud here for my own good also.. I want this to work as much as you do. I like getting into my car and having everything ready to go without my input, but you do what you gotta do :)
[Verizon Samsung Galaxy S III] rhcreed:
everything working clean on cm-11-20140724-NIGHTLY-d2lte.zip ??

been hearing chatter about bad battery life and some issue with recent nightlies.