I used to upload and download my photos fine from my samsung mobile phone. This is being showed to me since the past 5 days all of a sudden.
Is it really a problem of my phone ??
this post was submitted on 12 May 2026
34 points (94.7% liked)
techsupport
3132 readers
14 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Midori is indeed Firefox based. As @lordbritishbusiness@lemmy.world mentioned, it might be worth quickly trying to switch to desktop mode (in the browser menu).
If that doesn't work, try switching to Brave.
If that doesn't work either, ~~consider finding a new service, honestly, as this kind of user unfriendliness shouldn't be acceptable.~~ try open an issue here.
Thanks ๐๐
Might want to specify that it didn't work with Midori, but it worked with Brave.
Also that the "not powerful enough" error be updated to the actual issue. I seriously don't believe power is part of the reason here, but I'm open to being proved wrong.
It's opening on Brave, but the photos are not uploading.
Blocking html5 canvas improves privacy. The browser might be doing it due to that, in which case it can probably be allowed per site. Couldn't tell you how to do it in brave cause I don't like/use Brave, neither the software nor the Corp. Sorry. Could probably find something online when looking for 'Brave Android allow html5 canvas' or smth.
On Midori, it keeps on rolling. But on brave, it opened asap.
Any problem with Midori ??๐ค๐ค๐ค
The cynical possibility: perhaps due to being Firefox/Gecko-based, which usually entails being privacy-oriented
The statistical possibility: market share for Chromium browsers is so much bigger than Gecko's that developers didn't bother to implement compatibility after an update - or are experimenting to see if it's worthy it
The hopeful possibility: it was a glitch, the site or the browser having updated something that changed the user-agent or the expected one, and the site didn't know what to do with the current one.
Whatever might be the reason, the developers ought to have taken care of the browser aspect.