yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
If its working for you its fine, no worries.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Video recording in 1080p works for you on this build?

If that's the case I'd like to actually get a link to this build so I can give it a try (will nandroid just before).
[Verizon Samsung Galaxy S III] mastamoon:
Yes. 1080p works fine. :)
[Verizon Samsung Galaxy S III] open1your1eyes0:
Oh so is that the first nightly build that finally fixed it? :)

If you can PM me a link I'd be happy to give it a try at least.
[Verizon Samsung Galaxy S III] mastamoon:
I think it's been functional for a few but yeah, sure. :P
[Verizon Samsung Galaxy S III] skytbest:
Often times receiving MMS will fail on build 3/22. I'm using Hello as my texting app. When ever I get a group message it won't come through and Hello will give me a notification saying "Receiving message failed" along with who the message was from. Is this a known issue? I was using group messaging fine on a previous build of this same ROM.
[Verizon Samsung Galaxy S III] flyingpenguin:
Seconding this issue. Haven't been able to send/receive MMS for a long time. Persists through Hello, Hangouts and SMS. Performed an ODIN and reflashed, persists. Switched over to PA, issue persists. It's really weird.

Will try reflashing the 03/03 (last known before issue) and see if it fixes it... totally bizarre. I've never seen an issue that persists with different ROMs, though it could just be that potential VZW APN issue, not just a rom-centric one.
[Verizon Samsung Galaxy S III] skytbest:
Let me know how the 03/03 works if you flash that one
[Verizon Samsung Galaxy S III] darkknight1812:
There is a potential fix for apn issues and network extenders with the latest nightly. Let me nandroid and test and I will report back.

**Alright, so I dirty flashed the 3/31 nightly and it is still behaving the same as before. I then wiped cache/data/system and flashed it, and it the issue is still there. This time, I could not even go through the Cyanogenmod Account Setup because it fc. Back to my nandroid of the 03/03 nightly :( (I have attached the logs again)
[Verizon Samsung Galaxy S III] EatonZ:
Looking forward to hearing your results!
[Verizon Samsung Galaxy S III] mastamoon:
I notice from your log that your network extender is looking for mcc310mnc8 which is missing from our apns-conf, just how mcc310mnc00 was for [MENTION=1782878]Stealth111[/MENTION]. I added these lines to the file and uploaded it here for you to test.

Try this https://dl.dropboxusercontent.com/u/13144052/CM11/xda/apns-conf.xml by placing it in /system/etc and reboot. Let me know how it goes.
[Verizon Samsung Galaxy S III] :
I need a list of apps that were affected by the stretched video bug on the FFC about a month ago. Right now I have Snapchat and Hangouts on my list.

---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
[Verizon Samsung Galaxy S III] Defragger51:
I gave up because no matter what CM 11 nightly I went back to I still had the sms issue of working then not working . I finally gave up and went back to a 4.3 TW rom and I just passed 52 hours of run time with No sms problems at all. I am about to flash the final CM 10 4.3 rom because I really really hate TW, hopefully my sms will still work
[Verizon Samsung Galaxy S III] darkknight1812:
I tried your file with both a dirty flash and a clean flash and I am still experiencing the same issues. Could something be wrong with the ril? I see it mentioned in the dump after a crash. Here are my latest log files.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm having the same texting problems (using the last week or so CM11 nightlies), but discovered I can text using Voice+. Have you tried that as a workaround?
[Verizon Samsung Galaxy S III] neozen21:
Looks like CM 11 3/31 build breaks ART (at least for me).

Causes many modules/services to stop working, making phone unusable (never ending popup boxes saying XXX stopped working).

Even after a full wipe. Switching to Dalvik boots up with no problem.

Just FYI...
[Verizon Samsung Galaxy S III] Defragger51:
Nope never thought to use it , actually thought it was only for google voice txt not regular txt. will remember that the next time I give cm 11 a try again
[Verizon Samsung Galaxy S III] Hybridnoob:
It will send your texts from any SMS client on your phone through your Google Voice number.
[Verizon Samsung Galaxy S III] Stealth111:
I noticed when I downloaded the apns-conf.xml file, and went to open it up it gave me an error, that I have not noticed before ever, even with all the times we have messed with this file. It says: Invalid character in the given encoding. Line 1288 Position 17. I just wanted to throw that out there. If someone tried to drop that file in their phone to test, it may get ignored completely by the phone due to the invalid character. ;)
[Verizon Samsung Galaxy S III] open1your1eyes0:
Well, looks like 3/31 nightly finally fixed the 1080p video recording issue for me. :good:
[Verizon Samsung Galaxy S III] darkknight1812:
I saw that too. I just went to that line it highlighted the area so I just renamed it, saved it, and it did not give an error next time I opened it. I think it has to be something other than the apns config file. The whole screen flashes, for example, the homescreen will lose all of my icons for a second or I am in the settings and it will all of a sudden not display any content, all the while the mobile cell connection is rapidly connecting and disconnecting. If I get a chance, I will upload a video.
[Verizon Samsung Galaxy S III] mastamoon:
I fixed up the apns-conf.xml file. Something happened the way I saved the data from github.

[MENTION=5284825]darkknight1812[/MENTION] Yeah I saw that crash in your logs. I was hoping that it was a crash due to your phone not being able to grab the correct apn over and over again. Have you gone back to stock and back to CM again? What is your flashing process for dirty vs. clean?
[Verizon Samsung Galaxy S III] chowner:
Trying to take a video on 0401 = immediate reboot.
[Verizon Samsung Galaxy S III] mastamoon:
Front or Rear cam? Try wiping camera data.
[Verizon Samsung Galaxy S III] chowner:
cleared data and then rebooted and it still reboots with either the front or rear camera.
[Verizon Samsung Galaxy S III] mastamoon:
Stock camera I assume?
[Verizon Samsung Galaxy S III] chowner:
yes
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/62014/ should fix the camera issue for tonight's build.
[Verizon Samsung Galaxy S III] chowner:
nice

Thanks
[Verizon Samsung Galaxy S III] neozen21:
Lol... Anyone else getting a sheep "baaah" sound instead of their usual SMS/Alarm/Ringtone sound? (On 4/1 's build)

Good one CM... good one... :good:
[Verizon Samsung Galaxy S III] chowner:
Ha! Been on vibrate the whole day, I just checked though and yes.
[Verizon Samsung Galaxy S III] xs11e:
I wasn't brave enough to install an update for April Fool's Day, wanted to check here first. Now I'll wait for the April 2nd build, thanks for the warning.

Installed 4/2 build, sound is normal, no baaaaaaaa!
[Verizon Samsung Galaxy S III] Casper34:
So am I correct in my assumption that if I update from 2/26 to 4/1 that everything should to smoothly? I have been holding off due to the SMS issues. I will do a clean install, factory wipe.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] CrustyMcLovin:
Yup.. seeing the same thing on my end. Very annoying since I had to pull the battery and use the key-combo to get back into recovery.
[Verizon Samsung Galaxy S III] :
For a variety of reasons I'd recommend 4/2 over 4/1. I can't speak to SMS issues however. And you shouldn't need a wipe.
[Verizon Samsung Galaxy S III] SDQB17:
I have had an odd thing repeating a few times a day over the last 2 nightlies. Everytime I wake up the phone I get a message in the notification area " preparing sd card..this may take a few minutes." Usually does nothing. Once it completely froze. That was on 3/31 , downloading 4/2 as I type.
[Verizon Samsung Galaxy S III] RJQXCV:
ART fixed in 4/2?
[Verizon Samsung Galaxy S III] bmeek:
Yes. Are you implying there's a way to toggle art/Dalvik from recovery? I couldn't boot past the never-ending pop-up boxes to get to Dev options...
[Verizon Samsung Galaxy S III] skrusrnmz:
Just a heads up on 4/2 nightly. Manually update and wipe your caches. Dirty is cool.

I used cmupdater and got stuck at the spinning boot animation. For a long time. Started the update when I went to bed and woke up some time in the middle of the night to Cid starring at me, spinning. Got into recovery, wiped caches and booted fine.
[Verizon Samsung Galaxy S III] chowner:
Had no such problem.

Also video works again.
[Verizon Samsung Galaxy S III] merdely:
Same here. I used cmupdater to download the 4/2, but manually booted to recovery, backed up, flashed, booted, rebooted, and all has been golden so far.

I can't speak to this. I haven't tried video yet.
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
Nevermind, I'm blind.

I flashed this rom for the first time yesterday and flashed the 4/1 build. I thought the sheep thing was a glitch or something, then game on here last night as soon as I realized it was April 1st and checked. :laugh:
[Verizon Samsung Galaxy S III] bmeek:
Is ART functional again?
[Verizon Samsung Galaxy S III] merdely:
I don't use ART.
[Verizon Samsung Galaxy S III] bmeek:
Ah... I thought I recalled that you were a fan. I seem to get noticeably better battery life with ART with no problems up until the 3/31 build.
[Verizon Samsung Galaxy S III] alershka:
I just checked. It still doesn't work. Same parade of fc's.
[Verizon Samsung Galaxy S III] nickhex89:
Only issue I'm having is when I'm in a phone call I only get a blank screen after I answer or dial out I can't bring up my dial pad or even hang up they have to hang up or I have to lock the phone and swipe the status bar down and hit hang up from there. That's the only way I can hang up the call.
[Verizon Samsung Galaxy S III] softwarestealer0:
Hey guys, so whenever I disconnect from my cars bluetooth I need to rebbot my phone to get any sound to come out of it again. Also it auto starts playing as soon as im in the car regardless if I switch over to it. Anyone experiencing anything similar?
[Verizon Samsung Galaxy S III] stiltzkin:
Can anyone running 4/1 or 4/2 confirm the ability to receive and send SMS/MMS normally? I'm still running 2/13 and I just wanted to make sure that updating to a newer build won't cause irrevocable issues with messaging. Thanks.
[Verizon Samsung Galaxy S III] SDQB17:
Working perfect here...got and sent messages all day long on 4/2. I would use 4/2 over 4/1 btw. Camera and Vid all work.
[Verizon Samsung Galaxy S III] nickhex89:
Anyone having in-call dialer issues?
[Verizon Samsung Galaxy S III] EatonZ:
SMS issues persist in 4/3.:crying:

Is there still a fix in the works?
[Verizon Samsung Galaxy S III] darkknight1812:
I have gone back to stock a few times but the issue persists, I have not tried it with the new apns-config though. I even reprovisioned following the steps in your thread just in case. When I get a chance, I will odin back to stock and try the latest nightly with the apns-config. For dirty flash, I just wipe cache/davlik then flash nightly. For clean, I factory restore (cache/data) and wipe the system partition. If I unplug my network extender, the phone works fine, but when I plug it back in, it freaks out again. It will connect to the extender for a brief second, drop, then connect to the tower if there is a signal, drop, and it will continue to repeat the process. I am not sure if the face that the extender shows up as roaming has anything to do with it.
[Verizon Samsung Galaxy S III] Casper34:
Works for me!! I was afraid to try it also. I'm on 4/2. I was able to send 2 pics and it just so happened that a friend sent me a video. Videos never played right, but this one did!! I also sent and received 2 SMS texts and they all worked.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
Noob question, sorry - when I get a text and click it, the notification doesn't go away, even if I respond. I have to clear it manually. Is this a normal thing or a setting? Email it goes away.
[Verizon Samsung Galaxy S III] sil3ncer7:
Since I went to CM11 I have had diminishing service on the phone. I have to restart atleast 2 times a day to get service back. Usually I am on WiFi but when I disconnect from wifi I have to restart the phone to get signal back.

Once I am on Cell, I have MAYBE 1 bar of LTE, but mostly 3G and just 1 or 2 bars. I have great service and have never had bad service until CM11. Rom is great aside from this hiccup. I have been on nightlies for a few weeks and had a stable build before that.

Is there a list of radios out there that I can DL and try? or is there I log I can pull to submit?

Thanks
[Verizon Samsung Galaxy S III] Defragger51:
I did a completely clean install last night from CM 10 back to CM 11 latest nightly because you said sms/mms is working . I am here to tell you and everyone else that is Not the case CM 11 still has sms problems. After my 3rd txt message today I started getting the message Not sent error. Why can this issue not be fixed. this is getting really annoying completely wiping my phone every time someone claims sms/mms is fixed in CM 11.. None I need to wipe and go back to CM 10.
[Verizon Samsung Galaxy S III] Casper34:
I have noticed this since moving to CM from PACman, I just used to it.

I have not had a single issue with the 4/2 nightly. All my texts and MMSs have come through and sent. I am also on KT747 latest, thinks its a 4/2 also.

Again, no issues with a dirty flash from 2/27. I was very very hesitant on updating because of the texting issues.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Defragger51:
Ok Thanks I'll look for and give the KT747 kernal a try. I have never used anything but the stock cm 11 kernal.
[Verizon Samsung Galaxy S III] Casper34:
I have been using KTs kernel for about a year now. I have never had an issue with it. He is fast with updates and syncs with it also.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Reznor7:
I find that if I click the body of the text and respond, it won't clear. If I choose reply and use the quick reply pop-up, it does.
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
Yes, I've noticed this as well. It's quite annoying coming from another rom...just a small niggle I have. Weird that emails clear but SMS doesn't.
[Verizon Samsung Galaxy S III] jekern77:
Anyone else have borked WiFi tether on 4/4 build?

Rolled back to 4/2 and it works fine again.

Sent from my Galaxy S III with Tapatalk
[Verizon Samsung Galaxy S III] mewohkie:
Why is this in original development forums when they are unified nightlies?

Also is there a more stable build then 3/3 out yet?

been running that with latest KTkernal and only problem is random restarts and camera crashes if you open it through an app other than camera app.
[Verizon Samsung Galaxy S III] jekern77:
Confirmed same problem on 4/5 build... when I try to turn on tether, "error" shows up.

Sent from my Galaxy S III with Tapatalk
[Verizon Samsung Galaxy S III] Reznor7:
No problems here on 4/5 dirty flashed.
[Verizon Samsung Galaxy S III] Div033:
Same, using built in mobile hotspot. Works without a hitch.
[Verizon Samsung Galaxy S III] jekern77:
Interestingly enough...I wiped and did a clean flash of 4/5, no problem with tether, then I restored all of my apps, no problem, then themed, no problems. Must have been something weird with dirty flashing from 4/2 to 4/4

Sent from my Galaxy S III with Tapatalk
[Verizon Samsung Galaxy S III] MorphiousGX:
Anyone having problems charging? With this build I'm not able to charge regardless the phone is on or off
[Verizon Samsung Galaxy S III] Hybridnoob:
No problems here. What build are you running? Clean install?
[Verizon Samsung Galaxy S III] jager420:
Im using TWRP 2.7.0.0 as my recovery. Can I flash the latest nightly with this recovery?
[Verizon Samsung Galaxy S III] Defragger51:
Been using TWRP 2.7.0.0 and 2.6.3.1 before that and never had any problems installing any rom. am still waiting for sms to be fixed so that I can txt more than 3 messages before it stops working, so I am not using the latest nightlies, staying of 10.1 TW rom
[Verizon Samsung Galaxy S III] Casper34:
I dirty flashed 4/2 over a 2/?? And my text is fine.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Hybridnoob:
Consider yourself lucky then. I've Odin'd back to stock twice (among other things) and still can't get SMS to work (more than once without toggling airplane mode) on recent nightlies. The only work around I've found is using Voice+. The SMS bug hit me out of nowhere about a week or so ago. I'm surprised more people aren't posting about it here. A lot of people have mentioned it on Mastamoon's thread.
[Verizon Samsung Galaxy S III] Casper34:
I don't consider myself lucky. I only updated after more than a few said it was working. There were a ton of comments saying text stopped working, one or two said they never had any issues, when I saw five or six comments, and after I was convinced to take the plunge, I did and no issues.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] darkknight1812:
By any chance do you have a network extender?
[Verizon Samsung Galaxy S III] Hybridnoob:
No, I don't. I know I sounded like I was complaining earlier (not my intent, as I'm very happy with this ROM), but I just want to make sure people who ask about texting understand that it's not working well for everyone. I'm not the only person having issues with texting. As of 4/2 a clean install (from Odin) didn't fix it. Yes, I nvrestored before Odin and reprovisioned after. There's a reason why D2LTE doesn't have an M5 build yet. I trust the devs will fix it sooner or later and will wait patiently. This bug isn't near as bad as losing IMEI in the past!

Edit - I just tried fixing it using 4/5 and can confirm SMS is still not working for me. No big deal, but people should know.
[Verizon Samsung Galaxy S III] ChuckFarley:
What are your mobile settings? I noticed a few times that it would default to NV vs SIM setting. If it's not set to SIM, try switching it, reboot, and try text again.

I'm not running cm at the moment, but I believe it's in setting, more settings, mobile settings. Make sure you're on lte/cdma and whatever the SIM setting is set to SIM. You'll find it.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thank you for trying to help; I really appreciate it. Unfortunately, I already had all the correct settings. For good measure, I tried to toggle them and reboot, but no dice.

Looking at the changelog for tonight's pending nightly - looks potentially promising!
[Verizon Samsung Galaxy S III] 0331:
I'm no expert, but I seem to remember reading that its best to download straight from cm, and not the updater baked into the ROM. I could be wrong of course. I did have problems using the updater, FC's ,boot loops and such. I've had no issues downloading from cm. Im on 12/09 nightly. Just a thought.

sent from my I535 on CM11 KitKat
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I used the updater to download but I flashed the file myself... I didn't let the updater start the flashing process
[Verizon Samsung Galaxy S III] LudicrousPeed:
Thanks. I actually did download directly from CM. Anyway, to solve the keyboard issue, I was able to do a voice search for Google Keyoard APK and download that over LTE. Now I can sign into Wi-Fi and everything else. Thank goodness for voice search :)
[Verizon Samsung Galaxy S III] Hybridnoob:
If the hash value for the file is the same, it's the exact same file. How you flash the file after that may or may not make a difference.
[Verizon Samsung Galaxy S III] Defragger51:
Worst Battery Life Ever on Official CM_11, 12/09. Let me start by saying I have been using the unofficial 4.4 Rom's sense 11/12, without issue and great battery life. Was running the 11/28 unofficial until this morning, with out issue and great battery life. Then I did a complete clean wipe and installed the official CM_11 , 12/09 and battery life is unbelievably bad. On the unofficial rom I would take my phone of charge 8:30-9:00 am and at 12:30 midnight I would still have 37 percent battery left . on the 12/09 rom with very little phone use most of the day after I took it off the charge around 2 pm it was just setting on the counter.After 5 hours 58 minutes I only have 38% battery left. Sorry could not get the screen shots to load
[Verizon Samsung Galaxy S III] lou1210:
Are you using the PA gapps when you flashed? Need to be sure you're not using the gapps for 4.3. That will cause the issues you're seeing.
[Verizon Samsung Galaxy S III] Hellven:
So here is an article in Forbes stating that Cyanogenmod is incorporating text encryption into all builds. Does this mean that Titanium Backup will have issues with restores in this rom? Any ideas?

http://www.forbes.com/sites/andygre...t-messages-will-soon-be-encrypted-by-default/
[Verizon Samsung Galaxy S III] bmeek:
Try formatting /system before flashing, and make sure you flash the correct gapps. The rom is designed to preserve gapps for nightly updates, but I suspect you are coming from cm10.2 (with 4.3 gapps).

I experimented with letting cmupdater take me from cm10.2 to cm11 and saw the same errors you're reporting. Best to start clean with cm11 (including a freshly formatted /system). Subsequent nightlies via cmupdater should be fine...
[Verizon Samsung Galaxy S III] LudicrousPeed:
Yeah once I installed gapps (I used invisiblek) the issue went away. The strange thing is that I hadn't installed any gapps at all. Is android now so dependent on gapps that CM can't function without it?
[Verizon Samsung Galaxy S III] Akhileshjj:
Gravitybox not working..

Any one having issues with Gravitybox not working with the Rom? I am on 12/08 clean flash.

getting error "GravityBox system framework not responding.Exiting"

It was working with Android 4.4

Edit.. Sorry guys its working after Reinstall of Both Xposed framework and GravityBox...
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Great Start

Just took 12/9 for a full day spin.

Clean flashed from scratch, formatting everything and using latest gapps.

Good battery life once media cache built up after first boot. Black screen when flipping back to chrome, just like in more recent 10.2 builds, resolved by scrolling. Menu button does bypass lock screen. Both the built in calendar and Google calendar are refusing to sync and display most of my calendars. Voice+ is baked in and has been working perfect with built in messaging app and hangouts, surviving multiple reboots. LTE toggle, when added doesn't do anything yet. Received and made several calls with no issue. Camera appears to be working, took some video and photos throughout the day, but could not get Google goggles to scan any qr codes, it just refused to scan or take photos. Hasn't crashed on me all day, but I'm using Swype instead of the included keyboard, although the default keyboard made it through installing and logging in to about 30 different apps, without the slightest issue. Location lock is working and seems just as fast as normal.

I'd say it's ready for daily driver. My only real complaint is the calendar issue and the fact that a few apps don't allow for 4.4.1yet...
[Verizon Samsung Galaxy S III] harry_seaward:
Removing your Google account and re-adding it will fix the Calendar issue.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
You are correct. Thank you, clearing all manners of caches didn't help and I would not have thought this would do it.