TTA GO 1.18.01 Apk+obb Patched by DFoX 25/10/2019 with guide

Let's see, since you already had a 2DIN, I thought it was a Smartphone and it gave you the proven solution for the server problem.

[Login or Register to remove this advertisement]

But 2DIN is another movie. I suppose you have read in post 1 the incompatibility of the reported chip, and I know of many users who already had that problem since 1.4, simply could not install it.


Anyway there is something you should be aware of.
There are a lot of users and devices many do not have the obb folder, and it is passed to facilitate the installation all complete
obb / com.tomtom.gplay.navapp / main.xxx.com.tomtom.gplay.navapp.obb
When the original version of Play is obtained and the installation is verified, the content of obb is created and created if there is no obb and at the end of the installation it is deleted.


But the obb folder has not been invented by tomtom, on many devices depending on the apps they have installed, at the root, within Android there is the data folder and the obb folder, example on my device, in this case in external memory I have data, media (com.fundesvs.app.mediaconverter) and the obb folder it contains (com.facebok.katana and com microsoft.office.word) i.e.
the obb folder is system, and if it doesn't let you delete nothing happens, what counts is its content, and if it doesn't appear com.tomtom.gplay.navapp / main.xxx.com.tomtom.gplay.navapp.obb Well, this is it, the obb folder alone does nothing.


At first when passed com.tomtom.gplay.navapp / main.xxx.com.tomtom.gplay.navapp.obb more people confused copied it into data directly, and you don't see what a mess.


Regarding what other browser to use, if you can fit, put both of them to the test and decide, you should go little by little reading and clarifying ideas, because it is something new, the difference between a debutant and a veteran is that he has screwed up 2000 times more that you



Regards

Link URL:

Only the registered members can see the Link URLs. Please Login OR Register.

Link URL:

Only the registered members can see the Link URLs. Please Login OR Register.

Hi coukou



Try what is discussed in post 50, it works on several devices, in the background even if they use Android, manufacturers must do their own thing.


I hope it works for you, master.



Regards friend.

TNX menta for the infos
The smartphone in question is a brand new Samsung Galaxy A51 128 GTB, Android 10.

The first install was a real FIRST install as described in post 1 point 1. Then by launching the app I got "Not enable to connect to TomTom, Try later" message (see image above).

So, I uninstall the app deeply as described in post 1 point 5 and RE install the app::
1. run SD Maid Pro to (Find & remove left over files from uninstalled apps, delete common unnecessary files, remove various cache files)
2. uninstall the app and again run SD Maid Pro
3. check for com.gplay.navapp and navkit_tombstones folders inside both SD Card and Internal card.
4. Restart the smartphone (switch OFF, switch ON) .
5. copy the apk 1.18.01 fixed on the SD Card, then from the play store I install the original TTA GO 1.18.1, UNTIL the map download screen appears, at that point, I exit the application and uninstall (simple uninstall 1)
6. run the fixed apk from SD Card and install it.
Works like a CHARM

However, navkit_tombstones and com.gplay.navapp folders are missing in both internal and external card.
On the other hand, I have com.tomtom.gplay.navapp folders in both internal Card (empty) and external card with full sub folders.

TNX again

coukou

If you have solved it, great.

Thank you for your detailed post, device colleagues will do well.

navkit_tombstones folder contains the crashes that are reported to TT. This folder is created after a crash is verified not before.

If install in external memory Android / data / com.tomtom.gplay.navapp, will also be created in internal memory with empty folders.

You can delete the internal one or leave it, it does not interfere.


Regards Master

xxx1


Wifi or data make the apk work 100% its design is like this.


But wifi or data, are not essential in the operation with the gps sensor of the apk.


As you say it has worked for you, in fact many users with tablets without data, create their route at home, download the radars and start their journey, if they create a new route they are still there, which will not have updated traffic because they do not have a connection.


Do not know what device or what version of Android you use, this is fine if any user had it, could comment.


Another question would be to check how much RAM you have free, over time apks are incorporated and resources are scarce.


From what you say you already have experience in installation and handling, the apk has worked well for you, however if you want to get out of doubt, you should install the original of the company to rule out that it is not the phone.


At this point, it would be advisable to verify an effective uninstallation according to point 5 of post 1


Then, install the original version directly from the Play Store, load the map and make it work with the trial.


If it doesn't work, the problem is on the phone.


If it works, apply the procedure described in post 50.


Regards