Chris, I'm usually connected to my development targets via UART/Serial port. When I said disable all Android services (except ueventd and console) and reach to a console prompt, I meant reach to the point where your minimal Android (linux+ueventd+console) boots up and give you a prompt on your serial terminal. From there you can start Android services manually one by one and find out which one failed.
Hope I didn't confuse you much. Let me know if you have any more concerns. Regards, Amit Pundir On Mon, Sep 12, 2011 at 7:54 AM, lakehousetech <chris.l...@gmail.com> wrote: > Amit, > I've stumbled across the same problems while porting GB to a tablet > based on ARM MSM7227. I have set my loglevel to 8 in the init.rc, but > the last_kmsg from the boot failure doesn't give me enough information > to determine why my servicemanager is being killed 4 times in 4 > minutes. I read your recommendation about commenting out all services > and starting each manually to determine where the problem is, however > I don't understand what you mean when you refer to 'getting up to the > android console'. How are you able to monitor what is happening on the > device (and manually start services) without abd running and access > via terminal? I'm obviously missing something important when it comes > to debugging the startup process, so if you have any suggestions I > would be grateful. > > Chris > > On Aug 26, 2:49 am, Amit Pundir <pundira...@gmail.com> wrote: > > On Thu, Aug 25, 2011 at 2:47 AM, Radu Iscu <linke...@gmail.com> wrote: > > > Hello guys, > > > > > Here's the skinny: I'm trying to port the honeycomb to the ziio 7 and I > > > have to say that I can't even get the bare bones init.rc to boot. > > > I left the kernel partition intact as there's no point in messing with > that > > > (there's no recovery partition so the kernel doubles as a rescue). It > holds > > > a 2.6.29 kernel, which is the same as the default one in 3.0. > > > > > I never managed to get to a point where I have the new init/ueventd > > > working. The device gets stuck in a boot loop, never getting passed the > > > kernel logo. > > > > > I've tried putting exec logcat -d -f here and there in the init > process, > > > hoping for some clues, but that doesn't seem to be working. > > > Also there is nothing in /data/dontpanic/ > > > > > Any ideas about what I should do to get a clue about what's going on? > > > > Hi, I have been to this stage before where my system got stuck in boot > loop > > because my Android services was crashing. Try following modifications in > > your init.rc > > > > 1) Set your "loglevel to 8". That way you will get more logs. > > > > 2) Disable all the service except "ueventd" and "console". See if you are > > able to get up to Android prompt (Console). If you manage to get Console, > > then start the services manually (e.g. start debuggred) and find out the > > service which failed first. > > > > Regards, > > Amit Pundirhttp://arowboat.org > > > > > > > > > > > > > > > > > -- > > > Radu Iscu > > > Tel: 0742082607 > > > > > -- > > > 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 > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
