[FIX][STOCK][4.0.4][14/07]Working Camera + Video on 4.0.4 with non-stock kernels

[Tungstwenty]

Obsolete

This workaround was only relevant some time ago while custom kernels did not yet have updated sources from Samsung to work on 4.0.4 ROMs. This is no longer the case so this info is completely irrelevant now.


There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix for it.


Installation
Just take the CWM zip file and apply it on your ROM. It will leave a backup of the 2 files that will be replaced.

Removal
The Restore zip can be "installed" to remove the patched files and put back the original ones that were kept on your device.


Tested and working both for Camera preview and Video playback, on XWLPM.


Note: This is a temporary fix until the kernel devs have enough information to properly update their code, and when that happens this fix can be uninstalled.

 

[The Undertakerr]

Heyy Tungstwenty, another great fix by you!

Well done, it works great! Now also videoplayback works fine with siya on 4.0.4!

Now the only thing left not working on 4.0.4 with Siya is the bluetooth...

Thanks again!

 

[do3in]

he he he go 4.04 gooo!
Thanks man.

 

[danieldmm]

Hi @Tungstwenty
Time to go OUT of stock Kernel XWLPM and move to Siyha Kernel, thanks a lot my friend...
Cheers

 

[The Undertakerr]

Thanks again for the fix.

But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.

This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...

I tested this with all Siya kernels 3.3.2 and above.

Try this to reproduce this bug:

1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.

But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..

When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.

Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...

Can anybody try and see if they can reproduce this issue?

Thanks in advance...

EDIT: SOLVED by doing a wipe.

It must have been some old data from the nandroid data backup I restored.

Normally I don't post stuff like this if I'm not completely sure.

But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.

 

[john9]

Thanks for the tips!

 

[Prophet16]

Thanks again for the fix.

But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.

This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...

I tested this with all Siya kernels 3.3.2 and above.

Try this to reproduce this bug:

1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.

But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..

When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.

Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...

Can anybody try and see if they can reproduce this issue?

Thanks in advance...

I actually had that happen to me when i was on Neat Rom. Don't know what caused it but I ended up switching roms.

 

[Tungstwenty]

Thanks again for the fix.

But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.

This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...

I tested this with all Siya kernels 3.3.2 and above.

Try this to reproduce this bug:

1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.

But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..

When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.

Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...

Can anybody try and see if they can reproduce this issue?

Thanks in advance...

EDIT: SOLVED by doing a wipe.

It must have been some old data from the nandroid data backup I restored.

Normally I don't post stuff like this if I'm not completely sure.

But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.

Just did the test now and when I was about to post the results I saw your edit

I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.

BTW, was it a full wipe or wipe cache/dalvik?

 

[The Undertakerr]

Just did the test now and when I was about to post the results I saw your edit

I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.

BTW, was it a full wipe or wipe cache/dalvik?

I'm getting offtopic here, because it has nothing to do with your camera fix

But I'm still investigating the matter now as we speak.

When on Siya, only a full wipe solves the problem I have above.

Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.

Now the strange part: Also Dorimanxx Kernel solves my problem.

So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.

But Siya can't be the problem also, because when I fully wipe also Siya will work.

I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...

Sorry for the offtopic.

 

[Tungstwenty]

I'm getting offtopic here, because it has nothing to do with your camera fix

But I'm still investigating the matter now as we speak.

When on Siya, only a full wipe solves the problem I have above.

Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.

Now the strange part: Also Dorimanxx Kernel solves my problem.

So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.

But Siya can't be the problem also, because when I fully wipe also Siya will work.

I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...

Sorry for the offtopic.

I don't think it's offtopic

This is indeed very strange, but here's a possible explanation:
The custom kernels (Siyah, Dorimanxx, ...) each have their own tweaks; they're not exactly the same. While they might share lots of common changes and improvements, they do have different things hence the word "custom".
There's a possibility that the sequence of events to make the camera work is contained not only on the binaries (the ones in the zip file I posted), but also on some cached data that was already picked up when you first ran the camera app, which invoked a service, which in turn invoked a library, etc. Later, when reopening the camera, now with the "fixed" binaries, there might still be bad data that a particular kernel is not expecting. Even if you came from Siyah when initially running the camera app, the original libraries might have cached strange data that the kernel will no longer recognize even after the binaries are now in line with the kernel. And another kernel might have code that is lenient enough to still work with it.

I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.

 

[Krendelrus]

I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.

thanks a lot for the camera fix now I can use official 4.0.4 more often with my favourite kernel - Siyah

 

[cdaarif]

There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix

Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.

Sent from my GT-I9100 using xda app-developers app

 

[Tungstwenty]

Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.

I have worked on this fix using XWLPM as a secondary ROM (I'm still on XWLPG) but this should work both for LPM and LQ5.

 

[cdaarif]

Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.

Sent from my GT-I9100 using xda app-developers app

Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.


Sent from my GT-I9100 using xda app-developers app

 

[Tungstwenty]

I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.

Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.

This is just a fix for Camera + Video. I know bluetooth is also not working but as I posted before, I tried to fix it as well but don't think it's doable without changing the kernels. Kernel devs will have to find a way to fix it.

 

[marbutina]

Working bluetooth on LPM with stock Kernel and camera with your hack.

 

[Tungstwenty]

Working bluetooth on LPM with stock Kernel and camera with your hack.

If you're using stock kernel you can (should) uninstall my camera/video hack. It's only needed for custom kernels.

 

[marbutina]

Thanks.

 

[Krendelrus]

In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier

Well whaddaya know...

K3-9:
- Bluetooth now works for 4.0.4 ROMS

maybe his fix will work for S2 4.0.4 roms too

link to his site/news article
link to the newest hardcore note kernel source code

 

[The Undertakerr]

In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier



maybe his fix will work for S2 4.0.4 roms too

link to his site/news article
link to the newest hardcore note kernel source code

Thanks for the above info!

Best to repeat this message in the Siya thread, and/or send Gokhanmoral this info by PM. He might be able to use Hardcore's sources to fix bluetooth in Siya kernel...


Edit: I see you allready did that. Thanks again! Maybe soon we can have working bluetooth with a custom kernel, that would be great!