At Wed, 23 Sep 2009 11:50:41 +0200,
Martin Grimme wrote:
Hi,
I once had the same problem on my N810. Flipclock was messing with the
display timeout settings. I think I fixed it by manually correcting
the display timeout value in GConf. Look around for it using
gconf-editor (installable
Thanks, Eric, it seems to be working!
Sergey
On Fri, Sep 25, 2009 at 10:53 AM, Eric S Fraga ucec...@ucl.ac.uk wrote:
At Wed, 23 Sep 2009 11:50:41 +0200,
Martin Grimme wrote:
Hi,
I once had the same problem on my N810. Flipclock was messing with the
display timeout settings. I think I
On Wed, Sep 23, 2009 at 11:56:28AM +0200, Martin Grimme wrote:
No sorry, I don't remember what it was exactly but from looking at
that name of the key and the value it had it was pretty obvious that
this was the culprit. Maybe somebody else can provide more information
about where the screen
Hi folks
At some point, my n810 got strange habit - it never turns the screen
off, just dims it a bit. Needless to say, the battery dies fast. Is
there any way to check what's wrong?
In the control panel, brightness period is set to 30 seconds. And
switch off display - 30 seconds as well.
Hi,
I once had the same problem on my N810. Flipclock was messing with the
display timeout settings. I think I fixed it by manually correcting
the display timeout value in GConf. Look around for it using
gconf-editor (installable via application manager).
Cheers,
Martin
2009/9/23, Sergey
Thank, Martin
Most probably it is flipclock. By any chance, do you remember what
were those gconf entries?
Sergey
On Wed, Sep 23, 2009 at 10:50 AM, Martin Grimme martin.gri...@gmail.com wrote:
Hi,
I once had the same problem on my N810. Flipclock was messing with the
display timeout
No sorry, I don't remember what it was exactly but from looking at
that name of the key and the value it had it was pretty obvious that
this was the culprit. Maybe somebody else can provide more information
about where the screen blanking timeout is stored in GConf?
Cheers,
Martin
2009/9/23,
