Over the past couple days of programming I have looked at and debugged many of the ways that applications go about creating the interfaces which users interact with to get certain jobs done. Looking over code in Power Manager, I found a couple of instances where a contextual activity was leaked and held in code until the application was killed. This memory leak was minor, as the context only was able to point to one object, but the fact that it was arguably continually accessed would lead to large memory consumption in the future. Currently on my testing device, the Power Manager application reports that it uses 4.0 MB of RAM when the interface is not in the foreground. It uses 20 when in a foreground state. This is a large improvement from before where the application used a consistant 36 or so MB all the time. SoftGlow has undergone some code improvements to bring its background state down to a mere 2MB. Home Button is also down to only 3 MB background. Along with memory management improvements, code refactoring has led to perforamnce imprvements in almost all instances. The only time I would expect to not see improvement is when applications are being installed/uninstalled and you are trying to use the overlay. The uninstall process almost locks up all threads because of its massive use of resources when it comes to removing APKs from the system. So sorry if performance suffers if you try to use the overlay while uninstalling that 5GB game you just downloaded.
Still waiting on that GPS update to drop before I begin the process of uploading new packages.
Keep following pyamsoft for updates and announcements about the newest applications!
==
Like what I do?
Send me an email at: pyam.soft@gmail.com
Or find me online at: http://pyamsoft-official.blogspot.com/