Craig

How were you able to see if your were roaming on cricket, and not Verizon ?

 

 

Sent from my iPhone 5s using Tapatalk

Signal Check app probably. It tells you who you are connected to.

Sent from my Nexus 5 using Tapatalk

LTE downtown again, screen shots in the link.

Band 25, weak signal and speeds around 2 down and up.

https://docs.google.com/folder/d/0BxTEYpuf2UqIZHRCdjNRQTFKZFk/edit

 

Sent from my Nexus 5 using Tapatalk

Not letting us view it. . .

Sent from my Nexus 5 using Tapatalk

I have been combing through this forum, so I apologize for asking this since I am sure it has been asked MANY times. Even tried searching, but with so many results and not having a lot of time since I should be working, I thought I would just post and hope for a quick and simple response.

 

I bought a N5 yesterday and ended up flashing the .17 radio and a custom PRL and then also enabled B26. My question is if there is something I am missing for B26 from the N5? I know it isn't "officially" supported yet, but I have read numerous reports that it works on the N5 by just enabling the band.

 

So, I am just not completely sure if I'm missing something, or if it is just that the N5's RF performance is so good that it never even needs to look for it! (might slow down my Milwaukee market premier thread, but there's no such thing as too much LTE reception)

I never was able to connect to anything but band 25 initially using the .17 baseband. If I connected to a B25 site, then the site handed off to a B41 site, it worked as it should. Initially, even with all bands enabled and B25 as the lowest priority, it would only scan for a B25 signal and if it found none then no LTE for you. I'm using the 15 radio now and connect to all bands with no issues.

Sent from my Nexus 5 using Tapatalk

If there is not some kind of solid confirmation over there by this afternoon, then I'd say it's just someone toying with us. It'll come, just a matter of how soon. I've given up worrying about it every waking minute. For now, I've got enough of a workaround that I'm in no rush to undo everything for the OTA. I'll probably just wait to be able to TWRP it. 

Supposedly someone over on xda knows someone who just got the 4.4.3 update. Seems kind of suspect, but maybe the 24th will turn out to be D-Day after all. There are screen shots in their thread if you're interested

Sent from my Nexus 5 using Tapatalk

Arvada should be getting some cluster love on the next update or two. I'm getting 1x800 from the tower that serves my house and last night it was 1900 only.

Sent from my Nexus 5 using Tapatalk

You can enable manual exposure in advanced settings.

Sent from my Nexus 5 using Tapatalk

Well, this has certainly been anticlimactic so far, eh?

Apparently the 1% that initially got the update didn't include the 0.5% of the Sprint N5 users that are on here. . . Not that surprising actually when you look at those numbers.

Sent from my Nexus 5 using Tapatalk

No mention of anything specific to Sprint or Spark for that matter.

http://au.ibtimes.com/articles/547294/20140409/android-4-3-kitkat-os-update-roll.htm

Sent from my Nexus 5 using Tapatalk

Not really a place to post a complaint about Sprint. S4GRU is for productive conversations about Sprint services (WiMax, 3G, LTE, etc) devices and markets.

So is this the quiet before the storm or what?

 

 

Sent from my iPhone using Tapatalk

Probably. With the recent clusters accepted and subsequent LTE activation, it looks like things are going to pick up quickly around the Denver metro area.

Sent from my Nexus 5 using Tapatalk

Standing in a Sprint store downtown right now and a rep stated unequivocally to another customer that LTE should be fully deployed in Denver by the end of April. It's the corporate store too, not the Verity Wireless store.Take it for what it's worth.Sent from my Nexus 5 using Tapatalk

I think we all know how much that is worth. However, Sprint has publicly said the end of June , so that should be a good date. Not to say there won't be a lot of progress between now and the end of April, just doubtful it will be complete by then.

Sent from my Nexus 5 using Tapatalk

Would there be any interest or benefit in logging the "serving cell" info from the LTE engineering screens for various sites we know we are connected to? 

uploadfromtaptalk1395281003590.jpg

 

Can that be band 26 ? I did a little mapping this afternoon

 

Sent from my LG-LS980 using Tapatalk

Sensorly is going to be very annoying for lots of people toting B25 only LTE handsets once B26 and B41 are widespread and online since there is no way to differentiate what bands laid down what purple on their maps. I believe they have stated that there is no known way to get that data either so it's not going to be "fixed". 

I just added some band 41 purple to the maps on east 56th, I-76, I-70 west of downtown and Kipling/Ralston area. I think band 41 has better coverage in Denver than 25, at least for now.

Sent from my Nexus 5 using Tapatalk

Have you unlocked your radios using your MSL?

When my N5 arrived, first I rooted it, got my MSL then enabled the other two bands so I could actually play with it. I was LTE hunting within 10 mins tops. I did have success this evening on the way to the airport with multiple successful handoffs between multiple B41 sites, so I feel better that it's not my phone. In fact I was able to connect to the original site tonight that I was unable to yesterday. And yes, B41 is going to rock!

Sent from my Nexus 5 using Tapatalk

I was able to connect to B41 downtown by forcing LTE mode. It was great, but have not been able to get the connection a second time.

I sat about 1/2 mile from a known B41 site and tried different radios and different tricks and I could never get a connection, even though the LTE engineering screen showed a B41 signal at about -75dBm. This is in a B25 null area as well.

Sent from my Nexus 5 using Tapatalk

On a side note, has anyone with a Nexus 5 successfully connected to a B41 site in the Denver area?

It sounds like they are fairly confident that the cluster issues will be fixed by June with the announcement that Denver will be online by then. It would be a pretty bad PR FUBAR if they failed to deliver on that. Hopefully they built in some buffer on that date and really hope to be online perhaps a month sooner. We can only hope!

Even on the .15 radion and in LTE only mode, I have only been able to connect to B41 once in KC. It didn't last more than a few seconds either. I just don't think the N5 reliably connects to B41 yet. Some markets are better than others for some reason. 

 

I just played around with the 15 and 17 baseband radios and noticed some interesting things about them. Neither one connected to a known B41 site that was showing about a -70 signal in the engineering screen, be it with LTE only or the LTE/CDMA mode. The .15 radio did scan every band after each cycle of airplane mode, while the .17 did not. After the initial scan, it would only scan B25 unless you did the PRL trick which is not practical. Also, I noticed that often, while in LTE only mode, with the 15 radio I think it was, if it found no LTE for Sprint, it would park on Band 4 and alternate between two cells and wouldn't scan again until I cycled airplane mode. I find that behavior odd. 

All in all, it's kind of a disappointment. I thought LTE only mode would allow connections to any LTE tower that was broadcasting, but it seems to be more complicated than that. Can we just get this eCSFB issue fixed and the spark update for the N5 rolled out so we can use the device to its potential. Is this a similar situation with other Spark enabled handsets, or is this unique to the N5 because of it's wide band support?

It is not.  .17 basebands and beyond are subject to eCSFB and therefore will not connect without it.

However, in LTE only mode, it's a moot point, correct? Denver is way behind with eCSFB so I'm only doing this for LTE hunting and mapping purposes, knowing that I am without voice while in LTE only mode.

Do you mean Band 41? You're not going to be finding any Band 26 in Denver (yet).

Fark. I hate these band numbering schemes, They have no rhyme or reason. Yes, B41 is what I'm looking for. Wouldn't it just be easier to use layman's terms and speak in MHz vs band numbers? I'm glad you're picking up what I'm throwing up.

Interesting. Seeing how Denver seems to be far behind on the eCSFB issue, it would seem that the .15 baseband would be the preferred one for the area. Any idea if the .17 radio is the same in that respect as the .15?

In theory, if I have enabled all bands of LTE and am in LTE only mode, then I should be able to connect to any LTE site that is online, correct? I'm trying to sample the TD-LTE sites in Denver that are shown as complete in the premiere sponsors map in the Denver area. Earlier when I tried, I got only B25 while driving near completed B26 sites. I have since flashed the .15 radio as it seems that more people have success with this radio. Is there anything else I need to do, or should I be good to go at this point?

Anybody else disappointed with today's NV site acceptance report? We haven't been getting many sites accepted lately also I had a question whenever I do a speedtest I end up with a higher upload then my download speed and I end up getting a ping between 120-150?

I know we live in a time of instant gratification, but this is a massive project, both financially and logistically. Permits, equipment, crews, weather, etc, etc. Patience.