Articol disponibil numai în limba engleză
It happens that I have an ASUS R700 GPS device. Although a good piece of hardware, ASUS has dropped the software support for it, leaving the users only with map updates possibility (from Naviextras site) – but even this one only until 1 May 2016, the date from which map updates support for this device has also been dropped.
The original ASUS GO GPS application provided with the R700 was from the beginning (and remained) a sort of beta version of the Nav N Go iGO GPS application, with poor or broken automatic map overview in 3D mode, occasional software crashes and skipping full support for possibly additional map features on newer map versions. The latest software update from ASUS site occurred in 2008.
Note: Naviextras, which providesd official map updates for R700, also providesd a patch, required when connecting the device with their Naviextras Toolbox map update application; installing the patch also updates the ASUS GO application to a 2009 version (at least this is what the ASUS GO “About” menu says); although newer, apparently it retains the same functionalities and limitations of the original ASUS GO version (for example, the smart zoom button at the bottom of the map screen still does not seem to work).
Installing the newer Nav N Go iGO8 version on ASUS R700 GPS device is described and discussed on many web sites.
Note: weird, but it appears that the iGO8 software version cannot be purchased officially and installed legally on ASUS R700 GPS device; according to support representatives as stated on Naviextras forums,
PNA devices are sold with embedded software versions, you cannot buy a navigation software for these separately. The PNA-versions are different from the PDA version and therefore not compatible with each other.
ASUS R700 GPS device is a PNA.
Once installed in one way or another, the iGO8 software works fine, but on R700 in particular there are at least two issues left. In the following I provide a solution for these issues, or (in chapter (i) and then (ii)) just a way to get rid of the standby countdown annoyance that may be applied also to the original ASUS GO software:
When speaking about “device”, I am referring to the ASUS R700 GPS device, except if otherwise clearly stated.
In the following I assume that the device on which the patches are to be applied uses either the original software provided by ASUS (suitable for chapter (i) and (ii)), or an iGO8 software installed instead of the original ASUS GO version on the internal FlashDisk; the patches provided here can be applied in other scenarios as well, but I have no intention to provide support for those; feel free to reconsider the installation description or to modify the scripts in order to suit your particular needs.
I assume that the low level technical details of the device are familiar and that the person who reads this article (and wants to put it in practice) knows how to access the system partitions and files of the device.
I have done this just for hobby and retain no responsibility for whatever happens to your device if you apply the patches described below; the patches are provided “as is”; the responsibility for the success or failure of these operations belongs exclusively to the person that applies them !
Over the time there were a few things that constantly annoyed me during the use of it:
The solution provided here offers the following features:
Note: the standby dialog type can be specified only by editing the script (value 0, 1 or 2 for the last parameter in line 25 from “navigation.mscr” file; default script is 2, i.e. countdown dialog type).
Note: even so, the GPS software itself will not enter the map screen directly, it still starts with the “Find”, “Settings”, etc. dialog; for a complete self-operation when returning from standby, the hack described in chapter (ii) must be applied.
Note: the script provided here include simple translation text files for English, French, German, Hungarian (credits here goes to Laszlo Gere), Italian, Romanian and Spanish; please check the strings in your language before installing, or even add some more translation text file(s) in case your language is missing; after installing, the translation text files will reside in \FlashDisk\Programs\Secarica\locale\; each translation text file must be in UTF-8 encoding format, with BOM; each filename must include the decimal version of the Locale ID (LCID) for that language; take a look here for decimal LCID values of various languages.
With the standby patch applied, the standby flowchart looks like this (click on the image for a SVG version):
Note: the SVG may not be viewable with Microsoft Internet Explorer.
To install the patch, follow these steps:
Note: current patch version is 1.2 (click here for versions history)
That’s all. The device is now ready to be used with the new standby flowchart in action.
When invoked, the popup standby dialog should look similar to one of the snapshots shown below. Remember that the standby dialog type can be specified only by editing the script (value 0, 1 or 2 for the last parameter in line 25 from “navigation.mscr” file; default is 2, i.e. countdown dialog type) and that the standby dialog language matches the Windows CE multilingual user interface setting (or will fallback to English if the standby dialog translation is missing), which in turn is set by the ASUS main menu and not by the GPS software own language setup.
After resuming from standby, for a short period of time the display will show something like this:
Important: the standby script provided here checks for the readiness of the micro SD card; this is done by trying to read the “AsusGo” folder on it, which is true for the original ASUS GO software. Leave this folder as is, do not delete it, even if it’s empty ! If the micro SD card is not inserted, or if it is inserted but the “AsusGo” folder does not exists, the program will remain in a waiting loop. This check can be skipped by pressing the hardware standby button or by simply modifying the script, but I do not recommend this.
Note: an explicit status message can also be implemented instead of the system hour glass, but in my opinion the hourglass looks nicer :)
To deactivate the installed standby patch and return to the original ASUS behaviour, delete the file “navigation.exe” provided by this patch (or rename it to some random name of your choice) and then rename the file “iGO8.exe” back to “navigation.exe” as it originally was.
In my opinion, the standby patch presented above becomes truly complete only if the iGO application will start directly with the map screen. Follow the steps below for this to happen.
Voilà ! :)
After installing iGO8 on ASUS R700, the battery indicator no longer works. It remains blue as in external power mode, regardless if the device is running on battery, or the actual level of the battery.
Here is a working solution for this, but take note that the solution is not perfect: although the visual indication is correct over almost the whole range of the battery level, when the battery level is only 5% left, the indicator turns back to the blue external power mode indication. But take the half full part of the glass: when running that low on battery, the blue indicator just notify something like “hey, put me quickly on external power, else you will be lost !” :)
The working solution:
That’s all. The battery indicator should work ok now, except for the 5% remaining battery level amendment stated at the beginning of this chapter.
The correspondence in percents for the battery level indicator is shown below; percents were reported by the system in 5% steps, using the BatteryPercentage script command within a MortScript test script:
|actual battery percent|
|100% ? (during the tests I have never seen this percent when on battery)|
|5% or external power|