15 May
2011
15 May
'11
12:35 a.m.
Libor,
Log outputs from Android emulator are: times()-begin: c1=13829 tm1.tms_stime + tm1.tms_cstime=18, tm1.tms_utime + tm1.tms_cutime=638 times()-end: c2=13966 tm2.tms_stime + tm2.tms_cstime=18, tm2.tms_utime + tm2.tms_cutime=670 real 0.001s, cpu 0.000s (23.9%), user 0.000s, system 0.000s thread_clock: wall=1376ms, cpu=318ms
Could the problem be with the Android emulator rather than Android itself? Google seems to find multiple reports of problems with the Android emulator related to time. --Beman