Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 8 of 8
  1. #1
    TomTom Expert

    biggerdave's Avatar
    Join Date
    Dec 2011
    Location
    Darn sarf
    Posts
    1,771
    Rep Power
    508

    patch DSA patcher (latest in post #1)

    Latest version dsa-20-August-2014

    [Only registered and activated users can see links. ]
    Last edited by biggerdave; 21st August 2014 at 08:08.
    Please do not post "thanks" but use the "reputation" star(*) bottom/left or "like" bottom/left buttons
    S i m p l e s

    PS If you find any dead links on MY posts please pm me & I'll try to fix/reload

  2.    Advertissements


  3. #2
    Master Downunder35m's Avatar
    Join Date
    Aug 2010
    Location
    private
    Posts
    609
    Rep Power
    375

    Default

    As I'm in contact with DSA8310 for quite some time and use the tool for even longer I try to provide a short tutorial:

    The DSA tool is very powerful and if used correctly perfectly save.
    There is no need for anything else except a keygen to activate your map(s).

    Pros of the tool:
    Downloads the original cab files from TT.
    Unique patching, provided by no other tool I know.

    Provides the change of the emulation over the menu.
    Able to downgrade an incorrect bootloader (only if the device still can be accessed and boots).

    Cons : ???

    So how exactly do you use this tool?

    Download the tool and run the installer, if in doubt run as admin!
    Make sure your PC is up to date with Java.

    Start the tool.
    In the top right you see the CAB section, where you select the Navcore of your choice.
    Be aware that no all Navcores offer all features you might seek - this goes especially for the low end model Navcores and Navcores for "simple" devices.
    It makes sense to inform yourself about the features of a Navcore before testing it.
    Select the Cab of your choice.
    Directly underneath youhave the menu to select the available emulations.
    You can select none, which give all possible emulations for your device/NC combo or
    select the emulation(s) you need.
    Multiple selections are possible by holding the CTRL key.
    Again it makes sense to know what emulation you really need and what works on your device.
    Example: Selecting the Truck Navcore and trying to use it in Rider emulation on a XL would be a very bad choice. While using the 9.004 in X20,X30,X40 or X50 Emulation on a Go720 makes sense.
    The button for DLL/PND patching can be used to patch Home.
    Under there you find the bootloader selection - this is only needed in extreme cases and should be left alone. If you have a problem with your USB transfer like stopping or very slow transfer rates it can be caused by an incompatible bootloader.
    If you think you have this problem you can ask in this thread for further instructions.
    Tickboxes:
    K50 : used to embed the Kernel of the 9.205 into a V8 Navcore, used to get the Truck Navcore working on a X50 device.
    MB : only useful for V8 Navcores. It creates a "swapfile" which saves a lot of ram, making it possible to use LoquendoTT on 32mb devices and to improove general performance. On a ONE v3 with the current 8.398 I was able to get 8mb of free ram with working computervoices and an active route of over 1000km. No other tool can do it this good!
    CF : used for X10 devices if the inbuilt HDD is replaced by a CFcard with adapter.
    The tickbox next to the BL section activates the log window where you can what is happening after you pressed "patch".

    The Tomtom button is used to locate a blank SD/devices for the installation.

    To install a new Nacore using the tool it is best to follow some advice:
    Make a full backup using the Windows Explorer - Home is not able to create a complete backup!
    Delete all files folders except these:
    ttgo.bif
    voices
    LoquendoTTS (if existing)
    schemes
    ephem
    Your map folder
    Personal folders - like MP3 and so on

    Start the tool if nt already running.
    Select the Navcore of your choice.
    Mark the emulations you need - self always starts the device in the emulation meant for it.
    Tick the boxes you need.
    If your device is not already selected, do so using the Tomtom button.
    Tick the box next to the BL section.
    Hit patch and wait to finnish.
    Once the installation is complete you might want to delete the bootloader file system in the root of the device to prevent installing an unsuite bootloader.

    After the start you will find new menu items related to the DSA Navcore, they are speaking for themselfs I think.
    The "skin Cooser" in the menu selects the emulation, the internal device ID of the model is used for the numbers.
    You must complete the calibration correctly!
    Selecting the emu : use the arrows when done doubleclick in the center of the screen.

    Known problems:
    Sometimes a selected emulation causes the devices to hang or not to not start at all.
    Easiest way to fix is to re-install and not to select the problematic emulation for the installation.
    If your device is very slow and inresponsive first check the POI's - having a lot POI's active on the map display slows even 65mb devices down to a crawl.
    Removing unwanted menu items: either use the hide button or delete the corresponding .cap files in the folder "sdkregistry".
    The very first start can take a few minutes, but if your device still "hangs" after 5 you should do a hard reset and try again. If no better the slected Navcore/Emulation is not suited for your device!

    I hope this will help to use this tool safely.
    Password for all my files: downunder

  4. #3
    Master Downunder35m's Avatar
    Join Date
    Aug 2010
    Location
    private
    Posts
    609
    Rep Power
    375

    Default

    Keep in mind that this is only a temporary release, there will be a final version in August.
    Since this version makes some problems with some NC things it is recommended to stick to the old version for now.
    Password for all my files: downunder

  5. #4
    Junior Member
    Join Date
    Jul 2012
    Location
    Underground
    Posts
    1
    Rep Power
    0

    Default

    @Biggerdave Thanks for the tool

    @Downunder Thanks for the comprehensive tutorial. :-)
    Last edited by 4who; 30th September 2012 at 10:15. Reason: spelling

  6. #5
    TomTom Expert

    biggerdave's Avatar
    Join Date
    Dec 2011
    Location
    Darn sarf
    Posts
    1,771
    Rep Power
    508

    Default

    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
    Last edited by biggerdave; 2nd June 2014 at 16:33.
    Please do not post "thanks" but use the "reputation" star(*) bottom/left or "like" bottom/left buttons
    S i m p l e s

    PS If you find any dead links on MY posts please pm me & I'll try to fix/reload

  7. #6
    TomTom SModerator

    QUIN1965's Avatar
    Join Date
    May 2012
    Location
    al lado del mundo
    Age
    50
    Posts
    2,600
    Rep Power
    871

    Default

    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).
    Last edited by QUIN1965; 30th June 2014 at 08:55.

    [Only registered and activated users can see links. ]

    How to unhide links: After clicking LIKE this post, hidden links will be available.
    sncmz5
    [Only registered and activated users can see links. ]

  8. #7
    TomTom SModerator

    QUIN1965's Avatar
    Join Date
    May 2012
    Location
    al lado del mundo
    Age
    50
    Posts
    2,600
    Rep Power
    871

    Default

    dsa-1July2014.

    New: BT speed read from the hardware chipset.
    Just in case there are different chipsets, the maximum BT speed is read from /proc/barcelona/btspeed.
    (I recall that voyteke was complaining about some odd BT connection issues, maybe speed was a cause, now solved?)

    dsa-2July2014
    New: Bug fix, related to protocol timeout.
    Thanks to Zebra92's testing, a bug has been fixed.
    I have not checked out this version yet on my device...


    dsa-3July2014
    New: Enhanced protocol timeout correction.
    The protocol timeout issue is definitely solved now. The BT/DUN network raising happens now in parallel, asynchronously.

    dsa-4July2014
    After performing the GPRS/GSM testing, please collect files log and log2 from device, and publish them (for example, to zippyshare.com ).
    Thanks.

    dsa-5July2014
    New: Revised, optimized code.
    This is the recommended version, so far.

    dsa-6July2014
    if testing GPRS/GSM with it, please collect and publish files log & log2.
    A few bugs have been fixed: for instance, networking is now determined correctly as up, only after the updetach pppd option is really in effect.
    Before, even with Blue/DUN stopped (or BT off), there was possible a premature networking Connected report.
    However, in order to avoid the protocol exchange timeout, which was causing reboots, the Connected state is reached slightly later than the moment when the networking is already up, at next exchange. But it's a small price to pay for making code reboot proof.

    Now, I still hope to get more feedback from GPRS/GSM users...

    dsa-7July2014
    New: BT/DUN connection status is updated promptly.
    When BT/DUN networking gets up, the Connected status is updated promptly.
    This is for now the recommended version.


    dsa-8July2014
    to be tested out by GPRS/GSM users.
    You may force the BT/DUN mode by creating an empty file called gprs_blue on your device top storage (SD).
    And make sure that file gprs_disabled is erased.

    This way, the initial mode will be BT/DUN, to overcome the lack of a valid GPRS modem.
    But do not expect TomTom LIVE services, only the network will be up, with status Connected.

    Since the Toggle GPRS button is a three state switch, first click will disable networking, but next click will bring you back to the GPRS (failed) mode - to be avoided!

    dsa-9July2014
    New: Bug fix, now it's indeed a three state Toggle GPRS button.

    Beside fixing the three state Toggle GPRS switching button, there is an attempt of using a valid (fixed) SIM ID during BT/DUN network setup.

    According to keessie74's testing, dual networking, GPRS/GSM and BT/DUN, is functional, and provided that a valid subscription exists, TomTom LIVE services work regardless of the kind of network in use. But the SIM ID must be valid!(?)

    If the SIM ID trick will work, we may be closer than ever to getting TT LIVE services in the emulated 24/37/20/36 (mainly x40/50) modes, too!

    I may add that real GPRS devices lacking a TT SIM card may also get a patched "good" SIM ID, and another SIM card from a local data provider may be used instead (socket is on the motherboard, I believe). I might be wrong here, though.

    (do not forget about file serialnumber.txt which enables us to choose an appropriate device serial, in case it matters to TomTom)




    dsa-10July2014

    not better and not newer, just providing the extra log files, log & enhanced log2.
    And now, let's get ready for the second semi-final!

    dsa-11July2014
    New: file simid.txt could override the real SIM ID.

    Top file simid.txt (Windows text file, editable with notepad) could hold an overriding SIM ID string.
    It's useful for testing purposes. Together with file serialnumber.txt, it could change the TT LIVE authentication credentials.

    Note that real GPRS devices generate file simid.txt automatically, if missing, and it hopefully will ensure a working BT/DUN connection.
    However, an existing file takes precedence.


    dsa-12July2014
    The debug version is,no better, no newer, just providing log files log & log2.

    A surprising dsa.ko bug has also been ironed out (see sources).

    dsa-13July2014
    New: File simid.txt accepted with or without proper line terminators.

    dsa-14July2014
    The debug version is,no better, no newer, just provides log files log & log2 .


    dsa-15July2014
    New: nothing!
    This is the recommend version so far.
    (previously a .swp file was included by mistake)

    dsa-16July2014
    The debug version is dsa not newer, not better, just with log files log & log2.

    dsa-17July2014
    New: The real SIM ID is stored in file simid.txt automatically.
    The real SIM ID is saved, unless file simid.txt existed before, to be used across device restarts, in mode BT/DUN.
    The SIM ID value from file simid.txt overrides the real SIM ID, too (finally!).



    dsa-18July2014
    The debug version is dsa, not newer, not better, just with log files, log & log2.
    Hopefully it will be no longer needed, sooner than later.

    dsa-19July2014
    New: Perfect personification of real GPRS devices.
    In order to help GO x10/20/30 devices, BT-only capable, to present themselves as a "worthy" GPRS device to the TT LIVE servers, when masquerading a GPRS/GSM network connection via BT/DUN, the following text/Windows files could be added to the main storage, in order to override the built-in values:
    serialnumber.txt, holds a new device serial
    simid.txt, holds a SIM ID (aka ICCID)
    imei.txt, holds an IMEI
    usbname.txt, holds a new HW device name
    motd.txt, holds a new device name

    Only the first two files seem to be mandatory. The remaining three complete a perfect travesty as the desired device, with respect to TT LIVE servers.

    I recommend a new x40 serial, and TT-like ICCID & IMEI .

    The usbname/HW & device name should be those corresponding to the serial number. For example, for a 940:

    usbname.txt should contain GO 940 LIVE
    motd.txt should contain TomTom GO 940 LIVE

    This part could be automated, in that we could compute the right usb&device names from the serial. Next time...

    Unintentionally, the above scheme could be used to clone same class of devices, too.
    Or so I heard...


    dsa-20July2014
    New: A template ppp directory is installed if missing.

    It's convenient for users of the BlueDUN app on Android smartphones, in that there is no longer a need to set up a wireless connection in the x30 (25) mode.
    Simply add the phone (skip wireless setup) in any, current, mode.

    However, if using a real data provider, directory ppp should be configured with real data in the x30 mode, by setting up the wireless connection of the added phone.
    Manual editing of file ppp/gprs-connect-chat with real APN, eventual username & password, is possible if knowing the chat syntax.

    dsa-21-July-2014
    New: Help has been updated with a link explaining how to clone a device.
    Improperly called cloning, nevertheless Help details which are the user configurable files, how to connect to TTHome a cloned device, how to buy a new TT LIVE subscription for a BT-only device, how to set up BT/DUN networking, which is the role of the Toggle GPRS button, and last but not least, a policy change proposal for TomTom.

    I remind here that by simply creating a new SN, starting with a new combination of two chars, at TT's choosing, meaning "a BT-only device" (e.g. "BTxxxxxxxxxx"), and using it, at server side, as per real x40/50/XL LIVE IQ devices, together with any fake ICCID, the LIVE services will become possible for BT-only devices, in a "smartphone connected" way. A subscription for such "BT" devices will cost less, having the data plan paid by user.

    GPRS & BT devices, as dual networking capable devices, will buy a regular, full priced subscription, with a real ICCID, prepaid and working only in the covered areas/countries. However, people traveling between different areas of coverage, for example between EU and USA, will benefit greatly from not loosing their LIVE services when abroad - they simply switch to BT/DUN when abroad, and go from "always connected" to "smartphone connected".

    Maybe I should rewrite the proposal in the Help, here it sounds better, it's more clearly explained...
    (maybe TT listen, too)
    Last edited by QUIN1965; 19th July 2014 at 09:04.

    [Only registered and activated users can see links. ]

    How to unhide links: After clicking LIKE this post, hidden links will be available.
    sncmz5
    [Only registered and activated users can see links. ]

  9. #8
    TomTom Expert

    biggerdave's Avatar
    Join Date
    Dec 2011
    Location
    Darn sarf
    Posts
    1,771
    Rep Power
    508

    Default

    dsa-22July2014
    New: DeviceName and DeviceVersionHW are computed automatically from the new serial number.


    There is no need to provide a new device name or a new device hardware version as long as the new serial starts with R1, R2, WT, WL, WR, WB, W1-8, corresponding to an XL LIVE IQ Routes Edition, or GO x40/50 LIVE device.

    Note that optionally, the device name could be forced to an arbitrary value via file modelname.txt, and that file motd.txt has been phased out.

    The configurable device details will therefore be held by files: serialnumber.txt, simid.txt (mandatory) and imei.txt, modelname.txt, usbname.txt (optional).
    I would, however, use file imei.txt, for a better cloning.

    I recommend against using files modelname.txt and usbname.txt; but if present, they take precedence

    dsa-23July2014
    New: Bug fix, now DeviceName and DeviceVersionHW are computed automatically from the new serial number.


    There is no need to provide a new device name or a new device hardware version as long as the new serial starts with R1, R2, WT, WL, WR, WB, W1-8, corresponding to an XL LIVE IQ Routes Edition, or GO x40/50 LIVE device.

    Note that optionally, the device name could be forced to an arbitrary value via file modelname.txt, and that file motd.txt has been phased out.

    The configurable device details will therefore be held by files: serialnumber.txt, simid.txt (mandatory) and imei.txt, modelname.txt, usbname.txt (optional).
    I would, however, use file imei.txt, for a better cloning.

    I recommend against using files modelname.txt and usbname.txt; but if present, they take precedence.

    dsa-25July2014
    New: Mode 42, and XXL 540/550 details have been added.
    There are other LIVE capable devices, among them XXL 540/550 (SN starting with GL, RW, RX, RY, RZ), I think associated with mode 42, so now they are supported (emulated, since the real devices don't have network capabilities). They are good for USA, Canada, Mexico.

    Anyway, DeviceName and DeviceVersionHW could still be overridden (with files modelname.txt and usbname.txt, respectively) in case I got them wrong.

    dsa-26July2014
    New: Protocol speed-up.
    Toggle GPRS transitions are notably faster in the BT/DUN mode.
    A benign bug in the debug version of gprscomd has also been fixed.



    dsa-27July2014
    New: Extreme/unlikely detail handled.
    As I was saying, this is the recommended version!


    dsa-1August2014
    New: Aesthetics, in file skins/ttn...


    dsa-6August2014
    New: Even better BT/DUN management.
    Faster network start, regardless of order in which phone address_es are recorded by TT.


    dsa-7August2014
    New: Another improvement of BT/DUN, plus control over the GPRS modem.

    If a real GPRS modem is present, its power is turned on in the BT/DUN mode, and it is turned off when in the No Network mode.
    This way, the BT/DUN networking emulation is complete.
    (if I got it right)


    dsa-8August2014
    New: Clean, final dsa version!

    We are done!


    dsa-20August2014

    New: Trimmed-down version.

    Next version will be more interesting, hopefully.
    Last edited by biggerdave; 21st August 2014 at 08:10.
    Please do not post "thanks" but use the "reputation" star(*) bottom/left or "like" bottom/left buttons
    S i m p l e s

    PS If you find any dead links on MY posts please pm me & I'll try to fix/reload

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.