Lava Flair E2 vs ZTE Blade Force

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.

• WidthFlair E2: 17 mm narrowerFlair E2: 61 mm · Blade Force: 78 mm
• Screen diagonalFlair E2: 2 in smaller diagonalFlair E2: 3.5 in · Blade Force: 5.5 in
• DepthBlade Force: 2.9 mm thinnerBlade Force: 9.1 mm · Flair E2: 12 mm
• HeightFlair E2: 43 mm shorterFlair E2: 113 mm · Blade Force: 156 mm
• Release year2015 / 2017Flair E2: 2015 · Blade Force: 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. Flair E2

   Height

   113 mm

   Width

   61 mm

   Depth

   12 mm+2.9 mm versus Blade Force

   Weight

   Unknown

2. 2. Blade Force

   Height

   156 mm+43 mm versus Flair E2

   Width

   78 mm+17 mm versus Flair E2

   Depth

   9.1 mm

   Weight

   170.1 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. Flair E2 3.5 in · 3:2 About 36.5 cm² rectangular area
2. 2. Blade Force 5.5 in · 16:9 About 83.4 cm² rectangular area

Blade Force has approximately 128.6% more rectangular screen area than Flair E2.

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.