Tomtom_Go_Navigazione_e_Traffico_v1.17.3_Build_2124_Patched_By_DFoX

Versions I always have used were probably signed with Android testkey
However, a few versiosn ago, I found my self needing to sign manually to update. Hard to recall when this started...

Did you once change the signing from testkey or maybe it is a version I got somewhere else caused it ?

Now, to not uninstall and reinstall + download maps again, I am left to manually sign with standard testkey

Note: most releases use the testkey, so not sure what signature you are using by the way
Using testkey ensures compatibility between releasers, even if with TomTom you're the only one left for now :-)

So, here's the apk signed with the classic testkey
[Only registered and activated users can see links. Click Here To Register...]

Many thanks for your work

All we are doing is causing more problems with doing this.

As you can see the 2 apps are not the same size.

Your version is the first one and the second one is from DFoX.

Spoiler: Not the same

[Only registered and activated users can see links. Click Here To Register...]

Plus you should like I said before start a new thread with your version of TomTomGO.
Remove any reference to Patched By DFoX.

Because you have changed the signature of the app.

Put you name there so user's know right off the bat which app they are dealing with.


See app below:

Spoiler: DFox

[Only registered and activated users can see links. Click Here To Register...]

Quote:

---

Originally Posted by asprin624 [Only registered and activated users can see links. Click Here To Register...]

As you can see the 2 apps are not the same size.
.....
Plus you should like I said before start a new thread with your version of TomTomGO.
.....
Put you name there so user's know right off the bat which app they are dealing with.

---

Please don't jump in when you don't understand what I am talking about, neither answer any of the questions I do
Release is proper untouched from DFoX, no unpacking, just signed like any noob can do.
If you check zip content, you'll see there's no binary difference in files except the signature

It fixes the issue many are having to uninstall/reinstall on updating

Best friend gztr567

I have verified your version on various devices and android versions and it is not suitable to install over another version without any problems. Better to test well on different devices from now on before posting them here. The version of .v1.17.3_Build_2124_Patched_By_DFoX-FIXED1 is easy to install on different devices without problems .

Not on mine. Huawei p8 lite 2017 android 8

So far the versions of 1.17.2 and 1.17.3 provided by gztr567 (thank you) are the only ones that have installed correctly over previous TomTom Go versions under Android 6.01 on my Nexus 7 and Moto G3. So for me, the original and patched versions released by DFoX won't install over previous version of TomTom Go on my devices.

Cheers, Ian

I have tested DFox versions on all Android versions and have never had any problems installing over previous versions.

Yes his first versions on 1.17.2 had problems but were corrected ASAP.

I never install any app the minute a new fix comes out.

If 1.17.1 is working I wait a couples of days before I update.

Seeing this fix was only for problems with Android PIE there was no real rush to update.

Now that the Original version 1.17.2 had problems TomTom released version 1.17.3 which has not been posted yet on their forum or in some countries Google Stores.

But I must repeat there has never been any problems with DFox posted.

If it will not update over a previous version I wait.

And sure enough DFox found the problem and fixed it.

Staying with one version is the safest way to go.

I have seen so many splashes in the pan being posted here only to just fade away because of poor testing of there fix or not showing up to support for the app they posted when a user's have problems.

Stay with a proven version and you can not go wrong.

It is the rush to have the latest version and in most cases not even needed for every users Smartphone.


Then out of the blue other versions popup saying I fixed the problems when in reality there were no problems just some mistakes from DFox which were corrected ASAP.

I will only comment on one thing because to some extent I feel alluded to when you mention this:
I have installed versions exclusively of DFoX from the first moment and I am sorry to say it, but I have not always been able to update one directly on the other ... Is it really a problem? No, it's just annoying to have to do the whole protocol over and over again, but anyway, that's the way things are...
There are people who, in good faith, try to fix it in their own way, thanks to them too...
I just wanted to make this comment. Regards

Enviado desde mi ASUS_Z012D mediante Tapatalk

Like the most here, I never have any trouble with DFoX build.
It runs proper every time. Because He use the same Sign in the apk all time.

This is a so irrelevant debate mixing ignorance and paranoia
We're talking about signature, not a different release.
Just rename the apk to .zip and do a binary compare. This will make some people here understand what's an apk and what parts of it are the binaries, the resources and the signature.

I do not plan to post another version in the future here anyway, so relax. The post was meant to the OP so maybe he can consider using the stock and most used android testkey instead of some custom keys.

End of debate and please only get my signed apk if you are bored from uninstall and reinstall on each update. If you're not concerned, just enjoy what you have. If you are paranoid, just do the compare and stop bitching without even verifying.

Again, many thanks to the OP for patching TomTom, keep up the good work. No credits to me as I did not patch a bit :-)