Our development environment also uses NFS root filesystem & we use u- boot to load the kernel Image.
The average boot time on OMAP 3430 with Android 1.6 SDK is 1 min 18 sec. The average boot time on OMAP 3430 with Android 2.1 SDK is 1 min 30 sec. We are also trying to explore areas of booting phase other than 1. Pre loading & 2. Scanning for boot time reduction purpose. Any pointers/hints will be highly appreciated. On May 13, 12:22 am, Tim Bird <[email protected]> wrote: > On 05/12/2010 06:33 AM, ashutosh deshmukh wrote: > > > Hi , > > > > We are actually working on regular boot time optimization only. The > > stats & logcat output that I share was for regular boot of Android on > > OMAP3430. > > > > So the stats does not represent the factory reset boot, the very very > > first boot of phone. > > > > The very very first boot on OMAP 3430 Board takes even longer, @85 sec > > for scanning dirs. > > I'm also looking at boot time optimizations on an OMAP. In my > case it's a 3530, running at 600 MHZ, and I'm getting numbers > similar to yours. But I'm doing crufty stuff like using an > NFS root filesystem - so my numbers are probably pretty bogus. > But I still don't see how the Nexus One would be getting only > 2 seconds apiece for these operations. (I have one, maybe > I'll have to do a comparison myself.) > > I'm very interested in optimizing the class preloading and > scanning, as I had previously identified these as problem > areas. Maybe we can compare notes? > > Dianne mentioned that some others had tried to optimize these > phases, and possibly ended up causing bugs. Does anyone have > experience with this that they can share? > -- Tim > > ============================= > Tim Bird > Architecture Group Chair, CE Linux Forum > Senior Staff Engineer, Sony Network Entertainment > ============================= > > -- > unsubscribe: [email protected] > website:http://groups.google.com/group/android-porting -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
