You are hereForums / Android Software / Android Development / No maps visible in AT&T Samsung Captivate
No maps visible in AT&T Samsung Captivate
I cannot get a map visible in BackCountryNavigator. All I see are the tiles with Xs in circles. The map background changes from a checkmark looking graphic to the Xs no matter what map I select.
Gps, wireless, cell are all working with good strength in other apps. Other Google map apps work fine.
I have uninstalled & reinstalled to no avail. I have also tried killing all other apps & services just in case there was a conflict. I have also modified Android settings for GPS for Samsung Captivate poor gps (modifications worked great). BackCountryNavigatorn still shows no maps.
Any ideas?
Tags
Share This Page
Share |
If internet connectivity is strong, I would check the storage card. If it is in there, but mounted as USB storage for the computer, then it is invisible to us.
Some phones will mount automatically when the USB cable is connected.
Where is the map centered? If you don't know, use the Find a Place menu option.
The Captivate treats internal storage as SD card slot. The internal storage is used for normal storage but isn't reported to the Android OS as normal sd. Not sure if sticking a card in the external slot will help...
Lots of other apps are having issues with this as well
Everything I've read suggests that the internal SD Card is what BackCountry Navigator would find and try to use.
I am anxious to get to the bottom of this. Can you check your internal SD volume and see if it has a directory called /sdcard/bcnav, with subdirectories under that? If not, it is having trouble writing to that.
Alternately, could you install Log Collector (free app by xtraLogic) and then send me a log after running BackCountry Navigator. There should be all kinds of errors in it if no maps are showing.
IN case this helps, the original poster found that the internal sd card had 13 gig and *all* of it was being taken up by some cache files, and zero bytes were free.
Neither he nor I ever found out the reason for that, or what app was using all that up.