HTC One M8s vs Sendo X

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.

• WeightX: 40 g lighterX: 120 g · One M8s: 160 g
• WidthX: 21.6 mm narrowerX: 49 mm · One M8s: 70.6 mm
• Screen diagonalX: 2.8 in smaller diagonalX: 2.2 in · One M8s: 5 in
• ChipsetQualcomm MSM8939 Snapdragon 615 (28 nm) / TI OMAP 5910One M8s: Qualcomm MSM8939 Snapdragon 615 (28 nm) · X: TI OMAP 5910
• Rear camera layoutDual / SingleOne M8s: Dual · X: Single
• DepthOne M8s: 13.4 mm thinnerOne M8s: 9.6 mm · X: 23 mm

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 M8s

   Height

   146.4 mm+36.4 mm versus X

   Width

   70.6 mm+21.6 mm versus X

   Depth

   9.6 mm

   Weight

   160 g

2. 2. X

   Height

   110 mm

   Width

   49 mm

   Depth

   23 mm+13.4 mm versus One M8s

   Weight

   120 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. One M8s 5 in · 16:9 About 68.9 cm² rectangular area
2. 2. X Screen geometry unavailable or conflicting

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.