02-15-2015, 02:40 PM | #16 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
These are the values for Aura that I took as default for H2O too, because of a misunderstanding. You have to take other values.
|
02-15-2015, 02:50 PM | #17 | |
Member
Posts: 22
Karma: 53884
Join Date: Dec 2012
Location: Lyon
Device: Kobo H2O
|
Quote:
Code:
ksmGeometryValuesN=1080x1430+0+5 ksmGeometryValuesS=1080x1430+0+5 ksmGeometryValuesE=1430x1080+0+5 ksmGeometryValuesW=1430x1080+0+5 Last edited by Reventlov; 02-15-2015 at 02:56 PM. Reason: Modified the size to center the |
|
02-15-2015, 03:20 PM | #18 | |
Guru
Posts: 897
Karma: 149877
Join Date: Jul 2013
Location: Netherlands
Device: Cracked HiSenseA5ProCC, Cracked OnyxNotePro, Note5, Kobo Glo, Aura
|
Quote:
Code:
ksmGeometryValuesN=1070x1430+5+5 ksmGeometryValuesS=1070x1430+5+5 ksmGeometryValuesE=1430x1070+5+5 ksmGeometryValuesW=1430x1070+5+5 EDIT: Nope. The menu still gets drawn one line down when selecting koreader from the menu. Last edited by Markismus; 02-15-2015 at 03:23 PM. |
|
02-15-2015, 03:27 PM | #19 | |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Quote:
Edit: From the discussion below I guess the following values should fit: Code:
ksmGeometryValuesN=1080x1429+0+11 ksmGeometryValuesS=1080x1429+0+0 ksmGeometryValuesE=1429x1080+11+0 ksmGeometryValuesW=1429x1080+0+0 For H2O users: Please add to the file .adds\kbmenu\usersettings.txt the above 4 lines. Attention: You have to use a unix-style editor. Last edited by tshering; 02-17-2015 at 04:49 AM. |
|
02-15-2015, 04:13 PM | #21 |
BLAM!
Posts: 13,482
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@tshering: Yup, top 11 pixels are behind the bezel. (ie. 1080x1429+0+11 [I *think*?]). (KOReader's viewport is off by 1 pixel, I haven't gotten around to fixing it yet ).
(And by 'top', I mean in portrait mode, and not upside down. i.e. nickel's default orientation). Last edited by NiLuJe; 02-15-2015 at 04:17 PM. |
02-15-2015, 04:23 PM | #22 | |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Quote:
|
|
02-15-2015, 04:31 PM | #23 |
BLAM!
Posts: 13,482
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@tshering: That seems unlikely, given the fact that nickel very specifically blacks out those 11 pixels, and goes to the trouble of special-handling already-processed sleep images to make very sure said 11 top pixels are blacked out, rescaling everything in the process to make sure there's no actual useful content behind the bezel (which, while neat in theory, is annoying in practice, since it potentially rescales an already-dithered image, which is a bad, bad thing. [Yup, I did some extensive testing on the subject, to have pretty sleep covers ;p]).
That, plus the fact that the hidden screenshot feature also uses 11 pixels (although in a broken way, rescaling to 1080x(1440-11) instead of cropping the top 11 pixels off) . Last edited by NiLuJe; 02-15-2015 at 04:35 PM. |
02-15-2015, 04:36 PM | #24 | |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Quote:
|
|
02-15-2015, 04:41 PM | #25 |
BLAM!
Posts: 13,482
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@tshering: I'd be very interested to know. According to KOReader's code, there's a similar shenanigan going on with the *bottom* 12 pixels, but I'd need a proper fbgrab snapshot from an Aura to confirm that, and I don't have an Aura . (That, and I think the Aura is marketed as having a weird screen size off by 10 y px on the Kobo website, so, again, I'm not convinced the value is accurate).
(cf. my previous musings on the subject in the CR thread). (On a slightly related note: I recently updated the standalone FBGrab builds to handle said cropping automatically on the H2O ). Last edited by NiLuJe; 02-16-2015 at 02:06 PM. |
02-15-2015, 05:21 PM | #26 | |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Quote:
|
|
02-15-2015, 05:25 PM | #27 |
Guru
Posts: 897
Karma: 149877
Join Date: Jul 2013
Location: Netherlands
Device: Cracked HiSenseA5ProCC, Cracked OnyxNotePro, Note5, Kobo Glo, Aura
|
@NiLuje Your settings seem to have eliminated the "line shuffle" on my H2O. Thanks!
|
02-16-2015, 03:40 PM | #28 |
Enthusiast
Posts: 47
Karma: 384
Join Date: Nov 2013
Device: Kobo Mini (f/w 3.4.1) + Aura (f/w 3.12.1)
|
Hello tshering and thanks for KSM.
I just installed night mode but selected "install partial update" instead of "install update". Is it possible that harms the device in any way?? PS: it's on Aura f/w 3.12.1 |
02-16-2015, 03:49 PM | #29 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Everything is okay! In this case both update options will lead to the same result.
|
02-16-2015, 04:22 PM | #30 | |
Enthusiast
Posts: 47
Karma: 384
Join Date: Nov 2013
Device: Kobo Mini (f/w 3.4.1) + Aura (f/w 3.12.1)
|
Quote:
Also, is the method described here outdated or still the way to go in order to make an alternative setting for koreader? And where do one set the opening path for koreader? Last edited by gong; 02-16-2015 at 04:32 PM. |
|
Tags |
koreader/nickel, ksm 07 |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kobo-Adding alternative readers using Kobo Start Menu | Ken Maltby | KOReader | 75 | 01-10-2020 01:35 PM |
Kobo Start Menu | tshering | Kobo Developer's Corner | 918 | 10-12-2017 02:32 PM |
QT Browser for Kobo Start Menu? | gloriousglib | Kobo Developer's Corner | 1 | 05-24-2014 03:59 AM |
kobo menu and message | tshering | Kobo Developer's Corner | 26 | 01-15-2014 09:18 AM |
Calibre start menu icon | Cy1clown | Calibre | 1 | 02-06-2010 02:10 PM |