diff options
| author | Conn O'Griofa <connogriofa@gmail.com> | 2013-01-04 19:43:50 -0200 |
|---|---|---|
| committer | Gerrit Code Review <gerrit@review.cyanogenmod.com> | 2013-01-20 20:11:00 -0800 |
| commit | 47461baea89ba2483395082e9271ed9d94d1436b (patch) | |
| tree | 7c02c531b156033edfc6d9c1de75e910df848de2 /telephony/java/com/android/internal | |
| parent | c689d18ed42bff67d6a9ece4de5c3528e5441a45 (diff) | |
| download | frameworks_base-47461baea89ba2483395082e9271ed9d94d1436b.zip frameworks_base-47461baea89ba2483395082e9271ed9d94d1436b.tar.gz frameworks_base-47461baea89ba2483395082e9271ed9d94d1436b.tar.bz2 | |
Allow purging of asset bitmaps
It seems that neither CM9 nor CM10.x includes the actual framework-side
code to facilitate user-controllable bitmap purging. Odd, since the
CyanogenMod Settings app in both CM9/CM10.x includes the option.
Backported from original Gingerbread commit:
http://review.cyanogenmod.org/#/c/3908
Original description:
Allow the system to reclaim more free RAM when needed on 'low' memory devices
(e.g. Droid/Milestone) that are struggling with 2.3. This option enabled
efectively restores the froyo way of forcePurgeable BitmapFactory asset
handling.
Change-Id: I6a3b8a05b7be9c214a8548d6c6d1621e6533a1e0
Diffstat (limited to 'telephony/java/com/android/internal')
0 files changed, 0 insertions, 0 deletions
