HotblackDesiato

Yeah I notice in my area B26 has about the same signal as B25 if not a little worse, can't wait for Sprint to finally optimize it. I've had my Nexus 5 since August and it's been the same no improvement, hopefully by the new year it will be optimized. It's quite funny actually I get no B25/B26 in my house but I am picking up B41 from a Clearwire site a few blocks away.

Very similar up in the Pottstown area, i rarely "see" LTE800 despite being surrounded by it. If i do transition to LTE800 it's typically for a few seconds before dropping to EV-DO. On a plus LTE2500 rollout seems to be picking up pace.

Noticed a lot of B26 today Lansdale/West Point, Skippack, Schwenkesville, New Hanover and Gilbertsville. Doesn't seem that well configured at present but progress.

Update arrived this afternoon from stock 4.4.2(bb.23) to 4.4.3(bb.13) it seems largely invisible to me. No obvious change in RF performance on B25. Still no luck connecting to B41, toggled in and out of airplane mode and rebooted within 1/4mile of B41 site. B26 is not here yet so i can't comment.  

I had issues for around 30min ~6PM in the NW Philly suburbs. Was rolling between No signal-1xRTT-eHRPD for most of the time but even with a strong eHRPD signal there was no throughput. 

Has anyone noticed when they perform an update profile that their band 41 changes from first scan to second scan priority?

Yes same here.

Had the nexus gotten the update to allow connection? I don't believe it has.

No i do not believe so but i thought i'd read some N5 users had successfully connected, just by activating the bands.

I was more surprised b41 was already in this area. 

Surrounded by B41 here, at least according to the Sprint coverage map, but i can't get my N5 to connect to it. That said, if i use my UK SIM and run a network search i do not see "Clear" that some others are reporting either.

With e/CSFB, as long as you are remaining on LTE, you are not actually returning to the Pennsauken MSC.  You are staying registered at the Philadelphia MSC with any paging messages from that MSC being tunneled through LTE to wherever you are located.

 

AJ

Thanks! Makes sense now!

This is the CSFB issue.  The Pennsauken switch does not have CSFB active, yet.  It will keep shunting you back to 3G when on a Pennsauken LTE site until that switch receives CSFB upgrades.  It will probably be resolved within 2-3 weeks.

 

Robert

Thanks, yes i understand the basic CSFB issue shunting me back to 3G, what was puzzling me was why being on the Philadelphia switch for a few hours then meant LTE worked well when i returned to Pennsauken switch, at least until the phone was switch off again. 

http://www.engadget.com/2013/12/18/ting-sprint-spark-lte-select-phones/

 

Ting launches Galaxy Mega, S4 mini, and Netgear ZING with Spark Access.

More here....  https://ting.com/blog/ting-goes-for-three-tri-band-lte/

Still struggling to understand my LTE issues

Towers on the Philadelphia MSC always work as they should but the Pennsauken MSC is very odd.

The N5 will connect to a tower using LTE but after 30sec it gets forced back to 3G, it then attempts to re-connect every 12minutes. As soon as i drive on to a Philadelphia MSC tower all is fine, and If i spend more than a couple of hours on the Philadelphia MSC (on LTE) then i can typically drive back to the Pennsauken MSC and have no further LTE issues for days at a time BUT if i turn the phone off for a few hours then, once switched back on, it reverts to being kicked off of LTE after 30sec.

I assume you're using the new (4.4.1) radio?  Curious about other people's experience on 4.4.2.  I've thus far not taken the time to sideload it (from 4.4), and haven't gotten an OTA yet.

I'm finding the radio 5-6dBm under where it was on 4.4.  in the same location where prior to the update i was seeing a steady 115dBm, post update it initially found LTE but at 120dBm and  then dropped out of LTE after 30sec. 

I've also had the other issue described where the after toggling in and out of airplane mode the phone will not re-acquire the network, needs to be power cycled.

My LTE issues seem to related to the switch, the Philadelphia MSC sites seem to be fine while  Pennsauken MSC sites are not, at least some of the time. I'd never realized quite how mixed up sites the were in this area.  

N5 via Google

SEPA/Philadelphia Market.

Mixed results here on 3/4G accepted sites.

Some towers seem to allow LTE without an issue but some others causing problems.

3/4G tower covering 19525 no LTE connection, connects using 3G and every 3minutes drops the network completely and takes around 40sec to re-acquire then 3mins later drops it again repeating the sequence over and over.

3/4G tower covering 19486 i guess has the more typical issue, intermittent LTE, so connects using 3G then every 12mins connects to LTE for around 10secs before rolling back to 3G.