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

Further to post 2053:

Mobile Atlas Creator accesses and downloads raster images (tiles) already pre rendered from Tile Servers to create maps (atlases). MOBAC does this from any area covered by the Tile Server. MOBAC renders nothing itself from raw data.

Briefly explained previously were matters and issues arising in relation to your suggestion of providing pre rendered bulk mapping for direct download. Correct methods of how this can be done properly and legitimately were detailed, and how using these methods users wishing to do so can create their own in the interim until an appropriate and sustainable solution is available.

To further elaborate on matters and issues arising, MOBAC, and similar tools, can theoretically be used for creating limited offline mapping in circumstances where this is necessary or desirable.

Whether this is actually legitimately the case or not briefly depends if appropriate consent exists for usage and storage of mapping content in such a manner, and whether appropriate consent exists of the service provider(s) for usage of their infrastructure and bandwidth in such a manner, at what can be their considerable financial cost.

Unfortunately, MOBAC and similar tools have previously neither sought nor obtained appropriate consents, or taken measures to prevent usage of the software for creating bulk mapping. In some instances that remains the case. Regardless of liabilities elsewhere, the end user remains responsible for their own actions.

Third party OSM Tile Servers will likely eventually restrict and curtail access even if currently tolerated. Their primary purpose is ordinarily to allow online on demand access to mapping immediately required which can be cached for future use, or similarly downloaded separately for offline usage. It is generally and usually not for creating bulk offline mapping using automated tools rapidly capturing en masse inordinate and excessive amounts of pre rendered tiles creating disproportionate server processing and data bandwidth overheads, and potentially impacting quality of service for ordinary users.

This is a summary, not an exhaustive explanation, and there are other aspects.

Often responses are not intended just for those addressed, but to the wider readership generally that includes readers and users across the full spectrum of experience, ability, and understanding. I look forward to your future feedback with interest, as with that of all users that take the time to positively contribute.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Today another bicycle ride with GCC as guide: Beside some confusion at start ("80m to destination"), everithing was perfect. Start and destination were identically as rather usual. But GCC tried to get me back to destination for about 1km trip, until I aborted T2F and started it again.

Nice to have: A info-bar at top of map view with 2 or 3 user defineble route infos, e. g. "km to dest", "battery", ...

cu - WolWer
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello WolWer,

I guess the GPS receiver had a first point far away of your start position at switching on. To overcome this you could also try to reverse navigation direction (navigate backward) and switch back again.

To have some more infos in map display was already requested. How about to have some infos at the bottom, because top is already filled up.

Regards Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
I Think your right - GPS is rather weak inside of buildings.

I'll try that next time!

No prob - it would be great to have user definable informations somewhere in the map screen, either top, bottom - anyway!

Another Medion S38x7 specific "nice to have": Since these PNA havn't got a sound, but a buzzer - would it be possible to operate the buzzer instead, e. g. on every first branch advise? I guess, the buzzer is somehow controlled by buzzer.dll (hidden file in windows directory)

Regards and tx - Wolfgang
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello Wolfgang,

do you hear a buzzer sound if you press "Recall 3" (and have no such setting stored and see an error message)?

Do you hear a buzzer sound if you enable "beep on gps fix" and switch on GPS so that GPS indicator changes from red to green?

Can you send me the buzzer.dll? I don't promise anything, but I can have a look...

Regards, Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
Sorry, neither nor!

buzzer.dll is a hidden system file, thus I can't copy it via ActiveSync, and copying in file manager to my flash disk fails.

Registry entry for buzzer:

HKLM/Drivers/BuiltIn/Buzzer:

Dll "Buzzer.dll"

Index 1 (0x00000001)

Order 149 (0x00000095)

Prefix "BUZ"

cu & tx Wolfgang
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello Wolfgang and other friends of GCC,

attached a new beta version 4.12beta8.

Release notes:

- improved navigation (if multiple t2f lines on the same road)

- navigation symbols instead of letter abbreviations

- waypoints (at cursor coordinates) can be added to t2f

- if t2f only contains waypoints, they can be used as track to navigate

- multiple files can be appended to t2f (context menu of Track2Follow button)

- files can be renamed or deleted in file selector (not on WinCE)

I have slightly changed the philosophy of navigation. In former releases GCC searched the shortest distance to t2f and begun navigation from this point. Now GCC in principle begins at the first point of t2f and moves along t2f if you keep closer than 300m to t2f. If you deviate more than 300m from track GCC sticks on last point until you come closer than 300m again - also on other places of t2f (some km away). You can manual execute a new search of the minimum distance to t2f by executing "calc min dist. to t2f".

This approach should greatly improve behaviour if t2f have several segments on the same road or if the GPS signal is very unstable e.g. at startup.

Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, Klaus!

Beta8 is really great: Symbols are much better to understand than abbrevations and can easily be recognized by hyperopic people.

New navigation algorythm worked fine on a 40km tour, only one prob occurred: exactly, where two consecutive trackpoints had a distance of more than 1 km (exactly 1078m), direction arrow shows backward for quite a few meters. Perfect: Calculated distance to track - even though we didn't match track at nearest point, GCC noticed, when we joint track!

Many Tx and cu - Wolfgang

p. s.: Any tip to copy buzzer.dll? Even Total Commander fails!

Is it possible to have context menus in bigger letters, too? On that TP-Distance > 1km prob on the road It was rather difficult to hit the desired item on S3857, even with stylus!
[Touch Diamond, MDA Compact IV General] Blaustein:
Oh shi..., thats a design flaw. You were more than 300m away from the last point and more than 300m from the next point. I must use the calculated (right angled) distance from the line. But to do so, I must reorganize some things. Or I remove this 300m stuff again. It should help to keep current nearest t2f point when gps signal is jumping far away.

I'm not shure if I have time this week and at the weekend I am out for skiing.

Klaus

PS: menu letter size is given by windows. I don't know if and how it can be changed.

I tried to write a simple program to copy system dlls - no success up to now.
[Touch Diamond, MDA Compact IV General] WolWer:
Be careful - you know what happened to Angie and Michael when skiing!!!

Solution for this I found in registry: HKLM/system/gdi/sysfont "ht", HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\BarFnt and/or HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\PopFnt "ht" to be edited (they've been hex FFFFFFF4, changed to FFFFFFF2 - looks better now - bigger letters and line hight)

I guess, I can manage to copy buzzer.dll by means of cecopy.exe (part of Windows Mobile Developer Power Toys).

Regards, Tx and enjoy skiing - Wolfgang

p. s.: cecopy.exe only copies files from PC to CE-device - not vice versa. buzzer.dll must be in use from very early point of system start, since third action in system start sequence is a beep (after display of firmware release and start screen). HKLM/init - beside some dependencies - only contains Launch20 - device.exe, Launch30 - gwes.exe, Launch50 - explorer.exe, Launch60 - services.exe and Launch80 - ST.exe.
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, Klaus! Hope you're save and healthy back from skiing.

Big compliment for GCC: Today I've organized a ADFC cycling tour - only 40km, but rather tricky route (and pretty strong winds - mostly in face). Since I knew the route (I've designed it on a http://radservice.radroutenplaner.nrw.de/rrp/nrw/cgi?lang=DE) pretty well, I've gave the PNA to someone of the group and asked for guidance: Though there was nearly no experience with gps-navigation, at least we arrived at destination without any error! Ok: a very few branches were noticed after passing by, so buzzer indicating on approach to branch would be a great help, but that's merely a HW-Prob. cu - Wolfgang
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi Wolfgang,

I am helthy back from skiing, but I had little time the last days.

Attached a new beta9 with improved navigation (tolerance now 500m distance to track line).

Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
Same with me - I even didn't manage to extract buzzer.dll from ROM as indicated by low.flying.pigs. Tx for new version - WolWer

p. s.: ROM dump using "grab it" doesn't work with S3857, since it's got no sd-card slot. dumprom romfile extraction tool on firmware-Up R11 only shows following files - no buzzer.dll:

BIBDrv_iNand.dll, binfs.dll, ceddk.dll, coredll.dll, coredll-dll.sig, default.fdf, filesys.exe, fsdmgr.dll, initdb.ini, initobj.dat,

mspart.dll, nk.exe, nk-exe.sig, PL.exe !?

Copying e.g. filesys.exe to MyFlashDisc shows "files located in rom cannot be copied". Same attempt on buzzer.dll: there's no pop up, but no copied file, too! All these files (incl. buzzer.dll and quite a few more [ca. 50] not listed above) have the same date modified: 2/14/2012.
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Dear Blaustein / Klaus and WolWer / WoWe,

As per post 2066, buzzer.dll is within as can be observed when analysed with a Hex Editor as per example screen grabs therein. It may be possible to determine the required information to ascertain how it operates in attempt to incorporate GCC functionality that utilises it in this manner without needing to extract as a separate file. Blaustein / Klaus can advise accordingly in that regard.

Should an extracted separate file be required for analysis, it will need to be extracted from ROM as it cannot be ordinarily copied. Unfortunately some providers take steps to frustrate their official ROMs being extracted, or fully extracted, which may or may not be the case in this instance.

If necessary, when I have more time next week, I will apply some effort to properly extracting the manufacturer ROM for the purposes detailed above. The files listed that can be immediately extracted are in total a fraction of the total size of the ROM.

User created ROMs direct from device generally avoid deliberately created extraction issues, so you may wish to persevere in the interim. Regarding lack of SD Card slot on the Medion S3857, this was known, but it was unknown whether this was necessarily preventative. Some devices handle their internal memory essentially as a built in Memory Card. Whether or not this is the case with the Medion S3857, it may still be possible to manually run Grab It and then transfer the resultant ROM in the usual manner files are transfered to and from the device.

Failing this, if the Medion S3867 has buzzer.dll, and if this is the same or similar to the S3857, and if someone with a device willing to assist can be located, this may be an option as it does have a memory card slot.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
I've tested it with AutoRun_armv4.exe, and despite of failure indicating popup dump.bin (128MB) was created, but dumprom seems to stuck - only flashing underline in DOS-window, which has to closed only by means of cross at DOS window, but no resulting file, same with dumprom -5.

I'll try to get that from gopal-forum.

@ Blaustein: Todays test with beta9 was ok (I don't use waypoints at the time as HaukeRun does). I guess, those white dots on track ahead of actual position indicate those points used in branch calulations. Helpful are those yellow dot on track at branch points. One prob occurred (part of track ist attached) between TP 16 and 17: branch at TP 16 was correctly indicated, but about 50m behind TP 16 TurnBack advise occured and thin red line aimed back to TP 14 resp. 15 (track was generated by http://radservice.radroutenplaner.nrw.de without any algorythm applied after export from radroutenplaner.nrw). Just checking that area in detail I notice two identical TP 14 and 15 - maybe that's the reason for that (reproducable) behavior of GCC. Thus "cleanup" of tracks by Douglas-Peucker or Reumann-Wittkam Algorythm seems to be required before using it on GCC.

Another point: Trying to attempt context menu from map view in GCC mostly results in shifting map slightly instead of opening context menu. Any idea to avoid map shifting, maybe decreasing sensitivity of map shifting (map shifting only activateted when stylus slide is bigger than e. g. 5mm???)

Regards & tx - WolWer
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello low.flying.pigs,

I appreciate your engagement in extracting buzzer.dll, hope you will be successful. I will do my best but I can not promise that I can make buzzer working even when having buzzer.dll. In the hex editor viewing I could not find a simple call to operate the buzzer.

Wolfgang,

I am interested in the gpx track which has problems at TP14 to 16 (did you miss to attach it?).

The white points I use for debug purposes - I have forgotten to disable them.

Opening context menu is controlled by windowsCE (aygshell). There may be a registry tweak to address this issue (similar to double click tolerance). As low.flying.pigs suggests I will try to operate menu without aygshell.dll (when I have some time), then I may have the ability to address this issue.

Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
And I've forgotten to attach track - sorry! Regards and tx - Wolfgang
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello Wolfgang,

you have always very challenging gpx tracks. Now I can handle multiple points on the same coordinates and long gaps in the track. But in this track you have united all difficulties.

The problem with this track is:

- you have sharp corner at point 17 (<90degree)

- before the corner you have narrow points

- after the corner you have a long gap to the next point (18)

[- you move on the inner side of the curve (left of the track)]

All these items together lead to the problem. If you are somewhere behind the corner on the segment 17-18, then point 16 is closer than point 17 and point 18. Therefore Gcc routes you back to the segment 16-17 and not forward on the segment 17-18.

If you switch off one of the above mentioned items all works perfect, for example insert another point between 17 and 18 in similar distance from the corner as point 16.

I will have a look if I can handle such tricky situations without unreasonable effort in development and runtime calculations.

Regards Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, Klaus! Don't worry for that tricky tracks - they're all exported from radroutenplaner nrw resp. ...hessen (both operating on IVV-Software). As already indicated in GoPal forum, tracks from these sources should be cleaned by track reducing algorythm before use with GCC to avoid probs like that.

[MENTION=4474489]low.flying.pigs[/MENTION]: There's no buzzer.dll on S3867!

tx & cu - WoWe

p. s.: I've tried all rom dump proggies - no progress except of hard reset required with all those probs i face then because of hw-prob with stylus calibration

p. s.²: some info on buzzer in registry:

HKLM/drivers/Active/27

Bus Name "BuiltInPhase1_0_26_0

Bus Parent 200304(0x00030E70)

Hnd 388176 (0x0005EC50)

Interface Type 0(0x00000000)

Key "Drivers\BuiltIn\Buzzer"

Name "Buz1"

HKLM/drivers/builtIn

Dll "Buzzer.dll"

Index 1(0x00000001)

Order 149(0x00000095)

Prefix "BUZ"
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, Klaus! I've tested CE_Beep.exe: Operating the MessageBeep-button - nothing happens at all. On operating ConsoleBeep-button "an unexpected error has occurred in CE_Beep.exe. ..." as you expected it to do. ST.exe is the last executable in the registry-init-sequence, and it activates buzzer once, when that red MEDION GoPal start screen occurs (where CleanUpMenu can be opened by tapping "o" in GoPal - and any operation in CleanUp is accompanied by a beep). ST.exe (1,8MB) is available to user - could this one help?

tx & cu - WoWe
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Dear Blaustein / Klaus and WolWer / WoWe,

For the Medion S3857, as per the attached screen grab, mnavdce.exe seems to utilise the following commands to control the buzzer. These seem essentially to be Off and On switches, where frequency and duration are separately configurable. The test program CE_Beep.exe could be adapted as required to test these preliminary commands accordingly.

noBuzz()

freq.doBuzz(int)

Until the full command list is obtained once buzzer.dll has been extracted and analysed, what, if any, further commands may be available is unknown. Assuming there are further commands, it may be possible some could be determined if other S3857 files that appear to control the buzzer can be provided for analysis.

For the Medion S3867, the manual refers to 'Lautsprecher Öffnungen für die akustische Tonwiedergabe' which translates to English as 'Speaker openings for the acoustic reproduction', whereas for the for the S3857, the manual refers to 'Summer Öffnung für akustische Tonwiedergabe' which translates to English as 'Buzzer Opening for acoustic sound'. As the S3867 apparently does not have buzzer.dll, and the manual does not refer to a buzzer but rather an actual speaker, this implies ordinary sound capability. The following questions arise:

Does the S3867 actually have ordinary sound capability? If no, what sound capability does it have? Similar capability may be possible to add to GCC if files that appear to produce sound can be provided for analysis.

If yes, it does have ordinary sound capability, does GCC sound already work on the S3867? If no, again, if files that appear to produce sound can be provided for analysis it may be possible to resolve.

Further information to be added.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
ST.exe ist the last one in init-sequence according to registry entries. It controls start screen accompanied by a beep and optional start of "CleanUpMenu", where every action is accompanied by a beep. It can be copied, since on start of GoPal or other Application, ST.exe seems to be finished.

I guess your right assuming S3867 to have sound controller/speacer, since special start menu of Ralf25 (Moderator at GoPal Forum) produces e. g. button click sounds!

Big Tx - WolWer
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello,

I have adapted the testprog CE_Beep to call noBuzz() and doBuzz(freq). But this is only a poke around in the fog.

Regards Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
The fog is pretty misty - "can't find an entry point 'no/doBuzz' in a PInvoke DLL 'buzzer.dll' " - maybe low.flying.pigs to find the appopriate code to operate buzzer in ST.exe!?

Regards & tx - Wolfgang

p. s.: There's only one unique beep on every event - no different frequencies, just on/off!
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Dear Blaustein / Klaus and WolWer / WoWe,

For the Medion S3857, as per the attached screen grab, ST.exe contains the following which corresponds somewhat with the registry information in post 2074.

SetBuzzerTone::CreateFile(BUZ1: )

Note the space before the close bracket should not be present and needs to be removed, but unfortunately had to be inserted otherwise the forum automatically changes the : and ) to an unwanted smiley face, and it is not apparent how to disable that.

Any further files that can be provided for analysis may be similarly useful.

Further information to be added.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, Low.Fying.Pigs! I'am not shure, wether ST.exe of S3857 is identical with ST.exe of S3867. In fact, mnavde.exe and all other stuff of GoPal OD application is the same for both devices.

Regards & Tx - WolWer

p. s.: Other *.exe in init sequence are in use on device run state and cannot be copied. Not so MainShell.exe (starts installation advise and at least GoPal Navigator outdoor - without any beep)
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Dear Blaustein / Klaus and WolWer / WoWe,

Unfortunately, MainShell.exe does not appear to contain anything of relevance to buzzer operation.

It may be possible, if you wish to do so, to disable the init sequence by editing the registry as required. This might then possibly enable files to copied and provided for analysis.

Further information to be added.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
As I expected, since no beep occurs until start of ST.exe. ST.exe generates red start screen including clean up (if activated) and finally starts menu.exe in /My Flash Disc. This menu.exe opens mnavdce.exe (GoPal OD appl.). I've replaced menu.exe by another one, which doesn't start GoPal automatically, but gives a user-definable choice of up to 6 programs to start instead. Thus I've got no chance to achieve e. g. Explorer with ST.exe disabled to copy other files in init-sequence. Since there's no beep up to start of ST.exe, I guess this couldn't help solving buzzer-prob.

Tx & cu - Wolfgang

p. s.: Since I've got a ticket for repair of S3857 regarding stylus calibration prob, the device will not be available with me for at least 3 weeks.
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Dear Blaustein / Klaus and WolWer / WoWe,

As the files publicly available in the updates from Medion have already been analysed, and you are apparently unable to provide further files for analysis from the S3857, it would appear that method has for now been exhausted.

When you have your S3857 back from repair, if necessary and if you wish to do so, there is an alternative method of creating a ROM image which can be attempted.

It may be the case the commands identified to date are sufficient, however, once correct commands are known, these have to be correctly implemented in order to function. Unfortunately correct commands and implementation of them are at this time both unclear and uncertain.

Regarding implementation, it can be observed the test program CE_Beep.exe includes reference to buzzer.dll, however, from the content of mnavdce.exe and ST.exe that can be readily analysed, neither include reference to buzzer.dll, but do reference other .dll files. Possibly a different implementation is required to normal because buzzer.dll is a driver required for the hardware to function, loaded via registry at system boot, and thereby already 'available' to programs.

Further information to be added.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Why wait? Maybe I can manage HaukeRun to investigate ROM - e. g. by means of EZBackUp? cu - WoWe