Thanks Jessica for detailing your workflow and use case. I can assure you that it is supported. I tried to reproduce your issue on a Galaxy Note II with the specs below, but the app worked as expected. Here is the code I used:
public boolean onOptionsItemSelected(MenuItem item) {
// handle item selection
switch (item.getItemId()) {
case R.id.World_Street_Map:
mMapView.removeAll();
mMapView.addLayer(basemapStreet);
return true;
case R.id.World_Topo:
mMapView.removeAll();
mMapView.addLayer(basemapTopo);
return true;
case R.id.NatGeo:
mMapView.removeAll();
mMapView.addLayer(basemapNatGeo);
return true;
case R.id.Ocean_Basemap:
mMapView.removeAll();
mMapView.addLayer(basemapOcean);
default:
return super.onOptionsItemSelected(item);
}
}
Device specs that I tested on:Hardware: Verizon Samsung Galaxy Note IIModel number: SCH-I605Android version: 4.1.1Build number: JRO03C.I605VRALL4Kernel version: 3.0.31-414933 se.infra@SEP-79 #1 SMP PREEMPT Fri Dec 28 21:21:38 KST 2012The Android version is different and I suspect the kernel version will be as well. The carrier is Verizon, what carrier are you using as there are some differences in carrier models. This may have something to do with the issue as the fix may be in the device. Is it possible for you to update to Android 4.1.2 and see if that resolves it? Concerning your workflow: Have you created the option to manually add layers to the map with a user input URL? That should work and I am interested in your experience. We have a similar workflow in our ArcGIS App whereby users can input a URL to make a GIS Connection. The ArcGIS App is wholly built with the SDK.