Pleco for Android 3.2.10
- Thread starter mikelove
- Start date
ckatt
状元
Thans, actually it turns out I like dictionary and exit better. Also it may have something to do with using the little camera button on the input selection bar. If I swtitch apps then come back to pleco I can't use the back button. But if I used the menu on the left to enter OCR its not a problem.
Does anyone else also have the following issue:
A file freshly created by Pleco does not show up in MTP view. Unplugging the USB cable and plugging it back doesn't make it appear but rebooting the device will. To reproduce: on the device tap Menu, Settings, Backup Settings and/or History, Backup Settings Only, choose /storage/emulated/0 and leave the default filename, settings-*.xml. Plug in the device through USB, open Windows Explorer, click device name under Devices and drives, click Internal storage. The newly-generated file is not visible.
The file is accessible through ADB shell and from other Android apps. If I make a copy of it with a file manager app, that copy is visible immediately. If I rename the original file, it becomes visible too. It then stays visible when renamed back to the original name.
I find it hard to believe this could be an issue with Pleco and not something else but it happens for me with Pleco on two completely different devices, and does not happen with a file created with another app (I tried Sound Recorder). There is nothing unusual about the file permissions (original file):
Device 1:
Device 2:
The only other common point is the MTP client side (Windows 8.1 Update 1, can't test it with another OS at the moment) but an OS reboot does not resolve it either.
This might very well be unrelated to Pleco. Windows's MTP implementation is beyond redemption but as I'm out of ideas for the moment, I'd appreciate if anyone could confirm if they have this issue too.
A file freshly created by Pleco does not show up in MTP view. Unplugging the USB cable and plugging it back doesn't make it appear but rebooting the device will. To reproduce: on the device tap Menu, Settings, Backup Settings and/or History, Backup Settings Only, choose /storage/emulated/0 and leave the default filename, settings-*.xml. Plug in the device through USB, open Windows Explorer, click device name under Devices and drives, click Internal storage. The newly-generated file is not visible.
The file is accessible through ADB shell and from other Android apps. If I make a copy of it with a file manager app, that copy is visible immediately. If I rename the original file, it becomes visible too. It then stays visible when renamed back to the original name.
I find it hard to believe this could be an issue with Pleco and not something else but it happens for me with Pleco on two completely different devices, and does not happen with a file created with another app (I tried Sound Recorder). There is nothing unusual about the file permissions (original file):
Device 1:
Code:
% adb shell getprop ro.build.fingerprint
google/occam/mako:5.0.1/LRX22C/1602158:user/release-keys
% adb shell ls -la /sdcard/settings*
-rw-rw---- root sdcard_r 12969 2015-06-01 00:34 settingsbackup-1433111666.xmlDevice 2:
Code:
% adb shell getprop ro.build.fingerprint
Xiaomi/dior/dior:4.4.4/KTU84P/5.3.27:user/release-keys
% adb shell ls -la /sdcard/settings*
-rw-rw---- root sdcard_r 9959 2015-06-01 00:40 settingsbackup-1433112037.xmlThe only other common point is the MTP client side (Windows 8.1 Update 1, can't test it with another OS at the moment) but an OS reboot does not resolve it either.
This might very well be unrelated to Pleco. Windows's MTP implementation is beyond redemption but as I'm out of ideas for the moment, I'd appreciate if anyone could confirm if they have this issue too.
alex_hk90
状元
Have you checked if the file appears using standard USB mass storage mode (rather than MTP, which I've always found a bit flaky)?
I'll have a look if it happens for me this evening - I need to fire up my old dual-boot Windows machine.
OK, so Pleco is innocent. 
This appears to be caused by a bug in Android, unfixed since 2012:
https://code.google.com/p/android/issues/detail?id=38282
Files written using the Java API suffer from this problem. Files written with the C API show up immediately. The user-side solution is to trigger a media rescan. A workaround that can be implemented in an app is to feed the newly-created file to the media scanner using the ACTION_MEDIA_SCANNER_SCAN_FILE intent. Implementation example here: http://stackoverflow.com/a/25099099
(Since 4.4 this needs to be done on a per-file basis, as too many apps worked around the bug by triggering a full media rescan and the intent to do that is now restricted to system apps.)
This appears to be caused by a bug in Android, unfixed since 2012:https://code.google.com/p/android/issues/detail?id=38282
Files written using the Java API suffer from this problem. Files written with the C API show up immediately. The user-side solution is to trigger a media rescan. A workaround that can be implemented in an app is to feed the newly-created file to the media scanner using the ACTION_MEDIA_SCANNER_SCAN_FILE intent. Implementation example here: http://stackoverflow.com/a/25099099
(Since 4.4 this needs to be done on a per-file basis, as too many apps worked around the bug by triggering a full media rescan and the intent to do that is now restricted to system apps.)
Thanks! This would fix this problem as well, it seems, but officially there is no UMS on these devices anymore, only MTP or PTP (well, I guess I could enable it manually with setprop sys.usb.config ... but I'd expect it to have fun side effects).
alex_hk90
状元
I can confirm I get the same issue with not being able to see the file via MTP in Windows 7 (64 bit).
Interestingly, if I change it to MSC (mass storage) then back to MTP then I can see the file - I guess this does a full rescan of the files at some point, maybe when mounting/unmounting the external SD card (it only shows me the external SD card in MSC, not the internal storage).
To sum up, these are the three most straightforward ways I know of to solve this problem from the user side by forcing a media rescan:
- Go to Settings → Developer options → Development tools → Media Provider → Scan SD Card. If you don't see Developer options, open Settings → About phone first and tap seven (7) times on Build number. Then, on the computer, press F5 in Windows Explorer to refresh the view.
- If you would rather use the shell (command-line) you can do the following with ADB:
adb shell am broadcast -a android.intent.action.MEDIA_MOUNTED -d file:///sdcard
As of Android 4.4 this generally shouldn't be possible according to the documentation; it works for me though, and there's no harm in trying. - Install a Play Store app that uses the per-file workaround I wrote about in the previous post but it recursively feeds all the files to it, one by one. Should work with any Android version.
(Note: I didn't test it, so use it at your own discretion).
Yeah, that function (the ACTION_IMAGE_CAPTURE intent) is unusually prone to getting screwed up by device manufacturers who try to get cute with their camera apps - Google doesn't enforce any consistency on that particular bit of Android API, they don't even seem to test it when they're validating new devices. (not just us who are frustrated by it - see this rant from well-known Android developer Mark Murphy)
At the moment the only good fix for this would be to do away with the system camera screen and rely on our own for taking still images, but then you'd lose access to a lot of device-specific features and optimizations, so our best suggestion for now is simply that you take your pictures in the camera app separately and then bring them up in Pleco with the image open command instead of 'take a picture.'
At the moment the only good fix for this would be to do away with the system camera screen and rely on our own for taking still images, but then you'd lose access to a lot of device-specific features and optimizations, so our best suggestion for now is simply that you take your pictures in the camera app separately and then bring them up in Pleco with the image open command instead of 'take a picture.'