On Feb 10, 4:18 am, Tiago Maluta <[email protected]> wrote: > > I realized how to set "ro.factorytest" property by adding > androidboot.mode=factory to my kernel parameter. Besides the fact that > my board hangs on a loop, rebooting constantly... and the need to > discover why I'd like to get the practical idea behindfactorytest. If
I noticed the same thing on my system when I tried to boot into the FACTORY_TEST_LOW_LEVEL mode. It seems that without several of the services (such as the AccessibiltyManagerService), no UI elements can be displayed on the screen. I have a factory test application that overrides the home application, but the keyguard locking screen still tries to come up causing the SystemServer to die and restart constantly. I've had similar problems where the SystemServer tries to output logs using the DropBoxManager. Does anyone know whether the UI is supposed to work at FACTORY_TEST_LOW_LEVEL? I'm wondering just how low level "low level" is? Damian -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
