Nokia C1 vs Parla Sonic 3.5

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.

• WeightSonic 3.5: 50 g lighterSonic 3.5: 105 g · C1: 155 g
• WidthSonic 3.5: 9.2 mm narrowerSonic 3.5: 62.2 mm · C1: 71.4 mm
• Screen diagonalSonic 3.5: 1.95 in smaller diagonalSonic 3.5: 3.5 in · C1: 5.45 in
• DepthC1: 2.9 mm thinnerC1: 8.7 mm · Sonic 3.5: 11.6 mm
• HeightSonic 3.5: 31.6 mm shorterSonic 3.5: 116 mm · C1: 147.6 mm
• Release year2019 / 2013C1: 2019 · Sonic 3.5: 2013

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

   Height

   147.6 mm+31.6 mm versus Sonic 3.5

   Width

   71.4 mm+9.2 mm versus Sonic 3.5

   Depth

   8.7 mm

   Weight

   155 g

2. 2. Sonic 3.5

   Height

   116 mm

   Width

   62.2 mm

   Depth

   11.6 mm+2.9 mm versus C1

   Weight

   105 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. C1 5.45 in · 18:9 About 76.7 cm² rectangular area
2. 2. Sonic 3.5 3.5 in · 3:2 About 36.5 cm² rectangular area

C1 has approximately 110.1% more rectangular screen area than Sonic 3.5.

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.