Guest Christo0908 Posted March 31, 2011 Report Posted March 31, 2011 I get this error message see: 20110331202515.png and here is a copy of the logcat V/CameraHolder( 6849): open camera 0 D/QualcommCameraHardware( 142): createInstance: E E/QualcommCameraHardware( 142): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory! E/QualcommCameraHardware( 142): createInstance: startCamera failed! D/QualcommCameraHardware( 142): ~QualcommCameraHardware E D/QualcommCameraHardware( 142): ~QualcommCameraHardware X E/CameraService( 142): Fail to open camera hardware (id=0) E/CameraHolder( 6849): fail to connect Camera E/CameraHolder( 6849): java.lang.RuntimeException: Fail to connect to camera service E/CameraHolder( 6849): at android.hardware.Camera.native_setup(Native Method) E/CameraHolder( 6849): at android.hardware.Camera.<init>(Camera.java:258) E/CameraHolder( 6849): at android.hardware.Camera.open(Camera.java:220) E/CameraHolder( 6849): at com.android.camera.CameraHolder.open(CameraHolder.java:124) E/CameraHolder( 6849): at com.android.camera.Camera.ensureCameraDevice(Camera.java:1794) E/CameraHolder( 6849): at com.android.camera.Camera.startPreview(Camera.java:1846) E/CameraHolder( 6849): at com.android.camera.Camera.access$5900(Camera.java:94) E/CameraHolder( 6849): at com.android.camera.Camera$3.run(Camera.java:938) E/CameraHolder( 6849): at java.lang.Thread.run(Thread.java:1019) I/ActivityManager( 200): Displayed com.android.camera/.Camera: +833ms anyone know what the problem could be? or just a general hardware problem? because I REALLY don't want to send it back to Orange because they're useless! help would be appreciated.
Guest Christo0908 Posted March 31, 2011 Report Posted March 31, 2011 sorry, forgot to upload the file here it is
Guest Christo0908 Posted March 31, 2011 Report Posted March 31, 2011 I should also mentioned, from what I noticed, this problem began after I tried flashing one of the earlier CM7 builds, up until then it has been working fine, it seems the camera can't find the file msm_camera, any ideas on where this file might have hidden itself to?
Guest Christo0908 Posted March 31, 2011 Report Posted March 31, 2011 I looked into the file system X:/dev.... but there is no msm_camera, does this mean it has been deleted? if so where would I find it or replace it? c'mon people I'm racking my brains here :D
Guest Totyasrác Posted May 12, 2011 Report Posted May 12, 2011 I also have the same issue, and so far couldn't find the answer. Tried reflashing (I mean completely - official 2.1, 2.2 updates, gen1 -> gen2 -> gen1 restructuring the system memory), switching SD cards without any success... Attaching my own logcat later. Otherwise when checking the system info it reads: Camera info: ID:0x0 Nmae: No sensor or error!!! It has happened after TPT upgrade method and can not fix it (I mean so far) so I'd say it is a sw issue - no driver? But how/why? Any help would be appreciated!
Guest Azurren Posted May 12, 2011 Report Posted May 12, 2011 I also have the same issue, and so far couldn't find the answer. Tried reflashing (I mean completely - official 2.1, 2.2 updates, gen1 -> gen2 -> gen1 restructuring the system memory), switching SD cards without any success... Attaching my own logcat later. Otherwise when checking the system info it reads: Camera info: ID:0x0 Nmae: No sensor or error!!! It has happened after TPT upgrade method and can not fix it (I mean so far) so I'd say it is a sw issue - no driver? But how/why? Any help would be appreciated! Did you wipe data and cache before flashing a rom? Are you using the 5mp version of the blade? Have you tried Cyanogen Mod? Hope this helps :unsure:
Guest JT_daniel Posted May 12, 2011 Report Posted May 12, 2011 I have a similar problem, except I'm on GEN 1 and SS RLS5. I can't use the autofocus feature of the camera. Every time I take a picture with it, the camera app just crashes. And I have to restart before I can use the camera app again. Now I have the autofocus turned off and it works fine. Don't really use the camera, so it doesn't bother me. And Warranty isn't an option since I have the OSF. Any suggestions?
Guest Totyasrác Posted May 13, 2011 Report Posted May 13, 2011 (edited) Did you wipe data and cache before flashing a rom? Are you using the 5mp version of the blade? Have you tried Cyanogen Mod? Hope this helps :unsure: Hi there, yes, most of the times I do complete wipe (except for when it is suggested by the author(s) of the ROM that it's only necessary if problems occur like between Nightlies). Mine is on of the first SanFrans from the UK (OLED, 3MP camera, 512MB RAM). CM was the main reason for me to switch over to Gen2 in the first time. So at the moment I have a pretty decent Blade with official Froyo (I guess it won't stay long... :)) but without working camera, it must be a driver issue... Edit: here's my logcat: E/QualcommCameraHardware( 86): openCameraHardware: call createInstance E/QualcommCameraHardware( 86): createInstance: EE/QualcommCameraHardware( 86): Storing the current target type as 1 E/QualcommCameraHardware( 86): constructor EXE/QualcommCameraHardware( 86): startCamera EE/QualcommCameraHardware( 86): loading liboemcamera at 0x7000fe94 E/QualcommCameraHardware( 86): startCamera X: /dev/msm_camera/control0 open failed: Unknown error: 0! E/QualcommCameraHardware( 86): createInstance: startCamera failed! E/QualcommCameraHardware( 86): ~QualcommCameraHardware EE/QualcommCameraHardware( 86): ~QualcommCameraHardware X D/KeyguardViewMediator( 159): setHidden false E/CameraHolder( 1471): fail to connect Camera E/CameraHolder( 1471): java.lang.RuntimeException: Fail to connect to camera service E/CameraHolder( 1471): at android.hardware.Camera.native_setup(Native Method) E/CameraHolder( 1471): at android.hardware.Camera.<init>(Camera.java:120) E/CameraHolder( 1471): at android.hardware.Camera.open(Camera.java:100) E/CameraHolder( 1471): at com.android.camera.CameraHolder.open(CameraHolder.java:100) E/CameraHolder( 1471): at com.android.camera.Camera.ensureCameraDevice(Camera.java:2408) E/CameraHolder( 1471): at com.android.camera.Camera.access$7100(Camera.java:156) E/CameraHolder( 1471): at com.android.camera.Camera$5.run(Camera.java:1421) E/CameraHolder( 1471): at java.lang.Thread.run(Thread.java:1096) D/skia ( 159): purging 213K from font cache [9 entries] D/KeyguardViewMediator( 159): setHidden false W/WindowManager( 159): updateFocusedWindowLocked newFocus=null mode=3 mCurrentFocus = null D/KeyguardViewMediator( 159): setHidden false D/KeyguardViewMediator( 159): setHidden false I/ActivityThread( 159): Dispatching broadcast android.intent.action.CONFIGURATION_CHANGED to com.android.server.status.StatusBarService$5@30088e20 I/ActivityThread( 159): mRegistered=true mCurOrdered=false D/StatusBar( 159): updateNetworkName showSpn=true spn=T-Mobile H showPlmn=false plmn=T-Mobile H I/ActivityThread( 159): finish dispatching broadcast to com.android.server.status.StatusBarService$5@30088e20 I/ActivityThread( 159): Dispatching broadcast android.intent.action.CONFIGURATION_CHANGED to com.android.server.status.StatusBarPolicy$1@2fddff68 I/ActivityThread( 159): mRegistered=true mCurOrdered=false D/StatusBarPolicy( 159): StatusBarPolicy:mIntentReceiver action=android.intent.action.CONFIGURATION_CHANGED W/WindowManager( 159): updateFocusedWindowLocked newFocus=Window{30115878 com.android.camera/com.android.camera.Camera paused=false} mode=1 mCurrentFocus = null E/camera ( 1471): onResume():: e E/camera ( 1471): onResume():: x The interesting part (for which I believe it is a sw-related error): X: /dev/msm_camera/control0 open failed: Unknown error: 0! It can't open the camera control part for some reason... Edited May 13, 2011 by Totyasrác
Guest Christo0908 Posted May 13, 2011 Report Posted May 13, 2011 Totyasrác yes this is what I noticed, if it were a hardware issue, wouldn't that mean it would fail to connect AFTER loading the drivers and controls etc. it's been racking my brain for months as I bought it from ADVERTISING SPAM and it's simply too much hassle to get it fixed for free with there being no local repair centres, if anyone at all comes up with anything for this it would be fantastic, the camera may be abit crap, but I like to have everything on my phone working correctly. and Azurren I am using the 3.* whatever megasquixel camera version with the LCD screen not OLED version I've tried numerous different ROMs and landed on Pauls MCR FroYo as it seems like CM7 is moved on to Gen2 only =(
Guest Totyasrác Posted May 13, 2011 Report Posted May 13, 2011 (edited) Totyasrác yes this is what I noticed, if it were a hardware issue, wouldn't that mean it would fail to connect AFTER loading the drivers and controls etc. it's been racking my brain for months as I bought it from ADVERTISING SPAM and it's simply too much hassle to get it fixed for free with there being no local repair centres, if anyone at all comes up with anything for this it would be fantastic, the camera may be abit crap, but I like to have everything on my phone working correctly. and Azurren I am using the 3.* whatever megasquixel camera version with the LCD screen not OLED version I've tried numerous different ROMs and landed on Pauls MCR FroYo as it seems like CM7 is moved on to Gen2 only =( I guess it requires someone with a bit of Android knowledge to fix this... It's not Blade specific though but can not reproduced so as soon as a developer suffers from it we'll have the solution (hopefully). Now there are many 2.2 options available for Gen1 phones like FLB and Swedish Spring. (By the way you should be upgrading to Gen2 since even the latest CWM recovery is for Gen2 only... ) Best way could be the official 2.2 (Hungarian T-Mobile) update here... It did not solve my problems which tells me there's a slight chance for the issue to be hw-related... All my drivers have been fully updated with official update, and before that I went gen1 -> gen2 (that was when my camera stopped working), then gen2 -> gen1 (to be completely fit for the official update), then gen1 -> gen2 (with the update). All these steps meant that the whole internal memory had been restructured thus resulting in a complete, 100% fully wipe system-wise. And still I have a non-working camera no matter what I do (reformatting SD, wiping, reinstalling, restoring backups from the time it worked). Edit: Did some further research about this and have found some solutions - which don't work for me, just sharing with you as some interesting theories: 1. At XDAdevelopers' place there's some solution for the camera (not fully functional): "I have a workaround by copying /system/lib/libcamera.so and /system/lib/libqcamera.so from the original, stock image of my phone. This results in a working camera." I have tried it but just didn't find any libqcamera.so files in any of my stored ROMs (FLB version, SwedishSpring etc), only libcamera.so. Overwriting the existing (and rebooting) - still no success. 2. Then I got the idea to check wheter or not I have anything under /dev/msm_camera/ but I do not even have such a folder... (Checked with RootExplorer). I'd like to ask any of you whoever has a working camera to please check it and report back if I should have a /dev/msm_camera or not, please... 3. Another nice idea from here (supposing that it's some messed up resolution setting that stops my camera from starting). Tried it, didn't work either (app states something is wrong and suggests to be started in hw-compatibility mode - no success again). 4. Issue No. 2705 @Cyanogen (and some other sites) suggest that there's something messed up with the radio image... But then I did the official gen1 -> gen2 upgrade (official Hungarian T-Mobile 2.2 release for the ZTE Blade) which basically erases the whole system structure, resizes everything and then builds up the system from nothing... So should work. On the other hand most similar issues started with OTA upgrades or CM6-7 updates... And afterwards most of them stayed like that (even with restoring formerly working Nand backups to a fully wiped phone). Would be nice if some dev could take a look at the logs or tell me some things to try... :unsure: So this is where I am at now, doing some more research Edited May 16, 2011 by Totyasrác
Guest Totyasrác Posted May 16, 2011 Report Posted May 16, 2011 (edited) Just to keep it from sinking - should've done new post instead of editing the previous one... :unsure: Please read the previous, edited post! Edited May 16, 2011 by Totyasrác
Guest Totyasrác Posted May 17, 2011 Report Posted May 17, 2011 No I have asked my friend to please check the files and folders under /dev, and his Blade has the following stuff there: /dev/msm_camera/config0 /dev/msm_camera/control0 /dev/msm_camera/frame0 I don't even have the msm_camera folder meaning that at boot the kernel has not recognized my camera thus haven't published appropriate files in devfs (I don't get half of it but he's better at stuff like this than I am :unsure:). Any suggestions? This points at hw-related issue again but still I KNOW I didn't drop it and it all started with gen1 -> gen2 TPT method...
Guest Totyasrác Posted May 17, 2011 Report Posted May 17, 2011 Interesting might be, here are the devices visible to the system: $ export PATH=/data/local/bin:$PATH $cat /proc/devices Character devices: 1 mem 4 /dev/vc/0 4 tty 5 /dev/tty 5 /dev/console 5 /dev/ptmx 7 vcs 10 misc 13 input 21 sg 29 fb 81 video4linux 86 ch 89 i2c 90 mtd 108 ppp 116 alsa 128 ptm 136 pts 216 rfcomm 246 kgsl 247 taos 248 ttyHS 249 dia 250 adsp 251 oncrpc 252 smdpkt 253 smd 254 rtc Block devices: 1 ramdisk 259 blkext 7 loop 8 sd 31 mtdblock 65 sd 66 sd 67 sd 68 sd 69 sd 70 sd 71 sd 128 sd 129 sd 130 sd 131 sd 132 sd 133 sd 134 sd 135 sd 179 mmc 254 device-mapper $ So I guess the HW is not visible -> might be a coincidence between hw-failure and TPT method?!
Guest Totyasrác Posted May 20, 2011 Report Posted May 20, 2011 Hi all, asked some of my friends to dig deep down in my logs (dmesg), here are the results. I am not very familiar with these things, so I'm kinda providing update on what's happening (and also hope that some dev could check this and hopefully help me out on this one :P) The first interesting row in the dmesg log is: <3>[05-19 17:45:21.638148] [56: mt9t11x_wq]msm_i2c msm_i2c.0: Error during data xfer (-5) Now apparently mt9t modules' (integrated imaging devices' drivers) like i2c can't communicate meaning they can't poll the system for camera relevant stuff thus there's nothing about them under /dev folder (I have mentioned before in a previous post that I do not have a /dev/msm_camera at all). Under this we can find this row: <3>[05-19 17:45:22.398136] [57: ov5642_wq]msm_i2c msm_i2c.0: Error during data xfer (-5) "ov" is supposed to be the driver for the OmniVision 5642 which is the 5Mpx CMOS camera (I have the 3.2Mpx version!!!); while the MT9T is the integrated imaging device. These rows probably mean that the kernel at startup can't find any device according to either driver. My friend has found a thread over at CM's where they state that similar problems are caused by incorrect/incompatible radio firmware. After all I think the root cause is that the first TPT upgrade of mine (going from Gen1 to Gen2 with curl66's method) my radio firmware was overwritten with some (well, sort of) incompatible version resulting in losing camera functionality. 3.2Mpx version is supposed to be using MT9T and 5Mpx version the OV5642, but neither of these drivers are suitable for my version. Here's the thread from CM's site. So if anyone knows the following informations PLEASE tell me, or help me find the way out of this state: - Exactly what driver is required for the UK-sourced OLED Orange San Francisco for the 3.2MPx camera ? - How can I update (or reinstall) the original, working radio fw containing this driver? - Any other suggestions on my problem? Cheers! P.s.: I have attached the dmesg file for anyone interested... Dmesg.txt
Guest Totyasrác Posted June 27, 2011 Report Posted June 27, 2011 Excellent news - for some unexplainable reason after installing the leaked official 2.3.4 based ROM my camera has started working again... Now I am as happy as ever :)
Guest ufizo Posted June 28, 2011 Report Posted June 28, 2011 Im also using GSF, but my camera still isnt working. Exact same issue as yours. Tried everything! Full Wipes, TPT.. what not.. :)
Guest Totyasrác Posted June 30, 2011 Report Posted June 30, 2011 Weird... I have really tried all possible things from gen2 -> gen1 -> gen2, full wipe, with and without SD for a long long time without any success... Restoring previously working ROMs from backup, newer ROMs, TPT method, official update package and everything like these. And finally with GSF camera started working again! What is your diagnosis? (I mean dmesg output and so on, the ones I've posted - might be a slightly different issue, right?)
Guest Totyasrác Posted June 30, 2011 Report Posted June 30, 2011 Update - lost camera functionality again... First it FC'd, then after reboot again 'Cannot connect to camera'. Absolutely no clue why... :)
Guest ufizo Posted June 30, 2011 Report Posted June 30, 2011 (edited) ohh that is sad o.O Well, welcome back to the club bro :) BTW, my thread is here. Edited June 30, 2011 by ufizo
Guest Totyasrác Posted July 4, 2011 Report Posted July 4, 2011 During the weekend my camera started working again, so I tend to see this as more of a hw-related issue :rolleyes: Will check your thread now :)
Guest ufizo Posted July 4, 2011 Report Posted July 4, 2011 UPDATE: I reinstalled my stock ROM and recovery and sent my phone to service center. The guy there fiddeled with the softwares and reported that he had the camera running, but only for a small while. Later he gave up and has agreed for a replacement. So I'll be getting a brand new phone once again :) & even i think it has to be hardware related.
Guest Totyasrác Posted July 4, 2011 Report Posted July 4, 2011 UPDATE: I reinstalled my stock ROM and recovery and sent my phone to service center. The guy there fiddeled with the softwares and reported that he had the camera running, but only for a small while. Later he gave up and has agreed for a replacement. So I'll be getting a brand new phone once again :) & even i think it has to be hardware related. Well, your issue appears to be a bit different from mine (my phone didn't even see such a device as a camera on boot). Good for you that you can use warranty (mine is imported from the UK so postage fee would cost as much as the phone is 'worth' (I bought a 3 month old TFT one for my mom for about ~65 pounds with Hungarian warranty) so it's a no-go. On the other hand I love my OLED screen so if it gives up completely I'll go for a used Desire I guess but not for a TFT Blade... Conclusion: most of the time it has to be a hw-related issue when you receive a "Cannot connect to camera" message - mine was (sort of) fixed by installing GSF onto it which is "just" a ROM. Before that none of the (official & non-official) TPTs helped, no other (2.1, 2.2, 2.3.3) ROMs made the miracle so I guess it's just something that happened to (the physical) camera instead of anything done by software changes.
Guest McrRed Posted August 5, 2011 Report Posted August 5, 2011 Well, your issue appears to be a bit different from mine (my phone didn't even see such a device as a camera on boot). Good for you that you can use warranty (mine is imported from the UK so postage fee would cost as much as the phone is 'worth' (I bought a 3 month old TFT one for my mom for about ~65 pounds with Hungarian warranty) so it's a no-go. On the other hand I love my OLED screen so if it gives up completely I'll go for a used Desire I guess but not for a TFT Blade... Conclusion: most of the time it has to be a hw-related issue when you receive a "Cannot connect to camera" message - mine was (sort of) fixed by installing GSF onto it which is "just" a ROM. Before that none of the (official & non-official) TPTs helped, no other (2.1, 2.2, 2.3.3) ROMs made the miracle so I guess it's just something that happened to (the physical) camera instead of anything done by software changes. I have this problem. I get the "Cannot connect to camera" message when I use the stock camera app. If I use LGCamera the app loads...and auto focus responds to the objects in the room - but there's no picture in the viewer (screen). Strange. Did yours continue to work with the stock 2.3.4?
Guest McrRed Posted September 13, 2011 Report Posted September 13, 2011 I have this problem. I get the "Cannot connect to camera" message when I use the stock camera app. If I use LGCamera the app loads...and auto focus responds to the objects in the room - but there's no picture in the viewer (screen). Strange. Did yours continue to work with the stock 2.3.4? Still not working, despite trying multiple different roms...I guess it's time to revert to stock and send back to Orange <shudder>
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now