Open driedpampas opened 3 weeks ago
I also granted com.android.shell
root access but to no avail.
Notification shows for me. Tapping raises a segv in zygote64
type: crash
osVersion: google/oriole/oriole:14/AP1A.240505.004/2024051500:user/release-keys
uid: 2000 (u:r:shell:s0)
cmdline: zygote64
processUptime: 0s
signal: 11 (SIGSEGV), code 2 (SEGV_ACCERR), faultAddr d1e73168e000
threadName: m.android.shell
backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (__memcpy_aarch64_simd+44, pc 5c4ac)
/memfd:jit-zygisk-cache (deleted) (pc 1c57c)
I tried to open the manager through ksu and got this result: (check at the top of the logs)
And with the notification I only get this:
Update: Tried with Kitsune Mask and it only worked with built-in Zygisk.
The takeaway is that ZygiskNext does not currently work on Android 14 QPR2 (and above most likely)
I am experiencing this issue with Magisk latest commit on GrapheneOS built with this patch https://github.com/pixincreate/Magisk/commit/5b94840731b462897e0d00b4ce87b791497d230. From my understanding KitsuneMagisk is abandoned, so using it to solve this issue isn't exactly the best solution.
It doesn't work with either Magisk for me. Not with kitsune, not with normal Magisk. Both seem to suffer from the same issue.
I am experiencing this issue with Magisk latest commit on GrapheneOS built with this patch pixincreate/Magisk@5b94840. From my understanding KitsuneMagisk is abandoned, so using it to solve this issue isn't exactly the best solution.
I remember that there were issues with GrapheneOS and magisk but I do not use it so I don't deserve to comment on it.
It doesn't work with either Magisk for me. Not with kitsune, not with normal Magisk. Both seem to suffer from the same issue.
Did you use the built-in Zygisk or the Next module? also what Android version
I have tried more today. https://github.com/HuskyDG/magisk-files/issues/129#issuecomment-2081404931 Using this apk and native Zygisk, no luck. Using latest and patched magisk with both native and next, no luck. Android is GrapheneOS, 14
So I am messing around, and it seems to be a spotty issue affecting only some users. https://xdaforums.com/t/rom-14-official-stable-everestos-raven-19-04-2024.4667858/post-89490092 Here seems to be a user with the issue. This one I checked. A fresh install of DerpFest does not give me the crash. (20240527-1411; Device: Raphael) CRDroid (On raphael) also did not crash.
I have tried more today. https://github.com/HuskyDG/magisk-files/issues/129#issuecomment-2081404931 Using this apk and native Zygisk, no luck. Using latest and patched magisk with both native and next, no luck. Android is GrapheneOS, 14
GrapheneOS have applied a patch that broke zygisk or sth else iirc, so that's out of scope for this repo.
So I am messing around, and it seems to be a spotty issue affecting only some users. https://xdaforums.com/t/rom-14-official-stable-everestos-raven-19-04-2024.4667858/post-89490092 Here seems to be a user with the issue. This one I checked. A fresh install of DerpFest does not give me the crash. (20240527-1411; Device: Raphael) CRDroid (On raphael) also did not crash.
Are any of those 2 ROMS A14 QPR2 or greater?
GrapheneOS have applied a patch that broke zygisk or sth else iirc, so that's out of scope for this repo.
Zygisk on GrapheneOS works with this patch. https://github.com/pixincreate/Magisk so thats a non-issue.
Edit: The only thing to my knowledge which doesnt work on GOS is PIF due to the play services sandboxxing. (thats out of scope of this repo)
Did you tried to use another zygisk implementation, for example, Zygisk_mod? Now my device is Xiaomi 13 Pro, using ksu 11874 + zymod 226 + LSPmod 7295, all works fine
Did you tried to use another zygisk implementation, for example, Zygisk_mod? Now my device is Xiaomi 13 Pro, using ksu 11874 + zymod 226 + LSPmod 7295, all works fine
many thank, that latest ci build work for me on A10
I have Android 15 Beta 3 (stock rom) on a Pixel 7a, and Zygisk Next 1.0.5 worked for me. Now I switched to ReZygisk, which is a fork of Zygisk Next which is still open source, and upstream (original) Zygisk Next switched to a proprietary license since 0.9.2. This fork of LSPosed is working for me. Here is a screenshot:
Steps to reproduce
Expected behaviour
Everything to work.
Actual behaviour
The notification appears and when tapped shows a warning that is passed by clicking OK. The manager howver does not actually open. Subsequent taps only dismiss the notification shade but do not open the manager. I have installed the![337320306-e928c1a7-60c2-434b-9686-d99e973b138e](https://github.com/mywalkb/LSPosed_mod/assets/76390419/01d3a71e-ce31-4293-adba-986c3af9a5d2)
manager.apk
app from the zip but it reports that LSPosed is not installedXposed Module List
Magisk Module List
LSPosed version
7295
Android version
14
Magisk version
KSU 11838
Riru version
N/A
Version requirement
Logs
As specified above, the manager does not recognize LSPosed and the notification manager does not open so no logs could be attached at the time of writing.