https://www.genie9.com/Support/KB/KnowledgeArticle.aspx?KBID=113
https://answers.microsoft.com/en-us...tfs-file/1663db6b-490e-4021-9e36-f7a6976ac0c0
Explain to me what ext4 formatted anything have you gotten to EVER be recognized by a windows PC, or a Mac??? Ever... without installing some 3rd party software driver?
It's common knowledge mate, in fact, very common knowledge
So you provided 2 links about FAT32 and NTFS. Both are rejected as irrelevant, since the file system in question is ext4 (you didn't search for 'straw man', did you?)
No sources provided for your 'vfuse' claims.
Didn't try, or is not in your interest to tell us what happens if you try to copy a file > 4gb on the (according to your claims) non-ext4-effectively-FAT32 file system of Android.
As for your question, a driver acting as intermediary for ext4 PC connections is in no way related to an Android app (eg this thread's camera app) trying to access its file system internally. Which is the problem I originally mention.
And even if we are talking about Android PC connections, your claims of 'effectively FAT32' are disproved by reality.
Fuse is activated on a 'need to emulate' basis, it doesn't limit android's internal ext4 file system to 'effectively FAT32' as you claim.
If the common knowledge you are referring to is the FAT32 limits, well.. good morning.
If common knowledge is your claims about vfuse, where are links to this common knowledge?
---------- Post added at 09:34 PM ---------- Previous post was at 09:10 PM ----------
What is actually disturbing is that the symptoms show that this particular app may be using FUSE to access the file system..
Makes kind of sense since it already had much stricter restrictions (5 minute recording limit) so it wasn't expected to reach a 4gb size limit..