Acer beTouch E101 vs Philips D908

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.

• Weight

  beTouch E101: 11 g lighter

  beTouch E101:

  118 g

  D908:

  129 g

• Depth

  beTouch E101: 2.1 mm thinner

  beTouch E101:

  12.8 mm

  D908:

  14.9 mm

• Height

  D908: 2 mm shorter

  beTouch E101:

  113 mm

  D908:

  111 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. beTouch E101

   Height:

   113 mm +2 mm versus D908

   Width:

   56 mm

   Depth:

   12.8 mm

2. 2. D908

   Height:

   111 mm

   Width:

   56.2 mm

   Depth:

   14.9 mm +2.1 mm versus beTouch E101

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. beTouch E101

   Screen diagonal:

   3.2 in

   Aspect ratio (height:width):

   5:3

   Approximate rectangular screen area:

   29.1 cm²

2. 2. D908

   Screen diagonal:

   3.2 in

   Aspect ratio (height:width):

   5:3

   Approximate rectangular screen area:

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

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.