On Tue, Feb 1, 2011 at 5:10 PM, Tiago Maluta <[email protected]> wrote: > I'm checking the possibilities to validate my board through some > tests. Looking at documentation I read about factorytest mode where I > can analyze - individually - different subsystems of android > framework. I did not find documentation a steps to enter in this mode. > My initial step was use ADB to "setprop ro.factorytest 1" but, as > expect, didn't work. My second idea was create an application to enter > on factory test (editing Manifest file) mode but again I'd probably > violate some security design... Looking at system/core/init/init.c I > noted that "ro.factorytest" could be set depending on kernel > parameters, so I tried "androidboot.mode=factory" without success. > What's the correct (or recommended) way to get device running in > manufacturer test mode? >
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 behind factorytest. If I enable it how I'll test on my hardware? There are some pre-established codes to test android framework? (I found codes for specifics devices but not an generic list) Or should I create an application with my procedure (using something like [1]) . [1] http://developer.android.com/reference/android/content/Intent.html#ACTION_FACTORY_TEST --tm -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
