Jump to content

ingenium

S4GRU Premier Sponsor
  • Posts

    1,717
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by ingenium

  1. I mean we get roaming now for the most part. Ideally it would be able to use Tmobile sites in the same was as Clearwire was, but I suspect that roaming onto TMobile will still result in a hard drop of the data session. Sent from my Pixel 4 XL using Tapatalk
  2. California is known for stuff like this. Several years ago, I got a letter from the state saying that my small business owed an extra $800 to the state, because the state was late paying on a Federal loan, and the fed charged the state a late fee. So the state passed the fee onto all businesses operating in the state.... Sent from my Pixel 4 XL using Tapatalk
  3. That's likely because your phone got VoLTE in the OTA. 312-530 is the VoLTE PLMM. My phones have still logged it as 310120 though. For what it's worth, I talked to one of the cellmapper developers a few weeks ago and confirmed which Sprint PLMNs are the same network (those two being some of them). So it should merge them on the site eventually. Edit: Your phone is probably still logging it as 310-120, but may default to showing the 312-530 map. But if it's not showing 310-120 on the Cells screen anywhere, then it's logging as 312-530. Mine shows a blank entry for 312-530, but the actual LTE info is 310-120 (ignore the AT&T entries, my phone is dual SIM so connects to both)
  4. I think it always says that if it succeeded. I think it just fetches the current one and replaces what's there with it, even if it's the same version. So the only way to tell if it was really updated is to note the version number and see if it changed. Profile update is mostly just for CDMA, it shouldn't really do anything for LTE. All it does is fetch your username (used for MMS? I forget exactly what it's used for) and some other CDMA parameters/configuration data, so it'll never change unless something changes on your account or something gets messed up on your phone. Sprint can and will push an update remotely if something on your account necessitates it, so the only time you'd need to manually update it is if you're having issues. Sent from my Pixel 4 XL using Tapatalk
  5. 5G NR at the moment is always a SCC / secondary carrier. An LTE carrier is the primary. It's referred to as non standalone (NSA). NR at the moment is still using the LTE core. Standalone NR is coming eventually, but none of the eNB manufacturers have it implemented yet. I'm not sure if SA requires an NR core, or if it can use the LTE core. Eventually they will migrate the network to an NR core, and LTE can run on top of that. Then you can have standalone LTE, or NR as the primary carrier and LTE as secondary, or vice versa. Currently, T-Mobile requires B2 or B4 as the anchor primary carrier for LTE. You cannot have B12 or B71 as the primary LTE carrier with NR. The 5G indicator on T-Mobile unfortunately lies, it just means that some tower in the area is broadcasting NR, and that the LTE site you're connected to supports NR as a secondary carrier. Sprint does not have their 5G indicator configured that way, to my knowledge. Sent from my Pixel 4 XL using Tapatalk
  6. Some cities are better mapped than others, it depends how many people are in that area actively mapping. Take a look at Sprint in Pittsburgh on there. Pretty much all the sites in the city are mapped. Likewise with T-Mobile. Att and Verizon aren't mapped nearly as extensively, and are likely missing a lot of sites. Sent from my Pixel 4 XL using Tapatalk
  7. Are you sure that it belongs to that tower? If you're referring to Sprint, they only have 3 bands on air, and they will all automatically be associated with the same tower (unless it's a mini macro on macro setup, then each B41 sector will be different). To my knowledge, all the providers except AT&T use the same GCI for a given tower (excluding the mini macro situation above), and will all show as one dot. AT&T will sometimes have 2 GCIs, and thus two dots per tower. So it's possible that the second dot actually belongs to another nearby tower instead. Especially since you said you just see 1 sector of it. Just be 100% certain that the tower location is correct (perhaps double check that it's actually a tower for the provider you're mapping), because often times people will mark them incorrectly, and that's confusing and frustrating for other users. It's better to leave it as an estimate if you're not absolutely certain. Sent from my Pixel 4 XL using Tapatalk
  8. You cannot manually add PCIs or bands. It will only log what your phone connects to. So you'll have to just wait for it to collect other PCIs or drive around a bit and let it collect everything. To move tower locations, you have to load the website on a computer and login to your account. Then it'll let you move them. Just be 100% sure that you're putting the right tower in the right place. I've found that with enough data, it works pretty well for estimating the tower location. You might also want to change the collection interval from the default of 3 seconds to 1 second. It'll give you a lot more data points. Sent from my Pixel 4 XL using Tapatalk
  9. Pixel phones support all the bands for both providers, so they're an option. Samsung phones also are one SKU now, differing only in firmware, so they are physically capable of all the bands. I think pretty much any phone on the market now that works with Sprint will be capable of using TMobile bands, at least with a software update (if they artificially lock out bands). Or rather, they'll support B2, B4/66, and B12. The only one that you'll want to pay attention to is B71, since some may not have support for that. I know Google and Samsung phones do though. Sent from my Pixel 4 XL using Tapatalk
  10. It's definitely worth using in my opinion. Call quality is quite a bit better than 1x. I've had issues with robo garble and congested 1x for at least 6-7 years now. It was so bad I quit using my Sprint number and uses Google Voice VoIP instead, since every other word was cutting out. VoLTE lets me actually use my Sprint number again. Sent from my Pixel 4 XL using Tapatalk
  11. ingenium

    Pixel 4/4XL

    CA combos for the Pixel 4 in a format that's easier to browse. Missing Verizon combos because I don't have a Verizon SIM with active service (inactive SIM connects to CDMA only). https://cacombos.com/device?model=GA00677-US Some combos might be missing because so many were listed that it was getting truncated in the message. Sprint took a few attempts to get all of the non roaming combos, and some roaming combos may not be listed. So att and T-Mobile may also be missing some (they maxed out the message size too), but at first glance nothing stands out as missing. Sent from my Pixel 4 XL using Tapatalk
  12. Your best bet is to leave it on relay then. You can also get a battery backup (UPS) and plug your modem and router into that in case of power outages. The ISP usually has battery backup on their end (911), so as long as you can power your side you'll keep internet. I've been doing it for years and it works well. You can get away with a pretty small unit ($60-$100 range) and it should be able to power it for at least an hour, but probably several hours. Sent from my Pixel 4 XL using Tapatalk
  13. You can get a FreedomPop SIM (assuming they're still accepting new lines of service). With "friends", you can get a few hundred MB/month for free. I have a few of their SIMs, one I use as a backup SIM / logging SIM in my phone, and another I have in my car for Google maps and remote control features. As long as you can change the APN in your system, it'll work. Sent from my Pixel 4 XL using Tapatalk
  14. No unfortunately. They said technically they (a higher up tech with access to the right tools) can move it to B25, but it doesn't stick past a reboot. So the next time the device reboots (power failure, software update, etc), it will be back on B41. They did not want to set a precedent of doing this, and having people repeatedly call in to have it locked back to B25. Sent from my Pixel 4 XL using Tapatalk
  15. Do you have VoLTE turned on? VoLTE being on and connected to a supported eNB causes the phone to drop the CDMA connection, so it will only display LTE. Sent from my Pixel 4 XL using Tapatalk
  16. That's Google location services probably. LTE doesn't broadcast location information. When your phone gets a GPS lock, it reports nearby cell and wifi information to Google. Then when it can't get GPS, Google can estimate the location based on wifi or cell data. The more data they collect the more accurate it gets. When things change, there is a lag of a few days before it updates. I've had the same thing happen when moving wifi access points, or even if I've been VPNed into my home network for a while from another location. For a few days afterwards Google has associated my home IP with that other location and reports that (or reports a location in Kansas, basically the default "I don't know" location for the US) instead of the real location. Sent from my Pixel 4 XL using Tapatalk
  17. Something isn't right then. I've had no issues with VoLTE at all. One time while driving I noticed it beginning the cut out, and the network moved me to B26 (in a good coverage area) to presumably minimize tower handoffs and for there to be a lower likelihood of the call having issues. It kept me there for the duration of my call / drive, then I went back to B41 once I ended the call. Presumably that's how it's supposed to work, if the call starts having issues, then you get moved to a lower, more reliable band. Sent from my Pixel 4 XL using Tapatalk
  18. The tower I use is B2 and 12 only (along with most in the area). Only one nearby tower has B4 (and it's only 5x5 anyway). In my experience, 2+12 CA gives me the same speed as 2 only. It's as though band 2 is slowed down when on CA. Either way, it's usually 10-15 Mbps during peak usage (used to be 20), and 20-30 during non peak. Upload is almost always 15 Mbps. B2 is always the primary carrier for me. So disabling B12 may have no impact. Logically it makes no sense, but that's what I've seen on at&t. Sent from my Pixel 4 XL using Tapatalk
  19. Good, mine just autorenewed a few days ago. But I guess that's another sign to move to the postpaid plan. Plus save $15/month. Sent from my Pixel 4 XL using Tapatalk
  20. ingenium

    Pixel 4/4XL

    My Pixel 4 XL gets noticeable better performance than my 3 XL. I somewhat regularly drive a route that would cause me to drop Sprint service (or go to 1x only) and roam on all my Pixels until the 4. The 4 holds LTE constantly, doesn't even drop to 1x or 3G. Now I haven't tested how VoLTE performs on this route, but I honestly haven't seen my 4 drop LTE yet. Sent from my Pixel 4 XL using Tapatalk
  21. Meaning it's no longer offered? What about people who already have it? Sent from my Pixel 4 XL using Tapatalk
  22. VoLTE is literally just a config file. If a phone supports it in general (and really, anything based on a version of Android from the last few years does unless they stripped it out), then it can be added for any carrier. If you had root or Qualcomm tools you can take the config file from a supported phone and add it to a non supported phone and it'll work. I've seen this done a lot in Europe (and can be done on the Pixel 2 and maybe 3, at least pre Android 10). There may be FCC recertifications required, but from a technical standpoint there's nothing really stopping them. The config can even be rolled out via a device independent app in the Play Store, but I've never heard of a provider doing it. That being said, Android supports it, so it's possible. Sent from my Pixel 4 XL using Tapatalk
  23. All MBs have the same version in my experience. Sent from my Pixel 4 XL using Tapatalk
  24. ingenium

    Pixel 4/4XL

    It's easy to root Pixels. Especially if you do it as soon as you get the phone, before setting things up (I skip everything, even adding a Google account) since unlocking the bootloader does a factory reset. NSG is tricky on the Pixel 4 though, since Google removed the Qualcomm diagnostics interface in the production build. You have to also flash the userdebug vendor.img from Google, which breaks some things in the February build (no dual SIM, you'll get no service and a "No SIM" error, and breaks active edge / squeeze for assistant). They all worked in the January build, so I'm hoping it gets fixed in March. But worth it in my opinion for NSG. It's just such a useful app. You can find out so much information in LTE Signaling too if you know where to look (CA combos, the VoLTE enabled flag on an eNB, etc). Sent from my Pixel 4 XL using Tapatalk
  25. ingenium

    Pixel 4/4XL

    I haven't really seen a speedtest get above 10 Mbps upload on B41. But on NSG it does show 2xCS UL if the signal is strong (otherwise it does 1 carrier with HPUE). NSG shows upload though in the 15-20 Mbps range, which is about the most I'd expect. Samsung market. I've seen FDD-TDD in Ohio, Pennsylvania, and NYC market. It's only used when B41 is too weak to use as a PCC, and it would switch to B25 anyway. The result is that B41 throughput isn't very good usually since it's so weak. I managed to get a speedtest with NSG running, and you can see B25 has 2 MIMO streams (rank 2, at 13 Mbps on one stream and 4 Mbps on the other). B41 is too weak to do 2 streams, so it's 1 stream (rank 1, at 3 Mbps on one carrier, 5 Mbps on another, and the third having no throughput) Sent from my Pixel 4 XL using Tapatalk
×
×
  • Create New...