Anyway we'll have a super Pinephone with a super UT more within reach of the purse due to the convergence of the interests of two super structures (PINE64 and Ubports) !!

Indeed, freezing of the OTA-11 page tracker on UT phone.
Any explanation?
Is it related to a referenced bug (of morph-browser) or something else ?

Congratulations to @VFranchomme. This is particularly interesting because having an operational fingerprint sensor in the near future is something attractive. Whether we like it or not, this technology will become a daily necessity (not to mention an imposed technology...) and UT should not be left out !!

@MarkG_108 Hello.

I have already mentioned elsewhere that reading in UT media can be more and more problematic (at least for me on RC).

Anyway, try this which works (usually) for me:

1. make a copy of the file with File manager, paste the file into UT media and then proceed as usual and the file should open and be read.

2. If that's not enough, reboot the phone and go to 1.

Not very fluid, but it can help !

Incredibly smooth !! Seeing the video and soon it will be enough to blow on the screen of the Pinephone and it will move by itself !!

@kugiigi You are right. I used 17, a little too big.
With 15 not 16, it's good.

@advocatux Wow! I didn't work for nothing!
But it kept me a little confused...
Can these words 6.0.1 still be seen somewhere with a command ?

Hello @kugiigi
i just realized that i don't see the words
cut copy paste
with portrait mode on BQ E5 HD. I'm on RC

The words appear in landscape mode.

For NEXUS 5, there are the words in lands and portr.

I reflashed a Nexus 5 with the last androïd factory image 6.0.1 (M4B30Z dec 2016), then reflashed UT by following.
On arrival, I get as detected information this:

Is this normal ?

@domubpkm To clarify the meaning of my question (I had posted it in q and a and then i finally fired it): the purpose of posting it here is not to add this as a complement to a bug report in github or even to insist on the immediate resolution of this problem. The purpose of the question, which I think may be of interest to all Nexus 5 owners, is to know IF, the contribution of MIR, wayland, new unity 8 or whatever else could lead to solving the problem directly or even finding a workaround solution. That's it!
Thank you.