LG Optimus LTE SU640 vs Meizu MX

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.

• Width

  MX: 4.6 mm narrower

  Optimus LTE SU640:

  67.9 mm

  MX:

  63.3 mm

• Screen diagonal

  MX: 0.5 in smaller diagonal

  Optimus LTE SU640:

  4.5 in

  MX:

  4 in

• Height

  MX: 11.6 mm shorter

  Optimus LTE SU640:

  132.9 mm

  MX:

  121.3 mm

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. Optimus LTE SU640

   Height:

   132.9 mm +11.6 mm versus MX

   Width:

   67.9 mm +4.6 mm versus MX

   Depth:

   10.4 mm

2. 2. MX

   Height:

   121.3 mm

   Width:

   63.3 mm

   Depth:

   10.3 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. Optimus LTE SU640

   Screen diagonal:

   4.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   55.8 cm²

2. 2. MX

   Screen diagonal:

   4 in

   Aspect ratio (height:width):

   3:2

   Approximate rectangular screen area:

   47.6 cm²

Optimus LTE SU640 has approximately 17.2% more rectangular screen area than MX.

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.