Jump to content

boomerbubba

S4GRU Premier Sponsor
  • Posts

    704
  • Joined

  • Last visited

Everything posted by boomerbubba

  1. As for why they are used, that much is pretty obvious. The "tower" is just a location. Your connection is actually to one of the sector radios on each site. I assume you are talking about CDMA sectors, since they broadcast coordinates and LTE sectors do not. It is not a question of "advantage" for Sprint in using them. These sector IDs (Base Station IDs) are baked in the cake of the CDMA standard. Generally, the devices' own telephony is based on sectors. For some other purposes, Sprint does use its own site IDs. Presumably, Sprint's internal databases link from the more granular sector IDs to their own tower IDs comprehensively. So when troubleshooting based on sector, they can always know the tower. As for your location question, be aware that some Sprint towers' sector radios do broadcast the actual tower location's coordinates, identical for each sector, while other towers broadcast a different, offset coordinate for each sector. I do not know why this is, but it is. In my own experience, it does seem that the size of the offset is proportional to the designed coverage size of each sector. This subject is summarized in this FAQ comment, which contains a link to a fuller Sponsor thread:
  2. Netmonitor does not identify the site of LTE connections, only CDMA connections that happen to occur while you have an LTE connection from somewhere. That might not be the same place.
  3. It seems to me that the embedded Iframe map at the top of this thread has been broken for two days. This hold true for two different browsers on two entirely different systems.
  4. I have international roaming disabled on my GS3, and have travelled several times close to the border in El Paso. Never had a problem with unwanted connections to Mexico.
  5. It's hard to judge who was in the most danger -- the guy atop the tower or the guy taking pictures while driving 65 mph on the Interstate.
  6. Thanks! I have usually not been able to view the Sensorly map from my desktop at my usual daytime location because it is blocked by the local proxy server. (And Sensorly on my phone is almost useless there until NV reaches the area with some usable bandwidth.) But I can view the embedded version above.
  7. Sensorly doesn't do anything to "discover" LTE. It depends on the phone itself to make the connection, and just logs whatever connections are present. Running Sensorly or any other app that is sending and receiving data might even interfere with discovering LTE, because the phone may avoid switching to 4G while it has an active 3G data connection in progress. The thing that forces a scan, which then might make a 4G connection if a signal is present, is the workaround of toggling airplane mode.
  8. My own wish is for an app that would log my LTE connections so I can correlate them to towers offline after the survey: The log should include datetime stamp, user lat/lon coordinates, signal RSRP, signal RSRQ, Sector Physical Cell ID integer, and Sector Cell Identity (a 28-bit value) as a hex string. As it stands now, these two forms of LTE sector IDs are available manually on the LTE Engineering screens of different devices. But Samsung devices show only the Physical Cell ID; EVOs show only the Cell Identity values. We need both, so the same LTE tower sites must be surveyed twice -- once by each type of device. An app like this can do it all at once. Boths sets of LTE IDs are available in the Android telephony API for Jellybean, but not earlier Android versions..
  9. There is a reason that the NV Sites Complete map is in the Sponsor-level Interactive S4GRU Maps forum: The content is for Sponsors. Republishing such detail in this public forum violates S4GRU rules. The Sponsor forums provide a venue to discuss such details.
  10. But as far as I know, there are no equivalent Sponsor maps of the Shentel market area, which is not directly served by Sprint and outside the scope of the main Sponsor maps.
  11. Robert has an article on the Wall about Sprint's latest announced list of cities, to which he has inserted the following comment (boldface emphasis in his original).
  12. It was being set in place with a previous sprint tower, and i used open signal maps to find it This begs the question of how you knew the "previous Sprint tower" was actually a Sprint tower. And what does "being set in place" with it mean? Sounds like there are multiple towers at this location, and Sprint may or may not be sited there. Also, Open Signal is notoriously wrong about towers. It does not even purport to map actual tower locations, only imputed geographic coordinates derived -- usually inaccurately -- from crowdsourced signal-strength collection.
  13. The mapping of the CDMA base station is unrelated to the source of your LTE signal, which may be coming from a different site altogether. Further, for unrelated reasons, even the mapped CDMA coordinates may not reflect the actual CDMA site because some base stations broadcast CDMA coordinates that are far offset from there. So your mapping experience is irrelevant. More important, you empirically logged a pretty strong LTE signal and moderately fast speeds. That could just be load related.
  14. I would like to have an exportable log of my own data collection points, with lat/lon coordinates, timestamp, data type, signal strength and type (RSRP, RSSI, etc)
  15. My head actually cocked to the side when I read that as well! Aside from the issues with anchoring panels to something that is alive and potentially growing, I couldn’t figure out how something like downtilt would work on something that has the rigidity of a real tree. Can you imagine what your service would be like in a storm? “I have signal! No, wait neverm… THERE! Oh, gone again.” It’d be like a giant metronome. http://waynesword.pa...du/faketree.htm These fakes are pretty spot-on from a distance! This is not good news for my driving skills since S4GRU.com has taught me to keep an eye out only for conspicuous panels. Now I'm going to start questioning everything. A red herring. It is obvious that danny1st was not looking at the actual tower site, but was being fooled by the offset coordinates being squawked by the CDMA sector base stations. When the coordinates are offset from the actual antenna site, they might be far way from there. Even miles away in some cases. Yes, there are "stealth" towers disguised as trees, etc. But that was not the case here. This was a case of the user not understanding that the mapped coordinates displayed in the app might not be real. BTW, since you have Sponsor privileges, you might also be interested in this thread: CDMA towers that squawk the wrong coordinates
  16. Either CDMA Field Test or Netmonitor will export KML files for the squawked CDMA coordinates, warts and all. I prefer CDMA Field Test. (I used to use Netmonitor, but I uninstalled it because I decided I didn't like its privacy risk. Others may weigh that risk differently than I do.) Netmonitor did show multiple sites on its interactive screen. Of course, the log files for both include multiple sites. Both apps export KML files plotting the coordinates broadcast by CDMA sector base stations the handset connects to, which may or may not be the actual antenna sites. The output is still useful if you understand these limitations, and have access to the S4GRU master maps of the actual Sprint sites for reference to divine the actual site within a plotted triangle.
  17. CDMA FIeld Test and Netmonitor will export logs as CSV files and/or as KML files for mapping. But the content of the coordinates mapped has all the shortcomings of the interactive displays I described above, because those shortcomings originate with the Sprint base stations themselves. So I am sure your Blackberry app had the same limitations.
  18. You really cannot generalize about all purported "tower mapping" apps because they work differently The apps you are using (Open Signal and Signal Finder) do not show actual tower locations at all, only imputed locations that they have computed using crowdsourced signal strength collections. These computations are extremely and notoriously unreliable. I consider these apps, when used for this purpose, to be junk. At least the other class of apps (CDMA Field Test, Netmonitor, etc.) plots the locations that are broadcast by the CDMA base stations. In some cases, these locations are the actual sites so it is straightforward to see them. But in others, the locations do not represent the sites, but rather the offset locations, as the FAQ comment explains. Yes, it would be nice if Sprint and other carriers would just publish their full set of antenna sites, but they don't. For Sprint, the single best resource is the set of Sponsor maps here at S4GRU, which are sourced from internal Sprint project documents. With these Sponsor maps, CDMA Field Test and a little work, it is possible to isolate the CDMA site you are connected to. I have always been able to do it, but no app will do all the work for me. (BTW, the other major CDMA carrier, Verizon, goes even further to suppress tower locations. Even though Verizon sites apparently broadcast coordinates, the carrier seems to cripple the Android API on its handsets to block apps such as CDMA Field Test from mapping the sites at all.) None of this applies to LTE, which does not even include broadcast coordinates in its technical standard. So even with the S4GRU maps, the only way to correlate their mapped LTE sites to signal data available on the handsets is by field survey to build our own lookup table. No doubt Sprint has such tables internally, and it would be nice if they were published. But they are not.
  19. CDMA Field Test is mapping the coordinates broadcast by the base station site (tower). But those coordinates may not be the tower's actual location. The coordinates broadcast for the sites' sectors may be offset from there. That is why I said above, "You still might have to do some field work to figure out the exact sites." And you would probably need the S4GRU maps of all the Sprint towers, available to Sponsors here, to do that. See this comment in the FAQ thread for further explanation.
  20. Congratulations. You now have taken the initial step toward mapping LTE sites by their actual LTE IDs. But these have nothing to do with the NID, SID and BSID values, which all pertain to the CDMA hierarchy. Eventually these two sets of radios (CDMA and LTE) will tend to coexist on the same Sprint tower sites, but the only way for us to correlate them is by empirical surveys. Presumably Sprint has internal databases that can relate them, but we don't have access to them. Neither do our handsets, AFAIK. We think the LTE Record is just a crude way to build a local set of CDMA IDs that might trigger an optimized scan for some LTE signal. It might be good for that, but nothing else I can think of. It does not correlate specific LTE IDs to specific LTE IDs.
  21. I think the consensus speculation is that the LTE Record is just a list of 1x CDMA sites to which the device happened to be connected while it had an LTE connection. These are not necessarily the same sites as the one that had the LTE signal, and in a thinly developed market probably are not the same. These CDMA sites likely don't even have LTE upgrades yet. As best as anyone can tell, this "LTE Record" might form the basis for some scheme to optimize scanning for LTE sites. No one knows for sure. But we do know that mapping them would be a nonsensical way to show LTE. It would be pure misinformation. Some of us at S4GRU do know how to map the real LTE sector IDs using the LTE Engineering screens of most devices. We have reverse-engineered that much. But this takes a lot of work by users doing field surveys to capture the IDs and triangulate them so they can be correlated to antenna sites. It is not an automated process by any means, and no mapping app will do it all for you. To my knowledge, no one is even trying to map LTE sites by their sector IDs, except for those of us in the sponsor thread for Austin and nearby areas. We have mapped almost every live tower by its LTE sector IDs.
  22. If you are trying to track you LTE connections to specific antenna sites, there is no app that will do that for you directly. You have to survey the towers/sites yourself using your LTE Engineering screen. If you are trying to track CDMA connections, the apps you are using won't help either. Use CDMA Field Test. Or if you don't mind the privacy risk, try Netmonitor. You still might have to do some field work to figure out the exact sites. In any case, start with a comprehensive map of the Sprint towers, which you can get as an S4GRU sponsor. Sprint's own maps are incomplete.
  23. Does the monthly bill for cell/data service go down commensurately? And is there still a two-year contract?
  24. Well, that Sensorly hotspot is certainly evidence of an LTE tower. It may not be conclusive evidence that it is your particular tower, especially if there are any other possible Sprint towers in range, but it is evidence that poses the hypothesis to prove or disprove. (I wish you had mentioned that Sensorly fact before. The Speedtest results by themselves don't show tower location.) And it really does help to see the Sponsor maps because they show where the Sprint sites are. The best way to know for sure is to go close to the tower site and log the RSRP signal strength all around it using the LTE Engineering screen on your phone, seeking strong signals for all sectors. You also can log the values for each sector's Serving Cell ID. Then you can replicate the test from your original position to see if the ID matches.
×
×
  • Create New...