Share your experience!
It looks like there's some sort of incompatibility with the Xperia Z5c and the Chrome Browser using the standard HTML5 Camera API. This works perfectly fine on my Xperia Z1c and Z3c.
The Z5c camera fails to work on every test page I've found so it's not an issue of website code.
Test Parameters:
Firmware: 32.0.A.6.152
Chrome Mobile Browser: 46.0.2490.76
Camera Software: Sony Camera 1.0.0 AND Sony Camera 2.0.0.
Steps to reproduce:
1. Go here: http://aaronsaray.com/demo/onlinephotobooth/ in Chrome Mobile Browser
2. You will be prompted to allow Use of Camera - Choose YES
3. Notice that the Camera usage icon disappears and fails to load properly on the web page above.
have you contacted them regarding this? http://aaronsaray.com/
how about if you use a different browser ?
It's not an issue with that particular website. It's a problem on ANY site that properly implements the HTML5 getUserMedia API when using Chrome and the Z5c
This same site works on Firefox Mobile on my Z5c.
Also, Mobile Chrome (same version) works fine on other devices (Z1c and Z3c).
I'm sorry to hear that but that's something you have to take with the camera app developer, it's not a Sony issue.
just changed to z5 from z2.
previously was able to use full resolution in 3rd party camera apps for z2.
but in z5, other apps only can use til 8MP (16:9), if one wants 3:4 then resolutiom will drop to 3MP
it should be sony's issue as they somehow close the api in z5, not allowing other app developers have access tothe full 23MP.
i hope it's only temporary and sony can solve this issue because honestly, sony image compression is far from satisfactory.
This is an app developer issue, what you should do is contact the app developers and suggest for them to get in contact with Sony.
This is NOT an app developer issue.
Sony are responsible for implementing the standard android camera APIs. Their implementation of those APIs is not returning the full list of resolutions supported by the camera.
This is a non-standard change to those APIs and sony have not documented this anywhere publicly that I can see.
Expecting every single third party developer to contact them is crazy. This is sony's issue to fix.
Is there anyone here who is actually able to get sony to look at this?
@uliwooly wrote:This is an app developer issue, what you should do is contact the app developers and suggest for them to get in contact with Sony.
I got another answer by developer trough Play Store review messege: