Jump to content

ingenium

S4GRU Premier Sponsor
 View Profile  See their activity

  • Posts

    1,717

  • Joined

  • Last visited

  • Days Won

    17

 Content Type 

Everything posted by ingenium

  1. ingenium
    Very likely. I'm guessing that any phone that uses the new wifi calling infrastructure will be able to use it. The config is already there, it just needs forced on. Edit: what's interesting is that it allows VoLTE to be used on Airaves and Magic Boxes, which disables it on "supported" devices. I'm guessing that it also works outside of VoLTE enabled markets too. Albeit it probably doesn't have QOS in those cases, so quality may be an issue. Sent from my Pixel 3 XL using Tapatalk
  2. ingenium
    There's really no reason. One member here just figured out how to hack the Pixel to force VoLTE to be enabled (root required), and it works perfectly. It was literally just forcing the toggle to appear... The VoLTE implemention is standard and the software and config is already there, it just needs forced on. Sprint is just limiting the rollout, either because they feel the network isn't ready, or for other reasons. Sent from my Pixel 3 XL using Tapatalk
  3. ingenium
    Indeed you do [emoji6] Sent from my Pixel 3 XL using Tapatalk
  4. ingenium
    There is an adb command that you can run, without root I think, that sets what radios are affected by airplane mode. I set mine to not disable Bluetooth. Get an adb shell and run: settings put global airplane_mode_radios cell,wifi,wimax You can leave out wifi if you don't want it affected by airplane mode. The default list is cell,bluetooth,wifi,nfc,wimax Sent from my Pixel 3 XL using Tapatalk
  5. ingenium
    Does field test show the earfcn? That could be used as well. Sent from my Pixel 3 XL using Tapatalk
  6. ingenium
    No. There was a beta firmware that one person was able to get pushed to their MB, and it added some things to the non-relay backhaul options, but it still was not working. They're seemingly having trouble getting it to work for some reason. Sprint is apparently having lots of software configuration related issues lately, between this and VoLTE rollout issues. Sent from my Pixel 3 XL using Tapatalk
  7. ingenium
    Supposedly, at least on the Pixels (I assume Samsung uses the standard implementation now), it's continuously learning and refining the known prints. So every time it's scanned and accepted, it takes that new scan into account for future scans. In theory this should mean that it will adjust to changes in your prints. Sent from my Pixel 3 XL using Tapatalk
  8. ingenium
    Supposedly the airave doesn't support VoLTE, and when in range it supposedly disables it, as if you crossed into a non VoLTE market. It's possible that this isn't working properly and it's confusing your phone. Maybe try disabling it? I assume you've tried rebooting your airave? I've run into issues with mine that can last for weeks, where LTE from the airave does something to my phone and it will refuse to connect to LTE (on a magic box or macro, or the airave itself) until I airplane mode toggle. As soon as it connects to the airave LTE the problem repeated. I disabled LTE on the airave for a few weeks (blocked the LTE ipsec tunnel on my router, so it was 3g only), and when I reenabled it it had been fixed. [emoji2369] Sent from my Pixel 3 XL using Tapatalk
  9. ingenium
    I only browse with Tapatalk, but whatever Robert did last week fixed the speed issues that I was having. For people having issues, does Developer Tools show anything? Anything in the console, or any specific request that's hanging? That might be useful to help figure out the cause. Sent from my Pixel 3 XL using Tapatalk
  10. ingenium
    That's really interesting that it's showing the real T-Mobile PLMN instead of the Clear PLMN. Unless SCP replaces it automatically when displaying it. I believe this has always been the behavior on Android. The roaming indicator is the status of the CDMA connection only.
  11. ingenium
    Not sure if you were asking this question or answering it, but the speed increases only apply on a per UE basis, and doesn't directly affect others (more on that below). A (very technically inaccurate) analogy would be that each user has let's say 5 seconds to receive an incoming transfer before having to wait for their turn again. 256 QAM is a more efficient encoding that means more data can be sent in that 5 seconds. It would be like listening to someone speak, but being able to add extra "words"/data by varying the tone of other words, so that you need 33% fewer words to say the same thing. In a noisy environment (ie weak signal), you can't really hear the tone, so you have to revert to saying all the words (16 or 64 QAM). That being said, it can indirectly increase speeds for other users. Since a UE using 256 QAM will download faster, it will be finished faster, freeing up airlink to be used for other UEs.
  12. ingenium
    Are they showing up on your account? If not, they are likely on an engineering or some other account at Sprint. Those units seemingly can go indefinitely without being powered on. I had one off for 6-8 months before I put it back in service and it came up fine. For a unit on your account, I think it's like 2 weeks or so before you start getting calls and texts from Sprint telling you to return it. Sent from my Pixel 3 XL using Tapatalk
  13. ingenium
    Neither have I. I've confirmed that it's being used via NSG, but it doesn't seem to make much difference. I suspect backhaul is the bottleneck. Sent from my Pixel 3 XL using Tapatalk
  14. ingenium
    Last I heard was late January I think? So it should be coming soon, at Sprint Speed[emoji769] The Feb OTA should be dropping today (always the first Monday of the month), so there's a chance it will be in there. Sent from my Pixel 3 XL using Tapatalk
  15. ingenium
    That's the original software that it launched with. It's likely saying limited connectivity because it's unable to use it, and is probably falling back to LTE. Sent from my Pixel 3 XL using Tapatalk
  16. ingenium
    What software release are you on? Sent from my Pixel 3 XL using Tapatalk
  17. ingenium
    Perhaps T-Mobile or US Cellular is restricting the bands available, and not allowing carrier aggregation. It's also possible that T-Mobile or US Cellular is deprioritizing roaming on their congested sites, rather than Sprint throttling it. It certainly wouldn't surprise me if providers gave priority to their own customers over roaming UEs. Sent from my Pixel 3 XL using Tapatalk
  18. ingenium
    It will not use mobile data while connected to WiFi. It just makes handoffs from wifi to mobile data (such as when you move out of wifi coverage) quicker and smoother. Normally there is a slight delay while it brings up the LTE connection. I believe this option has to be enabled for wifi calling voice call continuity (VCC) to work reliability. The downside is that it will use slightly more battery, since it has to keep the LTE connection active. How much of an impact this will have depends on how strong your mobile signal is. In low signal areas it might have a noticeable difference, but then again it might not. For what it's worth, it's been enabled by default on my phones for years (Pixel 1, 2, and 3, and possibly the Nexus 6P and 6). Sent from my Pixel 3 XL using Tapatalk
  19. ingenium
    Are you connected to a magic box or airave now? Neither of those support VoLTE at the moment, and it will be disabled if/when you're connected to one. Sent from my Pixel 3 XL using Tapatalk
  20. ingenium
    I think so. I haven't tried it in the US. I'm not even sure if the option is shown when you aren't roaming. It's also possible that the option is there, but it won't let you authenticate on a domestic carrier's network if a Sprint signal is detected. Sent from my Pixel 3 XL using Tapatalk
  21. ingenium
    Do you have Android? On my Pixel, I go to Settings, Network & Internet, Mobile Network, Advanced, and untoggle Automatically Select Network. It will then do a scan and bring up all the networks it finds. You'll only be able to authenticate on one that Sprint has a roaming agreement with. It will often give an error at first saying that it can't associate, but it actually does. Not sure why. It starts with GSM, then EDGE, then maybe 15-30 seconds later it goes to HSPA, and finally 15-30 seconds later it ends up on LTE. At least that's how it's behaving for me now in Costa Rica (where Sprint has roaming agreements with all 3 carriers). Sent from my Pixel 3 XL using Tapatalk
  22. ingenium
    The LTE availability for international roaming on Sprint's website isn't accurate. It's only accurate in that it lists the roaming partners. In my experience, if the carrier has LTE, then you'll be able to use it assuming your phone supports the bands. You can actually force your phone to roam on whichever provider you want (if it's a roaming partner). Usually I find that one carrier has better coverage, but more subscribers so the speeds are slower. And another carrier(s) has worse coverage, but faster speeds. So I'll switch between them as appropriate. Sent from my Pixel 3 XL using Tapatalk
  23. ingenium
    It would cause massive interference and wouldn't work unless you had a buffer area with no b41. Or if they had an unused set of earfcns, they could potentially use those just at the stadium with a different TDD timing config. Sent from my Pixel 3 XL using Tapatalk
  24. ingenium

    PRL?

    ingenium replied to SprockG's topic in Apple/iPhone/iOS

    You can still edit PRLs with the correct software, but applying them back to a device is another story... I haven't been able to find a way to write a PRL in 5 years. The last phone I was able to do it on was a Galaxy S4. With newer phones, I believe the PRL is stored on the SIM in some way. Anything that uses a CSIM or ISIM. Sent from my Pixel 3 XL using Tapatalk
  25. ingenium
    I'm in Costa Rica right now, and the Pixel 2 XL has dramatically better reception on LTE band 3 and HSPA band 5 than my 3 XL does. Side by side, my 3 will have no service and the 2 has usable service. The 3 drops LTE frequently while moving, but the 2 holds on. Sent from my Pixel 3 XL using Tapatalk
×
×
  • Create New...