Competitor Heap Limit
2016-06-08 14:22
489 查看
Google Suggested minimal Java heap limit setting from chapter 3.7 of Android Compatibility Definition Document as below table. Although some devices might set higher heap limit than Google suggested minimal value, app should meet the Google suggested minimal Java heap limit to make sure app can execute without problem on all competitor devices. In other words, app that consumes larger memory usage than Google suggested minimal Java heap limit may run without problem on A device, but may meet OutOfMemoryError on B device.
Please be noted Google doesn’t give suggested Large Heap Limit setting in CDD. Google only defines default heap limits for each Screen size/DPI. It’s not suggested to set largeHeap=ture since it has risk to run on competitor devices with variant large heap limits. Thus, app still has chance to meet OutOfMemoryError even with largeHeap set as true on some devices.
Google also suggests “not” to set largeHeap as below
HMS apps should meet defined memory quota for running on competitor devices without problem, since the memory quota is defined according to app’s characteristics and makes sure the usage won’t cause memory problem on competitor devices.
Please be noted Google doesn’t give suggested Large Heap Limit setting in CDD. Google only defines default heap limits for each Screen size/DPI. It’s not suggested to set largeHeap=ture since it has risk to run on competitor devices with variant large heap limits. Thus, app still has chance to meet OutOfMemoryError even with largeHeap set as true on some devices.
Google also suggests “not” to set largeHeap as below
Most apps should not need this and should instead focus on reducing their overall memory usage for improved performance. Enabling this also does not guarantee a fixed increase in available memory, because some devices are constrained by their total available memory.
HMS apps should meet defined memory quota for running on competitor devices without problem, since the memory quota is defined according to app’s characteristics and makes sure the usage won’t cause memory problem on competitor devices.
Screen Size | Screen Density | Application Memory |
---|---|---|
small / normal / large | large ldpi / mdpi | 16MB |
small / normal / large | tvdpi / hdpi | 32MB |
small / normal / large | large xhdpi | 64MB |
small / normal / large | large 400dpi | 96MB |
small / normal / large | xxdpi | 128MB |
xlarge | mdpi | 32MB |
xlarge | tvdpi / hdpi | 64MB |
xlarge | xhdpi | 128MB |
xlarge | 400dpi | 192MB |
xlarge | xxhdpi | 256MB |
相关文章推荐
- 使用C++实现JNI接口需要注意的事项
- Android IPC进程间通讯机制
- Android Manifest 用法
- [转载]Activity中ConfigChanges属性的用法
- Android之获取手机上的图片和视频缩略图thumbnails
- Android之使用Http协议实现文件上传功能
- Android学习笔记(二九):嵌入浏览器
- android string.xml文件中的整型和string型代替
- i-jetty环境搭配与编译
- android之定时器AlarmManager
- android wifi 无线调试
- Android Native 绘图方法
- Android java 与 javascript互访(相互调用)的方法例子
- android 代码实现控件之间的间距
- android FragmentPagerAdapter的“标准”配置
- Android"解决"onTouch和onClick的冲突问题
- android:installLocation简析
- android searchView的关闭事件
- SourceProvider.getJniDirectories