Does anyone have any ideas why Slingplayer wont work on any of the ROMs for the GTablet?
As soon as you click on the icon to launch the app, the screen goes black and then goes right back to the launcher.
Any ideas?
Thanks in advance!
boostenmkiv said:
Does anyone have any ideas why Slingplayer wont work on any of the ROMs for the GTablet?
As soon as you click on the icon to launch the app, the screen goes black and then goes right back to the launcher.
Any ideas?
Thanks in advance!
Click to expand...
Click to collapse
I tried sideloding it with the same results. I could not find it when searching the market. I did read today that it is working on the Archos 101. So, I would think there should be a way to get it working.
birchs said:
I tried sideloding it with the same results. I could not find it when searching the market. I did read today that it is working on the Archos 101. So, I would think there should be a way to get it working.
Click to expand...
Click to collapse
Did you try running logcat then starting the app to see if it is logging what's failing??
I am running tapntap lite 2 and I can run my slingbox client. I have to try it several times but it does load. May sound crazy but when I run quick reboot right before I start trying i have better luck getting it to run. After it runs the first time its fine till a full reboot.
wlawyer said:
I am running tapntap lite 2 and I can run my slingbox client. I have to try it several times but it does load. May sound crazy but when I run quick reboot right before I start trying i have better luck getting it to run. After it runs the first time its fine till a full reboot.
Click to expand...
Click to collapse
thanks for the info. I'll be more persistent to see if i can get it to work.
jtbnet said:
Did you try running logcat then starting the app to see if it is logging what's failing??
Click to expand...
Click to collapse
sorry, that's beyond my skill level at the moment
wlawyer said:
I am running tapntap lite 2 and I can run my slingbox client. I have to try it several times but it does load. May sound crazy but when I run quick reboot right before I start trying i have better luck getting it to run. After it runs the first time its fine till a full reboot.
Click to expand...
Click to collapse
Holy Crap that worked. I just had to try it a few times and finally the log in screen came up. Once it is running works nicely! Thanks for the tip!
sling player
It works, but you have to try to launch it atleast 10x, then it catches. Not sure what's going on with that, but it does work great after that.
Hopefully someone has the SDK loaded and can run 'adb logcat' and maybe catch the errors the times it fails... it might be a fairly obvious error if we were to see it
The Dish Network Remote app (probably nearly the same thing) has the same problem when using the Zpad firmware, but it works fine using the TnT firmware.
jtbnet et al.
Wow, adb was MUCH harder to get working on this tablet than any previous android phone i've worked on. (mt3g,n1,DI,Droid,DX)
anyhow, here is the log:
D/WifiService( 884): acquireWifiLockLocked: WifiLock{SlingWifiTag type=1 [email protected]}
D/dalvikvm( 4940): Trying to load lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
D/dalvikvm( 4940): Added shared lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngine.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I/dalvikvm( 4940): "main" prio=5 tid=1 NATIVE
I/dalvikvm( 4940): | group="main" sCount=0 dsCount=0 s=N obj=0x4001d900 self=0xccd8
I/dalvikvm( 4940): | sysTid=4940 nice=1 sched=0/0 cgrp=default handle=-1345017812
I/dalvikvm( 4940): | schedstat=( 57004000 11633000 68 )
I/dalvikvm( 4940): at java.lang.Runtime.nativeLoad(Native Method)
I/dalvikvm( 4940): at java.lang.Runtime.loadLibrary(Runtime.java:448)
I/dalvikvm( 4940): at java.lang.System.loadLibrary(System.java:557)
I/dalvikvm( 4940): at com.slingmedia.slingPlayer.SPEKHandler.PlayerEngine.PlayerEngine.<clinit>(PlayerEngine.java:1330)
I/dalvikvm( 4940): at com.slingmedia.slingPlayer.SlingPlayerApplication.onCreate(SlingPlayerApplication.java:-1)
I/dalvikvm( 4940): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:969)
I/dalvikvm( 4940): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4244)
I/dalvikvm( 4940): at android.app.ActivityThread.access$3000(ActivityThread.java:125)
I/dalvikvm( 4940): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2071)
I/dalvikvm( 4940): at android.os.Handler.dispatchMessage(Handler.java:99)
I/dalvikvm( 4940): at android.os.Looper.loop(Looper.java:123)
I/dalvikvm( 4940): at android.app.ActivityThread.main(ActivityThread.java:4627)
I/dalvikvm( 4940): at java.lang.reflect.Method.invokeNative(Native Method)
I/dalvikvm( 4940): at java.lang.reflect.Method.invoke(Method.java:521)
I/dalvikvm( 4940): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
I/dalvikvm( 4940): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
I/dalvikvm( 4940): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 4940):
E/dalvikvm( 4940): VM aborting
I/DEBUG ( 837): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 837): Build fingerprint: 'nvidia/harmony/harmony/:2.2/FRF91/eng.build.20101107.131556:eng/'
I/DEBUG ( 837): pid: 4940, tid: 4940 >>> com.slingmedia.slingPlayer <<<
I/DEBUG ( 837): signal 11 (SIGSEGV), fault addr deadd00d
I/DEBUG ( 837): r0 00000026 r1 afd148c9 r2 afd148c9 r3 00000000
I/DEBUG ( 837): r4 808a13f4 r5 80883ad0 r6 80e5462c r7 80cf2dc9
I/DEBUG ( 837): r8 80816fc0 r9 0000ccd8 10 4208bc7c fp 00000000
I/DEBUG ( 837): ip deadd00d sp bef11150 lr afd1591f pc 808417a4 cpsr 20000030
I/DEBUG ( 837): d0 0000006a42d40000 d1 3ff0000042d40000
I/DEBUG ( 837): d2 0000000050baf6de d3 0000000000000000
I/DEBUG ( 837): d4 0000001a000000b4 d5 3fe999999999999a
I/DEBUG ( 837): d6 3fe8000000000000 d7 3eaaaaab3f800000
I/DEBUG ( 837): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 837): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 837): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 837): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 837): scr 80000012
I/DEBUG ( 837):
I/DEBUG ( 837): #00 pc 000417a4 /system/lib/libdvm.so
I/DEBUG ( 837): #01 pc 00032bea /system/lib/libdvm.so
I/DEBUG ( 837): #02 pc 00033a4c /system/lib/libdvm.so
I/DEBUG ( 837): #03 pc 00033ad4 /system/lib/libdvm.so
I/DEBUG ( 837): #04 pc 000f2dec /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so
I/DEBUG ( 837): #05 pc 00049c28 /system/lib/libdvm.so
I/DEBUG ( 837): #06 pc 000635d8 /system/lib/libdvm.so
I/DEBUG ( 837): #07 pc 0001bd58 /system/lib/libdvm.so
I/DEBUG ( 837): #08 pc 00022744 /system/lib/libdvm.so
I/DEBUG ( 837): #09 pc 000215e0 /system/lib/libdvm.so
I/DEBUG ( 837): #10 pc 0005bcb6 /system/lib/libdvm.so
I/DEBUG ( 837): #11 pc 0005bee8 /system/lib/libdvm.so
I/DEBUG ( 837): #12 pc 00067b48 /system/lib/libdvm.so
I/DEBUG ( 837): #13 pc 000694d2 /system/lib/libdvm.so
I/DEBUG ( 837): #14 pc 00018c28 /system/lib/libdvm.so
I/DEBUG ( 837): #15 pc 00022744 /system/lib/libdvm.so
I/DEBUG ( 837): #16 pc 000215e0 /system/lib/libdvm.so
I/DEBUG ( 837): #17 pc 0005be78 /system/lib/libdvm.so
I/DEBUG ( 837): #18 pc 000643fe /system/lib/libdvm.so
I/DEBUG ( 837): #19 pc 0001bd58 /system/lib/libdvm.so
I/DEBUG ( 837): #20 pc 00022744 /system/lib/libdvm.so
I/DEBUG ( 837): #21 pc 000215e0 /system/lib/libdvm.so
I/DEBUG ( 837): #22 pc 0005bcb6 /system/lib/libdvm.so
I/DEBUG ( 837): #23 pc 00047362 /system/lib/libdvm.so
I/DEBUG ( 837): #24 pc 0003a51c /system/lib/libdvm.so
I/DEBUG ( 837): #25 pc 0002db88 /system/lib/libandroid_runtime.so
I/DEBUG ( 837): #26 pc 0002ec7c /system/lib/libandroid_runtime.so
I/DEBUG ( 837): #27 pc 00008caa /system/bin/app_process
I/DEBUG ( 837): #28 pc 0000d3d8 /system/lib/libc.so
I/DEBUG ( 837):
I/DEBUG ( 837): code around pc:
I/DEBUG ( 837): 80841784 18612006 f7d418a2 2000eff8 e950f7d5
I/DEBUG ( 837): 80841794 58234808 b1036bdb 20264798 c018f8df
I/DEBUG ( 837): 808417a4 0000f88c e9b6f7d5 fffe26dc 0005fc78
I/DEBUG ( 837): 808417b4 fffe5950 0000039c deadd00d f8dfb40e
I/DEBUG ( 837): 808417c4 b503c02c 490aa200 aa03188b 1b04f852
I/DEBUG ( 837):
I/DEBUG ( 837): code around lr:
I/DEBUG ( 837): afd158fc 4b0db5f7 490da200 2600189b 585c4602
I/DEBUG ( 837): afd1590c 686768a5 f9b5e008 b120000c 46289201
I/DEBUG ( 837): afd1591c 9a014790 35544306 37fff117 6824d5f3
I/DEBUG ( 837): afd1592c d1ed2c00 bdfe4630 0002ca24 000000d4
I/DEBUG ( 837): afd1593c fb01b570 b086f602 9004460c a804a901
I/DEBUG ( 837):
I/DEBUG ( 837): stack:
I/DEBUG ( 837): bef11110 00000015
I/DEBUG ( 837): bef11114 afd148f9 /system/lib/libc.so
I/DEBUG ( 837): bef11118 afd42498 /system/lib/libc.so
I/DEBUG ( 837): bef1111c afd43b70 /system/lib/libc.so
I/DEBUG ( 837): bef11120 00000000
I/DEBUG ( 837): bef11124 afd1591f /system/lib/libc.so
I/DEBUG ( 837): bef11128 afd148c9 /system/lib/libc.so
I/DEBUG ( 837): bef1112c afd148c9 /system/lib/libc.so
I/DEBUG ( 837): bef11130 afd14920 /system/lib/libc.so
I/DEBUG ( 837): bef11134 808a13f4 /system/lib/libdvm.so
I/DEBUG ( 837): bef11138 80883ad0 /system/lib/libdvm.so
I/DEBUG ( 837): bef1113c 80e5462c /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so
I/DEBUG ( 837): bef11140 80cf2dc9 /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so
I/DEBUG ( 837): bef11144 afd1492b /system/lib/libc.so
I/DEBUG ( 837): bef11148 df002777
I/DEBUG ( 837): bef1114c e3a070ad
I/DEBUG ( 837): #00 bef11150 808a13f4 /system/lib/libdvm.so
I/DEBUG ( 837): bef11154 80832bef /system/lib/libdvm.so
I/DEBUG ( 837): #01 bef11158 808a13f4 /system/lib/libdvm.so
I/DEBUG ( 837): bef1115c 80833a51 /system/lib/libdvm.so
I/BootReceiver( 884): Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE)
D/Zygote ( 839): Process 4940 terminated by signal (11)
D/dalvikvm( 884): GC_FOR_MALLOC freed 4784 objects / 1053840 bytes in 45ms
D/WifiService( 884): releaseWifiLockLocked: WifiLock{SlingWifiTag type=1 [email protected]}
I/ActivityManager( 884): Process com.slingmedia.slingPlayer (pid 4940) has died.
I/UsageStats( 884): Unexpected resume of com.android.launcher while already resumed in com.slingmedia.slingPlayer
W/InputManagerService( 884): Window already focused, ignoring focus gain of: [email protected]
D/WifiService( 884): ACTION_BATTERY_CHANGED pluggedType: 0
Well the short of this...
D/WifiService( 884): acquireWifiLockLocked: WifiLock{SlingWifiTag type=1 [email protected]}
D/dalvikvm( 4940): Trying to load lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
D/dalvikvm( 4940): Added shared lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I/dalvikvm( 4940): "main" prio=5 tid=1 NATIVE
I/dalvikvm( 4940): | group="main" sCount=0 dsCount=0 s=N obj=0x4001d900 self=0xccd8
I/dalvikvm( 4940): | sysTid=4940 nice=1 sched=0/0 cgrp=default handle=-1345017812
I/dalvikvm( 4940): | schedstat=( 57004000 11633000 68 )
I/dalvikvm( 4940): at java.lang.Runtime.nativeLoad(Native Method)
...
The call to a function ('com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer') in libspsdk.so is failing based on the way the call was made...
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I'm not sure why if you run this 10 or more times it finally works... But JAVA/JNI is not my forte... hopefully this info will provide more info to someone more versed in this...
disabled stagefright in build.prop and slingplayer streams flawlessly and opens on the first try.... with stagefright enabled it takes about 10 tries before davlik vm stops calling abort, and even then it plays choppy... anyone elsewant to disable stagefright and see if you get results like mine?
im running latest tnt lite with experimental upgrade
Sent from my GTablet-TnT-Lite using Tapatalk
TheTruth said:
disabled stagefright in build.prop and slingplayer streams flawlessly and opens on the first try.... with stagefright enabled it takes about 10 tries before davlik vm stops calling abort, and even then it plays choppy... anyone elsewant to disable stagefright and see if you get results like mine?
im running latest tnt lite with experimental upgrade
Sent from my GTablet-TnT-Lite using Tapatalk
Click to expand...
Click to collapse
Can someone tell me how to disable stagefright ? Thanks!
make sure you have root.
use rootexplorer or similar and browse to the /system/ folder on your internal storage.
click the mount r/w button, click on the build.prop file and open it as a text file.
scroll down in the build.prop file and change the values from true to false... save then reboot.
this will make slingplayer playback smooth but will not impact the other issue of davlik aborting the process (which is why we have to keep opening the app till it sticks)
Sent from my GTablet-TnT-Lite using Tapatalk
TheTruth said:
make sure you have root.
use rootexplorer or similar and browse to the /system/ folder on your internal storage.
click the mount r/w button, click on the build.prop file and open it as a text file.
scroll down in the build.prop file and change the values from true to false... save then reboot.
this will make slingplayer playback smooth but will not impact the other issue of davlik aborting the process (which is why we have to keep opening the app till it sticks)
Sent from my GTablet-TnT-Lite using Tapatalk
Click to expand...
Click to collapse
I disabled all stagefright option in the build.prop but no change after a reboot.
wlawyer said:
I disabled all stagefright option in the build.prop but no change after a reboot.
Click to expand...
Click to collapse
odd, with stagefright sling is a slideshow... stagefright off and it plays like a dream... but still no impact on the abort () called by dalvik vm... perhaps a setting added to build.prop that disables jni checking would work... but that would make the system unstable if bad or unsupported code happened to be around..
Sent from my GTablet-TnT-Lite using Tapatalk
jtbnet said:
The call to a function ('com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer') in libspsdk.so is failing based on the way the call was made...
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I'm not sure why if you run this 10 or more times it finally works... But JAVA/JNI is not my forte... hopefully this info will provide more info to someone more versed in this...
Click to expand...
Click to collapse
I was doing some research on this error and found this.
it looks like you are using "." as a
separator instead of "/". ("." is Java surface syntax for separating
package names, but "/" is what is used at the API boundary.) So, I
would check to make sure that your JNI registration code is
well-formed.
Click to expand...
Click to collapse
I still don't have my tablet, but sling player is an important feature to me on it.
TheTruth said:
odd, with stagefright sling is a slideshow... stagefright off and it plays like a dream... but still no impact on the abort () called by dalvik vm... perhaps a setting added to build.prop that disables jni checking would work... but that would make the system unstable if bad or unsupported code happened to be around..
Sent from my GTablet-TnT-Lite using Tapatalk
Click to expand...
Click to collapse
Try to add "dalvik.vm.checkjni=false" to build.prop and reboot. That might do it.
Edit, if that doesn't work try "ro.kernel.android.checkjni=false"
If this works when set, it may explain problems with other apps people are having. According to here, jni checking should only be enabled on dev units.
I just checked boot.img and "-Xcheck:jni" is passed when it starts.
Adam B. said:
I was doing some research on this error and found this.
I still don't have my tablet, but sling player is an important feature to me on it.
I extracted and hex edited the library to use slashes for that class. Can someone with adb test this out (you'll probably have to uninstall the old version first)? I tested it on my droid and it worked, but it never had a problem on there.
Click to expand...
Click to collapse
Tested the edited sling apk for you. Still took about 6 or 7 attempts before it opened.
Also it forced closed after I selected my slingbox...never made it to video
harpua1980 said:
Tested the edited sling apk for you. Still took about 6 or 7 attempts before it opened.
Also it forced closed after I selected my slingbox...never made it to video
Click to expand...
Click to collapse
Thanks.
I think we're better off with the build.prop fix anyway. Can you test that?
Related
Hey all,
I finally got around to hacking my phone over the weekend. It went quite well (thanks to cyanogen, and all the people that help make this work).
I have firmware 4.0.4 installed (I did a wipe, firmware install, then another wipe), but the Gallery/Album crashes every time I try to start it. I can even take pictures with the camera, but when I try to view them through the gallery button, it crashes back to the camera - the pictures are there, though, I can view them via USB mounting.
I tried to get the debugger to attach to it, but it just waits forever.
I read that the album could be crashing when it tries to create thumbnails, but I completely emptied the fat32 partition, and it still has this problem.
I grabbed the logs, and they just show a segfault. I'm a Unix developer by day, but don't know what to do with an Android stack trace (don't have the dev tools for this set up).
Any help would be greatly appreciated. I tried searching the forums, and found nothing similar.
Code:
09-13 22:56:04.107 I/ActivityManager( 130): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.htc.album/com.htc.album.GalleryPicker} }
09-13 22:56:04.417 I/ActivityManager( 130): Start proc com.htc.album for activity com.htc.album/.GalleryPicker: pid=558 uid=10020 gids={1006, 3003, 2001}
09-13 22:56:04.877 I/ActivityManager( 130): Process android.process.media (pid 546) has died.
09-13 22:56:04.997 I/DEBUG ( 110): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-13 22:56:04.997 I/DEBUG ( 110): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRC1/150275:user/ota-rel-keys,release-keys'
09-13 22:56:04.997 I/DEBUG ( 110): pid: 558, tid: 558 >>> com.htc.album <<<
09-13 22:56:04.997 I/DEBUG ( 110): signal 11 (SIGSEGV), fault addr 42a1bf38
09-13 22:56:04.997 I/DEBUG ( 110): r0 42a1a730 r1 00000007 r2 434c4b50 r3 00000604
09-13 22:56:04.997 I/DEBUG ( 110): r4 42a1bf38 r5 001805b0 r6 ad079e1c r7 00001810
09-13 22:56:04.997 I/DEBUG ( 110): r8 00003071 r9 0000bc70 10 4104ac48 fp 00000000
09-13 22:56:04.997 I/DEBUG ( 110): ip 00000000 sp bed58538 lr ad05aae9 pc ad05a4d0 cpsr 00000030
09-13 22:56:06.567 W/GTalkService( 210): [DataMsgMgr] parseDataMessageIntent: not including app data -- key is reserved: account, -------
09-13 22:56:06.587 I/DEBUG ( 110): #00 pc 0005a4d0 /system/lib/libdvm.so
09-13 22:56:06.587 I/DEBUG ( 110): #01 pc 0005aae4 /system/lib/libdvm.so
09-13 22:56:06.587 I/DEBUG ( 110): #02 pc 000325ba /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #03 pc 0003a110 /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #04 pc 0004ea0e /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #05 pc 0003aec4 /system/lib/libdvm.so
09-13 22:56:06.617 I/DEBUG ( 110): #06 pc 000131d8 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #07 pc 00017a30 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #08 pc 000174c4 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #09 pc 00049a64 /system/lib/libdvm.so
09-13 22:56:06.627 I/DEBUG ( 110): #10 pc 00050b50 /system/lib/libdvm.so
09-13 22:56:06.637 D/Sync ( 130): Received network tickle for --------
09-13 22:56:06.637 I/DEBUG ( 110): #11 pc 000131d8 /system/lib/libdvm.so
09-13 22:56:06.657 I/DEBUG ( 110): #12 pc 00017a30 /system/lib/libdvm.so
09-13 22:56:06.657 I/DEBUG ( 110): #13 pc 000174c4 /system/lib/libdvm.so
09-13 22:56:06.657 I/DEBUG ( 110): #14 pc 00049c52 /system/lib/libdvm.so
09-13 22:56:06.667 I/DEBUG ( 110): #15 pc 0003844c /system/lib/libdvm.so
09-13 22:56:06.707 I/DEBUG ( 110): #16 pc 00027c9c /system/lib/libandroid_runtime.so
09-13 22:56:06.707 I/DEBUG ( 110): #17 pc 00028796 /system/lib/libandroid_runtime.so
09-13 22:56:06.707 I/DEBUG ( 110): #18 pc 00008c9e /system/bin/app_process
09-13 22:56:06.717 I/DEBUG ( 110): #19 pc 0000be8a /system/lib/libc.so
09-13 22:56:06.737 I/DEBUG ( 110): #20 pc b00015e4 /system/bin/linker
09-13 22:56:06.737 I/DEBUG ( 110): stack:
09-13 22:56:06.737 I/DEBUG ( 110): bed584f8 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed584fc 00000036
09-13 22:56:06.737 I/DEBUG ( 110): bed58500 000081a4 /system/bin/app_process
09-13 22:56:06.737 I/DEBUG ( 110): bed58504 00000001
09-13 22:56:06.737 I/DEBUG ( 110): bed58508 000003e8
09-13 22:56:06.737 I/DEBUG ( 110): bed5850c 00002716
09-13 22:56:06.737 I/DEBUG ( 110): bed58510 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58514 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58518 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed5851c 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58520 afe3bb40
09-13 22:56:06.737 I/DEBUG ( 110): bed58524 afe0ec98 /system/lib/libc.so
09-13 22:56:06.737 I/DEBUG ( 110): bed58528 00000000
09-13 22:56:06.737 I/DEBUG ( 110): bed5852c afe0eba8 /system/lib/libc.so
09-13 22:56:06.737 I/DEBUG ( 110): bed58530 df002777
09-13 22:56:06.737 I/DEBUG ( 110): bed58534 e3a070ad
09-13 22:56:06.737 I/DEBUG ( 110): #00 bed58538 001805b0 [heap]
09-13 22:56:06.737 I/DEBUG ( 110): bed5853c c0000000
09-13 22:56:06.737 I/DEBUG ( 110): bed58540 00003071
09-13 22:56:06.757 I/DEBUG ( 110): bed58544 afe0b85b /system/lib/libc.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58548 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed5854c 00000019
09-13 22:56:06.767 I/DEBUG ( 110): bed58550 00000019
09-13 22:56:06.767 I/DEBUG ( 110): bed58554 ad060aec /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58558 42a1a730 /data/dalvik-cache/[email protected]@[email protected]
09-13 22:56:06.767 I/DEBUG ( 110): bed5855c ad071516 /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58560 001805b0 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58564 ad079e1c /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58568 429c8000 /data/dalvik-cache/[email protected]@[email protected]
09-13 22:56:06.767 I/DEBUG ( 110): bed5856c 001805b0 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58570 00053000 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58574 ad05aae9 /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): #01 bed58578 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed5857c 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed58580 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed58584 00053000 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed58588 001805b0 [heap]
09-13 22:56:06.767 I/DEBUG ( 110): bed5858c 00000000
09-13 22:56:06.767 I/DEBUG ( 110): bed58590 00001000
09-13 22:56:06.767 I/DEBUG ( 110): bed58594 ad079e1c /system/lib/libdvm.so
09-13 22:56:06.767 I/DEBUG ( 110): bed58598 bed585b0 [stack]
09-13 22:56:06.767 I/DEBUG ( 110): bed5859c 00000019
09-13 22:56:06.767 I/DEBUG ( 110): bed585a0 bed5864c [stack]
09-13 22:56:06.767 I/DEBUG ( 110): bed585a4 ad0325bf /system/lib/libdvm.so
09-13 22:56:06.927 I/ActivityManager( 130): Stopping service: com.android.providers.subscribedfeeds/.SubscribedFeedsIntentService
09-13 22:56:07.577 I/DEBUG ( 110): debuggerd committing suicide to free the zombie!
09-13 22:56:07.587 D/Zygote ( 112): Process 558 terminated by signal (11)
09-13 22:56:07.587 I/ActivityManager( 130): Process com.htc.album (pid 558) has died.
when using any rom, do not wipe after flashing it. if you wipe you must flash another rom. just boot into recovery wipe one more time, then flash the cm 4.0.4 rom. all should be fine.
I did another wipe, and re-applied 4.0.4
The gallery still crashes immediately.
debuggerd committing suicide to free the zombie!
that is hilarious. though back to the problem at hand.
did you check the md5sum to see if your download is correct? if not, then it could provide problems.
Yup, the md5sum of the image on /sdcard is what it should be.
I've heard a couple of people say 4.04 has issues. Try 4.02.
I can manage without the gallery for a while. Really, if this is a firmware issue I'd like to help debug and fix it if I can. What's my next step?
http://code.google.com/p/cyanogenmod/issues/list
thats where cyan's debugging is going on.. see if your issue is there and provide them feedback
I'd looked over there before I'd posted here, but I didn't see anything like my issue. As a developer myself, there are few things more annoying than when a bug is filed against my code when it turns out to be user error - I was just trying to avoid that
Ok, so I got this after reinstalling Cyanogen's 4.1.10.1 after installing a theme on top of it. So far I've tried wiping, restoring a backup, and installing multiple builds, no success.
Heres the logcat:
Code:
W/dalvikvm( 136): JNI_CreateJavaVM failed
E/AndroidRuntime( 136): JNI_CreateJavaVM failed
D/AndroidRuntime( 140):
D/AndroidRuntime( 140): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 140): CheckJNI is OFF
D/dalvikvm( 140): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
D/dalvikvm( 140): DexOpt: --- BEGIN 'services.jar' (bootstrap=1) ---
I/DEBUG ( 116): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 116): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRC1/150275:
user/ota-rel-keys,release-keys'
I/DEBUG ( 116): pid: 142, tid: 142 >>> /system/bin/dexopt <<<
I/DEBUG ( 116): signal 11 (SIGSEGV), fault addr 44b60a42
I/DEBUG ( 116): r0 0000ea74 r1 415d0028 r2 41613df0 r3 44b60a42
I/DEBUG ( 116): r4 41051528 r5 00016510 r6 4000c358 r7 bedef9dc
I/DEBUG ( 116): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 116): ip ad07a0d0 sp bedef980 lr ad053349 pc ad052c5c cpsr 000
00030
I/DEBUG ( 116): #00 pc 00052c5c /system/lib/libdvm.so
I/DEBUG ( 116): #01 pc 00053344 /system/lib/libdvm.so
I/DEBUG ( 116): #02 pc 00053506 /system/lib/libdvm.so
I/DEBUG ( 116): #03 pc 00053c2e /system/lib/libdvm.so
I/DEBUG ( 116): #04 pc 00053e3e /system/lib/libdvm.so
I/DEBUG ( 116): #05 pc 00054352 /system/lib/libdvm.so
I/DEBUG ( 116): #06 pc 000471da /system/lib/libdvm.so
I/DEBUG ( 116): #07 pc 000476d4 /system/lib/libdvm.so
I/DEBUG ( 116): #08 pc 000478b4 /system/lib/libdvm.so
I/DEBUG ( 116): #09 pc 00008e20 /system/bin/dexopt
I/DEBUG ( 116): #10 pc 00008ed6 /system/bin/dexopt
I/DEBUG ( 116): #11 pc 0000bf12 /system/lib/libc.so
I/DEBUG ( 116): #12 pc b00016cc /system/bin/linker
I/DEBUG ( 116): stack:
I/DEBUG ( 116): bedef940 00000000
I/DEBUG ( 116): bedef944 afe0ec28 /system/lib/libc.so
I/DEBUG ( 116): bedef948 000119c4 [heap]
I/DEBUG ( 116): bedef94c afe0ed18 /system/lib/libc.so
I/DEBUG ( 116): bedef950 00000000
I/DEBUG ( 116): bedef954 afe0ec28 /system/lib/libc.so
I/DEBUG ( 116): bedef958 000119c0 [heap]
I/DEBUG ( 116): bedef95c ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef960 000014b4
I/DEBUG ( 116): bedef964 0000216c
I/DEBUG ( 116): bedef968 410514f0 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef96c ad051ba5 /system/lib/libdvm.so
I/DEBUG ( 116): bedef970 410514f0 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef974 00016510 [heap]
I/DEBUG ( 116): bedef978 df002777
I/DEBUG ( 116): bedef97c e3a070ad
I/DEBUG ( 116): #00 bedef980 ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef984 41051504 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef988 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef98c 4000c358 /dev/ashmem/mspace/dalvik-heap/0 (del
eted)
I/DEBUG ( 116): bedef990 4191a361 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef994 00016510 [heap]
I/DEBUG ( 116): bedef998 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef99c ad053349 /system/lib/libdvm.so
I/DEBUG ( 116): #01 bedef9a0 00002bd0
I/DEBUG ( 116): bedef9a4 000000dc
I/DEBUG ( 116): bedef9a8 00000000
I/DEBUG ( 116): bedef9ac afe0afbb /system/lib/libc.so
I/DEBUG ( 116): bedef9b0 42409e54 /data/dalvik-cache/[email protected]@s
[email protected]
I/DEBUG ( 116): bedef9b4 0000003a
I/DEBUG ( 116): bedef9b8 bedef9dc [stack]
I/DEBUG ( 116): bedef9bc 00000abe
I/DEBUG ( 116): bedef9c0 00000460
I/DEBUG ( 116): bedef9c4 00000b05
I/DEBUG ( 116): bedef9c8 00000002
I/DEBUG ( 116): bedef9cc 00000070
I/DEBUG ( 116): bedef9d0 415fdbf0 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef9d4 4000c3f4 /dev/ashmem/mspace/dalvik-heap/0 (del
eted)
I/DEBUG ( 116): bedef9d8 afe3bb8c
I/DEBUG ( 116): bedef9dc 00000abe
I/DEBUG ( 116): bedef9e0 00000000
I/DEBUG ( 116): bedef9e4 000be364
I/DEBUG ( 116): bedef9e8 00000722
I/DEBUG ( 116): bedef9ec ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef9f0 00016578 [heap]
I/DEBUG ( 116): bedef9f4 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef9f8 00000000
I/DEBUG ( 116): bedef9fc ad05350b /system/lib/libdvm.so
W/dalvikvm( 140): DexOpt: --- END 'services.jar' --- status=0x000b, process fai
led
E/dalvikvm( 140): Unable to extract+optimize DEX from '/system/framework/servic
es.jar'
D/dalvikvm( 140): Failed on '/system/framework/services.jar' (boot=1)
D/dalvikvm( 140): VM cleaning up
D/dalvikvm( 140): LinearAlloc 0x0 used 4100 of 4194304 (0%)
and repeats over and over... forever!
I've searched through the forums and on google and nothing relevant came up. Please help!
Ok, tried deleting the Dalvik-Cache from recovery console with no success. Formatted my linux parts and bam! fixed.
If your sdcard is partitioned try wiping your ext3, then trying flashing cm 4.0.4, if it still boot loops then you may need to go back to rc-29 and root again
david1171 said:
If your sdcard is partitioned try wiping your ext3, then trying flashing cm 4.0.4, if it still boot loops then you may need to go back to rc-29 and root again
Click to expand...
Click to collapse
Whats up david, glad you could finally join us. Must be nice to sleep in til noon.
nick_karstedt said:
Ok, tried deleting the Dalvik-Cache from recovery console with no success. Formatted my linux parts and bam! fixed.
Click to expand...
Click to collapse
Ive got the same problem along with several other people on this forum but none of us have been able to sort this out.
So pray tell how do you format linux parts?
i have hit a wall here with 4.2.8
info
was runing 4.2.7.1 with no issues
wiped data,flashed 1.6 recovery then installed 4.2.8
my g1 didnt want to connect to google to register, kept getting a cant connect to server or something so i reflashed
finally got that to go and now once i got it booted and started installing apps i got a repeating black screen like home fc'd silently then home reappears and goes black.. enless loop....
also i am not running hard spl... i have had issues when updating manually and with cmupdater in the past, never been able to update and keep all my apps .. can not having hardspl be the cause?? or am i just a tool that is missing something lol
this is what i get from logcat after i get up and running in 4.2.8 during the mentioned loop
Code:
I/DEBUG ( 2037): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 2037): pid: 2038, tid: 2052 >>> android.process.acore <<<
I/DEBUG ( 2037): signal 7 (SIGBUS), fault addr 474cf665
I/DEBUG ( 2037): r0 00000004 r1 04034b50 r2 06054b50 r3 474cf665
I/DEBUG ( 2037): r4 a9d4bb60 r5 0004b665 r6 0034c800 r7 47484000
I/DEBUG ( 2037): r8 45d9fda0 r9 42787d40 10 42787d28 fp 00311b50
I/DEBUG ( 2037): ip 80000000 sp 45d9fc70 lr a9d2c507 pc a9d2c24c cpsr 200
00030
I/DEBUG ( 2037): #00 pc 0002c24c /system/lib/libutils.so
I/DEBUG ( 2037): #01 pc 0002c502 /system/lib/libutils.so
I/DEBUG ( 2037): #02 pc 00020282 /system/lib/libutils.so
I/DEBUG ( 2037): #03 pc 00021276 /system/lib/libutils.so
I/DEBUG ( 2037): #04 pc 00021324 /system/lib/libutils.so
I/DEBUG ( 2037): #05 pc 000219f2 /system/lib/libutils.so
I/DEBUG ( 2037): #06 pc 00021b46 /system/lib/libutils.so
I/DEBUG ( 2037): #07 pc 0003a822 /system/lib/libandroid_runtime.so
I/DEBUG ( 2037): #08 pc 0000f1f4 /system/lib/libdvm.so
I/DEBUG ( 2037): #09 pc 00037fa4 /system/lib/libdvm.so
I/DEBUG ( 2037): #10 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 2037): #11 pc 00019890 /system/lib/libdvm.so
I/DEBUG ( 2037): #12 pc 00018d4c /system/lib/libdvm.so
I/DEBUG ( 2037): #13 pc 0004d73c /system/lib/libdvm.so
I/DEBUG ( 2037): #14 pc 0004d76a /system/lib/libdvm.so
I/DEBUG ( 2037): #15 pc 00041d60 /system/lib/libdvm.so
I/DEBUG ( 2037): #16 pc 0000ff88 /system/lib/libc.so
I/DEBUG ( 2037): #17 pc 0000fa5c /system/lib/libc.so
I/DEBUG ( 2037): stack:
I/DEBUG ( 2037): 45d9fc30 00000003
I/DEBUG ( 2037): 45d9fc34 afe3ba58
I/DEBUG ( 2037): 45d9fc38 003746f8 [heap]
I/DEBUG ( 2037): 45d9fc3c c0000000
I/DEBUG ( 2037): 45d9fc40 45d9fda0
I/DEBUG ( 2037): 45d9fc44 afe0be93 /system/lib/libc.so
I/DEBUG ( 2037): 45d9fc48 00311b50 [heap]
I/DEBUG ( 2037): 45d9fc4c ad04d745 /system/lib/libdvm.so
I/DEBUG ( 2037): 45d9fc50 0034cbd8 [heap]
I/DEBUG ( 2037): 45d9fc54 0000002e
I/DEBUG ( 2037): 45d9fc58 00000000
I/DEBUG ( 2037): 45d9fc5c 45d9fda0
I/DEBUG ( 2037): 45d9fc60 42787d40
I/DEBUG ( 2037): 45d9fc64 42787d28
I/DEBUG ( 2037): 45d9fc68 df002777
I/DEBUG ( 2037): 45d9fc6c e3a070ad
I/DEBUG ( 2037): #00 45d9fc70 003746f8 [heap]
I/DEBUG ( 2037): 45d9fc74 afe1b743 /system/lib/libc.so
I/DEBUG ( 2037): 45d9fc78 003af168 [heap]
I/DEBUG ( 2037): 45d9fc7c 0004b67b [heap]
I/DEBUG ( 2037): 45d9fc80 00000000
I/DEBUG ( 2037): 45d9fc84 a9d231d7 /system/lib/libutils.so
I/DEBUG ( 2037): 45d9fc88 0000004a
I/DEBUG ( 2037): 45d9fc8c 00000000
I/DEBUG ( 2037): 45d9fc90 00000000
I/DEBUG ( 2037): 45d9fc94 0004b67b [heap]
I/DEBUG ( 2037): 45d9fc98 00000000
I/DEBUG ( 2037): 45d9fc9c 0034cbd8 [heap]
I/DEBUG ( 2037): 45d9fca0 0000004a
I/DEBUG ( 2037): 45d9fca4 00000001
I/DEBUG ( 2037): 45d9fca8 a9d4bb60 /system/lib/libutils.so
I/DEBUG ( 2037): 45d9fcac 0034c800 [heap]
I/DEBUG ( 2037): 45d9fcb0 a9d4bb60 /system/lib/libutils.so
I/DEBUG ( 2037): 45d9fcb4 0000004a
I/DEBUG ( 2037): 45d9fcb8 003af168 [heap]
I/DEBUG ( 2037): 45d9fcbc a9d2c507 /system/lib/libutils.so
I/DEBUG ( 2037): #01 45d9fcc0 0004b67b [heap]
I/DEBUG ( 2037): 45d9fcc4 00000001
I/DEBUG ( 2037): 45d9fcc8 0034cbd8 [heap]
I/DEBUG ( 2037): 45d9fccc 0004b67b [heap]
I/DEBUG ( 2037): 45d9fcd0 00341e08 [heap]
I/DEBUG ( 2037): 45d9fcd4 a9d4bb60 /system/lib/libutils.so
I/DEBUG ( 2037): 45d9fcd8 00341e08 [heap]
I/DEBUG ( 2037): 45d9fcdc 00000000
I/DEBUG ( 2037): 45d9fce0 4b25bfff
I/DEBUG ( 2037): 45d9fce4 a9d20287 /system/lib/libutils.so
I/DEBUG ( 2037): debuggerd committing suicide to free the zombie!
I/DEBUG ( 2053): debuggerd: Dec 2 2009 20:35:30
I/ActivityManager( 154): Process android.process.acore (pid 2038) has died.
I/WindowManager( 154): WIN DEATH: Window{43d6b410 com.android.launcher/com.andr
oid.launcher.Launcher paused=false}
I/ActivityManager( 154): Start proc android.process.acore for activity com.andr
oid.launcher/.Launcher: pid=2054 uid=10013 gids={3003, 3002, 3001, 1015}
D/Zygote ( 135): Process 2038 terminated by signal (7)
W/UsageStats( 154): Something wrong here, didn't expect com.android.launcher to
be resumed
I/ActivityThread( 2054): Publishing provider com.android.globalsearch.Suggestion
Provider: com.android.globalsearch.SuggestionProvider
I/ActivityThread( 2054): Publishing provider com.android.launcher.settings: com.
android.launcher.LauncherProvider
I/ActivityThread( 2054): Publishing provider com.google.android.providers.enhanc
edgooglesearch: com.google.android.providers.enhancedgooglesearch.SuggestionProv
ider
I/ActivityThread( 2054): Publishing provider user_dictionary: com.android.provid
ers.userdictionary.UserDictionaryProvider
I/ActivityThread( 2054): Publishing provider com.android.globalsearch.stats: com
.android.globalsearch.StatsProvider
I/ActivityThread( 2054): Publishing provider contacts;call_log: com.android.prov
iders.contacts.GoogleContactsProvider
I/ActivityThread( 2054): Publishing provider applications: com.android.providers
.applications.ApplicationsProvider
I/ActivityThread( 2054): Publishing provider im: com.android.providers.im.ImProv
ider
D/dalvikvm( 2054): GC freed 3596 objects / 264784 bytes in 97ms
D/dalvikvm( 2054): GC freed 1096 objects / 62432 bytes in 90ms
D/dalvikvm( 2054): GC freed 240 objects / 12304 bytes in 85ms
D/dalvikvm( 2054): GC freed 48 objects / 2720 bytes in 85ms
D/HomeLoaders( 2054): load applications
D/HomeLoaders( 2054): loading user items
D/HomeLoaders( 2054): --> starting workspace loader
D/HomeLoaders( 2054): ----> running workspace loader (1)
W/InputManagerService( 154): Got RemoteException sending setActive(false) notif
ication to pid 2038 uid 10013
I/ActivityManager( 154): Displayed activity com.android.launcher/.Launcher: 188
4 ms (total 1884 ms)
D/HomeLoaders( 2054): --> done loading workspace
D/HomeLoaders( 2054): ----> worskpace items=7
D/HomeLoaders( 2054): ----> worskpace widgets=0
D/HomeLoaders( 2054): ----> items cloned, ready to refresh UI
D/HomeLoaders( 2054): ----> onDesktopItemsLoaded()
D/Launcher( 2054): ------> binding 7 items
D/Launcher( 2054): ------> binding 0 widgets
D/Launcher( 2054): ------> start binding items
D/HomeLoaders( 2054): ----> loading applications from workspace loader
D/HomeLoaders( 2054): --> starting applications loader unlocked
D/HomeLoaders( 2054): --> starting applications loader
D/HomeLoaders( 2054): ----> running applications loader (1)
D/dalvikvm( 2054): GC freed 1363 objects / 72504 bytes in 101ms
I/DEBUG ( 2053): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
any help greatly appreciated
Ok, I've had this phone rooted and setup with Cyanogen for months. Probably 7 or 8 months. Last night, it started having some issues, so I opened up the Cyanogen updater and told it to get the latest one, given I was running a rather old version. It downloads it, installs, goes to restart, and gets stuck on the boot screen (in my case, the Rogers screen).
Fast forward to today, I have been flashing and installing all sorts of different firmwares, trying to get it working. 0 luck. Started looking at the log, and this is the output of 4.2.7 with adb's logcat. Any help would be greatly appreciated.
Code:
E/AndroidRuntime( 422): JNI_CreateJavaVM failed
D/AndroidRuntime( 423):
D/AndroidRuntime( 423): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 423): CheckJNI is OFF
E/dalvikvm( 423): Unable to find constructor for StackTraceElement
D/dalvikvm( 423): VM cleaning up
D/dalvikvm( 423): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 423): JNI_CreateJavaVM failed
E/AndroidRuntime( 423): JNI_CreateJavaVM failed
E/vold ( 131): Unable to read framework command (Bad file number)
E/vold ( 131): Error processing framework command (Bad file number)
D/AndroidRuntime( 424):
D/AndroidRuntime( 424): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 424): CheckJNI is OFF
E/dalvikvm( 424): Unable to find constructor for StackTraceElement
D/dalvikvm( 424): VM cleaning up
D/dalvikvm( 424): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 424): JNI_CreateJavaVM failed
E/AndroidRuntime( 424): JNI_CreateJavaVM failed
D/AndroidRuntime( 425):
D/AndroidRuntime( 425): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 425): CheckJNI is OFF
E/dalvikvm( 425): Unable to find constructor for StackTraceElement
D/dalvikvm( 425): VM cleaning up
D/dalvikvm( 425): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 425): JNI_CreateJavaVM failed
E/AndroidRuntime( 425): JNI_CreateJavaVM failed
D/AndroidRuntime( 426):
D/AndroidRuntime( 426): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 426): CheckJNI is OFF
E/dalvikvm( 426): Unable to find constructor for StackTraceElement
D/dalvikvm( 426): VM cleaning up
D/dalvikvm( 426): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 426): JNI_CreateJavaVM failed
E/AndroidRuntime( 426): JNI_CreateJavaVM failed
D/AndroidRuntime( 427):
D/AndroidRuntime( 427): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 427): CheckJNI is OFF
E/dalvikvm( 427): Unable to find constructor for StackTraceElement
D/dalvikvm( 427): VM cleaning up
D/dalvikvm( 427): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 427): JNI_CreateJavaVM failed
E/AndroidRuntime( 427): JNI_CreateJavaVM failed
D/AndroidRuntime( 428):
D/AndroidRuntime( 428): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 428): CheckJNI is OFF
E/dalvikvm( 428): Unable to find constructor for StackTraceElement
D/dalvikvm( 428): VM cleaning up
D/dalvikvm( 428): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 428): JNI_CreateJavaVM failed
E/AndroidRuntime( 428): JNI_CreateJavaVM failed
D/AndroidRuntime( 429):
D/AndroidRuntime( 429): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 429): CheckJNI is OFF
E/dalvikvm( 429): Unable to find constructor for StackTraceElement
D/dalvikvm( 429): VM cleaning up
D/dalvikvm( 429): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 429): JNI_CreateJavaVM failed
E/AndroidRuntime( 429): JNI_CreateJavaVM failed
D/AndroidRuntime( 430):
D/AndroidRuntime( 430): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 430): CheckJNI is OFF
E/dalvikvm( 430): Unable to find constructor for StackTraceElement
D/dalvikvm( 430): VM cleaning up
D/dalvikvm( 430): LinearAlloc 0x0 used 20780 of 5242880 (0%)
W/dalvikvm( 430): JNI_CreateJavaVM failed
E/AndroidRuntime( 430): JNI_CreateJavaVM failed
Etc, etc, etc
what cyanogen rom were you on before you downloaded the rom from the updater?
oshizzle1991 said:
what cyanogen rom were you on before you downloaded the rom from the updater?
Click to expand...
Click to collapse
I don't remember an exact version, I want to say it was 4.1.x
You need to flash the htc recovery image the cyanogen ROM. You will probably need to wipe and format your ext partition also.
cloverdale said:
You need to flash the htc recovery image the cyanogen ROM. You will probably need to wipe and format your ext partition also.
Click to expand...
Click to collapse
Already done that with most of the latest flashes. That would be the one from the signed-dream_devphone_userdebug-ota- ***.zip, correct? If so, I have flashed with 14721, and repartitioned several times with sdparted.
I actually have it now at the "Welcome to T-Mobile G1" screen...only problem is that all the applications are dropping like flies.
Force close on com.android.mms, com.android.phone, come.android.process.gapps
Skipping through that and going to the home screen brings..
Force close on com.google.android.apps.uploader, and no home screen at all. Just a black screen and a notification bar.
Log output as such:
Code:
I/ActivityThread( 1531): Publishing provider com.android.launcher.settings: com.android.launcher.LauncherProvider
I/dalvikvm( 1531): Unknown chunk 0x99b00203 (??), size=-268302586 in aux data area
D/dalvikvm( 155): GC freed 9667 objects / 842832 bytes in 397ms
I/CheckinService( 155): Sending checkin request (15493 bytes)...
D/Zygote ( 130): Process 1525 terminated by signal (11)
I/ActivityManager( 155): Process com.google.process.gapps (pid 1525) has died.
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 87783ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 11887ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 21887ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 31886ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 57778ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 89045409464320ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 67776ms
W/ActivityManager( 155): Scheduling restart of crashed service com.google.android.googleapps/.GoogleLoginService in 77776ms
I/DEBUG ( 1535): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1535): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys'
I/DEBUG ( 1535): pid: 1531, tid: 1531 >>> android.process.acore <<<
I/DEBUG ( 1535): signal 11 (SIGSEGV), fault addr 35434798
I/DEBUG ( 1535): r0 0000004d r1 00000007 r2 d1918f9e r3 3c0081c4
I/DEBUG ( 1535): r4 002c90a0 r5 35434798 r6 ad07ff50 r7 f0020710
I/DEBUG ( 1535): r8 ad00f380 r9 0000bc20 10 4104eb9c fp 00000000
I/DEBUG ( 1535): ip afbc30c8 sp be8ae598 lr afbc1055 pc ad05ecc0 cpsr 20000030
I/ActivityManager( 155): Start proc com.google.process.gapps for restart com.google.process.gapps: pid=1539 uid=10020 gids={3003}
I/ActivityThread( 1539): Publishing provider com.google.settings: com.google.android.providers.settings.GoogleSettingsProvider
I/ActivityThread( 1539): Publishing provider gmail-ls: com.google.android.providers.gmail.MailProvider
I/dalvikvm( 1539): Unknown chunk 0x01190119 (), size=18415897 in aux data area
I/DEBUG ( 1535): #00 pc 0005ecc0 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 pc 0005f3b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #02 pc 000341cc /system/lib/libdvm.so
I/DEBUG ( 1535): #03 pc 0003c540 /system/lib/libdvm.so
I/DEBUG ( 1535): #04 pc 000525b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #05 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #06 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #07 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #08 pc 0004d468 /system/lib/libdvm.so
I/DEBUG ( 1535): #09 pc 00054f4c /system/lib/libdvm.so
I/DEBUG ( 1535): #10 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #11 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #12 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #13 pc 0004d77c /system/lib/libdvm.so
I/DEBUG ( 1535): #14 pc 0003a74c /system/lib/libdvm.so
I/DEBUG ( 1535): #15 pc 00028374 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #16 pc 00028e82 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #17 pc 00008c9e /system/bin/app_process
I/DEBUG ( 1535): #18 pc 0000c4c2 /system/lib/libc.so
I/DEBUG ( 1535): #19 pc b00018c6 /system/bin/linker
I/DEBUG ( 1535): stack:
I/DEBUG ( 1535): be8ae558 00000000
I/DEBUG ( 1535): be8ae55c 0001f032 [heap]
I/DEBUG ( 1535): be8ae560 000081a4 /system/bin/app_process
I/DEBUG ( 1535): be8ae564 00000001
I/DEBUG ( 1535): be8ae568 000003e8
I/DEBUG ( 1535): be8ae56c 00002718
I/DEBUG ( 1535): be8ae570 00000000
I/DEBUG ( 1535): be8ae574 d1918f9e
I/DEBUG ( 1535): be8ae578 00000000
I/DEBUG ( 1535): be8ae57c 002c90a0 [heap]
I/DEBUG ( 1535): be8ae580 45414088 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae584 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae588 f0020706
I/DEBUG ( 1535): be8ae58c ad05eca7 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae590 df002777
I/DEBUG ( 1535): be8ae594 e3a070ad
I/DEBUG ( 1535): #00 be8ae598 00000099
I/DEBUG ( 1535): be8ae59c 000000b0
I/DEBUG ( 1535): be8ae5a0 00000002
I/DEBUG ( 1535): be8ae5a4 00000003
I/DEBUG ( 1535): be8ae5a8 f0020706
I/DEBUG ( 1535): be8ae5ac 00000028
I/DEBUG ( 1535): be8ae5b0 00000028
I/DEBUG ( 1535): be8ae5b4 ad06587c /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5b8 45414090 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5bc ad076eb2 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c0 002c90a0 [heap]
I/DEBUG ( 1535): be8ae5c4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c8 453e4000 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5cc 002c90a0 [heap]
I/DEBUG ( 1535): be8ae5d0 00030090 [heap]
I/DEBUG ( 1535): be8ae5d4 ad05f3b9 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 be8ae5d8 00000000
I/DEBUG ( 1535): be8ae5dc 00000000
I/DEBUG ( 1535): be8ae5e0 00000000
I/DEBUG ( 1535): be8ae5e4 00030090 [heap]
I/DEBUG ( 1535): be8ae5e8 002c90a0 [heap]
I/DEBUG ( 1535): be8ae5ec 00000000
I/DEBUG ( 1535): be8ae5f0 00000400
I/DEBUG ( 1535): be8ae5f4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5f8 be8ae610 [stack]
I/DEBUG ( 1535): be8ae5fc 00000028
I/DEBUG ( 1535): be8ae600 be8ae6a8 [stack]
I/DEBUG ( 1535): be8ae604 ad0341d1 /system/lib/libdvm.so
I/CheckinService( 155): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
I/ActivityManager( 155): Process android.process.acore (pid 1531) has died.
I/ActivityManager( 155): Start proc android.process.acore for restart android.process.acore: pid=1545 uid=10008 gids={3003, 3002, 3001, 1006, 1015}
D/Zygote ( 130): Process 1531 terminated by signal (11)
I/DEBUG ( 1535): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1535): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys'
I/DEBUG ( 1535): pid: 1539, tid: 1539 >>> com.google.process.gapps <<<
I/DEBUG ( 1535): signal 11 (SIGSEGV), fault addr 45d67248
I/DEBUG ( 1535): r0 0000004b r1 00000007 r2 d1918f9e r3 0046404a
I/DEBUG ( 1535): r4 0011b998 r5 45d67248 r6 ad07ff50 r7 01190128
I/DEBUG ( 1535): r8 ad00f380 r9 0000bc20 10 4104eb9c fp 00000000
I/DEBUG ( 1535): ip afbc30c8 sp be8ae598 lr afbc1055 pc ad05ecc0 cpsr 00000030
I/ActivityThread( 1545): Publishing provider com.android.globalsearch.stats: com.android.globalsearch.StatsProvider
I/ActivityThread( 1545): Publishing provider contacts;call_log: com.android.providers.contacts.GoogleContactsProvider
I/DEBUG ( 1535): #00 pc 0005ecc0 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 pc 0005f3b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #02 pc 000341cc /system/lib/libdvm.so
I/DEBUG ( 1535): #03 pc 0003c540 /system/lib/libdvm.so
I/DEBUG ( 1535): #04 pc 000525b4 /system/lib/libdvm.so
I/DEBUG ( 1535): #05 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #06 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #07 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #08 pc 0004d468 /system/lib/libdvm.so
I/DEBUG ( 1535): #09 pc 00054f4c /system/lib/libdvm.so
I/DEBUG ( 1535): #10 pc 00013f58 /system/lib/libdvm.so
I/DEBUG ( 1535): #11 pc 00019888 /system/lib/libdvm.so
I/DEBUG ( 1535): #12 pc 00018d5c /system/lib/libdvm.so
I/DEBUG ( 1535): #13 pc 0004d77c /system/lib/libdvm.so
I/DEBUG ( 1535): #14 pc 0003a74c /system/lib/libdvm.so
I/ActivityThread( 1545): Publishing provider applications: com.android.providers.applications.ApplicationsProvider
I/DEBUG ( 1535): #15 pc 00028374 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #16 pc 00028e82 /system/lib/libandroid_runtime.so
I/DEBUG ( 1535): #17 pc 00008c9e /system/bin/app_process
I/DEBUG ( 1535): #18 pc 0000c4c2 /system/lib/libc.so
I/DEBUG ( 1535): #19 pc b00018c6 /system/bin/linker
I/DEBUG ( 1535): stack:
I/DEBUG ( 1535): be8ae558 00000000
I/DEBUG ( 1535): be8ae55c 0001f04d [heap]
I/DEBUG ( 1535): be8ae560 000081a4 /system/bin/app_process
I/DEBUG ( 1535): be8ae564 00000001
I/DEBUG ( 1535): be8ae568 000003e8
I/DEBUG ( 1535): be8ae56c 00002724
I/DEBUG ( 1535): be8ae570 00000000
I/DEBUG ( 1535): be8ae574 d1918f9e
I/DEBUG ( 1535): be8ae578 00000000
I/DEBUG ( 1535): be8ae57c 0011b998 [heap]
I/DEBUG ( 1535): be8ae580 44bd7120 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae584 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae588 01190119
I/DEBUG ( 1535): be8ae58c ad05eca7 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae590 df002777
I/DEBUG ( 1535): be8ae594 e3a070ad
I/DEBUG ( 1535): #00 be8ae598 00000001
I/DEBUG ( 1535): be8ae59c 00000019
I/DEBUG ( 1535): be8ae5a0 00000001
I/DEBUG ( 1535): be8ae5a4 00000019
I/DEBUG ( 1535): be8ae5a8 01190119
I/DEBUG ( 1535): be8ae5ac 0000001f
I/DEBUG ( 1535): be8ae5b0 0000001f
I/DEBUG ( 1535): be8ae5b4 ad06587c /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5b8 44bd7128 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5bc ad076eb2 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c0 0011b998 [heap]
I/DEBUG ( 1535): be8ae5c4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5c8 44b94000 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1535): be8ae5cc 0011b998 [heap]
I/DEBUG ( 1535): be8ae5d0 00043128 [heap]
I/DEBUG ( 1535): be8ae5d4 ad05f3b9 /system/lib/libdvm.so
I/DEBUG ( 1535): #01 be8ae5d8 00000000
I/DEBUG ( 1535): be8ae5dc 00000000
I/DEBUG ( 1535): be8ae5e0 00000000
I/DEBUG ( 1535): be8ae5e4 00043128 [heap]
I/DEBUG ( 1535): be8ae5e8 0011b998 [heap]
I/DEBUG ( 1535): be8ae5ec 00000000
I/DEBUG ( 1535): be8ae5f0 00000400
I/DEBUG ( 1535): be8ae5f4 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1535): be8ae5f8 be8ae610 [stack]
I/DEBUG ( 1535): be8ae5fc 0000001f
I/DEBUG ( 1535): be8ae600 be8ae6a8 [stack]
I/DEBUG ( 1535): be8ae604 ad0341d1 /system/lib/libdvm.so
Try again in this order:
Remove the sdcard (with the phone off) and format with gparted (do a fresh format at least to the ext). Place the sdcard in the phone and boot to recovery. Wipe everything, then flash the htc recovery, then WITHOUT A REBOOT, flash cyanogen.
I had something similar happen to me last week, and I had to repeat the above a few times, but it eventually worked.
cloverdale said:
Try again in this order:
Remove the sdcard (with the phone off) and format with gparted (do a fresh format at least to the ext). Place the sdcard in the phone and boot to recovery. Wipe everything, then flash the htc recovery, then WITHOUT A REBOOT, flash cyanogen.
I had something similar happen to me last week, and I had to repeat the above a few times, but it eventually worked.
Click to expand...
Click to collapse
Is there a huge difference if I mount the sdcard from the phone (via the console and echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) vs directly in the computer (given that the phone is the only way I currently have to access the sdcard.
Regardless, going to give your instructions a few steps right now with my method of loading it up, just to test. Wish me luck.
Result is the same, stuff dies and blank, black, useless home screen. Another interesting tidbit to this story is the fact that even though I am connected to a network, and show as having a full signal and 3G connection....no outgoing data seems to be going on.
Well, another update, but a bit of a sad one, in my opinion.
I got it working. But not with Cyanogen. I used this rom, and it installed and worked fine.
This is strange, it is way beyond me why this would be happening to you. lbcoder is one of the only people I can think of on here that would probably know.
Hello,
since the weekend m G1 (with Cyanogen 4.2.13) is suffering some bad errors.
It happens, that it just freezes.
activating adb logcat it gives me this output (which gets repeated in a two seconds cycle).
D/AndroidRuntime( 1476):
D/AndroidRuntime( 1476): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1476): CheckJNI is OFF
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/core.jar
(/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/core.j
ar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/ext.jar
(/data/dalvik-cache/[email protected][email protected]@classes.dex)
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/ext.ja
r'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/framewor
k.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/framew
ork.jar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/android.
policy.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/androi
d.policy.jar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/services
.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/servic
es.jar'
E/dalvikvm( 1476): ERROR: no valid entries found in bootclasspath '/system/frame
work/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/
framework/android.policy.jar:/system/framework/services.jar'
D/dalvikvm( 1476): VM cleaning up
D/dalvikvm( 1476): LinearAlloc 0x0 used 4100 of 5242880 (0%)
W/dalvikvm( 1476): JNI_CreateJavaVM failed
E/AndroidRuntime( 1476): JNI_CreateJavaVM failed
Click to expand...
Click to collapse
Does anyone have a hint whats failing here?
-Radioactive Man
Just a guess, but probably an I/O error.
opt header write failed: I/O error
Click to expand...
Click to collapse
and what does it mean? broken sdcard? broken internal memory? something else broken?
Now I get another output:
D/AndroidRuntime( 1392):
D/AndroidRuntime( 1392): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1392): CheckJNI is OFF
I/DEBUG ( 1342): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1342): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,re
lease-keys'
I/DEBUG ( 1342): pid: 1392, tid: 1392 >>> zygote <<<
I/DEBUG ( 1342): signal 7 (SIGBUS), fault addr 41a2633b
I/DEBUG ( 1342): r0 00015d80 r1 41a2633b r2 00015d18 r3 00352313
I/DEBUG ( 1342): r4 ad07ff50 r5 00015d80 r6 41746010 r7 00000000
I/DEBUG ( 1342): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 1342): ip ad080214 sp be94b828 lr ad058471 pc ad057bd6 cpsr 20000030
I/DEBUG ( 1342): #00 pc 00057bd6 /system/lib/libdvm.so
I/DEBUG ( 1342): #01 pc 0005846c /system/lib/libdvm.so
I/DEBUG ( 1342): #02 pc 0005867e /system/lib/libdvm.so
I/DEBUG ( 1342): #03 pc 00040690 /system/lib/libdvm.so
I/DEBUG ( 1342): #04 pc 0003681c /system/lib/libdvm.so
I/DEBUG ( 1342): #05 pc 000384b2 /system/lib/libdvm.so
I/DEBUG ( 1342): #06 pc 00028d7e /system/lib/libandroid_runtime.so
I/DEBUG ( 1342): #07 pc 00008c9e /system/bin/app_process
I/DEBUG ( 1342): #08 pc 0000c4c2 /system/lib/libc.so
I/DEBUG ( 1342): #09 pc b00018c6 /system/bin/linker
I/DEBUG ( 1342): stack:
I/DEBUG ( 1342): be94b7e8 000081a4 /system/bin/app_process
I/DEBUG ( 1342): be94b7ec 00000001
I/DEBUG ( 1342): be94b7f0 00000000
I/DEBUG ( 1342): be94b7f4 00000000
I/DEBUG ( 1342): be94b7f8 afe3bc10
I/DEBUG ( 1342): be94b7fc afe0f370 /system/lib/libc.so
I/DEBUG ( 1342): be94b800 00000000
I/DEBUG ( 1342): be94b804 afe0f280 /system/lib/libc.so
I/DEBUG ( 1342): be94b808 41a5f3b0 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b80c ad05f32f /system/lib/libdvm.so
I/DEBUG ( 1342): be94b810 00001df2
I/DEBUG ( 1342): be94b814 00001fff
I/DEBUG ( 1342): be94b818 416d4028 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b81c ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b820 df002777
I/DEBUG ( 1342): be94b824 e3a070ad
I/DEBUG ( 1342): #00 be94b828 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b82c 00015d80 [heap]
I/DEBUG ( 1342): be94b830 ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b834 ad056843 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b838 00000002
I/DEBUG ( 1342): be94b83c ad06587c /system/lib/libdvm.so
I/DEBUG ( 1342): be94b840 be94b874 [stack]
I/DEBUG ( 1342): be94b844 ad074a04 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b848 00015a60 [heap]
I/DEBUG ( 1342): be94b84c 00000000
I/DEBUG ( 1342): be94b850 0000bc20 [heap]
I/DEBUG ( 1342): be94b854 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b858 00015d80 [heap]
I/DEBUG ( 1342): be94b85c ad058471 /system/lib/libdvm.so
I/DEBUG ( 1342): #01 be94b860 00015a58 [heap]
I/DEBUG ( 1342): be94b864 00015a60 [heap]
I/DEBUG ( 1342): be94b868 ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b86c 00000000
I/DEBUG ( 1342): be94b870 ad06587c /system/lib/libdvm.so
I/DEBUG ( 1342): be94b874 41746010 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b878 000111b8 [heap]
I/DEBUG ( 1342): be94b87c ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b880 00000354
I/DEBUG ( 1342): be94b884 0000a9c0 [heap]
I/DEBUG ( 1342): be94b888 fffec080
I/DEBUG ( 1342): be94b88c ad058683 /system/lib/libdvm.so
Click to expand...
Click to collapse
what is happening with my phone?
Have you messed with anything lately, new boot image, removed system apps, went to an eclair ROM and back, metamorphed, themed, etc?
cloverdale said:
Have you messed with anything lately, new boot image, removed system apps, went to an eclair ROM and back, metamorphed, themed, etc?
Click to expand...
Click to collapse
Nothing like that. I only have installed Cyanogen and a few apps from market. Nothing special as I think.
I have had this happen in only three cases:
1.) I tried adding framework that was not compatible with my ROM.
2.) I tried adding a launcher that was not compatible.
3.) I tried coming to a new ROM without a fresh format of my ext partition on my sdcard.
In all cases a fresh wipe of the phone and re-format of the sd ext partition fixed it.
cloverdale said:
I have had this happen in only three cases:
1.) I tried adding framework that was not compatible with my ROM.
2.) I tried adding a launcher that was not compatible.
3.) I tried coming to a new ROM without a fresh format of my ext partition on my sdcard.
In all cases a fresh wipe of the phone and re-format of the sd ext partition fixed it.
Click to expand...
Click to collapse
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Ace42 said:
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Click to expand...
Click to collapse
Good call. I second this.
Ace42 said:
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Click to expand...
Click to collapse
well, I doubt it as I have never installed any theme so far. I will see if it happens again and if so I will try to make a fresh reinstall.