View Single Post
Old 01-20-2018, 01:00 PM   #19
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by nook_nerd View Post
Tshering,

Ok, did as instructed.

Read Rotate Value was:
-
### executed:cat /sys/class/graphics/fb0/rotate
0
-


Tried 4 or 5 times, and came back every time in correct orientation, OK was in upper left corner each time.

Hope it is useful..

Thanks,
John Feole
Thank you. That looks promising! Doesn't it?
After some seconds I realised that I was over enthusiastic. It seems we can prevent the rotation, when we know that the rotation has been destabilised. However, when we take the same measures without the rotation already being destabilised, we will produce the destabilisation ourselves. That means before each call of a KSM application we would have to know whether the rotation is stable or unstable. The only solution that comes to my mind now is to record whether nickel has been run in this session, and if yes presume that the rotation is unstable.
Any ideas?

Last edited by tshering; 01-20-2018 at 01:36 PM.
tshering is offline   Reply With Quote