Yezz LIV1 vs ZTE Maven

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

  Maven: 0.5 in smaller diagonal

  LIV1:

  5 in

  Maven:

  4.5 in

• Chipset

  LIV1:

  Unisoc SC7731E (28nm)

  Maven:

  Qualcomm MSM8916 Snapdragon 410 (28 nm)

• Height

  Maven: 3.6 mm shorter

  LIV1:

  138.5 mm

  Maven:

  134.9 mm

• Release year

  LIV1:

  2019

  Maven:

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

   Height:

   138.5 mm +3.6 mm versus Maven

   Width:

   65.8 mm

   Depth:

   9.5 mm

2. 2. Maven

   Height:

   134.9 mm

   Width:

   66 mm

   Depth:

   9.9 mm

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

   Screen diagonal:

   5 in

   Aspect ratio (height:width):

   18:9

   Approximate rectangular screen area:

   64.5 cm²

2. 2. Maven

   Screen diagonal:

   4.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   55.8 cm²

LIV1 has approximately 15.6% more rectangular screen area than Maven.

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.