Hello all,
How can I stop Android booting, once the kernel is up-and-running? Would
an empty "init.rc" do the job?
Regards,
Richard.
--
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
---
You received this message because
>From my own experience, "Android" is quite an abstract term. But yes, an
empty init.rc should give you a clean system (i.e. only basic kernel
processes/threads such as init, khelper, kworkers, binder).
I would leave the console and the adbd services though, so you get an
console and you still can
Hi,
Thanks, I'll give that a try then!
Regards,
Richard.
On 8 April 2014 17:44, Thiago C. Santini wrote:
> From my own experience, "Android" is quite an abstract term. But yes, an
> empty init.rc should give you a clean system (i.e. only basic kernel
> processes/threads such as init, khelper,
I believe there is also a headless android configuration which you specify
while building, essentially this would eliminate the surface flinger, audio
flinger and lot of other framework components so you will probably be left
with android kernel booting with a few of the android file system, yo
I also remember coming across some other interesting properties in
frameworks/base/services/java/com/android/server/SystemServer.java, a quick
grep yields:
String factoryTestStr = SystemProperties.get("ro.factorytest");
final boolean headless =
"1".equals(SystemProperties.get("ro.c
There is a factory test mode that attempts to do some of this, but you need
to dig deep in to the ActivityManager and friends to see what exactly
happens and how broken it might be.
On Wednesday, April 9, 2014 10:29:42 AM UTC-7, Somdutta Roy wrote:
>
> I believe there is also a headless android
