What hashrate does a Snapdragon phone get on RandomX?

A Snapdragon phone often gets roughly 50–500 hashes per second (H/s) on RandomX with a native mining app, but that is only a broad guide, not a benchmark for your phone. Older or low-end models can fall below that range, while some newer high-end phones can exceed it. Browser mining can be much slower, so you should not use a native-app result to predict what you will get in a web page.

Why “Snapdragon” is not enough to give one number

Snapdragon is a family of chips, not one processor. An older Snapdragon 600-series phone and a recent Snapdragon 8-series phone have very different processing power, memory systems, and cooling.

RandomX is the calculation method Monero uses for mining. Your hashrate tells you how many mining calculations your device completes each second. For reference, 100 H/s means 100 calculations per second, and 1 kH/s means 1,000.

To make a useful comparison, you need:

• Your exact Snapdragon chip and phone model.
• Whether the test used a native app or a browser.
• The number of mining threads—separate workers running calculations.
• Whether the speed was measured briefly or after the phone warmed up.

Even two phones with the same chip can produce different sustained results.

Why RandomX is demanding on a phone

RandomX favors CPUs, the general-purpose processors inside phones and computers. But being CPU-friendly does not mean it runs equally well on every CPU.

Its fast mode uses a dataset of about 2,080 MB, alongside other working memory. Its light mode uses a 256 MB cache, but trades lower memory use for much slower calculations.

RandomX also benefits from about 2 MB of L3 cache per mining thread. L3 cache is a small, fast memory area close to the processor. Phone chips have limited shared cache, so adding more threads does not necessarily improve speed.

Your phone also has powerful cores and smaller, energy-saving cores. Using all of them can create more heat without giving you a worthwhile increase in hashrate.

What changes when you mine in a browser

A browser cannot necessarily use the same optimized execution methods as a native miner. Browser memory limits and restrictions on background activity can also reduce performance or stop mining altogether.

Check what a mining page actually measures. Some services mine another algorithm and pay you in XMR. An XMR payout does not prove that the displayed hashrate is RandomX hashrate.

Only compare results when the algorithm, software type, and measurement conditions match.

How to measure your phone fairly

Start with a small thread count and watch the speed for 15–30 minutes, rather than trusting the first minute.

Phones reduce processor speed when they get hot. This is called thermal throttling, and it can make sustained performance much lower than an initial peak.

Keep the phone uncovered and ventilated. Stop if it becomes uncomfortably hot or shows a temperature warning. Avoid unknown mining apps, especially anything asking for your wallet’s recovery phrase.

The bottom line

Use 50–500 H/s as a rough native-app starting range, not a promised Snapdragon result. Your exact phone, mining software, and warmed-up speed matter most; for browser mining, measure the actual page rather than relying on native benchmarks.