jimwall

My X51 takes about 20-30 seconds before it is functioning normally after I turn it on. If I try to go into the calendar immediately after starting it, it seems to lock up for about 30 seconds and after that it will work OK. My X5 would work immediately when I turned it on. Anyone else having this issue? Is it restarting all the programs? What programs are supposed to be in the startup? Mine has 5 items: BTTray, odClientCeAu..., poutlook, Splash & WirelessIcon.

I wish my screen didn't go out on the X5 because I am unhappy with the X51. I have to do soft resets several times a day when it won't restart.

tostngdsnvoy

Remember, the X51 is pretty much exactly like your PC when it loads the OS - Files are stored in BIS, then loaded to RAM as it's being booted. ANd just like your PC, after you log in, your pc is busy loading startup apps. The same would be true for the X51 - after the OS is loaded, startup apps are loaded. And the more startup apps you have (Omega One products, SPB, etc), the longer it needs to load them.

We were warned up front that the X51 would be slower because WM2003SE is stored / loaded in RAM as well, but that RAM usage is doubled because of that. It's a double edge sword, but whatcha gonna do?

jimwall

Are there some items I mention in the Startup directory that I can do away with to speed it up or is it the OS in general that is loading that takes that much time?

tostngdsnvoy

Those startups are needed for Bluetooth & WiFi Status. Outlook may be used for Calander, Contacts, and E-mail. I do not know what the other two "odClientCeAu & Splash" are used for. You can try to MOVE them, but be perpared to move them back, just in case.

But overall, I would just be prepared for about a 1min boot time total. I am getting my X51v today also, and since I have to reboot my X50v occasionally, I'm used to mine taking about 40 sec or so

MonAccount

I installed the 2 free games off of the CD that came with it, as well as MS Voice Command, Tonaya Weather-To-Go, MagicButton, and the Belkin GPS software. There may have been some other packages, too. Well, I noticed that after about 2 days my 51v was soooo slooowwww to respond after powering on (not from a full power-off, just the everyday turn off/on). I made a list of software I know was working, hard reset, loaded those packages on and I've been fine for the past 3 or 4 days (I basically didn't install what I listed, above). I even turn it off then on a few times during the day, expecting it to be slow, but it responds immediately! You may want to try a hard reset and stick with software you know works. BTW- I was getting a lot of app crashes, too - Odyssey Client, etc. - that has cleared up. Not sure if this helps at all, but I do believe my slow-to-start problem stemmed from incompatible software - slimming down to only what I use cleared up my problems - thankfully everything I use works!

jimwall

Well, I am going to do a hard reset tonight and see what happens.

jimwall

Works fine now after the hard reset. Starts almost immediatly instead of the 20-30 seconds. I believe I had corrupted something when I got the device last week by loading Agenda Fusion and Pocket Quicken. These are not compatable with WM5 yet

kermitdefroghere

I experienced the same thing and contributed the slowdown to the Odyssey client.

Make sure you disable the Odyssey client and do a soft reset.

four86

My X50v only takes 10 seconds to boot up and find the WIFI network.
It only gets 'choppy' when I am entering my 4 digit password at boot. Not sure if the OS is loading files as I am doing this, if that is the case, it could be ~15 seconds for a entire boot before I can actually use it.

HvH

Originally Posted by kermitdefroghere

I experienced the same thing and contributed the slowdown to the Odyssey client. Make sure you disable the Odyssey client and do a soft reset.

I too experienced slowness on turning on after a few days of use. It also started displaying warnings about not being able to load \Windows\OdClientCE.exe.
I then did a hard reset, re-installed all the software I had before and did not find it slow at all (and the warnings disappeared as well). However, again after a few days of use, it started being slow again (right after turn on). I have now just had the first message about the OdClientCe again.

Effectively, it makes the device unusable as a datebook, because after switching it on, you have to wait for about 30s before the device actually starts processing your input (going to the next day or entering a new appointment). 30s in those circumstances is very, very long.

I was unable to actually disable the Odyssey client (the Odyssey icon was still visible in the task bar, although I had it disabled) and the slowness stayed. Even after a soft reset.

I have been able to actually disable the OC by restoring a registry I saved earlier (the icon is gone from the task bar) and now the unresponsiveness seems to have gone.

My conclusion: there is something wrong with the OC that was preinstalled on the X51v. After some use of the OC for WiFi, for some strange reason it makes the device slow on startup. Just my €0.02.

Is there anybody else out there that is experiencing the same thing and perhaps has some light to shed on this issue?

BTW I'm new on this forum and new on the WM platform as well. I used to use a Palm (still do, as I'm not feeling entirely secure about the X51v as yet).

grayfox5

I had purchased the Wi-Fi Companion software from Dell along with my X51v, and installed it immediately. I also had startup problems immediately, including the Odessey Client utility error messages. I finally gave up and removed Wi-Fi Companion yesterday, and the difference is remarkable. I still occassionally get the OC errors, so I will probably have to do a hard reset to get that back to square one. Hopefully the Dell WLAN utility is all I'll need for wireless.

tccox

Originally Posted by grayfox5

I had purchased the Wi-Fi Companion software from Dell along with my X51v, and installed it immediately. I also had startup problems immediately, including the Odessey Client utility error messages. I finally gave up and removed Wi-Fi Companion yesterday, and the difference is remarkable. I still occassionally get the OC errors, so I will probably have to do a hard reset to get that back to square one. Hopefully the Dell WLAN utility is all I'll need for wireless.

I also purchased the Wi-Fi Companion software from Dell. Please note that the version that came on the CD from Dell is not the version for Windows Mobile 5.0. You have to go to the developers website and download the version for WM 5.0 then use the key on the CD case to actvate it. Works just fine on my X51v

Noisy Crow

What plug-ins do you have loaded on your Today screen?

I have been using SPB Pocket Plus, and found that when I put it inside of Pocket Breeze and set it to initialize-when-tab-selected that I noticed two things:

1. Startup from soft-reset is a lot faster
2. There's a noticable time lag bringing up the SPB plugin the first time I access that PB tab

__________________
"Times fun when you're having flies." --Kermit the Frog


Walking crow credit: www.crowanimation.com.

grayfox5

Originally Posted by tccox

I also purchased the Wi-Fi Companion software from Dell. Please note that the version that came on the CD from Dell is not the version for Windows Mobile 5.0. You have to go to the developers website and download the version for WM 5.0 then use the key on the CD case to actvate it. Works just fine on my X51v

I did download the latest version from their site, that's a good tip for anyone who buys the wi-fi companion from Dell. I just did a hard reset on my Axim last night, and it made an incredible difference. It nows fires up in maybe 5 or 6 seconds, password and all. The Dell WLAN utility works fine. I'll probably try the wi-fi companion again at some point, but I'm afraid to fix it now if it ain't broken!

alanwong

Originally Posted by HvH

I too experienced slowness on turning on after a few days of use. It also started displaying warnings about not being able to load \Windows\OdClientCE.exe. I then did a hard reset, re-installed all the software I had before and did not find it slow at all (and the warnings disappeared as well). However, again after a few days of use, it started being slow again (right after turn on). I have now just had the first message about the OdClientCe again. Effectively, it makes the device unusable as a datebook, because after switching it on, you have to wait for about 30s before the device actually starts processing your input (going to the next day or entering a new appointment). 30s in those circumstances is very, very long. I was unable to actually disable the Odyssey client (the Odyssey icon was still visible in the task bar, although I had it disabled) and the slowness stayed. Even after a soft reset. I have been able to actually disable the OC by restoring a registry I saved earlier (the icon is gone from the task bar) and now the unresponsiveness seems to have gone. My conclusion: there is something wrong with the OC that was preinstalled on the X51v. After some use of the OC for WiFi, for some strange reason it makes the device slow on startup. Just my €0.02. Is there anybody else out there that is experiencing the same thing and perhaps has some light to shed on this issue? BTW I'm new on this forum and new on the WM platform as well. I used to use a Palm (still do, as I'm not feeling entirely secure about the X51v as yet).

I came on here about to post about my problem with the x51v... but your description of the symptoms are exactly the same as mine. Furthermore, if i have an appointment alarm/notification set to go off and the error of the "cannot execute \windows\odclientce.exe" pops up as well, I cannot close the error box or do anything at all and am forced to to a soft reset.

It is quite irritating, having to turn the thing on hoping to jot down something quickly, only to wait about a minute before i can use any functions (I came off the Tungsten T to the x51v hoping for something with more functionality, so i might be spoilt for speed at turn on).

Unfortunately I'm stuck in the same boat as you, I don't know how to remedy the situation (I would happily disable odclient for functionality, even if it means i can't use my wireless network with it for now at least).