Lenovo A820 vs Plum Sync

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.

• WeightSync: 41 g lighterSync: 110 g · A820: 151 g
• WidthSync: 5.8 mm narrowerSync: 62.4 mm · A820: 68.2 mm
• Screen diagonalSync: 1 in smaller diagonalSync: 3.5 in · A820: 4.5 in
• ChipsetMediatek MT6589 (28 nm) / Mediatek MT6572 (28 nm)A820: Mediatek MT6589 (28 nm) · Sync: Mediatek MT6572 (28 nm)
• DepthA820: 1.6 mm thinnerA820: 9.9 mm · Sync: 11.5 mm
• HeightSync: 17 mm shorterSync: 118 mm · A820: 135 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. A820

   Height

   135 mm+17 mm versus Sync

   Width

   68.2 mm+5.8 mm versus Sync

   Depth

   9.9 mm

   Weight

   151 g

2. 2. Sync

   Height

   118 mm

   Width

   62.4 mm

   Depth

   11.5 mm+1.6 mm versus A820

   Weight

   110 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. A820 4.5 in · 16:9 About 55.8 cm² rectangular area
2. 2. Sync 3.5 in · 3:2 About 36.5 cm² rectangular area

A820 has approximately 53% more rectangular screen area than Sync.

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.