Before Project Treble came around (before Oreo, that is), the operating system framework and the low-level software drivers needed to make a phone’s hardware work with the OS were part of the same code. That meant that any changes to the framework, which is the user interface you see and use on your phone, also needed updated low-level drivers (which allow the hardware to work with the software) before a software update could be delivered to the consumer. So, for example, on the Galaxy S8, Qualcomm would need to update its low-level code for the Snapdragon 835 so that it works with Pie on the device. Samsung would then add all of its own tweaks to the UI and make other necessary changes and then roll out the update. With Project Treble, that low-level code has been separated from the OS framework. So now, Qualcomm doesn’t need to offer updated drivers to Samsung before Samsung can implement the user interface changes. And if the existing code for the Snapdragon chip works with a newer version of Android, Samsung only needs to update its user interface to release the final update.
you probably know why it won’t help, either. Samsung heavily modifies the Android framework, by both changing the user interface visually and by adding tons of new features on top. So every time there’s a new version of Android, the company has to make its user interface work properly on the new vanilla Android framework that Google provides. And that procedure, unfortunately, can take time. It takes additional time every time Samsung makes major changes to its own UI.
Project Treble is an Android project, designed to allow for Faster and more timely updates, even if you're using third party phones. Project Treble reworked the OS such that it is no longer hardware dependant, allowing for cheaper development and faster updates
