K5 5.1.0 firmware & orientation

[silver18]

Good evening!

I hope this interests someone...

I just updated my Kindle Touch to 5.1.0 and I found out that orientation now doesn't works with browser and WAF applications.

Playing around, I managed to make the GUI launcher orientation script to work even in the home screen. I changed the value of this entry in appreg.db to URL (instead of U):



Anyway, creating a similar entry for the browser or any of the WAF doesn't work.

Any clue?

[silver18]

I investigated a little more....
It seems like something is preventing to send the orientationLock event...

While displaying the browser, or a WAF, I can't get this in the log file:

I lipc:evts:name=orientationChange, origin=com.lab126.winmgr, fparam=R:Event sent

or this, for vertical orientation:

I lipc:evts:name=orientationChange, origin=com.lab126.winmgr, fparam=U:Event sent

while I can see those logs while reading a book...

[silver18]

I found something in browser JS...

// set orientation
// eventually can get this information from webkit's orientation
// implementation, but it is not currently enabled

That's why the com.lab126.winmgr command doesn't work!

Anyway it seems that everything is ready to receive a rotation support!
Maybe in the next firmware release....

[ixtab]

Shamelessly plugging in here:

http://www.mobileread.com/forums/sho...6&postcount=49 contains a method to support all orientations (including upside-down) in the Reader, the Home screen, and even Kindlets. (Not WAF applications though). No changes required (except for installing the jbpatch thing )!

[silver18]

Thanks a lot for all your work!

I'll try it this evening!

I'm really thinking of converting my ImageGallery (WAF) to a kindlet as WAF have so many limitations...

[silver18]

Finally rotation is back even for WAFs!!!

You have to add this to your config.xml file:

<kindle:messaging>
       	<kindle:app name="com.lab126.pillow" value="yes"/>
</kindle:messaging>

and then call this function in your HTML:

kindle.dev.setOrientation(state);

Variable state can be "portrait", "auto" or "landscape"!!

Have fun!

[diba]

@silver: which config.xml file please. I am lost between "extensions" of GUI and ixtabs version. And how to activate pls, could you add a sentence to make it clear?

[silver18]

Originally Posted by diba

@silver: which config.xml file please. I am lost between "extensions" of GUI and ixtabs version. And how to activate pls, could you add a sentence to make it clear?

I'm talking about WAFs here.
You need to edit the config.xml file of your WAF adding these lines:

<kindle:messaging>
       	<kindle:app name="com.lab126.pillow" value="yes"/>
</kindle:messaging>

and then, to change orientation, use this in JavaScript:

kindle.dev.setOrientation(state);

where state can be:
- auto
- portrait
- landscape

Here are examples:

config.xml from ImageGallery: click

how to change orientation from ImageGallery: click

You're welcome!

[silver18]

I'm here again to share another finding...

You can use the old:

kindle.dev.setOrientation(state);

where

state

can be (and here's the finding):

portraitUp
portraitDown
landscapeLeft
landscapeRight

PortraitUp and portraitDown work really well!!
LandscapeRight and landscapeLeft work, but I had some UI problems I didn't have with

state="landscape"

You can see the problem in screenshots

All in all, we have 4 direction rotation now...

[silver18]

My Kindle just update itself to 5.1.2, and it seems that the UI problems are solved!
I don't know if this is related to the update (I didn't managed to test the 4-way-rotation deeply).

[geekmaster]

Originally Posted by silver18

My Kindle just update itself to 5.1.2, and it seems that the UI problems are solved!
I don't know if this is related to the update (I didn't managed to test the 4-way-rotation deeply).

You can always "debrick" to an earlier firmware version, so you can do more testing.

[silver18]

Originally Posted by geekmaster

You can always "debrick" to an earlier firmware version, so you can do more testing.

No way!!! This is the first update that didn't mess anything (or at least I didn't find anything!).

[knc1]

oops.