Now you can play the Polyphonic Ringtones on your XDA-I,Qtek1010,Siemens SX56,MDA-1 and T-Mobile with full instruments just by installing this file into your device :twisted: :
- MIDI56.sa.CAB
How to:
1- Copy the MIDI56.sa.CAB into your xda to any place you want then open the Explorer from your XDA,goto the folder you pasted the file in then click on the file after that get a *.mid file paste it into the \WINDOWS\RINGS,
Open the Phone from Settings and select the midi file you want it to be as your ringtone.
2- For whom the ringtone still doesn't work at all you just neet to extract the file >>CameraRC132_WWE_1.5.sa.zip<< and copy the cab file to your device and install it. Get the file from :
http://forum.xda-developers.com/viewtopic.php?t=6337&highlight=
Ps: My O/S is WM2003. I didn't test it on WM2002 if someone will just post here the result.
Enjoy my friends
We need to see the code can you pleas give use the code
Thanks
wwb95 said:
We need to see the code can you pleas give use the code
Thanks
Click to expand...
Click to collapse
I don't have the code that you're asking about bcz I didn't write it! I took this cab file from the Newest Himalaya's Extended-Rom :wink:
Your MIDI56.sa.cab has problems
Not that it matters that much to some folks...but in case you have an XDA-1 /MDA/PPC Phone Edition....I can confirm the following:
1. With WM2003, you will definitely need the Camera------.cab file installed, plus the MIDI56.sa. Mind you, you will have to install the MIDI56.sa file first, and then install the Camera------.cab
2. It will use up about 600+ K of needless memory on your XDA-1 because obviously, we don't have camera's. So.....what're you to do ? Well, go to
\WINDOWS
and look for Camera.EXE ( approx 500+ K )
Then, what you can do is launch Album, and look again at the \WINDOWS directory...and you will see a bunch of bitmaps obviously ( among other things ). Now..what you're looking for is files dated from 8/20/2003 ( that's 20/8/2003, for you folks EAST of the Atlantic ). Primarily they're bitmaps that were used by the Camera application. They add up to about 50-60 K. There's probably more files associated with the Camera.exe application that you won't need, plus any references in the PPC's registry will probably need to be ferreted out.
But...once you've done that, you've actually reclaimed approximately 800 K in space. Which on a 32MB unit, is a fair bit of memory.
Enjoy !
Marcelo
Re: Your MIDI56.sa.cab has problems
marcelol said:
Not that it matters that much to some folks...but in case you have an XDA-1 /MDA/PPC Phone Edition....I can confirm the following:
1. With WM2003, you will definitely need the Camera------.cab file installed, plus the MIDI56.sa. Mind you, you will have to install the MIDI56.sa file first, and then install the Camera------.cab
2. It will use up about 600+ K of needless memory on your XDA-1 because obviously, we don't have camera's. So.....what're you to do ? Well, go to
\WINDOWS
and look for Camera.EXE ( approx 500+ K )
Then, what you can do is launch Album, and look again at the \WINDOWS directory...and you will see a bunch of bitmaps obviously ( among other things ). Now..what you're looking for is files dated from 8/20/2003 ( that's 20/8/2003, for you folks EAST of the Atlantic ). Primarily they're bitmaps that were used by the Camera application. They add up to about 50-60 K. There's probably more files associated with the Camera.exe application that you won't need, plus any references in the PPC's registry will probably need to be ferreted out.
But...once you've done that, you've actually reclaimed approximately 800 K in space. Which on a 32MB unit, is a fair bit of memory.
Enjoy !
Marcelo
Click to expand...
Click to collapse
Marcelo,
I updated the installation instructions,you needed more to read about it.
Mind you, it doesn't matter what you install first cos I had the camera and album files in ppc b4 the midi cab file so it's ok.
Actually it's taking more than you are claiming, since those files installed in the \WINDOWS you can move them to "\Storage card\Album\Album.exe" "\Storage card\Camera\Camera.exe" like I did and gain back the used space , there's also a help file related to the camera it's about 56 kb you could remove it from "\WINDOWS" plus the little bitmaps. Thus you can as well fix the path in the registry for the files associations + making new shortcuts for the Album.exe,Camera.exe and by replacing them on the old ones.
Excellent !!!
I have to remind people that you MUST be careful when deleting the little bitmaps...look at them inside of Album first before deleting anything.
I had to reinstall my GPRS Monitor application because I deleted one of it's bitmaps by mistake....word to the wise !!!
Also I found TONS for MIDI files ( amateur ones ) to use as ringtones....,now if there were a way to make the ringtone directory point to my storage card, that would be great !!
Here's the link
http://www.ifnimidi.com/
TIPS
marcelol said:
I have to remind people that you MUST be careful when deleting the little bitmaps...look at them inside of Album first before deleting anything.
I had to reinstall my GPRS Monitor application because I deleted one of it's bitmaps by mistake....word to the wise !!!
Also I found TONS for MIDI files ( amateur ones ) to use as ringtones....,now if there were a way to make the ringtone directory point to my storage card, that would be great !!
Here's the link
http://www.ifnimidi.com/
Click to expand...
Click to collapse
Marcelo,
Moving the ringtones to the Storage card that was my other issue since a long time. I managed a way to do that it. Well for the first try it was successful but when the ppc turns it self off and some one calls you you’d hear the "windows default" ring and it remains whether you selects another ringtone. I kept a backup up on my registry to restore it back to the last status.
So if you like to share me your assistance I'd be grateful.
I'll give you tips of doing that and the project from here it starts…
------------------------------------------------------------------------------------
P.S: I recommend a backup on the registry b4 applying those tips
===============================================
1- (Looping Ringtones)
This tweak works perfectly you should apply it to your ppc's:
While playing a wav or midi or a wma as the ringtone the phone has a delay of 3 seconds before repeating, now this is really annoying if you've just created that great wav,wma ringtone, spent time making it loop properly in sound editor or whatever, and then the ppc does the silly delay, well, here’s the fix...
Open the registry editor:
HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0
Select 'Values'
And modify 'Script' by removing the w3 (eg. change 'av0pw3r' to 'av0pr')
"w3" stands for "Wait 3 seconds" you can make it "w1" or "w4" or remove to make the ringtone loops
===============================================
This tweak works for the first time you do it but when the ppc turn it self off the ringtone you selected won't play again :S be noticed.
2-Ringtones on SD/MMC Card
Open the registry editor:
HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0
Select 'Values'
Select 'Sound' and change the Value Data: \Storage Card\path to wav\wavname (eg. \Storage Card\Ringtones\mytone.wav)
We need here more try about this tweak and good ways to fix so ppl let’s do some tests
===============================================
This is the registry key where all ring tones s/w is playing whenever it comes to customizing a phone ring tone ... including PZP
and that's why all these s/w keeps a "live" component in the back ground to override what Windows is updating each time.
So, PZP was designed as today plugin, so Windows will force it to update the ring tones with each system referesh ... other s/w may keep a background process DLL running or to reconnect cprog.exe to their DLL ... or even to trap the system events to cprog.exe and redirect them to their handler.
So, I think (I might be wrong too ) the trick is to build a live demon to keep updating this registry key.
Necessary Files
I've been able to cut the necessary files for polyphonic ringtones down to ~570KB. Keep in mind I did this on a device with a ROM that was already cooked with supposed "support" for polyphonic ringtones, so there may be other files it is relying on. At any rate, the kitchens need to be updated with these files, because it doesn't work as-is.
There also may be ways to trim even more down, but this is what I have after many hard resets and adding/deleting files one by one. Hope it helps.
Shawn
Hello, this is one of the first posts, I don't know if you have any interest on this, but here it goes:
fact 1: EXE's and DLL's may be compressed
fact 2: PNG's may be compressed without any quality loss
based on that, I will explain what I do to make smaller CAB's and do not waste so many space when you have those installed.
tools used:
UPX (http://upx.sf.net)
pngout (http://advsys.net/ken/util/pngout.exe)
msceinf (http://www.codeppc.com/telechargements/msceinf/msceinf.htm)
cabwiz (from Microsoft)
let's put this together with a simple example with HTC Audio Manager CAB file:
size before: 1.135.294
size after: 327.204
(yes, 347% reduction, and all works well)
1. used msceinf to decompile the cab, and decompress it to a directory
2. used command "upx *.exe *.dll" on the decompressed directory
3. used command "for %i in (*.png) do pngout "%i" /kp" on the same directory
4. recreated the cab using "cabwiz Audio Manager.inf /compress"
that's it, until now I could regain a lot of space, of course that using exe compression makes programs a bit slower, but I believe there are more advantages than disavantages.
On Themes you can also achieve better compression using the same technique, decompiling the file, then using pngout on them and recreating the cab's back.
some results on a theme file:
Htc_New_Default.tsk original: 106.828
Htc_New_Default.tsk optimized: 44.835
I also saw some problems on some icon packages: sometimes the authors compile them with thumbs.db on it, resulting in complete waste of space.
Regards.
interesting. I never thought about it this way.
Optimized rom chefs, start your engines!!!!
In other news, dig the title.
It should be pointed out that one of the main negatives to upx'ing files is that they take up more memory. Example..a 100k program upx'd to 50k takes up 150k when ran and not all of the ram is released. This is typically why everyone doesn't just go crazy with compressing everything in site. If you need the space and are willing to sacrifice some memory then upx it..otherwise you'd be better off leaving it be. Also..if you are going to use upx or one of the other utils make sure you are using the most recent version to get best performance.
Yes, that's why I wrote that last sentence regarding EXE compression, some figures for CommManager that occupies 508KB as a process, it was tested by reading the in use memory when CommManager was running, and after I forced it's close (to check real memory usage, since process memory reads the same):
using UPX EXE: 33.77-32.89 = 0,88MB
original EXE: 33.67-32.89 = 0,78MB
so it's about 100KB difference for this EXE (since I don't usually run a lot of programs at the same time, I don't care about this), but for PNG's that are used more and more on pocket pc programs, it really makes a difference.
I've updated this with how to optimize Themes as well...
BullGates said:
I've updated this with how to optimize Themes as well...
Click to expand...
Click to collapse
You know there is a upx --ultra-brute switch that basically tries everything to get the smallest size?
Yes thanks. But as you pointed well, it's better to use EXE and DLL compression evaluating your needs. I've rebuilt many cab's concentrating on the graphics compression and I'm quite happy with the results. Smaller CAB's means smaller install times (not very noticed, but it's a fact) less need for storage - if you build your setups based on extended rom storage, this is quite handy. Also you have better performance since less bytes are involved on the loading (so better loading times).
Actually, I was looking to do exactly the same!
I had already found upx and was going to combine this with infocabxp and my own simple parser for the *.000/_setup.xml files, until I found the free msceinf tool - and about an hour later I find your post.
I just wish I found your post first, it would have saved me a lot of time
It is probably best to apply upx compression on exe's and dll's of standalone applications that you start manually or for short time use, and not all background processes as well, but I see there are already some thoughts on that subject
Thanks
How to do this
. used command "for %i in (*.png) do pngout "%i" /kp" on the same directory
Would u please explain more?
Regards
my 3 cents..
there's no reason to upx small files, lol...
40 kb of space may be equal of 40 kb mem less, if dll is persistent/resident(works all the time) - also not every dll/exe may be upxed - it may be broken after upx(i.e. isilo).
.net apps CANNOT be upxed for now.
DO NOT upx today plugins' dlls! they may lose stability/ you may have loading problems etc + mem loss, of course.
you can upx cpl's too.
always crunch at maximal pack setting!
do not pack exe icons, and relocs.
do not try to make xip modules from upxed files!
gfx resources like bmps may became smaller after pallette decrease(it is quite useful while reshacking - i.e. commgr may be smaller = faster launch times etc) regardless of saving method(24,32bit).
almost 100% of pngs, that are used in software/system etc usually loses its size after reedit = faster software loading/ working/less mem used(dialpad res's, home plug, etc) - usually palette decreasing works in same way, as with bmps - smaller file size(yeah, i know, that png is saved as 8bpp, but..sometimes palette may be 4 bit i.e.).
Next week I will outline for other Jade Clone owners how to install iGO8. Prior to that it will be back to basics on prepping your Clone. If done properly, the preparation will make installation of iGO8 a breeze.
The three biggest items for prepping your Jade clone are knowing how to turn on the GPS, a good sys.txt file and which version of iGO8 is best for our Clones. All this will be covered when scheduled maintenance on Novermber 23rd is complete.
I ask you to stay patient with me in the days ahead. If you follow the guide that will be outlined here, then I can promise you that installing iGO8 will be a breeze!
Reserved Second Thread
Reserved for future use.
Reserved Third Thread
Reserved for future use.
Preliminary Discussion about installing iGO8 on a Jade Clone
As a former Mod of another iGO8 Forum, I am amazed by difficulties encountered by some users when it comes to installing iGO8. I know that language and computer skills play a factor, but if you're capable of following instructions, installing iGO8 is not that hard.
Almost a year I upgraded my PDA, a Dell Axim x51V, to iGO8. Prior to that I was using ONC6. IMHO, iGO8 is considerably better than other satellite navigation (SATNAV) programs. While most have caught up it in terms of features like displaying 3D features, what seperates iGO8 is the ability to adapt skins to modify iGO8's display. Combined with route planning and saving, iGO8 easily beats the competition.
I specifically mentioned PDA because when you buy iGO8 (which I highly encourage you to do), NavNGo or its retailers will tell you that as a smartphone owner you should use the PDA version.Unfortunately the PDA version does allow text-to-speech (TTS) which is one feature that every SATNAV program is desired by all users. About three months after using the PDA version, I learned how to quote upgrade to the Personal Navigation Assistant (PNA) version which has TTS capability.
I then bought a PNA that did not come with iGO8 and successfully modified it to run iGO8. After I became an iGO8 Mod, I helped develop procedures for installing iGO8 on a car mounted double din (2DIN) SATNAV unit. It came in handy when I helped an Uncle install iGO8 on his new car. About two months later when I lost my cell phone, I upgraded that phone to a Jade Clone and successfully installed iGO8 on it too. About two weeks ago, I helped my brother install iGO8 on his smartphone. If you're keeping count, that is six different installations. The hardest one was the PNA installation but that was because of the mortscripts involved.
Installing iGO8 is easy if you have a gameplan which I will lay out for you. Over the next five days I will develop this thread to take you from preparing your Jade Clone to actual installation and usage.
You will need to stay patient and be willing to follow directions explicitly - IF you do, installation of iGO8 on your Jade Clone will be easy!
The Game Plan for Installing iGO8 on a Jade Clone
On every platform or system I have installed iGO8 on, I have had a game plan. Basically the plan is to use the KISS theory: Keep It Simple, Stupid.
Most botched installations occur because the user tried to have their system do too much or over-complicated the installation. There are six parts to the game plan I will recommend to my fellow Jade Clone owners:
1. Preparation and turn-on of the GPS chip.
2. Selection of the right version of iGO8.
3. Backing up the SD card sent by NavNGo.
4. Minimizing the number of files on this SD card so that iGO8 will compile quickly and in a minimum amount of time.
5. Having the correct sys.txt file.
6. Choosing a skin.
Each day I will cover one of these topics just like a coach who is preparing his team for victory. If you're willing to be patient, read carefully and follow instructions, iGO8 will be a breeze to install.
The first topic will be posted later today. . .
1. Preparation and turn-on of the GPS chip
You might have wondered why Preparation and turn-on of the GPS chip was listed as the first step of the game plan for installing iGO8. Believe it or not, GPS not found is the number one error message usually displayed by iGO8 when it is first installed. This can lead to a very frustrating search for how to get iGO8 to find your GPS. While iGO8 has a feature to AutoDetect the GPS, it cannot do this if the GPS is not turned on.
While most Personal Navigation Assistants (PNAs) will automatically turn-on the GPS chip by a line in their shell.ini file, most smartphones do not turn on the GPS automatically. The reason for this is that the GPS chip will consume energy and on some systems is a major power drain. While not being turned-on automatically might be a good thing, most smartphones do not have a utility for turning on their GPS chip.
My iGO8 game plan knows the importance of a turned-on GPS to iGO8 - without a functional GPS, iGO8 will not work. This is why prepping your Jade Clone to have its GPS chip turned-on comes before all other steps in the game plan. It is the very first thing I do whenever I turn on a new PDA, PNA or smartphone for the first time.
There are two steps needed for the Preparation and turn-on of the GPS chip:
1. Having your Jade Clone manage the GPS chip.
2. Installing an app to turn on the GPS chip.
1. Having your Jade Clone manage the GPS chip
With WM 5 and beyond, Microsoft has recommended that WM manage the GPS for all programs in order to deconflict them. WM 6.5 came with a program under Settings/System/External GPS to Manage GPS. In the first tab, the user will see what the system dictates where the GPS chip is found. In the second tab, the user will set a virtual Port that all the Clone's programs will use to get their GPS data from. This virtual Port can not be set to the actual Port setting. Since Port 9 is sometimes used by TMC programs, I recommend setting the virtual Port to Port 8.
In the event that your version of WM does not have the Settings tabs to manage the GPS, there is a cab file called Microsoft_Smartphone_GPSID_Settings attached to this message. Install this cab file to your Clone's main memory. Under the Programs tab, you will find it listed as GPSID_Settings. Use this program to set up the virtual GPS Port as listed above.
2. Installing an app to turn on the GPS chip.
A little known app as GPSToggle is a Today homescreen plug-in that can turn-on a Jade Clone's GPS chip.
Download GPSToggle CAB from this link:
http://www.megaupload.com/?d=7VRBH5RS .
GPSToggle works best when installed to main memory.
Once installed, you will need to add it to your Today screen. From your Today screen go to Settings, then choose Today settings. Go to the Items tab and you should see BAF GPS Toggle at the bottom of the list. Click the box to have it added to your Today Screen. Close the Settings screen and go back to your Today screen.
Now, a little bit of info about your GPS. It will work best when it has an unobstructed view of the sky overhead. It should stationery (not moving) and uninterrupted from the time you turn on the application.
Some people can get satellite signals inside a building. I can because I live in a one-story condo. If you can sit outside with your phone for about 30 minutes, GPSToggle should do the trick.
On your Today screen you will now see an item called GPS with the word OFF next to it. Click the word GPS and the word next to it will change to On indicating that the app has turned on your GPS.
Now sit back, be patient and wait. If you're lucky and outside, the SIRF III chip in your phone should lock on within as little as 42 seconds and as long as five minutes.
Attached to this message are four screens showing what your screen will look like:
GPSToggle 01 - Initial turn on. GPS is in search mode (no satellites detected).
GPSToggle 02 - GPS on. Communication beginning. 12 satellites possible.
GPSToggle 03 - GPS on. Four satellite bars displayed. Satnav not possible yet.
GPSToggle 04 - GPS on. Four satellites locked on. 3D satnav possible.
Note 1: I had not turned on my GPS today which meant it took about 2.5 minutes to lock on. This is not bad considering I am sitting in my front room. Normally, it takes about 60 seconds when I have turned on the GPS previously in the day and eperemis data which is satellite position and timing information is available from a previous session.
Note 2: According to most SIRF manufacturers, it takes three satellites for 2D satnav to occur. Most GPS programs can operate with that mode. Four satellites provide 3D satnav which is preferred.
See if this works for you. If it does, whenever you need to use your GPS, go to the Today screen and use GPSToggle to turn on the GPS for you which will quote warm it up for your GPS program. Once you see four green bars, you can turn on your GPS program and navigate like a champ!
You can read further about GPSToggle at this URL and thank the developer: http://www.freewarepocketpc.net/ppc-download-gps-toggle.html
Tomorrow, we will cover step two of the game plan!
2. Selection of the right version of iGO8
If you participated in the Easter Egg Hunt last week, you will notice that one of the hyperlinks took you to another thread here in our Jade sub Forum. Before I repost that link, I would like to explain further about why I posted this there:
http://forum.xda-developers.com/showpost.php?p=4985374&postcount=20
The right version of iGO8 is not necessarily the most current version. In upgrading to iGO8 from ONC6 during the past year I have noticed that NavNGo was pumping out versions like short order cook in fast food restaurant. Some times the versions were great because they corrected errors from previous updates. Some times the new versions were more buggy than the previous update.
My best advice to fellow Jade Clone owners is that if you want to experience iGO8, you do with a version that is known to be okay. As each new version came out, I wait one or two months to see what others thought of the update. If the update was not a good one, I passed on it. My Dad always said if you have a good thing, you should not be in a hurry to change just because others are jumping off a cliff.
RECOMMENDED VERSION - v8.3.2.71348
With that in mind, I am currently using iGO8 PNA version which was released during July 2009 with Gurjon skin 6p. I am basically a minimalist - iGO8 has a lot bells and whistles. While I use most of its features, I don't need every single item displayed onscreen. Why over tax the capabilities of my Jade Clone? My basic tenet is that I will do no harm to my Jade Clone (that should be your belief too)! While iGO8 should not be able to do something bad to your Clone, why take the chance by going beyond my recommendations.
I recommend you buy PNA v8.3.2.71348. Maps will vary. I prefer TeleAtlas for where I am in the United States. NavTeq works fine. This version has the standard lane assist, 3D effects and TTS features.
One of the nice things about iGO8 is that the majority of the update is built into its iGO8.exe file. Typically I wait until I know a good update comes out; download the updated file and post it to my SD card. I always keep a backup SD card with the old version that does not get changed or updated until I know the new version works for me.
With that in mind, I know that everyone has free choice. In the fore mentioned post from the first paragraph of this post, I will now point you to the current version:
http://forum.xda-developers.com/showpost.php?p=3325079&postcount=16
In that post, Tom Lenferink posted a link to a test drive version of iGO8 which is an update to v8.3.2.71348. The latest version with its driver alert feature exposed a flaw not only in iGO8 but also the maps available to be used with it. Supposedly only one version of NavTeq maps can be used with this new version. And then, even all the driver alerts are not fully implemented or working.
NavNGO seems to have slowed down on putting out a new version since this August update. This has led some to wonder about its future. I believe iGO8's future is bright because most likely NavNGO is working on its next version with both map vendors to get it right.
Last night I read an Associated Press article on Yahoo News about Black Friday GPS sales. The gist is that while the PNA/PDA *might* fade, the indash automobile (double din aka 2DIN) installations is growing faster than even the iPhone and smartphone markets at about 25 percent. Just about everyone has a car and when it gets replaced, chances are a new indash 2Din satnav program will be installed in the center screen. That is the future of iGO8 if you ask my humble opinion.
Guess what? My recommendation of v8.3.2.71348 works on a 2Din with slight modifications of the sys.txt file which will be covered in a future topic.
You can read about the GPS predictions here:
http://tech.yahoo.com/news/nf/20091125/tc_nf/70316
Backing up the SD card sent by NavNGo - Read and Heed!
I would be willing to bet that many of you are unaware that an SD card can be corrupted if your smartphone makes an incorrect read/write action to it!!! Usually this action occurs as the result of a program making a read/write action as the phone is being shutdown. Or, it can occur because one program has locked part of the card while another is trying to access it.
I've seen it a number of times on my PDA and just saw it last night on my Jade Clone. Normally your system will be able to access the directory where the corrupted entry (entry can be a file or even the entire directory) is located on the SD card. The way you can possibly tell your card is corrupted is if you are having problems with programs not running correctly off the SD card.
Or, if when you insert your SD card into a Windows computer, that system should tell you that it needs to do a chkdsk scan of your SD card because it has detected your SD is corrupted. Most times chkdsk will not do harm to the SD card but it can cause cross-linked files, delete incorrect entries and even deny access to directories.
Your best answer to preventing corrupted SD cards is to back up your SD card. I have a working copy and a protected unused copy (two seperate SD cards). I rotate my working copy and when I make changes will back up the card to it and protected unused card which sits in a special shelf.
I first noticed a corrupted directory because my PDA shut down accidently while running iGO8 off my original card. While the program ran again when I reapplied power to the PDA, I noticed that I could not access some maps and stored routes. Several directories had become corrupted and unreadable.
NavNGO will tell you to back up your card to your computer immediately if you only buy iGO8 on an SD card. If you buy the DVD with more maps on it, it will have a back up directory of iGO8 on it BUT:
iGO8.exe is a protected file that only works with the original SD card!!!
In the event that your original SD card becomes corrupted, iGO8 can be reinstalled to either from an update or a NavNGO DVD.
That is why you NEED to do a back up!
Fortunately this problem is minimized by the test drive version that was linked in a previous post in this thread!
Minimizing the number of files on this SD card so that iGO8 will compile quickly
Before I explain this part of the game plan, I have inserted a picture of a typical iGO8 directory. This came from my backup directory which is a mirror of what is on my SD card. Here are the files typically found in the SD card's iGO8 directory:
.3dl files go in the building directory
.dem files go in the dem directory
lang.*.zip files go in the lang file**
.fbl files go in the map directory
.POI files go in the poi directory
.zip voice files go in the voice directory**
**Do not unzip files in these two directories (very important not to unzip them)!!!
***The skin directory needs to be created and skins added to it.
****If a save directory is present before you run the program for the first time, you need to delete it.
When you get iGO8 on an SD card or by DVD, a minimal regional area like the United States will be about 1.7 Gb in size. The whole world map DVD comes in at just under 3.5 Gb. The reason I mention these facts are depending upon what maps you want to put on your SD card for iGO8 to use, it is much better to minimize the number of files it will compile in its initial installation.
Many users get a failed installation because they have too many or large files in the \building, \dem, \map or \poi. NavNGO automatically includes all the pertinent files in those directories that iGO8 *might* need. I emphasize MIGHT. If you have a speedcam file present in that directory, I can almost guarantee you your installation will fail. Why?
REASON FOR MINIMIZED FILES ON AN SD CARD
Well, when iGO8 is run for the first time - it compiles or associates all those files while it is building its INI file as well searching for a GPS. Unlike the little engine that could, iGO8 will overload your system memory because there are too many large files for it to compile. The best solution for an initial installation is to have just the files you need for the immediate area you live in. What does this mean?
Let's use France as an example. For it, while it would be nice to have the entire European continent loaded, on the SD card you just need France's map, language file (do not unZIP its zipped file - iGO8 works with ZIP files in the appropriate directory), POI file and voice file.
For a successful first-time installation, you want iGO8 to have an easy time finding and compiling everything. If it can't find the GPS, that will be the start of a bad day. Speedcam files typically will cause an Out of Memory error message. Too many map files can cause a database error message especially if you have the wrong license file.
In my case with just my state, which is a large one, loaded - my iGO8 directory fills about 0.7 GB with TTS files present. In essence, when I do a first time installation I literally have removed 1 GB of United States files to the backup directory on my PC.
It will take iGO8 about one minute to compile a minimal directory of files - during that time I recommend you be patient and do not touch your smartphone even though you will be tempted. After about 75 seconds, you can navigate to the Settings menu to go the Regional panel and set your preferences. From that panel, you can navigate to each Settings sub panel and set your preferences to your heart's content.
SOME DIFFERENCES YOU WILL NOTE IN MY PICTURE
1. When I backup my SD card, I do it to a temp iGO8 directory and then to the master iGO8PC directory you see in the picture. I find it easier and faster to manipulate the files on my PC versus comparing them off the SD card.
2. If you see a \Save directory on when you do an initial installation, one of two things is wrong. Either you are working with your backup files and included the old \Save directory OR you are working with a test drive version and it had a \Save directory present which you unRAR'ed to your SD card. On an initial installation, you do not want to have a \Save directory present. If you do, iGO8 will look to that directory and use the INI file present to set up iGO8. In many cases this will cause errors and possibly a failed installation. When you are looking at your SD card on your PC, if you see a \Save directory and you're doing an initial installation, DELETE IT!
3. Skins. On my picture, you will see a \Skin directory. There are a number (about eight that I know of) of skins available to give your iG08's display extra features. I have several loaded in that directory but only use the Gurjon 6p skin. Even that skin is somewhat outdated, but it's the one that works for me and does everything I need and like. I will cover skins in another post at a future date.
4. While we are not quite ready for the installation, I will jump ahead and say that after you have a good generic SYS.txt file to boot your iGO8 installation, and have a good installation - then and only then you can add back files that will give iGO8 added map coverage. Using the France example, you might want to add in contries like Spain, Italy, Germany, Belgium or other countries as appropriate. In that case it is just a matter of transferring files to your SD card from the backup directory.
5. I cannot begin to stress the importance of having a backup directory on your PC. Unless you get the deluxe iGO8 package of a DVD card and SD card, you will eventually see why having iGO8's files backed up is important. Better to do it now versus later.
Having the correct sys.txt file
One of the more common errors made on new installations of iGO8 is having an incorrect sys.txt file that has improper or incorrect data statements within it. Usually this error arises because the user either copies one from an iGO8 forum or uses a sys.txt file that might be part of test drive version.
Generally speaking, a generic sys.txt file is better than a specific one that the user does not know much about. As a former iGO8 Mod, I have looked closely at many sys.txt files and know what goes into my sys.txt file. In essence, the sys.txt file I use is very generic. You will not find statements in mine that make direct calls to the GPS, display type, time zone or other direct system components. Usually when a statement like:
name="igo8_pda"
or
vga=1
or
sync_os_timezone=1
or
gps="nmea"
On SD card or DVD provided by NavNGO, you will get a very short sys.txt file with little explanation of what should be put in it. Different statements can put into your sys.txt file to cause the map display or other parts of iGO8 to do something more than original sys.txt files calls for.
My sys.txt files works with my PDA, PNA, Jade Clone, another smartphone and even a double din (2Din). You can't get more generic than having one sys.txt file that works with five different systems. Here is what my sys.txt files looks like:
[folders]
app="%SDCARD%/iGO8"
[debug]
enable_roadshadow=1
show_residentonly=1
enable_roadsign=1
enable_landmark_occlusion=1
show_oneway_3d=1
show_oneway=1
show_gps_pos=1
show_signpost=1
background_navigation=1
screen_calibration=1
skip_eula=1
supress_trivial_left=0
supress_trivial_right=0
;max_memory=25000000
cache=2048
reserve_memory=1500000
[interface]
maxzoom2d=6000000
show_exit=1
shutdown_time=0
defaulttilt3d=7700
[map]
2dheadup=1
3d_max_tiltlevel=7700
3d_max_zoomlevel=3000
;3d_min_zoomlevel=40
3d_min_zoomlevel=80
3d_max_zfar=3000
stop_rotate_on_map_move=1
inertia_on_map_move=1
follow_gps=1
2dheadup=1
[poi]
poi_show_all_btn=1
poi_labels=1
show_poi_boundingrects=1
show_poi_areas=1
[navigation]
show_current_city=1
show_countrychange=1
autoreplan_action="AUTO"
gps_pos_to_road=1
[smartzoom]
minangle=0
maxangle=80
[msnd]
enabled=0
[map]
3d_scale_carmodel=1
3dcarsizemin=2500
3dcarsizemax=2500
3dcarsizemul=2800
[tts]
tts_buffer=131072
announce_exit_directions=1
tts_logics=3
priority="HIGH"
always_say_road_names=1
announce_street_name=1
skip_exit_numbers=0
[sound]
ding=0
queue_length=200
[3d_config]
;roadsign_lines_per_screen=12
disable_roadsign_navigation_mode=1
show_gps_pos=1
[rawdisplay]
highres=0
Sometimes in other iGO8 forums, you would have to copy those lines and insert them in a text file. A sys.txt file must be text file. Saving as a Doc file will not work.
But, to save you some time attached to this message you will find a copy of my sys.txt file.
Be patient as we still have one more part of the game plan to go before you attempt your installation. Additionally, I'd like to include one or two posts that should be helpful with a first time installation.
If you are willing to be patient and follow the game plan, you should get a good iGO8 installation.
6. Choosing a skin
Choosing a skin is a pretty difficult subject to discuss. What is an iGO8 skin you ask? Well, like other EXE files that are skinnable which means a graphic overlay can be used to change the normal appearance, iGO8 skins expand upon the basic interface to present not only the map appearance but also the way information is presented by the GPS.
To give you an example, when black and white televisions first came out most people thought what will they think of next. When color TV came out, some probably thought that was the end all experience. Next came big screen TVs followed by HDTV, gas plasma screens and next year 3D TV.
An iGO8 skin takes the color experience and brings it up an extra level almost comparable to HDTV - it is that radical in thought to see how the basic interface is modified to give more useful information. NavNGO built skin capability into its product years ago and iGO8 users have developed skins to enhance other users' experiences.
Choosing one skin is like putting you in a candy shop and telling you to tell everyone else what the best candy is - you can't do it! You would almost have to lock yourself into the shop, try all the candies and then decide for yourself which is best.
So it is with skins.
PRIMARY SKIN SITES
When I want information on what is going with skins, I go to two different sites to see what is on the cutting edge:
http://artwork-igo8.blogspot.com/
http://www.i-go8.com/
Both these sites usually do reviews of skins as new versions arise.
PRIMARY FOUR SKINS
As for skins themselves, I know of four major skins:
diMKA homepage: www.igo8mods.com
Gurjon homepage: www.gurjon.com/
Riks homepage: http://www.skin.riks.us/phpbb3/viewforum.php?f=3
Ultra skin: http://linknetonline.co.uk/igo8/index.html
There is a fifth skin called kikker but it's only available usually as a Rapid$hare link. I don't follow or use that skin. You would have to google it to find links to it which won't be included here because they change.
CHOOSING A SKIN
As with choosing a smartphone, you have to do your research on which skin is best for you. Each of us will have a different opinion. I have indicated which skin I prefer but will not mention it in this post as I would like all of you to visit the four primary skin homepages to make your own choice.
Skins really enhance the iGO8 interface which IMHO is the best anyway. Once you decide on a skin, you need to stay on that skin's homepage to keep up with changes and to ask questions as needed.
Skins take the 3D iGO8 screen to new heights. You are the one who chooses which skin will be your elevator to the heights.
Good luck in your choice!
Hello i wanted to ask, does a Jade clone work good with GPS? i mean does it find u like a normal GPS reciever? Finding "every" step u make cuz mine i move 100 meter it finds you, 100 meters and finds again and again, i still didnt have a lot of time to be outside for about 40min with ith on (got it a couple of weeks ago)
Thank you in regards
marspl said:
Hello i wanted to ask, does a Jade clone work good with GPS? i mean does it find u like a normal GPS reciever? Finding "every" step u make cuz mine i move 100 meter it finds you, 100 meters and finds again and again, i still didnt have a lot of time to be outside for about 40min with ith on (got it a couple of weeks ago)
Thank you in regards
Click to expand...
Click to collapse
If you follow the game plan to have WM manage the GPS and install GPSToggle you shouldn't have a problem with your GPS.
Part 1. That being said, your question has a two part answer to it. The first is that every GPS has an inherent lag to it. 100 meters is a too short a distance to gage this lag by.
Part 2. If you are trying to gage this lag with a GPS program, unless you are a geocaching program that shows a larger scale map and your GPS displacement (foot traffic) as what might be seen as someone directly overhead you at the same speed - a GPS program like iGO8 will not show the lag accurately or even your displacement because it uses a smaller scaled map. GPS programs like iGO8 are built to show your displacement at higher speeds than normal foot traffic.
If you don't use an app like GPSToggle to turn on your GPS, you will have problems.
GPS Tweak to improve iGO8 performance
While reading this thread, http://forum.xda-developers.com/showthread.php?t=523676 and thanks to beast0898 and monx®, I found some Registry tweaks that really improve the performance of iGO8. You will need a program like PHM Registry to add the following keys in your Registry:
ALL VALUES DECIMAL
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers]
"InputBufferSize"=dword:00000200
"OutputBufferSize"=dword:00000200
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Multiplexer]
"MaxBufferSize"=dword:00000200
Before adding these keys, you should backup your Clone because Registry tweaks if done incorrectly can affect its overall performance.
I noticed that when I added these three keys that GPSToggle now locks usually within 15 seconds of the app turning on the Clone GPS. Previously, it took usually longer than 30 and as long 45 seconds.
I always stay on my Today homescreen to see GPSToggle's satellites bar connect with four indicators meaning the Clone is capable of 3D satellite navigation (satnav).
____________
New Navteq 2Q 2009 maps released
I read somewhere that NavNGO is "trying to get it right" with future releases especially their software releases. They were releasing new versions every few weeks which in some cases corrected one error but introduced another. The Driver Alerts feature probably tipped the cart because now they either had a buggy version or just one map that worked with those versions.
Hopefully, NavNGO learned something from those versions and is most likely the reason we are now just seeing NavTeq Q2 maps. I would be willing to bet NT released the Q2 maps on their normal schedule but NavNGO held them back. In a vendor's case like NavNGO, it has to encode the maps to work with its product. If they "got it right" and are now just releasing those maps, hopefully we will see a new version soon that will enhance the Driver Alert feature. There are even rumors of an iGO9 floating around. . .
You may have noticed that last week several articles entitled GPS Cell Phone Apps Challenge Standalone Devices (see http://www.cbsnews.com/stories/2009/11/29/travel/main5826719.shtml - I read it first on Yahoo News, followed it to CBS News, CNET and then the AP author who wrote it). The gist of that article is that standalone apps like iGO8 and TomTom are challenging PNAs and PNDs which is forcing PNA manufacturers to become creative. REASON: Most everyone has a cellphone and more than likely will have a smartphone be it an iPhone, Android, or WM device. In essence by either using Google Maps (if you have a reliable GPRS signal and unlimited data plan) or or an app like iGO8, a smartphone now combines a cell phone, camera, GPS and PDA.
In some Forums I am part of (and one that I am sworn to double-secret probation), smartphone apps along with in-dash automobile satnav programs are where the market is pointing. If NavNGO is smart, it's probably working on iGO9 that will targeted towards those platforms. NavNGO has always been big on bundling, my bet is that they are working on bundles that will put their product on the leading-edge products.
As with any release, I usually wait a while until I get feedback on how good or bad the release is. You might want to do the same with these NT 2009 Q2 maps.
iGO 2009 Coming soon to Windows Mobile phones
Last week on another Forum I part of, one of the more experienced members released info on NavNGO's new iGO 2009. Don't know yet if the satnav program will be called iGO9 but that is what it has called in private posts I have been following. Here is the link to the undeveloped page:
http://www.igomyway.com/en/#
Supposedly NavNGO is working on improving much of the features we have seen in iGO8 like the Driver Alerts. While some users are worried that NavNGO will leave behind the PNA market, I find that hard to believe.
The primary reason for that is because the PNA version is easily adapted to other platforms like PDAs, 2Dins and smartphones. And knowing some characters on other boards, I am sure they will find a way to make it compatible with their old devices. Hopefully it will be more user-friendly towards finger-friendly smartphones and possess TTS. Some companies mistakenly think of smartphones as being PDAs and iGO8 did not have TTS available for its PDA version.
Most users like me have more than one platform or device. I presently have a PDA and smartphone. Plus I provide "expert advice" to my Brother and a friend who have a different smartphone and PNA respectively. Still, NavNGO has promised to release maps for those platforms up till 2010. Personally I don't travel in too many newly built up areas. So, my future 2010 maps will mostly likely serve me for at least two to three years beyond.
iGO9 probably will not be out much before February 2010 but I could be wrong (I hope; I hope)!
I tried to use version Nav.N.Go.iGO.8.v8.3.2.64029 (from your link).Followed all "game" steps,switch on the GPS, install IGO,but every time when try to start the program - the same one error massage :initialization error:no voice files were found.
In fact ,i download voice files(folder was empty) and past them i different variants-zipped,unzipped,in sub folder,directly in "voice" folder-but the result is the same one-can not start IGO.
Also,when change original sys.txt with your - IGO not start.Have a message :
Filed to open file:igo\240_320\loading.bmp exiting application.
So,can you help me where is my mistake?
kris555 said:
I tried to use version Nav.N.Go.iGO.8.v8.3.2.64029 (from your link).Followed all "game" steps,switch on the GPS, install IGO,but every time when try to start the program - the same one error massage :initialization error:no voice files were found.
In fact ,i download voice files(folder was empty) and past them i different variants-zipped,unzipped,in sub folder,directly in "voice" folder-but the result is the same one-can not start IGO.
Also,when change original sys.txt with your - IGO not start.Have a message :
Filed to open file:igo\240_320\loading.bmp exiting application.
So,can you help me where is my mistake?
Click to expand...
Click to collapse
Without being right next to see your screen and everything you have done, it is next to impossible for me to accurately tell you what you may have done wrong. BUT, I think based upon the two error statements you listed, I have an idea of what went wrong.
Please remember: I strongly advocate having a licensed version of the product because everything is spelled or laid out correctly for you on the proprietary SD card. The \iGO8 directory and its subdirectories are correctly built that the user has to do almost nothing other than periodic updates or maintenance.
That being said, if you went to the link and downloaded a "trial" or "test drive" version" as per that link, I do not know everything that is in that download. You have to go back to my post #9 and make sure you look at the imagevenue picture link to make sure that you have the right files in the right directories. The best way to install iGO8 is from its vanilla version (contained on the proprietary SD card) and then modify the sys.txt file as per my recommendation.
See this post again:
http://forum.xda-developers.com/showpost.php?p=5039782&postcount=9
and make sure you click on the imagevenue picture link to get the file placement correctly. Improper directory structure, improper file placement and improper files such as a \Save directory, speedcam or installation with a \Skin being called from an INI file will almost always cause failed installations.
Your first error message tells me that you don't have zipped voice files in the proper directory as listed. If the file structure is not correct, iGO8 will never find the files which also can be problem. The root file directory on an SD card should be \iGO8 - if you have something else that might be the problem. Again, hard to know without being over your shoulder.
Your second error statement, about a loading BMP file usually occurs because the wrong resolution is selected. This error alone tells me that there is either something wrong in the d/l files OR you did not use my sys.txt file as per its post.
My sys.txt file is a very generic or "vanilla" file. With the exemption of the highres statement, there are no resolution statements in my sys.txt file which tells me either you didn't use it or there is something wrong in the d/l files. The most likely culprit that I have seen as a Mod in another Forum is that you most likely initialized your test drive version with a \Save directory present.
If a \Save directory is present, iGO8 will not look at the sys.txt file. It will by nature default to the \Save directory because it believes it has already been installed and uses the .INI files in that directory.
Again, without standing over your shoulder, I can't with 100 percent accuracy tell you what you did wrong but I gave you two great indications. Test drive versions are okay but a proprietary copy on an SD card beats that like a straight flush beats four of a kind.
The instructions given here are primarily for a legimate user to set up their copy on the SD card sent by NavNGO. If you're going to use a testdrive version and encounter problems, you will need to ask questions in a testdrive Forum like the one you followed to get the links.
Again, in buying my Jade Clone, I knew that without some prior knowledge I might never get the GPS to work much less iGO8. In being on three other Forums and the former Mod of one, I have a better than average understanding of what it takes to set-up iGO8. The primary reason I went on other Forums was because the information on the NavNGO Forum was at the kindergarten level. Based upon all the Forums I follow, I have a Masters equivalence in Forum knowledge.
If you're going to go with a test drive version, this guide is a basic one that won't give you much more than a grade school education. You need to go to school at one of the other test drive Forums to achieve what you want to do OR else be willing to do trial-and-error which can really drive some people nuts.
One solution
Hi,
I have as you, a Jade clone with MARVELL cpu. under WM 6.1 see also:
screen01z.jpg
I tried unsuccessfully to use GPSToggle with IGO, but it never work.
GPSToggle goes to lock 5 state, but no program has worked (Tomtom, Igo, beelineGPS...) but i followed exactly the tutorial.
So. I found one solution by pure chance. The only things that I made are:
A registry edit: \HKLM\System\State\Hardware\GPSState : put 1, and i saw the blue light blinking, and put 0 to turn off GPS chip.
screen02vy.jpg
So I set the windows parameter as this:
screen03h.jpg
screen04i.jpg
screen05j.jpg
And it's working perfectly.
I set Igo as WM:
screen06n.jpg
When I start Igo8, the GPS chip turn on, automatically, when I quit Igo8, the GPS chip turn off. The fix is maded fast (less than 1 min).
(for the screenshot I was inside, in a building)
screen07h.jpg
screen08f.jpg
Enjoy.
PS: I can't put image from imagehack, if an administrator can unlock my account, i't would be nice. Thanks in advance.