Related
Issue fixed, thanks for all the feedback and report!!!
Hello, as many of you should be aware, the latest Magisk Manager (v4.2.5) crashes only on Samsung devices.
Here are the logs users submitted through Play Store:
Code:
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
at com.android.internal.policy.multiwindow.Docking.<init>(Docking.java)
at com.android.internal.policy.MultiPhoneWindow.<init>(MultiPhoneWindow.java)
at android.app.Activity.makeNewWindow(Activity.java)
at android.app.Activity.attach(Activity.java)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
As you might realize that according to the backtrace, non of them involves my code (which should start with com.topjohnwu.magisk.*), all of them are errors within internal and Zygote, and Samsung's multiwindow internal calls.
I am not able to identify where it crashes, and which part of the Magisk Manager code is breaking it, so of course without knowing why, I have no idea how to fix it. What makes the situation even worse is that I don't own any of the devices, so I cannot properly debug the issue.
This thread is for seeking help from users with a modern Samsung device, as I need more details.
Please describe when do the crash occurs (does splash screen even shows up?), and please upload a full logcat recording the FC.
Also, I'm looking for Samsung experts who are willing to assist me more in Samsung support for Magisk, as I never bought Sammy so I have little experience, but they seem to cause the most problems.
OT, I'm actually willing to buy a Sammy flagship, but I never buy outdated devices (older than 2 months = outdated IMO lol), so I might get the S8. The next Pixel device is already on my list, guess I'll have to spend all my tutor money on smartphones....
For Pixel support, I'll borrow my friend's Pixel XL for a couple of weeks to try things out, but this might not happen soon since school is quite busy.
@topjohnwu
it crash on opening the app, so unable to opeen the app it self
new root programs are unable to use root as it will crash when trying to enable root in the apps
old programs that use root already keep function
my device is
Samsng Galaxy s6 edge+ SM-G928F
Rom: Audax 13 Android MM 6.0.1
Kernel: Arter97
i don't know how to provide anymore info or how to use this logcat
so if you tell me how i can gather more info i do it with pleasure
From what I can tell it only happens in the versions after 4.1 so the problem is in one of the changes after 4.1. A Wild guesses that may or may not could help is that you could set a flag that tells the Samsung framework that it isn't compatible with multi window.
Gesendet von meinem SM-G925F mit Tapatalk
Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.
Didgeridoohan said:
Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.
Click to expand...
Click to collapse
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk
Hello topjohnwu, first of all I would like to thank you for you amazing work, really it made life simplier to many of us, so on behalf of everyone using Magisk I would like to say : THANK YOU.
To answer your question, when launching Magisk Manager, yes there's the splash screen before the crash.
I've attached a logcat to my post which shows "Magisk Manager v4.2.5" behaviour when crashing.
1 - Here are some informations about my device configuration :
- Device: Galaxy S7 Edge G935F (Exynos)
- Rom: Decent Ultralite 5.0 (Android 6.0.1) Based on TouchWiz (Stock Samsung)
- Kernel: SuperStock Kernel by Tkkg1994 (It's the stock Samsung kernel with only one change : SELINUX set to Permissive instead of Enforcing)
- Root: MagiskSU
- Recovery: TWRP v3.0.2.4
2 - Now some infos about my Magisk Config :
- Modules : Emoji One, Unified Hosts Adblock, Xposed Framework (SDK 23).
- Magisk Hide : Only Snapchat (which I don't even use lol)
- Settings Enabled : BusyBox, Magisk Hide, Systemless hosts
3 - Just in case, my modules of Xposed are :
- BootManager
- GalaxyXMod
- Greenify
- Unicon
- XInternalSD
That's it, if you need any more informations, I'm here.
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.
ken2802 said:
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Better to post it or a link here so topjohnwu doesn't have to search too much.
Didgeridoohan said:
Better to post it or a link here so topjohnwu doesn't have to search too much.
Click to expand...
Click to collapse
I made a new one.
https://drive.google.com/file/d/0B94u0_R6vixWbmtuUmFYQzhfWXM/view?usp=drivesdk
here is my logcat s7 edge android 6.0.1
I/Timeline( 5058): Timeline: Activity_launch_request id:com.topjohnwu.magisk time:68806449
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/MultiWindowPolicy( 4137): Gamemode - return 0, when calling identifyForegroundApp(com.topjohnwu.magisk)
V/WindowManager( 4137): addAppToken: AppWindowToken{d07f2779e token=Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594}}} to stack=1 task=594 at 0
D/ISSUE_DEBUG( 4137): InputChannelName : 9fd4a02 Starting com.topjohnwu.magisk
D/ActivityManager( 4137): Launching com.topjohnwu.magisk, updated priority
D/GameManagerService( 4137): NotifyRunnable. pkg: com.topjohnwu.magisk, type: 4, isMinimized: false, isTunableApp: false
E/AndroidRuntime(13507): Process: com.topjohnwu.magisk, PID: 13507
E/AndroidRuntime(13507): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.topjohnwu.magisk/com.topjohnwu.magisk.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
V/MARsPolicyManager( 4137): updatePackagesScore PackageInfo name -- com.topjohnwu.magisk
W/ActivityManager( 4137): Force finishing activity com.topjohnwu.magisk/.SplashActivity
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
V/WindowStateAnimator( 4137): Finishing drawing window Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
I/WindowManager( 4137): Screenshot max retries 4 of Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}} appWin=Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk} drawState=3
D/ISSUE_DEBUG( 4137): InputChannelName : 852d82d Application Error: com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/StatusBarManagerService( 4137): manageDisableList userId=0 what=0x0 pkg=Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=HAS_DRAWN
W/ActivityManager( 4137): Activity pause timeout for ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mServices
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mProviders
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mReceivers
I/ApplicationPackageManager( 4751): load=com.topjohnwu.magisk, bg=192-192, dr=192-192
W/ResourcesManager( 4751): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.android.systemui rsrc of package com.topjohnwu.magisk
I/ActivityManager( 4137): Process com.topjohnwu.magisk (pid 13507)(adj 9) has died(267,1161)
D/ActivityManager( 4137): isAutoRunBlockedApp:: com.topjohnwu.magisk, Auto Run ON
Click to expand...
Click to collapse
I'm gonna try to find out which build breaks it.
Does v4.1 works?
4.1 is the last that works on my s6 edge g925f
Gesendet von meinem SM-G925F mit Tapatalk
topjohnwu said:
I'm gonna try to find out which build breaks it.
Does v4.1 works?
Click to expand...
Click to collapse
Yes it works.
ok i hope ive done it right, i used catlog and saved log after crash magisk
hope its helpfull
see attachment
Samsung Galaxy S6 (SM-G920F) Alexis Rom 8.1, Arter97: Works
Samsung Galaxy S4 (GT-I9505) AICP 12.1: Works
Samsung Galaxy Tab S (SM-T800) IronRom 3.2: Doesn't Work
Samsung Galaxy S4 Mini (GT-I9195) AICP 12.1: Will check when battery is full again
Will try to get log cats from all and the crash occurs during the splash screen of Magisk Manager
edit: Added the log files dunno if they are properly for you.
@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:
aforss said:
here is my logcat s7 edge android 6.0.1
Click to expand...
Click to collapse
I would like to discuss with you about an issue on the S7 Edge, can you check you PMs ?
I don't want to pollute this thread.
Thank You
apc said:
@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:
Click to expand...
Click to collapse
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)
topjohnwu said:
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)
Click to expand...
Click to collapse
It works
No FCs
Works perfectly now
Working great (again) on my Galaxy S5 SM-G900F. Earlier (before MagiskSU) I had removed root to pass SN because Magisk had CTS profile mismatch error. But now SN is passed and I couldn't be happier. Thank you so much topjohnwu . Running RR-N rom 11 Feb 17 build with stock RR kernel, twrp 3.0.2-2
lahceneamine said:
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.
Click to expand...
Click to collapse
@topjohnwu
I've also noticed slow bootup times since Magisk v11.1 on a Samsung Galaxy Note 3 (stock android 5.0). It hangs at the first screen you see when you turn on the phone (before the Samsung logo screen). It eventually boots up and seems to work fine, but I didn't see this delay on earlier versions of Magisk.
Edit:
I'm using MagiskSU with no extra modules.
Just got a T280 - would like to get Nougat on it. I saw @jedld did awesome work on T285 and @_mone did with TWRP, however, I was hoping to create a thread to consolidate any ongoing efforts for T280 in one place, and see where I could help.
This is what I know of the state of the T280 development.
TWRP and root has been available for the T280 for some time, almost at the same time the T285 version has. There is no non-stock based rom available yet.
Custom T280 kernel here courtesy of @_mone, there are reports that it works with an updated T280 stock firmware.
Before flashing a generated boot.img note that it requires special headers for the T280 here: https://forum.xda-developers.com/showpost.php?p=68843058&postcount=81. There is at least one developer in this forum that is looking to make this process easier.
Assumming this works with the T280 stock firmware, the steps that I see are the following:
1. Patch the N and M related linux kernel patches to the T280 kernel http://jeffvanderstoep.blogspot.com/2016/05/selinux-kernel-patches-for-android-n.html. Update the arm defconfig to the latest recommended by android.
2. Create a lineage device tree, you can use my gtexslte manifest as a starting point https://github.com/jedld/android.git. Probably just need to take out the RIL related modules.
awesome - i'll give this a go.. right now I'm just testing building samsung's stock opensource kernel.
It's people like you that make me love xda. Thanks!
Downloading source code.....
@jedld I downloading lineage14.1 src and gtexslte kernel/device trees
How to create gtexswifi device tree based gtexslte?
tdukazudon said:
@jedld I downloading lineage14.1 src and gtexslte kernel/device trees
How to create gtexswifi device tree based gtexslte?
Click to expand...
Click to collapse
You can start by renaming gtexslte to gtexswifi, I believe flash partitions sizes and mountpoints are about the same for both SM-T285 and SM-T280 so you don't need to change much. You probably need to remove phone related configs. You also need to use the SM-T280 kernel also. I don't know if there are other hardware differences from the T280 and T285 (gps?) If this is your first time doing any sort of porting, this can be a daunting task, so I suggest you try to learn how to extract the stock boot and system images, modify some files and then flash it back as an exercise. There might already be a gtexswifi device tree in progress somewhere, I suggest that you contact those devs or probably set up an irc channel to coordinate your efforts.
@jedld - I'm confused - for the M/N Patches to the kernel, it seems like 2 sets of patches undo each other, namely:
Revert "SELinux: per-command whitelisting of ioctls" - https://android-review.googlesource.com/162275
selinux: extended permissions for ioctls - https://android-review.googlesource.com/162279
and
Revert "security: lsm_audit: add ioctl specific auditing" - https://android-review.googlesource.com/162276
security: add ioctl specific auditing to lsm_audit - https://android-review.googlesource.com/162278
What'd you do for those?
chiefwigms said:
@jedld - I'm confused - for the M/N Patches to the kernel, it seems like 2 sets of patches undo each other, namely:
Revert "SELinux: per-command whitelisting of ioctls" - https://android-review.googlesource.com/162275
selinux: extended permissions for ioctls - https://android-review.googlesource.com/162279
and
Revert "security: lsm_audit: add ioctl specific auditing" - https://android-review.googlesource.com/162276
security: add ioctl specific auditing to lsm_audit - https://android-review.googlesource.com/162278
What'd you do for those?
Click to expand...
Click to collapse
I ignored the reverts at first. I can't remember if it worked after that. Though I ended up just doing a straight diff with the selinux modules based on the aosp 3.10.y kernel sources and just merging them.
jedld said:
I ignored the reverts at first. I can't remember if it worked after that. Though I ended up just doing a straight diff with the selinux modules based on the aosp 3.10.y kernel sources and just merging them.
Click to expand...
Click to collapse
Sound good - i'll just diff w/ your repo Thx!
@jedld
This build error happened.Do you have solution?
hardware/sprd/libmemion/MemoryHeapIon.cpp:614:30: error: variable has incomplete type 'struct ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:614:16: note: forward declaration of 'ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:618:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_MAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_MAP'?
custom_data.cmd = ION_SPRD_CUSTOM_MAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_MAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:54:2: note: 'ION_SPRD_CUSTOM_MAP' declared here
ION_SPRD_CUSTOM_MAP,
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:638:32: error: variable has incomplete type 'struct ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:638:16: note: forward declaration of 'ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:642:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_UNMAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_UNMAP'?
custom_data.cmd = ION_SPRD_CUSTOM_UNMAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_UNMAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:55:2: note: 'ION_SPRD_CUSTOM_UNMAP' declared here
ION_SPRD_CUSTOM_UNMAP,
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:663:30: error: variable has incomplete type 'struct ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:663:16: note: forward declaration of 'ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:667:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_MAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_MAP'?
custom_data.cmd = ION_SPRD_CUSTOM_MAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_MAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:54:2: note: 'ION_SPRD_CUSTOM_MAP' declared here
ION_SPRD_CUSTOM_MAP,
^
Import includes file: /home/aletheia/smt280/out/target/product/gtexswifi/obj/SHARED_LIBRARIES/libRSCpuRef_intermediates/import_includes
hardware/sprd/libmemion/MemoryHeapIon.cpp:690:32: error: variable has incomplete type 'struct ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:690:16: note: forward declaration of 'ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:694:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_UNMAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_UNMAP'?
custom_data.cmd = ION_SPRD_CUSTOM_UNMAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_UNMAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:55:2: note: 'ION_SPRD_CUSTOM_UNMAP' declared here
ION_SPRD_CUSTOM_UNMAP,
^
8 errors generated.
tdukazudon said:
@jedld
This build error happened.Do you have solution?
hardware/sprd/libmemion/MemoryHeapIon.cpp:614:30: error: variable has incomplete type 'struct ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:614:16: note: forward declaration of 'ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:618:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_MAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_MAP'?
custom_data.cmd = ION_SPRD_CUSTOM_MAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_MAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:54:2: note: 'ION_SPRD_CUSTOM_MAP' declared here
ION_SPRD_CUSTOM_MAP,
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:638:32: error: variable has incomplete type 'struct ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:638:16: note: forward declaration of 'ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:642:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_UNMAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_UNMAP'?
custom_data.cmd = ION_SPRD_CUSTOM_UNMAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_UNMAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:55:2: note: 'ION_SPRD_CUSTOM_UNMAP' declared here
ION_SPRD_CUSTOM_UNMAP,
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:663:30: error: variable has incomplete type 'struct ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:663:16: note: forward declaration of 'ion_kmap_data'
struct ion_kmap_data kmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:667:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_MAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_MAP'?
custom_data.cmd = ION_SPRD_CUSTOM_MAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_MAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:54:2: note: 'ION_SPRD_CUSTOM_MAP' declared here
ION_SPRD_CUSTOM_MAP,
^
Import includes file: /home/aletheia/smt280/out/target/product/gtexswifi/obj/SHARED_LIBRARIES/libRSCpuRef_intermediates/import_includes
hardware/sprd/libmemion/MemoryHeapIon.cpp:690:32: error: variable has incomplete type 'struct ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:690:16: note: forward declaration of 'ion_kunmap_data'
struct ion_kunmap_data kunmap_data;
^
hardware/sprd/libmemion/MemoryHeapIon.cpp:694:27: error: use of undeclared identifier 'ION_SPRD_CUSTOM_UNMAP_KERNEL'; did you mean 'ION_SPRD_CUSTOM_UNMAP'?
custom_data.cmd = ION_SPRD_CUSTOM_UNMAP_KERNEL;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
ION_SPRD_CUSTOM_UNMAP
/home/aletheia/smt280/out/target/product/gtexswifi/obj/KERNEL_OBJ/usr/include/video/ion_sprd.h:55:2: note: 'ION_SPRD_CUSTOM_UNMAP' declared here
ION_SPRD_CUSTOM_UNMAP,
^
8 errors generated.
Click to expand...
Click to collapse
You need so sync up the kernel ion drivers and include files with the one used by the gtexslte
Pardon my stupidity, but from your post here with the custom t280 header, how would I go about modifying the degas-mkbootimg command with the permissive kernel that I have?
chiefwigms said:
Pardon my stupidity, but from your post here with the custom t280 header, how would I go about modifying the degas-mkbootimg command with the permissive kernel that I have?
Click to expand...
Click to collapse
best approach I believe would be to leave mkbootimg as is and just create another commandline utility that takes an exisitng boot.img and prepend the T280 header to it. I'll try to create a C program that does it if I have time.
jedld said:
best approach I believe would be to leave mkbootimg as is and just create another commandline utility that takes an exisitng boot.img and prepend the T280 header to it. I'll try to create a C program that does it if I have time.
Click to expand...
Click to collapse
I'll clone your repo & add something to repack the t280 boot.img. Sorry - had to read through that post a few times - didn't realize the seandroid header was at the end of the file..
Kernel question : the zImage I compile is ~ 5 megs (Image is ~12) - when i unpack the stock boot.img (or the ones that @_mone made), they're around ~10 megs. Any ideas?
chiefwigms said:
I'll clone your repo & add something to repack the t280 boot.img. Sorry - had to read through that post a few times - didn't realize the seandroid header was at the end of the file..
Kernel question : the zImage I compile is ~ 5 megs (Image is ~12) - when i unpack the stock boot.img (or the ones that @_mone made), they're around ~10 megs. Any ideas?
Click to expand...
Click to collapse
boot.img also contains the ramdisk aside from the compressed kernel image.
jedld said:
best approach I believe would be to leave mkbootimg as is and just create another commandline utility that takes an exisitng boot.img and prepend the T280 header to it. I'll try to create a C program that does it if I have time.
Click to expand...
Click to collapse
jedld said:
boot.img also contains the ramdisk aside from the compressed kernel image.
Click to expand...
Click to collapse
Right, but I'm talking about zImage.. doesn't that remain untouched?
chiefwigms said:
Right, but I'm talking about zImage.. doesn't that remain untouched?
Click to expand...
Click to collapse
If you are comparing to stock size, samsung might have less flags enabled when they built their kernel as compared to the sources available to us so it could be smaller
jedld said:
If you are comparing to stock size, samsung might have less flags enabled when they built their kernel as compared to the sources available to us so it could be smaller
Click to expand...
Click to collapse
I don't know - I merged most of your def config to mine, and rebuilt stock, _mone, the modified one ive been working on, and your performance_2 branch for the t285 - all the zImages are around 5 MB :
[email protected]:/gtaba# ls -la kernel_samsung_gtexslte/arch/arm/boot/*Image*
-rwxr-xr-x 1 root root 12788984 Aug 26 23:06 kernel_samsung_gtexslte/arch/arm/boot/Image
-rwxr-xr-x 1 root root 5622664 Aug 26 23:06 kernel_samsung_gtexslte/arch/arm/boot/zImage
[email protected]:/gtaba# ls -la android_kernel_samsung_gtexswifi/arch/arm/boot/*Image*
-rwxr-xr-x 1 root root 12516984 Aug 25 21:05 android_kernel_samsung_gtexswifi/arch/arm/boot/Image
-rwxr-xr-x 1 root root 5488912 Aug 25 21:05 android_kernel_samsung_gtexswifi/arch/arm/boot/zImage
chiefwigms said:
I don't know - I merged most of your def config to mine, and rebuilt stock, _mone, the modified one ive been working on, and your performance_2 branch for the t285 - all the zImages are around 5 MB :
[email protected]:/gtaba# ls -la kernel_samsung_gtexslte/arch/arm/boot/*Image*
-rwxr-xr-x 1 root root 12788984 Aug 26 23:06 kernel_samsung_gtexslte/arch/arm/boot/Image
-rwxr-xr-x 1 root root 5622664 Aug 26 23:06 kernel_samsung_gtexslte/arch/arm/boot/zImage
[email protected]:/gtaba# ls -la android_kernel_samsung_gtexswifi/arch/arm/boot/*Image*
-rwxr-xr-x 1 root root 12516984 Aug 25 21:05 android_kernel_samsung_gtexswifi/arch/arm/boot/Image
-rwxr-xr-x 1 root root 5488912 Aug 25 21:05 android_kernel_samsung_gtexswifi/arch/arm/boot/zImage
Click to expand...
Click to collapse
For the gtexslte the size is about similar as well:
[email protected]:~/android-work/kernel/samsung/gtexslte/arch$ ls -la arm/boot/*Image*
-rwxrwxr-x 1 jedld jedld 12672968 Aug 28 07:00 arm/boot/Image
-rwxrwxr-x 1 jedld jedld 5566008 Aug 28 07:00 arm/boot/zImage
jedld said:
For the gtexslte the size is about similar as well:
[email protected]:~/android-work/kernel/samsung/gtexslte/arch$ ls -la arm/boot/*Image*
-rwxrwxr-x 1 jedld jedld 12672968 Aug 28 07:00 arm/boot/Image
-rwxrwxr-x 1 jedld jedld 5566008 Aug 28 07:00 arm/boot/zImage
Click to expand...
Click to collapse
Alright.. I'll try that.. and just to make sure, you repack zImage not image right? Just curious why when I unpack _mone it's 2x the size
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.9.65 on OxygenOS 5.x and 4.9.106 on OxygenOS 9.0/Open Beta while the current version upstream is 4.9.135 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op6
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
God damn ! You here ! I'm feeling lucky ! Nexus 6P, Oneplus 5 and now Oneplus 6 damn :')
Thanks for your hard work !
Yea boiii
Imma flashing it rn <3
Thanks
Thank you @nathanchance for your efforts. Much needed for the new 4.9 kernel.
Nice one man!!
Sent from my OnePlus6 using XDA Labs
Who got 1 star ? really ?
btw, @nathanchance you have 5 star from me, good work ,and it is nice to see you here.
As always, good job with informing users , waiting for your kernel
Thanks a lot! :good:
marko94 said:
Who got 1 star ? really ?
btw, @nathanchance you have 5 star from me, good work ,and it is nice to see you here.
As always, good job with informing users , waiting for your kernel
Click to expand...
Click to collapse
Ratings mean absolutely nothing and I feel sorry for anyone who puts any stock in them but thanks
My kernel should be out tonight.
Hey, can you explain me we can install upper kernel version on the last firmware? And how to do it if we can?
Thank and good thread!
Devices : OnePlus 6
4.9.108 has been merged in.
black_file said:
Hey, can you explain me we can install upper kernel version on the last firmware? And how to do it if we can?
Thank and good thread!
Devices : OnePlus 6
Click to expand...
Click to collapse
Flash a kernel that has these changes. At this moment, I am the only one who has done so: https://forum.xda-developers.com/oneplus-6/development/op6-flash-kernel-1-00-t3801652
4.9.109 has been merged in.
Could you please provide instructions on how to flash a kernel?
Earlier, I could just extract the boot.img file from one of the ROM images and then extract+repackage with my built Image.gz-dtb using mkbootimg.
The newer Android ROMs seem to only contain a package.bin file instead.
phenoxis said:
Could you please provide instructions on how to flash a kernel?
Earlier, I could just extract the boot.img file from one of the ROM images and then extract+repackage with my built Image.gz-dtb using mkbootimg.
The newer Android ROMs seem to only contain a package.bin file instead.
Click to expand...
Click to collapse
Easiest way is to temporarily boot TWRP on stock then run
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot$(getprop ro.boot.slot_suffix) of=/tmp/boot.img
adb pull /tmp/boot.img .
then just unpack like you have before.
Sent from my Pixel 2 XL using XDA Labs
nathanchance said:
Easiest way is to temporarily boot TWRP on stock then run
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot$(getprop ro.boot.slot_suffix) of=/tmp/boot.img
adb pull /tmp/boot.img .
then just unpack like you have before.
Click to expand...
Click to collapse
I followed your advice with both the original OnePlus 6 kernel source and your android-linux-stable repo. I was able to build the kernel, repack it and flash it, but with both repos, the device is sitting with the bootanimation for about half hour or so. Do both repositories need additional work before it can boot?
I packaged boot.img with the following command:
Code:
mkbootimg --base 0 --pagesize 4096 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000
--second_offset 0x00f00000 --tags_offset 0x00000100
--cmdline 'androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000
msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 service_locator.enable=1 swiotlb=2048
androidboot.configfs=true androidboot.usbcontroller=a600000.dwc3 buildvariant=user' --kernel kernel --ramdisk ramdisk -o boot_1.img
phenoxis said:
I followed your advice with both the original OnePlus 6 kernel source and your android-linux-stable repo. I was able to build the kernel, repack it and flash it, but with both repos, the device is sitting with the bootanimation for about half hour or so. Do both repositories need additional work before it can boot?
I packaged boot.img with the following command:
Code:
mkbootimg --base 0 --pagesize 4096 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000
--second_offset 0x00f00000 --tags_offset 0x00000100
--cmdline 'androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000
msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 service_locator.enable=1 swiotlb=2048
androidboot.configfs=true androidboot.usbcontroller=a600000.dwc3 buildvariant=user' --kernel kernel --ramdisk ramdisk -o boot_1.img
Click to expand...
Click to collapse
They shouldn't... Did you use Image.gz-dtb as the kernel?
nathanchance said:
They shouldn't... Did you use Image.gz-dtb as the kernel?
Click to expand...
Click to collapse
Yes, I'm certain I did.
My full script is:
Code:
unmkbootimg --kernel kernel --ramdisk ramdisk -i boot.img.bk #This is what I obtained from your dd if=... of=/tmp/boot.img command
cp /android/kernel/opo6-stable/arch/arm64/boot/Image.gz-dtb kernel
mkbootimg --base 0 --pagesize 4096 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000
--second_offset 0x00f00000 --tags_offset 0x00000100
--cmdline 'androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000
msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 service_locator.enable=1 swiotlb=2048
androidboot.configfs=true androidboot.usbcontroller=a600000.dwc3 buildvariant=user'
--kernel kernel --ramdisk ramdisk -o boot_1.img
fastboot flash boot boot_1.img
phenoxis said:
Yes, I'm certain I did.
My full script is:
Code:
unmkbootimg --kernel kernel --ramdisk ramdisk -i boot.img.bk #This is what I obtained from your dd if=... of=/tmp/boot.img command
cp /android/kernel/opo6-stable/arch/arm64/boot/Image.gz-dtb kernel
mkbootimg --base 0 --pagesize 4096 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000
--second_offset 0x00f00000 --tags_offset 0x00000100
--cmdline 'androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000
msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 service_locator.enable=1 swiotlb=2048
androidboot.configfs=true androidboot.usbcontroller=a600000.dwc3 buildvariant=user'
--kernel kernel --ramdisk ramdisk -o boot_1.img
fastboot flash boot boot_1.img
Click to expand...
Click to collapse
Try using this boot image: https://nathanchance.me/downloads/kernels/op6/stock/oos-5.1.8-boot.img
You may also check out Android Image Kitchen too, that's what I used before TWRP.
First, thanks a ton for taking the time to help me out.
I tried unpacking/repacking with your boot.img file, and that didn't work either. However, your boot.img itself works just fine.
I just realized that my build produces a ton of warnings.
Code:
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
...
This is probably why my kernels are failing to boot. I'm essentially following the instructions you laid out on the github issue for this kernel.
Code:
export ARCH=arm64
export CROSS_COMPILE=/android/projects/cross-compile/aarch64-linux-android-4.9/bin/aarch64-linux-android-
make O=out sdm845-perf_defconfig
./scripts/config --file ./out/.config -e BUILD_ARM64_DT_OVERLAY
make O=out olddefconfig
make O=out DTC_EXT=dtc -j16
Following the comments in that issue, I'm running archlinux with the following software versions:
gcc
Code:
[email protected]:/android/kernel/opo6-stable$ gcc --version
gcc (GCC) 8.1.1 20180531
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
dtc
Code:
[email protected]:/android/kernel/opo6-stable$ dtc --version
Version: DTC 1.4.6
phenoxis said:
First, thanks a ton for taking the time to help me out.
I tried unpacking/repacking with your boot.img file, and that didn't work either. However, your boot.img itself works just fine.
I just realized that my build produces a ton of warnings.
Code:
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/qcom,[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
arch/arm64/boot/dts/qcom/enchilada-evb-overlay.dtbo: Warning (reg_format): "reg" property in /[email protected]/__overlay__/[email protected] has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
...
This is probably why my kernels are failing to boot. I'm essentially following the instructions you laid out on the github issue for this kernel.
Code:
export ARCH=arm64
export CROSS_COMPILE=/android/projects/cross-compile/aarch64-linux-android-4.9/bin/aarch64-linux-android-
make O=out sdm845-perf_defconfig
./scripts/config --file ./out/.config -e BUILD_ARM64_DT_OVERLAY
make O=out olddefconfig
make O=out DTC_EXT=dtc -j16
Following the comments in that issue, I'm running archlinux with the following software versions:
gcc
Code:
[email protected]:/android/kernel/opo6-stable$ gcc --version
gcc (GCC) 8.1.1 20180531
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
dtc
Code:
[email protected]:/android/kernel/opo6-stable$ dtc --version
Version: DTC 1.4.6
Click to expand...
Click to collapse
That's normal, I've hidden all of the warnings.
https://github.com/nathanchance/op6/commits/1d0f0ea36c0814efa36ef8b5c0c1ad9cb74cfe81
Those were the commits I used for my first boot. There is nothing in there that should be necessary to boot, just to make certain things work.
4.9.110 has been merged in.
Hello everyone,
Grim Fandango Remastered exits immediately when Magisk is installed.
Its working fine with SuperSU.
I am running LineageOS 14.1 on a Xperia Z4 Tablet and tried Magisk 16.0/16.3/16.4.
BTW: Netflix and Prime Video working fine despite CTS Profile failure. Basic integrity check is okay.
Any ideas?
Greetings,
Medizinmann
Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...
Didgeridoohan said:
Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...
Click to expand...
Click to collapse
Here is the logcat.....
Any help appreciated!
Greetings,
Medizinmann
Didgeridoohan said:
Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...
Click to expand...
Click to collapse
After analyzing the logcat i found the following...
Code:
[ 07-05 20:34:59.404 423: 428 E/Vold ]
ASEC loop device creation failed for /storage/emulated/0/Android/obb/com.doublefine.grimfandangoremastered/main.150.com.doublefine.grimfandangoremastered.obb (Permission denied)
[ 07-05 20:34:59.404 423: 428 W/Vold ]
Returning OperationFailed - no handler for errno 13
[ 07-05 20:34:59.404 1578: 2362 D/VoldConnector ]
RCV <- {400 21 obb operation failed (Permission denied)}
[ 07-05 20:34:59.390 428: 428 W/vold ]
type=1400 audit(0.0:415): avc: denied { getattr } for path="/data/adb/magisk.img" dev="mmcblk0p43" ino=508522 scontext=u:r:vold:s0 tcontext=u:object_r:adb_data_file:s0 tclass=file permissive=0
The problem seems to be, that the app can’t access their .obb-Files. But why is that?
Greetings,
Medizinmann
Medizinmann said:
The problem seems to be, that the app can’t access their .obb-Files. But why is that?
Click to expand...
Click to collapse
Yes, I saw that as well... And there's been similar reports for other apps.
It's because Magisk is using the loop device, and this seems to conflict with some apps. It's under investigation...
HI
does anybody know how to get rid of this error:
Code:
1|ASUS_I006D:/sdcard/Download # id
uid=0(root) gid=0(root) groups=0(root) context=u:r:magisk:s0
ASUS_I006D:/sdcard/Download # pm install $PWD/SMMI_TEST.apk
avc: denied { read } for scontext=u:r:system_server:s0 tcontext=u:object_r:fuse:s0 tclass=file permissive=1
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.asus.atd.smmitest has no signatures that match those in shared user android.uid.system; ignoring!]
1|ASUS_I006D:/sdcard/Download #
SMMI_TEST.apk is an app from the original Android for the ASUS Zenfone 8 and I want install it in OmniROM 12 .
regards
Bernd
Update 15.06.2022
Looks like this error can only be fixed by signing the app with the private key used in the running ROM
Update 22.06.2022
The test app works fine on a custom ROM if signed with the private key for that ROM (tested with a self compiled version of OmniROM 12)
Update 25.06.2022
"Resolved" by compiling my own CustomROM -- see How to use the Hardware Test App from ASUS on a Zenfone running a CustomROM
from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest
gothta said:
from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest
Click to expand...
Click to collapse
... without that permission the app can be executed but can not do anything anymore