Samsung Galaxy Fold receives Android 10 with One UI 2.0
The Samsung Galaxy Fold (review) might not be the perfect folding phone we had all hoped for, and the company has even released an alternate clamshell design with the Galazy Z Flip. Even with the insane pricing, Samsung has allegedly been able to sell a respectable number of Galaxy Fold units. Keeping aside the initial hype, the owners of this bleeding-edge device have been stuck with Android Pie to date, but there is a new ray of hope. Samsung has now started rolling out the long-anticipated One UI 2.0 update on top of Android 10 for the Galaxy Fold.
Samsung Galaxy Fold XDA Forums
According to Samsung’s Android 10 update schedule, the Galaxy Fold is expected to receive the taste of Android 10 in April. As the month of March is almost ending, the arrival of the OTA for this device – albeit only on the global 4G variant (model number SM-F900F) – is certainly a noteworthy event. The version number of the latest firmware is F900FXXU3BTCD, which is currently available in France. Samsung has not incremented the bootloader version (v3), thus it is possible to revert back to Android Pie though manual flashing. Regarding the Android Security Patch Level (SPL), it is bumped to March 2020 from January 2020.
We are unable to get our hands on the complete changelog at the time of writing this article, so it is not possible to tell whether Samsung shipped all the goodness of One UI 2.1 in this update or not. The OTA may take several weeks to reach other regional markets, but those who are interested can manually download the complete firmware package directly from Samsung update server using tools like Frija.
Samsung has not published the kernel source code for this particular build yet. Moreover, the aforementioned firmware is not at all compatible with the 5G Galaxy Fold variant (SM-F907x), so stay away from cross-flashing.
Source: Samfrew
The post Samsung Galaxy Fold receives Android 10 with One UI 2.0 appeared first on xda-developers.
from xda-developers https://ift.tt/2vPEVCk
via IFTTT
No comments: