DroidPlay 0.2.2

Changed

• droidnative is now DroidPlay Core, at enjoyerofslop/droidplay-core: it was renamed so it isn't mistaken for DroidNative, which runs Linux desktop apps on Android. Setup, Settings and the messages say DroidPlay Core, and Setup clones it into ~/Library/Application Support/DroidPlay/droidplay-core. A checkout cloned before, in a droidnative folder, is still found and keeps working: GitHub sends the old address on to the new one.
• The Android app is called DroidPlay on the device, with DroidPlay's icon, in place of nxnative and its mark: the launcher, its header and themed icons, from DroidPlay Core's next build (droidplay-core#25). Its package is still org.nxnative.android, so installing it is an update: the games and saves on the device stay. Build APK exports it as DroidPlay.apk, and its How to install.txt and install.sh say DroidPlay; an older export with nxnative.apk still counts as one.

Installing this release

This build is not signed with a Developer ID or notarized, so macOS blocks it the first time it opens:

1. Open the DMG and drag DroidPlay into Applications.
2. Open DroidPlay. When macOS says it can't check it, click Done, then open System Settings › Privacy & Security and click Open Anyway beside DroidPlay. Or, in Terminal: xattr -dr com.apple.quarantine /Applications/DroidPlay.app.
3. DroidPlay doesn't update itself. It says when a newer release is out: download each one from this page.

SHA-256 of DroidPlay-0.2.2.dmg: 43f7f08053f05fa92faa727dd10acefda238912444edb0177c9d93fd72964b22

DroidPlay 0.2.1

Added

• DroidPlay says when a new release is out. At launch and once a day it asks GitHub for the latest release. When that's newer than yours, a banner above the library, a pill in Console Mode's top bar and Settings › Updates say so. What's New lists every release since your version, and Open Release Page opens the release on GitHub, where you download the DMG and drag DroidPlay into Applications. Later hides the banner until the next launch. DroidPlay still downloads and installs nothing itself: its releases are ad-hoc signed, so it couldn't check that a download is DroidPlay's.

Changed

• Console Mode's logo is DroidPlay's icon, the controller on its light green tile, in the top bar and on the update card. It drew only the controller, NX Play's logo too, so it read as NX Play's.

Fixed

• Setup's password prompt says DroidPlay, not NX Play, when installing a tool needs an administrator. For maintainers: bin/screenshots and mise run app look for DroidPlay.app again, so they work.

Installing this release

This build is not signed with a Developer ID or notarized, so macOS blocks it the first time it opens:

1. Open the DMG and drag DroidPlay into Applications.
2. Open DroidPlay. When macOS says it can't check it, click Done, then open System Settings › Privacy & Security and click Open Anyway beside DroidPlay. Or, in Terminal: xattr -dr com.apple.quarantine /Applications/DroidPlay.app.
3. DroidPlay doesn't update itself. It says when a newer release is out: download each one from this page.

SHA-256 of DroidPlay-0.2.1.dmg: e5cfc3988745dfa88962757f98ff241a012d9bae264ea97232e2d211c17badf2

DroidPlay 0.2.0

Added

• Setup installs what Android needs, as it does for the Mac and iPhone. Install Missing now also installs a JDK and the Android SDK's command-line tools with Homebrew (each only when the Mac has none), then the NDK, CMake, build-tools, an Android platform and platform-tools into ~/Library/Android/sdk, about 3 GB. Before installing those, Setup asks you to accept Google's Android SDK License, unless it was accepted in that SDK already (Android Studio's, say). droidnative and Android have their own headings in Setup, and a missing droidnative clone is now something Install Missing fixes. Uninstall offers to remove the two Homebrew tools as well; it leaves the Android SDK.

Changed

• Releases are ad-hoc signed, as the pre-releases were, not with a Developer ID. The first time, macOS asks you to allow DroidPlay (System Settings › Privacy & Security › Open Anyway), and DroidPlay doesn't update itself: download each release from the releases page, where its notes give the DMG's SHA-256. For maintainers: bin/release does this by default, --prerelease marks a pre-release, and --developer-id signs and notarizes as before.

New Contributors

• @enjoyerofslop made their first contribution in #2

Installing this release

This build is not signed with a Developer ID or notarized, so macOS blocks it the first time it opens:

1. Open the DMG and drag DroidPlay into Applications.
2. Open DroidPlay. When macOS says it can't check it, click Done, then open System Settings › Privacy & Security and click Open Anyway beside DroidPlay. Or, in Terminal: xattr -dr com.apple.quarantine /Applications/DroidPlay.app.
3. DroidPlay doesn't update itself: download each new release from this page.

SHA-256 of DroidPlay-0.2.0.dmg: 7ae2fe2b245b2f08965be822e6422c6a58d12863f2679f6f84812f6a146ab305

DroidPlay 0.1.1 (pre-release, unsigned)

Fixed

• Setup clones droidnative into DroidPlay's folder (~/Library/Application Support/DroidPlay/droidnative), where Install on Android looks for it. 0.1.0 cloned it inside the app instead, so Install on Android said there was no droidnative checkout and the app's signature no longer matched its files. After updating, run Setup again; the copy inside the old app goes with it.

Installing this pre-release

This build is not signed with a Developer ID or notarized, so macOS blocks it the first time it opens:

1. Open the DMG and drag DroidPlay into Applications.
2. Open DroidPlay. When macOS says it can't check it, click Done, then open System Settings › Privacy & Security and click Open Anyway beside DroidPlay. Or, in Terminal: xattr -dr com.apple.quarantine /Applications/DroidPlay.app.
3. DroidPlay doesn't update itself in a pre-release: download each new one from this page.

SHA-256 of DroidPlay-0.1.1.dmg: 0e2aa8fe4eb353f4a8757c88e140f2777ca461a2e5122bfcdff2a1d995e02bae

DroidPlay 0.1.0 (pre-release, unsigned)

Added

• Install on Android: the Game menu builds a game with droidnative, nxnative with an Android port. It installs the game with adb on an Android device with USB debugging on, such as an Ayn Odin 2, then starts it there. The build has a folder of its own, <game folder>/android, with links to the game files, so it never touches the Mac build, kept or not. One app on the device carries every game built on this Mac, and its saves stay through updates. Play on Android starts a game the device already has. Settings › Devices › Android sets the droidnative checkout, which can be your own branch, and shows the devices adb sees. From the Terminal: nxplay --android <serial> <game folder>. Remove Game deletes the Android folder too.

• Build APK makes the same Android build without a device. It exports the app and the game's files to <game folder>/android/<game name> (Android), to install on any Android device: with the install.sh beside them (adb, from a Mac or Linux computer), or by hand as How to install.txt explains. From the Terminal: nxplay --apk <game folder>.

• Build Game App makes a game an Android app of its own, with its name, icon and saves, opening straight into the game without the nxnative app. APK gives <game name>.apk, with the game data inside for a game under 2 GB; a bigger one gets <game name>.romfs too, which the app asks you to pick once and reads wherever it is on the device. XAPK gives one <game name>.xapk for an XAPK installer. It needs a droidnative checkout with build_android_from_nsp.py --game-apk (droidnative's main). From the Terminal: nxplay --game-apk or --game-xapk <game folder>.

• Switch 2 games on Android: Install on Android, Build APK and Build Game App take a game in a .nup file, with a droidnative checkout that reads one (its main does). DroidPlay says when the checkout can't. Dumps still need a Mac or an iPhone.

Changed

• NX Play becomes DroidPlay, a fork that adds Android, at enjoyerofslop/droidplay. It has its own name, bundle ID (io.github.enjoyerofslop.droidplay), settings, folder (~/Library/Application Support/DroidPlay) and update feed, so it installs beside NX Play without sharing anything with it. Android builds use droidnative, nxnative with its Android port, in place of nxnative-android; Setup clones it, and a checkout still in an nxnative-android folder is found as before.
• DroidPlay's icon has a light green background in place of NX Play's dark one, so the two tell apart in the Dock and in Applications (the iPhone app's too).
• DroidPlay's own versions start at 0.1.0, as unsigned pre-releases: no Developer ID yet, so macOS asks once (Privacy & Security › Open Anyway) and the app doesn't update itself. The releases below are NX Play's.

Installing this pre-release

This build is not signed with a Developer ID or notarized, so macOS blocks it the first time it opens:

1. Open the DMG and drag DroidPlay into Applications.
2. Open DroidPlay. When macOS says it can't check it, click Done, then open System Settings › Privacy & Security and click Open Anyway beside DroidPlay. Or, in Terminal: xattr -dr com.apple.quarantine /Applications/DroidPlay.app.
3. DroidPlay doesn't update itself in a pre-release: download each new one from this page.

SHA-256 of DroidPlay-0.1.0.dmg: 74ba66ab38e95c6dab17f7d8f4076b4aae76fdd83e66b9397eb5f14f5704f776