Android Call Recorder for all VoIP Services

Cube ACR for Android enables you to capture cellular phone calls, record WhatsApp calls and conversations in other VoIP apps and messengers, like LINE, Viber, Skype, WeChat and many more!

Great recording quality

Record incoming and outgoing calls in the best possible quality with Cube Call Recorder. Select from multiple recording options and sources to find the one that suits you best.

Stable and reliable

Frequent updates and improvements ensure that all your calls will be recorded via Cube Call Recorder, no matter what.

Cloud backup

Save your recording to Google Drive or via email

Geotagging

See where calls took place on a map (works only on Android)

Smart clean

Auto-remove old recording to free up space

Privacy

Secure your recordings with a PIN lock/TouchID/FaceID

Shake-to-mark

Marking important parts of a conversation (works only on Android)

Vbmeta Samsung M31 ((exclusive)) -

VBMeta on Samsung M31 — Informative Overview

Summary

VBMeta (Verified Boot Metadata) is part of Android’s Verified Boot (AVB) system that ensures integrity of boot and system partitions by verifying cryptographic signatures at boot. On the Samsung Galaxy M31, which uses Samsung’s firmware and often a mix of Android versions and vendor customizations, VBMeta plays a key role in enforcing whether modified boot, recovery, or system images will boot. Bypassing or modifying VBMeta is commonly required for rooting, installing custom recoveries (e.g., TWRP), or flashing custom ROMs, but doing so affects device security and may trigger Knox/firmware flags and OTA update issues.

If you see "error verifying vbmeta image: invalid", it usually means the bootloader is still locked or the vbmeta file you flashed doesn't match the current firmware version of your device. Always ensure you are using files from the exact firmware build currently installed on your vbmeta samsung m31

The vbmeta.img is a core part of Android's Verified Boot 2.0. It contains cryptographic signatures used to verify that the boot, system, and vendor partitions haven't been tampered with. On the Samsung M31, if you modify the boot image (to root) or the recovery image (for TWRP) without patching or disabling vbmeta, the device will detect the signature mismatch and trigger a bootloop or an "invalid vbmeta header" error. How to Create and Patch VBMeta for Samsung M31 VBMeta on Samsung M31 — Informative Overview Summary

The Conflict: If you try to install a Custom ROM or Root your M31, the hashes won't match. If you see "error verifying vbmeta image: invalid",

is a partition that contains checksums and cryptographic signatures for other partitions (like boot, system, and vendor). Samsung uses this to ensure that only official, unmodified software runs on the device. When you modify the boot image (e.g., for Magisk), the signatures no longer match, and the device will refuse to boot—often stuck in a "VBMETA Error" or boot loop—unless verification is disabled. When do you need it? Rooting with Magisk

For users looking to customize their Samsung M31 with root access or custom ROMs, managing the vbmeta image is often the first and most vital step to avoid "bootloops" or security verification errors. What is VBMeta?