ACER A500 camera issues

davieso

Member
Oct 23, 2011
1
0
I started having a problem with the rear cam. When I start the cam app it takes a little while then when it comes up the actual cam app frame is gray, no picture. I can switch to the front cam but nothing working on the rear cam. I have checked to make sure nothing is obstructing the camera and have removed recently downloaded apps to no avail. The app eventually crashes, log is below...

09:44:27.750 <131>[InputManagerService]: Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@40b89ac0 (uid=10033 pid=229)
09:44:41.660 <131>[ActivityManager]: Duplicate finish request for ActivityRecord{408b2570 com.android.camera/.Camera}
09:44:42.160 <131>[ActivityManager]: Activity pause timeout for ActivityRecord{408b2570 com.android.camera/.Camera}
09:44:51.660 <131>[ActivityManager]: Launch timeout has expired, giving up wake lock!
09:44:52.170 <131>[ActivityManager]: Activity idle timeout for ActivityRecord{40d0dd70 com.android.camera/.Camera}
09:45:37.840 <131>[ActivityManager]: Duplicate finish request for ActivityRecord{40d0dd70 com.android.camera/.Camera}
09:45:49.640 <131>[ActivityManager]: Activity pause timeout for ActivityRecord{40ad0920 com.android.camera/.Camera}
09:46:24.790 <131>[InputManagerService]: Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@40b89ac0 (uid=10033 pid=229)
09:47:00.700 <85>[NvOmxCameraSettingsParser]: Param type 13 not supported
09:47:00.700 <85>[NvOmxCameraSettingsParser]: Param type 49 not supported
09:47:01.010 <85>[ImagerODM-mt9p111]: SensorYuv5_SetPowerLevel: Can not open camera device No such file or directory
09:47:01.010 <85>[ImagerODM-mt9p111]: SensorYuv5_SetMode: ioctl to set mode failed Bad file number
09:47:01.010 <85>[ImagerODM-mt9p111]: SensorYuv5_SetMode: ioctl to set mode failed Bad file number
09:47:01.340 <1198>[Camera]: Error 1
09:47:01.340 <1198>[CameraErrorCallback]: Got camera error callback. error=1
09:47:01.450 <131>[InputManagerService]: Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@40a0c3c8 (uid=10112 pid=3308)
09:47:01.460 <3308>[IInputConnectionWrapper]: showStatusIcon on inactive InputConnection
09:47:07.870 <131>[ActivityManager]: Activity pause timeout for ActivityRecord{40ad0920 com.android.camera/.Camera}
09:47:08.020 <131>[InputManagerService]: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@409d52b8
09:47:08.590 <3308>[webcore]: Can't get the viewWidth after the first layout
09:47:30.890 <3308>[webcore]: Can't get the viewWidth after the first layout
09:47:43.300 <3308>[webcore]: Can't get the viewWidth after the first layout
09:48:03.980 <131>[ActivityManager]: Launch timeout has expired, giving up wake lock!
09:48:04.010 <131>[ActivityManager]: Activity idle timeout for ActivityRecord{40ad0920 com.android.camera/.Camera}
09:48:06.490 <131>[ActivityManager]: ANR in com.android.camera (com.android.camera/.Camera)
Reason: keyDispatchingTimedOut
Load: 1.74 / 2.09 / 1.03
CPU usage from 9159ms to 272ms ago:
96% 253/android.process.media: 93% user + 2.6% kernel / faults: 3391 minor
7.8% 85/mediaserver: 7.8% user + 0% kernel
7.4% 131/system_server: 3.8% user + 3.5% kernel / faults: 49 minor
3.7% 1198/com.android.camera: 3.3% user + 0.3% kernel / faults: 13 minor
2.8% 188/com.android.systemui: 2.6% user + 0.1% kernel / faults: 33 minor
2.8% 444/com.google.android.apps.plus: 2.3% user + 0.4% kernel / faults: 159 minor
1.5% 105/dock_detect_daemon: 0% user + 1.5% kernel
0.4% 82/surfaceflinger: 0% user + 0.4% kernel
0.4% 848/org.antivirus: 0.2% user + 0.2% kernel / faults: 46 minor
0.1% 100/irq/182-3d: 0% user + 0.1% kernel
0% 183/dhd_dpc: 0% user + 0% kernel
0% 185/wpa_supplicant: 0% user + 0% kernel
0.1% 884/logcat: 0.1% user + 0% kernel
62% TOTAL: 57% user + 5% kernel
CPU usage from 570ms to 1126ms later:
90% 253/android.process.media: 85% user + 5.4% kernel / faults: 31 minor
83% 1080/Binder Thread #: 83% user + 0% kernel
1.8% 1077/Binder Thread #: 1.8% user + 0% kernel
1.8% 1082/Binder Thread #: 1.8% user + 0% kernel
1.8% 3077/Binder Thread #: 0% user + 1.8% kernel
1.8% 3078/Binder Thread #: 1.8% user + 0% kernel
12% 131/system_server: 3.6% user + 9% kernel / faults: 5 minor
7.2% 155/InputDispatcher: 1.8% user + 5.4% kernel
1.8% 135/Compiler: 1.8% user + 0% kernel
1.8% 138/SensorService: 0% user + 1.8% kernel
1.8% 139/er.ServerThread: 1.8% user + 0% kernel
1.8% 270/er$SensorThread: 1.8% user + 0% kernel
1.8% 289/Binder Thread #: 1.8% user + 0% kernel
1.8% 1176/Binder Thread #: 0% user + 1.8% kernel
7.1% 85/mediaserver: 7.1% user + 0% kernel
7.1% 128/Playback Thread: 7.1% user + 0% kernel
5.4% 444/com.google.android.apps.plus: 3.6% user + 1.8% kernel / faults: 19 minor
5.5% 1198/com.android.camera: 5.5% user + 0% kernel / faults: 1 minor
3.7% 3386/er$SensorThread: 3.7% user + 0% kernel
3.6% 188/com.android.systemui: 3.6% user + 0% kernel / faults: 3 minor
3.6% 188/ndroid.systemui: 3.6% user + 0% kernel
1% 82/surfaceflinger: 0% user + 1% kernel
1% 97/SurfaceFlinger: 0% user + 1% kernel
1.8% 105/dock_detect_daemon: 0% user + 1.8% kernel
1.8% 105/dock_detect_dae: 0% user + 1.8% kernel
1.2% 884/logcat: 0% user + 1.2% kernel
71% TOTAL: 58% user + 13% kernel
09:48:11.860 <131>[ActivityManager]: Activity pause timeout for ActivityRecord{40ad0920 com.android.camera/.Camera}
09:48:11.940 <3425>[dalvikvm]: Refusing to reopen boot DEX '/system/framework/com.acer.android.os.jar'
09:48:12.510 <131>[ActivityManager]: Activity pause timeout for ActivityRecord{40ccc228 com.acer.android.nidus/.NidusActivity}
09:48:21.360 <131>[ActivityManager]: Launch timeout has expired, giving up wake lock!
09:48:21.920 <131>[ActivityManager]: Activity idle timeout for ActivityRecord{40ccc228 com.acer.android.nidus/.NidusActivity}
09:48:22.530 <131>[ActivityManager]: Activity idle timeout for ActivityRecord{40ad0920 com.android.camera/.Camera}
09:48:31.070 <131>[ActivityManager]: Activity pause timeout for ActivityRecord{40ad0920 com.android.camera/.Camera}
09:48:31.250 <131>[InputManagerService]: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40bc8218
 

Icebike

Senior Member
Apr 28, 2011
1,523
186
Shut down everything else and see if it works.
First candidate for things to shutdown is your antivirus. (These things are a total waste of time and resources on Android if you buy from the market or Amazon, and they will never catch a virus you load from dodgy web sites.)

Check to see if your camera is set to store on the Tablet or the External_SD, and switch it to the other, on the assumption the storage is corrupt.
Turn off GPS, And use the wrench in the camera settings to turn off "store location", and reset to defaults.

Its possible that your rear camera simply failed, and needs warranty service.

But before we spend a lot of time on this issue, please tell us if this is a rooted tablet or if it is stock, and which version of honeycomb are you running.
 
Last edited:

spexwood

Member
May 11, 2011
229
18
I would try a factory reset and BEFORE reinstalling your apps, try the camera. If same problem, then its hardware and you need to get a hold of Acer. If no problem, then it was something you installed OR simply a software failure (which was obviously fixed by the reset).

Also, if the factory reset fixed the issue, then reinstall apps one-by-one, checking the camera in-between. This ill help you find the culprit.

I.hate suggestiing factory resets, but sometimes it just fixes problems that can't be fixed otherwise (or are a pain to fix).

Sent from my A500 using Android Tablet Forum
 

Douvie

Senior Member
Jun 10, 2011
1,030
71
There is an issue with the camera glass lifting or coming off. Maybe you got a bit of dust/dirt under glass. Or maybe you've touch the camera glass/lens with oily fingers - this can cause the glass to go milky like. Big problem with cameras that have plastic insteadd of glass.
 

ned

Member
Jan 4, 2012
4
0
have you solved this problem mate? it looks that i'm having similar problem with my a500 and i cant figure it out...
 

Douvie

Senior Member
Jun 10, 2011
1,030
71
have you solved this problem mate? it looks that i'm having similar problem with my a500 and i cant figure it out...
Don't know. He has not informed us that the problems is solved. Have you tried Icebike's suggestion?
 
Top