JakeRich

Originally Posted by zim2dive

The Wifi and BT problems aren't for a lack of experience. The 1st "network card error" I got was after pressing the "on" button... I'm not expecting that I'll learn to press it differently with more experience :) Maybe I ahve to learn to sneak up on it, I dunno. As detailed in other threads the BT works with some devices, and in with others only one one direction (OFF the Axim, but not TO the Axim). Its a driver issue with the BT stack, not a user-experience-level issue. Axim to Axim is the only place I've seen the BT work without a problem (one should hope they tested that). But it seems to have some serious interop issues with _some_ other BT devices. I'm happy for everyone that gets it to work, but its a real, and prevalent problem. Considering how few ppl use BT, I'm not suprised there aren't more problems. When I first reported it, the typical forum reply was "who cares, use the Wifi, or a card reader".. so if those ppl wouldn't care about fixing the problem, they just work-around/ignore it. Peronally I expect it to work as advertised, hence my posts about it. Email tech support has "punted" and pointed me to the telephone support now, seemingly they were unable to replay my case and have them call me. Mike

The fix is simple. Soft reset before invoking BT, if you have applications running, or at least make sure they are actually killed, not pushed back. I use BT every day, and the only time I get the BT error is if I have applications running before I start BT. I use Wisbar Advance 2 to kill applications completely instead of pushing them into the background. Most of the time I start BT from a "fresh" machine with nothing but my today plug-ins running and it's perfect. The odd occasion when I do get the message is a "d'oh" moment when I forget and start it with another app already running. I have been successful sometimes with just killing the app, but do occasionally have to soft reset to get the memory back so BT will start. It's not fatal, it's just a process of learning how to invoke BT in a manner that is more likely to succeed.

zim2dive

Originally Posted by JakeRich

The fix is simple. Soft reset before invoking BT, if you have applications running, or at least make sure they are actually killed, not pushed back.

Nothing personal, but you're flat wrong.

If you had read carefully, you'd see that I had this error out-of-the-box, brand new Axim, that was sent as a replacement to me b/c the 1st Axim had the same problem (and Dell thought maybe it was a one-off defect). Its not.

The BT is compatible only with some other BT devices. Great for you if it works, but for a good # of us, it does not.

Its not a lack of experience.
Its not too many other programs running.

Its a driver issue.

Again, glad for those for whom it works, but get your head out of the sand assuming that just b/c it works for you it should work for everyone... I make no such assumption in reverse. It doesn't work for me, and it doesn't work for several other people. Some people seem to have no trouble. But I do believe this is a driver/interop problem, and as such its hard to know whether the BT will work for any given person with THEIR device. At this point it is Buyer-beware IMO.

Mike

zim2dive

Originally Posted by bohica

I agree completely. BT is essential for me - especially in work. I'm sat at my desk at the moment with my laptop (BT), mobile phone (BT) two Axims (inc. my X50v) and the only way I can keep on top of things by having everything working together. The only time I've experienced any problems is with my Sony Clié - but Palms never seem to sit too well with Windows of any flavour :) It is an odd problem you're experiencing. It wouldn't surprise me if there's a firmware problem affecting some X50v's. It could be that models manufactured after a certain point had an amended version of the BT drivers that dealt with this problem. I suppose, in your case, it's a matter of waiting for deal to release a ROM update that hopefully fixes this problem. Good luck, Mark.

Yep, I suspect they just did not do enuf interop testing... works with some, fails with others. Axim to Axim to Axim seems to work fine for me... I've posted my driver versions in other threads and have not seen anyone report a different level of driver :(, so I suspect the lucky ones (like you) are just lucky enough to have BT hardware that this driver likes. And its not a complete... the only thing that fails is file xfers TO the Axim that are in excess of somewhere in the range of 100-400k... smaller files work TO the Axim, and big files always seem to work when copied OFF the Axim.. but I could not copy an mp3 file TO the Axim (3M). So its "close", but in a nutshell still not right.

Thanks for the luck, might need it. 30 minutes of listening to techsupport "muzak" about doing soft-resets and Outlook Express... my gawd it'll drive you mad. ;)

Mike

Gassius

To zim2dive


I feel your pain, but I think your are also FLAT WRONG on the "Its a driver issue." statement.

Do you understand that I, in 2 months now with my x50v, and heavily use of both WF and BT never got the infamous BT error? I think that discard any driver issue.

If I was you, I would asked for a second replacement, but hey, is just an opinnion! :D

I do think is not a common problem outside this forum (which is intended to talk about problems). and even here, theres a lot of users like me that doesnt have any problem related to BT (as you can see on this thread).

Good luck anyway! :)

__________________
----
Hate you all and your fancy signatures

Theophilus

Check that

__________________
.
"There never was a good war or a bad peace." -- Benjamin Franklin
"Life is pleasant. Death is peaceful. It's the transition that's troublesome." -- Isaac Asimov
"Newbie or not newbie, there is a question." -- Shakespeare, Hamlet 3/1 (Kind of)

Scott54

I use wifi a lot and have had no problems at all.

I have one bluetooth device, the Dell executive keyboard. I once I installed the program/driver into the default location I have had any problems with it.

I have experienced one problem that is a bit annoying. I had two or three movies on my SD card. The first movie ran great, the other two ran slow, dropped frames, etc. I made sure I didn't have any other programs running but that didn't fix the problems. Now I just put one movie on the SD card at a time and haven't had a repeat of the problem since.

Scott

__________________
"All that is necessary for evil to triumph is for good men to do nothing." Edward Burke

zim2dive

Originally Posted by Gassius

To zim2dive I feel your pain, but I think your are also FLAT WRONG on the "Its a driver issue." statement. Do you understand that I, in 2 months now with my x50v, and heavily use of both WF and BT never got the infamous BT error? I think that discard any driver issue.

Done much HW test? I have. 11 years embedded development and test of new boards and chips (HW/SW/FW).

Let me summarize the symptoms:
- copy of 8M file FROM Axim works
- copy of <100k file TO Axim works
- copy of >400k file TO Axim fails (the space btw 100-400k seems to vary between user and attempt)
- Axim to Axim, everything (attempted) works

So please, based on your embedded development/debug/test experience, explain how this is a HW manuf defect, such that a 3rd unit will exhibit different behavior. I'll be happy to meet you in the lab with oscope, logic analyzer and whichever piece of HW test equipment you'd like, so you can show me the HW failure. Don't forget your copy of the schematics.

Simply put, too much _works_ for it to be a HW issue (if this were high school, some engineer would get 90% as partial credit, for almost getting it right). That, um, leaves the driver having an interop issue. An interop issue would be one that fails only with certain other pieces of equipment.. which if you are not using those other pieces of equipment, but instead using pieces that do not have an interop problem, you can use until the y10k problem occurs, and have no error. That does not mean there are not interop problems that need to be corrected in the driver.

1 week of detailing the problem to email-support only to have them punt me to phone support, 40 minutes on hold there, so that they could ignore the email history and offer me yet another unit, 5 minutes to convince them to elevate, then another 5 minutes of them asking me how I'm going to "rate" their performance on the call.. nuts. Supposed to get a call tonite. Frankly I'd just want to get this in to their development side so they can know about it and test. They won't fix a problem that support doesn't let them know about.

Mike

jpooton

To the people who never get "Unrecognized Card" when enabling WiFi:

Could you please list what you have installed on your x50v ? Including Today Plugins? I have no idea what causes it but on mine after a hard reset it's fine. Somewhere along the way (or after use) things get hosed. I don't feel that I have a lot of junk installed but

-James

zim2dive

Originally Posted by jpooton

To the people who never get "Unrecognized Card" when enabling WiFi: Could you please list what you have installed on your x50v ?

I had, pretty sure, nothing on the replacement unit I got. LOL, let someone try to beat that :) I still have my original unit (will box it up tonite and ship it back), but could do some HW resets on that and try to recreate.

Mike

Theophilus

Originally Posted by jpooton

To the people who never get "Unrecognized Card" when enabling WiFi: Could you please list what you have installed on your x50v ? Including Today Plugins? I have no idea what causes it but on mine after a hard reset it's fine. Somewhere along the way (or after use) things get hosed. I don't feel that I have a lot of junk installed but -James

I have like 100 different applications, including a lot of junk. I actually managed to fill my 1 Gig SD card only with applications and games ! I like to try everythink (or almost) I fall upon, and I never had this "unrecognized card" problem... (My major apps are on "View MyPDA")

__________________
.
"There never was a good war or a bad peace." -- Benjamin Franklin
"Life is pleasant. Death is peaceful. It's the transition that's troublesome." -- Isaac Asimov
"Newbie or not newbie, there is a question." -- Shakespeare, Hamlet 3/1 (Kind of)

jpooton

Originally Posted by Theophilus

I have like 100 different applications, including a lot of junk. I actually managed to fill my 1 Gig SD card only with applications and games ! I like to try everythink (or almost) I fall upon, and I never had this "unrecognized card" problem... (My major apps are on "View MyPDA")

I assume you actively use Wifi also ? Do you enable it with a button or with via the Wifi icon/app ?

Thanks..

jpooton

Originally Posted by zim2dive

I had, pretty sure, nothing on the replacement unit I got. LOL, let someone try to beat that :) I still have my original unit (will box it up tonite and ship it back), but could do some HW resets on that and try to recreate. Mike

Yikes... So your on a brand new unit like I am. (Almost 2 weeks old). Maybe there is a bad batch? I sure wish I had a better feeling for how widespread this problem is. I certainly have it, so I feel your pain.

zim2dive

reply to post that was in the poll thread but really belongs here

Originally Posted by Gassius

Hey Mike Lets recap here, is a HW or SW problem in your opinion? Im really sorry you got a wrong x50 twice, but you better learn to live with the fact that a lot of people got a good, functionall, problem free, one.

The point that I am trying to make, that you fail to grasp, is that I do not believe I got an Axim that is any different thatn yours. I do not believe mine has a HW bug, or driver bug, that yours does not have. I am saying that you are lucky enough to use yours with devices that work, but that on a general level, there are BT bugs when used with other devices. The best term would be an interopability bug, which I believe is driver based... either a handshaking issue, a buffering issue, not sure, I don't know BT as well as I knew other wireless data protocols (worked on the original cell phone digital data protocol).

So when you imply that my unit is somehow uniquely flawed, you are missing the point. I believe my unit is the same as all the others, only I (and several others) are using the Axims with BT equipment that you are not. Hence we see the problem and you do not.

What is annoying is that you (and others) assume that just b/c their one case works, that anyone else is doing something wrong, or has a flawed unit. We're not doing something wrong, we're just trying to interoperate with different equipment. When you imply we are doing something wrong, you are getting in the way of helping us solve the problem. Reporting what works is great. Implying that anything different is wrong is not so great.

Mike

jnguy

The only problem I heard of and experienced would be the sticky headphone jack. Sometimes, after using headphones, the internal speaker won't work because it still thinks a headphone is in there. For the first few weeks, I stuck my stylus in there and twirled around a bit. Now, its not a problem at all. Dell will be willing to replace it if you don't want to twirl, I jsut didn't want to go through the trouble.

zim2dive

Originally Posted by jpooton

Yikes... So your on a brand new unit like I am. (Almost 2 weeks old). Maybe there is a bad batch? I sure wish I had a better feeling for how widespread this problem is. I certainly have it, so I feel your pain.

I dunno, airwolf reported this problem on 11-25

http://www.aximsite.com/boards/showt...+file+transfer

so I'd have to imagine its not just one bad batch (a really big batch :) )

I also wish there was a better grasp on how wide spread it was.

Gasius seems to have OBEX working (which is useful to know). I noticed that the Axim to Axim xfers did not explicitly say OBEX (OBject EXchange) as the Axim->laptop did, so they might use a different protocol?? OBEX has config parameters (packetlength, device discovery timeout) that perhaps are not set to what they need to be for maximum compatibility. I dunno, I haven't had a lot of time to dig into the details of OBEX and see if there are any params I can hack in the registry (I did find the BT stuff there, but nothing jumped out at me).

So I dunno. I just want to break thru the smothering blanket of tech support til I can reach someone that knows a packet from a helpdesk script.

Cheers,
Mike