Camera crash and error "Can't connect to the camera" - Nexus 6P Q&A, Help & Troubleshooting

Just got my phone and it is completely stock.
When using the video camera and switching between slow-motion modes (normal, 120 FPS & 240 FPS) the camera app crashes and I get the error message "Can't connect to the camera".
Then the camera wont work, no matter the app I use, that uses the camera.
After a reboot it works again though.
Sometimes it crashes the first time I've changed the mode to 240, sometimes after cycling through the modes a bit, but it always happen and it wont many cycles (1-3).
I've recorded functional 240 FPS videos, so that part works.
I've tried starting the phone in safe mode and deleting cache partition, with the same result.
There are others with the same problem, but it doesn't seem to be a common error.
Is there anyone on this board that has the same problem?
Is it a software problem or hardware, and is RMA the only option?

I would factory reset. It seems to fix a few software issues (Android System battery problem & glitchy Chrome for myself) that have been seen on stock. Google support will probably want you to do this before RMA anyway, and if it fixes the issue you won't have to go through RMA brain damage. (Although I've heard Google is very good in this regard.)
Or, you could flash Chroma ROM like I did. Clean sailing now!
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
Actually, never mind flashing a ROM... Best to rule out hardware defect first.

I'm in the same boat! hoping to find others who have this problem and get clear on whether it's a hardware or software issue. Mine first crashed when i tried loading 240fps slow-mo. restart was the only thing to get it going again. disabled google camera (which reverts to initial version), app updated back to latest, seemed to be fine when i went to 240fps mode, thought it was all resolved. then it came back again AFTER i recorded a slow-mo test at 240fps. When it's working (after restart) it works GREAT! but when this glitch occurs, can't do anything else with camera until I restart. I've attached screenshots of what it looks like when i try to take a pic after a crash.
I guess this is my window of opportunity to factory reset so I can unlock bootloader and root but would like to find a simpler solution if possible... anyone else out there with a similar issue?

I've had the same issue, I've corrected it with uninstalling the camera app and reinstalling it again from the play store.
I used root uninstaller pro to remove the camera app, note you must be rooted in order to use root uninstaller.
Sent from my Nexus 6P using XDA Forums Pro.

Same crash here on my Nexus 6P when I select 240 fps mode ...
full logcat is here : gist. github .com /GBouerat/1c6dd68ec655738d7e4a
12-13 13:05:23.188 599 8062 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x57d in tid 8062 (CAM_MctCtrl)
12-13 13:05:23.261 509 509 I SELinux : SELinux: Loaded file_contexts contexts from /file_contexts.
12-13 13:05:23.267 918 3459 W NativeCrashListener: Couldn't find ProcessRecord for pid 599
12-13 13:05:23.267 509 509 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-13 13:05:23.267 509 509 E DEBUG : AM write failed: Broken pipe
12-13 13:05:23.267 509 509 F DEBUG : Build fingerprint: 'google/angler/angler:6.0.1/MMB29M/2431559:user/release-keys'
12-13 13:05:23.267 509 509 F DEBUG : Revision: '0'
12-13 13:05:23.267 509 509 F DEBUG : ABI: 'arm'
12-13 13:05:23.267 509 509 F DEBUG : pid: 599, tid: 8062, name: CAM_MctCtrl >>> /vendor/bin/mm-qcamera-daemon <<<
12-13 13:05:23.267 509 509 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x57d
12-13 13:05:23.281 509 509 F DEBUG : r0 0000057d r1 f52452c0 r2 00000000 r3 f71e82a8
12-13 13:05:23.281 509 509 F DEBUG : r4 0000057d r5 ead7e5c0 r6 edebf000 r7 ee7c0000
12-13 13:05:23.281 509 509 F DEBUG : r8 f518b488 r9 f71db594 sl 00000001 fp f72aa3ed
12-13 13:05:23.281 509 509 F DEBUG : ip f71db5d0 sp f1ebf180 lr f71b9ab3 pc f71a527e cpsr 60010030
12-13 13:05:23.314 509 509 F DEBUG :
12-13 13:05:23.314 509 509 F DEBUG : backtrace:
12-13 13:05:23.314 509 509 F DEBUG : #00 pc 0004027e /system/lib/libc.so (pthread_mutex_lock+3)
12-13 13:05:23.314 509 509 F DEBUG : #01 pc 00054aaf /system/lib/libc.so (je_huge_salloc+16)
12-13 13:05:23.314 509 509 F DEBUG : #02 pc 00055721 /system/lib/libc.so (ifree+84)
12-13 13:05:23.314 509 509 F DEBUG : #03 pc 0005867b /system/lib/libc.so (je_free+374)
12-13 13:05:23.314 509 509 F DEBUG : #04 pc 00037404 /vendor/lib/libmmcamera_faceproc.so (MINT0170+24)
12-13 13:05:23.314 509 509 F DEBUG : #05 pc 0003b758 /vendor/lib/libmmcamera_faceproc.so (FACEPROC_DeleteDetection+36)
12-13 13:05:23.314 509 509 F DEBUG : #06 pc 000291b3 /vendor/lib/libmmcamera_imglib.so (facial_parts_wrap_destroy+210)
12-13 13:05:23.314 509 509 F DEBUG : #07 pc 0002595d /vendor/lib/libmmcamera_imglib.so (faceproc_hw_comp_deinit+316)
12-13 13:05:23.314 509 509 F DEBUG : #08 pc 00022cdf /vendor/lib/libmmcamera2_imglib_modules.so (module_faceproc_client_comp_destroy+42)
12-13 13:05:23.314 509 509 F DEBUG : #09 pc 0001e46f /vendor/lib/libmmcamera2_imglib_modules.so (module_faceproc_port_check_caps_unreserve+478)
12-13 13:05:23.314 509 509 F DEBUG : #10 pc 00031359 /vendor/lib/libmmcamera2_imglib_modules.so
12-13 13:05:23.314 509 509 F DEBUG : #11 pc 00031d4d /vendor/lib/libmmcamera2_imglib_modules.so
12-13 13:05:23.314 509 509 F DEBUG : #12 pc 0000565b /vendor/lib/liboemcamera.so (mct_module_unlink+118)
12-13 13:05:23.314 509 509 F DEBUG : #13 pc 0000b445 /vendor/lib/liboemcamera.so
12-13 13:05:23.315 509 509 F DEBUG : #14 pc 0001170d /vendor/lib/liboemcamera.so (mct_list_operate_nodes+36)
12-13 13:05:23.315 509 509 F DEBUG : #15 pc 00011715 /vendor/lib/liboemcamera.so (mct_list_operate_nodes+44)
12-13 13:05:23.315 509 509 F DEBUG : #16 pc 00011715 /vendor/lib/liboemcamera.so (mct_list_operate_nodes+44)
12-13 13:05:23.315 509 509 F DEBUG : #17 pc 00011715 /vendor/lib/liboemcamera.so (mct_list_operate_nodes+44)
12-13 13:05:23.315 509 509 F DEBUG : #18 pc 0000f159 /vendor/lib/liboemcamera.so (mct_stream_destroy+424)
12-13 13:05:23.315 509 509 F DEBUG : #19 pc 000082cd /vendor/lib/liboemcamera.so
12-13 13:05:23.315 509 509 F DEBUG : #20 pc 000041e9 /vendor/lib/liboemcamera.so
12-13 13:05:23.315 509 509 F DEBUG : #21 pc 0003f883 /system/lib/libc.so (__pthread_start(void*)+30)
12-13 13:05:23.315 509 509 F DEBUG : #22 pc 00019f75 /system/lib/libc.so (__start_thread+6)
12-13 13:05:23.667 509 509 F DEBUG :
12-13 13:05:23.667 509 509 F DEBUG : Tombstone written to: /data/tombstones/tombstone_05
12-13 13:05:23.671 918 934 I BootReceiver: Copying /data/tombstones/tombstone_05 to DropBox (SYSTEM_TOMBSTONE)
12-13 13:05:23.695 514 8064 E QCamera3HWI: static void qcamera::QCamera3HardwareInterface::camEvtHandle(uint32_t, mm_camera_event_t*, void*): Fatal, camera daemon died

Related

[Q] qtadb and droid explorer

i use both of those programs and a few months ago
when i was on sense 3.5 roms i noticed that when i tried to reboot or shutdown
thru them nothing happened
yesterday i updated both programs and tried it on the rom in my sig and it worked perfectly
so i flashed a sense 3.5 rom and the shutdown and reboot doesnt work on it
does anyone have any clue why it works on cm9 ics and not sense 3.5
sdk and adb are installed correctly and the variable is set
and it is seen thru command prompt adb devices and reboot and shutdown work also
would just like to try and get it working with those 2 programs
Thanks
The last time I tried a Sense ROM was Daekin's (3.5) and Dj Danik's (2.0? Dont remember). And QtADB's reboot commands did work - though it is a while back when I used Sense, I do remember because I do a bunch of mods to any ROM I flash and invariably use QtADB for logcat as well as other stuff, including reboot...
I will get to installing one of them in my spare HD2 to try and confirm, but not until this weekend (work, Work, WORK!!!)
ph03n!x said:
The last time I tried a Sense ROM was Daekin's (3.5) and Dj Danik's (2.0? Dont remember). And QtADB's reboot commands did work - though it is a while back when I used Sense, I do remember because I do a bunch of mods to any ROM I flash and invariably use QtADB for logcat as well as other stuff, including reboot...
I will get to installing one of them in my spare HD2 to try and confirm, but not until this weekend (work, Work, WORK!!!)
Click to expand...
Click to collapse
the last time i think i got it to work was on dungs 3.0 sense rom
ive tried it on tbd and pixelfreaks and nothing
those are the only sense 3.5 roms i use mainly tbd
cool i can wait
Thanks
Ok, here is what happens when I try the reboot option in QtADB:
Code:
14:51:13.912 Info DEBUG 84 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
14:51:13.912 Info DEBUG 84 Build fingerprint: 'htccn_chs/htc_runnymede/runnymede:2.3.5/GRJ90/248020.4:user/release-keys'
14:51:13.912 Info DEBUG 84 pid: 1289, tid: 1289 >>> reboot <<<
14:51:13.912 Info DEBUG 84 signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000c
14:51:13.912 Info DEBUG 84 r0 00000000 r1 be8d8b04 r2 80808080 r3 00000035
14:51:13.912 Info DEBUG 84 r4 00000000 r5 be8d8b64 r6 00000000 r7 00000001
14:51:13.912 Info DEBUG 84 r8 00000000 r9 be8d8b04 10 be8d8b24 fp 00000000
14:51:13.913 Info DEBUG 84 ip 00000080 sp be8d8ad0 lr afd193b1 pc afd19a28 cpsr 20000030
14:51:13.913 Info DEBUG 84 d0 64612f6e6962732f d1 0000000000000070
14:51:13.913 Info DEBUG 84 d2 0000000000000072 d3 000000000000006f
14:51:13.913 Info DEBUG 84 d4 0000000000000000 d5 0000000000000000
14:51:13.913 Info DEBUG 84 d6 0000000000000000 d7 0000000000000000
14:51:13.913 Info DEBUG 84 d8 0000000000000000 d9 0000000000000000
14:51:13.913 Info DEBUG 84 d10 0000000000000000 d11 0000000000000000
14:51:13.913 Info DEBUG 84 d12 0000000000000000 d13 0000000000000000
14:51:13.913 Info DEBUG 84 d14 0000000000000000 d15 0000000000000000
14:51:13.913 Info DEBUG 84 d16 0000000000000000 d17 0000000000000000
14:51:13.913 Info DEBUG 84 d18 0000000000000000 d19 0000000000000000
14:51:13.914 Info DEBUG 84 d20 0000000000000000 d21 0000000000000000
14:51:13.914 Info DEBUG 84 d22 0000000000000000 d23 0000000000000000
14:51:13.914 Info DEBUG 84 d24 0000000000000000 d25 0000000000000000
14:51:13.914 Info DEBUG 84 d26 0000000000000000 d27 0000000000000000
14:51:13.914 Info DEBUG 84 d28 0000000000000000 d29 0000000000000000
14:51:13.914 Info DEBUG 84 d30 0000000000000000 d31 0000000000000000
14:51:13.914 Info DEBUG 84 scr 00000000
14:51:13.914 Info DEBUG 84
14:51:13.914 Info DEBUG 84 #00 pc 00019a28 /system/lib/libc.so
14:51:13.914 Info DEBUG 84 #01 pc 000193ac /system/lib/libc.so
14:51:13.914 Info DEBUG 84 #02 pc 00008e00 /system/bin/reboot
14:51:13.914 Info DEBUG 84 #03 pc 000154c2 /system/lib/libc.so
14:51:13.915 Info DEBUG 84
14:51:13.915 Info DEBUG 84 code around pc:
14:51:13.915 Info DEBUG 84 afd19a08 624561c4 f8c062c6 62018028 81f0e8bd
14:51:13.915 Info DEBUG 84 afd19a18 e92d688b 46044ff7 2b004689 8128f000
14:51:13.915 Info DEBUG 84 afd19a28 07028980 6921d501 4620b941 fc54f003
14:51:13.915 Info DEBUG 84 afd19a38 f7f8b120 2209fe97 e1166002 7000f8d9
14:51:13.915 Info DEBUG 84 afd19a48 683e89a3 3708687d 0a02f013 e017d103
14:51:13.915 Info DEBUG 84
14:51:13.915 Info DEBUG 84 code around lr:
14:51:13.915 Info DEBUG 84 afd19390 b086b510 9004460c e8a8f7fc 2301a901
14:51:13.915 Info DEBUG 84 afd193a0 90039302 a8049005 46209001 fb34f000
14:51:13.916 Info DEBUG 84 afd193b0 bd10b006 b5108981 0309f001 d0012b09
14:51:13.916 Info DEBUG 84 afd193c0 e0012000 fcbaf7ff bf00bd10 47f0e92d
14:51:13.916 Info DEBUG 84 afd193d0 fb014d50 447df802 4614468a f1b8461e
14:51:13.916 Info DEBUG 84
14:51:13.916 Info DEBUG 84 stack:
14:51:13.916 Info DEBUG 84 be8d8a90 00000000
14:51:13.916 Info DEBUG 84 be8d8a94 00000000
14:51:13.916 Info DEBUG 84 be8d8a98 00000000
14:51:13.916 Info DEBUG 84 be8d8a9c 00000000
14:51:13.916 Info DEBUG 84 be8d8aa0 00000000
14:51:13.916 Info DEBUG 84 be8d8aa4 00000000
14:51:13.916 Info DEBUG 84 be8d8aa8 00000000
14:51:13.917 Info DEBUG 84 be8d8aac 00000000
14:51:13.917 Info DEBUG 84 be8d8ab0 00000000
14:51:13.917 Info DEBUG 84 be8d8ab4 00000000
14:51:13.917 Info DEBUG 84 be8d8ab8 00000000
14:51:13.917 Info DEBUG 84 be8d8abc 00000000
14:51:13.917 Info DEBUG 84 be8d8ac0 00000000
14:51:13.917 Info DEBUG 84 be8d8ac4 00000000
14:51:13.917 Info DEBUG 84 be8d8ac8 df002777
14:51:13.917 Info DEBUG 84 be8d8acc e3a070ad
14:51:13.917 Info DEBUG 84 #00 be8d8ad0 00000000
14:51:13.917 Info DEBUG 84 be8d8ad4 be8d8b04
14:51:13.918 Info DEBUG 84 be8d8ad8 80808080
14:51:13.918 Info DEBUG 84 be8d8adc 00000000
14:51:13.918 Info DEBUG 84 be8d8ae0 be8d8b64
14:51:13.918 Info DEBUG 84 be8d8ae4 00000000
14:51:13.918 Info DEBUG 84 be8d8ae8 00000001
14:51:13.918 Info DEBUG 84 be8d8aec 00000000
14:51:13.918 Info DEBUG 84 be8d8af0 00000000
14:51:13.918 Info DEBUG 84 be8d8af4 be8d8b24
14:51:13.918 Info DEBUG 84 be8d8af8 00000000
14:51:13.918 Info DEBUG 84 be8d8afc afd193b1 /system/lib/libc.so
14:51:13.918 Info DEBUG 84 #01 be8d8b00 00009485 /system/bin/reboot
14:51:13.918 Info DEBUG 84 be8d8b04 be8d8b10
14:51:13.919 Info DEBUG 84 be8d8b08 00000001
14:51:13.919 Info DEBUG 84 be8d8b0c 00000035
14:51:13.919 Info DEBUG 84 be8d8b10 0000949b /system/bin/reboot
14:51:13.919 Info DEBUG 84 be8d8b14 00000035
14:51:13.919 Info DEBUG 84 be8d8b18 0000a114
14:51:13.919 Info DEBUG 84 be8d8b1c 00008e03 /system/bin/reboot
14:51:13.919 Info BootReceiver 233 Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
This with Sense of Eclipse 3.14/ Marc1706's kernel v0.2.0
Note that a command prompt adb reboot works perfectly.
Daekin/ Marc - any thoughts?

WifiStateMachin Bug

Hey,
Issue: Once screen times out or is locked, the phone restarts. WiFi does not enable. Can reproduce every time.
Phone: N9005, BNL8 Modem/Bootloader, CM12 5.5 (same on every build though, since first builds).
Tried: Flashing back to stock then coming back, using KK Modem/Bootloader, Checking MD5.
The issue seems to be only with CM, as using any TW rom the Wifi works fine and the phone doesn't reboot.
Logcat: This is the whole 15 seconds before screen goes off http://pastebin.com/gVvxXzkj
Code:
--------- beginning of crash
01-17 18:39:58.686 696 847 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x5600001 in tid 847 (WifiStateMachin)
01-17 18:39:58.687 303 695 E audio_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null
01-17 18:39:58.691 295 347 I ThermalEngine: Mitigation:CPU[1]:2496000 Khz
01-17 18:39:58.692 696 4675 I WifiNative-HAL: Waiting for HAL events mWifiHalHandle=-2088550336
01-17 18:39:58.693 696 4675 E wifi : getStaticLongField sWifiHalHandle 0x5c6bea1c
01-17 18:39:58.804 300 300 I DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-17 18:39:58.804 300 300 I DEBUG : Build fingerprint: 'samsung/hltexx/hlte:4.4.2/KOT49H/N9005XXUENC2:user/release-keys'
01-17 18:39:58.804 300 300 I DEBUG : Revision: '8'
01-17 18:39:58.804 300 300 I DEBUG : ABI: 'arm'
01-17 18:39:58.804 300 300 I DEBUG : pid: 696, tid: 847, name: WifiStateMachin >>> system_server <<<
01-17 18:39:58.804 300 300 I DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x5600001
01-17 18:39:58.824 300 300 I DEBUG : r0 05600001 r1 781dfac8 r2 781d05cd r3 ffffffa8
01-17 18:39:58.824 300 300 I DEBUG : r4 05600001 r5 00000000 r6 781dfeb0 r7 6231e740
01-17 18:39:58.824 300 300 I DEBUG : r8 781dfad0 r9 6848d400 sl 781d05cd fp 131cb160
01-17 18:39:58.824 300 300 I DEBUG : ip b4cd1c94 sp 6231e718 lr 781d3d5d pc 781d3d5c cpsr 600f0030
01-17 18:39:58.825 300 300 I DEBUG :
01-17 18:39:58.825 300 300 I DEBUG : backtrace:
01-17 18:39:58.825 300 300 I DEBUG : #00 pc 00008d5c /system/lib/libwifi-service.so (getWifiHandle(wifi_interface_info*)+7)
01-17 18:39:58.825 300 300 I DEBUG : #01 pc 00008d65 /system/lib/libwifi-service.so (getHalInfo(wifi_interface_info*)+4)
01-17 18:39:58.825 300 300 I DEBUG : #02 pc 0000dd2d /system/lib/libwifi-service.so (wifi_get_link_stats+44)
01-17 18:39:58.825 300 300 I DEBUG : #03 pc 00004ed1 /system/lib/libwifi-service.so
01-17 18:39:58.825 300 300 I DEBUG : #04 pc 000379dd /data/dalvik-cache/arm/[email protected]@[email protected]
01-17 18:39:59.492 4678 4687 E cutils-trace: Error opening trace file: Permission denied (13)
01-17 18:40:03.535 300 300 I DEBUG :
01-17 18:40:03.535 300 300 I DEBUG : Tombstone written to: /data/tombstones/tombstone_02
01-17 18:40:03.552 696 726 I Choreographer: Skipped 285 frames! The application may be doing too much work on its main thread.
01-17 18:40:03.555 696 727 E libsuspend: Error reading from /sys/power/wakeup_count: Interrupted system call
01-17 18:40:03.551 847 847 W WifiStateMachin: type=1701 audit(0.0:268): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj=u:r:system_server:s0 reason="memory violation" sig=11
01-17 18:40:03.561 696 719 I BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
01-17 18:40:03.565 696 2214 E SharedPreferencesImpl: Couldn't create directory for SharedPreferences file shared_prefs/log_files.xml
Bump

MIUI 8

Hello I do not want to be rude, I wanted to make a request some dev would be able to bring MIUI 8 for this device, I do not have enough knowledge to do it for me
I'm going to be attempting my first port/ROM once I get my desktop up and running in the next week or two
fireball0093 said:
I'm going to be attempting my first port/ROM once I get my desktop up and running in the next week or two
Click to expand...
Click to collapse
God luck
fireball0093 said:
I'm going to be attempting my first port/ROM once I get my desktop up and running in the next week or two
Click to expand...
Click to collapse
I do not want to be rude (it is not my intention) as it goes with this ROM ????
nick more said:
I do not want to be rude (it is not my intention) as it goes with this ROM ????
Click to expand...
Click to collapse
Are you meaning was I referring to porting MIUI to our device or another rom? If so, I do plan on attempting to port MIUI
fireball0093 said:
Are you meaning was I referring to porting MIUI to our device or another rom? If so, I do plan on attempting to port MIUI
Click to expand...
Click to collapse
Sorry, I did not get it!
nick more said:
Sorry, I did not get it!
Click to expand...
Click to collapse
No that's fine! No need to be sorry
fireball0093 said:
No that's fine! No need to be sorry
Click to expand...
Click to collapse
What I wanted was if someone can do ROM miui for our device
nick more said:
What I wanted was if someone can do ROM miui for our device
Click to expand...
Click to collapse
Yeah, I really want MIUI as well. I had the Xiaomi Mi4 a while back but broke it sadly and got the Moto G4 Play. MIUI is probably my favorite build of Android. Once I get some spare money I will be buying a USB wifi adapter for my desktop to start attempting to get a good port of MIUI, my laptop doesn't have much storage space.
I did some work and managed to make a flashable zip, however I can't go any further since I'm getting "Updater process ended with signal: 11" in TWRP :/
I tried fixing it, searching and whatnot but couldn't fix it. I'll try some more things and let you know how it goes.
EDIT: I've managed to fix error 11, but then I got "System partition has unexpected contents after OTA update" and then an error 7.
EDIT2: Okay, managed to fix the issues and trying to boot now.
EDIT3: I got it to the boot animation however it doesn't go any further. Can't get logcat.
EDIT4: Couldn't get past boot animation. I'll try to change things one by one later and see if that works.
EDIT5: I've tried and tried but I just can't get past this message! It keeps appearing in my logcat every 20 seconds and I'm just stuck at the boot logo...
Code:
11-09 05:50:49.389 2231 2231 I Radio-JNI: register_android_hardware_Radio DONE
11-09 05:50:49.489 2231 2231 F Configuration: Unable to find static field mcc
11-09 05:50:49.489 2231 2231 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2231 (main)
11-09 05:50:49.489 295 295 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
11-09 05:50:49.489 295 295 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
11-09 05:50:49.489 295 295 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
11-09 05:50:49.591 295 295 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-09 05:50:49.592 295 295 F DEBUG : CM Version: '13.0-20161109-UNOFFICIAL-harpia'
11-09 05:50:49.592 295 295 F DEBUG : Build fingerprint: 'motorola/harpia/harpia:6.0.1/MPI24.241-15.3/3:user/release-keys'
11-09 05:50:49.592 295 295 F DEBUG : Revision: '0'
11-09 05:50:49.592 295 295 F DEBUG : ABI: 'arm'
11-09 05:50:49.593 295 295 F DEBUG : pid: 2231, tid: 2231, name: main >>> zygote <<<
11-09 05:50:49.593 295 295 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-09 05:50:49.617 295 295 F DEBUG : Abort message: 'Unable to find static field mcc'
11-09 05:50:49.617 295 295 F DEBUG : r0 00000000 r1 000008b7 r2 00000006 r3 b6f63b8c
11-09 05:50:49.617 295 295 F DEBUG : r4 b6f63b94 r5 b6f63b44 r6 00000002 r7 0000010c
11-09 05:50:49.617 295 295 F DEBUG : r8 becb7994 r9 becb79a8 sl 00000001 fp becb79e8
11-09 05:50:49.617 295 295 F DEBUG : ip 00000006 sp becb7410 lr b6ccb5fd pc b6ccd9ec cpsr 400d0010
11-09 05:50:49.626 295 295 F DEBUG :
11-09 05:50:49.626 295 295 F DEBUG : backtrace:
11-09 05:50:49.626 295 295 F DEBUG : #00 pc 000429ec /system/lib/libc.so (tgkill+12)
11-09 05:50:49.626 295 295 F DEBUG : #01 pc 000405f9 /system/lib/libc.so (pthread_kill+32)
11-09 05:50:49.626 295 295 F DEBUG : #02 pc 0001c4ff /system/lib/libc.so (raise+10)
11-09 05:50:49.626 295 295 F DEBUG : #03 pc 000196b1 /system/lib/libc.so (__libc_android_abort+34)
11-09 05:50:49.626 295 295 F DEBUG : #04 pc 000175c4 /system/lib/libc.so (abort+4)
11-09 05:50:49.627 295 295 F DEBUG : #05 pc 00008db3 /system/lib/libcutils.so (__android_log_assert+86)
11-09 05:50:49.627 295 295 F DEBUG : #06 pc 000af0b9 /system/lib/libandroid_runtime.so
11-09 05:50:49.627 295 295 F DEBUG : #07 pc 000af1d5 /system/lib/libandroid_runtime.so (_ZN7android42register_android_content_res_ConfigurationEP7_JNIEnv+56)
11-09 05:50:49.627 295 295 F DEBUG : #08 pc 0005e261 /system/lib/libandroid_runtime.so
11-09 05:50:49.627 295 295 F DEBUG : #09 pc 0005e743 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime8startRegEP7_JNIEnv+26)
11-09 05:50:49.627 295 295 F DEBUG : #10 pc 0005fa8f /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEEb+330)
11-09 05:50:49.627 295 295 F DEBUG : #11 pc 00001721 /system/bin/app_process32
11-09 05:50:49.627 295 295 F DEBUG : #12 pc 00017471 /system/lib/libc.so (__libc_init+44)
11-09 05:50:49.627 295 295 F DEBUG : #13 pc 00001868 /system/bin/app_process32
11-09 05:50:49.781 295 295 F DEBUG :
11-09 05:50:49.781 295 295 F DEBUG : Tombstone written to: /data/tombstones/tombstone_03
11-09 05:50:49.836 2619 2619 W init : type=1400 audit(0.0:18): avc: denied { execute_no_trans } for uid=0 path="/system/xbin/shelld" dev="mmcblk0p39" ino=4387 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
bsevcenk said:
I did some work and managed to make a flashable zip, however I can't go any further since I'm getting "Updater process ended with signal: 11" in TWRP :/
I tried fixing it, searching and whatnot but couldn't fix it. I'll try some more things and let you know how it goes.
EDIT: I've managed to fix error 11, but then I got "System partition has unexpected contents after OTA update" and then an error 7.
EDIT2: Okay, managed to fix the issues and trying to boot now.
EDIT3: I got it to the boot animation however it doesn't go any further. Can't get logcat.
EDIT4: Couldn't get past boot animation. I'll try to change things one by one later and see if that works.
Click to expand...
Click to collapse
If you want anyone to test builds of it too, shoot me a PM and I will gladly test
bsevcenk said:
I did some work and managed to make a flashable zip, however I can't go any further since I'm getting "Updater process ended with signal: 11" in TWRP :/
I tried fixing it, searching and whatnot but couldn't fix it. I'll try some more things and let you know how it goes.
EDIT: I've managed to fix error 11, but then I got "System partition has unexpected contents after OTA update" and then an error 7.
EDIT2: Okay, managed to fix the issues and trying to boot now.
EDIT3: I got it to the boot animation however it doesn't go any further. Can't get logcat.
EDIT4: Couldn't get past boot animation. I'll try to change things one by one later and see if that works.
Click to expand...
Click to collapse
If you want send me a PM and the test
No one can make MIUI for this device ??????
bsevcenk said:
I did some work and managed to make a flashable zip, however I can't go any further since I'm getting "Updater process ended with signal: 11" in TWRP :/
I tried fixing it, searching and whatnot but couldn't fix it. I'll try some more things and let you know how it goes.
EDIT: I've managed to fix error 11, but then I got "System partition has unexpected contents after OTA update" and then an error 7.
EDIT2: Okay, managed to fix the issues and trying to boot now.
EDIT3: I got it to the boot animation however it doesn't go any further. Can't get logcat.
EDIT4: Couldn't get past boot animation. I'll try to change things one by one later and see if that works.
EDIT5: I've tried and tried but I just can't get past this message! It keeps appearing in my logcat every 20 seconds and I'm just stuck at the boot logo...
Code:
11-09 05:50:49.389 2231 2231 I Radio-JNI: register_android_hardware_Radio DONE
11-09 05:50:49.489 2231 2231 F Configuration: Unable to find static field mcc
11-09 05:50:49.489 2231 2231 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2231 (main)
11-09 05:50:49.489 295 295 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
11-09 05:50:49.489 295 295 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
11-09 05:50:49.489 295 295 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
11-09 05:50:49.591 295 295 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-09 05:50:49.592 295 295 F DEBUG : CM Version: '13.0-20161109-UNOFFICIAL-harpia'
11-09 05:50:49.592 295 295 F DEBUG : Build fingerprint: 'motorola/harpia/harpia:6.0.1/MPI24.241-15.3/3:user/release-keys'
11-09 05:50:49.592 295 295 F DEBUG : Revision: '0'
11-09 05:50:49.592 295 295 F DEBUG : ABI: 'arm'
11-09 05:50:49.593 295 295 F DEBUG : pid: 2231, tid: 2231, name: main >>> zygote <<<
11-09 05:50:49.593 295 295 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-09 05:50:49.617 295 295 F DEBUG : Abort message: 'Unable to find static field mcc'
11-09 05:50:49.617 295 295 F DEBUG : r0 00000000 r1 000008b7 r2 00000006 r3 b6f63b8c
11-09 05:50:49.617 295 295 F DEBUG : r4 b6f63b94 r5 b6f63b44 r6 00000002 r7 0000010c
11-09 05:50:49.617 295 295 F DEBUG : r8 becb7994 r9 becb79a8 sl 00000001 fp becb79e8
11-09 05:50:49.617 295 295 F DEBUG : ip 00000006 sp becb7410 lr b6ccb5fd pc b6ccd9ec cpsr 400d0010
11-09 05:50:49.626 295 295 F DEBUG :
11-09 05:50:49.626 295 295 F DEBUG : backtrace:
11-09 05:50:49.626 295 295 F DEBUG : #00 pc 000429ec /system/lib/libc.so (tgkill+12)
11-09 05:50:49.626 295 295 F DEBUG : #01 pc 000405f9 /system/lib/libc.so (pthread_kill+32)
11-09 05:50:49.626 295 295 F DEBUG : #02 pc 0001c4ff /system/lib/libc.so (raise+10)
11-09 05:50:49.626 295 295 F DEBUG : #03 pc 000196b1 /system/lib/libc.so (__libc_android_abort+34)
11-09 05:50:49.626 295 295 F DEBUG : #04 pc 000175c4 /system/lib/libc.so (abort+4)
11-09 05:50:49.627 295 295 F DEBUG : #05 pc 00008db3 /system/lib/libcutils.so (__android_log_assert+86)
11-09 05:50:49.627 295 295 F DEBUG : #06 pc 000af0b9 /system/lib/libandroid_runtime.so
11-09 05:50:49.627 295 295 F DEBUG : #07 pc 000af1d5 /system/lib/libandroid_runtime.so (_ZN7android42register_android_content_res_ConfigurationEP7_JNIEnv+56)
11-09 05:50:49.627 295 295 F DEBUG : #08 pc 0005e261 /system/lib/libandroid_runtime.so
11-09 05:50:49.627 295 295 F DEBUG : #09 pc 0005e743 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime8startRegEP7_JNIEnv+26)
11-09 05:50:49.627 295 295 F DEBUG : #10 pc 0005fa8f /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEEb+330)
11-09 05:50:49.627 295 295 F DEBUG : #11 pc 00001721 /system/bin/app_process32
11-09 05:50:49.627 295 295 F DEBUG : #12 pc 00017471 /system/lib/libc.so (__libc_init+44)
11-09 05:50:49.627 295 295 F DEBUG : #13 pc 00001868 /system/bin/app_process32
11-09 05:50:49.781 295 295 F DEBUG :
11-09 05:50:49.781 295 295 F DEBUG : Tombstone written to: /data/tombstones/tombstone_03
11-09 05:50:49.836 2619 2619 W init : type=1400 audit(0.0:18): avc: denied { execute_no_trans } for uid=0 path="/system/xbin/shelld" dev="mmcblk0p39" ino=4387 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Click to expand...
Click to collapse
Hi, i have some experience in porting ROMs, if you can send me that ZIP i can try to make it functional. The only thing i didn't know how to do is the boot.img. So it don't bootup. If you can send my i will be grateful
Obs: Sorry for my english, I'm brazillian
Leeonardoo said:
Hi, i have some experience in porting ROMs, if you can send me that ZIP i can try to make it functional. The only thing i didn't know how to do is the boot.img. So it don't bootup. If you can send my i will be grateful
Obs: Sorry for my english, I'm brazillian
Click to expand...
Click to collapse
Yeah sure, here you go. Thank you!
Leeonardoo said:
Hi, i have some experience in porting ROMs, if you can send me that ZIP i can try to make it functional. The only thing i didn't know how to do is the boot.img. So it don't bootup. If you can send my i will be grateful
Obs: Sorry for my english, I'm brazillian
Click to expand...
Click to collapse
If you consume it would be great, I do not have much knowledge on the subject but in what I can help here I will be
bsevcenk said:
I did some work and managed to make a flashable zip, however I can't go any further since I'm getting "Updater process ended with signal: 11" in TWRP :/
I tried fixing it, searching and whatnot but couldn't fix it. I'll try some more things and let you know how it goes.
EDIT: I've managed to fix error 11, but then I got "System partition has unexpected contents after OTA update" and then an error 7.
EDIT2: Okay, managed to fix the issues and trying to boot now.
EDIT3: I got it to the boot animation however it doesn't go any further. Can't get logcat.
EDIT4: Couldn't get past boot animation. I'll try to change things one by one later and see if that works.
EDIT5: I've tried and tried but I just can't get past this message! It keeps appearing in my logcat every 20 seconds and I'm just stuck at the boot logo...
Code:
11-09 05:50:49.389 2231 2231 I Radio-JNI: register_android_hardware_Radio DONE
11-09 05:50:49.489 2231 2231 F Configuration: Unable to find static field mcc
11-09 05:50:49.489 2231 2231 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2231 (main)
11-09 05:50:49.489 295 295 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
11-09 05:50:49.489 295 295 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
11-09 05:50:49.489 295 295 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
11-09 05:50:49.591 295 295 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-09 05:50:49.592 295 295 F DEBUG : CM Version: '13.0-20161109-UNOFFICIAL-harpia'
11-09 05:50:49.592 295 295 F DEBUG : Build fingerprint: 'motorola/harpia/harpia:6.0.1/MPI24.241-15.3/3:user/release-keys'
11-09 05:50:49.592 295 295 F DEBUG : Revision: '0'
11-09 05:50:49.592 295 295 F DEBUG : ABI: 'arm'
11-09 05:50:49.593 295 295 F DEBUG : pid: 2231, tid: 2231, name: main >>> zygote <<<
11-09 05:50:49.593 295 295 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-09 05:50:49.617 295 295 F DEBUG : Abort message: 'Unable to find static field mcc'
11-09 05:50:49.617 295 295 F DEBUG : r0 00000000 r1 000008b7 r2 00000006 r3 b6f63b8c
11-09 05:50:49.617 295 295 F DEBUG : r4 b6f63b94 r5 b6f63b44 r6 00000002 r7 0000010c
11-09 05:50:49.617 295 295 F DEBUG : r8 becb7994 r9 becb79a8 sl 00000001 fp becb79e8
11-09 05:50:49.617 295 295 F DEBUG : ip 00000006 sp becb7410 lr b6ccb5fd pc b6ccd9ec cpsr 400d0010
11-09 05:50:49.626 295 295 F DEBUG :
11-09 05:50:49.626 295 295 F DEBUG : backtrace:
11-09 05:50:49.626 295 295 F DEBUG : #00 pc 000429ec /system/lib/libc.so (tgkill+12)
11-09 05:50:49.626 295 295 F DEBUG : #01 pc 000405f9 /system/lib/libc.so (pthread_kill+32)
11-09 05:50:49.626 295 295 F DEBUG : #02 pc 0001c4ff /system/lib/libc.so (raise+10)
11-09 05:50:49.626 295 295 F DEBUG : #03 pc 000196b1 /system/lib/libc.so (__libc_android_abort+34)
11-09 05:50:49.626 295 295 F DEBUG : #04 pc 000175c4 /system/lib/libc.so (abort+4)
11-09 05:50:49.627 295 295 F DEBUG : #05 pc 00008db3 /system/lib/libcutils.so (__android_log_assert+86)
11-09 05:50:49.627 295 295 F DEBUG : #06 pc 000af0b9 /system/lib/libandroid_runtime.so
11-09 05:50:49.627 295 295 F DEBUG : #07 pc 000af1d5 /system/lib/libandroid_runtime.so (_ZN7android42register_android_content_res_ConfigurationEP7_JNIEnv+56)
11-09 05:50:49.627 295 295 F DEBUG : #08 pc 0005e261 /system/lib/libandroid_runtime.so
11-09 05:50:49.627 295 295 F DEBUG : #09 pc 0005e743 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime8startRegEP7_JNIEnv+26)
11-09 05:50:49.627 295 295 F DEBUG : #10 pc 0005fa8f /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEEb+330)
11-09 05:50:49.627 295 295 F DEBUG : #11 pc 00001721 /system/bin/app_process32
11-09 05:50:49.627 295 295 F DEBUG : #12 pc 00017471 /system/lib/libc.so (__libc_init+44)
11-09 05:50:49.627 295 295 F DEBUG : #13 pc 00001868 /system/bin/app_process32
11-09 05:50:49.781 295 295 F DEBUG :
11-09 05:50:49.781 295 295 F DEBUG : Tombstone written to: /data/tombstones/tombstone_03
11-09 05:50:49.836 2619 2619 W init : type=1400 audit(0.0:18): avc: denied { execute_no_trans } for uid=0 path="/system/xbin/shelld" dev="mmcblk0p39" ino=4387 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Click to expand...
Click to collapse
Brother PM this logcat to some of our devs or modders..they will help you for sure
bsevcenk said:
Yeah sure, here you go. Thank you!
Click to expand...
Click to collapse
Thank you! I will try that!
But my phone just died and I sended that to Motorola for repair and I'm still waiting for it to came back to me... I will try that for sure when I get my phone back (hopefully until the end of this month)
And if you can help me too, it will be awesome!
---------- Post added at 04:04 PM ---------- Previous post was at 04:00 PM ----------
nick more said:
If you consume it would be great, I do not have much knowledge on the subject but in what I can help here I will be
Click to expand...
Click to collapse
For sure, when I get my phone back any help will be awesome. Then I will send you a PM
bsevcenk said:
Yeah sure, here you go. Thank you!
Click to expand...
Click to collapse
Which did you use as base ROM, reupload the file and I may help, I can edit and check boot.img
Ashutosh Sundresh said:
Which did you use as base ROM, reupload the file and I may help, I can edit and check boot.img
Click to expand...
Click to collapse
I think he used the cm 14, and he carried the miui of osprey

LePro3 don't let me play high end games

Mine le pro crashes some high end gaming apps. Tested this for "lord of the Fallen" and "Realboxing".
Here are the crash log für lotf:
http://pastebin.com/Mq86kkv4
And here are the log for Realboxing:
http://pastebin.com/ZeJFh9Z3
I hop you could help me a bit to find out why I can't play games, wich need high recources.
Chris
For LOTF I have now logged only for Errors and got this:
Code:
02-16 10:20:19.588 23449 23483 E MediaPlayer: stop called in state 1
02-16 10:20:19.589 23449 23483 E MediaPlayer: error (-38, 0)
02-16 10:20:19.589 23449 23449 E MediaPlayer: Error (-38,0)
02-16 10:20:23.179 3674 3682 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [4, 0]
02-16 10:20:24.707 23449 23535 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xc7f80084 in tid 23535 (AudioThread 0)
02-16 10:20:24.811 629 629 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-16 10:20:24.812 629 629 F DEBUG : Build fingerprint: 'LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys'
02-16 10:20:24.812 629 629 F DEBUG : Revision: '0'
02-16 10:20:24.812 629 629 F DEBUG : ABI: 'arm'
02-16 10:20:24.813 629 629 F DEBUG : pid: 23449, tid: 23535, name: AudioThread 0 >>> com.cigames.lotfbof <<<
02-16 10:20:24.813 629 629 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xc7f80084
02-16 10:20:24.871 629 629 F DEBUG : r0 00000014 r1 00000003 r2 f742d300 r3 c7f80000
02-16 10:20:24.871 629 629 F DEBUG : r4 c9996000 r5 00000000 r6 c52a8048 r7 c7f97280
02-16 10:20:24.871 629 629 F DEBUG : r8 f7420594 r9 f742d2f4 sl 00000001 fp ce851620
02-16 10:20:24.871 629 629 F DEBUG : ip c7f80050 sp ce851528 lr f7403f31 pc f7400a5a cpsr 20010030
02-16 10:20:24.880 629 629 F DEBUG :
02-16 10:20:24.880 629 629 F DEBUG : backtrace:
02-16 10:20:24.880 629 629 F DEBUG : #00 pc 00055a5a /system/lib/libc.so (ifree+53)
02-16 10:20:24.880 629 629 F DEBUG : #01 pc 00058f2d /system/lib/libc.so (je_free+388)
02-16 10:20:24.881 629 629 F DEBUG : #02 pc 0000e7c7 /system/lib/libutils.so (_ZNK7android7RefBase9decStrongEPKv+50)
02-16 10:20:24.881 629 629 F DEBUG : #03 pc 00009955 /system/lib/libwilhelm.so
02-16 10:20:24.881 629 629 F DEBUG : #04 pc 00014115 /system/lib/libwilhelm.so
02-16 10:20:24.881 629 629 F DEBUG : #05 pc 00019163 /system/lib/libwilhelm.so
02-16 10:20:24.881 629 629 F DEBUG : #06 pc 03c26be4 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN16FSLESSoundSource4StopEv+108)
02-16 10:20:24.881 629 629 F DEBUG : #07 pc 02d05804 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN12FAudioDevice11StopSourcesER6TArrayIP13FWaveInstance17FDefaultAllocatorEi+512)
02-16 10:20:24.881 629 629 F DEBUG : #08 pc 02d064b8 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN12FAudioDevice6UpdateEb+1880)
02-16 10:20:24.881 629 629 F DEBUG : #09 pc 01613d30 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN10TGraphTaskI18FFunctionGraphTaskE11ExecuteTaskER6TArrayIP14FBaseGraphTask17FDefaultAllocatorEN13ENamedThreads4TypeE+84)
02-16 10:20:24.881 629 629 F DEBUG : #10 pc 018f021c /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN16FNamedTaskThread23ProcessTasksNamedThreadEib+180)
02-16 10:20:24.881 629 629 F DEBUG : #11 pc 018efae0 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN16FNamedTaskThread21ProcessTasksUntilQuitEi+100)
02-16 10:20:24.881 629 629 F DEBUG : #12 pc 02d10a38 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN12FAudioThread3RunEv+84)
02-16 10:20:24.881 629 629 F DEBUG : #13 pc 01928808 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN22FRunnableThreadPThread3RunEv+100)
02-16 10:20:24.881 629 629 F DEBUG : #14 pc 018f24d8 /data/app/com.cigames.lotfbof-1/lib/arm/libUE4.so (_ZN22FRunnableThreadPThread11_ThreadProcEPv+104)
02-16 10:20:24.882 629 629 F DEBUG : #15 pc 0003fa3b /system/lib/libc.so (_ZL15__pthread_startPv+30)
02-16 10:20:24.882 629 629 F DEBUG : #16 pc 00019fe5 /system/lib/libc.so (__start_thread+6)
02-16 10:20:25.483 629 629 F DEBUG :
02-16 10:20:25.483 629 629 F DEBUG : Tombstone written to: /data/tombstones/tombstone_06
02-16 10:20:25.483 629 629 E DEBUG : AM write failed: Broken pipe
02-16 10:20:25.499 3674 3682 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [4, 0]
02-16 10:20:25.600 1613 1878 E InputDispatcher: channel 'f40a44d com.cigames.lotfbof/com.epicgames.ue4.GameActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
02-16 10:20:25.811 1613 3007 E libprocessgroup: failed to kill 1 processes for processgroup 23449
02-16 10:20:25.887 1613 3007 E WindowManager: Unknown window type: 1001
I specially installed Real Boxing for you and it's working fine. I also played in HOMM3 HD. Every app worked yet. Try to reinstall, then take it full permissions and turn on it.
I tried already and homm 3 Just run smooth and fine.
Maybe its a Problem with my Software.
Wicht Rom you have?
I am on eui 5.8 18s
I have 5.9.020s with x720.
Hm, I should Update soon
But I cant ota Update, due to root.
Have you unlocked the bootloader? And inatalled twrp?
No, full stock
There are some SElinux error in your log , and this error won't be fixed in bootimage . what a pity.
Soo nie i flashed 5.9 to my device and the game works Well, now i have flashed supersu and xposed and it is crashing again
Further more i Got werid random touches when i slide in my Screen after the Update?
Andy clues?
entchen66 said:
Soo nie i flashed 5.9 to my device and the game works Well, now i have flashed supersu and xposed and it is crashing again
Further more i Got werid random touches when i slide in my Screen after the Update?
Andy clues?
Click to expand...
Click to collapse
It's probably because of exposed uninstall it, it's not supported.:good:
But with you have so much adventages

Trouble compiling 8.2.0 kernel from source for ShieldTV 2017

I am trying to compile the 8.2.0 Kernel for my Shield TV 2017. I am hoping to adding the Wireguard kernel module.
I downloaded the source linked from https://developer.nvidia.com/shield-open-source following the instructions links here https://nv-tegra.nvidia.com/gitweb/...7;hb=1a508fa42d6ae55ee0fe62a3e07559a484794108
The source code checks out fine. I set up my cross compiler by setting these environment variables
Code:
ARCH=arm64
SUBARCH=arm64
CROSS_COMPILE=/absolute/path/shield-open-source/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
I removed the CONFIG_SYSTEM_TRUSTED_KEYS="signing_key.x509" from the tegra_android_defconfig file
I then went to ~/shield-open-source/kernel/kernel-4.9 and ran
Code:
make mrproper
make tegra_android_defconfig
make -j4
There were a few warnings that got flagged as errors and caused the build to failed. I modified the make files so the warnings wouldn't be flagged as errors (ex: ccflags-y += -Wno-error=maybe-uninitialized)
There is one more error with ~/shield-open-source/hardware/nvidia/platform/t210b01/ers/kernel-dts/ers-platforms/tegra210b01-ers-common.dtsi in that it can't find <tegra210b01-cpufreq.dtsi>. I changed this to include "darcy-platforms/tegra210b01-darcy-cpufreq.dtsi"
I also added Wireguard by following the kernel instructions from https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635
At this point I am able build the Image.gz file. I took the boot.img from the recovery images that NVidia provides and used AndroidImageKitchen (https://forum.xda-developers.com/showthread.php?t=2073775) to unpack the boot.img, swap out boot.img-Image.gz with the one Image.gz that I compiled and re-packed the boot.img I flashed this boot.img to my device using fastboot, and the device never boots.
I have some logs from the bootloop - here is the snipit that seems most relevant but I don't really know what I am looking for or how to determine what needs to change
Code:
09-12 22:00:42.120 3384 3384 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 1
09-12 22:00:42.120 3384 3384 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 1
09-12 22:00:42.120 3383 3383 E Netd : cannot find interface dummy0
09-12 22:00:42.120 3383 3383 I Netd : Initializing RouteController: 1.3ms
09-12 22:00:42.120 3384 3384 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 3384 (surfaceflinger), pid 3384 (surfaceflinger)
09-12 22:00:42.120 3383 3383 D XfrmController: Sending Netlink XFRM Message: XFRM_MSG_FLUSHSA
09-12 22:00:42.120 3383 3383 D XfrmController: Sending Netlink XFRM Message: XFRM_MSG_FLUSHPOLICY
09-12 22:00:42.120 3383 3383 I Netd : Initializing XfrmController: 0.2ms
09-12 22:00:42.121 3383 3383 I Netd : Registering NetdNativeService: 0.5ms
09-12 22:00:42.122 3383 3383 I Netd : Starting CommandListener: 0.1ms
09-12 22:00:42.123 3383 3383 I Netd : Registering NetdHwService: 1.0ms
09-12 22:00:42.123 3383 3383 I Netd : Netd started in 219ms
09-12 22:00:42.132 3378 3378 D Zygote : begin preload
09-12 22:00:42.132 3378 3378 I Zygote : Installing ICU cache reference pinning...
09-12 22:00:42.132 3378 3378 I Zygote : Preloading ICU data...
09-12 22:00:42.135 3379 3379 I Zygote : Accepting command socket connections
09-12 22:00:42.138 3378 3378 I Zygote : Preloading classes...
09-12 22:00:42.140 3436 3436 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
09-12 22:00:42.140 3184 3184 I /system/bin/tombstoned: received crash request for pid 3384
09-12 22:00:42.141 3436 3436 I crash_dump64: performing dump of process 3384 (target tid = 3384)
09-12 22:00:42.143 3436 3436 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-12 22:00:42.143 3436 3436 F DEBUG : Build fingerprint: 'NVIDIA/darcy/darcy:9/PPR1.180610.011/4079208_2235.1395:user/release-keys'
09-12 22:00:42.143 3436 3436 F DEBUG : Revision: '0'
09-12 22:00:42.143 3436 3436 F DEBUG : ABI: 'arm64'
09-12 22:00:42.143 3436 3436 F DEBUG : pid: 3384, tid: 3384, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
09-12 22:00:42.143 3436 3436 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
09-12 22:00:42.143 3436 3436 F DEBUG : Cause: null pointer dereference
09-12 22:00:42.143 3436 3436 F DEBUG : x0 0000000000000000 x1 0000000000000000 x2 0000000000000000 x3 00000025b1c537d0
09-12 22:00:42.143 3436 3436 F DEBUG : x4 0000000000000000 x5 0000007fe38db898 x6 0000000000000000 x7 0000000000000030
09-12 22:00:42.143 3436 3436 F DEBUG : x8 0101010101010101 x9 b72fc0062f2280b8 x10 000000005f647079 x11 0000000000000000
09-12 22:00:42.143 3436 3436 F DEBUG : x12 0000000000000001 x13 0000000000000000 x14 0000000000000001 x15 00000025b1c81a88
09-12 22:00:42.143 3436 3436 F DEBUG : x16 000000252f3b9e58 x17 00000025307de610 x18 0000000000000001 x19 00000025b1c537d0
09-12 22:00:42.143 3436 3436 F DEBUG : x20 0000000000000000 x21 0000000000000000 x22 000000252ed0c5e0 x23 0000000000000000
09-12 22:00:42.143 3436 3436 F DEBUG : x24 0000000000000001 x25 0000007fe38dbb00 x26 00000000000f4240 x27 0000007fe38dbb00
09-12 22:00:42.143 3436 3436 F DEBUG : x28 0000007fe38dba90 x29 0000007fe38db900
09-12 22:00:42.143 3436 3436 F DEBUG : sp 0000007fe38db8e0 lr 000000252f396f78 pc 00000025307de620
09-12 22:00:42.146 3378 3378 I PackageBackwardCompatibility: Loaded android.content.pm.OrgApacheHttpLegacyUpdater
Any pointers to what I am doing wrong, or how to further debug would be appreciated.
Also if there is already a kernel built with Wireguard support, a reference to that would be :good:
Hi, I've compiled kernel for Shield 2017 following your steps and I'm probably facing same issue. My boot hangs on Nvidia logo. I have a question - how you've obtained boot logs? ADB don't work from fastboot menu for me.
Hi, did you finally succeed in compiling a kernel for shield 2017 ?

Categories

Resources