Yes, you are right, for many applications it may not be that critical.
It rather reflects my own disappointment with the fact that whereas
modern Nokia phones meet my real-time requirements with Java ME and
offer satisfactory performance for users without any need to mess with
native code, the
This I cannot confirm. The C64 emulator Mobile C64 runs with AFAIK
10-15% of the original C64 speed on a G1 with its 528 MHz CPU. On my
Samsung SGH-i600, with a 624 MHz CPU, the J2ME variant ran at close to
100% of the original C64 speed. This is a factor of 6-10 faster
although the device's CPU
Correlation is not causation. Yes android is slower than it could be.
But jazelle isn't the only reason. I wouldn't be surprised if the j2me
variant isn't even using jazelle as jits tend to be faster in a lot of
applications. A simple jit would probably give a 5-10x+ speed up
of the java (not
A simple jit would probably give a 5-10x+ speed up of the java
Yes, this is what I observed in my tests of Nokia 6680 and Sony
Ericsson X1 versus Android G1 for the same computational benchmark. It
is not good for battery life either when the CPU has to spend 5-10
times as many clock cycles for
Just remember that for a lot of applications most of the time is
spent calling native routines not executing java code. It isn't great
for battery life but it isn't as bad as you first think since in a lot
of apps, you spend almost all your time in wait loops so the CPU drain
isn't as
5 matches
Mail list logo
