Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: After boot, in 3-5 minutes, apps that have not yet started refuse to start #109

Open
3 tasks done
antoniu200 opened this issue Jan 10, 2025 · 11 comments
Open
3 tasks done
Labels
bug Something isn't working not confirmed This issue or pull request is not confirmed to be done.

Comments

@antoniu200
Copy link

antoniu200 commented Jan 10, 2025

Version

1.0.0-rc1

Modules

autopif by vladrevers
encryptionspoof by nicksons28(xda)
Play Integrity Fork by osm0sis & chiteroman
ViPER4ANDROID repackagedhoch87 by ViPER520
YouTube ReVanced by j-hc

Zygisk - LSPosed by Jing Matrix
HideMyApplist (com.tsng.hidemyapplist)
Disable-FLAG_SECURE (com.varuns2002.disable_flag_secure)
CorePatch (com.coderstory.toolkit)
Bootloader Spoofer (es.chiteroman.bootloaderspoofer)

Description

Hello,

After installing this module, I have noticed that, even though no apps were detecting Zygote injection anymore, some apps refuse to start after 3-5 minutes since the phone was booted. The phone also starts lagging like crazy, but Franco Kernel Manager sees no offending apps that consume CPU or RAM.

Device: HMD Global Nokia 5.4 TA-1337
OS: Android 10 00WW_1_300 (is this version supported?)
Root method: Kitsune Mask by HuskyDG (yes I know it's vulnerable, but didn't have the time to upgrade)

Steps to reproduce

  1. Reboot the phone.
  2. Let it run for at least 3-5 minutes.
  3. Try to launch any app that you haven't used in the previous minutes.

Logs

EDIT: logcat.zip

I have no logcat currently, as I could not get it working in time, but will attach some as soon as possible (at this moment, I need to get my banking apps working again, as this problem caused my tap-to-pay service to get revoked remotely by the bank).

Confirmations

  • My environment meets the minimum requirements.
  • I have verified that this is not a duplicate issue.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@antoniu200 antoniu200 added bug Something isn't working not confirmed This issue or pull request is not confirmed to be done. labels Jan 10, 2025
@ThePedroo
Copy link
Member

Please use latest from either or both from main or remove/detection-points, in debug mode. If it persists, send logcat

@antoniu200
Copy link
Author

antoniu200 commented Jan 10, 2025

Uhhhh...

use latest from either or both

Not sure I understand your message. But my modules are as up-to-date as possible, including Kitsune Mask - using latest Canary from HuskyDG.

@antoniu200
Copy link
Author

antoniu200 commented Jan 10, 2025

Updated OP with logcat.

Off topic: The banking app does not work anymore, they must have marked my device somehow, because I pass Play Integrity. Other banking apps work just fine too.

EDIT: Not sure if this is relevant, but any kind of Zygisk causes Dex2oat to stop working.

@ThePedroo
Copy link
Member

Your ReZygisk version is too old, you must update to either latest from main branch or remove/detection-points branch

@antoniu200
Copy link
Author

antoniu200 commented Jan 11, 2025

I thought I had to get them from the Release tags. Got the correct ones now from the Actions tab.

The bug happens with main release and detection-points debug (builds 311). Haven't tested detection-points release.
The only build where the bug is not present is main debug, but the phone is noticeably more laggy than normal.

Some logcats. The apps that refused to open where Contacts, Momo and maybe others (I saw some relevant logs).

logcat.zip

@Qing0731
Copy link

l think you should use Cl version

@antoniu200
Copy link
Author

antoniu200 commented Jan 12, 2025

Okay, I just realised that I messed up yesterday and only tested main, twice, but no detection-points build.

I made sure this time I downloaded the detection-points builds (325) and tried both debug and release.
logcat 12-jan.zip

The bug happened on both.

l think you should use Cl version

Where can I get that?

@pluseach
Copy link

Where can I get that?

at the actions tab
#405 or #403

@antoniu200
Copy link
Author

I tested those builds (311) already, here: #109 (comment)

@ThePedroo
Copy link
Member

I need to know the package names of the applications that are crashing, as I don't see any crash caused by Zygisk there.

@antoniu200
Copy link
Author

They're not crashing, they're simply not starting up.

Their animation wants to start (the icon grows a bit in size), but the app never launches.

The logs I saw were mentioning timeouts for the apps that refused to start:

  • com.alibaba.aliexpresshd
  • com.google.android.calculator
  • com.google.android.deskclock
  • io.github.vvb2060.mahoshojo (Momo)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working not confirmed This issue or pull request is not confirmed to be done.
Projects
None yet
Development

No branches or pull requests

4 participants