[Verizon Samsung Galaxy S 4] FernBch:
Flashed 10/4 this morning. Looks promising but I don't want to get excited, yet.

This is a preliminary report.

Upon initial boot WiFi and BT can be turned on without any issues. This works from the tile and settings menu.

The first time I turned WiFi off mobile data did not automatically connect, airplane mode had to be cycled. Subsequent checks of turning WiFi off resulted in LTE connecting without any action on my part.

Next I checked connectivity of my Jabra earpiece. I was pleasantly surprised that I can turn BT on from the tile, then turn my Jabra on, and hear the proper tone sequence and see it repeatedly connect and disconnect on it's own. That has not happened in a couple weeks. I need to make/receive a few calls and see if the rest is good again.

GPS and compass (checked with GPS Status & Toolbox) seem to be working correctly. The first time opening the app required about 10 seconds to get a GPS lock. Direction orientation is also correct and returns to the correct orientation when I rotate the device. This happens quickly where before orientation response was very very slow.

Sending/receiving of SMS/MMS on WiFi and mobile data is working.

Looks good so far. I have to go into Better Battery Stats and install as a system app (is needed after each nightly flash) and check for wakelock issues and everything mentioned above after a reboot but this is better than yesterday right away. I also need to look in my logcat and see if any error messages are still present or if I see any new ones.

I have looked in logcat before reboot and I no longer see messages about the wpa_supplicant failing to initiate an AP scan or errors relating to google tts service. Maybe text to speech will work properly again as well.

I'll post again later on...........

Here is a Pre-reboot logcat for S&G's:

https://www.dropbox.com/s/fklhforq577iscp/Log_2014-10-04_09-18-42.txt?dl=0

---------- Post added at 01:10 PM ---------- Previous post was at 12:22 PM ----------

Time for an update. I have noticed something I find very interesting. Hopefully someone can either relay this to invisiblek or get me in contact with him (or him in contact with me) as it may shed light on what the root issue(s) is(are) or could be.

After a reboot the whole WiFi/BT/Mobile Data screwyness has returned.

My Jabra will only connect if I turn it on first and turn BT on from within the settings menu. Before rebooting it worked properly from the tile. The button would even answer and disconnect calls. After reboot it is back to yesterday's wonkyness.

WiFi will not turn on and connect. Turning on WiFi results in it hanging at "Turning on WiFi". It will be on and connected after a reboot. Before rebooting it worked properly.

Compass orientation is now off by 180 degrees. It was also correct before a reboot.

IMPORTANT CLUE:

I noticed this yesterday and again today. After the initial flash of the nightly and startup things seem to work properly, or better at least. After rebooting things are broken. Whatever is happening where WiFi/BT/Mobile Data get borked occurs during the reboot process. It's like something that was written/started/configured or whatever the proper term for the process is changes and/or goes wrong during the first reboot process AFTER the nightly is flashed.

At the risk of sounding redundant I want to emphasize this again. It goes like THIS:

1) Download nightly (sometimes is not working through the settings menu - sometimes does not detect a new nightly - also unable to view changelog)

2) Flash nightly from the update list in settings.

3) Next nightly flashes and phone reboots. Process seems to work 100%.

4) Test and see items mentioned above (Pre-reboot assesment) all appear to work and no errors in logcat.

5) Reboot device. Upon restarting everything seems to go south in a BIG way. WiFi, BT, Mobile Data, GPS, and Compass no longer work properly. I think whatever is going wrong is happening during the reboot process when apps/services, or whatever the proper term is, are being initialized and start up.

Does that make any sense?

Here is the Post Reboot logcat:

https://www.dropbox.com/s/1meg8c6g48rtmg4/Log_2014-10-04_09-37-42.txt?dl=0

This does raise a new question for me. I know that the logcat catches much, and the last_kmsg can be used to get info on a random reboot issue, but is there a different file or file type that I can upload that tracks the boot process? If so I could hopefully get one from the boot process that happens when a nightly is flashed and one from a regular reboot process and maybe they can be compared for differences.

To me it really seems like something is happening during the reboot process and that's where things are getting broken.

Thoughts??????