Mitac MIO 8860 vs Sharp Aquos Xx

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

  MIO 8860: 3.5 in smaller diagonal

  MIO 8860:

  2.2 in

  Aquos Xx:

  5.7 in

• Release year

  MIO 8860:

  2004

  Aquos Xx:

  2015

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. MIO 8860

   Height:

   Unknown

   Width:

   Unknown

   Depth:

   Unknown

   Weight:

   Unknown

   Unavailable dimensions are omitted from the drawing.

2. 2. Aquos Xx

   Height:

   146 mm

   Width:

   79 mm

   Depth:

   8.7 mm

   Weight:

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

At least two phones need compatible screen dimensions for a drawing.

1. 1. MIO 8860

   MIO 8860: Screen geometry unavailable or conflicting.

2. 2. Aquos Xx

   Screen diagonal:

   5.7 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

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

At least two unambiguous positive capacity values are needed for a chart. Original entries remain in the specifications.

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.