ViperOne + ElementalX dofstrim wakelock issue - solved - Sprint HTC One (M7)

I am using unlocked and activated HTC One M7 sprint edition in GSM network, rooted. ViperOne appeared to be the best ROM for my device, along with brilliant ElementalX kernel. but as some other people I've suffered from dotfstrim kernel wakelock that usually came at nights when phone was charged and sleeping on the table.
I've found that trim file system service could be made manually using fstrim tool and starting from 4.3 trim events processed at the volume daemon (vold) triggered by idle maintenance event. that event is interesting thing, triggered only when battery charge is > 80% and phone was not active for more than 73 minutes, but not more than once per day. now I was almost sure that dofstrim orphaned wakelock was left by that event processing.
instead of waiting for next event, I did more research and found that event can be fired anytime by shell command:
am idle-maintenance
voila! wakelock was there. knowing that idle maintenance running vold internal procedure for trim, I've checked daemon sources and found the following:
fstrim.c //
......
#define FSTRIM_WAKELOCK "dofstrim"
......
SLOGI("Finished fstrim work.\n");
release_wake_lock(FSTRIM_WAKELOCK);
......
acquire_wake_lock(PARTIAL_WAKE_LOCK, FSTRIM_WAKELOCK);
......
//
so wakelock was set before trim process but never released. logfile shown me following:
E/Vold (32356): failed to open /fstab.m7
E/Vold (32356): Error reading configuration (No such file or directory)... continuing anyways
......
I/fstrim (32356): Starting fstrim work...
...and then.. boom!
F/libc (31832): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 32353 (vold)
I/DEBUG ( 248): Build fingerprint: 'htc/sprint_wwe/m7wls:4.4.2/KOT49H/325784.5:user/release-keys'
I/DEBUG ( 248): AM write failure (32 / Broken pipe)
I/DEBUG ( 248): Write to AM fail, close AM fd
I/DEBUG ( 248): Revision: '4'
I/DEBUG ( 248): pid: 31832, tid: 32353, name: vold >>> /system/bin/vold <<<
I/DEBUG ( 248): debuggerd: checkTellHTCSettings
I/DEBUG ( 248): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
I/DEBUG ( 248): r0 2a01abd5 r1 fffffff0 r2 00000003 r3 00000000
I/DEBUG ( 248): r4 2a02017c r5 2a025290 r6 00000000 r7 b6b28d08
I/DEBUG ( 248): r8 00000000 r9 2a018bf6 sl b6c282d4 fp b6fac2f4
I/DEBUG ( 248): ip 00000003 sp b6b28ce8 lr b6fd1de1 pc 2a00f6ca cpsr 200b0030
so vold crashed but orphaned wakelock remained and prevents phone from sleeping ((
in theory problem caused by additional protected partition that exists on sprint model only but I had no time for vold recompiling so I've created a quite straightforward hex patch that simply removes trim process. so wakelock released and everyone's happy. just a note. vold will not run trim anymore so it must be done manually from shell by fstrim tool or from UI by LagFix app like once per week.
attached archive contains new (patched) and old (original) vold files that you have to upload to device using adb or any other method:
adb push vold /system/bin/vold
make sure you have fixed vold permissions from terminal like
chmod 755 /system/bin/vold
or you risk to stop on boot screen.
ps. this night my phone spent only 2% of battery for 7 hours. radio + wifi was on. so it was sleeping well ))

Verizon M7 solution?
I have the same issue with the dofstrim kernel wakelock preventing my phone from going into deep sleep after a charging cycle. Will your solution also work for the Verizon M7? I am rooted with the NuSenseSIX rom and ElementalX kernel.

aewald73 said:
I have the same issue with the dofstrim kernel wakelock preventing my phone from going into deep sleep after a charging cycle. Will your solution also work for the Verizon M7? I am rooted with the NuSenseSIX rom and ElementalX kernel.
Click to expand...
Click to collapse
I'd say probably not.. it's best not to flash zip files which are for different variants (they have different partition maps). Try posting here.

Any chance you can post sort of a noob guide on this fix? I'm a little confused with the steps you already posted, and then the additional steps needed for the weekly fix. Thanks.

fachadick said:
Any chance you can post sort of a noob guide on this fix? I'm a little confused with the steps you already posted, and then the additional steps needed for the weekly fix. Thanks.
Click to expand...
Click to collapse
While I cannot guarantee it will work for you, heres what I did:
1.) Extract the vold file from the .zip to the adb directory
2.) Have adb installed
3.) Do this:
Code:
adb devices
adb root
adb remount
adb push vold /system/bin/vold
adb shell
su
chmod 755 /system/bin/vold
CTRL-C
adb remount
Reboot and it should work.

Related

cant flash

i dunno what's happening
trying to flash few roms jacxhero, cest hero and cyano
and all of them dont boot
ive got the latest spl recovery and radio
sometimes my g1 goes loop sometimes it boots but lots of fc's
i wipe correctly
and adb logcat shows
Code:
I/DEBUG ( 2120): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 2120): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRB43/148830:user/ota-rel-keys,release-keys'
I/DEBUG ( 2120): pid: 3027, tid: 3034 >>> android.process.acore <<<
I/DEBUG ( 2120): signal 11 (SIGSEGV), fault addr 0000001c
i cant flash my phone for the second day
btw later i already user jacxhero and cyano but now it fails
someone i need help
Did you clear out your partitions before flashing any of the roms?
Supreme said it, clean out your partion, namely you ext, there are remnant files left over from a previous build that will not allow you to boot
im properly cleaning /data and /system/sd
i've tried reformating my card but it was useless
re partition it.
do you get these force closes's? "process.android.media"? if so, re partition it.
but what i would do is reformat and re partition it. thatway it eliminates any sd problems because your essentially starting from scratch

Random reboot

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.

[Q] Constant reboots on 4.4.2

I have a C6503 (Brazil) and after updating do 4.4.2 my phone reboots many times a day.
While it's on standby it reboot.
Yesterday during a call it rebooted.
Most of the times it's a few seconds after i unlock the phone , the phone freezes the UI and reboot. But it's never a boot loop. Sometimes i can use the phone for a few hours with no reboot.
I've updated via SUS from 4.3 to 4.4.2, and also installed 3 different versions of 4.4.2 (Baltic, Nordic, and Generic Brazil) via Flashtools, and in all of the three the problem happens.
I don't know what else to try!
Can someone give me a hint of what should i try next?
The log before it reboots is as follows (got it from Android Tuner):
(just the last lines, it's not complete)
Code:
I/ 123.634399 No errors detected
I/ 123.634399 Going down for restart now
I/ 123.632446
I/ 123.632415 Restarting Linux version 3.4.0-perf-g32ce454 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Apr 9 16:52:42 2014
I/ 123.632232
I/ 123.631622
I/ 123.631622 Restarting Linux version 3.4.0-perf-g32ce454 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Apr 9 16:52:42 2014
I/ 118.622985 Rebooting in 5 seconds..
I/ 118.621856 &@[email protected]:*mpdecision*
I/ 118.120025 wcnss_8960: crash shutdown : 1
I/ 118.119628 Kernel panic - not syncing: Fatal exception in interrupt
I/ 118.119415 ---[ end trace da227214a82491bb ]---
I/ 118.119018 Code: e1a01004 e300270d e59f000c eb603280 (e7f001f2)
I/ 118.118774 [<c0249fbc>] (sys_poll+0x48/0xa8) from [<c0106120>] (ret_fast_syscall+0x0/0x30)
I/ 118.118347 [<c0249db4>] (do_sys_poll+0x1e4/0x360) from [<c0249fbc>] (sys_poll+0x48/0xa8)
I/ 118.117919 [<c023aad8>] (fput+0x210/0x224) from [<c0249db4>] (do_sys_poll+0x1e4/0x360)
I/ 118.117645 [<c0887f80>] (__irq_svc+0x40/0x70) from [<c023aad8>] (fput+0x210/0x224)
I/ 118.117218 3ba0: 00000000 00000000 c0706c60 d8c83bc0 c0249db4 c023aad8 20000013 ffffffff
I/ 118.116790 3b80: 00000002 dc75f91c dc75f900 00000000 d8c83c0c 00000000 b6b018f4 d8c83c1c
I/ 118.116394 3b60: dc75f900 00000000
I/ 118.116180 Exception stack(0xd8c83b78 to 0xd8c83bc0)
I/ 118.115783 [<c01004b8>] (gic_handle_irq+0x90/0x10c) from [<c0887f80>] (__irq_svc+0x40/0x70)
I/ 118.115356 [<c01069e4>] (handle_IRQ+0x80/0xc0) from [<c01004b8>] (gic_handle_irq+0x90/0x10c)
I/ 118.115081 [<c01824f8>] (irq_exit+0x48/0xa0) from [<c01069e4>] (handle_IRQ+0x80/0xc0)
I/ 118.114654 [<c0181f64>] (__do_softirq+0x11c/0x27c) from [<c01824f8>] (irq_exit+0x48/0xa0)
I/ 118.114257 [<c0188b88>] (run_timer_softirq+0x1fc/0x354) from [<c0181f64>] (__do_softirq+0x11c/0x27c)
I/ 118.113800 [<bf06f0b4>] (hdd_ssr_timer_cb+0x2c/0x3c [wlan]) from [<c0188b88>] (run_timer_softirq+0x1fc/0x354)
And in the middle of the log i found this too:
Code:
I/ 118.098236 Stack: (0xd8c83ac8 to 0xd8c84000)
I/ 118.098022 Process mpdecision (pid: 2012, stack limit = 0xd8c822f0)
AND in the same log:
Code:
I/ 118.028839 CPU: 0 Tainted: P W O (3.4.0-perf-g32ce454 #1)
I/ 118.027709 Modules linked in: wlan(O) texfat(PO) cfg80211
I/ 118.027465 Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
I/ 118.026885 kernel BUG at /home/hudsonslave/root/workspace/offbuild_lagan-1.3_android_matrix/HUDSON_PRODUCT/odin/HUDSON_VARIANT/user/label/CM-12/kernel/../vendor/qcom/opensource/wlan/prima/CORE/HDD/src/wlan_hdd_early_suspend.c:1805!
I/ 118.026641 ------------[ cut here ]------------
I/ 118.026123 VOS BUG in hdd_ssr_timer_cb Line 1805
I/ 118.025848 wlan: [0:F :HDD] hdd_ssr_timer_cb: HDD SSR timer expired
I/ 117.572509 wlan: [1312:E :HDD] wlan_hdd_cfg80211_scan: HDD context is not valid
I/ 117.572082 wlan: [1312:E :HDD] wlan_hdd_validate_context: LOGP in Progress. Ignore!!!
I/ 116.565490 afe_send_hw_delay: config cmd failed
I/ 116.565032 afe_callback: cmd = 0x100dc returned error = 0x3
But most of the times Wifi isn't on, neither the 3g data connection.
Got two other reboots, the log is here with different messages:
http://pastebin.com/TSgiBTdL
http://pastebin.com/xX8dMfae
In the last few hours got at least five reboots, all with no wifi connection.
This might be some hardware problem?
Help anyone, thanks!
This is the Z section. The ZL Q&A forum is here - http://forum.xda-developers.com/xperia-zl/help
I also get the same problem sometimes after i unlock the screen
But its not hardware problem and its only with 4.4.2
Xperia™ Z (C6602) with Tapatalk
androidfreak70 said:
I also get the same problem sometimes after i unlock the screen
But its not hardware problem and its only with 4.4.2
Xperia™ Z (C6602) with Tapatalk
Click to expand...
Click to collapse
Same here.
I´ve downgraded do 4.3 and it´s running smooth, no reboots in the last two days.
Do you still use 4.4.2?
saddambea said:
Same here.
I´ve downgraded do 4.3 and it´s running smooth, no reboots in the last two days.
Do you still use 4.4.2?
Click to expand...
Click to collapse
Yeah
Xperia™ Z (C6602) with Tapatalk
After downgrading to 4.3, after a couple of days using it, it started to reboot. So it´s not a problem only in 4.4.2...
Guess i´ll have to send it to support...
Im having the exact same problem
saddambea said:
After downgrading to 4.3, after a couple of days using it, it started to reboot. So it´s not a problem only in 4.4.2...
Guess i´ll have to send it to support...
Click to expand...
Click to collapse
Okay so I have the xperia z and im using the android version 4.1.2 model number C6616. Yesterday my phone started to act up and do the same thing where if I dont have it plugged into my dock it will reboot even before I input my code for my sin card...sometimes it will reboot just after I input my code. But if i have the phone on my dock and keep it charging it never reboots for me...it works great. and then when I take it off the dock....it usually reboots but not for couple hours could be sooner the time varies and in order for me to use the phone when I start it up I have to put it on my dock and once I do that I have no problems again...but I dont like to keep it on the dock especially when its fully charged but once I take it off it will start to reboot again. Can anyone help me with this problem...to me it sounds like the battery because its fine when its on the dock but when I take it off the dock thats when it starts to reboot. I havent updated my phone either because I have a broken pin in my usb slot thats why I went out to buy a dock so I could at least use my phone because they wouldnt fix it for me and because I didnt get this fixed Im unable to use anything that requires the use of the usb. I cant see it being a problem because I havent updated the phone...I still think it sounds like the battery....HELP please I need to find out what is wrong if anyone has had this problem before....Thanks
londoner62 said:
Okay so I have the xperia z and im using the android version 4.1.2 model number C6616. Yesterday my phone started to act up and do the same thing where if I dont have it plugged into my dock it will reboot even before I input my code for my sin card...sometimes it will reboot just after I input my code. But if i have the phone on my dock and keep it charging it never reboots for me...it works great. and then when I take it off the dock....it usually reboots but not for couple hours could be sooner the time varies and in order for me to use the phone when I start it up I have to put it on my dock and once I do that I have no problems again...but I dont like to keep it on the dock especially when its fully charged but once I take it off it will start to reboot again. Can anyone help me with this problem...to me it sounds like the battery because its fine when its on the dock but when I take it off the dock thats when it starts to reboot. I havent updated my phone either because I have a broken pin in my usb slot thats why I went out to buy a dock so I could at least use my phone because they wouldnt fix it for me and because I didnt get this fixed Im unable to use anything that requires the use of the usb. I cant see it being a problem because I havent updated the phone...I still think it sounds like the battery....HELP please I need to find out what is wrong if anyone has had this problem before....Thanks
Click to expand...
Click to collapse
I sent my phone for service and got back a brand new cell phone. They said that my old phone did not had fix. We'll never know what was happening...

Viewing Magisk Manager apk file in a file explorer causes Fatal Signal

Simply viewing the Magisk Manager apk file (downloaded from APKmirror) causes the file explorer app to crash. The crash occurs when you are scrolling down the list of files and Magisk Manager apk is next to be shown.
Tested with Solid Explorer and CM13 Stock File Manager.
The offending apk files are:
Magisk Manager 5.1.1
Magisk Manager 5.1.0
The rest of the 5.0 release is untested. Currently have 4.3.3 installed and the apk does not cause any crashes.
Installing one of the offending apk's will severely mess up my phone. The phone will boot up and stay at a black screen (right when the lock screen is supposed to appear). Magisk uninstaller does NOT fix this boot up problem and I had to resort to re-flashing my ROM.
My setup:
Nexus 4
CM13.0 2016-12-21 Snapshot
Magisk Manger v4.3.3
MagiskSu v12.0
Here is the ADB log:
Code:
07-25 01:28:16.106 8548-8610/? I/SolidExplorer: pl.solidexplorer.thumbs.ThumbnailManager$FileThumbTask#run(ThumbnailManager.java:511)
07-25 01:28:16.106 8548-8610/? I/SolidExplorer: Cache size: 1006.27 KB
07-25 01:28:16.230 8548-8610/? I/SolidExplorer: pl.solidexplorer.thumbs.ThumbnailManager$FileThumbTask#run(ThumbnailManager.java:511)
07-25 01:28:16.230 8548-8610/? I/SolidExplorer: Cache size: 1.02 MB
07-25 01:28:16.316 8548-8610/? I/SolidExplorer: pl.solidexplorer.thumbs.ThumbnailManager$FileThumbTask#run(ThumbnailManager.java:511)
07-25 01:28:16.316 8548-8610/? I/SolidExplorer: Cache size: 1.05 MB
07-25 01:28:16.358 8548-8610/? A/libc: invalid address or address of corrupt block 0x430d87fe passed to dlfree
07-25 01:28:16.370 8548-8610/? A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xdeadbaad in tid 8610 (pool-3-thread-1)
07-25 01:28:16.371 736-736/? I/DEBUG: property debug.db.uid not set; NOT waiting for gdb.
07-25 01:28:16.371 736-736/? I/DEBUG: HINT: adb shell setprop debug.db.uid 100000
07-25 01:28:16.371 736-736/? I/DEBUG: HINT: adb forward tcp:5039 tcp:5039
07-25 01:28:16.473 736-736/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-25 01:28:16.473 736-736/? A/DEBUG: CM Version: '13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-mako'
07-25 01:28:16.473 736-736/? A/DEBUG: Build fingerprint: 'google/occam/mako:5.1.1/LMY48M/2167285:user/release-keys'
07-25 01:28:16.473 736-736/? A/DEBUG: Revision: '0'
07-25 01:28:16.473 736-736/? A/DEBUG: ABI: 'arm'
07-25 01:28:16.473 736-736/? A/DEBUG: pid: 8548, tid: 8610, name: pool-3-thread-1 >>> pl.solidexplorer2 <<<
07-25 01:28:16.473 736-736/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
07-25 01:28:16.515 736-736/? A/DEBUG: Abort message: 'invalid address or address of corrupt block 0x430d87fe passed to dlfree'
07-25 01:28:16.515 736-736/? A/DEBUG: r0 00000000 r1 00000000 r2 00000000 r3 00000002
07-25 01:28:16.515 736-736/? A/DEBUG: r4 430d87fe r5 deadbaad r6 b6d72f38 r7 98fcc000
07-25 01:28:16.515 736-736/? A/DEBUG: r8 430d8806 r9 9bc730cc sl b6cd38db fp b6cd38e4
07-25 01:28:16.516 736-736/? A/DEBUG: ip b6d6d5d8 sp 9bc72fb8 lr b6d3ecdf pc b6d3ecde cpsr 600f0030
07-25 01:28:16.524 736-736/? A/DEBUG: backtrace:
07-25 01:28:16.524 736-736/? A/DEBUG: #00 pc 00030cde /system/lib/libc.so (dlfree+1285)
07-25 01:28:16.524 736-736/? A/DEBUG: #01 pc 000157a9 /system/lib/libandroidfw.so (_ZN7android13ResStringPool6uninitEv+38)
07-25 01:28:16.524 736-736/? A/DEBUG: #02 pc 000164f9 /system/lib/libandroidfw.so (_ZN7android10ResXMLTree6uninitEv+14)
07-25 01:28:16.524 736-736/? A/DEBUG: #03 pc 00016517 /system/lib/libandroidfw.so (_ZN7android10ResXMLTreeD1Ev+4)
07-25 01:28:16.525 736-736/? A/DEBUG: #04 pc 00013263 /system/lib/libandroidfw.so (_ZN7android12AssetManager10getPkgNameEPKc+258)
07-25 01:28:16.525 736-736/? A/DEBUG: #05 pc 000132bf /system/lib/libandroidfw.so (_ZN7android12AssetManager18getBasePackageNameEj+62)
07-25 01:28:16.525 736-736/? A/DEBUG: #06 pc 0008967f /system/lib/libandroid_runtime.so
07-25 01:28:16.525 736-736/? A/DEBUG: #07 pc 737486e1 /data/dalvik-cache/arm/[email protected]@boot.oat (offset 0x1f93000)
07-25 01:28:16.554 736-736/? W/debuggerd: type=1400 audit(0.0:1525): avc: denied { search } for name="default" dev="tmpfs" ino=8252 scontext=u:r:debuggerd:s0 tcontext=u:object_r:storage_file:s0 tclass=dir permissive=0
07-25 01:28:17.416 1230-8698/? W/ActivityManager: Force finishing activity pl.solidexplorer2/pl.solidexplorer.SolidExplorer
07-25 01:28:17.417 736-736/? A/DEBUG: Tombstone written to: /data/tombstones/tombstone_02
07-25 01:28:17.417 736-736/? E/DEBUG: AM write failed: Broken pipe
07-25 01:28:17.418 1230-1250/? I/BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
07-25 01:28:17.502 1230-1403/? W/InputDispatcher: channel '5ab4980 pl.solidexplorer2/pl.solidexplorer.SolidExplorer (server)' ~ Consumer closed input channel or an error occurred. events=0x9
07-25 01:28:17.502 1230-1403/? E/InputDispatcher: channel '5ab4980 pl.solidexplorer2/pl.solidexplorer.SolidExplorer (server)' ~ Channel is unrecoverably broken and will be disposed!
07-25 01:28:17.511 1230-1241/? I/WindowState: WIN DEATH: Window{5ab4980 u0 pl.solidexplorer2/pl.solidexplorer.SolidExplorer}
07-25 01:28:17.511 1230-1241/? W/InputDispatcher: Attempted to unregister already unregistered input channel '5ab4980 pl.solidexplorer2/pl.solidexplorer.SolidExplorer (server)'
07-25 01:28:17.518 1230-8698/? W/ActivityManager: Exception thrown during pause
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:727)
at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:879)
at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:2992)
at com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:2848)
at com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:2828)
at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:12449)
at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:12320)
at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:13036)
at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:12541)
at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)
07-25 01:28:17.523 724-724/? E/lowmemorykiller: Error writing /proc/8548/oom_score_adj; errno=22
07-25 01:28:17.538 748-748/? I/Zygote: Process 8548 exited due to signal (11)
07-25 01:28:17.617 1230-4016/? I/ActivityManager: Process pl.solidexplorer2 (pid 8548) has died
07-25 01:28:17.674 1230-1412/? I/OpenGLRenderer: Initialized EGL, version 1.4
Corrupt downloads?
Delete the files and download again.
Edit: Since your file explorer crashes when viewing the thumbnails of the files, use terminal to delete them... The command is:
Code:
rm [I]<path-to-file>[/I]
Didgeridoohan said:
Corrupt downloads?
Delete the files and download again.
Edit: Since your file explorer crashes when viewing the thumbnails of the files, use terminal to delete them... The command is:
Code:
rm [I]<path-to-file>[/I]
Click to expand...
Click to collapse
SHA-256 and SHA-1 File hashes match the ones on APKmirror so no, the downloads are not corrupt.
Yes I can either delete using the terminal, or on a PC via USB connection, or in Downloads and long-press --> delete.
AndrewDam said:
SHA-256 and SHA-1 File hashes match the ones on APKmirror so no, the downloads are not corrupt.
Yes I can either delete using the terminal, or on a PC via USB connection, or in Downloads and long-press --> delete.
Click to expand...
Click to collapse
Still... Worth a shot deleting them and starting over.
Apk view crash
Same problem here on Moto G (titan) running on Mokee OS (based on cm13).
It is not the corrupt apk. And I also encountered same problem while trying to install Pixlr 3.0.2.apk.
The file explorer crashes, when about to browse that particular .apk file.
I once somehow installed Magisk Manager whilst crashing, after that the whole system went crazy! All the running apps started crashing continuously, even the Nova Launcher, the inbuilt Nox Launcher. EVERY SINGLE APP!
Then I powered down the phone, went to recovery and deleted the app manually.
But if try to install again, the problem kicks in!
And I also observed one more thing, no matter what, the app's icon is not displayed by the file manager. I tried the same thing with in-built file manager, which doesn't display the app icon, the file manager didnot crash this time. But if I install, BOOM! LITERALLY EVERYTHING STARTS TO CRASH!!
Same problem on my G2 Mini - fatal signal, file explorer crashing. When I installed the app, opening it caused soft reboot.
same here, using dual boot patcher when i tap the roms section, it crashed.. i found fatal signal in the logs
device: redmi note 3 sd (kenzo)
rom: nitrogen os
magisk 13.3

VirtualXposed App crashed on opening it on Redmi note 7 pro (9 PKQ1.181203.001 vers)

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!!

Categories

Resources