HTC One S vs Plum Axe 4

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.

• Display technologyOLED versus LCDOne S: OLED · Axe 4: LCD
• WeightAxe 4: 12.5 g lighterAxe 4: 107 g · One S: 119.5 g
• WidthAxe 4: 1 mm narrowerAxe 4: 64 mm · One S: 65 mm
• Screen diagonalAxe 4: 0.3 in smaller diagonalAxe 4: 4 in · One S: 4.3 in
• ChipsetQualcomm MSM8290 / Spreadtrum SC7731COne S: Qualcomm MSM8290 · Axe 4: Spreadtrum SC7731C
• DepthOne S: 2.1 mm thinnerOne S: 7.8 mm · Axe 4: 9.9 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 S

   Height

   130.9 mm+6.9 mm versus Axe 4

   Width

   65 mm+1 mm versus Axe 4

   Depth

   7.8 mm

   Weight

   119.5 g

2. 2. Axe 4

   Height

   124 mm

   Width

   64 mm

   Depth

   9.9 mm+2.1 mm versus One S

   Weight

   107 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. One S 4.3 in · 16:9 About 51 cm² rectangular area
2. 2. Axe 4 4 in · 5:3 About 45.5 cm² rectangular area

One S has approximately 11.9% more rectangular screen area than Axe 4.

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.