Eten M550 vs Plum Axe

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.

• WeightAxe: 67 g lighterAxe: 98 g · M550: 165 g
• WidthM550: 2.6 mm narrowerM550: 61 mm · Axe: 63.6 mm
• Screen diagonalM550: 1.2 in smaller diagonalM550: 2.8 in · Axe: 4 in
• DepthAxe: 11.6 mm thinnerAxe: 10.4 mm · M550: 22 mm
• HeightM550: 10 mm shorterM550: 112 mm · Axe: 122 mm
• Release year2006 / 2012M550: 2006 · Axe: 2012

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

   Height

   112 mm

   Width

   61 mm

   Depth

   22 mm+11.6 mm versus Axe

   Weight

   165 g

2. 2. Axe

   Height

   122 mm+10 mm versus M550

   Width

   63.6 mm+2.6 mm versus M550

   Depth

   10.4 mm

   Weight

   98 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. M550 2.8 in · 4:3 About 24.3 cm² rectangular area
2. 2. Axe 4 in · 5:3 About 45.5 cm² rectangular area

Axe has approximately 87.6% more rectangular screen area than M550.

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.

No unambiguous storage/RAM pairings are recorded. See the original specifications below.

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.