yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] papstar:
I've been having some issues sending MMS, so I tried this. Now I can't receive MMS at all. I just get the "no APN specified on device."
[Verizon Samsung Galaxy S 4] jkc120:
Which sms app are you using? It worked for me for 8sms, hangouts and simply text.
[Verizon Samsung Galaxy S 4] FernBch:
Just had a SOD experience (I think). S4 screen went black but I couldn't wake it. Held the power button for few seconds and hit home and it restarted (so much for what I thought was a pattern). But I did get a last_kmsg.

https://www.dropbox.com/s/4nc7dzuhs9c6895/last_kmsg?dl=0
[Verizon Samsung Galaxy S 4] TMYINC:
Were you plugging the charger into your phone when you got the sod?
[Verizon Samsung Galaxy S 4] drt054:
Everything working on M9.. Probably safest for now.
[Verizon Samsung Galaxy S 4] gonzlobo:
On my previous android phones, I used euroskank's CM kangs (they're usually a day or two 'fresher' than official CM). Haven't tried them on my S4, but will check tonight if that build has the same MMS/BT issues.

http://xdaforums.com/showthread.php?t=2385271
[Verizon Samsung Galaxy S 4] FernBch:
Not for any of them. Not sure what was going on or why for the last one. I usually only see it once in a 24 hour period and it seems usually after a notification when asleep (that's when I have noticed it, anyway).
[Verizon Samsung Galaxy S 4] papstar:
Using stock MMS app. Seems to be working now though.
[Verizon Samsung Galaxy S 4] gonzlobo:
So I did a dirty flash of euroskank's over official cm. Got lots of FCs, so restored back to 0804.

I may start from scratch with euroskank this weekend.
[Verizon Samsung Galaxy S 4] FernBch:
Ok, just experienced another what I think is a SOD event. It does have a pattern that seems to be repeatable. Kinda goes like this:

1) Phone goes to sleep

2) I get a new Yahoo Mail notice

3) Phone display will not come on. Hard and soft keys do nothing.

I do have a last_kmsg but no logcat.

https://www.dropbox.com/s/4nc7dzuhs9c6895/last_kmsg?dl=0

Strange part is it doesn't happen every time.
[Verizon Samsung Galaxy S 4] vanberge:
I've been pretty much flashing every nightly that comes up. I've had the same sporadic issues when going to/from WiFi where I wont get LTE/3G data from time to time. I've had the same BT issues you have mentioned, but I have not had any sleep of death issues at all.

I dirty flashed pretty much everything since M9, and just went with a clean flash of 8/26 yesterday.

Are you on a different kernel? I run stock CM kernel
[Verizon Samsung Galaxy S 4] FernBch:
None. I run a completely stock CM.
[Verizon Samsung Galaxy S 4] jkc120:
I'm starting to wonder if the SoD isn't related to LED. FernBch dk you have custom LED settings? Every SoD I've noticed (about 1/day) occurs after a notification from wordfeud which I have a custom LED color set for in settings. And when it does it, I can see the LED blinking abnormally. Like normal time between blinks but the blink duration is very short.
[Verizon Samsung Galaxy S 4] FernBch:
I don't think it's custom settings but I do agree with eitger LED or notifications in general. For me it mostly happens after a Yahoo Mail (default is purple) and once in a while Tapatalk (default is yellow). Tapatalk notices are jacked and don't always work right (tapatalk issue - always happens when Android builds increment) that why I think Yahoo is the usual. I haven't seen it happen with messaging but it just may be coincidence. I am going to turn notifications off for Yahoo and Tapatalk and see how long before another happens. If I don't experience any more (usually one/day) I'll start turning things back on with Yahoo being the first.

Only side note is I had no SOD's yesterday (8/27 build) but that may be meaningless as well.

---------- Post added at 09:44 AM ---------- Previous post was at 09:37 AM ----------

Figures, can't turn notifications off in Yahoo mail, so I'll freeze/unfreeze as needed with TiBu. At least the suspected culprit can be taken out of the picture. We'll see what happens and I'll report back this evening.
[Verizon Samsung Galaxy S 4] vanberge:
Interesting thoughts on the LED being the culprit. I haven't had any SOD issues, but I have always disabled my LED notification light and battery light...
[Verizon Samsung Galaxy S 4] FernBch:
Personally, I'm not sure if it's the LED, the notifications, or something else. It just seemed strange that I only have an SOD after a notification came through. That seems to be the common event, though.

That said I turned notifications off on a per forum basis and for Tapatalk as a whole and logged out of Yahoo mail (can't turn notifications off in Ymail app). I have yet to experience a SOD today. It's a new record, more than 24 hours since the last. I think I'll start with Yahoo and log back in so I can get email notices and see what happens. Notifications from Tapatalk are hit or miss and I'm pretty sure it's a Tapatalk thing. Every time Android goes up a version (ie: 4.3 to 4.4) Tapatalk notices don't work all the time so Ymail would be a better way to test the theory.

I'll report back again tomorrow.

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

Now, if Bluetooth could get the bugs out things would be golden again. I posted up my issues with it somewhere in the last couple pages complete with a logcat.
[Verizon Samsung Galaxy S 4] jkc120:
So you still had SoD on 8/27 prior to disabling notifications ?
[Verizon Samsung Galaxy S 4] FernBch:
No. I couldn't flash 8/27 until last night and I disabled notifications right after startup (I know, Imma flashaholic) So I'm gonna find out if 8/27 fixed it or if it's a notification issue of some kind. I'm not a developer but looking at the commits for 8/27 I didn't see anything notification related (unless I didn't read deep enough)

---------- Post added at 10:48 PM ---------- Previous post was at 10:22 PM ----------

Ya know, I gotta say one thing. Battery life has been rockin! 14 hrs off the charger, a few calls and messages, some web and forum surfin, a few emails, all the normal stuff. Sittin at 49% currently. No complaints in that area!
[Verizon Samsung Galaxy S 4] BaronLager:
has the MMS issue been resolved?
[Verizon Samsung Galaxy S 4] FernBch:
As far as I know and can tell (no issues here) MMS seems to be working.
[Verizon Samsung Galaxy S 4] BaronLager:
8/29 Nightly

I did a dirty flash of 8/29 over M9, and MMS was broke.

Did a clean flash of 8/29 this morning, and MMS is working fine.

Also noticed that when I step out of my office (where I get absolutely no signal) I transition from WiFi to LTE perfectly.

Steps in the right direction!
[Verizon Samsung Galaxy S 4] jkc120:
I wonder if wiping /system first would have worked as well and avoided re-setting things up?
[Verizon Samsung Galaxy S 4] BaronLager:
I guess I could restore my borked image and try that...
[Verizon Samsung Galaxy S 4] jkc120:
Yeah restore your M9 backup, then reboot into recovery again (just to be safe), and then wipe system manually. THEN flash 8/29.

Of course, you'd have to flash gapps again as well if you wipe /system.

I'd appreciate you testing that, as would others probably. Wiping /system is preferable I'd think to having to restore TiBu or similar :)
[Verizon Samsung Galaxy S 4] BaronLager:
Ok, I restored old image, wiped /system and installed 8/29 + gapps

Walked outside, got instant LTE signal. Tried to send MMS, and it just got stuck at SENDING......
[Verizon Samsung Galaxy S 4] jkc120:
Bummer, so it's something in the system settings (i.e. data) that requires the clean flash :(

I think as a workaround, doing the "reset APNs" worked for me. I will flash the 8/29 shortly and see if MMS remains working or if I have to reset APNs again. If I do, I guess it's time I clean flashed :(
[Verizon Samsung Galaxy S 4] jkc120:
Dirty flashed 8/29 on top of my working MMS build from 8/25 and whatever I did to fix MMS in 8/25 carries over so I guess once I fixed that, dirty flashing is OK. GPS also works fine for me still.
[Verizon Samsung Galaxy S 4] wowthatisrandom:
you could try killing the telephony.db and rebooting and letting it recreate it self, maybe some old apns got stuck in there.
[Verizon Samsung Galaxy S 4] FernBch:
There have been some pretty big changes since M9 so a clean flash maybe necessary. There was an experimental build in the midst of this and I believe it had some kernel changes in it.

As for me, I have not experienced one SOD since 8/27. I turned all of my notifications back on this morning and everything has been good so far. MMS has been working perfectly, and I have had no problems changing from mobile to wifi networks. I'm not positive but I think Bluetooth has been straightened out for me as well. Things are definitely looking up. Great work CM team.
[Verizon Samsung Galaxy S 4] FernBch:
I guess I spoke too soon about BT. It seems that my Jabra still does not connect when I turn it on until I power cycle BT. The button on the earpiece will answer calls but not hang them up. The only time it auto connects is when I turn the earpiece on and reboot my S4.
[Verizon Samsung Galaxy S 4] oreizinho:
i'm on i545vrufnc5 base band, can i install cyanogenmod?
[Verizon Samsung Galaxy S 4] FernBch:
Only if your device originally came with the MDK bootloader and it HAS NOT taken the OTA from Verizon. The MDK bootloader is the only one that will allow the installation of a custom recovery like CWM or TWRP. If you have a device that only allows the use of SafeStrap you are unable to flash CyanogenMod.
[Verizon Samsung Galaxy S 4] gonzlobo:
Yeah, I was flashing nightlies and getting temporary goodness, but I've returned to the M9 build & have been here for a few weeks. I'm staying here until I see commits that are kernel-related.
[Verizon Samsung Galaxy S 4] FernBch:
There have been a couple. Honestly even though it is a little aggravating I can deal with my BT issues. It's just a PITA to keep the screen up to hang up a call when I don't want/need to leave a VM. The SOD issue was another story. I was getting real tempted to go back to the experimental build to get away from it. That seems to be fixed as I haven't had one in over 48 hours. But, hey, I'm a bit of a flashaholic so..............
[Verizon Samsung Galaxy S 4] jkc120:
Hope you didn't jinx yourself on the SoD issue haha :)
[Verizon Samsung Galaxy S 4] oreizinho:
Thankyou brow
[Verizon Samsung Galaxy S 4] FernBch:
I hear ya, I'm goin on 72 and all is good so far. Maybe I'll get back to flashing the latest build.......
[Verizon Samsung Galaxy S 4] jkc120:
So are they not going to fix the overly high speaker output/gain? I'm constantly having to lower it because a) it sounds horrible and distorted and b) I'm worried it'll blow out my speaker. Does anyone know of an app that does the OPPOSITE of things like volume+ so I can limit the max volume?

That's really my only complaint as of 8/29. Other than that, terrific job by the CM team.
[Verizon Samsung Galaxy S 4] FernBch:
There is a way to do this, if you're daring.

Read the following:

http://xdaforums.com/showthread.php?t=2768182
[Verizon Samsung Galaxy S 4] jkc120:
hmm a little too dicey for me. Wonder if the volume thing is specific to the s4? maybe kernel related when the caf stuff got merged a while back?
[Verizon Samsung Galaxy S 4] FernBch:
Could be. If you want to try use option two and change only what is needed.

---------- Post added at 01:41 PM ---------- Previous post was at 01:38 PM ----------

Well gettin real close to 72 hours here and no more SOD's.

I did get the Tapatalk notification issue straightened out, so it seems. Just uninstalled and reinstalled the latest version and it seems to be working properly again.
[Verizon Samsung Galaxy S 4] FernBch:
Well, it has returned. Just had another episode of a device that refused to wake. Only thing is I had no notification show. I think I'm going to be "creative" and try something different.......
[Verizon Samsung Galaxy S 4] gonzlobo:
Over the years, 3 things have given me SODs.

1. Being too aggressive with undervolting/underclocking. You're probably running stock, so that's probably not it.

2. Being way too aggressive with Greenify. Now I Greenify 7 apps (no system apps).

3. Being too strict with permissions in Privacy Guard. Can't explain why, but when I allowed certain apps a few more permissions, they would sleep/awake properly.
[Verizon Samsung Galaxy S 4] FernBch:
1 - Nope. Completely Stock.

2 - Nope. No Greenify.

3 - Nope. No Privacy Guard Restrictions.

At a loss at this point as to what's behind it.
[Verizon Samsung Galaxy S 4] jkc120:
same here, though I do use greenify it's all things like facebook and non-system apps.
[Verizon Samsung Galaxy S 4] MustGoFast:
How does one get into this menu? I don't see any way to get into the screens you posted pictures of...
[Verizon Samsung Galaxy S 4] jkc120:
Open the voice dialer app. say "open APNs" and it should give you that option to select.
[Verizon Samsung Galaxy S 4] MustGoFast:
also why the heck did they remove access to the "Access Points" menu anyway?

---------- Post added at 09:31 PM ---------- Previous post was at 09:22 PM ----------

And according to this page Voice Dialer is a known broken app... so how did you get in there?

http://wiki.cyanogenmod.org/w/Known_Issues_page_for_jfltexx
[Verizon Samsung Galaxy S 4] FernBch:
Well, I broke down and did it. With some of the issues I've had (particularly the SOD) I have clean wiped and reflashed CM and Gapps. I guess we'll see what happens over the next few days.
[Verizon Samsung Galaxy S 4] MustGoFast:
I know this can be done in apns-conf.xml - I'm reading through that file and can't quite figure it out. It would seem that VZW has their APNs listed in this file at least 20 times. Not sure how they are different or what would need to change..
[Verizon Samsung Galaxy S 4] jkc120:
Weird, I don't know why it works for me! haha
[Verizon Samsung Galaxy S 4] FernBch:
I have a question.

Is there a place where we can go to make suggestions about CM features? I have a number that I would like to add to the blacklist but it shows up as a 12 digit number on caller ID and the list will only accept a 10 digit number. I would like to suggest removing the number of digits restriction.

My other options are to install a third party app (which will use resources) or find which file to edit to allow this (which I have no clue where to look).

This number is an annoyance because they won't identify themselves and call at strange hours.

Suggestions are welcome.
[Verizon Samsung Galaxy S 4] FernBch:
Ok. I flashed 8/31 and noticed one item right away. A pulsating LED has been added to the boot process. However, after boot completed the LED continued to flash. I also was unable to put the phone to sleep using the power button.

After about 5 minutes of looking for how to turn this new feature off I reverted to the 8/30 build.
[Verizon Samsung Galaxy S 4] vanberge:
Same here.. Couldn't find a way to shut the boot led off.. Reverted
[Verizon Samsung Galaxy S 4] bswides412:
Is the 8/17 experimental snapshot the most recent stable release? With so many versions and issues being discussed, it is hard to keep track.
[Verizon Samsung Galaxy S 4] jkc120:
As of now, my recommendation (if you want a nightly) is 8/29. Or stick with M9 if you want stability.
[Verizon Samsung Galaxy S 4] FernBch:
Agreed. 8/29 or 8/30, both worked quite well for me.
[Verizon Samsung Galaxy S 4] jkc120:
And if you are coming from an earlier nightly, you probably want to do a clean flash or you *might* have MMS issues.
[Verizon Samsung Galaxy S 4] FernBch:
Agreed again. There were some pretty big kernel related changes (and other stuff too) after the second experimental build was released. I would definitely wipe clean and reflash CM and Gapps if coming from anything before the 8/17 builds. I would also resist restoring any data except for maybe messages (mms & sms) using TiBu or similar apps. Start clean and reset everything plus install apps from Google Play.
[Verizon Samsung Galaxy S 4] drt054:
So BT, GPS and MMS working after 8/29?
[Verizon Samsung Galaxy S 4] FernBch:
MMS & GPS work well for me. The only BT I use is a Jabra earpiece. It does not auto connect and the button does not hang calls up but other than that it works. I can't speak for car audio as I don't use it.
[Verizon Samsung Galaxy S 4] drt054:
Thx.. I have a BT receiver that I plug into my car that acts as a headset.. I will give it a try
[Verizon Samsung Galaxy S 4] FernBch:
I'm gonna give the 9/1 build a shot. They have reverted the pulsating LED on boot. Other than some code cleanup for the dialer and in call UI doesn't look like much else has changed. Just a bunch of auto translation import entries.
[Verizon Samsung Galaxy S 4] gonzlobo:
Keeping m9, but keeping an eye on commits. Can't wait until bt is fixed.
[Verizon Samsung Galaxy S 4] jkc120:
Just noticed today that WiFi hotspot doesn't work. It won't turn on. I'm on the 8/29 build.
[Verizon Samsung Galaxy S 4] FernBch:
Interesting. I'm sportin the 9/1 build and it fires right up when turned on.
[Verizon Samsung Galaxy S 4] jkc120:
I had a SoD shortly after trying to turn it on. After the reboot, tethering worked.
[Verizon Samsung Galaxy S 4] FernBch:
Hmmmm....

I've been trying to pay attention to the SOD issue and just can't nail it down. Before 8/29 they were regular and almost predictable. When I flashed 8/29 I also turned off notifications for the apps that were suspect (Tapatalk 4.6.2 and latest Yahoo Mail). I went 72 hrs without one so I turned everything back on. A while later I got one but none of the suspect apps were active. I then factory reset including internal storage wipe, booted into recovery and wiped again, the clean flashed 8/30 and Gapps. I only restored data for sms and mms messages, everything else was setup fresh. Hopefully I'm not gonna jinx myself here but it's been over 48 hours and everything has been excellent. The only issue I had was the pulsating LED not turning off after flashing 8/31 (I reverted back to 8/30). On 9/1 everything seems good, too. The only exception is the issue with my BT earpiece. But I can deal with that until it's fixed.
[Verizon Samsung Galaxy S 4] phonedawg:
Can you please open a bug report for the compass on the M9 ROM at https://jira.cyanogenmod.org. Otherwise, it wont get taken seriously.
[Verizon Samsung Galaxy S 4] jkc120:
Well I don't know what happened but my phone cannot get a 1x or 3g signal!! I even factory reset and flashed 9/2 clean. Wtf? Any ideas what could be wrong? I even tried re-flashing the NC5 radios. NOTHING. I can get LTE but cannot do 3g voice or data. :(
[Verizon Samsung Galaxy S 4] FernBch:
I just read about someone else having what sounds like the same issue. Read page 37 in the modem thread:

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

If I understand what I read he was asked to flash the MDK+nonhlos modem then the NC5 modem only and it fixed him up.

I have heard of this more than once and it only happened when people flashed the NC5+nonhlos, I think.
[Verizon Samsung Galaxy S 4] jkc120:
Thanks, but didn't help. :( I have an empty triangle like you'd have without ANY signal at all. I think my CDMA modem is hosed. :(
[Verizon Samsung Galaxy S 4] FernBch:
I know it's a PITA but have you tried going back to stock?
[Verizon Samsung Galaxy S 4] jkc120:
I'm willing to try if there's a flashable tw ROM that is "close enough" to stock, but I really don't have time to screw with odin/heimdall tonight :(
[Verizon Samsung Galaxy S 4] FernBch:
Unfortunately going all the way back may be what has to happen. I had to do it last year, wasn't happy but it fixed my issue.

If you decide to go that route here's a link for stock in md5.tar format.

http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR

---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------

Oh, and FWIW, I haven't gone past the MK2 modem. It was just a gut feeling for me.

---------- Post added at 08:56 PM ---------- Previous post was at 08:47 PM ----------

I was just looking at the commit list for tomorrow's build. Some interesting items on the list. A couple referencing GPS and location API plus a couple related to telephony and BT. Can't wait for tomorrow so I can flash it!!

---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------

What's up with the compass on M9? I have not flashed it and am not sure what the issue is. Other than it being a little sluggish to come to the right orientation it seems to be working for me (currently on 9/2).

On a side note I have not experienced a SOD since the afternoon of 8/30 (hopefully I have not just jinxed myself).
[Verizon Samsung Galaxy S 4] jkc120:
Well thankfully an "almost stock" TW rom seems to have fixed it. Booted into it, had no data and no texts. Went into settings and network mode was somehow set to WCDMA. I set it to "LTE/CDMA/EvDO" and *boom* started getting a crap load of texts/MMS.

Rebooted into recovery and restoring my cm11 install now....wish me luck!
[Verizon Samsung Galaxy S 4] FernBch:
Cool! At least it looks like an easy fix. Starting over is a PITA!!
[Verizon Samsung Galaxy S 4] jkc120:
Yeah, and I should have backed this TW install up with CWM while I was at it JIC it happens again, but I forgot. :/ oh well, hopefully doesn't happen again!

*edit* and I *think* maybe going to "search for network operator" is what triggered this. Not 100% sure, but I would AVOID tapping that unless you want to go through this PITA process to fix it.
[Verizon Samsung Galaxy S 4] FernBch:
When it happened to me I had to go back and start over. Once I regained root and CWM I backed up. That stock MDK backup lives in my SD card and I have a copy on the PC JIC. When I learned about wiping cache and Davlik before making the back up I went back and did it again. I now have three backups (stock, CM10.2.1, and CM11) and they take up about the same amount of space that two did with without the wipe.
[Verizon Samsung Galaxy S 4] jkc120:
DAMNIT. And restoring my backup of cm11 - no 1x/cdma again.

Whatever happened to that install, it's part of the backup :(
[Verizon Samsung Galaxy S 4] FernBch:
Bummer. :(
[Verizon Samsung Galaxy S 4] jkc120:
Fixed! Per a suggestion on IRC:

- in the phone app, dial: *#*#info#*#*

- I selected "LTE/CDMA auto (PRL)"

I can now send and receive sms and phone works.

Phew.
[Verizon Samsung Galaxy S 4] FernBch:
Totally forgot about that. Cool deal. [emoji106]
[Verizon Samsung Galaxy S 4] jkc120:
Minor update. Doing that alone did not do the trick. I also had to go into the network modes, toggle it to 3g, then back to LTE. Then a reboot. Otherwise, it didn't stick and it would revert to "WCDMA preferred".
[Verizon Samsung Galaxy S 4] gonzlobo:
So I've been running nc5 radios since their release. Any chance *that* has affected my bt issues?
[Verizon Samsung Galaxy S 4] FernBch:
Not Likely. I had BT issues with every radio I have tried. The thing to remember is CM11, just like with CM10, was a major change from Google. Lots of things in coding changed, new drivers, blobs, etc were needed. When CM11 first hit the scene much was not as it should be. Things have come a long way since then.

On a side note I'll be on 9/3 when I return.......
[Verizon Samsung Galaxy S 4] gonzlobo:
Just got a message from [MENTION=2419035]fitsnugly[/MENTION] to try out his kanged CM nightlies. Today's build (0902) has a fix that might repair your BT. I can now reliably connect/disconnect/start/stop my Sennheiser MM400 headset with no issues. I'll see if I can connect to my truck's stereo later this afternoon. At that point, I'll call it good, but so far, all is well!

For those not familiar, the Euroskankers cherry pick CM commits and sends their fixes upstream to the mothership. I used fitsnugly's build with my GNex (CM10). Note: If CM nightlies are too 'dynamic' for your tastes, these builds probably are too (nandroid is your friend).

Thread forum (see post #1)

http://xdaforums.com/showthread.php?t=2385271

Downloads (with md5 files!)

http://fitsnugly.euroskank.com/?rom=cm11&device=jflte

I flashed over official CM with no issues.