Jump to content

dnwk

S4GRU Premier Sponsor
  • Posts

    583
  • Joined

  • Last visited

Posts posted by dnwk

  1. Just now, ingenium said:

    Nope. It's really easy, especially if you don't already have the Pixel 3 on your line. You just go to Settings and search for Carriers (or go to Settings, Network & internet, Mobile network, Advanced, Carrier). Tap Add Carrier, and then select Sprint and login to your account. They'll text you a one time authentication code to login, so don't turn off your old phone first. And that's pretty much it.

    If the Pixel 3 is already on your line, you'll have to swap it off first to an unused phone. There's no way to switch directly from a physical SIM to an eSIM without having an intermediate device.

    Good information. Thanks. I am hoping Android Q will bring eSIM / Physical SIM dual standby.

  2. On 4/16/2019 at 7:28 PM, ingenium said:

    Can you link to the thread? To my knowledge the only way to do it is indirectly via Fi. I don't believe Sprint will directly allow the use of the eSIM.

    Sent from my Pixel 3 XL using Tapatalk
     

    @lilotimz  mentioned that in Reddit. I don't know exactly.

  3. 4 minutes ago, RAvirani said:

    Not coming until late summer at the earliest.

    Most of Washington state lacks a mature 800 deployment due to IBEZ issues that were only resolved a little over a year ago. This is a non-starter for VoLTE.

    The Puget Sound area is >2/3 800 complete. VoLTE should launch here first and then spread throughout the state. 

    This is my home market so if you have more detailed questions, feel free to DM me. 

    I am in South Eastern Washington. We have Band 26 for couple years now. But I guess we are tied to Spokane MSC and you'll have to turn on VoLTE in the entire MSC, right? If there are portion of MSC that don't have Band 26 ready, they can't turn it on. Am I right?

  4. On 4/10/2019 at 2:41 PM, ingenium said:

    And the current software build has fairly serious bugs for older devices (Galaxy S6 or 7 era and Pixel 1) and VoLTE devices, that has been there for 9 months or so now. It basically prevents texts and phone calls from working when the Airave is in range (the phone can not be connected, it just has to be in range). It seems to mess up the IMS APN/EUTRA session. So texts and calls fail on eCSFB dependent devices and devices actively using VoLTE. As to why it affects devices if it's just in range.... I don't know.

    My solution to this was to disable just LTE on it, but leave CDMA active, via a firewall rule. It's an ugly hack, but it works. I assume a fix is never coming. It's a shame that they broke this on the last firmware build for it, since it worked on earlier builds.

    Sent from my Pixel 3 XL using Tapatalk
     

    So, I guess not using it would be better and probably wait for new version. 

  5. I have a hosted email address I could use (actually I use a wildcard hosted email so that I could figure out who leaked my info).

    For MR1100, I have tested and it worked with AT&T, Verizon and T-mobile. I can't get it to register with Sprint, even-though in network scan, Sprint will show up. But maybe somehow on the firmware level, they block it.

    • Like 1
×
×
  • Create New...