metayoshi

Got to test out the band 41 here in Eagle Rock on the corner of Eagle Rock and Colorado. Only giving me 25 down and 12 up, but I'm just glad that it transitions to band 41 smoothly with this latest update Sent from my Nexus 5 using Tapatalk

It's most likely not possible since the radio updates are in binary form, whereas things like AOSP based ROMs like CyanodenMod and kernels like Franco's kernel or the kernel page from Samsung, http://opensource.samsung.com/ are actual source code. That's why ROM developers love it when Samsung and other OEMs release their kernel source as soon as possible. It makes it easier to see what changes have been made so that they can easily change CyanogenMod, Slim ROMs, and put up modified TouchWiz/Sense/etc. kernels. Radios are never released in code form because they usually have some proprietary code specific to the radio/modem that the phone is using, so it's nearly impossible to reverse engineer what's in the radio.

I came from stock settings, Band 26 and 41 off, and after the update, mine turned into Band 26, on, priority 1, and Band 41, on, Priority 1, so my LTE priorities are B25 - 1, B26 - 2, B41 - 3. As previously discussed in many different threads on this site, I don't think priority matters. Sprint's towers will move you to whatever Band it thinks you should be on. Even though B41 was Priority 3, I was able to connect to it just fine in the 1 place near work that I know that has it.

It sounds like it depends on who you ask. I am personally very satisfied with this update. I finally have Spark working on my Nexus 5 seamlessly, and it seems like it's working in places that even the .15 radio wasn't able to for me. After I updated I did a profile update and I just left everything as it is: Mobile Preferred Network Type is Global, and all Band Priorities are set to 1 in the Edit menu.

Yeah, it depends where you are for sure. I remember in LA at my parents' house, when I used the .15 radio, I was getting ~30 Mbps. Here in Orange County at the airport is where I got the ~62 Mbps I posted a few pages ago.

Oh I see what your saying. The most likely case that you have, then, is that SuperSU is in your /data partition, so unless you wiped your data, you would have kept it.

I have yet to see the OTA update.zip or an untouched unrooted stock flashable zip go up yet, so the ROM you flashed from XDA was most likely Pre-rooted, so you didn't have to do anything.

pretty much. I was debating on waiting for a flashable zip, but I couldn't wait, plus I'm pretty comfortable using fastboot, so I decided to take the plunge. Sent from my Nexus 5 using Tapatalk

So I was able to try an area I tried to use the .15 radio in with the new update. It didn't connect right away, so I just did a profile update and prl update for the same of having a new radio. In the middle of the prl update, my phone switched to LTE and my prl update hung, probably due to the switch. Well... [emoji38] Sent from my Nexus 5 using Tapatalk

I fastboot flashed boot, radio, and system from the factory image, and then re-flashed SuperSU 1.97 through TWRP, and wiped cache and Dalvik Cache. I didn't expect a non-OTA-update.zip method to enable the Spark bands, but it looks like B26 and B41 are now enabled. I currently have no way to test whether I can connect to B41 yet, but I'm going up to LA for my cousin's wedding this weekend, so I should be able to test B41 up there. I've gotten B41 at my parent's house in LA a while ago with the .15 radio, so I hope I see good results up there.

Well... The .15 radio was never released in an official OTA due to its bugginess with eCSFB, and who knows what else. I wouldn't be surprised if the issue you're seeing was one of the bugs that Google/LG knew to be squished between .15 and .17.

Yeah, I used to be a huge fan of CWM recovery. I just got used to it from the OG EVO days. But that new security feature where I can't export my backup to a PC or something really killed it for me. TWRP all the way now.

It's definitely slowed down a bit down here, but I've seen some progress. A tower in Tustin just recently got LTE, and then two of the 4 towers I would love to get upgraded in Irvine finally have NV 3G. Definitely not as fast as I would like them to be, but there's definitely something going on.

I've had that happen to me a few times as well. I never figured out what caused it, but I didn't really care too much. Sent from my Nexus 5 using Tapatalk

I'm, by all means, not a heavy user. I typically only use my phone for a quick look at my twitter feed or Facebook, looking at news related to tech, browsing forums like this one and doing a quick Yelp. At work, I only use it for phone calls, so I typically get ~1 hour 30 minutes to 2 hours max. Right now I'm at 68% with 1 hour and 1 minute of screen on time after being off the charger for 14 hours, and in the 4 minutes it took to write this post, it's already down to 66%. Sent from my Nexus 5 using Tapatalk

I used to see a pretty noticeable difference with battery life with Google Now on pretty much all my android devices since I had the Epic 4G Touch. After going through different forums, I actually learned that it was simply location history that I had to turn off, and Google Now could still be on without sucking all of my battery life. I now have Google Now on, but location history turned off on my Nexus. To turn it off, you can go to Settings -> Location -> Google Location Reporting -> Location History -> Off. The other Google Service I know of that sucks battery life is Google+ Auto backup. I turn that off as well, since I'm not as paranoid as some people about keeping pictures saved to Google+ all the time. I am currently at 93% battery life remaining after 7h 46m 4s on battery, though I also have mobile data turned off since I work in a huge RF shield and I get pretty crappy Sprint signal in my office. Either way, it pretty much lasts me the whole day and I end up with around 60% left when I go to bed at 1 or 2 am.

Wow... That's... impressive. Samsung is actually supporting a 2 year old device, whether it's meant for VM/BST or not. As a previous GS3 owner, I can say that the GS3 was an awesome device aside from the lagginess introduced by Touchwiz. I may have actually kept mine to this day if it was triband capable.

MMS does work over WiFi for Textra as well. I have it enabled in the app: You can see I have prefer WiFi checked and I haven't missed any mms messages that I know of at home when I'm connected to WiFi. As a side note, I have Activate Mobile Data checked as well, but that's because I'm in a crappy signal area during work, so I disable mobile data, and if I don't have that option enabled, I'll miss MMS messages for obvious reasons.

I don't know the real reason for that 56% "time without a signal" number, but my guess is since the .15 radio is known to have issues with e/CSFB, and since I've seen screenshots way long ago where people were connected to LTE, but their notifications window showed "Searching for Service" instead of "Sprint", it's probably due to not being connected to CDMA all the time. I know people love to use the .15 radio as their daily driver, and if it works for them, it's perfectly ok, but there's a reason the first publicly released radio version was the .17 one. ... After looking around, here's one of the posts that said that:

What this guy said . But really, I'm confident Spark is coming. Heck, we even know it's in the next update. We even know that the update exists somewhere out there, but it's not being pushed to the public yet. It's basically 100% confirmed that Spark is in the next update. We're just waiting for Google to finalize the update process.

I went onto twitter to call out @sprint and even included @googlenexus to see what the twitter CS reps would say. @Sprint responded with the "it may take a week" bs, and all is quiet on the @googlenexus front. Oh well. Anytime this week would satisfy me. If nothing is out by the 21st, Sprint definitely got shafted by Google by announcing an update that didn't happen, and I'll be a little disappointed, but not angry or anything. If it takes a month, I'll definitely be more disappointed. What bothers me the most is actually how much more bad rep Sprint is getting for announcing an update that will probably show up in the next few days. I went onto XDA and there's so much "more Sprint lies" BS, that I think announcing an update this early is hurting their reputation more than anything. It's kind of sad how shortsighted people are, but what can I do? Sent from my Nexus 5 using Tapatalk

Remember guys, be patient. Sprint also jumped the gun a bit with KOT49H: http://www.androidpolice.com/2013/12/09/sprint-says-the-nexus-5-is-getting-an-update-to-kot49h-today-but-what-happened-to-kot49e/ Essentially, it looks like Sprint just likes to one-up Google by posting the update details before Google even makes it available.

Yup. I've already got my clean system image of KOT49H ready to be flashed, and I'm just waiting for someone to get the OTA .zip file on XDA or wherever it appears first.

Since the Nexus 5 itself is generic hardware, like what jeremyvbk above said, it's entirely possible that all the people that get it today are actually on T-Mobile. Sprint posted themselves that the rollout will start today and should reach 100% on the 21st, so whether that's quick or not is up to your interpretation. https://community.sprint.com/baw/message/769011#769011

Orange data icons, whether Wifi, 3G, or LTE, simply means you're not connected to Google's Services at that moment in time. You could technically have a perfect internet connection, but if Google's services are down, the icons will be orange. If you're using a custom ROM, it's possible that they can change the orange to mean "connected with no active data transfer", but the little up and down arrows usually indicate that, whereas orange means not connected to Google services. As for the straight to voicemail issues, I've had that, but only when in a fringe signal area like where I work. I personally don't use GV or Hangouts.