Database Users

Dead camera

Hey guys!
Hoping someone might be able to help. My camera stopped working about a year ago and I haven't been able to get it to work. Every time I try to use it my phone reboots. I've tried running every ROM available here, every radio, every SPL. At this point I figure it's probably hardware but I want to rule out every other possibility before I give up on it. Any suggestions ?
TY in advance.
PS. 32a Rogers - current radio is 6.35.16.19 - playing with gingerbread atm

I have the same issue with a Vodafone htc magic 32b. It started after the OTA of Vodafone to go to Android 2.2.1. I hoped it would work in Cyanogenmod 6.1 but it still gives reboots.
This is the log cat when I start the camera:
Code:
I/ActivityManager( 155): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera }
I/ActivityManager( 155): Start proc com.android.camera for activity com.android.camera/.Camera: pid=771 uid=10011 gids={1006, 1015}
I/WindowManager( 155): Setting rotation to 1, animFlags=1
I/ActivityManager( 155): Config changed: { scale=1.0 imsi=206/1 loc=nl_BE touch=3 keys=1/1/2 nav=3/1 orien=2 layout=18 uiMode=17 seq=8}
I/GPSButton( 155): Update State
I/ActivityManager( 155): Start proc com.ramesp.amissed for service com.ramesp.amissed/.LockWatchDog: pid=779 uid=10093 gids={1015}
E/mm-camera( 123): mt9t013_process_start: ioctl(MSM_CAM_IOCTL_ENABLE_OUTPUT_IND) error Invalid argument
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
D/RAMES ( 779): Registering--------------
D/Camera ( 771): app passed NULL surface
D/CameraSettings( 771): [antibanding-values=off,50hz,60hz,auto, antibanding=auto, effect-values=none,mono,negative,solarize,sepia,posterize,whiteboard,blackboa
rd,aqua, effect=none, exposure-compensation-step=0.5, exposure-compensation=0, focal-length=3.72, focus-mode-values=auto,infinity, focus-mode=auto, horizontal-v
iew-angle=51.6, jpeg-quality=90, jpeg-thumbnail-height=384, jpeg-thumbnail-quality=90, jpeg-thumbnail-size-values=512x384,0x0, jpeg-thumbnail-width=512, max-exp
osure-compensation=4, max-zoom=12, min-exposure-compensation=-4, picture-format-values=jpeg, picture-format=jpeg, picture-size-values=2048x1536,1600x1200,1024x7
68,512x384, picture-size=2048x1536, preview-format-values=yuv420sp, preview-format=yuv420sp, preview-frame-rate-values=15, preview-frame-rate=15, preview-size-v
alues=800x480,720x480,640x480,576x432,480x320,384x288,352x288,320x240,240x160,176x144, preview-size=384x288, vertical-view-angle=39.7, whitebalance-values=auto,
incandescent,fluorescent,daylight,cloudy-daylight, whitebalance=auto, zoom-ratios=100,102,107,109,114,117,123,128,131,138,141,148,155, zoom-supported=true, zoom=0]
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
V/camera ( 771): startPreview
It also reboots if I start any application that uses the camera e.g. goggles, barcode scanner,...
Would really like to have this fixed. Any suggestions?

my fix
try to reflash your rom if all else fail do a restore or flash of your stater rom and send it back to your carrier don't forget to unroot after that flash change your boot image back if not changed double check your fastboot

I've had this same issue. It looks from your logcat that the camera hardware works, it's just not loading properly.
The problem is that the camera's preferences file needs to be rewritten by the system. the solution is to adb shell into your phone, then go into /data/data/com.android.camera (or your Rom's specific directory; different Roms will likely have different directory names, but it shouldn't vary too much) and look for camera_hardware_preferences.xml (or your Rom's specific hardware preferences XML file for the camera) and move this to camera_hardware_preferences.xml_, then reboot.
Doing this will make your phone have to rewrite it's profile for camera hardware. Once done, it should work.

Findulmundo. I tried this and now my camera no longer crashes but is stuck on a black screen when starting the camera app. The camera_preferences.xml file is not being generated either. Any ideas?

Guys im having a similar issue, my camera will start normally but when i try to take a picture it will get stuck and wont shoot the pic. I can exit the app normally, no force close but im unable to take any pics any ideas?
Currently on cm5, already tried different sd cards, fastboot wipe and then reflashed the ROM, tried different roms also its still a no go though
Sent from my HTC Glacier using XDA Premium App

I'm not sure, but you should try to flash a new kernel - you'll find it in the dev section...
Btw. I'm using Ginger Yoshi RC 6.1 - to use it I needed to flash a new radio hboot and kernel - you can find the instructions in the ROM's thread step-by-step!

random reboots

Hy to all,
I have every third day a random reboot. And i don´t know why. The last reboot was today at 14:20 clock. I tried to make a logcat. I hope i make it right. when it´s wrong please tell how to make it and wait 2 or 3 days.
i am on PA 3.69 (07/22) and Franco 165
Thanks to all

To be honest, my gut tells me there is a deep derp in the hybrid engine since pa 3.0 that is causing all these random reboots. However, strangely it affects only certain group of people.
Many have tried to raise the issue, but the same answer was used to dismiss all of us: "Currently there is no known random reboot issue, do a clean install and gtfo". (Ok, they never said gtfo, it automatically appended in my mind.)
Don't blame them though, because the reboot is so random in nature, it can't be fix easily unless you want them to dig deep into 1 year+ of works and fix this derp for minority of users.

My Nexus 4 will get stuck and eventually (after about a minute of a black screen) reboot if I leave it charging after its already charged. Don't know WTF that's about, but I just try to check it and unplug it if its charged.

I took a quick look at your logs, the reboot happens when you were using whatsapp, twice, is it correct?
08-13 14:19:46.719 I/ActivityManager(506): START u0 {cmp=com.whatsapp/.Conversations} from pid 8481
08-13 14:19:47.049 E/WindowManager(506): Window Session Crash
08-13 14:19:47.049 E/WindowManager(506): java.lang.RuntimeException: Could not open input channel pair. status=-24
08-13 14:19:47.049 E/WindowManager(506): at android.view.InputChannel.nativeOpenInputChannelPair(Native Method)
08-13 14:19:47.049 E/WindowManager(506): at android.view.InputChannel.openInputChannelPair(InputChannel.java:91)
08-13 14:19:47.049 E/WindowManager(506): at com.android.server.wm.WindowManagerService.addWindow(WindowManagerService.java:2264)
08-13 14:19:47.049 E/WindowManager(506): at com.android.server.wm.Session.addToDisplay(Session.java:160)
08-13 14:19:47.049 E/WindowManager(506): at android.view.IWindowSession$Stub.onTransact(IWindowSession.java:111)
08-13 14:19:47.049 E/WindowManager(506): at com.android.server.wm.Session.onTransact(Session.java:123)
08-13 14:19:47.049 E/WindowManager(506): at android.os.Binder.execTransact(Binder.java:351)
08-13 14:19:47.049 E/WindowManager(506): at dalvik.system.NativeStart.run(Native Method)
Click to expand...
Click to collapse

MastaPole said:
Hy to all,
I have every third day a random reboot. And i don´t know why. The last reboot was today at 14:20 clock. I tried to make a logcat. I hope i make it right. when it´s wrong please tell how to make it and wait 2 or 3 days.
i am on PA 3.69 (07/22) and Franco 165
Thanks to all
Click to expand...
Click to collapse
Did you restore your hybrid settings throw the hybrid settings if you did that's your issue. Do a clean install and don't restore your hybrid settings.
Sent via BLACKED OUT LTE N4

ksilver89 said:
I took a quick look at your logs, the reboot happens when you were using whatsapp, twice, is it correct?
Click to expand...
Click to collapse
yes, that is right.
spaceman860 said:
Did you restore your hybrid settings throw the hybrid settings if you did that's your issue. Do a clean install and don't restore your hybrid settings.
Sent via BLACKED OUT LTE N4
Click to expand...
Click to collapse
I am on a clean install. Maybe my n4 is defect. Because sometimes my status bar freez and i can't scroll down
Sent from my Nexus 4 using xda app-developers app

[Q] Nexus 10 hangs every night - something in libEGL/OpenGL?

Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?

_anarion_ said:
Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?
Click to expand...
Click to collapse
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?

rlrbjr said:
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?
Click to expand...
Click to collapse
Hi!
I was able to find some old threads about this aptly named Sleep of Death issue, here for example.
Unfortunately no conclusion, most people seem to return their devices :/
Now I think this is indeed some massive memory leak, becasue I was able to see ADB logs with all processes stopping, and the screen blinking with lock screen once when this happened.
As for MovieMaker, this might be misleading - I froze it in TitaniumBackup but the issue still exists.
My plan now is to write a script that would run
Code:
adb shell dumpsys meminfo
every couple seconds/minutes and plot the memory usage until the issue strikes.
I will report here if I find anything.
Best regards,
anarion

I uninstalled Movie Editor (rather than freezing it) and my system is much better (so far). I have not had a single lockup. It still too early to know if this is a god long term solution but I will keep you informed.
Sent from my Nexus 10 using Tapatalk 4

Reboot loop due to WifiStateMachine bug in stock 5.0.1 update (i9500, Note 3 SM-N900)

A WiFi-related bug in Samsung's recent 5.0.1 Lollipop update causes devices to go into a continuous reboot loop (rebooting every 1-1.5 minutes) after certain conditions.
Known affected devices:
Samsung Galaxy S4 International (GT-i9500) on Android 5.0.1
Samsung Galaxy Note 3 International (SM-N900) on Android 5.0.1
If the device comes in range of an open wireless network with blank/no SSID, it attempts to connect to it. This adds the network to the list of known/configured networks with the network name being null. The next time WiFi is enabled (either through manual switching or a reboot), the WifiStateMachine goes through the list of configured networks as usual, checking each one. A String .equals() method is called on the name of each network, so upon reaching the null network the following fatal NullPointerException is caused, rebooting the device:
HTML:
I/WifiConfigStore(13460): null is a captive portal!
I/WifiConfigStore(13460): not authenticated yet
E/WifiConfigStore(13460): Not a HS20
E/WifiConfigStore(13460): Not a HS20
E/AndroidRuntime(13460): *** FATAL EXCEPTION IN SYSTEM PROCESS: WifiStateMachine
E/AndroidRuntime(13460): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime(13460): at com.android.server.wifi.WifiConfigStore.readNetworkVariablesFromSupplicantFile(WifiConfigStore.java:2079)
E/AndroidRuntime(13460): at com.android.server.wifi.WifiConfigStore.readNetworkVariableFromSupplicantFile(WifiConfigStore.java:2109)
E/AndroidRuntime(13460): at com.android.server.wifi.WifiConfigStore.loadConfiguredNetworks(WifiConfigStore.java:1940)
E/AndroidRuntime(13460): at com.android.server.wifi.WifiConfigStore.loadAndEnableAllNetworks(WifiConfigStore.java:586)
E/AndroidRuntime(13460): at com.android.server.wifi.WifiStateMachine$SupplicantStartingState.processMessage(WifiStateMachine.java:7341)
E/AndroidRuntime(13460): at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
E/AndroidRuntime(13460): at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
E/AndroidRuntime(13460): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(13460): at android.os.Looper.loop(Looper.java:145)
E/AndroidRuntime(13460): at android.os.HandlerThread.run(HandlerThread.java:61)
Solutions:
Enable Airplane Mode: reboot loop will end after next reboot as WifiStateMachine does not check networks if WiFi is off at boot
Factory reset: the list of configured networks is cleared, so the error-causing network is removed
The ideal workaround would be to delete the error-causing network (or all configured networks) without a factory reset, but networks can only be removed the normal way when WiFi is on and removing them from the shell requires root access (to delete a system file).
I have not been able to find a way to report this to Samsung.
EDIT 1: It looks like this bug only applies to null networks that have captive portals/require browser sign-in.

Hey,
I've got this bug on the S6 edge too
Since I'm rooted, maybe I can fix it without factory reset??
I reported this but here :
http://forum.xda-developers.com/showthread.php?t=3131416
[Q] Some "Null" Wifi puts phone into loop reboots

kaemon said:
Hey,
I've got this bug on the S6 edge too
Since I'm rooted, maybe I can fix it without factory reset??
I reported this but here :
http://forum.xda-developers.com/showthread.php?t=3131416
[Q] Some "Null" Wifi puts phone into loop reboots
Click to expand...
Click to collapse
If you're rooted, a possible solution might be to remove the null network from the wpa_supplicant.conf file. I'm not sure where it is located, possibly /data/misc/wifi/wpa_supplicant.conf

I don't think there is a real 'null' wifi anywhere...
Anyway, I managed to fix my problem thanks to application on the market, see this post : http://forum.xda-developers.com/showthread.php?p=60349787
Sent from my SM-G925F using XDA Free mobile app

For me it wasn't `wpa_supplicant.conf` that was causing the problem, it was
`/data/misc/wifi/networkHistory.txt`
I deleted this file and my tablet returned back to normal

Gcam not working

I've been trying tons of different gcam versions, some of them open up with a compatibility pop up, but do seem to work. However a lot of confirmed working ones, by other people, close immediately after opening them. My phone has been running China developer Rom for quite a while now, flashed through XiaomiToolV2 and was recognized as Lavender. It was also bought from the Xiaomi online store in China.
Here is a the error log MIUI gives me when I press View Summary after the crash:
java.lang.RuntimeException: Unable to create application com.google.android.apps.camera.legacy.app.app.CameraApp: java.lang.SecurityException: Failed to find provider com.google.android.gsf.gservices for user 0; expected to find a valid ContentProvider for this authority
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5954)
at android.app.ActivityThread.access$1200(ActivityThread.java:200)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1673)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6810)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
Caused by: java.lang.SecurityException: Failed to find provider com.google.android.gsf.gservices for user 0; expected to find a valid ContentProvider for this authority
at android.os.Parcel.createException(Parcel.java:1953)
at android.os.Parcel.readException(Parcel.java:1921)
at android.os.Parcel.readException(Parcel.java:1871)
at android.content.IContentService$Stub$Proxy.registerContentObserver(IContentService.java:849)
at android.content.ContentResolver.registerContentObserver(ContentResolver.java:1988)
at android.content.ContentResolver.registerContentObserver(ContentResolver.java:1977)
at lhq.a(Unknown Source:34)
at lhq.b(Unknown Source:3)
at lhq.a(Unknown Source:0)
at com.google.android.apps.camera.legacy.app.app.CameraApp.onCreate(Unknown Source:24)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1155)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5949)
... 8 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.content.ContentService.registerContentObserver(ContentService.java:340)
at android.content.IContentService$Stub.onTransact(IContentService.java:76)
at com.android.server.content.ContentService.onTransact(ContentService.java:262)
at android.os.Binder.execTransact(Binder.java:730)
Hope someone can decipher this and help me out here.

This should be causing because of China dev. rom, I think.

Its been the same situation since I bought this phone, so same happened on China stable as well. Never seen anyone talk about having a similar problem.

kogadin said:
Its been the same situation since I bought this phone, so same happened on China stable as well. Never seen anyone talk about having a similar problem.
Click to expand...
Click to collapse
Unlock bootloader and flash Global EEA stable ROM and try again. But don't lock the bootloader.