[ISSUE] Camera Error 100 - Motorola Atrix HD

Ok, guys. So I actually ran into a big issue. My camera died. I was running CM10.1 until I noticed I had a problem, so I flashed back to Stock ICS, and I still have the same problem. I pulled a logcat *:E, and I noticed a MAJOR error pop up. I'm hoping someone can look through this logcat and maybe figure out what it means. It all happens at the same time. Here's a brief; full file included.
Code:
08-12 06:27:57.456 2701 2786 E CameraHalWatchdog: Detected hang in camera library
08-12 06:27:57.456 2701 2786 E CameraHalWatchdog: Forcing restart of mediaserver
08-12 06:27:57.476 2276 2276 E Camera : Error 100
08-12 06:27:57.476 2276 2276 E MotoCameraDevice: Camera Error: 100
Here's hoping my camera isn't completely shot. :fingers-crossed:
I'm gonna reflash CM10.1 and run logcat again with the same parameters. I'll post that logcat, also. Thanks, guys.
EDIT1:
Strangest thing..... Face Unlock works.....
EDIT2:
So, I pulled logcats for CM10.1 and CM10.2. Both basically gave me the same thing. Except this time, I noticed something. Look at the end of CM10.2's logcat. Notice the AudioService died. I noticed it in the other 2, but ignored it. I'll pull a complete logcat tomorrow. Time for bed.

Another Update
Alright, guys. New update. I downloaded an app from the App Store called Mirror. On load, the front camera is used, bypassing the rear camera entirely. Guess what. No problems. It also allows pictures to be taken. Every chance I have to post an update, I will.

Kinda saddened that not a single person except myself has replied to this..... But, I'm still researching. Maybe I can save someone else the troubles that I've had one day.

FINAL UPDATE:
I finished my research. Unfortunately, my camera is kaput. Error 100 is thrown when the software cannot connect at all to the hardware, either that the connections have come loose, or it Just died altogether. More than likely, this arose after dropping my phone near the camera, but anything is possible. Thank goodness the rear camera only cost ~$10. For anyone else that has these troubles, here's the solution. Goodbye, XDA.

moebius_2033 said:
FINAL UPDATE:
I finished my research. Unfortunately, my camera is kaput. Error 100 is thrown when the software cannot connect at all to the hardware, either that the connections have come loose, or it Just died altogether. More than likely, this arose after dropping my phone near the camera, but anything is possible. Thank goodness the rear camera only cost ~$10. For anyone else that has these troubles, here's the solution. Goodbye, XDA.
Click to expand...
Click to collapse
Thanks for the solution,
I think I am facing the same issue, My rear camera doesnt open at all only front is working. I hope I will be able to get it repaired here in mumbai.

Related

BP Core Dump

I've had fairly mediocre success with the camera/camcorder app so far. they're terribly slow to open, the camera app sometimes has a hard time focusing and the camcorder app is continuously refocusing while recording to the point that it looks like the focus drops and then it needs to start over. i've confirmed these issues on my wife's phone, so i know they're not related to just my device.
yesterday, while trying to use the camera app, a black screen appeared with text (almost like a command screen) with "BP Core Dump" or something similar.
the only related thread i've seen where this has occurred was directly related to cyanogen's ROMs, to which i've never used.
640k said:
I've had fairly mediocre success with the camera/camcorder app so far. they're terribly slow to open, the camera app sometimes has a hard time focusing and the camcorder app is continuously refocusing while recording to the point that it looks like the focus drops and then it needs to start over. i've confirmed these issues on my wife's phone, so i know they're not related to just my device.
yesterday, while trying to use the camera app, a black screen appeared with text (almost like a command screen) with "BP Core Dump" or something similar.
the only related thread i've seen where this has occurred was directly related to cyanogen's ROMs, to which i've never used.
Click to expand...
Click to collapse
I've also seen a BP Core Dump, I was using a charger for another phone and it didn't fit snugly. It also said "Trying to activate USB" and eventually rebooted. All this happened on the lockscreen after waking it up.
here's holding out hope for an update soon. love this phone, the hardware is solid. i think moto rushed 2.3.4, though.
640k said:
here's holding out hope for an update soon. love this phone, the hardware is solid. i think moto rushed 2.3.4, though.
Click to expand...
Click to collapse
So after the core dump, I decided to reset my phone and last night, the camera app locked up and rebooted the phone. Today I called tech support and they're sending me a new one. I've read the backorder threads, so it'll be interesting to see when it arrives.
I've looked into this bug a bit more and narrowed it down to /system/bin/mdm_panicd which runs as root. Most likely a bootloader crash.
This is some of the output found in 'strings' for the file , it is what I saw in the "terminal" before it reset.
Code:
BP paniced
Into BP core dump mode
Trying to open USB ...
Also a line "/dev/graphics/fb0" which is what likely created the terminal.
It writes a log to /sdcard/coredump… this may have been on my device which was deleted if I remember correctly.
There was also another thread at droidforums about this. androidforums.com/motorola-droid-3/387878-my-d3-crashed-bp-paniced-error.html
Looking around it looks like there are two bugs for cyanogenmod4milestone opened last year related to this. It was eventually fixed. So this probably can happen on similar Moto devices.
code.google.com/p/cyanogenmod4milestone/issues/detail?id=22
code.google.com/p/cyanogenmod4milestone/issues/detail?id=27
The process has something to do with the modem. Through there's not much info beyond the source code and these trackers. There is a prop in build.prop just after the ril related entries.
persist.mot.mdm_panicd.nopanic=no to allow the dump
I have since had a replacement unrelated to this issue. I've tried a few things mentioned in the above trackers, but cannot reproduce it.
I've attached the strings output for reference, don't know where to go with this but thought I should throw it there.
wow, nice find. all i found was the cyanogenmod stuff
640k said:
wow, nice find. all i found was the cyanogenmod stuff
Click to expand...
Click to collapse
Was hoping for an exploit but very unlikely without it being reproduced.

[Q] N6 Camera Issues

Anyone else having issues like this? As far as the camera cannot connect error I have read about people with that problem and I literally tried every single suggestion. I'm not a n00b so this is really bugging me (see what I did there) Anyway all of these pictures are with the same phone. On stock 5.1.1 I RARELY could connect to the camera. With Android M preview I can at least connect about 80% of the time. However, results aren't always good. Should I just suck it up and call and get it replaced? Or is the actual phone OK and I'm one of the unlucky guys with the camera bug.
jacobryan_c said:
Anyone else having issues like this? As far as the camera cannot connect error I have read about people with that problem and I literally tried every single suggestion. I'm not a n00b so this is really bugging me (see what I did there) Anyway all of these pictures are with the same phone. On stock 5.1.1 I RARELY could connect to the camera. With Android M preview I can at least connect about 80% of the time. However, results aren't always good. Should I just suck it up and call and get it replaced? Or is the actual phone OK and I'm one of the unlucky guys with the camera bug.
Click to expand...
Click to collapse
I had to RMA mine because of the camera with same problems but my camera quit working completely.
do you have root? have you tried increasing your voltges, like 20-30mV?
renegaderon said:
I had to RMA mine because of the camera with same problems but my camera quit working completely.
Click to expand...
Click to collapse
Same here. Had to RMA. Unable to connect and purple pixilation.
Thanks guys. Got mine swapped out at the store. Camera pops up right away and works awesome. Other things I noticed is that this new one perfectly fits my case mate folio case. The other power button must have been off by a little bit. This new one also got 50k+ on Antutu. I was lucky if the old one hit 43k.

Problem with the Front Facing camera.

I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
FunYunZ said:
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
Click to expand...
Click to collapse
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
lennie said:
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
Click to expand...
Click to collapse
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
FunYunZ said:
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
Click to expand...
Click to collapse
hard reset = factory reset
have you tried using Odin and doing a fresh FW install?
htc-8925 said:
have you tried using Odin and doing a fresh FW install?
Click to expand...
Click to collapse
I have not. I did a factory reset.
My friend had the same issue.
whiteangelcl said:
My friend had the same issue.
Click to expand...
Click to collapse
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
FunYunZ said:
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
Click to expand...
Click to collapse
sounds like they're sending you a replacement. make sure you are satisfied with the replacement because they might send you a refurb.
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
emazens said:
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
Click to expand...
Click to collapse
Nope, Samsung never got back to me. I just went to the Tmobile store and they were like, yep, never seen that before. So they overnight me a new one.
I just begun to have the same issue on my phone and I'm not happy after spending 1k on it. I'm going to my career tomorrow but unfortunately don't know I this will be resolved. Please Let me know what Samsung did for you.
Same problem on my Note8. Following for solution.
solution anyone?
did anyone of u find a solution?
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
i'm suffering with this problem presently and is trying to find a solve.
totaldepth said:
Same problem on my Note8. Following for solution.
Click to expand...
Click to collapse
i am seeing when i open camera ,camera failed
can anyone advise on how to fix?
If you did not mistreat the device, dropped it or fiddle with system settings or something of the sort, warranty is the all time solution for these problems
Hey my note 8 front camera just experienced the same issue. I've talked to Samsung support, and frankly it seems like it is a hardware issue. It is recommended that you use Samsung Support to make a service request. Free shipping both ways, so if you can live without your phone for a week or two (or have a backup phone to use), that's the route I recommend people going.
Original Problem:
MENU / COMMON APPLICATION ( NATIVE) - CAMERA / VIDEO - CAMERA EFFECTS NOT WORKING
Problem found:
FRONT CAMERA FAIL
Solution:
REPLACED COMPONENT
Click to expand...
Click to collapse
Did you manage to find the cause of the problem?
My front selfie camera has the same problem!
sorry to raise up this issue again.. my s8+ is from Indonesia region, and facing the same issue when try to use front camera is failed with notification Warning Unknown Error Occured.
already try Wipe cache partition and hard reset but still facing the same issue..
but if i use front camera for video call thru whatsapp it's working fine, but yet again if check thru *#0*# for Front Camera it's Camera Failed..
is it hardware issue or FW issue ?
Front Facing camera has double image
Has anyone found a fix for this issue yet? Mine started this issue last year and I haven't found a remedy for it yet. Ugh.

Camera issue on Stock

Stock, unrooted, newly purchased Moto G5S Plus. I'm having an issue with the camera. It seems to not want to focus (or un-blur) 90% of the time. The other 10% (during which I have no idea what sort of magic I've done) it takes wonderful photos. I've tried third-party apps, clearing the cache in recovery, and Safe Mode. I'm upset and Motorola doesn't seem to want to help me. I'm just outside the return period (thanks for that, Motorola!) and am wondering what the community here thinks? I can always try to root and install a custom ROM but I don't know if that will help.
Hey so I've discovered if I tap my knuckles against the back of my phone either on or near the rear camera the picture immediately clears. The issue keeps happening and the tapping trick keeps working -- the tapping trick does not result in the picture going blurry again so I'm guessing it's an issue with software and not hardware. Just wanted to throw this out there in case someone else was having the same problem.
Motorola did tell me to send the phone back, but this was before I tried tapping it. I really don't want a used phone (this is my first new phone in like forever) so I'm tempted to just keep it as-is and hope the tapping keeps working.
Picture processing is terrible on this phone...
And it doesn't seem this phone is having good camera sensors..
Pictures come out blurry most of the times...
Anyways you can always try gcam after flashing a 64bit rom...
strangelady said:
Hey so I've discovered if I tap my knuckles against the back of my phone either on or near the rear camera the picture immediately clears. The issue keeps happening and the tapping trick keeps working -- the tapping trick does not result in the picture going blurry again so I'm guessing it's an issue with software and not hardware. Just wanted to throw this out there in case someone else was having the same problem.
Motorola did tell me to send the phone back, but this was before I tried tapping it. I really don't want a used phone (this is my first new phone in like forever) so I'm tempted to just keep it as-is and hope the tapping keeps working.
Click to expand...
Click to collapse
Tapping on the phone causing proper focus would indicate a hardware problem. You should return under warranty.

main camera blurr

Hi,
After the first 2020 ota update the camera started to get blurred and now is completely useless.
So i looked at the changelog and the update "fixed" something related to QRcode reading. So they must have messed something up.
Anyone knows anything about it?
Model: ZE620KL 128gb rom, updated to latest firmware, rooted with magisk and with twrp.
Thanks.
Additionally, wide camera works fine so far. But still it is strange that sometimes the main camera works and right after few minutes it gets all blurr again.
Hello, I have the same problem. It looks like the update killed a part of the camera. Your OIS is broken now. You can either replace your camera (around $10) or, as I did it, you can try to tap on the camera module. It may fix it temporary. A little bump could also work.
I am having a similar issue. Autofocus works fine for images close to the camera. Seems to be related to the QR code update mentioned by @Gyplay.
My phone has been serviced 3 times during warranty (free). It just died 20 days after receiving it. Then, around its 4th month of life it stopped holding charge. Around it's 10th month it just died again. No falls, not a single scratch and no liquid spills...
Now I have been living with this issue with the camera for almost a year...
Never had issues with any of my previous phones...
Perhaps I was unlucky, but will never buy an asus phone again.

Categories

Resources