Sensor and Performance

The Fantech Aria II is equipped with the PixArt PAW3395. According to specifications, the 3395 is capable of up to 26,000 CPI, as well as a maximum tracking speed of 650 IPS, which equals 16.51 m/s. Out of the box, four pre-defined CPI steps are available: 400, 800, 1600, and 3200.

All testing was done on the latest firmware (3.10/2.00). As such, results obtained on earlier firmware versions may differ from those presented hereafter.

CPI Accuracy

I've restricted my testing to the four most common CPI steps, which are 400, 800, 1600, and 3200. As you can see, there is no deviation at all, which is a perfect result.

Motion Delay

Testing is restricted to 2.4 GHz mode as Bluetooth is not suitable for non-casual gaming applications.

Wired testing

First, I'm looking at two xCounts plots—generated at 1600 and 26,000 CPI—to quickly gauge whether there is any smoothing, which would be indicated by any visible "kinks." Neither plot shows any kinks, strongly suggesting there not being any smoothing across the entire CPI range.


The Aria II also allows enabling MotionSync, which effectively synchronizes SPI reads with USB polls, resulting in very low SPI timing jitter as seen above.



In order to determine motion delay, I'm looking at xSum plots generated at 1600 and 26,000 CPI, both without (first row) and with (second row) MotionSync. The line further to the left denotes the sensor with less motion delay. Without MotionSync, there is no motion delay differential at 1600 and 26,000 CPI. Enabling MotionSync adds a bit more than 0.5 ms worth of motion delay.

Wireless testing

Unlike in wired mode, which defaults to corded mode, the sensor run mode can be modified in wireless mode. LP mode (first plot) displays slightly higher SPI timing jitter than HP mode (second plot).


Upon enabling MotionSync, SPI timing is tightened to a similar degree in both instances.



In LP Mode and without MotionSync (first row, first plot), a motion delay differential of a bit more than 1 ms can be measured, whereas in HP mode without MotionSync (first row, second plot), a motion delay differential of a bit more than 0.5 ms is present. Enabling MotionSync adds a bit more than 0.5 ms worth of motion delay for both LP and HP mode.

Speed-related Accuracy Variance (SRAV)

As you can see from the plot, no displacement between the two cursor paths can be observed, which confirms that SRAV is very low.

Perfect Control Speed

I've only managed to hit a measly 5.5 m/s, which is within the proclaimed PCS range and causes no observable sensor malfunction.

Polling Rate Stability

Wired testing


All the available polling rates (125, 250, 500, or 1000 Hz) are fully stable.

Wireless testing
For wired mice, polling rate stability merely concerns the wired connection between the mouse (SPI communication) and USB. For wireless mice, another device that needs to be kept in sync between the first two is added to the mix: the wireless dongle/wireless receiver. I'm unable to measure all stages of the entire end-to-end signal chain individually, so testing polling-rate stability at the endpoint (the USB) has to suffice here.


First, I'm testing whether SPI, wireless, and USB communication are synchronized. Any of these being out of sync would be indicated by at least one 2 ms report, which would be the result of any desynchronization drift accumulated over time. I'm unable to detect any periodic off-period polls that would be indicative of a desynchronization drift.



Second, I'm testing the general polling-rate stability of the individual polling rates in wireless mode. Running the Aria II at a lower polling rate can have the benefit of extending battery life. Initially, all polling rates display periodic off-period polls, though this ceases quickly, and polling becomes stable.

Paint Test

As you can see, no issues with angle snapping can be observed. No jitter is visible at 1600 CPI. 26,000 CPI with ripple control disabled (second row) shows major jitter, which is moderately lessened by enabling ripple control (third row). Lastly, there is no sensor lens movement.

Lift-off Distance

The Aria II offers two pre-defined LOD levels. At the "1 mm" setting, the sensor does not track at a height of one DVD (<1.2 mm). Using the "2 mm" setting, the sensor does track at a height of one DVD (1.2 mm<x<2.4 mm, with x being LOD height), but not at a height of two DVDs. Keep in mind that LOD may vary slightly depending on the mousing surface (pad) it is being used on.

Click Latency

In wired mode and using a debounce time of 0 ms, click latency has been measured to be 1.5 ms, with standard deviation being 0.24 ms. Using a debounce time of 1 ms, click latency has been measured to be 2.6 ms, with standard deviation being 0.24 ms.

In wireless mode and using a debounce time of 0 ms, click latency has been measured to be 2.6 ms, with standard deviation being 0.27 ms. Using a debounce time of 1 ms, click latency has been measured to be 3.4 ms, with standard deviation being 0.20 ms.

Though debounce time generally scales linearly, some values show higher variance, resulting in non-linear scaling.

The main button switches were measured to be running at 3.35 V. I'm not aware of the voltage specifications of the used Huano switches, but I consider it very likely that these are running within specifications.