metayoshi

Dropped to 3g on the first floor... I guess I have to wait for B26 for that, but still, very much improved since last year.

Finally seeing LTE in Irvine near the small Kaiser Permanente on Barranca and E Yale Loop. I finally have usable data while waiting for a Dr. appointment. Wow. This area has improved a lot. Just waiting for the one near work and the one near the district now.

You must be lucky to get good Wimax service here in Tustin because Wimax only covered very specific locations, namely, newport/mcfadden, 17th/the 55 freeway, very small parts of Tustin marketplace, Microcenter, and irvine blvd/newport. If you get B41 at all of those locations, there are pretty much no other towers to convert (you'd be able to see that on the Clearwire map in the Premier Sponsors section), and at this point, B25 and some new Sprint B41 LTE are covering those areas and more now.

The tower off of Red Hill and the 5? I live here, I would know if it was broadcasting for a while. Many towers around it have been broadcasting, but this specific tower wasn't broadcasting LTE until I got home on the 30th. In fact, S4GRU doesn't even show it as 4G accepted yet since there hasn't been any updates for a while. I do agree that Tustin does need work, but I don't think too many areas will improve until B26 LTE comes in a couple years to expand the footprint since most towers are broadcasting B25 now, and there are even some that have B41 enabled (Irvine blvd and Newport Ave is one area that has B41 now). I'm just happy that it's been so much better than before.

Wow, came home today to B25 LTE! I am so happy, lol. Only got 4-5 Mbps down, but who cares right now about since I finally have it. This is the tower right near the 5 freeway and Red Hill in Tustin. Just looked at my phone while getting out of my car, and had a great LTE signal.

Oh really? I was at Knott's when Scary Farm was going on, and I could hardly use what B25 I was able to get. Looks like they really are improving fast.

You're right, it did not change between 5.0 and 5.0.1. Whenever 5.1 comes out, that's when they said Silent mode will return.

My opinion in the whole Priority mode is that they basically "Windows 8"ed us Android users, i.e. taking something that people know and got used to and moving it somewhere else without any warning and the requirement of prior knowledge of the details of the update or the Googling of the answer to know what to do. For example, pressing down on the volume rocker multiple times to silence the phone is just as standard as finding the "Shutdown" button in the start menu of Windows since Windows 95. Microsoft decided that Windows 8 will have this new and "awesome" Charms bar, and that's where they'll hide the power options for Shutdown, Restart, and Sleep... Literally, hide. The first time I got Windows 8, I had to Google something as basic as how to shutdown the computer. Yes, it's doable, but was it really necessary to move it? Obviously, public reaction to the power options, among a host of other things, was indisputably negative. Eventually, in the Windows 8.1 Update, they returned the power options to the Start Screen, where it's obvious, and in my opinion, where it belongs. Same thing with the Silence mode. Yes, it can be achieved still in Lollipop, but was it really necessary to change how it's been done ever since cell phones have existed? Haven't they learned from Windows 8's mistakes that people don't like to change something that should be as basic as silencing the phone? I apologize for my rant, but even though I'm OK with this Priority mode (since I Googled it and know the answer already), I know a lot of people won't be, simply because of the fact that it takes a Google search to figure it out. I come from a background of web design, even though I'm currently a firmware engineer, and both the Windows 8 power options and Android Lollipop silence mode changes are huge User Interface blunders in my book. The UI's only job is to make things easier for a casual user. The fact that a user has to Google something to do something basic means the UI is failing. With that said, I'll be glad if Silent mode is back in 5.1. Windows 8 learned from their mistakes, it's only natural if Android does as well.

At least in my experience, WiMAX coverage was pretty horrible. No matter how many sites the LA metro area had of Clear's WiMAX, I could barely connect to it with my EVO 4G and E4GT. On the other hand Clear's B41 has been much more accessible, and with Sprint's B41 sites popping up randomly, it's definitely a gargantuan improvement over WiMAX coverage.

It's also out for the Nexus 4 too, now that I look closely. The main two that don't have it are the Nexus 5 and the Nexus 7 (2012).

5.0.1 doesn't even have factory images for the Nexus 5. Only the Nexus 7 (2013), 9, and 10 have this update so far. I did get the OTA for my Nexus 7 this Sunday, and it's been working fine so far.

Does he know exactly where he's not getting signal? A 10 mile radius is a pretty large area, as 10 miles is pretty much from home to work for me, yet I know a very large dead spot within that 10 mile distance, mainly because there are no towers there or very few towers can actually reach the areas. Most towers have been NV 3G upgraded and quite a lot are B25 capable, but that dead spot will always be there until either LTE 800 appears (which is not for a couple of years for us Orange County, CA people), or until they add towers there. Maybe your friend is in a similar situation? Otherwise, I would pinpoint the towers he should be getting connected to and start reporting them to Sprint, especially if it's an LTE launched market.

It doesn't look like the bug fix update I'm waiting for: http://www.xda-developers.com/android/android-5-0-1_r1-source-images/ Apparently, the Nexus 7 (2013) images are out, but who knows if the OTA will be pulled (or not even sent) again.

Finally. While I have my Nexus 5 unlocked and ready to flash updates anytime, I typically wait for OTAs on my Nexus 7 2013 since it's shared between me and my girlfriend. So my Nexus 5 is enjoying Lollipop for some time now, but the Nexus 7 hasn't gotten an OTA, and with the issues I've heard on the Nexus 7 on XDA, it sounded like Google pulled the OTA to make more bug fixes for the Nexus 7. I hope this is it.

Went to Maggiano's at the Grove this past Saturday night for a cousin's birthday, and, wow, that place was congested. I had full bars of B25 LTE and my speeds were 0.23 Mbps down. Ouch. That's definitely a location that could use some B41 for the busy days like that.

Great video. The difference is definitely noticeable in most apps, but the question is, is the extra latency ok? Judging by the video, I'd say so. I personally don't have encryption enabled, but for those that what it, I don't think it'll affect the day to day usage of the phone.

It's possible that either the tower nearest you went down, or they were doing equipment upgrades in the middle of the night. I've had more than my fair share of experiences like that. I literally live on the same block of a Sprint tower, and I've had the tower go down and my phone go roaming at home. I usually get good 3G (like actually usable 3G, even before NV) signal at home. Luckily for me, I live with my girlfriend who also uses Sprint, so we can see that we both go roaming when this happens and I know it's not a phone problem.

This. Yeah, I had to figure that out right before watching a movie last Friday. I used to silence my phone by holding the power button and then selecting silent, but that option is gone now as well. Holding the power button now just has "Power off". It was faster to do that for me than pressing down on the volume rocker until it goes into silent mode, so that was my normal method. Kind of unintuitive in my opinion. I think the word "silent" is more specific than "none", and I couldn't figure it out for a minute. It's not really a bug, more of an inconvenience in the sense that something that used to be there is now replaced by something else, and there's no real indication of it other than figuring it out yourself or Googling it. Otherwise I'm pretty happy with the update. Just have to get used to new ways of doing the same things.

Now that you mention it, it looks like I'm having the same issue as well. I double checked, and I do have Settings -> WiFi -> Advanced -> "Scanning always available" unchecked, but from 10 AM, which is when I tuned off WiFi, to now, I still have WiFi "on" according to the battery history graph.. This is probably that same WiFi battery drain bug that was supposedly squished a while ago on Lollipop. Hopefully this isn't the next Camera Daemon bug that plagued KitKat.

As what bigmachine said, Spark is pretty widespread in LA. I also typically get the mid 20s to 30s, which is great in my opinion, and I've seen it go up to 74 in certain places like West Hall of the LA Convention Center.

I had that issue back on Kit Kat. Uninstalled sensorly and it's been working fine. Too bad, Sensorly was a great app.

Oh no... Good luck. I hope something works. The 72786 code is usually the one thing that fixes all telephony related issues with my smartphones, but I've been doing a lot less modifications to my Nexus 5 compared to my Galaxy S 3 from a long time ago, so I haven't had to do that ever since I switched.

I'm surprised wiping the cache had that effect on your phone. I don't know if this will work since you have "no provider/no service", but it should be worth a try. Go into your phone app, then type *#*#72786#*#* and your phone should try reactivating itself on Sprint. Edit: Actually, rereading your post, it was probably not the wiping cache that cause this, but the fact that you shut down the phone in the middle of wiping the cache. Hopefully, you didn't accidentally erase something in the flash memory that was holding your phone information. That might be unfixable unless you happened to have your EFS backed up.

Make sure to have the latest version of adb as well, or else you won't be able to do it. A copy of it is attached to the bottom of the first post in the XDA link that liveToCheck posted.

I at least answered your question, though, didn't I? I was just trying to cover all bases since you weren't specific on which way you your trying to sideload the update.