Frequently Asked Questions: Difference between revisions
m (→What are the standards for navigating the system with the game buttons and nubs?: Only the nubs are configured by funkeymonkey. The dpad, like the shoulder buttons are a keyboard mapping.) |
|||
| (27 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
To get a general idea of what's in the Pyra, check out the [[Dragonbox Pyra]] page. | |||
=== What's the current development status? === | |||
What we're doing ([https://pyra-handheld.com/boards/threads/it-reminds-me-of-the-pandora.99197/page-16#post-1681265 as of October 26, 2020]) is: | |||
• Preassemble as many Pyras up to the state that only the mainboard and CPU boards need to be put in (so Lid, DisplayBoard, magnet, logo, LCD Cable, Hinge, speakers, keymat) as possible.<br> | |||
• Once everything is here, send out the emails to the preorders to finish the order. Then finish the assembly with the correct color and ship it. | |||
The preassembly is most of the work. Putting in the boards and closing it up is pretty fast. | |||
=== Who's ED? === | === Who's ED? === | ||
| Line 14: | Line 22: | ||
=== Help, I'm a Linux n00b! === | === Help, I'm a Linux n00b! === | ||
=== What are the standards for navigating | That's no problem. As Debian Linux comes pre-installed, you won't have any Driver problems and care is taken to make the System Beginner-friendly. Also you can always ask at [https://pyra-handheld.com/boards/ the Forums]. | ||
=== What are the standards for navigating the system with the game buttons and nubs? === | |||
The default settings are that the left nub acts as the mouse, and the right nub acts as the mouse buttons. The right nub can be moved left to invoke a left click, and moved right to invoke a right click and bring up a menu. It can be moved up or down to act as a scroll wheel. | |||
This behaviour is user configurable in /etc/pyrainput.cfg as powered by [https://dev.pyra-handheld.com/packages/funkeymonkey-pyrainput/-/blob/master/README.md FunKeyMonkey]. After editing the file, either reload the configuration or reboot. | |||
The d-pad is the unit's arrow keys. You can bring up the application menu (the Linux equivalent of the Windows start menu) by pressing the Pyra button, and step through the menu using the d-pad as arrow keys. You will need to press enter on the keyboard to actually select an item however. Or you can drive the whole operation with the nubs acting as the mouse, but experienced users tend to prefer using the buttons to drive the menu. | |||
The shoulder buttons also act as keyboard keys. They are set up so that L1 acts a shift key, and R1 acts as a control (ctrl) key. L2 acts as an extra Function (Fn) key giving you access to secondary functions on the keyboard keys, and R2 acts as Alt. These can speed up typing on the keyboard when holding the device in your hands and typing using your thumbs. | |||
=== How do I connect to WiFi? === | === How do I connect to WiFi? === | ||
| Line 25: | Line 44: | ||
For CPU/GPU-intensive programs such as games, however, the standard Debian packages won't be optimized well for the Pyra hardware. Like the [http://repo.openpandora.org/ Pandora community repository], there will be a Pyra repository which utilizes the [[.dbp|DBP]] (DragonBox Package) format. Check out the [[.dbp#Installing.2Fupdating_software|DBP install instructions]]. | For CPU/GPU-intensive programs such as games, however, the standard Debian packages won't be optimized well for the Pyra hardware. Like the [http://repo.openpandora.org/ Pandora community repository], there will be a Pyra repository which utilizes the [[.dbp|DBP]] (DragonBox Package) format. Check out the [[.dbp#Installing.2Fupdating_software|DBP install instructions]]. | ||
=== When will the GPU be fully utilizable? === | === When will the GPU be fully utilizable? === | ||
It is working as of the 29th of June, 2016. | |||
=== When will the phone software be ready? === | === When will the phone software be ready? === | ||
| Line 51: | Line 71: | ||
For the above carriers, probably, if/when they allow the device on the network, and if/when the [[Frequently_Asked_Questions#When_will_the_phone_software_be_ready.3F|software will be ready]]. | For the above carriers, probably, if/when they allow the device on the network, and if/when the [[Frequently_Asked_Questions#When_will_the_phone_software_be_ready.3F|software will be ready]]. | ||
=== Should I get 2GB or 4GB RAM? === | |||
Due to low demand, 2 GB is no longer an option. A few prototype PCBs were created with 2 GB, but all Pyras will ship with 4 GB RAM. | |||
=== Why is there not a camera? === | === Why is there not a camera? === | ||
At the time of development, all available camera modules are too thick (front to back) to fit inside the lid without enlarging the (already quite thick) case. Putting a camera in the base would result in an awkward and unusable camera angle. | At the time of development, all available camera modules are too thick (front to back) to fit inside the lid without enlarging the (already quite thick) case. Putting a camera in the base would result in an awkward and unusable camera angle. | ||
| Line 60: | Line 85: | ||
*Cost | *Cost | ||
A thread about adding a camera: [https://pyra-handheld.com/boards/threads/perfect-camera-for-pyra-pandora.74742 Camera thread] | |||
=== Why not include hardware X on the Pyra? === | === Why not include hardware X on the Pyra? === | ||
| Line 80: | Line 99: | ||
The Pyra will be a modular, hackable device. Just as the Pandora has been lovingly modded, there will be creative solutions to get the most out of the Pyra. The hardware designs for the Pyra are also expected to be open-sourced, so anything is possible in terms of homebrew hardware development. | The Pyra will be a modular, hackable device. Just as the Pandora has been lovingly modded, there will be creative solutions to get the most out of the Pyra. The hardware designs for the Pyra are also expected to be open-sourced, so anything is possible in terms of homebrew hardware development. | ||
=== Why use ARM instead of x86? === | |||
There are many reasons, some mentioned above, and still more: | |||
*Many emulators and programs work better on the Pandora than on their equivalent mobile x86 computers (REFERENCE??), because the algorithms have been optimized for ARM. This will be the same for the Pyra. (See [https://en.wikipedia.org/wiki/Algorithm#Computer_algorithms algorithms are technology].) | |||
*Most x86 developers target desktop computers, which the Pyra is not. This results in a bit of laziness in optimizing the program, which will make it run slower on the Pyra. (And since the developers aren't targeting mobile usage, they probably won't optimize it.) This would make a lot of people unhappy, if they realized their desktop games couldn't be played on the device without some tweaks. | |||
*ARM makes it easier to make Android work. | |||
*Most Linux programs don't need x86 to run; just recompile to ARM. | |||
*While Intel is bringing back their Atom line, their power consumption is still quite high for a mobile device. Perhaps this won't be as big of a concern in the future, but ED doesn't like his handhelds hot. | |||
Intel processors were considered, but ARM was chosen in the end. A future x86 module could be possible, if there is enough interest. But there is no real performance hit when using ARM in Linux, and instead a gain in certain games and emulators due to better-optimized algorithms. | |||
=== What's this about eSATA? === | === What's this about eSATA? === | ||
See: [[Storage]] | eSATA is provided via the unused Pins from the USB 3.0 Port.See: [[Storage#eSATA_via_Adapter|Storage]] | ||
Latest revision as of 03:38, 14 February 2021
Overview
To get a general idea of what's in the Pyra, check out the Dragonbox Pyra page.
What's the current development status?
What we're doing (as of October 26, 2020) is:
• Preassemble as many Pyras up to the state that only the mainboard and CPU boards need to be put in (so Lid, DisplayBoard, magnet, logo, LCD Cable, Hinge, speakers, keymat) as possible.
• Once everything is here, send out the emails to the preorders to finish the order. Then finish the assembly with the correct color and ship it.
The preassembly is most of the work. Putting in the boards and closing it up is pretty fast.
Who's ED?
You've probably seen this on the forums. It's the digrammaton for our benevolent dictator EvilDragon.
What to expect when booting Pyra for the first time
First Run Wizard
After booting, the screen will look something like this. Further refinements to be developed by various members of the community. The first run wizard will walk you through creating a user, setting a password, and the usual keyboard setup.
Help, I'm a Linux n00b!
That's no problem. As Debian Linux comes pre-installed, you won't have any Driver problems and care is taken to make the System Beginner-friendly. Also you can always ask at the Forums.
The default settings are that the left nub acts as the mouse, and the right nub acts as the mouse buttons. The right nub can be moved left to invoke a left click, and moved right to invoke a right click and bring up a menu. It can be moved up or down to act as a scroll wheel.
This behaviour is user configurable in /etc/pyrainput.cfg as powered by FunKeyMonkey. After editing the file, either reload the configuration or reboot.
The d-pad is the unit's arrow keys. You can bring up the application menu (the Linux equivalent of the Windows start menu) by pressing the Pyra button, and step through the menu using the d-pad as arrow keys. You will need to press enter on the keyboard to actually select an item however. Or you can drive the whole operation with the nubs acting as the mouse, but experienced users tend to prefer using the buttons to drive the menu.
The shoulder buttons also act as keyboard keys. They are set up so that L1 acts a shift key, and R1 acts as a control (ctrl) key. L2 acts as an extra Function (Fn) key giving you access to secondary functions on the keyboard keys, and R2 acts as Alt. These can speed up typing on the keyboard when holding the device in your hands and typing using your thumbs.
How do I connect to WiFi?
What software is available for the Pyra?
How do I install software?
The default Pyra OS is based on Debian, which allows for simple installs/upgrades.
For CPU/GPU-intensive programs such as games, however, the standard Debian packages won't be optimized well for the Pyra hardware. Like the Pandora community repository, there will be a Pyra repository which utilizes the DBP (DragonBox Package) format. Check out the DBP install instructions.
When will the GPU be fully utilizable?
It is working as of the 29th of June, 2016.
When will the phone software be ready?
When someone gets around to porting this stuff. It may be a couple months (or longer) after the first preorder Pyras arrive in people's pockets.
How can I customize my Pyra?
How can I change the theme?
How can I tweak the options for Pyra-specific hardware? (e.g. Keyboard, Nubs, Touchscreen, etc.)
Hardware questions
What carrier compatibility is there with the Pyra cell module?
The Pyra has a GSM module, so just say no to CDMA carriers. Check Carrier Compatibility for help/discussion for the country you reside in. But please note, compatible carriers would still likely have to approve the use of the Pyra on their networks.
How can I get the Pyra working on one of the compatible networks?
You may have to call or talk to someone about it, give them the device information, etc.
Can I turn off data and use the Pyra as a dumb phone?
For the above carriers, probably, if/when they allow the device on the network, and if/when the software will be ready.
Should I get 2GB or 4GB RAM?
Due to low demand, 2 GB is no longer an option. A few prototype PCBs were created with 2 GB, but all Pyras will ship with 4 GB RAM.
Why is there not a camera?
At the time of development, all available camera modules are too thick (front to back) to fit inside the lid without enlarging the (already quite thick) case. Putting a camera in the base would result in an awkward and unusable camera angle.
Concerns were also raised about:
- The utility of a small, low-performance camera
- Privacy implications
- Cost
A thread about adding a camera: Camera thread
Why not include hardware X on the Pyra?
The reason(s) may include but not be limited to:
- Limited funding
- Limited resources
- Need small minimum order quantities (MOQ) for a niche coummunity's production run, with linux drivers and decent design support
- Potential future upgrades/versions to add it
- Current expected specs are adequate for MOST of the existing community
- Feature creep would mean the Pyra would never get released
- EvilDragon made his decision to not include it
The Pyra will be a modular, hackable device. Just as the Pandora has been lovingly modded, there will be creative solutions to get the most out of the Pyra. The hardware designs for the Pyra are also expected to be open-sourced, so anything is possible in terms of homebrew hardware development.
Why use ARM instead of x86?
There are many reasons, some mentioned above, and still more:
- Many emulators and programs work better on the Pandora than on their equivalent mobile x86 computers (REFERENCE??), because the algorithms have been optimized for ARM. This will be the same for the Pyra. (See algorithms are technology.)
- Most x86 developers target desktop computers, which the Pyra is not. This results in a bit of laziness in optimizing the program, which will make it run slower on the Pyra. (And since the developers aren't targeting mobile usage, they probably won't optimize it.) This would make a lot of people unhappy, if they realized their desktop games couldn't be played on the device without some tweaks.
- ARM makes it easier to make Android work.
- Most Linux programs don't need x86 to run; just recompile to ARM.
- While Intel is bringing back their Atom line, their power consumption is still quite high for a mobile device. Perhaps this won't be as big of a concern in the future, but ED doesn't like his handhelds hot.
Intel processors were considered, but ARM was chosen in the end. A future x86 module could be possible, if there is enough interest. But there is no real performance hit when using ARM in Linux, and instead a gain in certain games and emulators due to better-optimized algorithms.
What's this about eSATA?
eSATA is provided via the unused Pins from the USB 3.0 Port.See: Storage