Develop Bugs

Having camera problems with CM 6.1.2

I justest loaded CM 6.1.2 on my HTC evo and now every time i try to use my camera it freezes and has to force close. Any idea's? I'm new at this whole phone moding thing, so if I left out any important info just tell me. I had someone who is more experienced help me root my phone and load the rom so I don't think I messed up anything there.

Hmmm...that's strange.....I had the CM on my phone, and didn't experience any camera issues. Are you using a custom kernel?

Have you tried clearing the data and cache from the camera and then opening the camera back up? (Settings/Applications/Manage Apps/Camera) This has helped others on certain roms. Not sure on CM though.
Also, agreed with the kernel thing from filmaker. Sometimes that will do it. Try a different one.
Good luck!

I'll try that, thanks. I loaded a different rom on my phone and I'm having some problems with it, I'll reload cm and try what you told me. As to the custom kernel question, I dont believe I do. I also read on the cm forum about CM6.1.2 having issues with the camera pm newer evos and they talked about a fix but I couldn't seem to find it.

Having sorta the same problem... I switched to CM6 and the camera is just buggie... It either wont take a picture, lags really bad or FC's... I've tried clearing the data out of it but that seems to have made it worse.... Any other idea people? Thanks
Oh, I'm runnin CM6 with a stock kernel... maybe try a different kernel? And if so, can I just flash a kernel without changin anything elese like radios and what not?

Well I reinstalled cm and the camera worked prefect for a while but its not working now. I tried what you said and it didn't work. I have the stock kernal as well.
Sent from my PC36100 using XDA App

hhhmm... that's prolly gonna be a deal breaker for me if I can't get it fixed... I use my phone camera quite a bit

Did you wipe data, cache, and dalvik between ROMs? How about system?

Well I know I wiped data, cache and dalvik... and I think I wiped system (If that's an option in to do from recovery then yeah I did)..

What recovery are you using and what rev? When I first tried CM6.1.2 I was using RomManger, which was using ClockWork 3.x.x.x recovery. I couldn't get CM6 to run for more than a day without having issues. I was able to switch to Amon_RA 2.2.1 and flash a few other ROMs which ran fine for days without any issues. I have since loaded up the EvoNonsense 4.3.1 ROM, which feels a lot like Cyanogen but still has Sense, so everything works (4G, HDMI, Camera/Camcorder, etc...). Anywho, not sure if using Amon_RA recovery will fix your Cyanogen issues or not but it may be worth a try. If that doesn't work out then you may want to try the EvoNonsense ROM.
http://forum.xda-developers.com/showthread.php?t=758197

[Q] Auto-rotate not working on apps

what's up guys so i recently rooted my phone and flashed the latest cm7 (7.0.2). i couldn't help but to notice that my auto-rotate does not work on apps. i.e. web browser, txting, etc. It DOES rotate when i slide the keyboard out, but it's stuck on portrait if i don't have the keyboard out. I've tried ticking an unticking various things such as auto-rotate, being able to rotate an additional 180 degrees..nothing seems to make it work. does anyone have a clue of what's wrong?? (f.y.i, i've tried reflashing the rom couple of times and also flashing cm nightly, wiping the cache, wiping data/reset, but still no progress). if anyone has encountered this problem, or might have a solution, that would be great ! it's starting to irritate me..so any help would be much appreciated. thanks for stopping by.

Yeah try a better more stable rom
Sent from my T-Mobile G2 using XDA Premium App

Spastic909 said:
Yeah try a better more stable rom
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
so i tried flashing a different rom (gingervillain 1.5) like you said..and it's still not working.....any other suggestions? should i unroot and root my phone again? would that cause any harm?

This has been happening occasionally on my G2 while running the stock deodexed ROM, and the only way I've known to fix it is to run "fix permissions" in CWM. I've also deleted the cache and dalvik cache as well, just to be safe, and these have fixed the problem for me. I'm not sure if it's related to the ROM or any of the apps I have installed, but I'm getting more & more concerned that it could be that my accelerometer slowly dying. Not sure.
I really hope that helps fix your problem.

dustrho said:
This has been happening occasionally on my G2 while running the stock deodexed ROM, and the only way I've known to fix it is to run "fix permissions" in CWM. I've also deleted the cache and dalvik cache as well, just to be safe, and these have fixed the problem for me. I'm not sure if it's related to the ROM or any of the apps I have installed, but I'm getting more & more concerned that it could be that my accelerometer slowly dying. Not sure.
I really hope that helps fix your problem.
Click to expand...
Click to collapse
ok so i tried to do your method, and it still doesnt work... i'm kind of bummed because i barely got a replacement on this phone..and its hard to believe that the accelerometer would be dying on mine because i just got it replaced like few weeks ago..i really don't know what the problem is

MIUI problem

I have a problem with MIUI rom. Some days ago, my phone suddenly had FC, now, my phone run really slow and laggy... If I turn off the screen, my phone won't wake up, only four button in the bottom light up.
I wiped everything in CMW (system,data, and cache, also sd-card) but it doesn't work.
The fresh install had the same issues
I have this problem only with MIUI rom
any help

You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?

zandroid said:
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
Click to expand...
Click to collapse
i have tried from 1.8.5 to 1.9.2.
it's very weird
this guy has the same problem with me, maybe he can explain better than me
http://forums.miui.us/showthread.php?3740-Display-won-t-wake-from-sleep
Hey guys, I flashed 1.819 yesterday and everything was going great. The ROM ran smoothly and I was having no issues at all. When I woke up the next morning my display would not turn back on. Every time I tried to turn on the display the soft lights would light up but the display remained unresponsive. The phone still seemed functional as I could hear e-mail and sms notifications coming through.
When I rebooted my phone it was abnormally slow.. mounting the sd card and syncing seemed like it was taking forever and the launcher was very jittery.. if I let my display time out it would not come back on and I'd be forced to pull the battery and try again.
I performed a full wipe through clockwork recovery (everything, including wiping system,data, and cache in 'mounts and usb') and reinstalled 1.819. The fresh install had the same issues.. if I let my display time out I wouldn't be able to turn it back on. I thought I was having some wonky hardware issue but after flashing my previous sense rom and everything is working perfectly.. so I'm pretty much scratching my head here. My phone was kickass for one day and became allergic to MIUI overnight!
Click to expand...
Click to collapse

Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)

PacerguyDon said:
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
Click to expand...
Click to collapse
i have tried both

Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.

ttupa said:
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
Click to expand...
Click to collapse
immediately after the flash. I don't install any other apps

since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?

spiderj said:
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
Click to expand...
Click to collapse
Try different kernel
Sent from my Incredible 2 3D using XDA App

tenchu_712 said:
immediately after the flash. I don't install any other apps
Click to expand...
Click to collapse
tenchu, your signature says you are not English or American. Are you running the MIUI.us ROM on your incredible 2 in English - and not another language?
.....just a thought.

[Q] What is wrong with my Gnex?

Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?

JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.

Are you sure it's the phone and not an app?

chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.

Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4

chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.

why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct

Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.

I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!

well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?

lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).

[Q] Can a ROM kill the camera?

I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
What killed the camera? Is it possible that a bad ROM could have done it?
Is it possible to fix this via software?
I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.

aalaap said:
I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
1) What killed the camera? Is it possible that a bad ROM could have done it?
2) Is it possible to fix this via software? I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.
Click to expand...
Click to collapse
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.

jsgraphicart said:
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.
Click to expand...
Click to collapse
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.

aalaap said:
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.
Click to expand...
Click to collapse
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895

jsgraphicart said:
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895
Click to expand...
Click to collapse
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.

aalaap said:
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.
Click to expand...
Click to collapse
Usually if the phone has any issues at all, that process fixes them. And if it doesn't, then there is usually something wrong with the hardware. I wouldn't think the problem was brought on by installing a ROM or kernel though.

I think it's related to the kernel that you're using

......
i think yes but if you change the rom it will work
some roms the camera has some bugs big bugs colors are broken and stuff