Programs Auto-Closing!

[Guest siemi1-OmniaII]

@Chainfire grate:) I can't wait to try that.

Can somebody tell me what should i change i registry to have auto turnig screen blank? i have made some changes and i can't find wich was for it:/

[Guest Whp1]

Within the hour.

That is good, and where ? :(

Thank you.

[Guest junalmeida]

VICTORY IS MINE

Just finished a patch that - without disabling taskmon or any other registry changes - changes the memory 'freeing' to not close any apps until free RAM drops below 15mb. Then it will only close apps until it reaches 20mb of free RAM - instead of the 45 or so that is done normally.

Doing some testing, release imminent!

(beta release this is, so far I see no side-effects, but who knows)

Sure!!!! I can't believe!!! I'm waiting!

[Guest Chainfire]

LOL, ok, preliminary test here:

http://www.chainfire.eu/articles/68/AutoCl...h_1_0_released/

Guess I took longer typing than I thought I would!

I'll create it's own thread for it here as soon as a few of you have tested it in more detail. I'm beat. Let me know your issues, and I'll look at it again tomorrow!

(I'm guessing we'll see at least two updates before this is really properly fixed :()

Edited February 24, 2010 by Chainfire

[Guest siemi1-OmniaII]

Testing started.

After SR i have 47MB RAM

1. I have opened Opera 10 b3 with 2 tabs+ Google maps 4.0 witf satelite, comunication, gps and wikiperdia on. memory went down to 1,3MB :( and maps autocloased but opera was stil opened:)

2. Opera 10 b3 + Resco photo viewer + java opera mini 2,86 MB free memory, i was able to use those apps for few minutes memory went down to 1,7MB i have tryied to change between apps using showcse but they werent shown on list but memory was used 99%. But SPB mobile Shell task manager (i have set it for long press cube key)worked fine thos \e 3 apps worked ok but after few mintes both operas were closed after fliping pictres in Resco photo viewer.

After closing all apps mentioned before memory went back to 46.2MB

Edited February 24, 2010 by siemi1-OmniaII

[Guest ock]

Just to report that it stops autoclosing on my i900 too :( . Managed to get down to 24 MB before the out of memory error comes up (with 7-8 apps running). Will play around with the threshold settings.

Edited February 24, 2010 by ock

[Guest acastiyo]

Great news!! Thanks a lot Chainfire, you are the best. This memory problem was one of the most annoying things in the phone. I will also try the currnt version to look for results and possible tweaking.

Cheers!

[Guest skoda60]

Only disabling the taskmon. Phone starts with 75 mb free. After using some programs drop down to 30-40 mb. Whatever ram freeing application I use.

In this case wm6.1 is a lot better with ram handling. (now WM 6.5 NXXJB1 rom).

I like the wm6.1 IH5 till JA5. It good because it have more free RAM after boot. So it can run more applications. Still the 45mb it started to closing down the programs. After running a while just after boot. Closed down everything, used cleanRAM1.94 and freeupRAM and I was lost 20mb. Same behavevior like JA5, JB1 and kstan 6.53 wwe ROM. Now I was testing kstan 6.5.3 ROM.With Taskmon disabled. Waiting to test chainfire's patched soon. Thank very much!

[Guest Whp1]

Donation sent :( Only one thing remains, when I close a program nothing releases unused memory. One more thing, if I send the O2 to stand by mode, I got back the lost memory...

LOL, ok, preliminary test here:

http://www.chainfire.eu/articles/68/AutoCl...h_1_0_released/

Guess I took longer typing than I thought I would!

I'll create it's own thread for it here as soon as a few of you have tested it in more detail. I'm beat. Let me know your issues, and I'll look at it again tomorrow!

(I'm guessing we'll see at least two updates before this is really properly fixed :()

[Guest xaznxplaya]

Hmm just wondering do we have to set Taskmon back to automatic before enabling the patch?

[Guest pine]

donation sent. even if at the end of day there is a problem with your patch, I would still consider my money well-spent to appreciate the kind of spirit that really makes our windows mobile world unique, flexible, fun, and really powerful. I really hope that MS won't take apple's bad approach and play the god in the WM 7 as it appears to be so.

LOL, ok, preliminary test here:

http://www.chainfire.eu/articles/68/AutoCl...h_1_0_released/

Guess I took longer typing than I thought I would!

I'll create it's own thread for it here as soon as a few of you have tested it in more detail. I'm beat. Let me know your issues, and I'll look at it again tomorrow!

(I'm guessing we'll see at least two updates before this is really properly fixed :()

[Guest barki82]

@Chainfire

Thanks for the hard work done, I have question can we use this patch for Omnia Pro B7610 also?

Edited February 24, 2010 by barki82

[Guest skoda60]

@Chainfire

Thanks for the hard work done, I have question can we use this patch for Omnia Pro B7610 also?

Thank Chainfire for your patch. It worked wonderful. Appriciate your hardworks and great knowledge which will contribute to windows mobile world.

[Guest Chainfire]

Seems it needs a bit more work on the part when it actually closes apps ... That's going to take a few days.

@barki82: try, see what it does.

Edited February 24, 2010 by Chainfire

[Guest janvalek]

Great news. Thanks Chainfire. Will test as soon as im home from work

[Guest yshaikh01]

Installed on my O2, looks like it is working, I have secany's JA1 ROM and mem went down to 22MB but no apps closed!

Great work Chainfire.

Edited February 24, 2010 by yshaikh01

[Guest Chainfire]

UPDATED TO V1.1

See http://www.chainfire.eu/articles/68/AutoCl...h_1_1_released/

This should fix some issues regarding app closings that were reported since 1.0 release. Let me know.

Edited February 24, 2010 by Chainfire

[Guest roisagi]

looks amaizng--

is it safe to try it on the omnia b-7610?

[Guest junalmeida]

UPDATED TO V1.1

Installed and testing...

:( :( :(

[Guest Chainfire]

looks amaizng--

is it safe to try it on the omnia b-7610?

Pretty much the worst that can happen is that apps will still close :(

[Guest skoda60]

Thank Chainfire, already download the Version 1.1. Testing phase.

Donation done.

I enjoy the omnia2 more.

[Guest daskalos]

Works with Omnia B7610 but with a "bug"

When memory reaches 24mb down (in my case 24-18mb) you cannot open anymore applications/programs,and those that were opened (16 apps opened with 24mb left) even the task manager cannot be opened, so soft reset is needed to close all... Though system apps (those in the settings) still open and run.

[Guest dwallersv]

Donation sent, and I haven't even tried it yet.

Chainfire's past work and reputation are enough for me. Also, many thanks for providing a tech explanation on your site!

If you decide to continue working on this, adding a "do not close" list in the registry would be a huge benefit. Gravy would be a GUI front-end to manage these settings, which I'll volunteer to create and save you the effort.

The ultimate would be several levels of persitence priority, maybe three: not listed -- close first. listed, level 2: close next. Level 1, close next. Level 0: do not close.

Edited February 24, 2010 by dwallersv

[Guest Chainfire]

Works with Omnia B7610 but with a "bug"

When memory reaches 24mb down (in my case 24-18mb) you cannot open anymore applications/programs,and those that were opened (16 apps opened with 24mb left) even the task manager cannot be opened, so soft reset is needed to close all... Though system apps (those in the settings) still open and run.

Can you check with something like Remote Process Viewer or dotFred (FDC) Task Manager exactly how many actual processes are running (not "applications" per se) ? If by apps you mean things from the start menu visible in 'normal' task managers, there are also around 8 or so system processes running at all times. That would make a total of 32.

Note that WM6.x is based on CE5, which has a 32 task limit. System settings are generally DLLs loaded into one of the system's existing processes, and are thus not affected by this limit.

If this is the case, it is a bug, though not in the way you might have thought - it means AutoClosePatch also prevents the system from shutting down apps when the process limit is reached.

[Guest Chainfire]

Donation sent, and I haven't even tried it yet.

Chainfire's past work and reputation are enough for me. Also, many thanks for providing a tech explanation on your site!

If you decide to continue working on this, adding a "do not close" list in the registry would be a huge benefit. Gravy would be a GUI front-end to manage these settings, which I'll volunteer to create and save you the effort.

The ultimate would be several levels of persitence priority, maybe three: not listed -- close first. listed, level 2: close next. Level 1, close next. Level 0: do not close.

Interesting thought and I had indeed thought of making it this way, however it is a LOT of extra work I'm not sure I'll have time to do anytime soon.

In essence I would probably have to completely disable WM's internal auto-close system, and roll my own. The problem with this is that there are still a few parts of the system I have not properly reverse engineered yet, and if I don't know and understand exactly how it works, it's going to be hard to duplicate correctly.