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

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

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