Writing to/Modifying data on external USB drive with Vega

[LeonM]

G'day ladies and gents,

Sorry if I missed out the subject in other threads, search did not yield anything that could console me -

I am toying with a recently bought Vega Standard box, running 1.5Finless ROM (Thanks for that, Bob!).
I've a 2TB Seagate USB HDD connected to it to manage downloads/docs I work with from home and I was appalled to discover that with KitKat I can't even create a folder on the external disk, not to mention download something onto it. Given the smallish internal storage space i don't need to emphasize how big the impact on the overall functionality of the box is.

Digging in on the subject on various resources such as xda and some blogs, I've seen the solution proposing a change of permissions in platform.xml that would allow writing to external storage, however after applying the proposed fix - I still didn't get it to work. Apparently the fix is sensitive on the type/model of the device and is not generic to any android run system.

Did any of you manage to solve the issue for the Vega? If so, how? Can it be resolved on a ROM ? If not, what's your take on this newly induced handicap by Google on this sort of products?

Thanks in advance!

[no_spam_for_me]

If you use NTFS
=> http://www.freaktab.com/showthread.p...l=1#post175781

[LeonM]

Thanks for the quick reply, I was already reading on the subject (after my initial post) and will get on it as soon as I'm home.
I am still confused though, people are managing to write on their external disks despite the change introduced with KitKat?

[no_spam_for_me]

At which device, with which kernel (maybe custom kernel with build in NTFS support)...???

[LeonM]

Again, sorry for not defining the issue well enough:

I've a Tronsmart Vega S89 Standard, on which I haven't modified anything except flushing it with 1.5 Finless ROM. I don't remember the kernel by heart, I'll make sure to update as soon as i am within reach of the box.
To the Vega, I have an external HDD connected, Seagate 2TB.
It's visible (as /sdcard1) and accessible for reading only without any additional actions required for me, with the only limitation - i can't write to it. Changing permissions with accordance to what is called "KitKat SD fix" didn't help.

As I understand, if I use Paragon NTFS i should be able to write to it?

[SuMo]

As I understand, if I use Paragon NTFS i should be able to write to it?

Thats right. I had success writing to my ntfs hdd with paragon ntfs mounter. Before that there was no writing possible.

[no_spam_for_me]

I think 'SDFix: KitKat Writable MicroSD' is something totally different...
If you use NTFS at the HDD, paragon fix your problem, because at the moment for this device there exist NO kernel which supports writing to NTFS at a HDD...

[LeonM]

I understand, or actually starting to understand.
What seems peculiar to me, is that if NTFS is not supported - how come i can see the files, and load them from the NTFS disk? Seems strange to me, but then again my understanding of these issues is quite limited, if not to say non-existing. That's the reason i suspected that the actual cause of my problem is permissions problems with KitKat, and not the NTFS thing, so i acted on it instead of trying Paragon.

Just want to say thanks to whoever replied so far, at least i am starting to get a clue.

[no_spam_for_me]

I understand, or actually starting to understand.
What seems peculiar to me, is that if NTFS is not supported - how come i can see the files, and load them from the NTFS disk? Seems strange to me, ...

The problem is, and please don't ask me why (maybe because of license), that normaly the kernel handles the filesystems (like fat, fat32, ntfs ...) but at the moment the stock kernel only able to read ntfs but not able to write... paragon fix this because instead to use the kernel to handle it, it handle it by it self...

[LeonM]

Well, thanks for sorting this out for me - Paragon NTFS did the trick.
Much obliged for the help, and sorry for 'recycling' this issue.