Google is not going to force a new file system on Android 13 after all

Spread the love

Google has chosen not to require Enhanced Read-Only File System, erofs, for new phones with Android 13. The use of ext4 and f2fs remains possible, according to a new commit.

Google has relaxed the requirements for the file system used, so says it itself. It’s unclear why Google did that. Whoever found the commit Mishaal Rahman of Esperalso says he doesn’t know why the company suddenly changed the requirements after months of preparations.

The requirement came out last week. By using erofs, manufacturers can save space on read-only partitions of phone firmware. With some devices this saves up to 800MB. It would also make the software run faster. It is unknown what disadvantages there are of using erofs. There is a chance that using erofs puts more strain on the processor and would therefore demand a little more from the battery, but there are no figures on that.

Google has not commented on the matter. The requirements for Android 13 are still changing, as the operating system is in beta. The intention was that erofs would be mandatory for phones that come out with Android 13. Huawei developed erofs a few years ago. OPPO and Xiaomi have also already used it on phones.

Google Android source code: No erofs obligation in Android 13 after all

You might also like