Develop Bugs

Evervolv 3.2/CM10.1 (4.2.2) development thread -All welcome

{
"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"
}
This is the start of the Evervolv build for the PrimoU, it should give us all a good base to learn how to build from source and get more roms up and running for this device. The original device tree and msm7x30 come from @1ceb0x who I am extremely grateful for helping me understand the little I already do.
https://github.com/mcgi5sr2 contains all the sources I have so far.
Working:
boot to adb
Not Working:
Everything else
XDA:DevDB Information
EV3.2/CM10.1 restart, a ROM for the HTC One V
Contributors
mcgi5sr2, mcgi5sr2, MScorporation95
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: PrimoU
Based On: AOSP
Version Information
Status: Alpha
Current Stable Version: N/A
Created 2014-04-07
Last Updated 2014-04-17

Status:
20140407: Rom boots past HTC logo and adb is available, no bootanimation
Handy Terminal Commands:
#Make rom command can use mka instead in CM based roms, also creates log -j* indicates number of cores to use in building
make -j8 otapackage 2>&1 | tee filename.log
#Adds logcat pull request -thanks Lloir
add this to your init.primou.rc
service logcat /system/bin/logcat -f /data/data/logcat
class main
oneshot
reboot into recovery once you got "enough"
adb pull /data/data/logcat
and tada you have a logcat
#Pulls last kernel kmsg - reboot straight into recovery then pull -thanks Simon
adb pull /proc/last_kmsg kernel.txt
#Clears the heads for a new clean sync - helps fix repo sync issues
repo forall -vc "git reset --hard"

So building from source is fun and can take a lot of time. Ultimately it will benefit you and the community somehow.
http://forum.xda-developers.com/showthread.php?t=2060017
Is a good starting point.
http://wiki.cyanogenmod.org/w/Development
Also contains loads of info on how to get started on it all
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
and also how to port
http://elinux.org/Android_Build_System
How building works...
Also the Evervol git hub:
https://github.com/Evervolv/android
will show you the sources we are currently using, I have no qualms with anyone going freelance and splitting into their own sources or anything else they want to try. I can help with the compiling errors etc, where I can but not with anything after that as I am yet to get through all of that myself.
Anyway I am trying to build the JellyBean version which relates to EV3.2 or Android 4.2.2

Code:
I/DEBUG ( 7076): memory map around fault addr deadbaad:
I/DEBUG ( 7076): be9f8000-bea19000 [stack]
I/DEBUG ( 7076): (no map for address)
I/DEBUG ( 7076): ffff0000-ffff1000 [vectors]
I/Netd (24351): Netd 1.0 starting
W/InterfaceController(24351): Warning (Cannot load library: load_library(linker.cpp:747): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
D/MDnsDS (24351): MDnsSdListener::Hander starting up
D/MDnsDS (24351): MDnsSdListener starting to monitor
D/MDnsDS (24351): Going to poll with pollCount 1
I/SurfaceFlinger(24558): SurfaceFlinger is starting
I/SurfaceFlinger(24558): use dithering
I/SurfaceFlinger(24558): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL (24558): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL (24558): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL (24558): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL(24558): <qeglDrvAPI_eglInitialize:294>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB.04.01.01.00.036_msm8960_JB_CL2644550_release_AU (CL2644550)
I/Adreno200-EGL(24558): Build Date: 07/31/12 Tue
I/Adreno200-EGL(24558): Local Branch:
I/Adreno200-EGL(24558): Remote Branch: quic/master
I/Adreno200-EGL(24558): Local Patches: NONE
I/Adreno200-EGL(24558): Reconstruct Branch: AU_LINUX_ANDROID_JB.04.01.01.00.036 + NOTHING
I/gralloc (24558): using (fd=20)
I/gralloc (24558): id = msmfb40_0
I/gralloc (24558): xres = 480 px
I/gralloc (24558): yres = 800 px
I/gralloc (24558): xres_virtual = 480 px
I/gralloc (24558): yres_virtual = 2400 px
I/gralloc (24558): bpp = 32
I/gralloc (24558): r = 0:8
I/gralloc (24558): g = 8:8
I/gralloc (24558): b = 16:8
I/gralloc (24558): width = 52 mm (234.461533 dpi)
I/gralloc (24558): height = 88 mm (230.909088 dpi)
I/gralloc (24558): refresh rate = 60.00 Hz
D/CALCFPS (24558): DEBUG_CALC_FPS: 0
D/CALCFPS (24558): period: 10
D/CALCFPS (24558): ignorethresh_us: 500000
D/CALCFPS (24558): DEBUG_CALC_FPS: 0
D/CALCFPS (24558): period: 10
D/CALCFPS (24558): ignorethresh_us: 500000
E/HAL (24558): load: module=/system/lib/hw/hwcomposer.msm7x30.so
E/HAL (24558): Cannot load library: soinfo_relocate(linker.cpp:989): cannot locate symbol "_ZN7overlay7Overlay12waitForVsyncENS_5utils5eDestE" referenced by "hwcomposer.msm7x30.so"...
E/SurfaceFlinger(24558): hwcomposer module not found
W/SurfaceFlinger(24558): getting VSYNC period from fb HAL: 16666666
W/Adreno200-EGL(24558): <qeglDrvAPI_eglChooseConfig:780>: EGL_BAD_ATTRIBUTE
W/SurfaceFlinger(24558): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
W/SurfaceFlinger(24558): no suitable EGLConfig found, trying without EGL_RECORDABLE_ANDROID
E/Trace (24558): error opening trace file: No such file or directory (2)
Code:
D/AndroidRuntime(24561):
D/AndroidRuntime(24561): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime(24561): CheckJNI is OFF
D/dalvikvm(24561): Trying to load lib libjavacore.so 0x0
D/dalvikvm(24561): Added shared lib libjavacore.so 0x0
D/dalvikvm(24561): Trying to load lib libnativehelper.so 0x0
D/dalvikvm(24561): Added shared lib libnativehelper.so 0x0
E/dalvikvm(24561): ERROR: couldn't find native method
E/dalvikvm(24561): Requested: Landroid/net/wifi/WifiNative;.killSupplicant:(Z)Z
E/dalvikvm(24561): Candidate: Landroid/net/wifi/WifiNative;.killSupplicant:()Z
E/JNIHelp (24561): RegisterNatives failed for 'android/net/wifi/WifiNative', aborting
F/libc (24561): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 24561 (zygote)
I/DEBUG ( 7076): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Seems its a wifi issue holding us up right now
@Lloir fancy throwing any helpful hints.

What I am trying to do next...
##New Stuff to look into
Its a Framework reboot issue. You need to collect ADB logs from the boot up.
adb logcat -v threadtime > logcat.txt
adb shell cat /proc/kmsg > kernellogs.txt
.............
adb bugreport > bugreport.txt
................
Make sure you clear below things at the beginning
/data/anr/*
/data/tombstone/*
Pull the traces and tombstone files from the /data/anr and /data/tombstone
adb pull /data/anr/ .
adb pull /data/tombstone .
Note: You can save in any folder by logging it outside the adb shell prompt
Search for the time stamp where you encountered the Framework reboot.
Map it appropriately with the traces/tombstones to find the issue
Click to expand...
Click to collapse
Scratch the tombstone bit as we don't seem to have that on the phone :'(

Hah Good luck. I can help you if you need, but I don't think that we can do new 4.2 base for it

Minto107 said:
Hah Good luck. I can help you if you need, but I don't think that we can do new 4.2 base for it
Click to expand...
Click to collapse
Thanks Minto, but I'm not sure what you mean?

This phone is not supported like some years ago. There is no one who can help us
Wysłane z mojego HTC One V przy użyciu Tapatalka

Minto107 said:
This phone is not supported like some years ago. There is no one who can help us
Wysłane z mojego HTC One V przy użyciu Tapatalka
Click to expand...
Click to collapse
If there's no one who can help us, we'll stick together and make it work..
@mcgi5sr2 I'm almost ready just syncing repos...

This phone is a fail and it was a fail so what do you want from it? It was next bad HTC phone, now there are more bad than good ones. Sure we can try.
Wysłane z mojego HTC One V przy użyciu Tapatalka

Minto107 said:
This phone is a fail and it was a fail so what do you want from it? It was next bad HTC phone, now there are more bad than good ones. Sure we can try.
Wysłane z mojego HTC One V przy użyciu Tapatalka
Click to expand...
Click to collapse
did you suddenly completely lose confidence.
and poland has a cool national anthem.
@mcgi5sr2 What's in logcat ...?

It's caused that I was using One S and S3 last time
Wysłane z mojego HTC One V przy użyciu Tapatalka

MameTozhio said:
did you suddenly completely lose confidence.
and poland has a cool national anthem.
@mcgi5sr2 What's in logcat ...?
Click to expand...
Click to collapse
I don't get what national anthem have to losing confidence because of bad phones

Hi guys,
I'm too happy to see people actually alive on the forum to worry about phone. Agreed it is a difficult beast, but I figure if we cut our teeth here everything else is only going to be easier in future! Also I think that a lot of the lessons we learn on Evervolv will help CM10.1 and then CM11 builds as well. The more of us know something about the phone, how it works, what loving it needs the better.
Logcat:
logcat.txt - 646.91 KB
BugReport:
bugreport.txt - 614.13 KB
Traces:
traces.txt.bugreport - 1.15 KB
I'm still perusing to try and work out what the magic is, I am starting to think its a frameworks problem, but thats only from the similarity in issues with other people I've found on google.
 @MameTozhio thanks for sticking with us !
 @MScorporation95 will do eventually we will end up as genuine Devs!
 @Minto107 I agree with almost all you said, but I have the phone until at least September, want to learn to Dev some more, and also don't know what I would do with a top of the line super powered phone right now...

Anything new? I'm looking at logcat which you sent.
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
First: There is a problem with Adreno drivers
Many libs are missing
This rly important lib is missing: libnetcmdiface.so ROM is calling it really often

Minto107 said:
Anything new? I'm looking at logcat which you sent.
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
First: There is a problem with Adreno drivers
Many libs are missing
This rly important lib is missing: libnetcmdiface.so ROM is calling it really often
Click to expand...
Click to collapse
Not made any real progress on EV3.2 but have now got a CM10.1 built and squished the first booting issue today. Will post sources once I'm back on a good connection. I am genuinely hopeful that we may get a build up and running both for CM10.1 and EV as AOSP.
With all this learning then we can apply it to CM11!
Sorry to be taking so long, but I am travelling for courses all month.

why everlov, sphongle is based on everlov

Hi cyber,
I used evervolv for that exact reason so that I could learn how it was done, and what did what. Also evervolv is a good base for use as it has legacy depositories.
I am also working through CM10.1 right now as well, I have ADB up and running and am currently looking for a fix for this badger
W/InterfaceController( 9806): Warning (Cannot load library: load_library(linker.cpp:771): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
might be able to add it to packages in the device make, but need to do a bit more research first. OK seemed to do the trick including the package, next up seems to be an egl error:
I/Netd ( 4825): Netd 1.0 starting
D/MDnsDS ( 4825): MDnsSdListener::Hander starting up
D/MDnsDS ( 4825): MDnsSdListener starting to monitor
D/MDnsDS ( 4825): Going to poll with pollCount 1
I/SurfaceFlinger( 5033): SurfaceFlinger is starting
I/SurfaceFlinger( 5033): use dithering
I/SurfaceFlinger( 5033): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 5033): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 5033): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 5033): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 5033): <qeglDrvAPI_eglInitialize:294>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB.04.01.01.00.036_msm8960_JB_CL2644550_release_AU (CL2644550)
I/Adreno200-EGL( 5033): Build Date: 07/31/12 Tue
I/Adreno200-EGL( 5033): Local Branch:
I/Adreno200-EGL( 5033): Remote Branch: quic/master
I/Adreno200-EGL( 5033): Local Patches: NONE
I/Adreno200-EGL( 5033): Reconstruct Branch: AU_LINUX_ANDROID_JB.04.01.01.00.036 + NOTHING
F/libc ( 5033): Fatal signal 11 (SIGSEGV) at 0x00000001 (code=1), thread 5034 (SurfaceFlinger)
I/DEBUG ( 1513): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1513): Build fingerprint: 'htc_europe/htc_primou/primou:4.2.2/JDQ39/330937:user/user-debug'
I/DEBUG ( 1513): Revision: '2'
I/DEBUG ( 1513): pid: 5033, tid: 5034, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<

Cool Rom!

Any progress?
Waiting for CM10.1 eagerly!
:good::good::good:

[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)

[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Q&A for [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

alarm clock
Recently discussed the problem that the included headphones alarm clock rang only from external speakers. Now it rings only from the headphones. But it would be optimal to it when headphones are connected rang simultaneously and external speakers and headphone out. So it is correct and it is so sold on the official firmware.
Sorry for my bad English.

Del
---------- Post added at 03:30 AM ---------- Previous post was at 03:24 AM ----------
Hi, will snapshot m12 for LTE?

Do you just dirty flash the nightlife? I tried going the update route but it doesn't work.

Hi all!
First of all thank you for the Roma and the whole tutorial is perfect on my side on my "tab pro lte"
I would like to know how to overclock the processor above its Standard power?
sorry for the mistakes, I'm French and I use google translation ... oO
thank you!

No mobile data
Thanks to the dev for his continuous efforts on this rom, keep up the good work. However, i noticed that mobile data doesn't work for 2g networks. I've tried using the "preferred network type" and even changing the sim but it still won't work. When i get into 3g or LTE zonse the mobile data begins to work. Please could you suggest a fix. I'm currently limited to 2g so it would be a big help. Thanks

Any hints on building CM12 for this device ? I'm willing to do it if there is any documentation help.

Firmware crude

CM-12 test
Deleted

DensonX said:
Sorry if this is off-topic, but I have seen a lot of people requesting CyanogenMod 12 for this device. I managed to build CM-12 for the mondrianlte, however it does not flash on my device. I get an error saying E: error executing binary in zip. I suspect this may be due to the fact that I have a european Tab Pro, so if anyone with a US Tab Pro LTE wants to try to install it here's a file. https://drive.google.com/file/d/0Bxf2YUR9_3hDX3JUbnJYbWVfTTA/view?usp=sharing
Do NOT forget to backup before attempting to install this, as it likely will not work.
Also if anyone knows how to solve my problem with flashing this please let me know.
Click to expand...
Click to collapse
Please do not post links to other builds in my thread. Especially ones that you can't even flash because it doesn't work for you!
This only adds confusion.
I will try to release something soon. It may have a broken camera (the camera is broken on picassolte and if I can't figure it out I'll have to just leave it broken for both mondrianlte and picassolte for now) but otherwise has been working well for me on picassolte.

SM-T325, CM12 and encryption
Hello,
First Thank you crpalmer for your great work on mondrianlte. I've been using for roughly one month and did not encounter any serious issue, it is working so much better than stock Samsung ROMs ! I only got into problems when trying to encrypt the tablet (with cm-12-20150321-UNOFFICIAL-mondrianlte).
Once the process was started it rebooted very quickly and got stuck on the boot cyanogenmod screen. A forced off/on cycle was able to restore the tablet normal operation, but it had not been encrypted.
Relevant portions of the adb log seem to be :
(just after the beginning of the encrytion process)
Code:
E/Cryptfs ( 243): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
D/Cryptfs ( 243): Just asked init to shut down class main
and later when the tablet reboots :
Code:
D/Cryptfs ( 243): unmounting /data succeeded
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 243): Loading keymaster app failed
E/Cryptfs ( 243): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 243): Failed to init keymaster
--------- beginning of crash
F/libc ( 243): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 315 (vold)
F/libc ( 243): Unable to open connection to debuggerd: Connection refused
I/Vold (26973): Vold 2.1 (the revenge) firing up
D/Vold (26973): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold (26973): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs (26973): Check if PFE is activated on Boot
E/Cryptfs (26973): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs (26973): Error getting crypt footer and key
files /vendor/firmware/keymaster/keymaster.* have permission 644, user/group root, and are symlinks into /firmware/image/. In /firmware/image/, keymaste.* files have permission 440, user system, group drmrpc. Based on the QSEECOMAPI errors above, I am unable to determine whether these access rights are correct. I assume that even if they were, some incorrect SElinux configuration could cause access problems ?
Is anyone able to figure out what is happening ? Is it useful that I post a full log of the process ?

"Welcome" Screen of ROM Fails to Respond to Touch

I rooted my SGH-T999, running Android 4.3, flashing TWRP recovery w/ Odin.
The rooting was successful.
Now, on to the part where I ran into trouble.
Problem: I can't successfully install any ROMs for Android M or later.
NOTE: I need Android M or later to have more control over individual apps' permissions.
I tried to flash Pac-ROM through TWRP, like so:
(from TWRP home menu)
1. Wipe>Swipe to Factory Reset
2. Go Back to Home Menu
3. Install>Select pac_d2tmo_MM.Beta.Official_20160920-165602.zip>Swipe to confirm Flash
Note: The first time I tried to flash Pac-ROM, I wasn't aware of GApps. So, I didn't flash it.
4. Reboot
The phone booted to the "Welcome/Language Selection" screen, but I couldn't select a language.
It seems that the UI elements belonging to the "Welcome" screen fail to respond to touch, while other UI elements respond normally (as demonstrated at the end of the video at the URL below).
All attempts to re-flash, since, have included the additional step off adding the GApps zip (for ARM, Android 6.0) to the "ZIP Queue".
However, all attempts end the same way.
I've documented the process in the video @ the following URL: youtu.be/EZTwaURkRSs
Another strange behavior (that isn't apparent in the video) is that, immediately after being shown on the display, the "Welcome" screen looks fine for a few hundred milliseconds or so before the screen is drawn with a yellowish-hue. As if blue-light filtering kicks in (even when the system clock is mid-day).
I also tried to flash a different ROM (Oct-OS OCT-M-R3) on a few of the attempts, but again I observed the same exact behavior ("Welcome" screen's yellowish hue and lack of response to touch).
It doesn't seem to be a hardware issue, because touch does work, just not on the "Welcome" screen.
I'm fairly certain I've selected the correct ROM for the model.
So, what did I mess up?

I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again

andynoob said:
I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again
Click to expand...
Click to collapse
Do you mean that you were able to flash a ROM successfully, after flashing stock (4.4.2)?
Or, you were ONLY able to flash stock (4.4.2) successfully?
Thank you for the reply,
Gerald

I just restored my twrp backup of stock os .. Had urgent work so couldn't try to flash those ROMs again.. will try them next week

UPDATE:
So, I successfully restored my stock backup.
With the stock setup I experienced no problems.
Since my original post, I've alternated between restoring stock backup and flashing ROMs.
I tried flashing Oct-OS and Pac-ROM, again and again.
I also tried to install LineageOS, as well.
I am able to install CyanogenMod 12.1, but this doesn't meet my requirement of android version 6 or later.
Installation of any of the custom ROMs has resulted in the same behavior demonstrated in the video (youtu.be/EZTwaURkRSs):
- after boot, device fails to respond to touch input
- however, device does accept touch input on some UI objects. so, I don't think it's a screen/hardware issue
How can I debug further?
I'd like to try to capture some sort of boot log, but adb is "offline" during boot process.
And, since I can't make it past the "language selection/welcome" screen, I can't get to settings and enable USB debugging.

UPDATE:
I managed to enable ADB during boot, by using the ADB shell while the device was in recovery mode.
Code:
[email protected] ~ $ adb push ~/.android/adbkey.pub /data/misc/adb/
[email protected] ~ $ adb shell
~# cd /data/misc/adb/
/data/misc/adb# cat adbkey.pub > adb_keys
/data/misc/adb# cd /
~# mkdir /system2
~# mount -o rw /dev/block/mmcblk0p14 /system2 ## NOTE: for this command, had to figure out which partition was the system partition; here it was /dev/block/mmcblk0p14
~# echo "persist.service.adb.enable=1" >> default.prop
~# echo "persist.service.debuggable=1" >> default.prop
~# echo "persist.sys.usb.config=mtp,adb" >> default.prop
~# echo "persist.service.adb.enable=1" >> /system2/build.prop
~# echo "persist.service.debuggable=1" >> /system2/build.prop
~# echo "persist.sys.usb.config=mtp,adb" >> /system2/build.prop
~# ## now press Ctrl-D to exit the ADB shell
NOTE: thanks to @ErnestChia for the following post forum.xda-developers.com/showpost.php?p=63829295&postcount=27
So, I was able to get a logcat during the SetupWizard.
There were 3 lines, related to the SystemUI, that were repeated over and over.
Code:
W BroadcastQueue: Timeout of broadcast BroadcastRecord{51dfd23 u-1 android.intent.action.TIME_TICK} - [email protected], started 10010ms ago
W BroadcastQueue: Receiver during timeout: BroadcastFilter{a4079bf u0 ReceiverList{4b103de 730 com.android.systemui/10018/u0 remote:448f719}}
I ActivityManager: Skipping duplicate ANR: ProcessRecord{768d889 730:com.android.systemui/u0a18} Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
All I've gathered is that SystemUI isn't responding.
Which seems to have started during boot, with the following output.
Code:
W ActivityManager: Timeout executing service: ServiceRecord{dd2251a u0 com.android.systemui/.ImageWallpaper}
E ActivityManager: ANR in com.android.systemui
E ActivityManager: Reason: executing service com.android.systemui/.ImageWallpaper
E ActivityManager: 4.1% 730/com.android.systemui: 2.2% user + 1.8% kernel / faults: 1246 minor 2 major
SystemUI Stack Trace
Code:
Cmd line: com.android.systemui
Build fingerprint: 'samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys'
ABI: 'arm'
Build type: optimized
Zygote loaded classes=3986 post zygote classes=991
Intern table: 46441 strong; 62 weak
JNI: CheckJNI is off; globals=427 (plus 368 weak)
Libraries: /system/lib/libandroid.so /system/lib/libcompiler_rt.so /system/lib/libjavacrypto.so /system/lib/libjnigraphics.so /system/lib/libmedia_jni.so /system/lib/libsoundpool.so /system/lib/libwebviewchromium_loader.so libjavacore.so (8)
Heap: 5% free, 12MB/13MB; 84371 objects
Dumping cumulative Gc timings
Total number of allocations 84371
Total bytes allocated 12MB
Total bytes freed 0B
Free memory 813KB
Free memory until GC 813KB
Free memory until OOME 179MB
Total memory 13MB
Max memory 192MB
Zygote space size 1972KB
Total mutator paused time: 0
Total time waiting for GC to complete: 0
Total GC count: 0
Total GC time: 0
Total blocking GC count: 0
Total blocking GC time: 0
...
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x745992a0 self=0xb77f9b30
| sysTid=730 nice=0 cgrp=default sched=0/0 handle=0xb6efab44
| state=S schedstat=( 0 0 0 ) utm=64 stm=14 core=1 HZ=100
| stack=0xbe5d0000-0xbe5d2000 stackSize=8MB
| held mutexes=
native: #00 pc 0004290c /system/lib/libc.so (__ioctl+8)
native: #01 pc 00049391 /system/lib/libc.so (ioctl+14)
native: #02 pc 0001e8c9 /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+132)
native: #03 pc 0001eefb /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+38)
native: #04 pc 0001f0b1 /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+124)
native: #05 pc 0001a0b3 /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
native: #06 pc 00089471 /system/lib/libandroid_runtime.so (???)
native: #07 pc 00db9189 /data/dalvik-cache/arm/[email protected]@boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+140)
at android.os.BinderProxy.transactNative(Native method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:421)
at java.lang.reflect.Method.invoke!(Native method)
at android.hardware.camera2.utils.Decorator.invoke(Decorator.java:80)
at java.lang.reflect.Proxy.invoke(Proxy.java:393)
at android.hardware.ICameraService.getCameraCharacteristics(ICameraService.java:-2)
at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:635)
at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:99)
- locked <0x0da89d30> (a java.lang.Object)
at com.android.systemui.statusbar.policy.FlashlightController.getCameraId(FlashlightController.java:126)
at com.android.systemui.statusbar.policy.FlashlightController.<init>(FlashlightController.java:62)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:1087)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3285)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3281)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:619)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:800)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:230)
at com.android.systemui.statusbar.ServiceMonitor.-wrap5(ServiceMonitor.java:-1)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5466)
at java.lang.reflect.Method.invoke!(Native method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

i solved this issue by flashing the pac rom 6.0 from at&t . (Flash only the rom )

Do you have a copy of carbon ROM or Pac man for the d2tmo?

[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

GL Error makes apps crash on CUSTOM ROM

i got a problem while trying to enter on Incognite Mode on Chrome, or when I try to play a song on Spotify while I got my headphones connected through bluetooth on Spotify, Chrome and Spotify crashes and they have the same error, which says "GL errors frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550"
My device is a MTK Processor MT6580 Kernel 3.18.19 Official Android version 6.0.1 but I ported it to 7.1.2 and running OS fine except this issue I dont know how to fix
the problem generated on the logs is this:
Process: com.spotify.music
Flags: 0x38d83e44
Package: com.spotify.music v85204766 (8.7.18.1138)
Foreground: Yes
Build: 'BLU/xxx/xxx:7.1.2/xxxx/xxx:userdebug/release-keys'
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Cardinal-AOSP Version: '4.5'
Build fingerprint: 'BLU/xxx/xxx:7.1.2/xxxx/xxx:userdebug/release-keys'
Revision: '0'
ABI: 'arm'
pid: 5099, tid: 5220, name: RenderThread >>> com.spotify.music <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'GL errors! frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550'
r0 00000000 r1 00001464 r2 00000006 r3 00000008
r4 8f5f0978 r5 00000006 r6 8f5f0920 r7 0000010c
r8 94ae0b80 r9 00000000 sl 973882fc fp 973882f8
ip 00000000 sp 8f5eff38 lr b4384ec7 pc b4387748 cpsr 20070010
backtrace:
#00 pc 0004a748 /system/lib/libc.so (tgkill+12)
#01 pc 00047ec3 /system/lib/libc.so (pthread_kill+34)
#02 pc 0001d6f5 /system/lib/libc.so (raise+10)
#03 pc 00019241 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 000171f8 /system/lib/libc.so (abort+4)
#05 pc 0000c1dd /system/lib/libcutils.so (__android_log_assert+112)
#06 pc 00024077 /system/lib/libhwui.so
#07 pc 00025a73 /system/lib/libhwui.so
#08 pc 00029035 /system/lib/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+80)
#09 pc 0000e3fd /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+140)
#10 pc 00066c11 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+80)
#11 pc 00047993 /system/lib/libc.so (_ZL15__pthread_startPv+22)
#12 pc 00019c8d /system/lib/libc.so (__start_thread+6)
Do u have any idea what file is causing that on the ported rom and what i have to replace from stock to there? I'd appreciate any help from you, I like porting and stuff so I wish i could fix this I'd appreciate any help

I fixed the issue years ago and shared it for mt6580 community. You can grab my fixcrash patch for mt6580 on Kernel 3.18.19.
You will find some other patches too, If you need it. A bit late, but maybe it helps someone.
MT6580 - Google Drive
drive.google.com
Otherwise port my latest LineageOS 14.1 which has newest / latest patches from LineageOS included (Security Patch Level is from 2022).
Also all issues are fixed, media codec issues (Video Playback), FM Radio works, no App crashes, power profiles are included and GPS is working as well. Lot of crashes in background are fixed, which i found with logcat (improves the speed and battery lifetime).
ROM LineageOS 14.1 | [Custom]-[Updated] add the 02/27/2022 on Needrom