Comparison Chart: Difference between revisions - Pyra Wiki

(An Small attemp to clean this thing up [https://www.pyra-handheld.com/wiki/index.php?title=Talk:Comparison_Chart (See the Discussion)])
(Moving Detailed LED description to references; Cleaning things up here and there; Add the posibility for 4Gb of ram on the Pyra;)
Line 88: Line 88:
|-
|-
|Touchscreen
|Touchscreen
| style="background-color: palegreen"| Dualtouch Resistive (Stylus included)<!-- uses same part as Neo900 -->
<!-- Touchscreen Types are too subjective to give a rating. Sure resistive is better for Desktop usage, but win10 is optimized for Cpacitive Touchscreens -->
| style="background-color: peachpuff"| Capacitive, multitouch<ref name="gpdwin_spec" />
| Dualtouch Resistive (Stylus included)<!-- uses same part as Neo900 -->
| style="background-color: palegreen"| Dualtouch Resistive (Stylus included)<ref name="neo900_spec" />
| Capacitive, multitouch<ref name="gpdwin_spec" />
| style="background-color: palegoldenrod"| Resistive (Stylus included)[http://pandorawiki.org/Display]
| Dualtouch Resistive (Stylus included)<ref name="neo900_spec" />
| Resistive (Stylus included)[http://pandorawiki.org/Display]
|-
|-
|Notification LEDs
|Notification LEDs
| style="background-color: palegreen"| Total 5 RGB LEDs:<br>2 on back<br>1 under power button<br>2 next to power button
| style="background-color: palegreen"| Total 5 RGB LEDs<ref><br>2 on back<br>1 under power button<br>2 next to power button</ref>
| style="background-color: pink"| Only power indicator
| style="background-color: pink"| Only power indicator
| style="background-color: palegreen"| Total 5 RGB LEDs:<br>1 on the display<br>2 on the sides<br>1 on left side of keyboard (not visible when closed)<br>1 on the rear above the camera (between the flash LEDs; visible only when camera open)
| style="background-color: palegreen"| Total 5 RGB LEDs<ref><br>1 on the display<br>2 on the sides<br>1 on left side of keyboard (not visible when closed)<br>1 on the rear above the camera (between the flash LEDs; visible only when camera open)</ref>
| style="background-color: palegoldenrod"| 8 single-colour/binary LEDs
| style="background-color: palegoldenrod"| 6 Non-RGB LEDs<ref>All are on the Hinge</ref> <!-- The 2 next to the Power LED aren't populated and the Driver transistor is missing -->
|-
|-
|Keyboard Layout (QWERTY)
|Keyboard Layout (QWERTY)
|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 -->
|style="background-color: peachpuff"| Problematic <ref name="gpdwin_issue" />
|style="background-color: peachpuff"| Problematic <ref name="gpdwin_issue" />
|style="background-color: palegoldenrod"| OK
|style="background-color: palegoldenrod"| OK
|style="background-color: palegoldenrod"| OK
|style="background-color: palegoldenrod"| OK
|-
|-
<!--
|Keyboard Layout (Dvorak)
|Keyboard Layout (Dvorak)
|style="background-color: pink"| Impossible
|style="background-color: pink"| Impossible
Line 111: Line 113:
|style="background-color: pink"| Impossible
|style="background-color: pink"| Impossible
|style="background-color: pink"| Impossible
|style="background-color: pink"| Impossible
Removing this as an Dvorak Keyboard Layout on an Thumb-typing Device isn't an huge advantage and would make this Table too long/Detailed -->
|-
|-
| Keyboard Backlight
| Keyboard Backlight
| style="background-color: palegreen"| Yes<ref name="pyra_spec" />
| style="background-color: palegreen"| Yes<ref name="pyra_spec" />
| style="background-color: pink"| No
| style="background-color: pink"| No
| style="background-color: palegreen"| Yes (6 RGB LEDs)[http://neo900.org/news/xmas-update]
| style="background-color: palegreen"| Yes <ref>Via 6 RGB LEDs[http://neo900.org/news/xmas-update]</ref>
| style="background-color: pink"| No
| style="background-color: pink"| No
|-
|-
Line 183: Line 188:
| style="background-color: palegoldenrod"| non-free 3D graphics drivers<ref name="neo900_faq" />
| style="background-color: palegoldenrod"| non-free 3D graphics drivers<ref name="neo900_faq" />
| style="background-color: peachpuff"| non-free 3D graphics drivers, WiFi, Bluetooth
| style="background-color: peachpuff"| non-free 3D graphics drivers, WiFi, Bluetooth
|-
|Hardware Documentation
| style="background-color: palegoldenrod"| Planned
| style="background-color: pink"| No
| style="background-color: palegreen"| [http://neo900.org/resources Yes]
| style="background-color: palegreen"| Yes
|-
|-
|Windows x86 compatibility <!-- The x86 is IMPORTANT: there are non-x86 MS Windows versions, which are essentially useless for most wanting "Windows compatibility" -->
|Windows x86 compatibility <!-- The x86 is IMPORTANT: there are non-x86 MS Windows versions, which are essentially useless for most wanting "Windows compatibility" -->
Line 202: Line 201:
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
| style="background-color: palegoldenrod"| dualboot OR via compatibility layer (like Shashlik)
|-
|-
|Android ARM compatibility <!-- The ARM is IMPORTANT: there are non-ARM Android versions, which would not run most high-performance ARM programs, which use native ARM code -->
|Android ARM compatibility <ref>The ARM is IMPORTANT: there are non-ARM Android versions, which would not run most high-performance ARM programs, which use native ARM code </ref>
| 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: peachpuff"| via emulator (such as Android SDK's QEMU variant)
| style="background-color: peachpuff"| via emulator (such as Android SDK's QEMU variant)
Line 221: Line 220:
|-
|-
|RAM
|RAM
| style="background-color: palegoldenrod"| 2 GB [[RAM|DDR3L]]-533 Dual-Channel<ref name="pyra_spec" /><ref>[http://www.intelligentmemory.com/fileadmin/pdf-datasheets/IM4G08-16D3FABG1.2-0821.pdf RAM Datasheet]</ref>
| 2 GB [[RAM|DDR3L]]-533 Dual-Channel<ref name="pyra_spec" /><ref>[http://www.intelligentmemory.com/fileadmin/pdf-datasheets/IM4G08-16D3FABG1.2-0821.pdf RAM Datasheet]</ref>; Maybe 4Gb[https://pyra-handheld.com/boards/threads/finalizing-everything.77289/]
| style="background-color: palegreen"| 4 GB LPDDR3-1600<ref name="gpdwin_spec" /> Dual-Channel<ref name="gpdwin_comment" />
| style="background-color: palegreen"| 4 GB LPDDR3-1600<ref name="gpdwin_spec" /> Dual-Channel<ref name="gpdwin_comment" />
<!-- Not sure if really LPDDR3-1600 -->
| style="background-color: peachpuff"| 1 GB<ref name="neo900_spec" />
| style="background-color: peachpuff"| 1 GB<ref name="neo900_spec" />
| style="background-color: peachpuff"| 512 MB DDR1 @ 200Mhz<ref name="pandora_spec" />
| style="background-color: peachpuff"| 512 MB DDR1 @ 200Mhz<ref name="pandora_spec" />
Line 353: Line 353:
| style="background-color: palegreen"| Yes<ref name="neo900_spec" /><ref>[http://neo900.org/stuff/papers/nfc-draft.pdf Neo900 NFC info]</ref>
| style="background-color: palegreen"| Yes<ref name="neo900_spec" /><ref>[http://neo900.org/stuff/papers/nfc-draft.pdf Neo900 NFC info]</ref>
| style="background-color: pink"| No
| style="background-color: pink"| No
|-
|Hardware Documentation
| style="background-color: palegoldenrod"| Planned
| style="background-color: pink"| No
| style="background-color: palegreen"| [http://neo900.org/resources Yes]
| style="background-color: palegreen"| Yes
|-
|-
| Shipping month
| Shipping month

Revision as of 18:03, 23 April 2016


Pyra GPD Win Neo900 Pandora 1Ghz
Price (EUR) ~500-600 ~265 (crowdfund)[1] or ~445 (retail) ~1200[2] n/a(EOL)
Price (USD) ~565-677 ~300 (crowdfund)[1] or ~500 (retail) ~1350[2] n/a(EOL)
Size ~140 x 84 x 29mm[3] 155 x 96 x 20mm[1] 111 x 60 x 20mm 140 x 83 x 27mm[4]
Screen size 5"[3] 5.5"[1] 3.5"[5] 4.3"[4]
Screen resolution 1280x720 (720p)[3] 1280x720 (720p)[1] 800x480[5] 800x480[4]
Touchscreen Dualtouch Resistive (Stylus included) Capacitive, multitouch[1] Dualtouch Resistive (Stylus included)[5] Resistive (Stylus included)[5]
Notification LEDs Total 5 RGB LEDs[6] Only power indicator Total 5 RGB LEDs[7] 6 Non-RGB LEDs[8]
Keyboard Layout (QWERTY) Good[9] Problematic [10] OK OK
Keyboard Backlight Yes[3] No Yes [11] No
Keyboard keys 47[12] (including ESCAPE and F11 away from main section) 67[13] 38 43[14]
Face buttons 6[3] 4[1] 0 4[4]
Shoulder buttons 4[3] 4[1] 0 2[4]
Control buttons 6[12] 4[13] 4 + slider & camera cover 3 + slider[14]
Analogue control Nubs, clickable[3] mini-joysticks[1] None Nubs[4]
Simultaneous use of mouse and all other controls Yes No (tentative)[1] n/a Yes
Volume control Wheel[3] (digital input device: software control[6]) Buttons[1] Buttons Wheel[4] (direct hardware control)
Vibration motor Yes No Yes No
Primary Operating System Debian GNU/Linux ARMhf (modified) Microsoft Windows 10[1] Devuan GNU/Linux (modified) SuperZaxxon[15]
Free/libre OS (per DFSG) default non-free 3D graphics drivers No non-free 3D graphics drivers[16] 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)[17] non-free 3D graphics drivers[16] 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[18] 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 [19] 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 dualboot[18] OR via emulator Native Native
CPU TI OMAP5432: 2x ARM Cortex-A15 1.5Ghz; NEON SIMD[3] Intel Atom x5-Z8550: 4x Intel Cherry Trail x86_64 1.44Ghz; SSE SIMD[18] TI OMAP3 DM3730: 1x ARM Cortex A8 @ 1.0 Ghz; NEON SIMD[5] TI OMAP3 DM3730: 1x ARM Cortex A8 @ 1.0 Ghz; NEON SIMD[4]
RAM 2 GB DDR3L-533 Dual-Channel[3][20]; Maybe 4Gb[7] 4 GB LPDDR3-1600[1] Dual-Channel[18] 1 GB[5] 512 MB DDR1 @ 200Mhz[4]
GPU PowerVR SGX544-MP2[3][21] Intel HD Graphics 400 @ 200-600MHz, 12-core, shared memory[18][22] PowerVR SGX530 @ 200MHz SGX530 @ 200MHz[4]
Co-processor(s)
  • TI C64+ DSP[3]
  • 2x ARM Cortex M4 @ 200Mhz(IPU)[3]
  • Vivante GC320 2D Accelerator[3]
  • None
  • TI C64x+ DSP
  • TI C64x DSP @ 800MHz[4]
Wireless LAN IEEE 802.11 a/b/g/n[8][3] IEEE 802.11 a/b/g/n[23] IEEE 802.11 a/b/g/n[5] IEEE 802.11 b/g[4]
Bluetooth Bluetooth 4.1[3] Bluetooth 4.1[23] Bluetooth 4.1[5] Bluetooth 2.0 + EDR[4]
Cell modem (SIM card slot) Optional: Built-in LTE Modem: 100Mbps download, 50Mbps upload[3] No Optional: Built-in LTE Modem: 100Mbps download, 50Mbps upload No
OR: UMTS HSPA 14.4/5.76 Mbps with CDMA[5]
Two Sim Slots switchable via Software[24] (Dual-SIM); unused SIM slot can be accessed by CPU as a smartcard
Satellite navigation (GNSS) If with cell modem: GPS, cell tower assisted A-GPS, GLONASS[3] No If with cell modem: GPS, cell tower assisted A-GPS, GLONASS[5] No
Upgrades Display, CPU-Board No Via HackerBus in battery compartment No
Battery 6000mAh[3], 3.7V-4.2V? 6000mAh, ?V[1] 1320mAh, 3.7V-4.2V 4200mAh[4], 4.2V
Removable Removable Removable
Battery life (claimed, high power draw) 10 hours[25] 8 hours[1] 4-5 hours 10 hours[4]
Battery life (claimed, standby) ??? ??? 10 days ???
Video output Micro-HDMI (type D)[3] Mini-HDMI (type C)[1] TRRS Composite[26] custom connector required, S-Video + RCA + Line-In &- Out[4]
USB 2x Type A 2.0, 1x Micro-B 3.0 (OTG), 1x Micro-B 1.1 (2.0?) (debug/charging)[3] 1x Type A 2.0, 1x Micro-B 2.0[1] Micro-AB 2.0 (OTG)[5] 1x Type A 2.0 (host, lacks 1.1 -- needs hub), 1x Micro-AB 2.0 OTG[4]
eSATA via adapter using one USB port (of two) No No No
External memory card slots[27] 2x SDXC <=512GiB/Slot = 1TiB[3] 1x microSD <=200GiB[1] No 2x SDXC <=512GiB/Slot = 1TiB[4]
Internal memory card slots[27] 1x microSDXC <=200GiB[3] No 1x microSDXC <=200GiB No
Embedded storage 32 GB eMMC[3] 64 GB eMMC[1] 64 GB eMMC + 512MiB NAND[5] 512 MB NAND[4]
FM radio No No Rx & Tx[5] No
Camera No No VGA front & 5 MP rear[5] No
NFC No No Yes[5][28] No
Hardware Documentation Planned No Yes Yes
Shipping month No earlier than July[29] October No earlier than July[30] 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 GPD Win specification
  2. 2.0 2.1 Store says 480 EUR is ~40% partial funding
  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 3.19 3.20 3.21 3.22 3.23 Pyra 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 4.16 4.17 4.18 Pandora specification
  5. 5.00 5.01 5.02 5.03 5.04 5.05 5.06 5.07 5.08 5.09 5.10 5.11 5.12 5.13 Neo900 specification

  6. 2 on back
    1 under power button
    2 next to power button

  7. 1 on the display
    2 on the sides
    1 on left side of keyboard (not visible when closed)
    1 on the rear above the camera (between the flash LEDs; visible only when camera open)
  8. All are on the Hinge
  9. Video of the Prototype (at around 5:40)
  10. 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]
  11. Via 6 RGB LEDs[3]
  12. 12.0 12.1 Pyra mockup image
  13. 13.0 13.1 GPD Win mockup image
  14. 14.0 14.1 Pandora photo
  15. derived from Ångström, a GNU/Linux variant for ARM[4]
  16. 16.0 16.1 Neo900 FAQ
  17. This depends on hardware details, particularly for the BIOS (currently non-free), WiFi and Bluetooth (non-free on the Pandora)
  18. 18.0 18.1 18.2 18.3 18.4 GPD Win comments & replies
  19. The ARM is IMPORTANT: there are non-ARM Android versions, which would not run most high-performance ARM programs, which use native ARM code
  20. RAM Datasheet
  21. PowerVR SGX544-MP2 benchmarks
  22. Cherry Trail GPU benchmarks
  23. 23.0 23.1 GPD Win development updates
  24. Neo900 block diagram
  25. No official statement
  26. Like the N900, per IRC discussion.
  27. 27.0 27.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.
  28. Neo900 NFC info
  29. "PCB-wise, once we can approve everything to be working fine, it'll take about 2 - 3 months until the production can happen."
  30. [14:19:59] <DocScrutinizer05> well, Q3 is optimistic, 2016 is honest
Back
Top