On Sun, 2018-10-14 at 02:57 +0300, Grazvydas Ignotas wrote:
Hi,
- the LCD is flickering at many brightness levels (same as older
unit). It depends on lighting conditions how much it disturbs, but I can always see it and just can't stand it. There is no flickering on full brightness, and it's almost invisible on the lowest levels, but all others are unusable for me. FWIW I don't see flickering on any brightness level on my pandoras.
That's not a hardware issue, it's a software setup of the PWM. Some don't see it, but it's annoying for me as well.
The frequency is set WAY too low right now, same for the keyboard LEDs. It can be set in the pyra-mainboard-v5.0.dtsi. You can find it searching for "pwm-backlight".
To my knowledge, this is the driver: http://www.ti.com/product/TPS61041/technicaldocuments
It supports switching up to 1MHz, which should be enough for a flicker- free backlight (it's also especially created for PDAs and Smartphones, so it should work)
- the wifi is extremely slow on my unit, tens of kB/s while the phone
does at least 1MB/s on the same router on the n (5GHz) band. On a different b/g router it does 200-300kB/s and at least works (older unit doesn't work at all there).
With the freezes I had, I couldn't test it yet - but will do so ASAP. According to the measurements, the antenna connection is fine... not sure if this could be a software issue...?
- the speakers make a disturbing loud crack while DE is loading (same
as older unit). No idea what's going on there, trying to play a boot sound? I've turned down and muted everything in audio mixers and it still does it. Ended up disabling everything audio related in dts just to get rid of this.
Sound is not working at all at the current kernel and as aTc never had speakers in his unit, even on older kernels (where audio wasn't broken at least), it was never properly implemented in the OS setup. I never had anything else except for crackling speakers here. The Audio Test I was running was form a test OS done by Nikolaus. He at least created a script which was able to play sound from the speakers.
Audio is still a software hell right now. ABE is not yet working with newer kernels and for some reason the setup is that channel 1 and 2 output on the headset and 3 and 4 on the speakers.
This is one of the biggest software-work still left, I guess :/
- shoulder buttons are barely usable (tend to get stuck pressed)
The case is not a final one. I'll tweak the buttons together with the new company once we've switched the molds. One of the CEOs is an avid gamer himself, so he knows how shoulder buttons should work (something FormAction doesn't have a clue with).
So yes, that's to be expected with the current version.
- there are periodic sata errors in dmesg ("exception Emask 0x10 SAct
0x0 SErr 0x4040000 action 0xe frozen"), don't know what it means, and I don't have anything connected
No idea about that :)
- still no signs of life from OTG port, but it's charging at least
Beware: The charging is a bit broken as well right now! The driver for some reason always sets the limit to 0.5A as soon as I connect a USB cable. Even setting it back manually to 2A doesn't work. It only works fine in U-Boot.
The driver was a quick hack by Nikolaus, as there wasn't an existing one. He is working on it and made some improvements but something is still wrong (most likely has something to do with VBUS detection).
About OTG: AFAIR there was still a software bug which is fixed as far as I know (it was discussed on the mailing list a few weeks ago), but I don't think that's implemented in our setup yet.
- lid switch isn't working (old unit too)
Okay, this is something we need to check. Have you tried triggering the lid switch with the lid magnet or with an external one? It could be the magnet in the lid is too weak - but I had no idea how I could test the lid switch, so couldn't check that.
AFAIK, Nikolaus tested the switch manually with a magnet, so it SHOULD work.
- touchscreen is unusable on the edges. With dead nubs it makes some
UI elements inoperable
Ah - damn. That means I accidentally put in one of the older screens which I didn't approve. They weren't marked in any way, so I probably mixed them up with the final ones :(
- (broken board?) nubs are never responding. On older board, they die
after some time (devices on the bus stop responding)
Yes, probably broken, as they work fine on the other boards I have here. Interesting though that they stopped working on an older board - never seen that before!
- (broken board?) noticeably draining the battery while off (older
unit doesn't do this)
I'll recheck, but I think that didn't happen here.
Well, the biggest issue is: I was never able to thouroughly test all the hardware / boards I have here, as the software wasn't finished. And with these frezes, I couldn't work on the automated testing script (similar to the one we have on the Pandora).
So while Nikolaus made low-level tests to confirm the hardware is working when the PCB is properly produced, I couldn't test the PCBs I've got here yet. The one I sent to you was completely untested as well.
I'll now try to finish the testing scripts ASAP so I can test all the units and give feedback to Global Components. It's very important we tell them what the failures on the PCBs are, so they can check these issues and make sure they won't happen in mass production.