alcatel One Touch Fire vs Sony Xperia E

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

  One Touch Fire: 7.7 g lighter

  One Touch Fire:

  108 g

  Xperia E:

  115.7 g

• Depth

  Xperia E: 1.2 mm thinner

  One Touch Fire:

  12.2 mm

  Xperia E:

  11 mm

• Release year

  One Touch Fire:

  2013

  Xperia E:

  2012

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. One Touch Fire

   Height:

   115 mm

   Width:

   62.3 mm

   Depth:

   12.2 mm +1.2 mm versus Xperia E

2. 2. Xperia E

   Height:

   113.5 mm

   Width:

   61.8 mm

   Depth:

   11 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. One Touch Fire

   Screen diagonal:

   3.5 in

   Aspect ratio (height:width):

   3:2

   Approximate rectangular screen area:

   36.5 cm²

2. 2. Xperia E

   Screen diagonal:

   3.5 in

   Aspect ratio (height:width):

   3:2

   Approximate rectangular screen area:

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