← Back to team overview

ubuntu-phone team mailing list archive

Re: Qt5 and touch performance issue

 

Just to clarify things in my mind, I have a couple few questions.
1. Is there a reason you keep using the word "ARCH" rather than
"architecture"? Or is it possible you are referring to something else
entirely?
2. How does the architecture of the underlying OS impact the functioning of
the dalvik VM, in your mind?
3. What changes to the architecture would make the DVM be more efficient?
For instance, what changes to the window manager would you propose to make
the DVM more efficient?
If we look at the ARCH of android, I think we need change the framwork,
expecially activity manager, window manager, content providers, view
system. If touch has such an ARCH chart, it would be easier to know what to
do from the ARCH aspect.


------------------ Original ------------------
*From: * "Thomas Vo "<thomas.voss@xxxxxxxxxxxxx>;
*Date: * Thu, Jun 20, 2013 11:18 PM
*To: * "leon lee"<llrraa@xxxxxx>; **
*Cc: * "ubuntu-phone"<ubuntu-phone@xxxxxxxxxxxxxxxxxxx>; **
*Subject: * Re: [Ubuntu-phone] Qt5 and touch performance issue

On Thu, Jun 20, 2013 at 4:53 PM, leon lee <llrraa@xxxxxx> wrote:
> When I say make android dvm available on touch, I mean keep the
performance
> of touch, and make dvm adapted to touch. It means that we will change the
> framwork of android. this would be much helpful for touch's marketing.
> Don't worry about the "good enough" issue. The competition of app
companies
> is tense. If touch's app performs better, and some of the companies would
> make use of it, and the others would have to follow up.
> Btw, why do I keep making new thread in the mailist?
>

Let us assume Ubuntu Touch would want to support Android apps:

Then we would not only need to pull in Dalvik (or an equivalent that
might need a lot of optimization to fly on mobile cpus) in its
functionality as an interpreter, but also walk through the complete
Android SDK & its class library and map all platform-specific
functionality down to the Ubuntu Touch platform. In essence, we would
need to re-implement huge portions of the SDK and maintain it over
time, as both the Android SDK and the Ubuntu Touch platform evolves.
While this is certainly doable from a technical perspective, I think
that two major issues need to be considered here first:

  (1.) There will certainly be areas in the Android SDK that we either
don't want or simply can't map to Ubuntu Touch.
  (2.) The sheer size of the overall Android SDK.

To address (1.) and (2.) we could start over with inspecting the
Android SDK and the class library and check for individual
namespaces/classes if there is an equivalent on Ubuntu Touch that they
map to. If so, it would be quite interesting to know how prominent the
component is for app developers in order to be able to prioritize the
porting effort.

Any help with this preliminary evaluation would be greatly appreciated :)

Thanks,

  Thomas

> ------------------ Original ------------------
> From:  "Josh Leverette"<coder543@xxxxxxxxx>;
> Date:  Thu, Jun 20, 2013 09:58 PM
> To:  "leon lee"<llrraa@xxxxxx>;
> Cc:  "ubuntu-phone"<ubuntu-phone@xxxxxxxxxxxxxxxxxxx>;
> Subject:  Re: [Ubuntu-phone]Qt5 and touch performance issue
>
> If you ever want the system to perform smoothly, then we must absolutely
> never officially support running Android apps on Ubuntu. Additionally, it
> would be a death sentence for Ubuntu touch. Adding Android app support
would
> crush any chance of Ubuntu ever having good apps. When companies see that
> their Android app on Ubuntu is "good enough", they will never bother to
make
> an "excellent" version for Ubuntu. But when the only option is excellence,
> mediocrity is not encouraged. Ubuntu will suffer at first because of this
> decision, but it will be stronger in the long run as a result. "Delayed
> gratification" is another way to describe it.
>
> I agree that making the system smooth is very important, but they are
> writing a new display server for Ubuntu touch. Until that is finished,
most
> time spent optimizing performance would be wasted. We must wait.
>
>
> On Thu, Jun 20, 2013 at 8:30 AM, leon lee <llrraa@xxxxxx> wrote:
>>
>> I still think the most important thing right now for touch is to have a
>> reliable smoth system. For app, in the long term, we should make android
dvm
>> available on touch. So we can make use of all the android apps.
>>
>>
>> ------------------ Original ------------------
>> From: "Josh Leverette"<coder543@xxxxxxxxx>;
>> Date: Thu, Jun 20, 2013 09:45 AM
>> To: "leon lee"<llrraa@xxxxxx>;
>> Cc: "ubuntu-phone"<ubuntu-phone@xxxxxxxxxxxxxxxxxxx>;
>> Subject: Re: [Ubuntu-phone]Qt5 and touch performance issue
>>
>> For now, features are most important. I hope that they will start fixing
>> performance soon. The design is good. Performance should not be an
issue. If
>> it is, that would make me sad. I am confident that they will fix it.
>>
>> Sincerely,
>> Josh
>>
>> On Jun 19, 2013 8:07 PM, "leon lee" <llrraa@xxxxxx> wrote:
>>>
>>> This would be the major issur of touch. Can we discuss more details?
>>> Let's if there's something we can do.
>>>
>>>
>>> ------------------ Original ------------------
>>> From: "Josh Leverette"<coder543@xxxxxxxxx>;
>>> Date: Thu, Jun 20, 2013 03:05 AM
>>> To: "leon lee"<llrraa@xxxxxx>;
>>> Cc: "ubuntu-phone"<ubuntu-phone@xxxxxxxxxxxxxxxxxxx>;
>>> Subject: Re: [Ubuntu-phone] how do you feel about touch
>>>
>>> It is based on Qt5, and Qt5 makes heavy use of GPU acceleration. Right
>>> now there are a few performance issues, but I expect that Ubuntu will
run
>>> very smoothly once finished.
>>>
>>>
>>> On Wed, Jun 19, 2013 at 8:54 AM, leon <llrraa@xxxxxx> wrote:
>>>>
>>>> After know the ARCH of android, which is using java as the framework, I
>>>> feel a little disappointed. That means that with the hardware, android
won't
>>>> be as smooth as IOS, which is on the native framework.
>>>> From that day, I'm looking forward to a better android. At first, I'm
>>>> thinking about the combination of android and meego, just like what
touch
>>>> does today. Luckly, I found touch, so I don't need to move a long way
to get
>>>> my goal.
>>>> Since I don't have a working touch handset, I hope people using touch
>>>> can share your feeling with me. Would it be faster and smoother with
touch
>>>> than android?
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~ubuntu-phone
>>>> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>
>>>
>>>
>>> --
>>> Sincerely,
>>> Josh
>
>
>
>
> --
> Sincerely,
> Josh
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Attachment: 2A07F7FD@11993842.F032C451
Description: Binary data

Attachment: 2A07F7FD@11993842.F032C451
Description: Binary data


Follow ups

References