yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
Mine is set like in the picture, never had a problem.

After you set it to that, you might have to toggle LTE mode or airplane mode or something. I remember having it happen when I changed mine also.
[Verizon Samsung Galaxy S III] Casper34:
That's the thing, I don't have to toggle anything. Everything worked out of the box, and continues to work.

If I set it to what yours is, I can toggle and reboot till I am blue in the face, it just wont work.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
Have you tried setting it like I have it, then dirty flashing the rom again? The setting should stick and it might get your service back.
[Verizon Samsung Galaxy S III] Casper34:
I have full service now. I wont change it and screw it up.

Sent from my ghost white SGS3!

---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------

@skytbest, have some bad or good news....... its not kernel related. I've been at 22% for the last hour or so and if just dropped to 21.

You can see where its leveled off. Do you remember where the files were to delete the battery stats? Just want to try it. I know there are 2 files you need to delete, just don't remember where they are.

Here you go.... phone shut off, plugged in to charge (while off) and it showed 18%. I unplugged, turned on, all it did was vibrate. I tried 2 more times, nothing. Plugged in, it showed 0%. Let it charge off till 4%, turned on took the screenshot and posted this.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] nickhex89:
Just an update on 4/11 nightly still same update check error.
[Verizon Samsung Galaxy S III] Mystikalrush:
4/10 seems to offer some better signal service at my location, which is nice at the very least.
[Verizon Samsung Galaxy S III] mastamoon:
Problem on CM's side....

https://twitter.com/CyanogenMod/status/454529200700289024

And fixed!

https://twitter.com/CyanogenMod/status/454532250324176896

:cool:
[Verizon Samsung Galaxy S III] jhanford:
What Fixed My SMS Sending Issue

Hi all,

Saw this on another site after having the same SMS sending issue again!

It turns out that my phone configuration doesn't like it if I select to use Voice+ for SMS. As this is something I typically set up when asked by the phone - which is usually after a clean setup - I'm finding that I'm killing my outbound SMS before even trying it.

So, I went to Settings > Apps > All > Voice + and cleared data and now all is good.

This may not work for you. Just putting it hear in case someone needs it.
[Verizon Samsung Galaxy S III] nickhex89:
Conforming it is back up and functional. Thanks for keeping me updated guys... Much appreciated.
[Verizon Samsung Galaxy S III] joedajoester:
Are the latest nightly's still causing SMS and data dropout issues? I've been staying away for a really long time in fear of getting these issues
[Verizon Samsung Galaxy S III] tpearsall:
This workaround to get sms back and use CM11 can be found here: http://xdaforums.com/showthread.php?t=2657822 BTW, the 1 sms message issue seems to only impact people in the east. Most issues seem to come from PA, MD, VA, NJ areas.

It's so nice to be off TW and back on CM!
[Verizon Samsung Galaxy S III] joedajoester:
I'm in New Jersey sadly. I really don't want to get these issues, in that thread it didn't seem like that method worked for everyone. It isn't clear if this is a Verizon issue or cyanogenmod issue. Its annoying how I can't flash a recent nightly without a chance of getting this issue especially if I have to Odin and nvrestore and flash cm all over again and there's still going to be a possibility that it won't resolve it.
[Verizon Samsung Galaxy S III] tpearsall:
Going back to TW fixes it reliably. The issue appears to be a regional change Verizon made (intentionally or not) that breaks ASOP based ROMs' messaging. You didn't need to flash an upgrade for it to break. There were people on the same ROM for months when sms stopped working around Feb 20th. I used the solution from post 120 of that thread which basically puts you on an old firmware/modem and then you restore CM11. From there the nightlies don't seem to bring back the issue. The workaround appears pretty reliable if you do it correctly, but it's still a pain. You mileage my vary.
[Verizon Samsung Galaxy S III] joedajoester:
I used to have my signal easily drop completely on a mid march nightly i was on in the past so I thought the issues were releated to each other. I flashed an older nightly I had and the signal dropping issues went away so it led me to believe it was a new cm issue, but your saying its not, and if I were to have problems, I would be having them already since its verizon's fault. Can anyone comment on the status of the recent nightly's?
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm posting this post in this thread in case others are still having SMS issues. The OP from that thread didn't work for me (I followed the instructions perfectly multiple times and could never send more than one SMS after using the method from the OP), but I read through the entire thread and found a solution that did fix my problem. Sorry I'm not crediting who gave me the idea (I can't remember which member did for sure, but I think it was [MENTION=5791025]net-cat[/MENTION]). Here's what solved my SMS issue for two different Verizon S3's:

1. Backup current ROM (CM11 in my case)

2. In Terminal Emulator - su (enter) reboot nvrestore - if you previously completed nvbackup

3. Battery pull once process completes, as it will bootloop

4. Boot into recovery, restore nandroid and flash MB1 firmware. I have had issues on all newer firmware versions.

5. Reboot system and profit. No SMS issues for at least 24hrs.

Side note - I had to manually wipe system, cache and dalvik, then install ROM and Gapps to get the next nightly to boot (CMUpdater bootlooped). Successive nightlies have installed and booted as expected. This was an easy and quick fix - I can't believe I didn't think to try this sooner. It's worth a shot if the OP method (much more time intensive) doesn't work or requires more effort than you're willing to put out.
[Verizon Samsung Galaxy S III] joedajoester:
Is it possible to overclock the gpu? Cm11 ui has some lag to it, and the s3 does have a kinda weak GPU, it'd be nice to push it a little further for that extra bit of power. Thanks
[Verizon Samsung Galaxy S III] Casper34:
[MENTION=2044079]Nardholio[/MENTION]

Sorry, I read the monitor incorrectly. But you can see that at 17% my phone shut off, and when I rebooted, that its reading correctly... till I get back down to 22%.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Leankernel exp builds have overclocked GPU but its been proven to show no difference to stock.
[Verizon Samsung Galaxy S III] Skyrocketing:
What exactly is the SMS issue? Because I've been texting someone but I don't know if they have been receiving them
[Verizon Samsung Galaxy S III] merdely:
You are now one of my new favorite people.

I followed your steps exactly (though "su reboot nvrestore" is not a command... "su", then "reboot nvrestore").

Thank you, thank you, thank you.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I did a clean flash of tonights build and it shows that AOSP Keyboard repeatedly force closes. This is preventing me from being able to sign into google play store to download a third party keyboard. Anyone getting this issue? There's nothing I can do without the keyboard.
[Verizon Samsung Galaxy S III] Hybridnoob:
You're welcome! I edited my post, but I'm glad you figured out what I meant [emoji106] I'm also glad I helped. That issue had bothered me for weeks and it seemed like no one else had that problem that couldn't fix it through other means.
[Verizon Samsung Galaxy S III] xwhofarted:
I know this happened the one time i flashed the wrong Gapps.
[Verizon Samsung Galaxy S III] skytbest:
Did you flash the correct G-APPS version? Make sure they are KK versions of GAPPS
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Yes I use pa gapps and have been using it for a long time
[Verizon Samsung Galaxy S III] skytbest:
I'm not sure. I use PA gapps too. I would try reflashing the ROM and flash stock gapps, then flash PA apps over if you want them later

---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------

Anyone know if the latest nightly is still having MMS issues? I'm on 4/07 and I cannot receive/send group or picture messages.

Also, this is not the SMS issue everyone is talking about, right? I can send/receive normal texts fine.
[Verizon Samsung Galaxy S III] d69oh:
[MENTION=4911449]Hybridnoob[/MENTION] thanks for the easy workaround for the SMS issue. I love you
[Verizon Samsung Galaxy S III] JohnnyTToxic:
A bit late in response, perhaps, but can you just flash the google keyboard from recovery ? http://goo.im/devs/paranoidandroid/roms/gapps-addons

It's the paranoid android version, but it should work and is technically a separate app from the AOSP keyboard and "This package will replace the stock/AOSP keyboard installed on your device (due to issues with using stock/AOSP keyboard if Google Keyboard is also installed in System partition)" according to http://xdaforums.com/showthread.php?t=2397942
[Verizon Samsung Galaxy S III] JMooney5115:
On the 4/10/2014 nightly I was able to send/receive group messages and receive picture messages. I'm now On nightly 4/15 and sending MMS works for me.

--

Mooney
[Verizon Samsung Galaxy S III] NegativeOne:
Is everything stable with regards to the theme engine? I'm surprised I am only hearing anything about messaging
[Verizon Samsung Galaxy S III] OneFast3:
Only thing I really noticed is my Google now is not themed after I updated.

I do have reboots sometimes now but I have not done a clean install in a long time now.
[Verizon Samsung Galaxy S III] NegativeOne:
What about the home button lag?
[Verizon Samsung Galaxy S III] joedajoester:
On the newest nightly's is signal easily dropping if it's really weak? On the 4/12 nightly, in a weak signal area my phone had no signal for part of the time and also switched between no signal to weak 1x. It also caused my battery to drain about 10% a half hour of being in my pocket. After that I switched back to an old nightly that didn't have the problems. Its annoying that it keeps happening to me whenever I want to run a recent nightly.
[Verizon Samsung Galaxy S III] rhcreed:
Everything stable on 4/16?
[Verizon Samsung Galaxy S III] chowner:
Haven't noticed anything out of the ordinary yet.

4/14 had amazing battery life. I'll see how 4/16 pans out and I might wipe and go back to 4/14 for the battery life.
[Verizon Samsung Galaxy S III] rhcreed:
4/14?

how was 4/14 for general stability?
[Verizon Samsung Galaxy S III] skytbest:
I just flashed 4/15 and group messages/MMS are not working for me. Anyone know if there is a fix for this? Gonna try 4/16 in a minute
[Verizon Samsung Galaxy S III] rhcreed:
What were you on before?

Where are you located (what state, there is a theory that it is a regional thing..)
[Verizon Samsung Galaxy S III] skytbest:
I was on 4/07 before. I'm in Hartford, CT.

I had it working on an older build, can't remember what it was, probably 3/XX.. Its pretty frustrating.

---------- Post added at 10:37 AM ---------- Previous post was at 10:03 AM ----------

To go back to an older version can you simply dirty flash that old nightly over the new one you have installed?
[Verizon Samsung Galaxy S III] skytbest:
Just flashed 4/16 nightly and MMS/group messaging is working again.
[Verizon Samsung Galaxy S III] joedajoester:
On 4-16, if you have a weak signal, does your phone completely drop the signal if it's weak. I am on a early March build because the problem has been there for me even on the 4-12 build. Also, is video really recording in 1080p? Even though it is selected it still does 720p. You can check by going to a video and tap details. Thanks
[Verizon Samsung Galaxy S III] darkknight1812:
[MENTION=3090069]skytbest[/MENTION] Try 03/03.
[Verizon Samsung Galaxy S III] skytbest:
Why do you say that?
[Verizon Samsung Galaxy S III] Reznor7:
Well crap, you're right about the video resolution. It checks out as 720p. And here I thought it was fixed...
[Verizon Samsung Galaxy S III] nrock2256:
So I've been running nightlies, and I'm flashing 4/16 tonight. I'm currently on the 4/11 nightly.

GPS: I get stable GPS locks fairly quickly whenever I go to use it. I'll admit, at first on the 4/4 nightly it took some finagling (I was on a road trip to Henderson, NV) but I'm getting locks and I'm happy now.

MMS/SMS: Both work just fine for me, however I'm using the Hangouts app for sms. Your results may vary. I stick to a pretty google layout.

Audio quality: Again, just fine through the speaker and headset, nothing messed up here

Camera: Works just fine

Cellular: Cellular connection is A-OK, but I live in a fairly well covered area. On the trip I took to Henderson, I had a constant connection to 3g, and mostly LTE (although the I-15 freeway has some damn good cell coverage). Nothing wrong here at all besides the usual heat spike if you get into a spotty 3g area.

Call quality: This, this I give a 2/5. Speakerphone doesn't work, and the earpiece is so damn quiet I can't hear a thing. However, today and yesterday it seemed to be fine so I have no idea what's going on there. Just be wary, the audio may be hella quiet, it may not. Seems buggy to me. I don't rely on calls so its not a huge deal.

Battery: Okay, sit back, because this is a doozy. If you are going to use CM 11 as your daily driver, carry an extra battery, a charger, or something to charge it with because battery drain is ridiculous. I'm noticing anywhere between 5%-10% drain at idle, with wifi on, cell data and location services off. I haven't bothered to check it out in detail with Battery stats, and it may very well be one of the many social networking apps I have. But for me, the battery life is absolutely terrible. I'm hoping the upgrade to 4/16 will fix this. Additionally, I'm having some charging issues, and it will actually DRAIN if I'm charging it and using it on 3g at the same time. the overall charge rate isn't anything to brag about either. Cyanogenmod based roms (I was using PACman before I decided that it was too much) have a reputation with me and my andriod friends with being very bad with battery life over the course of a few months after the CM team starts releasing nightlies for a new version of android. It will get better though, I can assure you of that.

If anyone has anything to add, feel free. I'm sure I missed some things that other users may need info on. If you have any tips on improving my battery life, PLEASE TELL ME BECAUSE I'm desperate for better battery life.

Have a good one.
[Verizon Samsung Galaxy S III] NedDasty:
I've been running the 3/28 build since it came out. I'm currently on the 9.5.1 leankernel. Absolutely everything works perfectly; I haven't had any reason to switch at all.

The new Google camera works perfectly. I never get any reboots. Signal is fine, SMS/MMS is fine.

Are there any features or improvements on later nightlies that give me any reason to update?
[Verizon Samsung Galaxy S III] skytbest:
So you had better battery life on PACman? Kitkat? I thought this was based off CM and battery life would essentially be the same. Is there really any reason not to switch over to PACman if this is the case? How are the ROMs different besides the extra stuff that PACman throws in?
[Verizon Samsung Galaxy S III] chowner:
drugs is the only explanation drugs
[Verizon Samsung Galaxy S III] merdely:
I wanted to highlight this post again (having just sent several texts in a row). It looks like Step 2 had "if you previously completed nvbackup" added to it. I had not previously done 'nvbackup'. However, I followed these steps EXACTLY. I have no problems texting anymore (I don't do MMS) and have been installing Nightly updates each night with no problem.

I heeded the note in "Side note", but I only wiped cache & dalvik before installing the next Nightly. I did not wipe system or re-install Gapps. I have had no issues.
[Verizon Samsung Galaxy S III] Defragger51:
I have to Ask, are you in a area that is having the sms problem . I am in Maryland and I followed those steps exactly and I am still having the sms problem and its getting very annoying doing airplane mode after every message so that I can send another message
[Verizon Samsung Galaxy S III] merdely:
I am in Maryland. Before following this process, I was able to send one text before having to toggle LTE off/on to be able to send another one. Since following this process, I have sent multiple texts in a row with no problem.
[Verizon Samsung Galaxy S III] dmginc:
This is worth a try (the root66 post). I know it says it's for getting data back, but I used it for my SMS issue and have had no issues for 2+ weeks now. You may get stuck at the Verizon boot screen but all you have to do is pull the battery, boot into recovery, then do a factory restore.

http://xdaforums.com/showpost.php?p=35600769&postcount=2
[Verizon Samsung Galaxy S III] joedajoester:
Google camera will not take a picture using the front camera at all. I'm on 4-15 nightly, can anyone comment if its still broken on the latest nightly's?
[Verizon Samsung Galaxy S III] dmginc:
You don't need to stay on a tw ROM. You can flash back to CM and the fix carries over.
[Verizon Samsung Galaxy S III] skytbest:
Is there any way I can find the 3/28 nightly for download somewhere?
[Verizon Samsung Galaxy S III] dmginc:
Here's Mastamoons 3/29 build. Might help.

http://mastamoon.invisiblek.org/ROM...cm-11-20140329-UNOFFICIAL-mastamoon-d2lte.zip
[Verizon Samsung Galaxy S III] LudicrousPeed:
4/16 is fantastic but it burns through the battery pretty badly. Also my phone seems significantly warmer than usual.
[Verizon Samsung Galaxy S III] skytbest:
Thank you! Is it ok to flash this over a newer nightly? I'm on 4/16 now

Argh, Chrome tagged that a malicious too. You know anything about that?
[Verizon Samsung Galaxy S III] Hybridnoob:
Not recommended. Reboot into recovery, then wipe system, cache and dalvik. Then install ROM and gapps. This process will not wipe your data, but should save you from boot looping.
[Verizon Samsung Galaxy S III] skytbest:
So I will keep my apps and their data?
[Verizon Samsung Galaxy S III] Hybridnoob:
Yes, as long as you're using CWM recovery, I can confirm that. Factory resetting or wiping sdcard will delete your apps and their data.

Do a nandroid first just in case. That should give you an peace of mind.
[Verizon Samsung Galaxy S III] skytbest:
Cool. Thank you! What is the reason for not wiping System when doing a dirty flash in that case? This sounds like the same as a dirty flash.
[Verizon Samsung Galaxy S III] Hybridnoob:
Wiping system is a less dirty flash. I only do it if a nightly won't boot through CMUpdater or for special circumstances like yours.
[Verizon Samsung Galaxy S III] dmginc:
That's what I do every time I flash a new nightly; wipe system, both caches, then flash the rom and gapps (if you wipe system you need to flash gapps).
[Verizon Samsung Galaxy S III] skytbest:
Great. Last question, sorry for the barrage. I'm about to flash Mastamoons 3/29 build, can I dirty flash (wiping system) over CM11 official? I believe it is a custom version of CM11
[Verizon Samsung Galaxy S III] Hybridnoob:
You should be fine. I've gone back and forth between those two a couple of times. Masta's ROM is mostly CM with minor tweaks. It's solid. You'll have to manually download CM if you want to come back (CMUpdater is removed from his ROM).
[Verizon Samsung Galaxy S III] skytbest:
Ok, that's how I've been doing it all along. Thanks for the help!
[Verizon Samsung Galaxy S III] LudicrousPeed:
We're a little off topic here, but...

I don't see where to wipe system in CWM, other than that in Mounts and Storage you can "format /system". That's what you're referring to?
[Verizon Samsung Galaxy S III] Hybridnoob:
Yep, that's it.
[Verizon Samsung Galaxy S III] dmginc:
Yup!
[Verizon Samsung Galaxy S III] skytbest:
Arrggh, boot looped :( Currently stuck at Kernel splash screen.

Edit: Realized why. I wiped system AFTER installing the ROM instead of before. Just reflashed and wiped BEFORE and all is good :)
[Verizon Samsung Galaxy S III] ckotten03:
S3 turns off randomly while charging

Has anyone's phone turned off randomly at night while charging? I'm on the 4/5 nightly. The first time I woke up & the phone was off but 100% charged. Last night I noticed the phone was off but only 68% charged (after being on the charger for 5 hours). I turned the phone back on & it was 100% this morning (and thankfully remained on, so my alarm went off). Any thoughts?
[Verizon Samsung Galaxy S III] cuban11182:
Has there been a fix to the SMS bug? Sorry if I missed it.
[Verizon Samsung Galaxy S III] dmginc:
Check the OP in mastamoon's thread.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
Same here.I was on an earlier April build and the battery would go forever. On the 4/16 build it drains pretty good
[Verizon Samsung Galaxy S III] dmginc:
Are you getting any wakelocks?
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
Good question. I just recharged the battery so I cant say for sure. Ill have to get back to you. Is there a way to tell besides looking at the graphical battery statistics in the settings?
[Verizon Samsung Galaxy S III] dmginc:
Wakelock detector is a really nice app on the play store. I'm sure there are others but it seems to be the best to me.
[Verizon Samsung Galaxy S III] ynot3363:
Meant to search something please disregard this post
[Verizon Samsung Galaxy S III] joedajoester:
Is battery on 4-16 bad for you guys? It seems to be the usual for me. I can max about 4 hours screen on time on WiFi. I have a buddy with an iPhone 5s and he can average about 7 hours on WiFi claims. Seems android is really really falling behind on one thing. Battery.
[Verizon Samsung Galaxy S III] THE SKATER DUDE:
You are using a phone that is almost 2 years old.lol Get a new android and you will most likely beat him in battery life.
[Verizon Samsung Galaxy S III] skytbest:
Are there any methods for getting MMS/group messaging working again? I had it working on certain nightlies (can't remember which, of course) and now it is not working. Though it doesn't seem to be dependent on what nightly I'm running. I've had MMS work one minute, and then not work another while on the same nightly.

I've just recently odin-ed back to stock, tested MMS/group and it was working, then full wiped and did a clean install of CM11 and no luck. MMS and group messaging is not working. Is there anything you'd recommend a I try, maybe a different radio/firmware? Anything at all! I've been using builds that others say MMS is working fine on, but they rarely work for me.
[Verizon Samsung Galaxy S III] d69oh:
Go back a couple of pages there's instructions for flashing the mb1 firmware it worked great for me. Feels great to not toggle airplane mode between texts
[Verizon Samsung Galaxy S III] NegativeOne:
Is the theme engine stuff going to get merged in here, or is it different rom that we have to install?
[Verizon Samsung Galaxy S III] softwarestealer0:
Hey guys,

Is anyone else having the issue of after a bluetooth connection you need to reboot for the on board speaker to work again. I've also found that making a call letting it ring once and hanging up restores speaker to working.
[Verizon Samsung Galaxy S III] Zacharybinx34:
I have issues where if I pause or skip ahead in Netflix I have to reboot fire Bluetooth to work again.

Also get a few crashes/reboots using video from time to time.
[Verizon Samsung Galaxy S III] MrBrady:
I heard CM fixed a lot of camera issues on the last one or two nightlies. Any comments on the new Google Camera functionality? Particularly high quality blur, photosphere and front camera functionality?