Apart from magisk I have also installed xposed framework. All banking apps are running but, the Raiffeisen app. I'm actually even not sure if it has to do with root. The app crashes immediately after it gets started.
Some suggestions?
I tried right now with Magisk Manager 20.4 (20400) and Raiffeisen app (Romania) and the Raiffeisen app works if you Hide Magisk Manager ( în Magisk manager Settings).
That means Raiffeisen Apps are searching for Magisk Manager. I think.
LE: Smart Mobile works. RaiPay doesn't Work.
xposed will always allow root to be detected.
Arak0n said:
xposed will always allow root to be detected.
Click to expand...
Click to collapse
Yes, but I installed many banking app which does not accept root. They all work as long I keep them in the magisk hide list.
XtraWater said:
Yes, but I installed many banking app which does not accept root. They all work as long I keep them in the magisk hide list.
Click to expand...
Click to collapse
That simply means that those other apps do not look for Xposed, while the app in question possibly does. Might also look for USB debuggin and/or Developer options being enabled, etc, etc...
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
XtraWater said:
All banking apps are running
Click to expand...
Click to collapse
& btw., not the best idea to use important data on a custom ROM.
I have the same problem with this raiffeisen app. Did you find any solutino for that?
Didgeridoohan said:
That simply means that those other apps do not look for Xposed, while the app in question possibly does. Might also look for USB debuggin and/or Developer options being enabled, etc, etc...
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
I can confirm the Raiffeisen banking app probably fails because of something else. There is no Xposed on my system, both safetyNet checks pass, Magisk Manager is also hidden. I have tried to activate MagiskHide to Phone-related apks as well since the app requests call management permissions, but it didn't help. I've also chmodded /proc/net/unix to 000. I tried disabling USB debugging and developer mode altogether.
What's interesting is that I think the app looks for the native camera app on my Mi A1 which was not present initially, but then I've created a Magisk module which placed the original camera apk at the correct location which did not help either. Decompiling the source revealed that it uses Vasco's technology for authentication which is also used by com.EquitasDigipass and interestingly enough it looks like it tries to do something with its resources too.
Code:
06-27 13:44:39.848 3219 3338 I ActivityManager: Start proc 17693:com.guidance.android.apps.raiffeisen.banklet/u0a192 for activity com.guidance.android.apps.raiffeisen.banklet/.ui.InitActivity
06-27 13:44:39.860 17693 17693 E ffeisen.bankle: Not starting debugger since process cannot load the jdwp agent.
06-27 13:44:39.866 1955 2382 I Magisk : proc_monitor: [com.guidance.android.apps.raiffeisen.banklet] PID=[17693] UID=[10192]
06-27 13:44:39.905 17693 17693 I ffeisen.bankle: The ClassLoaderContext is a special shared library.
06-27 13:44:40.305 17693 17693 D FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
06-27 13:44:40.306 17693 17693 D FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
06-27 13:44:40.306 17693 17693 I FirebaseInitProvider: FirebaseApp initialization successful
06-27 13:44:40.373 17693 17717 I FA : App measurement is starting up, version: 15300
06-27 13:44:40.373 17693 17717 I FA : To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
06-27 13:44:40.374 17693 17717 I FA : To enable faster debug mode event logging run:
06-27 13:44:40.374 17693 17717 I FA : adb shell setprop debug.firebase.analytics.app com.guidance.android.apps.raiffeisen.banklet
06-27 13:44:40.376 17693 17693 W : type=1400 audit(0.0:1832): avc: denied { read } for name="/" dev="rootfs" ino=1 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
06-27 13:44:40.513 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.alibaba.aliexpresshd-YKwyZRC-LJzYtvxBjpz3wQ==/base.apk' is compressed.
06-27 13:44:40.524 17693 17693 D OpenGLRenderer: Skia GL Pipeline
06-27 13:44:40.581 17693 17727 I Adreno : QUALCOMM build : 2df12b3, I07da2d9908
06-27 13:44:40.581 17693 17727 I Adreno : Build Date : 10/04/18
06-27 13:44:40.581 17693 17727 I Adreno : OpenGL ES Shader Compiler Version: EV031.25.03.01
06-27 13:44:40.581 17693 17727 I Adreno : Local Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Remote Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Remote Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Reconstruct Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Build Config : S L 6.0.7 AArch32
06-27 13:44:40.581 17693 17727 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8953.so from current namespace instead of sphal namespace.
06-27 13:44:40.602 17693 17727 I Adreno : PFP: 0x005ff087, ME: 0x005ff063
06-27 13:44:40.608 17693 17727 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
06-27 13:44:40.608 17693 17727 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
06-27 13:44:40.610 17693 17727 I OpenGLRenderer: Initialized EGL, version 1.4
06-27 13:44:40.610 17693 17727 D OpenGLRenderer: Swap behavior 2
06-27 13:44:40.628 17693 17727 D vndksupport: Loading /vendor/lib/hw/[email protected] from current namespace instead of sphal namespace.
06-27 13:44:40.628 17693 17727 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8953.so from current namespace instead of sphal namespace.
06-27 13:44:40.792 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.matteljv.uno-lwQ-HHADZe0GUWmTYstAvw==/base.apk' is compressed.
06-27 13:44:40.833 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.instagram.android-KGDMA_EyAMkGiZ0sDc7ZTA==/base.apk' is compressed.
06-27 13:44:41.191 17693 17722 W ziparchive: Unable to open '/system/priv-app/MiuiCamera/MiuiCamera.apk': No such file or directory
06-27 13:44:41.191 17693 17722 E ffeisen.bankle: Failed to open APK '/system/priv-app/MiuiCamera/MiuiCamera.apk' I/O error
06-27 13:44:41.192 17693 17722 E ResourcesManager: failed to add asset path /system/priv-app/MiuiCamera/MiuiCamera.apk
06-27 13:44:41.192 17693 17722 W PackageManager: Failure retrieving resources for com.android.camera
06-27 13:44:41.408 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.EquitasDigipass-hveat1DdrahqrzU15PUnjg==/base.apk' is compressed.
06-27 13:44:41.526 17693 17693 W : type=1400 audit(0.0:2011): avc: denied { read } for name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=0
06-27 13:44:41.578 17693 17717 W ffeisen.bankle: Long monitor contention with owner firebase-iid-executor (17721) at long com.android.org.conscrypt.NativeCrypto.RSA_generate_key_ex(int, byte[])(NativeCrypto.java:-2) waiters=0 in com.google.firebase.iid.aa com.google.firebase.iid.z.a(java.lang.String, java.lang.String, java.lang.String) for 1.181s
06-27 13:44:41.615 17693 17717 I FA : Tag Manager is not found and thus will not be used
06-27 13:44:45.480 17693 17693 I ffeisen.bankle: System.exit called, status: 0
06-27 13:44:45.480 17693 17693 I AndroidRuntime: VM exiting with result code 0, cleanup skipped.
06-27 13:44:45.545 3219 4238 I ActivityManager: Process com.guidance.android.apps.raiffeisen.banklet (pid 17693) has died: fore TOP
06-27 13:44:45.546 3219 3340 W libprocessgroup: kill(-17693, 9) failed: No such process
06-27 13:44:45.549 2426 2426 I Zygote : Process 17693 exited cleanly (0)
06-27 13:44:45.552 3219 3340 W libprocessgroup: kill(-17693, 9) failed: No such process
06-27 13:44:45.552 3219 3340 I libprocessgroup: Successfully killed process cgroup uid 10192 pid 17693 in 6ms
06-27 13:44:45.558 3219 3393 W ActivityManager: setHasOverlayUi called on unknown pid: 17693
hi guys,
So basically I came here to find a solution for this same problem, I have installed just the Magisk app, and try to hide myRaiffeisen app the root permission and the Magisk app itself and so far for me has no succeed, but after updated to magisk 201.1 (20100) version I give it a try and after clear cache and app data of the bank app at last it going o work,
so if this problem still persist the new version should able to handle the situation
cheers
svi_system said:
hi guys,
So basically I came here to find a solution for this same problem, I have installed just the Magisk app, and try to hide myRaiffeisen app the root permission and the Magisk app itself and so far for me has no succeed, but after updated to magisk 201.1 (20100) version I give it a try and after clear cache and app data of the bank app at last it going o work,
so if this problem still persist the new version should able to handle the situation
cheers
Click to expand...
Click to collapse
It's not working to me even after updating magisk...
danny3458 said:
It's not working to me even after updating magisk...
Click to expand...
Click to collapse
So if I understand you correctly, on your phone has installed magisk with 201.1 or newer version and in the magisk manager you also marked the raiffeisen app to hide root capabilities from it?
I used this method several times on different devices with success, so I hope you able to achieve it as well
I just flashed the newest LineageOS 17.1 build onto my Pixel 3. The Austrian version of the Raiffesein App "Mein Elba" immediately forwarded me to a website where they made some security claims regarding custom roms.
Fortunately installing Magisk has solved these issues immediately. No additional work had been required.
I'm running LineageOS 17.1 (build from the 5th of march by razorloves together with magisk 20.3.
When I run the SafenetCheck in the Magisk Manager it shows "basicIntegrity: true, ctsProfile: false".
Best Regards,
Michael
::Michael:: said:
I just flashed the newest LineageOS 17.1 build onto my Pixel 3. The Austrian version of the Raiffesein App "Mein Elba" immediately forwarded me to a website where they made some security claims regarding custom roms.
Fortunately installing Magisk has solved these issues immediately. No additional work had been required.
I'm running LineageOS 17.1 (build from the 5th of march by razorloves together with magisk 20.3.
When I run the SafenetCheck in the Magisk Manager it shows "basicIntegrity: true, ctsProfile: false".
Best Regards,
Michael
Click to expand...
Click to collapse
From Mr. Magisk himself. https://mobile.twitter.com/topjohnwu/status/1237656703929180160?s=19
Do you block Google Play Wakelocks/Analytics (@MeggaMortY) ? This is crashing the Sixt app for example. I cannot block them in xXx rom.
I have never rotted my Galaxy S8 before and it still shows "rooted device detected" I also tried to disable OEM unlock and even the whole developer mode but it still shows the same message.
Sent from my SM-G950F using Tapatalk
<deleted>
badmania98 said:
I tried right now with Magisk Manager 20.4 (20400) and Raiffeisen app (Romania) and the Raiffeisen app works if you Hide Magisk Manager ( în Magisk manager Settings).
That means Raiffeisen Apps are searching for Magisk Manager. I think.
LE: Smart Mobile works. RaiPay doesn't Work.
Click to expand...
Click to collapse
life saver
Related
Upgraded to Magisk v15.0 and now when I run SafetyNet check I receive an API Error.
I am running Android 8.1 on Nexus 6P and have uninstalled Magisk using the Uninstaller and re-installed and still receive the same API error.
I've searched and read through quite a few threads and haven't come up with any fixes. Closest thing I found was a fix on the OnePlus forum.
Attached is a screenshot of the Magisk screen for reference.
Any help would be greatly appreciated.
Thanks in advance!
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Sent from my A0001 using Tapatalk
I had the same problem. I solved it by doing a clean install of Magisk (completely uninstall previous version, install new version).
J_M_V_S said:
I had the same problem. I solved it by doing a clean install of Magisk (completely uninstall previous version, install new version).
Click to expand...
Click to collapse
I tried this before and still received the error.
iPusak Gaoq™ said:
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
That worked! Thanks so much for the quick fix.
mandhir said:
I tried this before and still received the error.
That worked! Thanks so much for the quick fix.
Click to expand...
Click to collapse
Worked for me too!! Thanks a lot!
SafetyNet not passed
Samsung Galaxy S5 G-900F latest magisk 15.1 and magisk manager 5.5.2 SafetyNet not passed. Clean install, no problem on 14.0 version.
Code:
06-20 02:29:05.240 265 265 I Magisk : * Creating /sbin overlay
06-20 02:29:05.390 265 265 E Magisk : mount tmpfs->/sbin failed with 13: Permission denied
06-20 02:29:05.390 265 265 E Magisk : symlink /root/adbd->/sbin/adbd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/bgcompact->/sbin/bgcompact failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/emmc_quickverify->/sbin/emmc_quickverify failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ffu->/sbin/ffu failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/healthd->/sbin/healthd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/knox_changer->/sbin/knox_changer failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/sswap->/sbin/sswap failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ueventd->/sbin/ueventd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/watchdogd->/sbin/watchdogd failed with 17: File exists
06-20 02:29:05.390 265 265 I Magisk : * Mounting mirrors
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/system failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /dev/block/platform/msm_sdcc.1/by-name/system->/sbin/.core/mirror/system failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : mount: /sbin/.core/mirror/system
06-20 02:29:05.390 265 265 E Magisk : symlink /sbin/.core/mirror/system/vendor->/sbin/.core/mirror/vendor failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : link: /sbin/.core/mirror/vendor
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/bin failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : bind_mount: /sbin/.core/mirror/bin
06-20 02:29:05.390 265 265 I Magisk : * Setting up internal busybox
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/busybox failed with 30: Read-only file system
06-20 02:29:05.390 269 269 E Magisk : execvpe failed with 2: No such file or directory
06-20 02:29:05.390 269 269 E Magisk : symlink /sbin/.core/mirror/bin/busybox->/sbin/.core/busybox/busybox failed with 2: No such file or directory
06-20 02:29:05.390 269 269 I Magisk : Magisk v15.1(1510) daemon started
06-20 02:29:05.390 269 273 I Magisk : ** post-fs mode running
06-20 04:29:06.210 269 277 I Magisk : ** post-fs-data mode running
06-20 04:29:06.210 269 277 I Magisk : * Mounting /data/adb/magisk.img
06-20 04:29:06.210 269 277 E Magisk : mkdir_p /sbin/.core/img failed with 30: Read-only file system
06-20 04:29:06.340 269 277 I Magisk : * Running post-fs-data.d scripts
06-20 04:29:06.340 269 277 I Magisk : * Running module post-fs-data scripts
06-20 04:29:06.350 269 277 I Magisk : * Loading modules
06-20 04:29:06.350 269 289 I Magisk : * Starting MagiskHide
06-20 04:29:06.350 269 289 I Magisk : hide_utils: Hiding sensitive props
06-20 04:29:06.360 269 289 I Magisk : hide_list: [com.google.android.gms.unstable]
06-20 04:29:06.380 269 289 I Magisk : proc_monitor: init ns=mnt:[4026531840]
12-30 17:08:38.099 269 575 I Magisk : ** late_start service mode running
12-30 17:08:38.099 269 575 I Magisk : * Running service.d scripts
12-30 17:08:38.099 269 575 I Magisk : * Running module service scripts
12-30 17:08:42.049 269 289 I Magisk : proc_monitor: zygote ns=mnt:[4026534515]
mkdante381 said:
Samsung Galaxy S5 G-900F latest magisk 15.1 and magisk manager 5.5.2 SafetyNet not passed. Clean install, no problem on 14.0 version.
Code:
06-20 02:29:05.240 265 265 I Magisk : * Creating /sbin overlay
06-20 02:29:05.390 265 265 E Magisk : mount tmpfs->/sbin failed with 13: Permission denied
06-20 02:29:05.390 265 265 E Magisk : symlink /root/adbd->/sbin/adbd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/bgcompact->/sbin/bgcompact failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/emmc_quickverify->/sbin/emmc_quickverify failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ffu->/sbin/ffu failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/healthd->/sbin/healthd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/knox_changer->/sbin/knox_changer failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/sswap->/sbin/sswap failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ueventd->/sbin/ueventd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/watchdogd->/sbin/watchdogd failed with 17: File exists
06-20 02:29:05.390 265 265 I Magisk : * Mounting mirrors
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/system failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /dev/block/platform/msm_sdcc.1/by-name/system->/sbin/.core/mirror/system failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : mount: /sbin/.core/mirror/system
06-20 02:29:05.390 265 265 E Magisk : symlink /sbin/.core/mirror/system/vendor->/sbin/.core/mirror/vendor failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : link: /sbin/.core/mirror/vendor
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/bin failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : bind_mount: /sbin/.core/mirror/bin
06-20 02:29:05.390 265 265 I Magisk : * Setting up internal busybox
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/busybox failed with 30: Read-only file system
06-20 02:29:05.390 269 269 E Magisk : execvpe failed with 2: No such file or directory
06-20 02:29:05.390 269 269 E Magisk : symlink /sbin/.core/mirror/bin/busybox->/sbin/.core/busybox/busybox failed with 2: No such file or directory
06-20 02:29:05.390 269 269 I Magisk : Magisk v15.1(1510) daemon started
06-20 02:29:05.390 269 273 I Magisk : ** post-fs mode running
06-20 04:29:06.210 269 277 I Magisk : ** post-fs-data mode running
06-20 04:29:06.210 269 277 I Magisk : * Mounting /data/adb/magisk.img
06-20 04:29:06.210 269 277 E Magisk : mkdir_p /sbin/.core/img failed with 30: Read-only file system
06-20 04:29:06.340 269 277 I Magisk : * Running post-fs-data.d scripts
06-20 04:29:06.340 269 277 I Magisk : * Running module post-fs-data scripts
06-20 04:29:06.350 269 277 I Magisk : * Loading modules
06-20 04:29:06.350 269 289 I Magisk : * Starting MagiskHide
06-20 04:29:06.350 269 289 I Magisk : hide_utils: Hiding sensitive props
06-20 04:29:06.360 269 289 I Magisk : hide_list: [com.google.android.gms.unstable]
06-20 04:29:06.380 269 289 I Magisk : proc_monitor: init ns=mnt:[4026531840]
12-30 17:08:38.099 269 575 I Magisk : ** late_start service mode running
12-30 17:08:38.099 269 575 I Magisk : * Running service.d scripts
12-30 17:08:38.099 269 575 I Magisk : * Running module service scripts
12-30 17:08:42.049 269 289 I Magisk : proc_monitor: zygote ns=mnt:[4026534515]
Click to expand...
Click to collapse
Same with me, HTC A9, latest magisk 15.2 and magisk manager 5.5.3 SafetyNet not passed!! orz
---------- Post added at 03:56 AM ---------- Previous post was at 03:00 AM ----------
I removed Xposed installer and re-installed Magisk 15.2 with Magisk Manager 5.5.3, then SafetyNet is worked again!
Also on NOTE 8 it does not pass
HTML:
01-02 09:01:52.873 3244 3244 E Magisk : symlink /root/magisk->/sbin/resetprop failed with 17: File exists
01-02 09:01:52.874 3244 3244 I Magisk : * Mounting mirrors
01-02 09:01:52.874 3244 3244 I Magisk : mount: /sbin/.core/mirror/system
01-02 09:01:52.874 3244 3244 I Magisk : link: /sbin/.core/mirror/vendor
01-02 09:01:52.874 3244 3244 I Magisk : bind_mount: /sbin/.core/mirror/bin
01-02 09:01:52.874 3244 3244 I Magisk : * Setting up internal busybox
01-02 09:01:52.882 3244 3244 I Magisk : Magisk v15.2(1520) daemon started
01-02 09:01:53.005 3244 3253 I Magisk : ** post-fs mode running
01-02 09:01:53.628 3244 3360 I Magisk : ** post-fs-data mode running
01-02 10:01:53.628 3244 3360 I Magisk : * Mounting /data/adb/magisk.img
01-02 10:01:53.776 3244 3360 I Magisk : * Running post-fs-data.d scripts
01-02 10:01:53.777 3244 3360 I Magisk : * Enabling systemless hosts file support
01-02 10:01:53.777 3244 3360 I Magisk : bind_mount: /system/etc/hosts
01-02 10:01:53.777 3244 3375 I Magisk : * Starting MagiskHide
01-02 10:01:53.777 3244 3375 I Magisk : hide_utils: Hiding sensitive props
01-02 10:01:53.777 3244 3375 I Magisk : hide_list: [com.google.android.gms.unstable]
01-02 10:01:53.787 3244 3375 I Magisk : hide_list: [fr.bnpp.digitalbanking]
01-02 10:01:53.796 3244 3375 I Magisk : proc_monitor: init ns=mnt:[4026531840]
01-02 10:01:54.252 3244 3499 I Magisk : ** late_start service mode running
01-02 10:01:54.253 3244 3499 I Magisk : * Running service.d scripts
01-02 10:02:11.097 3244 3375 I Magisk : proc_monitor: zygote ns=mnt:[4026533806] zygote64 ns=mnt:[4026533796]
01-02 10:02:30.700 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=7258 ns=mnt:[4026533924])
01-02 10:02:30.703 7264 7264 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:03:07.270 11262 11262 W Magisk : su: request rejected (10225->0)
01-02 10:03:20.984 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=12816 ns=mnt:[4026533889])
01-02 10:03:20.992 12831 12831 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:03:35.121 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=13855 ns=mnt:[4026533969])
01-02 10:03:35.124 13861 13861 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:04:22.494 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=17089 ns=mnt:[4026533924])
01-02 10:04:22.499 17095 17095 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:06:34.773 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=20020 ns=mnt:[4026533924])
01-02 10:06:34.789 20034 20034 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:06:35.792 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=20079 ns=mnt:[4026533931])
01-02 10:06:35.795 20085 20085 I Magisk : hide_daemon: Permissive detected, hide the state
iPusak Gaoq™ said:
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Click to expand...
Click to collapse
Worked for me.Thankyou.:good:
arya12321 said:
Worked for me.Thankyou.:good:
Click to expand...
Click to collapse
+1 This worked for me and as far as I can tell all modules and settings were retained.
please how can i root my tecno k9 plz i have tried evey thing help me out plz i need this root plz guys
hi. how to clear magisk manager data? i cant see the options in app settings
Hi, I seem to be having a problem with safetyNet API, I have a samsung s5 with the newest Magisk installed have tried all the suggestions on this thread but nothing works. Still get "Safety API Error" anybody have any other suggestions. Im running Android 6.0.1 on security patch 1 October 2016.
iPusak Gaoq™ said:
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Oh thanks. That was easier than what I have imagined. Thanks a lot.
mandhir said:
Upgraded to Magisk v15.0 and now when I run SafetyNet check I receive an API Error.
I am running Android 8.1 on Nexus 6P and have uninstalled Magisk using the Uninstaller and re-installed and still receive the same API error.
I've searched and read through quite a few threads and haven't come up with any fixes. Closest thing I found was a fix on the OnePlus forum.
Attached is a screenshot of the Magisk screen for reference.
Any help would be greatly appreciated.
Thanks in advance!
Click to expand...
Click to collapse
You Can Simply Add A Google Account If You Dont Have Any To Solve This Problem. I Did The Same.
Guys i have the same problem and The most strange point is that it all came up after I fresh installed a rom I had been using for a while and had no problem. I tried like every solution here e.g. adding google account or clearing magisk data etc. with no joy.
Any help is appreciated
Yesterday SuperSU & suhide suddenly disappears from my app drawer. I tried to reinstall both, with no errors, but both still vanished...
Then I restored a (quite old) data backup of and then it worked again. But after updating the apps both disappears again.
Every time I boot I get these kind of messages in logcat:
Code:
01-29 20:40:08.609 749 749 W installd: Ignoring /data/data/eu.chainfire.supersu/requests with unexpected GID 0 instead of 10087
01-29 20:40:08.609 749 749 W installd: Ignoring /data/data/eu.chainfire.supersu/requests with unexpected GID 0 instead of 10087
01-29 20:40:08.609 749 749 W installd: Ignoring /data/data/eu.chainfire.supersu/logs with unexpected GID 0 instead of 10087
01-29 20:40:08.614 749 749 W installd: Ignoring /data/data/eu.chainfire.supersu/logs with unexpected GID 0 instead of 10087
01-29 20:40:08.807 749 749 W installd: Ignoring /data/user_de/0/eu.chainfire.supersu/requests with unexpected GID 0 instead of 10087
01-29 20:40:08.807 749 749 W installd: Ignoring /data/user_de/0/eu.chainfire.supersu/requests with unexpected GID 0 instead of 10087
01-29 20:40:08.807 749 749 W installd: Ignoring /data/user_de/0/eu.chainfire.supersu/logs with unexpected GID 0 instead of 10087
01-29 20:40:08.811 749 749 I installd: Fixing /data/user_de/0/eu.chainfire.supersu/logs/L15172305400000.GRANTED.dev.ukanth.ufirewall with unexpected GID 0 instead of 10087
01-29 20:40:08.811 749 749 I installd: Fixing /data/user_de/0/eu.chainfire.supersu/logs/L15172305410000.GRANTED.com.grarak.kerneladiutor with unexpected GID 0 instead of 10087
01-29 20:40:08.812 749 749 W installd: Ignoring /data/user_de/0/eu.chainfire.supersu/logs with unexpected GID 0 instead of 10087
01-29 20:40:09.466 968 968 E RankingHelper: createDefaultChannelIfNeeded - Exception: android.content.pm.PackageManager$NameNotFoundException: eu.chainfire.suhide
01-29 20:40:09.466 968 968 E RankingHelper: deleteDefaultChannelIfNeeded - Exception: android.content.pm.PackageManager$NameNotFoundException: eu.chainfire.suhide
01-29 20:40:09.466 968 968 E RankingHelper: createDefaultChannelIfNeeded - Exception: android.content.pm.PackageManager$NameNotFoundException: eu.chainfire.suhide
01-29 20:40:09.466 968 968 E RankingHelper: deleteDefaultChannelIfNeeded - Exception: android.content.pm.PackageManager$NameNotFoundException: eu.chainfire.suhide
01-29 20:40:17.980 968 982 I BackupManagerService: Package eu.chainfire.suhide not installed; dropping from full backup
I suspect that maybe Google is blacklisting SuperSU & suhide apks from being installed...
Curiously all the apps that I gave root permission before this mess were still working with root privileges. So SuperSu and suhide apks are killed but su is still working as supposed.
Am I the only one blessed with this problem? My system data is in my signature under Nexus 5x section.
More info: when I install suhide from zip in recovery, here is what I get on next boot:
Code:
01-29 20:58:03.565 980 1005 I ActivityManager: Force stopping eu.chainfire.suhide appid=10297 user=-1: deletePackageX
01-29 20:58:03.794 980 980 W PackageManager: Destroying orphaned/data/app/eu.chainfire.suhide-L7XE6XF32M8cUz9PEhRN1A==
01-29 20:58:03.896 980 1023 I ActivityManager: Force stopping eu.chainfire.suhide appid=10297 user=0: pkg removed
01-29 20:58:05.350 980 980 I ConditionProviders: Disallowing condition provider eu.chainfire.suhide
01-29 20:58:14.169 980 1004 I ActivityManager: Start proc 3462:com.android.keychain/1000 for service com.android.keychain/.KeyChainService
01-29 20:58:23.158 4069 4069 I dex2oat : /system/bin/dex2oat --input-vdex-fd=-1 --output-vdex-fd=14 --compiler-filter=quicken -j4 --classpath-dir=/data/app/eu.chainfire.suhide-53wHVYknxTCQ9p5y4EC5Eg== --class-loader-context=PCL[]
01-29 20:58:24.306 980 1023 V BackupManagerService: restoreAtInstall pkg=eu.chainfire.suhide token=1 restoreSet=0
01-29 20:58:24.315 1232 1232 I Pm : Package eu.chainfire.suhide installed in 17494 ms
01-29 20:58:24.426 1462 1462 D ImsResolver: maybeAddedImsService, packageName: eu.chainfire.suhide
Now suhide apk is installed but without root granted...
I have the same issue on Oreo 8.1 on my Nexus 5X
Any solution so far?
Background - Barclays owned banks in Africa (for ease of simplicity let's call it Absa) they have since sold. There is still probably some lingering software between them.
Problem - The Absa app detects Magisk everytime for probably last the 3 months
So Magisk is running on my OPO3T using Validus 8.1 - 7 Jul 18 Build - I realise I think the keys are 8.0.0 when running props?
So I have attached 3 files:
1 - AbsaLogcat.txt
2 - AbsaLogcatNoMagisk.txt
3 - magisk.log
Code:
[b]File 1[/b]
Boot phone
Run App
Get logcat from adb
Code:
[b]File 2[/b]
Boot phone
Uninstall Magisk Manager
Run App
get logcat from adb
Code:
[b]File 3[/b]
Boot phone
Uninstall Magisk Manager
Run App
get logcat from adb
get /cache/magisk.log
I am intrigued that without Magisk there's a whole lot more information. Is the stuff in ActivityManager the ones I should be looking out for?
From File 1
Code:
$ cat AbsaLogcat.txt | grep ActivityManager
08-02 22:16:14.349 2534 2585 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity (has extras)} from uid 10020
08-02 22:16:14.391 2534 4437 I ActivityManager: Start proc 6469:com.barclays.absa.banking/u0a246 for activity com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity
08-02 22:16:18.863 2534 4435 I ActivityManager: START u0 {cmp=com.barclays.absa.banking/.phone.login.RootTamperActivity} from uid 10246
08-02 22:16:19.367 2534 2618 W ActivityManager: Activity pause timeout for ActivityRecord{b2bee4e u0 com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity t13938 f}
08-02 22:16:24.862 2534 3370 I ActivityManager: Killing 6469:com.barclays.absa.banking/u0a246 (adj 900): remove task
[/code]
From File 2
Code:
$ cat AbsaLogcatNoMagisk.txt | grep ActivityManager
08-02 22:30:07.725 2458 7396 I ActivityManager: Start proc 7487:com.barclays.absa.banking/u0a246 for broadcast com.barclays.absa.banking/com.imimobile.connect.core.internal.services.BootCompleteReceiver
08-02 22:30:15.125 2458 6584 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity (has extras)} from uid 10020
08-02 22:30:23.519 2458 7027 I ActivityManager: START u0 {cmp=com.barclays.absa.banking/.v4.presentation.passcode.passcode_login.SimplifiedLoginActivity (has extras)} from uid 10246
08-02 22:30:32.684 2458 7599 I ActivityManager: START u0 {flg=0x4000000 cmp=com.barclays.absa.banking/.rebrand.home.HomeContainerActivity (has extras)} from uid 10246
08-02 22:30:40.490 2458 3337 I ActivityManager: START u0 {flg=0x14008000 cmp=com.barclays.absa.banking/.v4.presentation.passcode.passcode_login.SimplifiedLoginActivity} from uid 10246
08-02 22:30:40.505 2458 2475 W ActivityManager: Duplicate finish request for ActivityRecord{25f32ea u0 com.barclays.absa.banking/.rebrand.home.HomeContainerActivity t13940 f}
08-02 22:30:41.765 2458 2634 I ActivityManager: Displayed com.barclays.absa.banking/.v4.presentation.passcode.passcode_login.SimplifiedLoginActivity: +1s247ms
08-02 22:30:48.976 2458 8419 I ActivityManager: Killing 7487:com.barclays.absa.banking/u0a246 (adj 900): remove task
I'm replying to you here instead of in the MagiskHide Props Config thread...
Your issue has nothing to do with build.prop. The app is simply detecting Magisk.
Not sure which specific app is causing you issues, but I tested the Barclays app from the Play store and can start it just fine with Magisk active, after setting everything up properly.
The trick is that you also have to add the phone app (com.android.dialer) to the Hide list. Notice how the app asks for phone permission? With both the app and the phone on the Hide list it no longer detects root, during my test.
Also, if the app has detected root once, you have to clear data for the app since it seems to store your device state.
Edit: Never mind... I found the app and it's much simpler. It's looking for "Magisk" in the app name. That kind of detection will be fixed in a future Magisk release. Meanwhile you can uninstall the Manager whenever you need to use the banking app, or try this, some have reported success with changing the app name with that:
https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor
yeah i've been uninstalling magisk when i need to use it.
will try that app as well in the meanwhile
Used this solution from another thread (edited it)
Pietolsen said:
You can change the app name with the app called APK Editor on the playstore. Works for me, just select Magisk Manager and select common edit, change the name (to Magic or whatever), also tick the "Rename package name in DEX file(s)" box and install the new APK you generate (you will need to uninstall first if it is still installed). I just changed the name to Magic and it works just fine for me now.
Click to expand...
Click to collapse
Is there a way to get the xperia-original symbols ported to LOS?
I dont like the LOS-symbols ( for example the signal-strength).
muebbel said:
Is there a way to get the xperia-original symbols ported to LOS?
I dont like the LOS-symbols ( for example the signal-strength).
Click to expand...
Click to collapse
I assume you'd just need to change a few xmls from SystemUI\res\drawable from one to the other. So you'd have to decompile both SystemUI apks and compare the xmls, make changes if needed, recompile and test.
1. decompiled
2. cp ORIG/res/drawable/stats* LOS/res/drawable/
3. recompiled without problems
4. replace /system/priv-app/SystemUI/SystemUI.apk with the new new
5. reboot
6. phone stuck in "prepare for startup"
7. going back to TWRP replace new compiled SystemUI.apk with old from Backup
8 reboot phone
9. nothing to see in the display (but logcat looks like everything works)
10. need to wipe /data else the phone stuck "somewhere"
It seems i missed something here (wipe cache dont help).. any suggestions?
muebbel said:
1. decompiled
2. cp ORIG/res/drawable/stats* LOS/res/drawable/
3. recompiled without problems
4. replace /system/priv-app/SystemUI/SystemUI.apk with the new new
5. reboot
6. phone stuck in "prepare for startup"
7. going back to TWRP replace new compiled SystemUI.apk with old from Backup
8 reboot phone
9. nothing to see in the display (but logcat looks like everything works)
10. need to wipe /data else the phone stuck "somewhere"
It seems i missed something here (wipe cache dont help).. any suggestions?
Click to expand...
Click to collapse
Welcome to modding! Did you copy the original AndroidManifest.xml and META-INF from the old apk into the new after compiling the new one? Give this THREAD a read if not.
ahh i isee, in this howto u going to decompile the framework-res.apk, i just do it with the SystemUi.apk (xz1c). Lets give a try
It seems only modify some XMLs isnt the way to go... because in the SystemUI.apk and framework-res.apk from the LOS are all the 'res/drawable-hdpi/stat_sys_signal*'.png things missing...
The Question for me is: can i just copy the stat_sys_signal*.png files into the LOS SystemUI.apk and recompile it? :/
Hmmm, everything was done fine so far... (after dd if=SystemUI.apk there was new symbols).
There was some errors related to systemui after dd .. but seems to work
06-09 02:41:23.748 4939 4964 D InstalledAppProviderSer: insertAppIntoDb com.android.systemui
06-09 02:42:35.648 2258 2258 I chatty : uid=10047(com.android.systemui) identical 1 line
06-09 02:56:39.520 2258 2258 F libc : Fatal signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 0x70a0b45bbc in tid 2258 (ndroid.systemui), pid 2258 (ndroid.systemui)
06-09 02:56:39.611 5209 5209 F DEBUG : pid: 2258, tid: 2258, name: ndroid.systemui >>> com.android.systemui <<<
06-09 02:56:40.188 1403 1765 W InputDispatcher: channel 'fc9237e com.android.systemui.ImageWallpaper (server)' ~ Consumer closed input channel or an error occurred. events=0x9
06-09 02:56:40.188 1403 1765 E InputDispatcher: channel 'fc9237e com.android.systemui.ImageWallpaper (server)' ~ Channel is unrecoverably broken and will be disposed!
06-09 02:56:40.198 1403 2456 D NotificationListeners: Removing active service ComponentInfo{com.android.systemui/com.android.systemui.statusbar.NotificationListener}
06-09 02:56:40.200 1403 1403 W WallpaperManagerService: Wallpaper service gone: ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper}
06-09 02:56:40.200 1403 4001 I ActivityManager: Process com.android.systemui (pid 2258) has died: pers BFGS
06-09 02:56:40.206 1403 4001 W ActivityManager: Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
06-09 02:56:40.206 1403 4001 W ActivityManager: Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
06-09 02:56:40.206 1403 4001 W ActivityManager: Scheduling restart of crashed service com.android.systemui/.keyguard.KeyguardService in 0ms
06-09 02:56:40.215 1403 4001 W ActivityManager: Re-adding persistent process ProcessRecord{f307f7f 2258:com.android.systemui/u0a47}
06-09 02:56:40.225 1403 1692 W WindowManager: Failed to report 'resized' to the client of Window{fc9237e u0 com.android.systemui.ImageWallpaper}, removing this window.
06-09 02:56:40.228 1403 1692 W InputDispatcher: Attempted to unregister already unregistered input channel 'fc9237e com.android.systemui.ImageWallpaper (server)'
06-09 02:56:40.305 1403 1697 I ActivityManager: Start proc 5220:com.android.systemui/u0a47 for restart com.android.systemui
06-09 02:56:40.360 5220 5220 E ndroid.systemu: Dex checksum does not match for dex: /system/priv-app/SystemUI/SystemUI.apk.Expected: 1801530101, actual: 1791375372
06-09 02:56:40.593 5220 5220 W AlarmManager: Unrecognized alarm listener com.android.systemui.keygu[email protected]cf2ccef
06-09 02:56:40.631 5220 5220 V SystemUIService: Starting SystemUI services for user 0.
06-09 02:56:40.642 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.Dependency took to complete: 10ms
06-09 02:56:40.667 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.util.NotificationChannels took to complete: 25ms
06-09 02:56:40.673 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.statusbar.CommandQueue$CommandQueueStart took to complete: 6ms
06-09 02:56:40.800 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.keyguard.KeyguardViewMediator took to complete: 127ms
06-09 02:56:41.000 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.recents.Recents took to complete: 200ms
06-09 02:56:41.126 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.volume.VolumeUI took to complete: 126ms
06-09 02:56:41.193 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.stackdivider.Divider took to complete: 67ms
06-09 02:56:41.931 1403 5087 W ActivityManager: Receiver with filter [email protected] already registered for pid 5220, callerPackage is com.android.systemui
06-09 02:56:41.990 5220 5220 V WifiManager: registerSoftApCallback: callb[email protected]a403528, handler=Handler (android.os.Handler) {2790241}
06-09 02:56:42.099 5220 5220 V WifiManager: registerSoftApCallback: callb[email protected]a403528, handler=Handler (android.os.Handler) {2790241}
06-09 02:56:42.173 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.SystemBars took to complete: 979ms
06-09 02:56:42.194 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.usb.StorageNotification took to complete: 21ms
06-09 02:56:42.213 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.power.PowerUI took to complete: 18ms
06-09 02:56:42.218 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.media.RingtonePlayer took to complete: 5ms
06-09 02:56:42.221 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.keyboard.KeyboardUI took to complete: 3ms
06-09 02:56:42.260 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.pip.PipUI took to complete: 39ms
06-09 02:56:42.263 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.shortcut.ShortcutKeyDispatcher took to complete: 2ms
06-09 02:56:42.263 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.VendorServices took to complete: 1ms
06-09 02:56:42.270 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.util.leak.GarbageMonitor$Service took to complete: 6ms
06-09 02:56:42.272 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.LatencyTester took to complete: 2ms
06-09 02:56:42.277 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.globalactions.GlobalActionsComponent took to complete: 5ms
06-09 02:56:42.287 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.ScreenDecorations took to complete: 9ms
06-09 02:56:42.304 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.fingerprint.FingerprintDialogImpl took to complete: 17ms
06-09 02:56:42.306 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.fingerprint.FODCircleViewImpl took to complete: 2ms
06-09 02:56:42.308 5220 5220 D SystemUIBootTiming: StartServicescom.android.systemui.SliceBroadcastRelayHandler took to complete: 2ms
06-09 02:56:42.309 5220 5220 D SystemUIBootTiming: StartServices took to complete: 1677ms
06-09 02:56:44.059 5220 5220 I chatty : uid=10047(com.android.systemui) identical 7 lines
06-09 02:57:25.649 5220 5235 W ndroid.systemu: Checksum mismatch for dex SystemUI.apk
and after a reboot:
[email protected] ~ $ grep -i systemui /tmp/foo4
06-09 03:01:50.283 1364 1669 W PackageParser: Ignoring duplicate uses-permissions/uses-permissions-sdk-m: android.permission.CONFIGURE_WIFI_DISPLAY in package: com.android.systemui at: Binary XML file line #134
06-09 03:01:50.292 1364 1364 I PackageManager: /system/priv-app/SystemUI changed; collecting certs
06-09 03:01:50.310 1364 1364 W PackageManager: Failed to scan /system/priv-app/SystemUI: Failed to collect certificates from /system/priv-app/SystemUI/SystemUI.apk
06-09 03:01:50.527 1364 1364 W PackageManager: System package com.android.systemui no longer exists; it's data will be wiped
06-09 03:01:50.536 1364 1364 W PackageManager: Removing dangling permission: com.android.systemui.permission.SELF from package com.android.systemui
06-09 03:01:50.536 1364 1364 W PackageManager: Removing dangling permission: com.android.systemui.permission.PLUGIN from package com.android.systemui
06-09 03:01:50.536 1364 1364 W PackageManager: Removing dangling permission: android.permission.systemui.IDENTITY from package com.android.systemui
06-09 03:01:50.568 1364 1364 W PackageManager: Destroying /data/user_de/0/com.android.systemui due to: com.android.server.pm.PackageManagerException: Package com.android.systemui is unknown
06-09 03:01:51.236 1364 1364 W BluetoothManagerService: Unable to resolve SystemUI's UID.
06-09 03:01:51.236 1364 1364 W BluetoothManagerService: android.content.pm.PackageManager$NameNotFoundException: com.android.systemui
06-09 03:01:51.570 1364 1364 E WifiConfigManager: Unable to resolve SystemUI's UID.
06-09 03:01:51.732 1364 1364 E RankingHelper: createDefaultChannelIfNeeded - Exception: android.content.pm.PackageManager$NameNotFoundException: com.android.systemui
06-09 03:01:52.463 1364 1364 W ActivityManager: Unable to start service Intent { cmp=com.android.systemui/.keyguard.KeyguardService } U=0: not found
06-09 03:01:52.464 1364 1364 I SystemServer: StartSystemUI
06-09 03:01:52.465 1364 1364 W ActivityManager: Unable to start service Intent { flg=0x100 cmp=com.android.systemui/.SystemUIService } U=0: not found
06-09 03:01:52.465 1364 1364 W ActivityManager: Unable to start service Intent { flg=0x100 cmp=com.android.systemui/.keyguard.KeyguardService } U=0: not found
06-09 03:01:52.465 1364 1364 V KeyguardServiceDelegate: *** Keyguard: can't bind to ComponentInfo{com.android.systemui/com.android.systemui.keyguard.KeyguardService}
06-09 03:01:52.466 1364 1364 D SystemServerTiming: StartSystemUI took to complete: 1ms
06-09 03:01:52.600 1364 1364 V WallpaperManagerService: bindWallpaperComponentLocked: componentName=ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper}
06-09 03:01:52.601 1364 1364 W WallpaperManagerService: Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
06-09 03:01:52.601 1364 1364 W WallpaperManagerService: Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
06-09 03:01:52.613 2020 2020 W BluetoothAdapterService: Unable to resolve SystemUI's UID.
06-09 03:01:52.613 2020 2020 W BluetoothAdapterService: android.content.pm.PackageManager$NameNotFoundException: com.android.systemui
06-09 03:02:23.301 1364 1482 W PackageManager: Destroying /data/user/0/com.android.systemui due to: com.android.server.pm.PackageManagerException: Package com.android.systemui is unknown
But i dont see any mistake? :/
muebbel said:
It seems only modify some XMLs isnt the way to go... because in the SystemUI.apk and framework-res.apk from the LOS are all the 'res/drawable-hdpi/stat_sys_signal*'.png things missing...
The Question for me is: can i just copy the stat_sys_signal*.png files into the LOS SystemUI.apk and recompile it? :/
Click to expand...
Click to collapse
The icons aren't pngs anymore, it's just the xml files you need to concentrate on, and open them up to compare the code.
wtf, why its so hard to change this signal_cluster icons:
{
"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"
}
in this:
i cant compare the XML's of the 2 ROMs, because the stock XZ1c uses PNG's, so i guess i need to copy this PNGs. :/
muebbel said:
because the stock XZ1c uses PNG's
Click to expand...
Click to collapse
No, they do not, as I said above, pngs haven't been used for a long time. Look at the naming of the xmls, that usually gives you a clue. It's not something I've changed so giving suggestions as to what I would do if I looked to change them.
muebbel said:
i cant compare the XML's of the 2 ROMs, because the stock XZ1c uses PNG's, so i guess i need to copy this PNGs. :/
Click to expand...
Click to collapse
Any joy? https://developer.android.com/guide/topics/graphics/vector-drawable-resources
I'm not a developer myself, but I know you can change status bar icons with substratum themes if you have used that before.
Here is the link to substratum info:
https://www.xda-developers.com/substratum-hub/
And a theme that has similar notification icons to the Xperia ones:
https://play.google.com/store/apps/details?id=liv.white.substratum
SXUsr said:
Any joy? https://developer.android.com/guide/topics/graphics/vector-drawable-resources
Click to expand...
Click to collapse
I have a few problems with the xz1c and the LOS16 from modpunk, so i decided to put the "style" topic at the end of the queue.
MDomokos said:
I'm not a developer myself, but I know you can change status bar icons with substratum themes if you have used that before.
Here is the link to substratum info:
https://www.xda-developers.com/substratum-hub/
And a theme that has similar notification icons to the Xperia ones:
https://play.google.com/store/apps/details?id=liv.white.substratum
Click to expand...
Click to collapse
Substratum for Pie isnt a solution, because this needs root, but root kills my "banking app" (even with magisk hide).
muebbel said:
Substratum for Pie isnt a solution, because this needs root, but root kills my "banking app" (even with magisk hide).
Click to expand...
Click to collapse
Ah, I see.
Hopefully you can get the icons working. Keep us posted.
[NOT SOLVED] It started working after I submitted this hahah, maybe it is because I charged the mobile fully.. Then it failed after some time.
Hi! New to this, installed a few days ago, and since then I did not see any stats EXCEPT for Alarms and CPU states, so the message "No stats have been collected yet" shows on all views except Alarms and CPU states. This morning I charged the battery, rebooted and took all the debugging info possible from the app. More details:
MODEL: Poco X3 Pro
OS: MIUI EEA 12.5.1
Granted permission to BSS: Yes, via ADB
Autostart: Yes, enabled autostart
Battery saver: Yes, no restrictions
BSS version: 2.6-382 (99) XDA edition, from AppCenter
Rooted: nope
Logcat (couldnt attach): https://cryptpad.fr/pad/#/2/pad/view/vNayXLuR+OJvdblkUQwfgKpanvCzVgIhgZ-QC2s5tTI/
More details:
* I uninstalled several apps via "Xiaomi ADB/Fastboot Tools":
Code:
com.android.browser
com.android.chrome
com.android.providers.downloads.ui
com.android.providers.partnerbookmarks
com.android.soundrecorder
com.facebook.appmanager
com.facebook.services
com.facebook.system
com.google.android.apps.googleassistant
com.google.android.apps.subscriptions.end
com.google.android.apps.wellbeing
com.google.android.calendar
com.google.android.feedback
com.google.android.gm
com.google.android.googlequicksearchbox
com.google.android.inputmethod.latin
com.google.android.youtube
com.mi.android.globalFileexplorer
com.mi.android.globalminusscreen
com.milink.service
com.mipay.wallet.in
com.miui.analytics
com.miui.backup
com.miui.bugreport
com.miui.calculator
com.miui.cloudbackup
com.miui.cloudservice
com.miui.cloudservice.sysbase
com.miui.micloudsync
com.miui.compass
com.miui.fm
com.miui.freeform
com.miui.global.packageinstaller
com.miui.mybrid
com.miui.miservice
com.miui.mishare.connectivity
com.miui.msa.global
com.miui.notes
com.miui.phrase
com.miui.player
com.miui.touchassistant
com.miui.videoplayer
com.miui.weather2
com.miui.yellowpage
com.netflix.partner.activation
com.tencent.soter.soterserver
com.xiaomi.discover
com.xiaomi.glgm
com.xiaomi.joyose
com.xiaomi.mi_connect_service
com.xiaomi.midrop
com.xiaomi.mipicks
com.xiaomi.miplay_client
com.xiaomi.payment
com.xiaomi.scanner
Some exceptions and lines I have in the logcat, so this is easier to find on the forums and you can get a preview:
Code:
# logcat fragments
[...]
06-27 10:30:38.220 E/tats_xdaeditio( 5707): failed to connect to jdwp control socket: Connection refused
[...]
06-27 10:30:38.964 E/BatteryStatsProxy( 5707): An exception occured in BatteryStatsProxy(). Message: com.android.internal.app.IBatteryStats.getStatisticsStream [boolean]
06-27 10:30:39.009 E/JavaBinder( 5707): !!! FAILED BINDER TRANSACTION !!! (parcel size = 96)
06-27 10:30:39.009 E/BatteryStatsProxy( 5707): An exception occured in BatteryStatsProxy(). Message: Transaction failed on small parcel; remote process probably died
06-27 10:30:39.010 D/BatteryStatsProxy( 5707): getWakelockStats was called with params [iStatType] = 1
06-27 10:30:39.010 W/tats_xdaeditio( 5707): Accessing hidden method Lcom/android/internal/os/BatteryStatsImpl;->computeBatteryRealtime(JI)J (greylist, reflection, allowed)
06-27 10:30:39.011 E/StatsProvider( 5707): An exception occured processing kernel wakelocks. Message: null
06-27 10:30:39.012 E/StatsProvider( 5707): Exception: com.asksven.android.common.privateapiproxies.BatteryInfoUnavailableException
06-27 10:30:39.012 E/StatsProvider( 5707): at com.asksven.android.common.privateapiproxies.BatteryStatsProxy.computeBatteryRealtime(BatteryStatsProxy.java:600)
06-27 10:30:39.012 E/StatsProvider( 5707): at com.asksven.android.common.privateapiproxies.BatteryStatsProxy.getKernelWakelockStats(BatteryStatsProxy.java:2693)
06-27 10:30:39.012 E/StatsProvider( 5707): at com.asksven.betterbatterystats.data.StatsProvider.getCurrentKernelWakelockStatList(StatsProvider.java:1192)
06-27 10:30:39.012 E/StatsProvider( 5707): at com.asksven.betterbatterystats.data.StatsProvider.populateReference(StatsProvider.java:2622)
06-27 10:30:39.012 E/StatsProvider( 5707): at com.asksven.betterbatterystats.data.StatsProvider.setCurrentReference(StatsProvider.java:2493)
06-27 10:30:39.012 E/StatsProvider( 5707): at com.asksven.betterbatterystats.StatsActivity$LoadStatData.doInBackground(StatsActivity.java:912)
06-27 10:30:39.012 E/StatsProvider( 5707): at com.asksven.betterbatterystats.StatsActivity$LoadStatData.doInBackground(StatsActivity.java:901)
06-27 10:30:39.012 E/StatsProvider( 5707): at android.os.AsyncTask$3.call(AsyncTask.java:394)
06-27 10:30:39.012 E/StatsProvider( 5707): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
06-27 10:30:39.012 E/StatsProvider( 5707): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
06-27 10:30:39.012 E/StatsProvider( 5707): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-27 10:30:39.012 E/StatsProvider( 5707): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-27 10:30:39.012 E/StatsProvider( 5707): at java.lang.Thread.run(Thread.java:923)
06-27 10:30:39.015 I/System.out( 5707): The method is: public abstract long com.android.internal.app.IBatteryStats.computeChargeTimeRemaining() throws android.os.RemoteException
[...]
Any ideas? I searched and part of the problem (!!! FAILED BINDER TRANSACTION !!!) has something to do with arguments being too long or something like that (https://stackoverflow.com/questions/36007540/failed-binder-transaction-in-android, https://stackoverflow.com/questions...hen-putting-an-bitmap-dynamically-in-a-widget)
Thanks!
Edit 1: added more explanation to where the "No stats collected yet" is shown.
Edit 2: added if the phone is rooted or not (it is not rooted).
Edit 3: uploaded logcat file
Edit 4&5: could not upload logcat, pasted into a pastebin (https://cryptpad.fr/pad/#/2/pad/view/vNayXLuR+OJvdblkUQwfgKpanvCzVgIhgZ-QC2s5tTI/)
Gosh... it started working... maybe because I charged the mobile fully? Not sure...
Failed again, more or less with the same tracebacks. Will investigate further and see where I end up.
I'm having a similar issue (https://forum.xda-developers.com/t/...lect-most-of-the-stats-status-failed.4315889/). Were you able to solve it?
Hi! I updated the first post to make it clear. I did not solve it fully. Restarting the phone fixed it during a period of time. Maybe the SO is killing something in the background and preventing the App to gather information.
I ended uninstalling.
this does not work on android 12 at all
I loved this app as it showed you the best and accurate stats but no updates since June
Yep, not working for me on Android 12 on my Pixel 6 Pro.
Same. Not working on pixel 5 in Android 12
Utini said:
Yep, not working for me on Android 12 on my Pixel 6 Pro.
Click to expand...
Click to collapse
Same here, pixel 6 pro rooted.
Hi,
excuse me digging, but I have registered just to write I had the same issue and installation of older version (2.5-314) solved it
I thought it was beacause I deleted Joyose and Daemon from my MiUI, but it was just a coincidence
Same here, using OP 9 Pro running Android 13. I can only see information in the Alarms and CPU states screens.