Closed GoogleCodeExporter closed 8 years ago
Please see the changelog: http://code.google.com/p/droidwall/wiki/ChangeLog
The signature has changed in the latest version, so you must uninstall the
previous
version first.
Original comment by rodrigo...@gmail.com
on 2 Feb 2010 at 11:21
Hi Dear,
I've already removed the old version. The strange thing is that I've removed
the apk
and config manually because the app manager doesn't see droidwall installed.
Original comment by zioa...@gmail.com
on 2 Feb 2010 at 12:51
Okay, so it seems that the application was somehow not completely removed.
You may try removing the app package using adb:
adb uninstall "com.googlecode.droidwall"
And then trying to install it again
Original comment by rodrigo...@gmail.com
on 2 Feb 2010 at 8:50
Nothing!
I get the follow error:
adb uninstall com.googlecode.droidwall
Failure
I tried to reinstall:
adb install -r droidwall-v1_3_6.apk
510 KB/s (36182 bytes in 0.069s)
pkg: /data/local/tmp/droidwall-v1_3_6.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
I don't know where but something of the old droidwall is there somewhere...
Original comment by zioa...@gmail.com
on 3 Feb 2010 at 8:59
I've find an occurence in /data/system/package.xml
<package name="com.googlecode.droidwall"
codePath="/data/app/com.googlecode.droidwall.apk" system="false"
ts="1265027749000"
version="135" userId="10100">
Can I delete just that line or I must remove the entire file?
Or I can modify that?
Original comment by zioa...@gmail.com
on 3 Feb 2010 at 9:12
According to the docs, this error appears "if a previously installed
package of the same name has a different signature than the new package
(and the old package's data was not removed)."
The important part here is the "(and the old package's data was not removed)".
To avoid messing with your package.xml, you could try re-installing the old
version
of Droid Wall (you can find it in the Downloads section here) and immediately
removing it again along with the data.
This should remove any reference to the old signature and allow you to install
the
new version.
Original comment by rodrigo...@gmail.com
on 3 Feb 2010 at 11:10
zioalex, can you confirm if you were able to install the new version so that I
can
close this issue? thanks
Original comment by rodrigo...@gmail.com
on 22 Feb 2010 at 1:02
Rodrigo I'm sorry but meanwhile I've changed ROM so I can't track that problem
anymore. However now after a fresh ROM installation everything is OK! :-D
Original comment by zioa...@gmail.com
on 22 Feb 2010 at 3:04
Okay, closing this issue.
Original comment by rodrigo...@gmail.com
on 22 Feb 2010 at 3:07
Original issue reported on code.google.com by
zioa...@gmail.com
on 2 Feb 2010 at 11:11