Develop Bugs

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

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.

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!

he he he go 4.04 gooo!
Thanks man.

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

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.

Thanks for the tips!

The Undertakerr said:
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...
Click to expand...
Click to collapse
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.

The Undertakerr said:
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.
Click to expand...
Click to collapse
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?

Tungstwenty said:
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?
Click to expand...
Click to collapse
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.

The Undertakerr said:
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.
Click to expand...
Click to collapse
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.

Tungstwenty said:
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.
Click to expand...
Click to collapse
thanks a lot for the camera fix now I can use official 4.0.4 more often with my favourite kernel - Siyah

Tungstwenty said:
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
Click to expand...
Click to collapse
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

cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Click to expand...
Click to collapse
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 said:
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
Click to expand...
Click to collapse
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 said:
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.
Click to expand...
Click to collapse
cdaarif said:
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Click to expand...
Click to collapse
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.

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

marbutina said:
Working bluetooth on LPM with stock Kernel and camera with your hack.
Click to expand...
Click to collapse
If you're using stock kernel you can (should) uninstall my camera/video hack. It's only needed for custom kernels.

Thanks.

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
hardcore said:
Well whaddaya know...
K3-9:
- Bluetooth now works for 4.0.4 ROMS
Click to expand...
Click to collapse
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

Krendelrus said:
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
Click to expand...
Click to collapse
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!

[FIX][20-NOV] Omega v33.1 and v33.2 (+stockXXELK4) GPS fix

**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.1+v33.2 ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far).
**Where you can use it ?**
Tested so far on Omega v33.1, confirmed working on Omega v33.2 as well including some other XXELK4 stock/custom based ROMs
Not needed for Omega >=v33.3 or patched stock ROM XXELK4
**Just press THANKS if it worked**
Thanks to Omegas Team.

All you need to do to fix is flash a different kernel

Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Incorrect. Lots of people running 4.1.2 on various kernels and still facing the same problem. Myself included having tried 3 different kernels.
Sent from my GT-I9300 using xda app-developers app

Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Not helping. Already tried. This is nearly annoying like the hello hello bug. Not all got it and every phone needs a different fix.
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member

Chris_84 said:
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Click to expand...
Click to collapse
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
*sorry* I just flashed also another modem just prior to that fix, see 1st post...however when I flashed different modem before I was trying to fix GPS issue, it didn't help at all

shaarky said:
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
Click to expand...
Click to collapse
Don't know for sure but think maybe the video fix who install the old libs brake GPS again but I'm not sure. As I wrote in omega thread. After dirty flash it works perfect even with custom kernel and after installing the video fix it brake down again.
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member

It's working so far.
I haven't flashed fix video but installed siyah so sooner or later I'll need the video fix.
I'll let you know how it goes.
Sent from my GT-I9300 using xda app-developers app

shaarky said:
**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.x ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far). Tested so far on Omega v33.1 only, but should work on v33.2 as well including some other XXELK4 stock based ROMs
**Report and let others know if this helps or not and/or press THANKS**
Thanks to Omegas Team.
Click to expand...
Click to collapse
Tried all what you have said you had tried and also no luck - still having GPS problems.
Installed the fix.
Before installation, using Waze, I used to get a fix within 5 seconds, and then I used to lose the signal after 3-5 Mins. max.
After installation - got a fix same within ~5 secs, and I kept it on for about 10 mins and I had no signal loss.
I will try it further on my way home (about 20-30 min drive) and post results.
Thanks alot - hope this might just do it!
***EDIT***
Drove 20-25 mins home - all working fine.
Will do more testing tomorrow, but looks like this is the fix, for me anyhow.
Big thanks!

Work for me.
This fix work for me. Test during 40 min of navigation .I´m on Omega 33.1 with video fix and Kernel Perseus 26.1
Will test again on the end of the day.

is the "use wireless network" is turn on on your rom??
or turn off??

not working for me on omega 33.2 + stock kernel

liad1981 said:
is the "use wireless network" is turn on on your rom??
or turn off??
Click to expand...
Click to collapse
Is ON
Sent from my GT-I9300 using Tapatalk 2

Small report:
Today morning I use GPS (Waze and Be On Road) to navigate to my work (15km).
Lost signal every 3 - 5 minutes. Strange.
In my work I flash your fix.
Navigate (Be On Road) approximately 15km to customer and 15km to work. Working absolutely good.
Thank you.
I will test later much more and report again.
Update1: On the way home from work gps navigation (Be On Road) work like a charm. I am lucky
Update2: Today on way from home to work, working very well. Thank you. Now I vote for YES

Hi my friend. But suddenly your fix work here. Did another full wipe. Installed my usual stuff and got no fix. Then I thought I try again your zip and it works for now. Will test how long but really hope that's it.
Sent from my GT-I9300 using xda premium

i installed 33.2 with no wipe on 33.1 and i had the gps problem.
it found the first fix but after 2-3 minutes the fix isnt possible.
i did a first check with your fix and it seems to work now...tomorrow on my way to office i will give it a try
thx

How did I miss this! Going to flash and test on the way to work tomorrow...looks promising!
Sent from my GT-I9300 using Tapatalk 2

Not sure i tried this one, but just flashed it and will try in about 2 hours and will report back.

For me it's working now.. I'm on Omega 33.2 and latest Siyah
tapatalked via SGS3 on OMEGA and Motomoto00

Oke, just had my 25 minutes drive.
Flashed your zip before went on the road, double checked that Use wireless networks was enabled again, this afternoon i disabled it and gps worked again.
And from work to home, not one single drop off gps noticed using Sygic.
Also watched carefully to Sygics speed meter and it was corresponding with the speed i actually drove, not going from 30 to 100 i saw yesterday before gps broke down.
Looks your file did it for me.

Deleted

[Q] Viper DHD - phone rebboting when taking pictures with flash

I'm on ViperDHD 2.1.3, coming from Blackout 3.2.
After flashing the new ROM, I am experiencing this issue: everytime I need to take a picture with flash, my Desire HD reboots.
Anyone can help me? Is it a ROM issue? Kernel maybe?
Thank you.

Probably battery issue.

Try with another battery or try with another rom.

bananagranola said:
Probably battery issue.
Click to expand...
Click to collapse
Not at all, it happens only with this ROM. Battery is ok.

tomerFire said:
Try with another battery or try with another rom.
Click to expand...
Click to collapse
Thank you, but this is not what I really asked. I was wondering why I have this problem only with this new ROM.
Anyhow, it is fair enough to say that if I want to solve the problem I can flash another ROM.

Full wipe? It's probably got to do with the ROM's flash intensity and an older battery. Maybe the battery works with other ROMs with lower flash intensity. I would give a new battery a try if you like the ROM. Even if it doesn't work, batteries are less than $10 last time I checked.

it isn't a ROM bug, maybe you flashed sense 4+ camera in aroma which is unstable

I had the same problem with my DHD and it solved by replacing the battery
http://forum.xda-developers.com/showthread.php?t=1720677
I am using Venom Rom and I have no issue like that..
Note: before replacing the battery do this:
1- backup your SD card.
2- Format your SD card.
3- do full wipe for your DHD and it mean everything (system,DATA,Battery state, boot,SD card)
4- flash any ROM you like - ViperDHD 2.1.3, and see if the issue is gone or not.
- If not so you have battery issue and it need to be replaced,

torxx said:
it isn't a ROM bug, maybe you flashed sense 4+ camera in aroma which is unstable
Click to expand...
Click to collapse
Tahnk you torxx... first of all for the amazing ROM!!! I'm using stock camera and I cannot understand this issue. I'll try and flash again the ROM, maybe something went wrong even if I performed a full wipe.
Anyhow, I tried a different camera from the market and it works , so this one can be a solution too.

Which app .?
I am facing this problem too tried other roms also, issue is in every Rom . battery timing is good . Flash light application is working . But flash with camera is causing reboot

---------- Post added at 12:36 AM ---------- Previous post was at 12:35 AM ----------
It is ok with stock rom but other custom rom ( aokp , cm 10.1 , pacman, viperdhd ) cause reboot with flash on camera picture . any solution ?
Video recording with flash on is working. Only snap shots cause reboot .

I had same issue on my 2 years old DHD. New battery completely solve the problem with flash. Some other users reported the same.
Sent from my Nexus 7 GSM using xda app-developers app

I bought new battery and problem is solved.

try "Force GPU rendering"
Settings -> Developer options -> Force GPU rendering
it might help especially if you have stock S4 camera, the one that comes originally with ViperDHD
it happened to me and this just fixed it right away
hope it helps

battery
I think it's related to the battery.You try to change one other battery performance outcome.If not then you should update the Viper 2.2.0

[Q] Screen Problem NEXUS GSM

Hello. I have a problem whit my galaxy nexus maguro device. When i install something different then stock google images 4.1.2 or stable "cm-10.0.0-maguro.zip" i have a problem whit screen when i'm during my phone call. Every time i install something different for exp: stock 4.2.1 or 4.2.2 or every custom rom (xylon,pa,xenon,slim bean etc. etc. ) and when i starting a conversation my screen of course is off but when i geting off my phone from ear screeen whant to turn on and it is almost every single time i having a phone call.I was trying every basband,rom, kernel and always i the same result -screen issue. Of corse when i'm on 4.1.2 or cm-10.0.0-maguro.zip there is no problem. so my question is WTF ? Please try to forgive me for my english - this is not my thing

?
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?

?
ryza666 said:
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?
Click to expand...
Click to collapse
And i've changed animation window to 0.5 and it's not working. PLS help MEEEEEEEEE !

Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S

irizwan said:
Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S
Click to expand...
Click to collapse
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?

ryza666 said:
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?
Click to expand...
Click to collapse
And sorry for your "quick" response:angel:

Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus

bk201doesntexist said:
Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus
Click to expand...
Click to collapse
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case

ryza666 said:
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case
Click to expand...
Click to collapse
Is your screen protector covering the proximity sensors? My screen protecter once covered them and I had the same issues but when i removed it, it worked again

If you are using a custom kernel, try up-ing you min screen off setting in trickster mod.
I used to get a lot of these problems. But not any more since I am on Diamond series of AK kernel.
I am using these settings: http://forum.xda-developers.com/showpost.php?p=38030897

[Q] Camera Error

I always go the "camera error - can't connect to the camera" when taking photo with rear camera.
HOWEVER, the strange thing is I can record video with the rear camera and the front camera works as well.
I've tried to factory reset, still unsolvable. I have this problem when using CM9 by ipromeh.
One thing I notice is I tried to upgrade to KK 4.4 but failed somehow, is that a conflict or a problem and related to my camera problem ?
PLS help me out !!! =<
ps : i tried using camera360, the error poped out is due to security problem o.o?:crying:

For update to android 4.4 you must have the last cwm

The camera still doesn't work =(

any solution?

what your CWM and OS version?

me too
i have updated to 4.4.2 and have the same pb even my wifi doesnt work

4.2.2 latest K.K latest CWM..
the problem is i have this prob since ICS. ><

just format everything and return to stock rom . it may work.

MeowNYC said:
I always go the "camera error - can't connect to the camera" when taking photo with rear camera.
HOWEVER, the strange thing is I can record video with the rear camera and the front camera works as well.
I've tried to factory reset, still unsolvable. I have this problem when using CM9 by ipromeh.
One thing I notice is I tried to upgrade to KK 4.4 but failed somehow, is that a conflict or a problem and related to my camera problem ?
PLS help me out !!! =<
ps : i tried using camera360, the error poped out is due to security problem o.o?:crying:
Click to expand...
Click to collapse
Camera not working is a known issue on AOSP ROMs. Many fixes have been put in place but apparently the camera ignores them. It works if you're lucky (apparently u aren't) but doesn't if have bad luck. Try reflashing another ROM. Might work. Worked for me.
Smack that Thanks button if I helped!
XDAing from a N7105 powered by Illusion ROM.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA

Irwenzhao said:
Camera not working is a known issue on AOSP ROMs. Many fixes have been put in place but apparently the camera ignores them. It works if you're lucky (apparently u aren't) but doesn't if have bad luck. Try reflashing another ROM. Might work. Worked for me.
Smack that Thanks button if I helped!
XDAing from a N7105 powered by Illusion ROM.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Click to expand...
Click to collapse
still the same
somehow i can record video but not take photo @@