Related
I have tried my best to make this work but I cant get it going. I have a sandisk 64gb microsd w/ a USB OTG adapter. When I plug it in and use stickmount i can read the device but no write. This is a problem because I want to carry roms on the card to play in retroarch and it needs to be able to write back to the card. I mounts it fine w/o the exfat binaries but even with i dont have write access. I tried total commander with the usb plugin which give me write access but I cannot find where it mounts the usb for other apps to access. As far as i can tell you can only access within total commander. this would be fine for launching videos and such but it wont launch my roms this way. Is there a happy solution somewhere in the middle?
If you can't get writable storage, you'll need support at a kernel level
Sent from my Nexus 5 using Tapatalk
^+1
Sent from my Nexus 5 using XDA Premium 4 mobile app
What file manager are you using?
Sent from my Nexus 5 using Tapatalk
Im using ES file explorer. strange thing is that even without any of the exfat binaries it reads just fine through stickmount but cant write. Last night I formatted to NTFS and tried USB Go Helper which is supposed to support NTFS read/write. USB Go Helper gives me an error code 9 when I try to mount it but I can read the stick just fine still no write.
As far as I know there's only 1 kernel that supports r/w but I wanted to go w/ the franco kernel but it doesnt support it.
Munkee915 said:
Im using ES file explorer. strange thing is that even without any of the exfat binaries it reads just fine through stickmount but cant write. Last night I formatted to NTFS and tried USB Go Helper which is supposed to support NTFS read/write. USB Go Helper gives me an error code 9 when I try to mount it but I can read the stick just fine still no write.
As far as I know there's only 1 kernel that supports r/w but I wanted to go w/ the franco kernel but it doesnt support it.
Click to expand...
Click to collapse
Is there a particular reason you don't want to use FAT32? Last I checked, I was able to read and write to my SanDisk 64GB MicroSD card after formatting it to FAT32.
4GB+ files is usually the reason
Sent from my Nexus 5 using Tapatalk
Mostly because of the 4gb file size limit.
rootSU said:
4GB+ files is usually the reason
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah. I have Blu-ray MKV files (average size 9GB) since all I really use it for is video consumption. I just use mkvmerge to split them up into 4GB files. Works beautifully. However, I can see this limitation being a deal breaker for some.
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
Munkee915 said:
Mostly because of the 4gb file size limit.
Click to expand...
Click to collapse
Pardon my ignorance, but are the retroarch rom files that big? I've only used a few emulators (the ones by yongzh from back in the day), but I remember the files being pretty small.
charesa39 said:
Yeah. I have Blu-ray MKV files (average size 9GB) since all I really use it for is video consumption. I just use mkvmerge to split them up into 4GB files. Works beautifully. However, I can see this limitation being a deal breaker for some.
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
Pardon my ignorance, but are the retroarch rom files that big? I've only used a few emulators (the ones by yongzh from back in the day), but I remember the files being pretty small.
Click to expand...
Click to collapse
Yep, no doubt conversion can compress massively. Most average length 1080 movies can get to 2GB without loss of quality but it can be a chore and time consuming.
Not an issue for me. As a cross-platform user, I have no choice but to use FAT32
Sent from my Nexus 5 using Tapatalk
charesa39 said:
Yeah. I have Blu-ray MKV files (average size 9GB) since all I really use it for is video consumption. I just use mkvmerge to split them up into 4GB files. Works beautifully. However, I can see this limitation being a deal breaker for some.
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
Pardon my ignorance, but are the retroarch rom files that big? I've only used a few emulators (the ones by yongzh from back in the day), but I remember the files being pretty small.
Click to expand...
Click to collapse
the roms are not that big. biggest would be some PSX roms around 700mb. But its a 64gb card so I'll also be storing some movies and other things on there. I guess conversion/splitting is an option but I was kind of hoping for a solution that 'just works'.
I think perhaps you should look at elementalx kernel. I know you want to stay with franco but its worth testing all solutions
Sent from my Nexus 5 using Tapatalk
rootSU said:
I think perhaps you should look at elementalx kernel. I know you want to stay with franco but its worth testing all solutions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I loaded up the elementx kernal but still having the same issue. I can mount and read the drive fine, but cant write to it. Tried enabling exfat support and tested NTFS and exfat but neither work. Tested this in ES and in Total Commander.
Munkee915 said:
I loaded up the elementx kernal but still having the same issue. I can mount and read the drive fine, but cant write to it. Tried enabling exfat support and tested NTFS and exfat but neither work. Tested this in ES and in Total Commander.
Click to expand...
Click to collapse
Try accessing it via /mnt/media_ rw
Sent from my Nexus 5 using Tapatalk
Munkee915 said:
I have tried my best to make this work but I cant get it going. I have a sandisk 64gb microsd w/ a USB OTG adapter. When I plug it in and use stickmount i can read the device but no write. This is a problem because I want to carry roms on the card to play in retroarch and it needs to be able to write back to the card. I mounts it fine w/o the exfat binaries but even with i dont have write access. I tried total commander with the usb plugin which give me write access but I cannot find where it mounts the usb for other apps to access. As far as i can tell you can only access within total commander. this would be fine for launching videos and such but it wont launch my roms this way. Is there a happy solution somewhere in the middle?
Click to expand...
Click to collapse
Try the following : open up terminal, type su, hit enter, type set enforce 0, hit enter, now see if you can also write on you NTFS-FORMATTED card.
rootSU said:
Try accessing it via /mnt/media_ rw
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Going this rout I see a USB and USB disk dir but both are empty. Not sure which one to use or if I should be able to see
ObiDanKenobi said:
Try the following : open up terminal, type su, hit enter, type set enforce 0, hit enter, now see if you can also write on you NTFS-FORMATTED card.
Click to expand...
Click to collapse
Tried this but no change that I can see.
One thing I noticed is that I am able to delete and rename files on the drive. Seems that I just cant create new files/folders on there.
ObiDanKenobi said:
Try the following : open up terminal, type su, hit enter, type set enforce 0, hit enter, now see if you can also write on you NTFS-FORMATTED card.
Click to expand...
Click to collapse
So as a follow up, it looks like your command was a bit off. it should be setenforce 0. This worked for me and I can now write to NTFS and exfat! Thanks for the help.
Munkee915 said:
So as a follow up, it looks like your command was a bit off. it should be setenforce 0. This worked for me and I can now write to NTFS and exfat! Thanks for the help.
Click to expand...
Click to collapse
You can also use SELinuxModeChanger app to do this. Kitkat runs with mode set to Enforcing. I use the app to set Permissive (same as your command above) when I need to write to my OTG 64GB exFAT Sandisk, but then switch it back to Enforcing when I'm finished so nothing else is compromised.
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
I've been getting this error whenever I try to copy anything onto a flash drive:
"EACCES (Permission denied)"
It used to work just fine before, so I don't know why it isn't working now.
The flash drive is EXFAT formatted. Phone is rooted, running ElementalX with EXFAT support ticked and Stickmount Pro. Reading any file still works.
Any ideas as to what happened?
keepcalmrollon said:
I've been getting this error whenever I try to copy anything onto a flash drive:
"EACCES (Permission denied)"
It used to work just fine before, so I don't know why it isn't working now.
The flash drive is EXFAT formatted. Phone is rooted, running ElementalX with EXFAT support ticked and Stickmount Pro. Reading any file still works.
Any ideas as to what happened?
Click to expand...
Click to collapse
What location are you browsing to to get to the flash drive? Is it the latest elemental?
rootSU said:
What location are you browsing to to get to the flash drive? Is it the latest elemental?
Click to expand...
Click to collapse
sdcard/usbstorage/sda1
Yes, I'm using Elemental 0.40
Does stickmount support exfat?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Does stickmount support exfat?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I believe so, as long as the kernel does as well. I know I've been able to write to this drive before, just haven't done so in a while.
no idea.
keepcalmrollon said:
I believe so, as long as the kernel does as well. I know I've been able to write to this drive before, just haven't done so in a while.
Click to expand...
Click to collapse
Anyone any ideas? I am having the same problem, exact same scenario using rooted stock on nexus 5. :crying:
My solution to NEXUS 5 can write to OTG USB pendrive
Ok, that's that I did, and it worked ( 4 or moure hours testing various things)
I used a Corsair Voyager GO 64 gb with NTFS filesystem.
My Nexus 5 is rooted.
I installed Chainfire "StickMount". So we can mount out USB pendrive to /sdcard/ubsStorage/sda1 No need to be PRO app.
I installed Paragon "paragon NTFS&HFS". Open it, and will ask to fix SELinux policies to Permisive. So Root Explorer can see now /Data/Media/ClockWorkmod/backup
I installed Jrummy Apps inc. "Root Explorer". I will copy, for example /Data/Media/ClockWorkmod/backup to /sdcard/ubsStorage/sda1 whithout any problems.
Don't forget to unmount USB drive before disconnecting it, go to StickMount and choose unmount
ES FILE EXPLORER WILL SAY "No space" "Error" or similar
Worked for me!
I'm happy with my investigation. I used Root Explorer in the past, and now it's useful again.
Sorry about my english, not perfect.
ENJOY!
As the title stats I cant seem to get it to work or find the appropriate folder in which its located any help would be appreciated
Hit Thanks if I Helped
-_-NAMELESS ROM 1+1-_-
Same problem for me. Installed the full image and it doesn't work. It didn't work when I had just installed it and it still doesn't work after rooting.
How are you using it? Custom kernel? App? Which ones?
Stock 5.0 image with root via chainfire autoroot. Solid Explorer file manager and I can't see the USB OTG
MasterTB said:
Stock 5.0 image with root via chainfire autoroot. Solid Explorer file manager and I can't see the USB OTG
Click to expand...
Click to collapse
Are you supposed to? I thought an app.was needed to mount it. Is ES supposed to do that? Did it on KK
rootSU said:
Are you supposed to? I thought an app.was needed to mount it. Is ES supposed to do that? Did it on KK
Click to expand...
Click to collapse
ES used to (on 4.4.4)
I did notice that my Thermal Seek camera (also USB OTG) works fine with Lollipop, so I guess ES has to be updated.
Yes, I forgot about ES. It does open it. I had been using solid because I like it better but I also forgot that stock Android is NOT AOSP and that was my problem. It does see it now with ES so, problem solved. Also it reads both fat32 and NTFS. too bad it doesn't read exFAT
MasterTB said:
Yes, I forgot about ES. It does open it. I had been using solid because I like it better but I also forgot that stock Android is NOT AOSP and that was my problem. It does see it now with ES so, problem solved. Also it reads both fat32 and NTFS. too bad it doesn't read exFAT
Click to expand...
Click to collapse
That is so strange - I use ES and I am not able to get it to recognize my USB flash drive! Sheeeeeeesh! :crying:
Well we are all seeing strange things with 5.0 For example, root is not working as it should, apps like App Quarantine can't seem to properly disable some system apps or Google Apps, I can't seem to be able to correctly install a recovery and most apps that should allow to do reboot options (like flashify or twrp manager) don't work. My guess is that we'll have to wait a few days until development has matured a bit..
Then, I can use/see/write my USB by otg only with Es explorer without stickmount or I have to use stick mount mandatorily ?
sorry if you give the answer already but did not understand English very well
Always i used stick mount, but it would only need/use ES Explorer
I can only add that on nexus7 (2013) official 5.0 OTG doesn't work either.
I can access external drive through ES or stickmount, but the system itself is 'blind'.
Using custom kernels (e.g elementalX) built for lollipop which in theory should support OTG break stickmount (and still no OTG support, possibly something in OS beyond the kernel) - internal memory is not mounted anymore to /storage/sdcard0. ES still works though.
lolote said:
Then, I can use/see/write my USB by otg only with Es explorer without stickmount or I have to use stick mount mandatorily ?
sorry if you give the answer already but did not understand English very well
Always i used stick mount, but it would only need/use ES Explorer
Click to expand...
Click to collapse
Yes, you can just use ES Explorer to use USB OTG devices. No need for stickmount.
Update your drivers.
Please read here what I did.
http://forum.xda-developers.com/showpost.php?p=56789129&postcount=50
Work fine.
MasterTB said:
Yes, you can just use ES Explorer to use USB OTG devices. No need for stickmount.
Click to expand...
Click to collapse
but in nexus 5 lollipop ?
Because i when connect my usb 8gb Es explorer askme and showme a pop up, and later show a usb1002 but when i want open it is load for ever and frezze the app.
with stickmount nop frezze no load, open fine.
i mean?
Works fine with this app.
https://play.google.com/store/apps/details?id=com.kyuudroid.nexususbotgfilemanager
Yes in 5.0.
I have the google stock image, rooted with CFAR and all I use is ES Explorer to see my USB OTG. You have to be in either NTFS or Fat32 for it to read the drives.
It does show as a USB 1002 like you say and if you click on it it will open a new window with the contents of the drive. That's all I do.
No tweaks or apps to mount the drives.
MasterTB said:
Yes in 5.0.
I have the google stock image, rooted with CFAR and all I use is ES Explorer to see my USB OTG. You have to be in either NTFS or Fat32 for it to read the drives.
It does show as a USB 1002 like you say and if you click on it it will open a new window with the contents of the drive. That's all I do.
No tweaks or apps to mount the drives.
Click to expand...
Click to collapse
Hi all,
I can see on ES Explorer the US1002 tab like you, and if I click on it, I can see the file inside the USB storage, but i can't put other files on the drive, even if I try to create a new file, the app show up a pop up with the message "unsupported operation", instead the copy from the USB drive to the phone is possibile.
This happens since I flashed the Stock Lollipop build.....
Have you tried to copy or create a file on the drive?
Many Thanks! Bye!
Russosniap said:
Hi all,
I can see on ES Explorer the US1002 tab like you, and if I click on it, I can see the file inside the USB storage, but i can't put other files on the drive, even if I try to create a new file, the app show up a pop up with the message "unsupported operation", instead the copy from the USB drive to the phone is possibile.
This happens since I flashed the Stock Lollipop build.....
Have you tried to copy or create a file on the drive?
Many Thanks! Bye!
Click to expand...
Click to collapse
Yes, I get the same message. You can read files, copy them TO your phone but not copy from your phone to the USB OTG. I guess we will have to wait for some developer to patch things or for AOSP roms to catch up...
MasterTB said:
Yes, I get the same message. You can read files, copy them TO your phone but not copy from your phone to the USB OTG. I guess we will have to wait for some developer to patch things or for AOSP roms to catch up...
Click to expand...
Click to collapse
Probably kernel related. Might need to export to usb otg properly. Probably mounted with no permissions. You can check when OTG is plugged in by typing the "mount" command into a terminal emulator
rootSU said:
Probably kernel related. Might need to export to usb otg properly. Probably mounted with no permissions. You can check when OTG is plugged in by typing the "mount" command into a terminal emulator
Click to expand...
Click to collapse
Ehi guys!
I think I found the problem, my usb drive was formatted in NTFS, android can't white on it, but only read!
I formatted in FAT32 and the problem is solved!! I was so stupid
Bye!!
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
I use https://play.google.com/store/apps/details?id=com.alphainventor.filemanager
It mounts my usb stick fine.
Anyway i think Google File Manager should BE able to do the Same.
Skuddle said:
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
Click to expand...
Click to collapse
Android can't read NTFS
Skuddle said:
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
Click to expand...
Click to collapse
Enable OTG.
If it doesn't help, it means the Pixel cannot read NTFS formatted file system.
Use one of these to read NTFS formatted systems:
1. ZUGate
2. exFAT/ NTFS for USB by Paragon
elong7681 said:
Android can't read NTFS it needs to be FAT32
Click to expand...
Click to collapse
OnePlus devices CAN.
elong7681 said:
Android can't read NTFS it needs to be FAT32
Click to expand...
Click to collapse
Not true. It was true about 6 or 7yrs ago
Maybe it can't read NTFS, I'm not sure. But USB connectivity on Pixel devices is read only, and not r/w. exFAT has been supported for years now
elong7681 said:
Android can't read NTFS
Click to expand...
Click to collapse
It can.
JohnTheFarm3r said:
It can.
Click to expand...
Click to collapse
I stand corrected. Just tried it myself and it can read it.
Some people have had success with writing to USB flash drives, through third-party apps like Total Commander and others. You might need additional plugins for such apps though.
Edit: Mixplorer also works well for writing to USB flash drives. If needed, the custom USB OTG driver can be enabled from Mixplorer settings.
Skuddle said:
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
Click to expand...
Click to collapse
xunholyx said:
Not true. It was true about 6 or 7yrs ago
Maybe it can't read NTFS, I'm not sure. But USB connectivity on Pixel devices is read only, and not r/w. exFAT has been supported for years now
Click to expand...
Click to collapse
I'm confused where there is any trip-up; I apologize if it's simply going over my head.
I use the Kingston DataTraveler MAX (256 GB) USB-C flash drive directly plugged into the P7P, formatted to exFAT, and that's all there is to it to do my monthly backup (that I do before I manually update the security Full Factory image) -- both using Swift Backup, SMS Backup&Restore, and manually moving non-data folders from the internal SD!
It pops up in the stock Files app (in "Storage devices" section under "internal storage"; I can't recall what exactly it comes up as off the top of my head), and it definitely can do r/w. No plugins needed, no third-party app needed, no OTG setting required to be ticked (at least with the stock Files app).
It's very straightforward; I'm afraid I'm missing something. Is the comments only speaking on running it with NTFS format?
Again, sorry if I'm missing something obvious...
@simplepinoi177
Google Files app is buggy, and often does not even show the USB flash drive as one of the destinations to choose from, after selecting the copy file operation, even though it otherwise shows the USB flash drive.
When it does work, it does not copy over the original timestamps of the files to the USB flash drive.
The timestamp issue is also present while copying with the good old Documents UI.
halfbytecode said:
@simplepinoi177
Google Files app is buggy, and often does not even show the USB flash drive as one of the destinations to choose from, after selecting the copy file operation, even though it otherwise shows the USB flash drive.
When it does work, it does not copy over the original timestamps of the files to the USB flash drive.
The timestamp issue is also present while copying with the good old Documents UI.
Click to expand...
Click to collapse
Thank you for explaining. I wasn't aware of those issues with it.
My personal experience is never having any issues with it (both the flash drive nor the Files app); and I use it on my two P7Ps every month since getting it release day. And all I do is do the copy file operation as I only use that drive for backing my data up.
I've never took notice of the timestamps, but it's not a priority for me, but it's good to be aware of; so thank you for informing me.
simplepinoi177 said:
formatted to exFAT
Click to expand...
Click to collapse
Yours is formatted in exFAT (which is an improved version of FAT32) which is kind of universal. Works on Windows, Android , Linux and macOS too.
simplepinoi177 said:
Is the comments only speaking on running it with NTFS format?
Click to expand...
Click to collapse
Yes. NTFS is Microsoft's file system that works as read-only in macOS and doesn't work in many Android devices (OnePlus is a known exception).
TheMystic said:
Yours is formatted in exFAT, which is kind of universal. Works on Windows, Android , Linux and macOS too.
Yes. NTFS is Microsoft's file system that works as read-only in macOS and doesn't work in many Android devices (OnePlus is a known exception).
Click to expand...
Click to collapse
And Samsung (read-only).
JohnTheFarm3r said:
And Samsung (read-only).
Click to expand...
Click to collapse
Since when? As far as I can remember, I had to install a 3rd party app to make it work. It's been quite a while since I connected a NTFS formatted drive.
When I plug a USB stick (that has been formatted the long way as ExFAT) into my P7P and get to USB Preferences, tapping "This device" results in "Couldn't switch". And I'm using whatever File app came with my (as of April 2023) new unit. And it's using Android 13, and the unit tells me that all apps have been updated (as of May 8 when I performed the Update operation).
I see that there is no consensus on how to format the USB stick. Some say ExFAT, some say FAT32, some say that the P7P can read NTFS and others say that it can't... What's a guy to believe??? In any event, I've tried all formats and my P7P is not able to read any of them.
Skuddle said:
When I plug a USB stick (that has been formatted the long way as ExFAT) into my P7P and get to USB Preferences, tapping "This device" results in "Couldn't switch". And I'm using whatever File app came with my (as of April 2023) new unit. And it's using Android 13, and the unit tells me that all apps have been updated (as of May 8 when I performed the Update operation).
I see that there is no consensus on how to format the USB stick. Some say ExFAT, some say FAT32, some say that the P7P can read NTFS and others say that it can't... What's a guy to believe??? In any event, I've tried all formats and my P7P is not able to read any of them.
Click to expand...
Click to collapse
Use exFAT. It is universal and is supported by most operating systems.
Are sure your USB stick isn't corrupt?
Skuddle said:
When I plug a USB stick (that has been formatted the long way as ExFAT) into my P7P and get to USB Preferences, tapping "This device" results in "Couldn't switch". And I'm using whatever File app came with my (as of April 2023) new unit. And it's using Android 13, and the unit tells me that all apps have been updated (as of May 8 when I performed the Update operation).
I see that there is no consensus on how to format the USB stick. Some say ExFAT, some say FAT32, some say that the P7P can read NTFS and others say that it can't... What's a guy to believe??? In any event, I've tried all formats and my P7P is not able to read any of them.
Click to expand...
Click to collapse
I don't see where you're getting USB Preferences...it's never anything I need to do/choose "tapping 'this device'", it merely shows up under internal storage (as I've mentioned before) -- as DataTraveler MAX. This is using the stock Files app as well. I'm also updated to May update.
If anything, the only thing I found that I do that I didn't need to before is there is an "eject" option in the notifications to choose to safely remove it. Other than that, there isn't/wasn't anything particular to get it all working for me; to detect, read, write, delete, etc.
I did a bit of research on what to format USB-C flash drives for Pixel 7's and it said to do ExFAT; and ExFAT is the only format that can be read by both Microsoft and MacOS -- so I figured that kind of compatibility is also the reason why it's best for Android/Pixels....
It's curious how you're having so much issues when it's so simple (at least to me in my experience).
Like @TheMystic said, it makes me think it might be a corrupted drive if you're having that much inconsistencies and issues....
simplepinoi177 said:
I don't see where you're getting USB Preferences.
Click to expand...
Click to collapse
It shows up in the notification area when you connect a USB. You can choose how you want to control the connection: using the phone itself or using the computer that the phone is connected to.
You'll basically see 2 notifications every time you connect a USB device.
simplepinoi177 said:
If anything, the only thing I found that I do that I didn't need to before is there is an "eject" option in the notifications to choose to safely remove it.
Click to expand...
Click to collapse
It has always been there, unless you turn OFF Android System notifications. Not sure about custom ROMs though.
TheMystic said:
It shows up in the notification area when you connect a USB. You can choose how you want to control the connection: using the phone itself or using the computer that the phone is connected to.
You'll basically see 2 notifications every time you connect a USB device.
It has always been there, unless you turn OFF Android System notifications. Not sure about custom ROMs though.
Click to expand...
Click to collapse
I'm familiar with the 2 choices on choosing how to control the connection -- but why would that apply with a USB Flash (HD/SD) Drive; as opposed to a computer? It would neither gain power from a flash drive nor need to make the "distinguishment" to transfer via MTP or PTP, or need any device "control" -- it's a flash drive, it would only be for file transferring/storing.
At the very least, when I connect mine, there is no such options in my notification (nor is it needed/necessary)...I only get the two options to "Explore" or "eject"; not like the multiple I get when connecting to the computer...
So I've been trying different Android 13 roms bc I was looking for a specific feature. I finally found one that works, only to discover it can't recognize my 128gb, or any NTFS usb drive (recognizes fat32 no issues). I did a research but I only found work arounds through apps but this won't work bc I use the drive for Swift backup and restore. Is there a fix for this issue? Device is rooted.
thanks in advance
exFAT/NTFS for USB by Paragon - Apps on Google Play
Full non-root access to files on Microsoft exFAT / NTFS USB-stick from Android
play.google.com
I
WoKoschekk said:
exFAT/NTFS for USB by Paragon - Apps on Google Play
Full non-root access to files on Microsoft exFAT / NTFS USB-stick from Android
play.google.com
Click to expand...
Click to collapse
Like I said I don't just want to have access to the files. I want the OS itself to recognize it so it's accessible through all apps
Aserar said:
I
Like I said I don't just want to have access to the files. I want the OS itself to recognize it so it's accessible through all apps
Click to expand...
Click to collapse
It is by using the SAF (storage access framework/Documents UI).
WoKoschekk said:
It is by using the SAF (storage access framework/Documents UI).
Click to expand...
Click to collapse
it doesnt work. I've tried it before I even post. I'm looking for a mod/driver etc on the operating system level, not through an app
Aserar said:
it doesnt work. I've tried it before I even post. I'm looking for a mod/driver etc on the operating system level, not through an app
Click to expand...
Click to collapse
you can't implement NTFS support that simple since VOLD manages your external file systems. It would be much easier not to take NTFS.
WoKoschekk said:
you can't implement NTFS support that simple since VOLD manages your external file systems. It would be much easier not to take NTFS.
Click to expand...
Click to collapse
I know it used to be possible through magisk mod and custom kernel. I'm just not up to date. NTFS is a must for me. I'll keep looking hopefully I find something
Aserar said:
I know it used to be possible through magisk mod and custom kernel. I'm just not up to date. NTFS is a must for me. I'll keep looking hopefully I find something
Click to expand...
Click to collapse
You are going to flash a custom kernel to be able to use NTFS with a Magisk Module? Then trying to use a USB stick with NTFS (which could be an unstable connection) for saving your backup files created with Swift Backup? Sounds quite complicated.
Aserar said:
So I've been trying different Android 13 roms bc I was looking for a specific feature. I finally found one that works, only to discover it can't recognize my 128gb, or any NTFS usb drive (recognizes fat32 no issues). I did a research but I only found work arounds through apps but this won't work bc I use the drive for Swift backup and restore. Is there a fix for this issue? Device is rooted.
thanks in advance
Click to expand...
Click to collapse
Have visited this site?
Full NTFS Read/Write Support for Android
www.xda-developers.com
WoKoschekk said:
You are going to flash a custom kernel to be able to use NTFS with a Magisk Module? Then trying to use a USB stick with NTFS (which could be an unstable connection) for saving your backup files created with Swift Backup? Sounds quite complicated.
Click to expand...
Click to collapse
No mate! I meant there was solutions back in the day to add ntfs fs through custom kernel and through Magisk mods, not together. Been using ntfs USB sticks for titanium/swift/nand backup and restore for 10 years never had an issue. I rarely save backups on internal storage
jwoegerbauer said:
Have visited this site?
Full NTFS Read/Write Support for Android
www.xda-developers.com
Click to expand...
Click to collapse
No I have not. Thank you. I'll check it out.
Aserar said:
I know it used to be possible through magisk mod and custom kernel.
Click to expand...
Click to collapse
Aserar said:
No mate! I meant there was solutions back in the day to add ntfs fs through custom kernel and through Magisk mods, not together.
Click to expand...
Click to collapse
If you don't use it together then use "or".
WoKoschekk said:
If you don't use it together then use "or".
Click to expand...
Click to collapse
Lol that's not how English works mate!
Aserar said:
Lol that's not how English works mate!
Click to expand...
Click to collapse
You make things very complicated