metayoshi

If you know how to use fastboot to flash single partitions, you can preserve your user data by not flashing the data partition. If you flash an OTA zip file (or most flashable zips from XDA), you also won't lose any data. Edit: Flashing an OTA zip file will make your recovery stock, though, if your recovery is custom like TWRP or CWM. It's only if you use the flash-all script that comes with the factory image that wipes user data. The thing with manually flashing is to remember to wipe cache and dalvik cache to prevent any issues.

I installed using manual fastboot commands to dirty flash. Everything so far running pretty well. One thing I noticed was I was holding onto a pretty weak LTE signal in the lobby at work, and it was relatively usable. I've never gotten an LTE signal there that was usable before, and I know for sure that the nearest tower hasn't been LTE upgraded yet. Soon though, we'll see. The whiteness of the UI elements kind of threw me off (I'm not much for developer previews/beta software), but I'll get used to it. The power off animation is pretty slick compared to the CRT-off animation of the GB to KK days. Time to enjoy some lollipop goodness.

Yeah, if you've ever tried ART on KitKat and had a lot of apps, this would have happened to you too. The ART runtime compiles apps at first boot or first install, so the ART equivalent of the Dalvik cache is huge enough to make your first boot take forever. This is actually what I'm dreading about most from the update as a 15-20 minute wait for a phone booting up is a significantly large amount of time. Either way, I finally have some peace and quiet at work, so I'm currently downloading the images. Hopefully my phone boots up before my girlfriend starts asking about dinner plans...

No. Your phone will just show LTE with the Spark "sun" icon in your notification bar, whether you're on Spark or just on normal LTE. However, there is an app out there called SignalCheck (with a Lite free version or a Pro version with some extra features) that will tell you whether you are on LTE Band 26 or LTE Band 41 or just the normal Sprint Band 25 (labeled just as "Sprint"). You should check it out.

I, too, have seen the maps, and it does look very impressive. Can't wait to see what the network will actually be like in the next 6 months. I'm kinda disappointed that 2 of the towers I've been watching are scheduled for little to no upgrades, but the rest... It's really nice. The thing that confuses me the most is that one of the towers I'm talking about that will have no upgrades is the tower that services THE Sprint store I went to to get my OG EVO 4G back in 2010, and Epic 4G Touch later on. I guess it must be hard to get any sort of permit for upgrades on that specific tower, because everything around that area seems to be pretty good.

Again, I don't know how Google's firmware works. I'm just making guesses based on what guirae was seeing with picking up LTE in less than 5 minutes. Edit: To add to that, maybe Google's timer is 2 minutes at first and then 5 or 10 minutes later. Again, I don't know.

I'm not speaking for Google or anything, but my guess is they have an adaptive timer that activates an LTE scan that could probably range from a few milliseconds to 5 minutes or longer. As an example, if you just got out of LTE range and it dropped to 3G, it might scan for LTE in 10 seconds or so. After failing a couple times, it'll drop the frequency to every 1 minute or so, and after that it may go up to 5 or 10 minutes to save battery life. We don't really know what that timer is since none of us programmed the actual firmware on the phone.

I'm surprised it's a Note 3 and not a G2. I mean, a Note 3 is not only Single Band LTE, but the fact that you're getting a phablet as a replacement for an average sized phone is also pretty off-putting. I guess they just have an abundance of refurbished Note 3s sitting around in their warehouse?

Yep... I always make sure my buyers are legit. And I always make sure the money is in my Paypal account before shipping. I did have to deal with those Nigerian scam artists before, and I had to try a second chance offer to a 2nd place winner. In the end they didn't respond and I ended up relisting the item. Luckily, it sold for pretty much the same amount to a legit person. Edit: Oh, there's also a reporting mechanism for eBay if you want to report a buyer. I ended up doing it for that specific account, but it takes a while because eBay allows a month or so for the buyer to try to fight the dispute. A month is soooo long when you're trying to sell something right away.

Reading the TKTechNews article about the Verizon and AT&T exclusive gave me a headache. That author can't write grammatically correct sentences to save his life. An "and" was missing the "d." Snapdragon was spelled with a space. Nexus wasn't capitalized in a few places. There were inconsistencies all over the place. I definitely would read this article with a grain of salt, and if he turns out right, well, then either his sources were correct or it was pure coincidence, and good for him, but I cannot take that kind of writing if they are aiming for credibility.

That was the Nexus 4 announcement from 2012. What happened was Google was going to make a huge announcement in New York, but Hurricane Sandy basically stopped those plans. Well, what happened was that they had a quiet launch of the Nexus 4, literally just a press release at the end of October, and they still sold millions. I think after that, Google thought, "Huh, I guess we don't need a fancy event to sell millions." One year later, the Nexus 5 is quietly announced through a Google blog post on Halloween. I don't know what the numbers are for the Nexus 5, but I'm sure there is a pretty sizable number considering the number of us here added with the rest of the Sprint Nexus 5 userbase added with the T-Mo and AT&T userbases, and the rest of the world. Edit: Looks like you edited your post as I was writing mine.

Yeah, it is a bummer for anyone that loves the AOSP experience such as ourselves. There are other options though, and while I also personally hate TouchWiz, I believe Sense and LG's UI have evolved significantly throughout the years, and they don't slow down the UI as much as TouchWiz anymore. My girlfriend has an LG G2 and I personally enjoy using her phone just as much as mine, and I wouldn't mind having an LG phone as a future phone. Another option, if you really like AOSP, is the Moto X. Unlike other OEMs, Motorola has been able to get updates relatively quickly. After reading reviews and watching videos of the original and 2nd gen Moto X, it seems like they have a bunch of features that is a "nice to have" instead of a "gotta have it", but it's all just building on top of AOSP instead of doing crazy modifications like Sense or TouchWiz. I personally would probably get a Moto X successor if Sprint is out of the Nexus program when the time comes for me to upgrade. However, I will personally be staying on the Nexus 5 until it either dies on me, or a Moto X/Nexus like phone with Sprint's VoLTE is available. Since Nexus 5 is a very good Triband phone, I actually don't see a need for me to switch anytime soon, and until big features like Carrier Aggregation, which excites me but doesn't really convince me to get a new handset, or VoLTE becomes available, I don't see a need for me to upgrade. As VoLTE will finally be the big return of data and voice at the same time, that will definitely be a huge step forward in my opinion.

We also have to remember that there was a Verizon and Sprint variation of the Galaxy Nexus, which housed the TI OMAP 4460, and that seemed like a mess of things to manage due to the two different versions (CDMA version and GSM/UMTS version). That mess could have also contributed to Verizon and Sprint getting cut from the Nexus 4. I feel like for the Nexus 5, Sprint was lucky that Google and LG decided on the Snapdragon 800 so implementing a CDMA network on it would be much simpler, and I'm guessing Sprint was willing to get a non-Sprint-unique version of the phone in order to just have it on their lineup. If the Nexus 6 did use the Snapdragon 805, Sprint would probably have to pull some strings to make Google create a CDMA specific handset similar to what happened with the Galaxy Nexus. However, I don't think we Sprint Nexus 5 users are that big of an audience in either group's (Sprint's and Google's) eyes, so I think if we don't get the Nexus 6, it'll probably be due to political reasons more than technical... though, I'm not an expert on what standalone modem chipsets could be used with the Snapdragon 805 to provide a CDMA+LTE based network.

Wow. I know about the "if you don't use it, then it obviously will last a long time" standard, but your battery life is definitely insane. I also turn off location history, but I just set location to Battery Saving instead of Device Only. My phone can last me a little over a day, and that's good enough for me since I don't mind charging it every day. As long as I don't have to charge it in the middle of the day, that's what would really bother me.

I think it depends on the person using the phone. I personally have a lot of sites and articles I like to look at thanks to my many admittedly nerdy interests, and for example's sake, let's say I'm on a 3G connection. I will most likely skip anything that requires Youtube/videos or anything with a data heavy load like some sites with tons of images. Not only that, but with regards to the "suddenly [having] the need to click another webpage or two on a [faster internet connection]"... Well, yes, in a way, but it's more of a "I would have wanted to click that website, but my 3G connection is too slow, so I would rather click on it when I do have a faster connection" rather than a "Oh, I have a faster internet connection so now I want to click on this link that I never had interest in in the first place." Let me use an another extreme unrealistic, but possible easy mathematical example of what AgathosAnthropos probably meant. Let's say you have no more than 30 minutes of free time. On a 3G connection it takes 10 minutes to load an article, and on LTE, it takes 5 minutes. It also takes 5 minutes to read 1 article. Let's say an article takes about 5 MB of data. So on a 3G connection, you use 10 mintues to load an article, another 5 to read it, and then 10 minutes to load a 2nd article, and then 5 minutes to read it again. That's 30 mintues for 10 MB of data, and now your free time is over. Now on an LTE connection, it takes 5 mintues to load the article, another 5 to read, and then another 5 to load a 2nd article, and then another 5 minutes to read, and now you have time to load and read a 3rd article that you would have wanted to look at, but ran out of time on a 3G connection. So now you're using 15 MB of data, and to the user, their "usage" didn't seem like it went up because they were using the phone for 30 minutes both of the time. Obviously this is a different case from your "If I'm done reading, then I'm done reading" scenario since this means I was not done reading by the time my 30 minutes was up on a 3G connection, so I agree that your point is valid, but only if you're really done reading everything you wanted to. There are some people like me though, where there is always something to read, but I just don't have the time, or other higher priority tasks are waiting for me to do, so on an LTE connection, I would naturally be able to click on more of the links I wanted to click on in the first place since it shrinks the amount of time I'm waiting for something to happen.

I don't think they were talking about the same problem in your link. They were having problems making and accepting calls while on LTE, an eCSFB issue. Your problem is the issue (feature?) where the phone is frequently dropping CDMA to scan for LTE, probably a Nexus 5 firmware bug/change that sets the internal timers on the phone to scan for LTE too often. They are completely different and separate issues.

It sounds like network side eCSFB issues. Since a call can't be done on LTE until Sprint implements Voice over LTE, eCSFB is supposed to notify the handset to switch to 3G CDMA to accept the call. Since it sounds like calls work perfectly on 3G, and you're not on some experimental radio like the .15 radio that some people love, it doesn't seem like a handset issue. From what I know, it does sound like a network issue and doesn't have anything to do with your handset. If you've had no problems with LTE prior to recently, perhaps your area is getting Sprint upgrades to enable LTE Band 41 or Band 26, but they didn't fix eCSFB on those bands. That seemed to be a problem that a few markets were having when getting new LTE bands.

Sounds like eCSFB issues. Are you on the latest radio or do you happen to be on one of the experimental pre-release radios?

I use textra, and I agree the new UI looks pretty nice. I don't seem to have the same problems as you. My number keys work, and after sending a test text message, I was able to press back and get to the message list. Maybe see if any settings got messed up after the update (I know I have had an update mess with my settings before). For the number thing, I'm using the stock Google Keyboard, are you using any 3rd party ones? I'm just wondering if maybe there's an interaction issue. I don't know. If all else fails, maybe clear cache and Dalvik cache or uninstall and reinstall the app as a last resort. I also know there was a second update recently, a day after the UI change. Maybe see if you have the latest version. Otherwise, I wish you luck in getting this problem fixed.

The problem is that bits and bytes CAN use 1 TB to 1024 GB OR 1 TB to 1000 GB. If everyone used the same thing, then sure, 1024 gigabytes is 1 TB. I'd have no problem with that except that 1 TB is ALSO 1000 GB. Now which one do I use? Who's using what? The problem is they are BOTH CORRECT depending on which standard they want to follow.

I wholeheartedly disagree. Giga, due to its usage, can mean either 10^9 and 2^30 depending on the context. Hence, we have, confusing calculations like Google saying 1 TB is 1000 GB, vs. Windows saying 1 TB is 931 GB. Same exact word, completely different meaning. Both are right because they're both standardized, but I believe there should be a unique designation for the 2^x family of prefixes because it is simply just different than the 10^x prefixes. With the numbers we're dealing with, it's only a 7% difference, It's not that big of a deal, but when we get into the larger numbers the percent error is going to be bigger. I just disagree that we can have one prefix mean two different things. In that case, we might as well start using 1024 meters to a kilometer when I feel like it, or 1024 for a kilogram whenever we feel like it.

Oh but it is. The politically correct way to say 1024 bytes, 1024^2 bytes, and 1024^3 bytes, is kibibyte, mebibyte, and gibibyte. Only the crazy storage industry (Hard drives and SSDs) and Windows actually standardizes 1024 as a kilobyte instead of a kibibyte. Mac OS and Linux use the correct prefix.

You should be able to see it on the MySprint webpage on Sprint.com. It should look like this: Edit: If you're looking for an app specifically, unfortunately, I don't know of one.

I seem to have the complete opposite experience on the 4.4.4 radio. I feel my LTE scan time is too low and that it scans too frequently. That might seem like a good thing, but where my apartment happens to be, it tends to drop a very good 3G signal very often to look for an LTE signal. I see it happen at least once a day, and I don't check my phone that often at home. Luckily I use WiFi at home, so it's not a big deal, and when I'm out and about, I pretty much have LTE unless I'm at or around work, but the scan time has definitely decreased for me when compared to 4.4.3 and before.

I would jump to the Xperia Z1 Compact so fast if that happened. The only reason I get big phones is because they have the latest and greatest hardware on them, but I hate how huge they are. Sony's the only one who gets it, but unfortunately, no CDMA... yet?