(August 22, 2017 at 9:44 am)Atheist_BG Wrote:(August 22, 2017 at 9:39 am)emjay Wrote: Where Android RAM is concerned, I think it's just wise to reboot the phone frequently... that solves most RAM problems for me; ie I tend leave my phone on and charging for weeks at a times, and it degrades performance, but when I reboot I get that performance back. And I think that's because the nature of Android apps in the sense that once they have been opened, they don't really close, they just going into the background... but still occupying RAM. I used to think that they were eventually closed in that situation... after laying dormant for a certain time... but I'm starting to doubt that now... so I think rebooting is perhaps the only way to truly remove them from memory. But that's just my opinion, and it could be wrong.Android apps are closed when you drag their title bar down to the bottom of the screen. If you just tap the X button, they go into background.
That's how it works on my best friend's phone.
What I mean is, even when it's closed, as opposed to 'minimised' as it were, I still think it stays in memory... ie that Android phones aren't that good at 'Garbage Collection' in programming terms (or that some apps themselves don't cleanly shut down (ie have memory leaks) in that regard); ie releasing stuff from memory once there are no more references to it. That's just my theory though to explain why my general experience of Android is that regardless of how long I leave my phone on for, performance seems directly related to the number of apps I've opened since the boot of the phone, regardless of whether they have been properly closed (as opposed to minimised... put into the background) or not.
