Thread: DSA patcher (latest in post #1)

24April2014

change log:-

New: This is the version that might work with two remotes at once.


Could be checked out like this: connect the BT remote to device (go x00/x10) first; then use the RF remote too (but not the other way around).
If it does not work like that, at least the remotes could be used alternatively, as per the previous version of dsa...

30April2014

change log:-

New: Remote code revisited...


For lack of feedback on dual remote use, another version that might support them concurrently (BT remote first).

To disable the BT remote control chatter, while preserving the RF remote control availability, apply the skins/ttn trick

1May2014

change log:-
New: Code clean-up.

Sorry for so many versions, it's stable now, hopefully.
To disable the BT remote control chatter, while preserving the RF remote control availability, apply the skins/ttn trick
All TT sources went to directory dsa.app/Contents/Resources/Java/tomtom/src .

Source btserver.zip is not cleaned yet, a fixed release will follow shortly...

3May2014

change log:-

New: almost nothing... just the BT Console menu item is updated.


I am happy to confirm that both the BT & RF remotes will work together, provided that the BT remote is connected first.
Re-enabling bluetooth, or powering off and on the device will disconnect any remote, and thus one could switch between remotes.
The remote control capability could be disabled entirel. However, the RF remote will still be usable.

---
The previous dsa version has got the very same btserver, and only the BT Console menu item has been revisited.

---
As a reminder, only GO x00/x10 devices will support the RF remote, while the BT remote is accepted only by BT capable devices. For example, a GO 910 is capable of using both remotes, simultaneously, while a GO 720 will work with the BT remote only.
Last detail, use any of the shipped kernels (with switches MB, K50, CF) in order to activate the RF remote control.

---

20May2014

change log:-

: BT modem baud rate increased to 460800.


It's not much, but previously it was four times lower (115200).



24May2014

change log:

New: nothing worth mentioning.

30May2014

change log:-

New: networking via BT/DUN in emulated modes x40/50 (24, 36, 37,...,?).


This is work in progress, an ugly hack, but it works!
Be prepared to have a good data plan... I might have exhausted mine already.
There is no Wireless OFF button yet. Use the x00/10/20/30 modes as before, after checking it out.

For testing purposes, the "set another serial number" coding is included (in skins/ttn, read the included comment). It seems that a QJ prefixed serial does wonders for those in a location supported by TT.

I hope to get better log data soon, to organize the protocol more efficiently. I couldn't have advanced this far without the help of two native x40 device users whom I'll nominate if OK with them (please let me know).

When switching between modes (e.g. x30 to x40 and back), take care of the so called "Information Sharing" status, which flips without human intervention, making connection to TT live services impossible, until, for example, the LIVE/Weather item is selected - then you may reset it to "yes", to have the LIVE services running.
It's similar to the BT enabling status, it needs adjustment between modes, too.

The BT networking is determined in an identical mode as for the QuickGPSfix menu item: one needs the BT wireless setup done correctly in a lower mode (e.g. x30) in order to use it in the x40/50 modes, which do not have the BT setup option (except for handsfree).

Understandably, native GPRS devices are unaffected.

For all, the fallback version is dsa-24May2014 still. [Only registered and activated users can see links. ]

As usually, sources are in directory dsa.app/Contents/Resources/Java/tomtom/src/.


31May2014

change log (from DSA himself):-

New: networking via BT/DUN in emulated modes x40/50 (24, 36, 37,...,?), done properly.

A Toggle GPRS extra menu item disables/enables wireless networking in the emulated x40/50 modes, persistently over restarts.

Updated Help and hidden Toggle GPRS menu item in non x40/50 modes, next time...


1June2014

change log (from DSA himself):-

New: Finalized networking via BT/DUN in emulated x40/50 modes.


With Toggle (fake) GPRS menu item, and an updated Help.
With arbitrary serial number, see file skins/ttn.

It took us more than five years to reach this point, I hope it was worth it.


2June2014

change log (from DSA himself):-

New: for convenience, the new serial number should be entered into first line of file called serialnumber on the main storage.


It's a Windows file, edit the 12 char new serial with notepad, on first line.
(ignore all previous dsa versions, this is final for today )


3Jun2014

change log (from DSA himself):-

New: A few adjustments, for convenience.

The following files are renamed to have a .txt extension, the notepad default; they remain Windows text files:

skins/reskin.txt
serialnumber.txt
motd.txt

(ttn is unchanged, but still a Windows text file)

File serialnumber.txt should be created by user on main storage, with notepad, to hold a new device serial, different from the default device serial.
If the file does not exist, TT falls back to its default serial number.

And, this version (date!) is still ahead of times

dsa-4June2014

New: Dual networking for native GPRS devices (GO 950/750/550 LIVE, GO 940/740/540 LIVE, and XL LIVE IQ Routes, aka modelid 37, 24, 36).


The networking selection is done with the Toggle GPRS button: the device starts using the native GPRS network; at first click, it drops GPRS and starts using BT DUN (if BT available); at next click it drops the BT DUN and now there is no network access available; at next click, native GPRS is used again, and so on, it cycles between GPRS, BT DUN, no networking.
Across restarts, the last mode is preserved. This means that no networking could be enforced.

In order to use BT DUN, a native GPRS device has to be switched into mode x20/30 first (with Skin Chooser), and a DUN capable phone has to be added and wireless configured - that is a directory called ppp containing configuration files is created on main storage. This had not been possible before for such devices, now it is. Double check it by connecting the device to PC (via USB) to make sure the directory exists. Afterwards, the device should be restarted in its Self mode (with Skin Chooser), and kept so.

Of course, the BT DUN support is present in the emulated 24, 37, 36 modes too, when the Toggle GPRS button serves to disable/enable networking.

I hope that native GPRS device owners will give a try to their new dual networking capability. The same for only BT DUN capable device owners, I hope the networking in the emulated 24/37/36
will work for them as well - it works for me!

dsa-5June2014
New: to stay ahead (a day) of time

I felt compelled to make a small adjustment..

dsa-18June2014
New: A recommended version...


I could not add anything of significance. The network is up, but authentication with LIVE services depends on TomTom. Setting up a proxy to ensure backward compatibility between the "smartphone connected" new services and the old style "always connected" GPRS services for x40 - 24, x50 - 37, XL LIVE IQ Routes - 36 devices is too complicated, for lack of testing data.

How to convince TomTom that it is better to support "smartphone connected" LIVE services for all devices, regardless of device type, even as an alternative to "always connected" devices (new or old), is up to the user community at large.

dsa-19June2014
New: This is the recommended version
Sorry for that, I had overlooked a small (benign) detail, now fixed.

dsa-20June2014
New: For convenience, the cabinet list is updated (and reordered).

Although anyone could enter a new entry in the cabinet list (either online, by editing any entry in the drop down list, or offline, by editing with notepad file dsa.app/Contents/Resources/Java/tomtom/cabs/cabs.txt) I have updated (and reordered) the list in this dsa release.

dsa-22June2014
New: The non-permanent extra menu items are hidden by default.

The Show/Hide Extras button could be used to reveal the technical menu items, of little interest to the regular user.


dsa-23June2014

New: Hopefully increased compatibility with free BlueDUN, and temporary, a quick reboot upon toggling GPRS for real x40/50 devices.


It's a temporary version, which reboots instead of killing gprscomd, for faster transition. Note that switching from BT/DUN to No Network causes no reboot (my actual gprscomd.blue process is not killed, just switches to a no network state).

However, the free BlueDUN support is hopefully better and recommended for all devices.

A permanent gprscomd proxy will follow...


dsa-24June2014

New: Dual networking, gprs & bt/dun.

This version supports toggling between gprs and bt/dun for real gprs devices (native modes 24, 37, 36) without reboot.
Same cycling between three states: gprs --> bt/dun --> No Network, with the Toggle GPRS button.
Devices emulating modes 24/37/36 will have only two states: bt/dun --> No Network.
Changes to gprscomd are included in source (TTMP.zip) as usually.
(File gprscomd.blue is phased out, and can (will, in the next version?) be deleted from device)

The cabinet list is indeed updated for Windows machines (previously was only for Linux & MacOS ones).

There is hopefully better support for the free version of the BlueDUN app - required for Android smartphones with no native modem.

Multipath support (simultaneous gprs & bt/dun networking) some other time... After checking out if bt/dun is or will be supported by TomTom's LIVE services - don't hold your breath

---
Don't forget about setting up the BT/DUN connection in the x30/20 (15, 18) modes before attempting to use it in the native x40/50/XL LIVE modes (24, 37, 36 - self).


dsa-25June2104

New: The Suspend TomTom extra menu item is fixed.

Although intended for the obsolete case of native x50 devices installing a v8 (truck/work) NC with K50 (v9 kernel support) selected, Suspend TomTom works pretty well in all cases, as a software suspend to memory button.

Now let's wait for some (positive!) feedback...




dsa-26June2014

New: The support for (the trial version of) BlueDUN is now OK.

Finally, I've got it (almost) right, thanks to a hands-on approach.
All types of BT/DUN capable devices will be supported.

dsa-27June2014

New: Improved gprscomd engine.
The gprscomd engine was restructured and is getting closer to a bug free version, pending testing with a real x40/50 GPRS device.
If that test will be OK then we could see whether switching alternatively between GPRS & BT/DUN works, too.
Whether the TomTom LIVE services will work in the BT/DUN mode, with a valid subscription, that is another issue...

dsa-28June2014

New: Better gprscomd engine.
Check this version out!
I will rest until keessie74 (or another native GPRS device owner with a valid TT LIVE subscription?!) tests that GPRS works, that BT/DUN works also, and if TomTom LIVE services are supported in the BT/DUN mode.
In the emulated x40/50/XL LIVE modes (24, 37, 36) BT/DUN works well (but I cannot ascertain the status of TomTom LIVE services for lack of a valid subscription).

dsa-30June2014
New: A better set of skins.
An updated set of skins is included (for use by Skin Chooser).