Android 8.0 Oreo Discussion - Zenfone 5 General

You guys can discuss things at here or release test builds at here
 @tank0412 @flex1911

Well, i built AOSP O.
But, well, there are major problems with hwcomposer again.
OMG.
https://drive.google.com/open?id=0B-Fin8UxrD6PaHBXTEtDdEFZT2s
LOL.
Code:
08-22 10:50:52.816 158 158 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.816 158 158 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.817 158 158 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.822 158 158 E hwservicemanager: Failed to aquire binder FD. Aborting...
08-22 10:50:52.881 165 165 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.882 165 165 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
08-22 10:50:52.882 165 165 F /system/bin/hw/androi[email protected]: service.cpp:24] Unable to register allocator service: -38
--------- beginning of crash
08-22 10:50:52.882 165 165 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 165 ([email protected])
-22 10:50:52.966 175 175 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.966 175 175 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.966 175 175 F DEBUG : Revision: '0'
08-22 10:50:52.966 175 175 F DEBUG : ABI: 'x86'
08-22 10:50:52.966 175 175 F DEBUG : pid: 165, tid: 165, name: [email protected] >>> /system/bin/hw/[email protected] <<<
08-22 10:50:52.966 175 175 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.968 174 174 I crash_dump32: obtaining output fd from tombstoned
08-22 10:50:52.968 174 174 E libc : failed to connect to tombstoned: No such file or directory
08-22 10:50:52.969 174 174 I crash_dump32: performing dump of process 166 (target tid = 166)
08-22 10:50:52.969 174 174 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.969 174 174 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.969 174 174 F DEBUG : Revision: '0'
08-22 10:50:52.969 174 174 F DEBUG : ABI: 'x86'
08-22 10:50:52.969 174 174 F DEBUG : pid: 166, tid: 166, name: [email protected] >>> /vendor/bin/hw/[email protected] <<<
08-22 10:50:52.969 174 174 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.970 175 175 F DEBUG : Abort message: 'service.cpp:24] Unable to register allocator service: -38'
08-22 10:51:11.421 210 210 E IMGSRV : :0: PVRSRVConnect: Unable to enumerate devices.
08-22 10:51:11.421 210 210 E IMGSRV : :0: Couldn't connect to services
08-22 10:51:11.442 210 210 E IMGSRV : :0: SRV_ServicesInit: need wait service init
08-22 10:51:11.442 210 210 E IMGSRV :
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086849 (strerror returns no value.).
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVEnumerateDevices: BridgeCall failed

tank0412 said:
Well, i built AOSP O.
But, well, there are major problems with hwcomposer again.
OMG.
https://drive.google.com/open?id=0B-Fin8UxrD6PaHBXTEtDdEFZT2s
LOL.
Code:
08-22 10:50:52.816 158 158 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.816 158 158 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.817 158 158 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.822 158 158 E hwservicemanager: Failed to aquire binder FD. Aborting...
08-22 10:50:52.881 165 165 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.882 165 165 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
08-22 10:50:52.882 165 165 F /system/bin/hw/[email protected]: service.cpp:24] Unable to register allocator service: -38
--------- beginning of crash
08-22 10:50:52.882 165 165 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 165 ([email protected])
-22 10:50:52.966 175 175 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.966 175 175 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.966 175 175 F DEBUG : Revision: '0'
08-22 10:50:52.966 175 175 F DEBUG : ABI: 'x86'
08-22 10:50:52.966 175 175 F DEBUG : pid: 165, tid: 165, name: [email protected] >>> /system/bin/hw/[email protected] <<<
08-22 10:50:52.966 175 175 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.968 174 174 I crash_dump32: obtaining output fd from tombstoned
08-22 10:50:52.968 174 174 E libc : failed to connect to tombstoned: No such file or directory
08-22 10:50:52.969 174 174 I crash_dump32: performing dump of process 166 (target tid = 166)
08-22 10:50:52.969 174 174 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.969 174 174 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.969 174 174 F DEBUG : Revision: '0'
08-22 10:50:52.969 174 174 F DEBUG : ABI: 'x86'
08-22 10:50:52.969 174 174 F DEBUG : pid: 166, tid: 166, name: [email protected] >>> /vendor/bin/hw/[email protected] <<<
08-22 10:50:52.969 174 174 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.970 175 175 F DEBUG : Abort message: 'service.cpp:24] Unable to register allocator service: -38'
08-22 10:51:11.421 210 210 E IMGSRV : :0: PVRSRVConnect: Unable to enumerate devices.
08-22 10:51:11.421 210 210 E IMGSRV : :0: Couldn't connect to services
08-22 10:51:11.442 210 210 E IMGSRV : :0: SRV_ServicesInit: need wait service init
08-22 10:51:11.442 210 210 E IMGSRV :
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086849 (strerror returns no value.).
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVEnumerateDevices: BridgeCall failed
Click to expand...
Click to collapse
You could try using fugu device tree as reference: https://android.googlesource.com/device/asus/fugu/+/android-8.0.0_r4
But I really recommend you to wait before trying. There's no other ROM than stock-based of Oreo so you can't really have a base for an unnoficial device.

Soo ROM is booting??

Guys, can somebody test new O build?
system.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PT0ZFYk14TFc3N28
boot.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PV19lZ1FfdG5zUHM
I updated binder in kernel sources.
https://github.com/zf5/android_kernel_asus_T00F/commits/aosp8.0
I need logcat and dmesg.
Thanks.

masterofpc said:
Soo ROM is booting??
Click to expand...
Click to collapse
Based on what I understood, they were able to get AOSP Oreo going (with some sort of problem). And even if they manage to fix that "issue", they still need to port the AOSP Oreo for ZenFone 5 based on ASUS sources.
To make it short, yea. The devs are probably getting something going. But it's gonna take a while before even just an "Alpha" build will be available for our use.

cnswico said:
Based on what I understood, they were able to get AOSP Oreo going (with some sort of problem). And even if they manage to fix that "issue", they still need to port the AOSP Oreo for ZenFone 5 based on ASUS sources.
To make it short, yea. The devs are probably getting something going. But it's gonna take a while before even just an "Alpha" build will be available for our use.
Click to expand...
Click to collapse
Thanks a lot

tank0412 said:
Guys, can somebody test new O build?
system.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PT0ZFYk14TFc3N28
boot.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PV19lZ1FfdG5zUHM
I updated binder in kernel sources.
https://github.com/zf5/android_kernel_asus_T00F/commits/aosp8.0
I need logcat and dmesg.
Thanks.
Click to expand...
Click to collapse
I just downloaded and gave a try.
But it stock at bootloader(ASUS logo), then keep rebooting. After several times reboot, it autometically boot into fastboot mode.
Code:
D:\Downloads\Zenfone 5>fastboot devices
0123456789ABCDEF fastboot
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611688448 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.458s]
writing 'boot'...
OKAY [ 1.146s]
finished. total time: 2.608s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611688448 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 71.458s]
writing 'system'...
OKAY [ 34.281s]
sending sparse 'system' (330425 KB)...
OKAY [ 38.129s]
writing 'system'...
OKAY [ 20.437s]
finished. total time: 164.315s
D:\Downloads\Zenfone 5>adb logcat
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- waiting for device -
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611218773 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.704s]
writing 'boot'...
OKAY [ 1.128s]
finished. total time: 2.836s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611218773 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 82.793s]
writing 'system'...
OKAY [ 34.381s]
sending sparse 'system' (330425 KB)...
OKAY [ 41.286s]
writing 'system'...
OKAY [ 19.840s]
finished. total time: 178.309s
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>
Here's my Zenfone 5 environment:
TWRP 3.1.1.-0 by narueon
Droidboot version: 2.1 BUILD Dec 8 2014 16:02:41
I first go to recovery and wipe /data, /cache, /system, then reboot to fastboot to flash boot and system.
Thx

f870103 said:
I just downloaded and gave a try.
But it stock at bootloader(ASUS logo), then keep rebooting. After several times reboot, it autometically boot into fastboot mode.
Code:
D:\Downloads\Zenfone 5>fastboot devices
0123456789ABCDEF fastboot
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611688448 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.458s]
writing 'boot'...
OKAY [ 1.146s]
finished. total time: 2.608s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611688448 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 71.458s]
writing 'system'...
OKAY [ 34.281s]
sending sparse 'system' (330425 KB)...
OKAY [ 38.129s]
writing 'system'...
OKAY [ 20.437s]
finished. total time: 164.315s
D:\Downloads\Zenfone 5>adb logcat
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- waiting for device -
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611218773 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.704s]
writing 'boot'...
OKAY [ 1.128s]
finished. total time: 2.836s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611218773 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 82.793s]
writing 'system'...
OKAY [ 34.381s]
sending sparse 'system' (330425 KB)...
OKAY [ 41.286s]
writing 'system'...
OKAY [ 19.840s]
finished. total time: 178.309s
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>
Here's my Zenfone 5 environment:
TWRP 3.1.1.-0 by narueon
Droidboot version: 2.1 BUILD Dec 8 2014 16:02:41
I first go to recovery and wipe /data, /cache, /system, then reboot to fastboot to flash boot and system.
Thx
Click to expand...
Click to collapse
Thank you.
Thw problem is we must patch binder in kernel sources to at least pass Asus OEM.
I patched it but it looks like patches broke kernel at all.
It said. I am puzzled what to do with it.

I had the same result as you and f870103. bootlooped

tank0412 said:
Guys, can somebody test new O build?
system.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PT0ZFYk14TFc3N28
boot.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PV19lZ1FfdG5zUHM
I updated binder in kernel sources.
https://github.com/zf5/android_kernel_asus_T00F/commits/aosp8.0
I need logcat and dmesg.
Thanks.
Click to expand...
Click to collapse
i tried to flash this new android o but it caused me a bootloop. it doesn't cross the asus logo. whenever i boot my device, it just stuck at the asus logo.

@tank0412 yeah its bootloops.I wait 1 hour.But unfortunately.

Any news ??????

@tank0412
I was looking at lineage os Gerrit.. there are some changes made for Asus Z00D for Lineage Os 15.
Here is the link...
https://goo.gl/w89D8T
I am not sure if it can be of any help but consider looking at it...

narueon said:
@tank0412
I was looking at lineage os Gerrit.. there are some changes made for Asus Z00D for Lineage Os 15.
Here is the link...
https://goo.gl/w89D8T
I am not sure if it can be of any help but consider looking at it...
Click to expand...
Click to collapse
Well, they actually will...

narueon said:
@tank0412
I was looking at lineage os Gerrit.. there are some changes made for Asus Z00D for Lineage Os 15.
Here is the link...
https://goo.gl/w89D8T
I am not sure if it can be of any help but consider looking at it...
Click to expand...
Click to collapse
Yeah, thanks.
I merged all this commits.
https://github.com/zf5/android_device_asus_T00F/commits/aosp8.0
But maybe i did something wrong because it still did not pass Asus OEM logo. What is a shame.
UPD: Asus OEM is passed. Stuck on bootanimation.
Audio server is dead. Dammed.
Build:
https://drive.google.com/open?id=0B-Fin8UxrD6PaHBXTEtDdEFZT2s

Im always trust you tank :victory:

Hi, all.
OREO IS BOOTED ON T00F
EVERYTHING ARE DEAD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

tank0412 said:
Hi, all.
OREO IS BOOTED ON T00F
EVERYTHING ARE DEAD
Click to expand...
Click to collapse
Great work!! But everything's dead? Is it literal or overstatement?

ZeeJcG said:
Great work!! But everything's dead? Is it literal or overstatement?
Click to expand...
Click to collapse
Only wifi is works.

Related

[ROM][4.4.2][WIP] OmniROM [UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since KitKat is becoming stable, I have built another ROM and decided to share it with you.
OmniROM is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance, reliability and features over stock Android for your device. It is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restores the Google parts.
All the source code for OmniROM is available in the OmniROM Github repo.
More information about Omni
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NOT WORKING/BROKEN
Same as in CM11
Camera
CHANGELOG
Code:
[B][U]29/05/2014:[/U][/B]
[LIST]
[*]Fixed USB Mass storage - [URL="gerrit.omnirom.org/#/c/5041/"]gerrit.omnirom.org/#/c/5041/[/URL]
[*]Omni/omniarmv6 upstream
[/LIST]
[B][U]06/05/2014:[/U][/B]
[LIST]
[*]Fixed OMX
[*]Fixed camera video recording
[*]Omni/omniarmv6 upstream
[/LIST]
[B][U]01/05/2014:[/U][/B]
[LIST]
[*]Initial release
[/LIST]
DOWNLOAD
OmniROM - team-simplicit.com
BTW: This ROM is not rooted, you have to flash SuperSU!
SCREENSHOTs
SOURCEs
Manifest
Device Config
Kernel Source
CREDITS
My awesome team (izi501, feroxx, Kevinjoa, thehacka1) for being so awesome!
WinSuk for the linker/reboot fix
benjamingwynn
niks255
JDevs and the OWL Team
The androidarmv6 team
The Omni team
Great job Oli. [emoji111]
Gesendet von meinem LG-gee mit Tapatalk
Info about ME
You're impossible @Olivier :laugh:
Anyway... New dev is coming
CyanFrank said:
You're impossible @Olivier :laugh:
Anyway... New dev is coming
Click to expand...
Click to collapse
Oh my goodness I really can't get it Just gonna press the download button...
I can haz logcat?
Logcat time!
The rom is quite smooth IMHO even with INT2EXT enabled, there are a few quirks here and there
This is something that pops up quite some times in the logcat, something to do with the GPU
Code:
[ 05-03 16:55:09.561 5054: 5054 E/memalloc ]
/dev/pmem: Failed to map buffer size:4202496 offset:1843200 fd:83 Error: Invalid
argument
[ 05-03 16:55:09.561 5054: 5054 E/gralloc ]
Could not mmap handle 0x2a1eac10, fd=83 (Invalid argument)
[ 05-03 16:55:09.561 5054: 5054 E/gralloc ]
gralloc_register_buffer: gralloc_map failed
[ 05-03 16:55:09.561 5054: 5054 W/GraphicBufferMapper ]
registerBuffer(0x2a1eac10) failed -22 (Invalid argument)
[ 05-03 16:55:09.561 5054: 5054 E/GraphicBuffer ]
unflatten: registerBuffer failed: Invalid argument (-22)
[ 05-03 16:55:09.561 5054: 5054 E/Adreno200-EGLSUB ]
CreateImage() Invalid Native Buffer or handle
[ 05-03 16:55:09.561 5054: 5054 E/Adreno200-EGL ]
<qeglDrvAPI_eglCreateImageKHR:4160>: EGL_BAD_PARAMETER
Also, "Advanced settings" in "Performance" FCs
Code:
[ 05-03 16:58:34.951 4889: 4889 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.settings, PID: 4889
java.lang.NullPointerException
at java.io.File.fixSlashes(File.java:185)
at java.io.File.<init>(File.java:134)
at java.io.FileInputStream.<init>(FileInputStream.java:105)
at java.io.FileReader.<init>(FileReader.java:66)
at com.brewcrewfoo.performance.fragments.VoltageControlSettings.getVolts
(VoltageControlSettings.java:229)
at com.brewcrewfoo.performance.fragments.VoltageControlSettings.onCreate
(VoltageControlSettings.java:77)
at android.app.Fragment.performCreate(Fragment.java:1678)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:859)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062
)
at android.app.BackStackRecord.run(BackStackRecord.java:684)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.ja
va:1447)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:443)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5017)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit
.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
at dalvik.system.NativeStart.main(Native Method)
The lights of capacitive keys and the notification LED do not work. Suggestions to get logcats for these?
Finally, The phone doesn't show any charging status or animation when the phone is plugged in, the phone is charging though.
Very Very good new htc wildfire s good olivier
csoulr666 said:
Logcat time!
Click to expand...
Click to collapse
Thanks for the logs! :good:
csoulr666 said:
The rom is quite smooth IMHO even with INT2EXT enabled, there are a few quirks here and there
This is something that pops up quite some times in the logcat, something to do with the GPU
Click to expand...
Click to collapse
Should be fixed in the next release...
csoulr666 said:
The lights of capacitive keys and the notification LED do not work. Suggestions to get logcats for these?
Finally, The phone doesn't show any charging status or animation when the phone is plugged in, the phone is charging though.
Click to expand...
Click to collapse
Look at the first screenshot, the device does show the charging symbol in the statusbar.
However, the lights and the notification LED really don't work. I will look into it ASAP.
EDIT: New update is up, check the OP!
Olivier said:
Look at the first screenshot, the device does show the charging symbol in the statusbar.
Click to expand...
Click to collapse
It does show a charging animation(I was using percent only, no animation there), but in the quick settings toggle or the diag menu(*#*#4636#*#*) do not show the charging status.
However, the lights and the notification LED really don't work. I will look into it ASAP.
Click to expand...
Click to collapse
Actually I found saw that LED works for certain notifications(only Gmail so far) but never for charging.......the latter might be because the system doesn't show the charging status
Also I have a question, will flashing the new update on the rom without wiping remove root as well??
csoulr666 said:
Will flashing the new update on the rom without wiping remove root as well??
Click to expand...
Click to collapse
I think so, because system (where SuperSU is located) gets wiped.
Olivier said:
I think so, because system (where SuperSU is located) gets wiped.
Click to expand...
Click to collapse
I just remembered, SuperSU asked me to install an addon script just to survive flashing...... Silly me:silly:
Question, you have not added UMS as of now am I right?? Because nothing pops up when I connect my phone to my PC
Wow! Looks like I'm the only one using OMNI, everyone else is glued to CM11 :laugh:
I got some more logs, hopefully helpful ones, regarding VPN ,bluetooth and wifi tethering
Thanks for the logs! Yep I just noticed that bug too - I will maybe look into it on the weekend.
Build from source ?
Olivier said:
Thanks for the logs! Yep I just noticed that bug too - I will maybe look into it on the weekend.
Click to expand...
Click to collapse
I have built CM11 from source, and would love to build this one too, to compare, I was expecting an omni branch in your github but didn't see it ?
Omni is at "android-4.4".
Gesendet von meinem Lenovo A3000-H mit Tapatalk
Awesome ROM but the quick pulldown disappear after reboot.
The patch not working camera
You always do the best olivier
Sent from my XT1032 using XDA Free mobile app
I'm not using this ROM
But,there is a workaround for USB Mass Storage bug,you see you can maybe use mobogenie pc app to make it work,because it mounts sd to pc without having to unmount it from device.
Best Wishes and tell me if it works
Camera?
I tried the camera patch with a complete wipe(including system) following the 6th may build........The "Can't connect to camera" prompt doesn't come but I'm greeted with a completely black screen, I tried a few other photo taking apps(Splitpic, Instagram and even a barcode scanner) but I still go the same result.
So here's a logcat of me opening the stock camera app
Code:
[ 05-07 21:02:49.867 615: 667 I/ActivityManager ]
Start proc com.android.camera2 for activity com.android.camera2/com.android.came
ra.CameraLauncher: pid=4766 uid=10050 gids={50050, 3003, 1028, 1015, 1023}
[ 05-07 21:02:50.817 4766: 4766 D/CameraStorage ]
External storage state=mounted
[ 05-07 21:02:50.827 4766: 4766 V/NFC ]
this device does not have NFC support
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
On resume.
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
Executing onResumeTasks.
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
Open camera device.
[ 05-07 21:02:50.858 129: 129 D/AK8975 ]
Compass Start
[ 05-07 21:02:50.878 124: 1053 D/CameraHAL ]
CameraHAL_GetNum_Cameras: loading libcamera at 0x4077eed8
[ 05-07 21:02:50.888 4766: 4766 V/CameraHolder ]
open camera 0
[ 05-07 21:02:51.298 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.558 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.808 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.919 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.119 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.299 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.519 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.719 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.920 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.110 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.190 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.410 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.590 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.790 124: 4221 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:53.790 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.021 124: 668 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:54.031 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.231 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.411 124: 1053 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:54.421 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:59.786 615: 631 E/WindowManager ]
Starting window AppWindowToken{420b01a8 token=Token{420af890 ActivityRecord{420a
f6b8 u0 com.android.camera2/com.android.camera.CameraLauncher t453}}} timed out
[ 05-07 21:02:59.796 615: 632 W/ActivityManager ]
Launch timeout has expired, giving up wake lock!
[ 05-07 21:03:10.857 615: 632 W/ActivityManager ]
Timeout executing service: ServiceRecord{42208360 u0 com.android.camera2/com.and
roid.camera.MediaSaveService}
[ 05-07 21:03:10.917 615: 632 I/Process ]
Sending signal. PID: 4766 SIG: 3
[ 05-07 21:03:10.917 4766: 4771 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:10.967 4766: 4771 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:10.967 615: 632 I/Process ]
Sending signal. PID: 615 SIG: 3
[ 05-07 21:03:10.967 615: 620 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.538 615: 627 E/Sensors ]
poll() failed (Interrupted system call)
[ 05-07 21:03:11.578 615: 632 I/Process ]
Sending signal. PID: 991 SIG: 3
[ 05-07 21:03:11.578 991: 996 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.608 615: 620 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.608 615: 632 I/Process ]
Sending signal. PID: 803 SIG: 3
[ 05-07 21:03:11.618 803: 815 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.728 803: 815 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.738 615: 632 I/Process ]
Sending signal. PID: 795 SIG: 3
[ 05-07 21:03:11.738 795: 809 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.758 991: 996 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.768 615: 632 I/Process ]
Sending signal. PID: 783 SIG: 3
[ 05-07 21:03:11.768 783: 794 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.858 783: 794 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.958 795: 809 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:13.920 615: 632 E/ActivityManager ]
ANR in com.android.camera2
PID: 4766
Reason: Executing service com.android.camera2/com.android.camera.MediaSaveServic
e
Load: 10.33 / 14.25 / 12.94
CPU usage from 6040ms to 0ms ago:
1.3% 129/akmd: 0.1% user + 1.1% kernel
1.3% 615/system_server: 0.8% user + 0.4% kernel
0.3% 5/events/0: 0% user + 0.3% kernel
0.1% 109/yaffs-bg-1: 0% user + 0.1% kernel
0.1% 754/wpa_supplicant: 0.1% user + 0% kernel
1.8% TOTAL: 0.6% user + 1.1% kernel
CPU usage from 2456ms to 2995ms later:
12% 615/system_server: 1.7% user + 10% kernel
10% 632/ActivityManager: 1.7% user + 8.9% kernel
1.7% 615/system_server: 1.7% user + 0% kernel
9.2% TOTAL: 1.8% user + 7.4% kernel
[ 05-07 21:03:22.719 615: 632 W/ActivityManager ]
Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
[ 05-07 21:03:22.729 615: 632 I/ActivityManager ]
Killing 4766:com.android.camera2/u0a50 (adj 0): user request after error
[ 05-07 21:03:23.019 129: 129 D/AK8975 ]
Compass CLOSE
[ 05-07 21:03:23.439 615: 625 W/InputMethodManagerService ]
Window already focused, ignoring focus gain of: com.android.internal.view.IInput
[email protected] attribute=null, token = [email protected]
41ed3308

Crash Debug on LineageOS 14.1

I just flashed my mobile with LineageOS 14.1
To my surprise I see the crashes that they dont show full stack trace.
Only this:
01-03 22:44:01.189 12773 12807 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x42424242 in tid 12807 (hci_thread)
Do I have to enable it somehow?
I would expect to see something like this (this I remember from Cyanogenmod and Stock Android)
02-05 16:45:13.279 307 1231 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1 in tid 1231 (netmgrd)
02-05 16:45:13.351 6570 6570 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-05 16:45:13.352 6570 6570 F DEBUG : CM Version: '14.1-20170131-NIGHTLY-osprey'
02-05 16:45:13.352 6570 6570 F DEBUG : Build fingerprint: 'motorola/osprey_retus_2gb/osprey_u2:6.0.1/MPI24.107-55/33:user/release-keys'
02-05 16:45:13.352 6570 6570 F DEBUG : Revision: '0'
02-05 16:45:13.352 6570 6570 F DEBUG : ABI: 'arm'
02-05 16:45:13.352 6570 6570 F DEBUG : pid: 307, tid: 1231, name: netmgrd >>> /system/bin/netmgrd <<<
02-05 16:45:13.352 6570 6570 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1
02-05 16:45:13.352 6570 6570 F DEBUG : r0 b6b01f10 r1 00000001 r2 b6b06560 r3 00000040
02-05 16:45:13.352 6570 6570 F DEBUG : r4 b647f3fc r5 b6b06eac r6 b6b01f10 r7 b6b02d07
02-05 16:45:13.352 6570 6570 F DEBUG : r8 b5f07520 r9 b5f07500 sl 00000001 fp b6f7ea49
02-05 16:45:13.352 6570 6570 F DEBUG : ip 00000000 sp b647f000 lr b6af9ba5 pc b6af9bce cpsr 20070030
02-05 16:45:13.363 6570 6570 F DEBUG :
02-05 16:45:13.363 6570 6570 F DEBUG : backtrace:
02-05 16:45:13.363 6570 6570 F DEBUG : #00 pc 00007bce /system/vendor/lib/libnetmgr.so (netmgr_nl_decode_nlmsg+269)
02-05 16:45:13.363 6570 6570 F DEBUG : #01 pc 00020f7d /system/bin/netmgrd
02-05 16:45:13.363 6570 6570 F DEBUG : #02 pc 00033893 /system/bin/netmgrd
02-05 16:45:13.364 6570 6570 F DEBUG : #03 pc 00041b09 /system/bin/netmgrd
02-05 16:45:13.364 6570 6570 F DEBUG : #04 pc 0000bef9 /system/vendor/lib/libdsutils.so (stm2_process_input+632)
02-05 16:45:13.364 6570 6570 F DEBUG : #05 pc 0000c7dd /system/vendor/lib/libdsutils.so (stm2_instance_process_input+204)
02-05 16:45:13.364 6570 6570 F DEBUG : #06 pc 0001213d /system/bin/netmgrd
02-05 16:45:13.364 6570 6570 F DEBUG : #07 pc 00003f9f /system/vendor/lib/libdsutils.so
02-05 16:45:13.364 6570 6570 F DEBUG : #08 pc 000477d3 /system/lib/libc.so (_ZL15__pthread_startPv+22)
02-05 16:45:13.364 6570 6570 F DEBUG : #09 pc 00019b7d /system/lib/libc.so (__start_thread+6)
Thanks,
marcinguy said:
I just flashed my mobile with LineageOS 14.1...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3466246
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks!
Actually it is a general Question in regards to LineageOS 14.1.
The device I use is S3 Neo+ GT-9301I
I pasted sample output as I it remember from Motorola device.
So on my device, as stated I just get:
Code:
12-31 13:11:00.180 8059 8096 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8096 (bt_workqueue)
12-31 13:11:00.181 209 209 W : debuggerd: handling request: pid=8059 uid=1002 gid=1002 tid=8096
12-31 13:11:00.220 8059 8096 F libc : failed to resend signal during crash: Operation not permitted
12-31 13:11:00.229 8335 8335 E DEBUG : unexpected waitpid response: n=8096, status=00000000
12-31 13:11:00.229 8335 8335 E : debuggerd: timed out waiting for signal
12-31 13:11:00.231 8335 8335 E : debuggerd: ptrace detach from 8096 failed: No such process
12-31 13:11:00.233 8335 8335 E : debuggerd: failed to kill process 8059: No such process
12-31 13:11:00.236 778 810 I BootReceiver: Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
Any ideas?
Where there is "Operation not permitted"?
Ibuprophen said:
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3466246
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Narrowed it down to this:
int rc = syscall(SYS_rt_tgsigqueueinfo, getpid(), gettid(), signal_number, info);
if (rc != 0) {
__libc_format_log(ANDROID_LOG_FATAL, "libc", "failed to resend signal during crash: %s",
strerror(errno));
_exit(0);
}
12-31 14:35:20.070 14851 14881 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 14881 (bt_workqueue)
12-31 14:35:20.070 16288 16288 W : debuggerd: handling request: pid=14851 uid=1002 gid=1002 tid=14881
12-31 14:35:20.100 14851 14881 F libc : failed to resend signal during crash: Operation not permitted
Wondering why it gets Operation not permitted?
marcinguy said:
Thanks!
Actually it is a general Question in regards to LineageOS 14.1.
The device I use is S3 Neo+ GT-9301I
I pasted sample output as I it remember from Motorola device.
So on my device, as stated I just get:
Code:
12-31 13:11:00.180 8059 8096 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8096 (bt_workqueue)
12-31 13:11:00.181 209 209 W : debuggerd: handling request: pid=8059 uid=1002 gid=1002 tid=8096
12-31 13:11:00.220 8059 8096 F libc : failed to resend signal during crash: Operation not permitted
12-31 13:11:00.229 8335 8335 E DEBUG : unexpected waitpid response: n=8096, status=00000000
12-31 13:11:00.229 8335 8335 E : debuggerd: timed out waiting for signal
12-31 13:11:00.231 8335 8335 E : debuggerd: ptrace detach from 8096 failed: No such process
12-31 13:11:00.233 8335 8335 E : debuggerd: failed to kill process 8059: No such process
12-31 13:11:00.236 778 810 I BootReceiver: Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
Any ideas?
Where there is "Operation not permitted"?
Click to expand...
Click to collapse
Figured it out.
Had to modify debbugerd (bionic) and adjust selinux.
Now debuggerd can attach to the process and show the debug info and backtrace.
marcinguy said:
Narrowed it down to this:
int rc = syscall(SYS_rt_tgsigqueueinfo, getpid(), gettid(), signal_number, info);
if (rc != 0) {
__libc_format_log(ANDROID_LOG_FATAL, "libc", "failed to resend signal during crash: %s",
strerror(errno));
_exit(0);
}
12-31 14:35:20.070 14851 14881 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 14881 (bt_workqueue)
12-31 14:35:20.070 16288 16288 W : debuggerd: handling request: pid=14851 uid=1002 gid=1002 tid=14881
12-31 14:35:20.100 14851 14881 F libc : failed to resend signal during crash: Operation not permitted
Wondering why it gets Operation not permitted?
Click to expand...
Click to collapse

System Hangs on Whyred

Hello guys, my whyred system sometimes is hanging while on sleep, do someone knows what can be?
On bugreport i found this:
Code:
--------- beginning of crash
06-23 16:39:54.585 root 643 21653 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7b9eb1aa7a in tid 21653 (netd), pid 643 (Binder:643_2)
06-23 16:39:54.669 root 21658 21658 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-23 16:39:54.669 root 21658 21658 F DEBUG : Build fingerprint: 'Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys'
06-23 16:39:54.669 root 21658 21658 F DEBUG : Revision: '0'
06-23 16:39:54.669 root 21658 21658 F DEBUG : ABI: 'arm64'
06-23 16:39:54.669 root 21658 21658 F DEBUG : pid: 643, tid: 21653, name: netd >>> /system/bin/netd <<<
06-23 16:39:54.670 root 21658 21658 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7b9eb1aa7a
06-23 16:39:54.670 root 21658 21658 F DEBUG : x0 0000007b9fa1ab44 x1 0000007b9eb1aa7a x2 000000000000007e x3 0000007b9fa1ab40
06-23 16:39:54.670 root 21658 21658 F DEBUG : x4 0000007b9eb1aaf8 x5 0000007b9fa1abc2 x6 0000000000000000 x7 0000000000000000
06-23 16:39:54.670 root 21658 21658 F DEBUG : x8 0000007b9eb1aaf8 x9 0000000000000004 x10 0000007b9fa1ab40 x11 0000007b9fa1abbf
06-23 16:39:54.670 root 21658 21658 F DEBUG : x12 0000000000000001 x13 0000000000000000 x14 0000007c21cc37c0 x15 aaaaaaaaaaaaaaab
06-23 16:39:54.670 root 21658 21658 F DEBUG : x16 00000063e43cb348 x17 0000007c216faf70 x18 00000000000000fe x19 0000007ba005e780
06-23 16:39:54.670 root 21658 21658 F DEBUG : x20 0000007b9ea1f408 x21 0000007b9fa1ab40 x22 0000007b9ea1f588 x23 0000007b9eb1aa7a
06-23 16:39:54.670 root 21658 21658 F DEBUG : x24 0000007b9eb1aaf8 x25 0000007b9e922000 x26 0000007b9eb1d588 x27 0000000000000002
06-23 16:39:54.670 root 21658 21658 F DEBUG : x28 0000007ba00d28c0 x29 0000007b9ea1f3e0
06-23 16:39:54.670 root 21658 21658 F DEBUG : sp 0000007b9ea1f390 lr 00000063e439080c pc 0000007c216fb058
06-23 16:39:54.687 root 21658 21658 F DEBUG :
06-23 16:39:54.687 root 21658 21658 F DEBUG : backtrace:
06-23 16:39:54.687 root 21658 21658 F DEBUG : #00 pc 000000000001e058 /system/lib64/libc.so (memcpy+232)
06-23 16:39:54.687 root 21658 21658 F DEBUG : #01 pc 0000000000074808 /system/bin/netd (android::net::DnsTlsSocket::sendQuery(android::net::DnsTlsSocket::Query const&)+352)
06-23 16:39:54.687 root 21658 21658 F DEBUG : #02 pc 0000000000074304 /system/bin/netd (android::net::DnsTlsSocket::loop()+300)
06-23 16:39:54.687 root 21658 21658 F DEBUG : #03 pc 0000000000074c04 /system/bin/netd
06-23 16:39:54.687 root 21658 21658 F DEBUG : #04 pc 0000000000090328 /system/lib64/libc.so (__pthread_start(void*)+36)
06-23 16:39:54.687 root 21658 21658 F DEBUG : #05 pc 0000000000023a28 /system/lib64/libc.so (__start_thread+68)
and on the bottom of file have this:
Code:
========================================================
== Dropbox crashes
========================================================
------ DROPBOX SYSTEM SERVER CRASHES (/system/bin/dumpsys -T 30000 dropbox -p system_server_crash) ------
Drop box contents: 586 entries
Max entries: 1000
Searching for: system_server_crash
(No entries found.)
------ 0.113s was the duration of 'DROPBOX SYSTEM SERVER CRASHES' ------
------ DROPBOX SYSTEM APP CRASHES (/system/bin/dumpsys -T 30000 dropbox -p system_app_crash) ------
Drop box contents: 586 entries
Max entries: 1000
Searching for: system_app_crash
========================================
2019-06-21 16:26:00 system_app_crash (text, 967 bytes)
Process: pl.zdunex25.updater
PID: 2137
Flags: 0x3888be47
Package: pl.zdunex25.updater v83 (8.3)
Foreground: Yes
Build: xiaomi/whyred/whyred:9/PKQ1.180904.001/9.6.13:user/release-keys/1560434479
java.lang.NullPointerException: Attempt to read from null array
at pl.zdunex25.updater.MainActivity$3.onClick(MainActivity.java:340)
at android.view.View.performClick(Unknown Source:17)
at android.view.View.performClickInternal(Unknown Source:3)
at android.view.View.access$3100(Unknown Source:0)
at android.view.View$PerformClick.run(Unknown Source:2)
at android.os.Handler.handleCallback(Unknown Source:2)
at android.os.Handler.dispatchMessage(Unknown Source:4)
at android.os.Looper.loop(Unknown Source:208)
at android.app.ActivityThread.main(Unknown Source:107)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
at com.android.internal.os.ZygoteInit.main(Unknown Source:274)
------ 0.083s was the duration of 'DROPBOX SYSTEM APP CRASHES' ------
========================================================
== Final progress (pid 31206): 1422/1452 (estimated 1452)
I am using Xiaomi.eu ROM, on Pixel Experience it happens the same

Problem Flashing new Android 11 magisk_patched.img

Hello, I'm trying to update my pixel 2xl to the latest Android 11 using Magisk Cannary 20426 and everytime I've tried to either patch boot.img or install the magisk,zip using TWP I'm getting this similar error in my `adb logcat`. I'm able to still aceess the phone after a failure to flash the new boot.img but flashing the stock. This means that I donot have root on my phone anymore.
Things I've tried:
Reinstalling the magisk app using cannary
different usb port / cable
updated platformtools
any advice to assist in debugging this would be greatly appreciated
Code:
12-31 19:42:47.054 2244 2244 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-31 19:42:47.054 2244 2244 F DEBUG : Build fingerprint: 'google/taimen/taimen:11/RP1A.200720.009/6720564:user/release-keys'
12-31 19:42:47.054 2244 2244 F DEBUG : Revision: 'rev_10'
12-31 19:42:47.054 2244 2244 F DEBUG : ABI: 'arm'
12-31 19:42:47.055 2244 2244 F DEBUG : Timestamp: 1969-12-31 19:42:47-0500
12-31 19:42:47.055 2244 2244 F DEBUG : pid: 2209, tid: 2209, name: app_process32 >>> /system/bin/app_process32 <<<
12-31 19:42:47.055 2244 2244 F DEBUG : uid: 0
12-31 19:42:47.055 2244 2244 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3
12-31 19:42:47.055 2244 2244 F DEBUG : Cause: null pointer dereference
12-31 19:42:47.055 2244 2244 F DEBUG : r0 00000003 r1 00000003 r2 00000000 r3 00000005
12-31 19:42:47.055 2244 2244 F DEBUG : r4 ff955690 r5 f646837c r6 00000300 r7 f5f42f50
12-31 19:42:47.055 2244 2244 F DEBUG : r8 00000003 r9 00000000 r10 f6468680 r11 f6468310
12-31 19:42:47.055 2244 2244 F DEBUG : ip 80000000 sp ff955618 lr f63dc38b pc f644595a
12-31 19:42:47.056 2244 2244 F DEBUG : backtrace:
12-31 19:42:47.056 2244 2244 F DEBUG : #00 pc 0008395a /apex/com.android.runtime/bin/linker!ld-android.so (offset 0x1a000) (__dl_strlen_a15+22) (BuildId: 24c8b5ac82b22718002810e56f914352)
12-31 19:42:47.056 2244 2244 F DEBUG : #01 pc 0001a387 /apex/com.android.runtime/bin/linker (__dl__ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEC2IDnEEPKc+18) (BuildId: 24c8b5ac82b22718002810e56f914352)
12-31 19:42:47.060 1203 1203 I ServiceManager: Waiting for service 'package_native' on '/dev/binder'...
12-31 19:42:47.060 1267 1267 I ServiceManager: Waiting for service 'sensorservice' on '/dev/binder'...
12-31 19:42:47.060 2178 2240 D audio_hw_primary: out_set_parameters: enter: usecase(29: audio-playback-voip) kvpairs: routing=2
12-31 19:42:47.063 2185 2185 I AudioFlinger: openOutput() this 0x7c12bc8a30, module 10 Device type:0x10000,@:, SamplingRate 48000, Format 0x000001, Channels 0x3, flags 0x10000
12-31 19:42:47.063 2178 2240 E voice_extn: voice_extn_check_and_set_incall_music_usecase: Invalid session id 0
12-31 19:42:47.064 2185 2185 I AudioFlinger: HAL output buffer size 240 frames, normal sink buffer size 960 frames
12-31 19:42:47.065 2185 2185 E AudioFlinger: Failed to add event callback
12-31 19:42:47.065 2185 2251 I AudioFlinger: AudioFlinger's thread 0x7d94509040 tid=2251 ready to run
12-31 19:42:47.065 2185 2251 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.065 2185 2251 D AudioFlinger: ro.audio.silent is ignored since no output device is set
12-31 19:42:47.065 2185 2251 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.065 2185 2251 D AudioFlinger: ro.audio.silent is ignored since no output device is set
12-31 19:42:47.094 2178 2240 D audio_hw_primary: out_set_parameters: enter: usecase(31: incall-music-uplink) kvpairs: routing=65536
12-31 19:42:47.097 2185 2252 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2252 ready to run
12-31 19:42:47.097 2185 2252 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.098 2185 2252 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.099 2185 2254 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2254 ready to run
12-31 19:42:47.100 2185 2254 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.100 2185 2254 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.101 2185 2256 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2256 ready to run
12-31 19:42:47.101 2185 2256 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.101 2185 2256 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.101 2185 2185 E APM_AudioPolicyManager: onNewAudioModulesAvailableInt: Input device list is empty!
12-31 19:42:47.103 2244 2244 E crash_dump32: unable to connect to activity manager: Connection refused
12-31 19:42:47.103 2185 2259 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2259 ready to run
12-31 19:42:47.103 2185 2258 E FastThread: did not receive expected priority boost on time
12-31 19:42:47.103 928 928 E tombstoned: Tombstone written to: /data/tombstones/tombstone_17
12-31 19:42:47.103 2246 2246 I crash_dump64: performing dump of process 2208 (target tid = 2208)
12-31 19:42:47.108 2246 2246 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-31 19:42:47.108 2246 2246 F DEBUG : Build fingerprint: 'google/taimen/taimen:11/RP1A.200720.009/6720564:user/release-keys'
12-31 19:42:47.108 2246 2246 F DEBUG : Revision: 'rev_10'
12-31 19:42:47.108 2246 2246 F DEBUG : ABI: 'arm64'
12-31 19:42:47.109 2185 2261 I AudioFlinger: AudioFlinger's thread 0x7d93ddd040 tid=2261 ready to run
12-31 19:42:47.109 2246 2246 F DEBUG : Timestamp: 1969-12-31 19:42:47-0500
12-31 19:42:47.109 2246 2246 F DEBUG : pid: 2208, tid: 2208, name: app_process64 >>> /system/bin/app_process64 <<<
12-31 19:42:47.109 2246 2246 F DEBUG : uid: 0
12-31 19:42:47.109 2246 2246 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7e54c33f08
12-31 19:42:47.109 2185 2261 W AudioFlinger: no wake lock to update, system not ready yet
12-31 19:42:47.109 2246 2246 F DEBUG : x0 0000007bef61a210 x1 0000000000000101 x2 0000000000000000 x3 0000007e54891db8
12-31 19:42:47.109 2246 2246 F DEBUG : x4 0000000000000000 x5 0000007e55dc41a8 x6 f2aa9131d283ec11 x7 d61f0220f2c00fd1
12-31 19:42:47.109 2246 2246 F DEBUG : x8 0000007e54c34000 x9 0000000000000031 x10 0000007bef61a210 x11 0000000000000000
12-31 19:42:47.109 2246 2246 F DEBUG : x12 00000000000000c4 x13 f4beda67985e8bfb x14 0000000000000008 x15 0000000000000001
12-31 19:42:47.109 2246 2246 F DEBUG : x16 0000007e4ffda130 x17 0000007e54891f60 x18 0000007e54803c50 x19 95440998b0b39c01
12-31 19:42:47.109 2246 2246 F DEBUG : x20 0000007bef61a210 x21 0000007bef61a210 x22 0000007e54ad0000 x23 0000007e54ad0000
12-31 19:42:47.109 2246 2246 F DEBUG : x24 0000007e54748508 x25 0000007e5085edc2 x26 0000007e5087a000 x27 0000007d1f61128b
12-31 19:42:47.109 2246 2246 F DEBUG : x28 0000007e5085eda5 x29 0000007fc5dc2fe0
12-31 19:42:47.109 2246 2246 F DEBUG : lr 0000007e54891f98 sp 0000007fc5dc2f80 pc 0000007e54c33f08 pst 0000000000000000
trying this in the morning
https://forum.xda-developers.com/pixel-2-xl/help/stuck-flashing-patched-magisk-t4019013
Are you flashing the debug.zip (magisk)?
You could try changing the A/B slot.
Also, boot twrp.img, do not install it.
I dunno why people insist on doing things the hard way...moving the boot image to and from the device and patching it manually with magisk
If you fastboot TWRP, and just flash the magisk zip file, guess what it knows what to do and none of that slot swapping and other nonsense
Copy twrp-*.img and magisk-*.zip to folder on PC with platform tools (fastboot and adb etc), then:
Code:
ren magisk*.zip magisk.zip
ren twrp*.img twrp.img
adb reboot bootloader
fastboot boot twrp.img
adb push magisk.zip /tmp
adb shell twrp install /tmp/magisk.zip
adb reboot

[ROM][Android 12][OP7T Pro][Unofficial] crDroid v8.1 [20 January 2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device
also attempting to bringing many of the best features existent today
Features:: Click Here
Flashing Instructions:: Click Here (Thanks to @mukesh22584 )
Sources::
ROM: https://github.com/crdroidandroid
Kernel: Click Here
Download::
ROM: Click Here
Changelog:: Initial Build
GAPPS: Already Included
Visit official website @ crDroid.net
Donate to help our team pay server costs
crDroid Community Telegram
crDroid Updates Channel
Hi.
Device tree for "hotdog" are you using branch 11.0?
"My way" for installing this ROM (may be working on other custom ROMs)
Originally you required to format phone - this bring problem for copying all media up and down - i have > 130 Gb photos and videos
Phone rooted, was on crDroid A11
Found working on 7T PRO TWRP - https://androidfilehost.com/?fid=17825722713688250768
Extracted boot.img and run it through Magisk - got patched boot.img
Than all is very simple - install full ROM .zip through TWRP or sideload, reboot, reboot to TWRP and install new boot.img
That's all - everything working, rooted, all files, settings and progs in place!
All took time around 10 min (copying media to PC took ages!)
This TWRP booting very slowly - ~30 sec, but managed to decrypt everything and make backups
PS! Everybody welcome to try, but i'm not responsible for any bad outcome - do it on your own risk!
In anyway you have to format phone (install fresh stock ROM through MSM will take extra 15 min)
ROM is very good, fast and stable!
Addy-95 said:
GAPPS: Already Included
Click to expand...
Click to collapse
Can you build without them?
I used to always use CrDroid 7 (android 11), and always had some issues with VERY slow storage..
Then when KOSP was released on Android 12, I used that for a while and noticed the faster storage
The difference was very much noticeable, CrDroid gives me around 5MB/s over Wifi, KOSP around 55MB/s
So I hoped this was an android 11 quirk, but after flashing this CrDroid 12 version, I noticed the same slow transfer speeds..
Since I still wanted to flash Magisk, I had to flash a boot.img anyway... and thus I chose to flash the KOSP boot.img (magisk patched), and noticed the instant higher transfer speeds
I'm not sure what's different between the two kernels, I have not tested other functionality of the KOSP kernel on CrDroid ROM, but a quick test of Wifi, Mobile (data), Bluetooth and camera all seem fine
Giblet-dono said:
I used to always use CrDroid 7 (android 11), and always had some issues with VERY slow storage..
Click to expand...
Click to collapse
The same story with A11!
But with installing A12 "My way" got full speed!
ADB file transfer over 100Mps
USB-3 cable to USB-3 port on PC
WiFi over 50Mps
There is a problem with the link. can you check ?
Cemk91 said:
There is a problem with the link. can you check ?
Click to expand...
Click to collapse
Links works fine for me, make sure you choose the ROM download link, not the ROM Source link
NFC not working
logcat:
Code:
01-21 17:35:50.074 934 12901 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 12901 ([email protected]), pid 934 ([email protected])
01-21 17:35:50.201 12921 12921 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-21 17:35:50.201 12921 12921 F DEBUG : Build fingerprint: 'OnePlus/OnePlus7TPro/OnePlus7TPro:11/RKQ1.201022.002/2108161818:user/release-keys'
01-21 17:35:50.201 12921 12921 F DEBUG : Revision: '0'
01-21 17:35:50.201 12921 12921 F DEBUG : ABI: 'arm64'
01-21 17:35:50.201 12921 12921 F DEBUG : Timestamp: 2022-01-21 17:35:50.148935910+0300
01-21 17:35:50.202 12921 12921 F DEBUG : Process uptime: 0s
01-21 17:35:50.202 12921 12921 F DEBUG : Cmdline: /vendor/bin/hw/[email protected]
01-21 17:35:50.202 12921 12921 F DEBUG : pid: 934, tid: 12901, name: [email protected] >>> /vendor/bin/hw/[email protected] <<<
01-21 17:35:50.202 12921 12921 F DEBUG : uid: 1027
01-21 17:35:50.202 12921 12921 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
01-21 17:35:50.202 12921 12921 F DEBUG : x0 0000000000000000 x1 0000000000003265 x2 0000000000000006 x3 00000075aa8077c0
01-21 17:35:50.202 12921 12921 F DEBUG : x4 0000007636788000 x5 0000007636788000 x6 0000007636788000 x7 0000000000098e74
01-21 17:35:50.202 12921 12921 F DEBUG : x8 00000000000000f0 x9 00000000000003a6 x10 ffffff00ffffffdf x11 ffffff80ffffffdf
01-21 17:35:50.202 12921 12921 F DEBUG : x12 00000075aa807290 x13 0000000000000028 x14 00000075aa807418 x15 000048d2fca3d898
01-21 17:35:50.202 12921 12921 F DEBUG : x16 000000762e93f258 x17 000000762e914f80 x18 00000075aa612000 x19 00000000000003a6
01-21 17:35:50.202 12921 12921 F DEBUG : x20 0000000000003265 x21 00000000ffffffff x22 00000075aa807892 x23 00000075aa808010
01-21 17:35:50.202 12921 12921 F DEBUG : x24 00000075aa8078a0 x25 0000000000000009 x26 0000007630afd430 x27 0000007630adb1a5
01-21 17:35:50.202 12921 12921 F DEBUG : x28 0000007630afdd70 x29 00000075aa807840
01-21 17:35:50.202 12921 12921 F DEBUG : lr 000000762e8c2cf8 sp 00000075aa8077a0 pc 000000762e8c2d28 pst 0000000000000000
01-21 17:35:50.202 12921 12921 F DEBUG : backtrace:
01-21 17:35:50.202 12921 12921 F DEBUG : #00 pc 0000000000099d28 /apex/com.android.runtime/lib64/bionic/libc.so (abort+168) (BuildId: 89026beeb59556e9546bb64e92aedf90)
01-21 17:35:50.202 12921 12921 F DEBUG : #01 pc 0000000000029a3c /vendor/lib64/nfc_nci_nxp.so (phNxpNciHal_emergency_recovery()+60) (BuildId: d9a8fcfdb46a77277369241588022875)
01-21 17:35:50.202 12921 12921 F DEBUG : #02 pc 0000000000022050 /vendor/lib64/nfc_nci_nxp.so (phNxpNciHal_ext_process_nfc_init_rsp(unsigned char*, unsigned short*)+784) (BuildId: d9a8fcfdb46a77277369241588022875)
01-21 17:35:50.202 12921 12921 F DEBUG : #03 pc 0000000000021758 /vendor/lib64/nfc_nci_nxp.so (phNxpNciHal_process_ext_rsp(unsigned char*, unsigned short*)+2664) (BuildId: d9a8fcfdb46a77277369241588022875)
01-21 17:35:50.203 12921 12921 F DEBUG : #04 pc 000000000001a6ac /vendor/lib64/nfc_nci_nxp.so (phNxpNciHal_read_complete(void*, phTmlNfc_TransactInfo*)+316) (BuildId: d9a8fcfdb46a77277369241588022875)
01-21 17:35:50.203 12921 12921 F DEBUG : #05 pc 000000000001a3e8 /vendor/lib64/nfc_nci_nxp.so (phNxpNciHal_client_thread(void*)+328) (BuildId: d9a8fcfdb46a77277369241588022875)
01-21 17:35:50.203 12921 12921 F DEBUG : #06 pc 0000000000104b8c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 89026beeb59556e9546bb64e92aedf90)
01-21 17:35:50.203 12921 12921 F DEBUG : #07 pc 000000000009b440 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 89026beeb59556e9546bb64e92aedf90)
01-21 17:35:50.214 1128 2274 W NativeCrashListener: Couldn't find ProcessRecord for pid 934
01-21 17:35:50.224 3732 4016 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4016 (HwBinder:3732_1), pid 3732 (com.android.nfc)
01-21 17:35:50.240 1128 1823 I BootReceiver: Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
01-21 17:35:50.241 1128 1823 I DropBoxManagerService: add tag=SYSTEM_TOMBSTONE isTagEnabled=true flags=0x6
01-21 17:35:50.250 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
01-21 17:35:50.250 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-21 17:35:50.255 1128 1823 E NativeTombstoneManager: Tombstone's UID (1027) not an app, ignoring
01-21 17:35:50.256 1128 1823 I DropBoxManagerService: add tag=SYSTEM_TOMBSTONE_PROTO isTagEnabled=true flags=0x4
01-21 17:35:50.261 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
01-21 17:35:50.261 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-21 17:35:50.817 12933 12933 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-21 17:35:50.818 12933 12933 F DEBUG : Build fingerprint: 'OnePlus/OnePlus7TPro/OnePlus7TPro:11/RKQ1.201022.002/2108161818:user/release-keys'
01-21 17:35:50.818 12933 12933 F DEBUG : Revision: '0'
01-21 17:35:50.818 12933 12933 F DEBUG : ABI: 'arm64'
01-21 17:35:50.818 12933 12933 F DEBUG : Timestamp: 2022-01-21 17:35:50.396693539+0300
01-21 17:35:50.818 12933 12933 F DEBUG : Process uptime: 0s
01-21 17:35:50.818 12933 12933 F DEBUG : Cmdline: com.android.nfc
01-21 17:35:50.818 12933 12933 F DEBUG : pid: 3732, tid: 4016, name: HwBinder:3732_1 >>> com.android.nfc <<<
01-21 17:35:50.818 12933 12933 F DEBUG : uid: 1027
01-21 17:35:50.818 12933 12933 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
01-21 17:35:50.818 12933 12933 F DEBUG : x0 0000000000000000 x1 0000000000000fb0 x2 0000000000000006 x3 0000006ffa2c3690
01-21 17:35:50.818 12933 12933 F DEBUG : x4 0000007059797080 x5 0000007059797080 x6 0000007059797080 x7 0000007059642dc0
01-21 17:35:50.818 12933 12933 F DEBUG : x8 00000000000000f0 x9 0000000000000e94 x10 ffffff00fffffbdf x11 ffffff80fffffbdf
01-21 17:35:50.818 12933 12933 F DEBUG : x12 0000006ffc94d22c x13 0000000000000007 x14 0000006ffa2c32e8 x15 00002c8ea875aa5a
01-21 17:35:50.818 12933 12933 F DEBUG : x16 00000070f8fd2258 x17 00000070f8fa7f80 x18 0000006ff9eb4008 x19 0000000000000e94
01-21 17:35:50.818 12933 12933 F DEBUG : x20 0000000000000fb0 x21 00000000ffffffff x22 0000006ffa4e9790 x23 000000008008720f
01-21 17:35:50.818 12933 12933 F DEBUG : x24 0000006ffa2c4000 x25 0000006ffa2c3cb0 x26 0000006ffa2c3ff8 x27 00000000000fc000
01-21 17:35:50.818 12933 12933 F DEBUG : x28 0000006ffa1cb000 x29 0000006ffa2c3710
01-21 17:35:50.818 12933 12933 F DEBUG : lr 00000070f8f55cf8 sp 0000006ffa2c3670 pc 00000070f8f55d28 pst 0000000000000000
01-21 17:35:50.818 12933 12933 F DEBUG : backtrace:
01-21 17:35:50.818 12933 12933 F DEBUG : #00 pc 0000000000099d28 /apex/com.android.runtime/lib64/bionic/libc.so (abort+168) (BuildId: 89026beeb59556e9546bb64e92aedf90)
01-21 17:35:50.818 12933 12933 F DEBUG : #01 pc 00000000000c8994 /system/lib64/libnfc-nci.so (NfcHalDeathRecipient::serviceDied(unsigned long, android::wp<android::hidl::base::V1_0::IBase> const&)+260) (BuildId: 8cbb444ca1caaf151c08c91dde2fd826)
01-21 17:35:50.818 12933 12933 F DEBUG : #02 pc 0000000000056a80 /system/lib64/libhidlbase.so (android::hardware::hidl_binder_death_recipient::binderDied(android::wp<android::hardware::IBinder> const&)+112) (BuildId: 3c8aaa4d61f2720f45004b0dcbd3cd17)
01-21 17:35:50.818 12933 12933 F DEBUG : #03 pc 0000000000078c0c /system/lib64/libhidlbase.so (android::hardware::BpHwBinder::reportOneDeath(android::hardware::BpHwBinder::Obituary const&)+124) (BuildId: 3c8aaa4d61f2720f45004b0dcbd3cd17)
01-21 17:35:50.818 12933 12933 F DEBUG : #04 pc 0000000000078b04 /system/lib64/libhidlbase.so (android::hardware::BpHwBinder::sendObituary()+196) (BuildId: 3c8aaa4d61f2720f45004b0dcbd3cd17)
01-21 17:35:50.818 12933 12933 F DEBUG : #05 pc 00000000000769fc /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+2860) (BuildId: 3c8aaa4d61f2720f45004b0dcbd3cd17)
01-21 17:35:50.818 12933 12933 F DEBUG : #06 pc 0000000000075df0 /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+96) (BuildId: 3c8aaa4d61f2720f45004b0dcbd3cd17)
01-21 17:35:50.818 12933 12933 F DEBUG : #07 pc 0000000000075d78 /system/lib64/libhidlbase.so (android::hardware::PoolThread::threadLoop()+24) (BuildId: 3c8aaa4d61f2720f45004b0dcbd3cd17)
01-21 17:35:50.818 12933 12933 F DEBUG : #08 pc 00000000000123a4 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+260) (BuildId: 976956de34b149071d3fc12c09b86d86)
01-21 17:35:50.818 12933 12933 F DEBUG : #09 pc 00000000000bc950 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+144) (BuildId: bfc9c365ddfcf8f1bd2511d931bc86a3)
01-21 17:35:50.818 12933 12933 F DEBUG : #10 pc 0000000000011bf4 /system/lib64/libutils.so (thread_data_t::trampoline(thread_data_t const*)+404) (BuildId: 976956de34b149071d3fc12c09b86d86)
01-21 17:35:50.818 12933 12933 F DEBUG : #11 pc 0000000000104b8c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 89026beeb59556e9546bb64e92aedf90)
01-21 17:35:50.818 12933 12933 F DEBUG : #12 pc 000000000009b440 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 89026beeb59556e9546bb64e92aedf90)
01-21 17:35:50.852 1128 1823 I BootReceiver: Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE)
01-21 17:35:50.852 1128 1823 I DropBoxManagerService: add tag=SYSTEM_TOMBSTONE isTagEnabled=true flags=0x6
01-21 17:35:50.859 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
01-21 17:35:50.859 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-21 17:35:50.875 1128 1823 E NativeTombstoneManager: Tombstone's UID (1027) not an app, ignoring
01-21 17:35:50.876 1128 1823 I DropBoxManagerService: add tag=SYSTEM_TOMBSTONE_PROTO isTagEnabled=true flags=0x4
01-21 17:35:50.900 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
01-21 17:35:50.900 1128 1564 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-21 17:35:50.937 1128 12768 I ActivityManager: Process com.android.nfc (pid 3732) has died: pers PER
01-21 17:35:50.939 1128 12768 W ActivityManager: Re-adding persistent process ProcessRecord{71f2edb 3732:com.android.nfc/1027}
01-21 17:35:50.941 1128 12768 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 1027; state: DISABLED
Problem with SELinux:
[ 1571.481815] [20220121_17:35:44.954532]@2 type=1400 audit(1642775744.951:355): avc: denied { write } for comm="[email protected]" name="nfc" dev="dm-10" ino=273 scontext=u:r:hal_nfc_default:s0 tcontext=ubject_r:vendor_nfc_vendor_data_file:s0 tclass=dir permissive=0
Click to expand...
Click to collapse
All SELinux denials:
# dmesg | grep avc: | grep -v untrusted
hotdog:/ # dmesg | grep avc: | grep -v untrusted - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
This commit kills [email protected]. It needs to be rolled back.
In sepolicy/vendor/hal_nfc_default.te need to add
Code:
allow hal_nfc_default vendor_nfc_vendor_data_file:dir rw_dir_perms;
At the moment, for me, the service does not fall, but payment does not occur either. The terminal began to give an error (before my changes, the terminal did not connect to the phone at all)
Perhaps they just didn't implement proper support for Google Pay on A12 ROMs yet.
I'm on Xtended and get the same behavior, NFC works but payment doesn't trigger.
I fixed the NFC. I'll post the fixes a little later.
ShevT said:
I fixed the NFC. I'll post the fixes a little later.
Click to expand...
Click to collapse
@Addy-95
Commits · 12.0 · ShEV / proprietary_vendor_oneplus_sm8150-common · GitLab
Forked from https://github.com/crdroidandroid/proprietary_vendor_oneplus_sm8150-common
gitlab.com
Commits · 12.0 · ShEV / android_device_oneplus_sm8150-common · GitLab
Fork: https://github.com/crdroidandroid/android_device_oneplus_sm8150-common
gitlab.com
Magisk module for fix nfc
@Gwolf2u, @Addy-95 - no guys, this is my job, not yours.
sm8150-common: nfc: pin firmware and update config hash (d3177598) · Commits · crDroid Android / proprietary_vendor_oneplus_sm8150-common · GitLab
GitLab.com
gitlab.com
Please correct copyright
The conflict is over. Thank you for your work!​
@ShevT thanks a million for looking into and fixing the NFC regression.
And also supplying a flashable magisk fix for other roms, now that's what I call respect.
Unfortunately I've already reverted back to OOS (due to the lack of Google Pay), but I'll probably go back to A12 and flash your ROM this coming weekend!
Installed flawlessly, will start set up now. Thank your for A12.
Hi together,
Somebody know if this build will be get offical? I want to update from 7.12
Thanks a lot
@Addy-95, If you don't have time to support the project, I can take care of it.
ShevT said:
@Addy-95, If you don't have time to support the project, I can take care of it.
Click to expand...
Click to collapse
ofcourse

Categories

Resources