yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello profaner667,

Without specific information which device you are attempting to use and which operating system, I cannot give specific information. I can however share the following information and experience which may or may not be useful / relevant to you and your device.

I had similar symptoms with my old Windows Mobile 2003 SE device. The device had two batteries. The main removable battery and an internal backup battery not normally user accessible without dismantling the device. When the main battery was depleted, the backup battery, unable to hold charge any more would cause the unit to constantly 'hard reset' each time, removing anything user installed and reverting to the device factory clean state. I got by for some time by keeping the device charged however replacement of the internal battery resolved the issue properly.

Unless using Active Sync, which was difficult / impossible as the device required a non standard special cable I could not obtain, or make as the special connector was unobtainable, apps could not be installed directly to a Memory Card. The .cab installation file could however be placed on the Memory Card using a Card Reader plugged in to a PC. When the card was inserted in the device, the device would install the .cab accordingly to the device. Using other software, the installed program could then be moved from device internal storage to the Memory Card.

There is probably enough space on the device to install .Net and GCC without needing to install those to memory card. I would start by ensuring your device is fully charged. If the device has been unused for some time previously then I would suggest a good overnight charge. Then hard reset to return the device to factory clean state (copy any data you wish to keep first) (procedure varies device to device, thus unable to be specific). Then install .NetCF 3.5. Then install GCC 4.10 and configure logs etc to the memory card. Then report back how you got on and if you need any further help.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] profaner667:
OK I make some progres :)

Just files store in Windows dir are removed after reboot.

I just have to copy files frome one folder to another.

But could you help me how to do this at start up?

I need some solution just like bat file just to put command :copy source dest and put in autorun
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello low.flying.pigs,

24 Hour:

ok if you do without "AM" or "PM"

heading from sensor:

I had a short look on your link. In my understanding this ModDriver should work with any GPS application. The chances are good that it will work with GCC. Have you ever tried?

keep touch on:

Pitch for you. Do you use the option "use alternate method to keep GPS on"? I have no corresponding alternate method to keep touch on.

I you are a risk taker and experimental joyfully you can open [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State\Unattended] and create a DWord value with name "kpd1:" and value "0".

Or the same value in key [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State\Suspend].

zooming altitude:

what is the problem with this implementation? Is the zoom active area to narrow at the axes and therefore difficult to hit? I could enlarge the area somewhat into the diagram.

4096 points:

GCC handles all track data internal in arrays of size 4096, also the main track. But the main tracking data are recorded in the .gcc file in unlimited number of records. For displaying tracks on the screen or for navigation the whole array must be processed and therefore you must limit the size to keep it working with reasonable speed. RAM usage could also be an issue. GCC uses 12 arrays with 4096 float or int which consumes 160KB.

Audio waypoints are used to create a nice trip documentation. I don't know how you should activate the audio waypoints if they are displayed on the map. A separate list where you can click on the entries is not very useful IMHO.

Is voice navigation now working with your new device?

Attached is my todo list. - are todo. + are already done

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

maybe you want to have a look at "Mortscript".

Klaus
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
What you seem to be describing is not normal, and certainly not usually necessary. From your descriptions it seems you have an underlying issue that needs resolving, that being, why your device is loosing / not retaining user installed data.

Furthermore, if your device is loosing user installed data (files and registry entries) and if I have interpreted you correctly then I do not know how any script or method of automatically copying files will work as that script or method itself will presumably have to be installed and / or run from the device during the boot process, and therefore that will also be lost at the same time as the other user data on the device is lost. Copying files may not be enough anyway, as there will probably also be missing registry entries.

As previously stated, without specific information which device you are attempting to use and which operating system, I cannot give specific information or help further.

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

Thank you again for your prompt attention. In response to your comments:

When in 12 hour clock mode, I think we can live without AM or PM notification if needs be. AM or PM notification could however be squeezed in centrally below the time within the clock face.

Yes I have tried and will continue to do so. As stated earlier hardware compass is a feature implemented with GPS Mod Driver which does work in GCC (when I say work, I mean that cursory testing shows a heading, the direction the phone is facing, is displayed when stationary, and when moving. I have not progressed far enough in the testing to know if any issues with the operation of GCC arise or not). However, finding the optimal GPS Mod Driver configuration so everything else functions as desired and is usable requires further testing. It does not seem possible to enable the compass functionality only. Instead a multitude of parameters require setting. GPS Mod was designed for either driving or walking, neither of which lends itself particularly to cycling. Another difficulty is that the configuration screens are very sluggish. If necessary I will post in the GPS Mod Driver forum.

No, not ordinarily as I do not have a problem with the GPS. As you mention it, I have tried it however, and it has no effect on the issue. Neither does 'keep touch on while backlight off'.

I have created both registry entries and rebooted. Neither has any effect on the issue.

I can restore easily within minutes from a full backup, so for me, there exists no real concerns with testing anything.

I do not find the current implementation user friendly or indeed particularly usable at all, especially for large logs. Possible improvements in my opinion are:

Replace the switch graph and help buttons with a + button to stretch / zoom the graph and a - button to shrink the graph along the horizontal axis.

Drag the graph left or right to smoothly scroll graph along the horizontal axis. Tap graph to switch between altitude / speed graphs.

Implement the units consistent with user preference suggestion previously detailed.

Implement the colour suggestions previously detailed.

It seems to me the capabilities of GCC and current devices are being crippled to retain compatibility with legacy devices. Why not have user selectable options:

Legacy Device - Existing implementations

Current Device - New implementation with 4096 point issues removed / resolved, and other features more modern devices can support

Is there some reason why they cannot just be played when the way point is reached, or when tapped?

I can hear the voice now. In due course I will create new voice files as per the readme, and share accordingly if they are any good.

Many thanks. Very interesting. Lots of familiar things on the list. A few surprises as well, such as G-Sensor. I was considering suggesting that dependent upon the response to internal compass for headings. Please continue to post the list when updated.

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

keep touch on:

if you want you can check [HKEY_LOCAL_MACHINE\Drivers\Active] and search in the subkeys for something that looks like the keyboard touch pad. On my device it is the Name "KPD1:" and the Key "Drivers\BuiltIn\Keypad". Then I can try to keep this driver active.

Klaus

PS: G-Sensor I will also not implement (same reason as compass)
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Klaus,

I have an issue moving the map that I have downloaded for offline viewing in the latest 4.11b2 version.

When I scroll the map to where I have not any map downloaded yet the map totaly disappear even that the other tiles parts of the maps still exists so should be visible. The older version 4.10 then only displayed the worse magnification on that parts that are not yet downloaded in this zoom level. This behavior of the map now is not so friendly when I see nothing (black screen) and not partialy worse map as it was before and I think this is not much improovement at this time. :(

Also tha map is working much much slower to me than before on my Omnia I8000. When I am holding my finger and moving it seems to there is some kind of check which pixels to be redrawn on the screen and this slows down scrolling very much. If it was a try to avoid the sometimes black corners I think the better solution should be to draw the screensize same mapsize around the screen and display it everytime you are holding the finger - if it is possible to implement this (this may takes more memory for map) but you will never get black because you could not scroll more than a screensize for every direction for one touch, and the drawing then may stay as it was before - just like the picture is moving.

There may also be an option to use better/old scrolling method in the settings menu somewhere, if it will take much more memory or other resources for it. Not everyone should have as much free memory as it may takes (if it will take) for just a little improovement.

Also it will be fine to have the double-tap speed option in the settings. It often happens to me that when I am trying to zoom the map I am too much fast for the plus/minus button and it behaves like double tap and then the buttons simply do nothing, so I must wait and press it again.

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

Klaus "Mortscript" seems to be a perfect solution.

I have problem to run the scrip it just don't work :)

I use only 2 commands copy and run.

low.flying.pigs copy files to windows it's enough... all registry entry and other files stay just from windows it disappear.
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus,

I will investigate the registy entries and settings and report back any findings. I can confirm at this stage there are no KPD1 entries in the registry, except the two created as per your earlier suggestion, which implies to me that is perhaps not correct for the HTC HD2.

That is exactly what I had thought, hence surprise to see it on the to do list.

I have been unable thus far to locate my old 400Mhz device and have therefore been unable to test with it.

However, as an experiment, I have underclocked the HTC HD2 from 1GHz (998Mhz) to the lowest available speed of 384Mhz using LeoCpuSpeed V4

http://xdaforums.com/showthread.php?t=682663

I can confirm that running GCC 4.11beta2 at 384MHz with a 10 zoom level .png map in 'OSMTracker tile storage' format consisting of 77655 .png files (tiles) in 590 folders loaded from a 32GB Class 10 SD Card, the smoothness and fluidity of the map on GCC 1.41beta2 is notably different but however remains very good indeed, and is both more than acceptable a vast improvement over the previous implementation. At full 998MHz speed it is exceptional.

ElfKaa reports some observations. From my own observations of the above experiment, it would seem the 800MHz Samsung L8000 Omnia II should be more than capable and available CPU speed is probably not the issue if there is not acceptable map fluidity.

My initial thoughts are perhaps without knowing the SD card speed in usage it could be that is a factor, the SD card cache size, or CPU autoscalling, or maybe the map type itself makes a difference. I will do some further experiments with those factors.

The missing tiles at a zoom level being missing from the map display was I thought normal behavior being how logically one would expect a missing tile to be blank with only tiles of that level displayed, and to zoom accordingly to see other levels. I don't recall seeing any infill of the missing tiles with the nearest available lower zoom level when I was experimenting but it could have escaped my attention.

There may be some refinements possible with the latest smooth maps implementation, however, I'm not convinced there is any need to radically alter and certainly no need to abandon it. I am convinced however it seems perfectly possible to have both the classic implementation of maps and other features which can also continue in development, alongside the new improved maps and other features selectable as user preferences.

Legacy Device - Classic implementations

Current Device - New improved implementations

That way GCC continues to satisfy everyone and continues to develop to its potential. It makes no sense in my view to cripple GCC because some devices may not be capable, or exclude those still useful devices from future versions.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
My SD card is Class 10 and the power of CPU I have always set to Maximum (800MHz). I am also using more applications running in background but therefore this will probably could not slow down the scrolling as much. The previous moving implementation works superfast - as I am holding the finger on map the map reacts immediately. But in the 4.11b2 when I try to move - I move the finger, then the map move after a while (quater or half a second later) so it is now very frustrating to me to move the map. I think this may never mind if I drive my bike with the map view on, then the scroll may have slower reaction and not affect the experience of using as much.

The totaly blank (black) screen will happen when there is just a title missing somewhere on map - then there is no other tiles displayd even they exists.

I have not downloaded whole maps on every levels - it is very demanding for the storage space, so I have nicer parts and for bigger territory I have only worse zoom level parts.

In the previous version then the worse zoom level was displayed so the map will not dissapeared completely and only some parts wasnt look as nice as existing tiles. Now I have to zoom out to upper level manualy to be possible to see something on the map.
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello ElfKaa,

If I interpret your messages correctly, there are at least three separate issues I can identify you are highlighting with the new maps implementation in your circumstances:

1: Initial delay before map scrolling starts. 2: Smoothness and fluidity of map scrolling when in motion. 3: Map behaviour when tiles are missing at a particular zoom level.

1: The slight delay is probably a programmed necessary feature of GCC and could perhaps be addressed to reduce the delay somewhat. For me on the HTC HD2 with maps as previously detailed, if a moving finger is placed on the screen the map moves near instantly as expected. This is the way I would expect to move the map. However, if the finger is placed stationary momentarily on the screen initially, and then moved, there is a delay after that movement occurs, before the map then moves. I would estimate this to be 250-500ms (quarter to half second) delay. This sounds similar to what you describe, but I would consider it normal.

A finger held stationary on the map activates the timer for activating the context menu, and if held long enough the context menu would appear. The context menu will even still appear if the finger pressed to the screen and held is moved slowly and sligtly within the vacinity of the original place on the screen. This again I would consider normal for ease of activating the context menu as riding along it could be difficult to hold perfectly stationary in position. The context menu timer is only cancelled (allowing the map to begin to move) if the finger held to the screen is moved quickly out of the vacinity of the original place on the screen, hence the slight delay in how long context menu cancellation takes.

Does this match your observations, if not, kindly clarify what exactly are your observations?

2: What is the actual smoothness and fluidity of the map like when in motion? Does this change if background applications are not running? GCC supports different methods of creating maps and different map formats. What type of map are you using? How was the map created? What is the typical size of a map tile? It is possible these factors could be having an effect. Does behaviour change when missing tiles are not present? (to test, copy your existing map, then delete the zoom levels with tiles missing, then set this as your map in GCC) Ideally, if you can upload your whole map folder somewhere (private message the details if you wish) I could properly investigate and experiment and determine the issue. Failing that I will try and recreate the issues based on your response.

3: This infill of missing tile with the nearest lower zoom level tiles available could potentially be addressed with a refinement of the new maps implementation. I can remove tiles and these tile areas are black (black) as expected, however the remainder of the map at that zoom level is still visible and unaffected, and scrolls smoothly and fluidly, hence my thoughts the issues you report could relate to factors about the map itself.

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

a short intermediate statement from my side:

- the map display (select the required tiles, load them from SD and display on the screen) in 4.11 is aktually somewhat faster than in 4.10.

- on shifting the map, 4.10 only moved the pixels in the screen backbuffer. Therefore this was very quick, but with black areas which were not in the backbuffer. When lifting the finger the map was displayed new (see above).

In 4.11 the map is displayed completely new with every short movement of the finger (with every windows mouse move event). This makes the feeling not so fluently, but the map is always shiftet to the point where you lift your finger and you can see the new appearing parts.

- the missing tiles of other zoom factors is my fault. I will fix.

Elfkaa, your idea to hold the map one screen size around the actual screen in memory is good, but it is 9-fold the area and number of tiles. I will try to make both of you happy.

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

I think if the backbuffer size can be 9 times bigger than the screen / if it is not a problem / why not make this improovement just as new implementation? It will be more memory consuming but superfast and accurate. What is better on the new now implementation then this one I have suggested if we forget the memory (backbuffer) size?

If the new now is faster in displaying, the other one will be superfast and the drawing of the other tiles will be on that moment when it is hidden out of the screen. Only in the first moment when you select the map view from the main screen it will draw the map slower then yet. (How much?)

So maybe we will not need any compromise :o

And I have another idea - it will be very great if the screen can be fully covered with the map - I mean without the windows up bar (I don´t know the exact name of that bar - taskbar/statusbar?) Maybe this will need of DX drawing but I am not sure.. Is this the problem? It should be super if it could dissapear because the screen is harming if it is displaying the same things whole the time (at least on the amoled screens like mine) and also the buttons at the bottom should be hidden until the tap on the screen will happen. The same for the onscreen display.

---------- Post added at 10:10 PM ---------- Previous post was at 09:18 PM ----------

Hello low.flying.pigs,

Yes, this is what I mean - but if you will try the same on the previous 4.10 version you will see that the old finger tap and move will move the map without any delay - immediately!

No - it is exactly what I mean - you explained it very comprehensively :)

heh - yes, I can upload it for you - but it will have about 1GB ;) and they will not be your location.. I am from Czech Republic :cool:

I think it is not necessary..

I am using the standard map tiles (I think 256x256 px of size). The standard I mean Open Street map tiles in PNG format and some Gmap/satelite tiles in JPG format together.. But as Klaus wrote upper it is his fault that I have now blank (black) screen. (You may have white - I have set it to black in the settings menu.)

I will not dissable my background applications - some of them will be very complicated to dissable yet - but this will not do many difference if you have nearly the same/or exactly the same responds as me on your 1GHz HTC HD2.

It is not about missing nearest lower zoom level. It is about missing current zoom level tiles. The nearest lower should be displayed but are not - will be fixed - as Klaus wrote upper.

It is about that if I have missing the tile at the current zoom level and move my finger a little to black - where another tiles are missing at the current zoom level - the whole map then completely disappear! Even I didn´t moved as far - I should see the other tiles at the current zoom level which was there just right before I moved - but they disappear also!

I hope it will also be fixed - just like the Klaus wrote..

Thank you for that you have rechecked that behavior also after me again and describe it very comprehensively in details. :cyclops: