Solution - Axim not turning on, Disappearing CF/SD Cards and Battery Discharge

[mad0865]

After applying the A06 ROM, I saw the battery drain issue with the battery being hot. Both times, after a couple of hours of being turned off I would check something to see an error on the screen that looked like:

Error in \windows\task\something task (can't remember exactly)

And the battery would be at about 19-25%. This happened twice in one week. I applied the active sync fix to set it to manual, and I haven't had the problem since (48 hrs so far). Thanks dude, nice catch.

[dwoloz]

I was having all those problems with my x50v and just tried this method and finally put back in my microdrive and SD card. We'll see if this works...my fingers are crossed!

My battery would be drained pretty rapidly so Ill see tomorrow morning if anything happened






So if this works, why doesn't Dell know about it?!?!

[david632]

Hello All
I honestly cant see this so called fix, fixing anything, ive tried it and it dosent even stop activesync connecting all the time, regards to this fixing the white screen of death, i think this was fixed in rom upgrade A06, as for loosing flashcard, this will not be fixed with this rememdy as its down to windows mobile 5 and not a activesync problem, i just wish dell and microsoft will sort this out, always having to soft reset cant do this pda any good.

[g00nerz]

david632 - Welcome to the forum

When you say it doesn't stop Activesync connecting all the time, is that when your Ax is docked? Or when it's undocked? This 'trick' only addresses Activesync loading and attempting to connect when undocked, or on standby - and therefore stops the power on problem and disappearing cards.

If this fix didn't work on your particular Axim, and you are 100% sure you did the 'trick' properly (set both Schedule boxes to Manually), that is unfortunate. I think the posts in this thread and the hundreds of others all over the forum indicate it actually does fix problems in at least 99% of cases. You may be one of the unlucky few I'm afraid. I guess the only recourse you have is to send it back to Dell for replacement, or wait until Dell release a new Rom to fix it properly.

[SteveFLHTCI]

g00nerz, I find it amuzing that you are so convinced that this absolutely fixes the problems. I remember people being equally sure that keeping bluetooth on also fixed all the problems, and I, for one, am 100% sure that the problems were NOT corrected by bluetooth. And yet, people are still touting that as a cure-all workaround.

I am not saying your method doesn't work for you, and for some of the other people on here. But isn't it possible that the software has so many glitches that there is no one fix for everyone without a true software update?

I am still waiting to hear from ANYONE what their available RAM is after aplying this fix before I re-flash my x50 and try it again.

[locutus555]

g00nerz, I find it amuzing that you are so convinced that this absolutely fixes the problems.

It did help my X51v c A06, but here are the results:

X51v c WM5 A06:
1/12 2302 60% 26 Mb free memory
1/13 0912 46%

X50v c 2003 SE:
1/12 2302 100% 31 Mb free memory
1/13 0912 97%

Both were soft reset at 2300 hrs 1/12 and both have exactly the same programs running.

But my X51v is usable now, except for the battery drain, but not entirely dead as it was before the fake server trick. Still something running that shouldn't be. or does the change in memory type require more battery power to maintain??

Locutus

[SiGriffin]

I am still waiting to hear from ANYONE what their available RAM is after aplying this fix before I re-flash my x50 and try it again.

Not quite sure what your point is, but my x51v has 29.97MB available for programs.

As I've said earlier I was equally skeptical having read the first post, but decided to try this fix anyway. So far I haven't had any problems since then whatsoever and am very pleased that I tried it.

[g00nerz]

Hi Lizard, thanks for posting such a positive and friendly message. Allow me to address your concerns:

1. This workaround fixes things perfectly well for me, and many many other x51(v) users for the time being. We are all very aware that this is a temporary solution, and if the software had been designed properly in the first place we wouldn't have to scrabble around for ways to bypass these bugs. Dell will fix it in the end, of that I am sure.

2. I am not the person that discovered this Activesync workaround, I am merely a person who had seen enough people asking about the problem every day to think it was about time someone wrote a sticky for it. I am trying to help new people sort their Axims out, and simultaneously stop the flood of posts asking the same question. As someone mentioned elsewhere, floods of people asking the same question can invariably ruin a forum in the long run.

3. As mentioned earlier in the thread - this works on 99% of x51v's reported by users so far that I have read. Do a search, there are plenty of people that state it worked for them.

4. This thread was created with x51(v) owners in mind only - I have no idea if this works on x50(v)'s. I would suggest the x50(v) WM5 update has created many problems above and beyond the help of this Activesync workaround judging by the posts I've read.

Finally, I am only trying to help - that is all. If you do not approve of these suggestions to help people with their x51(v)'s, try and keep your opinions constructive and simply state it didn't work for you. You don't have to be the big man and flame my attempt at helping others. Remember, if you have nothing good to say, don't say anything at all.

Thanks

[rlarson_mn]

I agree with you tottaly.

I was one using BT to fix the issues in this thread (which they did 100%). I did however try the method described here and turned my BT off. It worked 100% also! The advantage I see is that one, no extra battery loss and two this fix (trick) stays in place after a soft reset or replacement of your battery. I am sold and wish to say thanks for posting this and the effort it took to do it. This is typical of the good people that visit this site. They want to help others over bumps they have experienced and willingly give advise and posible solutions. Dell should just use this site instead of their India connection .

Hi Lizard, thanks for posting such a positive and friendly message. Allow me to address your concerns:

1. This workaround fixes things perfectly well for me, and many many other x51(v) users for the time being. We are all very aware that this is a temporary solution, and if the software had been designed properly in the first place we wouldn't have to scrabble around for ways to bypass these bugs. Dell will fix it in the end, of that I am sure.

2. I am not the person that discovered this Activesync workaround, I am merely a person who had seen enough people asking about the problem every day to think it was about time someone wrote a sticky for it. I am trying to help new people sort their Axims out, and simultaneously stop the flood of posts asking the same question. As someone mentioned elsewhere, floods of people asking the same question can invariably ruin a forum in the long run.

3. As mentioned earlier in the thread - this works on 99% of x51v's reported by users so far that I have read. Do a search, there are plenty of people that state it worked for them.

4. This thread was created with x51(v) owners in mind only - I have no idea if this works on x50(v)'s. I would suggest the x50(v) WM5 update has created many problems above and beyond the help of this Activesync workaround judging by the posts I've read.

Finally, I am only trying to help - that is all. If you do not approve of these suggestions to help people with their x51(v)'s, try and keep your opinions constructive and simply state it didn't work for you. You don't have to be the big man and flame my attempt at helping others. Remember, if you have nothing good to say, don't say anything at all.

Thanks

[XV66]

I'm using an XV50v with the WM5 upgrade, this fix so far has ended my WSOD, the missing CF card and the "no power" issue. I see a boost in overall performance and speed. I'm not sure about the battery issue yet.

Most importantly I think you need to have the most current XP update on your desktop. My first install was not as smooth till I upgraded XP and Outlook on both of my sync partnered pc's. I also did a clean install the second time.... no backup. So far my X50v is sailing smooth, no soft resets yet.

[medgirl2001]

If you do have problems with powering on etc then you could set the sync to manual and just sync whenever you need to, and not let the Axim do it automatically.

This does defeat the object of having an Exchange server though.

I have an Exchange server, and this still seems to work. As far as I can tell, the point of the server "trick" is to have access to the Schedule setting to set it to sync manually. Why this is not accessible without an Exchange server I have no idea.

What I did was add my Exchange server and then set it to sync manually on the desktop and on the Axim and it works fine. When I sync with my desktop, the Exchange server is automatically synced. I can also sync the Exchange server wirelessly by going to ActiveSync and telling it to sync.

[medgirl2001]

Actually guys, there might be a solution regarding the Wi-Fi & Bluetooth synch-ing problem.

You might want to look into this URL: http://www.airscanner.com/downloads/airfix/airfix.html

It is a free software provided by Airscanner to solve the issue.

I personally have only downloaded the software and have not actually tried it yet. But Airscanner seemed pretty confident with this program.

CHECK IT OUT! Hope it helps.

I don't think this lets you sync via WiFi. This is to let you use wireless while syncing. I'm not sure when this issue would come up - maybe if you had wireless on your laptop and simultaneously wanted to sync your Axim? At any rate, it doesn't allow WiFi synchronization. I think that's a (deliberate) limitation of WM5 that there isn't a fix for at this time.

[SteveFLHTCI]

Hi Lizard, thanks for posting such a positive and friendly message. Allow me to address your concerns:

1. This workaround fixes things perfectly well for me, and many many other x51(v) users for the time being. We are all very aware that this is a temporary solution, and if the software had been designed properly in the first place we wouldn't have to scrabble around for ways to bypass these bugs. Dell will fix it in the end, of that I am sure.

2. I am not the person that discovered this Activesync workaround, I am merely a person who had seen enough people asking about the problem every day to think it was about time someone wrote a sticky for it. I am trying to help new people sort their Axims out, and simultaneously stop the flood of posts asking the same question. As someone mentioned elsewhere, floods of people asking the same question can invariably ruin a forum in the long run.

3. As mentioned earlier in the thread - this works on 99% of x51v's reported by users so far that I have read. Do a search, there are plenty of people that state it worked for them.

4. This thread was created with x51(v) owners in mind only - I have no idea if this works on x50(v)'s. I would suggest the x50(v) WM5 update has created many problems above and beyond the help of this Activesync workaround judging by the posts I've read.

Finally, I am only trying to help - that is all. If you do not approve of these suggestions to help people with their x51(v)'s, try and keep your opinions constructive and simply state it didn't work for you. You don't have to be the big man and flame my attempt at helping others. Remember, if you have nothing good to say, don't say anything at all.

Thanks

It was not my intent to "flame" you, and if that was how it was taken I apologize. I was merely pointing out that this is one of several fixes that have been previously posted on the site that may or may not help. The bluetooth fix was touted as a 100% fix by multiple users. After trying that particular fix myself I found that although it did help, it certainly did not fix all the problems. The fact that there is at least one person who claims to have tried this fix and have it not work suggests to me that this is yet another workaround similar to the last. It may help some but it is at best a panacea for a flawed OS.

The fact that I am using an x50 rather than an x51 is really irrelevant. The problems noted were common to both systems. The only difference now being the couple ROM updates that have been made available for the x51's and not the x50's. Any fix that really works should work on both.

As far as memory, one of my main reasons for wanting to go to WM5 was to increase the amount of program memory available. After a soft reset, I will typically be able to adjust my slider to allow 34Mb of memory for programs. To date, the most I have seen anyone state for WM5 is 30Mb. This particular facet really disappinted me with WM5. Now having said that, I can also tell you, as soon as the "majority" of the problems are fixed by a ROM update, I will return to WM5 immediately.