Related
i am new to pda's so take care with me, i am a real novice!!
any way it keeps frezzing up,
i have tomtom 3 blutooth sat nav, loaded on, which a college has given me!! it works fine but every time i touch the pda it frezzes (plus i dont need to touch it it just does it on its own accord,)
it isnt just when the tomtom is on,
it does it what ever i am doing!!
if you can help, please do!! but remember i may need well detailed info on what to do to rectifi the problem,
thanks bill
Bill, I had a similar problem with my wifes XDA II when I loaded Tomtom software onto it. I did the following and it resolved the problem for me, so you may want to give it a try (assuming you still have the problem).
Tap on Start (on the desktop screen)
Select Settings
Select the system tab at the bottom of the screen
Tap on the memory icon
Select the Running Programs tab
This opens up a window which shows you all the programs which are currently running on your PPC
Select STOP ALL from the options available
This will close all programs running on the system and free up your memory resource, so now go back to the desk top view.
Then start your Tomtom program up again as you would do normally and see if it freezes on you this time.
IMPORTANT ADVISE - You must close Tomtom down from the options within the program which, on my system is a large red EXIT APPLICATION icon found in the Navigator Menu.
Hope this works for you as well as it did for me.
Good luck :lol:
Piper
8) Go to the windows startup folder and delete connections.exe.
That will free up a lot of resources
Fatzzz
whats this do
connections.exe.
Other than connections.exe..
Hey everyone,
I just received my XDA IIs from Hong Kong 3 days ago. Since then, the PDA portion is working great. But the phone keeps locking up. I cannot hear caller and they cannot hear me. I have been soft resetting at least 2 x a day...and missing calls..
is there anything else that we should delete?
Thanks!
max0002
There is an inherent problem with the audio on this particular model (Blue Angel)
The problem seems to escalate if you use the Bluetooth Audio.
I experience the problem 2-3 times a week, even with the connections.exe removed from the Windows/Startup Folder.
Hopefully a new release of the Radio/Firmware will cure the problem.
Fatzzz
Since I've installed Rom 1.40, I've literally never been able to use Bluetooth without doing two consequtive soft resets. Bad case of "insufficient driver memory" -- I don't know if anybody else has it that bad? I've read all the posts about this and nothing seems to help in my case (BA with Rom 1.40, BT 3900, NOT running SPB Pocket plus).
Anyway, I did a routine pc backup just now with Sprite, which kills all processes first. When the backup is complete, it always prompts to perform a soft reset (in order to resume all processes that are normally loaded at startup, I guess). I was wondering what would happen if I didn't do this so I pressed cancel. Then I tried to turn on Bluetooth -- and voilà, it worked.
Ok, guess it's pretty logical, anyone could have figured out that some running process must cause the "insufficient driver memory" error. But I'd like to examine this further and find out which process exactly, hoping I might one day be able to use Bluetooth by killing that process (if it's nothing vital, off course) instead of doing my usual two soft resets.
So my question is: does anyone know of an application that can show and kill running processes (more selectively than Sprite Backup does), and that isn't too large?
This is a great question.
Ever since 1.40 has been installed, I feel like my SX-66 just "isn't the same" anymore.
I am not sure if it has to do with the 1.40 upgrade, or another app I installed, but I tell you...
I need to suspend the unit and turn it back on to get Wi-Fi to work sometimes.
I need soft-resets for the BT driver to work...
I'll often put it in the cradle and activesync starts and then stops right away...
(And plus I am stuck with the buzzing oscillator, too).
This has gone from my #1 favorite PPC in the world, to something that is getting more and more annoying.
I wonder how things would have been if I left the OLD firmware, the OLD EXT-ROM, and the OLD Radio ROM, right out of the box...
Strange...
Maybe a new ROM will come out soon enough that solves all these problems.
I do hope someone responds to this thread.
It would be great if we could find out which process is preventing the BT radio from working. (Although, maybe it's just the number of processes, and/or the memory used....)
I am going to try allocating more program memory and see what happens...
Thanks for your answer. Problems here, apart from Bluetooth:
WiFi -- Often can't turn it on. This is an known problem on the forum. My workaround: if I turn it on and off immediately after a soft reset, before I do anything else, it generally works fine when I need it later. Otherwise, I have to soft reset again.
Active Sync -- Sometimes slow, sometimes connects and disconnects again, sometimes does nothing at all. Also, there's a growing number of stored e-mail messages that get sync'ed almost every time, even though nothing's changed. Other than that, it usually works ok.
Whistling screen -- NO, fortunately this hasn't happened to me yet. I hope I stay safe, because from what I've read it's a pain... :?
I remember I had some WiFi and BT problems before I installed 1.40, and besides I really really want Media Player 10 so downgrading is not an option...
Well, even if the problem is the number of running processes rather than a specific one, I still hope we'll be able to kill some non-vital ones to free up driver memory...
This morning, I tried PHM Task Manager 0.1 which allows you to view running processes and, theoretically, end them, but every process I tried to end just stayed right where it was (even after refreshing the screen)!? Are there any other task managers that can do this? Anyone?
Please report if you had any luck after allocating more memory. Although I read somewhere that the amount of memory for loading drivers is limited by default, and that allocating more overall working memory doesn't help... I've tried it myself, allocating as much memory as I could (probably about 40-50 MB free program memory), but still had the "insufficient memory" issue with Bluetooth.
A way to get bluetooth working everytime
It might not be the easiest way to get your bluetooth working but it does work everytime. First thing you do is set your phone to flight mode. After that then you perform a soft reset. When you are back up then turn on your bluetooth. After your bluetooth is on then you can turn the phone back on again. Click on your signal icon at the top of the screen and choose settings. It will ask you if you want to turn the phone on. Choose yes and for me I have to do this twice before the phone comes back on. After that it will work everytime I reset until I turn off bluetooth. Hope this helps
A way to get bluetooth working everytime
It might not be the easiest way to get your bluetooth working but it does work everytime. First thing you do is set your phone to flight mode. After that then you perform a soft reset. When you are back up then turn on your bluetooth. After your bluetooth is on then you can turn the phone back on again. Click on your signal icon at the top of the screen and choose settings. It will ask you if you want to turn the phone on. Choose yes and for me I have to do this twice before the phone comes back on. After that it will work everytime I reset until I turn off bluetooth. Hope this helps
Twice ? :wink:
Active Sync -- Sometimes slow, sometimes connects and disconnects again, sometimes does nothing at all.
Click to expand...
Click to collapse
Activesync conflics with McShield.exe and so runs painfully slowly.
This is the active virus scan part of McAfee Antivirus. If you are using McAfee, before you dock your BA, right click the McAfee icon in your system tray and disable virus scan.
Hope that helps.
I have a Cingular SX66. No ROM upgrades yet. I have experienced similar problems and have been able to conclusively trace mine to Goodlink. This app is a necessary evil on my (corporate) device. This hog takes 6+ MB to run, more than 3 times any other program I have. If people think MS VoiceCommand is crappy programming (although I love it), then you ought to load Goodlink on and watch it muck up the works. As soon as I kill Goodlink.exe with MemMaid (great app by the way) bluetooth has no problems.
Not sure if this is a design function but everytime I turn the device off it returns to Today's screen.
Actually even when I toggle to screen in WMP and turn the screen back on the PPC throws me back to Today.
I initially thought it was a problem with my ROM (LSG then Custel 1.3) but after flashing to VP3G 3.0 on my 8525 (I have both an 8525 and TyTN) and without anything else installed it does that.
Any ideas if this can be changed? I'd like to open app to stay visible.
Thanks in advance for the help.
I really don't have this problem on my ROM, see signature. I have especially tested it for you to be sure.....
Perhaps flashing 1 device to a different ROM. Can you see it yourself.
that's what i figured so I had my 8525 that was running WM5.
I HardSPL, SuperCID it then flashed it with VP3G.
There is nothing else on the phone but my exchange and pop account setup, owner info and basic stuff like this.
I also have the clock shown on every apps and the extended rom unlock/mounted (though it does it with or w/o).
My TyTN is running Custel 1.3.
I just can't think what could be causing the device to always minimize open apps when the phone is turned off (standby).
It seems that some plugins force a redraw of the today screen when coming out of stb. Nothing much to do but turn off the offending plugin.
Go to settings/today and on tab for objects remove the flag for timeout. Problem gone.
Nice try, no prize - problem not gone.
This appears to be a WM6 "feature".
This discussion exists in another xda thread here, and in a Microsoft forum here.
HunterST said:
Nice try, no prize - problem not gone.
This appears to be a WM6 "feature".
This discussion exists in another xda thread here, and in a Microsoft forum here.
Click to expand...
Click to collapse
This is a really annoying "feature" of WM6. So far no answer in the Microsoft forums regarding this. Would be glad if i could return to exactly the screen where i switched off the device or in which the timeout forced it to suspend.
If it is not possible to fix this with a registry hacking, would it be possible to develop a small helper application which saves which application was open before the atual suspend takes place and upon a wakeup reads this information and switches to the last active window ? The app itself is still active, isn't it ?
Regards,
Secuspec
Wait. So what exactly happens? I also used vp3G 3.0 and let's say I have Resco File Explorer open and my phone sits idle for 1 minute and goes into standby mode.. when I press the power button to make the screen turn on again, it still shows Resco File Explorer for me.. Is the bug causing it to go back to the today screen every time the phone goes into standby mode?
if a program is left open when the device is turned off (or screen "muted") the program will be minimized when you turn the Pocket PC back on (you're kicked back to Today).
Glad I'm not the only once having issues. Thought it may be a design (flaw) but IMO it's a crappy one. Wish someone can find a fix.
interesting, it looks like if you remove the device password it doesn't minimize the apps. kinda weird IMO.
samw52000 said:
interesting, it looks like if you remove the device password it doesn't minimize the apps. kinda weird IMO.
Click to expand...
Click to collapse
Isn't that what you would expect if you have a device password set!?
Mike
ericc - that's exactly the problem. Are you sure you're really going to "sleep", and you aren't just seeing your backlight turn off? (you should have to hit the power button to wake it back up).
Especially annoying when driving with navigation software - I want to just turn it on and see what I saw before it went to sleep.
MikeC - that's a very interesting point. I have exchange push email going, and my system administrator pushes restrictions onto my phone... I use Zenyee Stayunlock to allow me to change the ridiculous 5-minute lockout to something more reasonable.... perhaps either the device lock or Zenyee is the culprit.
mikechannon said:
Isn't that what you would expect if you have a device password set!?
Mike
Click to expand...
Click to collapse
Actually not really... my Windows workstation locks I expect to see the program I had maximized still on screen not all down in the toolbar minimized. IMO that doesn't make much sense (and even if it did they should have an option to select the default behaviour).
HunterST said:
Nice try, no prize - problem not gone.
This appears to be a WM6 "feature".
This discussion exists in another xda thread here, and in a Microsoft forum here.
Click to expand...
Click to collapse
Works fine on my Tytn with WM6 official Swedish. I don't have a device lock enabled btw.
yes if the lock is turned off the programs will stay open and full screen on resume/screen toggle.
Problem seems to only take place when the device lock is enabled, no matter how long the lock period.
samw52000 said:
yes if the lock is turned off the programs will stay open and full screen on resume/screen toggle.
Problem seems to only take place when the device lock is enabled, no matter how long the lock period.
Click to expand...
Click to collapse
Thanks for the hint samw52000! That perfectly worked for me And it also sped up a lot of programs directly after wake up -what makes perfectly sense since no other program is interfering anymore.
Long time after last reply, but still no solution.
I notice if time in suspend mode is longer that programmed in settings/Lock/Prompt if device unused for... (if you have to tap your password) then screen is same as before suspend.
Hi,
We have developed an application for Windows mobile (we run 6.1 and 6.5).
When running the application, we rarely face a "Freeze" of the applications, i.e. the display is not updated
anymore.
The application can not be stopped, as the device seems not to react to input.
Thru logging we know that the application is running fine, only the graphics are frozen.
If we face the issue, we can only get rid of it by removing the battery, wait a few seconds and put the battery back
in its place.
Can anyone give a hint, what might be the problem? We currently have no idea, where we have to look for the issue.
Thanks in advance for helpfull answers,
Jan
Hello all,
My phone is not working properly. I've had some bugs most people seem to be having, but now I have something which is quite annoying. I can't find it on these forums or anywhere on the internet.
I have seen a 1 line reference to my problem here:
/showthread.php?t=666332&highlight=standby
Flaws & annoyances with the HTC Desire (with workarounds!) [updated Apr 23, 2010
Hardware defects. Eg. Dust under screen, device not going into standby properly. Most of us don't experience these. Contact your retailer to exchange the unit or HTC to claim warranty.
So, I seem to have this problem. The phone wakes up with whatever button I press, and I don't have to unlock the phone. I have a unlock pattern set. It also doesn't ask me for this.
I couldn't find a proper topic about this problem, but I assume I'm not the only one. Is there a fix, or is it a hardware problem?
It wouldn't make sense to me if it's a hardware problem since the screen does turn off when I press the 'power' button.
Any info would be appreciated.
Thanks, Bart.
Which Lock?
are you using the built in lock or a third party lock app? I had the same problem when I used LockBot. If it's the standard lock, have you tried Powering the phone off then back on?
I am just using the built in application. I haven't used any other lock app.
I have tried turning the phone off twice, and both times it came back (might have been after charging it, but I don't know at all if that's the reason).
edit: I'm gonna try to recreate the problem with restarting and trying to find out when it stops working properly.
edit2: I restarted now... and it hadn't saved the new background I set... strange... :/
edit3: Ok, it still locks itself... I guess I'll just need to wait and see when it doesn't work anymore... maybe it's just a matter of time for it to stop working...
The problem that you quote in your opening post is probably the problem concerning the Desire (or rather an application running on the Desire) not properly releasing a wake lock which causes severe battery drain, e.g. the calendar app about which another thread exists.
Your problem seems to be quite strange. You do not happen to have an application called 'No lock' installed, right?
No, I don't have 'No lock' installed.
I use 2 calander widgets though... (the little one on my home screen, and an more advanced one on another screen.)
I've got quite some applications installed though... I'll just type them here, maybe someone can see something wrong...
Math Workout Lite
EStrongs File Explorer
Alarmering Droid
Groceo-NL
Q-Park parkeerfaciliteiten
ATM Locator NL
Text-To-Speech Extended
Google Translate
G-MoN for Android 2.x
Buienradar.nl v2
Gesture Search
Scoreboard
Listen
My Tracks
Air Horn!
Bonsai Blast
Star Wars Light Saber
Kaloer Clock - Night Clock
Coloroid
AudioManager Widget
IMDB Top 250
Pobs
Simply Cyanide
Voetbal nieuws
Barcode Scanner
Classic Simon
XDA-Developers
Backgrounds
SchottGunn
Shazam
Funny jokes
Ringtones
Google Maps
Google Goggles
I'm just trying some of the stuff of course... It's quite a long list...
Maybe Kaloer Clock brakes something?
I'll use it tonight again, going to sleep soon... Maybe it'll be broken again tomorow.
Lets hope it wont brake again... but that's probably too optimistic.
First off: sorry for the double post, but I have some new information which will also mean the end of this topic.
This morning it didn't work anymore, and the only application that did it's thing this night was the kaloer clock (night clock).
I looked at the settings, and there are some settings about screen lock.
It's not clear at all, but I changed some settings, and it locks again.
So, I guess it was just me using an app which I didn't fully understand. I'm glad you guys helped me though. And I'm definitely glad that my problem is solved!