HTC Primo vs i-mate SPJAS

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.

• WidthSPJAS: 10.7 mm narrowerSPJAS: 49 mm · Primo: 59.7 mm
• Screen diagonalSPJAS: 1.5 in smaller diagonalSPJAS: 2.2 in · Primo: 3.7 in
• DepthPrimo: 5.6 mm thinnerPrimo: 9.2 mm · SPJAS: 14.8 mm
• HeightSPJAS: 7.9 mm shorterSPJAS: 112.4 mm · Primo: 120.3 mm
• Release year2012 / 2006Primo: 2012 · SPJAS: 2006

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

   Height

   120.3 mm+7.9 mm versus SPJAS

   Width

   59.7 mm+10.7 mm versus SPJAS

   Depth

   9.2 mm

   Weight

   115 g

2. 2. SPJAS

   Height

   112.4 mm

   Width

   49 mm

   Depth

   14.8 mm+5.6 mm versus Primo

   Weight

   115 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. Primo 3.7 in · 5:3 About 39 cm² rectangular area
2. 2. SPJAS 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.

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.