S2U2 v2.34 is Now Available :)

[Biker1]

There was a post awhile back regarding:
adding s2u2.exe and ilock2.exe to the cleanRAM exceptions list to avoid:
S2U2 not starting and iLock2 not working. That solution worked for me temporarily which means it way have never worked and had been a coincidence because shortly after,I had the same issues and only a soft reset would help resolve the issue.
I still don't know what is causing the intermittent problem.
I think it is a conflict with another app.
The question is which one?
I don't feel like deleting and adding apps so the intermittent problem is ok.
Btw, when the issue arises, the green is missing from the S2U2 battery.

[syrguy1969]

Originally Posted by Solange82200

Edit: What do you guys have in the S2u2 settings, what do you have under this setting: "On wake up, delay (ms) start of S2u2", and also what do you have under "Boot-up Delay"? Does it help to delay any of those things, or is it better to keep it off?

I have the stock settings for those you mentioned, I never had a need to adjust them.

[Solange82200]

Originally Posted by syrguy1969

I have the stock settings for those you mentioned, I never had a need to adjust them.

Thanks for answer. I guess what Im trying to fix when I mess with that is this: I have an Omnia, and when I get a call, for a second my regular incoming screen pops up, before it switches to the S2U2 caller ID screen. It looks unseamless, if that is even a word, hopefully you know what I mean. I know Im being picky, but since Ive solved most of my other problems with it now I have that little thing to nitpick on lol. Does anyone else's do that? I have the Omnia by the way, may just be an omnia thing

[syrguy1969]

Mine does that occasionally, not all the time though. I don't know what could help it, but if I run across something, I'll pass it along!

[deboy69]

Originally Posted by Biker1

There was a post awhile back regarding:
adding s2u2.exe and ilock2.exe to the cleanRAM exceptions list to avoid:
S2U2 not starting and iLock2 not working. That solution worked for me temporarily which means it way have never worked and had been a coincidence because shortly after,I had the same issues and only a soft reset would help resolve the issue.
I still don't know what is causing the intermittent problem.
I think it is a conflict with another app.
The question is which one?
I don't feel like deleting and adding apps so the intermittent problem is ok.
Btw, when the issue arises, the green is missing from the S2U2 battery.

I ran into the exact same problem. The solution so far that I have found and it is still working is that i added a shortcut of S2U2.exe under programs to the startup file. This has resolved my issue and is working just fine for me for the last couple of hours.

[Biker1]

Originally Posted by deboy69

I ran into the exact same problem. The solution so far that I have found and it is still working is that i added a shortcut of S2U2.exe under programs to the startup file. This has resolved my issue and is working just fine for me for the last couple of hours.

How do you create the shortcut for s2u2.exe in programs in the start up file?
I saw ilock2.exe under Device > Windows > StartUp which is where I tried to create the new folder. Is that the correct file to put it in?
I got up to where I created a New Folder but was unable to add to it.

[coreyoli]

Originally Posted by Biker1

There was a post awhile back regarding:
adding s2u2.exe and ilock2.exe to the cleanRAM exceptions list to avoid:
S2U2 not starting and iLock2 not working. That solution worked for me temporarily which means it way have never worked and had been a coincidence because shortly after,I had the same issues and only a soft reset would help resolve the issue.
I still don't know what is causing the intermittent problem.
I think it is a conflict with another app.
The question is which one?
I don't feel like deleting and adding apps so the intermittent problem is ok.
Btw, when the issue arises, the green is missing from the S2U2 battery.

Very strange, been rock solid for me... Although I do tend to cook my own ROMs and reflash every couple of days, so I suppose I just haven't run it long enough to stop working ...

Sorry you're having trouble though ...

I'm considering trying a different memory cleaner as CleanRAM does seem a touch finicky at times..

-Corey