we ported android 2.3.1 to our architecture and board. the response time is terrible up now.
according to my profile, i think it's because drawing windows are very slow. i have 2 clues which drawed my idea on graphics: i) bootanimation is slow; ideally, bootanimation is 12fps. however, we can only got 1 fps. it takes much more time in GL-functions. ii) i profiled Laucher and analyzed the data in traceview. it turns out that over 95% time Launcher consumed are for android.view.ViewRoot.handleMessage. on just group, some one complained that pixelflinger was significantly slower except ARM. it's because arm has a codeflinger which generates code on-the-fly. we are doing the similar optimization right now. thanks, --lx On Thu, Sep 1, 2011 at 2:51 AM, Pradeep <[email protected]> wrote: > Hi, > > On my device the system regularly goes into a state where launch of > apps takes lot of time ( 5-10 secs ). This happens after using the > system for sometime and more often with apps with GLSurfaceView. > > My device config > > RAM - 384 MB > Resolution - 1024 * 600 > CPU - 1 Ghz Tegra dual core > > In this state I see a lot of processes being killed so I think > lowmemorykiller is running during this time. Also in adb shell cat / > proc/meminfo I see around 40-50 MB free but cache memory is on the > lower side. > > Any ideas ? > > Regards, > Pradeep > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
