You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 22, 2020. It is now read-only.
With Kindle DX gravity sensor on, when kpv is launched then go to sleep, if I turn on the DX with it in landscape orientation, because there is a small time window of kindle original software in the wake up procedure, the DX will respond to the landscape orientation, i.e. rotate screen, then go back to kpv mode.
The kpv mode will still be in portrait without problem. However, once I quit kpv, the screen became messed up. I have to use shift-P-R to restart amazon framework, the sequence still works.
This is not really problem of kpv, but the situation is not too difficult to meet: keep the sensor on, wake up dx in landscape mode.
Is there any command in launchpad to force dx to portrait mode? I usually just turn off the gravity sensor, but I can't always remember to turn it off once I restarted the DX.
The text was updated successfully, but these errors were encountered:
With Kindle DX gravity sensor on, when kpv is launched then go to sleep, if I turn on the DX with it in landscape orientation, because there is a small time window of kindle original software in the wake up procedure, the DX will respond to the landscape orientation, i.e. rotate screen, then go back to kpv mode.
The kpv mode will still be in portrait without problem. However, once I quit kpv, the screen became messed up. I have to use shift-P-R to restart amazon framework, the sequence still works.
This is not really problem of kpv, but the situation is not too difficult to meet: keep the sensor on, wake up dx in landscape mode.
Is there any command in launchpad to force dx to portrait mode? I usually just turn off the gravity sensor, but I can't always remember to turn it off once I restarted the DX.
The text was updated successfully, but these errors were encountered: