WM5 GPS issue and really easy question - MDA III, XDA III, PDA2k, 9090 General

Get the really easy question out of the way first. In the wiki and other places concerning making settings last through a soft restart to poweroff the device for 10-15 seconds. What exactly does that mean, just press the power button and wait 10-15 seconds? I thought that only turned the screen off...so is that not the same as just waiting 10-15 seconds or am I missing something.
Now to the GPS issue. I got a BT-338 and iGuidance (2.1.3 + WM5patch from the inav site) for Christmas and installed it on my laptop and BA (PDA2K w/WM5). Everything works correctly on the laptpop, it shows the correct coordinates and the software worked great as I drove around. However, when I use iGuidance on my PDA, it gives me incorrect coordinates (ex 22.625977N 2.347656W which is in Africa and I am in Alabama). I have checked out the posts at gpspassion.com and followed the standard setup. I feel like I have tried just about everything, but I just can't seem to get it working.
So, does anyone have any insight as to what the problem might be or have any ideas as to how to trouble shoot this problem?
Thanks in advance for the help,
Jonathon

Related

Boot Delay

I was wondering if anyone has a solution for my strange problem.
When switching on the unit from the power button there is a 20 second delay before the today screen shows up.
The backlight comes on initially and I get a black screen for about 20 seconds then the today screen loads.
If I swithc the unit off and on rapidly then there is no problem , but if I switch it off ( using the power button of course) and leave it for a few minutes I have to wait for the screen to boot.
Wierd eh?
Rom: 1.31.00WWE
Rom Date : 12/13/04
Radio: 1.06.00
Protocol: 1337.38
Ext Rom : 1.31.139WWE
Help please if you can , thanks to all.
I'm guessing it's just the programs you have running on Startup and that's how long it takes to boot.
I'm running PhotoContacts (with 301 contacts/photos), GPS Gate, vCard, Voice Command, MultiIE, GPRS Notify, and some other bits and bobs and I'm lucky if I get into mine in under 45 seconds. I know it's just the software loading that takes a while because if I remove all the startup files it boots up in a matter of seconds.
Take a look in \Windows\Startup there might be things in there you don't need loading on startup, but MOVE them out of there to somewhere else rather than delete incase you have to put them back later!
Oh and "Today plugins" as will also slow you down since it'll have to load each one of those and each plugin will have to "update" itself on the screen as well before the device is fully usable.
Hi , thanks for the reply!,
The device has had a hard reset and is not running anything on startup , I actually did a corporate install so I don't even have the O2 active gubbins going on.
Yet mysteriously the boot up is ages slow!!!!!
Its got me highly baffled and frustrated.... argh
Hmm I'm not really sure what to suggest. I cooked my Extended ROM / Got rid of everything O2 as fast as I can so I can't remember what the times were like on mine for starting up with O2's firmware. Sorry!
Hey Xanth , thanks for trying to help!
Looks like I'm going to have to bite the bullet and do a reflash of the rom and etc. , hope that cures it or its going to be an interesting phone call to O2.
Unless anyone else has any suggestions it seems that the flashing is my only recourse.

TomTom lock up

Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
I am still on my S100 with tt6 6.010 (7720) and no SIM since I currently use it solely for navigation. What I experience is not really a lockup but just a big delay (almost 1 min) after tt has initialized and only if "Enable wireless data" is enabled.
UPDATE
Turns out that this was a system resource problem. I have Wisbar 2 Advance, PocketBreeze 5, Phone Alarm, and PhotoContacts Pro all active on my device. I guess this is just too much to handle for the Omap when I try to add TomTom on top of that. When I exit WA2, PA and PhotoContacts, shut the device off for about 30 seconds, then turn it back on and launch TomTom, I have no problems. I have also been able to do it only shutting down WA2 and PhotoContacts, but it still locks from time to time like this. I have to shut down all three to be safe. Leaving PocketBreeze running (with some plug-in tabs active too) seems to be a managable workload for the processor. It's kind of a pain, but at least it works! It's not like I need a nav program every day!
Later...
Glad to know you found the source of your problem.
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Magic Button - Pocket PC Task Manager
This will CLOSE the program instead of MINIMIZING it to the background process.
JC#79 said:
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Click to expand...
Click to collapse
I only started putting things on the card two days ago - day two i started having tomtom problems.
I'll def give this a go though and let you know if any improvements...
Thanks!
i have the exact same problem with my dopod p800w/artemis etc etc......i found a way to eliminate the freezing and hanging.......rule of thumb is to open the program by going into its root directory and opening it from there, instead of opening it via the start/programs shortcut or today screen......basically just make sure you open the program by going into File Manager and look for the tomtom navigator.exe file (usually in the program files folder and then navigator folder) and open it that way......ever since i tried it this way i never get any freezing and the program would start all the time.......it works for me......

M3100 thinks something is constantly tapping top right corner of screen

I've been trying some WM6 roms on my M3100 (Black and two versions from Faria so far, along with HardSPL and the latest radio rom). While they all seem to work very stably for the most part, I find that if I turn the wireless on after a few minutes the phone starts reading constant tapping on the top right corner. So if I'm in landscape mode, the Start menu keeps popping in and out, and if I'm in portrait it hits the close button and everything I've got open disappears.
I've read about some Hermes having alignment issues, but I'm not sure this is to do with alignment, it seems to read other taps correctly if I touch the screen while it's malfunctioning, but it doesn't stop reading tapping in the top right.
A soft reset or turning the wireless off usually cures it for a while, but as soon as the Wi-Fi is on it can start again. If I turn the phone off fully, it seems to last longer when the Wi-Fi is on. It's almost like it's overheating and turning it off means it starts off cooler and has longer to heat up. Black was much worse than Faria's for this, as it had more stuff running by default. I had a devil of a time getting it stable enough for ActiveSync to work so I could flash something else.
I've tried searching the forums and I couldn't see anything, but I might not be using the right search terms. Has anyone seen this before and can you offer any advice/fixes? If not I'll probably make the long slog back to WM5!
Thanks for any help you can give.
This is a common problem with the Hermes. Search for touchscreen problems and you'll find you're not the only one with the problem. My previous one had the exact same symtoms, only it did it when the ambient temp was about 90F or so. I'd advise you to either look at getting it repaired, or look for another one. It's not going to fix itself
photoboy said:
I've been trying some WM6 roms on my M3100 (Black and two versions from Faria so far, along with HardSPL and the latest radio rom). While they all seem to work very stably for the most part, I find that if I turn the wireless on after a few minutes the phone starts reading constant tapping on the top right corner. So if I'm in landscape mode, the Start menu keeps popping in and out, and if I'm in portrait it hits the close button and everything I've got open disappears.
I've read about some Hermes having alignment issues, but I'm not sure this is to do with alignment, it seems to read other taps correctly if I touch the screen while it's malfunctioning, but it doesn't stop reading tapping in the top right.
A soft reset or turning the wireless off usually cures it for a while, but as soon as the Wi-Fi is on it can start again. If I turn the phone off fully, it seems to last longer when the Wi-Fi is on. It's almost like it's overheating and turning it off means it starts off cooler and has longer to heat up. Black was much worse than Faria's for this, as it had more stuff running by default. I had a devil of a time getting it stable enough for ActiveSync to work so I could flash something else.
I've tried searching the forums and I couldn't see anything, but I might not be using the right search terms. Has anyone seen this before and can you offer any advice/fixes? If not I'll probably make the long slog back to WM5!
Thanks for any help you can give.
Click to expand...
Click to collapse
also try the business card fix on your hermes maybe your screen protector is hitting or the foam liner inside has jammed itself. or maybe something like a piece if dirt has lodged itself in there. there are many things that could cause this some being hardware other being dirt dust chunks of stuff
If it appears when it heats up (sounds like it does), chances are you're looking at a repair/warranty. Just sent one in to HTC with the same problem. I replaced the screen myself and thought for a day or two it was fixed, but as soon as it went on the charger for the first time the phantom tapping returned.
Thanks for the help guys! I'll have a look and see if there's anything trapped in the corner or if the seal is pressing on it and if not I'll get it repaired/swapped.
unfortunately, my M3100 does the same problem as yours, photoboy..
i noticed the problem starts when the pda gets warm..
anyway, tomorrow i'll take the "toy" to warranty.. and see how it can be fixed

Phone will not come out of standby

hi guys,
has anyone experienced a problem where their Trinity will not "wake up" with the short press of the on/off button?
I'm sure I read about this some time ago and am trying to work out if it's hardware or OS related.
I'm running mUn's TE WM6 which I have been for many months now.
The problem has only started in the last 2 weeks or so.
I haven't installed anything new, but have enabled Push Mail for OTA mail.
It's doing it 1 or 2 times a day now and is very frustrating. The only way to wake the phone is soft reset.
When calling the phone from a landline, it does not ring and goes to voicemail.
Any advice or solutions gratefully received.
no one seen this then I guess.
Bummer (for me!)
Try hard reset
sickboy555 said:
hi guys,
has anyone experienced a problem where their Trinity will not "wake up" with the short press of the on/off button?
I'm sure I read about this some time ago and am trying to work out if it's hardware or OS related.
I'm running mUn's TE WM6 which I have been for many months now.
The problem has only started in the last 2 weeks or so.
I haven't installed anything new, but have enabled Push Mail for OTA mail.
It's doing it 1 or 2 times a day now and is very frustrating. The only way to wake the phone is soft reset.
When calling the phone from a landline, it does not ring and goes to voicemail.
Any advice or solutions gratefully received.
Click to expand...
Click to collapse
Try hard reset
softreset helps, sometimes i have the problem with windows mobile 5 too
jmermel said:
Try hard reset
Click to expand...
Click to collapse
thanks John.
But do you have any fact based reason for this suggestion?
I'm happy to give it a go if there's more than 50% chance it will work.
Hard reset
sickboy555 said:
thanks John.
But do you have any fact based reason for this suggestion?
I'm happy to give it a go if there's more than 50% chance it will work.
Click to expand...
Click to collapse
You might have loaded a program that is not liked. Use a backup program. If this does not work then load your backup after the hard reset and you will be back to where you started
P3600 with D810 WM6 ROM; also happens occasionally, recovered with soft reset. Seems to happen most often when I press the On/Off button twice too quickly.
thanks guys.
I'm going to try the hard reset route-I'll report back.
Some time ago this happened to me so often, but said it was due to some application, in my case was Slide2Unlock.
Since I removed by their consumption of memory it didn't happened to me.
(Sorry for my english)
Bugger, this has started to happen to me as well. Only 3 times in the last 3 days but if it keeps is up that will be enough for me to do a hard reset (overdue). Strange cause the only new thing I put on in the last week has been PCM 16 which is only a copy/paste exercise.
The fix in the Hermes forum is to force your device to sleep and not let it go into standby.
I have had some problems recently with DeviceLock 1.2 just ceasing to work and have to uninstall/reinstall to make it work again. I set it to turn the screen off when locked, as this does not put the device on standby, maybe there is the same issue with it going into standby by itself.
I have the same problem..i think that it has to do with the phone hanging..most probably due to some background programs eating too much power and memory and the phone just lacks till it hangs..happens when you have other programs that have hanged as well..my problem is with PocketAlarm..it takes so long to load my phone went to standby and the phone couldnt be called back..in brief the phone just hangs because of a program..i don think it has any problem do to with the hardware or strictly the OS..cant really explain..but the role the OS play in this problem is that it allows the program to make full use of the phone till the phone cant cope with it..its the core of the OS so it cant be avoided with any other versions or anything..sorry it seems rather unclear..hope you guys understand..
same problem for me ... from times to times, when a call hang up, i push a lot of times the red button for going back to the today screen and as it shows up, i click immediately on the Power button for turning off the screen. right after when i forgot to do something (approx 1sec) i push the power button and there it doesn't turn on the screen ... strange ...
what i've installed on it :
TomTom 6
BatteryStatus with today plugin ver 1.04.203 beta4 i put tray icons too.
i've bluezard for sniffing and/or hacking bluetooth devices.
OBDgauge too it's a software that works with a bluetooth dongle i plug into the diag port of my car.
and that's all. ah yes one more thing -> i disable the "HTC Home" because i don't like it.
Same problem here...
Still no solution?
I got this problem from some version of rom by Karmba. But V7.2 is OK so far. It seems happened when I close Egress reader by click X button then turn off screen by power switch. It then would not wakeup again. But if I close Egress and check the running programs from Task Manager to make sure the Egress is not running at the background, then I can turn on or off the screen freely.
So I think this wakeup problem is caused by some running program that was not closed properly by X button then crash the WM.
That was just my personal finding. Hope it help you guys a bit.

Touchscreen problem with WM6?

Hi, to all!
I have a problem with the touchscreen of my hermes alias O2 trion.
When starting from cold state the touchscreen works normal. After some time the screen reacts not allways and shortly after that it does not react at all. Reset does not change anything.
Is it a upgrading problem or is it a hardware problem?
Here the hole story:
I bought a used device with Win Mobile 5 on it. At the first try out it worked, but afer some time the screen did not react to my stylus at all. After a reset it worked again so i dit not pay much attention to this and upgraded to official Windows mobile 6 (which was downloaded from O2). Update worked fine.
Then i ran a rom update on the computer to change the start screen. The tion disconnected (update stopped at 0%). Little shock, but the trion still worked. The program and radio versions did not change.
First thought: this was no official update, so trion did not accept it. Was something installed or was everything blocked?
Could this make problems?
What do you think?
Thanks
i think this problem:
http://forum.xda-developers.com/showthread.php?t=285062
Alienax said:
After some time the screen reacts not allways and shortly after that it does not react at all. Reset does not change anything.
Click to expand...
Click to collapse
Did you try to re-calibrate your screen? It could be a question of the screen loosing calibration so bad that when you press it, it works but you are not HITTING any buttons, because the calibration is off...
I have that problem with my Hermes, I need to recalibrate several times every day, especially after sliding out the keyboard (since the screen flips then) .
There's a very nifty short-cut to the calibration app: press the middle button on the D-pad while pressing the messaging button to go to the calibration screen, then press the middle D-pad button to launch the calibration (same as pressing "calibrate" with your stylus).
There seems to be a lot of Herms that have serious calibration issues. I'm personally so tired of it I am thinking of buying something else.
Good luck,
Laz
It's KNOWN hardware issue where the processor heats up and *somehow* transfer heat to the digitizer which make it unresponsive. I got a Hermes just like that laying around. Can't fix it.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Problems
Thanks!
Today the touchscreen worked good. Even playing spider solitair was possible. Then i pluged it into power supply and the device got slightly warm. The touchscreen did not work any more.
Could be a heating problem of the prozessor like Mikro_ Tech described. Thanks by the way
How can i be sure it is this problem and not something else?
@LazPL: That was one of my first thoughts as well and i did.
When the Touchscreen works, it works just fine and accurate. Then it behaves strange (sometimes not corresponding to touches, programms close all of a sudden) and shortly after that it doesn not work at all.
@the_passenger: The Hermes Version is HT 626... Anything special to this, because the link just lists screen allignment issues for this modell?
What do you think of the solution from the link LazPL posted?

Categories

Resources