Quick Launch Camera Bug on JB

[piotrom87]

I found the next bug of Jelly Bean.

After Quick Launch, Camera doesn't start - it's only black screen.

You can see this bug here: http://www.youtube.com/watch?v=M2uEqdjaTyo

The Xperia P JB Quick Launch Camera bug we can see between 0:02 and 0:19 (black screen instead of camera view).

Correct camera run we can see between 0:20 and 0:31.

I tried to fix it by PCC and SUS...it doesn't help...

The problem comes sometimes (random), not always.

Sometimes I can run camera without problems.

If want to check this option on your phone - try to lock and run Quick Launcher 3-5 times.

I'm sure you see the problem persist.

[_alexdon_]

I have tried this on my phone and works great,I think you kept your hand on the camera,thats why it showed black screen where the objective is.But it took quite some time to shoot,maybe you really have a bug.For me works well everytime.

[piotrom87]

No,my hand it's not the problem.

Look at 2 things on the movie:

- in the first (bad) run: the camera doesn't start quick, after taping first we see the clock again and the next is camera app (what is '0' ?  in the right-down corner on the screen from 0:14), beside photo/movie switch)

- in the second (well) run: the camera run immediately - one second after taping

[Johan]

This is very strange since you say it happens randomly. Do you know if this always happen after reboot? Is the camera app running in the background when this happen?

[piotrom87]

The movie above was recorded by me on 6.2.A.0.400.

Now (6.2.A.1.100), I have the other problem:

http://talk.sonymobile.com/message/487205#487205

After reboot everything is OK (the first running of Quick Launch is always good).

Yes, the problem happens only when camera is running in background - when I force stop in phone settings, the first Quick Launch after that is everytime OK (I only noticed green lines for a while but it's not a problem).

Next times running? Is random (sometimes is fine, sometimes I get error).

[piotrom87]

Has anybody faced that problem?

May it be a hardware problem?