digiblur

500 pounds each? Yikes! We're they trying to put only one antenna per sector?

Did someone say PRL? 

Band 2 GCI suffix is 08, 09, 0A if you want to add that to your list for 310410

Let me summarize my trip to LA. My phone had no issues switching between Band 25 and Band 41. It was seamless. In fact, my Nexus 5 was picking up LTE better than my iPhone 5S. From all the issues you guys have been having, I just can't believe I had such a great connection.

 

And the area of LA I'm in has very little LTE with the closest 2 sites still not LTE accepted.

Sent from Josh's iPhone 5S using Tapatalk 2

Although different bands but I think this radio is awesome as well. Watched it slip between band 17, band 4 and band 2 with ease. Even some of those transitions were different channels. I would have never noticed unless I wasn't looking. Never dropped LTE through some very rural roads for 3 hours. Excellent work on this side of the modem.

Well, Sprint "fails" at nearly everything it does. Is Sprint practically cursed? Or maybe Sprint just lacks the scale to force its initiatives to work.

Not everything, they are good at a few things.. (stares at spectrum analyzer, only sees multiple LTE channels on 700mhz and AWS from the other 3 carriers in Sprint launched LTE market)

Let me get back to you on those things

And that would be a risky investment with no guaranteed return. Sure, Sprint could theoretically throw the $30 billion at CAPEX instead to expand the network greatly. But what if that would attract away from VZW, AT&T, and T-Mobile only an additional three million subs? Great, Sprint just spent $10,000 per sub to acquire them. That would be a poor return on the investment and might be enough finally to sink Sprint for good. Thus, you can see why Sprint wants the scale automatically gained from T-Mobile's 40 million subs.

 

AJ

Someone needs to mash that wash rinse repeat cycle of the Fail to Plan is a Plan to Fail.

The plan to continue to give away tablets with free data plans to fluff up the numbers is working very well. Samsung loves it!

The hub he was referring to in that video also showed up on the Network Vision map a while back:

 

 

I confirmed it with permits dating all the way back to 2007 for all 4 major carriers when it was constructed, and with Street View imagery of the hut/cabinets themselves.

That odd kinda sorta DAS cascade threw us off for while especially with it not listed as a DAS. Glad to see all the pieces come together on that mystery.

Imagine if they put that $$$$ towards network expansion and bit of marketing that is dumbed down for the masses.  Simple commercials without all the talking elephants, giraffes, thugs, hippies, etc, just some average folks.  People love maps so show them a map points all over with new coverage.  Zoom into the point quickly showing some people posting/viewing videos, pics, listening to music on their phones with the quickness.  Then you can adopt the Done. thing again.  "More Coverage.  More Speed. That's Sprint speak.  Done."

Thanks for the screenshots and report, Vince.. in your screenshots, the app still thought it was on 311490 (indicating B41) but the UL/DL channels displaying are for B26 (26763/8763) and B25 (26665/8665). So the app was applying the B41 frequency calculations to B26 and B25 connections, giving you the goofy information. It is one of the issues I'm working on addressing now for the next update. I'm going to end up having two separate branches of code; one for HTC devices that can grab the frequency data, and therefore provide more reliable information; and one for everyone else, where the app has to essentially guess what it is connected to. For some reason, the PLMN is not updating as fast as it should, resulting in people on many different devices getting "stuck" PLMNs.

 

 

 

All of this is in the plans.. just trying to focus on getting B26/B41 identification more stable first. I don't want to highlight band information knowing that it's not reliable yet. As you can see by Vince's example above, it is still rough around the edges. It's challenging because there is no method that directly gives me the band.. it's all based on calculations from PLMN/GCI patterns that S4GRU users and others have identified.

 

-Mike

Another GCI range to add to your chart, some folks in the NOLA area found a DAS with GCI's ending in 04, 05, 06.  It's an odd one since it covers many streets.  After some digging and researching things, this video was also found by JWMaloney.

If you feel like doing a 310-410 conversion as well for 0F, 10, 11 being B17 and 16, 17, 18 being B4.  Their B17 DAS's seem to be 13, 14, 15 for B17. Not sure if that mess up anything as I have no idea what they use on PCS or Cellular LTE bands for GCIs.

Done and done, I think/hope. GSM logging seems to work sitting in the house on my Nexus 4. Can't test the 310150 MNC since I don't have any AT&T SIMs to try (I do have an old H2O SIM lying around, but I'd have to cut it down & don't have a tool), but the logic looks right. I also enabled logging of non-ESMR CDMA sites in case anyone wants to map those for VZW or CSpire or something.

Wow you work fast!  Excellent work.  Nailed it on both items perfectly!

What MCC-MNC is AT&T using in your area? I thought I caught them all but I might have missed one. That's an easy fix. When/if I switch to the Mapbox map framework I can probably make that setting more persistent too.

 

And sure, I can add GSM and WCDMA logging. Shouldn't be much extra work to speak of - just a few LoC.

Sounds good. The sites use 310410 as reported by your app and mikejeeps but my SIM is 310150.

Can't wait for the HSPA mapping! Been bored on mapping lately and want to figure out their pattern on the HSPA side. But of course, no hurry.

FYI, I pushed another update to the apk a couple of days ago that changes a couple of things; most notably it now hides information that's absent, reducing screen clutter on triband devices or when you don't have LTE.

 

I expect in the next update to do a better job of sorting the LTE neighbor cells list and I may also swap out Leaflet.js for the new Mapbox slippy map API for Android (mostly because it's silly to be running a browser window + JavaScript when it could all be just native Java with ART goodness) if I can get it to work sensibly without too much pain. There probably won't be many more features after that; mikejeep's excellent SignalCheck Pro scratches most of my other itches, and I have other projects I probably should work on (both professionally and hobby-wise).

 

Anyway, have fun with it!

Happened to snag it on a reload the other day. Glad to see the updates. One thing I have noticed is my SIM makes it go to Sprint LTE on the map instead of AT&T by default.

No biggie as I use it for logging more and throw it into Google fusion tables. Hands down the best app for manually finding a site! Mapped over 80 sites out and tracked them down. Couldn't have done it any other way.

One question.. Is there a way we can log the HSPA sites? Like tower ID, signal, LAT long, etc? That would be awesome.

Thanks to this info, I just updated to 55019. Any ideas on what's changed?

 

Sent from my HTCONE using Tapatalk

We wait for someone to pull it...

Is SignalCheck granted root access on your device? As others have stated, looks like the FTM update references a change in 4.4.3 that requires root to trigger the shortcut now. I hope to find time to update by the end of this week so I will mess around with it and see what I can do. Most others say its still working in the app but I'm guessing it's a root permissions issue.

 

-Mike

Well at first it wasn't as I rarely use the Reset Mobile button.  I had to grant it root and it still didn't let me access the engineering screen.  I exited the app completely and started it again to be sure.  Just says not available on this device or something like that.

I'm afraid to upgrade since I'm on AT&T. I like being able to access Engineering screens on AT&T. Only device I know that does.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

No issues with the upgrade here. Works well. Just use this for the shortcut for now.

https://play.google.com/store/apps/details?id=com.cellmapper.nexus5fieldtestmode

I always found that the older radio, the one that shipped with the initial N5 (think that was 17?) held on to LTE way too long before dropping to 1x/EV.  I would end up in places with hanging on to LTE that wasn't usable and texting would end up not working plus inbound calls would fail.  And this wasn't a CSFB issue.

I flashed the .13 radio but won't have a chance to do the full upgrade for a few days. B25 is about 3-5 dB worse than the .15 radio and it drops back to 3G much quicker. It's debatable, but obviously Google/LG/Sprint has determined that this is the best overall configuration. Wonder if hanging on to fringe LTE might be the cause of some of us completely missing calls on occasion.

 

Do the system shortcuts still work in SignalCheck? Sounds like they should be broken now..

 

-Mike

The debug/engineering one doesn't work, I haven't pulled the logcat yet to see what it is doing.  The Nexus field app was updated today and that one opens the LTE engineering screen just fine though.  My Quickshortcut stopped working so I figure I just need to do a root script on my home screen to fix it. 

Liking this radio a bit better.  The transition to and from B4 from 17 wasn't bad before but I see they've tweaked it a bit better. 

Yes.. the site notes and logging is all kept in an sqlite database (/data/data/com.blueline.signalcheck/databases/signalcheck_log.db) that can be manually edited however you wish. Run the Site Logger for a little while to populate the database with some data, then take a look at it with the sqlite editor of your choice to see the format. You can just add the PLMN, GCI, and Site Note if you want; or go all out and fill in PCI, TAC, etc. If you manually put in PLMN+GCI+note, the first time you connect to the site with the Logger enabled it will populate the remaining fields.

 

Finally got the B26 pattern figured out for both markets for my folks and made a file with all the sectors. Right around 3000 rows. I did add an index based on the plmn and GCI for quicker lookups though. All seems well and it identifies them fine even with a big file.

Minutes to do and the signal looks a hair better on band 17 like I used to get a -103 in the house and now I see a -98 or so. Curious to see how it handles the shifts between band 4 and 17.

They locked out permissions on the debug app so my shortcut no longer works and dialer code doesn't work with my SIM type. Might have to do a shell script with root access to call it. No biggie. Weird part is they didn't update the apk for it so something else is blocking it.

My phone will not ring when connected to LTE. It will only ring when it's on 3g. If I place it on LTE or global I get nothing but 3g only works fine. My wife's phone works fine most of the time but mine won't work at all. Anybody have any idea what is causeing this?

 

Sent from my HTC EVO 4G LTE using Tapatalk

If you are using that old 15 radio then you will need to upgrade it.

I also saw this same thing on dead LTE sites or when LTE was very marginal.

In theory, if it's affecting everyone with tri-band devices, Sprint's automatic network monitoring should catch the falloff in LTE traffic and kick Ericsson to investigate and fix eCSFB on those band 26 sites. Or you could always tweet @sprintcare.

Unfortunately no.  A member watched a Ericsson truck roll to the site, LTE was working on B25, Ericsson enabled B26 with no CSFB.  His phone dropped to EVDO.  Ericsson did a quick drive test and hit the road.  Leaving it broken for a while for B26 CSFB users.  The reason being is they test with EVO LTE's and aircards and call it a day. 

And I'll take the last sentence of your message as a joke   or maybe the whole thing next time.

I've gotten over $500 worth of stuff in the last year from beta testing. The stuff I can talk about -- because the test is over and I'm not under the NDA's anymore -- is a Roku box (streaming netflix, hulu, etc), a AV500 powerline adapter w/gigabit, a wifi powerline adapter that doubles as a wifi extender, a wifi range extender that works better than my Ubiquiti Nano Loco M2, and most recently, an AC1750 DSL Modem/Wireless router combo. For doing the tests, the devices were mine to keep and use as I want (or sell). I just keep them all..that last test, the AC1750 router/modem is a $130 value by itself (or more). Since its also the latest in wifi with the AC standard, I'm using it until it blows up.

Caught this today. It's b26 because it rolled right to 1b sector after. But strange. I'm in new Orleans.

 

Sent from my Nexus 5 using Tapatalk

I think that's Ericsson spending too much time on Bourbon street again.  The PCI shows it as being the gamma sector, but who knows if they can add 169 anymore.

4.4.3 is coming soon. Unless something drastic changed from last week, it's still on it's way. Anything that says otherwise is click bait.

Let's see how good the weather man's forecast is this time...

I will say, that at first, QPST did not list any ports let alone the port my Nexus was connected on. If that is the case, dont worry. Simply click Add port to add it manually and then once you do that it will show up and you can continue on with the steps just the same.

If you have the Franco kernel loaded you don't have to do that boot from kernel step.