tripmaster 2.3- suprise?

[just4fn]

tripmaster 2.3- surprise?

The new vesion fix's some memory leaks but also a little surprise. what is the surprise?

 

[imokah]

My guess is pale yellow numbers and lettering on the custom night screen.

 

[pianoCM]

I haven't seen any "good" surprise yet but I've experienced some "bad" surprise. It could well be my specific case only.
With v2.0, turnt it on, everything seemed LOCKED (means good) after receiving satellites.
With v2.2 (I skipped v2.1), turnt it on, after receiving satellites, staying at the same spot, no moving, Altitude display was OFF, just displayed some randome number (and just that number only, no change) unless I started moving, then it picked up and display "seem to be right" number.
With v2.3, turnt it on, staying at same spot, two bad things
1. Altitude displays inconsistently, seconds ago it shows 55ft, then suddenly shows 256ft then 20" later, shows 150ft. Basically, it popping around
2. Even staying at the same spot, somehow the everage speeds (both for driving and entire trip) keep rolling. Max speed still shows 0 (which is good) but other speed displays jumping.

 

[canderson]

2. Even staying at the same spot, somehow the everage speeds (both for driving and entire trip) keep rolling. Max speed still shows 0 (which is good) but other speed displays jumping.

Sounds like what I recall as the latter of the dual display of a) average speed when moving vs. b) average speed inclusive of stops. Last time I fired it up (2.2?) it had both. Sure you're not looking at the latter? It'll keep changing when you come to a halt. The former will not.

 

[imokah]

My second guess is: the world globe inside the compass has a 3D affect.

 

[runarg]

My second guess is: the world globe inside the compass has a 3D affect.

The compass does NOT have a 3D effect. It is the same as it always have been. You must be referring to a background image on the web site? That has also been there all the time.

 

[pianoCM]

It'll keep changing when you come to a halt. The former will not.

That's true when you "come to a halt". In my case, the travel distance is equal to Zero, therefore, velocity should be at Zero as well. I don't expect it pumping, jumping at all.

Another note: after a little trip outside, the Altitude and Inclinometer somehow, lagging behind a lot AND display horribly wrong. I was driving on the flat road (or .5% max), at one point, it showed 129%.
Also, these 2 numbers (Altitude and Inclinometer) are overlapped.

 

[pianoCM]

Few others "bad" surprises
+ tracksaving as "new" but it keeps working as "append"
+ autologging as "no" but every time turnt on, it's automatically enable logging.
+ with default setting (trackcourse, trackdistance, trackperiod), waypoints seem to be created too many.

 

[a720user]

looks like the behavior of the accelerometer has changed.

the app seems to be working perfectly for me...

 

[roussillat]

Hello,

The good surprise is an esthetic point : look carefully at your screen and compare it to the screenshots on my site.

For the bad surprises you've noticed :
- everything related to values changing although you're not moving, it's not related to Tripmaster but to a poor GPS reception that makes GPS values change. If you'd gone in Tomtom app at the same time, you'd have seen the map moving.
- for tracksaving, I'll will investigate this, same thing for autologging
- for display lagging in height and inclinometer, I've noticed that too and will investigate it.

 

[roussillat]

Hello,

Some important informations about several problems detailed here :

- altitude in Tomtom is everything but accurate, especially when the Tomtom is not moving and if GPS reception is poor. The more satellites you get, the better the altitude information will be. When staying at the same GPS position, the altitude may change without any reasons. If it changes in Tripmaster screen, it's because it has changed in the GPS module output and I can't do anything against that.

- the total average speed will change when you stop and it's normal : this total average is the result of the division of the distance by the total time of the trip, including stops. So, it will change constantly whether you're moving or not. The moving average speed will not change when you stop.

- some known bugs around the touchscreen makes that when you launch Tripmaster, it does catch the touchscreen action that has launched it and if Tripmaster's icon is the upper left corner of your menu, Tripmaster will start and launch the logging, which you can take for a sort of autologging function... Same thing when you stop Tripmaster, which can produce the corresponding action in the nav. screen, because the touchscreen action is not deleted after Tripmaster catches it...

I will investigate all this in the next days.

 

[pianoCM]

Hello,

The good surprise is an esthetic point : look carefully at your screen and compare it to the screenshots on my site.

For the bad surprises you've noticed :
- everything related to values changing although you're not moving, it's not related to Tripmaster but to a poor GPS reception that makes GPS values change. If you'd gone in Tomtom app at the same time, you'd have seen the map moving.
- for tracksaving, I'll will investigate this, same thing for autologging
- for display lagging in height and inclinometer, I've noticed that too and will investigate it.

Item1: reasonable explanation
Item2: don't waste your time on this just yet. Give me another day or two. I almost come down to the conclusion that was actually my mistake (or mis-read). It hasn't behaved like I described in the previous post today. I think it happened (as posted) when I just turnt the Tripmaster off but actually not deactivate log so next time, turn on, it's automatically "append" to the previous tracking log. I highly think it was my mistake, I'll pay more attention on activate/deactivate log this time.
Item3: you definitely need to look into that.

 

[roussillat]

Item3: you definitely need to look into that.

For this display lag, I'm afraid it will be complicated to understand it... I have added in Tripmaster v2.4 (soon to be delivered) a colored indicator of GPS data queue, to confirm or infirm my hypothesis. I will make some deep tests before delivering this version.

 

[roussillat]

Hello,

For this altitude display lag, I need some betatesters to investigate the problem. Feel free to send me a private email, with your email, if you've noticed the problem and want to help me to understand it.

 

[Statman]

Perhaps it goes without saying that many of us appreciate your efforts. I have been using tripmaster for some time now and it is quite nice. Thanks again.

 

[just4fn]

I see a 1/2 a clock behind the time on the lower part of the screen. That may be the surprise.

I have moved the tripmaster icon to the lower part of the screen instead of the top middle and my logs will still activate when pressed. I have no autologging checked.

 

[roussillat]

I see a 1/2 a clock behind the time on the lower part of the screen. That may be the surprise.
I have moved the tripmaster icon to the lower part of the screen instead of the top middle and my logs will still activate when pressed. I have no autologging checked.

The surprise is only that all characters on the screen are anti-aliased, ie. drawn with smooth surroundings and they look better, that's all.

For your touchscreen problem, I know it, but I haven't got any working solution for the moment. It seems that even flush command, which works with any input device, doesn't work with this specific one. One more strange thing : a touchscreen action done in Navcore seems to be duplicated when an application opens the device (your problem) and a touchscreen action done in the application is also duplicated in Navcore (Navcore reacting when you press somewhere in Tripmaster to give control back to Navcore (hide Tripmaster or exit Tripmaster)... Very strange and currently unfixeable...

 

[pianoCM]

Item 2 updated: It happened again (auto logging), one yesterday after work and one this morning. I did carefully deactivated it b4 turnt it off but it still automatically enable when turns on

Note: I place the Tripmaster icon on the first page of Main Menu and in the lower left corner.

 

[gatorguy]

As I mentioned in another thread here, altimeter reports on any of the highway use pnd's is inherently unreliable. Even with 7or more sats locked, you can expect a vertical error range 3 times the reported horizontal accuracy, and sometimes much more than that as users have reported in this thread. For instance, your TomTom is reporting horizontal accuracy of 15 feet. Multiply that by approx 2.5 times to get a 95% position accuracy, then around 3 times that for vertical. In this case the reported altitude could vary by up to 112 feet 95% of the time. Keep in mind these are only rough figures. Barometric altimeters available on many handheld devices mitigate the errors quite a bit. Also if your latitude is greater than 65 degrees the vertical accuracy error can be even more pronounced, quickly increasing the further North/South you are.

 

[roussillat]

Item 2 updated: It happened again (auto logging), one yesterday after work and one this morning. I did carefully deactivated it b4 turnt it off but it still automatically enable when turns on
Note: I place the Tripmaster icon on the first page of Main Menu and in the lower left corner.

When it happens, can you stop Tripmaster and have a look at your /tripmaster/config.txt file and tell me which value has got the autologging parameter.