IssueTracker

To qualify, these files are being written to the public "external" storage.

After a bit further review, the issue might not have anything to do with C versus Java, but it's still a bug nonetheless, because changes to the platform should not break the user experience, and right now, it does. The workaround at the moment is to add the following code after every file close:

MediaScannerConnection.scanFile(this, new String[] { file.getAbsolutePath() }, null, null);

[Comment deleted]

This is pretty poor, and needs to be fixed.

Nearly a year on and Google still haven't ack'd this? It's still a problem - It's a pretty simple fix, refresh the cached info...

/me continues shouting at the sky

still not fixed.. (4.2.2)
are Google employees not using Android phones??

Are you sure the problem lies with the phone?

Which OS is the computer using, and what version of that OS?

Every OS and every version of that OS. Personally I've gotten hundreds of customer complaints about this, but that went down a lot after I started recommending SD Rescan and after I started just calling MediaScannerConnection manually on every single file (which can have its own drawbacks -- on some devices this will cause the file to be added to media libraries even if there's a .nomedia file present in the same directory).

[Comment deleted]

Same the latest 4.3.
Seriously Google...

This is ridiculous. How's about fixing some bugs instead of ploughing ahead
with new stuff with even more bugs in it?

Hello!
Discovered this bug today on Asus TF300 with Android 4.2.1 and on Google Nexus Maguro with Android 4.0. The only one working solution is to use SDRescan before plugging USB-cable - it updates MTP database.

Please confirm and fix this annoying bug on all active Android versions.

yup, affects me too

I have this problem too. In fact, sometimes even a reboot doesn't help.

Yes, this problem still sucks. See workaround here:
http://stackoverflow.com/questions/13737261/nexus-4-not-showing-files-via-mtp

Dammit, google! Is no one using usb cables anymore for copying data? Oo

Problem confirmed for Nexus 7 2013 model running 4.3

for fucks sake google wake up !

This problem is up to Nexus 4 running 4.3 too!

I can confirm this also happens with with a HP slate7 runninng 4.1.1 and unlike nexus devices there's no USB storage mode so now I can't access file that I only saved on my tablet

[Comment deleted]

Still an issue on Nexus5/Kitkat...

Obviously still an issue.
Status: "NEW".

Problem confirmed, new Sony Xperia Z tablet "SGP311" with Android 4.1.2. Fixed by tablet reboot.

Reproduce:
- Use this tablet with factory/reset stock OS.
- Folder created by (my dev/debug) app was hidden in Windows mount, had ".nomedia" file.
- Other (or copy of above) folder created by "Sony File Transfer" app was shown in Windows mount as it should.
- Reproducable after each tablet reboot.

A location observation:
Folder created by (my) app was in Environment.getExternalStorageDirectory() which oddly mounted to windows as "This PC/Xperia Tablet Z/Internal Storage/". Confuzzling on itself but, might bug reproducability be location related?

Confirmed on 4.4 on a Nexus 4. Any files made by any app (specifically backup apps for me) can't be seen until a reboot. Pretty sad bug if you ask me...this needs to be fixed.

I'm having the same issue with 4.4 on Nexus 4.  I notice this most frequently when downloading a torrent - it'll finish downloading, I'll hook the phone to my computer, and cannot find the file or folder.  I never noticed this in earlier versions.

Same issue for me on n7 2012 WiFi using KRT16S . downloaded files using bit torrent app. Folders were created in Downloads directory but my PC running Linux using mtp can't see the folders. Using a file manager in the n7 shows the folders and files. Rebooting n7 solves the prob.

Maybe I imagined it, but thought 4.4 was supposed to fix this. Well, it's still broken. I have found things that used to work now don't in 4.4 Why not report them? What's the point - not one I have reported or starred has been fixed in 3 years.

Still present in Android 4.4/Nexus 5.This hasn't been even ack'd by Google ? Is there a way to increase the priority of the bug.Right now it says Medium.

PLEASE fix. it sux to have to restart the phone each time.

i'm affected by this issue, as is anyone who uses their device for storage.  this issue affects almost every Android user and has persisted through at least 3 OS versions.  kinda ridiculous, isn't it?  Google has been remiss in acknowledging the problem.  Bad form, fellas.  Get this fixed, seriously.

Well, 4.4.2 is here. Fixed? No! Acknowledged even ? No!

Hi guys,
I was having the same problem with Mp3 files not showing up. I went on a limb and enabled USB Debugging, and somehow the files appeared. Can anyone confirm that this is a fix? Performed on Galaxy S2 Skyrocket using CM10.1.3

4.4.2 on Nexus 4, stock rooted and having the same bug. For me the problem is with Dropsync app, also Copilot navigation app, probably many but didn't notice it.

4.4.2 on Nexus 5, I see this bug with File Manager (Explorer). Downloading a file with Google Drive and moving it to another folder will not take effect (other applications cannot read it) until a restart.

Let's see... reported 15 months ago... not even acknowledged by Google... you wonder why you even bother reporting bugs...

4.4 on MotoX, same problem.  Turned on USB debugging per #32, which was unsuccessful.  SDRescan does not seem to run on my phone, so used AirDroid to move files for the time being.

i guess the only way to get this bumped up on the priority list is to hit the "vote" button on the issue (star icon).  bump it up.  this needs to get fixed.  we have hundreds of clients using Android devices and every time an output file is generated, the device has to be reset.  this is just unacceptable...  i don't understand how this defect doesn't have higher priority.

is anyone going to get google to fix it ? could never understand cant the developers rewrite the code?

Problem is that it's probably a specification issue of MTP itself. Might not be fixable

Hey everyone in this, just to let you I have fixed this ish.

Just going on my lunch but will need some testers, it is a proof-of-concept for now.

Will be posting the apk and source soon.

@#40 I'm in for beta testing

So here's the APK

https://github.com/Sarkie/mtp-fix/blob/master/MTPFixProject/MTPFix/build/apk/MTPFix-debug-unaligned.apk

Click View Raw to download it.

Here's the src

https://github.com/Sarkie/mtp-fix/tree/master/MTPFixProject

Install the APK
Attach Cable in MTP Mode
Load the App
Load the directory in Windows Explorer
Then go to an application that produces a file, save a file
See if it appears in Windows Explorer (can take a while if the file is big)

For coders, I am watching Recursively External Storage Directory and then adding to Media Scanner once a file has been created

Future:
I will look into Android events see if there's a "File Created" Event so I don't need to have loads of File Observers.
I will look into doing this as a Service that loads at boot so is always running and fixing this.
Look into stopping the GC collecting the File Observers.

Notes:
Probably won't work that well, as I did it in 10 minutes and guessed, but works on my Moto G on 4.4.2

I guess there is some mechanism that updates the sdcard data after data is deleted from /storage/emulated/0 ??

Am I close?

FYI, the .scanFile() "solution" isn't. I've been fighting this problem for two days now.

I ran across the .scanFile() suggestion elsewhere and have tried it several ways, including inferring the MIMEtype (passing null) and specifying it explicitly (passing an array with a single string), and nothing makes any difference. My app creates a file in external storage, the file is visible in ADB with the same permissions as other files in the directory, but the file simply isn't there on the other end of a USB cable.

Broken, broken, broken.

This reminds me of the other USB bug that's driving me crazy: "Unable to cleanly close USB accessory FileInputStream". A blocked Accessory read thread cannot be unblocked, even if the underlying FileInputStream object is closed (!!!). This prevents an app from cleanly relaunching. This problem is discussed at:

http://code.google.com/p/android/issues/detail?id=20545

...and has languished without attention from Google for well over a year now. There must be somebody at Google that doesn't like USB because apparently any bugs associated with USB are simply ignored forever.

Still an issue with HTC One X running 4.2.2.

Can confirm SDrescan works but this is still a big problem as I want to run a data logger esque program and have the user remove data onto a pc via usb.

Google pls

Issue affects Nexus 7 tablet (2013 model).

Particularly noticeable using BitTorrent Sync to copy files to the system Music folder: files are not visible to Google Play (or other media players, e.g. doubleTwist) until restart.

Extremely disappointing to see this issue is over a year old, and not yet assigned...!

A "workaround" as a user is to take a picture. That probably makes the MediaScanner scan the new files, and they are shown after it.

Of course this is just a little less painful then rebooting the phone, still...

The best workaround is to rescan, which updates the MTP cache.. great solution here:

http://stackoverflow.com/a/20413888/1992342

[Comment deleted]

One year later, and this is still a mess. Since Google refuses to acknowledge this problem, I use the following workarounds at the moment:

CREATE FILE:

context.sendBroadcast(new Intent(Intent.ACTION_MEDIA_SCANNER_SCAN_FILE, Uri.fromFile(file)));

DELETE FILE:

The above can also be used, but on some devices causes a 0-byte file to be created. So instead, I do one of the following:

context.sendBroadcast(new Intent(Intent.ACTION_MEDIA_MOUNTED, Uri.fromFile(file.getParentFile())));

This can also be used for notifying the media scanner of changes to a given folder. Unfortunately, it doesn't work on KitKat and above. For those devices, you can try doing this:

context.getContentResolver().delete(Files.getContentUri("external"), Files.FileColumns.DATA + "=?", new String[] {file.getAbsolutePath()});

This might not work on all devices or will probably get broken in some scenario or another, but it does work in my testing on the Nexus 5. Until Google fixes this properly on their side, these calls are the best I've found for now.

Note that SDRescan does not support Android 4.4, so it can no longer be used as a workaround for this bug after you upgrade to Kit Kat.

Is anybody fixing this? its been like more than a year now?

This wasted my two days.. feeling doomed...

I'm getting this same problem on my Samsung Note II.

Ha this is soooo ridiculous, I got the same problem on Xperia Z1 Compact with 4.3. All newly created folders are visible instantly, but they are displayed as files and are thus not browsable. Tip from #15 running SDRescan and then un- and replugging in the device works for me too.
Until now I didn't experience these problems on the Nexus 4 @4.4 but I use MTP very seldom.
Google seems to be a bunch of slowpokes when it comes to fixing bugs. It seems google employees get free iPhones from their company :) Better let the community provide patches than troubleshooting themselves ...

Can we please get some Google representation about this issue? Having the same problem with Nexus 5

Same problem on new nexus 7 by asus.  This is very annoying.

I wonder if it could be fixed downstream at the custom ROM level

This code seems to be able to make my new files appear over MTP, but this only seems to be working on individual files.  I tried passing in a reference to a parent directory and it didn't do anything.

        public void makeFileDiscoverable(File file, Context context){
                MediaScannerConnection.scanFile(context, new String[]{file.getPath()}, null, null);
                context.sendBroadcast(new Intent(Intent.ACTION_MEDIA_SCANNER_SCAN_FILE,
                Uri.fromFile(file)));
        }

You could try my APK to see if that fixed it. I didn't continue with it because I got no feedback on creating a service to fix it for you guys...

https://code.google.com/p/android/issues/detail?id=38282#c42

When is this cr*p going to be fixed? Why can we not just have normal mass storage device, which is known to work?

Sarkie's patch is working fine on my Xperia M running official 4.3.

#62 Thank you, only took someone 5 months to help me, I will look into making this a service to constantly run to fix this issue if Google don't care that much to fix it asap.

[Comment deleted]

[Comment deleted]

[Comment deleted]

I confirm this bug in android 4.1.2 ,samsung gt-s7572 phone.

Thanks to socram8... I think I have it all sorted.

Please can people test the APK attached on their phone, if you don't know how to install it, google.

The code is here for the curious:

https://github.com/Sarkie/mtpfix

Install the app, the application is called "MTPFix" and click the button to start the service, or just reboot your phone and it *should* run on boot and fix this issue.

Testers welcome!

Same thing on the Galaxy S3.

I swear, Kit Kat is proving to be more trouble than it's worth. Oh boy the calculator icon changed, and the buttons on it look different, and the battery icon is white now! How about instead of cosmetic crap that was fine before - fix stuff like this!

wtf google

Recently I faced with the same problem but some additional research helped find hidden files. It seems that Google has made some changes in storage structure. All these files were moved to another folder "This Computer\HTC One\Internal Storage\storage\emulated\0". But it's strange that not all files were moved.
HTC One (M7) Android 4.4.2

Hope it helps :)

WAKE UP GOOGLE, WTF

I recently downloaded a file using bittorrent,and was able to view the file using es explorer app. Using nexus 7 first gen .. With 4.4.2 (I think .. Device not with me now). Had no chance to test via mtp.

Samsung S4 on 4.2.2 seems to (still) have this issue.

files written by apps in /storage/emulated/0/Android/data/ only appear in Windows Explorer after disconnecting/reconnection USB (Windows 7)

F5 (refresh) does not help.

Not fixed in latest update 4.4.3 on nexus 4.

Could you try my fix I posted in comment #68 then?  Rather than complaining, help me, help you guys...

https://code.google.com/p/android/issues/detail?id=38282#c68

I can give it a try, but just for information... does it keep running in the background all the time?

The same f... problem. Oh god.. almost 2 years.

#77 Yes, it monitors all the folders for new files and then adds its to the media scanner, I could change it so it was just a button that went through all your files and adds everyone it finds, but I need to first verify it actually works on a few devices before putting any more effort in.

Can someone explain why a cache needed at all? Why not simply rescan the folder every time?

#76 I just tried MTPFix on my Xperia S and it works! Thank you so much!

#81 Brilliant news. Anyone else care to test it? Need a few more and the'll I'll package it up properly.

Thanks for your efforts to fix this bug, but I think the lack of enthusiasm for testing this app stems from your approach to fix this problem. I dont think anyone wants to run a service permanently on their device when its impact on battery life and performance and other security issues are unknown. also this bug doesnt happen very often.
I believe the right approach is to write an application which forces a media rescan and rebuild of MTP cache by request of the user and doesnt run as a background service.

[Comment deleted]

#83 As in comment #42 that is what it did initially and I still didn't get any testers for that. Since I thought it'd be better if it was just running then using the events from the filesystem so it didn't kill a battery or fill up the memory.

I didn't know how it'd perform hence I really wanted testers before I put my name to it.

The source code is provided if you have any issues with the code.

#68 Just tried Sarkie's MTRfix on Nexus7 running Android 4.2.2. Seems to work fine.

Took a reboot and reconnecting the USB connection but, working on Android 4.4.4 PA on a GNex.

Still a bug. Had to install SD Rescan or reboot whenever out of sync.
Nexus 7 Tablet
Android 4.4.2

Anybody tried Android K Preview regarding this problem? Any change?

After 4.4.4 also No fix ... Damn google..... :(

Well, lets pray this will be fixed in Android L ! Apparently Google sucks.

what is this this fast-paced update cycle good for if not to fix bugs like this? but at least now I know that its not my but you're fault that my files are sometimes missing on MTP until I reboot...

galaxy s3, rooted, archidroid....works from time to time....had to reboot when stopped working

i am talking about mtpfix ofc

I am on 4.4.4 - not fixed !!
But rebooting Android device helps!

this is on 4.4 too

GOOGLE, WAKE THE FRAK UP AND BRING BACK NORMAL USB-STORAGE INTERFACE!!!

YES, please bring back normal USB storage. This new system truly sucks. What were you thinking.

As someone who hates this bug; the problem with normal USB storage mode is that it completely hands over the control of the entire filesystem to the guest system.
Which is bad. Very bad (security, filesystem integrity, lots of issues at stake).

Thanks for explaining that :) OK, so we need some other file storage mode
that is open and comes built-in to OSX and Windows (wishful thinking). Yeh
I tried the Win XP driver.. didn't work. Hope this improves because current
system method sucks so bad..

can this fix work for an Iphone connected to my Won 7 PC or am Ipad? About a month agon after IO7 & a few forced Windows Updates, I can no longer see photo I take on my Ipad until I connect and re-connect the ipdad and run through tthe whole folder look=up process.

Sarkie, thank you very much for the mtpfix !!! it works ...

google nexus 4.2 / linux / mtpfs
mtp on nexus  worked ok...
but about a month ago, could not get dir listing of files on nexus anymore...
installed mtpfix.apk -> works like a charm

thanks !
google turning into bloatware / big brother ware - beware :-)

I have been experiencing this problem for several releases and am now on 4.4.4, but MEDIUM priority!?!?! Are you kidding? Not being able to see files that are clearly there can cause all sorts of issues!!! What if I copy all files from the folder (e.g. camera images), thinking I got them all, and then delete them on the phone, not knowing I DID NOT ACTUALLY GET THEM ALL! Accidental loss like this, in my eyes is a SEVERE defect.

[Comment deleted]

I have written a small app. The files created by my app is not visible on PC. But if I use this code " sendBroadcast(new Intent(Intent.ACTION_MEDIA_SCANNER_SCAN_FILE, Uri.fromFile(file)));" foreach file. The files are visible. I think there is no bug. The problem is developers who not use fully the Android enviroment.

I have tries a couple File Explorer, and ES File Explorer is working good. The changes it cause is immediately applied to PC.
Stock apps (camera,contacts) are also working well. New photos, deleted photos, the export file of contacts is immediatly applied to PC.

So the problem is not Android. The problem is developers who not uses the Android enviroment properly.


Android developers may add this process to the .createNewFile, .delete, etc. methods. But maybe there is something which we don't know why theye don't add.

Thus, if an app which creates (copies) , moves (renames), and deletes files-directories, has this problem, tell it to the developer of the app. They should use some code like a sent above.

[Comment deleted]

Addition to post 105

I cannot find a method to update the modified files which already exist.

If I edit inside of txt file from phone, the change is not visible from PC, even is I use sendBroadcast(new Intent(Intent.ACTION_MEDIA_SCANNER_SCAN_FILE, Uri.fromFile(file)));

[Comment deleted]

[Comment deleted]

This isn't a perfect solution, but at least on my Moto G LTE (4.4.3), I can get a clean MTP file listing if I:

1. Unplug the USB cable from the Moto.
2. Applications -> Settings -> Storage -> "Unmount SD card".
3. Wait a moment, then tap "Mount SD card".

A notification appears with the text 'Preparing SD card'. I can then plug the cable back in, wait a few moments, and the MTP file system appears synchronized/clean to the phone's internal filesystem. I've tested this on both the emulated/0 and emulated/1 devices, and it seems to work okay.

Obviously, forcing a scan via a remount operation isn't a real solution. This may not work if your device doesn't have an external SD card to rescan in the first place, but as I don't have any other Android devices to test, I can't confirm that.

I agree with the folks who suggest this is a high-priority defect. The change from MSC to MTP is a big one with what I'm sure are many complications, but this problem is related to core functionality. tl;dr - using the MTP protocol, an atomic *file transfer* protocol, is effectively pointless if the end user can't *transfer files* because they can't see them.

Further, I understand why MSC is generally seen as a security problem. Still, considering how annoying MTP is in general, I propose that Developer Options offer a setting to allow knowledgeable users access to the MSC protocol, with the understanding that they're responsible for whatever happens (warning dialogue -> 'i agree' writes a byte somewhere that could be checked later to see if the user was in MSC). Just an idea.

Cheers,
dsm.iv.tr

nb. I don't know how much of a problem this is for non-casual users, but most of the people I know have never removed anything from their DCIM or Music directories, mitigating the impact of this bug. :)

If I use FX Explorer's "Rescan Media" function before I connect via MTP then I can see all files that were missing before.

google, you should hire Sarkie cos he's doing your work better than y'all
MTPfix.apk works on Sony Xperia S (LT26i)running Jellybean 4.1.2

Thanks Sarkie!

[Comment deleted]

Have tested Sarkie's MTPfix.apk (on Nexus 5, 4.4.4) from #68 and these are my findings:

1. [OK] create text file (test.txt) on phone (with content "abc")
   - appears on windows explorer (no issue with content)
2. [BUG] update content on phone (is now "a1bc")
   - content appears truncated on windows (showing "a1b")
   - WORKAROUND: using phone, rename file to something else and rename back again
3. [BUG] rename text file (to test1.txt)
   - explorer continues to show test.txt
   - no workaround
4. [BUG] delete file (test.txt)
   - explorer continues to show test.txt
   - no workaround

there should not be a WORKAROUND. i wrote file to the external storage and it was not visible to an android application running on the device. nor was it visible to the MTP connection. wow.

Still a problem with Android "L" developer preview.

I have different kind of problem, but might be related: I had a 11 MB PDF with about 180 pages of annotations. I copied it to phone to continue annotating on the road and about 130 pages of annotations; the file size increased to 27 MB. Now when I want to copy it back to computer (Windows 8), in that folder I see the original 11 MB PDF! Yes, I see it, I can copy it, but the changes I made on the phone are not there!

This is utter bulshit.

OK, restart did fix it. So it means every time I want to copy something from my phone, I have to reboot it? Since when Android became Windows ("Have you tried turning it off and on again?")?

Just ran into this on Nexus 7 into Mac OS. Spent the best part of 1/2 day trying to get to the bottom of this. Restarting device reveals the files. Not sure how this has gone unpatched for so long.

Hitting this too.

So glad I didn't put my app. onto Play yet, and don't have any customers facing this crap. Right now I'm seriously rethinking the plans I had in that direction.

Because this KILLS functionality.

WTF?  Nexus 7, flagship Google product? Doesn't fix a serious bug that makes any kind of Android app. that works with files, basically USELESS?

2 YEARS after it was reported?????

Deeply disappointed by this.

Having the same issue - need to reboot phone to see any file changes

how is this even acceptable i cant change music, videos, games and other stuff on my phone without having to restart my phone and all sorts of other things... make it back the way it was who cares if you cant run your phone while its plugged? i wanna change what i want to change dammit

So is this fixed in Lollipop then?  A little information to accompany the change in status would be nice.

hmm, why was this marked as obsolete? At least up to 4.4.4 the problem definitely still exist and afaict it also still exists in lollipop?

I'm a little confused, too. Some idea of why this was made obsolete would be welcome. I truly don't understand the sentiment of "it's not an Android problem": developers are supposed to be responsible for updating the MTP list themselves? Isn't that super-backwards? I mean, the only way I could see it not being totally backwards if if we made the bold claim that MTP wasn't a 'filesystem', but a 'protocol', which would be super-hard to defend given that it's effectively being used as a filesystem.

I'm really just confused. Maybe this is the wrong spot for this kind of discussion.

[Comment deleted]

It looks like many bugs and feature requests (that still exist in Lollipop, AFAIK) were closed as "Obsolete" within a few hours of each other, all by that same user.. not sure why though. Per the AOSP "Life of a Bug" FAQ, "Obsolete" is defined as  "Similar to Unreproducible, but with a reasonable certainty that the bug did exist in the reported version but was already fixed in a later release."

Perhaps Google can post an explanation?

I don't think it's fixed in Lollipop, I've listed steps to reproduce at https://code.google.com/p/android/issues/detail?id=24713#c9

So what's happened? Fixed is fixed. What does "obsolete" mean? That they aren't going to fix it?

This still occurs, stop shirking bugs google.

Nexus 4, Lollipop build LRX21T. Created an app to create/save a file in /Downloads. Could see it with FileExplorer App but not using Windows/Ubuntu through USB. This drove me crazy. Luckily found this webpage. Using ediaScannerConnection.scanFile(this, new String[] { file.getAbsolutePath() }, null, null); fixed it.

I too am experiencing this same problem on a OnePlus One with KitKat 4.4.4. How in the world is this obsolete when it hasn't been fixed?

This bug appears on Sony Xperia Z1 Compact  (D5503) with Android 4.4 (KitKat).
Newly created files are not shown through mtp. Mving files with builtin file explorer shows the files on the computer, but on sd card it is restricted, and can't move the file around.

Only fix is to reboot each time before I plug to the computer.

Sad to see this was never resolved. I saw this bug burn.. it damages backups and wasted hours of our onsite technician abroad. This does not bode good for Android, featureslack is setting in.

[Comment deleted]

Check this out: Issue 36949180

Wow Android has this issue known since 2012 and still not resolved in latest 5.0.1!!!! Google is getting lazy, working on the latest & coolest features, but forgetting the basics.

for developer...

just add this code after create a file.

MediaScannerConnection.scanFile(context, new String[] { YOUR_FILE.getAbsolutePath() }, null, null);

Still not resolved in Android 5.1!  Google, pretty please with sugar on top, fix the fucking bug!

In the meantime, the work-around in #139 appears to work, thanks!  I've wrapped it in a FileUtils class with a static method for creating files.  After creating the File, it simply invokes the mentioned scanFile() before returning the File.

Obsolete?? OMG...

WTH?!
this bug is really pain in the ass!
it SHOULD be fixed!

This bug still exists in Android 5.1, even on Google's own Nexus 5. Marking this bug, which was reported more than 2.5 years ago(!), as obsolete without any reason is extremely poor software and community management by Google.

谷歌你牛逼，这还不解决你升个屁的lollipop

It's annoying when I need to copy files to my computer for debugging.
Google should be shamed of this old bug!

Google: Can you please finally take this issue serious and fix it. It's still occurring in Android 5.1.1 on Nexus 7. That sucks!

Nexus 4, andr.5.1 and issue occured after connecting via MTP. I am throwing nexus away and buying windows phone. After the first year when the guarantee expired I had following issues with my phone:
 lollipop upgrade stucked - had to clean reinstall. I lost all my data
 Recovery partition not working
 Unable to roll back to 4.4.4
 Battery bursted after one year
 Media files unreadable with MTP
 Phone not visible on Win 7 pc

This leads me to conclusion: Nexus is not a premium flag ship.It is a lab rat for android.
As I sad, I go back to windows phone.

Android sucks.

蛋疼的BUG居然存在了3年也不fix。

#149, 他们可能认为酷炫新奇的技术比用户体验更重要把.

[Comment deleted]

Google sucks!!!

Struggling to get a listing of directories through MTP created by some apps... Wondering if it is related.
Using Sony Xperia one
Android version 4.4.2

Rebooting didn't help.

2 years in, reported with version 4.2.2 and still nothing. Are you joking?
2 years in and the only thing my USB cable is good for, is charging my phone?

So I have to use bluetooth now. I don't see Gurgle giving a shit here.

I'm only amused that after 271 stars and 153 comments (and that's just the people who found it on the bug tracker), nobody from Google has made any sort of comment other than to mark this as obsolete. (Are there really no Google employees who are annoyed by this?)

I can confirm the problem also for Nexus 5 with Android 5.1.1 .

As per previous comments I tried creating the file using the C-API fopen and C++-API ofstream, without success. I see the file when connecting via shell, but not from the File Explorer.

I would like to point out that when taking a picture with the camera, the file pops up immediately, so there is definitely a workaround.

I can confirm the issue with the Moto G (2014) using FileOutputStream in Java to write to any location on external storage. The written files are not visible using MTP on Ubuntu (I haven't tested other platforms).

Rebooting fixes the problem, but that takes a couple minutes. My research entails generating a large number of files which must be copied to the computer which makes this is a serious inconvenience.

This shouldn't be obsolete.  Android File Transfer is completely unusable for me with the Nexus 5 on 5.1 because the file list is always massively out of date.

I also encounter this problem. I had to transfer my folders with mp3 by wi-fi to PC, then to categorize it properly. And after that send it back.
Could be done in a matter of few clicks by cable but well, it's better than the thing I've done one year ago before I knew about this shitty bug and formatted my phones internal storage cause it's files weren't appearing. I thought something got broken or I got a virus :/

GOOGLE, what are you doing? 3 YEARS...

Why is this bug marked as obsolete and closed? it is still ruining my apps on july 2015!

I needed to create a directory and copy some sample files for my app. After a lot of experiments and research the following procedure worked flawlessly for me:

1) Created directory using File.mkdir().

2) Copied files in directory and run MediaScanner on each file.

MediaScannerConnection.scanFile(context, new String[]{file.getAbsolutePath()}, null, null);

3) Run MediaScanner on directory.
MediaScannerConnection.scanFile(context, new String[]{directory.getAbsolutePath()}, null, null);

Result:
The files and directory appear instantaneously on PC over MTP.

I am using Oneplus One with CM12s

Still facing this issue and running MediaScanner on directories and files not working for me on device running 4.4.

Same issue Nexus 9 M Preview.  What the fuck google?!?!?!   How many years will it take to fix this!?!??!?!?!

[Comment deleted]

God damn it..
It's middle of 2015 and i'm using Android L and still faced this issue

Think for me it is the same: Android Version 4.4.2 . copying a file from Android to Win 7 has a prious content until reboot of Android.
Why has this Issue the status obsolete and why is it closed. Can someone reopen it or create a new issue?

It's still an issue on 5.1.1!!!

Lollipop, this IS STILL A BIG ISSUE!

I basically cant do anything with phone on PC because of stupid MTP not working or showing 2 files!

GOOD OLD USB MASS STORAGE

Still an issue on Nexus 6, Android 5.1.1 connected to Windows 8.1 PC.
We create log files (*.log") in the Download directory and cannot access them without reboot. This is ridiculous. At least the phone reboot fixes it temporarily, but this is not helpful...

I hate, HATE, H*A*T*E this stupid MTP interface. I want a real disk connected to my pc.
I want to have real date/time attributes...

I have found this "obsolete" bug while searching for a reason why my Motorola MotoG 2014 with Lollipop 5.0.1 is not showing correctly my media via MTP after the new Motorola's "Gallery" app, the one that let us create "albums" via moving files to DCIM's subdirectories...
Now I know why and I'm once more piXXed off by this fXXXXXing MTP.

...and 3 years have passed...

Hello
I have the same problem on Motorola TC 55 running 4.4.3
Android developers should ask some help from Microsoft ... they usually take less than 3 years to fix bugs like this

This just happened to me under 5.1.1 OnePlus 2.

Solved by doing the following:

Go to settings > apps > all applications > media storage > tap 'clear data' ...

Reboot and everything will appear in Windows Explorer once again.

5.1.1 cataclysm rom, literally every picture taken with an app that isn't by google doesn't show up. This is definitely not obsolete, and very much a current issue.

To the developer e...@google.com... you're an asshole for marking this obsolete. Android 5.1 and this still exists.