Windows Mobile 6 Professional IM client crashes and will not lanch

Out of curiosity, what chipset is your phone based on (if you know)?

CPU: Samsung SC32442
Width of Machine Word: 32 bit
CPU Clock: 400 MHz
CPU Core: ARM920T
Level 1 cache: 16KB data cache / 16 KB instruction cache
Instruction Set: ARMv4T

is this what you are looking for ?

Hey gottalove it:
I had the exact same problem as well, same phone, same setup, and I worked very hard with support a while back to see about getting it fixed. I did many tests for them, they gave me some older versions of the software to try and test, and was able to confirm that the Samsung I series for Verizon Wireless simply is not compatible with EQO except for the very first beta release, which could not keep a connection to the IM clients. Here are the final letters that pretty much ended any hope for us right now. Peter said in March he was still trying to get help for us Samsung VZW users, but i have not heard from him since.

2/7/2008
Hello Daniel,
To be honest, we have no idea what’s causing your problem. It could be that your phone is CDMA, but then it might not. EQO works for us and we can’t reproduce your problem. The only way we could figure it out for sure is to test directly on your phone, but that likely can’t be arranged. I’m sorry to say that you should stick with Palringo because that’s what works for you.

My reply:

As someone who does tech support for Windows Mobile devices, the whole "it works for us, and we don't know why it doesn't work for you, sorry" phrase is very very old, and usually translates to "we don't want to spend the time to figure this out" :)

I would find it hard to believe that with quite a few CDMA phones available out there (especially in the US) that your company/group would not have provided you with at least ONE CDMA phone to test on. I mean, you don't even have to get it to connect. At this point, you're just trying to get the program to launch. And whether it was my phone or not, any CDMA phone should be enough to test that theory on, even if you buy an old cheap one from ebay. (I700's from samsung are CHEAP!) The issue happens for two phones I have used now, so the CDMA theory is at least looking at, unless your company's strategy is to exclude all CDMA customers. And since you don't know if it is the CDMA issue or not, you very well could be taking the chance that if it is CDMA related, you are doing just that!

And if you're using the embedded C++ emulators, i can probably get you a package with the CDMA Rom in it. Verizon Wireless has a package available on their website that upgrades one of their phones from 2003 to WM5, and i'm sure it includes the entire rom in it. (http://download.vzwshop.com/vzw/samsungos/Samsung_i730_WM5_Upgrade.exe)

So what do you say? :) I implore you to not give up. I like your program, and i'm sure the bottom line will look better to be able to include CDMA customers in your pool. Being that CDMA is not used the world over, international calling is not usually an inherent feature, and your program would be quite beneficial.

Here's hoping! :)

And then the final letter back to me:

Indeed, we do not want to spend the time to figure it out. I would have kept going, but you said you were good with Palringo. I thought you’d given up, so I was willing to let you go. It’s not like we don’t want to support everyone, but when we’re getting hundreds of support requests some days we’re willing to lose some.

We raised this issue with the dev guys, who said they fixed it. I sent you the latest version available to me, which apparently didn’t contain the fix. The release candidate is in QA now and I suggest you try that one when it comes out. We are not even sure that this is the reason your phones don’t work. We haven’t had any other CDMA users complain. The dev guys say they fixed it and aren’t willing to drop their schedule to look into this again, not until there is an official release.

Yes, although we are in Canada, we could probably buy a CDMA Windows Mobile device, but no we don’t have any now. Buying a new phone depends on the budget, which is tight what with us being a startup and all.

The bottom line is that we are willing to keep working on this problem if you are. I’m sure that we’ll be able to solve it with patience and persistence.

So unfortunately, until enough of us Samsung I-users have the same problem to prove to the dev guys that they just thought they fixed it, we're screwed.

Thanks for posting again Daniel. You hit the nail on the head, the only way something will move on our side is when the people ask for it--which you have done, loud and clear. I have still been asking for help with this issue, but until now it has remained a low priority from our product development team's point of view. Hopefully, your post will help to speed up the process.

Peter
EQO Customer Support

In what must be the quickest and determined response in my history, the guys at EQO worked with us to identify what seems to be the exact cause of the issue. It looks like they're going to put that fix into the next release. We are totally stoked about it, and are happy to have this great program on our phones!

Thanks!!!