[Magisk] milomak:
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

[b]File 1[/b]
Boot phone
Run App
Get logcat from adb

[b]File 2[/b]
Boot phone
Uninstall Magisk Manager
Run App
get logcat from adb

[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

$ 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

$ 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