com.qualcomm.qcrilmsgtunnel about universal-android-debloater-next-generation HOT 13 CLOSED

This issue was noted before me:
0x192/universal-android-debloater#146
0x192/universal-android-debloater#169 (comment)

My suggestion from now on:
Read the open issues on the original UAD and learn from them (add/remove/change packages) so something like this won't happen to a different user.

from universal-android-debloater-next-generation.

Something is weird with the commits to this specific package, it seems like it was already fixed in the original UAD (moved to Advanced) and somehow broke in one of the PR merges here (moving it back to Recommended), you'll have to investigate this and use blame to see what exactly went wrong since those kind of issues could have happened more than once on other packages.

from universal-android-debloater-next-generation.

It was probably the AnonymousWP mega merger, or blitz's fix. Thank you for pointing this out. We'll resolve it asap

from universal-android-debloater-next-generation.

Opened a PR and changed it to Expert. I also added a warning to the description.

from universal-android-debloater-next-generation.

Have you found out what caused it (to be changed back to Recommended?)?

from universal-android-debloater-next-generation.

Have you found out what caused it (to be changed back to Recommended?)?

GitLens told me it was last modified by https://github.com/Blitz517.

from universal-android-debloater-next-generation.

Fixed with #59.

Oh by the way, you people use dual-SIM? See description of the package.

from universal-android-debloater-next-generation.

No, I don't use dual-SIM

from universal-android-debloater-next-generation.

So if it's blitz's fix, maybe there are more mistakes like this one in there? have you checked it?

from universal-android-debloater-next-generation.

So if it's blitz's fix, maybe there are more mistakes like this one in there? have you checked it?

Perhaps, but it's a lot of work to check all packages for issues, and how would I test all of that? I don't have all phones that exist.

from universal-android-debloater-next-generation.

I was thinking about something more specific:
Take blitz's fix original base file of UAD it was based on (if you can find that info that would be great), like specific date or specific commit, and compare it to the latest original UAD and then cross-reference the changes to blitz's fix to see what regressions (like the one here) happened.
Sounds simple and if I had to summarize it - it's like an equation with 3 variable, the first one is blitz's base file, the second is latest UAD file, and the third is blitz's fix file itself.

from universal-android-debloater-next-generation.

Don't think it's worth it, considering how much time it takes. Blitz is going through a lot of packages already and improves them where possible (see open PRs). Or, if you want of course, feel free to open a PR yourself.

from universal-android-debloater-next-generation.

For information, same issue, I couldn't receive SMS messages on Oppo Find X2 Pro after disabling this package (call and sending was OK).
Took me some time to find it!

from universal-android-debloater-next-generation.