Jump to content

ingenium

S4GRU Premier Sponsor
  • Posts

    1,717
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by ingenium

  1. Ooo that sucks. Is it a regular T-Mobile plan, or their home internet plan? I didn't think they checked the IMEI for normal lines? Sent from my Pixel 4 XL using Tapatalk
  2. Yup no problem. I find that VoLTE works fine on it, but it does still oddly have random very brief cutouts at times. Which is surprising to me with Ethernet backhaul (and gigabit symmetrical fiber). I'm guessing the cutouts may have been just the airlink having an issue (the eNBs are pretty basic). Personally I still have wifi calling preferred, and find that the call quality is better / more consistent. But it's nice to be able to take the call on LTE and have it handoff right away to wifi calling, since sometimes wifi calling will drop randomly for some reason. Pre-volte, when this happened I'd be stuck on 1x for the duration of the call. Sent from my Pixel 4 XL using Tapatalk
  3. Yes. It didn't work initially, but around February or so I factory reset it and it got VoLTE a few days after that. Supposedly T-mobile has been proactive at going back and enabling it on MBs that never got in the queue, but if you don't have it yet, just factory reset it. It can take up to 3 weeks to get it the first time (or so I was told by MB support). My Airave 4 took 2.5 weeks after a factory reset. I'm not sure if it's still the case, but having VoLTE enabled was a manual process, where it would get entered into a queue and someone had to manually toggle it on. That's why it took so long the first time, and why some MBs seemingly never got it. Factory resetting puts you back in this queue. Sent from my Pixel 4 XL using Tapatalk
  4. I just got that same email for my Magic box that has been on Ethernet backhaul for 9+ months (I checked and the serial number matched that unit). It was still on Ethernet when I got the email, since I speed tested faster than Sprint's nearby macros (they're fairly congested even on B41). So they're just blanket sending it out to everyone, even people who are already off of LTE backhaul.
  5. It can be used. T-mobile sells the same device and it works with N71 and N41 using T-mobile anchor bands. Sent from my Pixel 4 XL using Tapatalk
  6. In my experience, even with a paid subscription, it can take 3 weeks for trails to show up. I think they do each area in batches, and anything submitted before that batch is run gets processed. Anything that comes in after has to wait for the next scheduled batch. Tower data (for LTE anyway) shows usually in the same day though. It's just whatever process they use to generate the trails. It's possible that a paid account might bump up the areas you visit in the queue, but I suspect that so many people have paid accounts at this point that it doesn't really make much of a difference. Sent from my Pixel 4 XL using Tapatalk
  7. There might be a u.fl connector inside for a GPS antenna, but I really don't know. There should be pictures on the FCCs website if you feel like digging. How many satellites does it see? Is there a large building outside the window where your magic box is? Anything significantly blocking the view of the horizon and sky? If so, is there a different spot you can move it? Sent from my Pixel 4 XL using Tapatalk
  8. The main scenario where I envision NR CA being useful is edge of cell scenarios, where N71 can be used for PCC and N41 as SCC. You gain the better and more stable uplink from low band, extending the range of N41. There are a lot of places now where B41 uplink is basically failing, but can still be used for download if uplink was on another band. The wider carrier widths of N41 width helps, plus NR is supposed to be better with weak signal uploads than LTE I believe, but it would still be nice to have and see N71+N41. It would also likely take load off of N71. Sent from my Pixel 4 XL using Tapatalk
  9. NR right now is operating in a mode called non standalone (NSA). LTE has to be the anchor band (primary carrier) and NR is aggregated. It uses the LTE core. For voice calls, it actually drops the NR carrier. Honestly I'm not sure what about those phones prevents them from being able to use B2 or B66 as an anchor other than software/certifications. I'm not aware of any technical limitation of the modem that would prevent it Supposedly standalone (SA) NR is coming by the end of the year. This will use NR as the primary carrier, and use the NR core (and enable VoNR). I think it can still aggregate LTE carriers as secondary, but no current modems support aggregating multiple NR carriers. For that we have to wait for the x60. I guess technically once SA NR comes, these older phones would be able to use it. The issue would be whether or not they're actually capable of SA, and if they can do VoNR with software updates. And I guess also whether or not they'd get those software updates if so. Sent from my Pixel 4 XL using Tapatalk
  10. Factory reset it and make sure it has a good GPS signal. After a factory reset it should get it within a couple weeks assuming that it has a good GPS lock. Sent from my Pixel 4 XL using Tapatalk
  11. I'm still getting 50-90 Mbps (depending on how close I am to it). You might want to double check that it didn't fall to 2.4 GHz. Mine is Ethernet backhauled though. VoLTE has been live for many months on all the femtos. They don't need to cap anything for it to work. In my experience using LTE backhaul on a magic box with VoLTE, it didn't do well at congestion control (was cutting out because the donor was congested), so I'm skeptical that they tunnel VoLTE over a prioritized EUTRA session on relay. So if they aren't doing something as "basic" as this when they completely control the network, they almost certainly won't be doing anything on wifi or Ethernet backhaul to try to give VoLTE special treatment. Sent from my Pixel 4 XL using Tapatalk
  12. That's really weird. Have you connected to T-Mobile before? On my Pixels I'm able to disable the Sprint bands and they happily connect to T-Mobile. That almost seems like something is preventing you from using T-mobile in general. And just to confirm, you're using Sprint postpaid right? Not an MVNO? Sent from my Pixel 4 XL using Tapatalk
  13. Do you have a Samsung phone? You can probably use the Samsung Band Selector app to force T-mobile bands. It's the app that S20 users have been using to force their phones back to Sprint, but I think I can be used the other way around too. Sent from my Pixel 4 XL using Tapatalk
  14. If it keeps the same earfcn, it means they haven't refarmed the spectrum. I don't foresee them shutting down relay backhaul entirely. They just want to get as many people on wifi or wired backhaul as possible before moving them to B2/25 I think. There have been issues with MBs lately, I assume from backend changes T-Mobile is making. One of my Ethernet connected magic boxes lost connectivity (it didn't display an x in the signal bars, so I thought it was fine, but no data passed) and I got the email from Sprint saying to turn it back on. I'm usually on wifi so I hadn't noticed it was having an issue, since I had a full signal. Interestingly the email made no mention of getting charged for it if it's not used or returned. I rebooted the MB and it had some initial connectivity issues (DNS lookups failed, but everything else worked) for 10 minutes or so, and then everything began working again. I think other people have had similar issues recently as well. Sent from my Pixel 4 XL using Tapatalk
  15. You can go into field test and it will show the plmn (mcc and mnc) along with the band. Either will be able to tell you which you're connected to. Sent from my Pixel 4 XL using Tapatalk
  16. Has the magic box earfcn changed? I'm surprised that they don't just kill it from B41 and instead force it to use B25. And what market are you in? Sent from my Pixel 4 XL using Tapatalk
  17. Is it on B41 for backhaul? Did you have it last summer? Leaves on trees have a dramatic effect on signal strength. At my parents' house it's the difference between B41 on the MB (albeit shitty and slow) and only B25. B25/2 drops by about 6-8 dbm on some high gain directional antennas that I have setup. On ATT on my phone it's the difference between decent B12 and literally no service. Sent from my Pixel 4 XL using Tapatalk
  18. Do you know if they reused the existing mmimo equipment? Did it move racks? Is there still B41 on Sprint? I wonder if they can have NR go to one core and LTE to another.
  19. Factory reset? One of mine (wired backhaul) was apparently offline long enough to trigger the email yesterday to plug it back in. My phone would connect to it, but no data would pass (but it didn't have the X in the signal bars). A reboot still had it acting weird (DNS lookups failed), then it started working. So they may be making changes to the backend and causing issues. Sent from my Pixel 4 XL using Tapatalk
  20. It doesn't affect your plan or any of your other lines in any way. The existing lines keep their plan, and the new line has its own plan of sorts that can't be changed. Honestly I'm a little confused why they did this. I guess it would be good to get as a line for a son or daughter (or grandparent?) who doesn't have one yet, but I got one just to have for logging/mapping or in case I find a use in the future. I don't think you can port in to it, so it would really just be an extra line? Most people I'm guessing probably won't use it too much and won't consume that much data, especially with the throttling, such that it doesn't really cost them anything to provide. So it's a freebie that doesn't cost Sprint/T-Mobile much, if anything. On the other hand, if it allows port ins (or someone doesn't care about losing their number), then that's a different story. And it would potentially get new customers who may upgrade to a paying plan in the future if they want HD streaming or hotspot. Sent from my Pixel 4 XL using Tapatalk
  21. This utility is supposedly on most phones and can be triggered with adb or a local shell https://osmocom.org/projects/quectel-modems/wiki/Diag_mdlog I was told that NSG can open those logs. So if you can get one of a B25 neighbor, I can look through the signaling and try to confirm that T-mobile is asking the UE to scan B25. Sent from my Pixel 4 XL using Tapatalk
  22. If it's showing a true B25 neighbor and not bad data, then it's because the T-Mobile network is asking the phone to scan that earfcn and report the PCIs, earfcn, and signal strength back. So it would suggest that T-Mobile is planning to start using it at some point. If you look at signaling messages in NSG, you can watch it happen every second or two. It's how the network does handoffs basically. Sent from my Pixel 4 XL using Tapatalk
  23. Basically an Airave. If you have a VoLTE capable device, then the MB gold is better. It should have a much better range. Sent from my Pixel 4 XL using Tapatalk
  24. That's the case with almost all providers other than Sprint. AT&T does the same thing. Though on my Pixel 4, even with modest data usage (basically background usage with the screen on), it keeps at least 2-3x CA (capable of 4 or 5x CA). On a PCIe LTE modem that I have that's capable of 2xCA, it only does CA when there is data flow, and only if using B12 as the PCC (tower only has 2+12). If B2 is the PCC, it will never add B12 as an SCC. In that case I think it's to keep B12 open. CA uses up resource blocks. On other providers, they're often spectrum constrained (Sprint isn't on B41), so it makes sense to not needlessly tie up resource blocks. Sent from my Pixel 4 XL using Tapatalk
  25. I wonder if it's a permission issue somehow? Perhaps even an selinux permission not getting set properly on one of the database files internally. Not much that the app can do about that though. Have you tried wiping data for SCP, uninstalling, reinstalling (wiping I think will prevent a cloud backup from getting restored?), and then importing again? Since you have root, you can go into the SCP data directory and check the Linux permissions, ownership, and selinux contexts/permissions to make sure everything matches. Another possibility is that the copy of sqlite on that device is buggy or something. But I'm not sure if anything can be done about that other than statically linking sqlite in SCP so that it's consistent across devices.
×
×
  • Create New...