Hello All,
I am running
ROM: TNT.1933 TouchFLO Edition
I/SPL is 2.25
Radio is 2.19.11 and
OS is 11.0.0.1
TNT comes with Oxios Hibernate and CloseApps, which seems to have very naughty behavior on my system. I can only ever open one application, even if I just switch to “Today” from an open app, the app I was in closes (not shown in Task Manager, truly closed). This stinks. Tried to delete the .exe files, but can’t – they’re marked as “ROM” and “READ ONLY” and can’t make a change to those – just reverts right back. Also can’t kill the prog via task manager because it doesn’t show up there. Please please please tell me how to get rid of this program bundle – I really really hate it!
Thanks!
-tynk-
Both oxious closeapp and hibernate only do something when YOU run them...they run once and exit...the difference between the two is closeapps tries to close ALL apps...hibernate tries to free as much memory as it can without closing any apps.
Neither would be closing any apps without your knowledge.
that's what I thought, too!
But soft reset or shutdown/restart, and upon loading the today screen, the progs up and running (can see the closeapps bars in upper left corner of the screen). I checked startup and it isn't in there (even checked "show all files" in case it's hidden, but nothing).
From my research (yes, I did try figuring this out on my own - other than a couple mentions of instability with these two progs and WM6, there wasn't any good help to be found ), I thought if I didn't click on either icon, it wouldn't start but that doesn't seem to be the case here.
They are somehow loading/starting automatically, so even if I could change the attributes so they were 'delete-able', if I can't get them to stop running (again, neither is visible in taskmanager), I won't be able to delete them! Arrrggg!
Thanks for the response, though! Any other thoughts?
First, any programs built into the rom can NOT be removed. You could create dummy files (create a blank text file and rename it to the name of the file you want to "remove" and it will be used instead of the one in the rom).
For them to be starting automatically as you claim, then there has to be either a link for them in the \Windows\Startup folder, or an entry in the registry (look in HKEY_LOCAL_MACHINE\init , or just do a search with a registry editor).
But as Famewolf indicated, what you are describing is NOT how either of these programs work. They don't stay in memory and continue to run. You start them, they try to free up memory (in two different ways depending on which one you run) and then put up a dialog to show you what they did. After you close the dialog then they exit.
I'm not doubting the behavior you are seeing on your phone, but I am doubting that you are looking in the right direction claiming that the Oxios apps are causing this. As I tell people that run my own roms... If things don't work for you, then switch to a different rom. Also, if you've installed ANYTHING on the rom, then make sure what you have installed is working properly and isn't what is causing the issue. If you hardreset or reflash, and do NOT install anything else, do you still see this same behavior?
Finally, due to the odd nature of your problem, did you by chance install the rom, then do some sort of restore from like spb backup or sprite backup or similar? If so, you've most likely screwed up the registry as you can not restore a backup from one rom to another one.
Good luck, and hope maybe this helps you in figuring out what is going on.
famewolf said:
Both oxious closeapp and hibernate only do something when YOU run them...they run once and exit...
Click to expand...
Click to collapse
NOT TRUE!
oxios with skull icon(i forgot its name, because i am not using it, only hibernate..)WILL close ANY app that is running in background!!!!!
so be aware of this.,
nothin said:
NOT TRUE!
oxios with skull icon(i forgot its name, because i am not using it, only hibernate..)WILL close ANY app that is running in background!!!!!
so be aware of this.,
Click to expand...
Click to collapse
guys, both of you are right
first, both oxios apps will be started after the request from the user, then do their job and exit. The skull-one will close apps, the snowflake (or what it is) will free memory. But none of the application will be running in background, closing everything the user starts
His observation is correct, silly as it may sound.
For a long time i wondered why my apps would keep closing (i was using mbutton so i could see which apps were open), as soon as i opened another app, the app which went to background would get closed, even though I would have plenty of program memory free. I started tracking the reason for this and soon found out that this behaviour started as soon as i executed oxios hibernate. It would keep happening until i did a soft-reset, after which the system would work fine until (guess what!) i ran the hibernate app again!
Best thing to do is get the sktools lite version and use its free ram shortcut. Or better yet, forget about free ram at all, remove all indicators on your today screen etc etc, and surprisingly you'll never be worried about free ram and your system will work smoothly enough. If you're so worried about free ram, schedule your system to automatically soft reset once a day during the night.
ammarr said:
His observation is correct, silly as it may sound.
For a long time i wondered why my apps would keep closing (i was using mbutton so i could see which apps were open), as soon as i opened another app, the app which went to background would get closed, even though I would have plenty of program memory free. I started tracking the reason for this and soon found out that this behaviour started as soon as i executed oxios hibernate. It would keep happening until i did a soft-reset, after which the system would work fine until (guess what!) i ran the hibernate app again!
Best thing to do is get the sktools lite version and use its free ram shortcut. Or better yet, forget about free ram at all, remove all indicators on your today screen etc etc, and surprisingly you'll never be worried about free ram and your system will work smoothly enough. If you're so worried about free ram, schedule your system to automatically soft reset once a day during the night.
Click to expand...
Click to collapse
I use oxios hibernate ALL THE TIME..I even have it on a quick launcher button....having apps close on their own is NOT normal behavior and I'll say again oxios hibernate is not causing this..I keep palringo and other apps running all the time in background...either your registry had issues or your rom did because it works fine here...I sometimes go days without rebooting the phone because of oxios hibernate.
famewolf said:
I use oxios hibernate ALL THE TIME..I even have it on a quick launcher button....having apps close on their own is NOT normal behavior and I'll say again oxios hibernate is not causing this..I keep palringo and other apps running all the time in background...either your registry had issues or your rom did because it works fine here...I sometimes go days without rebooting the phone because of oxios hibernate.
Click to expand...
Click to collapse
I have traced the problem specifically back to oxios hibernate. It does not happen with sktools free ram. For some reason the WM_HIBERNATE message doesn't die and keeps killing all background applications. I've had the problem on the stock wm5, ppctuning's superrom, wrcx1 etc etc (basically all ROMs i've tried).
There could be a reason why this is just happening for some devices, i dunno, but the culprit definitely is oxios hibernate.
Have you tried to check your softkeys? I had a problem with them and even if the label says an app when I pressed the button ot activated another thing... well that happeneded sometimes... now it works correctly...
Hi All,
Thanks for all the helpful responses. I really am stumped on this one. Checked my registry (did searches for 'oxios', 'hibernate', and 'close') and found nothing. Yet after a soft-reset or normal restart, it's up and running again, and I am unable to open multiple apps or switch from one to the other and back.
I did have an odd thought - I am assuming the program in question is Oxios CloseApps, but maybe I'm wrong? I can't access any of the options on it, so just occurred to me to check. On the today screen, upper right corner, next to the time is a set of 3 small horizontal bars (forming a box) with a small up arrow. Tapping this yields a single line iconic menu that has a set of three boxes, a wrench, and a 'memory' bar with %. If I click on the boxes or wrench, nothing happens. If I click on the memory icon, it takes me to my Memory setting, showing how much storage and program memory I have, my storage card, and my running progs (no, this is not ever listed there - if only it were that easy!) This is CloseApps, right?
Thanks again for all the help!
Tynkrrbell said:
Hi All,
Thanks for all the helpful responses. I really am stumped on this one. Checked my registry (did searches for 'oxios', 'hibernate', and 'close') and found nothing. Yet after a soft-reset or normal restart, it's up and running again, and I am unable to open multiple apps or switch from one to the other and back.
I did have an odd thought - I am assuming the program in question is Oxios CloseApps, but maybe I'm wrong? I can't access any of the options on it, so just occurred to me to check. On the today screen, upper right corner, next to the time is a set of 3 small horizontal bars (forming a box) with a small up arrow. Tapping this yields a single line iconic menu that has a set of three boxes, a wrench, and a 'memory' bar with %. If I click on the boxes or wrench, nothing happens. If I click on the memory icon, it takes me to my Memory setting, showing how much storage and program memory I have, my storage card, and my running progs (no, this is not ever listed there - if only it were that easy!) This is CloseApps, right?
Thanks again for all the help!
Click to expand...
Click to collapse
the program you are talking about is
HTC Task-Manager 2.0 / x button
go to start - settings - system - task manager
steph
I recently flashed my uni to tomal 8.2 and I love the automatic memory management, I no longer have to soft reset to get more memory, however I think this is preventing me from being able to run background (minimized) applications, such as mortplayer behind tomtom like I could before. Is there a way to do this, even if it means temporarily disabling the automatic memory management?
you can temporarly close the task manager by long pressing the [x] upper right and choosing functions---exit
for disabling it permanently, from the same menu above, go to preferences---startup (in the bottom line) and choose disable, or just delete the link wktask.lnk from windows\startup folder
I'm not sure that the memory management and the task manager are the same thing.
Cheers,
Steve.
ops, my fault... thought the problem was minimizing the application instead of closing them, didn't pay much attention at the question.
anyway, i haven't experienced problems with apps in background, but i don't use tomtom and mortscript, so i'm no help for you, sorry for the useless answer.
Whenever I try to run a background application (like playing music with Media Player) and I return to the home screen or I open another application through the start menu, my TC kills the background application after a few seconds. Does this also happen to any of you? Is it something I've done? As it is, I cannot multitask, and frankly it is very annoying.
Just for the record, I'm not closing applications with the X button (configured to minimize only), but this happens even if I switch applications without touching the X button.
mpmf said:
Whenever I try to run a background application (like playing music with Media Player) and I return to the home screen or I open another application through the start menu, my TC kills the background application after a few seconds. Does this also happen to any of you? Is it something I've done? As it is, I cannot multitask, and frankly it is very annoying.
Just for the record, I'm not closing applications with the X button (configured to minimize only), but this happens even if I switch applications without touching the X button.
Click to expand...
Click to collapse
This happens to me as well. I especially find this troublesome, because I'm running SecondToday for some critical plugins, like PhoneAlarm. The OS always kills SecondToday when I'm trying to activesync or if I open a large program, like Copilot. It does this despite the fact I have over 100MB of free program memory. Very frustrating.
I've found that if I have more than 110MB free, it will leave most programs alone. It's when I get below 110MB that it starts to kill programs. Not sure why it's closing programs with so much free program memory... :-/
By the way, this is known WM behaviour. I'm just used to it doing it when I'm down to 4-6MB left.
This was a thorn in my side for almost a week until I found this fix:
Using a registry editor (I use Total Commander) go to
//registry / HKCU / software / HTC / Taskmanager / EnableAutoKill
Value by default is "1"
Change to "0"
Do a soft reset and your problem will be solved
There is also a way to decrease the threshold so that it will autokill when less than the default memory is remaining, but for me; when I have the most things running is likely to be the worst time for the phone to autokill my processes. That is why I would disable it altogether
It worked... Thanks!
I actually tried that tweak several days ago, but it did not solve the problem. It appears something else besides the HTC task manager was killing SecondToday. I suspect the actual OS, because it would happen ALWAYS when I tried to Activesync.
I've since scrapped SecondToday and am using another method to run PhoneAlarm on the actual Today screen, which is much more reliable. I needed a stable solution.
I thnk you can under task manager, assign those programs to the exclusive list, then it won't shut it down?
starstreak said:
I thnk you can under task manager, assign those programs to the exclusive list, then it won't shut it down?
Click to expand...
Click to collapse
Nah. That was the first thing I tried.
That won't keep WM from killing programs anyway, if the OS *thinks* it needs more memory.
This has always been a "feature" of WM -- I just don't understand why it's killing apps when I have >100MB of free program memory... ??
I got my father a sprint HTC Snap (Dash 3g) and was wondering if there is a program that would automatically kill running tasks. I don't think he will bother to go to the task manager and kill the task from there. There are no apps that he would want running in the background so Everything can be killed.
Any app for that? There is no exit option in IE and the camera and many other apps which I think is retarded.
I think the way he exits a program is by pressing the Home key and it keeps the program running in the background.
master4g said:
I got my father a sprint HTC Snap (Dash 3g) and was wondering if there is a program that would automatically kill running tasks. I don't think he will bother to go to the task manager and kill the task from there. There are no apps that he would want running in the background so Everything can be killed.
Any app for that? There is no exit option in IE and the camera and many other apps which I think is retarded.
I think the way he exits a program is by pressing the Home key and it keeps the program running in the background.
Click to expand...
Click to collapse
I'm using Oxios CloseApps, works perfect.
Google for it!
Thanks for the reply. This program seems good, Does this program shut the apps automatically, or do I have to run it once in a while. Maybe shuts all programs every 5 minutes if the phone isn't currently on... or maybe shuts idle tasks after they havent been used for several minutes.. etc
If there isn't such an app, is there an app that would automatically open a program every xx minutes? then I can train that app to open Oxios every couple of minutes.
If it was my phone, I wouldn't mind running it, but then again this is for my father and I don't think he would bother.
Moved as not software release.
Hey everyone,
This is intended to people who use Whatsapp or apps that show similar behavior.
If Whatsapp is in the background app list, I can easily hold the back button, access the list, and click on it and it will resume from where I was.
However, if the background is still in the background app list, and I clock on the Whatsapp live tile, the app has to re-launch itself instead of resuming from where I left it.
Is that a Whatsapp malfunction or normal WP7 behaviour? Other apps do not behave like that so I am guessing it's whatsapp.
I only had my Lumia 900 for a week and still new to WP7.
Your help/comment/feedback will be appreciated.
Thank you.
clicking on the app-tile will force every app to relaunch (except some built-in "apps" like your browser and so on)
roqstr said:
clicking on the app-tile will force every app to relaunch (except some built-in "apps" like your browser and so on)
Click to expand...
Click to collapse
I find that a bit odd don't you think? What for?
It's a limitation of Windows Phone right now. I think it's mostly done to reduce the amount of background processes running and hence will give better battery life.
Hopefully this will change with WP8!
Actually, that's mostly incorrect. It is the default behavior of WP7, and the reason for that behavior is to allow the user to re-launch an app that has become hung in some way (since apps can trap teh Back button, it's entirely possible to make an app that the OS provides no other way for the user to exit from). In theory (I haven't tried it myself), it's possible to make a configuration change that causes the default "launch" behavior to be resume, rather than restart.
Background processes are completley irrelevent, because WP7 has no (significant) process limit and does not let apps run in the background (consuming battery) anyhow. Backgrounded apps are fully suspended; they use RAM but if another program needs it, the suspended app will be tombstoned (think of it as "hibernated"), the process ended, and the RAM freed.
Interesting although a bit annoying since the app takes 5 seconds to relaunch and fetch messages although the messages have been received and notifications have appeared on the top.