Oppo Reno vs Samsung Galaxy A30

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.

• Weight

  Galaxy A30: 20 g lighter

  Reno:

  185 g

  Galaxy A30:

  165 g

• Chipset

  Reno:

  Qualcomm SDM710 Snapdragon 710 (10 nm)

  Galaxy A30:

  Exynos 7904 Octa (14 nm)

• Depth

  Galaxy A30: 1.3 mm thinner

  Reno:

  9 mm

  Galaxy A30:

  7.7 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. Reno

   Height:

   156.6 mm

   Width:

   74.3 mm

   Depth:

   9 mm +1.3 mm versus Galaxy A30

2. 2. Galaxy A30

   Height:

   158.5 mm

   Width:

   74.7 mm

   Depth:

   7.7 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. Reno

   Screen diagonal:

   6.4 in

   Aspect ratio (height:width):

   19.5:9

   Approximate rectangular screen area:

   100.5 cm²

2. 2. Galaxy A30

   Screen diagonal:

   6.4 in

   Aspect ratio (height:width):

   19.5:9

   Approximate rectangular screen area:

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

No unambiguous storage/RAM pairings are recorded. See the original specifications below.

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.