Why don't you try building with ''tiny android'' $ BUILD_TINY_ANDROID=true make -j4 On Tue, Nov 6, 2012 at 6:59 AM, Alvin Wong <alvinhoc...@gmail.com> wrote:
> Simply make it fail to mount `/system`. Or you can remove all services > which references a binary on `/system`. > > Remember to add your test program as a service, or enable the shell so > that you can start your test. > > Sagar Shinde於 2012年11月3日星期六UTC+8下午6時31分58秒寫道： > >> Hi, >> For testing of our kernel driver in our production testing, we wanted to >> boot Android in few seconds (as less as possible). >> After flashing images to the device we wanted to test our drivers >> immediately after Android boot sequence gets completed. >> We test out drivers with our own native application which uses >> framebuffers. >> >> Now since setting up the framework takes most of the time during booting, >> I am trying to remove framework from the boot sequence. >> Also since we use framebuffers for our test application we do not need >> GUI or any other services started by system-server. >> >> To remove framework or GUI from boot sequence I tried stripping Android >> of system service from boot sequence. >> In init.rc, I dint pass "--system-server" parameter when zygote service >> is started so that system service is not started at all on boot. >> But this causes the Android to reboot. >> >> Could anyone please suggest clean way of removing system-server from boot >> sequence? >> Or any other method so that only Android kernel boots up and the >> framework doesnot bootup during boot sequence? >> >> Thanks, >> >> Sangi >> > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
