LG Vu 3 F300L vs TECNO Camon CX

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.

• Screen diagonal

  Vu 3 F300L: 0.3 in smaller diagonal

  Vu 3 F300L:

  5.2 in

  Camon CX:

  5.5 in

• Chipset

  Vu 3 F300L:

  Qualcomm MSM8974 Snapdragon 800 (28 nm)

  Camon CX:

  Mediatek MT6750T (28 nm)

• Release year

  Vu 3 F300L:

  2013

  Camon CX:

  2017

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. Vu 3 F300L

   Height:

   Unknown

   Width:

   Unknown

   Depth:

   Unknown

   Weight:

   Unknown

   Unavailable dimensions are omitted from the drawing.

2. 2. Camon CX

   Height:

   152.8 mm

   Width:

   75.8 mm

   Depth:

   5.6 mm

   Weight:

   150 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. Vu 3 F300L

   Screen diagonal:

   5.2 in

   Aspect ratio (height:width):

   4:3

   Approximate rectangular screen area:

   83.7 cm²

2. 2. Camon CX

   Screen diagonal:

   5.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

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