Jump to content

Galaxy tab e


Rocket87

Recommended Posts

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

Link to comment
Share on other sites

  • 2 weeks later...

I just updated my Tab E today to the newest build. It's been since late last year that it got an update, so at least they still are updating the security of it. Did you notice anything else different? It was over 300MB, so I would think that would include something other than security, but I haven't noticed anything else different. 

  • Like 1
Link to comment
Share on other sites

On 9/17/2017 at 4:05 PM, Galaxyguy said:

I just updated my Tab E today to the newest build. It's been since late last year that it got an update, so at least they still are updating the security of it. Did you notice anything else different? It was over 300MB, so I would think that would include something other than security, but I haven't noticed anything else different. 

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.

  • Like 1
Link to comment
Share on other sites

I'm taking my Tab E to Sprint to have it wiped and the OS reloaded from scratch.  I can't find a tar for the QH2 build recently released.  This is the last suggestion that MB support has.

Link to comment
Share on other sites

  • 3 weeks later...

It looks like the update from a few weeks ago was just a precursor. I just downloaded a new update yesterday, Android 7.1.1. So far, it looks pretty good, and maybe seems just a little faster than 6.0. The only thing I wish it had is a built in blue light filter. All the Samsung phone builds have had that in Android 7, but for some reason, they decided to omit it from the Tab E build. One nice feature is they finally put in a quick access button on the drop down for the hotspot. It's so much faster than having to dig through the settings just to turn the hotspot on. 

Link to comment
Share on other sites

Yup,  I got the update too. Saw an Android Police article about Verizon and T-Mobile getting updated,  so I checked last night. 

I don't expect any further updates

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...