Related
Correct me if I'm wrong. From the readings I have made , WM5 works by not closing the programs launched and keeps on working in the background even after closing the program (tapping the x button on the right upper hand). The only way to close this program completely and to free the memory is by stopping the program using the running program window. It is then that you free the memory. Unlike 2003SE once you close the program it also frees the memory.
This makes it a problem for WM5, because I notice that if you open a lot of program, eventually you loose memory and cannot run other program , not until closing all those previously opened programs using therunning program window.
I was wondering if there are any program/registry hack/patch to go around this problem.
Thanks
There are many programs that turn the x into a permanent close, instead of just minimize. I use Wisbar Advance Desktop but that is a full Today Screen replacement program. If you press the x it minimizes, if you press x and hold, it closes.
There are tons of other programs... do some searching.
It shouldnt be a problem. Too many people think of WM5 as Windows XP. When your memory is low you need to close thigns. This is not the case.
As you quite rightly say when memory gets low WM5 should close the oldest app to free up the required memory, the reason it leaves things open is to keep things fast. When you need memory, it just closes something.
I use mine for TomTom as well as memory hungry push email and my memoy always has at least 10mb free and I have never run out. If the device is running slow its normally down to a particualr app using all the processor. Skype for example which can be closed with the exit command in its menu.
Unless your having particular problems I say let it be. Closing apps each time is a pain and a waste of time.
Actually, the problem is the same in WM 2003 and 2002.
The program you are looking for is called MagicButton and it's free.
http://www.trancreative.com/mb.aspx
thanks for your reply. I will try the magic button, will update you...
Magic button lets you to define what to close and what to keep alive. I'm set to keep alive mesaging and some other applcations to get ot on faster and to closу other.
Ok button = close app
I have tried various app but none gave me what I want: when I press the hardware button ok or for example the red button (end call) to close the active window without the use of the touchscreen. Does anybody knows an app whick behaves like this ?
spb pocketplus (not free) also has this capacity, and with it you can map the "close all" or "close" to a button. you may also define exceptions for this (applications that do not close even if you choose "close" or "close all").
Hi, See and try this.It has good capacities and work really fine in Prophet.http://insoftwarehouse.com/downloads/inclose/xe.php?l=en
Hi.
When using my Diamond I noticed some processes don't disappear when they should. They fill up memory. Either you kill 'em with some Task Manager, or you soft reset.
Don't wanna SR or kill processes manually? Let my thing do it for you!
NoTSR is a very very simple program which kills some predefined processes, based on my experience with Diamond.
Source code (eVC++ 4) is for you to use and modify whatever you want. However, it would be nice if you gave me some credit if using it!
Have fun!
p. s. Sorry for the icon.
If anyone is wondering, this is what it kills off (copied straight from the source code):
"Opera9.exe", // everything still loads well
"OperaPreL.exe", // after killing them
"pword.exe", // for some reason Pocket Word leaves its process even after leaving
"CommManager.exe", // other Office apps seem to be fixed
"AudioManager_eng.exe", // last ones are opened by manila for quicker loading of tabs.
"AlbumSearcher.exe" // killing AudioManager stops music and rewinds current track.
I keep getting a "Can't list processes" dialog box when I launch the app. I tried placing the NoTSR.exe within in the extracted NoTSR subdirectory and also outside the subdirectory.
JNGold said:
I keep getting a "Can't list processes" dialog box when I launch the app. I tried placing the NoTSR.exe within in the extracted NoTSR subdirectory and also outside the subdirectory.
Click to expand...
Click to collapse
I can confirm that.
What did we wrong? Do we have to place it in a special folder, like windows?
It worked for me, but my phone was very sluggish after running the app and I had to soft reset to bring it back to par.
Thanks for starting this development, there is definitely a gap to be filled by it, I use oxios hibernate and a task manager to finish off opera .exe, this is much easier to use and your icons not so bad either!
uniqueboy said:
It worked for me, but my phone was very sluggish after running the app and I had to soft reset to bring it back to par.
Thanks for starting this development, there is definitely a gap to be filled by it, I use oxios hibernate and a task manager to finish off opera .exe, this is much easier to use and your icons not so bad either!
Click to expand...
Click to collapse
Thanks for positive feedback. I wonder why th sluggish reaction. Loading of opera as well as some TF3D tabs will for sure be slower, but whole phone is weird. After all, it just kills and leaves (see src if unsure). I use NoTSR myself and I got no problems at all. Maybe you could test it again and if it slows down show the list of processes?
@others: try using the app with rest closed. It should work in any folder; I keep it in my docs and launch via Start.
Thanks again for interest!
same error message for me. sprint touch pro with jd6.1 rom
I can't reproduce that error to analyze and fix it, so I post new version which tells you what went wrong. Try with it.
trying now
kosherpig said:
Thanks for positive feedback. I wonder why th sluggish reaction. Loading of opera as well as some TF3D tabs will for sure be slower, but whole phone is weird. After all, it just kills and leaves (see src if unsure). I use NoTSR myself and I got no problems at all. Maybe you could test it again and if it slows down show the list of processes?
@others: try using the app with rest closed. It should work in any folder; I keep it in my docs and launch via Start.
Thanks again for interest!
Click to expand...
Click to collapse
OK, so I've been using the NoTSR app for a couple of days and I can't reproduce the lag that I had when I first ran it, odd. I think it may be something to do with the fact that when I first ran it it was from within file explorer, after using it I could not get explorer to open up again properly. Now I have put a shortcut in my windows/start up/programs folder and I am running it from my start menu everything seems just fine and is all working as it should with no sluggish side effect, so thanks again kosherpig for the very useful app.
SKTools Lite (free) comes with a small program called "Free up ram." During SKTools Lite install, it will tell you something about your windows version, just click through that and let it install.
Once it's installed, go to your programs page and you'll see it there: "Free Up RAM". Just run it once. It will look like nothing is opening, but its because it's working in the background. You'll get a message box very shortly telling you how much ram (in KB) you freed up.
http://s-k-tools.com/index.html?sktools/m_lite.html
I use it all the time. Brings me from 45 -50 down to 35-40. Lowest I've seen was 32%.
Our programs are slightly different. My one doesn't free RAM by itself; it closes processes which won't close by a "close all" command. And NoTSR is not resident (after all its name is No Terminate-Stay-Resident ). Its goal is to be as small as possible, also in term of occupied disk space (~9kB now). Maybe this SKTools and NoTSR could be used in conjunction to free up even more RAM?
And, I also got the error message 2 times.
1st when I was running FM radio.
2nd when I was at the Music tab.
I solved them:
1st by closing FM radio and invoking NoTSR. Everything went OK.
2nd switched to the Home tab. NoTSR failed again. Waited some seconds, ran again. OK now.
Solution: fails? Shut everything using the HTC task manager, go to today/home screen, and invoke NoTSR after some time. I can say the behavior is really weird, since my code doesn't depend on running apps.
However, I run NoTSR everytime after using Opera. I got that error 2 times in my whole usage.
Anyways. Thanks for all responses
I find "Oxios Hibernate" frees up more ram than sk tools "free up ram" does, it is also free, but must be run manually, a useful addition to any start menu.
I'm getting about 10 mb back with NoTSR after opera browsing, "free up ram" or "hibernate" practically nothing back after opera browsing. Basically if you use opera then this is a "must have".
A small update.
If you know when Oxios Hibernate works and NoTSR fails, check this exe out. I tried to contain the Hibernate in it.
This version is bugged.
Please use version from 1st post.
If you ran this version already perform a soft reset.
Sorry for inconvinience.
chronster said:
SKTools Lite (free) comes with a small program called "Free up ram." During SKTools Lite install, it will tell you something about your windows version, just click through that and let it install.
Once it's installed, go to your programs page and you'll see it there: "Free Up RAM". Just run it once. It will look like nothing is opening, but its because it's working in the background. You'll get a message box very shortly telling you how much ram (in KB) you freed up.
http://s-k-tools.com/index.html?sktools/m_lite.html
I use it all the time. Brings me from 45 -50 down to 35-40. Lowest I've seen was 32%.
Click to expand...
Click to collapse
it lowers your memory usage by 10%???
To me it goes from 63% to 61%...
On my Diamond
thats frustrating...
Hi there, trying to use this app I'm getting the same error as others...
"Can't list processes: The parameter is incorrect. (#0)"
Task Manager is empty, I've tried leaving it on the home screen for 20 secs and running it but still the same problem.
Any ideas? I'd really like to get this working as Dutty 3.1 does appear to suffer from this memory problem.
EDIT.... OK, did a reset and it's working fine. I'll play with it over the next day or so, and fingers crossed Dutty 3.1 will be good enough for me as I don't need YouTube.
EDIT2... Worked for a while, now has the same problem as earlier.
Are you using the version form 1st post?
If not, please use it.
By the way, something is really wrong... AFAIK "Invalid parameter" has error code 87, 0 is "success". I've looked at program code to see where I could mess up memory, but I saw no such places. Help with finding this bug (you've got the source) would be very appreciated.
hi kosherpig
can you add a settings file where we can put our personal process to stop?
I've try to modify the source but I'm not able to compile it
kosherpig said:
Are you using the version form 1st post?
If not, please use it.
By the way, something is really wrong... AFAIK "Invalid parameter" has error code 87, 0 is "success". I've looked at program code to see where I could mess up memory, but I saw no such places. Help with finding this bug (you've got the source) would be very appreciated.
Click to expand...
Click to collapse
Hi Kosherpig, I am using the version from the 1st post.
I'm happy to help finding the bug, but not sure what to do here! I THINK it stopped working after I used TomTom7, but can't be sure.
It's only 1635 and it's down to 16% battery already (I think this is a problem with Dutty 3.1), so I don't want to do lots of tests. However, when I'm home and charging it, I'll try each app individually until I pin point which one "causes" the problem.
Does this help? Anything else you want me to try?
Hi kosherpig, getting on great with NoTSR now, I just have one small idea that it would be nice to show the memory stats in the pop up dialogue in a similar way to oxios hibernate. Unless of course this would significantly affect the size and speed of the app, in that case I think it is easy enough to check on the memory usage other ways with a couple of quick taps.
As posted on my blog: http://www.chainfire.eu/articles/68/AutoClosePatch_1_0_released/
Updated to 1.1 on 24 February 2010
AutoClosePatch
Some devices, especially the new 2009 Omnia series from Samsung do not have a lot of memory available. Some of these are also configured to use rather aggressive memory management. The result is that you can hardly start any amount of applications (3 or 4, usually) before the system starts to shut down already running applications, while half or more of the available physical memory is not being used at all.
What AutoClosePatch attempts to do is hook into these memory management functions and beat them into submission, preventing them from doing anything we have not explicitly told them to do.
Of course, we do have to have automatic application closing functionality so our devices do not get stuck in a low memory position, so occasionally we let the system do what it wants within specified parameters.
Note that this patch was specifically written and only tested on the Omnia II (I8000), but it should work on many WM 6.5 devices. This patch does not need any of the other changes mentioned in various MoDaCo threads and is compatible with TaskMon!
Also note that the system is not always very smart, and in my experience tends to close the last application I openened instead of the first.
Beta
Consider this a beta version (even though it is a 1.0 release). Several factors come into play and operation cannot be guaranteed. Works great for me, though!
I take no responsibility for issues that may occur, at all. If your dog explodes due to using AutoClosePatch, tough luck.
Settings
By default, my Omnia II starts closing apps when available memory drops below about 30mb, and doesn't stop closing apps until available memory has risen above about 45mb. As I start out with about 50mb of available memory this isn't very handy.
AutoClosePatch's default settings are to not start closing apps until available memory drops below 15mb, and to stop closing apps when available memory has risen to above 20mb.
The "Ultra" variant lowers this to 10/15, but has more chance of showing you an 'out-of-memory' dialog.
Installation
Install the AutoClosePatch CAB. If you want to play with the "Ultra" variant, install the normal version first!
Soft-reset after installation
Uninstallation
Simply uninstall the CAB files if you are not using the "Ultra" variant. Uninstalling will clear most settings but not some system settings. These changes aren't harmful, but you'll need to hard-reset to clear them up.
Soft-reset after uninstallation
Technical
Skip this part if you're not a techy
The whole thing is done through run-time patching, this means no files are modified on the device itself, only in-memory.
Some system calls are overridden / intercepted in shell32.exe, and depending on actual memory state WM_CLOSE may be re-cast as WM_HIBERNATE.
For the new 2009 Omnia series from Samsung TaskMon.dll is also patched, disabling it's application closing functionality. All other TaskMon functions should remain fully operational. In essence, only the standard WM application closing functionality should remain functional.
The low memory boundary (when apps start being closed) can be configured through the following registry key:
HKEY_CURRENT_USER\Software\Chainfire\AutoClosePatch\CloseStartMB
The high memory boundary (when apps stop being closed) can be configured through the following reigstry key:
HKEY_CURRENT_USER\Software\Chainfire\AutoClosePatch\CloseStopMB
You must soft-reset after changing these keys for them to take effect.
Also note that if you are going below the default 15/20 value you must install the "Ultra" settings first.
Furthermore, if you are playing with very low settings (and are thus using the "Ultra" settings) make sure to NOT set the CloseStopMB value above 20!
Downloads
REDISTRIBUTION AND COOKING INTO ROMS IS EXPLICITLY FORBIDDEN (for the time being)
AutoClosePatch v1.1
AutoClosePatch v1.1 Ultra (Settings only)
Donate
Donations can be made through PayPal
Changelog
1.1 Adjusted closing behavior so it closes less programs
1.1 Slightly adjusted default settings
1.0 Initial release
looks pretty cool
my omnia should arrive sometime next week, will definitely use this.
thanks !
does not really work for me, whenever i get to 10mb of free ram, all applications get closed ...
khomen that should be fixed in 1.1
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.
Thank you my good man 08C54399RW746270M Here you have little something for beer
fire_z said:
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.
Click to expand...
Click to collapse
Did this happen with 1.0 or 1.1 ?
Please try agian with 1.1 and make sure to soft-reset after installation !
Thank you!
Works great on my omnia i900!
Just what I needed!
Best regards!
Hi Chainfire,
Donation sent to keep your research on.
Thanks very much.
Thank you so much.
I found this thread from WinMo and is now going to give it a try.
Thanks again for your work!
Not working?
Hi,
This is exactly what I am looking for, but it does not seem to work on my devise TP2, the programs still close randomly...
I try to run the regular and ultra manually, I do not see any loaded progam (I guess that is normal since it leaves only the dll), but I do not see any entries/changes in the Registry?
Please help to make this work or propose another solution.
THanks,
Hi Stephane,
personally I switched from AutoClosePatch to EverApp (see http://www.modaco.com/content/pocket-pc-software/291321/app-everapp-v0-2-application-persistence-under-wm6-x/ for details).
It is working more confident for the case that you have individual apps that must not be closed when running in background (apps like countdown-timers, SIP-phones etc.).
This is good.. i thought closing down apps is a problem of Omnia pro only...
With this patch, my Omnia is very powerful again as my previous Touch Pro..
Thanks a lot..
Im trying it on my Omnia II now and its look really good
Thx for it!
i always have out of memory crash
Thanks for your great work. But i have a doubt:
Is there a way to exclude only one App from being closed?
I really like the autoclose function, it keeps my mobile working correctly all the day, but I'm working with my mobile ERP all the day long and i don't want anyone to close it...
thanks!
Nosfi said:
Thanks for your great work. But i have a doubt:
Is there a way to exclude only one App from being closed?
I really like the autoclose function, it keeps my mobile working correctly all the day, but I'm working with my mobile ERP all the day long and i don't want anyone to close it...
thanks!
Click to expand...
Click to collapse
To do no repost, here is the link to my advice http://forum.xda-developers.com/showpost.php?p=8508020&postcount=12.
This sounds great, but,does not work on my Omnia Pro B7610...
It installs correctly, but i get something like that after soft reset:
An unhandled exception occured at $000115E0 : EAccessViolation : Acces Violation
$000115E0
$00011818
i wish U could tell me what's wrong... i am using FluidX ROM based on 6.5.3 i guess...
Hmmm. Not really. The only idea I have is that maybe you have no .NET Compact Framework 3.5 installed. You can download it from Microsoft. If this does not help you may ask your question in the developers' thread at http://windows.modaco.com/topic/291321-app-everapp-v02-application-persistence-under-wm6x/.
hello, I know there are some other threads on the xda forum related to potential memory leaks in Android phones, but if you check those threads you will see that they remain ignored, as some optimistic people said that the memory leak concept is irrelevent in Android because "Linux handles memory in different ways ... & blah blah blah ...". Don't know if those people actually got an Android phone in their hands more than a few days ...
If you own a Samsung i5800 Galaxy 3, you may have discovered that if your phone slows down or hangs when launching a new app, even after having killed all apps, that a quick and dirty way to get the phone healty again is to switch it off, then let it reboot !
Lets hope that lifts, cars, trucks, planes and boats are not relying on Android ! Saying to people "you may need to reboot your device" is a dangerous joke. Devices needing reboots while in use should be banned. Where are the regulating authorities ?
You may have noticed that the displayed amount of available RAM (Android Assistant) is not a good measure of the phone ability to quickly and safely launch a new app. There is a huge difference in the lauch time of a new app, say when 80MB remains free, between a phone that just got rebooted, and a phone that has been used for a few minutes, going from an app to another app, manually killing apps for getting the same 80MB (said so) RAM free, and trying to launch a new app.
My phone is :
GT-I5800
2.2
I5800XXJP4
2.6.32 root SE-S508 #1
FROYO.XWJPD
Just after booting my phone, Android Assistant is reporting a 02:10 minutes boot time (01:04 for the system) and 102MB RAM free.
Launching some newspaper read app on Internet reduces the available RAM to 98MB, then 94MB when using another newspaper reading app.
When launching GPS Status, and after closing it and closing all newspaper read apps, the available RAM drops to 90MB.
My phone is doing absolutely nothing.
When launching Android Assistant, the Froyo task manager becomes very slow and the icons of all the installed apps went replaced by the default android app icon, then gradually and very slowly getting replaced by the actual icons. This is an indication that the system is now cutting the corners for saving RAM, but why is it so as 90MB RAM are still free, and why is the reaction time becoming so slow ?
At this stage, when I try opening Navigon (my off-line navigation software), it takes ages to open, but it finally opens.
Then I close it. Android assistant is then reporting 85MB RAM free.
The phone gets less and less reactive. From this point, if I try opening one of my two newspaper reading apps, it always takes much more time, and sometimes never gets to run. The system sometimes waits indefinitely. The "return" (right key) is inoperative. I need to enter the Froyo task manager (long center key press) and manually kill the newspaper reading task. At this stage, Android assistant is reporting 81MB RAM free. And the "return" key is still inoperative, even in Android Assistant. I thus need to manually kill Android Assistant using the Froyo task manager (long center key press).
At this stage, if I again try opening Navigon, it takes much more time to open, so much time that I need to reboot my phone.
Actually, I learned to always reboot my phone before launching Navigon. And always reboot my phone after having used Navigon. That's completely ridiculous.
The system "thinks" there is enough memory, but obviously when comes the time to allocate memory to a new app, the allocation takes a huge time to complete (sometimes never completes), and while doing the allocation, and even when running the app, the "return" key gets inoperative. When entering the Froyo task manager (long center key press), the apps icons went replaced by default icons.
Please tell me what's going on. Is such misbehaviour particular to the Samsung i5800 hardware, or particular to the 2.6.32 kernel ? Are there other Android phones showing the same behaviour ?
This behaviour is quite normal in every froyo build samsung has rolled out...
It couldn't be the hardware or the kernel because the things you highlighted work perfectly on gingerbread I.e cm7 for g3...
Wrongly constructed froyo could be the root cause of it IMO..
Have you given a try to custom roms ? If not cm7 give a try to kyrillos' rom... Memory management works just fine, at least better than stock..
Also "hot reboot" app from market does the job for me when froyo task manager fails...
Hi fellas,
Something's been peeving me lately with the Atrix, and it's got to do with its memory handling & auto-killing functionality.
This particular situation has been driving me nuts:
I like to use both the native browser & and the Opera browser. Primarily I use the native browser, which is set as the default, and Opera when I want to check something and I want the full (non mobile) webpage layout and its superior (in my opinion) rendering quality and speed.
So, say I've got Opera open on Engadget or XDA, one or two tabs open. I hit the Home button and open Youtube to look something up. Finish the video, hit the Home button again, and launch Opera, and it has exited already and has to reload my tabs again. This of course can cause issues like losing my place in the page or a flash video I had paused, or a message I was typing and wasn't done with.
In this simple example, all I did was launch a browser, open 2 tabs (40-60 or maybe even 80 MBs of RAM usage, depending on page complexity), hit the Home button, launch the YouTube player (30 to 50 MBs RAM usage), hit the Home button again and Opera's already been killed.
OS Monitor shows there's about 470 MBs of RAM free.
What gives? Checking the autokill settings it shows that the OS will kill empty processes when free RAM hits 82 MBs of free RAM (default settings, haven't messed with them)
This behavior doesn't happen only right after a fresh reboot. Once I've opened a few apps, google readers, twitter, facebook, camera/gallery, browser etc., it happens every time. I say this because, while I'm not a programmer (beyond high school level C++ and general computer curiosity), from what I understand by watching the app life cycle videos on Google's Android programmer site, if Opera and YouTube were the last apps to be launched, they should have the highest priority in being kept in memory and not being killed, and previously open apps should be killed off to reclaim memory before them.
I found that using Gemini app manager I can set an app to not be killed automatically, and while I understand that it's not recommended that this is done by end users, it does work, and I use the Exit button in Opera to exit it once I'm done using it.
It just seems ridiculous that I always have between 350-450 of free RAM available to the system, while apps that I use often end up being killed in the background.
Before someone jumps on me, I understand that Android apps are designed to be shut down and reopened seamlessly. My annoyance stems from the behavior of a phone that has 836 MBs of RAM to work with, and about 570 available on startup (I've frozen several motorola processes I don't use, such as the social network integration and home launcher).
I just tried what you did (open opera, loaded bbc and endgadget, watch a youtube video than returned to opera) and opera retained everything including webpage, where I have scrolled to etc. I would suggest you to unfreeze the moto apps and try again, maybe that is what is causing the problem. Sorry I could not be of greater help =(
I'm not disagreeing with you -- like I said, it's not the case after a fresh reboot, or perhaps when not using the phone heavily. It had been a couple of days since rebooting the phone for me, and kept happening all evening long every time I switched apps.
Still, even when I force keep Opera open through the Gemini third party app manager, and while opening other apps, the RAM usage never goes below 300. The OS is overly aggresively in keeping RAM free, and considering it never falls below 100 MBs free of RAM, it shouldn't be shutting down apps EVER -- at least according to the autokill levels. Is there something else I should be looking at in determining when Android kills apps open in the background?
Was it just a fluke due to memory leaks, etc?
Edit:
Further research shows that Gemini app manager doesn't stop it from being killed, but rather removes it from its own auto task kill list (which I don't use). Seeing Opera stay open for a while after a fresh reboot shows that after two or three days of being used, the phone's memory management gets bogged down & that's what caused the very short app lifespan.
I wouldn't mind rebooting more frequently if it wasn't for that damned battery jumping issue.