Photos Saving and Sharing on Android Not Working

android-mobile

#1

This used to work, now saves as a blank image on the device, sharing shows black background when attempting to share as well, has this been reported?


#2

It's working fine for me. What versions of PMS (and OS) and the Android App are you using?


#3

Sorry should state it works fine over local wifi but does not work over mobile data connections. Same issue on latest android app as well 5.0.0.737. Synology server running 1.2.2.2857


#4

Works for me over mobile too. Can you recreate the problem then get me the Android app log and the PMS log?


#5

Attached both logs
Re-created the problem over mobile 4g connection when saving an image locally to the phone. Comes up as a blank image not viewable. (see attached photo) (same issue on 2 different android phones (htc 10, samsung s7)
Then re-created a working save over local wifi. image saved fine to the same device location.! (see attached photo)

(/uploads/default/original/3X/5/7/570244ddb3c2dd8f12fb63988e1edf5dc7f8a406.png “”)


#6

Has this issue ever been fixed?
Experiencing the exact same problem.
Have Nexus 6P and Google Pixel XL and on both devices "Photos Saving and Sharing" while away from the Plex Server is not working. (Note: when saving creates a file with 0 Bytes!)
Plex on Android version 5.5.0.227 (a6afa533)


#7

SOLUTION?
i was having same problem here,
on wifi (same lan as plex) no problem. on mobile data, problem of file being 0 bytes after saving.

i was able to save pictures before. but then i enabled upload limit on plex server
then the saved files on android became 0 bytes.

when i disabled the upload limit i was able to ave good pictures again.

some lines in plex logs pointed me to my solution:
Mar 31, 2017 14:46:43.577 [15984] WARN - Streaming Resource: Bandwidth exceeded: 2147483647 kbps > 12000 kbps
Mar 31, 2017 14:46:43.577 [15984] ERROR - Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data

something wrong in bandwidthlimiter when uploading photo's to android device?


#8

I seem to be having the same issue. Save saves a 0 byte image. Sharing also "shares" a 0 byte file.


#9

sadly android has lots of bugs like this and little acknowledgement from the plex staff even with logs provided


#10

I'm having the same problem on my Note 5


#11

Still having the exactly same problem. And isn't only on mobile data, but also on Wifi when not on local network.

Please Plex Team :hushed:


#12

Any update on this issue? I experience the same thing .. browse to photos in the Android app, select desired photo, select the options menu (three vertical dots), select save and only a 0 (zero) byte 'file' is saved.

My setup:
Plex Media Server for Windows version 1.11.0.4666-fc63598ba
Plex Android app version 6.11.3.3147 (bb34b27a)


#13

Hi guys. I wasn't following this old thread. I am now able to reproduce the issue. I'll let the devs know.


#14

Any updates regarding this issue? I am experiencing it on my Samsung Galaxy S7 Edge, attempting to download images from my Plex server.


#15

Same here. Samsung Galaxy J3 (2016)


#16

This is a known issue. It has to do with the bandwidth limit setting in Plex Media Server.

Settings \ Server \ Remote Access \ Limit remote stream bitrate

Turn this off and downloading will work.


#17

I am not seeing this as a workaround…

I don’t have an upload limit set, “Original(no limit)” , and I am still seeing this issue

The logs would have you believe that I have it set at 80Mbps

Anyway, attached are a snapshot of debugs logs, maybe it can help


#18

Do you have the Internet upload speed setting enabled at 80 Mbps? That could also be causing this issue.


#19

It is set at 100Mbps, what is default or how to set no limit becuase if you set it to “0” plex complains about it…


#20

The default is no limit, which is the same as 0 or having it blank. There shouldn’t be an issue using 0. I have mine set to 0 and it streams just fine. If you are getting an error when trying to set that to 0, you might have another issue.