Palm Treo 500v vs Sharp R1S

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.

• Screen diagonal

  Treo 500v: 3.1 in smaller diagonal

  Treo 500v:

  2.4 in

  R1S:

  5.5 in

• Rear camera layout

  Treo 500v:

  Single

  R1S:

  Dual

• Release year

  Treo 500v:

  2007

  R1S:

  2018

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. Treo 500v

   Height:

   110 mm

   Width:

   61.5 mm

   Depth:

   16.5 mm

   Weight:

   120 g

2. 2. R1S

   Height:

   Unknown

   Width:

   Unknown

   Depth:

   Unknown

   Weight:

   Unknown

   Unavailable dimensions are omitted from the drawing.

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. Treo 500v

   Screen diagonal:

   2.4 in

   Aspect ratio (height:width):

   4:3

   Approximate rectangular screen area:

   17.8 cm²

2. 2. R1S

   Screen diagonal:

   5.5 in

   Aspect ratio (height:width):

   16:9

   Approximate rectangular screen area:

   83.4 cm²

R1S has approximately 367.5% more rectangular screen area than Treo 500v.

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.