So after a reboot today I tested that once more and it really manifests that after closing aliendalvik the camera/flashlight does not work when called the first time.
Tested after reboot and only settings applet opened.
Ad started --> all works
AD closed --> on first try black screen, second try works
AD started and it repeats…
So 100% reproducible
1 Like
Thanks for testing this. We have updated the bug report.
1 Like
I’m seeing this also, and AD seems to have absolutely no impact on it. This happens on a freshly booted device.
- I boot with AD turned off (my default) --> Camera black
- Turn on AD --> Camera black
- Turn off AD --> Camera black
SFOS: 3.3.0.16
HW: Xperia 10 Dual-SIM
nemo@PGXperia10:~ $ jolla-camera
[W] unknown:0 - Focus mode selection is not supported
[W] unknown:0 - Focus mode selection is not supported
[W] unknown:0 - Focus mode selection is not supported
[W] unknown:0 - Focus mode selection is not supported
[W] unknown:0 - CameraBin error: "Failed to allocate required memory."
[W] unknown:0 - CameraBin error: "Internal data stream error."
(jolla-camera:25684): Tracker-WARNING **: 10:50:25.340: tracker-backend.vala:211: Falling back to bus backend, the direct backen d failed to initialize: Locale change detected (DB:en_GB.utf8, User/App:en_GB.utf-8)
nemo@PGXperia10:~ $ free -m
total used free shared buff/cache available
Mem: 2672 1174 661 24 836 1506
Swap: 1023 16 1007So for you it does not work also without touching AD… it’s good you are reporting this, I could not get this issue for days as I keept it off after a reboot (i am testing on an xa2).
However you seem to be confirming it also does not work after activating/deactivating AD. If that is 100% reproducible, it could be good starting point for debugging.
It’s even weirder: When running AD, I can display the camera image using Alien Dalvik Control’s “Camera” function. But while this is working, the native one still does not.
I mean I can switch between the Alien Dalvik Control window, see the camera picture, close that, open jolla-camera and the latter’s image still shows black. Close jolla-camera, open ADC again, image displayed OK.
1 Like
Another (maybe completely unrelated but yet to do with camera) observation:
from time to time I felt that my XA2 gets warm even not heavily used, just some browsing and mails open
did not really bother …
But this morning it got warm right after switching on
it was switched off and charged over night
I did my normal mail and browser check, felt it getting warm and shut down apps
then a few hours later I heard this well known sound, checked battery and it was down to 10% after maybe 5h
I checked with top and found the android process consuming 24% CPU
cameras+ 3297 21.1 0.6 153868 16444 ? Sl 01:46 160:33 /vendor/bin/hw/android.hardware.camera.provider@2.4-service
I opened camera app --> black window
switched to selfie mode and back --> cam working
checked with top, normal
temperature went down soon
Bump.
Any news on this?
What can I do to assist in debugging?
1 Like
Well, update to 3.4.0.24 solved this magically…
for the record, on my device (xa2) this is still present on 3.4.0.24
3 Likes
As @enrish I still have the problem with the camera. I have a XA2 (single SIM) with SFOS 3.4.0.24. Yesterday I tried to evoke the error. But it wasn’t possible. But after charging I tried the camera today morning and it didn’t work. So I did what @peterleinchen recomanded (in terminal on the phone):
devel-su -c kill -9 $(ps aux | grep .*android\.hardware.camera.* | tr -s ' ' | cut -f2 -d' '); killall -r .*camera.*;
I got the error:
kill: sending signal to 22552 failed: No process found
cameraserver(8354): Opteration not permitted
.*camera.*: no process found
But anyway afterwords the camera worked again.
What can I do to fix the camera problem? Or how I can help to solve it?
I wrote above command from memory.
Both kill needs to be executed as root!
So better to do devel-su first and then issue both commands.
As one-liner (updated):
devel-su; kill -9 $(ps aux | grep .*android\.hardware\.camera.* | grep -v grep | tr -s ' ' | cut -f2 -d' ') || kill -9 $(ps aux | grep .*android\.hardware\.camera.* | grep -v grep | tr -s ' ' | cut -f3 -d' '); killall -r .*camera.*; echo done; exit
Good, so android can server is/was the culprit.
No idea, this is up to @Jolla!
(I still believe in bad menory management or misuage from Android side…)
1 Like
Just got this on XA2 Ultra Dual SIM / SFOS 4.3.0.15.
While I was taking pictures, the main (rear) camera suddenly stopped working (black screen, no reaction to shutter button/icon). I rebooted the phone. After that, access to the rear camera disappeared completely and only the front camera was available and set as default (even pressing the “Torch/Flashlight” button was enabling the flash of the front camera). In Advanced Camera only one camera could be selected - the front one. In CSD Tool the rear camera could be selected for test but kept failing (black screen, spinning wheel, no reaction to pressing the shutter button). Multiple reboots didn’t change anything.
Strangely, what did help right away was turning off the Android support, then the main camera became available and normally working. And so far it continues to work, even after a few reboots, and with Alien Dalvik running.
1 Like
I’m late to the party here.
XA2 Plus.
I have been seeing this problem for a very long time, but it never quite bothered me enough to follow-up on it. For me it happens a few times a month. But when it happens, it typically happens a lot.
For a while, switching to the front camera and then back to the rear camera works-around it. But eventually, even that fails.
On a good day, the camera takes 10-60 seconds to start. Although I don’t think that that was the case when the bug first appeared.
A restart usually (always?) fixes it for me.
@ksandom: this bug has been through quite some history already, and it looks like this should now be working okay. The internal bug that was tracked against it has also been marked as resolved since 4.0.1.
Would you mind please creating a new bug describing exactly what the issue is that you’re experiencing? This would be a big help to ensure different issues don’t get mixed together.
In the meantime, I’ve tagged this bug as “fixed”, but if there are strong objections that the original bug as described has not been fixed, then please say.
Hi @flypig, when marking the bug as fixed, please provide root cause and/or fix which was applied so we can track it later if the issue pops back up. A detailed bug report deserves a root cause analysis and fix in my humble opinion
Thank you!
Yes, it is good being able to jump directly to the solution.
As there are hundreds of bug reports, it’s a lot of work. Maybe we should more often ask the OP to mark as solved and eventually edit the 1st post to sum up?
I get that putting together a good bug report isn’t straightforward, and we do our best to respect that effort (we certainly appreciate it). As such I generally do my best to provide feedback, and specifically links to fixing commits, where I can. Unfortunately this isn’t always possible.
In this case, Jolla’s testing team were able to reliably reproduce the bug. Certain potential causes were investigated and ruled out. Over the period of two releases significant changes were made to the camera stack, particularly as it relates to Android App Support. In subsequent testing it wasn’t possible to reproduce the issue.
Are you still experiencing the bug @Swayer?
I’d definitely encourage this, yes.
@flypig This bug is not fixed. Camera and flashlight still work hit-or-miss when Android App Support is enabled.
With it disabled, they work all the time.
Xperia XA2, Sailfish 4.4.
1 Like
Hi @Idesmi, thanks for checking this. Would you mind providing a bit more detail just so I can tally it with our internal bug report (e.g. the steps you go through to reproduce it, the exact outcome that you get), please?
Can you give advice on what evidence migh be useful to collect?