Out of box: the phone ships with Google’s mobile platform release 13 paired with the maker’s custom skin (UI 4.x in most regions). Factory builds typically carry an RMX-style model code and a security-patch date stamped in the About section; check that date to confirm current protection level before installing any system-level upgrades.

Vendor support for this budget line usually includes at least one major platform upgrade and a minimum of two years of security patches, though cadence may be monthly or quarterly depending on market. For precise entitlement, consult the official support page for your regional variant – carrier-locked units often follow a different rollout schedule than unlocked units.

How to proceed: open Settings → About phone → Software information to read the platform release and patch level; back up user data to cloud or local storage; install only stable over‑the‑air vendor upgrades (avoid public betas unless you accept potential instability); if a new build causes issues, contact vendor support with the build number and security-patch date for rollback or remediation options.

Installed OS Details

Recommendation: open Settings → About phone and record Build number, UI release name, Security patch level and Kernel version before applying any firmware upgrade or flashing files.

• Where to find core fields (UI): Settings → About phone
  • Build number / Build ID – exact ROM tag shown in updates list.
  • UI release name – vendor skin label (e.g., UI 4.x, UI 5.x).
  • Security patch level – formatted YYYY-MM-DD; determines monthly security status.
  • Baseband / Radio firmware – important for connectivity and carrier compatibility.
  • Kernel version – shows kernel build date/time and git tag used by vendor.
• Advanced retrieval via PC (fast, exact)
  1. adb shell getprop ro.build.id – ROM build ID displayed by the system.
  2. adb shell getprop ro. If you adored this article so you would like to get more info regarding 1xbet app apk download nicely visit the website. build.display.id – user-facing build string.
  3. adb shell getprop ro.build.version.sdk – API level number (example: 33 = platform release 13).
  4. adb shell getprop ro.build.version.security_patch – security patch date.
  5. adb shell uname -a – kernel name, version and build timestamp.
• How to read a build string
  • Prefix often includes device SKU or model code; middle segment shows release tag; suffix may include regional or carrier marker.
  • Stable-channel builds typically lack beta/alpha tags; look for words like «stable», «beta», «trial» to identify channel.

Interpretation and quick checks:

• API level (numeric) → maps to platform release (use API mapping table if unsure).
• Security patch older than three months → plan for a security patch upgrade; check vendor support pages before proceeding.
• Mismatch between build ID and displayed UI name → possible custom or carrier-modified firmware; avoid sideloading generic images that don’t match build family.
• Unlocked bootloader shown in developer options or fastboot → needed for custom ROMs but voids official warranty and may block some banking apps.

Practical recommendations:

• Back up full user data (local + cloud) and note current build strings before any upgrade/flash.
• Prefer official channel packages that match your exact build ID and region.
• When troubleshooting connectivity or camera regressions, supply kernel build timestamp, baseband version and security patch date to support personnel.
• Use adb dumpsys package or Settings export when reporting bugs to include precise build/display IDs and API level.

Stock Android version at launch

Shipped with the 13th major release of Google’s mobile operating system (API level 33) as the factory firmware.

Factory build included the vendor’s custom skin layered on the base OS; initial units carried a launch software image with a security patch roughly from late 2023 (verify exact date on your device under Settings → About → Security patch level).

To confirm the shipped build: go to Settings → About phone → Software information and note the OS release number, API level and security patch date. Record the build ID before installing any OTAs so you can track incremental changes.

Update guidance: enable automatic system updates over Wi‑Fi, create a full backup before applying major upgrades, ensure battery ≥50% (preferably charging) and free storage ≥2–3 GB. Expect first public OTA to be several hundred megabytes up to ~2 GB depending on carrier/customization.

Carrier-branded units may receive patches later than unlocked models; if timely security fixes matter, prefer unlocked variants or check carrier support pages for rollout schedules.