MobileRead Forums - View Single Post

NiLuJe · 08-05-2016, 10:33 AM

@Minuscule: Your device isn't misindentified (it rightly should be using PW2+ binaries [granted, that error message could be slightly clearer, but then to even get to see it you have to have a spectacularly broken setup in the first place ;p]), you just have an incomplete MRPI setup (said binaries are missing).

As @knc1 said, reinstall it from the current snapshots. Make sure nothing in your workflow gets any bright ideas and tries to automatically unpack tarballs along the way...

@zxczxc: Wasn't aware, no. I don't *think* there's anything I can do about it, the setup is done at a point where the orientation used might not match what might be the one used when the device goes asleep. (i.e., "last" mode doesn't actually 'do' anything when you put your device to sleep, everything is done at framework start, which, in that specific context always starts with a set orientation anyway, I believe).

And in that context, even if it were reacting on the 'go to sleep' event, that's too late to do anything useful anyway.

Best I could do is probably add another setting to the KUAL extension to manually ask to use a landscape overlay?

08-05-2016, 10:33 AM	#2171
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Minuscule: Your device isn't misindentified (it rightly should be using PW2+ binaries [granted, that error message could be slightly clearer, but then to even get to see it you have to have a spectacularly broken setup in the first place ;p]), you just have an incomplete MRPI setup (said binaries are missing). As @knc1 said, reinstall it from the current snapshots. Make sure nothing in your workflow gets any bright ideas and tries to automatically unpack tarballs along the way... @zxczxc: Wasn't aware, no. I don't think there's anything I can do about it, the setup is done at a point where the orientation used might not match what might be the one used when the device goes asleep. (i.e., "last" mode doesn't actually 'do' anything when you put your device to sleep, everything is done at framework start, which, in that specific context always starts with a set orientation anyway, I believe). And in that context, even if it were reacting on the 'go to sleep' event, that's too late to do anything useful anyway. Best I could do is probably add another setting to the KUAL extension to manually ask to use a landscape overlay? Last edited by NiLuJe; 08-05-2016 at 10:37 AM.