Hi, I'm trying to setup an AOSP rom for my brother on his i9305 and everything is working great for the latest CM build but the camera app cannot start saying it cannot connect to camera:
02-16 02:37:04.725: E/SecCameraHardware(1951): camFW = GHFJ02
02-16 02:37:04.725: E/SecCameraHardware(1951): FimcV4l2 init: error -1, VIDIOC_S_INPUT
02-16 02:37:04.725: E/SecCameraHardware(1951): initCamera X: error, /dev/video0
02-16 02:37:04.725: V/SecCameraHardware(1951): FimcV4l2 deinit EX
02-16 02:37:04.725: E/SecCameraHardware(1951): createInstance: error, camera cannot be initialiezed
02-16 02:37:04.725: E/SecCameraHardware(1951): Instance is not created
02-16 02:37:04.725: E/CameraWrapper(1951): vendor camera open fail
02-16 02:37:04.725: E/CameraClient(1951): Could not open camera 0: -38
02-16 02:37:04.725: E/CameraClient(1951): initialize: Camera 0: unable to initialize device: Function not implemented (-38)
02-16 02:37:04.725: I/CameraClient(1951): Destroying camera 0
02-16 02:37:04.730: E/CameraHolder(3885): fail to connect Camera
02-16 02:37:04.730: E/CameraHolder(3885): java.lang.RuntimeException: Fail to connect to camera service
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.native_setup(Native Method)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.<init>(Camera.java:340)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.open(Camera.java:302)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.Util.openCamera(Util.java:366)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:323)
Now, the camera firmware version GHFJ02 is nothing like any I've been able to come across (none start with GH****) and have seen that changing the firmware can help with this problem. Does anyone know if it would be ok for me to install (downgrade as I could figure from the letters - revisions) a differently labeled firmware like for instance GDFE01 which (mostly) works ok with CM? Also, is it possible to backup the current firmware so I can restore it in case of problems? I see a dump firmware option but dont have a clue where this dump ends up being stored.
Also, if someone can give any more info on the above error message and what exactly does it mean? Maybe I can help in fixing the camera interface if it's possible.
Since it's such a crucial part of the phone, either I get it working somehow or he's better of with a rooted stock rom.
Thanks
I9305 forum .
jje
Post at I9305 section thanks
Sent from my GT-I9300 using xda premium
XeactorZ said:
Post at I9305 section thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I'm sorry, I must have been blind. I'll reply to the associated thread with a similar issue in the i9305 section.
Related
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
I/ActivityManager( 93): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.cooliris.media/.Gallery }
V/RenderScript_jni( 6329): surfaceDestroyed
V/RenderScript( 6329): setSurface 0 0 0x0
D/ViewFlipper( 6329): updateRunning() mVisible=false, mStarted=true, mUserPresent=true, mRunning=false
D/LocationManager( 6198): removeUpdates: listener = [email protected]
D/NetworkLocationProvider( 93): removeListener(): wallpaper
D/NetworkLocationProvider( 93): enableLocationTracking(): false
E/NetworkLocationProvider( 93): releaseCheckLocationLock: wake lock has already been released
D/SensorManager(18699): found sensor: BMA150 3-axis Accelerometer, handle=0
D/SensorManager(18699): found sensor: AK8973 3-axis Magnetic field sensor, handle=1
D/SensorManager(18699): found sensor: AK8973 Orientation sensor, handle=2
D/SensorManager(18699): found sensor: CM3602 Proximity sensor, handle=4
D/SensorManager(18699): found sensor: CM3602 Light sensor, handle=5
W/ResourceType(18699): Failure getting entry for 0x7f02003a (t=1 e=58) in package 0: 0xffffffb5
D/AndroidRuntime(18699): Shutting down VM
W/dalvikvm(18699): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
E/AndroidRuntime(18699): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(18699): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cooliris.media/com.cooliris.media.Gallery}: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime(18699): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime(18699): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime(18699): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime(18699): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18699): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(18699): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime(18699): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18699): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.content.res.Resources.getValue(Resources.java:891)
E/AndroidRuntime(18699): at android.content.res.Resources.getDrawable(Resources.java:579)
E/AndroidRuntime(18699): at com.cooliris.media.HudLayer.<init>(HudLayer.java:121)
E/AndroidRuntime(18699): at com.cooliris.media.GridLayer.<init>(GridLayer.java:134)
E/AndroidRuntime(18699): at com.cooliris.media.Gallery.onCreate(Gallery.java:78)
E/AndroidRuntime(18699): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime(18699): ... 11 more
I/Process ( 93): Sending signal. PID: 18699 SIG: 3
I/dalvikvm(18699): threadid=7: reacting to signal 3
I/dalvikvm(18699): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 93): Added state dump to 1 crashes
Click to expand...
Click to collapse
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
arctu said:
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
Click to expand...
Click to collapse
Q&A section ma man
I believe this is the right section, it's a question on compiling/development. I believe Gallery3D might be lacking mdpi images, and you're compiling for mdpi devices (may be wrong, not able to check now).
What you can do is to do a search for "PRODUCT_LOCALES", within all your files, I think it's in build.mk or product.mk. You will see that the default is mdpi, follow by <something> (can't remember now) += nodpi. Add a <something> += hdpi after the nodpi line, and compile and push again. I had a similar issue and was able to fix it this way, with advice from cyanogen.
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
nano build/core/product_config.mk
Click to expand...
Click to collapse
2. Find:
PRODUCT_LOCALES += nodpi
Click to expand...
Click to collapse
3. Add in after that line:
PRODUCT_LOCALES += hdpi
Click to expand...
Click to collapse
4. Save and Exit: Ctrl+X
5. Run make again:
make Gallery3D
Click to expand...
Click to collapse
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
*** Build configuration changed: "generic-eng-{mdpi,nodpi}" -> "generic-eng-{mdpi,nodpi,hdpi}"
*** Forcing "make installclean"...
*** Done with the cleaning, now starting the real build.
Click to expand...
Click to collapse
It works now. Hope this helps the others.
arctu said:
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
2. Find:
3. Add in after that line:
4. Save and Exit: Ctrl+X
5. Run make again:
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
It works now. Hope this helps the others.
Click to expand...
Click to collapse
cheers, helped me out
after quick grep to confirm I used sed
Code:
sed s/PRODUCT_LOCALES\ \+\=\ nodpi/PRODUCT_LOCALES\ \+\=\ hdpi/ build/core/product_config.mk -i
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
i am trying build a custom rom everything is working execpt camera ...can anyone help
here is logcat
E/AKMD2 (10488): akmd2 : Device can't be opened.
E/AKMD2 (10493): akmd2 : Device can't be opened.
E/QualcommCameraHardware( 290): ***read_camera_id: open CAM_ID_FILE failed!No such file or directory
E/QualcommCameraHardware( 290): Unable to determine the target type. Camera will not work
E/QualcommCameraHardware( 290): createInstance: startCamera failed!
E/CameraHolder(10495): fail to connect Camera
E/CameraHolder(10495): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder(10495): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder(10495): at android.hardware.Camera.<init>(Camera.java:110)
E/CameraHolder(10495): at android.hardware.Camera.open(Camera.java:90)
E/CameraHolder(10495): at com.android.camera.CameraHolder.open(CameraHolder. java:100)
E/CameraHolder(10495): at com.android.camera.Camera.ensureCameraDevice(Camer a.java:2019)
E/CameraHolder(10495): at com.android.camera.Camera.access$6900(Camera.java: 105)
E/CameraHolder(10495): at com.android.camera.Camera$4.run(Camera.java:1133)
E/CameraHolder(10495): at java.lang.Thread.run(Thread.java:1096)
W/Process ( 339): Unable to open /proc/10466/status
E/AKMD2 (10505): akmd2 : Device can't be opened.
W/InputMethodManager(10507): Ignoring onBind: cur seq=217, given seq=216
E/AKMD2 (10517): akmd2 : Device can't be opened.
E/AKMD2 (10523): akmd2 : Device can't be opened.
P500 device doesnt have a akmd2 sensor, you need to replace the sensor files
and camera libs.
Thanks andy i will try that now.....
Hi,
Internation Pardus v15 image on rooted i9300, works very well except for this really odd USB connection error when connecting it to my Sony BT3900u car stereo, it was previously connecting without issue on the v15 Pardus build but for unknown reasons to myself now always presents an error.
Does anyone have any ideas as to what might be causing this issue? Any help would be greatly appreciated.
After getting this issue the first time, I ran through a full rebuild, wiped phone/cache/dalvick and error still persisted post rebuild.
Model:
GT-i9300
Android Version:
4.2.2
Baseband
I9300XXEMA5
Kernel version:
3.0.31-702147
Build Number:
Pardus HD Rom XV XXUDME7
Logcat:
E/MTPRx ( 8982): Read Error Came false
E/ ( 8982): read error [0] [Success]
E/MTPRx ( 8982): state from USB_STATE eventDISCONNECTED
E/MTPRx ( 8982): /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt: open failed: ENOENT (No such file or directory)
E/MTPRx ( 8982): stop observing and calling usbRemoved
E/MTPRx ( 8982): In usbRemoved Status bar enabled
E/MTPRx ( 8982): Sending Broadcast
E/MtpService( 8982): onDestroy.
E/MtpService( 8982): Unregister Mtp disable Receiver
E/MtpService( 8982): Receiver not registered: [email protected]
E/MtpService( 8982): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 8982): Receiver not registered: [email protected]
E/MTPJNIInterface( 8982): noti = 3
E/ ( 8982): ****** [mtp_usb_mtp_finalize] mtp_close_fd Calling
E/ ( 8982): [mtp_close_fd] fd = 50...
E/ ( 8982): [mtp_close_fd] USB endpoint [50] closed...
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Updating the gInitializeFlag Flag to FALSE
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Calling mtp_stop_io
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input1/enabled: No such file or directory
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input8/enabled: No such file or directory
E/videowall-TranscodeReceiver(10572): broadcastMSG : android.intent.action.ACTION_POWER_DISCONNECTED
E/MTPRx (10600): In MtpReceiverandroid.hardware.usb.action.USB_STATE
E/MTPRx (10600): check value of boot_completed is1
E/MTPRx (10600): check booting is completed_sys.boot_completed
E/MTPRx (10600): Sd-Card path/storage/extSdCard
E/MTPRx (10600): Status for mount/Unmount :mounted
E/MTPRx (10600): SDcard is available
E/MTPRx (10600): The value of first_boot is 1
E/MTPRx (10600): [ 662] The value of first_boot is 1NORMAL SEQUENCE
E/MTPRx (10600): Received USB_STATE with sdCardLaunch = 0
E/MTPRx (10600): configured is false
I'm guessing this is the correct part of the log that pretains to the MTP/USB part. If not I have attached a full log.
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
xpmode said:
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I did that as quoted, nothing seems to have changed, What should I be looking for?
Thanks!
This problem has been encountered by tons of people and there are tons of threads, which I think I have read all of, but I still can't solve the problem. My problem started when I decided I want to put CM10.2 (cyanogenmod for those who don't know) on my Galaxy S3 (i9300 intl version). I use a mac and so I looked up how to root from a mac. I found this site and followed the instructions. After finishing, my phone was not rooted and for some strange reason, my camera stopped working. I decided to ignore that since I figured once I rooted it and put CM on it, it would solve itself. Note: I didn't make a backup. I know, stupid stupid stupid. Once I got CM on there however, the problem persisted. I have now spent 3 days and untold number of hours on this and I can't solve it.
The following is a log of everything I have done from the very beginning:
1. Tried to root using method from this site. It tells you to download a zip file which contains: heimdall suite 1.3.2 (mac) and CWM-SuperSU-v0.87.zip which further contains an apk called Superuser.apk and also su command for xbin. It also contains a file called s3pit.pit which you flash via heimdall first. Result of this was camera on original stock rom not working and not rooted.
2. I rooted my s3 using the proper method which involved using my PC using Odin3 v1.85 to flash CF-Auto-Root-m0-m0xx-gti9300.tar.md5. This worked fine.
3. Flashed clockworkmod recovery using Odin3 v.3.07 and file recovery-cwmtouch-6.0.3.2-GTI9300.tar
4. Installed CM 10.2 without any issues. Tried camera, no go.
5. I am in spain and bought my phone here unlocked. I did the best I could to find out what my original stock rom was. Using This thread as a guide I restored GT-I9300XXEMG4_KOR_MULTI_FACTORY which included new pit, modem and bootloader. Still no dice.
6. I read multiple posts in which people were able to fix the problem by simply putting the correct camera firmware .bin file into the /data/cfw folder. I downloaded every .bin I could find and put them in there but... no dice.
7. Using the dialer, I enter *#34971539# to find out what firmware and camera I have but nothing comes up. It just says "Standard Firmware"
8. I flashed an updated stock firmware: PHE-I9300XXUGMK6-20131228140138. Everything great... except for the camera
9. Opened up ADB and started looking for clues in the log. Here's the log I got under this ROM:
E/SecCameraHardware( 1919): camFW =
E/SecCameraHardware( 1919): FimcV4l2 init: error -1, VIDIOC_S_INPUT
E/SecCameraHardware( 1919): initCamera X: error, /dev/video0
V/SecCameraHardware( 1919): FimcV4l2 deinit EX
E/SecCameraHardware( 1919): createInstance: error, camera cannot be initialiezed
E/SecCameraHardware( 1919): Instance is not created
E/SecCameraCoreManager( 1919): Could not open camera 0: -38
D/SecCameraCoreManager( 1919): SecCameraCoreManager destroyed: pid=1919
I/SecCameraCoreManager( 1919): Destroying camera 0
E/CameraEngine(20826): service cannot connect. critical exception occured.
"destroying camera" (and soul)
I'm not convinced the fw files I placed in the /data/cfw folder are being recognized or used because where it says in the log "camFW=", the value is null. Other users' log files for this problem usually have a value in there for the firmware.
10. I decided to hell with this, I need my phone back to at least usable state so I reflashed my nandroid backup of CM10.2 (still no camera) but had a look at the log to see if it was different and it is. I guess because of exynos:
--------- beginning of /dev/log/main
D/exynos_camera( 1911): exynos_camera_get_number_of_cameras()
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41255c18)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_get_camera_info(1, 0x41738c18)
D/exynos_camera( 1911): Selected camera: S5K6A3
--------- beginning of /dev/log/system
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41902c18)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_get_camera_info(1, 0xbeed47d0)
D/exynos_camera( 1911): Selected camera: S5K6A3
V/CameraHolder( 6705): open camera 0
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41738bb0)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41738ba0)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_open(0x40dca004, 0, 0x40d8e8dc)
E/exynos_camera( 1911): exynos_camera_start: Unable to set inputs
E/exynos_camera( 1911): exynos_camera_open: Unable to start camera
E/CameraHolder( 6705): fail to connect Camera
E/CameraHolder( 6705): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 6705): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 6705): at android.hardware.Camera.<init>(Camera.java:366)
E/CameraHolder( 6705): at android.hardware.Camera.open(Camera.java:322)
E/CameraHolder( 6705): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:304)
E/CameraHolder( 6705): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder( 6705): at com.android.camera.Util.openCamera(Util.java:457)
E/CameraHolder( 6705): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:311)
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41902c18)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_get_camera_info(1, 0xbeed47d0)
D/exynos_camera( 1911): Selected camera: S5K6A3
V/CameraHolder( 6705): open camera 0
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41902bb0)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41902ba0)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_open(0x40dca004, 0, 0x41efbc44)
E/exynos_camera( 1911): exynos_camera_start: Unable to set inputs
E/exynos_camera( 1911): exynos_camera_open: Unable to start camera
E/CameraHolder( 6705): fail to connect Camera
E/CameraHolder( 6705): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 6705): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 6705): at android.hardware.Camera.<init>(Camera.java:366)
E/CameraHolder( 6705): at android.hardware.Camera.open(Camera.java:322)
E/CameraHolder( 6705): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:304)
E/CameraHolder( 6705): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder( 6705): at com.android.camera.Util.openCamera(Util.java:457)
E/CameraHolder( 6705): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:311)
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41902c18)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_get_camera_info(1, 0xbeed47d0)
D/exynos_camera( 1911): Selected camera: S5K6A3
V/CameraHolder(12444): open camera 0
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41738bb0)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_get_camera_info(0, 0x41738ba0)
D/exynos_camera( 1911): Selected camera: S5C73M3
D/exynos_camera( 1911): exynos_camera_open(0x40dca004, 0, 0x40d9b6cc)
E/exynos_camera( 1911): exynos_camera_start: Unable to set inputs
E/exynos_camera( 1911): exynos_camera_open: Unable to start camera
E/CameraHolder(12444): fail to connect Camera
E/CameraHolder(12444): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder(12444): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder(12444): at android.hardware.Camera.<init>(Camera.java:366)
E/CameraHolder(12444): at android.hardware.Camera.open(Camera.java:322)
E/CameraHolder(12444): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:304)
E/CameraHolder(12444): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder(12444): at com.android.camera.Util.openCamera(Util.java:457)
E/CameraHolder(12444): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:311)
To my knowledge, there is only one thing I have not tried yet which I read in another thread which is that in addition to putting the .bin FW files into /data/cfw, you also need to place them into /system/cameradata. For some reason, even with root access I cannot copy files into that folder. I get a permission denied if I try to do it with ES File explorer app and via ADB I cannot do an mv command between the data folder and that system folder. I'm not a very experienced linux user.
I really don't know where to go from here. I have a feeling it all went to sh*t with the original s3pit.pit file but I really do not have the expertise to know what could have happened there. I know very vaguely that a pit file allocates the partitions but I wouldnt know what the implications of changing it are. Yeah... shoulda done a full nandroid backup first. DOH!!!!
I feel your pain.. There is a pool of people out there, me included, that have this issue with the s3 and aosp ROMs. I hope a fix comes along soon.
How I fixed the camera error
I have had the same error as lots of other folk.
I flashed the AOKP latest nightly and the error occurred, needed to reboot after taking one photo.
I than flashed the latest Liquidsmooth rom and that did exactly the same.
Yesterday as the camera would not work after taking one photo without a reboot.
I did as suggested elsewhere and un-installed a lot of the apps to no avail.
I then decide to re-install the original AOKP rom that I first flashed.
aokp-i9300-kitkat-nightly-2014-03-27
I then installed all my apps using Titanium backup and guess what the camera works faultlessly.
All the apps are updated so not them causing the problem
Conclusion:
The cause of the camera failing is the Rom.
Both the Liquidsmooth and AOKP latest roms cause the same problem.
Not technically savy enough to understand why this should be but it is a fact.
Camera error Remedy is flash an earlier rom.
I may flash some later ones and see if I can determine when the error started happening.
Hope this help
If anyone does flash later roms than the one I did and no fault occurs please post which one here.