📩 Technical Firmware-Level Bug Report — Petal Maps Region Failure on DUDU7
Subject: Incorrect Region Exposure in DUDU7 Firmware Prevents Petal Maps Initialization (Requires Proper Android Country Code Handling)
The app installs successfully, but consistently returns:
“Map service is unavailable in your current region.”
This behaviour is reproducible and appears unrelated to user configuration. The issue stems from how DUDU OS exposes regional information to Android apps, and differs from the standard Android locale model.
Confirmed Requirements from Huawei
Huawei specifies that Petal Maps only enables map services in supported countries (e.g., UK, DE, NL, FR, etc.) and not broad regions such as “Europe” or “Asia.” Apps check the device’s assigned country/region to determine service availability.
— Supported countries are explicitly listed in Huawei’s documentation. [en.todoandroid.es]
Therefore, for Petal Maps to run, the device must expose a valid ISO 3166‑1 alpha‑2 country code such as:
GB, DE, FR, NL, ES, IT, etc.
Observed DUDU OS Behaviour (Based on User Reports & Verification)
✔ All Android locale properties (system properties) can be correctly set:
Examples:
persist.sys.locale=en-GB
persist.sys.country=GB
persist.sys.language=en
(These are already set correctly on affected units.)
✘ Despite correct Android locale values, Petal Maps does not read them
Users confirmed that even with full GB locale settings, Petal Maps still refuses service with the region error.
This implies that Petal Maps is receiving its region data from DUDU OS’s custom region layer, not from the Android locale subsystem.
- Root Cause: DUDU OS Uses a Non‑Standard, Non‑Country Region Model
From developer discussions on your forum:
DUDU OS does not expose a valid Android country code.
It uses continent-level selectors (“Europe”, “Asia”, “South America”), which are not valid ISO country codes and not acceptable for Android apps performing region checks.
Multiple users confirmed the region appears to be hardcoded in firmware/MCU, not changeable through Android Settings.
Apps such as Petal Maps rely on:
getConfiguration().locale
getResources().getConfiguration().getLocales()
System properties (persist.sys.locale, persist.sys.country)
Telephony / network-based country if available
On DUDU7, these mechanisms appear overridden or bypassed by the firmware, and Petal Maps effectively receives only the DUDU OS’s “Europe/Asia/etc.” region, which is invalid.
This causes Petal Maps to reject the device regardless of correct Android locale data.
- Required Firmware Changes (Technical)
To restore compatibility, the following must be changed at the system or MCU layer:
1️⃣ Expose a valid Android country code
Replace DUDU OS continent identifiers with actual ISO country codes (e.g., GB, DE, FR) for:
ro.product.locale
persist.sys.locale
persist.sys.country
And ensure these values propagate to app-facing APIs.
2️⃣ Stop overriding Android Locale APIs with DUDU OS region values
Apps must be able to call standard locale APIs without receiving DUDU’s continent values. Specifically:
Locale.getDefault()
Configuration.getLocales()
Resources.getConfiguration()
These should reflect the real user’s selected country, not “Europe.”
3️⃣ Add a genuine Android “Country/Region” selector
Under:
Settings → System → Language & Region → Region
This should expose countries, not continents.
Users report this menu does not exist on DUDU7.
4️⃣ Ensure the MCU layer does not re-inject invalid region identifiers
Users and developers suspect that the region system is MCU-level or hardcoded.
If the MCU is injecting:
region="Europe"
…it must be changed to pass a valid country code or defer entirely to Android.
- Reason This Must Be Changed
Huawei Petal Maps validates service availability based on the country reported by the OS. Because the DUDU7 reports a non-country region identifier, Petal Maps correctly fails its regional eligibility check.
This behaviour has been confirmed by multiple users and cannot be resolved via standard Android configuration.
- Request
Please confirm whether:
The DUDU7 can be updated to properly expose a valid country code to apps.
A future firmware or MCU update will correct the region handling.
There is an internal configuration file or system property (outside user control) that can be modified to pass correct region values to Android.
This is a fundamental OS/firmware compatibility issue affecting navigation and mapping apps that rely on proper Android region reporting.
Thank you for your assistance.