jefbal99

I thought only unlocked devices had the MSL 000000

No changes, that i could tell other than security patches. But an entire years worth of security patches Samsung is testing/building Android 7 for the Tab E, I'm hopeful for one more release.

Still working with MB support on my Galaxy Tab E not connecting to the MB. Its so odd in the LTE available file, I see the two towers to the East and West, but no mention of the MB. Support requested a factory reset of the Galaxy Tab E so I'm going to try that out tonight

I thought SMS ran over the CDMA 1x/1xA network

SMS doesn't run thru the MB, but the macro network. If your phone can't see the macro network, texting won't work.

I got it late August 2016

That little birdie had the Test Drive updated to the September security patches. On a different note, took my Moto X Pure with the busted screen in for a repair to a local shop today. $130 parts/labor, not bad, I have to send my Nexus 6P in for a battery replacement to Hauwei, so I need a functional device for a couple weeks. Will be nice having Miracast back, might be swapping the SIM around when I need to stream Netflix

rgr

So much great information here, thanks for the long reply Few notes/additions: 1. West Michigan Tower spacing is terrible, the network was originally built by iPCS before being acquired by Sprint. The layout was at max spacing for phones with external antennas. It has gotten better, but still needs a great deal of densification. 2. Sprint is not doing a good job of keeping users in the B25/B41 rings off from B26. Not sure if it is due to a lack of capacity on B41, but my Nexus 6P would never use B25, it was always B41 or B26, until B26 was disabled. I would be outside walking and see one or two macro sites in Lansing, MI, would never touch B25. Something with the load balancing or priority is funky. I've tried to work with Sprint support a few times, but it never leads anywhere. 3. Towers in West Michigan follow the freeways for the most part, so if the town/city is a mile or two from the freeway, B41 is under utilized. 4. 10x10 B25 seems to be under utilized in this region, always great performance when on that carrier

Are sites live with four B41 carriers?!?!

That's what I thought too, but it wasn't the experience. Just think about any one in their house with a phone in their pocket, or an older home with poor RF reception. They'll be in the area you'd expect B41 or B25, but they will move to B26, then stay there.

Interesting, no B71 for TMobile 600Mhz LTE

Are the specs out on the LTE connectivity for the Watch? Triband?

Be prepared for it to get overwhelmed very quickly and basically unusable. Not trying to be debbie downer, but on the westside of Michigan, B26 has become a joke. I had to disable it on my Nexus 6P

Well that's interesting, can I PM you for some information to share with MB support?

Update: According to Hauwei, my device is under warranty until November 21st and they will replace the battery for free, however, they don't offer swaps or replacements. I'll be without a phone for a 7-10 days. I don't have any spare devices as my Ex-wife destroyed them all over the last few years. Need to get the screen replaced on my Moto X Pure so I can utilize that before sending this one in. I also have to fully wipe the device and clear anything from it, ugh!

Got a call from MagicBox support regarding the Galaxy Tab E not connecting. Went over everything I had done so far and they are looking into it, hope to hear more in the next few days.

I'm not sure if it's hardware or software or a combo of one impacting the other, but they need to support customers. Replacing a battery for $165 is a bunch of crap. We'll see what my experience is, but live and learn...

That doesn't mean CA, its just a known third carrier that you are connected to

I meant bigger as in the number of users impacted. This will probably be my last Huawei device if they don't give decent support.

Still loving my MagicBox, at times my device prefers the Macro network, but it gets on the MB pretty consistently. My Galaxy Tab E is still not connecting to it, trying to avoid the Factory reset that support has suggested. MB support has indicated that the Tab E should connect to it. Edit: Confusion between me and MB support, they wanted me to reset the MB and re-run the setup wizard, not my tablet. I did that this morning and we'll see what happens.

You'l need someone to capture it for you, why can't you update automatically?

I hope not, this seems to be a much larger issue...

Ugh, so the reboot issue I've been experiencing since April with the phone shutting down with about 15%-18% battery remaining is driving me nuts, I was so hoping that Oreo would resolve, but alas, it hasn't. Started with Google support, I've already done a reset back in June with no joy. Because my phone was purchased via Amazon, they directed me to Hauwei support. I've emailed them, we'll see where it goes. Hoping something can get resolved as my purchase was 8/26/16

Troubleshooting this device, trying to get it to connect to my MB. Did a manual update check for the first time in a month and had a 300+MB update to T377P-VPU2BQH2. Still Marshmellow 6.0.1, but up to the August 1, 2017 security package. Build number MMB29M.T377PVPU2BQH2. With the new update, the device has latched onto the B25 10FDD carrier, hasn't touched B41 or the MB yet. Keeping an eye on SCP for connections changing. QH2 i think indicates September 2nd 2017 build date