Comparison Chart: Difference between revisions

From Pyra Wiki
Jump to navigation Jump to search
(ref for Pyra ship month)
(On a small screen, high resolutions without software changes make text unreadable, not to mention increased power draw, reduced performance etc. touchscreens: app-dependent. DVORAK: WTF? Of COURSE it is mappable, GNU/Linux: practicalities)
Line 20: Line 20:
|-
|-
|Screen resolution
|Screen resolution
| style="background-color: palegreen"| 1280x720 (720p)<ref name="pyra_spec" />
| 1280x720 (720p)<ref name="pyra_spec" />
| style="background-color: palegreen"| 1280x720 (720p)<ref name="gpdwin_spec" />
| 1280x720 (720p)<ref name="gpdwin_spec" />
| style="background-color: palegoldenrod"| 800x480<ref name="neo900_spec" />
| 800x480<ref name="neo900_spec" />
| style="background-color: palegoldenrod"| 800x480<ref name="pandora_spec" />
| 800x480<ref name="pandora_spec" />
|-
|-
|Touchscreen
|Touchscreen
| style="background-color: palegoldenrod"| Resistive (Stylus included)
| Resistive (Stylus included)
| style="background-color: peachpuff"| Capacitive, multitouch<ref name="gpdwin_spec" />
| Capacitive, multitouch<ref name="gpdwin_spec" />
| style="background-color: palegreen"| Dualtouch Resistive (Stylus included)<ref name="neo900_spec" />
| Dualtouch Resistive (Stylus included)<ref name="neo900_spec" />
| style="background-color: palegoldenrod"| Resistive (Stylus included)[http://pandorawiki.org/Display]
| Resistive (Stylus included)[http://pandorawiki.org/Display]
|-
|-
|Notification LEDs
|Notification LEDs
| style="background-color: palegreen"| 5 RGB LEDs, 2 on back, 1 under power button, 2 next to power button
| style="background-color: palegreen"| 5 RGB LEDs, 2 on back, 1 under power button, 2 next to power button
| style="background-color: pink"| Only power indicator
| style="background-color: peachpuff"| Only power indicator
| style="background-color: palegoldenrod"| 1 RGB LED on the face
| style="background-color: palegoldenrod"| 1 RGB LED on the face
| style="background-color: palegoldenrod"| 8, single-colour/binary
| style="background-color: palegreen"| 8, single-colour/binary
|-
|-
|Keyboard Layout (QWERTY)
|Keyboard Layout
|style="background-color: palegreen"| Good<ref>[https://youtu.be/d4t9Ys8wI6k?t=5m45s Video of the Prototype (at around 5:40)]</ref>
|style="background-color: palegreen"| Good<ref>[https://youtu.be/d4t9Ys8wI6k?t=5m45s Video of the Prototype (at around 5:40)]</ref>
<!-- pink should represent a missing feature, not something we dislike -->
<!-- pink should represent a missing feature, not something we dislike -->
Line 43: Line 43:
|style="background-color: palegoldenrod"| OK
|style="background-color: palegoldenrod"| OK
|style="background-color: palegoldenrod"| OK
|style="background-color: palegoldenrod"| OK
|-
|Keyboard Layout (Dvorak)
|style="background-color: pink"| Impossible
|style="background-color: palegoldenrod"| Mappable
|style="background-color: pink"| Impossible
|style="background-color: pink"| Impossible
|-
|-
| Keyboard Backlight
| Keyboard Backlight
Line 130: Line 124:
|Android compatibility
|Android compatibility
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
| style="background-color: palegoldenrod"| dualboot<ref name="gpdwin_comment" /> OR via emulator (such as Android SDK's QEMU variant)
| style="background-color: peachpuff"| dualboot<ref name="gpdwin_comment" /> OR via emulator (such as Android SDK's QEMU variant)
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
Line 140: Line 134:
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
|-
|-
|Desktop Linux compatibility
|Desktop GNU/Linux compatibility
| style="background-color: palegreen"| Native
| style="background-color: palegreen"| Native (note: not with proprietary x86 software)
| style="background-color: palegoldenrod"| dualboot<ref name="gpdwin_comment" /> OR via emulator
| style="background-color: palegoldenrod"| dualboot<ref name="gpdwin_comment" /> OR via virtual machine (like VirtualBox)
| style="background-color: palegreen"| Native
| style="background-color: palegoldenrod"| Native (note: not with proprietary x86 software), but internal storage too small for liberal use of apt-get
| style="background-color: palegreen"| Native
| style="background-color: palegoldenrod"| Native (note: not with proprietary x86 software), but internal storage too small for liberal use of apt-get
|-
|-
|CPU
|CPU
Line 173: Line 167:
|-
|-
|Wireless LAN
|Wireless LAN
| style="background-color: palegreen"| IEEE 802.11 a/b/g/n/ac[https://pyra-handheld.com/boards/threads/gpd-is-going-to-release-an-x86-console-palmtop-computer.76762/page-27#post-1370758]<ref name="pyra_spec" />
| style="background-color: palegreen"| IEEE 802.11 a/b/g/n<ref name="pyra_spec" />
| style="background-color: palegoldenrod"| IEEE 802.11 a/b/g/n<ref name="gpdwin_updates" />
| style="background-color: palegreen"| IEEE 802.11 a/b/g/n<ref name="gpdwin_updates" />
| style="background-color: palegoldenrod"| IEEE 802.11 a/b/g/n<ref name="neo900_spec" />
| style="background-color: palegreen"| IEEE 802.11 a/b/g/n<ref name="neo900_spec" />
| style="background-color: peachpuff"| IEEE 802.11 b/g<ref name="pandora_spec" />
| style="background-color: peachpuff"| IEEE 802.11 b/g<ref name="pandora_spec" />
|-
|-
Line 199: Line 193:
| style="background-color: palegreen"| [[Display]], [[CPU-Board]]
| style="background-color: palegreen"| [[Display]], [[CPU-Board]]
| style="background-color: pink"| No
| style="background-color: pink"| No
| style="background-color: palegreen"| Via USB in battery compartment
| style="background-color: palegoldenrod"| Via USB in battery compartment
| style="background-color: pink"| No
| style="background-color: pink"| No
|-
|-
Line 228: Line 222:
|USB
|USB
| style="background-color: palegreen"| 2x Type A 2.0, 1x Micro-B 3.0 (OTG), 1x Micro-B 1.1 (2.0?) (debug/charging)<ref name="pyra_spec" />
| style="background-color: palegreen"| 2x Type A 2.0, 1x Micro-B 3.0 (OTG), 1x Micro-B 1.1 (2.0?) (debug/charging)<ref name="pyra_spec" />
| style="background-color: peachpuff"| 1x Type A 2.0, 1x Micro-B 2.0<ref name="gpdwin_spec" />
| style="background-color: palegoldenrod"| 1x Type A 3.0, 1x Micro-B 2.0<ref name="gpdwin_spec" />
| style="background-color: peachpuff"| Micro-B 2.0 (OTG)<ref name="neo900_spec" />
| style="background-color: peachpuff"| Micro-B 2.0 (OTG)<ref name="neo900_spec" />
| style="background-color: peachpuff"| 1x Type A 2.0 (host, lacks 1.1 -- needs hub), 1x Micro-AB 2.0 OTG<ref name="pandora_spec" />
| style="background-color: peachpuff"| 1x Type A 2.0 (host, lacks 1.1 -- needs hub), 1x Micro-AB 2.0 OTG<ref name="pandora_spec" />

Revision as of 21:06, 15 April 2016

Pyra GPD Win Neo900 Pandora 1Ghz
Size ~140 x 84 x 29mm[1] 155 x 96 x 20mm[2] 111 x 60 x 20mm 140 x 83 x 27mm[3]
Screen size 5"[1] 5.5"[2] 3.5"[4] 4.3"[3]
Screen resolution 1280x720 (720p)[1] 1280x720 (720p)[2] 800x480[4] 800x480[3]
Touchscreen Resistive (Stylus included) Capacitive, multitouch[2] Dualtouch Resistive (Stylus included)[4] Resistive (Stylus included)[4]
Notification LEDs 5 RGB LEDs, 2 on back, 1 under power button, 2 next to power button Only power indicator 1 RGB LED on the face 8, single-colour/binary
Keyboard Layout Good[5] Problematic [6] OK OK
Keyboard Backlight Yes[1] TBD Yes[5] No
Keyboard keys 47[7] (including ESCAPE and F11 away from main section) 67[8] 38 43[9]
Face buttons 6[1] 4[2] 0 4[3]
Shoulder buttons 4[1] 4[2] 0 2[3]
Control buttons 6[7] 4[8] 4 4 (including power/lock slider)[9]
Analogue control Nubs, clickable[1] mini-joysticks[2] None Nubs[3]
Simultaneous use of mouse and all other controls Yes No (tentative)[2] n/a Yes
Volume control Wheel[1] (digital input device: software control[6]) Buttons[2] Buttons Wheel[3] (direct hardware control)
Vibration motor Yes No Yes No
Primary Operating System Debian GNU/Linux ARMhf (modified) Microsoft Windows 10[2] Debian GNU/Linux ARMhf (modified)[4] SuperZaxxon[10]
Free/libre OS (per DFSG) default non-free 3D graphics drivers No non-free 3D graphics drivers[11] non-free 3D graphics drivers, WiFi and Bluetooth
Free/libre OS (per DFSG) when running Linux non-free 3D graphics drivers Possibly (at least free 3D graphics drivers)[12] non-free 3D graphics drivers[11] non-free 3D graphics drivers, WiFi, Bluetooth
Windows x86 compatibility via WINE plus an x86 emulator (such as Exagear) Native x86_64 via WINE plus an x86 emulator (such as Exagear) via WINE plus an x86 emulator (such as Exagear)
Android compatibility dualboot OR via compatibility layer (like Shashlik) dualboot[13] OR via emulator (such as Android SDK's QEMU variant) dualboot OR via compatibility layer (like Shashlik) dualboot OR via compatibility layer (like Shashlik)
Android ARM compatibility dualboot OR via compatibility layer (like Shashlik) via emulator (such as Android SDK's QEMU variant) dualboot OR via compatibility layer (like Shashlik) dualboot OR via compatibility layer (like Shashlik)
Desktop GNU/Linux compatibility Native (note: not with proprietary x86 software) dualboot[13] OR via virtual machine (like VirtualBox) Native (note: not with proprietary x86 software), but internal storage too small for liberal use of apt-get Native (note: not with proprietary x86 software), but internal storage too small for liberal use of apt-get
CPU TI OMAP5432: 2x ARM Cortex-A15 1.5Ghz NEON SIMD[1] Intel Atom x5-Z8550: 4x Intel Cherry Trail x86_64 1.44Ghz SSE SIMD[13] TI OMAP3 DM3730: 1x ARM Cortex A8 @ 1.0 Ghz NEON SIMD[4] TI OMAP3 DM3730: 1x ARM Cortex A8 @ 1.0 Ghz NEON SIMD[3]
RAM 2 GB DDR3L-533 Dual-Channel[1][14] 4 GB LPDDR3-1600[2] Dual-Channel[13] 1 GB[4] 512 MB DDR1 @ 200Mhz[3]
GPU PowerVR SGX544-MP2[1][15] Intel HD Graphics 400 @ 200-600MHz, 12-core, shared memory[13][16] PowerVR SGX530 @ 200MHz SGX530 @ 200MHz[3]
Co-processor(s) TI C64+ DSP[1]

2x ARM Cortex M4 @ 200Mhz(IPU)[1] Vivante GC320 2D Accelerator[1]

None TI C64x+ DSP TI C64x DSP @ 800MHz[3]
Wireless LAN IEEE 802.11 a/b/g/n[1] IEEE 802.11 a/b/g/n[17] IEEE 802.11 a/b/g/n[4] IEEE 802.11 b/g[3]
Bluetooth Bluetooth 4.1[1] Bluetooth 4.1[17] Bluetooth 4.0[4] Bluetooth 2.0 + EDR[3]
Cell modem (SIM card slot) Optional: Built-in LTE Modem: 100Mbps download, 50Mbps upload[1] No Built-in LTE Modem: 100Mbps download, 50Mbps upload; OR: UMTS HSPA 14.4/5.76 Mbps with CDMA[4] No
Satellite navigation (GNSS) If with cell modem: GPS, cell tower assisted A-GPS, GLONASS[1] No GPS/GLONASS[4] No
Upgrades Display, CPU-Board No Via USB in battery compartment No
Battery 6000mAh[1], 4.2V? 6000mAh. ?V[2] 1320mAh? 4200mAh[3], 4.2V
Battery life (claimed, high power draw) 10 hours[18] 8 hours[2] ??? 10 hours[3]
Removable battery Yes No Yes, hotswap Yes
Video output Micro-HDMI (type D)[1] Mini-HDMI (type C)[2] Yes (???)[4] custom connector required, S-Video + RCA + Line-In &- Out[3]
USB 2x Type A 2.0, 1x Micro-B 3.0 (OTG), 1x Micro-B 1.1 (2.0?) (debug/charging)[1] 1x Type A 3.0, 1x Micro-B 2.0[2] Micro-B 2.0 (OTG)[4] 1x Type A 2.0 (host, lacks 1.1 -- needs hub), 1x Micro-AB 2.0 OTG[3]
eSATA via adapter using one USB port (of two) No No No
External memory card slots[19] 2x SDXC <=512GiB/Slot = 1TiB[1] 1x microSD <=200GiB[2] No 2x SDXC <=512GiB/Slot = 1TiB[3]
Internal memory card slots[19] 1x microSDXC <=200GiB[1] No 1x microSDXC <=200GiB No
Embedded storage 32 GB eMMC[1] 64 GB eMMC[2] 64 GB eMMC + 512MiB NAND[4] 512 MB NAND[3]
FM radio No No Rx & Tx[4] No
Camera No No VGA front & 5 MP rear[4] No
NFC No No Yes[4] No
Shipping month No earlier than July[20] October TBD n/a
Main countries of manufacture Germany, Greece China Germany (N900 from Finland) Germany, UK, China
  1. ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 Pyra specification
  2. ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 2.14 2.15 2.16 GPD Win specification
  3. ↑ 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 Pandora specification
  4. ↑ 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 4.11 4.12 4.13 4.14 4.15 Neo900 specification
  5. ↑ Video of the Prototype (at around 5:40)
  6. ↑ The GPD Win seems to be too large to reach the Center Keys see here: [1] Also the Keyboard is not Centered, and the Layout isn't optimal[2]
  7. ↑ 7.0 7.1 Pyra mockup image
  8. ↑ 8.0 8.1 GPD Win mockup image
  9. ↑ 9.0 9.1 Pandora photo
  10. ↑ derived from Ångström, a GNU/Linux variant for ARM[3]
  11. ↑ 11.0 11.1 Neo900 FAQ
  12. ↑ This depends on hardware details, particularly for the BIOS (currently non-free), WiFi and Bluetooth (non-free on the Pandora)
  13. ↑ 13.0 13.1 13.2 13.3 13.4 GPD Win comments & replies
  14. ↑ RAM Datasheet
  15. ↑ PowerVR SGX544-MP2 benchmarks
  16. ↑ Cherry Trail GPU benchmarks
  17. ↑ 17.0 17.1 GPD Win development updates
  18. ↑ No official statement
  19. ↑ 19.0 19.1 Using already available SD(XC)-Card sizes as the SDXC-Standard has an theoretical maximum of 2TiB/Card and those Cards simply don't exist yet.
  20. ↑ "PCB-wise, once we can approve everything to be working fine, it'll take about 2 - 3 months until the production can happen."
Retrieved from "http://pyra-handheld.com/wiki/index.php?title=Comparison_Chart&oldid=513"