Hi All, This issue is solved after taking the patches specified in the below post.
http://groups.google.com/group/android-porting/browse_thread/thread/ce4c8939427c29cc?pli=1 Now i'm able to see the home screen of android. Is there any way to interact with the system through minicom. Regards, Raghu B On Mon, Jan 17, 2011 at 12:57 PM, Raghu N.B <[email protected]> wrote: > Hi All, > > Thanks Dianne. > > To be more specific, im seeing the exception related with Battery Interface > in logcat. Please explain me what are all the changes i have to take for > running android on a non battery device. I found a similar discussion > happened some time back in this forum. > http://www.mail-archive.com/[email protected]/msg12832.html > > But the patch suggested is pointing to specific file in the driver of OMAP. > Im using Davinci board and its not applicable in my case. Please explain me > with the changes required in my kernel and as well as File system. > > E/AndroidRuntime( 1785): *** FATAL EXCEPTION IN SYSTEM PROCESS: > android.server.d > E/AndroidRuntime( 1785): java.lang.UnsatisfiedLinkError: > native_update > E/AndroidRuntime( 1785): at > com.android.server.BatteryService.native_upd) > E/AndroidRuntime( 1785): at > com.android.server.BatteryService.update(Bat) > E/AndroidRuntime( 1785): at > com.android.server.BatteryService.<init>(Bat) > E/AndroidRuntime( 1785): at > com.android.server.ServerThread.run(SystemSe) > I/Process ( 1785): Sending signal. PID: 1785 SIG: > 9 > E/AndroidRuntime( 1785): Error reporting > crash > E/AndroidRuntime( 1785): > java.lang.NullPointerException > E/AndroidRuntime( 1785): at > android.os.DropBoxManager.isTagEnabled(DropB) > E/AndroidRuntime( 1785): at > com.android.server.am.ActivityManagerService) > E/AndroidRuntime( 1785): at > com.android.server.am.ActivityManagerService) > E/AndroidRuntime( 1785): at > com.android.internal.os.RuntimeInit$Uncaught) > E/AndroidRuntime( 1785): at > java.lang.ThreadGroup.uncaughtException(Thre) > E/AndroidRuntime( 1785): at > java.lang.ThreadGroup.uncaughtException(Thre) > D/BootAnimation( 1795): SurfaceFlinger died, > exiting... > I/ServiceManager( 1720): service 'meminfo' > died > I/ServiceManager( 1720): service 'batteryinfo' > died > > I also attached the logcat file for your reference. > > Regards, > Raghu B > > > On Mon, Jan 17, 2011 at 1:14 AM, Dianne Hackborn <[email protected]>wrote: > >> This really has nothing to do with the boot animation. It is just some >> crash during system boot; the boot animation is shown by the system while it >> is booting, so if it crashes then the boot anim gets restarted along with >> everything else. >> >> Anyway the key is just what error gets printed in the log when it crashes. >> >> On Sat, Jan 15, 2011 at 7:12 AM, Raghu N.B <[email protected]> wrote: >> >>> Dear All, >>> >>> Im porting android 2.2 on DM355 EVM board. Two weeks back, i faced a >>> problem "Service Manager Exits 4 times in 4 minute". I posted the problem in >>> this group and got some nice suggestion. That problem was due to that config >>> options are not properly enabled for compiling staging dirver. After >>> correcting that problem, now there is one more problem in bootanimation. >>> Bootanimation is getting restarted with other services like zygote and >>> media. I understand from the web (from similar kind of post), that this kind >>> of problem is due to memory constraint. I have 128MB total memory and also >>> almost 40 MB is free when the problem occurs. I also reduced the no of >>> services(like bootanim, RIL, ) in init.rc but that didnt help. Im using >>> NFS. >>> >>> Please help me in solving this issue. >>> >>> PS: i have attached the log file for your reference. >>> >>> Regards, >>> Raghu B >>> >>> -- >>> unsubscribe: >>> [email protected]<android-porting%[email protected]> >>> website: http://groups.google.com/group/android-porting >>> >> >> >> >> -- >> Dianne Hackborn >> Android framework engineer >> [email protected] >> >> Note: please don't send private questions to me, as I don't have time to >> provide private support, and so won't reply to such e-mails. All such >> questions should be posted on public forums, where I and others can see and >> answer them. >> >> > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
