It may have taken XDA Senior Recognized Developer rovo89 a while to get Xposed Framework working on Nougat, but that wasn’t the case with Android Oreo. Three months after was released for Nougat, the first beta version of the framework for Android 8.0 and Android 8.1 Oreo was released. Today, the Xposed —the Xposed ’s frontend installation and management tool—has been updated to version 3.15.

As we see with virtually every beta release, there’s always something to work on and this initial release of Xposed Framework for Android is no different. With the Xposed Installer bump up to 3.15 we have a couple of small changes paired with a couple of more important ones. Here’s the full change-log:

Xposed Installer v3.15 Change-log

  • Fixed a crash in download list search on Oreo.
  • Fixed a crash when sending log on Oreo.
  • “Optimize apps now” menu item, will trigger cmd package bg-dexopt-job. It’s available since Oreo and will start the job that usually runs once per night if the device is charging. If you feel degraded performance after installing Xposed, it might be because all apps are running purely on JIT and interpreter. That’s because Xposed needs additional information to identify methods it has to invalidate, and that information will be determined during the next compilation. If you want that to happen now, use this new feature. It took about 20 minutes on my Pixel. For more background, see here.
  • Detection if Verified Boot (dm-verity) is active. If yes, any changes to the system partition will be detected and you’ll end up in a boot loop. The detection might not be 100% perfect yet, so if you notice false positives or negatives, please report a bug along with the output of adb shell getprop.

Xposed Framework v90-beta2

rovo89 has also published v90-beta2 and uninstaller 20180117, and you can find these available via the Xposed Installer and the Xposed website. These support (un)installing Xposed via TWRP on the Google Pixel and probably other “system root image” devices, which rovo89 describes as devices where the system partition is mounted as the root directory and /system is actually just a subdirectory. Lastly, the previous uninstaller had a typo, which probably led to boot loops on all devices so be sure to always use the latest uninstaller!

Want more posts like this delivered to your inbox? Enter your email to be subscribed to our newsletter.

Source link


Please enter your comment!
Please enter your name here