Android 4.4 CAN be used successfully with an External card if certain procedures are followed.
This topic is old. Please do not read it.
Instead, go to:
http://support.crittermap.com/entries/67437220-Using-External-Storage-
=======================================================
Quick Summary:
With Android 4.4, all sorts of bad things start happening if you were using an external storage card in settings. It was a decision Android made to lock apps out of the external storage.
This was not our decision, this was Android.There are some actions needed on your part.
These are the options you have:
- Just use internal storage(the default)
- Use a root fix to let us write to the storage card. Some are discussed below.
- Use a new folder setting, which is an option given as of 5.3.2. Something long like "/storage/extSDcard/Android/Data/com.crittermap.backcountrynavigator.license/files" Please note it means that all of these files will be deleted if you uninstall BCN. Even if you install again right away. If you have valuable data in "/storage/extSdCard/bcnav" you can move it to "storage/extSDcard/Android/Data/com.crittermap.backcountrynavigator.license/files/bcnav". If you want just the waypoints/tracks, you can just transfer the data folder. To do this you will have to use a file explorer either on the device or on the desktop.
We would like you to have access to a folder on external storage that does *not* disappear on uninstall. Unfortunately, Android thinks otherwise.
To sum up, let me be clear. You CAN use the external card on 4.4 but you MUST use the folder name we suggest and you WILL lose the data on uninstall unless you back it up.
History:
I have been made aware of a number of people having problems after a 4.4 update to their Samsung S4 or Galaxy Tab 3. These are people who used an advanced option to change Root storage.
The symptoms vary, but on investigation, it appears that Android and/or Samsung has locked third party apps from writing to the external storage.
While Android probably initiated this change, I do believe Samsung could get around it. Please contact Samsung and indicate your displeasure.
At this time, we have no good workaround to suggest other than using internal storage, which is the default. It is, of course, very tempting to use a removable storage if it has a bunch more space, but in our experience it has had more headaches. Headaches which we cannot prevent.
Long term, when buying an Android device, get one with large internal storage, rather than counting on buying a card for a different storage area. Unfortunately, it is all too common that Android believes that you do not have the interest in using storage that you bought with your own money for whatever you want.
The only rumored fix, which requires you to have root access is to 'add the "media_rw" item to the write external storage permission on "/system/etc/permissions/platform. xml"'. Not accessible to most users. Please note that this is not a fix that we have tested ourselves. Do not root your device just to do this, because you might find that it doesn't work after all.
We have looked into another kind of loophole, but found that our files could be easily deleted in their entirety when reinstalling the application - not a desirable outcome.
I have gotten this link from several of you that explains the root fix. We don't know of any non root fix.
Please Note:
You may find articles or claims to the effect that BackCountry Navigator is just not compatible with Android Kitkat. In fact, you may hear that from Google Play Support. That is absolutely not true. If we could fix it as easily as checking a few boxes and rebuilding that would be great, but it is not so.
Possible workaround that is not reccommended:
It is possible that we could write to "/storage/extSDcard/Android/Data/com.crittermap.backcountrynavigator.license". However, it has some dangerous implications. The files cannot be seen outside the app. All of them are deleted when the application is uninstalled. Since many of you uninstall and reinstall often, this has permanent effects. Even you are just moving from DEMO to paid, everything would be gone.
It is not know whether you can browse to this location in storage root settings. We do not have hardware to test this yet.
Still recommended actions are:
- Use the root fix above.
- Use Internal storage.
- Complain to Samsung.
To use Internal Storage:
- If you haven't set it to it external storage before (via Settings->Storage Root), then do nothing. The default will work.
- If the storage root setting points to "/storage/extSdCard", it probably needs to point to "/storage/sdcard" (please confirm these locations as I've only heard them second hand). You can reinstall to restore that setting.
- If you have valuable data in "/storage/extSdCard/bcnav" you can move it to "/storage/sdcard/bcnav". If you want just the waypoints/tracks, you can just transfer the data folder. To do this you will have to use a file explorer either on the device or on the desktop.
Data Volatility
I am adding to this article to get some feedback.
I have noticed that many apps are using app specific space on external storage. Big drawback is, if you happen to uninstall and reinstall the app, everything is gone. Maps. Waypoints. Tracks. Everything.
You can get around that by backing up the directory and/or never uninstalling the app. However, our statistics show that people uninstall and reinstall often, and we don't know how often.
In version 5.3.0, we give you this option, with a warning that we strongly recommend against it. Even with that, we expect that we will hear from angry people later.
Comments
78 comments
I've now investigated a bit further.
I've moved the files back from "storage/extSDcard/Android/Data/com.crittermap.backcountrynavigator.license/files/bcnav" to ExtSDcard and app operations have reverted to normal so I'm convinced that the problems with app storage (noted in my previous posts) were caused by the substantially map data in "storage/extSDcard/Android/Data/com.crittermap.backcountrynavigator.license/files/bcnav".
Of course moving data back to ExtSDcard caused BNC to be unable to read & write map, track and way points normally.
I also run Oruxmaps on the same phone (galaxy S4 running 4.4.2) so I investigated this and found that this app allowed map files to be stored on ExtSDcard while tracks/routes/waypoints could be stored on SDcard0. As a result Oruxmaps continued to work normally except that maps cannot be downloaded directly to ExtSDcard. Is possible for BCN to store track/route/waymark data on SDcard0 and maps on ExtSDcard? This could result in BCN operating normally while allowing the use of large map files on ExtSDcard.
I realise that care would be needed to load new map files but its not too difficult
a) Switch destination for downloaded map files to SDcard0
b) Download the desired maps files.
c) Use a File Manager to move the map files from SDcard0 to ExtSDcard.
d) Switch destination for map files back to ExtSDcard.
Would this work?
Could someone knowledgeable please post how to set my Samsung Galaxy Note 3 storage so I can get on with my horseback riding in the back country? Thanks.
I have a Galaxy Note 8 N5100 and since my 4.4.2 OS update BCN has ceased to function (not working) and all my BCN files are installed on my internal default device storage so should be OK there but the app is still not working after 36hrs.
DSCF0300.JPG
IT WORKED.
I'm quoting a link that was defined by the poster of this forum:
" . . . this link from several of you that explains the root fix. We don't know of any non root fix.
http://www.androidheadlines.com/2014/02/galaxy-s4-note-3-kitkat-sd-card-update-issue-youre-not-alone-root-fix-inside.html
(top of this forum; first post of this forum)".
I added notes here below of what I had to do. I did not exactly record what I was doing over this time period since I did not anticipate teaching others how to overcome googles decision on helping rookies not lose their external data... or wt-ever it was that caused that decision.
If you lack root and have Samsung s3 then this is how I rooted my phone
I managed to use a "one click" rooting program called "towelroot" version 3 by geohot:
I had to use various internet browsers to actually get the file to download,
for some browsers claimed the site unsecure or similar. . . just google "towelroot", I am sure you'll find it.
I had to tell my anti virus to ignore the app...
Had to re-launch the app twice due to anti virus program requesting permissions, and it updated from v1 to v3...
But the fun does not end there :D
Within the instructions of the link I re posted...
there is a file you edit called "platform.xml" ...
that file's permissions have to be altered ...
and I'd recommend undoing the permission change once you have completed the change...
so undo the permission change right before the reboot-part of the instructions (instructions in the link)...
I used the root explorer called " solid explorer " along with its file editor called " SE TextEditor "...
The permissions were
Owner rw
Group r
Others r
I added w to everyone
Owner rw
Group rw
Others rw
and took those 2 w back before reboot....
Great App
Galaxy S4 /Sprint - Android 4.4.2
Calls, calendar and a few apps for me for me so, I never uninstall BCNAV. Long-name storage option works well. Track Stats got lost.
Quick question:
Could you list what Folders are created by bcnav and differentiate which stay in bcnav (on device) and which Folders can go on extSdCard?
Yes a folder tree, locations and purpose would be helpful. Many of us such as myself are not that computer literate. I love the program and it works well, just trying to understand it better.
Galaxy s3 and note 2014 edition.. Also, my old phone is a Samsung Charge with spare batteries and I only use it for BC Navigator, camera and wifi internet browsing as cell connection has been disabled.
Sometime ago I asked
"I run Oruxmaps (as well as BNC) on a galaxy S4 running 4.4.2, so I investigated this and found that this app allowed map files to be stored on ExtSDcard while tracks/routes/waypoints are written to and stored on SDcard0. As a result Oruxmaps continued to work normally after Kitkat except that maps cannot be downloaded directly to ExtSDcard. Is possible for BCN to store track/route/waymark data on SDcard0 and maps on ExtSDcard? This could result in BCN operating normally while allowing the use of large map files on ExtSDcard
Would this work?'.'
I just installed this app on my Tab4, I was able to move BCN to the sd card, with no issues, whether or not I can save the maps to the SD card also, I do not know at this time, haven't tried yet
I had no issues moving this app to the SD card in my Galaxy Tab4-7.
Screenshot_2014-12-27-20-03-53.png
I have a Samsung Galaxy S4. I first noticed a problem with this SD card lock when I used my "My Phone Explorer" program to sync my phone to my PC. I got a message at the end of the sync, when the program tried to execute my setting to delete photos from my phone after transferring them to my PC. The message simple explained that due to the ANDROID security restriction, it could not delete files from the SD card. As I only have 16GB Internal storage on the phone with about 3GB currently available, it is ludicrous to expect me to use Internal storage for pictures and videos. I am left to manually delete imaging files from my phone. I have explored Samsung for a similar program that handles syning automaticly and have been thouroughly disappointed. SideSync is JUNK! Kies is limited. Is there anything I've missed?
I know this is not a recent post but I suspect you might be able to answer my question. My Galaxy Tab 3 thinks there is no SD card mounted but that is not true. Since it doesn't seem to recognize it anymore (it used to) the only Settings option I can select is "mount an SD card". Is there a way to remove the current one without going through those setting options? I am not very tech savvy so I apologize if this is a silly question with an easy answer. Thanks for anything anyone can suggest.
I just purchased a BLU 5.0 C HD 4.4.2 android and it has the same protection problems as discussed above. We were able to root the phone using KingoRoot which uses the developer access and USB debugging function. I was then able to use NextAPP SD Fix (play store) to fix the permissions. It went smoothly.
Seems like the Developers of BDN just got the short end of the stick from Samsung. I loved the concept of this program, it is really cool with multiple maps in memory - but the hardware let's it down.
My Samsung Galaxy Note 10.1 tablet screen cannot deal with sunlight - so it is darn near worthless for my backcountry motorcycle trips. Now my Samsung S-4 phone's screen is better in sunlight, but I have the above referenced storage issue.
I guess I will have to stick with my Garmin 64 gps.......really wanted the tablet to work for me in the field. You get a lot more real estate on the tablet display versus phone or handheld Garmin.
Sally, you need to check with Samsung support. That isn't an app issue.
Dave, will you please reread what we have as the basic instructions above.
Yes, Android (not just Samsung) has messed with the SD Card. But we are NOT saying you can't use it and have to give up and go to Garmin.
To sum up, let me be clear. You CAN use the external card on 4.4 but you MUST use the folder name we suggest and you WILL lose the data on uninstall unless you back it up.
Article is closed for comments.