Stabitilité signal GPS avec twonav 6
Problème de stabilité signal GPS avec twonav 6 sur GPS trail 2 plus. L'acquisition diu signal GPS est beaucoiup plus longue qu'avec la version 5.9 précédente. Autre point : l'écran du GPS reste figé après 2min puis l'écran d'acceuil "powered by Twonav 6 s'allume". Ensuite vous démarrez votre enregistrement et puis de nouveau le message "activité en cours" s'allume et le GPS se réinitialise de nouveau avec le message "Powered by twonav 6". Je n'avais absolument aucun de ces problèmes sur la version précédente. A quand la mise à jour pour remédier à ces bugs.
-
Bonjour,
Ici c'est un forum d'utilisateurs, TwoNav ne repond jamais ici..
Je t'invite a utiliser le lien : envoyer une demande en haut a droite de l'écran
Il y a un autre post ou un utilisateur signale que la version TwoNav 6 mise en ligne ne serait pas la bonne,
Il y a d'autres bugs significatifs de signalés :
- l'audio qui ne fonctionne plus,
- Un redémarrage intempestif,
- J'ai utilisé TwoNav 6 sur un Terra trois fois sans constaté le bug que tu signale ni un autre..
Par contre avec TwoNav 6 il est maintenant possible de créer des itinéraires avec ou sans Road book, soit sur l'écran de l'application soit sur l'écran du GPS. Si tu utilise dans le GPS un RoadBook creer via l'application il y a des artefacts.
Remonte le cas que tu rencontre via le lien envoyer une demande mais avant tu met ton GPS sur ON laisse le demarrer et fait un rapport d'état il va partir directement chez TwoNav ce qui va leur permettre de voir ce qui s'est exactement passé dans ton GPS.
Cdlt
-
Ok , merci..
Je viens de reproduire ce bug sur le mien, dans des circonstances un peu différentes .. Il se ferme et redémarre, la trace du défaut dans le log file.
MT [E] Error_Vectores_DG_x: VDGerr:7--tot:0,index:-1,max:500,delta:-500 THREAD MAIN 1952575488
Reportez votre cas à TwoNav
Complément, reproduit en faisant la même manip sur un TERRA, le défaut est nouveau dans la dernière version TwoNav 6
Le Terra est un peu plus bavard, c'est une banale erreur de dimensionnement de variable qui peut donc se produire dans n'importe quelle partie du code
2025-05-15 13:00:44 [pid:506, thid:1952292864, thspid:506] MT [E]
Error_Vectores_DG_x: VDGerr:7--tot:0,index:-1,max:500,delta:-500 THREAD MAIN 1952292864argc 1 argv[0] (CompeTwoNav)
Exception caught in TwoNav. const char*:
Calling SDL_Quit.CDlt
-
Bonjour,
Le passage d'une version majeure (v5) à une autre (v6) est rarement sans soucis au tout début.
En production, il est prudent d'attendre quelques semaines (ou mois) que le firmware se stabilise.
A savoir que cette première version 6 publiée est la 6.0.5, la release candidate qui corrige des problèmes remontés est actuellement la 6.0.8 (vous n'avez pas vu les 6.0.6 ni 6.0.7, pas plus que les version 6.0.0 à 6.0.4). Il y a donc espoir qu'elle passe en production avec défauts corrigés prochainement.
Tout en confirmant qu'il ne fallait peut-être pas se précipiter à installer le premier firmware version 6 dès sa sortie ... ;-)
La version 6.0.5 production est sortie prématurément à mon avis... en même temps, c'est un peu les utilisateurs qui font les tests à grande échelle, il y a tellement de cas d'usages qu'il est complexe de faire des tests exhaustifs préalables... c'est malheureux, mais que ce soit des GPS ou n'importe quel équipement HiTech aujourd'hui, on ne passe pas à coté de la nécessité (obligation) de mettre à jour les firmwares après que le produit ai été mis en vente...
Même les derniers processeurs Intel sont bugués (et grave) ... !Cordialement,
-
Hello Everyone....
I apologize in advance for the long post that may not contribute anything to the discussion or solving the problem, but I want to vent my anger at TwoNav and the entire technical support.
I’ve been using the TwoNav Cross device since the first model was released, so it's been several years now. I replaced my old and reliable Anima+, which actually worked better – it was faster, smoother, and had instant GPS and location connection.
From the beginning, I had problems with the Cross: it was extremely slow, the menu lagged and responded poorly, as if the processor was underpowered or the device didn’t have enough RAM. As a result, the device was far from smooth. Over time, new software versions were released, which brought slight improvements, but I always maintained – and even showed in comparison videos of the Anima+ vs. Cross – that the device is simply slow and unstable. It frequently crashes, resets itself, has very slow menus, long loading times for maps, and takes ages to acquire a GPS fix and position.
I sent it in for service – they reinstalled the software and restored factory settings – but the same issues returned shortly after.
Now, with the new 6.0.5 firmware update, I honestly feel like throwing this device in the trash. Today was the first time I did a longer route using a previously saved track since the update. The device restarted itself (shut down) about 10–15 times. Acquiring GPS + GLONASS signal took over 30–40 minutes. And once it finally restored the route, it reset again. The menu is slower than old Nokia phones from the '90s. Today, my patience completely ran out. Anything I try to turn on or change in the menu takes forever or doesn’t respond at all.
Did anyone even test this software before releasing it? Maybe it works on newer devices, but the Cross simply doesn't function properly. I can record a video showing how slow and laggy everything is. GPS fix takes forever – especially when traveling to a new location different from where I usually ride.
This is absolutely unacceptable. Here’s a strange but relevant comparison: my old Garmin Forerunner 935 watch acquires signal instantly, and my old Anima+ (which I still own) does the same. But the Cross? It makes you wait endlessly.
I’ve reported this multiple times. The explanation that “GPS + GLONASS means more satellites to connect to” – really? Then why do other cheaper devices connect instantly, even though they also use those satellite systems?
I want to use the Cross and stick with TwoNav, because I prefer the quality and appearance of your maps over Garmin’s. But I’m tired of constantly struggling with the device, never knowing whether I’ll even be able to use it properly when I go somewhere. TwoNav – I’ve simply had enough. This is my third and last device. I’m switching to the Garmin Explorer 2.
Best Regards Jacek R.
-
Hello,
Regarding Twonav version 6, there was an unfortunate delivery with a defect that caused reboots. This is expected to be fixed in version 6.0.8. I've done several outings with this version without experiencing any crashes. I've never noticed any particular slowness in the operation of my GPS devices. Two weeks ago, we did a joint activity with three TwoNav GPS owners (Cross +, Terra, ROC) and it went well. Good luck with the Edge Explore 2 because on other forums, some also have complaints about this GPS. I have two TwoNavs, a TERRA and a TRAIL 2; they both work perfectly. Then, when your CROSS comes back from repair without actually being repaired, you have to request a replacement under warranty; it's possible. You also need to properly support your repair request file because it is possible that the after-sales service representative does not understand the nature of the defect (this is not specific to Twonav). With some users we have built files to obtain a replacement with a new one and each time it worked. In principle, if you make a status report by cutting the WiFi it will remain blocked in your GPS. You go and look for it with your PC, unzip it and the defect should be traced. At worst, leave a way to contact you in order to use this status report to support a repair or replacement request if you have kept the previous traces of sending it for repair. 3:30 this morning without any defect!
Best Regards
-
@ Jacek Rydecki This issue was seen quickly, but for some unknown reason TwoNav is not releasing the fix.
-
Hi Jacek, I'm not sure if you got a broken device from the start. As Thierry wrote, they are working on a fix for the reboot issue and are very near to publish it. Though that does not explain the laggish menu. If you want some more specific help, it would be necessary to know which maps&maptypes and track and waypoint files you have opend while your problems arose.
I myself own several Cross devices and I'm quite happy with them. Satfix is acceptable too with all of them.
Edit: But if bigger mpv maps are opend, the device gets soon to its limits, so don't use them, create mpvf maps and rename them to vmap.
-
Jacek,
There are two things to distinguish in your message: version 6 of Twonav, and the Cross.
The first version 6 of Twonav contains bugs. This is unfortunately the case with many software programs these days; it's unwise to install new major versions too early.
But your disappointment comes mainly from the Cross: for me, it's the worst GPS Twonav has ever produced. I had a Sportiva, an Anima, then a Cross: I was very disappointed, and I ended up parting with it. Hardware problems (unreliable USB port), the worst GPS reception I've experienced, etc., all of this is certainly due to poor internal design. Since then, I've had a Cross+, and it's night and day. The Cross+ is a good machine, but not the Cross.Best regards,
-
Hi guys,
@Bernard – you confirmed the feelings and conclusions I’ve had over the past four years regarding the Cross device. I’m honestly frustrated with how TwoNav and their technical support team treat users.
I’ve reported issues many times: slow menu performance, delayed screen response when changing direction, and very long GPS acquisition times in new locations. And what did I hear in response? That the device is working properly, they restored it to factory settings – and that was the end of the discussion.
I’ve learned to live with it, but I’ve never felt satisfied – quite the opposite, every trip came with stress and frustration. This is already my third device of this type. Should I send it in for service? There’s no point – the warranty has expired, and I’m not going to buy a newer version just because the company never admitted the truth: that the Cross was flawed and simply runs slowly and sluggishly.
As for maps – I only use topographic maps of Poland and Germany, with an OSM overlay. The issue I encountered recently is clearly software-related. The map I was using at the time was a topographic map of Czechoslovakia.
Another issue is connecting the device to macOS – it simply doesn’t work anymore, because the system no longer recognizes it. Previously, using older software, I could access and browse files on the device. Now, that access has been completely blocked for quite some time. Maybe Windows still detects it as a drive, but macOS Ventura doesn’t see it at all.
I’m sorry to share so many negative experiences here, but honestly – it shouldn’t be this way. We, the users, shouldn’t be the ones testing the software and endlessly waiting for someone to finally fix it. I won’t even go into the fact that the first Cross model was – and still is – a complete failure. They tried to convince me it was a great product, and that long GPS acquisition times were “normal.”
Now I know that even the latest software updates won’t improve the performance of the first-generation Cross, because the hardware itself is simply weak and unfinished.
@Thierry – thank you for all your help in the past. You supported me several times and tried to explain many technical issues. I truly appreciate it.
Will I buy a Garmin Explorer? Time will tell – I plan to test it. I ride a lot. With the Anima+, I completed the TransAlp twice, and with the Cross I rode the Tour du Mont Blanc and many other long-distance trips. I always managed to reach my destination, but looking back – every trip involved some strange issue or technical failure with the Cross...
I remember once in Livigno, I waited 4 hours for the GPS to lock onto a signal... unbelievable. A whole day wasted.
What’s left for me? Just wait for new, improved software and pretend I’m happy.
The only upside is that on my short daily rides, it basically serves as a trip counter. :)
Greetings to all of you,
Jacek R. -
Hi Jacek,
"Should I send it in for service?"
IMHO, probably useless, try to negotiate a replacement with a Cross+
"Will I buy a Garmin Explorer?"
Hmmm... If you are very used to Twonav's ergonomics, you may be very disappointed... Garmin is a very separate and very closed ecosystem. And abandon the idea of easily putting your cards there.
It would be better to replace it with a smartphone with a good GPS, and an application such as Locus or OruxMaps whose features are excellent.We have to face the facts: the era of GPS devices like those from Twonav is over... Besides, Twonav doesn't seem to be planning a new model for a long time... or ever...they only seem to be interested in the software.
Best regards,
-
Thank you for your response. I seriously doubt that TwoNav would agree to replace my Cross device with a new Cross+ one, even with a small additional payment. I remember losing my Anima+ during a race once — the mount was very weak. All I received at the time was a 5% discount on a new device, and that was just a week before my planned TransAlp trip.
Buy a new Cross+ for 700 euros? Never in my life — that’s far too much money. And since, as you mentioned, the company seems to be pulling back from developing and improving its devices, it’s safe to assume things won’t get any better.
What can replace it? Probably only one of the big players like Garmin. :(
Still, I’m very attached to TwoNav’s maps — they’re excellent. I’ve bought quite a few, and some of them look just like traditional paper hiking maps. I really like them, and that’s why I’ve always chosen TwoNav.
I only use Garmin as a running watch and bike computer. But I love to travel, explore, discover, and follow unknown trails — and that’s why I always went with TwoNav maps and devices.
Today has been a really tough day. This whole situation has brought me to the edge of my patience.
I won’t hesitate to write this in an official email to the manufacturer and ask for a solution to the problem.Best Regards Jacek R.
-
Hello,
It's a shame to have waited so long. We could have had it replaced with a new one; it's still possible with concrete evidence.
Your CROSS most likely has an excessively high internal RFI level. This is a combined effect of the internal design and the accumulation of RFI levels in the components. This is a very complex technological problem that is not specific to TwoNav. However, it is well documented and justifies a replacement. This phenomenon clearly explains the difficulties receiving satellites. A standard after-sales service is not equipped to understand this type of problem; you should contact the engineers responsible for development.
Combined with the bug in the latest version of TwoNav, the exasperation you are expressing is justified.
Could you prove the slowness, either in operation or in capturing satellites, with photos or videos to support a replacement request? Send this proof to customer service with a replacement request and forward it to me at the same time to support your claim (you still have my email address). If you request a replacement, avoid requesting a CROSS+ if possible; it's better to request either a ROC or a TERRA (less battery life).
As Bernard at Garmin says, the Topo hiking map is not included with the cycling GPS range; it's a Garmin Velo map. You need to install a free map such as FreizeitKart based on OSM data or an OPENXXXX map.
Best regards
-
Bonjour,
Depuis son acquisition je n'ai jamais constaté de lenteur d'acquisition des satellites avec on Trail 2, la durée BOOT inclut est inférieure a 2 minutes (1'40").
C'est probablement une problématique d'utilisation exposée dans ce tutoriel.
https://blog.utagawavtt.com/fr/blog/comment-localisation-gps-rapide
Cdlt
Please sign in to leave a comment.
Comments
18 comments