Every day I get at least one or two random reboots... Anyone know the issue or have it too?
Sent from my C6903 using xda app-developers app
teamHTC said:
Every day I get at least one or two random reboots... Anyone know the issue or have it too?
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
+1
Experienced the same issue 2 weeks ago twice:
first time after clearing RAM with NQ Android Booster (all my apps collected in folders got "unfoldered" and some icons were suddenly missing (phone-icon, TXT-msg-Icon etc.)
After uninstalling NQ Android booster I got it a second time while adjusting camera settings during a photo-session.
Uninstalled "junk cleaner" too, since then no reboot any more.
Seems that SOME functions of Z1 get killed by optimizing apps and might cause a reboot. Check if You have apps like junk cleaner, RAM-cleaner or whatsoever installed ........
I had similar problems. Phone rebooted without me having even touched it. Noticed it when sitting in a passive car holder since it´s in my field of view.
I reflashed the phone with the latest firmware using the pc companion software from the sony mobile web page. Have not had any reboots since.
I got one random reboot per day after the new firmware update. I don't know if it was the same with the old firmware cause I used it just few hours. I don't have any app that optimize the system.
Sorry to bring this up again. But I somehow managed to collect the log from the kernel panic causing my Z1 random reboot (same every time).
I have a C6903. I have been suffering from random reboots since upgraded to firmware 14.1.G.2.257. Software ID: 1276-7842 R9A. Did the usual such as factory reset, PCC repair etc. but still happened.
Perhaps we can take a look at it if Sony releases the kernel source. Here is the stack trace:
<3>[41418.428108] ocmem: Failed to lock region graphics[0 -- fffff] ret = -22
<3>[41418.428119] ocmem: Failed to secure request de02fd00 for 0
<3>[41418.428129] ocmem: Failed to map ocmem request
<3>[41418.428148] ocmem allocation failed
<3>[41418.428159] kgsl kgsl-3d0: |adreno_start| OCMEM malloc failed
<3>[41418.429800] kgsl kgsl-3d0: |kgsl_pwrctrl_wake| start failed -12
<6>[41418.429812] SurfaceFlinger (1027): undefined instruction: pc=c0410014
<6>[41418.429822] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.429852] ------------[ cut here ]------------
<2>[41418.429861] kernel BUG at /home/hudsonslave/root/workspace/offbuild-rhine-1.0.2-honami-matrix/HUDSON_PRODUCT/honami/HUDSON_VARIANT/user/label/CM_OFFBLD/kernel/drivers/gpu/msm/kgsl_pwrctrl.c:1577!
<0>[41418.429880] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
<4>[41418.429888] Modules linked in: wlan(O) adsprpc adsp_loader cfg80211 texfat(PO) hid_sony(O) [last unloaded: wlan]
<4>[41418.429916] CPU: 0 Tainted: P W O (3.4.0-perf-g66807d4-02450-g9a218f1 #1)
<4>[41418.429929] PC is at kgsl_active_count_put+0x28/0x1f0
<4>[41418.429937] LR is at kgsl_ioctl+0x224/0x2f8
<4>[41418.429945] pc : [<c0410014>] lr : [<c0402a00>] psr: 60000013
<4>[41418.429947] sp : e2ca9e98 ip : 00000000 fp : 00000002
<4>[41418.429958] r10: c040395c r9 : 00000001 r8 : 40533814
<4>[41418.429966] r7 : c0402a00 r6 : fffffff4 r5 : e2ca9eb4 r4 : c0e66258
<4>[41418.429975] r3 : 00000000 r2 : c0ea7094 r1 : c0b53d24 r0 : c0e66258
<4>[41418.429984] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[41418.429993] Control: 10c5787d Table: 2b5f006a DAC: 00000015
<4>[41418.430000]
<4>[41418.430001] PC: 0xc040ff94:
<4>[41418.430008] ff94 eb007d50 e3a00000 e8bd8038 e5943418 e3530005 da000004 e5940000 e1a03005
<4>[41418.430034] ffb4 e59f102c e59f2018 eb007d24 e1a00004 e3a01000 ebfff917 e3e00015 e8bd8038
<4>[41418.430058] ffd4 c0b5017f c0940dff c0b50166 c0940e12 c0940e19 c0b50195 e92d41f0 e1a0700e
<4>[41418.430083] fff4 e5903354 e1a04000 e3530001 1a000000 e7f001f2 e5903370 e3530000 1a000000
<4>[41418.430108] 0014 e7f001f2 eb0002bd e5943370 e3530001 9a000026 e59f21a8 e2433001 e5843370
<4>[41418.430133] 0034 e5923004 e3530000 08bd81f0 e1a0100d e3c13d7f e3c3303f e5931004 e2811001
<4>[41418.430157] 0054 e5831004 e5926010 e3560000 0a00000c e2868008 e1a05006 e5953000 e1a01004
<4>[41418.430182] 0074 e5950004 e1a02007 e2855008 e12fff33 e0663005 e0833008 e5133008 e3530000
<4>[41418.430208]
<4>[41418.430209] LR: 0xc0402980:
<4>[41418.430215] 2980 13a0b001 1a000008 e5932410 e3520005 da000034 e5930000 e1a03004 e59f1128
<4>[41418.430240] 29a0 e59f2118 eb00b2aa ea00002e e5970000 e2800fd5 eb114b07 e35b0000 0a000003
<4>[41418.430265] 29c0 e5970000 eb003415 e2506000 ba000009 e3a09001 e1a00007 e1a01004 e1a02005
<4>[41418.430290] 29e0 e12fff3a e3590000 e1a06000 0a000006 e35b0000 0a000001 e5970000 eb00357a
<4>[41418.430315] 2a00 e5970000 e2800fd5 eb114a7e e3540000 aa000015 e1a0100d e3c13d7f e3c3303f
<4>[41418.430340] 2a20 e7ed2854 e5933008 e0981002 30d11003 33a03000 e3530000 1a000003 e1a00008
<4>[41418.430365] 2a40 e1a01005 ebfd4e55 e1a02000 e3520000 13e0600d ea000004 e3e0600b ea000002
<4>[41418.430389] 2a60 e3e0600d ea000000 e59f6060 e7ed4854 e354003f 9a000001 e1a00005 ebf8e429
<4>[41418.430415]
<4>[41418.430416] SP: 0xe2ca9e18:
..... <truncated>
<0>[41418.432046] Process SurfaceFlinger (pid: 1027, stack limit = 0xe2ca82f0)
<0>[41418.432055] Stack: (0xe2ca9e98 to 0xe2caa000)
<0>[41418.432063] 9e80: c0140910 e2ca9eb4
<0>[41418.432074] 9ea0: fffffff4 e3377b00 40533814 c0402a00 00000041 00000002 41433528 00000002
<0>[41418.432086] 9ec0: 00016e49 00000004 000003e8 0000000f c024767c e219f200 c0e1dcf8 011da09c
<0>[41418.432098] 9ee0: 02448000 d9ed20c8 e49c9190 00000000 c0252304 271ae91c e4803600 e3804b60
<0>[41418.432110] 9f00: 40533814 e3375b40 00000012 c0105f84 e2ca8000 00000000 00000000 c024f1ac
<0>[41418.432122] 9f20: 417157b8 c0252304 e219f200 00000000 e219f200 00000000 e219f24c c0252c48
<0>[41418.432134] 9f40: 00000002 d9ed20c0 e4641d78 e219f200 00000010 c0241ff0 c010b3e8 c01c5190
<0>[41418.432146] 9f60: e2ca9f90 e3375b40 40533814 c0140910 00000012 c0105f84 e2ca8000 00000000
<0>[41418.432158] 9f80: 00000000 c024f254 00000012 00000001 40533814 4056a04c c0140910 00000012
<0>[41418.432170] 9fa0: 00000036 c0105e00 4056a04c c0140910 00000012 c0140910 40533814 405337d4
<0>[41418.432181] 9fc0: 4056a04c c0140910 00000012 00000036 40533814 00000004 41433528 00000000
<0>[41418.432193] 9fe0: 40569f10 405337b8 40105a71 400f2088 00000010 00000012 00000000 00000000
<4>[41418.432209] [<c0410014>] (kgsl_active_count_put+0x28/0x1f0) from [<c0402a00>] (kgsl_ioctl+0x224/0x2f8)
<4>[41418.432224] [<c0402a00>] (kgsl_ioctl+0x224/0x2f8) from [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc)
<4>[41418.432238] [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc) from [<c024f254>] (sys_ioctl+0x34/0x54)
<4>[41418.432253] [<c024f254>] (sys_ioctl+0x34/0x54) from [<c0105e00>] (ret_fast_syscall+0x0/0x30)
<0>[41418.432266] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.432277] ---[ end trace 1b0d75d46d636dc3 ]---
<0>[41418.432286] Kernel panic - not syncing: Fatal exception
<3>[41419.435763] wcnss crash shutdown 0
patwang0311 said:
Sorry to bring this up again. But I somehow managed to collect the log from the kernel panic causing my Z1 random reboot (same every time).
I have a C6903. I have been suffering from random reboots since upgraded to firmware 14.1.G.2.257. Software ID: 1276-7842 R9A. Did the usual such as factory reset, PCC repair etc. but still happened.
Perhaps we can take a look at it if Sony releases the kernel source. Here is the stack trace:
<3>[41418.428108] ocmem: Failed to lock region graphics[0 -- fffff] ret = -22
<3>[41418.428119] ocmem: Failed to secure request de02fd00 for 0
<3>[41418.428129] ocmem: Failed to map ocmem request
<3>[41418.428148] ocmem allocation failed
<3>[41418.428159] kgsl kgsl-3d0: |adreno_start| OCMEM malloc failed
<3>[41418.429800] kgsl kgsl-3d0: |kgsl_pwrctrl_wake| start failed -12
<6>[41418.429812] SurfaceFlinger (1027): undefined instruction: pc=c0410014
<6>[41418.429822] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.429852] ------------[ cut here ]------------
<2>[41418.429861] kernel BUG at /home/hudsonslave/root/workspace/offbuild-rhine-1.0.2-honami-matrix/HUDSON_PRODUCT/honami/HUDSON_VARIANT/user/label/CM_OFFBLD/kernel/drivers/gpu/msm/kgsl_pwrctrl.c:1577!
<0>[41418.429880] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
<4>[41418.429888] Modules linked in: wlan(O) adsprpc adsp_loader cfg80211 texfat(PO) hid_sony(O) [last unloaded: wlan]
<4>[41418.429916] CPU: 0 Tainted: P W O (3.4.0-perf-g66807d4-02450-g9a218f1 #1)
<4>[41418.429929] PC is at kgsl_active_count_put+0x28/0x1f0
<4>[41418.429937] LR is at kgsl_ioctl+0x224/0x2f8
<4>[41418.429945] pc : [<c0410014>] lr : [<c0402a00>] psr: 60000013
<4>[41418.429947] sp : e2ca9e98 ip : 00000000 fp : 00000002
<4>[41418.429958] r10: c040395c r9 : 00000001 r8 : 40533814
<4>[41418.429966] r7 : c0402a00 r6 : fffffff4 r5 : e2ca9eb4 r4 : c0e66258
<4>[41418.429975] r3 : 00000000 r2 : c0ea7094 r1 : c0b53d24 r0 : c0e66258
<4>[41418.429984] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[41418.429993] Control: 10c5787d Table: 2b5f006a DAC: 00000015
<4>[41418.430000]
<4>[41418.430001] PC: 0xc040ff94:
<4>[41418.430008] ff94 eb007d50 e3a00000 e8bd8038 e5943418 e3530005 da000004 e5940000 e1a03005
<4>[41418.430034] ffb4 e59f102c e59f2018 eb007d24 e1a00004 e3a01000 ebfff917 e3e00015 e8bd8038
<4>[41418.430058] ffd4 c0b5017f c0940dff c0b50166 c0940e12 c0940e19 c0b50195 e92d41f0 e1a0700e
<4>[41418.430083] fff4 e5903354 e1a04000 e3530001 1a000000 e7f001f2 e5903370 e3530000 1a000000
<4>[41418.430108] 0014 e7f001f2 eb0002bd e5943370 e3530001 9a000026 e59f21a8 e2433001 e5843370
<4>[41418.430133] 0034 e5923004 e3530000 08bd81f0 e1a0100d e3c13d7f e3c3303f e5931004 e2811001
<4>[41418.430157] 0054 e5831004 e5926010 e3560000 0a00000c e2868008 e1a05006 e5953000 e1a01004
<4>[41418.430182] 0074 e5950004 e1a02007 e2855008 e12fff33 e0663005 e0833008 e5133008 e3530000
<4>[41418.430208]
<4>[41418.430209] LR: 0xc0402980:
<4>[41418.430215] 2980 13a0b001 1a000008 e5932410 e3520005 da000034 e5930000 e1a03004 e59f1128
<4>[41418.430240] 29a0 e59f2118 eb00b2aa ea00002e e5970000 e2800fd5 eb114b07 e35b0000 0a000003
<4>[41418.430265] 29c0 e5970000 eb003415 e2506000 ba000009 e3a09001 e1a00007 e1a01004 e1a02005
<4>[41418.430290] 29e0 e12fff3a e3590000 e1a06000 0a000006 e35b0000 0a000001 e5970000 eb00357a
<4>[41418.430315] 2a00 e5970000 e2800fd5 eb114a7e e3540000 aa000015 e1a0100d e3c13d7f e3c3303f
<4>[41418.430340] 2a20 e7ed2854 e5933008 e0981002 30d11003 33a03000 e3530000 1a000003 e1a00008
<4>[41418.430365] 2a40 e1a01005 ebfd4e55 e1a02000 e3520000 13e0600d ea000004 e3e0600b ea000002
<4>[41418.430389] 2a60 e3e0600d ea000000 e59f6060 e7ed4854 e354003f 9a000001 e1a00005 ebf8e429
<4>[41418.430415]
<4>[41418.430416] SP: 0xe2ca9e18:
..... <truncated>
<0>[41418.432046] Process SurfaceFlinger (pid: 1027, stack limit = 0xe2ca82f0)
<0>[41418.432055] Stack: (0xe2ca9e98 to 0xe2caa000)
<0>[41418.432063] 9e80: c0140910 e2ca9eb4
<0>[41418.432074] 9ea0: fffffff4 e3377b00 40533814 c0402a00 00000041 00000002 41433528 00000002
<0>[41418.432086] 9ec0: 00016e49 00000004 000003e8 0000000f c024767c e219f200 c0e1dcf8 011da09c
<0>[41418.432098] 9ee0: 02448000 d9ed20c8 e49c9190 00000000 c0252304 271ae91c e4803600 e3804b60
<0>[41418.432110] 9f00: 40533814 e3375b40 00000012 c0105f84 e2ca8000 00000000 00000000 c024f1ac
<0>[41418.432122] 9f20: 417157b8 c0252304 e219f200 00000000 e219f200 00000000 e219f24c c0252c48
<0>[41418.432134] 9f40: 00000002 d9ed20c0 e4641d78 e219f200 00000010 c0241ff0 c010b3e8 c01c5190
<0>[41418.432146] 9f60: e2ca9f90 e3375b40 40533814 c0140910 00000012 c0105f84 e2ca8000 00000000
<0>[41418.432158] 9f80: 00000000 c024f254 00000012 00000001 40533814 4056a04c c0140910 00000012
<0>[41418.432170] 9fa0: 00000036 c0105e00 4056a04c c0140910 00000012 c0140910 40533814 405337d4
<0>[41418.432181] 9fc0: 4056a04c c0140910 00000012 00000036 40533814 00000004 41433528 00000000
<0>[41418.432193] 9fe0: 40569f10 405337b8 40105a71 400f2088 00000010 00000012 00000000 00000000
<4>[41418.432209] [<c0410014>] (kgsl_active_count_put+0x28/0x1f0) from [<c0402a00>] (kgsl_ioctl+0x224/0x2f8)
<4>[41418.432224] [<c0402a00>] (kgsl_ioctl+0x224/0x2f8) from [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc)
<4>[41418.432238] [<c024f1ac>] (do_vfs_ioctl+0x548/0x5bc) from [<c024f254>] (sys_ioctl+0x34/0x54)
<4>[41418.432253] [<c024f254>] (sys_ioctl+0x34/0x54) from [<c0105e00>] (ret_fast_syscall+0x0/0x30)
<0>[41418.432266] Code: e7f001f2 e5903370 e3530000 1a000000 (e7f001f2)
<4>[41418.432277] ---[ end trace 1b0d75d46d636dc3 ]---
<0>[41418.432286] Kernel panic - not syncing: Fatal exception
<3>[41419.435763] wcnss crash shutdown 0
Click to expand...
Click to collapse
So it was a software failure?
El.Guaje said:
So it was a software failure?
Click to expand...
Click to collapse
Think it is. When I was using 1.534, I didn't even see a single random reboot. I have now just reverted back to that older firmware to see if it will last a week without reboot.
I recall seeing Google claimed to have fixed Nexus 10 random reboot issue with the release of 4.3 (btw, N10 was having similar kernel panic with GPU code a while back) - not sure if that's really fixed. Hopefully Sony is aware of this rather than denying it and give us a fix some time in the future.
I have mentioned in another thread that you can actually accelerate the occurrence of random reboot by turning on 'Force GPU Rendering' in 'Developer Options'. That will force all 2D apps to render with GPU -> which will make it crashes a lot sooner. Not ticking that option won't make the problem go away, just delaying it from happening unless you don't use your GPU at all.
patwang0311 said:
Think it is. When I was using 1.534, I didn't even see a single random reboot. I have now just reverted back to that older firmware to see if it will last a week without reboot.
I recall seeing Google claimed to have fixed Nexus 10 random reboot issue with the release of 4.3 (btw, N10 was having similar kernel panic with GPU code a while back) - not sure if that's really fixed. Hopefully Sony is aware of this rather than denying it and give us a fix some time in the future.
I have mentioned in another thread that you can actually accelerate the occurrence of random reboot by turning on 'Force GPU Rendering' in 'Developer Options'. That will force all 2D apps to render with GPU -> which will make it crashes a lot sooner. Not ticking that option won't make the problem go away, just delaying it from happening unless you don't use your GPU at all.
Click to expand...
Click to collapse
I see, me phone reboot after 3 days. Sometimes one day it reboot twice.
It does not reboot while I'm using the phone. It happen when I leave the phone alone in my desk or in my pocket.
I hope 4.3 will fix this problem, with 4.2.2 build 534 I've heard that It may cause Sleep of Death so I don't reverse back.
Same problem, I need solution
teamHTC said:
Every day I get at least one or two random reboots... Anyone know the issue or have it too?
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
I am having the same problem with my Xperia Z1, I have tried too many things and read a lot of threads to solve this issue but no one solution or trick works on this issue.......... Help me..
I have the same problem - the phone restarts. But I can stop the restarts by:
1) Turn of Bluetooth. When Bluetooth is on, it restarts 1-2 times a day. When using bluetooth for external devices it restarts more often.
2) Turn off wi-fi. And just using 3G/4G/LTE. When entering a 'known' wi-fi (home or Work) it surely restarts every time.
It's not a solution, but hopefully it's solved in 4.3 and 4.4. I have tried to reset phone, new simcard etc.
Related
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.
I've experienced a huge problem with my G1. I always liked to play with it, so I rooted it instatly after buying it. Now I have Haykuro, Amon_Ra recovery, .26i radio. I flashed new ROM every week and everything was OK. Until now. Something happened and almost every ROM is getting bootloop! Some hangs on G1 splash, some on their bootscreen. I tried SuperF, SuperD, CM6 RC3, Donut AOSP TheOfficial, Chromatic, SpeedTeam Froyo, SuperE, Dwang, Froyo AOSP and more, but only SuperE and FroyoAOSP booted (but only once - when I turn them off they never boot again). Before every flash I was doing full wipe, sometimes also a fastboot system -w.
Fastboot and recovery working. Tried to reflash radio and recovery, to format SD Card - nothing helped.
I wonder if I should try to unroot and then root again? Did anyone ever encountered this strange situation? Everything was all right and then BANG! everything crashes ;/.
I am always wathing logcat and discovered one interesting thing - few ROMs hang in the same place:
Code:
D/AndroidRuntime( 731):
D/AndroidRuntime( 731): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 731): CheckJNI is OFF
D/AndroidRuntime( 731): --- registering native functions ---
I/Zygote ( 731): Preloading classes...
D/dalvikvm( 731): GC freed 800 objects / 44048 bytes in 6ms
I/DEBUG ( 699): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 699): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 699): pid: 731, tid: 731 >>> zygote <<<
I/DEBUG ( 699): signal 11 (SIGSEGV), fault addr 0000001e
I/DEBUG ( 699): r0 08000000 r1 bea5c5ec r2 bea5c5ec r3 bea5c604
I/DEBUG ( 699): r4 00000200 r5 bea5c604 r6 00000000 r7 00000001
I/DEBUG ( 699): r8 bea5c5ec r9 000904e0 10 bea5c604 fp bea5c5bc
I/DEBUG ( 699): ip ad4abe54 sp bea5c508 lr ad48f551 pc ad47070a cpsr 000
00030
I/DEBUG ( 699): #00 pc 0007070a /system/lib/libicui18n.so
I/DEBUG ( 699): #01 lr ad48f551 /system/lib/libicui18n.so
I/DEBUG ( 699): stack:
I/DEBUG ( 699): bea5c4c8 0007b228 [heap]
I/DEBUG ( 699): bea5c4cc 000001b4
I/DEBUG ( 699): bea5c4d0 000000dc
I/DEBUG ( 699): bea5c4d4 00002bcc
I/DEBUG ( 699): bea5c4d8 00000001
I/DEBUG ( 699): bea5c4dc afe0b70f /system/lib/libc.so
I/DEBUG ( 699): bea5c4e0 afe39dd4 /system/lib/libc.so
I/DEBUG ( 699): bea5c4e4 00000034
I/DEBUG ( 699): bea5c4e8 40031fe0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c4ec 00000004
I/DEBUG ( 699): bea5c4f0 00000001
I/DEBUG ( 699): bea5c4f4 00000001
I/DEBUG ( 699): bea5c4f8 bea5c510 [stack]
I/DEBUG ( 699): bea5c4fc 00000000
I/DEBUG ( 699): bea5c500 df002777
I/DEBUG ( 699): bea5c504 e3a070ad
I/DEBUG ( 699): #00 bea5c508 ad084aa8 /system/lib/libdvm.so
I/DEBUG ( 699): bea5c50c 00000200
I/DEBUG ( 699): bea5c510 ad5c1b50 /system/lib/libicuuc.so
I/DEBUG ( 699): bea5c514 00000001
I/DEBUG ( 699): bea5c518 00000001
I/DEBUG ( 699): bea5c51c 0007b228 [heap]
I/DEBUG ( 699): bea5c520 ad080008 /system/lib/libdvm.so
I/DEBUG ( 699): bea5c524 40031fb0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c528 00000007
I/DEBUG ( 699): bea5c52c 40031fb0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c530 40031fb0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c534 bea5c620 [stack]
I/DEBUG ( 699): bea5c538 4104ee54
I/DEBUG ( 699): bea5c53c 4104ee44
I/DEBUG ( 699): bea5c540 00000000
I/DEBUG ( 699): bea5c544 40031fe0 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 699): bea5c548 0000a9c8 [heap]
I/DEBUG ( 699): bea5c54c 00000001
Maybe this is the key? Some hangs in other place, I will try to catch it and post here too. Please, help! I don't want to lose my G1...
If there was someone with same problem, please, post me a link to thread.
OK, I got second place when ROM hangs. Got cyan 5.07 to work and then it hanged after second boot. This is where it was looping:
Code:
D/libEGL ( 255): Setting TLS: 0xafe43b6c to 0xac70a2ec
D/AndroidRuntime( 255):
D/AndroidRuntime( 255): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 255): CheckJNI is OFF
D/AndroidRuntime( 255): --- registering native functions ---
E/JNIHelp ( 255): Native registration unable to find class 'com/android/interna
l/os/RuntimeInit'
E/AndroidRuntime( 255): Unable to register all android natives
I/ServiceManager( 91): service 'media.audio_flinger' died
I/ServiceManager( 91): service 'media.player' died
I/ServiceManager( 91): service 'media.camera' died
I/ServiceManager( 91): service 'media.audio_policy' died
D/libEGL ( 256): Setting TLS: 0xafe43b6c to 0xac70a2ec
I/ ( 256): ServiceManager: 0xad08
I/HTC Acoustic( 256): libhtc_acoustic.so version 1.0.1.2.
E/HTC Acoustic( 256): Fail to open /system/etc/AudioPara_Era.csv -1.
I/HTC Acoustic( 256): open /system/etc/AudioPara4.csv success.
I/HTC Acoustic( 256): acoustic table version: Sapphire_VODAFONE_20090305
I/HTC Acoustic( 256): read_audio_para_from_file success.
I/HTC Acoustic( 256): get_audpp_filter
I/HTC Acoustic( 256): open /system/etc/AudioFilter.csv success.
I/HTC Acoustic( 256): ADRC Filter ADRC FLAG = ffff.
I/HTC Acoustic( 256): ADRC Filter COMP THRESHOLD = 2600.
I/HTC Acoustic( 256): ADRC Filter COMP SLOPE = b333.
I/HTC Acoustic( 256): ADRC Filter COMP RMS TIME = 106.
I/HTC Acoustic( 256): ADRC Filter COMP ATTACK[0] = 7f7d.
I/HTC Acoustic( 256): ADRC Filter COMP ATTACK[1] = 3096.
I/HTC Acoustic( 256): ADRC Filter COMP RELEASE[0] = 7ff7.
I/HTC Acoustic( 256): ADRC Filter COMP RELEASE[1] = 4356.
I/HTC Acoustic( 256): ADRC Filter COMP DELAY = 16.
I/HTC Acoustic( 256): EQ flag = 00.
I/HTC Acoustic( 256): get_audpre_filter
I/HTC Acoustic( 256): open /system/etc/AudioPreProcess.csv success.
D/AudioHardwareMSM72XX( 256): mNumSndEndpoints = 67
D/AudioHardwareMSM72XX( 256): BT MATCH HANDSET
D/AudioHardwareMSM72XX( 256): BT MATCH SPEAKER
D/AudioHardwareMSM72XX( 256): BT MATCH HEADSET
D/AudioHardwareMSM72XX( 256): BT MATCH BT
D/AudioHardwareMSM72XX( 256): BT MATCH CARKIT
D/AudioHardwareMSM72XX( 256): BT MATCH TTY_FULL
D/AudioHardwareMSM72XX( 256): BT MATCH TTY_VCO
D/AudioHardwareMSM72XX( 256): BT MATCH TTY_HCO
D/AudioHardwareMSM72XX( 256): BT MATCH NO_MIC_HEADSET
D/AudioHardwareMSM72XX( 256): BT MATCH FM_HEADSET
D/AudioHardwareMSM72XX( 256): BT MATCH HEADSET_AND_SPEAKER
D/AudioHardwareMSM72XX( 256): BT MATCH FM_SPEAKER
D/AudioHardwareMSM72XX( 256): BT MATCH BT_EC_OFF
D/AudioHardwareMSM72XX( 256): BT MATCH CURRENT
D/AudioHardwareMSM72XX( 256): BT MATCH BT_EC_OFF
D/AudioHardwareInterface( 256): setMode(NORMAL)
I/AudioHardwareMSM72XX( 256): Set master volume to 5.
I/CameraService( 256): CameraService started: pid=256
I/AudioFlinger( 256): AudioFlinger's thread 0xd8a8 ready to run
I/AudioHardwareMSM72XX( 256): Routing audio to Speakerphone
D/HTC Acoustic( 256): msm72xx_enable_audpp: 0x0001
D/AudioHardwareMSM72XX( 256): setVoiceVolume(1.000000)
I/AudioHardwareMSM72XX( 256): Setting in-call volume to 5 (available range is 0
to 5)
No one knows what is going on? No one to help? Please, I'm going nuts because of this, I really don't know what's going on. Almost every ROM hangs in same 2 places, someone has to know what's going on!
WOOPS, double post. Sorry, i thought that it will automatically merge two posts in one.
EDIT: CM6 RC3 boots all right. I can even reboot it. But still, this situation is not normal .
Dont let this piss you off but have you tried a new SDcard?
I have had trouble going from Froyo to Cupcake and vice versa --- they always involve a fresh new SDcard and I really do not know why.
I want to try something... what if I send you some nandroid backups would you want to try fastbooting them in? That may work and I've got only so many gigs of nandroids saved from the past year.
Tried another SD Card, but nope, it's not it. Same results: CM6 RC3 is booting well while everything else is looping. Tried to apply MTD Part Hack (don't know why, I thought that it might help and if it is not working I will have a reason to ask Firerat what's going on ) and loop in SuperD boot changed a little, now it is like this:
Code:
v/0 (deleted)
I/DEBUG ( 132): bedea848 0000bc48 [heap]
I/DEBUG ( 132): bedea84c 0000a9c0 [heap]
I/DEBUG ( 132): bedea850 0000bc48 [heap]
I/DEBUG ( 132): bedea854 0000a9c0 [heap]
I/DEBUG ( 132): bedea858 df002777
I/DEBUG ( 132): bedea85c e3a070ad
I/DEBUG ( 132): #00 bedea860 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bedea864 0000bc48 [heap]
I/DEBUG ( 132): bedea868 0000a9c0 [heap]
I/DEBUG ( 132): bedea86c ad036569 /system/lib/libdvm.so
I/DEBUG ( 132): bedea870 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bedea874 ad080a54 /system/lib/libdvm.so
I/DEBUG ( 132): bedea878 0000a9c0 [heap]
I/DEBUG ( 132): bedea87c ad036923 /system/lib/libdvm.so
I/DEBUG ( 132): bedea880 00000000
I/DEBUG ( 132): bedea884 00000000
I/DEBUG ( 132): bedea888 0000036c
I/DEBUG ( 132): bedea88c ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bedea890 bedea970 [stack]
I/DEBUG ( 132): bedea894 0000a9c0 [heap]
I/DEBUG ( 132): bedea898 0000a978 [heap]
I/DEBUG ( 132): bedea89c ad03854f /system/lib/libdvm.so
I/DEBUG ( 132): bedea8a0 00000003
I/DEBUG ( 132): bedea8a4 ad080c00 /system/lib/libdvm.so
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 179, tid: 179 >>> /system/bin/rild <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80004160
I/DEBUG ( 132): r0 80004160 r1 00000000 r2 00000e60 r3 00000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp befff738 lr 00000000 pc b000268c cpsr 200
00010
I/DEBUG ( 132): #00 pc b000268c /system/bin/linker
I/DEBUG ( 132): #01 pc b00011e2 /system/bin/linker
I/DEBUG ( 132): #02 pc b0001464 /system/bin/linker
I/DEBUG ( 132): #03 pc b0001560 /system/bin/linker
I/DEBUG ( 132): #04 pc b0001cec /system/bin/linker
I/DEBUG ( 132): #05 pc 00008bee /system/bin/rild
I/DEBUG ( 132): #06 pc 0000c572 /system/lib/libc.so
I/DEBUG ( 132): #07 pc b00018c6 /system/bin/linker
I/DEBUG ( 132): stack:
I/DEBUG ( 132): befff6f8 b00107e0 /system/bin/linker
I/DEBUG ( 132): befff6fc 000002ff
I/DEBUG ( 132): befff700 00000000
I/DEBUG ( 132): befff704 00000000
I/DEBUG ( 132): befff708 b000d288 /system/bin/linker
I/DEBUG ( 132): befff70c befff6ac [stack]
I/DEBUG ( 132): befff710 00000000
I/DEBUG ( 132): befff714 00000000
I/DEBUG ( 132): befff718 00000000
I/DEBUG ( 132): befff71c ffffffff
I/DEBUG ( 132): befff720 00000000
I/DEBUG ( 132): befff724 b00041c1 /system/bin/linker
I/DEBUG ( 132): befff728 00000004
I/DEBUG ( 132): befff72c 00000003
I/DEBUG ( 132): befff730 df002777
I/DEBUG ( 132): befff734 e3a070ad
I/DEBUG ( 132): #00 befff738 80004160 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff73c b0017690
I/DEBUG ( 132): befff740 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff744 b0011a3c
I/DEBUG ( 132): befff748 b0010448 /system/bin/linker
I/DEBUG ( 132): befff74c b00011e5 /system/bin/linker
I/DEBUG ( 132): #01 befff750 00000003
I/DEBUG ( 132): befff754 00004000
I/DEBUG ( 132): befff758 b000ca4b /system/bin/linker
I/DEBUG ( 132): befff75c b000c760 /system/bin/linker
I/DEBUG ( 132): befff760 00000000
I/DEBUG ( 132): befff764 00000000
I/DEBUG ( 132): befff768 00000000
I/DEBUG ( 132): befff76c b0011ad0
I/DEBUG ( 132): befff770 00000160
I/DEBUG ( 132): befff774 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff778 80000000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): befff77c 00004000
I/DEBUG ( 132): befff780 b001761c
I/DEBUG ( 132): befff784 00000002
I/DEBUG ( 132): befff788 00000003
I/DEBUG ( 132): befff78c b0011b34
I/DEBUG ( 132): befff790 b0011b38
I/DEBUG ( 132): befff794 b0011ad4
I/DEBUG ( 132): befff798 befff99c [stack]
I/DEBUG ( 132): befff79c b0010448 /system/bin/linker
I/DEBUG ( 132): befff7a0 b0011a3c
I/DEBUG ( 132): befff7a4 00000003
I/DEBUG ( 132): befff7a8 b0011ac8
I/DEBUG ( 132): befff7ac b0001469 /system/bin/linker
I/ ( 180): ServiceManager: 0xac38
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 180, tid: 180 >>> /system/bin/mediaserver <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80604164
I/DEBUG ( 132): r0 80604164 r1 00000000 r2 00000e80 r3 c0000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp be822ab8 lr 00000000 pc b0002668 cpsr a00
00010
I/DEBUG ( 132): #00 pc b0002668 /system/bin/linker
I/DEBUG ( 132): #01 pc b00011e2 /system/bin/linker
I/DEBUG ( 132): #02 pc b0001464 /system/bin/linker
I/DEBUG ( 132): #03 pc b0001560 /system/bin/linker
I/DEBUG ( 132): #04 pc b0001cec /system/bin/linker
I/DEBUG ( 132): #05 pc 0000481a /system/lib/libaudio.so
I/DEBUG ( 132): #06 pc 00004a32 /system/lib/libaudio.so
I/DEBUG ( 132): #07 pc 000051a8 /system/lib/libaudio.so
I/DEBUG ( 132): #08 pc 000183ec /system/lib/libaudioflinger.so
I/DEBUG ( 132): #09 pc 00018626 /system/lib/libaudioflinger.so
I/DEBUG ( 132): #10 pc 0000873e /system/bin/mediaserver
I/DEBUG ( 132): #11 pc 0000c572 /system/lib/libc.so
I/DEBUG ( 132): #12 pc b00018c6 /system/bin/linker
I/DEBUG ( 132): stack:
I/DEBUG ( 132): be822a78 b0013e54
I/DEBUG ( 132): be822a7c be822a94 [stack]
I/DEBUG ( 132): be822a80 a7a043c9 /system/lib/libopencore_net_support.s
o
I/DEBUG ( 132): be822a84 b0010ae0 /system/bin/linker
I/DEBUG ( 132): be822a88 be822b04 [stack]
I/DEBUG ( 132): be822a8c 02ff0fa4
I/DEBUG ( 132): be822a90 a600bb68 /system/lib/libopencore_common.so
I/DEBUG ( 132): be822a94 b0000495 /system/bin/linker
I/DEBUG ( 132): be822a98 00000000
I/DEBUG ( 132): be822a9c ffffffff
I/DEBUG ( 132): be822aa0 00000000
I/DEBUG ( 132): be822aa4 b00041c1 /system/bin/linker
I/DEBUG ( 132): be822aa8 00000004
I/DEBUG ( 132): be822aac 00000007
I/DEBUG ( 132): be822ab0 df002777
I/DEBUG ( 132): be822ab4 e3a070ad
I/DEBUG ( 132): #00 be822ab8 80604164 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822abc b0017690
I/DEBUG ( 132): be822ac0 80604000 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822ac4 b0014084
I/DEBUG ( 132): be822ac8 b0010448 /system/bin/linker
I/DEBUG ( 132): be822acc b00011e5 /system/bin/linker
I/DEBUG ( 132): #01 be822ad0 00000007
I/DEBUG ( 132): be822ad4 00004000
I/DEBUG ( 132): be822ad8 be822ae8 [stack]
I/DEBUG ( 132): be822adc b00009ab /system/bin/linker
I/DEBUG ( 132): be822ae0 00000000
I/DEBUG ( 132): be822ae4 00000000
I/DEBUG ( 132): be822ae8 00000000
I/DEBUG ( 132): be822aec b0014118
I/DEBUG ( 132): be822af0 00000164
I/DEBUG ( 132): be822af4 80604000 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822af8 80600000 /system/lib/libhtc_acoustic.so
I/DEBUG ( 132): be822afc 00004000
I/DEBUG ( 132): be822b00 b001761c
I/DEBUG ( 132): be822b04 00000002
I/DEBUG ( 132): be822b08 00000007
I/DEBUG ( 132): be822b0c b001417c
I/DEBUG ( 132): be822b10 b0014180
I/DEBUG ( 132): be822b14 b001411c
I/DEBUG ( 132): be822b18 00000000
I/DEBUG ( 132): be822b1c b0010448 /system/bin/linker
I/DEBUG ( 132): be822b20 b0014084
I/DEBUG ( 132): be822b24 00000007
I/DEBUG ( 132): be822b28 b0014110
I/DEBUG ( 132): be822b2c b0001469 /system/bin/linker
D/AndroidRuntime( 181):
D/AndroidRuntime( 181): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 181): CheckJNI is OFF
D/dalvikvm( 181): Unable to stat classpath element '/system/framework/com.htc.f
ramework.jar'
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 181, tid: 181 >>> zygote <<<
I/DEBUG ( 132): signal 11 (SIGSEGV), fault addr 00000000
I/DEBUG ( 132): r0 00000000 r1 00000000 r2 ffffff08 r3 00000000
I/DEBUG ( 132): r4 000000f8 r5 00000000 r6 00000000 r7 00000007
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip ad080214 sp bed82860 lr ad20cae9 pc ad213d62 cpsr 400
00030
I/DEBUG ( 132): #00 pc 00013d62 /system/lib/libnativehelper.so
I/DEBUG ( 132): #01 lr ad20cae9 /system/lib/libnativehelper.so
I/DEBUG ( 132): stack:
I/DEBUG ( 132): bed82820 ad233ff4 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed82824 0000001d
I/DEBUG ( 132): bed82828 ad233120 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed8282c 00000ed4
I/DEBUG ( 132): bed82830 0000a9c0 [heap]
I/DEBUG ( 132): bed82834 ad233120 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed82838 ad235670 /system/lib/libnativehelper.so
I/DEBUG ( 132): bed8283c ad21543d /system/lib/libnativehelper.so
I/DEBUG ( 132): bed82840 0000a9c0 [heap]
I/DEBUG ( 132): bed82844 4000fd18 /dev/ashmem/mspace/dalvik-heap/zygote
/0 (deleted)
I/DEBUG ( 132): bed82848 0000bc48 [heap]
I/DEBUG ( 132): bed8284c 0000a9c0 [heap]
I/DEBUG ( 132): bed82850 0000bc48 [heap]
I/DEBUG ( 132): bed82854 0000a9c0 [heap]
I/DEBUG ( 132): bed82858 df002777
I/DEBUG ( 132): bed8285c e3a070ad
I/DEBUG ( 132): #00 bed82860 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bed82864 0000bc48 [heap]
I/DEBUG ( 132): bed82868 0000a9c0 [heap]
I/DEBUG ( 132): bed8286c ad036569 /system/lib/libdvm.so
I/DEBUG ( 132): bed82870 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bed82874 ad080a54 /system/lib/libdvm.so
I/DEBUG ( 132): bed82878 0000a9c0 [heap]
I/DEBUG ( 132): bed8287c ad036923 /system/lib/libdvm.so
I/DEBUG ( 132): bed82880 00000000
I/DEBUG ( 132): bed82884 00000000
I/DEBUG ( 132): bed82888 0000036c
I/DEBUG ( 132): bed8288c ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 132): bed82890 bed82970 [stack]
I/DEBUG ( 132): bed82894 0000a9c0 [heap]
I/DEBUG ( 132): bed82898 0000a978 [heap]
I/DEBUG ( 132): bed8289c ad03854f /system/lib/libdvm.so
I/DEBUG ( 132): bed828a0 00000003
I/DEBUG ( 132): bed828a4 ad080c00 /system/lib/libdvm.so
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 182, tid: 182 >>> /system/bin/rild <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80004160
I/DEBUG ( 132): r0 80004160 r1 00000000 r2 00000e60 r3 00000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp bea06738 lr 00000000 pc b000268c cpsr 200
00010
I/DEBUG ( 132): #00 pc b000268c /system/bin/linker
I/DEBUG ( 132): #01 pc b00011e2 /system/bin/linker
I/DEBUG ( 132): #02 pc b0001464 /system/bin/linker
I/DEBUG ( 132): #03 pc b0001560 /system/bin/linker
I/DEBUG ( 132): #04 pc b0001cec /system/bin/linker
I/DEBUG ( 132): #05 pc 00008bee /system/bin/rild
I/DEBUG ( 132): #06 pc 0000c572 /system/lib/libc.so
I/DEBUG ( 132): #07 pc b00018c6 /system/bin/linker
I/DEBUG ( 132): stack:
I/DEBUG ( 132): bea066f8 b00107e0 /system/bin/linker
I/DEBUG ( 132): bea066fc 000002ff
I/DEBUG ( 132): bea06700 00000000
I/DEBUG ( 132): bea06704 00000000
I/DEBUG ( 132): bea06708 b000d288 /system/bin/linker
I/DEBUG ( 132): bea0670c bea066ac [stack]
I/DEBUG ( 132): bea06710 00000000
I/DEBUG ( 132): bea06714 00000000
I/DEBUG ( 132): bea06718 00000000
I/DEBUG ( 132): bea0671c ffffffff
I/DEBUG ( 132): bea06720 00000000
I/DEBUG ( 132): bea06724 b00041c1 /system/bin/linker
I/DEBUG ( 132): bea06728 00000004
I/DEBUG ( 132): bea0672c 00000003
I/DEBUG ( 132): bea06730 df002777
I/DEBUG ( 132): bea06734 e3a070ad
I/DEBUG ( 132): #00 bea06738 80004160 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea0673c b0017690
I/DEBUG ( 132): bea06740 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea06744 b0011a3c
I/DEBUG ( 132): bea06748 b0010448 /system/bin/linker
I/DEBUG ( 132): bea0674c b00011e5 /system/bin/linker
I/DEBUG ( 132): #01 bea06750 00000003
I/DEBUG ( 132): bea06754 00004000
I/DEBUG ( 132): bea06758 b000ca4b /system/bin/linker
I/DEBUG ( 132): bea0675c b000c760 /system/bin/linker
I/DEBUG ( 132): bea06760 00000000
I/DEBUG ( 132): bea06764 00000000
I/DEBUG ( 132): bea06768 00000000
I/DEBUG ( 132): bea0676c b0011ad0
I/DEBUG ( 132): bea06770 00000160
I/DEBUG ( 132): bea06774 80004000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea06778 80000000 /system/lib/libhtc_ril.so
I/DEBUG ( 132): bea0677c 00004000
I/DEBUG ( 132): bea06780 b001761c
I/DEBUG ( 132): bea06784 00000002
I/DEBUG ( 132): bea06788 00000003
I/DEBUG ( 132): bea0678c b0011b34
I/DEBUG ( 132): bea06790 b0011b38
I/DEBUG ( 132): bea06794 b0011ad4
I/DEBUG ( 132): bea06798 bea0699c [stack]
I/DEBUG ( 132): bea0679c b0010448 /system/bin/linker
I/DEBUG ( 132): bea067a0 b0011a3c
I/DEBUG ( 132): bea067a4 00000003
I/DEBUG ( 132): bea067a8 b0011ac8
I/DEBUG ( 132): bea067ac b0001469 /system/bin/linker
I/ ( 183): ServiceManager: 0xac38
I/DEBUG ( 132): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 132): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:
user/ota-rel-keys,release-keys'
I/DEBUG ( 132): pid: 183, tid: 183 >>> /system/bin/mediaserver <<<
I/DEBUG ( 132): signal 7 (SIGBUS), fault addr 80604164
I/DEBUG ( 132): r0 80604164 r1 00000000 r2 00000e80 r3 c0000000
I/DEBUG ( 132): r4 00000000 r5 00000000 r6 00000000 r7 00000000
I/DEBUG ( 132): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 132): ip 00000000 sp bef62ab8 lr 00000000 pc b0002668 cpsr a00
00010
And about sending nandroid - of course, I am so glad that someone looked here . What should I do? Flash a ROM that does not work, try to boot it, reboot to recovery, do a nandroid and send to you?
can anyone please tell me how to do fastboot system -w. ?
step by step and treat me as a beginner....
You have to have installed sdk on your computer and installed adb drivers for your phone (you should find out how install drivers on your own). I assume you are using Windows as 90% users of PC, so I will explain how to do it on Windows.
Download SDK HERE
Unzip it to C:\ (or wherever you want, just remember path)
Open windows terminal (command) by typing "cmd" in search bar in start menu (if you are using windows Vista or 7, on XP it's in the All Programs -> Accesories -> Command line (or sth like that))
Power off your phone and boot it with BACK + POWER combination
Plug your phone to PC
In command type (do not type "*" I included for explanations):
Code:
cd android-sdk-windows/tools *
fastboot devices **
fastboot erase system -w
* or any other path where your sdk is placed
**to make sure that your phone is properly connected, it should give you something like -serial number- fastboot
Now you can press MENU to poweroff phone
But honestly, I was expecting some help in my rather bad situation, not more questions about things which you can really google easily -_-.
raven_raven said:
You have to have installed sdk on your computer and installed adb drivers for your phone (you should find out how install drivers on your own). I assume you are using Windows as 90% users of PC, so I will explain how to do it on Windows.
Download SDK HERE
Unzip it to C:\ (or wherever you want, just remember path)
Open windows terminal (command) by typing "cmd" in search bar in start menu (if you are using windows Vista or 7, on XP it's in the All Programs -> Accesories -> Command line (or sth like that))
Power off your phone and boot it with BACK + POWER combination
Plug your phone to PC
In command type (do not type "*" I included for explanations):
Code:
cd android-sdk-windows/tools *
fastboot devices **
fastboot erase system -w
* or any other path where your sdk is placed
**to make sure that your phone is properly connected, it should give you something like -serial number- fastboot
Now you can press MENU to poweroff phone
But honestly, I was expecting some help in my rather bad situation, not more questions about things which you can really google easily -_-.
Click to expand...
Click to collapse
You may want to do
Code:
#df -h
and make sure your system partition is not ridiculously small. If its less than 90 you will have trouble.
Outside of that, maybe reroot but I doubt it will help. You may have corrupt areas in the internal memory.
Can you install and run Dwang? That has always worked for me when nothing else would.
That is all I can think of now I will give it some thought.
Maybe erase every thing then flash it back
fastboot erase system -w
fastboot erase recovery
fastboot erase boot
That will leave you with just fastboot working.
You will need to reflash recovery and every thing. Stay away from nandroids until you have it all working. You may accidentally reinstall whatever is the problem.
Good luck.
Thank you very much for advices, I will try every of them. One question though: I know how to flash recovery, but how to restore boot? Is it flashed with ROM?
And is there a possibility to test an internal memory? It can be it... However EVERY ROM should not work, but FEW are working (but only for one boot) and one (CM6 RC3) is booting flawlessy every time.
Results of
Code:
df -h
are standard to Haykuro:
90M of /system
89.8M of /data
30M of /cache
I will try to flash Dwang and see what results are.
I just rerooted my phone. I used DREAIMG.nbh to back to stock recovery, bootloader, ROM and radio, then gained root, then slowly upgraded everything to previus state (Amon_Ra + Haykuro + .26i radio). Finally I flashed SuperD... again, same bootloop. I am disappointed and I have no idea what is going on . I guess my G1 is saying me "enough of this flashing, I'm tired" and I should stick with stock 1.6...
Did you overclock your last ROM? I am only guessing, but when I restart my phone, SetCPU shows me always some "standard values" (245/576). What will happen if the CPU clock is set too high? I imagine, this may cause a kernel panic and a boot loop. Only guessing ...
Nope, I wasn't using OC since IMO this was only helping to drain battery faster . Even if it was OC, I think that corrupted kernel was wiped many flashes ago when I was unrooting or even further in past, when I was doing thousand wipe and fastboot erase system -w.
I come to conclusion that internal memory of my G1 must've became corrupted. This is only explanation of what's going on.
What will happen if this information is written into some hidden space which is not wiped, like the reboot to recovery flag when flashing radio from recovery?
It may be that some parts of ROM is not wiped even if I did all this unrooting and rooting stuff. The question is: How to find it and how to get rid of it? Man, if some kind of genius like Firerat or Cyanogen looked at this thread .
... or just lbcoder !
Sorry that I cannot help you so much, unfortunatey I am not such an expert as lbcoder or Firerat
Sorry, no offence of course, I really aprecceate your help ! Yep, lbcoder also might know what's going on . Don't know, maybe I'll try to PM one of them, maybe they'll have some time for me.
an old SD card did this to my old G1... not exactly this but something eerily similar. G1 bootoops, depending on rom... very slow on the ROMs that worked, etc..etc.. and the new G1 i have running now is doing the same thing.. time for a new SD. GET YOURSELF A NEW (not "another") get yourself a NEW class 6! micro. Worked for me for a little, then lots of flashing, partitioning, and all that heavy wear... now its getting slow again. These SDs wear down quickly is seems. This phone has a high-speed SDHC card slot for a reason -- why not put it to it's full potential. Another thing that happened to me was that the app "switch pro widget" fried my phones wifi. Makes no sense to you does it? But it happened, and - to me... it didn't seem like coincidence. I went to turn the wifi on via the widget, and the bar turned a shaded green while it turns on, then once connected it went dark green. Well i went to turn it on, and it got the the shaded green and said "updating wifi status" or and it never connected --- and my wifi never worked again. After that i would always get "ERROR" when i turned my wifi on. Flashed tons of new ROMS, new SDs, wiping over and over, new wifi hardware (board and coax cable)... ANYWAYYYY the conclusion is that for some reasons -- these G1's and their external memory (the SD) hold onto info somewhere and i believe theres potential for SOMETHING to become corrupt that we dont even know about, that does not show up on logcat, that stays with the phone....
then there is always potential for a HARDWARE ISSUE that we could be unaware of... at this point, for you and me it seems like kind of a guessing game lol.
are u sure u have death or danger spl and when u wipe do this
1 factory wipe
2 wipe ext partition
3 repair ext partition then flash ur rom and reboot
Yep, I'm 100% sure. I also did fastboot erase system -w, reflashed recovery, radio, tried another SD card and so on, and so on... Even unrooting and rooting again didn't help.
Instead of using the pc try flashing on ur phone from sd and reflaash ur radio and spl from the sd and see wht happens u probably don't have danger spl because its required to flash bigger roms like eclair and etc and post again if it works or not
Sent from my HTC Dream using XDA App on CM 6.00 RC3
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?
Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...
xduser1 said:
Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...
Click to expand...
Click to collapse
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.
xduser1 said:
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.
Click to expand...
Click to collapse
I have the same issue with every 8.1 build I have tried. I think LOS is less problematic and I have fewer disconnects reconnects. Glad I'm not the only one with the issue. I was going to flash back to stock to see if the issue persists, but I'm pretty sure Bluetooth is incomplete for the N6 and 8.1. Every ROM i have tried also misreports Bluetooth battery drain.
I can say, I use a Bluetooth headset and external gps and connect to my ODBII port all simultaneously without any disconnects. I'm using ABC for shamu and it's been rock solid. I also do not get misreported numbers.
If that's one of the rooms you've tried, and you've clean flashed, then think about trying inn safe mode. Maybe some app is interfering. Safe mode will reset your settings and desktop. You probably want to take a nandroid first.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Several data points:
On 8.1, I only experience this issue with this one car, all other bluetooth devices and cars that I've tried worked perfect.
I do not experience this issue with this car on 7.1.2..
All ROMs were clean flashed.
Also tried friend's Pixel 2 with stock 8.1, and it worked with this car without any issues.
Build fingerprint: 'xiaomi/violet/violet:9/PKQ1.181203.001/V10.3.7.0.PFHINXM:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 30714, tid: 30720, name: Jit thread pool >>> io.va.exposed <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
r0 00000000 r1 e6b6d264 r2 dfb0b000 r3 00000000
r4 dfb0b000 r5 e5e51240 r6 e5861e1a r7 e5861e13
r8 00000043 r9 e58b2374 r10 e58b3e9c r11 0000005b
ip dfaff8c8 sp dfaff8d0 lr e56849b9 pc e5698b22
backtrace:
#00 pc 00264b22 /system/lib/libart.so (offset 0x258000) (art:rofileSaver::NotifyJitActivity()+2)
#01 pc 0000affe [anon:libc_malloc:dfb00000]
This was the error thrown and the app just crashed. I tried reseting app preferences clearing cache data installing and reinstalling app but it didnt work. Please help!!