Jump to content

ingenium

S4GRU Premier Sponsor
  • Content Count

    1,674
  • Joined

  • Last visited

  • Days Won

    12

ingenium last won the day on March 23

ingenium had the most liked content!

Community Reputation

1,324 Wireless Expert

3 Followers

About ingenium

  • Rank
    Member Level: 4G WiMax

Profile Information

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

Recent Profile Visitors

5,887 profile views
  1. Hmm, let me know when you have a fix, I'm curious what you come up with. So far I've been sticking with my MC7455 solely because of the IMEI rewriting just in case ATT decides to implement that policy on postpaid. Sent from my Pixel 4 XL using Tapatalk
  2. Pittsburgh has great B41 coverage and speeds. I rarely drop B41. B26 is very usable as a result (I really only see it deep in buildings or in basements). The SF bay area is hit or miss, since they had good density but due to permitting issues had trouble getting it on every site. Also they're limited to 2 contiguous carriers due to AT&T squatting, which makes B41 congested in some places. I think almost all the sites have B41 now though. Most cities in my experience are pretty good with B41 now. The issue I see most often is hanging onto weak B41, causing uploads to fail or be painfully slow, instead of dropping to B25. Pittsburgh has a 15x15 B25 carrier that is often wide open and unused due to the solid B41 coverage. It would have been nice to utilize that more, especially with B25-41 CA. Sent from my Pixel 4 XL using Tapatalk
  3. I heard they originally planned to shut down EDGE at the end of this year, and 3G at the end of next year, before moving it up. Having EDGE and GSM I think still ties up resources on the site (maybe port power limitations). I heard that they basically turn it off unless a UE requests it, in which case the carrier is turned on. But I don't know how they can turn it off and still be available, unless it's some low power mode or something. I'm guessing that they don't plan to enable it on the DSS capable equipment, so it'll realistically probably be shut off as they upgrade sites. Sent from my Pixel 4 XL using Tapatalk
  4. All calls Sent from my Pixel 4 XL using Tapatalk
  5. I think it could be VoLTE related. I lost VoLTE on my magic box, so I factory reset it last weekend to try to get it back. It hasn't come back yet, but when I come home the macro will not hand me off to it, possibly because it doesn't support VoLTE (handoffs are 100% controlled by the network unless you completely lose service). It will however handoff to my Airave, which does have VoLTE. Once I'm on the Airave, it will handoff to the magic box. Before I lose VoLTE on my magic box, the network would hand me off to the magic box as soon as I approached my house (on B41). Now it will move me to b26 instead of the magic box, until I get in range of the Airave, when it immediately moves me there. So it's possible/likely that the network is avoiding doing handoffs which would cause the loss of VoLTE. My phone sees it in neighbors while on the macro, so it's being reported as an option for handoffs. The network is just actively deciding to not handoff. It's so frustrating that VoLTE is still a manual toggle for these femtos....
  6. NR SA can aggregate LTE. You may lose the latency benefit, though honestly I wouldn't even notice. Sent from my Pixel 4 XL using Tapatalk
  7. You might need to factory reset. My Magic Box lost VoLTE about a week ago (Airave is fine). Rebooted it, still no VoLTE. So I factory reset it on Friday or Saturday. Still no VoLTE, but hopefully in a few days it'll get re-enabled. There's something going on with the provisioning I think. I kept getting emails saying that my MB was offline (it wasn't). And to move it to wireless or wired backhaul (it was). So I figured a factory reset would fix whatever backend provisioning issues they might be having. Just very weird that it would lose VoLTE when the GPS lock is still solid (12 satellites), power is fine (it's on a UPS), and my internet is fine (also on a UPS, and haven't had any downtime in years). So you might be having a similar issue. It seems like the macro has "forgotten" about your Magic Box and won't handoff to it, resulting in it not getting used. 2GB/month is probably just from keeping the ipsec connection alive and normal background idling. A factory reset should force all the provisioning and such to happen again, and hopefully get things fixed. Sent from my Pixel 4 XL using Tapatalk
  8. If you have an LTE signal from the macro network, then chances are your phone won't really see the magic box for a few days. It has to be integrated into the network before your phone will handoff to it. Sent from my Pixel 4 XL using Tapatalk
  9. What is HD+? In my experience, when I'm on calls with Verizon users it uses EVS for the codec. I may have seen EVS-WB once with a Verizon call too. Calls to att customers used a lower tier codec, AMR-WB. I don't call other Sprint users very often, but I think it's usually EVS if they're on VoLTE or Vowifi. VoLTE/vowifi calls that go through POTS use regular AMR. Sent from my Pixel 4 XL using Tapatalk
  10. 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
  11. 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
  12. 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
  13. 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.
  14. 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
  15. 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
×
×
  • Create New...