MMY game APK: the file behind the games
Every game page on this site points back at one file. This page is that file's record, dumped with aapt2 on 10 November 2026. If the file you download reports different values, the file wins and this page is history.
| App name | MMY |
|---|---|
| File | mmy.2rwkt.apk |
| Size | 19.98 MB (20,954,528 bytes) |
| Version | 2.2.5 |
| Version code | 225 |
| Package | com.mmyuionn.opp02 |
| Android | 7.0 and newer (minSdk 24) |
| Target SDK | 35 |
| CPU | arm64-v8a only |
| Engine | Cocos 3.8.2 |
| SHA-256 | b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421 |
| Measured | 10 November 2026 |
Why the version code matters when picking a game page
Game directories go stale in a specific way: the catalogue changes inside the app while the pages describing it stand still. The version code is how you catch that. Version name 2.2.5 is a label for people; version code 225 is the integer Android compares. If the APK you install reports a higher code than 225, you are holding a newer build than the one these game pages were written against, and anything the in-app tables show outranks what you read here. Check the code before you lean on a page, not after a table surprises you.
The published game descriptions this directory relies on could outlive several builds unchanged, or change tomorrow. That is why each game page separates the developer's published text, which is dated and quotable, from the in-app table values, which are whatever the app shows the day you open it.
One listing, two files
The install listing serves the channel file mmy.2rwkt.apk, 20,954,528 bytes, package com.mmyuionn.opp02. It also serves a second file, mmy.apk, 21,049,457 bytes, package com.Mymuqiueb.ineb, carrying the same 2.2.5 version label. Android keys identity on the package name, so these are two different apps to the system: they install side by side, they keep separate data, and signing in on one does nothing for the other. The record on this site describes the channel file. If your download reports the other package name, the size and package line above will not match, and that mismatch is the tell.
Thirteen manifest permissions
INTERNET | Opens the network connection every game runs over. |
ACCESS_NETWORK_STATE | Checks whether the phone is online before a round starts. |
ACCESS_WIFI_STATE | Reads the Wi-Fi state; the manifest also declares the wifi hardware feature. |
MODIFY_AUDIO_SETTINGS | Adjusts the app's own audio stream. |
WAKE_LOCK | Keeps the screen awake during a round. |
POST_NOTIFICATIONS | Shows notifications on Android 13 and newer; the prompt appears at runtime. |
VIBRATE | Vibrates the handset on in-app events. |
READ_PHONE_STATE | Reads phone state. The one line worth reading twice before you accept the sheet. |
AD_ID | Reads the Google advertising id through Play services. |
BIND_GET_INSTALL_REFERRER_SERVICE | Asks Play which link led to the install. |
RECEIVE | Receives push messages through Google cloud messaging. |
READ_APP_INFO | A Samsung-only vendor permission; other phones ignore it. |
GET_COMMON_DATA | A Huawei AppGallery vendor permission; other phones ignore it. |
READ_PHONE_STATE is the single line that reads device state beyond the network and the screen, and it is worth a deliberate look on the install sheet. The Samsung and Huawei entries are vendor permissions that other phones ignore. Nothing in the manifest asks for contacts, messages, the camera or location, so a permission sheet showing any of those would mean you are not holding this file.
What the package holds back
The app is built on Cocos 3.8.2 and ships its game logic as one encrypted index.jsc, so the game inventory cannot be read out of the file. That single technical fact shapes this whole site: the six game pages come from the developer's published descriptions, the seven category labels come from the install listing, and the APK itself confirms neither list. A directory that claims to have read the catalogue out of this package is describing something it could not have seen.