Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 15 12311 ... LastLast
Results 1 to 10 of 143
  1. #1
    Master Downunder35m's Avatar
    Join Date
    Aug 2010
    Location
    private
    Posts
    609
    Rep Power
    375

    Guide Tomtom "unable to connect" or simply ending without any error - and possible fixes

    I never had a real problem getting the Android versions of TT to run on various devices - until I updated my Nexus7 (gen2) to Kitkat.
    Since I fixed it I thought I put all possible causes and fixes in one place.
    All does not mean all! Only the problems that I'm aware of and was able to fix, so don't blame it on me if you still can't get it to work

    One of the most common cuases of problems for noobs is simply a wrong installation.
    (I assume you got the right APK and map as well as the correct activation if needed)
    Might sound hard, but if you already tried without luck it is best to fully remove Tomtom before proceeding!
    To make sure you got the folders right I recommend to install the APK only and to start it.
    Tomtom will create a folder called "tomtom", within there the "com.tomtom.COUNTRY-NAME..." folder an all content (later on).
    If all goes well you should see this Tomtom folder on your SD - if not, don't panic!
    Your Tomtom will complain about being unable to connect to TT - that is normal as we have not added any content yet.
    On many devices there will be no Tomtom folder being created on the SD,
    so copy the "Tomtom" folder from your download (or that you created for a non-Android map) to your SD and start TT again.
    In most cases the app will find the content folder on the SD and it just works.
    If not:

    The missing dot...
    I noticed in many cases that the .metadata.xml file does not have the leadin dot, so it is only metadata.xml - TT will not work without the dot in front, so if missing simply change the filemane
    Ok, still not working?? Keep reading...

    Sometimes it happens that either you or someone else messed up the activation.
    Possible causes are:
    The map was activated with the deviceID of a different APK than what you use - if unsure simply create a new DCT inside the map folder with the correct activation.
    You activated again with correct values but you did not delete the old DCT file first - some keygens don't overwrite existing DCT files! So if in doubt delete or rename the DCT file before you activate again.

    Last but not least....
    Of course it can also happen that for some reason you downloaded an unpatched APK from dubious sources (that we don't support anyway) or that you try to use a map that is not compatible.
    In general all full featured maps for the GO series and of course the Android maps can be used, not other map versions are support by the Android TT version.

    Hard core....
    In my special case all of the above was ruled out and I even tried the content folder from a working installation on a different device.
    Modifying the .metadata.xml like suggested in other threads (like setting the size to zero or adjusting the path) only resulted in two things:
    a) "unable to connect" or
    b) the app closed with a sorry note.
    I knew the apk is good, same for the content on the emulated SD, so what was wrong?
    Seemed Kitkat works a bit different or my Nexus just has a special tick:
    Checking the "data/data" folder in the root I noticed the same folder structure that was on the SD only there was no content.
    Copying all from the SD into the data folder worked but was not a solution I liked.
    After a few experiments I noticed that only the .metadata.xml needed to be copied from the SD to the same location inside the data folder in the root to make TT working.
    Although I alread got feedback that other users dont have such problems on Kitkat I though I share my findings anyway as I was able to replicate it 3 times after a full factory reset.
    On the other hand, after flashing the Cyanogenmod onto the Nexus TT installed as usual with no fuzz at all.

    I hope this might help someone in case nothing else seems to work.
    Password for all my files: downunder

  2.    Advertissements


  3. #2
    VIP Master windrider42's Avatar
    Join Date
    Sep 2009
    Location
    Alberta
    Posts
    11
    Rep Power
    0

    Default

    Ok I had troubles getting it working on my Samsung Galaxy S5, so I bought it

    On the phone, there is Phone\Android\data\com.tomtom.uscanada\files but then its empty folder

    and on my SD card its installed at Card\Android\data\com.tomtom.uscanada

    So if that helps anyone I am not sure.

  4. #3
    Junior Member
    Join Date
    Apr 2014
    Location
    Sheffield
    Posts
    2
    Rep Power
    0

    Default

    Hi windrider42

    Could you tell me what is in the folder on the SD card for your us maps, i.e. the folder structure? I've tried moving the data into Card\Android\data\com.tomtom.ukireland (I have the UK App) but it refuses to load the maps. It will only work from internal memory in the standard tomtom folder on the root for me

    Thanks

  5. #4
    VIP Master windrider42's Avatar
    Join Date
    Sep 2009
    Location
    Alberta
    Posts
    11
    Rep Power
    0

    Default

    Quote Originally Posted by TickPick View Post
    Hi windrider42

    Could you tell me what is in the folder on the SD card for your us maps, i.e. the folder structure? I've tried moving the data into Card\Android\data\com.tomtom.ukireland (I have the UK App) but it refuses to load the maps. It will only work from internal memory in the standard tomtom folder on the root for me

    Thanks
    Its the whole structure on sd card. I would have to take screenshot to show you. But from what I understand there is an update you need to install to get it working on SD card

    [Only registered and activated users can see links. ]

  6. #5
    Junior Member
    Join Date
    Dec 2010
    Location
    uk
    Posts
    2
    Rep Power
    0

    Default

    Quote Originally Posted by TickPick View Post
    Hi windrider42

    Could you tell me what is in the folder on the SD card for your us maps, i.e. the folder structure? I've tried moving the data into Card\Android\data\com.tomtom.ukireland (I have the UK App) but it refuses to load the maps. It will only work from internal memory in the standard tomtom folder on the root for me

    Thanks
    I finally got the UK maps to work. Using A771LA's tomtom apk:
    Uninstall tomtom, delete any com.tomtom folders that you have on the internal phone and external sd card memory
    Rename the com.tomtom.ukireland folder you downloaded to just com.tomtom
    Inside that folder there is a folder called files - - you need to make another folder in there, also called files and transfer all the contents of the original files folder to the new files folder (i.e. your directories should now go com.tomtom>files>files>United_Kingdom_and_republic_of_ireland
    Rename the _metadata.xml to .metadata.xml
    Edit the metadata.xml to replace references to com.tomtom.ukireland to just com.tomtom (don't change the URL path)
    Now copy the com.tomtom folder to the android/data directory of your SD card
    Install tomtom apk but don't run it
    Reboot your phone
    Now run tomtom and it should work

  7. #6
    Member Pancio's Avatar
    Join Date
    May 2007
    Location
    poland
    Age
    36
    Posts
    18
    Rep Power
    0

    Default

    i found this solution somewhere in the internet, meaby it will be helpfull, cheers.

    How to solve unable to connect error

    1. If you installed the navigation and it shows the unable to connect error, go into application manager, clear all data for installed navigation and uninstall it, remove the tomtom directory from the device
    2. Copy your tomtom .apk and tomtom folder with map on your android device memory (i.e there where you have: "android", "download", "DCIM", "Picures" etc.)
    3. Before you start installing TomTom, switch your phone offline by setting flight mode to ON or disable data on your phone/ tablet
    4. Now you are ready to install, find the navigation .apk on your device memory and start installing it, when installation finishes click “ready” to exit installer, DO NOT PRESS “OPEN”!
    5. Restart your device
    6. Keep you device offline and open the TomTom navigation by using the icon on your phone / tablet
    7. When application starts without the unable to connect error, exit the application, enable data on your phone or switch off flight mode and you are done, enjoy the TomTom again
    [Only registered and activated users can see links. ] - Amiga EXE Games
    [Only registered and activated users can see links. ] - Best romhacks, translations and public domain roms

  8. #7
    Junior Member
    Join Date
    Jun 2014
    Location
    london
    Posts
    1
    Rep Power
    0

    Default

    thanks for assistance, one thing that worked for me after fustration on sony z1 and samsung tab 3 was when i transfered files to sd directly then to internal memory rather than using a cable to put files on sd or device, this may help other people

  9. #8
    Junior Member
    Join Date
    Nov 2010
    Location
    uk
    Age
    31
    Posts
    1
    Rep Power
    0

    Default

    After tried millions of times, I finally got it working. It turns out to be a very very stupid error.
    I am Mac user so have to use Android File Transfer to upload all files to my phone.
    But AFT would not upload .metadata.xml - just miss the file and would not give any error message....
    At the end I upload the file via dropbox and finally TT works....
    WTF!!!!!

  10. #9
    Member +
    Join Date
    Oct 2007
    Location
    Italy
    Age
    63
    Posts
    41
    Rep Power
    15

    Default

    This solved for me: inside metadata, after the </download>, set <size>0</size>...

  11. #10
    Senior Member
    Join Date
    Jun 2011
    Location
    at Home
    Posts
    104
    Rep Power
    7

    Default

    "The map was activated with the deviceID of a different APK than what you use "
    how do I find the deviceID of an Android API to generate a new .dct ?
    thanks

 

 
Page 1 of 15 12311 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.