Sharp Aquos V vs Xiaomi Mi A1

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.

• WeightMi A1: 8 g lighterMi A1: 165 g · Aquos V: 173 g
• Screen diagonalMi A1: 0.4 in smaller diagonalMi A1: 5.5 in · Aquos V: 5.9 in
• ChipsetQualcomm MSM8998 Snapdragon 835 (10 nm) / Qualcomm MSM8953 Snapdragon 625 (14 nm)Aquos V: Qualcomm MSM8998 Snapdragon 835 (10 nm) · Mi A1: Qualcomm MSM8953 Snapdragon 625 (14 nm)
• DepthMi A1: 1.7 mm thinnerMi A1: 7.3 mm · Aquos V: 9 mm
• Release year2019 / 2017Aquos V: 2019 · Mi A1: 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. Aquos V

   Height

   157 mm

   Width

   76 mm

   Depth

   9 mm+1.7 mm versus Mi A1

   Weight

   173 g

2. 2. Mi A1

   Height

   155.4 mm

   Width

   75.8 mm

   Depth

   7.3 mm

   Weight

   165 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. Aquos V 5.9 in · 18:9 About 89.8 cm² rectangular area
2. 2. Mi A1 5.5 in · 16:9 About 83.4 cm² rectangular area

Aquos V has approximately 7.7% more rectangular screen area than Mi A1.

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.