[Q] cannot connect to camera - HTC Inspire 4G

The camera on my inspire stopped working randomly, it was working just fine and now all or the sudden it says cannot connect to camera when I attempt to open the application. I was running cm7 nightly 76 then just updated to cm7 7.1 RC1 thinking that would fix the problem ......no such luck. Any ideas?

RAGE 33 said:
The camera on my inspire stopped working randomly, it was working just fine and now all or the sudden it says cannot connect to camera when I attempt to open the application. I was running cm7 nightly 76 then just updated to cm7 7.1 RC1 thinking that would fix the problem ......no such luck. Any ideas?
Click to expand...
Click to collapse
My understanding is that the nightlies aren't guaranteed to be stable.
And going from a cm7 nightly to the rc1 wouldn't seem to me to be a sure-fire way of resolving the issue, seeing as both are cm7.
Perhaps try flashing a non-cm7 ROM and see if the problem persists?
After full wiping, of course.

Did you happen to flash any other kernels with your ROM's?

Related

phone reboots when using camera

Am having some problem with my nexus one ive notice since i wipe my phone and install froyo, i tried going back to my cyano 5.0.6 but my camera isnt working whenever i switch to recorde a video the phones automatically reboots,but when i flash the froyo rom the camera is working perfectly there but when i try going back to my cyanogen its not working, anybody know what the problem is, also today i flashed cy 5.0.7 and am having the same problem.

[Q] HTC Sensation Cyanogenmod 9 (Hypersensation 2.9) Camera Issue

Hello,
I am new to this forum and am having an issue with my HTC Sensation 4g. Since I've installed Cyanogenmod 9 -Hypersensation 2.9, the Camera as well as the Torch have not been working properly. I've tried going to the Applications and Clearing the Data as well as re-installing the ROM, but to no avail. Any help with this issue would be greatly appreciated. Thank you. Also, whenever I try to access the Camera app it says "Cannot Connect to the Camera" and when I try to access the Torch app, it says "Unfortunately the Torch app has stopped working". I have also noticed that the GPS function does not work.
I have the same issue since I first installed a CM9 nightly on my Sensation XE.
Installing the CM RC1 and the CM Open Sensation did not fix this either.
I also tried the Android Revolution rom and had the same issues.
Would appreciate any suggestions that anyone has.
Did you fullwipe before installing CM9?
Because on my pyramid with cm9 RC1 the torch app and GPS both work fine and allways have.
andy01q said:
Did you fullwipe before installing CM9?
Because on my pyramid with cm9 RC1 the torch app and GPS both work fine and allways have.
Click to expand...
Click to collapse
Yeah - absolutely. If you don't do that on an initial install CM9 (or any other ROM) will very likely go into a boot loop.
donalmc said:
Yeah - absolutely. If you don't do that on an initial install CM9 (or any other ROM) will very likely go into a boot loop.
Click to expand...
Click to collapse
If it helps, I did a system format with CWM 5.8.0.9 and installed cm10. Camera and torch came back, but only for a week. No it shows the same as before and for you. I will do a system format soon when i have time.
Good luck.
If you have bulletproof solution to make the camera work, pls share with us.

[Q] No signal in AOKP build 40

I have recently installed AOKP build 40, but the problem is I often receive no signal until rebooting into recovery and wiping the cache. This works but it is very frustrating to have to do this frequently. Does anyone know of a permanent fix to this problem?
I was having a similar problem. You can turn on airplane mode, leave it for about thirty seconds, and turn it off. It works better than nothing.
Now can you answer me a question as you do seem to still be running AOKP. Do you have trouble downloading stuff from the Google Playstore? It keeps timing out on me. Won't let me down anything until I force stop, disable, and re enable. The bigger issue is that it followed me back to a sense rom and I'm still having trouble downloading.
Sounds like the RIL startup bug which was fixed a week or so ago by intervigil in CM9 alpha 12. I think the fix is in the kernel and that it'll work on AOKP as well. Try to fastboot flash boot a recent CM9 boot.img, from alpha 12 or newer. Download from ville.giev.de or cm9 thread in development

Wifi doesnt work on CM 7.2

So I got bored of the whole ICS and JB revolution and decided to go for some good old fashioned Gingerbread love, so I went to the cyanogen site and downloaded CM 7.2, but since then my wifi isn't working but cellular data works, wifi just connects and stays put, doesn't work, even tried changing the regulatory channels but no luck, any idea? Please help
It's working fine for me on CM 7.2, so there's most likely an issue with your setup. Sometimes coming from ICS back to GB, requires a couple of wipes.
wmdunn said:
It's working fine for me on CM 7.2, so there's most likely an issue with your setup. Sometimes coming from ICS back to GB, requires a couple of wipes.
Click to expand...
Click to collapse
Wiped and Installed twice, still wont work.

[Q] In call volume muted and random network disconects

Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Meshelton said:
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Click to expand...
Click to collapse
If you were happy with everything working WHY in the world did you upgrade to a Nightly? Nightly by definition is only for people who know what they're doing and are not afraid of the Night.
Anyway, there are like 6.0221413e+23 changes from cm 10.0.0 to 10.1 RC2. What can I say you did a dirty flash (upgrade!), and probably didn't back up.
So the first thing you should do is back up. NOW (go to CMW recovery and back up)
Download a better behaving nightly like the one JD1639 uploaded. get it from http://forum.xda-developers.com/showthread.php?t=2272261
Download the UCMC1 radio (assuming you're on at&t)
Download the gapps 20130301
Put them all on in one folder for easy access
goto the CWM recovery and get to work:
1-backup
2-cleanup: go to mounts and format data, cache, system (don't format the sdcard!!!) and don't reboot until everything is finished
3-clean dalvik cache from advanced
4-install in this order: RADIO file.zip (UCMC1)
5-CM ROM
6-gapps
7-go to Advanced Restore option, find you back up and restore the "DATA" portion ONLY
This should save you ... good luck,
Commodore 64
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Meshelton said:
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Click to expand...
Click to collapse
You know I don't think it is a hardware issue since it started after one of your updates. If you were on a ROM for while, and one morning you wokeup and the sound didn't work ... maybe. But i'm not convinced since also I remember around Feb-March there were some complains on sound not working after flashing to 4.2.2 version of the cm. Try flashing back to the stock UCMC1 ROM (absolute stock flashed with Odin not CMW) and then do a factory reset.

Categories

Resources