search

wasdennnoch / AndroidN-ify

[Discontinued] An Xposed module to use features introduced in Android N on your LP+ Device
265 stars 93 forks source link

System ui crash on clicking battery tile #922

Open abhijitkadam03 opened 8 years ago

abhijitkadam03 commented 8 years ago

System ui crash and restart on clicking battery tile. (on all the builds so far) Running stock 6.0.1 aosp rom from google (Android one)

Logcat: https://drive.google.com/open?id=0B9NF9zUoJGzeQjhUdGJnZ2tXcDg

xposed error loghttps://drive.google.com/open?id=0B9NF9zUoJGzeYW1ETjhmUlBpems

systemuicrash_logcat.txt systemuicrash_logcat.txt systemuicrash_logcat.txt error.txt

abhijitkadam03 commented 8 years ago

sorry the earlier log attached was not proper. I am attaching it again error.txt Log report battery crash systemui.txt

abhijitkadam03 commented 8 years ago

Had done the same. Anyways I repeated it again. Please find the logcat here: https://drive.google.com/file/d/0B9NF9zUoJGzeVWR0bkRkRFVUUkE/view?usp=drivesdk

joeyhuab commented 8 years ago

Hi there. I think I found the cause of the issue. When I checked the versions, version 569 is the final version with the battery QS tile working with our stock ROM (https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/569/). Upon updating to version 570, the SystemUI crashes already whenever clicking the Battery QS tile. (https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/570/changes).

Here are the notable changes you made that may have led to the crashing issue: https://github.com/wasdennnoch/AndroidN-ify/commit/4e6eae61e9fe2dd1e646b15fd3e6a2d501fcc992

abhijitkadam03 commented 8 years ago

True, it works on 569. Didn't work on any version after it. By the way the latest version with Google assistant support is awesome, just loving it.

Let me know if you need any more logs

joeyhuab commented 8 years ago

@wasdennnoch hope this helps. Found the changes you made that insinuated the crashes.

wasdennnoch commented 8 years ago

@joeyhuab if you are having the same issue can you post a logcat too?

joeyhuab commented 8 years ago

@wasdennnoch Will try to recreate the issue and get back to you. I'm currently using the battery tile from GravityBox so I'll try the stock one from N-ify when I get home.

joeyhuab commented 8 years ago

Here you go @wasdennnoch I found that the intent tile of for the BatteryView is causing the crashed. Just don't know how to resolve it. Here's the logcat I did while doing the crash. Disabled all other Xposed modules. Hope you see what's the cause.

2016-10-24-18-07-49.txt

wasdennnoch commented 8 years ago

I'm wondering if your ROM disabled crash logging, the only thing in the log is

10-24 18:07:34.619 F/libc    (1876): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3be8d7ac in tid 1876 (ndroid.systemui)
10-24 18:07:34.721 F/DEBUG   (160): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-24 18:07:34.721 F/DEBUG   (160): Build fingerprint: 'google/H940/H940_sprout:6.0.1/MOB31E/3142026:user/release-keys'
10-24 18:07:34.722 F/DEBUG   (160): Revision: '0'
10-24 18:07:34.722 F/DEBUG   (160): ABI: 'arm'
10-24 18:07:34.722 F/DEBUG   (160): pid: 1876, tid: 1876, name: ndroid.systemui  >>> com.android.systemui <<<
10-24 18:07:34.722 E/DEBUG   (160): AM write failed: Broken pipe
10-24 18:07:34.722 F/DEBUG   (160): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3be8d7ac
10-24 18:07:34.756 F/DEBUG   (160):     r0 6f3795ec  r1 134e9b00  r2 00269d36  r3 b32c5070
10-24 18:07:34.756 F/DEBUG   (160):     r4 00269d36  r5 6f378c48  r6 134e9b00  r7 6f8935e8
10-24 18:07:34.756 F/DEBUG   (160):     r8 12c477c0  r9 b7b88700  sl 6fb3e138  fp be9b74b4
10-24 18:07:34.756 F/DEBUG   (160):     ip b32c5070  sp be9b7430  lr 71c93a73  pc b4cffc48  cpsr 000e0030
10-24 18:07:34.759 F/DEBUG   (160): 
10-24 18:07:34.759 F/DEBUG   (160): backtrace:
10-24 18:07:34.759 F/DEBUG   (160):     #00 pc 000eac48  /system/lib/libart.so (art_quick_imt_conflict_trampoline+7)
10-24 18:07:34.759 F/DEBUG   (160):     #01 pc 71c93a71  /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x1ef2000)
10-24 18:07:35.405 F/DEBUG   (160): 
10-24 18:07:35.405 F/DEBUG   (160): Tombstone written to: /data/tombstones/tombstone_02

Can you please try to grab the log from another source, for example the Xposed module 'Cracker' which catches (almost) all crashes.

EDIT: Actually wait, this looks like a native error which could be there because of failed IPC, so the SystemUI couldn't communicate with the system to fetch the battery stats. That may be very hard or even impossible to fix.

abhijitkadam03 commented 8 years ago

This is stock ROM provided by Google for android one phones. Will try the xposed module 'cracker' and report back.

abhijitkadam03 commented 8 years ago 
build.board: unknown
build.bootloader: 0.6.7
build.brand: google
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: AQ4502_sprout
build.display: MOB31E
build.fingerprint: google/AQ4502/AQ4502_sprout:6.0.1/MOB31E/3142026:user/release-keys
build.hardware: sprout
build.host: vped13.mtv.corp.google.com
build.id: MOB31E
build.manufacturer: Micromax
build.model: Micromax AQ4502
build.product: AQ4502
build.radio: unknown
build.serial: 2864004CI86CAI2
build.tags: release-keys
build.time: 1470967455000
build.type: user
build.user: android-build
version.codename: REL
version.incremental: 3142026
version.release: 6.0.1
version.sdk_int: 23

10-24 23:12:34.378 F/libc    (4707): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c8657ac in tid 4707 (ndroid.systemui)
10-24 23:12:34.480 F/DEBUG   (166): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-24 23:12:34.481 F/DEBUG   (166): Build fingerprint: 'google/AQ4502/AQ4502_sprout:6.0.1/MOB31E/3142026:user/release-keys'
10-24 23:12:34.481 F/DEBUG   (166): Revision: '0'
10-24 23:12:34.481 F/DEBUG   (166): ABI: 'arm'
10-24 23:12:34.481 E/DEBUG   (166): AM write failed: Broken pipe
10-24 23:12:34.481 F/DEBUG   (166): pid: 4707, tid: 4707, name: ndroid.systemui  >>> com.android.systemui <<<
10-24 23:12:34.481 F/DEBUG   (166): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3c8657ac
10-24 23:12:34.500 F/DEBUG   (166):     r0 6fcc15ec  r1 134fd580  r2 00269fab  r3 b32e9070
10-24 23:12:34.501 F/DEBUG   (166):     r4 00269fab  r5 6fcc0c48  r6 134fd580  r7 701db5e8
10-24 23:12:34.501 F/DEBUG   (166):     r8 1344e4c0  r9 b8d95600  sl 70486138  fp be8104b4
10-24 23:12:34.501 F/DEBUG   (166):     ip b32e9070  sp be810430  lr 725dba73  pc b4d35c48  cpsr 000e0030
10-24 23:12:34.503 F/DEBUG   (166): 
10-24 23:12:34.503 F/DEBUG   (166): backtrace:
10-24 23:12:34.503 F/DEBUG   (166):     #00 pc 000eac48  /system/lib/libart.so (art_quick_imt_conflict_trampoline+7)
10-24 23:12:34.503 F/DEBUG   (166):     #01 pc 725dba71  /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x1ef2000)
10-24 23:12:35.244 F/DEBUG   (166): 
10-24 23:12:35.244 F/DEBUG   (166): Tombstone written to: /data/tombstones/tombstone_02

Cracker was unable to detect the crash. I have pasted the log. Hope it helps

joeyhuab commented 8 years ago

Nothing shows up when I try to re-create the crash. It just crashes the SystemUI and same logs are found.

On Oct 25, 2016 1:37 AM, "Joey Huab" iamtherealjoeyhuab@gmail.com wrote:

Alright. Thanks for the info. Downloader Cracker already. Will try to do it again.

On Oct 25, 2016 1:30 AM, "MrWasdennnoch" notifications@github.com wrote:

I'm wondering if your ROM disabled crash logging, the only thing in the log is

10-24 18:07:34.619 F/libc (1876): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3be8d7ac in tid 1876 (ndroid.systemui) 10-24 18:07:34.721 F/DEBUG (160): * * * * * * * * * * * * * * * * 10-24 18:07:34.721 F/DEBUG (160): Build fingerprint: 'google/H940/H940_sprout:6.0.1/MOB31E/3142026:user/release-keys' 10-24 18:07:34.722 F/DEBUG (160): Revision: '0' 10-24 18:07:34.722 F/DEBUG (160): ABI: 'arm' 10-24 18:07:34.722 F/DEBUG (160): pid: 1876, tid: 1876, name: ndroid.systemui >>> com.android.systemui <<< 10-24 18:07:34.722 E/DEBUG (160): AM write failed: Broken pipe 10-24 18:07:34.722 F/DEBUG (160): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3be8d7ac 10-24 18:07:34.756 F/DEBUG (160): r0 6f3795ec r1 134e9b00 r2 00269d36 r3 b32c5070 10-24 18:07:34.756 F/DEBUG (160): r4 00269d36 r5 6f378c48 r6 134e9b00 r7 6f8935e8 10-24 18:07:34.756 F/DEBUG (160): r8 12c477c0 r9 b7b88700 sl 6fb3e138 fp be9b74b4 10-24 18:07:34.756 F/DEBUG (160): ip b32c5070 sp be9b7430 lr 71c93a73 pc b4cffc48 cpsr 000e0030 10-24 18:07:34.759 F/DEBUG (160): 10-24 18:07:34.759 F/DEBUG (160): backtrace: 10-24 18:07:34.759 F/DEBUG (160): #00 pc 000eac48 /system/lib/libart.so (art_quick_imt_conflict_trampoline+7) 10-24 18:07:34.759 F/DEBUG (160): #01 pc 71c93a71 /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x1ef2000) 10-24 18:07:35.405 F/DEBUG (160): 10-24 18:07:35.405 F/DEBUG (160): Tombstone written to: /data/tombstones/tombstone_02

Can you please try to grab the log from another source, for example the Xposed module 'Cracker' which catches (almost) all crashes.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wasdennnoch/AndroidN-ify/issues/922#issuecomment-255808414, or mute the thread https://github.com/notifications/unsubscribe-auth/AGW-Jxx92IpUPR-1MHO8U8K071C4pdlDks5q3OsggaJpZM4KCulT .

joeyhuab commented 8 years ago

Alright. Thanks for the info. Downloader Cracker already. Will try to do it again.

On Oct 25, 2016 1:30 AM, "MrWasdennnoch" notifications@github.com wrote:

I'm wondering if your ROM disabled crash logging, the only thing in the log is

10-24 18:07:34.619 F/libc (1876): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3be8d7ac in tid 1876 (ndroid.systemui) 10-24 18:07:34.721 F/DEBUG (160): * * * * * * * * * * * * * * * * 10-24 18:07:34.721 F/DEBUG (160): Build fingerprint: 'google/H940/H940_sprout:6.0.1/MOB31E/3142026:user/release-keys' 10-24 18:07:34.722 F/DEBUG (160): Revision: '0' 10-24 18:07:34.722 F/DEBUG (160): ABI: 'arm' 10-24 18:07:34.722 F/DEBUG (160): pid: 1876, tid: 1876, name: ndroid.systemui >>> com.android.systemui <<< 10-24 18:07:34.722 E/DEBUG (160): AM write failed: Broken pipe 10-24 18:07:34.722 F/DEBUG (160): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3be8d7ac 10-24 18:07:34.756 F/DEBUG (160): r0 6f3795ec r1 134e9b00 r2 00269d36 r3 b32c5070 10-24 18:07:34.756 F/DEBUG (160): r4 00269d36 r5 6f378c48 r6 134e9b00 r7 6f8935e8 10-24 18:07:34.756 F/DEBUG (160): r8 12c477c0 r9 b7b88700 sl 6fb3e138 fp be9b74b4 10-24 18:07:34.756 F/DEBUG (160): ip b32c5070 sp be9b7430 lr 71c93a73 pc b4cffc48 cpsr 000e0030 10-24 18:07:34.759 F/DEBUG (160): 10-24 18:07:34.759 F/DEBUG (160): backtrace: 10-24 18:07:34.759 F/DEBUG (160): #00 pc 000eac48 /system/lib/libart.so (art_quick_imt_conflict_trampoline+7) 10-24 18:07:34.759 F/DEBUG (160): #01 pc 71c93a71 /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x1ef2000) 10-24 18:07:35.405 F/DEBUG (160): 10-24 18:07:35.405 F/DEBUG (160): Tombstone written to: /data/tombstones/tombstone_02

Can you please try to grab the log from another source, for example the Xposed module 'Cracker' which catches (almost) all crashes.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wasdennnoch/AndroidN-ify/issues/922#issuecomment-255808414, or mute the thread https://github.com/notifications/unsubscribe-auth/AGW-Jxx92IpUPR-1MHO8U8K071C4pdlDks5q3OsggaJpZM4KCulT .