From Newsgroup: comp.mobile.android

I'm 100% sure my Samsung Portable SSD T7 (1 TB), exFAT formatted, worked
under my Pixel 6 with Total Commander (and File explorer), but
apparently, this doesn't work anymore with Pixel 10.

I've searched for a solution and Total Commander once offered USB Stick
plugin to fix this, but this plugin seems to be gone. There's this
plugin:

Microsoft exFAT/NTFS for USB by Paragon Software

but this isn't freeware. They don't charge much, but it's not like I'm
going to use this daily. The free option would be to connect my Pixel 10
to my PC and transfer the files (I think I could even use Bluetooth if I wanted).

Bottom line: is there a way I can access my exFAT SSD with some sort of freeware?

Tnx!
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Thu, 18 Dec 2025 16:54:40 +0100, s|b wrote:

I've searched for a solution and Total Commander once offered USB Stick plugin to fix this, but this plugin seems to be gone. There's this
plugin:

Microsoft exFAT/NTFS for USB by Paragon Software

<https://www.ghisler.com/androidplugins/googleplay/>
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

s|b wrote:

I'm 100% sure my Samsung Portable SSD T7 (1 TB), exFAT formatted, worked under my Pixel 6 with Total Commander (and File explorer), but
apparently, this doesn't work anymore with Pixel 10.

I only have Pixels 3 and 8a, but you seem convinced the issue is 10
specific, so I can't do any tests.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Thu, 18 Dec 2025 17:16:14 +0000, Andy Burns wrote:

I only have Pixels 3 and 8a, but you seem convinced the issue is 10 specific, so I can't do any tests.

I did some more searching and it seems to be a problem with /all/ Pixel devices. I'm 100% sure it worked on my Pixel 6, but I just tested again
with my P6 and it's a no go.

Le Chat (AI) told me exFAT isn't supported anymore since December 2025.

Apparently exFAT and NTFS are owned by Microsoft and Google doesn't want
to pay them for support. I installed Microsoft exFAT/NTFS for USB by
Paragon Software and wanted to activate the (2 day) trial, but it
claimed I had no access to internet, which is BS. So not going to give
them my money. I went ahead and connected my Pixel to my PC and
transferred the files. Still, I'm pissed that I have an external SSD
with USB-C connection and it doesn't work on my smartphone anymore.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

s|b <me@privacy.invalid> wrote:

On Thu, 18 Dec 2025 17:16:14 +0000, Andy Burns wrote:

I only have Pixels 3 and 8a, but you seem convinced the issue is 10 specific, so I can't do any tests.

I did some more searching and it seems to be a problem with /all/ Pixel devices. I'm 100% sure it worked on my Pixel 6, but I just tested again
with my P6 and it's a no go.

Le Chat (AI) told me exFAT isn't supported anymore since December 2025.

Apparently exFAT and NTFS are owned by Microsoft and Google doesn't want
to pay them for support. I installed Microsoft exFAT/NTFS for USB by
Paragon Software and wanted to activate the (2 day) trial, but it
claimed I had no access to internet, which is BS. So not going to give
them my money. I went ahead and connected my Pixel to my PC and
transferred the files. Still, I'm pissed that I have an external SSD
with USB-C connection and it doesn't work on my smartphone anymore.

I don't know the first thing about exFAT, but it isn't owned (anymore)
by Microsoft, so Google doesn't have to pay them.

Wikipedia [1] says, "exFAT was proprietary until 28 August 2019, when Microsoft published its specification.".

If exFAT was proprietary/licensed/paid/<whatever>, it couldn't be
supported on Linux and FreeBSD.

So while there is indeed no longer support on Android >13 [1], the
reason given "Google doesn't want to pay them for support" is false.

[1] <https://en.wikipedia.org/wiki/ExFAT>
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On 18 Dec 2025 20:46:49 GMT, Frank Slootweg wrote:

I don't know the first thing about exFAT, but it isn't owned (anymore)
by Microsoft, so Google doesn't have to pay them.

Wikipedia [1] says, "exFAT was proprietary until 28 August 2019, when Microsoft published its specification.".

If exFAT was proprietary/licensed/paid/<whatever>, it couldn't be
supported on Linux and FreeBSD.

So while there is indeed no longer support on Android >13 [1], the
reason given "Google doesn't want to pay them for support" is false.

[1] <https://en.wikipedia.org/wiki/ExFAT>

This site: <https://en.androidguias.com/The-best-diagnostic-apps-for-your-Android-hardware/>

states: Android natively recognizes FAT32 and exFAT systems on USB OTG
devices.

That's great, but it doesn't work on my Pixel 6 (not anymore) or my
Pixel 10. As soon as I get the chance I'll try on another Android
smartphone.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On 2025-12-18 21:46, Frank Slootweg wrote:

s|b <me@privacy.invalid> wrote:

On Thu, 18 Dec 2025 17:16:14 +0000, Andy Burns wrote:

I only have Pixels 3 and 8a, but you seem convinced the issue is 10
specific, so I can't do any tests.

I did some more searching and it seems to be a problem with /all/ Pixel
devices. I'm 100% sure it worked on my Pixel 6, but I just tested again
with my P6 and it's a no go.

Le Chat (AI) told me exFAT isn't supported anymore since December 2025.

Apparently exFAT and NTFS are owned by Microsoft and Google doesn't want
to pay them for support. I installed Microsoft exFAT/NTFS for USB by
Paragon Software and wanted to activate the (2 day) trial, but it
claimed I had no access to internet, which is BS. So not going to give
them my money. I went ahead and connected my Pixel to my PC and
transferred the files. Still, I'm pissed that I have an external SSD
with USB-C connection and it doesn't work on my smartphone anymore.

I don't know the first thing about exFAT, but it isn't owned (anymore)
by Microsoft, so Google doesn't have to pay them.

Wikipedia [1] says, "exFAT was proprietary until 28 August 2019, when Microsoft published its specification.".

If exFAT was proprietary/licensed/paid/<whatever>, it couldn't be supported on Linux and FreeBSD.

Linux has supported many things that were proprietary, ignoring their licenses. At worst, you had to compile the files at home and install
them. like NTFS.

So while there is indeed no longer support on Android >13 [1], the
reason given "Google doesn't want to pay them for support" is false.

[1] <https://en.wikipedia.org/wiki/ExFAT>

--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On 2025-12-18 22:16, s|b wrote:

On 18 Dec 2025 20:46:49 GMT, Frank Slootweg wrote:

I don't know the first thing about exFAT, but it isn't owned (anymore)
by Microsoft, so Google doesn't have to pay them.

Wikipedia [1] says, "exFAT was proprietary until 28 August 2019, when
Microsoft published its specification.".

If exFAT was proprietary/licensed/paid/<whatever>, it couldn't be
supported on Linux and FreeBSD.

So while there is indeed no longer support on Android >13 [1], the
reason given "Google doesn't want to pay them for support" is false.

[1] <https://en.wikipedia.org/wiki/ExFAT>

This site: <https://en.androidguias.com/The-best-diagnostic-apps-for-your-Android-hardware/>

states: Android natively recognizes FAT32 and exFAT systems on USB OTG devices.

That's great, but it doesn't work on my Pixel 6 (not anymore) or my
Pixel 10. As soon as I get the chance I'll try on another Android
smartphone.

Try a plain FAT device, just to make sure it works.
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Frank Slootweg, 2025-12-18 21:46:

[...]

Wikipedia [1] says, "exFAT was proprietary until 28 August 2019, when Microsoft published its specification.".

Just because the specification is published does not mean you don't have
to get a license to use it.

Quote:

"exFAT was proprietary until 28 August 2019, when Microsoft published
its specification. Microsoft owns patents on several elements of its
design."

And as far I know Microsoft did not give up the patents.

If exFAT was proprietary/licensed/paid/<whatever>, it couldn't be
supported on Linux and FreeBSD.

Linux implemented many things by reverse engineering like NTFS even
without a specific license for it.

So while there is indeed no longer support on Android >13 [1], the
reason given "Google doesn't want to pay them for support" is false.

[1] <https://en.wikipedia.org/wiki/ExFAT>

If adding ExFAT does not need any license there would not be any reason
not to do so.
--
Arno Welzel
https://arnowelzel.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Arno Welzel <usenet@arnowelzel.de> wrote:

Frank Slootweg, 2025-12-18 21:46:

[...]

Wikipedia [1] says, "exFAT was proprietary until 28 August 2019, when Microsoft published its specification.".

Just because the specification is published does not mean you don't have
to get a license to use it.

Quote:

"exFAT was proprietary until 28 August 2019, when Microsoft published
its specification. Microsoft owns patents on several elements of its
design."

And as far I know Microsoft did not give up the patents.

See the end of the 'Legal status section':

"There was, however, discussion within Microsoft over whether Microsoft
should allow exFAT in Linux devices,[52][53] which eventually resulted
in Microsoft publishing the official specification for open usage[8]
and releasing the exFAT patents to the OIN in August 2019.[33]"

(OIN is Open Invention Network, a company specialising in Linux patents)

So they published the official specification *and* released the
patents.

If exFAT was proprietary/licensed/paid/<whatever>, it couldn't be supported on Linux and FreeBSD.

Linux implemented many things by reverse engineering like NTFS even
without a specific license for it.

Yes, they did, but I'm talking about what is the exFAT status now.

So while there is indeed no longer support on Android >13 [1], the
reason given "Google doesn't want to pay them for support" is false.

[1] <https://en.wikipedia.org/wiki/ExFAT>

If adding ExFAT does not need any license there would not be any reason
not to do so.

Indeed, so it's just Google's decision to no longer support it.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

s|b wrote:

I did some more searching and it seems to be a problem withall Pixel
devices. I'm 100% sure it worked on my Pixel 6, but I just tested again
with my P6 and it's a no go.

I took a 128GB NVMe, inserted into a USB-C caddy, plugged into Win11
laptop, deleted old partitions, created single new partition, formatted
as exFAT, created one folder and one .txt file, ejected it, plugged into Pixel8a, got a toast that said "USB available", went into Files by
Google app, the folder and text file were present.


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Andy Burns wrote:

I did some more searching and it seems to be a problem withall Pixel
devices. I'm 100% sure it worked on my Pixel 6, but I just tested again
with my P6 and it's a no go.

I took a 128GB NVMe, inserted into a USB-C caddy, plugged into Win11
laptop, deleted old partitions, created single new partition, formatted
as exFAT, created one folder and one .txt file, ejected it, plugged into Pixel8a, got a toast that said "USB available", went into Files by
Google app, the folder and text file were present.

s|b is a well known troll who is trolling us in this thread (IMHO).
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

s|b, 2025-12-18 20:30:

On Thu, 18 Dec 2025 17:16:14 +0000, Andy Burns wrote:

I only have Pixels 3 and 8a, but you seem convinced the issue is 10
specific, so I can't do any tests.

I did some more searching and it seems to be a problem with /all/ Pixel devices. I'm 100% sure it worked on my Pixel 6, but I just tested again
with my P6 and it's a no go.

My Pixel 6a has no problem wit exFAT formatted USB sticks connected via
USB-C.
--
Arno Welzel
https://arnowelzel.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Arno Welzel <usenet@arnowelzel.de> wrote:

s|b, 2025-12-18 20:30:

On Thu, 18 Dec 2025 17:16:14 +0000, Andy Burns wrote:

I only have Pixels 3 and 8a, but you seem convinced the issue is 10
specific, so I can't do any tests.

I did some more searching and it seems to be a problem with /all/ Pixel devices. I'm 100% sure it worked on my Pixel 6, but I just tested again with my P6 and it's a no go.

My Pixel 6a has no problem wit exFAT formatted USB sticks connected via USB-C.

As s|b was also interested in trying other brands: Same for me on a
Samsung Galaxy A51 with Android 13 and a A56 with Android 16.

USB stick is a Samsung FIT 64GB formatted exFAT and connected via a
USB-A to USB-C cable. N.B. The stick was formatted exFAT from the
factory and subsequently 'Quick Format'ted on Windows 11.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Fri, 19 Dec 2025 02:58:08 +0100, Carlos E.R. wrote:

Try a plain FAT device, just to make sure it works.

I don't have a FAT device with a USB-C connection. I want to use my 1 TB
SSD. It worked before.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Fri, 19 Dec 2025 11:10:26 +0000, Andy Burns wrote:

I took a 128GB NVMe, inserted into a USB-C caddy, plugged into Win11
laptop, deleted old partitions, created single new partition, formatted
as exFAT, created one folder and one .txt file, ejected it, plugged into Pixel8a, got a toast that said "USB available", went into Files by
Google app, the folder and text file were present.

When I reconnect the SSD to my PC (W11 25H2), after it was connect to my
Pixel 10, I get a message telling me I have to scan the drive for
errors. When I do the scan doesn't find anything. No errors to be
repaired.

So maybe the SSD is to blame? I don't have any other drives to test and
I don't feel like formatting the drive again...
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Sat, 20 Dec 2025 11:41:23 +0100, Arno Welzel wrote:

My Pixel 6a has no problem wit exFAT formatted USB sticks connected via USB-C.

I'm beginning to think there's something wrong with the drive... I'm
100% sure it worked before on my Pixel 6, but not anymore. I'll see if I
can somehow store that data on it elsewhere and then try reformatting.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On 20 Dec 2025 11:23:54 GMT, Frank Slootweg wrote:

As s|b was also interested in trying other brands: Same for me on a
Samsung Galaxy A51 with Android 13 and a A56 with Android 16.

USB stick is a Samsung FIT 64GB formatted exFAT and connected via a
USB-A to USB-C cable. N.B. The stick was formatted exFAT from the
factory and subsequently 'Quick Format'ted on Windows 11.

Tnx for testing, Frank. As I already stated, I'm starting to think the
SSD is the problem.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

s|b <me@privacy.invalid> wrote:

On Fri, 19 Dec 2025 11:10:26 +0000, Andy Burns wrote:

I took a 128GB NVMe, inserted into a USB-C caddy, plugged into Win11 laptop, deleted old partitions, created single new partition, formatted
as exFAT, created one folder and one .txt file, ejected it, plugged into Pixel8a, got a toast that said "USB available", went into Files by
Google app, the folder and text file were present.

When I reconnect the SSD to my PC (W11 25H2), after it was connect to my Pixel 10, I get a message telling me I have to scan the drive for
errors. When I do the scan doesn't find anything. No errors to be
repaired.

The error on Windows is probably because the SSD was not properly
ejected from the Android device (for the simple reason you couldn't
eject it, because it wasn't recognized).

If that was the case, a 'chkdsk <drive_letter>:' should fix it. Or is
the SSD not even recognized in Disk Management?

I had a somewhat similar problem with my test with the exFAT USB
memory stick. On the Samsung A51 there was some kind of Eject function,
so I used that and all was fine. But on the A56 I could not find such a function, so I just unplugged the USB stick and then the A56 complained
about it not being ejected properly (Duh!) and advised to reboot to
prevent any possible crashes.

So maybe the SSD is to blame? I don't have any other drives to test and
I don't feel like formatting the drive again...

If Windows' Disk Management, chkdsk and File Explorer don't complain,
I don't see a reason to suspect the SSD, but perhaps Paul over there -->
:-) has other/better ideas.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On 21 Dec 2025 18:29:01 GMT, Frank Slootweg wrote:

The error on Windows is probably because the SSD was not properly
ejected from the Android device (for the simple reason you couldn't
eject it, because it wasn't recognized).

If that was the case, a 'chkdsk <drive_letter>:' should fix it. Or is
the SSD not even recognized in Disk Management?

Oh, man, I should have known this earlier. )-: I did it the hard way: I
copied about 500 GB to another drive, deleted the rest and then did
quick format of the SSD to exFAT. It runs fine now. (I'm not in the
process of copying everything back.)

The SSD ran fine under W11, after the scan, so I think Disk Management
wasn't a problem either. I didn't look at it.

I will make of note of

chkdsk <drive_letter>:

because I did exactly what you suggested: I didn't safely unmount the
SSD from my smartphone. Could this also be the cause of the problem?

I had a somewhat similar problem with my test with the exFAT USB
memory stick. On the Samsung A51 there was some kind of Eject function,
so I used that and all was fine. But on the A56 I could not find such a function, so I just unplugged the USB stick and then the A56 complained
about it not being ejected properly (Duh!) and advised to reboot to
prevent any possible crashes.

I just learned 2 ways to safely unmount the SSD. There was a
notification giving me this option and it should also be possible with
the Files app. I assume it's also possible with Total Commander.

If Windows' Disk Management, chkdsk and File Explorer don't complain,
I don't see a reason to suspect the SSD, but perhaps Paul over there -->
:-) has other/better ideas.

Well, it's working now. I had no chance to try chkdsk, so if it happens
again I'll certainly try that. For now, I blame the problem on me not
safely unmounting the SSD.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Thu, 18 Dec 2025 16:54:40 +0100, s|b wrote:

Bottom line: is there a way I can access my exFAT SSD with some sort of freeware?

As others have confirmed: exFAT should be no problem under Android. I
did a (quick) format to exFAT on the SSD and it is now visible in my
Pixel 10. I think the problem started after not safely unmounting the
SSD from my Pixel.

One thing I'll keep in mind next time it happens:

chkdsk <drive_letter>:

Tnx, everybody!
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Sun, 21 Dec 2025 21:10:13 +0100, s|b wrote:

(I'm not

_now_

in the
process of copying everything back.)

--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android


s|b wrote:

I didn't safely unmount the SSD from my smartphone. Could this also
be the cause of the problem?

Yes, any operating system will leave the "dirty bit" set when you do
that to exFAT/NTFS partitions.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

s|b <me@privacy.invalid> wrote:

On 21 Dec 2025 18:29:01 GMT, Frank Slootweg wrote:

[...]

I will make of note of

chkdsk <drive_letter>:

because I did exactly what you suggested: I didn't safely unmount the
SSD from my smartphone. Could this also be the cause of the problem?

After an unsafe removal, Windows might give some error/notification
message, but in most cases, the SSD should still be accessible and most
if not all of the data should still be there. As Paul mentions, most filesystems have some kind of dirty/clean bit and if the bit is in the
dirty state after an unsafe removal, the OS will complain, but otherwise
work.

[...]

I just learned 2 ways to safely unmount the SSD. There was a
notification giving me this option and it should also be possible with
the Files app. I assume it's also possible with Total Commander.

Good.

[...]

Well, it's working now. I had no chance to try chkdsk, so if it happens
again I'll certainly try that. For now, I blame the problem on me not
safely unmounting the SSD.

Glad you got it sorted.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

s|b, 2025-12-21 18:55:

On Fri, 19 Dec 2025 11:10:26 +0000, Andy Burns wrote:

I took a 128GB NVMe, inserted into a USB-C caddy, plugged into Win11
laptop, deleted old partitions, created single new partition, formatted
as exFAT, created one folder and one .txt file, ejected it, plugged into
Pixel8a, got a toast that said "USB available", went into Files by
Google app, the folder and text file were present.

When I reconnect the SSD to my PC (W11 25H2), after it was connect to my Pixel 10, I get a message telling me I have to scan the drive for
errors. When I do the scan doesn't find anything. No errors to be
repaired.

This is the standard procedure, if the drive was not properly disconnected.

So maybe the SSD is to blame? I don't have any other drives to test and
I don't feel like formatting the drive again...

Well - without any other drives to test it is hard to tell, if the drive
is the problem or not.
--
Arno Welzel
https://arnowelzel.de
--- Synchronet 3.21a-Linux NewsLink 1.2