Android M is now available for testing as part of the Developer Preview program. You can install Android M right now onto Nexus 5, 6, 9 and Nexus Player. The improvements are already showing from what we have tested and that is pretty good keeping in mind this is isn’t anywhere near the final stage as we saw with Android L. What’s more exciting is, the rumored multi-window functionality can be enabled — with a hack, thanks to an awesome guy on Reddit.
The option to enable or disable multi-window is not shown to normal users. The workaround? See the full list of steps below to find out after the jump. This feature is still half-baked into Android M, and we really hope it gets completed by the time the final version is ready to be shipped to everyone in Q3 2015.
How To Enable Multi-Window On Android M:
Step 1 – Install TWRP on your device. If you haven’t done that already, use the following links to install TWRP on your corresponding Nexus device.
Step 2 – Boot into TWRP, go into “Mount” and make sure that System is already mounted. If it says mount system than click it. Our target is, it should display “unmount System”.
Step 3 – Download Android SDK from the Android Developers website and install. Also set it up with downloading platform-tools and USB drivers package in SDK. See: How to Set up ADB and Fastboot on Windows.
Step 4 – Navigate to android-sdk-windows\platform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 5 – Type in the following commands and press enter.
Step 6 – In order to enable Multi-Window, change
Step 6 – Exit all the windows including the editor and shell. Reboot your device. You might get a notification saying unable to verify and your device might not work properly. From what we have seen, this doesn’t effect anything.
Step 7 – Go to Developer Options, Enable the Multi-Window Option.
Step 8 – In order to utilize Multi Window, just tap on recents and tap on the new icon alongside the closing one.
This feature is still in the works and it is closed even in the developer preview because it is very buggy and still in development phase.