Motorola Moto E5 Play Go vs Plum Phantom

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

  Moto E5 Play Go:

  Qualcomm MSM8917 Snapdragon 425 (28 nm)

  Phantom:

  Mediatek MT6580A (28 nm)

• Release year

  Moto E5 Play Go:

  2018

  Phantom:

  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. Moto E5 Play Go

   Height:

   Unknown

   Width:

   Unknown

   Depth:

   Unknown

   Weight:

   Unknown

   Unavailable dimensions are omitted from the drawing.

2. 2. Phantom

   Height:

   165.5 mm

   Width:

   84.2 mm

   Depth:

   8.8 mm

   Weight:

   138 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. Moto E5 Play Go

   Screen diagonal:

   5.84 in

   Aspect ratio (height:width):

   18:9

   Approximate rectangular screen area:

   88 cm²

2. 2. Phantom

   Screen diagonal:

   6 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   99.2 cm²

Phantom has approximately 12.8% more rectangular screen area than Moto E5 Play Go.

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.