[Samsung Galaxy S8+ Guides, News, & Discussion] 0vermind:
Btw, if anyone wants to look at the TMobile XML file http://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G955U/version.test.xml. (Just for fun. Otherwise useless.)

Now, I

don't want to get anyone's hopes up

, but, I really doubt that if DRKE shows on the XML file, that it's still a long ways away. Why would the XML index file reference to a build that's not even close to being ready? Seems odd to me. Remember, this is the beta/dev list.

Reasons why I think we're close to a beta/dev Pie build:

1. SIMILARITIES, RIGHT DOWN TO THE HARDWARE. No reason not to test the S9 and S8 at the same time.

Samsung already has to do the work on the S9, might as well test the S8 builds at the same time. Just like Cyanogen/Lineage receives commits for other phones, and all builds get recompiled. Many are saying that Pie build will be announced on the SX/S10 first, followed by release of the build for S9, with S8 to follow. This theory seems BS to me. The logic follows the S7, which received the Oreo update in May/June. This isn't the S7. The S8 and S9 are incredibly similar. Such that many people didn't bother to upgrade. +2GB RAM on the + model, and the Snapdragon 845 in place of the 835. See here for differences. Both are 10nm architecture. Both are have similar memory, bandwidth, and processing speed. The 845 received a very small boost in these areas.

In addition, the cat's already out of the bag about One UI. Beta builds are all over the place. Samsung has released pages about it. Everyone is super excited. It's not a surprise feature that comes on the X/!0 first.

2. PROJECT TREBLE. DEBUNKING THE DOUBTS.

Google designed Project Treble as a modular Android framework that would allow OEMs to release much more stable builds, in a shorter amount of time. Yes, I know there are reports like, https://www.androidheadlines.com/2018/02/galaxy-s8-s8-plus-oreo-update-not-project-treble.html, that state that Oreo didn't have Treble, therefore, we're screwed. While little is known exactly how Treble works, we do know that the mechanism involves partitions for low-level firmware and drivers. As a software engineer myself, I will say, it doesn't make sense that Treble has to be on the phone first. It's software. Treble still allows Samsung to push out much quicker and more stable OS updates. Doesn't matter if they didn't include the framework initially. A small prereq update would fix that. Obviously our Oreo is already stable, to recompile the build with Treble partitions would be easy.

In summary, I don't buy it. Treble still helps Samsung in any situation I look at; it's something Samsung uses backend in their software engineering labs that would make it lickity split and snapity snap to compile and release a new build without the worry of "drivers." Whether this requires a pre-req or not, as in, take 1 update, a week later, the real update is released. Don't know, but could be. Either way I see it, we're all to benefit.

3. TRENDING DATA SHOWS PROGRESSION.

Samsung is improving their baking skills. They're getting better in the kitchen. Throw in Treble, throw in the other programs Google has implemented, and Samsung should be starting to bake builds by Summer. I for one am excited in the direction that Samsung is going in. The Note 7 left a bad taste in my mouth. I swore they would never regain my trust. Then, they removed the home button, redesigned the GS8 with thin borders, rounded corners, lighter software, and a sexy look. Instantly won me over, and it's been the best phone I've ever had. That's saying something, as I've been a root 'em and rom 'em type of guy since the OG Droid.