goodfellaslxa

I visited my parents this past weekend, who live in a cell dead-zone. Verizon, tmobile, sprint, etc. usually get 0-1 bars, or try to roam. With .13, I was able to get 3g with a speed test of .5 down/.2up. Not blazing, but very usable. Further, when driving between 2 LTE towers, I used to drop to 3g and stay there (if there was an active data connection). Now I either don't drop to 3g, or do so briefly and then reconnect back to LTE. I did have problems the first 2 days with band26 on one of my local towers, but since it was apparently updated, I love the .13 modem. If you are having problems on .13, hopefully they will be remedied very soon.

The .13 modem is better than expected. Today I had to run errands all around the local Court house. Lots of elevators and basements. Not only did my N5 hold a call going down an elevator into the basement, I never went below 3g in the basement. A speed test ran at 1/1mb. Before .13 I could not get 3G in that basement. Today I did not lose it.

It is entirely possible that there was a setting/switch/etc. that Sprint needed to flip when 4.4.3 rolled out, and bleed-edge adopters simply beat them to the punch. I flashed 4.4.3 within an hour of Google posting it. It's my understanding that it's just starting to roll-out OTA.

Well, after 2 days of not being able to get LTE at work, using the .13 modem, today I get bands 25 and 26 without being forced to 3G. Apparently sprint fixed something last night. I am in Louisiana.

How are you flashing the radio.img? Can you flash it using a custom recovery (I use CWM), or do you have a flashable .zip file?

Correct. I get B25 all day long when using .23. If I flash to .13, it will only connect to 3g unless I force it to LTE only, at which point I get either B25 or B26 depending on signal strength (as is intended). The issue is that the .13 radio will not connect to LTE on this tower no matter how strong the signal strength is. It connect briefly (1 sec.) before jumping to 3g. This tower has had LTE for almost a year, and has always worked well. There is either an issue with .13 and some towers, or this tower has not been fully upgraded to be compatible with Spark. This tower never did require me to force LTE, voice calling and LTE have always functioned properly (ie. handing off between the two). Another nearby tower functions properly. I can get B25 or B26 even with a weak signal.

On .23 I get band 25 consistently. On .13 I cannot get LTE unless I force it, at which point I get band 26 but lose voice as a result of forcing LTE. I cannot get LTE on .13 when it's set to auto despite driving past the tower where I get excellent LTE reception. This tower must have an issue with the handoff, as the tower by my home provides bands 25 or 26 depending on what part of my house I'm in, and both are very fast. Maybe a lot of towers haven't been fully upgraded for Spark devices? Not sure why this tower, which seems to be favoring band 26, kicks me to 3g every time.

I just flashed .23 using fastboot, and whereas before I could only get 3g, I'm back on LTE.

I live and work in the Covington/Mandeville area of Louisiana. Prior to the 4.4.3 modem upgrade, I was on LTE 95% of the time, only dropping to 3g in a brief deadzone between two moderate LTE signals. Now I am on 3g constantly, 100% of the time while I am in Covington, and on B25 or B26 while in Madisonville. B26 is great when I get it. I ran a 22mb down, 8mb up speed test... but being forced to 3g the rest of the time doesn't make sense.

Haha, sorry Mike. It was very early in the morning and I was perusing the forums while half awake. I had previously saved the change log update and had posted on other forums wherein people were citing Signalcheck as proof their Nexus 5 wasn't connecting to any other bands. Also, I was able to get my msl from sprint chat simply by saying I needed to reset my phone. The rep gave it up immediately. I have my N5 set to all bands and have checked debug, but only band 25 north of New Orleans.

From the Signalcheck Pro description: What's New Version 4.171 (11/6/2013): Removed recognition of Sprint LTE Band 41 connections. Feature will be improved and included in a future.

I will be driving down Hwy. 190 towards I-12 later today, and will run sensorly during that time as well.

I am the other person in the area. I live in Madisonville. Covington:

Covington is lit up and going strong. Haven't had time to get screenshots of debug, but I will when I can. Speedtest reached 22mbps down, 13mbps up! Had sensorly running while driving to work, it should update soon.

I will map it out later.