Phonovi
Log inCompare plans

Help centre

Follow the next useful step.

Search practical guides for setup, native Android apps, cryptocurrency payments, devices, and account safety.

Phonovi support context

Ask a useful question. Get a useful starting point.

Tell us the app, plan, order, or payment step involved and the exact result you see. Add a reference when relevant—never passwords, recovery codes, or wallet keys.

  • Choosing a plan: List the active projects that need separate Android contexts, then compare one-, three-, and 25-cloudphone plans.
  • App installation or sign-in: Send the app name, device name, step reached, and exact error. For Snapchat verification, use your own recovery channels and never disclose a password or code.
  • Order or crypto payment: Include the plan, order or deposit reference, network, and transaction hash. If the transfer is pending, do not send a second payment unless you receive clear instructions tied to the same order.

Help topic

Payments

Payments

Understand the minimum wallet top-up

The minimum wallet deposit is $20.00 USD.
  1. The wallet deposit minimum does not change the price of a direct plan purchase.
  2. Use the exact asset, network and destination shown on the payment request. Payments are reviewed manually.
  3. A confirmed wallet deposit adds credit to your account; it does not automatically order or activate a phone.
Link to this guide

Payments

Create a cryptocurrency payment request

Select both the asset and its network before sending funds.
  1. In checkout, confirm the plan and enter an email address you can access.
  2. Select the exact asset and network pair you will send, such as USDT on Tron or USDT on Ethereum.
  3. Create the payment request and copy the destination and amount from that request.
  4. In your wallet, compare the network, destination, and amount one more time before confirming the transfer.
Link to this guide

Payments

Understand payment and activation statuses

Read the payment and order status without assuming that a device will be delivered automatically.
  1. Pending means the payment request exists but has not reached the required confirmation state.
  2. Confirmed means the payment has been recognised and the order is recorded. It does not mean a cloudphone is ready to open.
  3. Automatic device provisioning and delivery are not connected. Keep the order reference and contact support for the current fulfilment route.
  4. Only use Devices after a device record has actually been added. If none exists, do not place a duplicate order to try to create one.
Link to this guide

Payments

Handle an expired payment request

Create a fresh request instead of sending to old payment details.
  1. Stop before sending if the request is marked expired, even if you copied its destination earlier.
  2. Return to checkout and confirm the plan you still want.
  3. Create a new payment request and use only the amount, network, and destination shown on the new request.
  4. If you already sent after expiry, keep the transaction ID and contact support with the order reference and network.
Link to this guide

Payments

Resolve an underpaid order

Gather the exact payment facts before asking for a review.
  1. Open the order and compare the requested cryptocurrency amount with the amount actually sent.
  2. Check whether wallet or exchange fees were deducted from the amount received.
  3. Do not send a second transfer unless the active order instructions explicitly tell you to do so.
  4. Use the contact form with the order reference, transaction ID, asset, network, and amounts requested and sent.
Link to this guide

Help topic

Getting started

Getting started

Create and follow your first cloudphone order

Follow your cloud phone order from payment to device activation.
  1. Choose a monthly plan for 1, 3 or 25 cloud phones. Confirm availability and activation timing before paying.
  2. Complete the payment request only after reviewing the asset, network, amount, address, and current delivery limitation.
  3. Keep the order and payment references while manual verification is in progress.
  4. A confirmed payment records the order; it does not automatically create or deliver a cloudphone. Contact support with the reference for the current fulfilment route.
Link to this guide

Getting started

Open your Android cloud phone

Use the browser workspace as the window into your remote Android device.
  1. Use this guide only after support has confirmed that a device record is available, then open your workspace and select Devices.
  2. Choose the device by its name and current status. Wait until the status shows that it is ready before opening it.
  3. Use Android navigation inside the device view just as you would on a phone: Home returns to the launcher and Back returns to the previous screen.
  4. Close the device view when you finish. Your Android workspace remains separate from the computer or phone you used to access it.
Link to this guide

Help topic

Apps

Apps

Install an Android app

Add an app inside the cloudphone, then sign in directly in that Android environment.
  1. Once your device is active, open it and launch its Android app source.
  2. Search for the exact app name and check the publisher before installing.
  3. Review the permissions requested by the app, then install only if they make sense for your use.
  4. Open the app from the Android launcher and sign in. Keep recovery details for the app account somewhere secure.
Link to this guide

Apps

Prepare Snapchat in your workspace

Install Snapchat, sign in with your own account and check the features you need.
  1. Once your cloud phone is active, open Android and install Snapchat from its available app source.
  2. Launch Snapchat and sign in with your own account. Complete any verification requested by Snapchat.
  3. Allow only the permissions you need for your intended use. You can review Android app permissions later in Settings.
  4. Before relying on the workspace, confirm that you can open the app again and that your Snapchat recovery email or phone number is current.
Link to this guide

Help topic

Plans

Plans

Choose your cloud phone plan

Match your plan to the number of separate Android spaces you need.
  1. List the activities or accounts that need their own Android space.
  2. Essential is the one-device plan, Plus the three-device plan and Workspace the 25-device plan. Activation is arranged separately.
  3. Leave capacity for a new project only if you expect to use it; you can review plan choices again later.
  4. On the pricing page, open checkout from the plan card so the correct plan is carried into your order.
Link to this guide

Plans

Prepare a cancellation request

Collect the account and order details needed to identify the plan without sharing secrets.
  1. Review the terms and refund policy that apply to your order.
  2. Record the account email, current plan, device names affected, and relevant order reference.
  3. Use the contact form, choose the billing or plan topic, and state the action you want and the reason in plain language.
  4. Keep your copy of the request and avoid deleting app data until you understand what happens to the device after cancellation.
Link to this guide

Help topic

Devices

Devices

Find and organise several devices

Use clear labels so each Android space is easy to choose at a glance.
  1. Use this guide only if device records have been added through manual fulfilment, then open Devices and review their current names.
  2. Keep a simple list matching each device name to its project or purpose. If you need a label changed and no rename control is available, include the device reference in a support request.
  3. Keep sensitive credentials out of device names because names may appear in workspace lists and order context.
  4. Before opening a device, confirm both its name and status to avoid working in the wrong Android space.
Link to this guide

Devices

Recover a device that feels stuck

Try the smallest recovery step first and preserve your work where possible.
  1. Wait briefly for the current Android action to finish, especially after installing or updating an app.
  2. Close the live device view, refresh the workspace page, and open the device again.
  3. If the device controls provide a restart action, use it once and allow the Android system time to return.
  4. If the same issue continues, note the device name, visible status, time, and last successful action before contacting support.
Link to this guide

Devices

Ask whether a device reset is available

Reset controls and workflows are not confirmed. If support confirms a reset route for a fulfilled device, first protect anything you are permitted to retain.
  1. Review the apps, files, and sign-ins stored only inside the cloudphone.
  2. Save anything you are allowed to retain using the app’s own export or sync options.
  3. Confirm that account recovery methods work without relying on the device you plan to reset.
  4. Ask support whether a reset is available for that device and what it would remove. Do not assume a dashboard control or automatic reset workflow exists.
Link to this guide

Help topic

Account

Account

Protect your account and app sign-ins

Secure the service account and each Android app account as separate things.
  1. Use a unique password for your service account and a trusted password manager to store it.
  2. Keep the email account used for sign-in secure and update its recovery methods.
  3. Turn on the strongest verification offered by each app you install, and store recovery codes away from the cloudphone.
  4. If access looks unfamiliar, change the affected account password, review active sessions in that service, and contact support with relevant order or device context.
Link to this guide