Quote:
Originally Posted by geek1011
That's interesting. Does it happen with devmode on? Also, does the syslog or dmesg say anything interesting?
|
I enabled devmode in my Aura HD and the issue is still happening, I enabled dark screen and suddenly go back to normal screen. Here's an extract from the syslog (I do not know if there is anything useful):
Quote:
Jan 24 11:41:35 nickel: (NickelMenu) showing menu (src/nickelmenu.cc:393)
Jan 24 11:41:36 nickel: ( 4221.614 @ 0x154adf0 / performance.debug) 10 ms to composite
Jan 24 11:41:36 nickel: ( 4221.614 @ 0x154adf0 / eink.debug) QRegion KoboScreenNXP::blit(const QRegion&) QRect(704,813 376x523) wf=257 upd=0 flags=1 can_collide=1
Jan 24 11:41:36 nickel: ( 4221.615 @ 0x154adf0 / eink.debug) QRegion KoboScreenNXP::blit(const QRegion&) QRect(864,1336 216x104) wf=257 upd=0 flags=1 can_collide=1
Jan 24 11:41:37 nickel: ( 4223.070 @ 0x1863248 / input.debug) 0 : QPoint(973,178) => QPoint(902,973) QFlags(0x1) 100
Jan 24 11:41:37 nickel: ( 4223.097 @ 0x1863248 / input.debug) 0 : QPoint(972,178) => QPoint(902,972) QFlags(0x4) 101
Jan 24 11:41:37 nickel: ( 4223.127 @ 0x1863248 / input.debug) 0 : QPoint(971,177) => QPoint(903,971) QFlags(0x4) 100
Jan 24 11:41:37 nickel: ( 4223.130 @ 0x1863248 / input.debug) 0 : QPoint(971,177) => QPoint(903,971) QFlags(0x8) 0
Jan 24 11:41:37 nickel: ( 4223.142 @ 0x154adf0 / performance.debug) 9 ms to composite
Jan 24 11:41:37 nickel: ( 4223.142 @ 0x154adf0 / eink.debug) QRegion KoboScreenNXP::blit(const QRegion&) QRect(704,813 376x523) wf=257 upd=0 flags=1 can_collide=1
Jan 24 11:41:37 nickel: (NickelMenu) item 'Dump Syslog' pressed... (src/nickelmenu.cc:387)
Jan 24 11:41:37 nickel: (NickelMenu) action 0x325e50fd with argument logread > /mnt/onboard/.adds/syslog.log : (src/nickelmenu.cc:658)
|
Nonetheless if I enable "Invert Screen" from "Drawing" section in the developers options, the dark mode remains.
Thanks for your help!