-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Phone (cannot hear/mic muted) #5
Comments
De-Bloater really doesn't have any database to know the consequences of disabling an app. It is really difficult to do. The only thing possible is to use the app more carefully by the user. Just don't touch an app if you're not sure. |
yes but it should restore to the initial state after restoring apk |
App will definitely restore the original APK file after a reboot, if you removed it from the Inactive applications page. However, the app settings removed will be lost forever. Also. the app which shows issues might be dependent on some other apps, that are still debloated. That's why, removing the module solves the issues on your side. The only option to solve this issue is to identify the culprit(s) and avoid them from debloating. |
I found that the app that shows notification after disabling magisk module is com.oneplus.carrierlocation which i didn't even debloated. As you say , the cause of phone app stopping working might be due to this apk (which comes from oneplus) that has dependencies in some of the apks that i debloated. quite messy.. |
I disabled these using de-bloater:
ok google enrollment
x google enrollment
google location history
photos
google pay
GOOGLE CONTACTS SYNC
Now, one of these, (not very sure which) BREAKS PHONE APP (cannot hear/mic muted).
The problem with de-bloater is that, even if i restored all the above apps and rebooted, still couldn't call.
I had to remove the apk and magisk module + restart to make it work again.
Most probably it was due to the google location history being disabled. Then carrier location notification appeared after reboot.
The text was updated successfully, but these errors were encountered: