yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Div033:
Hey there, resident smoothness OCD freak here. I get the same lag you are. A lot of people don't have an eye for it like you and I, and I envy them for it.

Going from 4.3 to 4.4 introduced a major backend graphics engine change and is now based on the chromium rendering engine for the UI. If you've ever used chrome in the past on your android, you may have noticed some of the laggy behavior there is now present on all sorts of places on our device.

This isn't a bug of CM11 nor is it an android bug, but a sign of aging hardware. Google is making strides to unify their software to make development less of a headache and they've recently targeted the android rendering engine as I mentioned. I immediately noticed the rendering lag upon switching to 4.4. Heck I even noticed more lag moving from 4.2 to 4.3!

It's our GPU... It's getting old. We're lucky performance is still largely acceptable. Before my S3 I had a droid incredible with an adreno 200 inside. When 4.0 dropped and was inevitably ported to the old incredible, it was nearly unusable due to how laggy it was. Our adreno 225 might be aging, but it still handles things very well.

I've learned to accept it and have begun looking to the future for a device upgrade. I suggest you do the same or roll back to 10.1/2. I don't think it'll get any better for us.

The HTC M8 is looking mighty good right now.
[Verizon Samsung Galaxy S III] merdely:
I use Enterprise WPA2 authentication at home with no problem with CM11. I have never had to modify any files. My set up is an enterprise grade Cisco Access Point pointing to a RADIUS server.
[Verizon Samsung Galaxy S III] scadilla:
I believe it maybe an issue with EAP authentication. I haven't had issues with 4.3, in connecting all I have to do is manually add the through the normal wifi interface by specifying the SSID (as we don't broadcast ours), choose 802.1x, put my user name and password in and I am connected. I tried the same steps with 4.4.2 and no luck. I do know that we use IEEE8021x for key management, OPEN SHARED for authentication algorithms, eap is set to PEAP (PEAPVER is 1) and phase 2 is MSCHAPV2. So maybe your setup is different?
[Verizon Samsung Galaxy S III] AlphaXray:
So is anyone else's GAPPS not working with 3/5? Is there a fix?
[Verizon Samsung Galaxy S III] RRF12:
Gapps working good on 3/05 for me everything is very good .
[Verizon Samsung Galaxy S III] AlphaXray:
I continually get an error saying com.android.phone has stopped. If I hit ok it comes right back. Tried downgrading to 3/03 and I get the same thing. I also have no service or wi-fi now.

Even downgraded to 1/20 and it still does it....

Installed the KK GAPPS from 20140105 and this did not fix it.

I haven't changed anything on the phone so I have no idea why this would happen. Is there a newer kernel I missed or something?

Using TWRP 2.6.3.1 to flash
[Verizon Samsung Galaxy S III] AlphaXray:
Complete factory reset did not resolve the issue
[Verizon Samsung Galaxy S III] bmeek:
Not sure what "Complete factory reset" means to you, but did you format /system before you flashed the ROM and current gapps?
[Verizon Samsung Galaxy S III] AlphaXray:
Got it now. I believe I didn't format /system that first time.
[Verizon Samsung Galaxy S III] ScottIsMyName:
Can anyone confirm if they have 'Wifi Tether' working on kit kat? I had it working on 4.3 but not with 4.4. If anyone has it working, could you post your settings and//or anything special you had to do to get it to work?

Thanks!
[Verizon Samsung Galaxy S III] chowner:
0305 is a no go for me. Process literally constantly crashing had to pull the battery to get past the "this process has ended windows"
[Verizon Samsung Galaxy S III] merdely:
That's unfortunate. I haven't had any issues so far.

Sent from my Verizon GS3 running CM11
[Verizon Samsung Galaxy S III] chowner:
What gapps?
[Verizon Samsung Galaxy S III] Argent36:
0303 did the same thing to me - downloading 0305 now - hope it doesn't do the same :(
[Verizon Samsung Galaxy S III] jasoncallahan:
I have it working (Wifi Tethering) . I'm on a current nightly. it's been working for some time. BT Tethering has been more problematic, but no issues with Wifi for at least a month. No special setup or anything required for me.
[Verizon Samsung Galaxy S III] chowner:
what gapps are you running?

Are you using the google dialer?
[Verizon Samsung Galaxy S III] WarER4X:
Is there a way to choose a custom lockscreen slide selector app icon that isn't in the "system icons" set? I've tried installing a few icon packs, but they don't show up as available choices.

-SR-
[Verizon Samsung Galaxy S III] element1966:
I was wondering why my phone wasn't ringing correctly until today when I had a minute to play with it.

Two things I found:

"Digital Phone" ringtone does not work correctly. It will only ever ring once and not loop when a call comes in. Use Pyxis instead if you like that ringtone (Why have the same ringtone in there twice to begin with?)

I couldn't get the ascending ringtone setting to work with any of the "basic" ringtones. It never ascends in volume when set to "On each ring" but it does ascend when set to a time value in seconds.
[Verizon Samsung Galaxy S III] dpn982:
I personally use the PA 0-Day GAPPS for all roms: http://xdaforums.com/showthread.php?t=2397942
[Verizon Samsung Galaxy S III] chowner:
:confused:
[Verizon Samsung Galaxy S III] bmeek:
The install scripts of many ROMs clear /system - but not the CM nightlies. This is so that you can use CMUpdater to update with nightly builds and not need to update gapps every day.

Meanwhile the "Wipe data / factory reset" option in CWM recovery only clears your data etc. This makes it common for folks coming from a 4.3 ROM to CM11 to end up with leftover gapps of the wrong version.
[Verizon Samsung Galaxy S III] merdely:
From CM's page from 20131208.

Sent from my Verizon GS3 running CM11
[Verizon Samsung Galaxy S III] chowner:
Thanks I suspect that's the difference.

I'm running PA and google dialer.
[Verizon Samsung Galaxy S III] merdely:
For what it's worth, I also installed the Browser Sync from BaNkS. I just wasn't at my computer to be able to look it up and mention it when I replied earlier.
[Verizon Samsung Galaxy S III] NedDasty:
Hi Element1996,

I found the fix to this yesterday. The reason is because the "digital phone" sound file (Ring_Digital_02.ogg) is missing a meta tag that says ANDROID_LOOP=TRUE.

I fixed it, and you can download the fixed file here: https://dl.dropboxusercontent.com/u/3983762/Ring_Digital_02.ogg. You have to put it into /system/media/audio/ringtones, replace the other version, and set permissions to rw-r-r-. Reboot, and it should work.
[Verizon Samsung Galaxy S III] jasonbtx:
No
[Verizon Samsung Galaxy S III] brockkk:
Home button isn't turning on my phone anymore. Have it checked in settings.
[Verizon Samsung Galaxy S III] brockkk:
are you using the stock messaging app? mine is sending mms just fine.
[Verizon Samsung Galaxy S III] soohyunk83:
skype

Is Skype not working on cm11 a known issue?

Just wanted to see if it was only me.
[Verizon Samsung Galaxy S III] Jdelta9889:
No
[Verizon Samsung Galaxy S III] jabhall:
I am getting the same thing. I normally use Hangouts, but I have tried the stock messaging app as well. I also tried adding the APN in the MMS settings for Hangouts but I can't get them to save. I'm running the 03/05 nightly.
[Verizon Samsung Galaxy S III] esjames:
I am having this same issue at this moment. Looking for a fix.
[Verizon Samsung Galaxy S III] RedRumy3:
I am also getting "No APN Specified on the device." after flashing latest nightly.
[Verizon Samsung Galaxy S III] EatonZ:
Getting the APN issue as well.
[Verizon Samsung Galaxy S III] spscoral:
I am getting the No APN Specified on the Device on 3/6 as well (and MMS images are not coming in). Just reverted back to 3/5 and still had the same problem. Went back to 3/3 and everything is FUBAR now (wasn't before on 3/3) and I'm getting the Android Process Has Stopped messages. Going to try to flash 3/3 and gapps again...
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
This is also happening on PACman roms which started up on 3/4 so it's something changed recently
[Verizon Samsung Galaxy S III] spscoral:
Went to 3/3 and reflashed gapps: still having problems. Went to 2/28 and reflashed gapps: boot loops! Looks like a clean install is in my future.
[Verizon Samsung Galaxy S III] jabhall:
I had the exact same experience. I tried going back even further, to a pre-merged build (thinking maybe it broke when they merged to D2LTE), but I was already in a boot loop. I did a clean install to 03/06 and still have the APN issue. So a clean install didn't fix it either.
[Verizon Samsung Galaxy S III] spscoral:
I just did a clean install back to 2/28. Seems ok now...
[Verizon Samsung Galaxy S III] AlphaXray:
Getting very similar issues as you guys. I had the com.android.phone has stopped working problem on 3/5. Completely wiped and clean installed. Got everything working. But now on 3/6 my service goes in and out about every 5 minutes. Haven't received the APN error though.
[Verizon Samsung Galaxy S III] spscoral:
My advice would be to get off 3/6 ASAP. If you don't have the APN error there may still be hope. I was ok on 3/6 for almost 20 hours with no problems before things went south...
[Verizon Samsung Galaxy S III] Durhammer:
Does anyone have a stable, battery-sipping, camera-working d2lte to recommend? 02/07 d2vzw
[Verizon Samsung Galaxy S III] ecooce:
It started with 3/05 but Im now on 3/07 and I still get an error when trying to send an mms, it says "no APN specified on this device", text works on hangouts and mms app. I normally just have hangouts installed, but I wanted to make sure mms.apk was having the same issue, so I added that to the cm11 update.zip this time around on 3/07, but still have the APN error, any ideas???
[Verizon Samsung Galaxy S III] EatonZ:
Hopefully the developer is aware now and maybe 3/08 will fix the bug.:fingers-crossed:
[Verizon Samsung Galaxy S III] badseed767:
I was able to temporarily fix the apn. I used titanium backup to restore phone settings from a few days ago. That gave me back my apn after rebooting but it went away again after a few hours. And I lost my recent text messages and call log.
[Verizon Samsung Galaxy S III] jabhall:
Thanks for the info. When I have a chance I will try a clean install of the 2/28 build.
[Verizon Samsung Galaxy S III] chowner:
clean install of 03/07 all seems well
[Verizon Samsung Galaxy S III] RedRumy3:
I will wait for next nightly if it doesn't fix the apn issue I will do a clean install I guess.
[Verizon Samsung Galaxy S III] spscoral:
Based on my experience if you get the no APN issue, then moving to different nightlies that didn't have the problem doesn't do anything. The only way I got back on track was a clean install. As badseed767 said, restoring from a backup might do it but from what I saw, once you get the issue just moving to a different nightly won't solve it.
[Verizon Samsung Galaxy S III] rhcreed:
no mms / no erro

Noticed that I'm not getting/sending mms messages any more (was on 3/6, tried 3/7 same deal). Not seeing the apn error some people are reporting. Sending shows trying, then fails. Receiving gives the "click to download image" but never succeeds. Using hangouts as my sms/mms client.

Any suggestions? Can I hope this gets resolved in next nightly? thx!
[Verizon Samsung Galaxy S III] mastamoon:
Try this build http://mastamoon.truelinux.net/ROMs/test/cm-11-20140307-UNOFFICIAL-mastamoon-d2lte.zip ******* DOESNT seem to fix anything, atleast permanently.. :(

I was having the same issues, after flashing this I no longer have the issue. Mebbe I fixed it... mebbe its a fluke... you tell me! :P
[Verizon Samsung Galaxy S III] rhcreed:
Can I dirty flash over the official CM11 latest nightly?
[Verizon Samsung Galaxy S III] mastamoon:
Shouldnt be a problem.. its like 99.9% CM11 nightly.
[Verizon Samsung Galaxy S III] jabhall:
I just had the same experience with 3/7. Didn't get the APN error, but still unable to send/recieve MMS. This was a clean install.
[Verizon Samsung Galaxy S III] mastamoon:
:cowboy:
[Verizon Samsung Galaxy S III] skrusrnmz:
Wiped cache and dalvik. Dirty flashed this over 3/5 and still get No APN specified on device.

Really don't want to have to clean install to fix this. Is that the only solution?
[Verizon Samsung Galaxy S III] mastamoon:
Not sure yet. My issues eventually came back also... back to the drawing board.
[Verizon Samsung Galaxy S III] jabhall:
Well that's unfortunate. I tried dirty flashing this over a clean install of 3/7, no MMS. Tried clean install with this ROM, still no MMS. :(

Thanks for trying though!! :cool:
[Verizon Samsung Galaxy S III] Shakes The AssClown:
The builds were good for awhile. Started noticing some glitches and such. Been on SlimKat... Pretty darn stable.
[Verizon Samsung Galaxy S III] chowner:
Back your stuff up and you can do a wipe and reflash and be back to where you were in minutes.

Takes a little longer, but for me it's a cost of running these roms.
[Verizon Samsung Galaxy S III] soapinmouth:
Are you using interactive governor?

---------- Post added at 08:17 PM ---------- Previous post was at 08:14 PM ----------

Clean flashing doesn't seem to fix mms for me.
[Verizon Samsung Galaxy S III] jabhall:
FYI, I clean flashed back to the 2/27 build and MMS is working again with no APN error. I know someone said the 2/28 build worked for them, but I couldn't find that download and already had the 2/27 on my phone so I went with it. Whew... I'm just glad to get everything working again. :victory:
[Verizon Samsung Galaxy S III] Defragger51:
I am running the 03/03 build with out any sms or mms issues. So I see no need to go back to 02/27 build. I actually know someone on that build and there phone reboots itself daily. I have been running 03/03 build just under 102 hours since I last rebooted with out any problems. Any body have any idea when we going to get a working google wallet or know of another 4.4 build where it does work ?
[Verizon Samsung Galaxy S III] RedRumy3:
I restored back to 3/3 build I had saved thank God. I usually make new backup every couple of flashes I do and I guess I made one for 3/3 and the no apn issue is fixed so I will stay on this until they fix it.
[Verizon Samsung Galaxy S III] rhcreed:
wifi networks list missing

just noticed that when I flash the 3/7 nightly, I loose my list of wifi networks. That's a long list and a lot of passwords, anyone know how to get that back? I don't have a backup. thx!
[Verizon Samsung Galaxy S III] iwearthebelt:
You could always flash back to your last good nandroid, then use Titanium Backup to backup your WiFi networks then restore them after you flash the latest nightly. I recommend anything you backup with TB you backup to an external SD card. If you don't have a nandroid there's not much you can do.
[Verizon Samsung Galaxy S III] Casper34:
OK...... with all this talk about apns across many roms, I have not updated.

BUT.....

This morning I showed full Verizon service, uploaded a picture to Facebook, went inside a grocery store for 15 minutes, and nothing. Could not call, could not send a text, could not go to web pages, NOTHING! Mind you I was on 3-3 when this happened. I went back to my 2-28 Nan and still nothing. I let the phone sit for about 30 minutes on my car charger, I'm out of town, and I have been fine since......... knock on wood!

Wonder if there was a tower update or something? Mine happened at 7a est, lasted about 45-60 minutes. Maybe this will help, maybe not, but if not, why would I show full service with no access to anything?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] jabhall:
I did a clean install of 03/03 and all is well so far. Thanks for the info!
[Verizon Samsung Galaxy S III] skrusrnmz:
Went back to CM official. Installed 3/8 and problem persists. Didn't clean flash. Maybe someone wants to try that.

I did notice something. I use Google voice with voice+ and the default messaging app exclusively for texting. For the occasional mms I have to send from my phone. That's when the apn issue popped up.

That's the weird part. Apparently voice+ has no effect now. With voice+ enabled texts are still being sent from my phone, not GV. And they're going out fine, with no errors. Sending mms gives the apn error.

So I don't know what the correlation is between voice+ and the apn issue but they both started with the 3/5 nightly.
[Verizon Samsung Galaxy S III] ecooce:
Seems like there is an issue with the .rils and blobs being implemented, or the way they are being implemented into the new AIO multi-device update.zips, this would cause network and APN issues...
[Verizon Samsung Galaxy S III] skrusrnmz:
Clean flashed 3/8 (factory reset, format dalvik and system). Still apn issue with sending mms messages only. Regular texts go through no problem.

Also, I installed Google voice and then went through the voice+ setup process. Sent texts with the stock messaging app and they are still going from my phone, not from my GV number.

Just passing along my experiences.
[Verizon Samsung Galaxy S III] rhcreed:
Anyone having APN issues on apps other than hangouts? I cannot send MMS though hangouts (tried manually adding APN, no joy). But when I swap to handcent it works fine... So try that until they get hangouts fixed.. Hope it helps..
[Verizon Samsung Galaxy S III] Hybridnoob:
People can also try EvolveSMS - no issues with that here.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Hopefully they don't ignore these SMS and MMS problems the way they do the Bluetooth and camera issues
[Verizon Samsung Galaxy S III] gt43aw:
Well.... I hadn't upgraded since mid last month right after we went to the unified builds and then suddenly last week my MMS started failing and then my SMS is completely nonfunctional as of today. I reset my phone and it still didn't work and then after someone said 03-03 build was working for them I did a complete wipe including system and davlik and installed that build and SMS is still not working. I don't get any APN notification error. I guess I'm posting because I wanted to ask if you guys are sure this has to do with the later builds only as that wasn't my experience (I.e. I was on 227 and it failed after a week), or maybe its something else?
[Verizon Samsung Galaxy S III] bmeek:
I've been updating nightly, currently on the 03/08 build, and this all sounds very curious to me... I've been using the stock cm11 SMS app, and just tested MMS. No problems at all.

I never switched to Hangouts for texts and MMS, seemed a bit too bulky for this simple task.
[Verizon Samsung Galaxy S III] merdely:
I upgraded to the 03/08 snapshot last night and got in a weird reboot loop. I got a text and that froze my phone, it'd reboot, get the same text again, reboot, rinse, repeat.

I restored back to 03/07, got a couple of texts with no problems.
[Verizon Samsung Galaxy S III] gt43aw:
OK. So today's one of those days I wonder why I run anything but stock instead of being nerdy and mucking with my phone on a perfectly good sat. Anyway. Problem seems to be solved.

What didn't work: clean install with system format of latest cm11, pre merge cm11, and 10.2.1. As well as me activating a random Sim card I had laying around

What did work (wish I had done this first): going into my mobile network settings and toggling between turning everything off, to 3g only, to 4g lte only and sending texts between each. Now it seems my sms and MMS are back and I'm using latest cm11 nightly. No clue if that's what did it or just dumb luck. But I'm going out to do some day drinking here in SD and try and talk to some ladies instead of staring at my phone. Wish me luck, because I just spent a day mucking with my phone. My guess is I've forgotten how to talk to girls ;).
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Are the D2lte download links broken for anybody? I can't download any builds :(

Edit: I can't download any d2VZW Snapshot builds either

Edit2: Links are back up
[Verizon Samsung Galaxy S III] metalcated:
Same thing! I messed around switching apn's, data on/off, roaming etc... Kept getting no APN toast errors and eventually they stopped and poof... Suddenly got a few MMS texts and problem fixed. I also have no clue the combination that worked.
[Verizon Samsung Galaxy S III] Argent36:
Switched to GoSMS Pro and am able to send and received MMS again must just be a hangouts problem?
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
It's not a hangouts thing
[Verizon Samsung Galaxy S III] wolficus:
Curious... What does apn manager pro show after making it a system app.

I am on cm10.2 btw. I use that combo to work with my apn though.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I'm using pacman and I just installed APN manager pro... Moved it to system and tried but didn't work
[Verizon Samsung Galaxy S III] wolficus:
damn... was worth shot though.

thanks for trying :)
[Verizon Samsung Galaxy S III] metalcated:
OK so it stopped working after a reboot and I can't get it working again. So idk what to do but wait for a fix and I hope soon.
[Verizon Samsung Galaxy S III] gt43aw:
Ditto. Wish i hadn't rebooted. Back to hitting airplane mode and then back out to send a single text before everything goes to crap. Maybe Ill give up Texting instead of diet cokes for lent. Hahaha.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
This might have been appropriate to post in the SlimKat thread but definitely not here. It's great changing ROMs fixed your issue but next time you should either keep to yourself or just mention it in the SlimKat thread in a much better tone. Every ROM has there buggy days. Post like these just discourage the ROM builders/creators from posting their builds. Please go away now.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
So for what it's worth I just came from PA Beta 6 and I clean installed the 9/08 D2LTE nightly build and I have no problems.I tried Hangouts with about 10 or so SMS and 1 MMS. Had done 2 reboots in between. No issues.

I then switched to GoSMS which is my preferred and performed the same tests with 2 reboots in between. I had no issues. I suggest clean flashing the 9/08 D2lte nightly build to see if you have any issues. Hope this helps. I just jumped on this from a very long break from CM builds and so I gotta catch up on the thread myself.

Also if you live in PA and you are having issues with SMS u may want to visit this post. It's the 570 and 717 area codes having problems:

http://xdaforums.com/showthread.php?p=50634797

---------- Post added at 09:18 PM ---------- Previous post was at 09:01 PM ----------

Thank you! Yes that is much better. I just don't like to see posts that might hurt a developers feelings. They work very hard for us and they receive very little thanks. I hope there were no hard feelings :)
[Verizon Samsung Galaxy S III] esjames:
I had issues where i could only send out one text. I now can send texts again like normal. I found out i had too many devices registered and cleared out every android device on my account. Via this link -> https://www.google.com/settings/personalinfo . Navigate to the security tab and in the account permission box, click on the view all link. There you will see all devices registered under your account. I removed ALL, re-registered my phone and voila!!!! Texts started working again!

I hope this can help, but I do not think this will solve the APN issue as I was not experiencing that issue.

---------- Post added at 01:05 PM ---------- Previous post was at 12:55 PM ----------

Also a question, which i think it seems fitting to this forum, Is our Monthly snapshot builds going to be under the new D2LTE name?
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Just flashed latest nightly... Text messaging fails after I send the first text... Tried the suggestion above but no go
[Verizon Samsung Galaxy S III] gt43aw:
Ditto. Seems to be a pervasive problem across a lot if ROMs. Great to know from anybody if they've found a solution or where the development community is at.