It's software this time!

[FBnil]

So the pyra will be there in 2 months now!

Hey, it's 2 months (don't jinx it!)

 

[Nintendo]

Make a script or something to find out who voted no

 

[matzesu]

Reminds me on a case where somewhone in the German Bundestag ditnt voted for Heidi Simonis, and then the Bildzeitung dit a Artikel whit "Heidi Mörder"..

But i think a Democraty should also allow other votes, even if one votes whit No..
Whe have 1 No until now, so i think its save for him to get the Pyra early..

Dos the End of the Vote on 18.06 means that then whe have the regular release ??

 

[NetBLOKS]

Dos the End of the Vote on 18.06 means that then whe have the regular release ??

No, the official release will of course be the 17th of June so that the Pyras will arrive at the end of the poll

 

[iArnold]

I did not order, nor think I really will, money issue so I will not vote in this matter. But my view is you should just have taken this decision yourself ED. Just like with the prototypes, this is similar and it will be your call to have software improvements before shipping out early Pyra's with still faulty software and issues. (My vote would have been a Yes.) Be a real Boss, without you no Pyra, you call the shots!

 

[matzesu]

18th of June is maybe a bit short, this is in 3 Days.. ^^

 

[Hardcoreufo]

I'm all onboard letting those who can actively contribute to improving the software jump ahead. As long as you let us know what they will be doing. So I'm voting yes!

 

[Haraldur]

That's Box86 running. Couldn't get my hand on Unreal sources unfortunatly...

The guy who makes the Unreal 227 patch (https://www.oldunreal.com/oldunrealpatches.html) claims to have access to the source code, but is not allowed to share it further. I suppose that, in theory, he could cross-compile to armhf.

Although I do wonder how playable games like Unreal are when using nubs rather than a mouse. I have played Unreal before and I found it quite hard (on hard/Unreal difficulty, admittedly) with a mouse, so I would expect to only be able to play in on tourist/adventure difficulty with a Pyra. Am I wrong? Can a player be nimble enough in that kind of FPS when using the Pyra's nubs?

 

[matzesu]

On Pandora, playing Shooters whit Right Nub and DPAD was quite confortable, although maybe a bit slow somethimes,
If i remember correctly, they even used my Mapping on the Official PND on Pandora after i postet it..
Also i just changed the Mouse Funktion on the Nubs to the oposide, so i ditnt need to bother whit Joystick Input in the Game Config..

 

[Palmiga]

Yes

FullAck.

 

[God Ginrai]

IIRC, plenty of developers got early access to the GP2X. Additionally, there were developers who got early Pandoras. I don't see why we can't let someone who can help us to have a better initial end-user experience have a go at it before we get our systems.

-God Ginrai

 

[lordbobjones]

Do it!

 

[o-neon-e]

Definitely yes
That is exciting news!

Thanks for involving the community in this decision, it really proves your commitment to the open (-source) character of this project.

 

[ClockworkCoder]

So we may be just a little over a day before the first production unit gets dispatched (albeit no official box or manual)? Please correct me if I'm wrong!

 

[netcat]

can someone plz point me to the relevant bug-tracking page(s)?

all the ones i found seem to be out-of-date.

 

[docbroke]

Latest updates may be found on kernel mailing list https://pyra-handheld.com/pipermail/kernel/

 

[jakko]

According to my understandning (please correct me, anyone)...


Letux Kernel Issues with Label Device: Pyra
https://projects.goldelico.com/p/gta04-kernel/issues/label/1799/open/

Letux Kernel Issues with Label Device:Pyra - A Linux Distribution Kernel optimised to run identically on GTA04, Pyra, Neo900, OpenPandora, BeagleBoard and others

projects.goldelico.com

Toastbuckets work kernel issues
https://dev.pyra-handheld.com/kernel/pyra-kernel/issues

That one is Toastbuckets work kernel. It's not exactly the one we're currently using but an older clone with some fixes from Toastbucket, but any fixes for TILER there can be applied to any other 4.19 kernel as well.
So for working and testing, this one would be okay.

The end goal is to use the Letux Kernel with our own kernel config and that's it. But we can provide patches to Nikolaus when it's working.

Pyra OS issues
https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues


Additionally, prototype related thread "Information about OS / Kernel / Prototypes" in the "Prototype information and bug tracker" section

Welcome to this information section.
This section is primarily meant for the prototype preorderers to get some information about the unit they just received, but it also gathers the information about where to post bug reports and feature requests.
It will be updated regularly.

1. Known issues with the currently delivered prototypes

Congrats on receiving your prototype and thanks a lot for helping out the project with that
Here are some notes you should know when using your prototype:

• Touchscreen not 100% accurate at the edges: Unfortunately, this is a problem with resistive touchscreens: It's always unresponsive at the edges. The touchscreen would need to be a bit bigger to compensate that,but modern displays don't have a huge surrounding. It should work fine in normal use though.
• The nub clicks don't do anything: That's normal, their events are not yet configured. They're currently using the same setup as the Pandora nubs. See here: https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues/6
• Soft reboot (either using reboot or Power + top-left shoulderbutton) doesn't work and the Pyra hangs. This is a software bug. If that happens, press and hold the power button for 8 seconds which should switch off the unit completely.
• When powered off, the battery is drained! This only happens with our own OS, according to Nikolaus, Letux OS doesn't have that issue. Something probably isn't powered down completely, my guess is that it's the modem.
• The modem needs a few minutes to appear. This also only happens with our own OS, it's instantly available in Letux OS. Might also be related to the power drain issue.
• The lid switch doesn't do anything at the moment - it's not configured to do anything. Additionally, I've tried different magnets and some in the prototypes are probably too weak.
• The display flickers - that's due to the power regulator used in the display board. It's too weak. The final units will use a different regulator for the backlight which doesn't have that issue.
• Keyboard brightness changes sometimes: The OS sees the keyboard backlight as the display brightness, which is the reason it lowers the light after a few seconds and increases the brightness when you press a key. It seems to use its own brightness settings though, so it interferes with our own script which is why it sometimes increases the brightness to full strength.
• Audio wheel currently changes the speaker volume in ALSA, it does not change the master volume (which would make more sense). So the headset volume needs to be changed manually using ALSAMixer
• If the volume is set too high, the following two things can happen:
  a) It overdrives and distorts (DC-Offset and Gain need to be setup in the driver)
  b) The driver somehow outputs some weird loud noise after a while until you stop the current audio stream.
  So make sure the volume isn't set too high.
• Speaker and Headphones currently have the same output, and you need to use ALSAMixer to enable / disable the speakers / headsets manually. See also here: https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues/12
• If you don't hear any audio, try checking with ALSAMixer that the speakers are enabled.
• Programs scanning the ALSA bus for devices will lead to a driver lock up. This is because of the WIP of ABE / AESS integration. See also here: https://dev.pyra-handheld.com/kernel/pyra-kernel/issues/4
• Per default, the unit runs on kernel 4.19.60-letux-lpae-pyra. You can install other Letux kernels via apt install. To boot them, you either need to edit extlinux.conf and change the default one or boot with serial output (connect the middle Micro-USB to a PC) where you'll see a bootmenu when you switch on the unit.

2. Bug reports / fixes / feature requests / patches for anything OS related

We're still discussing about how and where to best report / post these.
At the moment, you can either use this forum section (I've created prefixes so you can use them similar as bugtracker) or post them on this git project: https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues
We'll take care moving them to the appropriate place.


3. Bug reports / fixes / feature requests / patches for anything Kernel related

This is even more a mystery right now. We're basically using Letux kernel, so any reports to kernel related stuff would make most sense on the Letux project. I'm currently waiting for an answer from Nikolaus if he's okay with that and which GIT and tracker we should use for that.
So for the moment, please also use this forum section or the pyra kernel git project: https://dev.pyra-handheld.com/kernel/pyra-kernel/issues
This project is a temporary working kernel. We plan to submit all patches to Letux and then switch over using Letux Kernels as standard in the Pyra.


4. Ressources

Some important ressources:

Pyra Kernel issue tracker: https://dev.pyra-handheld.com/kernel/pyra-kernel/issues
Pyra U-Boot Git with issue tracker: https://dev.pyra-handheld.com/kernel/pyra-uboot
Pyra OS Issue tracker: https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues/12
Pyra Development Site: https://dev.pyra-handheld.com/
Pyra Images (to boot off SD or eMMC): https://packages.pyra-handheld.com/images/buster/
Letus Kernel issue tracker: http://projects.goldelico.com/p/gta04-kernel/issues/

 

[daveshah]

The Goldelico Letux kernel issues list is probably the best one to work with. Unfortunately, the registration isn't working for me there, I get to the last step but the "Enable Your Account" button doesn't do anything...

 

[docbroke]

Issues related to pyra seem to have scattered everywhere. Needs bit of organization. We need to create a place to have all issues at one place

 

[sleepy]

Captain, prioritising the production assets to the develpoment deck would yield far better results for the crew in the long term. The logic is clear.