Edit:
Not that it matters. I was looking for estimated performance like the
WTK does for J2ME and not exact performance.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this gro
> An emulator that accurately models the performance of real hardware
> will not be able to run in realtime on any machine sitting on
> someone's desk.
That is not true. It can be done for a cell phone. You need about
10x to do it. I would hope most people desktops are in that range.
Oddly tha
On Aug 20, 9:16 pm, tberthel <[EMAIL PROTECTED]> wrote:
> 1. The emulator to run on a system much faster than the real device.
> 2. Instrumentation to control timing.
An emulator that accurately models the performance of real hardware
will not be able to run in realtime on any machine sitting on
This is why performance emulation requires:
1. The emulator to run on a system much faster than the real device.
2. Instrumentation to control timing.
I was just looking for a rough estimate like say a Centrino Duo 1.7
Ghz with 1 Gig.
On Aug 20, 7:20 pm, "Jeff Hamilton" <[EMAIL PROTECTED]> wrot
I was obviously referring to the first phone I.E. the T-Mobile phone
coming out in Nov.
On Aug 19, 11:58 pm, "Justin (Google Employee)" <[EMAIL PROTECTED]>
wrote:
> > Could someone give us the PC hardware of something that is running it
> > the same speed as the real phone?
>
> There is no "the p
It's hard to make such statements about a certain PC emulating a
certain level of phone. There are a lot more factors at play than pure
CPU clock speed when determining end user performance. Things like the
memory bus speed, the speed of flash, cache sizes, cache replacement
algorithms, adjustable
I think what people are looking for is some rough estimate to the
correlation between the speed of the emulator and the speed of the
phone.
Such as, a 1 GHz CPU in the emulator would roughly equal a 100 MHz CPU
in the phone, for most loops or calculations. (Just an example, i
don't know.)
On 20
> Could someone give us the PC hardware of something that is running it
> the same speed as the real phone?
There is no "the phone". Android is designed to run on a variety of
hardware and we expect it will run on many hardware configurations.
Therefore the statement "running it the same speed as
I assume your referring to Issue 739, and not one of the other 18
issues. Hmm.
Well i have it working the way I want now so it doesn't matter much
now. Oddly I thought I could not use the SD as well, but it works I
just can't use inputstream.
On Aug 19, 9:12 pm, Steve Oldmeadow <[EMAIL PROTECTE
Could someone give us the PC hardware of something that is running it
the same speed as the real phone?
When will the PC not determine the performance as much? I assume they
could provide a sleep timer to provide semi accurate performance to a
phone with a profile until instrumentation is added f
On Aug 19, 6:54 pm, tberthel <[EMAIL PROTECTED]> wrote:
> Are the first phones going to be this fast?
The spend of the emulator depends entirely on the PC you are running
it on, so there is no way to correlate whatever speed you see with the
speed on an actual device. (And that is ignoring other
On Aug 20, 9:54 am, tberthel <[EMAIL PROTECTED]> wrote:
> Will the MediaPlayer work with inputstream for the final 1.0 version?
>
In the read me for 0.9 it says this will not be possible in 1.0.
There is an issue in the issue tracker related to this.
--~--~-~--~~~--
12 matches
Mail list logo
