Actually, I already did it. Based on the latest Android kernel tree (2.6.27), patched using the diff between the stock 2.6.27 and the H&D 2.6.27 trees.
Unfortunately, it's still a no-go. : ( Cheers. P.S. How you got your trace logs...? On Dec 24, 10:08 pm, "Sameh M. Shaker" <samehshaker552...@gmail.com> wrote: > I think i've got some progress here... > According to the trace logs generated in /data/anr/traces.txt > > ----- pid 666 at 2008-12-24 14:02:11 ----- > Cmd line: android.process.acore > > DALVIK THREADS: > "main" prio=5 tid=3 NATIVE > | group="main" sCount=1 dsCount=0 s=0 obj=0x400113a8 > | sysTid=666 nice=0 sched=0/0 handle=-1093161860 > at android.os.BinderProxy.transact(Native Method) > at android.app.ActivityManagerProxy.handleApplicationError > (ActivityManagerNative.java:2023) > at com.android.internal.os.RuntimeInit.crash(RuntimeInit.java:302) > at com.android.internal.os.RuntimeInit > $UncaughtHandler.uncaughtException(RuntimeInit.java:75) > at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:853) > at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:850) > at dalvik.system.NativeStart.main(Native Method) > > "refqueuewor...@org.apache.http.impl.conn.tsccm.connpoolbyroute@4349a338" > daemon prio=5 tid=15 WAIT > | group="main" sCount=1 dsCount=0 s=0 obj=0x4349e380 > | sysTid=678 nice=0 sched=0/0 handle=547096 > at java.lang.Object.wait(Native Method) > - waiting on <0x86358> (a java.lang.ref.ReferenceQueue) > at java.lang.Object.wait(Object.java:195) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:113) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:82) > at org.apache.http.impl.conn.tsccm.RefQueueWorker.run > (RefQueueWorker.java:102) > at java.lang.Thread.run(Thread.java:935) > > "Binder Thread #2" prio=5 tid=13 NATIVE > | group="main" sCount=1 dsCount=0 s=0 obj=0x4348fc28 > | sysTid=677 nice=0 sched=0/0 handle=836096 > at dalvik.system.NativeStart.run(Native Method) > > "Binder Thread #1" prio=5 tid=11 NATIVE > | group="main" sCount=1 dsCount=0 s=0 obj=0x4348baa0 > | sysTid=676 nice=0 sched=0/0 handle=833696 > at android.database.sqlite.SQLiteDatabase.native_setLocale(Native > Method) > at android.database.sqlite.SQLiteDatabase.setLocale > (SQLiteDatabase.java:1470) > at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java: > 1424) > at android.database.sqlite.SQLiteDatabase.openDatabase > (SQLiteDatabase.java:537) > at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase > (SQLiteDatabase.java:558) > at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase > (SQLiteDatabase.java:551) > at android.app.ApplicationContext.openOrCreateDatabase > (ApplicationContext.java:427) > at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase > (SQLiteOpenHelper.java:98) > at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase > (SQLiteOpenHelper.java:158) > at android.content.SyncableContentProvider.query > (SyncableContentProvider.java:370) > at android.content.ContentProvider$Transport.bulkQuery > (ContentProvider.java:111) > at android.content.ContentProviderNative.onTransact > (ContentProviderNative.java:96) > at android.os.Binder.execTransact(Binder.java:276) > at dalvik.system.NativeStart.run(Native Method) > > "JDWP" daemon prio=5 tid=9 VMWAIT > | group="system" sCount=1 dsCount=0 s=0 obj=0x434892a0 > | sysTid=673 nice=0 sched=0/0 handle=831280 > at dalvik.system.NativeStart.run(Native Method) > > "Signal Catcher" daemon prio=5 tid=7 RUNNABLE > | group="system" sCount=0 dsCount=0 s=0 obj=0x434891e8 > | sysTid=671 nice=0 sched=0/0 handle=1013648 > at dalvik.system.NativeStart.run(Native Method) > > "HeapWorker" daemon prio=5 tid=5 VMWAIT > | group="system" sCount=1 dsCount=0 s=0 obj=0x4264c4a0 > | sysTid=667 nice=0 sched=0/0 handle=1013080 > at dalvik.system.NativeStart.run(Native Method) > > ----- end 666 ----- > > I think it's all about the binder driver within the kernel, I've > checked out hack&dev's kernel tree with the tag android... > However, the guys there seem to have back-ported older android patches > into 2.6.27... > > Just today I noticed that android git tree is now 2.6.27, which is > great news, I think now we can patch either the treo kernel tree or > the android kernel tree with the other's patches.... > > I'm a bit sleepy now, but I bet you understand what I mean... :) > > that's all for now... > > On Dec 18, 9:15 pm, Lo Yuk Fai <loyuk...@gmail.com> wrote: > > > Hi there. Some other people and me had been trying to do it not long > > ago but had probably the same problems. > > >http://groups.google.com/group/android-porting/browse_thread/thread/d... > > > Among other things, it seemed that everytime when SurfaceFlinger was > > about to launch, the whole process crashed and looped again. > > > I'm wondering whether the Android code as present supports the > > particular resolutions of Treo devices. > > > On Dec 18, 6:39 pm, "Sameh M. Shaker" <samehshaker552...@gmail.com> > > wrote: > > > > Thanks Rupesh, > > > > After googling for a while, I think I can skip the /sys errors also, i > > > believe they will only result in in correct battery information, so > > > now after some digging within the rest of the logs, I've managed to > > > resolve most of the problems, however, now I'm stuck with this: > > > > . > > > . > > > . > > > I/SystemServer( 615): Starting Content Manager. > > > W/ActivityManager( 615): Unable to start service Intent > > > { action=android.accounts.IAccountsService comp= > > > {com.google.android.googleapps/ > > > com.google.android.googleapps.GoogleLoginService} }: not found > > > W/AccountMonitor( 615): Couldn't connect to the accounts service > > > (Missing service?) > > > . > > > . > > > . > > > I/SystemServer( 615): Starting Location Manager. > > > D/LocationManagerService( 615): Constructed LocationManager Service > > > E/LocationManagerService( 615): Exception loading providers: > > > E/LocationManagerService( 615): java.lang.IllegalArgumentException: > > > key.length > 31 > > > E/LocationManagerService( 615): at > > > android.os.SystemProperties.get(SystemProperties.java:42) > > > . > > > . > > > . > > > W/ActivityManager( 615): Unable to start service Intent > > > { action=android.accounts.IAccountsService comp= > > > {com.google.android.googleapps/ > > > com.google.android.googleapps.GoogleLoginService} }: not found > > > W/AccountMonitor( 654): Couldn't connect to the accounts service > > > (Missing service?) > > > W/ResourceType( 654): Failure getting entry for 0x7f030006 (t=2 e=6) > > > in package 0: 0xffffffb5 > > > D/AndroidRuntime( 654): Shutting down VM > > > . > > > . > > > . > > > W/dalvikvm( 654): threadid=3: thread exiting with uncaught exception > > > (group=0x40010e28) > > > E/AndroidRuntime( 654): Uncaught handler: thread main exiting due to > > > uncaught exception > > > D/PhoneApp( 651): [PhoneIntfMgr] publish: > > > com.android.phone.phoneinterfacemana...@434d0130 > > > E/AndroidRuntime( 654): java.lang.RuntimeException: Unable to start > > > activity ComponentInfo{com.android.launcher/ > > > com.android.launcher.Launcher}: android.content.res.Resources > > > $NotFoundException: Resource ID #0x7f030006 > > > E/AndroidRuntime( 654): at > > > android.app.ActivityThread.performLaunchActivity(ActivityThread.java: > > > 2140) > > > . > > > . > > > . > > > W/ActivityManager( 615): Timeout of broadcast BroadcastRecord > > > {435caaa0 android.intent.action.BOOT_COMPLETED} - > > > receiver=android.os.binderpr...@435dc6c8 > > > W/ActivityManager( 615): Receiver during timeout: ResolveInfo > > > {435ca830 com.android.providers.media.MediaScannerReceiver p=0 o=0 > > > m=0x108000} > > > I/ActivityManager( 615): Start proc com.android.alarmclock for > > > broadcast com.android.alarmclock/.AlarmInitReceiver: pid=709 uid=10017 > > > gids={} > > > I/ActivityThread( 709): Publishing provider com.android.alarmclock: > > > com.android.alarmclock.AlarmProvider > > > I/ActivityManager( 615): Start proc android.process.im for broadcast > > > com.android.im/.receiver.ImServiceAutoStarter: pid=719 uid=10019 gids= > > > {3003} > > > I/ActivityManager( 615): Exiting empty application process > > > com.android.mms (android.os.binderpr...@4357af38) > > > I/Process ( 615): Sending signal. PID: 676 SIG: 9 > > > I/ActivityManager( 615): Exiting empty application process > > > com.android.calendar (android.os.binderpr...@435b1c68) > > > I/Process ( 615): Sending signal. PID: 684 SIG: 9 > > > I/ActivityManager( 615): Exiting empty application process > > > android.process.media (android.os.binderpr...@435dc6c8) > > > I/Process ( 615): Sending signal. PID: 699 SIG: 9 > > > D/ActivityManager( 615): Received spurious death notification for > > > thread android.os.binderpr...@4357af38 > > > D/ActivityManager( 615): Received spurious death notification for > > > thread android.os.binderpr...@435b1c68 > > > D/ActivityManager( 615): Received spurious death notification for > > > thread android.os.binderpr...@435dc6c8 > > > D/ImServiceAutoStarter( 719): onReceiveIntent > > > I/ActivityManager( 615): Exiting empty application process > > > com.android.alarmclock (android.os.binderpr...@435f3d20) > > > I/Process ( 615): Sending signal. PID: 709 SIG: 9 > > > D/ActivityManager( 615): Received spurious death notification for > > > thread android.os.binderpr...@435f3d20 > > > D/dalvikvm( 651): GC freed 2686 objects / 163056 bytes in 158ms > > > W/ActivityManager( 615): Activity pause timeout for HistoryRecord > > > {435cc5b0 {com.android.launcher/com.android.launcher.Launcher}} > > > > On Dec 18, 12:34 pm, Rupesh Gujare <rupesh.guj...@embinux.com> wrote: > > > > > Ignore /dev/pmem error, although not sure about /sys/* errors. > > > > > Regards, > > > > > -- > > > > Rupesh Gujarehttp://embinux.com > > > > > Sameh M. Shaker wrote: > > > > > Ok, I've got dropbear running now, and here are my findings, I'll only > > > > > paste the lines that seems to have errors from logcat output.... > > > > > > D/AndroidRuntime( 684): >>>>>>>>>>>>>> AndroidRuntime START > > > > > <<<<<<<<<<<<<< > > > > > . > > > > > . > > > > > . > > > > > E/MemoryHeapBase( 685): error opening /dev/pmem: No such file or > > > > > directory > > > > > I/SurfaceFlinger( 685): SurfaceFlinger's main thread ready to run. > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
