905153 - Photos received via Bluetooth sharing not appearing in Gallery because the file name begins with '.'

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Bluetooth, defect)

Description

[Ben Francis [:benfrancis]]

If I share a photo from the Facebook or Gallery app on an Android phone via bluetooth I can receive the file in Firefox OS, but it doesn't seem to be persisted and doesn't appear in the Gallery app. Is this expected behaviour?

Discovered during dogfooding Geeksphone 1.1 build on a Keon.

Comment 1

[Eric Chou [:ericchou] [:echou]]

Hey Ben,

AFAIK, Gallery app won't handle large-size and high-resolution photos because of lack of memory. Would you mind checking if there is a warning 

"Content JS WARN at app://gallery.gaiamobile.org/shared/js/mediadb.js:1711 in metadataError: MediaDB: error parsing metadata ...... Ignoring high-resolution image ......"

right after receiving the photo? Or maybe you could just tap the notification on notification center and see if the "Image is too large to display on this device" dialog prompts. ;)

Thanks in advance.

Comment 2

[Ben Francis [:benfrancis]]

If I send a high resolution JPEG image from the gallery app on Android, the transfer completes. When I tap the notification I see the message "Image is too large to display on this device".

If I send a low resolution JPEG or GIF file from the gallery app on Android, the transfer completes, I can view the image, but then I get a message saying "Can not open unknown media type: /emmc/downloads/bluetooth/filename.jpeg" though the file is viewable and is saved in the gallery.

If I share a photo from the Facebook app on Android, the transfer completes, I can see the image, I see the same unknown media type error message but then when I open the gallery the photo is not displayed.

So it seems there are two issues here:

1) Showing the unknown file type error message even when it's not necessary
2) Some issue specific to photos from the Facebook app that I haven't been able to reproduce elsewhere.

I don't see any errors on the command line.

Comment 3

[Eric Chou [:ericchou] [:echou]]

Hi Ben,

Thanks for your help.

(In reply to Ben Francis [:benfrancis] from comment #2)
> If I send a high resolution JPEG image from the gallery app on Android, the
> transfer completes. When I tap the notification I see the message "Image is
> too large to display on this device".
> 

This is as expected.

> If I send a low resolution JPEG or GIF file from the gallery app on Android,
> the transfer completes, I can view the image, but then I get a message
> saying "Can not open unknown media type:
> /emmc/downloads/bluetooth/filename.jpeg" though the file is viewable and is
> saved in the gallery.

Confirmed. When you open the received photo by tapping the notification, you will be able to see the photo, but the error message will appear after pressing 'Home' key. On the other hand, if users click the back button "<-" on the left-top corner of the UI, then no error message will be seen.

> If I share a photo from the Facebook app on Android, the transfer completes,
> I can see the image, I see the same unknown media type error message but
> then when I open the gallery the photo is not displayed.
> 

Confirmed. It happens because the file name of the photo retrieved from Facebook app has prefix '.', and MediaDB ignores see these as hidden files. Please refer to Bug 838179 for related discussion.

Nevertheless, I think any photos shared via Bluetooth should be able to be viewed in Gallery app since these transfer requests are all confirmed by users. I'm going to make a patch for this.

> So it seems there are two issues here:
> 
> 1) Showing the unknown file type error message even when it's not necessary
> 2) Some issue specific to photos from the Facebook app that I haven't been
> able to reproduce elsewhere.
> 
> I don't see any errors on the command line.

I'll file a bug for issue (1) and use this for tracking issue (2).
Thanks again, Ben.

- Eric

Comment 4

[Eric Chou [:ericchou] [:echou]]

Let's wait for David's feedback to bug 908140 then we'll know how we should deal with this bug.

Comment 5

[Eric Chou [:ericchou] [:echou]]

Based on David's feedback on bug 908140 comment 4, the more appropriate solution should be the patch of bug 838179. If we want to solve this in FxOS v1.1, we should unify the behaviour of showing hidden files. Therefore I explained the circumstances at bug 838179 comment 12 and nominated that bug as a leo+. Let's wait for release drivers deciding if we should fix this in v1.1.

Comment 6

[Eric Chou [:ericchou] [:echou]]

(In reply to Eric Chou [:ericchou] [:echou] from comment #5)
> Based on David's feedback on bug 908140 comment 4, the more appropriate
> solution should be the patch of bug 838179. If we want to solve this in FxOS
> v1.1, we should unify the behaviour of showing hidden files. Therefore I
> explained the circumstances at bug 838179 comment 12 and nominated that bug
> as a leo+. Let's wait for release drivers deciding if we should fix this in
> v1.1.

Since the nomination of bug 838179 failed, media files started with a period will be ignored by mediadb in gaia:v1-train. By the way, those files can be viewed in gaia:master (bug 838179).

Mark this as resolved won't fix.