I don't know that you were asking me, but as you quoted me, I guess I will reply as best I can...
Thank you for your response and answers.
I totally disagree with "free memory is wasted memory". I understand many Android users think that way too and so called experts are missing the points too. More free memory means in any given OS session user can crunch more data and faster (i.e. loading a web page in a new tab, opening a large pdf file, opening email program, unzipping a large file, streaming data). Many Android apps start itself after a boot complete to launch faster once the user tab on its shortcut. These apps are wasting the memory by holding on to them whether the user use them or not. I'm referring to the apps that have no justification other than giving users a sense that the apps launch quickly.
This ability was essential for early days of Android when CPU power was very limiting but these days doing so will be waste of precious memory capacity. I actually uninstall any apps holding the memory of phone hostage with no good reason.
I extracted the following from your link. "So all is fine and you do not have to be afraid that you run out of memory." This is more of a bad design to me. This is not practical in real world and I have often found my browser being shut down while downloading few files while acrobat reader remained active and the memory wasn't even critically law.
Android limits the number of background processes to four, at least in ICS, and this is Android's way to compact the law memory scenarios. I have 460MB free RAM on my Note after a boot up and I have to constantly shut down apps in Task Manager to avoid getting my critical processes crashed by Android when I still have 200MB+ free memory for instance. I would be so pissed off if I had a phone with 2GB of RAM today and I had to deal with only four processes at a time. Just for the record, I have managed to get 600MB free memory on a CM10.1 based ROM for my Motorola Atrix phone with only my essential apps installed.
I hope things are changed in Android 5 how Android decides which and how resources should be freed. Maybe this idea of mine is more practical. Any background processes that were started by a user and are inactive would remain in memory for a giving period of time and after the expiration period the process would be hibernated to the disk, freeing the memory, for as long as the OS session is running. Just thinking loud...
---------- Post added at 07:15 PM ---------- Previous post was at 07:01 PM ----------
Apologies but 1.2.3.5.6 are unanswerable and hence we dont provide the data in the OP and to 4, i dont know what openPdroid is so i havent tested with it, perhaps it would be better to ask whoever makes openPdroid if their software is compatible with a 4.2.2 aosp rom as thats what this is..
Thank you for your response. I was hoping someone in the carbon team may have tried openpdroid for compatibility, otherwise, I know where to go next.
OpenPDroid is a system level privacy protection layer enabling downloaded and system apps to be configured not to access sensitive data from a device.
---------- Post added at 07:18 PM ---------- Previous post was at 07:15 PM ----------
as to 4: I tried to run pdroid autopatcher over SB, but it finished with errors, so I'd suggest LBE for now
Thank you for sharing this info. Yes, I have been using LBE forever.
