Android traceview - behavior on Android 3.2 vs. 4.1 -

this question not meaning of data columns presented traceview - think understand that.

i noticed couple of things when looking traces in traceview captured on android 3.2 devices vs. android 4.1 device. question whether these known improvements made newer android releases, or if limitation of device, or if not artifacts meaningful.

the 2 devices/oses i'm comparing

• samsung galaxy tab 10.1 2 cores, running android 3.2
• google nexus 7 tablet 4 cores, running android 4.1

the first thing noticed traces captured on samsung galaxy tab android 3.2, there no "real time" columns, "cpu time" columns. know why?

the second thing noticed although samsung galaxy tab android 3.2 has 2 cores, traceview thread activity lines captures taken samsung galaxy tab show 1 thread running @ exact point in time. whereas for google nexus 7, multiple threads shown running simultaneously.

the app running both devices test app launches threads , each thread, including main ui thread, loops awhile calculating fibonacci sequence. there no reason why 2 of these threads can't run simultaneously, on samsung galaxy tab or other device 2 cores. furthermore, time takes perform fixed amount of calculation same each thread when there 2 threads vs. when there 1 - 2 threads must executing simultaneously expected. when there 3 threads on 2-core device, time takes each thread calculation increased 50% expect.

so, think limitation of trace capturing on samsung galaxy tab 10.1 running android 3.2. on device "real" apps lot of calls, traceview appears show 2 threads running simultaneously if zoom way in, activity interleaved , never 2 threads shown active @ same time.