Comparison Chart: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(GPD Win's Crowdfounding Campaing is over. Added striketrought.) |
||
Line 60: | Line 60: | ||
| style="background-color: palegoldenrod"| ~500€[https://pyra-handheld.com/boards/threads/finalizing-everything.77289/] | | style="background-color: palegoldenrod"| ~500€[https://pyra-handheld.com/boards/threads/finalizing-everything.77289/] | ||
~600€(LTE Version) | ~600€(LTE Version) | ||
| style="background-color: palegreen"| ~266€ (crowdfund)<ref name="gpdwin_spec"/> or ~445€ (retail) | | style="background-color: palegreen"| <strike>~266€ (crowdfund)<ref name="gpdwin_spec"/> or</strike><ref>The Indiegogo Campaing is over</ref> ~445€ (retail) | ||
| style="background-color: peachpuff"| ~1200€<ref name="neo900_price">[https://my.neo900.org/index.php?id_product=1&controller=product&id_lang=1 Store says 480 EUR is ~40% partial funding]</ref> | | style="background-color: peachpuff"| ~1200€<ref name="neo900_price">[https://my.neo900.org/index.php?id_product=1&controller=product&id_lang=1 Store says 480 EUR is ~40% partial funding]</ref> | ||
| n/a(EOL) | | n/a(EOL) | ||
|- | |- | ||
| style="background-color: palegoldenrod"| ~$565 or ~$677 | | style="background-color: palegoldenrod"| ~$565 or ~$677 | ||
| style="background-color: palegreen"| ~$300 or ~$500 | | style="background-color: palegreen"| <strike>~$300 or</strike> ~$500 | ||
| style="background-color: peachpuff"| ~$1350 | | style="background-color: peachpuff"| ~$1350 | ||
| n/a(EOL) | | n/a(EOL) |
Revision as of 11:34, 26 April 2016
Pyra | GPD Win | Neo900 | Pandora 1Ghz | |
Price | ~500€[5]
~600€(LTE Version) |
~1200€[3] | n/a(EOL) | |
~$565 or ~$677 | ~$1350 | n/a(EOL) | ||
Size | ~140 x 84 x 29mm[4] | 155 x 96 x 20mm[1] | 111 x 60 x 20mm | 140 x 83 x 27mm[5] |
Screen size | 5"[4] | 5.5"[1] | 3.5"[6] | 4.3"[5] |
Screen resolution | 1280x720 (720p)[4] | 1280x720 (720p)[1] | 800x480[6] | 800x480[5] |
Touchscreen | Dualtouch Resistive (Stylus included) | Capacitive, multitouch[1] | Dualtouch Resistive (Stylus included)[6] | Resistive (Stylus included)[6] |
Notification LEDs | Total 5 RGB LEDs[7] | Only power indicator | Total 5 RGB LEDs[8] | 6 Non-RGB LEDs[9] |
Keyboard Backlight | Yes[4] | No | Yes [10] | No |
Keyboard Layout | Good[11] | Problematic [12] | OK | OK |
Keyboard keys | 47[13] (including ESCAPE and F11 away from main section) | 67[14] | 38 | 43[15] |
Face buttons | 6[4] | 4[1] | 0 | 4[5] |
Shoulder buttons | 4[4] | 4[1] | 0 | 2[5] |
Control buttons | 6[13] | 4[14] | 4 + slider & camera cover | 3 + slider[15] |
Analogue control | Nubs, clickable[4] | mini-joysticks[1] | None | Nubs[5] |
Simultaneous use of mouse and all other controls | Yes | No (tentative)[1] | n/a | Yes |
Volume control | Wheel[4] (digital input device: software control[7]) | Buttons[1] | Buttons | Wheel[5] (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[16] |
Windows x86 Applications | via WINE + x86 Emulator (Exagear/qemu) | Native x86_64 | via WINE + x86 Emulator (Exagear/qemu) | via WINE + x86 Emulator (Exagear/qemu) |
Free/libre System provided (per DFSG)[17] | non-free 3D graphics drivers | No | non-free 3D graphics drivers[18] | non-free 3D graphics, WiFi and Bluetooth |
Android apps | ARM+Java via dualboot or compatibility layer (like Shashlik) | Java-only+x86 via dualboot or ARM+Java via emulator (like Android SDK's QEMU variant) | ARM+Java via dualboot or compatibility layer (like Shashlik) | ARM+Java via dualboot or compatibility layer (like Shashlik) |
CPU | TI OMAP5432: 2x ARM Cortex-A15 1.5Ghz; NEON SIMD[4] | Intel Atom x5-Z8550: 4x Intel Cherry Trail x86_64 1.44Ghz; SSE SIMD[19] | TI OMAP3 DM3730: 1x ARM Cortex A8 @ 1.0 Ghz; NEON SIMD[6] | TI OMAP3 DM3730: 1x ARM Cortex A8 @ 1.0 Ghz; NEON SIMD[5] |
RAM | 2 GB DDR3L-533 Dual-Channel[4][20]; Maybe 4Gb[8] | 4 GB LPDDR3-1600[1] Dual-Channel[19] | 1 GB[6] | 512 MB DDR1 @ 200Mhz[5] |
GPU | PowerVR SGX544-MP2[4][21] | Intel HD Graphics 400 @ 200-600MHz, 12-core, shared memory[19][22] | PowerVR SGX530 @ 200MHz | SGX530 @ 200MHz[5] |
Co-processor(s) |
|
|
| |
Wireless LAN | IEEE 802.11 a/b/g/n[9][4] | IEEE 802.11 a/b/g/n[23] | IEEE 802.11 a/b/g/n[6] | IEEE 802.11 b/g[5] |
Bluetooth | Bluetooth 4.1[4] | Bluetooth 4.1[23] | Bluetooth 4.1[6] | Bluetooth 2.0 + EDR[5] |
Cell modem (SIM card slot) | Optional: Built-in LTE Modem: 100Mbps download, 50Mbps upload[4] | No | Optional: Built-in LTE Modem: 100Mbps download, 50Mbps upload | No |
OR: UMTS HSPA 14.4/5.76 Mbps with CDMA[6] | ||||
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[4] | No | If with cell modem: GPS, cell tower assisted A-GPS, GLONASS[6] | No |
Upgrades | Display, CPU-Board | No | Via HackerBus in battery compartment | No |
Battery | 6000mAh[4], 3.7V-4.2V? | 6000mAh, ?V[1] | 1320mAh, 3.7V-4.2V | 4200mAh[5], 4.2V |
Removable | Non Removable | Removable | Removable | |
Battery life (claimed, high power draw) | 10 hours[25] | 8 hours[1] | 4-5 hours | 10 hours[5] |
Battery life (claimed, standby) | ??? | ??? | 10 days | ??? |
Video output | Micro-HDMI (type D)[4] | Mini-HDMI (type C)[1] | TRRS Composite[26] | custom connector required, S-Video + RCA + Line-In &- Out[5] |
USB | 2x Type A 2.0, 1x Micro-B 3.0 (OTG), 1x Micro-B 1.1 (2.0?) (debug/charging)[4] | 1x Type A 2.0, 1x Micro-B 2.0[1] | Micro-AB 2.0 (OTG)[6] | 1x Type A 2.0 (host, lacks 1.1 -- needs hub), 1x Micro-AB 2.0 OTG[5] |
eSATA | via adapter using one USB port (of two) | No | No | No |
External memory card slots[27] | 2x SDXC <=512GiB/Slot = 1TiB[4] | 1x microSD <=200GiB[1] | No | 2x SDXC <=512GiB/Slot = 1TiB[5] |
Internal memory card slots[27] | 1x microSDXC <=200GiB[4] | No | 1x microSDXC <=200GiB | No |
Embedded storage | 32 GB eMMC[4] | 64 GB eMMC[1] | 64 GB eMMC + 512MiB NAND[6] | 512 MB NAND[5] |
FM radio | No | No | Rx & Tx[6] | No |
Camera | No | No | VGA front & 5 MP rear[6] | No |
NFC | No | No | Yes[6][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.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 GPD Win specification
- ↑ The Indiegogo Campaing is over
- ↑ Store says 480 EUR is ~40% partial funding
- ↑ 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 4.19 4.20 4.21 4.22 4.23 Pyra specification
- ↑ 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 5.14 5.15 5.16 5.17 5.18 Pandora specification
- ↑ 6.00 6.01 6.02 6.03 6.04 6.05 6.06 6.07 6.08 6.09 6.10 6.11 6.12 6.13 Neo900 specification
- ↑
2 on back
1 under power button
2 next to power button - ↑
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) - ↑ All are on the Hinge
- ↑ Via 6 RGB LEDs[1]
- ↑ Video of the Prototype (at around 5:40)
- ↑ The GPD Win seems to be too large to reach the Center Keys see here: [2] Also the Keyboard is not Centered, and the Layout isn't optimal[3]
- ↑ 13.0 13.1 Pyra mockup image
- ↑ 14.0 14.1 GPD Win mockup image
- ↑ 15.0 15.1 Pandora photo
- ↑ derived from Ångström, a GNU/Linux variant for ARM[4]
- ↑ I.e. Open Source BIOS, Drivers, Firmware that needs to be loaded
- ↑ Neo900 FAQ
- ↑ 19.0 19.1 19.2 GPD Win comments & replies
- ↑ RAM Datasheet
- ↑ PowerVR SGX544-MP2 benchmarks
- ↑ Cherry Trail GPU benchmarks
- ↑ 23.0 23.1 GPD Win development updates
- ↑ Neo900 block diagram
- ↑ No official statement
- ↑ Like the N900, per IRC discussion.
- ↑ 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.
- ↑ Neo900 NFC info
- ↑ "PCB-wise, once we can approve everything to be working fine, it'll take about 2 - 3 months until the production can happen."
- ↑ [14:19:59] <DocScrutinizer05> well, Q3 is optimistic, 2016 is honest