S2U 2.03

[Guest lohtus]

The S2U new version is out.

Lets hope that this one works without bugs... but for free software we cannot be too much greedy

Changes of v2.03

- added auto-checking of missing core graphic files.

- added options to mark an already previewed SMS/Email as "read".

- added "Country/Region Code" to set the proper Canonical number format for different devices.

- fixed the issue that system was unstable after a phone call on some devices.

- removed the notification queue warning introduced in v2.02.

- fixed the CallerID did not work on some devices (e.g. Spainish) but used to work in v1.6x.

- fixed the issue that after soft-reset, the first CallerID would not be shown on some devices.

- improved Ans/End response.

- fixed the issue that some hardware keys not locked on some devices.

- fixed SMS/email pop-up ocassionally not the same as the one opened when "slide to view".

- fixed the Task date was not update when changed.

- a few minor bugs fixed.

[Guest xiphrex]

I cant be bothered to update and then have to deal with the wierd random bugs again, so tell us how it goes on the omnia and if its working properly now, cheers.

[Guest pallen]

I'm running 2.02. the only issue I have is the slide to answer/callerID occaisionally wont pickup a call. It will ring, but the screen doesnt change. I just hit the phone hardware button to answer when it does that. I think its great for a free program. If the update fixes that issue, I'll be really happy!

EDIT:

Just updated and immediately got a call. CallerID and slide to answer came up as it should. Of course with previous versions it only failed to do so randomly. So far, so good.

Edited July 8, 2009 by pallen

[Guest gorf1000]

Pallen, I have been running 2.02 and would run into the same problem with the CallerID occasionally not picking up a call, I didn't mind it that much but I knew my wife would get annoyed if she went to answer my phone and didn't know what to do.

I installed 2.03 this morning as soon as I saw it on the website and so far I haven't had a failure on the CallerID. I've only received a couple of calls in but both have worked perfectly. I'll update if I run into the same old problem again.

[Guest matotej]

Any new thoughts about this version? Does it work better?

Any problems with CallerID or Slide2Answer?

[Guest pallen]

Its still working normally for me, but I dont receive a lot of calls. So far, so good. My batterry seemed to go down really fast last nigh, but I have installed a couple of things lately, so I dont know what the cause is.

[Guest vinbeaver]

Now is anyone using the Caller ID option in S2U2 on their Omnia running WM 6.5? I've disabled the new lock and have it set on the windows classic lock, and when a new call comes in the old caller id from winmo and S2U2 are both trying to work at the same time and makes it damn near impossible for me to answer a call. I also use ph0nex but have disabled the incoming call feature as I am not a fan of the incoming call option in ph0nex. I love the caller id option in S2U2 and it would be nice if I could get it to work right.

[Guest gorf1000]

So far since I've installed 2.03 I have not had a caller ID failure yet. I also don't receive a lot of calls in the day (that makes me feel kinda sad to say ;) ) but by now I would have expected to see a failure given how the last couple of versions have performed. Unfortunately Vinbeaver I'm only running WM 6.1 so I'm not sure how it would handle under 6.5 but I would highly recommend the upgrade for anyone running 6.1.

[Guest pallen]

Now is anyone using the Caller ID option in S2U2 on their Omnia running WM 6.5? I've disabled the new lock and have it set on the windows classic lock, and when a new call comes in the old caller id from winmo and S2U2 are both trying to work at the same time and makes it damn near impossible for me to answer a call. I also use ph0nex but have disabled the incoming call feature as I am not a fan of the incoming call option in ph0nex. I love the caller id option in S2U2 and it would be nice if I could get it to work right.

I think I noticed something like this once. I happened to be looking at my phone when it rang - I noticed some wierd graphics flashing for a second that appeared to be the default Windows Mobile popup, but it was quickly replaced by the S2A/callerID screen. The S2A screen worked fine and I was able to answer the call. If I had looked at the phone after I heard the ring, I wouldnt have seen the "glitch". I dont know if this happens all the time or if it was a fluke since normally I'm not looking at the phone when it rings.