[N900] Camera app crashes/no longer functions... any ideas? - Page 2 - maemo.org

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 6 hrs, 2 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 18 hrs ago
more...

Page 2 of 4

< Prev

Next >

Thread Tools

	b666m	2010-01-25 , 07:19
	Posts: 1,090 \| Thanked: 476 times \| Joined on Jan 2010 @ Ingolstadt, Germany	#11

so... happened to me right now several times... wanted to take pictures for the poll because of the chrome ring around the cam reflects the light and is responsible for a hazy look of the right top of the picture...

here's how i make my cam app crash:
1. start the cam app
2. take one photo and wait till the preview is gone
3. take another photo and wait again till it's gone
4. click the "view images" button at the right bottom
5. click on one of the two pics you made
6. when it's zoomed in click in the middle of the pic to pop up the menu at the bottom
7. delete the pic with the trash-icon and "yes"
8. the other pic will show up
9. delete it the same way you did with the other picture
10. go back with the arrow top right
11. close the image view with the cross top right
12. click in the dashboard on the preview of the cam-app which is in standby
13. when it's fullscreen again try to take a photo
14. it crashes!? o.O
15. now you can open the cam app but you can't take pictures/videos anymore - it crashes immediately

edit: reboot helps to get it work again. plausible.
BUT: connecting usb, entering mass storage mode and disconnecting usb get it working too?!?!?!

Last edited by b666m; 2010-01-25 at 07:26.

Quote & Reply |

slender	2010-01-25 , 07:24
Posts: 2,829 \| Thanked: 1,459 times \| Joined on Dec 2009 @ Finland	#12

Some people have reported that they can only save to external sd memory card.

Quote & Reply |

	b666m	2010-01-25 , 07:25
	Posts: 1,090 \| Thanked: 476 times \| Joined on Jan 2010 @ Ingolstadt, Germany	#13

Originally Posted by slender

Some people have reported that they can only save to external sd memory card.

mhm... could you please try the steps above and tell me if it's happening on your phone too?
thx

Quote & Reply |

slender	2010-01-25 , 07:27
Posts: 2,829 \| Thanked: 1,459 times \| Joined on Dec 2009 @ Finland	#14

tried couple of times and can't make it crash.

Quote & Reply |

The Following User Says Thank You to slender For This Useful Post:
fr3sh

	b666m	2010-01-25 , 07:35
	Posts: 1,090 \| Thanked: 476 times \| Joined on Jan 2010 @ Ingolstadt, Germany	#15

Originally Posted by slender

tried couple of times and can't make it crash.

thx

mhm... after it crashed i tried to create a file with dmesg content in my MyDocs folder but xterm throws an error:

Code:

 ~sh: cannot create MyDocs/.documents/cam_dmesg: Read-only file system

so it seems the the drive is remounted with only read-rights while using the cam-app and deleting same pics?!

here's what dmesg had to say while doing the steps:
(the slide open/closed message is just to see where it started and where it ended ^^)

Code:

[ 7383.025024] slide (GPIO 71) is now closed
[ 7386.280700] musb_hdrc periph: enabled ep1in for bulk IN, maxpacket 512
[ 7386.280761] musb_hdrc periph: enabled ep1out for bulk OUT, maxpacket 512
[ 7386.280792] g_file_storage gadget: high speed config #1
[ 7406.837951] cam_shutter (GPIO 110) is now open
[ 7409.259796] cam_focus (GPIO 68) is now active
[ 7409.470703] cam_launch (GPIO 69) is now active
[ 7410.744110] cam_launch (GPIO 69) is now inactive
[ 7410.798797] cam_focus (GPIO 68) is now inactive
[ 7422.595733] cam_focus (GPIO 68) is now active
[ 7422.736267] cam_launch (GPIO 69) is now active
[ 7423.853546] cam_launch (GPIO 69) is now inactive
[ 7423.948822] cam_focus (GPIO 68) is now inactive
[ 7440.222717] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.222747]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.222778]     File system has been set read-only
[ 7440.223052] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223083]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223083] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223114]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223144] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223144]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223175] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223175]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223205] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223205]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223236] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223236]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223266] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223266]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223297] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223297]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223327] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223327]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223358] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223388]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223388] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223419]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223419] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223449]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223449] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223480]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223480] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223510]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223510] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223541]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223541] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223571]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223602] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223602]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223632] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223632]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223663] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223693]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.223724] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.223724]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425476] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425506]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425537] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425567]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425567] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425598]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425598] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425628]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425628] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425659]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425659] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425689]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425689] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425720]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7440.425720] FAT: Filesystem error (dev mmcblk0p1)
[ 7440.425750]     fat_get_cluster: invalid cluster chain (i_pos 280254492)
[ 7447.658355] cam_focus (GPIO 68) is now active
[ 7447.806701] cam_launch (GPIO 69) is now active
[ 7448.964050] cam_launch (GPIO 69) is now inactive
[ 7448.964111] cam_focus (GPIO 68) is now inactive
[ 7455.111328] slide (GPIO 71) is now open

i'll shutdown ubuntu and boot windows... then i'll do the filesystem-check as mentioned in this thread.... when it's done i'll try to make the steps again and look what will happen xD

Last edited by b666m; 2010-01-25 at 07:41.

Quote & Reply |

	b666m	2010-01-25 , 08:51
	Posts: 1,090 \| Thanked: 476 times \| Joined on Jan 2010 @ Ingolstadt, Germany	#16

mhm... windows check solved this problem... for now...
i wonder what will happen if i'll work some time with ubuntu...
last time it suddenly changed the mount-behaviour first on ubuntu then (some time later) on the phone...

Quote & Reply |

PuercoPop	2010-06-20 , 18:27
Posts: 2 \| Thanked: 0 times \| Joined on Jun 2010 @ Peru	#17

I have the same problem. Can't take any pictures. Already have run the filesystem check and have verified my MyDocs partitions is mounted as rw. I'm at a loss as to what to do.

Quote & Reply |

andyfrommk	2010-06-20 , 18:41
Posts: 116 \| Thanked: 75 times \| Joined on Nov 2009	#18

Doing this..

Code:

apt-get autoremove omap3camd --purge && apt-get install omap3camd

..helped me, but i still occasionally get it.

Quote & Reply |

PuercoPop	2010-06-20 , 21:06
Posts: 2 \| Thanked: 0 times \| Joined on Jun 2010 @ Peru	#19

Didn't fix it. I'm at a loss what to do. I got this phone last week! dmesg also doesn't give any message, just cam shutter open cam focus active/inactive messages.

Quote & Reply |

sygys	2010-11-11 , 07:47
Posts: 508 \| Thanked: 130 times \| Joined on Sep 2009	#20

i got the same thing. removing and installing omap3camd isnt working rebooting isnt also. starting fcam results in having grey screen where the camera view should be.

my thought is that the drivers are damaged...

My camera stopped working after i couldnt shut down my alarm this morning. it crashed and kept playing the anoying sound. then all of a sudden the alarm crashed, accelometer stopped working, camera stopped working and almost everything i launched stopped working.

After reboot all was fixed accept for the camera drivers. MyDocs and sdcard are not read only,