yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Jaegermeiste:
I've noticed more consistent connection to LTE and improved WiFi connection. Of course, it might be completely in my head.
[Verizon Samsung Galaxy S III] Darryl Henley:
on 0611 compass does not work. went back to 0609 and compass is working.

anyone else having this problem?

EDIT:

new quickpanel setting seems to enable the compass but apps can't access it.

also, display settings force closes.
[Verizon Samsung Galaxy S III] lakingslayer:
My display settings FC also.
[Verizon Samsung Galaxy S III] Master Cylinder:
I haven't been able to get mine to FC, on 6/11 or 6/12. I'm not using Google Experience Launcher, if that's what you're using. Don't know why that would make a difference, though. Got any other non-standard items installed? I've got Xposed+XBlast+XHalo floating windows but not having any problem. Did have occasional systemUI FC when bringing up XBlast setup but haven't noticed it on 6/12 yet.
[Verizon Samsung Galaxy S III] billquinn1:
The earlier build was just as bad. Maybe something with Verizon. I'm going to try a stock ish Rom today just to see.
[Verizon Samsung Galaxy S III] bobloblaw1:
I've ended up settling back on stock for the same reasons ubfortunately. I keep getting stuck on the 1x/3g/4g handshake on aosp. On stock its fine. :(
[Verizon Samsung Galaxy S III] Zacharybinx34:
I still get problems with Netflix losing audio.

---------- Post added at 05:21 AM ---------- Previous post was at 05:20 AM ----------

Also hangouts video chat being laggy and freezing up.
[Verizon Samsung Galaxy S III] Hans5849:
Well, my S3 died yesterday. It looks like there's a problem with the power button microswitch, it's reading presses when I'm not touching the button. Looks like I'm off to the HTC One (M8).
[Verizon Samsung Galaxy S III] chadamir:
Anyone else finding the in call volume too loud? I feel like I'm going to blow out my eardrum
[Verizon Samsung Galaxy S III] Hans5849:
Also looks like there's a new gapps 2014-06-06
[Verizon Samsung Galaxy S III] dmginc:
mine is loud and basically inaudible. Just sounds like muffled mush most of the time now.
[Verizon Samsung Galaxy S III] chadamir:
Glad it's not just me. Hopefully there will be a fix soon.
[Verizon Samsung Galaxy S III] Master Cylinder:
I wonder what there would be to fix if it's not a common problem? I don't have it. I wonder how common it is? I guess one could look on the cm11 nightly forum and see if there are a lot of complaints about this.
[Verizon Samsung Galaxy S III] Whisk_33:
I had the same problem. I was able to get it fixed by a vender on eBay. It was about 15 bucks plus doing to NJ. It works great now. PM me of you can't find it.
[Verizon Samsung Galaxy S III] mikejr83:
You can try looking at /etc/snd_soc_msm/snd_soc_msm_2x and adjusting the earpiece values. We made an adjustment in that file for low speaker volume some time back. If you can find an acceptable value report back. Masta may be able to get it into a build so we all can test it.
[Verizon Samsung Galaxy S III] Whisk_33:
I have been having issues with Apollo ever since the 4.4.3. If I remember correctly, this used to be a problem back in the day. Anyone else experiencing issues in Apollo? I'll be trying a clean install if I'm unable to find an alternative solution

The issue I'm having is when I am Using Apollo the sound stutters every minute or so when the screen is off. Its really annoying.
[Verizon Samsung Galaxy S III] Master Cylinder:
Has anyone seen the problem of not being able to interact with one's voicemail after automatically logging in? If I set up my voicemail number to include a couple of commas and my code, it enters it fine, with very long tones, but I cannot make selections after that like to delete, save or replay a message - the pad makes a very quick tone but the signals are not received.

If I eliminate the automatic pin code entering, then I enter it manually and I can also interact normally with the remote voicemail server. I don't know how long this has been going on but it's been awhile - since before 4.4.3 at least.

Come to think of it, this may have been happening on my 4.3 TW ROMs, too! Maybe it's a ML1 issue?
[Verizon Samsung Galaxy S III] dmginc:
no issues here. sounds like something specific to you.
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm special!:angel:

-------------------

PS - I am really getting the best battery life of any ROM I've ever run!
[Verizon Samsung Galaxy S III] goatman101:
Anyone running Masta's new 6/23 build? How is it running?
[Verizon Samsung Galaxy S III] mastamoon:
I am! ☺
[Verizon Samsung Galaxy S III] sjpritch25:
I too am getting really good battery life. Here are my settings
[Verizon Samsung Galaxy S III] Master Cylinder:
Ha!!

I'm running it - no problems, but, it's only been out 4 hours.... Still, these builds have been great with great battery life!:good:
[Verizon Samsung Galaxy S III] goatman101:
June 12 build? Is there a reason why you did not update to current build?
[Verizon Samsung Galaxy S III] jlokos:
I've had that on almost all of the AOSP roms I have used. Is not a problem on TW roms when I used to use them.
[Verizon Samsung Galaxy S III] sjpritch25:
I was happy with that build & getting great battery life

---------- Post added at 07:38 PM ---------- Previous post was at 07:37 PM ----------

I dirty flashed 6/23 build & Pandora & pulse kept f/cing. Restored back to 6/12

---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------

I was happy with that build. Honestly , I don't flash every build. I use my phone for work, so I need it working on all cylinders
[Verizon Samsung Galaxy S III] ef-civic:
My phone boot looped yesterday when I tried to do a dirty install from 20140426 version. Anyone else have problems?
[Verizon Samsung Galaxy S III] iamrazor:
No boot loop issues here on a clean install. However, I am noticing the power button is uber sensitive. Is it me or has anyone else experienced this?
[Verizon Samsung Galaxy S III] fromthesticks:
I've had power button issue before but nothing lately

No boot loops with me
[Verizon Samsung Galaxy S III] zcmack:
i've been having serious power button issues (lots of random reboots) and am thinking about jumping ship. sorry to derail the topic a little bit here, but does anyone know what phone they're moving to next?
[Verizon Samsung Galaxy S III] Whisk_33:
I don't know if you should move. My power button was broken for a bit and I got it fixed from a vendor on ebay for about 15 bucks plus shipping. It was an awesome fix and my phone has completely new life. Just saying.
[Verizon Samsung Galaxy S III] zcmack:
have any details / a link to the seller?
[Verizon Samsung Galaxy S III] bobloblaw1:
I'm also interested if you could give some details. Currently I've been using Xposed Additions to ignore all power button presses.
[Verizon Samsung Galaxy S III] zcmack:
i'm not sure if the power button is the cause for my issues or what.. i get frequent random reboots.. it happens when opening different apps or sometimes just when the phone is sitting in my pocket. i figure if it was a power button issue, i would see the advanced power menu before it shuts off, but no dice. in addition, the phone will constantly reboot and show the samsung splash screen until i hold power or pull the battery to turn it off and then turn it back on again. no issues booting after that.

i tried clean flashing the latest nightly and that didn't help, then tried an old backup and the behavior continues. it actually did it once when i was in recovery doing a restore, so i'm about ready to rule out a software issue. for what its worth, i also opened the phone up and made sure ribbon cables were tight and the power button wasn't gunked up (this was a previous fix when i had power button issues).

i think shes a goner... i'd like to keep my unlimited data, so i've been browsing for a used S3 on craigslist. from what i can tell, the S4 is still locked down.
[Verizon Samsung Galaxy S III] droidxxxxx:
Couldn't get data to turn on..but all my info was there
[Verizon Samsung Galaxy S III] fromthesticks:
I don't think is your phone, in the past week my s3 has gone from reboots once in awhile to this morning it was just shutting off complely every 5-15 mins, every time I went to use it it would just go black, I uninstalled the newest google apps that were from L and wiped cache and dalvik, but the same thing continued. Applied today's build just after masta posted and I've had 1-2 shutoffs since. But none in the past 3 hours.
[Verizon Samsung Galaxy S III] mastamoon:
I have like 0 issues. Wonder why you guys are having such a hard time.
[Verizon Samsung Galaxy S III] fromthesticks:
I've had little issues until Thursday or Friday, may be some of the L apks I insta lled. Up until then I had been as steady as this phone has ever been. Thanks masta for helping my phone out, after this month my 2year contract is up, bought an unlocked lg phone for cheap until I find out what the next phone is gonna be, hopefully a new nexus in the coming months when lollipop is released, until then thanks again.
[Verizon Samsung Galaxy S III] RRF12:
I have zero issues running great for me everything works.
[Verizon Samsung Galaxy S III] Master Cylinder:
No issues here either.

However, I went back to 6/19, the last 4.4.3 build, because the battery life for me was 20-30% better on those builds than anything before or after. Haven't tried 6/30 yet, but my uninformed opinion is that those 4.4.3 versions worked better on my phone - System, Android System and System UI services all running 1/2-1/3 less CPU usage (watching OS Monitor) than any other ROMs.
[Verizon Samsung Galaxy S III] zcmack:
just for the hell of it, i flashed the recommended recovery and tried updating to the latest build. my phone won't connect to verizon data (3g or LTE). i have everything installed as per the first post in this thread, so i'm not really sure where to turn. all of my numbers are showing in the about phone status screen and restoring from an old backup (3/11) seems to function as expected.
[Verizon Samsung Galaxy S III] droidxxxxx:
Same for me..except I used the newest TWRP recovery..
[Verizon Samsung Galaxy S III] jonny30bass:
No 3g or LTE 6/30 build

I don't seem to have any data connection using 3g or LTE on the 6/30 build. I was on ML1 modem, then i flashed MF1 firmware and have the same issue. Before this build I was on the 6/20 build and was also having connection issues. On 6/20 if I were to be connected to wifi and then leave the wifi broadcasting area, it would not automatically connect back to LTE (only 3g). I had to toggle airplane mode on and off to get LTE back.
[Verizon Samsung Galaxy S III] Whisk_33:
My power button was actually broken. You could go into recovery and see that when you pressed it, tens of presses and holds were registered. A vendor named "gamepartsstore10" fixed it for me. You can just search "Power Switch Button Repair Service for Samsung Galaxy S III gamepartsstore10" on google.

This issues some of you have been describing doesn't sound exactly the same.
[Verizon Samsung Galaxy S III] Hans5849:
I used this guy too, my fixed phone should be arriving shortly
[Verizon Samsung Galaxy S III] BrwnSuperman:
I'm stuck on 3g. What APN do you have selected?
[Verizon Samsung Galaxy S III] mikejr83:
Is anyone else experiencing major wakelocks? It seems like my phone is not going into deepsleep like it should. I killed some update service related to Google services but it still seems bad.

Attached is the current wakelock that I'm trying to figure out.
[Verizon Samsung Galaxy S III] mastamoon:
Mine is sleeping like a boss.
[Verizon Samsung Galaxy S III] Master Cylinder:
Ooh! I'm loving what I'm seeing on thie 7/2 build. Like to see those main system services purring.
[Verizon Samsung Galaxy S III] CrucialBT:
I'm also experiencing severe wakelocks from Google play services the moment. I'm not sure what the deal is the moment. But it seems to have started a several days after flashing a newer version the Rom, so i don't suspect the Rom to be the cause.
[Verizon Samsung Galaxy S III] mastamoon:
Check the version of your google play services... Here is 5.0.84 from my phone, Im not having any wakelock issues. Phone is sleeping fine. http://mastamoon.truelinux.net/other/google_play_services_5_0_84.zip
[Verizon Samsung Galaxy S III] CrucialBT:
That's the exact version I have well. I rebooted and cleared the cache. We'll see what happens.
[Verizon Samsung Galaxy S III] mikejr83:
I used "Disable Service" from the Play Store, went to System Apps, found Google Play Services, then found SystemUpdateService, and checked the checkbox. That seemed to kill the biggest wakelock for me. I have one wakelock called "DirectTrack" that I can't figure out. Seems to be media player related? IDK.

Battery life today wasn't bad, but I seem to remember it better. I went to a much more conservative KT747 setup, but I'm still not happy with how the batter life should be. With the three day weekend it may be time for a good cleaning and a very conservative installing of apps to see if I can pinpoint the issue.
[Verizon Samsung Galaxy S III] Byonik:
FYI for anyone thinking about kicking the tires, 7/02 is working great for me. My first time on a non-TW ROM in a few months, and this has basically been rock solid for the last 2 days.
[Verizon Samsung Galaxy S III] Master Cylinder:
Bug Reporting?

Does anybody know what to do with a bug report? I generate a few a week. Is there a use to anybody for them?

Yesterday I had a reboot while looking at some pictures using QuickPic, generated a bug report. It's got great info - a lot! Almost 10mb of text data.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well! My bluetooth works with my Jawbone but not my Jabra! At least it shows that it can work - I'm on 7/3. I'll have to test these others on another phone to see if they'll connect.

Woops! The Jabra works too! Got it figured out - Bluietoothing no problems! (No external speaker/car system to test at the moment, though.)
[Verizon Samsung Galaxy S III] olm3ca:
The 7/3 nightly is performing really well for me - great battery life, too. I had one random reboot so far but I'm not worried about it.

The main issue for me is SMS - they get stuck but not consistently. I read the OP and understand the required steps for the SMS fix that other folks have taken, but I think this is related to the security settings for the annoying "SMS Message Limit." Some people report changing System Settings => Security => App Security => SMS Message Limit from 30 (default) to "none" but that just gives me an annoying message to allow Hangouts every time I want to send a text. That can't be the solution. I also tried 200 instead of 30 and that didn't help.

I don't text that much but have noticed that if I try to send more than one or two per hour they get stuck and I have to put the phone on airplane mode and then off again for them to send.

My question is this: Am I really dealing with the same old SMS issue that everyone else had, or is this just related to this SMS Message Limit thing? Or something to do with Voice+? Someone mentioned going to Settings -> more -> voice+ -> disable, but I don't see that option. I don't use Google Voice.

I am on the dreaded ML1 modem and read all of the months of back & forth about the SMS fix required for CM11-based ROMs. I really don't think this is it, though. Could someone let me know? Thanks in advance!
[Verizon Samsung Galaxy S III] capt730:
I had the 1 sms issue where one would send and nothing would send after that. I flashed the MB1 AIO and been smooth sailing since.
[Verizon Samsung Galaxy S III] Master Cylinder:
Hmm..., I did think this problems was over with. You could disable Blacklist - that was one thing. Another remedy was to try a different SMS client. 8sms is a clone of stock with a couple extra features. I like Handcent - extremely customizable with themes, plus scheduled messaging. It's very easy to switch default SMS clients without having to uninstall anything.

PS - I've never had even a hiccup with ML1.
[Verizon Samsung Galaxy S III] mastamoon:
OMFG ---- CENTER CLOCK YA'LL!!!

:silly:

http://review.cyanogenmod.org/#/c/67606/ & http://review.cyanogenmod.org/#/c/67607/

:highfive:
[Verizon Samsung Galaxy S III] neolink1:
Cool... But, more than anything thanks for your continued support for this phone... My upgrade isn't due until next month, and you've made this phone awesome all this time.
[Verizon Samsung Galaxy S III] Unoid:
I'm totally diggin this rom.

I'm pissed CM gave up on the verizon GS3,

Thanks for the great work. this rom is FAST and rocks.
[Verizon Samsung Galaxy S III] razorloves:
WAT? lol
[Verizon Samsung Galaxy S III] Unoid:
I've always gone here for VERIZON gs3 downloads that are CM.

https://download.cyanogenmod.org/?device=d2vzw

They stopped updating there in feb. There's also no message there saying it's continued elsewhere.
[Verizon Samsung Galaxy S III] HankStorm:
You need to go here.

https://download.cyanogenmod.org/?device=d2lte
[Verizon Samsung Galaxy S III] ugachris:
There actually was an announcement made:

http://www.cyanogenmod.org/blog/unified-builds
[Verizon Samsung Galaxy S III] greekstile:
Stock Browser Issue

Anyone else getting SSL errors in the stock browser while trying to browse secure sites?

There is a summary of the issue here.

http://forum.slimroms.net/topic/2362-weekly-build-510-native-browser-error/

I've had this problem since the Android version was updated to 4.4.3.
[Verizon Samsung Galaxy S III] fromthesticks:
Nope, not having that problem, I disable stock browser and install chrome, but haven't noticed
[Verizon Samsung Galaxy S III] Master Cylinder:
Hoora for 7/9! 7/7 systemUI fc'd and restart every time I implemented a theme. But, since 7/3 80% of my themed elements disappear a couple of times a day. We'll see how this one holds up. :cyclops:
[Verizon Samsung Galaxy S III] CrustyMcLovin:
Yeah I agree, 7/9 is working great for me. I had been using the official CM11 for a while but had constant problems with mobile data and GPS so I'm back and couldn't be happier (at the moment!)
[Verizon Samsung Galaxy S III] greekstile:
Yeah, Chrome works fine. But not all of us like Chrome. U much prefer the stock Browser.

Anyone have any ideas?
[Verizon Samsung Galaxy S III] razorloves:
is this the same problem you're having?

https://jira.cyanogenmod.org/browse/CYAN-4572
[Verizon Samsung Galaxy S III] greekstile:
Yes, that's exactly the issue. Hopefully this is fixed soon. I'm surprised nobody else has mentioned it here. Its been broken over a month now.

Masta, any thoughts?
[Verizon Samsung Galaxy S III] mastamoon:
As far as I can tell, these patches already exist.

Ive had instances where chrome just wont load a website, period.. jump over to stock browser and it works fine. Annoying but im over it :P
[Verizon Samsung Galaxy S III] greekstile:
That's just it though. Its the stock browser that has the issue. Chrome works fine. Stock browser basically cannot load any https website and it causes other issue with Gmail, search, etc.
[Verizon Samsung Galaxy S III] razorloves:
well, there's a patch on gerrit to test, for this problem.

http://review.cyanogenmod.org/#/c/67866/

Maybe you can sweet talk Masta into cherry-picking it for you. lol
[Verizon Samsung Galaxy S III] mastamoon:
What the heck. I looked yesterday and it looked like this fix was already merged.. It was actually rem'd out along with the code that the fix disables.. But I guess I read it wrong.

I'm on vacation for a week but might still throw up a build at some point. I'll add this in if it doesn't get pushed through by then.
[Verizon Samsung Galaxy S III] TwistingSoul:
So, I have QuickPic installed to move photos to my external SD card, which has worked flawlessly until today, when I received an error message that there is a change in KitKat that won't allow this anymore.

This worked just fine through all of these builds, so why now, did it stop working? Even using ES File Explorer times out and won't move this photo over.

I installed this: https://play.google.com/store/apps/details?id=nextapp.sdfix

Rebooted and still no joy.

Edit: I noticed that the file name had ":nopm:" before the .jpg extension (the second colon may not be there), but renaming this file without that nopm part allowed me to move it to external storage. Weird.
[Verizon Samsung Galaxy S III] greekstile:
That would be awesome, thanks Masta!!!

I'm really surprised more people haven't complained about this issue. I guess most people are using Chrome these days? Or haven't noticed the issues caused with Gmail, Google Search bar, etc?
[Verizon Samsung Galaxy S III] bullah:
Gmail Pictures Working!

I just dirty flashed the 7/11 build over top of the 6/27 build (without flashing gapps) and I finally have pictures properly showing up in the gmail app. While on the 6/27 build and a few previous ones, I always had about half of the pics load and the others have a question mark logo. Not sure if this has already been addressed, but just thought I'd share my experience. Thanks Masta for your continued builds!
[Verizon Samsung Galaxy S III] Master Cylinder:
That's bizarre! :eek: I've been using QuickPic for months now and never saw that - I've been up to date on these builds most of the time for the last month. I just checked and mine works fine.

Question: Did you change to a different camera app?

Edit: Or edit or process it someway with an app?

Just trying to figure out how that 'nopm' thing got in there.
[Verizon Samsung Galaxy S III] TwistingSoul:
I think the :nopm: handle is when you send a picture with the Hangouts app by selecting its built-in camera function instead of using the CM 11 default camera app, and sending the picture that way.
[Verizon Samsung Galaxy S III] Master Cylinder:
What masta? You took a break from the Slot Machines to hook us up with a new build?

:laugh:
[Verizon Samsung Galaxy S III] Stigy:
Using a friend's old S3 because my G2 is getting fixed right now.

It's currently running a very old CM version (CM10.1-20130713-EXPERIMNETAL) and I'd like to get it updated to the latest 4.4.x release.

Do I need to do anything special before I flash this ROM or do I just download it and GApps and flash in recovery?

Thanks!
[Verizon Samsung Galaxy S III] Whisk_33:
Mobile network state: Disconnected

So, I noticed yesterday, I wasn't getting data (4G/3G) at home so I used Wifi. I'm not getting any data again today, so I upgraded to the newest nightly, but I am getting no data. I can make calls and send sms, but I'm getting no data. Anyone else experiencing something similar?

Network: Verizon Wireless

Signal Strength: -105 dB, 37 asu

Mobile Network Type: LTE

Service State: In Service

Roaming: Not Roaming

Mobile network state: Disconnected

IP address: unavailable

I am on the MB1 Baseband version since I was one of those lucky individuals that had that problem back in the day as well. Thoughts? ideas? creative insults?

Edit:7/17 Dirty flashes of the todays build didn't change anything. I still couldn't get data over the mobile networks. I did a factory reset and it seems to have come back. When I try to restore my backup nandroid I loose the connection again. I notice there is a custom restore in the Philz recovery. I'm not clear what each option controls. Anyone have a link that I can read for some edification?
[Verizon Samsung Galaxy S III] Srambo217:
Got a couple random powerdowns with 7/11 today. It's been fine since I flashed. Odd. Otherwise great ROM, I'm really enjoying it.

Galaxy SIII

My Podcast*-*http://bit.ly/WWSXbz

Twitter - http://bit.ly/VVAdb8
[Verizon Samsung Galaxy S III] Whisk_33:
Some people might suggest making back ups of the current ROM and updating the recovery. But you listed all that needs to be done.
[Verizon Samsung Galaxy S III] Chris123NT:
You're on MB1? I would upgrade the firmware to MF1 if I were you, that's the newest SAFE firmware that doesn't brick or permalock your phone.
[Verizon Samsung Galaxy S III] neolink1:
Several of us had to use MB1, as MF1 brings back the single text issue. (Error to send SMS). I'm on MB1 as well, with no issues so far. (Other than random reboots now and then when sending a text).