[lastnikita]

I think the most important is not to free up RAM, but to be able to use those available without gettings apps closed.
I never had that much ram before in my WM devices, but none of them started closing apps before it actually ran out of memory (means 0, not 10 not 40)

[Sponsored Links]

[rodrigofd]

lastnikita, on Feb 13 2010, 13:20, said:

I think the most important is not to free up RAM, but to be able to use those available without gettings apps closed.
I never had that much ram before in my WM devices, but none of them started closing apps before it actually ran out of memory (means 0, not 10 not 40)

That's true... Actually, during my usual cooking, i know there are two Samsung processes/services which i havent' discover exactly what are they for: Launch DLLs, and Screen Capture. They run automatically on startup.

I do know for ex., Launch DLLs is some kind of background process that monitors several system things, and reacts upon them.. in some situations displays a typical omnia2-styled message box (like when you 'changed system colors.. reboot to fully apply them') .. etc.
Also, i am 99% sure it is responsible of the 'X button close app' behavior. If i remove them from ROM, some unexpected behavior happens.


But it is very possible that any of this two, might be responsible for app. closure ... perhaps anyone has more info on this..

[junalmeida]

rodrigofd, on Feb 13 2010, 14:47, said:

That's true... Actually, during my usual cooking, i know there are two Samsung processes/services which i havent' discover exactly what are they for: Launch DLLs, and Screen Capture. They run automatically on startup.

I do know for ex., Launch DLLs is some kind of background process that monitors several system things, and reacts upon them.. in some situations displays a typical omnia2-styled message box (like when you 'changed system colors.. reboot to fully apply them') .. etc.
Also, i am 99% sure it is responsible of the 'X button close app' behavior. If i remove them from ROM, some unexpected behavior happens.
But it is very possible that any of this two, might be responsible for app. closure ... perhaps anyone has more info on this..

I guess that ScreenCapture.exe is responsible to show screenshots on Task Switcher. Also, I have killed it and everything runs as before.

BTW, still have apps closing, even with much memory available (20-30mb free).

[pajaa]

rodrigofd, on Feb 13 2010, 17:47, said:

That's true... Actually, during my usual cooking, i know there are two Samsung processes/services which i havent' discover exactly what are they for: Launch DLLs, and Screen Capture. They run automatically on startup.

I do know for ex., Launch DLLs is some kind of background process that monitors several system things, and reacts upon them.. in some situations displays a typical omnia2-styled message box (like when you 'changed system colors.. reboot to fully apply them') .. etc.
Also, i am 99% sure it is responsible of the 'X button close app' behavior. If i remove them from ROM, some unexpected behavior happens.
But it is very possible that any of this two, might be responsible for app. closure ... perhaps anyone has more info on this..

Hi
Maybe ScreenCapture.lnk is for Task Switcher, without it there is no picture inside rectangle windows in Task Switcher
Regards

repeted reply, sorry

This post has been edited by pajaa: 13 February 2010 - 05:05 PM

[mariothecat]

rodrigofd, on Feb 13 2010, 18:47, said:

That's true... Actually, during my usual cooking, i know there are two Samsung processes/services which i havent' discover exactly what are they for: Launch DLLs, and Screen Capture. They run automatically on startup.

I do know for ex., Launch DLLs is some kind of background process that monitors several system things, and reacts upon them.. in some situations displays a typical omnia2-styled message box (like when you 'changed system colors.. reboot to fully apply them') .. etc.
Also, i am 99% sure it is responsible of the 'X button close app' behavior. If i remove them from ROM, some unexpected behavior happens.
But it is very possible that any of this two, might be responsible for app. closure ... perhaps anyone has more info on this..

A similar screen capture process was running on my Samsung Innov8(Symbian) phone.

[ratsbane]

I'm running WinMo 6.1 and there's nothing like screencapture in Startupservices or running services..

This post has been edited by ratsbane: 13 February 2010 - 08:56 PM

[kibiwi]

rodrigofd, on Feb 13 2010, 17:47, said:

That's true... Actually, during my usual cooking, i know there are two Samsung processes/services which i havent' discover exactly what are they for: Launch DLLs, and Screen Capture. They run automatically on startup.

I do know for ex., Launch DLLs is some kind of background process that monitors several system things, and reacts upon them.. in some situations displays a typical omnia2-styled message box (like when you 'changed system colors.. reboot to fully apply them') .. etc.
Also, i am 99% sure it is responsible of the 'X button close app' behavior. If i remove them from ROM, some unexpected behavior happens.
But it is very possible that any of this two, might be responsible for app. closure ... perhaps anyone has more info on this..

Rodrigo I think the autoclose issue is partially solved take a look at this post. There are still some side effects but not bad for now. The best solution is to hack the TaskMon.dll to a lower memory threshold as said in the post 113. For now anyway it is still necessary to create as said in the post a cab to automatize all the neccessary changes to get rid of the autoclosing problem. I don't know very well mortscript so I can't create directly the cab anyone can help?
in addition anyone have news how patch the nk.exe to unlock the pagepool change?

This post has been edited by kibiwi: 21 February 2010 - 09:41 AM

[junalmeida]

Check this thread:
http://www.modaco.com/index.php?s=&sho...t&p=1200237

[Sponsored Links]