Related
Hi,
what does it mean technically if an app is "freezed"? Is the APK moved to another location, or are the unix access rights altered, or is a reference to the app deleted from some kind of "registry" of the Android system, or what else? Can it be done manually by a file manager?
Thanks,
Stefan
It can be done using the purchased version of Titanium Backup and probably a few other apps. It basically renders the app inactive without uninstalling it. Helpful for bloatware that runs in the background but you can't decide if you want to delete it or not.
Thanks, but this was not my question...
lowandbehold said:
It can be done using the purchased version of Titanium Backup and probably a few other apps. It basically renders the app inactive without uninstalling it. Helpful for bloatware that runs in the background but you can't decide if you want to delete it or not.
Click to expand...
Click to collapse
Yes, I know, but what does it do exactly on file system level? Doesn't anybody know?
stbi said:
Yes, I know, but what does it do exactly on file system level? Doesn't anybody know?
Click to expand...
Click to collapse
Most freezing apps simply rename the app to be frozen with an extension, like in the case of Bloat Freezer (IMHO the best one) the frozen app gets a .bzw extension. It remains in place but of course cannot be executed. The nice part is that if you run into an issue you can just rename the app back to what it was (assuming that you have root).
It works!
docfreed said:
Most freezing apps simply rename the app to be frozen with an extension, like in the case of Bloat Freezer (IMHO the best one) the frozen app gets a .bzw extension. It remains in place but of course cannot be executed. The nice part is that if you run into an issue you can just rename the app back to what it was (assuming that you have root).
Click to expand...
Click to collapse
Cool, so simple - thanks! So it can be done with any file manager.
I've just successfully frozen the preinstalled "LGWorld.apk" by renaming it to "LGWorld.apk.bak". As soon as I had done this, a message popped up, saying "Deinstalled", and the icon disappeared from the app drawer, and also the update for "LG World" vanished from the Market app.
Hmm.. freezing doesn't mean rename. It is being remove from system. If.you rename yourself, the apps may failed to work.
Accidentally sent from my Google Nexus S using XDA Premium
Freezing the app works via decreasing the temperature of the app to roughly 50 Kelvin. At this point the the app's molecular structure becomes a super condensed crystal lattice. Due to the nature of the crystal lattice, android treats the super dense app as non existent. Essentially the app is deleted from your system completely. However, think of it not as a permanent deletion but rather a reversible one. Should you chose to 'restore' the app, you can defrost the app. You could defrost the app using a microwave but I for one use TB Pro as it does a far better job.
lambstone said:
Freezing the app works via decreasing the temperature of the app to roughly 50 Kelvin. At this point the the app's molecular structure becomes a super condensed crystal lattice. Due to the nature of the crystal lattice, android treats the super dense app as non existent.
Click to expand...
Click to collapse
Haha smart ass.
lambstone said:
Freezing the app works via decreasing the temperature of the app to roughly 50 Kelvin. At this point the the app's molecular structure becomes a super condensed crystal lattice. Due to the nature of the crystal lattice, android treats the super dense app as non existent. Essentially the app is deleted from your system completely. However, think of it not as a permanent deletion but rather a reversible one. Should you chose to 'restore' the app, you can defrost the app. You could defrost the app using a microwave but I for one use TB Pro as it does a far better job.
Click to expand...
Click to collapse
ha ha ha! that was hilarious man
Press THANKS
stbi said:
Hi,
what does it mean technically if an app is "freezed"? Is the APK moved to another location, or are the unix access rights altered, or is a reference to the app deleted from some kind of "registry" of the Android system, or what else? Can it be done manually by a file manager?
Thanks,
Stefan
Click to expand...
Click to collapse
Press thanks if I helped
Source - How TO Geek
Manufacturers and carriers often load Android phones with their own apps. If you don’t use them, they just clutter your system and sometimes in the background, draining resources. Take control of your device and stop the bloatware.
We’ll be focusing on disabling – also known as “freezing” bloatware here. It’s a safer process than uninstalling the bloatware completely, and is also easier to accomplish with free apps.
Uninstalling vs. Freezing
Uninstalling an app is exactly what it sounds like – the app is entirely removed from your device. Unfortunately, it’s not possible to get many of these preinstalled apps from the Play Store if you ever need them again. Uninstalling some preinstalled apps may result in problems or instability, so you could run into problems.
It’s safer to “freeze” apps instead of uninstalling them. A frozen app is disabled completely – it won’t appear in your app drawer and it won’t automatically start in the background. A frozen app cannot run in any way until you “unfreeze” it. Freezing and unfreezing are instant processes, so it’s easy to undo your changes if you end up freezing a necessary app.
If you really must uninstall apps, you should freeze them first and wait a few days to ensure that your phone or tablet works properly without them.
You can’t uninstall or freeze preinstalled bloatware apps without root access and third-party app managers. Try and you’ll find the options grayed out in the standard Android interface.
klacenas said:
ha ha ha! that was hilarious man
Click to expand...
Click to collapse
I understand and have frozen quite a few apps with TB Pro. My issue is there are shine pre-installed apps that I like to use, but when I run the task killer, they're always running. Is there a way I can fix them where they don't keep starting immediately after killing them, but still having them available when I want to use them?
donnebonn said:
I understand and have frozen quite a few apps with TB Pro. My issue is there are shine pre-installed apps that I like to use, but when I run the task killer, they're always running. Is there a way I can fix them where they don't keep starting immediately after killing them, but still having them available when I want to use them?
Click to expand...
Click to collapse
you can try greenify it will hibernate the apps and hence the app will be available for you any time
donnebonn said:
I understand and have frozen quite a few apps with TB Pro. My issue is there are shine pre-installed apps that I like to use, but when I run the task killer, they're always running. Is there a way I can fix them where they don't keep starting immediately after killing them, but still having them available when I want to use them?
Click to expand...
Click to collapse
Another app called greenify. Or using an autostart manager to prevent them from running without ykur intervention.
sangalaxy said:
you can try greenify it will hibernate the apps and hence the app will be available for you any time
Click to expand...
Click to collapse
Thx a bunch. I dwld and installed the grenify app and disabled them, however, when I run my task killer the gallery app is always running. I wanted to greenify it, but it's not showing up in the greenify app, even when I did a search for it, it just took me to my home screen. I clicked on the app and it just opened but I didn't see any options to greenify it. Any suggestions? Thx for ur help.
so at the end is freezing and renaming the same thing? no one cleared that up, i usually just rename to BAK and thats it, what does TItanium apart from renaming?
ok i answer myself, freezing is the same as going to app manager, and selecting DISABLE
or from a root terminal using:
pm disable {package_name} (e.g. # pm disable com.android.browser)
wich calls:
/system/bin/pm
wich in turn contains:
# Script to start "pm" on the device, which has a very rudimentary
# shell.
#
base=/system
export CLASSPATH=$base/framework/pm.jar
exec app_process $base/bin com.android.commands.pm.Pm "[email protected]"
what it does is set a flag for a component to some of different values:
COMPONENT_ENABLED_STATE_DEFAULT
COMPONENT_ENABLED_STATE_DISABLED
among others. (http://developer.android.com/reference/android/content/pm/PackageManager.html)
where does it store this flag: I DONT KNOW
is this flag a value inside some manifest/ini file? : IDK
is this flag st in the file system? IDK
can someone show me the light?
edit: I DONT KNOW for sure but i think it stores it in : /data/system/packages.xml
that is generated by package manager taking info fro each app manifest. i hope i am right, but dont take my word as absolute truth since it was a quick google research lol
Renaming the apk file can result in unwanted behaviour... I learned by trial&error! I'm running MIUI 6 and wanted Google Play as default app store and not the MI Market. Renaming the apk file for the Mi Market gave me the result I wanted: launching Google Play whenever I clicked a link to a certain app. But that was until I rebooted the phone... it got stuck on the MI startup logo. After renaming the Mi Market apk file in twrp recovery, my phone booted again.
So might try freezing it to see if it will do the job properly.
Freezing Mi Market with AppFreezer worked like a charm!
el_jefe said:
Renaming the apk file can result in unwanted behaviour... I learned by trial&error! I'm running MIUI 6 and wanted Google Play as default app store and not the MI Market. Renaming the apk file for the Mi Market gave me the result I wanted: launching Google Play whenever I clicked a link to a certain app. But that was until I rebooted the phone... it got stuck on the MI startup logo. After renaming the Mi Market apk file in twrp recovery, my phone booted again.
So might try freezing it to see if it will do the job properly.
Click to expand...
Click to collapse
Depends what you mean by "renaming." Changing the extension from .apk to .apkold or .bak or something like that will harmlessly freeze the app since it's no longer seen as an apk by the system. Renaming the app itself is another thing entirely.
I renamed the extension to .noapk and Miui wouldn't boot anymore.
Good stuff
I thought that if you greenified an app, that it wasn't supposed to open again unless you opened it yourself...
But I'm getting apps that need to be greenified constantly...
I understand syncing happens and that activates some apps, but for example, I don't use Google+, but it's constantly running, even though it's supposed to be greenified, so I'm constantly having to hit the greenify shortcut, then other times YouTube will be running, because Google+ apparently opened it, so now they are both open and running, even though I've never opened them...
And I noticed the feature where you can cut an app off so whichever app opened it in the background, can't do that again. But it pops up this notification warning you, and I don't know what it means really... Is using that cut feature the way to get certain apps to stop opening other apps? Is it safe to do if I'm not using the apps?
Thanks for any info
Sent from my SGH-M919 using Tapatalk
SaintCity86 said:
... Is using that cut feature the way to get certain apps to stop opening other apps?...
Click to expand...
Click to collapse
Yep, that's what it's for.
While it is true that cutting the wake up path will stop the app running, understand what will happen if a path is cut off from a system app before doing it. You may end up with unintended consequences.
tnsmani said:
While it is true that cutting the wake up path will stop the app running, understand what will happen if a path is cut off from a system app before doing it. You may end up with unintended consequences.
Click to expand...
Click to collapse
I'm saying though, if one app I don't use opens another app I don't use.... It's gotta be harmless. Idk. Love n learn I guess
Apparently the owner is just as INSANE as his rom.
I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
scandiun said:
I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
Click to expand...
Click to collapse
Look elsewhere. Greenify doesn't "freeze" any app.
tnsmani said:
Look elsewhere. Greenify doesn't "freeze" any app.
Click to expand...
Click to collapse
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
scandiun said:
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
Click to expand...
Click to collapse
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
tnsmani said:
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
Click to expand...
Click to collapse
Yes Hibernation Manager and Greenify only work when screen is off. That's enough for me, but do you know if any app that does it also when the screen is on? (App always hibernating unless on foreground)
Hi,
for my basic understanding of Greenify I would like to know:
I ran Greenify 2.7 in root mode, currently without Xposed. This because I want to read more about Xposed first before installing.
It normally should hibernate the configured Apps automatically if I understand right.
In what time intervalls does Greenify check if such a App has been woken up and therefore hibernated again?
I watch the battery comsumption with 3C Tools and see, that the saving effect takes place only if I check manually every hour or so. Doing so, Greenify hibernates woken up Apps well and the battery saving effect is really good. But during the night I can see that the hibernation does not take place and I have 20% less capacity.
Sorry, if this question has already been discussued elsewhere. I have seearched here already, but being not sure, to find the right answers.
Edit: Now I Installed Version 2.8 Beta 8 and watch the behaviour.
Regards, Onurbi
onurbi said:
Hi,
for my basic understanding of Greenify I would like to know:
I ran Greenify 2.7 in root mode, currently without Xposed. This because I want to read more about Xposed first before installing.
It normally should hibernate the configured Apps automatically if I understand right.
In what time intervalls does Greenify check if such a App has been woken up and therefore hibernated again?
I watch the battery comsumption with 3C Tools and see, that the saving effect takes place only if I check manually every hour or so. Doing so, Greenify hibernates woken up Apps well and the battery saving effect is really good. But during the night I can see that the hibernation does not take place and I have 20% less capacity.
Sorry, if this question has already been discussued elsewhere. I have seearched here already, but being not sure, to find the right answers.
Edit: Now I Installed Version 2.8 Beta 8 and watch the behaviour.
Regards, Onurbi
Click to expand...
Click to collapse
Have you enabled Greenify in Device>Settings>Security>Device Administrator?
Do you have the donation pack?
Which version of android and what phone?
Normally, Greenify watches for apps waking up and hibernates them. There is no fixed interval for checking.
From your description I would guess that only manual hibernation is working and not automatic hibernation.
Thank you for your answer!
tnsmani said:
Have you enabled Greenify in Device>Settings>Security>Device Administrator?
Click to expand...
Click to collapse
Yes, there is a "Greenify Automator". This entry is there since Version 2.7 has been installed. It is ok for 2.8 Beta 8 also?
Do you have the donation pack?
Click to expand...
Click to collapse
Yes, I have.
Which version of android and what phone?
Click to expand...
Click to collapse
5.0.1 ,64 Bit, rooted, Huawei P8 Lite (ALE-21)
Normally, Greenify watches for apps waking up and hibernates them. There is no fixed interval for checking.
Click to expand...
Click to collapse
Ok. I could imagine, that a timer controlled action like I do it, would help.
When Greenify is not in "root" mode, it does an automated "Stop" of the Apps. With root mode it reports, that the found Apps are hibernated. When Greenify does this only once and another App will be waked up later, this now again running App will drain the battery anyway. That's not particular senseful I find. Therefore my question about regular checks.
From your description I would guess that only manual hibernation is working and not automatic hibernation.
Click to expand...
Click to collapse
I think so as well. But the Settings tell me that automatic hibernation is active (in German)!
The last 2 hours suddenly a process has been started named SUPL20Services. It will be reported by the 3C Toolbox analyser. This process caught my eyes several times already. The only context I found googling has to to with GPS. But when I disable GPS, this process comes up anyway. I tried to identify the parent process of it with "ps -t", but to no avail. There is no.
In this case Greenify can do nothing I believe.
Regards, Onurbi
onurbi said:
Thank you for your answer!
When Greenify is not in "root" mode, it does an automated "Stop" of the Apps. With root mode it reports, that the found Apps are hibernated. When Greenify does this only once and another App will be waked up later, this now again running App will drain the battery anyway. That's not particular senseful I find. Therefore my question about regular checks.
Click to expand...
Click to collapse
When an app is hibernated, it can not wake up again unless you specifically open it or another app/process wakes it up. So a hibernated app continuing to run does not happen unless you permit it.
If you find that a hibernated app is woken up again (not specifically by you), long press the app's name in Greenify and you will get a scissors icon on top. Clicking that icon will pop up a dialogue box which will tell you what woke up that app and if you don't want it to be woken up, click the appropriate button in the dialogue box.
If you find that a hibernated app is woken up again (not specifically by you), long press the app's name in Greenify and you will get a scissors icon on top. Clicking that icon will pop up a dialogue box which will tell you what woke up that app and if you don't want it to be woken up, click the appropriate button in the dialogue box.
Click to expand...
Click to collapse
Yes I understand this.
I think I tried this in the past and Google Services has been reported what has woken up, in this case, Hangouts. Hangouts is very "aggessive" I found and will very often be active again.
I'll have a look at the scissors next time a app will be active.
onurbi said:
Yes I understand this.
I think I tried this in the past and Google Services has been reported what has woken up, in this case, Hangouts. Hangouts is very "aggessive" I found and will very often be active again.
I'll have a look at the scissors next time a app will be active.
Click to expand...
Click to collapse
A word of caution: some apps require such wakeups to function properly. So if after using the scissors, you find that the app is not functioning correctly, you can again long press it and then click the three dot menu at top right in Greenify. You will get an option to reattach whatever you had cut earlier.
tnsmani said:
A word of caution: some apps require such wakeups to function properly. So if after using the scissors, you find that the app is not functioning correctly, you can again long press it and then click the three dot menu at top right in Greenify. You will get an option to reattach whatever you had cut earlier.
Click to expand...
Click to collapse
Thanx, I'll have a look at ths fact!
I lost magnify icon....im usin greenify 2.7.1 final stable with donation. Why??
Thankss
Can someone help?
hawkdown77 said:
I lost magnify icon....im usin greenify 2.7.1 final stable with donation. Why??
Thankss
Click to expand...
Click to collapse
Which magnify icon are you talking about?
tnsmani said:
Which magnify icon are you talking about?
Click to expand...
Click to collapse
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
hawkdown77 said:
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
Click to expand...
Click to collapse
I am on 2.8 beta9. There is no such icon. I have never used such an icon in Greenify and so I am not sure whether it was available in any version.
I am not saying that you are wrong but just that I don't remember. I also don't think that it is of much use unless you have hundreds of apps.
hawkdown77 said:
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
Click to expand...
Click to collapse
Due to restriction enforced by newer Android system, that selector could no longer work, thus was removed long ago.
oasisfeng said:
Due to restriction enforced by newer Android system, that selector could no longer work, thus was removed long ago.
Click to expand...
Click to collapse
But there some apps that i can not choose because it not show in the list of apps. How can i proceed to greenify them?
first of all - amazing app!!
I have one question, maybe I got it completely wrong ...
If I hibernate an app, and restart it later again, e.g using the recent key, shouldn't the app state also be restored??
e.g. I use root explorer and navigate to a folder, then press the home key. When I get back to the application ( not using greenify) I will see the same folder that I was in before (if LMK did not kill my app of course).
But when the app was hibernated (greenifed), it always starts up "fresh"... Is this intended??
Galaxy s6, android 5.0.2 rooted
The app is stopped so is normal. Btw in Root Explorer is an option to restore your last working folder, check it if you want to go back to your folder.
MihaiSG said:
The app is stopped so is normal. Btw in Root Explorer is an option to restore your last working folder, check it if you want to go back to your folder.
Click to expand...
Click to collapse
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
That is how the app is designed. You are not supposed to Greenify every app especially those you use frequently. That will consume more battery. This is stated in the OP of the main thread by the Dev himself and repeated many times in many sub-threads.
Makes sense.
tnsmani said:
That is how the app is designed. You are not supposed to Greenify every app especially those you use frequently. That will consume more battery. This is stated in the OP of the main thread by the Dev himself and repeated many times in many sub-threads.
Makes sense.
Click to expand...
Click to collapse
Yes, makes sense.
Thank you for the clarification.
GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
I believe the closest equivalent of the IOS behavior that you are looking for is generated through Doze, a function implemented in Android phones with Marshmallows. For a more aggressive Doze behavior, you can use greenify. And if you don't have marshmallow on your phone, I believe there is a dedicated Doze app on the play store
Surfinette said:
I believe the closest equivalent of the IOS behavior that you are looking for is generated through Doze, a function implemented in Android phones with Marshmallows. For a more aggressive Doze behavior, you can use greenify. And if you don't have marshmallow on your phone, I believe there is a dedicated Doze app on the play store
Click to expand...
Click to collapse
Ok thank you. I assume the app you are taking about is shutApp... The doze app (same developer) just cuts off the network activity using a dead VPN connection. I will try shutApp on my device phone, but for now I am happy with greenify, it works great except for Chrome and YouTube... Thanks for your help..
GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
You may try the new experimental feature - "Shallow Hibernation" if your device is running Android 6.0 and rooted. It preserves the app running context even in hibernation.
oasisfeng said:
You may try the new experimental feature - "Shallow Hibernation" if your device is running Android 6.0 and rooted. It preserves the app running context even in hibernation.
Click to expand...
Click to collapse
I will give it a try, thanks!