Am 14.06.2018 um 05:10 schrieb Michael Mrozek EvilDragon@openpandora.org:
Hi,
to help our new developers get started, here are some issues I think are the most critical and should be fixed before release:
- Audio:
While getting the AESS driver (https://projects.goldelico.com/p/gta04-k ernel/issues/883/) to work before relase would be great, it is no showstopper (just a battery drainer).
However, the following two are more important: https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues/2
Right now, the headset and speakers are ONE audio device, the headset being channel 1 and 2 and the speakers being channel 3 and 4. This of course doesn't make sense and as a result, you don't have any audio out on the speakers.
I'm not sure whether this is a driver issue or a setup in ALSA / PulseAudio. Anyone wants to look into that?
Second thing: https://dev.pyra-handheld.com/EvilDragon/pyra-os/issues/9
The volume wheel is unusable right now, and it would be nice to get it to work properly without CPU-Usage :)
- TILER / 3D:
Getting the 3D driver to work is also something important. I think our TILER rotation gets in the way at the moment and the 3D driver doesn't load at all right now. Not sure if anyone is working on that and what the status is, but if anyone wants to comment on this (and if help is needed), feel free to post it here.
Info on TILER: https://projects.goldelico.com/p/gta04-kernel/issues/884 / A discussion about 3D was recently done on this mailing list, so you can check that out as well.
- Reboot / Configuration / Power Saving / etc.
Not everything seems to be setup properly right now.
For example, right now, only a coldstart works. On a reboot, the Pyra simply hangs starting the kernel: https://projects.goldelico.com/p/gta04-kernel/issues/876/
Also, you cannot boot without a battery for the first time (it runs out of juice, so the input probably is limiting it). This setting does change when the system has been booted up - as then you can remove the battery and as long as you don't connect the power source, you can shutdown the unit and reboot it as much as you like.
Additionally, it's using too much power at the moment. One reason is that not everything can be properly switched off (https:/ /projects.goldelico.com/p/gta04-kernel/issues/856/) and I don't think SmartReflex 3 is properly setup yet (though zmatt did some work in his U-Boot already, AFAIK: https://github.com/mvduin/u-boot)
So checking what needs how much power and how we can minimize power usage would be great as well.
I think those are the most important points - let me know if you think there's anything else critical.
Another annoying thing is that unplugging USB power/charger after the device was powered down automatically powers it on.
This is against a typical use pattern of using the device, recognizing battery is getting empty, plugging in a power supply and working for a while. Then your shut it down. Next morning you just want to grab the powered down device and unplug power. But you don't want to wait until it has booted and shut it down again.
This seems to be a behaviour of the Palmas differently from the twl4030 we are used to from the Pandora.
http://projects.goldelico.com/p/gta04-kernel/issues/721/
Maybe u-boot could/should already set this so that it does not depend on the kernel variants.
BR, Nikolaus