> Comparisons like this are meaningless if you don't specify the screen
> resolution. An app running well on a slow CPU can run much faster at a
> low resolution than the same app running on a fast CPU at a high
> resolution.

I Romain I really appreciate your effort to help me, really thanks for
this
but I don't know if you are trying to avoid to admit an android flaw
or if
you are convinved of what you are saying.
Please don't take me as a disrespectful person, I really want to
understand the problem
and you are the "best" people here to help me in this. I'm sorry if I
can seem rude, I don't want
to be rude or disrespectful, sometimes the language barrier can make
me seem more rude than I am, I'm sorry for this.

The problem starts when you say that I can't compare different devices
with different screen resolution.
We started with 176x220 to 800x480.
We are talking about devices with 20x less (and lesser) the power of
the actual galaxy nexus,
do you really think that resolution may affect performance in such a
way?
I'm quite "graphics oriented" (console, pc, tablet, mobiles, embedded
devices) and I never seen a platform that needs 20x the horse power
for a doubled resolution :)
Do you know one?

> I am not denying that your app worked well on Java ME feature phones
> but this doesn't mean it optimized to run on the GPU at 1280x720. If
> you could tell me more about what your app does exactly I would be
> able to help. Could you show me an example of the drawing code used by
> your app please?

My apps draws line and rect as I saied and uses StaticLayout to write
on canvas with the correct wrapping.
this simple codes require double the time
for (i = 0; i < 640; i++) {
    g.drawLine(0, alt + i, 360, alt + i, paint);
}
to be rendered on my galaxy nexus than on my feature phone with the
same canvas resolution.
put this code in a loop and see how performance decrease over time.
On my feature phone this code is drawn at the light speed, on galaxy
nexus it is slow not tested
but surely slower with hw acc on.
This code runs really better on gingerbread where we see the best
performance.
We are comparing a 800x480 devices with a 1280x720, the "drawable"
canvas is 800x480 on both devices.

> > You are talking about drawLines() over the drawLine(), should we
> > abandon antialiasing to draw some
> > lines on a 1.2GHz smartphone? (drawLines() does not support
> > antialiasing)
>
> If drawLines() doesn't do antialiasing then there's a bug. It should.
> If so, please file a bug athttp://b.android.com. I was recommending
> drawLines() not because of antialiasing but because it can batch
> operations on the GPU which is a great optimization.

Your suggestion is great and reasonable but why we should use
something that we don't need
with such a huge amount of horse power? Don't you think if a feature
phone, a bada phone,
a windows phone, a blackberry phone, can do this also android should
do this?

In any case on the android documentation (API Level 11) I finded that
drawLines() doesn't support antialiasing:
http://developer.android.com/guide/topics/graphics/hardware-accel.html
why do you call this a bug?

> And again, the CPU speed has nothing to do with performance of the GPU
> (since you love to talk about frequency, the GPU in the Galaxy Nexus
> runs at 384 Mhz; this is meaningless since you cannot really compare
> frequencies between CPU and GPU.)

I well know the difference from a GPU and a CPU rendering, performance
are bad on both in ICS (for the hardware used)
but on GPU are unacceptable.
In any case the Galaxy Nexus uses an OMAP4460 from Texas Instruments,
the specs teach that the CPU is capable of
two core running at 1.5GHz with an SGX540 running at 384MHz.
The real world says us that the CPU is running at 1.2GHz and the GPU
at 308MHz.

Why I say that performance are bad? It is simple, I run the same code
on Bada, on Windows, on BlackBerry, on feature phones and for the
hardware used ICS is the worst performer. Gingebread was far better
than this.

Thanks for taking the time to talk with me Romain, I feel the need to
pay you a beer for this :)

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to