Hi,
I have a problem with using Open Camera App. I save the photos to SD-Card. When I download those photos to a Windows 10 desktop, the size is 0kb and I can't open the file.
On my Sony Xperia X Compact I can handle the photos without problems and I can even send them per email.
Any solution for that?
Yours
Mario
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the same problem. Only solution for me is to upload them via owncloud to my server and then sync it to the pc via owncloud. I don't know how to reproduce this bug because some images have a size but some have not.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure why this is - some things to try: Does it happen with any other 3rd party camera apps? Does the problem still exist after rebooting the phone?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Mark,
Okay, it's the same with Camera MX. Called the Sony Support and they say I should contact Microsoft because it happens when I want to transfer the photos. Seems like no one wants to be responsible.
Do you have any ideas?
Yours
Mario
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found this page via Google and figured I'd add to it. I've tried out a handful of different camera apps and only have this issue when using Open Camera.
When I save to the internal storage photos reflect their proper file size and are viewable when connected to a PC. When I save to the SD card the photos have a file size and are viewable on the device, but appear as 0kb files with no image data when connected to a PC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It started when I updated to Cyanogenmod 13 (android 6), also happens with Lineage 14.1 (android 7). Cyanogenmod 12 (android 5) didn't have this issue.
OpenCamera set up using StorageAccessFramework to save direct to SD.
When connected by MTP file size reads as 0 bytes.
Photos open fine in any photo editor on the phone.
The phone files app can copy the files to another location which corrects the size when viewed by MTP.
When phone is booted to recovery (TWRP in my case) and connected via MTP files show correct size without having to copy them using the phone.
When you wipe out the media cache on the phone once the cache rebuilds the files show the correct size via MTP, but new photos taken will be 0 bytes.
Hope some of this info helps debugging this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I too have this problem with Win7pro and Nokia 6. The Open Camera photos goes to SD (128GB 10-U3) and in the phone they look and work OK in every app, but when I try to copy the photos via USB (transfer files mode) then the Windows FileManager reports 0 bytes for every Open Camera photo, I can copy them to PC but the copied files are empty (when examined by Hex editor). However, when I use ZarchiverPro in the phone to create a 7z archive of photos and copy that to PC and extract the archive there, then the photos are good. Also, when I create a Gmail draft mail in the phone that has a photo as an attachement, then when I save that attachement from the draft on a PC the image is also OK.
I hope this issue could be resolved soon since The Open Camera is so very very good camera software.
With Best Regards,
Tmo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have thesame problem with my Galaxy S3 and lineage 14. I can use my pc to send the "unreadable files" and as soon as they are loaded into the email client, I can see the proper icon and open the files normally. But trying to see the files direclty using file explorer in win 10 - nothing!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I faintly remember this probem from the time before the Web era (so before 1995) it was discussed on Usenet. It had to do with some small difference in how Unix/Mac and Windows hande jpg files (or files in general), if I remember correctly one byte had to be added to the very end of the jpg file (using HEX editor in Unix) but I do not remember what that byte was nor was there any other changes.
Last edit: Anonymous 2017-10-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
follow on from 24 mins ago; using the S3 stock file explorer I can copy the "PC unreadable files" from the SD to internal memory, and there the PC open them normally.If I use the PC to copy the files to internal memory, they are still unreadable to the PC?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For additional testing, I installed the Windows USB drivers that comes with the Nokia 6. When the the phone is connected to a PC via USB then those drivers install automatically (unless the user has disabled automatic installations in Windows). Then rebooted the Win7pro. This had no effect, the 0 byte photos are still 0 bytes when inspected via USB using Windows Explorer.
Then I took the mSDXC out from the phone and put it into an USB adapter (tried three diffrent type of adapters). This way there is not any 0 byte photos, all look & behave normally, with all the three adapters. However, this is not a solution to this problem either because there is too much work to first take the card out of the phone, then transfer the photos using USB adapter stick and finally to put back to the phone. Really, all the tricks mentioned in this thread are too time consuming and in some case can also require more memory that there is avaiable.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Running 1.41.1 camera now but the problem still persists for me (I'm the poster from 2017-10-02) - however I've noticed that since 10th October or so the camera now works correctly on some photos (correct size when viewed in windows explorer) but not others (0 bytes). On a day out I took about 20 photos and 50% of them show the correct size, I can't see any pattern to that behaviour though. Previously every photo showed 0 bytes.
The most weird thing is in one instance 2 of my photos were taken a couple of seconds apart. The first image reads as 0 bytes, the second image reads its proper size.
I don't know if any work was done to resolve this issue, but something seems to be at least partially working.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, I just exported the Contacts from Nokia 6 (OS v7.1.2), from the stock Contacts app to the Internal memory. When I inspect that 0000x.vcf from Win7 it appears to have the correct size. BUT, I run the FolderSync app on the phone that collects various files from the Internal memory into the SDcard (so that I can simply backup one directory) and the copy that the FolderSync wrote to the SDcard appear as 0 bytes from Win7. So, could this be an issue in how the Android v.7.1.1 and v.7.1.2 handles the SDcard.
Another finding, when I manually Rename a problem file (using ZArchive app on the phone) then that file will appear to have the correct size when inspected on Win7.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I connected my phone for photo transfer and the folder for OpenCamera (This PC\A0001\Internal storage\DCIM\OpenCamera) is not there but when I use an app called FileManager on the phone it is. I selected all the photos from:
This PC\A0001\Internal storage\DCIM\OpenCamera
and copied them to:
This PC\A0001\Internal storage\DCIM\100ANDRO
where I could then access them on Windows 10.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a similar issue. I store the open camera images on the SD card, and all was well up to 2nd Dec 2017. Up to that date I could copy the jpg files to my desktop (win 10 pro) and they opened no problems. However, after 2nd Dec 2017 none of the open-camera jpg files will open on the Desktop computer, with any programme - even gimp will not open them. if I email a jpg file from the phone to myself then it will open OK with any of the programmes on my desktop computer.
It seems likley that an update either to open-camera, or to the phone android programme, has screwed things up?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-05-22
I'm having the same problem with Sony XPeria M4 Aqua.
Phtotos saved on the SD card can be viewed normally on phone.
Can be send via email, then downloaded to PC, then they work normally.
Can pick out SD card from phone, transfer it into an adapter, then PC handles pictures on it normally.
So, every way works, except the most simple: connecting the phone to the PC via USB cable and handle/transfer pictures on/from SD card (taken by Open Camera). Photos show 0 byte and can't open.
Videos don't have the problem, photos saved on the internal storage of the phone don't have it neither. Just photos on the SD card.
Do anyone have a solution for it since the last post, or has the developer any advice?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-06-08
go to settings/apps (tick show system apps) go to media storage and clear data, reboot android to recreate data. What happens is it will recreate database of your media files stored on your device and sd card and properly propagate it to MTP host which will then correctly show it to you PC.
Opencamera app probably does someting wrong when saving picture so this database gets corrupted. (i would say it saves 0bytes file first and then rewrites it with actual picture, but media storage gets fooled by this).
You need to do this every time you want to transfer(backup) files... still better solution than copying to internal storage or using zip etc...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The code Open Camera uses in typical cases (no std photo mode, no post-processing options like auto-stabilise or photo stamp) is basically:
OutputStream outputStream = new FileOutputStream(picFile);
outputStream.write(data);
outputStream.close();
(from ImageSaver.saveSingleImageNow())
Not sure what's going wron I'm afraid.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-11-21
Saving images and videos from Open Camera to SD card. Files show up in W10 with 0 bytes. Then I unmount the SD card and remount it again. Problem solved! All files get the actual size in W10, and opens correctly in suitable software. Not sure yet why, but have to remount SD card every time I save one or more images/videos. The same error does not happen to videos saved from dashcam app (Autoby) though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-02-22
Huh....I also encounter the same issue. Need to remount the SD card every time too. I am using I9100G Galaxy S2 (LineageOS 13). The default camera apps doesn't have this problem when saving to sdcard.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-03-29
This is a problem with a SD card handling in Android 7.1 On Android 5.1 everything works fine. On 7.1 however, i can save photo on SDcard (with SAF turned on) and then i can use this file as i want. But when connecting to PC, Windows says 0B in all files writen this way.
Only way to go around that, is UMS mode - which mounts your SDcard as a removable storage in your PC. Then your SD is fully accesible in PC and you can download the photos. BUT....BUT when you disconnect USB cable, then UMS mode switches off and SD card should be mounted back in the android. But it is not, you have to restart the phoone in order to get access to the files again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi,
I have a problem with using Open Camera App. I save the photos to SD-Card. When I download those photos to a Windows 10 desktop, the size is 0kb and I can't open the file.
On my Sony Xperia X Compact I can handle the photos without problems and I can even send them per email.
Any solution for that?
Yours
Mario
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi,
I have the same problem. Only solution for me is to upload them via owncloud to my server and then sync it to the pc via owncloud. I don't know how to reproduce this bug because some images have a size but some have not.
I'm not sure why this is - some things to try:
Does it happen with any other 3rd party camera apps?
Does the problem still exist after rebooting the phone?
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Mark,
Okay, it's the same with Camera MX. Called the Sony Support and they say I should contact Microsoft because it happens when I want to transfer the photos. Seems like no one wants to be responsible.
Do you have any ideas?
Yours
Mario
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I found this page via Google and figured I'd add to it. I've tried out a handful of different camera apps and only have this issue when using Open Camera.
When I save to the internal storage photos reflect their proper file size and are viewable when connected to a PC. When I save to the SD card the photos have a file size and are viewable on the device, but appear as 0kb files with no image data when connected to a PC.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Also have this issue, Sony Xperia Z.
It started when I updated to Cyanogenmod 13 (android 6), also happens with Lineage 14.1 (android 7). Cyanogenmod 12 (android 5) didn't have this issue.
OpenCamera set up using StorageAccessFramework to save direct to SD.
When connected by MTP file size reads as 0 bytes.
Photos open fine in any photo editor on the phone.
The phone files app can copy the files to another location which corrects the size when viewed by MTP.
When phone is booted to recovery (TWRP in my case) and connected via MTP files show correct size without having to copy them using the phone.
When you wipe out the media cache on the phone once the cache rebuilds the files show the correct size via MTP, but new photos taken will be 0 bytes.
Hope some of this info helps debugging this.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I too have this problem with Win7pro and Nokia 6. The Open Camera photos goes to SD (128GB 10-U3) and in the phone they look and work OK in every app, but when I try to copy the photos via USB (transfer files mode) then the Windows FileManager reports 0 bytes for every Open Camera photo, I can copy them to PC but the copied files are empty (when examined by Hex editor). However, when I use ZarchiverPro in the phone to create a 7z archive of photos and copy that to PC and extract the archive there, then the photos are good. Also, when I create a Gmail draft mail in the phone that has a photo as an attachement, then when I save that attachement from the draft on a PC the image is also OK.
I hope this issue could be resolved soon since The Open Camera is so very very good camera software.
With Best Regards,
Tmo
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Just a quick note, yesterday my Nokia 6 had the 7.1.1 firmware, now I updated to 7.1.2 and the 0 byte photos issue is still the same.
With Best Regards,
Tmo
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I have thesame problem with my Galaxy S3 and lineage 14. I can use my pc to send the "unreadable files" and as soon as they are loaded into the email client, I can see the proper icon and open the files normally. But trying to see the files direclty using file explorer in win 10 - nothing!
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I faintly remember this probem from the time before the Web era (so before 1995) it was discussed on Usenet. It had to do with some small difference in how Unix/Mac and Windows hande jpg files (or files in general), if I remember correctly one byte had to be added to the very end of the jpg file (using HEX editor in Unix) but I do not remember what that byte was nor was there any other changes.
Last edit: Anonymous 2017-10-14
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
follow on from 24 mins ago; using the S3 stock file explorer I can copy the "PC unreadable files" from the SD to internal memory, and there the PC open them normally.If I use the PC to copy the files to internal memory, they are still unreadable to the PC?
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
For additional testing, I installed the Windows USB drivers that comes with the Nokia 6. When the the phone is connected to a PC via USB then those drivers install automatically (unless the user has disabled automatic installations in Windows). Then rebooted the Win7pro. This had no effect, the 0 byte photos are still 0 bytes when inspected via USB using Windows Explorer.
Then I took the mSDXC out from the phone and put it into an USB adapter (tried three diffrent type of adapters). This way there is not any 0 byte photos, all look & behave normally, with all the three adapters. However, this is not a solution to this problem either because there is too much work to first take the card out of the phone, then transfer the photos using USB adapter stick and finally to put back to the phone. Really, all the tricks mentioned in this thread are too time consuming and in some case can also require more memory that there is avaiable.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
This is now fixed in version 1.41.1 (21 October 2017).
Thank you very much!
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Running 1.41.1 camera now but the problem still persists for me (I'm the poster from 2017-10-02) - however I've noticed that since 10th October or so the camera now works correctly on some photos (correct size when viewed in windows explorer) but not others (0 bytes). On a day out I took about 20 photos and 50% of them show the correct size, I can't see any pattern to that behaviour though. Previously every photo showed 0 bytes.
The most weird thing is in one instance 2 of my photos were taken a couple of seconds apart. The first image reads as 0 bytes, the second image reads its proper size.
I don't know if any work was done to resolve this issue, but something seems to be at least partially working.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Oh, I just exported the Contacts from Nokia 6 (OS v7.1.2), from the stock Contacts app to the Internal memory. When I inspect that 0000x.vcf from Win7 it appears to have the correct size. BUT, I run the FolderSync app on the phone that collects various files from the Internal memory into the SDcard (so that I can simply backup one directory) and the copy that the FolderSync wrote to the SDcard appear as 0 bytes from Win7. So, could this be an issue in how the Android v.7.1.1 and v.7.1.2 handles the SDcard.
Another finding, when I manually Rename a problem file (using ZArchive app on the phone) then that file will appear to have the correct size when inspected on Win7.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Perhaps the app compiler (or whatever it is that is used to write apps) has been updated and not all developers are using the latest version.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I connected my phone for photo transfer and the folder for OpenCamera (This PC\A0001\Internal storage\DCIM\OpenCamera) is not there but when I use an app called FileManager on the phone it is. I selected all the photos from:
This PC\A0001\Internal storage\DCIM\OpenCamera
and copied them to:
This PC\A0001\Internal storage\DCIM\100ANDRO
where I could then access them on Windows 10.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I have a similar issue. I store the open camera images on the SD card, and all was well up to 2nd Dec 2017. Up to that date I could copy the jpg files to my desktop (win 10 pro) and they opened no problems. However, after 2nd Dec 2017 none of the open-camera jpg files will open on the Desktop computer, with any programme - even gimp will not open them. if I email a jpg file from the phone to myself then it will open OK with any of the programmes on my desktop computer.
It seems likley that an update either to open-camera, or to the phone android programme, has screwed things up?
I'm having the same problem with Sony XPeria M4 Aqua.
Phtotos saved on the SD card can be viewed normally on phone.
Can be send via email, then downloaded to PC, then they work normally.
Can pick out SD card from phone, transfer it into an adapter, then PC handles pictures on it normally.
So, every way works, except the most simple: connecting the phone to the PC via USB cable and handle/transfer pictures on/from SD card (taken by Open Camera). Photos show 0 byte and can't open.
Videos don't have the problem, photos saved on the internal storage of the phone don't have it neither. Just photos on the SD card.
Do anyone have a solution for it since the last post, or has the developer any advice?
go to settings/apps (tick show system apps) go to media storage and clear data, reboot android to recreate data. What happens is it will recreate database of your media files stored on your device and sd card and properly propagate it to MTP host which will then correctly show it to you PC.
Opencamera app probably does someting wrong when saving picture so this database gets corrupted. (i would say it saves 0bytes file first and then rewrites it with actual picture, but media storage gets fooled by this).
You need to do this every time you want to transfer(backup) files... still better solution than copying to internal storage or using zip etc...
The code Open Camera uses in typical cases (no std photo mode, no post-processing options like auto-stabilise or photo stamp) is basically:
OutputStream outputStream = new FileOutputStream(picFile);
outputStream.write(data);
outputStream.close();
(from ImageSaver.saveSingleImageNow())
Not sure what's going wron I'm afraid.
Saving images and videos from Open Camera to SD card. Files show up in W10 with 0 bytes. Then I unmount the SD card and remount it again. Problem solved! All files get the actual size in W10, and opens correctly in suitable software. Not sure yet why, but have to remount SD card every time I save one or more images/videos. The same error does not happen to videos saved from dashcam app (Autoby) though.
Huh....I also encounter the same issue. Need to remount the SD card every time too. I am using I9100G Galaxy S2 (LineageOS 13). The default camera apps doesn't have this problem when saving to sdcard.
This is a problem with a SD card handling in Android 7.1 On Android 5.1 everything works fine. On 7.1 however, i can save photo on SDcard (with SAF turned on) and then i can use this file as i want. But when connecting to PC, Windows says 0B in all files writen this way.
Only way to go around that, is UMS mode - which mounts your SDcard as a removable storage in your PC. Then your SD is fully accesible in PC and you can download the photos. BUT....BUT when you disconnect USB cable, then UMS mode switches off and SD card should be mounted back in the android. But it is not, you have to restart the phoone in order to get access to the files again.