[Q] Problem with File transfers to SD Card

Search This thread

Android.Ninja

Senior Member
Jan 3, 2010
912
1,822
Samsung Galaxy S21 Ultra
Is not working for me. Lost ability to see my sd card and all apps where failing. ALOT!! Not exactly sure what the issue was. I had to reflash using odin twice to fix the issue. Also before reflashing it seems I lost the ability to write to either sd card. Internal or external.

Got it to work o the second try. Make sure the format is exactly the same when you add the new line or things go crazy
Sent from my SM-P900 using XDA Premium HD app

Hi, glad to hear you were able to get it fixed. I saw your post in the other forum about the 5 GHz band missing in the UK. If you need any help with anything just give me a holler. :)


Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button. ;)
 

Duly.noted

Senior Member
Dec 5, 2013
506
114
Hi, glad to hear you were able to get it fixed. I saw your post in the other forum about the 5 GHz band missing in the UK. If you need any help with anything just give me a holler. :)


Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button. ;)

Thanks. I've lurked for years LOL. Just got active recently. Really good at setup and implementation usually LOL. You should turn your attention to the Screen mirror issue on rooted devices. Its broken for most.

Sent from my SM-P900 using XDA Premium HD app
 

Buji

Senior Member
Jan 9, 2007
121
11
I have tested and can confirm following these directions to the letter on a rooted device, does solve the problem on the Samsung Galaxy Note Pro 12.2 - SM-P900. I'm now able to write & save to my Sandisk 64gb HS SD card without any problems at all! ;)

I can write to the card now too (same card) but only by manually copying files over. I guess I was expecting to be able to relocate apps to the new card via the regular system menu but so far it seems that just does the same fake 'move to SD' as before.
I've used foldermount in the past with some success, but when I went to try it tonight I got an error message on start I'm not so sure about. My main goal will be to relocate apps to the external card (and comics).
 

Cyper_EX

New member
Mar 20, 2014
1
0
I have tested and can confirm following these directions to the letter on a rooted device, does solve the problem on the Samsung Galaxy Note Pro 12.2 - SM-P900. I'm now able to write & save to my Sandisk 64gb HS SD card without any problems at all! ;)

I can write to the card now too (same card) but only by manually copying files over. I guess I was expecting to be able to relocate apps to the new card via the regular system menu but so far it seems that just does the same fake 'move to SD' as before.
I've used foldermount in the past with some success, but when I went to try it tonight I got an error message on start I'm not so sure about. My main goal will be to relocate apps to the external card (and comics).

Too sad! An external drive that's pretty much useless. Are they scared people might actually use it?
 

AstroDigital

Senior Member
Aug 10, 2010
1,078
152
The thing that annoys me is Google said the locked down the external SD card for security.

What is more secure hardware that you own, or the cloud that is out of your control?
 

aarowm

Member
Jul 30, 2014
7
0
All about sales.

Perhaps they are thinking that you will buy the devices with higher internal capacitys.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    It looks like this is a widespread issue caused by Android 4.4. Since Samsung is running KitKat on these out of the gate, it seems to be a pretty widespread issue. From https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn:

    Now, there is a fix for this, but you need a rooted device.

    Hello All,

    Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).

    **Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **

    1. Using a root-enabled file manager, navigate to /system/etc/permissions
    2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
    3. Add an additional group definition for this permission...
    4. Save the changes to the file.
    5. Restart.

    Attached is a copy of my platform.xml.


    I have tested and can confirm following these directions to the letter on a rooted device, does solve the problem on the Samsung Galaxy Note Pro 12.2 - SM-P900. I'm now able to write & save to my Sandisk 64gb HS SD card without any problems at all! ;)

    Developers don't need no stinkin' signature!
    If I've been able to help you, please hit the "Thanks" button. ;)
    1
    I'm having a similar issue when transferring a 1.3g video file from my notepro storage to the micro sd card.... It starts to transfer the data and then fails.

    It's like the sd card had been removed as when I look at the sd card using a file Explorer it is accessible but all info on the card isn't present. If I unmount the sd card I can't remount it, I have to manually remove the card and put it back in to see any info on the card!!!!


    Definitely a faulty sd card reader or a bug in the firmware!!!

    Sent from my SM-P900 using xda app-developers app
    1
    I have repeated the process a few times but cannot see anything obvious in logcat. There are certainly no errors in the log immediately after the event.

    logcat.zip file attached.

    Maybe a problem with SELinux permissions on the card? I see a lot of errors with Knox/SELinux from that logcat.

    MTP is the media transfer protocol.

    W/ContextImpl( 7677): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1464 android.content.ContextWrapper.sendBroadcast:377 android.content.ContextWrapper.sendBroadcast:377 com.samsung.android.MtpApplication.MtpReceiver.finishSync:606 com.samsung.android.MtpApplication.MtpReceiver$2.handleMessage:485

    W/ContextImpl( 7677): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1464 android.content.ContextWrapper.sendBroadcast:377 android.content.ContextWrapper.sendBroadcast:377 com.samsung.android.MtpApplication.MtpReceiver.finishSync:613 com.samsung.android.MtpApplication.MtpReceiver$2.handleMessage:485

    I/SELinux (13275): Function: selinux_android_load_priority [0], There is no sepolicy file.

    I/SELinux (13275):

    I/SELinux (13275): Function: selinux_android_load_priority [1], There is no sepolicy version file.

    I/SELinux (13275):

    I/SELinux (13275): Function: selinux_android_load_priority , loading version is VE=SEPF_SM-P900_4.4.2_0004

    I/SELinux (13275):

    I/SELinux (13275):

    I/SELinux (13275): selinux_android_seapp_context_reload: seapp_contexts file is loaded from /seapp_contexts

    I/JAM ( 2248): isRunningJackd : stopped...

    W/System.err(13275): java.lang.NoSuchFieldException: SYSTEM_UI_FLAG_REMOVE_NAVIGATION

    E/JAM ( 5470): print sendControlCommand error: Invalid argument

    W/System.err(13275): at java.lang.Class.getField(Class.java:724)

    W/System.err(13275): at com.sec.android.gallery3d.util.GalleryFeature.checkSystemUiVisibility(GalleryFeature.java:1517)

    W/System.err(13275): at com.sec.android.gallery3d.util.GalleryFeature.init(GalleryFeature.java:320)

    W/System.err(13275): at com.sec.android.gallery3d.app.GalleryAppImpl.getDataManager(GalleryAppImpl.java:229)

    W/System.err(13275): at com.sec.android.gallery3d.provider.GalleryProvider.onCreate(GalleryProvider.java:126)

    W/System.err(13275): at android.content.ContentProvider.attachInfo(ContentProvider.java:1591)

    W/System.err(13275): at android.content.ContentProvider.attachInfo(ContentProvider.java:1562)

    W/System.err(13275): at android.app.ActivityThread.installProvider(ActivityThread.java:5029)

    W/System.err(13275): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4624)

    W/System.err(13275): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4538)

    W/System.err(13275): at android.app.ActivityThread.access$1500(ActivityThread.java:164)

    W/System.err(13275): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1318)

    W/System.err(13275): at android.os.Handler.dispatchMessage(Handler.java:102)

    W/System.err(13275): at android.os.Looper.loop(Looper.java:157)

    W/System.err(13275): at android.app.ActivityThread.main(ActivityThread.java:5341)

    W/System.err(13275): at java.lang.reflect.Method.invokeNative(Native Method)

    W/System.err(13275): at java.lang.reflect.Method.invoke(Method.java:515)

    W/System.err(13275): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1259)

    W/System.err(13275): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1075)

    W/System.err(13275): at dalvik.system.NativeStart.main(Native Method)

    E/EnterpriseContainerManager( 2707): ContainerPolicy Service is not yet ready!!!

    As a temporary workaround you should be able to transfer files to the sdcard using an external reader. I should be getting mine soon so I can test this out.
    1
    It looks like this is a widespread issue caused by Android 4.4. Since Samsung is running KitKat on these out of the gate, it seems to be a pretty widespread issue. From https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn:

    KitKat will make your SD Card completely useless: per the Android API specification, apps can no longer write files to your SD card. And Samsung is following it.

    This only applies to dual-storage devices, i.e., devices with a user-writable internal flash storage AND a removable SD card.

    From http://source.android.com/devices/tech/storage/index.html:

    "The WRITE_EXTERNAL_STORAGE permission must only grant write access to the primary external storage on a device. Apps must not be allowed to write to secondary external storage devices, except in their package-specific directories as allowed by synthesized permissions."

    If your device has user-accessible internal flash storage, your SD Card is a "secondary external storage device".

    What this means is that with KitKat, applications will no longer be able create, modify, or remove files and folders on your external SD card. As a for-instance, you can no longer use a file manager to copy files from your computer to the SD card over a network. This ability, which has existed since the beginning of Android, has been taken away.

    The only stated reason for this removal of functionality is that, "Restricting writes in this way ensures the system can clean up files when applications are uninstalled." I do not pretend to understand this logic. Apps are still allowed to write in arbitrary directories on the primary storage (with the appropriate permission), but are denied the same access to external storage.

    Samsung has implemented this feature with their KitKat OTA updates. Note3 users are now complaining that FX File Explorer can no longer write to their external SD cards. There are solutions to this problem for users with root access. Users without root access appear to be screwed.

    I'm not quite certain how Google intends for you to place files on your SD card. Perhaps you have to use proprietary Google apps that contain permissions unavailable to the rest of the developer world. Perhaps you're supposed to put everything on the cloud and pay carrier data fees to get it there. Perhaps you're supposed to use some kind of WIRE to attach your WIRELESS device to your computer and have the computer do that work for you.

    In my opinion this is a horrible misstep by Google and the Android Open Source Project. Functionality has been removed without reason, to the severe detriment of users and developers alike.

    I apologize for not bringing this to everyone's attention when KitKat 4.4 was released, but it was not mentioned in the Android 4.4 changes document: http://developer.android.com/about/versions/android-4.4.html. It's only mentioned in the article on source.android.com. I was only made aware of its existence from user reports as a result of Samsung implementing this change in its KitKat OTA updates.

    Now, there is a fix for this, but you need a rooted device.
    1
    I have tested and can confirm following these directions to the letter on a rooted device, does solve the problem on the Samsung Galaxy Note Pro 12.2 - SM-P900. I'm now able to write & save to my Sandisk 64gb HS SD card without any problems at all! ;)

    Developers don't need no stinkin' signature!
    If I've been able to help you, please hit the "Thanks" button. ;)

    Working for me as well!