[Windows Mobile Development and Hacking General] A_C:
I'm back...

Hey guys,

Just back from vacation. After spending hours to read your posts, I've summarised some problems as below:

Huge RAM requirement

Yes, the latest SLIDE eats about 5M RAM. It's because the nature of PPL (the programming language used). However, when comparing to the 7M eater of version 1, it's already much reduced. I'm not saying I'm satisfied with the current requirement, but it's what it is right now. If there is some more motivation & time is available, I may consider a "Light" version in the future. But of course, no promises could be made right now.

Caller ID issue

As I said in the post, I know there is still a long way to go to make it perfect. I think there're 2 main issues:

1. "Unknown caller" - right now the CallerID info are alll depend on the SNAPI to provide. Although I've tested v1.19 with a emulator, "unknown caller" never come out. So, I start to doubt the reliability of SNAPI...

2. "CloseApp=1" - when a call is incoming, your device is already quite busy. At the same time, if "CloseApp" is set to 1, then iLock will invoke SLIDE to start from zero. The result is you'll hear the phone ring, but it takes seconds to tell you who is calling. Even worser is when it's in Landscape mode, SLIDE will take extra more seconds to start (I've been talking to Arianesoft since day one, but still no solution yet... :( )... the result will be missing a call finally. So if you really want to use the CallerID function, please set "CloseApp" to ZERO.

Configuration

Luckily, we've got a genius who just wrote a tool for you guys who are not familiar with the registry editing tool. Please head over here to grab it. Although it's not up-to-date, it's brilliant. Just remember to restart iLock everytime you have changed any settings. Special thanks to dmagician.

Landscape Mode

As said in day one, this is still a problem for SLIDE to start in Landscape mode. It even cannot start in some devices. So no need to tell me about it. I'll let you know or need your test if it's going to be fixed in the future.

SafeMode

If your device freeze after running iLock for a certain period, please do try to set "SafeMode" to 1; then soft-reset your device. And let me know does it work for you.

@Ginex

1. I assume you have WeatherPanel installed, right?

2. pls restart iLock after any settings are changed.

@vladimin2989

The "Red Button" issue is a device specific problem that cannot be solved yet.

@Timb320

The PIN Lock/Shown Owner Info is a well known problem since many version ago. To let SLIDE quit is the only solution.

@CheezWiz

- thanks for the comment

- most functions of SLIDE uses memory dynamically, i.e. if they're disabled, lesser RAM will be used

- it's already mentioned in the 1st post/readme that in order to recover the system default CallerID, you have to soft-reset the device after changing the settings

- when you device freezed, what other applications are running?

@steph71

Athena is not supported by PPL, i.e. your problem is device specific.

@lucausee

To restore the static wallpaper, you have to set "WpFrameNo" to 1; "WpFrameRate" to 0 & edit the path of "Wallpaper" to point to the static wallpaper.

For the freeze problem, have you try the options "NoPowerSuspend" & "SafeMode"? Pls read the readme for details.

@korea206

Do you have any other CallerID apps installed?

@PianoSam

Did you restart iLock after setting changed?

@ksjulsen

Could you post your animation file here?

@tckk

dddd will produce long week (in chinese e.g. 星期五)

@lucein

What's your device? OS?

@lawmangrant

Did you set "ShowWeather" to 2?

@fastmike

Are u running v1.19?

Touch interface is a device specific problem that cannot be solved.

@wwyw

Hope I'll find a solution for Atom Life in the future...

@xamot69

I think your problem (i730 & your slider switch) is a device specific problem that cannot be solved.

@luxmen

"topbars" & "botbars" can only be modified but not hidden.

@berndhufmann

1. those unread counts are "zero hidden"

2. any screen shot?

3. "End Call + Answer" only shows up when it's a call waiting. And I'm afraid you cannot use this soft button on your WM6 Standard device.

@matthew232

Have you tried the "SafeMode" option?

What's the language of your device?

@imdbui

I doubt the lag is because your device is running out of RAM.

Hope that addressed your problems.