Jump to content

ingenium

S4GRU Premier Sponsor
  • Content count

    1,008
  • Joined

  • Last visited

  • Days Won

    3

ingenium last won the day on December 10 2016

ingenium had the most liked content!

Community Reputation

833 Trusted

About ingenium

  • Rank
    Member Level: 4G WiMax

Profile Information

  • Phones/Devices
    Google Pixel XL
  • Gender
    Male
  • Location
    San Francisco, CA & Pittsburgh, PA
  • Here for...
    4G Information

Recent Profile Visitors

2,965 profile views
  1. Galaxy S9 Series user thread

    Which market? Sent from my Pixel 2 XL using Tapatalk
  2. Network Mapping

    I like CellMapper because it shows the most detail. With enough data you can see the coverage of each sector very nicely in the cloverleaf pattern. It also gives clues for where new sites might be located. I'm finding it useful to visualize small cell coverage areas. Sent from my Pixel 2 XL using Tapatalk
  3. Network Vision/LTE - New York City Market

    Yes, all the converted wimax sites should be fiber or Ethernet fed. The relay sites are likely new builds. Sent from my Pixel 2 XL using Tapatalk
  4. SITE UPGRADE WARNING

    Just got blocked for the first time. Using the most recent version of Tapatalk free (with VIP from the pay version). My home IP has been blocked for about 32 hours now. I thought it expired after 24 hours? Sent from my Pixel 2 XL using Tapatalk
  5. Network Vision/LTE - New York City Market

    Yes, relay small cells are limited to broadcasting a single carrier. Only fiber / non-relay small cells broadcast 2 carriers. It's the same in SF, though I haven't seen any relay fed ones there yet. Sent from my Pixel 2 XL using Tapatalk
  6. Galaxy S9 Series user thread

    Depends. Most Samsung markets (ie all except Chicago) still don't have B25 2xCA. My guess is it will be at least a year before 25/26 CA and 41/25 CA is enabled. Sent from my Pixel 2 XL using Tapatalk
  7. Official Airave 3 LTE / S1000 NSC Thread

    My Pixel is back on 1x800 :-( I temporarily disabled BC10 to kick it to the Airave, but 2 days later it was back on 1x800. For almost the first 2 months it worked great and stayed on the Airave. I might have to just keep 1x800 disabled and reboot and enable it just when I'm in low signal areas. Sucks that that even has to be done... Inherent problem to constant SRLTE devices I guess Sent from my Pixel 2 XL using Tapatalk
  8. Pixel 2 XL Preview/User Thread

    You can do it with Tasker. Make a new task that runs system lock (display->system lock). You can then add a shortcut to that task with some launchers (Nova being one of them). I'm not sure if the stock launcher allows Tasker shortcuts. Sent from my Pixel 2 XL using Tapatalk
  9. Official Airave 3 LTE / S1000 NSC Thread

    It seems that, at least in Pittsburgh, the Airave uses its own CDMA channels, different from the macro. Pittsburgh has C+G block B25, and then another contiguous 10x10 before it (for a total of 20x20 contiguous). The macro has 3 CDMA carriers in the first 5 MHz of this, then there's 5 MHz unused, and then 10x10 LTE (confirmed with spectrum analyzer). The Airave broadcasts its evdo carrier in this unused 5 MHz (channel 975), but its 1x1900 is overlapping the B25 carrier and extends into the unused 5 MHz block (channel 1100). It's partially in the LTE guard band. LTE is 1985 MHz - 1995 MHz, and the 1x carrier is centered at 1985 MHz. Odd that they wouldn't shift the 1x carrier to be somewhere else in the unused 5 MHz block. I wonder if this is just an oversight, the result of legacy channel assignments, or a sign that Sprint is going to attempt to put 1x in LTE guard bands in the future like T-Mobile does with GSM? When Sprint eventually adds another 5x5 or extends the 10x10 to 15x15, they'll have to make the Airave share CDMA channels with the macro I assume. Or else try to put it in guard bands. I wonder if the Airave has its own CDMA channels in markets without unused spectrum. Sent from my Pixel 2 XL using Tapatalk
  10. Official Airave 3 LTE / S1000 NSC Thread

    No. It's supposedly being worked on, but nothing is even in testing yet from what I've heard. So it won't be anytime soon... Sprint claims they can't add custom software on Google devices, yet Google has a complete framework for doing this very thing that they deployed a few years ago and have continued to expand with each Android revision. Verizon, T-Mobile, and other carriers seem to have no problem getting their custom software on it for VoLTE and wifi calling. Sprint also has Sprint DM for hands free activation on Pixel devices, so I think that excuse is BS. Sent from my Pixel 2 XL using Tapatalk
  11. Yeah there are 2 sets of 2 contiguous carriers below the 3 contiguous macro carriers. So some could be fiber fed small cells (otherwise they'd be limited to 1 carrier), or they're starting deployment of 4th and 5th carriers on macros. We need someone with SCP and earfcn logging to see what shows up. Sent from my Pixel 2 XL using Tapatalk
  12. Network Vision/LTE - Chicago Market

    It might be complicated by the fact that the wires go through a hole in the brick exterior. Perhaps that has something to do with the holdup. But at the very least they should be able to give it GMO LTE. It's also possible they can't get to the radios easily inside (it looks like the top is an addition. The bricks look to be a different color). Sent from my Pixel 2 XL using Tapatalk
  13. Official Airave 3 LTE / S1000 NSC Thread

    1x hands off from an Airave to the macro network, but not the other way around. VoLTE will handoff in both directions. Calling+ does this now. Sent from my Pixel 2 XL using Tapatalk
  14. You can just set them the same and let devices decide which to use. I do that for my guest network. The reason it's often done is that many devices will pick 2.4 GHz over 5 GHz, or when they get out of 5 GHz range they don't switch back when they come back in range. It's the only way to force 5 GHz to be used. For my personal network I invert the network name, so for example I have "SSID" for 5 GHz And "SSID-2.4" for 2.4 GHz. Better APs like Ubiquiti can try to make clients use 5 GHz (basically disconnect them and hope they reconnect to 5 GHz), but the band selection is completely under the control of the client device. Sent from my Pixel 2 XL using Tapatalk
  15. In my experience, it might make it into your neighbor's yard, but likely not indoors (at least not very well). I guess it also depends on how close they are and how strong the macro is. A stronger macro, even congested B26, is preferred when the MB signal gets weak ( For houses, it's basically one per household for proper coverage, but you can easily cover a couple units in an apartment building. Sprint is giving them out pretty freely right now. Sent from my Pixel 2 XL using Tapatalk
×