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??
hope someone could help...
im having problems with my 1G SD memory card. I have mp3s and movies on there and when i enter it into my XDAII and play it while using another program (ie file explorer), my music/movie lags and skips. What's the problem? is it because my device is dirty? or a bad card? it was running smoothly before when i first bought it. But now its doing this when i play music.
help please
i had the same problem once
i solved it by removing journalbar which took
too much cpu while running so the xda2 got audio issues
try removing your today items one by one and see
also using the program
www.GB-SOFT.cz/XDAII
and setting audio streaming prioity up also helps alot
thank you sooo much it worked.
Hi. O2 swapped out my 2s for a 2i. I've got a MMC card with some MP3s on used to play fine in WMP9 on the 2s however... on the 2i the song cuts out randomly and crashes WMP10 until I take the card out and put it back in or do a soft reset. Also my friend with another 2i has the same problem playing video files from storage card it hangs in random places... Anyone else experienced this?
Cheers
I have similar issues though I find its if I actually have something running/playing from the storage card and have to use the phone...
so its just another crappy bug then? Text messages or the phone ringing also kill WMP on mine aswell...
I've had problems with SD card on my XDA 2i.
It keeps freezing up when programs are run from storage card, or playing music or video from storage card.
Anyone else come across this? And is there a solution to it?
Is anyone able to shed some ight on this problem?
I cannot fit much else on the built in memory after installing tom tom navigation software and maps. Installing it to the memory card causes the program to freeze after a few minutes, and i have to reset.
Please help.
I'm not experiencing this.
I woul not run programs from the SD. Just store the maps there. I'm using Tom Tom too - installed in main memory and maps on SD.
Hi, I had a similar problem with my II when running TomTom, with the maps on the sd card. Changed the make of the card and all now well. Seemed as if the card was not compatable with the XDA.
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:
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