Problem uploading a file using Bluetooth

[milp]

Hi all,

I feel that this exact question may have been asked before but honestly, after searching for many pages in all x50 forums, I could not find. So here goes:

I have Axim x50v and Motorola MPx220 smartphone with BT.
I have successfully paired the 2 devices and can send small files like 15K from my PDA to the phone.
But I have noticed that a tad bigger files (like 200Kbytes) do not get sent. They just start out good and then hang the operation of my pda.
I have also confirmed remaining space on the phone and that is not a problem. After many unsuccessful attempts to send the file via BT to the phone, I tried sending the same file via IR. It takes a lot of time but atleast it get the job done. I also tried to send a 1.6MB file via BT to the cellphone but the same problem. Even this files when I sent via IR, it went without any hiccup.

So guys, whats happening here ? Please help.

Thank you.

Regards,

MP

[Zori]

I believe it is a stupid bug on Axim from day 1. The PDA doesn't like to accept "PUT" file protocol if the file is over 40kb big.

There is a sort of "work around" solution. Put the BIG file into the default Bluetooth Exchange folder on your device and use Axim to do the Browse files on a remote device. Then do a "GET" file. It works fine for me this way, I was able to download a 8Mb file through BT from my PC.

Good Luck

[milp]

I believe it is a stupid bug on Axim from day 1. The PDA doesn't like to accept "PUT" file protocol if the file is over 40kb big.

There is a sort of "work around" solution. Put the BIG file into the default Bluetooth Exchange folder on your device and use Axim to do the Browse files on a remote device. Then do a "GET" file. It works fine for me this way, I was able to download a 8Mb file through BT from my PC.

Good Luck

What is a "Default BT exchange folder" ? Do U mean MyDocuments folder on Axim ?
FYI: I am trying to copy a file FROM my Axim TO my cellphone.

Please help.

[milp]

*bump* (for more people to see.)

[zim2dive]

milp, see

http://www.aximsite.com/boards/showthread.php?t=61141

sorry you are one that is affected too.

If you can confirm your problem is similar, please send me the details of your hardware (Motorola MPx220), ie any version, firmware level, OS version, etc, so I can add that info the edit-in-place list I have in the above thread of HW that the Axim has problems with.

Also I'd strongly encourage you to file this with Dell tech support. I'm not sure they are at the point of feeling like they have "critical mass" of the breadth of HW with which their drivers fail such that they feel it is _their_ problem to fix, and not that of all the other equipment.

Cheers,
Mike

[milp]

milp, see

http://www.aximsite.com/boards/showthread.php?t=61141

sorry you are one that is affected too.

If you can confirm your problem is similar, please send me the details of your hardware (Motorola MPx220), ie any version, firmware level, OS version, etc, so I can add that info the edit-in-place list I have in the above thread of HW that the Axim has problems with.

Also I'd strongly encourage you to file this with Dell tech support. I'm not sure they are at the point of feeling like they have "critical mass" of the breadth of HW with which their drivers fail such that they feel it is _their_ problem to fix, and not that of all the other equipment.

Cheers,
Mike

OH, Thank you very much for replying. And I thought that it was only I, who was going crazy and not doing it right.
Well here are the version numbers:

Dell Axim x50v:
BT-PPC version 1.5.0 Build 2600

Motorola MPx220:
(Updated)Firmware verion: 1.300
I dont know what version of BT is on MPx220.

I very much belive that the problem lies in Axim PDA coz
I am very much able to transfer any size files from my MPx220
phone to my wife's MPx220 phone.

Is there any s/w update for this problem from Dell or the original s/w manufacturer ?

[zim2dive]

MP, if you read the other thread to the end you'll see that as of now, there is no fix, and no commitment from Dell to issue a fix. They seem to acknowledge the problem, but I think its going to take more people calling to complain to help motivate them. So please, do call Dell tech support, and file a problem report on this issue. They will offer to send you a replacement, but it is probably not worth your while... this problem seems to be a driver problem and any other unit they ship you will have the same driver = same problem. Insist that they escalate the issue to a "research team" and/or "upper level" support (the terms that my tech support guy used). This will take some time on your part.. so call from a speaker phone that you can put down while you spend a fair bit of time on hold .. that way you can hear when they finally pick up.. cradling a phone by your ear for that long is incredibly annoying. (you have to wonder what their phone bill is to international outsourced techsupport when you are on hold so long)

I'll post any updates to the other thread, tho I feel like my particular problem ticket is probably on hold now, vs being actively worked... which is why we need more people to call and file more tickets on this issue)

cheers
Mike

[milp]

1st of all, thanx Mike for replying in detail :)

OK, I did not wait for your reply and had already called Dell
Tech support. It took me 58 mins of holding time to get to
the 1st guy and then 13 more mins of talk time....
I also talked to the supervisor level and he was very polite and 'helpful'.

What he told me was that they had done this "in-house" test of ALL the x50 Axims on this very same issue and all of them checked out fine. He also said that they transmitted a 5MB file between all the axims and it worked flawlessly.

Since I'm a programmer too, I know what this means. In our lingo, it means that "Since this works on my end without any problems, there is no way I can replicate this error AND because of this I cannot help you." - A very polite way of saying that you are on your own. (Mind you, most of the times they are right too)

IMPORTANT: During our conversation, I also mentioned him about the freak "License expired" issue and guess what ? He told me that very soon (8-10 days), Dell is coming out with a ROM update for x50 (v only? or all types), which will be an OVERALL update which takes care of the before mentioned License issue, WEP encryption in WiFi and other bug fixes. He said that maybe the 40KB size limit issue (or whatever that is ailing my x50v) may also be take care of by this ROM update.

So guys, there is your inside scoop. Hope this ROM update does us all a huge good.

MP

[zim2dive]

I would call back and insist that the Axim<->Axim test is not enough. Tell them to search for other reported incidents of this. My case # is 89959009.

I was also able to make Axim<->Axim work (while I had the replacement and my original). And several people here have no problem Axim<->computer.. they are simply lucky enough to use a computer (or phone, or whatever) that is not affected by this design flaw in the driver.

I do HW and SW too, so yes, I know the trap of their thinking, 'it works for us, so it must work for everyone'. That is the biggest fallacy in all of HW or SW design.

Was also told about the forthcoming ROM patch, but don't expect it to help... they seem to unaware of this issue for it to already be in this patch. so if you are up to it, try to call back and see if you can get them to recognize your case as another incident of the same problem I reported to them. They seem to acknowledge that problem is real (I _think_ they confirmed it on a T42 on their side), tho what they plan to do about it is not known. too much of the tech support person being the 'middle man' for the information flow to be clear.

Cheers,
Mike

[milp]

Thanks for giving your case number.

I will call the tech support later in the day or max. tomorrow. Already I spent a lot of time during my work hours !

[zim2dive]

LOL, I know what ya mean... just wish I had speaker phone at work, so I could drop iton the desk and keep editting docs.

Cheers,
Mike