Coolpad NX1 vs Plum Axe LTE

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.

• Screen diagonal

  Axe LTE: 1 in smaller diagonal

  NX1:

  5 in

  Axe LTE:

  4 in

• Chipset

  NX1:

  Mediatek MT6735P (28 nm)

  Axe LTE:

  Mediatek MT6580 (28 nm)

• Release year

  NX1:

  2017

  Axe LTE:

  2015

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. NX1

   Height:

   Unknown

   Width:

   Unknown

   Depth:

   Unknown

   Weight:

   Unknown

   Unavailable dimensions are omitted from the drawing.

2. 2. Axe LTE

   Height:

   128.8 mm

   Width:

   58.2 mm

   Depth:

   8.9 mm

   Weight:

   124 g

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. NX1

   Screen diagonal:

   5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   68.9 cm²

2. 2. Axe LTE

   Screen diagonal:

   4 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   44.1 cm²

NX1 has approximately 56.3% more rectangular screen area than Axe LTE.

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.