[Sprint Samsung Galaxy S 4 Android Development] mark.wayne:
Hello again,

I've flashed the latest iteration of the release from this morning in an effort to resolve some issues that I was having. Previously, last night I discovered that I had issues with phone calls - more specifically, making them. I tested via calling my work mobile cell and noticed that I had issues hearing it dial out, despite the fact that the call did work. In addition to that, my phone was randomly rebooting.

In any case, I attributed it to a bad flash on my part. When I had downloaded the version yesterday, I was at work and was trying to get it "up to par" with the standard apps I'm used to seeing, and so forth. Anyways, just a brief synopsis of the situation prior to my flashing:

* At Home, I have 4G connectivity. It's pretty good connectivity, full bars - quite surprising.

* At Work, I have 3G connectivity. Very good connectivity, full bars.

This morning, I decided to try and get this flashed right. I wiped in recovery, as well as manually formatting the /system folder therein. I flashed the release from earlier this morning, and much to my pleasure, I was able to dial out without the phone locking up - and more importantly, I was able to finally send an MMS text out to a friend of mine.

In any case, the majority of my issues are resolved - however, I'm still seeing data issues with the ROM. I notice, if I'm on WiFi here at work, everything's fine. If I'm off WiFi, certain apps time out and are unresponsive- this is when my phone is on full 3G connectivity. The perk between my testing here at work and at home, is that at home I was on 4G, and was able to run my apps without fail. In fact, prior to leaving for work, I installed most of my apps that way.

However, here at work, I'm strictly on 3G if not on WiFi. While on 3G, I notice in the Google Play Store, I have trouble searching for an app and receive a connection timeout. In my Google+ app (not in browser), I notice that it seems to be endlessly trying to refresh. This time around, however, I managed to perform a logcat from the Android Terminal Emulator app I was using on my phone.

My work laptop doesn't have an ADB setup installed, so I ended up using the SlimFileManager to find the file (for some reason, Win7 isn't showing my text output) and having it sent to myself via Gmail. Ironically, it looks like I wasn't able to send via my mobile's Gmail client until I jumped onto the WiFi, so that I can extract it from my desktop browser and post it here accordingly.

Whew! Hope the attached helps. Any advice would be appreciated- I very much like this theme and would like to see it succeed.

My apologies for the logcat, I think it comes out to 1.5 megs in size. I had to kill Android Terminal Emulator to get it to stop processing.

* Logcat was initiated prior to my attempts to search for an app in Google Play Store. I also opened up Google+ app for it to refresh, which took sometime.

* Logcat was ended when I tried to self-email the output from my phone. I apologize that this wasn't included, but it appears outgoing emails from my phone (when not on WiFi) are succumbing to the data issues I'm seeing.

Long story short:

- Not having trouble when on 4G and WiFi with data issues in actual applications.

- If off WiFi, and connection is 3G (instead of 4G), data issues within Google Play Store, Google+ app, and Gmail client trying to send outbound emails.