ZTE Axon Pro vs ZTE nubia M2 Play

Key differences

Calculated from recorded specifications using minimum difference thresholds. These are differences, not an overall ranking. For three phones, numeric highlights compare the two extremes.

• Chipset

  Axon Pro:

  Qualcomm MSM8994 Snapdragon 810 (20 nm)

  nubia M2 Play:

  Qualcomm MSM8940 Snapdragon 435 (28 nm)

• Rear camera layout

  Axon Pro:

  Dual

  nubia M2 Play:

  Single

• Release year

  Axon Pro:

  2015

  nubia M2 Play:

  2017

Relative size, not calibrated actual size. Front and side outlines share one scale and a bottom baseline. Generic outlines use recorded body dimensions, excluding camera bumps.

1. 1. Axon Pro

   Height:

   153.9 mm

   Width:

   73.7 mm

   Depth:

   9.4 mm

   Weight:

   172.9 g

2. 2. nubia M2 Play

   Height:

   Unknown

   Width:

   Unknown

   Depth:

   Unknown

   Weight:

   Unknown

   Unavailable dimensions are omitted from the drawing.

Screen size

Approximate rectangular screens calculated from recorded diagonal and aspect ratio at one relative scale. Rounded corners and cutouts are not subtracted. These are not phone outlines or calibrated actual sizes.

1. 1. Axon Pro

   Screen diagonal:

   5.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   83.4 cm²

2. 2. nubia M2 Play

   Screen diagonal:

   5.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   83.4 cm²

Memory variants

Each row compares the same storage capacity. Cells show recorded RAM alternatives, not combined maxima. Not recorded does not mean unavailable in every market.

Practical features

Explicit Yes and No values are shown directly. Qualified or regional records retain their details. Unknown means the record is missing.

Battery capacity

Capacity is not battery life. No endurance test is implied.

Open a section for more detail. On narrow screens, swipe sideways or use Left/Right arrow keys while the table is focused. Unknown means missing data, not No. Recorded zero values are shown as recorded.