Celkon A22 vs QMobile Linq X300

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

  Linq X300: 2.4 mm narrower

  A22:

  67 mm

  Linq X300:

  64.6 mm

• Depth

  Linq X300: 0.9 mm thinner

  A22:

  9.9 mm

  Linq X300:

  9 mm

• Height

  A22: 5 mm shorter

  A22:

  131 mm

  Linq X300:

  136 mm

• Release year

  A22:

  2012

  Linq X300:

  2014

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

   Height:

   131 mm

   Width:

   67 mm +2.4 mm versus Linq X300

   Depth:

   9.9 mm +0.9 mm versus Linq X300

   Weight:

   145 g

2. 2. Linq X300

   Height:

   136 mm +5 mm versus A22

   Width:

   64.6 mm

   Depth:

   9 mm

   Weight:

   Unknown

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

   Screen diagonal:

   4.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   55.8 cm²

2. 2. Linq X300

   Screen diagonal:

   4.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

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

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.