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

    • 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.
    • At some point over the weekend, T-Mobile bumped the Omaha metro from 100+40 to 100+90 of n41! That's a pretty large increase from what we had just a few weeks ago when we were sitting at 80+40Mhz. Out of curiosity, tested a site on my way to work and pulled 1.4Gpbs. That's the fastest I've ever gotten on T-Mobile! For those that know Omaha, this was on Dodge street in Midtown so not exactly a quiet area!
    • Did you mean a different site? eNB ID 112039 has been around for years. Streetview even has it with C-band back in 2022 - https://www.google.com/maps/@40.7303042,-73.9610924,3a,24.1y,18.03h,109.66t/data=!3m8!1e1!3m6!1s2ossx06yU56AYOzREdcK-g!2e0!5s20220201T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D2ossx06yU56AYOzREdcK-g%26cb_client%3Dmaps_sv.share%26w%3D900%26h%3D600%26yaw%3D18.027734930682684%26pitch%3D-19.664180274382204%26thumbfov%3D90!7i16384!8i8192?coh=205410&entry=ttu Meanwhile, Verizon's eNB 84484 in Fort Greene has been updated to include C-band and CBRS, but not mmWave. I've seen this a few times now on updated Verizon sites where it's just the CBRS antenna on its own, not in a shroud and without mmWave. Odd.
    • Drove out into the country today.  Dish stuck to my phone like glue. At least -120 rsrp. Likely only good for phone calls (should have tested.) It then switched to T-Mobile. Getting back on Dish was another issue. I am used to dragging out coverage so I expected a few miles, but had to drive at least 10 miles towards a Dish site. Airplane mode, which worked for Sprint, did nothing. Rebooting did nothing. Finally got it to change over about 2 miles from the site by manually setting the carrier to Dish then it had great reception. Sprint used to have a 15 minute timeout but I did not have the patience today.  Previously I did a speed test on Dish out in the country at the edge of Dish coverage. My speeds were 2g variety. Dish has really overclocked some of these sites. Seen rssp readings in the 50s. Would have called them boomer sites with Sprint but much  more common with Dish.  
  • Recently Browsing

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