ingenium
-
Posts
1,717 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Posts posted by ingenium
-
-
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.Yeah, first time I tried ... Long time ago ... I didn't have it for a few days, then opened a chat with customer service, and they told me it wasn't possible. I may give it another try. Thanks for the reply and the reset tip.
Sent from my Pixel 2 using Tapatalk
Sent from my Pixel 4 XL using Tapatalk
-
1
-
-
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.Does volte work for you when connected to your Ethernet backhauled magic box?
Sent from my Pixel 2 using Tapatalk
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
-
1
-
-
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.I got this email from Sprint:You’re just a few steps away from a better network experience with Sprint and T-Mobile. Improve your coverage now by reconnecting your Sprint Magic Box to your home internet. 
My MB Gold is currently on Wi-Fi working just fine, so wondering if this a general spam sent to all owners, or does this process to re-select Wi-Fi force it update its config in some way. -
It can be used. T-mobile sells the same device and it works with N71 and N41 using T-mobile anchor bands.Thanks. I saw this too. Seems like it "should" continue with 5G even post merger but probably still up in the air. I will follow this closely.
Sent from my Pixel 4 XL using Tapatalk
-
1
-
-
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.Looks like CellMapper is still either extremely backlogged or having issues mapping NR coverage. I went through Nashville twice over a week ago and none of my AT&T NR mapping is showing up from that entire trip. It was from two different sessions, I went down to Linden TN on Friday afternoon and came back on Monday. Uploaded all points when I got there Friday. Looks like my T-Mobile mapping is showing, I don't think there was any NR showing in Nashville previously. I do have the paid subscription for Cellmapper, which is supposed to prioritize uploads over non-subscribers.
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
-
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 any way to connect an external GPS antenna? While my phone can get a good GPS lock, the MB Gold does not seem to be capable of doing so. I don't mind taking this thing apart if it is possible.
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
-
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.The nice thing about T-Mo's 5G network though is that there shouldn't be a burning need to aggregate NR, with the exception of areas where their 2.5 holdings are chopped up into smaller channels due to licensing weirdness (which to my knowledge is a relatively small chunk of territory). Since NR channels can be 40/60 MHz, you just plop one of those channels down in 2.5 and have a significant amount of capacity to play with, while n71 is left for folks who aren't close enough to the cell for n41, similar to how T-Mobile prioritizes B71 right now.
If T-Mobile wants to fill in more speed in areas with contiguity issues, they can add B41 channels (which they're already doing in some areas). B41 is less efficient of course, but virtually every Sprint phone can use it, as well as plenty of T-Mobile phones, so they can push more users to T-Mobile primary without making (more of) a hash of their network.
At some point of course, they'll want more capacity in areas where they don't have enough contiguous spectrum to just make a bigger NR carrier, but the X60 will have dropped by then...sounds like it could actually wind up in the iPhone 12 series.
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
-
1
-
-
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 itWait, so what's the difference between T-Mobile's 2.5GHz 5G and Sprint's 2.5GHz 5G, that causes older 5G phones that could connect to Sprint's implementation to not be able to connect to T-Mobile's? I figured it would just be a PLMN change or something (if that's even a thing with 5G).
Apologies at my lack of understanding of 5G. It's been awhile since I've been active on the forum and I'm going off my previous LTE knowledge. Feel free to link something that may help me understand better [emoji28]
-Anthony
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
-
2
-
-
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.I know on mine anytime I make a call it switches to 1x for the duration of the call and then goes back to LTE when the call is over. I am able to VOLTE when out in town though. Maybe soon.
Sent from my Pixel 4 XL using Tapatalk
-
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.Anyone noticed that MB Gold speeds have been drastically capped even with Wi-Fi Backhaul? I'm not getting more than 7Mbit anymore where I used to see 30Mbit +.
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.VoLTE requires better bandwidth control, so capping speeds night indicate VoLTE is coming.
Sent from my Pixel 4 XL using Tapatalk
-
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.Downloaded the app, tried bands 2, 4, 12, 66 and 71. Showed no service on all bands. Band 71 tried to connect, but ultimately failed. Thanks for the idea though!
Sent from my SM-G975U using Tapatalk
And just to confirm, you're using Sprint postpaid right? Not an MVNO?
Sent from my Pixel 4 XL using Tapatalk
-
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.Yeah, I do facilities maintenance so when stuff doesn't work I go into panic mode. Because everything has to work, right?
I guess I'll just live with the MB quirks for now and wait until T-Mobile parks me on their network before I pack it up and send it back. B66 LTE is very strong in my house (T-Mobile tower is a bit closer than the Sprint one) and has great speeds.
Sent from my SM-G975U using Tapatalk
Sent from my Pixel 4 XL using Tapatalk
-
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.
UPDATE: Rebooted once more this morning before I went to work, still not connected to LTE backhaul when I returned home. Rebooted once more, and it reconnected about 15 minutes in. I guess it was just stuck on stupid for a day or two.
It’s broadcasting the same EARFCN as before 39874, 2518.4MHz. It’s connecting to the same frequency it always does also, 2640.4 MHz. Phoenix market. I didn’t note the broadcast EARFCN when I connected to WiFi momentarily, but I’m afraid to connect to that again for fear of losing LTE because it works now.
It’s become increasingly finicky the past couple of weeks, where occasionally it’s connected to backhaul and broadcasts nothing (LTE icon is greyed out) and my devices won’t connect for an hour or two then boom, it works again. Maybe it’s on the fritz.
Sent from my iPhone using Tapatalk Pro
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
-
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.Got carrier update 41.7.34 on my iPhone 11 don't know what it's about but I also have IOS 14 developer beta....yes, living dangerously! No way with IOS to determine which network I been getting but I assume TMO is available.
Sent from my Pixel 4 XL using Tapatalk
-
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.Well, looks like they finally killed LTE backhaul in my area yesterday. MB connects to Wi-Fi backhaul, but refuses to connect to B41. Rebooted three times, factory reset once. No dice. Looks like I'm packing it up and sending it back, no way in hell im using Wi-Fi backhaul.
Sent from my SM-G975U using Tapatalk
And what market are you in?
Sent from my Pixel 4 XL using Tapatalk
-
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.It finally reconnected but it is SLOWWWWWWWWWWW..... 1.09 / 0.75
Sent from my Pixel 4 XL using Tapatalk
-
I also found 2 cell sites in LI that had N41 from Sprint and have already be switch over to N41 on T-mobile. Probably helps that the sites had both Sprint and T-mobile on them.
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.
-
Factory reset?My Magic Box Gold fell offline overnight and it won't connect back to the network after a couple tries.
Could be a fluke or something else...
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
-
1
-
-
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.I've searched for ten minutes or so on this forum for discussion related to Sprint's current offer for existing customers: a free line?!
What's the catch?
We're a four phone Sprint family with, I guess, a grandfathered plan that sits squarely between the two existing Sprint plans.
If I sign up for an extra line (which has downgraded video and audio streaming bandwidths)...will my existing plan be modified in any way?
We've been with Sprint for nearly twenty years...in all that time only one real complaint.
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
-
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_mdlogNot gifted yet to be able to access those details
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
-
1
-
-
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.I have a Sprint phone and 3 Tello (Sprint) as well. Definitely from two nearby Sprint sites base on known PCIs plus earfcn. Locking onto b25 on my T-Mobile network phone gets nothing.
Edit: My T-Mobile normal is b71 from 1 of 3 nearby sites. A fourth T-Mobile site is getting b71 but not public yet. All of the T-Mobile sites are Sprint Co-Sites. Inside that perimeter lies 4 Sprint Sites. These two b25 neighbors are the center most.
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
-
Basically an Airave. If you have a VoLTE capable device, then the MB gold is better. It should have a much better range.What's the Pebble and how do its features compare to Magic Box Gold?
Sent from my Pixel 4 XL using Tapatalk
-
One thing I have noticed about CA is that Sprint seems to connect it whenever possible, where T-Mo seems to only add CA as needed, actively data transferring.
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
-
2
-
-
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.
Build your own devices, routers, relays, IoT etc.
in Hotspots/USB Modems
Posted
Sent from my Pixel 4 XL using Tapatalk