yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] ElfKaa:
I think then you answered yourself. If the graph is zoomed in a lot - you have to redraw only few points - so it never minds if you redraw also the green point to fit the blue more often. And when you have the whole graph visible, then the blue moves very slowly - so also you can redraw the green when the blue will move - as it is not as often. Was I missed something or I don´t understand it?

Also you have answered yourself - if you can check that the blue point is visible - so then you can automatically switch the Track mode to ON and then when you will move by a finger - then you can switch it temporarily OFF and then check if it is still on the screen afrer releasing the finger - if yes - turn the Track mode ON - if no - turn the track mode OFF. So then you can do whatever you want and the track mode will work in every case. The same I think can be useful for the Map view.

I have checked the intuitive zoom again and I must say it was my fault as I didn´t understand it well before - it is working with "the only but" that is that if you have the graph whole visible and autoscaled and the graph is in the whole length higher then 100 meters then the autoscale will correctly align the graph y axis to starting at 100 m. But when you use the intuitive scaling to zoom on x axis even that the y axis automaticaly sets to start at 0 so the graph also move automatically higher - I think this may not happen as I didn´t changed the y axis (move or zoom) only x axis. It seems to me it is a bug.

Lukas
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello Lukas,

Ok, I have improved auto and track display of graph.

Now the current point is also displayed even if not logging, but only GPS is on (t2f must be loaded to have a reference).

Quote: interactive zoom ... the graph also move automatically higher... It seems to me it is a bug.

It's not a bug, it's a feature. You can zoom both axes at the same time by moving diagonal.

But you are right, it's hard to not to move a little upwards. I have now introduced a small threshold.

Now in 4.11beta13 track name and track description is saved in .gcc files. Gcc2Gpx will be updated in the next days.

Bug fixed which caused sometimes an offset of the track when reloaded.

Regards

Klaus
[Touch Diamond, MDA Compact IV General] jerome34:
Hello,

I think I've found, with your help, the reason for dysfontionnement on my mobile (freeze and blank screen with the latest beta versions). :laugh:

Just as well explain Low.flying.pigs, install the beta 3 (which is .cab file) BEFORE installing the following beta versions (which they replace only the executable file .exe).

For my part, after the hard reset my mobile, I just installed the cab version 4.10 that I thought would be the last and then just

replaced. exe with the last beta versions. :rolleyes:

I will confirm with other tests this week but I am very confident.

A big thank you to everybody for your help (and especially low.flying.pigs, ElfKaa / Lukas, Blaustein / Klaus who investigated the bugs I encountered). :good:

Jerome
[Touch Diamond, MDA Compact IV General] Tverts:
Hello,

where in the settings to change the miles to kilometers (speed, ​​distance)?

(GPS Cycle Computer 4.10 in storage card

Phone HTC Touch A1++ with Windows Mobile 6.5 )
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Tverts,

Icon Menu - Menu Options, Tab "Main screen" - then on the top is Units: roll down menu

---------- Post added at 04:23 PM ---------- Previous post was at 04:02 PM ----------

Hello Klaus,

the GCC has freezed twice to me yet. It happened while on Map view. I noticed you fixed the double tap to zoom buttons that now correctly zooms instead autoscale as before. I also noticed you added the black line under with the distance to track while navigation is On - but now the distance is shown twice - green at the top and white on black on the bottom.

I tried to zoom in while the logging was ON and the T2F was loaded and navigation was ON also. I zoomed a lot - as max as it is possible, then tried to quickly zoom out and then zoom in to maximum as possible.. Then the GCC has freezed completely and I firstly had to remove the battery. On second case it after long press and long wait to power button the device has shut down while the screen still leaved displayed the freezed GCC. It will only happen when the GPS signal is present already and the logging is ON so the blue line is drawing. Maybe it has some connection with the new Tracking function.

It freeze only sometimes - while on Map view try to move to see the blue line is drawing then move to not see the blue point and then move back. Then try zoom many times in and out. Then it will freeze surely - but I don´t exactly when.. I am still trying what exactly was happened.

P.S.: Yet I leaved the GCC working while freezed and after some minutes when the GPS signal was lost the GCC has unfreezed and started to react again.. (I have found the GPS signal was lost on main screen after unfreeze.)

Lukas
[Touch Diamond, MDA Compact IV General] jerome34:
For my part, I can confirm that now no bug found on my mobile with beta 13 release. ;)

bye
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello jerome34,

Good news that your issue appears to have been resolved. You seem to be indicating this was by installing 4.11 beta 3 and then replacing the .exe with that of the latest beta.

When you were installing 4.10 Final and replacing the .exe with that from a 4.11 beta and encountering the issues you detailed, did you carry out any testing with the screen on, to establish if the crash also occurred with screen on, and if so what is on screen, as previously detailed? That would assist with identifying and understanding any underlying issues and resolving them as may be required. If not, it would still be useful now if you were willing to do so.

http://xdaforums.com/showpost.php?p=45560037&postcount=1916

low.flying.pigs
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Hello Blaustein / Klaus,

Additional feedback below for issues already covered previously. Some reiterated for clarity.

Altitude and Speed Graphs::

- Remove 'speed' from context menu of Altitude graph when selection would result in 'no data to plot' as speed data is unavailable.

- Lines of the graph in some circumstances exceeds the boundary of the grid, and can obscure the scales. Lines should be constrained within the grid?

- When 'over distance' selected, when units are 'miles / mph', graph does not seem to operate as it does when units are 'km / kmh' (other units untested). Load any long .gcc and switch between units to see effect. Last worked normally in beta 11, seems broken in beta 12 and 13. Further testing of graphs will be done when this is resolved.

Live Logging:

90 - Could not establish a connection to the server!

Further information: The issue remains unchanged as at 4.11 beta 13.

Network Protocol Analysis, using WireShark, of packet data between GCC and Crossingways servers when attempting upload shows:

HTTP	7455	POST /services/livetracking.asmx/UploadGPX HTTP/1.1 (application/x-www-form-urlencoded)

HTTP/1.1 500 Internal Server Error (text/plain)

Analysis of GCC source code seems to show discrepancies between it and the sample HTTP POST code, specifically clientInformation=string:

http://www.crossingways.com/services/livetracking.asmx?op=UploadGPX

GPS Cycle Computer - Switching between versions:

Further information: At least the following settings are not retained when switching between 4.10 and 4.11 beta 13:

- Keep touch on while backlight off

- Show 'Exit' after Stop

- Change menu 'Options' <--> 'BKLight'

- Data array size (clears data)[settings other than 4k revert to default 4k]

- Select fore/back/mapLabel-color	[map label colour reverts to default blue]

There may be others settings affected, and effects other than loss of settings when switching between versions. Reproducible as follows: 1: Run 4.11 beta 13, enable settings as below. Exit from menu page to save settings. 2: Run 4.10 Final, exit from menu page. 3: Run 4.11 beta 13, error message is shown 'Warning Unexpected EOF while reading........', settings when checked are now disabled.

Skin / Theme: Expansion of existing functionality:

Facility for separate skins for Day and Night schemes (Colours can be separately configured for Day and Night already)

Facility for user configuration of colour of line effect and text (if implemented) for unavailable buttons.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello low.flying.pigs,

in short, can you please clarify and show:

what is not operating with miles.

what are the discrepancies with crossingways.

Klaus

PS: it is clear that you loose the new options when downgrading to a version which don't know this new options. You can save the options with a button and recall later.
[Touch Diamond, MDA Compact IV General] Site watcher:
Hello Klaus,

I have some observations and remarks concerning v11. All observed on:

- Pocket PC - MIO P350

- upgrade to v11 was made through beta 3

- both 'Safe Energy' options were unchecked.

1. Hardware power on/off button. Functionality has changed.

- v10: only screen and backlight were switched off/on when pressed

- v11: real powered off state is introduced (GCC stops its operations)

Changing 'use alternative method to keep GPS on' option has no effect. I know, there is 'backlight off' software button, but it is much more convenient to use hardware button to switch off the screen (like it was in v10), especially in the car or on the bike. Moreover, when the screen is switched off and hardware power button is pressed accidentally, the device is powered off by Windows after defined period of time (if defined) and GCC stops (see point 2).

This change is probably good for smartphones, but in my opinion not for PDAs. Could we have a checkbox option to change this behavior to previous (v10) state?

2. 'Safe Energy: do not keep Backlight on' option.

- v10: worked good

- v11: does not prevent the system from switching the backlight off and from power off (as defined in the system options).

3. GCC disables sound occasionally. When this happens all system sound controls remain unchanged, but there is no sound at all. I have observed this in the following circumstances:

- GPS is on

- Windows performs power off after specified time of inactivity (point 2)

- the device is waked up by pressing hardware button - there is no sound here

- sound functionality is restored after closing GCC and powering off/on the device. No system restart is needed.

Regards

Site watcher
[Touch Diamond, MDA Compact IV General] jerome34:
Hello,

The bug i encountered was this:

Sync GPS OK + start of the record of the track (screen : ON)

Getting off of the screen and start the track.

Put ON the screen (with button): blank screen and freeze (no response from the touch screen and hard buttons).

If I let the screen ON during the course, it froze (total freeze of the device) and the buttons are not responding to (but the screen is ON)

if need to do more tests, I am of course available :cowboy:
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello jerome34,

Thank you for your response. It confirms 'total freeze' occurs with screen on. Unfortunately is is unclear from your response what, if anything, is actually displayed on screen when left on until the 'total freeze' occurs. Please clarify.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
It seems to me it is not necessary to switch the screen off. It freezes sometimes on Map View screen while track is recording. I do not exactly know the reason when exactly yet..

---------- Post added at 11:30 PM ---------- Previous post was at 11:26 PM ----------

..but it sometimes unfreeze when you will wait a lot.. And/or maybe until the GPS signal is lost/found - but it doesn´t depend on it exactly.
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello

Attached new V4.11beta14.

It should solve most recent reported bugs:

- black lines

- sticky pressed image

- wrong context menu

- speed accessible in context menu

- anomalies in graph with miles

- keep GPS and backlight on

Pressed image on menu buttons: Does this work for any one?

The three lower buttons change to dark if pressed, but the menu buttons don't since I have intoduced context menu for menu buttons.

Only after context menu is shown the button gets dark. Then it should not. I think I should remove this 'feature' for the menu buttons, since I can't make it work.

Then the issue with sticky dark buttons is fully solved.

Regards

Klaus
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Klaus,

I have a bug after I started recording the track - loaded t2f track, wait for GPS signal OK, then I pressed Map Viev, returned back to menu by long press navigate button, go to icon menu then pressed Speed Graph button - after it GCC has crashed with the following system message (see the attachment). The log has not been updated - so no error then in log file.

As low.flying.pigs already wrote, the menu buttons pressed images only appear when long press on them.

I noticed the greyed text of inactive icons - yes it seems better, but the greyed buttons seems to me still too much light on my Omnia II - but I will get used to it. :)

Other fixes I haven´t tested yet but this bug seems to me the most critical at this time..

Lukas
[Touch Diamond, MDA Compact IV General] ElfKaa:
..lately discovered it only happened while you have Align T2F feature enabled.. If you disable it, there is no crash while you try to go to speed graph.
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Klaus,

the problem with the complete freeze still remaining as I described in the post 1927:

It seems to me it will freeze when the blue point leaves the arrow.. (I don´t know how it should happened - maybe while you move physically where you are while zoom in or out on device, so you move but the blue is not drawn together with arrow - but it is only mine imagination) Now it freezed and I was on Map View and had zoomed in a lot and I could see the blue point is in another place then the arrow of where you are then the GCC completely freezed while the device still live but is slowed down very and you can not do anything - but if you wait for a long time then it reacts e.g for sleep button. Then sometimes it unfreeze if you will wait e.g. 15 minutes - sometimes not anymore..

I don´t know how you mean the track function of the graph. Previously it was working well in beta 13 - you could leave the Track function while you moved out by finger. Now it doesn´t work :( The only what was wrong - that when then enter back the area with the blue point by moving by your finger or just the blue reach it as you move, it should switched automatically the Track function back ON. Maybe you did not understand me well. Now it is not possible to leave the area at all if you have Track function ON.

On the Map View it is not yet implemented also - the behavior can be the same.. If you see the blue (recording line) point the Track should be ON, while not - it should be OFF. But you should be able to leave the area by finger move.

And I don´t understand the black navigation bar on the bottom with the distance to track (I don´t understand the meaning why it is here), but it don´t display the same numbers as the green at the top, a little less or a little more..

Lukas
[Touch Diamond, MDA Compact IV General] jerome34:
The 'total freeze' totally blocks the display if the display is ON (no variation of GCC data on the screen) and if the screen is off, no key/display response.
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello jerome34,

Thank you for your response. Unfortunately, it confirms for you that while 'total freeze' occurs with screen on, there is no error message or any information visible on the screen to indicate what the underlying issue may be.

Since the issue, whatever the underlying cause, appears for you to have been resolved by installation of 4.11 beta 3 and replacement of the .exe with that of the latest beta, the limit for now of what can be readily investigated seems to have been reached.

Thank you for your assistance. Please do continue to upgrade to the latest betas and report any recurrence, and or any other feedback you may have.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Site watcher,

Thank you for the feedback. Briefly:

Firstly, before proceeding further, do you have any GpsCycleComputer.log or similar named .log files in the installation folder? If so, kindly upload for analysis.

Secondly, it will in any event be necessary to establish the situation when running the latest beta, currently 4.11 beta 14 from a known initial condition. Having taken backups of files if desired, please uninstall GCC. Soft reset / restart your device. Install 4.11 beta 3. Replace the .exe with that of 4.11 beta 14. Run GCC and ensure Menu > Options > Main Screen > Data Array Size is set to 4k. Test accordingly. If symptoms persist, exit GCC. Delete or rename GpsCycleComputer.dat to run GCC with default settings. Test accordingly and report findings which are awaited with interest.

Further information: Installation, Testing and Troubleshooting | GCC operation / Windows Settings.

To briefly address your actual feedback: Whatever the underlying issues are, they are not universal and do not affect all devices. The announced changes between 4.11 beta 10 and 11 include nothing that would readily account for what you describe in section 1 and 2, nor are any such changes apparent from source code comparison analysis. Others have resorted sound anomalies, which are also unexplained.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Klaus,

I have some new screenshots of the complete freeze for you. It is made after unfreeze by itself after about 10 minutes. The GPS is as you can see ON but there is no square (red, green, yellow) indicating the status. On the Map view there is no arrow. Previously in the morning it freezed while the Arrow on the Map view screen was grey instead blue and shifted from the blue point (last possition). I have removed personal data of the exact location from the picture.

Lukas

P.S.: Sorry GPS is off on the picture - but I didn´t switched it off - it has self switched off after unfreeze probably. The arrow as you can see is still blue.
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello low.flying.pigs,

I checked once again upload gpx crossingways.

I have checked "Upload GPX file (after saving)" and then saved a file as GPX. After a vew seconds I had the response from crossingways:

"Track saved. Have a nice Day."

The clientInformation is only a string to identify the uploading device and can be anything you like.

- Safe Energy: Backlight has now immediate effect

Lukas,

- NullReference bug should be fixed (the align t2f hint was very important)

It was not intended to prevent shifting the point in graph outside of the screen while in track mode.

- should be fixed

automatic reenable track mode when point is inside screen is too difficult. Also it may not be intended.

Also it is much easier to make a double tap to enable track mode (then the point is shifted automatically inside screen) than to shift the point manual inside the screen and let automatic enable track function.

- now 1/3 of "T2F in advance" is visible in track mode

Maybe you are right that the track distance is double and the black line at the bottom can be removed.

About your freezes:

I think it happens more often when there are many map tiles missing. On your screen shot there are 3 zoom levels missing 23,22,21 (upper right string 23-3).

Maybe you can try the option - Map Screen - Multi.maps - multi maps, 4x zoom.

Do you have any tools installed which provide any debug function or additional error reporting or something. This could slow down the device when exceptions occur, like missing tiles.

Also attached is V1.3 of gcc2gpx. It is necessary for the new feature "name and description stored in gcc files".

Now it can also create kml files.

Regards

Klaus
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Klaus,

no don´t have any debug tool installed on my device and by the way - it is not accurate to say "slow down" It will totally freeze. You must wait for ANY action many minutes - I mean e.g. 10 minutes. If I will press the sleep button for long and wait 10 minutes it will maybe go to sleep after long wait. If I long press the power button for many minutes - then - sometimes - after about that will shutdown the device. So you normally can not do anything - it is freezed completely, but the device is not at all freezed - it is still living but it is on some abnormal state - like the GCC will try do some command in loop forever (my imagination). If it is caused by zoom - it should be - but it must be solved somehow, as nobody has all the zoom levels completely downloaded and there will exist the case that this can happened. And also the zoom 23 does not exist on any map yet - it is good that it is ready for it, I have map on level 20 at maximum and probably I will not have 21-23 for now, but it is alright that I can zoom the highest level more to see it bigger even I will not see more detailed map..

Also the information about the zoom can be on the final version reduced to the real level. You don´t have to know that you have some tiles missing and it is a bit misleading to see information like 23-3 instead of 20 (which is the real displayed zoom level). But I understand that it is for now good for testing.

The freeze is still there on beta 15. It seems if I will not zoom as much it will not freeze, but for now a quick test only was made. On level 20/.. it seems it is still working well yet. It seems to me yet it will freeze while I´ll zoom in much more - but it will then surely freeze.. On the previously sent screenshot there is 23-3/.. level but it is zoomed much more - but there is no higher numbers displayed, then the GCC will freeze.

Lukas

P.S.: I have tried to zoom more and it has freezed. Then after a while (a few minutes) it unfreezed and the level 20/.. of the map was displayed..It seems to me interesting.. It didn´t helped to create more folders (21-24) - even that it will freeze while you will zoom more.