Autopilot does not fully work on xenial / Qt 5.5/ Mir

Hi Timo, would you please provide more information about how to update qt? I've tried a couple of approaches described here: https://wiki.ubuntu.com/Touch/QtTesting but none of them worked out

flashed the device with the image from ubuntu-touch/staging/ubuntu. Used revision 61 since the one included in the document (40) is not available. With that image the device is not even booting after flash

flashed the device with the latest image from rc-proposed, updated qt with the version in silo 048 and reboot. After the reboot, the device does not initialize

Thanks
Santiago

Hi Santiago. Thanks for trying the instructions, you did everything you could...

Unfortunately bug #1604421 prevents for some unknown reason working of recent images, even if dist-upgrade from image #40 works fluently (which means the problem is not in the ubuntu image, but in device/custom images or some infrastructure). But as you found out, it seems image #40 has been cleaned away now meaning you can't use that way either anymore.

Regarding vivid Qt 5.6 port, it has been unmaintained for a while with the focus having been in xenial/yakkety and the outdateness of it means it can't be used at the moment. I will upgrade the wiki page to indicate that.

Please debug what you can on the desktop instead, by using xenial + stable-overlay + silo 11. You should be able to investigate the status of autopilot and the functionality of introspection over there as well to certain extent.

Note that this bug report is originating from Unity 8 team's earlier findings, and right now we simply feel there's "something" not working properly within autopilot itself, but validating that claim would need investigating.

Hi Timo, I've tested what you suggested: xenial + stable overlay + silo 011 and autopilot is working just fine. I was able to introspect applications, select elements and interact with them without problems. Once the bug above is fixed I'll give it another try in the phone, but in the meantime do you have an idea of the problems that we might face and that originated this bug report?

I've asked Saviq for his experience but he also doesn't have recent experience now.

I seem to have a lot more failures on xenial but it might be real problems indicated.

For now, I think this bug can be set as Incomplete, to be revisited when the phones can be investigated in more detail. It's very good to know that introspecting applications and interaction with them would seem to work on desktop with Qt 5.6. That means there's no huge problems at least to be expected, together with the fact that my UITK AP run on phone was okayish (maybe 75% pass).

I'm attaching my unity8 autopilot log from Qt 5.5 (as opposed to using the Qt 5.6 PPA), which did have more trouble than UITK but I believe Unity 8 team will also look into that once phone can be tested.