Another weird tomtom5 thing - MDA III, XDA III, PDA2k, 9090 General

Tomtom5 will not stay running for more than 5 minutes!
i run it, it works then just closes for no reason.
Stranger still everytime i reopen it the tomtom hands move one space to the left on the bottom bar. (as if there were mutilple programs running)
it never used to do this with my old orange roms, but that was TT5 and now im using the imate roms and TT5.1 so im unsure of where the issue lies.
Help!

Turn of POI or just update to 5.10

turn off poi?
im running 5.10

I have exactly the same thing, both the closing issue and the icon moving along. I'm also using 5.1 on the imate 1.40 Rom. very wierd.
I'll try turning off POI tonight - but why does this affect it?

I have just upgraded to the imate 1.40 ROM with Radio 1.13 and have not experienced any tomtom problems (yet). :wink: It ran fine for my 45 minute commute this morning
I also hear that the imate 1.40 ROMs have problems with GPRS disconnects, but I've not experiences these so far - maybe its because I went to Radio 1.13

Related

GPRS attach weirdness on WMXL 0.10

I'm experiencing strange problem with GPRS on WMXL 0.10
After upgrade, GPRS can attach just when radio starts.
When attached, GPRS works just fine, but if GPRS occasionally deattaches (corresponding icon with 2 opposite arrows and 'x'), there's no way to attach it, besides restart of radio (phone off/on through comm.manager, or network select).
If I set "search [G] on start GPRS connection" via GB-Soft Tweak (instead of default "Search GPRS [G] on start radio") it never connects (unless network reconnect happens)
PIE silently does nothing, Opera says "Could not establish network connection [Error:33]".
Before upgrade WM5 could easily reattach GPRS if it was off.
Any ideas ? I've searched through the forum with no success.
Radio versions 1.35, 1.34, 1.27 were tried with the same symptoms (SSPL)
Thank you in advance.
HTC TyTN (HERM200)
WMXL 0.10
ROM date: 01/04/07
Radio 1.27.00.00
mih_ said:
I'm experiencing strange problem with GPRS on WMXL 0.10
After upgrade, GPRS can attach just when radio starts.
When attached, GPRS works just fine, but if GPRS occasionally deattaches (corresponding icon with 2 opposite arrows and 'x'), there's no way to attach it, besides restart of radio (phone off/on through comm.manager, or network select).
If I set "search [G] on start GPRS connection" via GB-Soft Tweak (instead of default "Search GPRS [G] on start radio") it never connects (unless network reconnect happens)
PIE silently does nothing, Opera says "Could not establish network connection [Error:33]".
Before upgrade WM5 could easily reattach GPRS if it was off.
Any ideas ? I've searched through the forum with no success.
Radio versions 1.35, 1.34, 1.27 were tried with the same symptoms (SSPL)
Thank you in advance.
HTC TyTN (HERM200)
WMXL 0.10
ROM date: 01/04/07
Radio 1.27.00.00
Click to expand...
Click to collapse
I would wait and see if the same happens on v0.2 ??
Have you used HTweakC to set the auto-attach? That is how I do it and I must say that I've not experienced this issue.
mrvanx said:
I would wait and see if the same happens on v0.2 ??
Click to expand...
Click to collapse
Certainly, i'll upgrade to 0.20 as soon, as it would be possible.
But I wonder, if i'm the one, who meet the problem.
Im the same. My connection on WM5 AKU3.3 was rock solid and if lost, would always reconnect. Now it is upredictable at best. Probably 80% of the time its fine but if I disable the connection overnight using bandswitch when the connection reenables I can pretty much guarantee that the data connection wont reconnect. None of the programs that should start it such as activesync will do so.
This is the one glitch that has had me considering going back to WM5, but Im hanging on for the next version hoping this will come right.
Ive tried different radio roms but makes no change. Currently using 1.27 which seems to be the best of the bunch.
Really want to stay with WM6 as I love the built in apps, especially the new email but this seems like a typical beta glitch.
Rob
kyphur said:
Have you used HTweakC to set the auto-attach? That is how I do it and I must say that I've not experienced this issue.
Click to expand...
Click to collapse
Yes, and it works - when radio starts, GPRS successfully attaches and everything is alright.
Until it occasionally deattaches (2 contrary arrows and 'x' icon instead of [G] appears) and there's no way to use it, besides radio restart or network reselect.
Q. to Kyphur:
robt2379 said:
Im the same. My connection on WM5 AKU3.3 was rock solid and if lost, would always reconnect. Now it is upredictable at best. Probably 80% of the time its fine but if I disable the connection overnight using bandswitch when the connection reenables I can pretty much guarantee that the data connection wont reconnect. None of the programs that should start it such as activesync will do so.
This is the one glitch that has had me considering going back to WM5, but Im hanging on for the next version hoping this will come right.
Ive tried different radio roms but makes no change. Currently using 1.27 which seems to be the best of the bunch.
Really want to stay with WM6 as I love the built in apps, especially the new email but this seems like a typical beta glitch.
Rob
Click to expand...
Click to collapse
Well, I've flashed AKU3.3 and GPRS reattaches transparently.
Is WMXL 0.2 worth of trying in order to fix this issue in your opinion?
Or, it needs "special" radio version? It seems interaction with Radio has changed in WM6.
I have the same experience with WMXL 0.10, when the connection is lost trying to reconnect will crash the connection manager.
No matter how many times you tap in the PIN for your SIM it will not reconnect.
So then it is down to soft reset or switching off to get things working again.
The HSDPA addin also don't seem to work for me. Even after shutting down the 3G / GPRS connection to change the band in HTweakC or in settings/phone/band.
i'm experiencing exactly the same.
after connection is lost gprs won't reconnect or if so it takes very long (10min?) even with a good reception. my gprs and 3g connection was very solid before upgrading to wm6. tried 1.27 and 1.35, same problems. even with nothing installed: same problem.
i've never experienced anything like that before. not on my hermes with wm5, not on my htc wizard or htc universal with wm6.
it has to be something about hermes and wm6. i don't know what it is. i did a HR many times and wanted to see which app is causing the problem (actually resco explorer runs weird on my hermes with wm6), but nothing. as i said even with nothing installed (just the pushmail being used) it's still the same.
and it's really annoying.
still no solution or explanation?
same problem here, FWIW. no solution AFAIK. I see Daniel has found some bug in WM6 as it relates to his bandswitcher app here:
http://forum.xda-developers.com/showthread.php?p=1169643#post1169643
facing same problem with k-jam (wizard) in WM6
i tried all radio ROMs but of no use
as soon as i shift back to WM5, it works flawless. i think the problem is with wm6
What is WITH everyone bumping the old WMXL threads???

Tomtom s..l..o..w..! (Official Dopod ROM)

Has anyone else had any issues with Tomtom Navigator 6 since upgrading to WM6 (offical SEA ROM)?
Under my old buggy WM5 ROM, it was perfect. As part of the WM6 upgrade I reinstalled it, and not it is unusably slow. It takes about 5 seconds between screen refreshes etc... you miss your turns by the time they are announced.
Does anyone know the cause or fixes? I've done a forum search and the problem has been reported on a couple of threads, but no real solution.
Some initial questions:
Under WM6, are people using the GPS manager in system settings? Or just pointing TT6 at the COM port directly? (What should the baud rate be set to?)
Is tngpseng.exe still required (never been entirely sure what this does exactly)
Does running it from the storage card (SanDisk 4GB) cause any performance hit? (I'm hoping not as my device memory is full)
The other chance I made is upgrading to the latest Australian maps. (Sinsis v675?) Are these known to be worse performance wise?
Does anyone else have Hermes, WM6 (official), TTN6, latest Australia maps working? can you post your settings?
Any help greatly appreciated!
Zilch said:
Has anyone else had any issues with Tomtom Navigator 6 since upgrading to WM6 (offical SEA ROM)?
Under my old buggy WM5 ROM, it was perfect. As part of the WM6 upgrade I reinstalled it, and not it is unusably slow. It takes about 5 seconds between screen refreshes etc... you miss your turns by the time they are announced.
Does anyone know the cause or fixes? I've done a forum search and the problem has been reported on a couple of threads, but no real solution.
Some initial questions:
Under WM6, are people using the GPS manager in system settings? Or just pointing TT6 at the COM port directly? (What should the baud rate be set to?)
Is tngpseng.exe still required (never been entirely sure what this does exactly)
Does running it from the storage card (SanDisk 4GB) cause any performance hit? (I'm hoping not as my device memory is full)
The other chance I made is upgrading to the latest Australian maps. (Sinsis v675?) Are these known to be worse performance wise?
Does anyone else have Hermes, WM6 (official), TTN6, latest Australia maps working? can you post your settings?
Any help greatly appreciated!
Click to expand...
Click to collapse
MrVanx's BT Receiver Setup
Works fine with me.
TT v6.201 (Build 7160)
OZ Map v675.1431
Zilch said:
Has anyone else had any issues with Tomtom Navigator 6 since upgrading to WM6 (offical SEA ROM)?
Under my old buggy WM5 ROM, it was perfect. As part of the WM6 upgrade I reinstalled it, and not it is unusably slow. It takes about 5 seconds between screen refreshes etc... you miss your turns by the time they are announced.
Does anyone know the cause or fixes? I've done a forum search and the problem has been reported on a couple of threads, but no real solution.
Some initial questions:
Under WM6, ....
Any help greatly appreciated!
Click to expand...
Click to collapse
Not related to WM6 but have you checked the number of Points of Interest that TT6 is trying to display. I use TT6 and have noticed no problems with WM6 so far - but regardless of ROM I found that unless I turned off the POIs that TT6 slowed right down and kept freezing.
Regards
tony.wheeler said:
Not related to WM6 but have you checked the number of Points of Interest that TT6 is trying to display. I use TT6 and have noticed no problems with WM6 so far - but regardless of ROM I found that unless I turned off the POIs that TT6 slowed right down and kept freezing.
Click to expand...
Click to collapse
Thanks Tony. I've turned them all off except the speed/red-light cameras and it does seem to have helped. (I won't know 100% until I take it out in the car, but it seems much faster at home on my balcony!)
The strange thing is I many POIs enabled on the previous install under WM6/older maps. Maybe the newer map is larger or something.
Does anyone know if custom POIs are more performance intensive than the build in ones?
I've had some kind of issue with TomTom since upgrading from Black Dymond (first to Magik and now to Satin). On the first upgrade I had to reregister my unit with my account to get access to my plus content (device ID change).
Now, I intermittently get a warning that it cannot find some file. I can't replicate it reliably and haven't had a chance to note the missing file. I suspect it has something with how TomTom is accessing info on the card.
My problem only presents itself when shutting down, so it's not a real issue for me. If it was, like yours is, I would first try increasing your caches. If that doesn't work, try going into the TomTom manager console when synced with the computer and remove everything (program, maps, voices, etc.) from your device/card and then reinstall it (make sure you have your disk or a backup, plus your registration code). If it has anything to do with lost file links, this should solve it theoretically.
I suspect your issues are due to either caching or lost links in TomTom itself, or both.
Tomtom has some problems with some wm6 roms not all.
My experience:
It worked fine with black dymond. No slowdown. No Problem.
It was painfully slow with black majik
It was OK with VP3g's v2.0 but after I added HTC home plug it slowed down considerably
Currently I am running latest Black Satin and TomTom runs just fine, stable, superfast, no freezes. This time I am going to stay away from HTC home plug.
You do not have shut down all of the 'nice to haves' (POI's) in such unnecessary and draconian fashion, quote "have you checked the number of Points of Interest that TT6 is trying to display".
Like Quist, I beleive the build of the ROM is much more at issue.
From my observations - Dopod / Black Satin / Sleuth's and Black Dymond are not at a problem.
I have noted significant refresh delays when using Schaps and Black Majik.
Good luck.
I've never seen TomTom run as fast as it does on my phone with vp3G's 3.0 WM6 rom.
I'm running TomTom version 6.100 (8330)
Im using Schaps 3.57a with TT6. So fast. Cold boot around 10s to 20s. Thanks

GSM/GPRS Crashing but Everything Else OK

I'm finding I tend to have to do a soft-rest on my MDAC III about once a day, because although the phone continues to function fine, the radio (i.e. the GPRS/phone, not the FM radio) crashes. All appears fine, the device still works and has a signal showing on the bar, but I won't get any incoming calls, I can't make outgoing ones, and when I look at Activesync, instead of saying "Exchange: Connected", it says "Exchange: Last synchronised at 10:48am", which I guess is when the thing crashed. It's very frustrating because the only way I realise this has happened is when I notice that I haven't had any e-mails for a while.
One thing I have noticed is, working in London, I use the tube, and on my normal tube journey the train goes above and below ground, so the signal frequently comes and goes. The times it shows me I lost my ActiveSync Exchange connection usually corresponds to these times, so I think it seems to be that the phone loses the signal, but then never picks it up again (even though the top bar shows it's got a signal).
I'm currently using a WM6 ROM (3.7), but I also had this with an earlier WM6 ROM and the original WM5 ROM.
Anyone else have problems like this?
Yep, had exactly the same thing with the SEA Dopod Rom, had to soft reset to get it working again. The problem seems to be more of an O/S thing as the radio update (2.95.90) didn't make a difference.
The worst I have seen it is on the Dopod Rom where I had to soft reset, I didn't have any issues with the O2 WWE rom (except that it was rubbish!). I am now on Tom's B&B 4 Rom which does have this issue but I am able to recover by simply restarting the phone side of things via the comm manager.
Its a bit annoying but I'm happy to live with it for now and I'm keeping my fingers crossesd that Tom can cobble together a 4.1 rom out of the Kaiser extract he's got his hands on.
Cheers
Alex
Yeah it's the SEA Dopod I'm running at the moment, and although I've always had this problem, it seems a lot worse with this ROM, and like you said, with the others I could just restart with Comm Manager.
I'm not a big fan of the B&B interface, so I guess I need to either roll back to WWE v3.5 or find an alternative v3.7

Artemis Vanilla 4.01 and Touch 4.01 issues

I have serious problems with Touch 4.01 and even Vanilla 4.01 reported as stable. It is fare away to be stable at all. Continuous freezing the mobile phone functionality. Telephone looks like everything is fine, but SMSes are not delivered and calls are in my voice mailbox. To find out the problem, I have downloaded Bepe's Artemis kitchen 2.1, what was (my feeling) the source of this ROM. And possibly recognized the problem. The Bepe issued two versions, second is fixed. But it seems that this Vanilla and Touch (4.01) has been generated by the first one. I have checked the size, date and time of OEMDrivers and they are different. Meschle, is it possible to generate your ROM by this fixed version? Thanks in advance.
josef.bilek said:
I have serious problems with Touch 4.01 and even Vanilla 4.01 reported as stable. It is fare away to be stable at all. Continuous freezing the mobile phone functionality. Telephone looks like everything is fine, but SMSes are not delivered and calls are in my voice mailbox. To find out the problem, I have downloaded Bepe's Artemis kitchen 2.1, what was (my feeling) the source of this ROM. And possibly recognized the problem. The Bepe issued two versions, second is fixed. But it seems that this Vanilla and Touch (4.01) has been generated by the first one. I have checked the size, date and time of OEMDrivers and they are different. Meschle, is it possible to generate your ROM by this fixed version? Thanks in advance.
Click to expand...
Click to collapse
Hi, how long do u have such problems and who is ur mobile operator. according to ur name I suppose that u r from Czech Rep.
I'm asking b'cause during last weekend I had also problem with my phone which leaded to reflashing of my phone but it was problem of operator.
I'm by O2 and have O2 XDA Orbit. I wasn't able to get any sms or report of delivery, i could send them only. and now i have bit different problem, sometimes sms from me is delivered, is shown in phone but it is something what i sended already before and then it dissapears from phone reciever's phone.
Such serious problems with ROM are strange, b'cuause those ROMs are out more then month and as I know, nobody had the same problem as u. I'm using Touch 4.01 without cube from first day when it was published here with no problem. i'm not couting problem with memory leaking which is probably problem of wm6.1 rom in general then Touch 4.01.
No, I am not only one who referring this problem. Look at this thread: http://forum.xda-developers.com/showthread.php?t=375930
Correct, I am from CZ and using T-Mobile, but in roaming quite often. But it happens independently on network. Touch Full 4.01 was more or less horrible, Vanilla 4.01 is better, but still time to time is freezing the radio part. To avoid discussion about radios, I have tried last 3 versions with the same result (3.08,2.98,2.97). But I really believe that problem is with OEMDrivers in Bepe's Kitchen. What Bepe even highlighted, that these drivers in first version are for different type of phone. The most stable version, what I had, it was B&B4.2 for more than 1/2 year. But of course WM6.1 is much faster. It was my reason for upgrade.
ok, then i cannot help, this is up on guys which r cooking ROMs.
will cross my fingers for u to solve this problem. it is nice from guys that they provided new ROMs based od WM 6.1 two months earlier than Macro**** but such serious problem takes us back to prehistory, b'cause having phone with which u r scared to call b'cause of freezing has no point.
Same problem here, flashed a lot of different roms to my device but only having these freeze problems since touch 4.01.
Right now it's only once per week. But it's been much worse: reboot, lock after 30 secs, freeze 5 secs later, repeat. Had to reflash my device. (And i always flash twice with a new rom).
I hope the fix is as easy as just building the rom with a newer version kitchen.
same problem for me.
i am running 4.01 Touch with full cube, operator is orange netherlands.
sometimes i have to reset the phone 3 times a day, after that i get a whole lot of sms (normal) and the calls i missed.
going to try 4.02 now, hope that's one's better
doesnt matter what version do you use - but always flash twice(one by one) and make a hard reset after flashing. Result is - much more stable work.
@d3ton4tor
I'm on dutch orange too, but haven't had a problem with touch lite 4.01. I'm using touch vanilla 4.02 now and still no probs.. I've got a MDA Compact tho..
I never had any problems with 4.01, or any of the previous roms, but since using 4.02 i have had several lockups now, about once a week. So maybe i better reflash it again see if that cures it ?
It is interesting. I have made update for Touch Vanilla 4.02 and everything works perfect. Sometime the less is more. I would never go for all Cube staff, it is only the memory eater from my perspective. I have realized that I can remove from StartUp folder WiFi link (I have T-Mobile ARTE110 - WiFi missing) and it is better. Under more or less conditions above 20 MB and it is very valuable especially for navigation SW like iGO.
Try PagePool 8M
Try PagePool 8M.
Pagepool
My English is so bad.
Or try the 4.02 it works fine here in my HTC 3300 also t-mobile client ;-).
Flashed it yesterday and works fine no freeze or what ever, even gps and radio works fine.
Greetz THeM
Destinator n maps
hey i just installed destinator 7 on my o2 orbit it doesnt detect the map infact no map at all
can any1 help me with this???
Hi,
You need to ensure that the maps folder is included in the destinator apps folder. That is when your destinator would be able to detect the maps.
By the way can you share your Destinator 7 (Mumbai Map) with me ??
Regards,
kailash
I too have problems with the Touch 4.1 vanilla rom but my issues manifested themselves after I had been using the rom for a while without any problems. Now I run out of memory quicker when using PIE and have to reset a lot more. Also sometimes am unable to connect to GPRS/EDGE without a reset. I will be trying any new roms that come out but its becoming clear to me that I need to upgrade.

verizon tp2 problem...

hi my friends,
I'm getting real mad with this verizon tp2 gps,
this is the problem, i solved he problem with the gps lag in tomtom installing the moddriver app or using copilot, when i start the gps program, all work fine and really fast, but after 15/20 minutes of use, the program (copilot or tomtom) start to lost the gps fix and after a while is not more able to fix the satellite anymore (the back of the phone became real hot also), i have to close the program and restart but after few minutes it happens again and again...
i tried many different rom, the stock 6.1 and 6.5, energyrom and many other, all gave me the same problem....
the radio can affect the gps?
please help me, i need the gps badly...
thanks
p.s. usted the task29 app to clean completely the phone and now re installing the
"RUU_Rhodium_W_WM65_VERIZON_WWE_3.04.605.3_RS_2.23. 00WV_NV_VZW_1.94_1111_PRL58005_Ship.exe"
now i will try...
p.p.s. first freeze on copilot after 30 min o perfect working....

Categories

Resources