Guide

Mammotion Android app: version history

A version-by-version changelog for the Mammotion companion app on Android, compiled from third-party APK mirrors, not the mower's own firmware.

From owners' reports in English and German, not from Mammotion's own pages.

Last updated
03 Nov 2026
Affects
Phone app — not the robot
Details
Last updated
03 Nov 2026
Affects
Phone app — not the robot

What to do next

  1. Read your app version from the app's About/Settings screen and find it in the list below. Remember the dates are mirror-indexing dates, not confirmed store dates, and only the month is shown where the two mirrors disagree.

    More about this step

    Applies when: an app update changed something and you want to know whether it is already documented.

    Worked if: you know whether the version you are on is a known-broken one.

    Didn't work? Next: step 2 — The app has a confirmed rollback path: note the version,...

    Method: the two APK mirrors, with this page's own conservative dating rule

  2. The app has a confirmed rollback path: note the version, uninstall, install a prior build. Get it from an APK archive with unknown sources enabled, and turn off auto-updates. One documented case is 1.15.4.16, where zone selection broke for four independent owners and a forum member agreed to a request to host an older APK as the workaround.

    Stop and get help if

    verify the publisher and package name before installing anything from a third-party mirror.

    More about this step

    Applies when: you are on a version this page flags, or an app update broke your workflow.

    Worked if: the app is back on the version that worked, and the store will not move it forward again.

    Didn't work? Next: step 3 — If the app hangs or white-screens on launch right after an...

    Method: the Android rollback guide's own steps, and the 1.15.4.16 reports cited here

  3. If the app hangs or white-screens on launch right after an auto-update, give it until a follow-up update arrives. Check the store, rather than assuming a device problem: three owners hit exactly that in July 2024, and the two who reported back were working again by the next morning once another update landed.

    More about this step

    Applies when: the app will not open at all immediately after updating itself.

    Worked if: the app opens again without any rollback being needed.

    Didn't work? Next: step 4 — Tell us if you can supply a Play Store release date. Also tell...

    Method: three independent owners, July 2024

  4. Tell us if you can supply a Play Store release date. Also tell us if you have a changelog for a version this page marks as having no individual page found.

    More about this step

    Applies when: you can cross-check any of these versions.

    Worked if: the gaps in the list close, and the dating stops being an inference from mirrors.

    Method: this page's own closing request

Phone app — not the robot. See our app vs. firmware vs. RTK guide if you're not sure which one you're dealing with.

On this page
  1. What to do next
  2. Where this comes from, and why the dates are approximate
  3. Version list, newest first
  4. Owner complaints about the update process itself
  5. Sources
This is the companion app, not mower firmware. App version and mower body firmware are two separate things that update independently. See app vs. firmware vs. RTK, explained if you're not sure which one you actually need to roll back. This page only covers the Android app; see iOS app rollback for that platform's much thinner options.

Where this comes from, and why the dates are approximate

Two third-party APK mirrors, Uptodown1 and APKPure2, each list their own version history for this app, and each version below links directly to its own APKPure page where one exists. APKPure is the primary source here because, unlike Uptodown's bare version/date list, most of its individual version pages carry an actual "What's New" changelog: real release notes, not just a number and a date. APKPure also offers multiple CPU-architecture builds (e.g. armeabi-v7a, arm64-v8a) per version; that detail isn't cataloged row-by-row below, but if a specific download fails on an older device, check you grabbed the matching architecture on APKPure's own page for that version.

The dates are mirror-indexing dates, not confirmed Play Store release dates, and the two mirrors routinely disagree with each other on the same version: sometimes by weeks, in a few cases by over a year. So the date shown for each version below follows one rule: when Uptodown and APKPure agree on the exact same day, that's shown as an exact date (two independent mirrors corroborating each other is real evidence). Everywhere they disagree, only the month is shown, using whichever mirror's month is earlier, a deliberately conservative "known to exist by at least this month" reading rather than implying a precision neither mirror actually supports. A handful of versions only appear on one mirror; those are rounded to month-only too, for consistency with everything else on this page rather than mixing exact and approximate dates row to row.

Three of the disagreements are large enough to flag specifically, not just silently round away: 1.12.134 is dated April 2025 on APKPure but June 2026 on Uptodown, over a year apart for the same version number. 1.13.10.5 (the version that first added SPINO E1 support) is dated June 2025 on APKPure vs. September 2025 on Uptodown, a three-month gap. 1.12.76 is dated February 2025 on APKPure vs. September 2025 on Uptodown, about seven months apart. These are stated as-is rather than guessed at; if you can pin down the actual release date for any of these, let us know.

Version list, newest first

Several version numbers below carry near-identical changelog text (e.g. 2.3.4.22 / 2.3.4.19, and 2.3.2.13 / 2.3.2.7), reproduced faithfully from each mirror rather than a transcription error on this site's part.

2.3.18.21: August 2026 · APKPure

LUBA 3 AWD / LUBA mini 2 AWD 1000 & 1500 / YUKA mini 2 Vision & LiDAR: added a Travel Speed setting, Auto-reverse Mowing Direction (reduces grass matting), Real View Map, automatic task resumption after rain, a Basic mode for AI Obstacle Detection, and support for resuming unfinished tasks. SPINO: E1 gained Scheduled Parking; S1 got optimized map features.

2.3.18.20: August 2026

No individual changelog page found on APKPure for this version (Uptodown-only date).

2.3.18.19: August 12, 2026 (corroborated by both mirrors) · APKPure

Same feature set as 2.3.18.21 above (Travel Speed, Auto-reverse Mowing Direction, Real View Map, rain task resumption, Basic AI Obstacle Detection, resume unfinished tasks; SPINO E1 Scheduled Parking, S1 map optimizations).

1.15.6.6: August 2026

No individual changelog page found on APKPure for this version (Uptodown-only date).

2.3.12.14: August 2026 · APKPure

"Improved safety during turns". No further detail given.

2.3.12.11: July 2026 · APKPure

Added Japanese and Korean language support and optimized display/interactions on certain pages (all models). LUBA 3 AWD / LUBA mini 2 AWD 1000 & 1500 / YUKA mini 2 Vision & LiDAR gained Cloud Backup (up to 10 maps), EcoSleep (reduces long-term energy use), and mapping without first setting up the charging station. LUBA mini also gained Cloud Backup. SPINO S1 added mapping and map-viewing support.

2.3.8.19: May 2026 · APKPure

Redesigned home page and device list (cleaner layout, multi-device list, expandable second screen). LUBA 3 AWD / LUBA mini 2 AWD 1000 & 1500 / YUKA mini 2 Vision & LiDAR gained support for mapping a separate lawn by temporarily lifting the robot over obstacles en route. SPINO S1 added support and some new features; other fixes.

1.12.134: April 2025 (see the large-discrepancy callout above) · APKPure

LUBA mini AWD / YUKA mini: updated the installation diagram for the RTK reference station.

2.3.4.22: May 2026 · APKPure

SPINO E1 added Waterline Parking, device sharing, and task-completion notifications. LUBA 3 AWD / LUBA mini 2 AWD 1000 & 1500 / YUKA mini 2 Vision & LiDAR gained dual-mode task settings and more precise cutting-height adjustment. LUBA 2 AWD / LUBA mini AWD / YUKA / YUKA mini gained the new Cloud Backup. Plus fixes, display/layout optimization, and improved remote-connection stability.

2.3.4.19: April 2026 · APKPure

Same release notes as 2.3.4.22 above.

2.3.2.13: April 2026 · APKPure

LUBA 3 AWD / LUBA mini 2 AWD 1000 & 1500 / YUKA mini 2 Vision & LiDAR: added a Redraw Section feature, auto-switching between 4G and Wi-Fi for iNavi, and expanded battery status indicators. LUBA mini AWD added decorative pattern mowing and the same Redraw Section feature. Plus 4G connection/signal optimization for certain models and other fixes.

2.3.2.7: April 2026 · APKPure

Same as 2.3.2.13 above, described as "Redraw Border" rather than "Redraw Section" for the equivalent feature.

2.2.4.13: March 2026 · APKPure

LUBA 3 AWD / LUBA mini 2 AWD 1000 & 1500 / YUKA mini 2 Vision & LiDAR gained No-go Zone perimeter tasks, task path sequencing, and optimized recharge-path settings. LUBA mini 2 AWD 1000 & 1500 gained a battery-heating feature for low-temperature conditions. Now compatible with LUBA mini 2 AWD 1500; plus fixes and UI optimization.

2.2.2.4: February 2026 · APKPure

YUKA mini 2 Vision / LUBA 3 AWD gained an off-peak charging schedule, optimized map visualization in Task Reports, improved initial mapping guidance, and manual-refresh support in Find My Device. LUBA 3 AWD specifically added Auto Mapping; YUKA mini 2 Vision added Relocate Charging Station (re-syncs the map after moving the charging station). Now compatible with YUKA mini 2 LiDAR and LUBA mini 2 1000.

2.1.2.16: January 2026 · APKPure

Redesigned Message Center and Signal & Positioning displays (all models); added support for the new LUBA 3 AWD. YUKA mini 2 / LUBA 3 AWD gained an improved Work Report and new Power Management (precise battery charge/discharge and auto-return settings). YUKA mini 2 specifically added an Auto Lighting toggle, lawn-pattern printing, and Wildlife Safety support, and removed nighttime mowing task restrictions.

1.15.10.35: December 2025 · APKPure

YUKA mini Vision: fixed a crash some users hit when connecting the device. General: fixed a model display error.

1.15.10.22: November 2025 · APKPure

YUKA mini Vision gained an all-new Mowing Report with richer data displays, Edge Distance settings, the ability to add no-stop zones during mapping, and an Update Map feature. Also increased max mowing speed for Manual Mowing/Manual Control and redesigned how task progress displays on the map.

1.15.6.14: September 28, 2025 (corroborated by both mirrors) · APKPure

Easier access to Manual Control (all models). YUKA mini Vision gained device sharing, volume settings, and improved mapping/DropMow UI. SPINO E1 got a new mode icon for clarity.

1.15.4.16: September 2025 · APKPure

YUKA mini Vision: robot icon now greys out when positioning is invalid. YUKA mini / YUKA 2025 / LUBA 2 AWD X / LUBA mini AWD / LUBA mini AWD LiDAR gained No-stop Zones (robot passes through unconditionally while working). All models: fixed overlapping text in Map Settings for some languages.

Known bad release, corroborated by 4 independent reports: after updating to this version, mow-zone selection broke: tapping a zone required repeated re-taps to register, or the wrong zone mowed; one owner had the app show only one zone selected but the mower cut every zone anyway. A forum member in the same thread agreed to a request to host an older APK as a downgrade workaround, though the file itself was ultimately too large to actually upload to that forum6. If you're on this version and hitting zone-selection problems, this is a known issue, not a device fault. Downgrading to a prior version (see the list below) is the only reported workaround.

1.14.2.29: July 2025 (see the discrepancy note above; Uptodown dates this September 2025) · APKPure

Improved RTK reference station connectivity in weak-signal environments. Fixed LUBA mini AWD LiDAR failing to auto-undock during auto-mapping due to a missing positioning signal. Fixed the cutting-path angle not displaying (all products).

1.13.10.5: June 2025 (see the large-discrepancy callout above; this is the version that first added SPINO E1 support) · APKPure

"Support SPINO E1 products", the app's first release with SPINO E1 support.

1.12.78: September 2025

No individual changelog page found on APKPure for this version (Uptodown-only date).

1.12.76: February 2025 (see the large-discrepancy callout above) · APKPure

LUBA / LUBA 2 AWD / YUKA: fixed app crashes caused by performance issues, fixed lag/delay controlling the robot via Bluetooth, and fixed relative-angle setting not working. LUBA 2 AWD X / YUKA 2025: improved the range for path-spacing settings.

1.11.230: September 2025

No individual changelog page found on APKPure for this version (Uptodown-only date).

1.11.188: September 2025

No individual changelog page found on APKPure for this version (Uptodown-only date).

If you've cross-checked any of these against the actual Play Store release date, or found a changelog for one of the versions marked "no individual page found," let us know.

Owner complaints about the update process itself

Separate from what any individual version changes, several recurring complaints are about the app's update process: owners reporting they can find no release notes at all for a version they'd already installed3 (the in-app path, Settings → Manage robot → Firmware release notes, isn't always populated the same day a firmware update ships). Others are a firmware update that forced itself on the user and blocked normal app use behind a gate4, and the app/site's password reset not working5. None of these are tied to a specific version number here: they're documented as an ongoing pattern with the update/account infrastructure, not a per-release bug.

July 2024: an auto-installed Android app update briefly broke the app entirely. Three independent owners hit an identical hang/white-screen on launch the same evening, immediately after the auto-installed app update. About three hours after the first post, one of them saw that another app update had arrived and the app opened again; the next morning a second owner confirmed theirs worked too. The third owner did not post again7. No version number is recorded for either the broken or fixed release; if you hit an app that suddenly won't open at all right after an app update, this pattern (broken, then a follow-up update the same evening) is worth waiting out before assuming a device problem.

Sources

Did this work, or not?

Telling us what happened helps the next owner with the same fault.

Tell us what happened

Fixed it? Share with other owners.

Post directly to Reddit or use link in text, email, Facebook, etc.

Reddit