Cloud phone scores surpass real phones by 18%: A silent revolution in virtualization technology

On May 15th, at the Google I/O conference, the release schedule for Android 14 was announced. Instantly, everyone started to worry: most cloud phones are still on Android 11, does this mean they will fall behind by a whole generation?

However, the answer is surprising.

Last week, NestBox quietly launched an Android 13 image. In real tests, the AnTuTu score was 18% higher than that of a real device with the same SoC, and the temperature control curve was as stable as a straight line, with no frequency reduction even after 60 minutes of continuous operation. For the first time, cloud phones have turned “version number anxiety” into a “performance bonus.”

What exactly happened behind the scenes?

---

01 Real Devices Can’t Keep Up with Cloud Phones? GPU Passthrough Redefines Virtualization

The traditional architecture of cloud phones works like this: GPU instructions are translated into OpenGL and then sent back to the original machine for rendering. This is akin to making a sprint champion run with sandbags, and performance loss is inevitable.

NestBox adopted the GPU-Passthrough solution: the physical GPU card is divided into virtual functions through SR-IOV, and the VF is directly passed through to the QEMU virtual machine. VirtIO-gpu is only responsible for frame buffering, and the instruction translation layer has been almost completely removed.

Real test data confirms the advantages of this architecture: with the same Snapdragon 865 reference design, the real device scored 778,000 points on AnTuTu, while NestBox reached 920,000 points. The 18% difference mainly comes from the absence of the “translator” in the middle. Simply put, by eliminating the translation step, performance naturally improves.

---

02 Behind Zero Frequency Reduction: Rethinking Thermal Management

When a phone’s SoC hits the thermal limit, it is common for the CPU to reduce from 4 cores to 1 core and for the GPU frequency to be halved. This is a physical limitation of the device—the cooling capacity of the terminal device determines the upper limit of performance release.

NestBox deploys computing power in a 30°C constant-temperature water-cooled cabinet, completely removing the SoC’s power wall. The platform can continuously maintain 100% performance output.

After pinning all 8 cores for 2 hours with stress-ng, the frequency remained a straight line, with frame rate jitter less than 0.3%. This is a “cool” performance that real devices can never provide.

---

03 Android 13 Deployment: Taking Advantage of Google’s Push Window

Although Android 14 has been officially announced, the actual GMS push in China will not happen until Q4. This means that even with the latest flagship, many developers will have to wait several months to adapt and verify API 33+.

NestBox fully launched the Android 13 image on May 19th, achieving full-stack alignment with API 33: new permission models, notification runtime permissions, per-app language preferences, and more are all included.

For developers, this means that they can now upgrade the targetSdkVersion in CI to 33 and complete Monkey testing on cloud real devices, which is a whole quarter faster than waiting for the real device OTA.

---

04 Scalable Debugging: A New Paradigm for CI/CD with ADB/IP Whitelisting

A common pain point for Android developers is that local USB debugging lines start to drop connections when connected to more than 10 devices.

NestBox maps the ADB port to the public network, achieving secure access through IP whitelisting. A single YAML in GitHub Actions can concurrently connect to 200 devices:

- name: Connect cloud phones
  run: |
    for ip in $(cat phone_list.txt); do
      adb connect $ip:5555
    done

Unit Test, UI Automator, and Gradle Managed Device processes require no code changes, making cloud phones “scalable real devices” for the first time.

---

05 Full Technical Architecture Overview: The True Capabilities of QEMU + VirtIO

NestBox’s published “Android 13 Virtualization Technology White Paper” reveals key details of the underlying architecture:

• KVM Virtualization: 8-core 5G specification vCPU bound to physical cores, L3 Cache exclusive
• VirtIO-blk: NVMe backend support, 4K random read 230k IOPS, 3 times higher than eMMC real devices
• VirtIO-net: 10 Gbps vDPA passthrough, live streaming latency <40ms
• GPU SR-IOV: 1:8 slicing, maximum 16GB video memory per card, 1080p 60fps gaming without frame drops
• Android Container Layer: android-ranchu device tree, CTS compatible, can pass Google official certification

---

06 More Than Just Scores: Cloud Phones Are Reshaping Workflows

The significance of technical parameters ultimately lies in their practical applications:

APP Automation Testing: 200 concurrent runs, 200 hours of Monkey testing, zero disconnections, at a cost of only 1/5 of a physical real device farm.

Live Streaming Traffic: Professional version supports 32 simultaneous 1080P streams, with a monthly cost of 130 yuan per stream, saving 97% compared to purchasing 32 flagship phones.

Mobile Office: Internal authorization management for financial, operational, and customer service group control, with data stored in the cloud, ensuring no data leakage even if the phone is lost.

Marketing Fission: Batch group control supports one-click device modification and one-click new device, generating 500 UA data entries in 5 minutes, tripling the speed of effect advertising.

---

While others are still worrying about version numbers, NestBox has already used Android 13 + GPU passthrough to create a new species of “cloud real devices” that are faster, more stable, and cheaper.

But this is just the beginning. As SR-IOV virtualization technology matures and data center infrastructure continues to optimize, the potential for cloud computing power release is far from reaching its ceiling.

So, the question arises: when the performance of cloud phones consistently surpasses that of real devices, and the cost is only a fraction of the latter, do developers still need to wait for real device OTAs? Is the next step in mobile testing inevitably moving to the cloud?

Feel free to share your thoughts in the comments section.

---

Learn More: NestBox Official Website