Hello all
I've done lots of searching on here and elsewhere and I've found lots of useful info but no definitive answer to this...
Until recently I was using TT5.21 with the original GB-only map on an unbranded 512MB SD card on my 3-year-old Himalaya (02 XDAII) with no problems. I then upgraded to the TT5 v6.60 Western Europe map and needed a new, larger SD card. Realising that my Himalaya is of advancing age, I avoided the latest high-speed cards and settled for a basic Kingston 2GB card.
Since then my TT has periodically frozen - often in one particular spot that I pass regularly, always whilst travelling in the same direction (edit: I pass the spot most days travelling both east and west but TT only freezes when going west). I have put this down to the well-documented issue of the Himalaya having insufficient oomph to power both the card reader when it is reading the TT map and the phone handshaking with a new cell.
I have uninstalled some little-used apps from storage memory and used the slider to allocate as much memory as possible to programs (original 02 WM2003 1.72 ROM). This has improved matters somewhat (I presume that the Himalaya does not have to read the map so often, thus reducing the chance of this activity coinciding with a cell change - am I right?) but I still get occasional freezes and only a soft reset and restarting TT sorts it out.
So far this has only happened on the open road and hasn't caused me too much trouble yet. However if I was in the city on an unfamiliar route it could get me into big trouble!
My question is - would a ROM upgrade sort this out? what about an updated driver for the card reader (is there such a thing or is it built into the ROM?)? am I using the wrong spec of SD card? or is it a hardware problem with the Himalaya that can never be fixed?
I have also read that an MMC card may solve the problem as it doesn't use as much power - any comments?
Thanks in advance
The Doctor
Sounds familiar..the only solution for me, was to obtain 2gb mmc card, and that solved my problems. I also had kingston 2gb, which was said to be compatible, but really wasn't.
Fixed!
Hi all
In the end I took Jarno's advice and switched to a 2GB MMC card. It's now been in use for several weeks with not a single freeze - thanks for the tip, Jarno666!
Of course, now that I've posted this the damned thing will of course freeze on the way home...
...the upside being that if it doesn't, I will know that it is really, really fixed.
Cheers
The Doctor :
Of course, now that I've posted this the damned thing will of course freeze on the way home...
...the upside being that if it doesn't, I will know that it is really, really fixed.
Click to expand...
Click to collapse
It didn't, so I guess it is.
The Doctor
Related
Since I have a new SD card (tried Sandisk 512MB now using Extrememory 1GB) my Himalaya is suffering frequent lock-ups when I am running TomTom 3.03 (with TomTom GPS 3.07) and I end a phone call.
Also the device is reacting much slower in general with the new card in: Sometimes when trying to answer a phone call vai my BT headset the call simply isnt transfered (but after few secs in the same call transferring does work)
When I put in my 'old' Kingston 256MB everything is fine. I did not change anything else.
Filesystem on all cards is FAT.
Any clues ont this???
good question. also happens to me on a sandisk 256mb. but i can't attribute it to the card for sure YET..
Since I did not change anything at all, I must be the SD . . .or at least my Himalaya together with my SD . . .
Hi,
It has to do with the SD card. I have an Apacer 256MB SD card and also tested HP branded 128MB SD card. Everytime that the card is in the SD slot the machine is slow. Slow to switch on (about 2 seconds) delay and 5 seconds delay to switch off. Most noticable is to activate the bluetooth setting page. Clicking on the BT icon on the lower right hand corner, at times takes between 5 to 30 seconds for the page to display. Selecting any options will also cause delays and closing the page also causes delay. I have tested this countless of times. Remove the SD card everything goes back to normal (that is no delay at all).
The problem presists from the first version of ROM ie 1.52.00WWE and now the 1.60.00WWE. I wonder if it is resolved in higher version of the ROM.
Regards,
Kueh.
Hey guys,
This file should fix SD cards stability issue.
this was provided from i-mate support site.
hope it will work :wink:
Thanks for the patch, but I have some extra questions on this:
- Is the patch for Himalaya specifically?
- Is There a reason why some devices act differently on certains SD cards (I have had he same behaviour with a Sandisk 512MB, that card is widely spread, also in the himalaya world)
- What is causing the behaviour (ie what aspect of the Himalaya or the SD card, can we detect such SD card from the outside (ie via a blacklist wiht model/serial numbers)?
edsub said:
Thanks for the patch, but I have some extra questions on this:
- Is the patch for Himalaya specifically?
- Is There a reason why some devices act differently on certains SD cards (I have had he same behaviour with a Sandisk 512MB, that card is widely spread, also in the himalaya world)
- What is causing the behaviour (ie what aspect of the Himalaya or the SD card, can we detect such SD card from the outside (ie via a blacklist wiht model/serial numbers)?
Click to expand...
Click to collapse
yes the patch is designed for himalaya.
[HKEY_LOCAL_MACHINE\SOFTWARE\Drivers\SDIO]
"SDMemory"="0.15.00 HIMA"
I have no idea why some SD react differently???
me and a friend of mine both have i-mate and went together to by Kingmax 512 SD ! guess what ? mine did work smoothly , his card was hanging the device all the time!
so same SD brands also act diffrently on different devices. :!:
I did not run the patch yet, but I checked the registry.
Guess what: This value is allready set.
The following values apear to be present under the SDIO key:
Common = 0.15.10 HIMA
SDBusDriver = 0.15.00 HIMA
SDMemory = 0.15.00 HIMA
Any other suggestions??
Is it stated on the iMate website for what ROM version this should work? I have a 1.72.00 / 1.72.903 (T-Mobile 1.72.192 based) ROM
@edsub:
I am using your created Homecooked ROM 1.72.903 without any problem regarding SD 1GB. Have you tried different vendor other than Sandisk (eg. from friends that have same size card)?
I am using Lexar 1 GB SD, without any lock-ups so far (finger crossed).
edsub said:
I did not run the patch yet, but I checked the registry.
Guess what: This value is allready set.
The following values apear to be present under the SDIO key:
Common = 0.15.10 HIMA
SDBusDriver = 0.15.00 HIMA
SDMemory = 0.15.00 HIMA
Any other suggestions??
Is it stated on the iMate website for what ROM version this should work? I have a 1.72.00 / 1.72.903 (T-Mobile 1.72.192 based) ROM
Click to expand...
Click to collapse
The patch is advised to be use on ROM 1.72.
the reg value in my last post was to show that it is designed for himalaya.
find below full reg values for the patch. i have checked on my device and it seems that Driver\active\47 is missing!!! so this patch is adding it.
this is according to my ROM 2.06 se.
i did't try the patch because i don't have SD problems, please let me know your feed back. is it working?
[HKEY_LOCAL_MACHINE\SOFTWARE\Drivers\SDIO]
"SDMemory"="0.15.00 HIMA"
[HKEY_LOCAL_MACHINE\Drivers\Active\47]
"Hnd"=dword:00627c40
"Name"="DSK3:"
"Key"="\Drivers\SDCARD\ClientDrivers\Class\SDMemory_Class"
"ClientInfo"=dword:006103e8
:wink:
Ok, thanks for the update (yesterday I want able to open the cab).
The 47 key was missing with me.
Just ran the patch, I will let you know the results. . .
@superperry: The situation before running the patch: I have NO issues with my 256MB Kingston. I DID have the issues with a new Sandisk 512MB. For that reason the shop took it back and I bought the 1GB Extrememory instead. Also with the Extrememory 1GB I DO have the issues.
no success
Unfortunately running the patch did not solve the lockup-issue.
Maybe it has something to do with the characteristics of my SD card. As you might know just the Sd card label is not enough to identify it.
Could anyone please post the model no & country of manufacture of cards that do and dont work?
Does work:
Kingston 256MB - SD-256B1 - Japan
Doesn't work:
SanDisk 512MB - ??? - China
Extrememory 1GB - SD1GBM04S0449 - Taiwan
I use a Sandisk 1 GB from china and a Sandisk 64 MB from Taiwan
both of them work just fine.
Pleun: no issues with TomTom either?
Nope, I have benelux, austria, germany, france, switzerland and major roads of europe on it plus a load of MP3 , no problems yet.........
btw just upgraded to 2.20 SE rom, must reinstall all applications, but so far so good :lol:
re installed tt3, sprint db and some databases, no problems so far, looks good. I'm now 2.20.07CHS
kingston 128,
trancend 128,
both working....
just one question.... the trancend package indicates it runs 45X, how come when i benchmarked it using pocket mechanic it only scores 5.5X read and 1X write?
The actual speed is the result of combined capabilities of the device & the card.
My SD Cards also perform around 5.5x read and <1.0x write . . .
This SD-Card sh*t is really annoying me. WHAT could make the difference???
BEWARE of the SD patch
Just a warning before you use the SD patch posted above.
After I installed it, I saw it did not solve my problem. That's just bad luck.
BUT: After I installed it my Bluetooth headset stopped working. Even worse: I wasnt able to bond it anymore (incorrect pin). I was able to bond it to my old Nokia phone, so the headset was ok.
Uninstall of the patch did not solve this.
Neither did a soft-reset.
Had to hard-reset
Lucky me I had a pre-patch backup!! 8)
I still hate it I cannot determine from the outside if any SD card will work on my Himalaya!!!!!! :evil:
COULD it be the card speed that creates the issues I have.
My benchmarks (using Pocketmechanic trial):
Works:
Kingston 256MB Read 0,87MB/s (5.9x) Write 0,01MB/s (0.1x)
Problems:
Extrememory 1GB Read 0,81MB/s (5.5x) Write 0,10MB/s (0,7x)
Can anyone post his benchmarks??
Hi Guys,
As you may have read from previous posts, TomTom & I have had a very stormy relationship! Add to that huge memory leak problems on my XDA IIi & I was sure that Nav5 was going to get the usual thumbs down, but after removing the O2 Active UI by following the instuctions here:-
http://forum.xda-developers.com/viewtopic.php?t=18963
(didn't even need a hard re-set!!! :lol: my memory is fine now.
Loaded Nav 5 onto my unit from update CD
Then loaded all the maps from the 6 CDs (Hmm, that bit is still very naff but better than with Nav3), they won't quite fit onto 2 1gb SDs, & activated the free trial of TT Plus.
Then I drove from Sudbury, Suffolk to Dover via London, using the GB map, then on to Belfort, France (near Swiss & German borders) I always go via Luxembourg to avoid the french tolls. put in Belfort and Main Roads of EU kicked in from main app. it immediately asked if I wanted to avoid the toll roads, clicked yes & lo & behold it found my tried & tested route! Impressed! What's more it din't crash once :wink:
But when you get an incoming call it cuts of your GPS connection but then (most of the time) it re-establishes it (tho sometimes you have to re-configure, but that's now a lot easier if you use a TT receiver)
Last night used it all the way to Roskilde, Denmark, tonight we're off to Kristiansand, Norway. So far so, very, good!!!!
See! When something's right I big it up! I don't only whinge about the negative bits!!!
So far it's a big well done to TomTom for this version (XDA IIi-wise anyway)
Same here matey. Recently installed TT5 with GB maps only onto my XDA 2. No problems at all, connects within 20secs, never crashed yet and even works when receiving calls on my bt headset. GPS doesn't disconnect and when I hang up, it shows me at the correct location.
GENIUS
ive got an XDA2i and my TT5 seems to crash more often than not. especially when searching for POIs (ie take me to nearest petrol station... CRASH)
i admit i am using a hooky version, but if it's this bad i wont be buying it! (which i intended to)
im running an XDA2i with corporate install (no O2 Active UI) and an aftermarket bluetooth GPS.
its also annoying that TT5 disables bluetooth when you quit, and its v. awkward to re-enable it whilst driving (its a little button afterall...)
I'm using a hooky version too. TT5 £10 from ebay!!! Works like a dream. I've got an XDA II, removed 02 Active UI.
Bluetooth doesn't disconnect when TT5 is ended. I must be so lucky!!
jim galbally said:
ive got an XDA2i and my TT5 seems to crash more often than not. especially when searching for POIs (ie take me to nearest petrol station... CRASH)
i admit i am using a hooky version, but if it's this bad i wont be buying it! (which i intended to)
im running an XDA2i with corporate install (no O2 Active UI) and an aftermarket bluetooth GPS.
its also annoying that TT5 disables bluetooth when you quit, and its v. awkward to re-enable it whilst driving (its a little button afterall...)
Click to expand...
Click to collapse
I'be got a ~5mb patch which will fix this problem, EVERY time I turned on certain POI's it would crash
Not any more and it seems MUCH more stable.
If you've got anywhere I can up it, let me know.
jim galbally said:
ive got an XDA2i and my TT5 seems to crash more often than not. especially when searching for POIs (ie take me to nearest petrol station... CRASH)
i admit i am using a hooky version, but if it's this bad i wont be buying it! (which i intended to)
im running an XDA2i with corporate install (no O2 Active UI) and an aftermarket bluetooth GPS.
its also annoying that TT5 disables bluetooth when you quit, and its v. awkward to re-enable it whilst driving (its a little button afterall...)
Click to expand...
Click to collapse
Jim, there is no way of knowing what bugs can arise when using patched/cracked software. I never use bluetooth gps either since I got an xda because I see so many problems, also if its for car use only I think a wired gps is more practical/reliable.
@ PC_Arcade:
You could always post the patch here, but if not then you could always PM me with the patch, it would be HIGHLY Appreciated!!!!!
Cheers!!!!!!!
OK, I've PM'd you the patch
Please could you upload it to the ftp for me (I'm @ work and I can't use FTP) so it can be linked here?
cruisin-thru said:
Jim, there is no way of knowing what bugs can arise when using patched/cracked software. I never use bluetooth gps either since I got an xda because I see so many problems, also if its for car use only I think a wired gps is more practical/reliable.
Click to expand...
Click to collapse
...TomTom5 is known to have a lot of bugs, even for legit users. I've had every version of TomTom and every major release sucks till they patch it..
@ PC_Arcade:
If the patch is too large for PM, you could always email me!
Thanks again in advance!
Cheers!!!
it's just over 5mb, too big for hotmail too IIRC
dangel said:
cruisin-thru said:
Jim, there is no way of knowing what bugs can arise when using patched/cracked software. I never use bluetooth gps either since I got an xda because I see so many problems, also if its for car use only I think a wired gps is more practical/reliable.
Click to expand...
Click to collapse
...TomTom5 is known to have a lot of bugs, even for legit users. I've had every version of TomTom and every major release sucks till they patch it..
Click to expand...
Click to collapse
Just for the record I am a legit user and I like TomTom 5 just for one reason and that is the street signing, its like somebody is holding the sign out for you to read as you go along, neat.
OK, the patch is here
I have been totally unable to upload it onto the ftp here
Could someone please move it to there so I can change the link?
Thanks VERY much for the patch Arcade, have yet to test it, but I'm sure it will help. Installed it into the "2577" folder, is that correct? Its the only one with "ttn.cab" in it.
On a seperate note I want to install TomTom on the main memory of my XDA, with the maps still on SD card. I've heard this helps. Anyone know exactly which folders I need to copy to memory? Is it all, except maps? How will TTN know to look on the SD card for the maps though ?
Chop - thanks for success story, I brought the XDA and TTN5 expecially for a road trip around europe in a months time. Although I'm taking paper maps for backup, I was hoping I would be able to rely on TTN5. Don't think thats gonna happen now.
foaf said:
Thanks VERY much for the patch Arcade, have yet to test it, but I'm sure it will help. Installed it into the "2577" folder, is that correct? Its the only one with "ttn.cab" in it.
Click to expand...
Click to collapse
Not quite, you need to copy all the files in the rar over then run the .cab file. which will re-install TTN5
For safety's sake it might be work backing up your data.chk file as well.
On a seperate note I want to install TomTom on the main memory of my XDA, with the maps still on SD card. I've heard this helps. Anyone know exactly which folders I need to copy to memory? Is it all, except maps? How will TTN know to look on the SD card for the maps though ?
Click to expand...
Click to collapse
The easiest way is to reinstall tomtom using the patch I posted and just install it to main memory, it will automatically use the maps on the card
All I have on the storage card is the GB map directory and an empty tomtom directory, hope that helps
Chop - thanks for success story, I brought the XDA and TTN5 expecially for a road trip around europe in a months time. Although I'm taking paper maps for backup, I was hoping I would be able to rely on TTN5. Don't think thats gonna happen now.
Click to expand...
Click to collapse
TTN5 is fantastic, I can't remember how I lived without it :lol:
It's incredibly stable now too, although I did have to create a blank directory called tomtom on the SD card to get 7 digit postcodes to work
to make the postcodes work you need to put the file in a folder called zip in the root of the sd card.
Hi all
Could you tell me which file i have to put in the ZIP folder on the SD card?
@ pc_arcade : Is it the poi.dat file that is patched or the ttn.cab ?
Will it only work for GB map or for all maps ?
pleun said:
@ pc_arcade : Is it the poi.dat file that is patched or the ttn.cab ?
Will it only work for GB map or for all maps ?
Click to expand...
Click to collapse
It's the content of the cab file that contains the patched files
AFAIK it works for all maps, can anyone confirm?
Can you tell me how to get full (7 didget) postcode working please ?????
I tried looking on the forums but my head started to hurt can anyone help me with this
I have just helped my friend setup Tomtom 5 in their XDA IIi they are using the standard O2 rom only other app installed is sprite back up
They are using a wired reciever
Tom tom opens fine and aquires 7 or 8 sats no problems
Route is planned and off they go
But after a couple of mins it locks completely
No phone calls or texts sent or recieved to make it lock up, it just stops
I havent got a clue cos it worked fine for me on my M1000 and now on my Wizard, (i know about unticking recieve in coming beams)
At frist i thought it my be the reciever but surely it would'nt aquire the sats in the frist place
Anyone got any clues ??
My firend has bought this set up because of the way i priased everything up, and now it wont work and i fell like a muppet, please help so i can sort it out and look more brainer than I am
Have you applied all the upgrades for TT5?
No we have'nt upgraded it yet if we upgrade to 5.2 will this sort it out ???
Had the same problem myself - after trawling thru posts here changed my sd card to a transcend x80 one and works fine now.
Apparently alot of slower cards won't work in the xda2i for tomtom.
My original card was a 512 sandisk (bog standard type) and when i tried tomtom it just locked up after a couple of minutes ( running tomtom5.21).
Since changing to the transcend x 80 its not locked at all.
I bought a 80x 1GB transcend card after looking at the forums...didn't stop it crashing.
My symptoms are:
1. Freezes at more or less defined/fixed regions in the journey - conclusion: the phone handoff singalling when moving from one cell to another is causing the sd card to stop working.
2. Taking the sd card out and immediately putting it back in will, most of the time, get the device back on track, without having to restart the xda or tomtom softwre (only works for a limited no. of tries...after that a rest is required).
My fix:
take the sim card out OR put the device into flight mode (if not using bluetooth).
Still worth getting a high speed 'quality; sd card (like a transcend) for your pda... it makes moving files back and forth much faster...and it's more stable when watching mini videos.
Same here!
TT5 also crashes and closes after a while on my QTek S100. I tried to take out the sim card, but didn't work. Any more suggestions?
sd card
if i buy a new sdcard how do i transfer the tomtom data from the old card, a question from a complete novice, keith :lol:
Hi all first post here,
I bought a T-Mobile MDA vario on Saturday and wondered what size mini sd card I will need to load on the Tom Tom software.
Any advice will be appreciated :lol:
Please help I wanna order it online today so I can get it this week.
And also is it easy to do? My mate has all the software discs and he has done it on his ipaq will it be easy to do onto my phone? Could anyone post an idiot proof guide
bump
Don't know about TomTom's maps size, but can say it might be around
1 to 5Mb, so take 1 or 2Gb card and have fun not only with map, but mp3 either :wink:
I would think you would need as big a card as possible to hold the data. As to loading it then I would think it's a case of running the installer and aiming it at the memory card instead of main memory.
256 mb will be ok
Hi,
The maps will fit on a 256mb card.
I have a 256mb card and it is way too small- I have the TTN Germany map installed which only leaves approx 20 mb for MP3's, software etc.
I have just ordered myself a 1GB card from ebay (bargain at £12)
Guys thanks very much I will get myself a 1 gb card
Do not...............go for a 2gb minimum....you'll regret it else !
Oh...and I assume that you're purchasing TT from new...and not trying to use your friends..which is, of course, illegal. Not only that, but you'll (and he/she) will probably run into problems with TT trying to activate both devices.
nmonger said:
I have a 256mb card and it is way too small- I have the TTN Germany map installed which only leaves approx 20 mb for MP3's, software etc.
I have just ordered myself a 1GB card from ebay (bargain at £12)
Click to expand...
Click to collapse
can you post a link to the sellers shop please, all the ones i found were stupid postage to avoid the final value fees(unless their cards weigh over 20kg :lol: )
Here you go - gotta be quick - these go fast!
http://cgi.ebay.de/ws/eBayISAPI.dll...3927&ssPageName=MERC_VIC_ReBay_Pr4_PcY_BID_IT
I think this guy only ships to Germany (which is where I live at the moment) You may find that he ships to UK as well.
i bought a 1GB and wish i had bought a 2GB, learn from me and get the bigger card right away.
Hi,
I've tried searching but without much luck, so apologies if this has all been covered before.
I used to have a Hermes but I sold it because I was so annoyed at the Bluetooth problems. Now, I'm thinking about buying a Trinity but I'm worried that I'll get the same problems (i.e. bluetooth turning off if the device is suspended for 10 minutes or so; Voice Command not working properly, etc.).
I know about the slow-down issue if you hold the stylus on the screen, but I can live with that (and hope that there's a fix soon)!
So, if I buy a Trinity, am I going to be disappointed?
Thanks.
In my experience the bluetooth stack is quite reliable in the Trinity. It may not be as feature rich as the Widcomm stack but it works well.
The annoying problems with the trinity are probably those related to the miniSD cards disappearing, losing files, etc. Be sure to use a slow miniSD because things seem to be worse with faster cards. All in all I am not disappointed with my Trinity, but I am actually rather disappointed with the way HTC handles customer support.
Thanks. I'm still trying to decide between a Trinity and an Artemis.
Interesting about using a slow miniSD though - when I had my old Wizard, I had quite a few miniSD corruption problems on a slow card, but it never happened again after I replaced it with a fast miniSD!