I can confirm the issue with system language in English on my Huawei Y3 - WTF :-q .
BTW: HW rendering did not work with waypoints before 2.2.33+ - fortunately this crappy version I used in Ireland ran perfectly with SW rendering. I must admit that it had been my fault to make an unevaluated software update.
Immediately after the application was updated I encountered one crash when tapping on the map. so to be sure I rebooted my phone.
After that one crash it was stable.
(I switch off my phone anyway at nights and switch it on again in the morning: I don't need it and it is (slightly) better for environment), so most of the time I'm on a "fresh" phone.
I think, I discovered a problem with crash of application. It happens when I changed definition of some buttons on panel with shows when I click map. When buttons are default everythink is OK.
The latest beta versions have been crashing on my android device.
Since testing navigator version 2.2.38 and beyond I am no longer able to load the application. Only version 2.2.37 and previous versions successfully load.
I noticed in the version update description that for version 2.2.38 a new build system was introduced. Could this be the problem?
I receive the following messages
"Checking data files integrity. Please wait."
After a few minutes I receive, "Unfortunately, Navigator has stopped." and then the application crashes.
Rebooted Android 4.4.2 twice. Still same unsuccessful results.
@WillyJ - new build system was real problem - APK version were destroying atlas.idc files. You have to delete your navigator folder and then download everything again. I am not sure if TomTom maps will work automatically...
I deleted the Navigator folder and all its contents. Re-installed version 2.2.44 and was able to retrieve the tomtom maps and the application opened successfully. I started adding back in my POI MCA (import) files that I created through digger and noticed that after 35 of them the application would crash like before. If I maintain no more than 35 of these MCA files the application opens successfully.
This was not the case with version 2.2.37 where I had around 40 POI MCA (import) files working correctly.
Is there a restriction on the number of POI MCA (import) files in the latest beta version?
Hi Lubos, having serious problems across the board with build 2.2.44. Keeps crashing. I've never had so many problems on one build before so a bit disappointed as I assume that you at least do some alfa testing before releasing for beta. One serious problem is when selecting any area of the map, whether a POI or just an area, the program crashes. In fact, I have had to give up on testing as I can't get it running stable. Is a new build due soon to fix this as it is obviously not fit for purpose? If not, then please explain to all how we can revert back without losing our TomTom maps, POIs, favourites etc.
After re-installing version 2.2.44 having deleted the Navigator folder and its content, I retrieved the tomtom maps through the map download. I started adding back in my POI MCA (import) files that I created through digger and noticed that after 35 of them the application would crash like before. If I maintain no more than 35 of these MCA files the application opens successfully.
This was not the case with version 2.2.37 where I had around 40 POI MCA (import) files working correctly.
Is there a restriction on the number of POI MCA (import) files in the latest beta version?
Hi Tomas, sorry I didn't get back to you earlier. My crashes happened when clicking anywhere on the map. It would start to launch the location menu then crash. I now have version 2.2.51 and all appears OK now. Obviously the last build had problems.
Option to change navigation arrow colour is not available with Software renderer (or Automatic mode in my case). Is only available with Hardware renderer. I thought that both renderers should have the same functions and features. Is this difference by design or an oversight?
Changed colour using HW reverts to normal when switching back to Automatic / SW render
Today I started my daily route to work with 2.2.54. As mostly I've choosen the destination onmydrivewaytothegarage-the positionisabout 30m outside the road. GPS normally is always on and the initial position on my driveway had been correctly shown.
When I started the program mostly had shown a frozzen picture and jumped to a new position from time to time. Sometime new position was not even near the actual position on calculated route. Normal navigation started after 20min and about 17km on the road.
Hi @lubos - somehow a couple of the latest updates have not reached me via the testing program.
Any chance you can update the download link with v2.2.61
Also while navigating (planned route) touching the screen to bring up the menu from the bottom (in my case to clear a missed waypoint) is not very responsive ie it takes quite a few tries before it works - sometimes i have to stop and do it.
It responds very quickly while stationed or in non-navigating modes.