Android: bad call: specified pacakge **** under uid 10121, but it's really -1

Question

I get a strange warning in my catlog when I run the application on my Samsung Galaxy Nexus (Android 4.3, rooted). I am reading a log using logcat on the phone itself.

Background: I recently changed the package name for my project using the Eclipse refactoring tool. I also looked at each file and manually searched for the old package name; in particular, I updated all the links in AndroidManifest.xml. I also used Windows to manually search for the package name, search for a few extraneous links, and update them. My project has a NOWHERE that references the old package name. I also cleaned and rebuilt the project from scratch.

Here's a warning:

11-25 14:20:35.684 Bad call: specified package com.old.package.name.appname under uid 10121 but it is really -1. 

And the header for the error in the catlog left column:

 374 AppOps 

This warning is updated almost instantly, sometimes several times in a millisecond, and completely fills my journal.

It is strange when I install the application on my ASUS TF301 (4.2, root), I do not receive this warning. When I run it on an emulator on my PC (starting with Eclipse), I do not receive this warning.

Answer 1

After cheating with him for a while, I noticed that my logarithm showed the same thing even when the application was removed, which made me believe that the previous version (with the old package name) was not completely removed. So I restarted my phone and now the problem is gone. So the solution: restart!