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

BIZARRE warning in my logcats right after flashing superuser.zip ! #37

Open
noisnogit opened this issue Jan 30, 2016 · 3 comments
Open

Comments

@noisnogit
Copy link

Hello.

After flashing the superuser.zip for the first time, a strange warning started to show in my logcats. Something like:

W/su ( 3736): hacks: Testing (com.keramidas.TitaniumBackup:-1:0)
W/su ( 3737): hacks: Testing (com.keramidas.TitaniumBackup:10060), 0

This warnings were appearing continuously but without a pattern. I imidiately stop using the device for its original purpose and start to meticulously search for the origin of the warning. But the only thing I found out is that the messages appear only when wifi or data are on or in the boot process.

After several tests I was thinking that the problem could be with the superuser binary. I wiped my device and clean installed CM 12,1. After the installation I only installed the superuser app and changed the root configurations on developer options (always paying attention to the logs) and right after that I flashed the supersu.zip.

Right after booting my device, the same warnings start to appear again :( The most bizarre of all, is that I never installed the TitaniumBackup app or nothing similar...

Someone have a similar problem or could give me some light about the situation, please?

PS: Sorry for my poor english...

@Inphi
Copy link

Inphi commented Jan 30, 2016

That's expected. Superuser runs some hacks for TitaniumBackup, even if you don't have it installed, to ensure it's executing on the appropriate context.
You may ignore those warnings.

@noisnogit
Copy link
Author

Seriously? I mean, why?

@lbdroid
Copy link

lbdroid commented Oct 24, 2016

It isn't actually running ANYTHING. It is only looking to see if that particular package is installed, and only IF it is installed, does it actually do something... and only IF that particular application is the one making the su request.

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

3 participants