yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] FernBch:
I have decided to flash the experimental build today. After 30 minutes so far so good. I'll report back later how it is.
[Verizon Samsung Galaxy S 4] orateam:
Is anyone else experienced delayed text messages?

This thread talks about it, but don't see it as a fix.

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

I'm assuming SMS is broken in CM11.
[Verizon Samsung Galaxy S 4] FernBch:
SMS has been working fine here. Only issue I have had I discovered yesterday (see a my post just a few back).
[Verizon Samsung Galaxy S 4] FernBch:
Ok, I've run into an issue with the experimental build and am abandoning it for the 8/15 nightly. After installing Better Battery Stats XDA edition I repeatedly get a force close for Google Play Services and no connection to Google Play. These items worked perfectly under 8/14. Logcat attached:

https://www.dropbox.com/s/4rf3tnf9gpa6191/Log_2014-08-15_11-47-31.txt

Also while browsing Google support in the web browser I experienced a random reboot.
[Verizon Samsung Galaxy S 4] dansan382:
was original on snapshot 2, just flashed snapshot 8 about 2 days ago. so far, battery life is worse and the phone seems to get a little warm. Only problem I'm having is the full charge LED. it seems to come on once the phone hits like 90% charged. I hate how you cant turn off individual battery lights without having to turn them all off.
[Verizon Samsung Galaxy S 4] FernBch:
Green at 90% has been like that for a long time with Android.

---------- Post added at 10:36 PM ---------- Previous post was at 09:40 PM ----------

Earlier I flashed the experimental build but had to back away from it (FC's in Google Play Services), so I flashed 8/15 and had the same problem. I dirty flashed both so that may have been the issue. I restored a nandroid of 8/14 and dirty flashed 8/15 over it and all seems good so far. I'll test drive for a while and report back.

I may try the experimental again but I'll clean flash next time.
[Verizon Samsung Galaxy S 4] FernBch:
I have a new issue to report on the 8/15 nightly. I use a Jabra BT earpiece about 80% of the time. While looking at the tiles if I turn the earpiece off the BT tile says it's still connected. If I turn the BT earpiece back on the tile shows it connected but it actually is not as no sound comes through it. I have to turn BT off, then back on again before the earpiece will actually connect again.

Logcat attached:

https://www.dropbox.com/s/w9ickuogctau55h/Log_2014-08-15_20-42-52.txt
[Verizon Samsung Galaxy S 4] gonzlobo:
Which nightly did they change the kernel? I need to restore to a stable version.
[Verizon Samsung Galaxy S 4] vanberge:
Looks like 8/7 was the last before kernel revamp. Let me know if you find a link to it
[Verizon Samsung Galaxy S 4] dansan382:
Looks like a "long time" only means a few months because I didn't do that on snap shot 2.
[Verizon Samsung Galaxy S 4] gonzlobo:
I rolled back to the 0804-Snapshot, just to be safe.
[Verizon Samsung Galaxy S 4] FernBch:
It's always done it for me and I've been running CM on the GS4 since I got it new. I have always had it on CM11 been running it since CM11 came out.

---------- Post added at 11:08 AM ---------- Previous post was at 11:04 AM ----------

I have made a random reboot discovery. There one forum app that I use (written for a Jeep community - been using it for some time now), when replying to a post I can get a reboot while typing at least once per day. This one instance is almost repeatable. I do, however, still get one randomly. Never had this issue until after the kernel revamp.
[Verizon Samsung Galaxy S 4] gonzlobo:
My crashes *sometime* occurred when I scrolled up/down in plume/feedly/tapatalk. I could scroll all day in Chrome Beta w/o lock ups.
[Verizon Samsung Galaxy S 4] FernBch:
I get reboots scrolling up/down/left/right in Dolphin Browser and tapatalk on rare occasions.
[Verizon Samsung Galaxy S 4] jkc120:
I'm back on the 8/3 nightly but I can't get hangouts or simplytext to send group texts. 8sms works though. Weird. Is MMS/group text working on the 8/16 nightly?

---------- Post added at 01:27 PM ---------- Previous post was at 01:22 PM ----------

Weird if I go into MMS settings and try to select an APN, it's all sprint and metropcs options, no Verizon to speak of.
[Verizon Samsung Galaxy S 4] MustGoFast:
Anyone seen a chance to address the reboot. It's quite annoying. I've found it randomly in different places each time.
[Verizon Samsung Galaxy S 4] jkc120:
tried 8/16, no GPS lock again. I'm staying on 8/3 until the next M release and after they've fixed the plethora of issues. Figured I'd give 8/16 a try but nope.
[Verizon Samsung Galaxy S 4] FernBch:
Nothing that I have noticed. Flashed 8/16 today and I haven't had one yet {fingers crossed}.

Weird, GPS locks for me......
[Verizon Samsung Galaxy S 4] jkc120:
Weird. Guess I will have to lock, then immediately reboot to update and see if that works again, what a PITA.

And on 8/3, going to "display and lights" force closes settings. sigh. Damned if I do, damned if I don't.
[Verizon Samsung Galaxy S 4] FernBch:
Did you restore a nandroid to get back to 8/3? When I tried the experimental I had an FC issue that persisted after going back to 8/14. I then "Factory Reset" and restored my nandroid and the FC issue was gone.
[Verizon Samsung Galaxy S 4] jkc120:
yes I restored a nandroid. that's horribly bad if cwm doesn't format the partitions before restoring or doesn't cleanly restore. I've never had that problem with twrp

---------- Post added at 06:45 PM ---------- Previous post was at 06:22 PM ----------

Dirty flashed 8/16 this time RIGHT after getting a GPS fix on 8/3 and it took longer to lock than usual it seemed, but did work.
[Verizon Samsung Galaxy S 4] FernBch:
I've had that happen before, not sure if CWM formats/wipes partitions automatically on a restore or not.

I also noticed it took a few seconds longer for a GPS lock, too. It seemed like it took a few moments to pick up the sats.
[Verizon Samsung Galaxy S 4] jkc120:
Scrolling around in dolphin hd caused a freeze then reboot today on 8/16, so the instability is still there, at least for me. Can't remember if you said you'd gone without a reboot or not.
[Verizon Samsung Galaxy S 4] FernBch:
That's where I would get them at random, although I did not get one caused by that on 8/16. I see in the 8/17 build there are a couple kernel related commits that may be related to display issues (driver related, underrun issues). I have just flashed it (8/17) so we'll see how it is today. I did check GPS and it gets a lock pretty quickly but to me it still seems like the compass is a little wonky. I do know that originally the compass issue was because Sammy did not release drivers (firmware related) and I am not sure if the compass working properly is still a Sammy issue or not. I think some were using a workaround involving the mag sensor but you know how workarounds can be....
[Verizon Samsung Galaxy S 4] jkc120:
Guess I'm back on the "living dangerously" band wagon :) flashed 8/17 this morning and GPS locked quite quickly.
[Verizon Samsung Galaxy S 4] FernBch:
That's the spirit.
[Verizon Samsung Galaxy S 4] jkc120:
Is it me or is the output sound/gain higher on recent builds? it almost sounds like my speaker might blow out, like NY usual notification sounds are distorted
[Verizon Samsung Galaxy S 4] FernBch:
There was a commit recently to increase in-call volume, maybe it has affected other things, too.

On a bug related note:

I have tested MMS this morning and it seems that I can once again send MMS messages while connected to my home WIFI again. I still have a couple other things to check out but it seems that progress is being made on some things.

I also hope to not jinx myself, but doing the usual activities so far has not resulted in a reboot. Out of all the recent issues that was the one there seemed to be no workaround for.

8/17 is lookin really good so far.

[emoji106]
[Verizon Samsung Galaxy S 4] bsimpson1:
There's definitely been some changes to mpdecision in these recent builds. The behavior of the core hotplugging seems to be much more reasonable and it looks like they've chosen to finally strip the debugging output that previously resulted in very polluted logs.
[Verizon Samsung Galaxy S 4] FernBch:
I guess it is possible the debugging info was so prevalent to help identify issues after the kernel revamp. If issues are being resolved then it would stand to reason that the extra debug info is no longer needed.

If that makes any sense.

---------- Post added at 02:30 PM ---------- Previous post was at 02:05 PM ----------

Well, sadly I must say the random reboot issue persists. Just had one scrolling a pic heavy thread in another forum while using Tapatalk.

I have also noticed the increase in volume. Notification and ringtone volume seem really loud and border on distorted. I'll back off on the volume level for now.

Also, after the reboot WIFI would not reconnect. Not sure if I didn't wait long enough or not but it did reconnect after toggling airplane mode.

Is there a preferred way to possibly capture what happened in the moments before a reboot. Logcats are wiped after the reboot.

---------- Post added at 02:47 PM ---------- Previous post was at 02:30 PM ----------

After the reboot and everything came back I set my phone down and it did like it normally does, screen turned off. A few minutes later I received a text. Problem was I could not wake the screen. I had to do a battery pull and restart it. After restarting WIFI would not auto connect (waited several minutes). I toggled airplane mode on and the WIFI tile said WIFI connected while all other services were off. Toggling airplane mode back off and everything is connected again.

Logcat attached

https://www.dropbox.com/s/3gcotse0kqsgqnw/Log_2014-08-17_11-46-40.txt

Edit:

Also on the first restart after the battery pull messaging FC'd.

2nd Edit:

Rebooting into recovery and wiping cache seems to have corrected the WIFI auto connect for now.
[Verizon Samsung Galaxy S 4] jkc120:
I can cause a random reboot almost 75-80% of the time just typing in Google search (now is disabled).
[Verizon Samsung Galaxy S 4] FernBch:
last_kmsg from last random reboot.

https://www.dropbox.com/s/4nc7dzuhs9c6895/last_kmsg

---------- Post added at 05:05 PM ---------- Previous post was at 04:17 PM ----------

It also looks like the BT earpiece I use will not auto connect either. I have to cycle BT off and back on to get it to connect.
[Verizon Samsung Galaxy S 4] invisiblek:
Experimental build here: <bleh, failure, hold tight, will get something else out>

Need testers, report back if you get any reboots (with a /proc/last_kmsg too please)

Do NOT flash anyone else's kernel over this or it completely defeats the purpose of the test.
[Verizon Samsung Galaxy S 4] bsimpson1:
Aside from last kmesg you could also run something like "logcat *:W > /sdcard/logcat" from Terminal Emulator but the downside would be that it would probably be somewhat taxing on your cpu. The '*:W' argument tells logcat to only report messages labelled as a warning or higher in severity, reducing the log size -- which may be necessary if it's running for hours at a time. Sometimes serious messages can be incorrectly categorized as lower priority messages like 'D (debug)' or 'V (verbose)' though. A better way if possible would be to connect the phone to a computer and run "adb logcat" from the computer.
[Verizon Samsung Galaxy S 4] FernBch:
I have adb 3.07, I'll have to become more familiar with it as I've only used it a couple times for root and whatnot.

Thanks
[Verizon Samsung Galaxy S 4] invisiblek:
Sorry about that guys, yea, don't flash that experimental rom, you wont get display =P

Here's one to test for real: http://www.invisiblek.org/roms/cm-11.0/jflte/cm-11-20140817-UNOFFICIAL-jflte.zip

last_kmsg from a crash if you get one please!
[Verizon Samsung Galaxy S 4] FernBch:
I'm flashing the experimental now.
[Verizon Samsung Galaxy S 4] MustGoFast:
Is anyone else seeing a lock up of WiFi too? I've been getting this on the builds since the last M (and on the last M).

At some point the on/off for wifi will be grayed out and I'll be unable to re-enable wifi. I reboot and this problem goes away.
[Verizon Samsung Galaxy S 4] FernBch:
Experimental is up and running. No FC's on boot is definitely a good sign. Opened Tapatalk first thing and I must say, very nice. Opening the app, then the forum, then this thread was quick. Overall things seem very crisp and snappy. I like it so far. I think I'm gonna stick with this for a couple days anyway and really take it for a test drive.

I have tested GPS and got a lock in a few moments, good there.

First time turning on the Jabra earpiece required cycling BT on and off for it to connect. Subsequent power cycles of the Jabra and it connects just fine.

WIFI speed seems great and auto connects just fine.

Also, the tiles for WIFI and LTE are orange instead of white.

Yup, definitely gonna run this for at least a day or two.

Great work Invisiblek!
[Verizon Samsung Galaxy S 4] vanberge:
Did you clean or dirty flash?
[Verizon Samsung Galaxy S 4] FernBch:
Almost three hours on the experimental build and it's runnin nice and solid.

If you try it make sure to use the latest Gapps. There was an updated version published on 8/11.
[Verizon Samsung Galaxy S 4] bsimpson1:
I flashed the test build also and have so far had no reboots either.
[Verizon Samsung Galaxy S 4] vanberge:
I flashed invisiblek's test build... Smooth. No problems to report. Most importantly no reboots. Going on 8 hours and maybe 3 heavy
[Verizon Samsung Galaxy S 4] wessiide:
Anyone have a link to the gapps package we should be using on these builds?
[Verizon Samsung Galaxy S 4] FernBch:
Gapps are all the same as they are written by Google, unless you get one that is themed.

I personally have always used PA Gapps without issue. They updated their packages on 8/11 and all of the core components are the latest version (my system reports 4.4.4 on many of them).

But you may use the flavor of your choice, just make sure to use the latest available version and that they are for KitKat (4.4.x)
[Verizon Samsung Galaxy S 4] wessiide:
Is mms working on the experimental build? Before the latest nightlys I had to toggle airplane mode every time I tried to send a text message, but now that is gone but mms doesn't send anymore. Plus the random reboots but hoping that's been solved now.
[Verizon Samsung Galaxy S 4] vanberge:
I just used the latest from cyanogenmods website.
[Verizon Samsung Galaxy S 4] FernBch:
Been running the experimental for the last 14 hours. Have NOT experienced any reboots at this time. Only issue I have had is when I turn off my Jabra BT earpiece and turn it back on I have to cycle BT off and back on before it will connect. Unpairing and pairing does not fix the issue.

Logcat attached:

https://www.dropbox.com/s/tcehiha18bdu94j/Log_2014-08-18_09-52-08.txt
[Verizon Samsung Galaxy S 4] brizey:
Was the fix for the test a kernel fix or a ROM fix or both?
[Verizon Samsung Galaxy S 4] FernBch:
Because of the changes in behavior (seems stable and more responsive) I would guess both. Although it doesn't matter to me because it is very stable and I have not had any major issues.
[Verizon Samsung Galaxy S 4] jkc120:
I wonder if the responsiveness is just an added bonus or part of the reason they were updating the kernel stuff? Do you have any objective data on the improvements in performance/responsiveness? Don't mean to doubt you, but could it be placebo?
[Verizon Samsung Galaxy S 4] joshm.1219:
How could one get objective data of performance /responsiveness? Outside of benchmarking apps, which of course don't mean anything.

Honest question, not trying to troll if it sounds like that
[Verizon Samsung Galaxy S 4] invisiblek:
I'm confident we have a winner here.

All changes have been pushed.

Next nightly will have the goods.

Thanks for all the help testing everyone!
[Verizon Samsung Galaxy S 4] bsimpson1:
I don't know about performance improvements regarding that specific test build, but I'd say that this new group of builds definitely performs better despite the the reboot issue in some builds. I know for a fact that, because mpdecision no longer reports all the intricate details of what it's doing, there is less overhead, as I used to overwrite the relevant bytes of the mpdecision binary with null data to remove the debugging myself, and would see a substantial reduction in idle CPU usage (Idle here meaning the screen is on and set to a long auto-off time, but absolutely nothing is being done to the phone. Previously, with the debugging info being reported, after stopping every possible app, daemon (not mpdecision, obviously), and any other unnecessary process for the sake of more accurately reflecting only the relevant usage, the system would average between about 5-7% with periodic spikes up to 8-12% CPU on a single core. With the modified binary, the usage would drop to to an average of 1% with no spikes higher than 2% and occasionally reaching 0%. This modification isn't necessary anymore since these new builds no longer include versions that flood the logs. I still, however modify sensors.8960msm.so to prevent the temperature/HumiditySensor from writing to the log about how "mcompengine is null" every few seconds. I doubt this has much of an impact though.
[Verizon Samsung Galaxy S 4] brizey:
I guess I should have been more clear: if the fix for the reboots is in the kernel/modules then an extracted kernel may help all of the CM-based ROMs, or at least help them more quickly since a lot of them use the CM kernel straight up or only very lightly modified. ROM fixes may take a bit more time to percolate.
[Verizon Samsung Galaxy S 4] vanberge:
Yeah I'm with Fern here. The test build has been rock solid for me...
[Verizon Samsung Galaxy S 4] gonzlobo:
Cool. Can't wait to flash.

I had to run with 0804 since I was on vacation and needed a stable build (was GPSing all day).
[Verizon Samsung Galaxy S 4] Loop4zil:
I get WiFi lock when I transition from WiFi to Data...for example getting in my car and driving away from my house: typically by the time I hit the end of my drive way I should be out of range of WiFi and then VzW Data takes over...with the last 2 or 3 nightlies the LTE comes on and the WiFi symbol stays on ...but I'm not getting any data (lol). When this happens I can't turn off WiFi or Data either. I have to reboot the phone to fix OR I turn off the WiFi and switch to Data prior to outdistancing WiFi signal.

Also

My Bluetooth will not connect unless I turn off BT and then restart BT. Some times BT will just cut out in the middle of connectivity. So yeah...typical nightlie stuff...

I have been considering doing a full wipe and install...but I just cant bring myself to do it...lazy

I hope they have something for BT and WiFi in the next couple of nightlie updates.
[Verizon Samsung Galaxy S 4] kyuubi08:
so i just migrated my phone over to tmobile from verizon after being taken off my family plan. it pulls everything that it should, and for the most part, runs the way it should. however, i do have an issue receiving and making phone calls. i am not able to receive phone calls, and anytime i try to make a phone call, the end button does not actually end the call. is there an easy fix for this?
[Verizon Samsung Galaxy S 4] FernBch:
Definitely a winner. I have been running this for 26 hours now. Absolutely ZERO reboots, more responsive, solid, and clean. Other than a minor BT issue it is a vast improvement over just a few days ago. I give it one gigantic thumbs up. Can't wait for 8/19 to post up so I can flash away!!
[Verizon Samsung Galaxy S 4] bsimpson1:
When you guys are getting GPS locks, are you sure it's GPS and not network-based location? I just noticed that I'm completely unable to get any GPS apps to report my location using "device only" location mode.
[Verizon Samsung Galaxy S 4] wessiide:
On which build?

Anyone tried the new nightly yet? Is it essentially same as experimental build or were there anymore changes?
[Verizon Samsung Galaxy S 4] jkc120:
Just flashed the 8/19 build. Couple of things (some of which are not unique to this build):

- mobile data did not work, I had to toggle airplane mode to get it to work after it booted

- vibration intensity does not survive a reboot, it keeps resetting itself to 50%

- soft nav buttons remain enabled after I update, but the samsung buttons are active with no backlight. I have to toggle nav off and back on again to fix that (once each time I update)

I'l chime in later if I find anything else. It does seem snappier, but I can't quantify it.
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 8/19 earlier today. I see one issue that has been around for a while. When I leave an area where I am on WIFI mobile data does not automatically connect, I have to toggle airplane mode for it to connect. Also, if I leave an LTE are and go to a 3G or no service area mobile data either does not automatically reconnect or does not switch back to LTE.

Screenshot

Logcat

https://www.dropbox.com/s/xxsmfq1err9tydg/Log_2014-08-19_08-37-49.txt
[Verizon Samsung Galaxy S 4] gonzlobo:
0819 looks good. Previous builds would've crashed by now. God job invisblek.
[Verizon Samsung Galaxy S 4] jkc120:
Can't send group message with 8sms

Tried to send a group message and it got stuck sending (noticed because my batter was being destroyed due to it keeping the phone awake).

---------- Post added at 01:28 PM ---------- Previous post was at 01:02 PM ----------

Yeah, MMS sending is completely broken for me. anyone else?
[Verizon Samsung Galaxy S 4] FernBch:
Confirmed. MMS will not send to a group or individual.

---------- Post added at 04:42 PM ---------- Previous post was at 04:38 PM ----------

One more item. When opening the voice dialer and speaking "Open APN's" nothing happens. Unless the method to open APN settings has changed they are not accessable.
[Verizon Samsung Galaxy S 4] jkc120:
Thanks for checking. Bummer. I tried different apps and manually specifying APN MMS settings, nothing I can do allows it to send.
[Verizon Samsung Galaxy S 4] phonedawg:
Have these been fixed in that build?

https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-25975

https://jira.cyanogenmod.org/browse/CYAN-2927
[Verizon Samsung Galaxy S 4] jkc120:
I haven't experience the first one, but yes the 2nd still is an issue, at least for me.
[Verizon Samsung Galaxy S 4] jkc120:
Looks like MMS should get fixed in 8/20:

http://review.cyanogenmod.org/#/c/70371/
[Verizon Samsung Galaxy S 4] phonedawg:
Both issues exist in M9. These are the only issues that still exist although the links state them as fixed.

The compass issue is annoying. I can't use my phone when I travel of the country because of the GSM issue.

I am hoping they get fixed soon. As long as they exist, it does not feel like I am using a fully functional ROM.
[Verizon Samsung Galaxy S 4] gonzlobo:
My phone is very stable, but BT is slightly flaky *. I use BT audio about 8 hours a day switching between 2 devices (headset and truck stereo). Other than that, great build.

*Haven't bothered to reboot since loading, so it may be as simple as that.

---------- Post added at 06:09 PM ---------- Previous post was at 05:28 PM ----------

Ugh, after rebooting, it refuses to release the previously listened to device. I can't switch between devices.
[Verizon Samsung Galaxy S 4] bsimpson1:
Mine isnt working on the test build or the 8-19 release
[Verizon Samsung Galaxy S 4] Nath5:
Is anyone having problems with the ir remote. I am sure I used it in the past.
[Verizon Samsung Galaxy S 4] gonzlobo:
Bluetooth refuses to release BT, so back to 0804.

-signed Flaky Flasher.
[Verizon Samsung Galaxy S 4] jkc120:
So we may get an MMS fix in the 8/20 nightly, but there were a bunch of jf kernel commits as well:

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

Not sure if they're relevant to all jf variants or if it's a harmless merge, but just a heads up...
[Verizon Samsung Galaxy S 4] jkc120:
8/20 GPS and MMS both work :) haven't had it booted long enough to confirm stability just yet.