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

Custota crashes after rebooting after installation on kernelsu #45

Open
josevega96 opened this issue Mar 19, 2024 · 3 comments
Open

Custota crashes after rebooting after installation on kernelsu #45

josevega96 opened this issue Mar 19, 2024 · 3 comments
Assignees

Comments

@josevega96
Copy link

After installing the module in kernelsu it gets installed as com.chiller3.custota.MainAplication it works after adding it in the superuser section, but after rebooting the app doesn't open, to fix it you need to reinstall the apk manually again but after rebooting again it will crash again
custota.txt

@josevega96 josevega96 changed the title Custoota crashes after rebooting after installation on kernelsu Custota crashes after rebooting after installation on kernelsu Mar 19, 2024
@chenxiaolong chenxiaolong self-assigned this Mar 20, 2024
@chenxiaolong
Copy link
Owner

It's crashing because Android is blocking it from accessing android.os.ServiceManager.getServiceOrThrow. This means, for whatever reason, Android itself is blocked from accessing the /system/etc/sysconfig/config-com.chiller3.custota.xml file from Custota's module.

This is usually caused by root hiding things. Is there anything else you have installed that might be preventing the system from accessing Custota's files? I unfortunately don't really have any other suggestions.

it gets installed as com.chiller3.custota.MainAplication

This is the same root cause. Same thing if the icon was just a generic icon instead of Custota's icon. It happens when certain Android components (like the home screen) are blocked from accessing Custota's .apk.

@josevega96
Copy link
Author

Being doing some testing in a clean installation. the app works on pixel stock february, but once it gets updated to march it stops working after a reboot, also tried installing the module with Magisk and the result is the same

@chenxiaolong
Copy link
Owner

Hmm, if it's happening even on a clean installation, I'm not really sure where the issue might be then. I'm personally also using the Pixel stock OS on the March update + Magisk, but I'm not able to reproduce this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants