<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 13/01/2015 10:32, Eskil Abrahamsen
Blomfeldt wrote:<br>
</div>
<blockquote cite="mid:54B4E63D.70504@theqtcompany.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 01/13/2015 10:31 AM, BogDan wrote:<br>
</div>
<blockquote
cite="mid:156593010.372319.1421141493739.JavaMail.yahoo@jws10001g.mail.ne1.yahoo.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div style="color:#000; background-color:#fff;
font-family:HelveticaNeue-Light, Helvetica Neue Light,
Helvetica Neue, Helvetica, Arial, Lucida Grande,
sans-serif;font-size:13px"><br>
<div dir="ltr"><span>Sadly </span><span style="font-family:
'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida
Grande', sans-serif; font-size: 13.3333330154419px;"
class="">run-as doesn't work on most of devices out there
and we can't rely on it. My hope is that Google will fix
that problem.</span></div>
</div>
</blockquote>
<br>
Is it really most devices? It's worked on every device I tried at
least. <br>
<br>
I think we should implement the work-around for Lollipop anyway,
since it will definitely not work without it. We could add a
warning in the Qt Creator device selection if you are using debug
deployment on a Lollipop device, saying that it might not be
compatible with all devices so that people are prepared and know
what to do if it fails.<br>
<br>
</blockquote>
<br>
I second this motion. I don't think it is a show-stopper if not all
devices are supported for *development*. I suspect most serious
developers already have multiple devices to pick from. Plus doesn't
google recommend nexus line for development?<br>
<br>
Harri<br>
<br>
</body>
</html>