S2U2 v1.5 causing problems?

volsmcfalls · #1 (**permalink**) 03-02-2009, 12:48 PM

I recently installed the new S2U2 (v 1.5 I believe) and have run into some odd problems.

For some reason, from time to time, when I get an incoming call while the phone is locked, I hear the ringtone and the phone vibrates, but S2U2 doesn't show that I am receiving a call. I use the slide bar to unlock the phone, and it unlocks normally. The phone isn't telling me I am receiving a call. I can't answer or ignore it with the hard buttons. But, the missed call DOES show up in the call log. So I have no way of knowing who is calling me when it does this until AFTER they have called.

I thought this was related to my disabling the Samsung Dialer, but I have re-enabled the Samsung Dialer (I got tired of starting programs with my face

) and the problem persists.

The only other thing I can think of that might be causing this problem is that I am now using Imarche's SPBMS skinning app, but it's not really a "program" but is rather a series of scripts that run dependent of each other.

Also, another thing I am running into is that sometimes after I unlock the phone the original Samsung Menu pops up and I have to exit out of it.

Is anybody else having these problems?

**Adrynalyne** · #2 (**permalink**) 03-02-2009, 12:50 PM

Its definitely a bug in 1.5. I was just experiencing this today.

volsmcfalls · #3 (**permalink**) 03-02-2009, 05:20 PM

Quote:

Originally Posted by Adrynalyne

Its definitely a bug in 1.5. I was just experiencing this today.

In regards to which issue? The incoming calls or the Samsung menu popping up?

a_c_s · #4 (**permalink**) 03-02-2009, 05:30 PM

I have had the call not showing up issue in the last few iterations of S2U2 including the current one, 1.5D that I am using on my Touch Pro...I can tell a call is coming in and see the phone ringing, but by the time I am able to unlock it the call can no longer be answered...and while it is ringing, S2U2 does not show me the name as you said...this does not happen 100% of the time, but enough that it's annoying...

gaurhoth · #5 (**permalink**) 03-02-2009, 06:07 PM

I haven't had that exact issue, but I have the Caller ID feature turned on in S2U2 and usually once or twice a day, a call will come in and neither hard buttons nor onscreen green/red buttons (from S2U2) will work to answer the call. I end up having to call the person back from Missed Calls.

devinc · #6 (**permalink**) 03-02-2009, 06:28 PM

I get these problems too. Just have to wait for AC to get out a fixed version.

Someone should probably alert him on the XDA forums. I will if I can remember.

Devin

**Adrynalyne** · #7 (**permalink**) 03-03-2009, 12:53 AM

I was referring to the first issue.

osyrus · #8 (**permalink**) 03-03-2009, 01:11 AM

I have expierenced in my touch pro that as long as I dont have the caller id feature on, then I can answer without problem.

**darren.wlsn1** · #9 (**permalink**) 03-03-2009, 01:38 AM

i use s2u2 newest version and turn caller id off and use s2a for the caller id with 0 problems.

**syrguy1969** · #10 (**permalink**) 03-03-2009, 09:39 AM

I almost hate to say this, but the latest version (1.50, not d) works flawlessly on my Omnia. I have had what is described in the OP happen with past versions, but it was very few and far between, and all I had to do was press the hardware phone button and the call came right through.