Motorola Moto E3 vs Xolo Cube 5.0

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.

• Memory variants

  At 8 GB storage

  Moto E3:

  1 GB RAM

  Cube 5.0:

  2 GB RAM

• Chipset

  Moto E3:

  Mediatek MT6735P (28 nm)

  Cube 5.0:

  Mediatek MT6582M (28 nm)

• Depth

  Cube 5.0: 1.6 mm thinner

  Moto E3:

  8.5 mm

  Cube 5.0:

  6.9 mm

• Release year

  Moto E3:

  2016

  Cube 5.0:

  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. Moto E3

   Height:

   143.8 mm

   Width:

   71.6 mm

   Depth:

   8.5 mm +1.6 mm versus Cube 5.0

   Weight:

   140.6 g

2. 2. Cube 5.0

   Height:

   143 mm

   Width:

   71 mm

   Depth:

   6.9 mm

   Weight:

   Unknown

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 E3

   Screen diagonal:

   5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   68.9 cm²

2. 2. Cube 5.0

   Screen diagonal:

   5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

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