Closed GoogleCodeExporter closed 9 years ago
I cannot seem to reproduce the problems, please try to find something in common
or a way we can reproduce it.
Just a wild guess based on you description:
The first and may be the third problems are probably caused by entering custom
menu (400plus,shortcuts) and then interrupting it somehow (i.e. not leaving the
menu). Try not to leave the menu with focus/shot button or by any other means
of interrupting it, at least until we have a better way of handling the menus.
Original comment by fired...@gmail.com
on 10 Apr 2011 at 1:54
I know random locks-up are hard to reproduce (precisely due to their random
nature), but unless I can reproduce a problem, there is little I can do to
solve it, sorry.
Original comment by eduardo....@gmail.com
on 10 Apr 2011 at 8:00
I understand that I have no precise ways to reproduce it.
I've encountered not one, but a couple lock ups during last night when working.
As I'm working, I can't exactly pay attention to the problem, and it's all in
the dark as well.
I can tell you, I'm not using the 400plus menu at all.
The most I use is change to ISO3200, which is why I request to bring back the
disable the SC menu and change the DP back to an ISO button.
All I do is take pictures, press the playback button and show people the image
taken.
When I stand aside to review the pictures and when deleting some, I notice that
the left and right buttons are no longer working and there for it's a form of a
lock up.
The left and right buttons locking up is the one I've experienced the most.
Try and do what I do.
Take pics, review them, press shutter to turn off screen, and repeat for a few
pictures.
Then review the pictures and delete them.
That's the best I can do, for steps to reproduce the problem.
Original comment by kay...@gmail.com
on 10 Apr 2011 at 11:14
Ok, let's try some guesswork... could it be that you accidentally press both
the shutter and one of the cursor buttons at the same time? From your
description of your workflow, looks like you quickly change from review mode to
shot mode back and forth.
[Not trying to blame you, this is a bug nevertheless, just wanting to isolate
the cause.]
Original comment by eduardo....@gmail.com
on 11 Apr 2011 at 6:24
No, I don't push the shutter and one of the cursors at the same time.
I push the shutter only when I need to exit playback mode and back into
shooting mode, or after viewing the image.
Yeah, I'm a club photographer, so I take photos, and review them quickly, then
exit playback mode.
Then once in a while I would stand aside and go back a few pictures and delete
the bad ones, and like I said the camera would lock up once in a while.
Gets frustrating, but since I have a battery grip, doing a quick battery pull
is no problem.
Original comment by kay...@gmail.com
on 11 Apr 2011 at 9:02
Our code intercepts the cursor buttons when the user has his face on the camera
(for both the "ISO in viewfinder" and the "nose affair" features); but we know
that the face sensor does not work when the display has been turned off (issue
reported by this same user, by the way). If our code mistakenly interprets that
the user has his face on the camera, then the LEFT and RIGHT buttons would do
nothing at all.
Just more guessing... I'll do more tests as soon as possible.
Original comment by eduardo....@gmail.com
on 11 Apr 2011 at 1:06
I have been bashing the camera for a good amount of time, trying to reproduce
this, but I couldn't; I tried to hit all the paths and buttons that I could
think of, to no avail...
I am not saying that this bug does not exist, but until we find a sequence to
reproduce the issue, I am afraid that I cannot do much more about it; sorry.
Original comment by eduardo....@gmail.com
on 11 Apr 2011 at 7:02
I made some HDR shots this evening, with HandWave Script configured to activate
Ext. AEB with 5 shots. I've used the camera in this setup for about half an
hour and did not get any lockups... Still I reviewed the taken photos with the
Play button.
This weekend I'll make extreme use of the camera, hopefully I'll get some
results.
Original comment by fired...@gmail.com
on 11 Apr 2011 at 7:22
Hmm. I don't have another XTi to test this on. Maybe it's my camera only?
I can make a video of the problem happening.
I'll see if I can record what I'm doing and we'll see if it happens.
I'll post a link here when I have a video.
Don't worry. I understand that you would need to have replicated the problem to
troubleshoot what's going on exactly.
Original comment by kay...@gmail.com
on 13 Apr 2011 at 7:24
I have an idea of what may be happening, and how to fix it; you may want to
wait for an update, before wasting your time on this. Thanks.
Original comment by eduardo....@gmail.com
on 13 Apr 2011 at 7:48
I have the video! I was able to replicate it. I do have an idea however.
It MAY have something with the idle time that is going on in between taking
photos.
HOWEVER, I'm only able to replicate it with my 580EXII attached, as my work
requires a flash.
I have my auto shut off at 30 seconds, and my image view time at 8 seconds.
It may be a combination of the two wait times over a few shots, and then when I
delete something I find out that the buttons are locked up.
Will link you to the video download as soon as it's uploaded.
Original comment by kay...@gmail.com
on 13 Apr 2011 at 7:58
Here you go. Each video is a 100MB, already compressed.
I hope these may be of use.
Video 1: http://www.mediafire.com/?g7l84sg69lmjye4
Video 2: http://www.mediafire.com/?bsg4fgeyxm6ym64
Original comment by kay...@gmail.com
on 13 Apr 2011 at 8:23
I tried to configure my camera as similar to yours as possible, and then
repeated the same sequence of buttons you show on your videos; but after lots
of attempts, I still could not lock my camera. I do now own a flash, so if you
have determined that it only happens when you attach one, I will probably never
be able to reproduce it here.
Let's try plan B: I can send you special versions of AUTOEXEC.BIN, then you
test them and report back. It is going to be slow and tedious, but unless you
are willing to send me a flash, I do not see what else we can do.
Attached to this comments there are two files; please rename them to
AUTOEXEC.BIN, and try if you can reproduce the bug with each of them. Many
thanks.
Original comment by eduardo....@gmail.com
on 13 Apr 2011 at 8:59
Attachments:
Hold on, I actually remember that the camera has locked up on me WITHOUT an
external flash attached.
I was actually on the bus headed home, so I would review my photos to cut down
the workflow afterwards.
The camera has locked up in the same way before, just viewing photos.
Original comment by kay...@gmail.com
on 13 Apr 2011 at 11:09
Yes, I managed to lock my camera once without a flash, too; but I cannot repeat
it, and thus I cannot fix this. Could you please test the attached files and
report back? Many thanks for your patience.
Original comment by eduardo....@gmail.com
on 14 Apr 2011 at 6:37
I found a way to reproduce something similar to what you show in the Videos...
I played with some new flags and found FaceStatus flag which shows what reads
Face Sensor...
so while I played with that flag I was able to reproduce this problem.
1. Camera in normal display (the main white screen)
2. put your finger on the face sensor ... so the display turns off
3. press play button while holding your finger on face sensor
4. photos preview shows up and left/right btns not working ... only the dial...
so if that turns to be your problem it could be a broken face sensor (or
somehow the external flash is breaking its function)
it turns to be the same if you activate MENU instead the preview (PLAY) with
finger on the sensor. checked w/o the CF card to see how is working the OFW and
its working normally.
Original comment by fired...@gmail.com
on 17 Apr 2011 at 11:23
FaceStatus flag and FLAG_FACE_SENSOR are the same actually.
Original comment by fired...@gmail.com
on 18 Apr 2011 at 12:04
Precisely, the attached AUTOEXEC.BIN.2 file has all the face sensor logic
disabled; "ISO in viewfinder" and "the nose affair" will not work with that
version, but buttons will work normally in any dialog, even if we have a bug in
that path. I am waiting for user feedback, to confirm whether the problem is
there or somewhere else.
Original comment by eduardo....@gmail.com
on 18 Apr 2011 at 9:05
I just made a change that solves the issues presented on comment #16, and could
solve your issue, too; please test next nightly build.
Original comment by eduardo....@gmail.com
on 20 Apr 2011 at 10:02
Mine just locked up while doing a timelapse with the intervalometer.
It was on Av mode, 2 sec intervals, manual focus.
The blue LED was blinking as it would normally do during a timelapse however no
button would respond and I had to take the battery out.
The screen was displaying the standard screen that shows you ISO/shutter
speed/etc
Original comment by b...@bbrks.me
on 22 Apr 2011 at 5:23
what version/revision ?
Original comment by fired...@gmail.com
on 22 Apr 2011 at 11:11
I experienced the "camera freeze" while in the 400plus "Settings menu"
adjusting values with the Av button. It occurred soon after I adjusted an
Intervalometer setting and then pressed the SET button to save my settings.
There does not seem to be any rhyme or reason for why this happens yet... I
tried over a dozen more times to repeat the problem and could not reproduce it
again. I will continue to try to determine a reason for this.
The "camera freeze" required removal of the battery to continue. The version
was Release "20110425-0".
Original comment by mike.guf...@gmail.com
on 25 Apr 2011 at 9:03
Oooooo. Interesting. Sorry, i haven't had time to play around with the camera
to test some more.
I just work, and if there's a problem, battery pull haha.
But thank you to others finding out the problem and testing as well!
Original comment by kay...@gmail.com
on 28 Apr 2011 at 2:19
Any updates on this, please?
Original comment by eduardo....@gmail.com
on 18 May 2011 at 6:40
So far, there hasn't been any lock ups! So kudos! :)
I've just kept shooting and shooting during work, and no problems with locking
up!
HOWEVER, there is one thing.
Every now and then after taking a photo, (I have my review time set to 8 to
show the people right after), I accidently hit any button that brings the
camera out from review mode back into shooting mode.
So when I show the people, they say there's nothing on the screen, that's how I
know a button was pressed. (Most likely the shutter was half pressed)
So when they say there's nothing, I go and push the playback button, but
nothing occurs for a couple of seconds.
Usually I just battery pull, and reinsert and playback the image. (Which works)
However, I've noticed that if I wait a few seconds and try the playback again,
(after the people say there's nothing on the screen, and the playback button
doesn't work) the playback button works fine.
It seems though it's like a delay.
As most times, taking an image then pressing the playback button right after
the camera plays back the image.
I hope you understand what I'm trying to describe.
Original comment by kay...@gmail.com
on 22 May 2011 at 2:47
Could you please confirm this is the sequence you are describing:
* Camera set to 8s review time.
* Take a photo.
* Wait for image to appear on display.
* Half-press shutter button (image disappears).
* Press PLAY immediately.
* Image is not displayed.
* Camera set to 8s review time.
* Take a photo.
* Wait for image to appear on display.
* Half-press shutter button (image disappears).
* Wait a few seconds and press PLAY.
* Image is displayed.
Many thanks.
Original comment by eduardo....@gmail.com
on 23 May 2011 at 5:23
Yes. Exactly like that.
The second sequence is what works most of the time, however, from time to time,
I've experienced the first sequence.
When I experience the first sequence, I just quickly do a battery pull to speed
things up.
But there has been a few times where I just waited the first sequence out, and
then pressed PLAY again, and it works.
Original comment by kay...@gmail.com
on 23 May 2011 at 10:53
I cannot reproduce this issue, have you found any pattern to trigger this
behavior constantly? Thanks.
Original comment by eduardo....@gmail.com
on 23 May 2011 at 10:14
Nope. All I can tell you is that after I take a picture, I would accidentally
hit a button (not necessarily the shutter button), and the image disappears.
It seems to be a periodic thing that happens.
Not so sure when or how. It just happens.
Original comment by kay...@gmail.com
on 24 May 2011 at 5:21
We cannot reproduce this, nobody else has complained about a similar behavior,
and we have not received any update for a long time. I am closing this issue,
please open a new one if the problem persists; thanks.
Original comment by eduardo....@gmail.com
on 20 Jun 2011 at 9:36
Problem hasn't been happening at all recently.
I guess it's fixed!
Original comment by kay...@gmail.com
on 28 Jun 2011 at 5:45
The only time it seems to happen to me now is when my battery or gripped
batteries are getting low - even when the camera battery power indicator shows
they are not yet fully exhausted. I get a lockup or freeze (whatever you want
to call it) which power-off by itself does not fix (requires pulling the
battery or batteries). I do not believe this has anything to do with 400plus.
Original comment by mike.guf...@gmail.com
on 28 Jun 2011 at 3:05
i got the same problem with empty batteries on the grip, but i think this is
because the batteries are not reporting the current level (via it's chip)
instead the camera tries to measure the charge via the voltage of the battery
(may be)
so i do not think this is a problem we can fix in the firmware... may be the
original firmware will hang too, but when the camera restarts it (the original
fw) will manage to shut down the mirror and turn off the camera. in our hack we
hold the starting of the firmware with about 1.5 sec. so it has no chance to
shutdown the camera... the power is too low after 1.5 secs.
may be after we find a solution for issue 92, we can do the battery level check
at the init routine and shutdown the camera if it's not good. this could fix
this problem.
Original comment by fired...@gmail.com
on 28 Jun 2011 at 3:25
I'm almost sure that one known bug of the 400D is random hangs when shooting
with flash and low power. I came across it a lot of time with my camera in the
last 5 years (I found chdk just some week ago)
Original comment by scri...@gmail.com
on 29 Jun 2011 at 5:04
hi...been reading the thread and have experienced exactly same problems of
intermittent locking up, including not being able to turn camera off without
pulling battery pack out to reset, this has only ocured when a bg-e3 canon
battery grip is attached, never when the normal battery is fitted, to test the
problem i swapped grip to my other 400d and it did exactly the same, first
camera has an 16gb card with 20130414-00 bin and second camera using same bin
with a 2gb cf card.... the problem does not occur on either camera when using
20120415-17 bin with grip or standard battery, an old version that i have found
really stable and has never given me any problems...hope this is of some help
Original comment by jason.fe...@gmail.com
on 22 Apr 2013 at 10:56
Bug has also been reported to the mailing list... reopening.
Original comment by eduardo....@gmail.com
on 30 Apr 2013 at 11:58
I have the same problem. Camera locks up (cannot reproduce it but I did nothing
special) and the only soltion is to take out the battery.
Original comment by friedl...@gmail.com
on 22 May 2013 at 6:32
Moving to a new issue, as this time it seems to be completely unrelated to the
old problem.
Original comment by eduardo....@gmail.com
on 30 May 2013 at 10:07
[deleted comment]
My cam also locked up during an event i was shooting where i had to take of the
batt several times and i could not shut it down, the green light was always on,
the display was dark and non of the keys were functional.
Original comment by ohad.isr...@gmail.com
on 8 Jun 2013 at 3:19
me too today i have i lot of locked cam crash with take of battery solution
Original comment by alberto....@gmail.com
on 15 Jun 2013 at 9:12
This issue is no longer active, please continue the discussion at issue #338.
Original comment by eduardo....@gmail.com
on 17 Jun 2013 at 4:43
Original issue reported on code.google.com by
kay...@gmail.com
on 10 Apr 2011 at 10:54