FORUMS
Remove All Ads from XDA

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

1,827 posts
Thanks Meter: 4,550
 
Thread Closed Email Thread
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 Following 61 Users Say Thank You to Tungstwenty For This Useful Post: [ View ] Gift Tungstwenty Ad-Free
 
 
14th July 2012, 08:32 PM |#2  
Senior Member
Thanks Meter: 175
 
More
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!
The Following User Says Thank You to The Undertakerr For This Useful Post: [ View ] Gift The Undertakerr Ad-Free
14th July 2012, 09:27 PM |#3  
Senior Member
Flag Timisoara
Thanks Meter: 25
 
More
he he he go 4.04 gooo!
Thanks man.
14th July 2012, 09:56 PM |#4  
danieldmm's Avatar
Senior Member
Flag France
Thanks Meter: 11,884
 
Donate to Me
More
Hi @Tungstwenty
Time to go OUT of stock Kernel XWLPM and move to Siyha Kernel, thanks a lot my friend...
Cheers
14th July 2012, 11:26 PM |#5  
Senior Member
Thanks Meter: 175
 
More
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.
The Following User Says Thank You to The Undertakerr For This Useful Post: [ View ] Gift The Undertakerr Ad-Free
15th July 2012, 12:07 AM |#6  
Account currently disabled
Thanks Meter: 267
 
More
Thanks for the tips!
The Following User Says Thank You to john9 For This Useful Post: [ View ] Gift john9 Ad-Free
15th July 2012, 02:00 AM |#7  
Prophet16's Avatar
Senior Member
Flag Fremont, CA
Thanks Meter: 19
 
More
Quote:
Originally Posted by 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...

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.
15th July 2012, 09:21 AM |#8  
Tungstwenty's Avatar
OP Senior Member
Thanks Meter: 4,550
 
Donate to Me
More
Quote:
Originally Posted by 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.

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?
15th July 2012, 01:42 PM |#9  
Senior Member
Thanks Meter: 175
 
More
Quote:
Originally Posted by Tungstwenty

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.
15th July 2012, 06:04 PM |#10  
Tungstwenty's Avatar
OP Senior Member
Thanks Meter: 4,550
 
Donate to Me
More
Quote:
Originally Posted by The Undertakerr

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.
The Following 4 Users Say Thank You to Tungstwenty For This Useful Post: [ View ] Gift Tungstwenty Ad-Free
15th July 2012, 06:41 PM |#11  
Senior Member
Thanks Meter: 476
 
More
Quote:
Originally Posted by 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.

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

Tags
4.0.4, camera, fix, stock, video
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes