you have change the global_cfg 🤔
Phoneme; you have a WinCE device 🤔 Android iGO, then a problem 😉
Question: Do you constantly change card providers to create problems for yourself 🤔 In December 2023 it was TomTom 😮😒
Sorry if I crossed any lines here, but I have never had this problem before until installing the Australia and New Zealand HERE 2023.Q2 maps so I thought it was on topic. I will search the phoneme posts.
Last edited by Boki; 28th February 2024 at 07:40 AM. Reason: unnecessary quote removed
you have change the global_cfg 🤔
Phoneme; you have a WinCE device 🤔 Android iGO, then a problem 😉
Question: Do you constantly change card providers to create problems for yourself 🤔 In December 2023 it was TomTom 😮😒
Last edited by rondoan; 29th February 2024 at 09:01 AM.
---
ex calipoint say: my Knowledge of today is what I read yesterday 🧐😉
I did change the global_cfg but that made no difference. I have both Tom Tom and Here maps on my gps. I tried the Tom Tom phoneme as I had never had the problem before upgrading the maps to Here 2023 q2 and it did work better with the TT phoneme but still was not right. I am not sure what you are referring to with December 2023 Tom Tom. Deleting the phoneme did solve the problem and all seems good now. I did search for info on phoneme on the forum which is why I thought it may be relevant to the phoneme being uploaded with the Here maps. My bad as I had no idea till now that phoneme causes problems with Android Igo. This is how we learn.
In fact, phonemes cause a problem with here maps. They don't make for TomTom ...
You should also pay attention to the lang file
Thanks Boki, All seems to be working well now. I will never again install the phoneme files with updated maps.
Bookmarks