vs
HTC J Butterfly HTC One S

HTC J Butterfly vs HTC One S

HTC J Butterfly

Reasons to consider the J Butterfly

4G, Google Android 4.1 (Jelly Bean)
Screen resolution Much higher resolution screen 1,920x1,080 vs 960x540 4x higher resolution screen
Screen PPI Much higher PPI screen 440 PPI vs 256 PPI More than 70% crisper display of text, images and video
Screen size Larger screen 5.0"" vs 4.3"" Around 40% larger screen
Network Faster max data speeds LTE (80 mbps) vs HSPA (42 mbps) Higher theoretical max data transfer speeds over cell networks (more than 40% faster)
HTC One S

Reasons to consider the One S

3.5G, Google Android 4.0 (Ice Cream Sandwich)
Size Smaller 65×131×8 mm vs 71×143×9 mm Around 30% smaller
Weight Lighter 119 g vs 140 g Around 20% lighter
Thickness Slightly thinner 8 mm vs 9 mm More than 10% thinner

Competitors

Common Pros and Cons

Compared to recent cellphones

Pros Cons
Bluetooth The latest bluetooth support
4.0
Thickness Thin
J Butterfly9 mm
One S8 mm
Camera resolution Capture very high resolution images
8 MP
Multi-touch Both support multi-touch
Intuitive gestures such as pinch to zoom
GPS Have assisted GPS
Assisted GPS
Processor Powerful processors, very snappy and responsive
Unknown, 1500 MHz
Touchscreen type Touch sensitive screens
Easy to use with your fingers
Wifi Both have fairly fast wifi support
802.11n (150 mbps)
Screen PPI Sharp display of text, images and video
J Butterfly440 PPI
One S256 PPI
Network Fast data transfer
J ButterflyLTE (80 mbps)
One SHSPA (42 mbps)
compatibility-score Works with many headphones
1.0
Internal storage More internal storage than most for storing music, photos and movies
16 GB
Numeric keypad Neither has a numeric keypad
Its often harder to dial numbers with a touch screen or keyboard

Compared to recent smartphones

Pros Cons

We're not aware of any interesting pros shared by these two products.

Keyboard Neither has a physical keyboard
No keyboard

Appearance

HTC One S HTC J Butterfly HTC J Butterfly HTC J Butterfly

Comments

Which phone do you like, and why?

Showing 0 comments