Since I installed tomtom5 my XDA2s is no-longer powering down after a set period of inactivity.
Anyone else seen this situation and fixed it?
Related
I have been having this strange problem of my eten m500 going to sleep and requiring a hard reset to wake up once a week.Normally this happens on fridays/saturday/sundays.
when i urgraded the rom it didnt sleep for a good 15 days but again the problem has started.
Any thoughts as to what the problem could be?
You might find the answer in this thread.
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
Hi,
I have a Problem with my mdaIII. When bloetooth is on and my Blueangel go out after 3 minutes, sometimes it makes a softreset when I power up it again.
Can anyone help me???
Thanks Grave
rescently my artemis has started to be unresponsive for about 10sec to 15sec after pushing buttons. i've removed all the software installed since it started happening but it still does it. I usually notice it when trying to turn on the device. It will not come on at first. Also does it while the phone is on. Just wondering if anyone else has experienced this.
BTW: I'm using the latest O2 Premium ROM. Too bad Meschle's retired
I think I found my problem. The refresh rate in BatteryStatus was changed from 10 to 5 around the same time this started. Since I've changed it back to 10 I haven't had the problem since. Strange.
I have a Sprint Touch Pro2 running stock 6.5 ROM and a 2005 Acura TL. When I got the phone a few weeks ago, I was able to pair the two without problems and it persisted reliably. I was able to shut BT off and turn it back on and the pairing would take place immediately.
Four or five days ago, though, the pairing would drop periodically, forcing me to re-pair, and now, the pairing will disappear almost immediately if I'm able to get them to pair at all. Most of the time I can't get the phone to 'see' the car.
FWIW, I use my own 4-number PIN, and when the phone sees the car, I'm able to enter that PIN and pair them.
I of course was installing a lot of stuff on the phone, although nothing that one would expect might affect the BT, so I flashed back to the stock 6.5 ROM last night to see if it helped (it didn't- same prob today).
Before I take this thing back to Sprint and smash it on their counter, anyone have any ideas about settings I might not be aware of that could affect this?
Thanks in advance for any help.
PS: I'm going to be testing my old phone (Treo 800w) on the car later to see if it still pairs to eliminate the car as the problem.