[Galaxy Note 4 Accessories] Purah:
thanks for the replies folks.

another attempt i had now was to connect an ethernet cable to the note, preferable a connection through the dock station. looks like it wont work since the samsung touchwiz for note 4 has not the appropriate kernel for it.

currently the note 4 works with the custom smart dock from leicke. i tested the hdmi slot, an usb stick with 4 gb with ntfs (had few problems) aswell as with exfat (ran smoothly with android) and the usb ports seem to work flawlessly because the cabled mouse and keyboard from my computer were recognized in an instant. i havent tried the audio output so far but since its a custom smart dock designed for the note 4 i expect it to work, not like with the smart dock from samsung.

now im again trying the hdd with the dock station. first time i did it with 2 partitions and it was wrong as i recall it now. i thought at least the first partition on the hdd will be recognized but no chance. only the hdd itself was recognized but no real connection was established. now i try it with ntfs, only 1 partition and lets see what happens now. after that i will try it with exfat and see if i can use 8 tb with exfat file system.

edit:

i think the adapter for the hdd is the problem. the ntfs usb stick worked under total commander but not the hdd. here the pastebin link and a snapshot from the log i found recently of the ntfs mount plugin.

http://pastebin.com/51eKW1Xx

08-06 02:10:59.038 13256 13278 D UsbDeviceConnectionJNI: close
08-06 02:10:59.038 13256 13278 D ParagonUMSLibraryNative: CheckDeviceType( UMSDevice 0xae1fb2fc, iClass FF, iSubClass FF, iProto FF )
08-06 02:10:59.038 13256 13278 D ParagonUMSLibraryNative: CheckDeviceType( UMSDevice 0xae1fb2fc, iClass FF, iSubClass FF, iProto FF )
08-06 02:10:59.038 13256 13278 D ParagonUMSLibraryNative: CheckDeviceType( UMSDevice 0xae1fb2fc, iClass FF, iSubClass FF, iProto FF )
08-06 02:10:59.038 13256 13278 D ParagonUMSLibraryNative: CheckDeviceType( UMSDevice 0xae1fb2fc, iClass FF, iSubClass FF, iProto FF )
08-06 02:10:59.038 13256 13278 D ParagonUMSLibraryNative: CheckDeviceType( UMSDevice 0xae1fb2fc, iClass FF, iSubClass FF, iProto FF )
08-06 02:10:59.038 13256 13278 D ParagonUMSLibraryNative: CheckDeviceType( UMSDevice 0xae1fb2fc, iClass FF, iSubClass FE, iProto FF )
08-06 02:10:59.058 13256 13278 D ParagonTCPlugin: [InitUSBManager:doInBackground:153]: Error 0xb: SCSI command failed
08-06 02:10:59.058 13256 13278 D ParagonUMSLibraryNative: CheckDeviceType( UMSDevice 0xae1fb2fc, iClass 8, iSubClass 6, iProto 50 )
08-06 02:10:59.068 13256 13278 D ParagonUMSLibraryNative: GetLunCount -> 1
08-06 02:10:59.128 13256 13256 D ViewRootImpl: #1 mView = com.android.internal.policy.PhoneWindow$DecorView{c46c038 V.E...... R.....I. 0,0-0,0}
08-06 02:10:59.228 13256 13256 D ViewRootImpl: MSG_RESIZED_REPORT: ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
08-06 02:11:00.968 13256 13256 D ViewRootImpl: ViewPostImeInputStage processPointer 0
08-06 02:11:00.998 13256 13256 D ViewRootImpl: ViewPostImeInputStage processPointer 1
08-06 02:11:01.018 13256 13256 D Mail_reporter: beta-test@paragon-software.com Paragon UMS plugin issue report. Please, specify the following data.
08-06 02:11:01.018 13256 13256 D Mail_reporter:
08-06 02:11:01.018 13256 13256 D Mail_reporter: 1) Storage device model and capacity:
08-06 02:11:01.018 13256 13256 D Mail_reporter: <enter answer here>
08-06 02:11:01.018 13256 13256 D Mail_reporter: 2) How was the storage formatted (partitioned):
08-06 02:11:01.018 13256 13256 D Mail_reporter: <enter answer here>
08-06 02:11:01.018 13256 13256 D Mail_reporter: 3) Have you used additional power supply (yes/no):
08-06 02:11:01.018 13256 13256 D Mail_reporter: <enter answer here>
08-06 02:11:01.018 13256 13256 D Mail_reporter: 4) What exactly appeared on the screen after connecting the device:
08-06 02:11:01.018 13256 13256 D Mail_reporter: <enter answer here>
08-06 02:11:01.018 13256 13256 D Mail_reporter: 5) Steps for reproducing the issue:
08-06 02:11:01.018 13256 13256 D Mail_reporter: 1. <describe step 1>
08-06 02:11:01.018 13256 13256 D Mail_reporter: 2. <describe step 2>
08-06 02:11:01.018 13256 13256 D Mail_reporter: …
08-06 02:11:01.018 13256 13256 D Mail_reporter:
08-06 02:11:01.018 13256 13256 D Mail_reporter: Please, note that the detailed bug report greatly increases possibility to fix reported issue in the next release.
08-06 02:11:01.018 13256 13256 D Mail_reporter: Thank you for assistance!
08-06 02:11:01.018 13256 13256 D Mail_reporter:

edit 2:

the adapter works now like a charm, i used the power cable for the 2,5" hdd instead the one for the 3,5" hdd. :D

beside my failure, using exfat with a 8 tb hdd wasnt quite the expierence i expected. android shows me that the hdd is broken and should be restored, thus creating a 1,3 or 1,7 tb partition (dont know which one of it) and leaving the rest of the space unused at all.

i gave paragon ntfs hfs a new try and it worked like a charm too.

my problem is now that i cant mount the partition to a folder which has write permission and is visible under all apps, not only es file explorer or total commander.

i tried to mount the system as read/write but it didnt worked.

how is it possible to give an app write permission to protected folders?

the standard hdd mount path is "root/data/media/0/ParagonNTFS" but i cant write on the folder with my app and the paragon app itself sees not much folders to create an directory which is both visible and writable.

the next problem is that i have to copy content from the hdd before i can use it or i need to save it first to the sd card before i can move it finally to the hdd.

is this caused by missing read and/or write permission on the mounted path?

or is this in general a problem?