Modding Libra 2

undecimo · 10-21-2021, 08:40 PM

Just received a Libra 2 today and started poking around after updating to the October firmware.

KFMon and NickelMenu installed without complaint.

KOReader presented its bomb screen because it couldn't identify the device. I wasn't sure of the Libra 2's codename, so I modified frontend/device/kobo/device.lua to assign any unidentified devices to the Libra H2O bucket. KOReader then launched and rendered nicely, but 180 degrees from the desired orientation. (Touches were parsed correctly as the device rotated, but the screen orientation always redrew upside down.)

I haven't had a chance to hack further, but it appears that it won't take much work to get KOReader up and running.

davidfor · 10-21-2021, 09:52 PM

It's been mentioned elsewhere, but the codename for the Libra 2 is "io". And for the Sage it is "cadmus".

NiLuJe · 10-22-2021, 01:39 AM

I'll be working on initial support over the next week (might had been this week-end, but apparently my Sage is currently lost in the post-office ether

).

If you're willing to dig into it over shell (i.e., ssh/telnet), I have a test script that'll spit out all the gory details I need that I can send you?

NiLuJe · 10-22-2021, 01:43 AM

As in, unpack this in a temporary folder on your device, run the devcap_test.sh
script from said directory, and send me the output of /mnt/onboard/devcap_log.txt & /mnt/onboard/devcap_done.png once it's done

.

NiLuJe · 10-22-2021, 02:32 AM

Because I forgot to mention it earlier: for better accuracy, this should be run from within Nickel, after a cold boot

.

I also wouldn't mind a look at the full KFMon log (/usr/local/kfmon/kfmon.log).

undecimo · 10-22-2021, 09:22 AM

Logs attached. Thanks for the quick reply.

In the KFMon log, you'll see that I had a few .ini files set up - I copied the whole .adds folder from my old Aura. Tapping the icons in Nickel brought up an image preview instead of launching the associated app, but the generator :main :kfmon section in NickelMenu did populate correctly.

Plato was much more confused than KOReader and couldn't even render a list of books. I didn't try pbchess.

NiLuJe · 10-22-2021, 04:16 PM

Can you try this one, and do *not* touch the screen at the end (wait for the 10s timeout)?

(I kinda forgot about this bit ;p).

The goal is to avoid any broken Nickel refresh for the final screenshot

.

undecimo · 10-22-2021, 04:36 PM

Done. Did not touch the screen.

NiLuJe · 10-22-2021, 04:48 PM

Okay, that looks slightly less worse

.

Does stuff magically work if you copy the fbdepth binary from that final package to the koreader folder (.adds/koreader, FYI), overwriting the older one in there?

(I suspect we're not quite there yet, though. I'll double-check the kernel tomorrow, once I have a working brain again

).

NiLuJe · 10-22-2021, 04:59 PM

To that effect, try this one, which dumps a few more things in the log

.

(I also wouldn't mind an actual *picture* of the screen after the test, because the screengrab are getting confused by the rotation shenanigans ;p).

undecimo · 10-22-2021, 05:25 PM

Working perfectly with one additional edit to device.lua. touch_mirrored_x needs to be false.

So good to be back in KOReader, I really don't like Nickel...

7hir7een · 10-22-2021, 10:57 PM

Quote:

Originally Posted by NiLuJe

Does stuff magically work if you copy the fbdepth binary from that final package to the koreader folder (.adds/koreader, FYI), overwriting the older one in there?

It does with touch_mirrored_x = false,

Glad to have it up and running without weird mirror world shenanigans... I made the mistake of upgrading for the 32gb and then realized, oh no, can't live without koreader. Now I can start playing around with it!

NiLuJe · 10-23-2021, 07:35 AM

I'm not entirely convinced we're quite there yet...

Could you try enabling KFMon's boot spinner (touch /mnt/onboard/.adds/kfmon/config/BAR), rebooting, and then sending me the KFMon log again?

undecimo · 10-23-2021, 10:09 AM

Sure, here's the log.

NiLuJe · 10-23-2021, 11:40 AM

Ahah, inching closer to the truth...

Could I get a *picture* of the screen/device after running this version (again, no touching ;p).

10-21-2021, 08:40 PM	#1
undecimo Junior Member Posts: 8 Karma: 10 Join Date: Oct 2021 Device: Kobo Aura & Libra 2	Modding Libra 2 Just received a Libra 2 today and started poking around after updating to the October firmware. KFMon and NickelMenu installed without complaint. KOReader presented its bomb screen because it couldn't identify the device. I wasn't sure of the Libra 2's codename, so I modified frontend/device/kobo/device.lua to assign any unidentified devices to the Libra H2O bucket. KOReader then launched and rendered nicely, but 180 degrees from the desired orientation. (Touches were parsed correctly as the device rotated, but the screen orientation always redrew upside down.) I haven't had a chance to hack further, but it appears that it won't take much work to get KOReader up and running.

10-22-2021, 04:48 PM	#9
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Okay, that looks slightly less worse . Does stuff magically work if you copy the fbdepth binary from that final package to the koreader folder (.adds/koreader, FYI), overwriting the older one in there? (I suspect we're not quite there yet, though. I'll double-check the kernel tomorrow, once I have a working brain again ). Last edited by NiLuJe; 10-22-2021 at 04:53 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Libra Libra H2O vs Libra 2 (from reddit)	Deobulakenyo	Kobo Reader	19	10-20-2021 09:21 PM
Advice on modding for highlighting?	303	Kobo Reader	0	08-07-2020 01:25 PM
modding the EE?	summatusmentis	enTourage Archive	28	07-08-2010 03:53 PM
Modding My Kindle	DiggerG	Amazon Kindle	15	11-01-2009 12:01 PM
case modding	alexxxm	Sony Reader	6	01-01-2008 02:44 PM

10-21-2021, 09:52 PM	#2
davidfor Grand Sorcerer Posts: 24,907 Karma: 47303748 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	It's been mentioned elsewhere, but the codename for the Libra 2 is "io". And for the Sage it is "cadmus".

10-22-2021, 01:39 AM	#3
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	I'll be working on initial support over the next week (might had been this week-end, but apparently my Sage is currently lost in the post-office ether ). If you're willing to dig into it over shell (i.e., ssh/telnet), I have a test script that'll spit out all the gory details I need that I can send you?

10-22-2021, 02:32 AM	#5
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Because I forgot to mention it earlier: for better accuracy, this should be run from within Nickel, after a cold boot . I also wouldn't mind a look at the full KFMon log (/usr/local/kfmon/kfmon.log).

10-22-2021, 05:25 PM	#11
undecimo Junior Member Posts: 8 Karma: 10 Join Date: Oct 2021 Device: Kobo Aura & Libra 2	Working perfectly with one additional edit to device.lua. touch_mirrored_x needs to be false. So good to be back in KOReader, I really don't like Nickel...

10-23-2021, 07:35 AM	#13
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	I'm not entirely convinced we're quite there yet... Could you try enabling KFMon's boot spinner (touch /mnt/onboard/.adds/kfmon/config/BAR), rebooting, and then sending me the KFMon log again?

Advert

Advert