ok just got this kindle hd 7 and been tweaking since day one. i got twrp with cm10.1 running on it. some apps that have help my kindle are:
https://play.google.com/store/apps/details?id=net.selfip.unet.developer_options
https://play.google.com/store/apps/details?id=ccc71.pmw
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
developer option, system tuner, and greenify is all you need to may kindle fly.
developer option app: turn off all animation scales
system turner: freeze Google system apps, stop startup apps, tweaks
greenify: hibernate most all apps
before i had about 90-100mb free ram when first boot. now i get over 300mb free ram after boot. makes kindle a bit more responsive imo. and freezing those google apps will make your wakelocks go away and should increase battery life significantly. Google search is a big battery hog and needs to be put to sleep.
Related
Hello!
I installed ES task manager today on my new Nexus 7 and I was shocked to see that several apps are consuming 20mb+ of RAM when I don't even have them open, such as Titanium Backup, Facebook Messenger, PIE Controls, Auto Hide Softkeys. Even apps like YouTube, Gallery, Chrome, Currents and Hangouts seem to be running and using RAM and I have never opened any of these applications before. The actual app switcher shows that I have no apps open, yet ES Task Manager reports that 25% of my CPU is being used. All in all, an almost fresh install of Android idling is consuming 1GB of ram and 1/4th of my CPU time.
I have Googled this issue and discovered that many people are annoyed at developers who have background services, and sometimes even refuse to use an app that has such background services, but I haven't been able to discover why these background services use so much RAM (or even why titanium needs a background service), and I would really like to be able to just kill Chrome, Youtube, Currents etc because I never use these, but of course when I kill them in ES Task Manager they re-open within several minutes.
Can anybody shed some light on what's going on here? From what I can gather after searching around the forums, some people advocate the use of task killers, and some people also say killing all these services and apps just makes battery life even worse.
Edit: google+ is using 20mb of ram and I never even use it-- why!
If you are rooted you can use apps like Greenify to pause them temporarily until you run them. You can also use apps like Clean Master that will kill all task on every screen off. Ultimately you can remove these apps that are taking up a lot of ram as the best solution.
youngnex said:
If you are rooted you can use apps like Greenify to pause them temporarily until you run them. You can also use apps like Clean Master that will kill all task on every screen off. Ultimately you can remove these apps that are taking up a lot of ram as the best solution.
Click to expand...
Click to collapse
Wow, didn't know something like greenify existed, thank you!
I am trying to reduce my phone boot time and boost performance and battery life and want to better understand how applications manage to load themselves on system boot. I have a lot of apps installed, several hundred; and using the Bootmanager in XPosed as well as the Autostarts App I seemed to be able to turn off most auto running apps, however,
1) Some apps still manage to load and I have not a clue how .. so I will turn the phone on and as soon as the launcher appears go to the settings and apps and see what is running, and processes will appear which I have no desire to be there. For example RocketPlayer manages to load itself even though not a startup app and has no widgets etc. It does have several receivers still active but none of these seem obviously related to system boot.
2) If I look at all the applications that have a receiver hooked up to 'Connectivity Changed' for example .. do they all get run when the connectivity changes, or are they only notified if that application is open at the time?
3) in general is it a bad idea to have lots of apps and better to stick to the minimum of what you use regularly?
4) should one just Greenify all apps not regularly used or essential?
Any help on this subject would be appreciated!
I understand the whole approach Android uses to memory management as opposed to Windows etc....
I also found this blurb below
It's important to note that Greenify is not a task killer (which you shouldn't use anyway), and it doesn't "freeze" apps. The apps that Greenify hibernates are still usable if you want to switch to them, and you can still pass data to them as though they were running. When you switch back to them, it's like you never left. Greenify just keeps those apps from launching new background processes (a problem with task killers) and you don't have to unfreeze or thaw an app to use it when you want to (a problem with "frozen apps").
Click to expand...
Click to collapse
But here is what I don't understand:
1) Even though it isn't a Task Killer per-say, it sure sounds like an advanced task killer to me. If it is preventing something from starting up, it is killing it.
2) What benefit is Greenify supposed to have? Having all (by all I mean maybe 5 at most) desired apps hibernating, I have 700MB of free memory (using xposed method). If I remove Greenify I have 1.5GB of free RAM. These numbers are with ALL applications already open since boot that I use on a daily basis.
While full memory is not a bad thing in Android, how can it be better having 1 app hog all of the memory vs having 5 apps running in the background using less memory. Can someone shed some further light on this?
mikemikemikexxx said:
While full memory is not a bad thing in Android, how can it be better having 1 app hog all of the memory vs having 5 apps running in the background using less memory. Can someone shed some further light on this?
Click to expand...
Click to collapse
If I understand you correctly you're saying that greenify uses a lot of ram? Greenify for me is idling at 5-7 mb of ram all for time.
cAase said:
If I understand you correctly you're saying that greenify uses a lot of ram? Greenify for me is idling at 5-7 mb of ram all for time.
Click to expand...
Click to collapse
Correct, it was literally using around 700Mb. I rebooted to make sure it wasn't a fluke. I removed Greenify, rebooted again and had 1.5Gb free Ram
mikemikemikexxx said:
Correct, it was literally using around 700Mb. I rebooted to make sure it wasn't a fluke. I removed Greenify, rebooted again and had 1.5Gb free Ram
Click to expand...
Click to collapse
Sounds completely weird.
the main benefit of greenify is the point that it prevents apps from starting (they are frozen untill you open them) this way the apps can't force wakelocks and your device kann stay in deepsleep state longer
mikemikemikexxx said:
Correct, it was literally using around 700Mb. I rebooted to make sure it wasn't a fluke. I removed Greenify, rebooted again and had 1.5Gb free Ram
Click to expand...
Click to collapse
As I understand, greenify to me is more to battery saver depends on stopping unwanted and unneeded wakelock when app is Greenified. Also as I understand, when an apps launch or relaunched, it will consume more ram in normal way (without being Greenified).
Try this, its not a solution, more to suggestion. Try use Wake Lock Detector along with Greenify, one app will detect the problem and another will execute an action to prevent "unwanted battery and RAM usage".
Above all, it depends on how and what method of modding you perform on your device.
Its just my logic thought(not black n white proven). Hope it will help us a little.
i8190n SlimKat9.0(Android-Andi)
But all the settings. It won't let me hibernate the apps before I've completed 10 - 15 settings and there are no explanations to what the settings are. Greentify is totally useless if you're not a techie.
RolfyBerg said:
But all the settings. It won't let me hibernate the apps before I've completed 10 - 15 settings and there are no explanations to what the settings are. Greentify is totally useless if you're not a techie.
Click to expand...
Click to collapse
Well - not my experience; defaults work well on most devices. There are brief in-app explainations for many options with expanded material in FAQs, XDA forum and G+ pages. Best consider an iDevice if you need/want handholding; genius bars everywhere.
I'm seeing sluggish performance after turning my screen back on. My battery usage is already fairly good. I mainly am using Greenify to attempt to free up some memory. There are apps that I rarely use but don't want to uninstall (ie facebook, whatsapp, etc). The way I understand it, the more I hibernate, the more memory I save. However, I read that doing this too much can cause sluggish performance when waking up. How does this work exactly? I have noticed sluggish performance after turning the screen back up. However, what does this have to do with greenify? The apps are still hibernated.
eng3 said:
I'm seeing sluggish performance after turning my screen back on. My battery usage is already fairly good. I mainly am using Greenify to attempt to free up some memory. There are apps that I rarely use but don't want to uninstall (ie facebook, whatsapp, etc). The way I understand it, the more I hibernate, the more memory I save. However, I read that doing this too much can cause sluggish performance when waking up. How does this work exactly? I have noticed sluggish performance after turning the screen back up. However, what does this have to do with greenify? The apps are still hibernated.
Click to expand...
Click to collapse
- Greenify won't directly free up memory
- sluggishness is likely do to multiple apps/services competing for resources when the device wakes; that's why native doze has occational​ maintenance windows
- aggressive doze can contribute to this behavior
- consider a start-up (broadcast receiver) blocker if the social media apps you reference are found running after the device starts; that way they never get loaded into memory in the first place
Can you recommenced a start-up blocker? this means the app will never be launched into memory unless I do it manually?
I thought that "greenify" will "compress" the program in memory causing it to use less. I don't want the app to be completely disabled (otherwise I could just freeze it). For example, if someone sends me a message on facebook (which is very rare), I'd like to know.
My background apps are killed way too often. Is it possible to change that behaviour? Even music apps are killed while I'm playing music.
I have tried several custom roms and kernels but nothing seems to change the settings. Is either able to change RAM management settings?
I have also tried several apps that claim to be able to change RAM management settings without success.
Disabling battery optimisation doesn't help.
I have uninstalled unused apps and disabled autostart (boot completed receiver) for non-essential apps to reduce RAM usage.
When I use a RAM monitor it will show RAM usage at ~75% when apps are killed.
My old phone (Note 4) only had 3 GB ram but could still keep more apps in memory.
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
ChazzMatt said:
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
Click to expand...
Click to collapse
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Telorast said:
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Click to expand...
Click to collapse
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Worth a try. Installed Greenify and added most apps with ignore background-free.
Telorast said:
Worth a try. Installed Greenify and added most apps with ignore background-free.
Click to expand...
Click to collapse
I even hibernate alleged background free apps, just in case.
ChazzMatt said:
Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Click to expand...
Click to collapse
VERY TRUE!
This always infuriated me, not just on phones, PCs too, all the way back to the DOS days. An obsession with running in the background, as if it's particularly clever. :cyclops:
I've also found that turning off battery optimization for apps I don't want killed helps. I've had the same experience with music and podcast apps getting killed in the background and turning off their battery optimization usually fixes it.
There are some simple things to try that do not require any special apk's. One is to look in the apps section of the "Developer options" sub-menu. The default settings work well in most instances. Perhaps you accidently enabled closing of apps when a background limit has been reached or have ticked force closure of apps on exit.
Another place to look is in the "Power saving exclusions" sub-menu in the Battery settings. Music makes some boring forms of exercise less tiresome and provides additional motivation for activities that are challenging but fun (mountain biking). The music should not stop, but it might for default settings. Enabling a power saving exclusion for your music app will keep it running.
ChazzMatt said:
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Click to expand...
Click to collapse
Been using Greenify for a bit now and doesn't seem to help much. It shows a bunch of hibernated apps but multitasking is still nearly impossible.
I had assumed the problem was related to the Mem Free settings rather than actual free memory but no one here has mentioned it. Is that because no one else thinks it's the problem or maybe I have misunderstood what those settings do?
I thought apps were free to use as much memory as they want until certain thresholds on total memory usage were met, then the system would ask or force apps to release memory.
Apps that let you edit those settings usually shows several thresholds where the system gets progressively more aggressive at freeing memory as memory is running out. But they all look hopelessly out of date so maybe it works completely differently today?