After a minute or so, the browser has access to the Catalyst position and is able to refresh it.īut if I disable "Connect" in TMM and run the steps mentioned above, the problem still exists. TMM shares current positions, but in Firefox, I get a Timeout. Unfortunately, disabling the default phone locations, did not help to fix the error: all devices should be supported according to Trimble Catalyst | Compatible Devices).and Chrome 64 (not recommended, see Mock locations and browser behaviour with Trimble Mobile Manager (TMM) and Trimble Catalyst ). ![]() īut "disconnecting" (in TMM, not USB/device) and reconnecting is the fastest way to reproduce the error. closing the TMM app - open it again, connecting, enable sharing.locking the screen - waiting some time - unlocking.The logfile shows a message: "Publish old positions". Only "internal GPS" positions (you can tell by the accuracy) are availabe. TMM Enable "Connect" again, wait till TMM has a position (sharing is still active)Īfter 1-3 iterations, in step 1, the "Trimble position" is not availabe to the browser, although TMM shows position updates.Browser: "Get position": after a few clicks, I get the less acurate "internal smartphone GPS" position => OK!!.Firefox (JSFiddle website) also uses these positions and updates them after every click on "Get position" => OK!! TMM working, delivers and shares valid, current positions.The Trimble position gets "lost", when I perform the following steps: To test the behaviour, I've adapted a JSFiddle: Geolocation API Demo - JSFiddle When I "lose" the "Trimble position" in the browser, I can't manage to get an current, valid Trimble position again. I have encountered some odd behaviour concerning the browser position:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |