Why such error can occure ?
It's my app that uses OSMDROID map lib, that uses lots of memory, as i can imagine.
Manifest now is so:
Error occurs only under Android 4.0.3 and 4.0.4.
Can it be caught ? Or avoided by manifest settings?
And second error set is about OutOfMemory that occurs in various subs, any Android versions, and even on 2GB device (Sony). Can it be caught ?
It's my app that uses OSMDROID map lib, that uses lots of memory, as i can imagine.
Manifest now is so:
B4X:
AddManifestText(
<uses-sdk android:minSdkVersion="11" android:targetSdkVersion="14"/>
<supports-screens android:largeScreens="true"
android:smallScreens="false"
android:normalScreens="true"
android:xlargeScreens="true"
android:resizeable="true"
android:requiresSmallestWidthDp="480"
android:anyDensity="true"/>)
AddManifestText(<uses-feature android:name="android.hardware.location.gps" android:required="false" />)
AddManifestText(<uses-feature android:name="android.hardware.location" android:required="false"/>)
AddManifestText(<uses-feature android:name="android.hardware.location.network" android:required="false"/>)
AddApplicationText(<activity android:name="de.amberhome.objects.preferenceactivity"/>)
SetManifestAttribute("android:installLocation", "auto")
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
SetApplicationAttribute(android:hardwareAccelerated, "false")
SetApplicationAttribute(android:isGame, "true")
SetApplicationAttribute(android:largeHeap, "true")
Error occurs only under Android 4.0.3 and 4.0.4.
Can it be caught ? Or avoided by manifest settings?
And second error set is about OutOfMemory that occurs in various subs, any Android versions, and even on 2GB device (Sony). Can it be caught ?
Last edited: