![]() |
2008-10-11
, 23:44
|
Posts: 3 |
Thanked: 0 times |
Joined on Sep 2008
|
#52
|
![]() |
2008-10-14
, 01:40
|
Posts: 164 |
Thanked: 18 times |
Joined on Dec 2007
|
#53
|
![]() |
2008-12-18
, 19:19
|
Posts: 164 |
Thanked: 18 times |
Joined on Dec 2007
|
#54
|
The Following User Says Thank You to migs For This Useful Post: | ||
![]() |
2008-12-18
, 21:06
|
Posts: 47 |
Thanked: 3 times |
Joined on May 2007
@ Herndon, VA, USA
|
#55
|
![]() |
2009-02-07
, 21:25
|
|
Posts: 3,220 |
Thanked: 326 times |
Joined on Oct 2005
@ "Almost there!" (Monte Christo, Count of)
|
#56
|
For all those who have this annoying camera bug
1. Shutdown N800 with camera pushed in
2. Take out battery for 10 mins (some report less time is ok)
3. ****Pull out the Camera**** while unit is off and battery is out
4. Replace battery (make sure camera still out)
5. Start N800
6. Start New Internet Call application while camera still out
(it should work) then close app and push camera in.
7. Now pull camera out should autolaunch internet call app and autoflip
This process was the only thing that worked for me and I had tried everything else.
![]() |
2009-02-08
, 14:38
|
Posts: 77 |
Thanked: 10 times |
Joined on Nov 2007
|
#57
|
![]() |
2009-02-08
, 15:00
|
|
Posts: 3,220 |
Thanked: 326 times |
Joined on Oct 2005
@ "Almost there!" (Monte Christo, Count of)
|
#58
|
![]() |
2009-02-09
, 15:07
|
Posts: 631 |
Thanked: 837 times |
Joined on May 2007
@ Milton, Ontario, Canada
|
#59
|
![]() |
2009-02-09
, 16:05
|
|
Posts: 3,220 |
Thanked: 326 times |
Joined on Oct 2005
@ "Almost there!" (Monte Christo, Count of)
|
#60
|
All Nokia Politics aside, in my experience with the N800 camera issue I've found that it seems to be related in powering up the device from the "charging" state. If you have the tablet connected to the charger but "turned off" and you turn the tablet on, the camera doesn't work properly; if you disconnect the charger and make sure the tablet is completely "off off", then turn it on from there it seems to work just fine everytime... in my experience at least. Can anyone else verify that behaviour? If so my bet would be that there's something in the Diablo low-power initfs that's causing the issue... I mean, no closer to a permanent resolution, but at least if we can narrow down the problem to what exactly in software is actually causing the problem it'd be a start...
Just for the record, I had no such issues prior to Diablo so I am sorry that I can't help anyone.
Re the removing and replacing battery fix, I do that every day (my batteries are charged externally) so that had no effect on my experience.