View Single Post
  #1 (permalink)  
Old 03-02-2009, 12:48 PM
volsmcfalls's Avatar
volsmcfalls
Regular 'Geeker
Offline
 
Join Date: Dec 2008
Posts: 294
Reputation: 105
volsmcfalls is keeping up the good workvolsmcfalls is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
S2U2 v1.5 causing problems?

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?