What steps will reproduce the problem?
1. Start aLogcat.
2. Save the log.
3. Browse phone storage over ADB.
What is the expected output? What do you see instead?
I would expect the new log file in the aLogcat folder, but it is missing. If I
trigger a media scan (using Android's Developer Tools) and refresh the folder
on the computer, the new log is there.
What version of the product are you using? On what operating system?
Version 2.6.1 (downloaded from F-Droid), on Cyanogenmod 11.0m11.
Please provide any additional information below.
This only affects MTP devices. My old Nexus S (which exposed its file system as
USB mass storage) did not have this issue. I reported this as a bug in
Cyanogenmod and was told that apps are expected to call
MediaScannerConnection#scanFile
http://developer.android.com/reference/android/media/MediaScannerConnection.html
#scanFile(java.lang.String, java.lang.String) after creating a new file.
Apparently aLogcat is not doing this.
Original issue reported on code.google.com by
mich...@vonglasow.comon 27 Feb 2015 at 9:57