Physical buttons on Kindle Voyage don't work?

vurt · 01-29-2023, 05:25 PM

Hi everyone. Can I check or confirm the physical page turn buttons on the Kindle Voyage don't trigger page turns in KOReader?

Or maybe I missed a setting somewhere?

I'm new to KOReader on Kindle Voyage. I'd given up on jailbreaking my KV until last night when I discovered there's a jailbreak

NiLuJe · 01-29-2023, 10:00 PM

There should be workarounds in place for that in current KUAL versions, but I can't vouch for their efficacy as I don't have access to a Voyage.

That they *can* be disabled in userland apps *is* a known "feature" though.

vurt · 01-29-2023, 10:09 PM

Quote:

Originally Posted by NiLuJe

There should be workarounds in place for that in current KUAL versions, but I can't vouch for their efficacy as I don't have access to a Voyage.

That they *can* be disabled in userland apps *is* a known "feature" though.

I searched mobileread first but your response got me googling and I found a few Github issues that described the problem.

One of them seems to have a fix and it was closed, but I'm not sure what that means (not a dev unfortunately, just know how to dig around).

I think you commented in it too.

Does the issue/fix being closed mean it's been fixed in newer KOReader? Trying to understand if this is still a bug with KV or it's been fixed but not working for me.

Thank you!!

vurt · 01-29-2023, 10:17 PM

I've been starting KOReader with (no framework) which kills KUAL and the Kindle front end I think? That kills the physical buttons.

When I start KOReader normally (first option in KUAL menu "Start KOReader), the buttons work.

Does starting KOReader with no framework help make KOReader run faster?

NiLuJe · 01-30-2023, 02:26 AM

Oh, forgot this was a thing.

Yeah, no framework will most likely kill the buttons until someone with the device figures out how exactly they're neutered.

The main purpose of the no framework mode is to lower memory pressure, which is otherwise fairly high on Kindle because said framework (i.e., the stock UI & backend) eats a humongous amount of RAM (hai, java). Should be mostly irrelevant unless you're reading PDFs, though.

vurt · 01-30-2023, 09:24 AM

Quote:

Originally Posted by NiLuJe

The main purpose of the no framework mode is to lower memory pressure, which is otherwise fairly high on Kindle because said framework (i.e., the stock UI & backend) eats a humongous amount of RAM (hai, java). Should be mostly irrelevant unless you're reading PDFs, though.

Good to know, thank you very much!

kpopconnoisseur · 03-31-2023, 12:24 PM

hello. i used to have the exact same problem as you, vurt, and on reading this thread decided to investigate and then make a mobileread account to share my findings:

i was able to reactivate the pageturn buttons on the voyage by setting the fsrkeypadEnable and fsrkeypadPrevEnable properties on com.lab126.deviced (back) to 1 after launching koreader with the no framework option.

Code:

# lipc-set-prop com.lab126.deviced fsrkeypadPrevEnable 1

Code:

# lipc-set-prop com.lab126.deviced fsrkeypadEnable 1

NiLuJe · 03-31-2023, 01:33 PM

@kpopconnoisseur: That's cool, feel free to send a quick PR to expand https://github.com/koreader/koreader/pull/9419 so that it does so automatically on the Voyage

.

01-29-2023, 05:25 PM	#1
vurt Enthusiast Posts: 29 Karma: 28 Join Date: Apr 2016 Device: KV	Physical buttons on Kindle Voyage don't work? Hi everyone. Can I check or confirm the physical page turn buttons on the Kindle Voyage don't trigger page turns in KOReader? Or maybe I missed a setting somewhere? I'm new to KOReader on Kindle Voyage. I'd given up on jailbreaking my KV until last night when I discovered there's a jailbreak

03-31-2023, 12:24 PM	#7
kpopconnoisseur Junior Member Posts: 1 Karma: 10 Join Date: Mar 2023 Device: Kindle Voyage	hello. i used to have the exact same problem as you, vurt, and on reading this thread decided to investigate and then make a mobileread account to share my findings: i was able to reactivate the pageturn buttons on the voyage by setting the fsrkeypadEnable and fsrkeypadPrevEnable properties on com.lab126.deviced (back) to 1 after launching koreader with the no framework option. Code: # lipc-set-prop com.lab126.deviced fsrkeypadPrevEnable 1 Code: # lipc-set-prop com.lab126.deviced fsrkeypadEnable 1

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Replacing kindle 3: need to have TTS, physical buttons	Neikius	Which one should I buy?	9	09-13-2016 06:52 PM
Touch Do the page next physical buttons work on browser?	ST889	Barnes & Noble NOOK	2	05-06-2013 08:36 AM
When I making a new post, why the buttons don't work?	xiongmao86	Feedback	2	02-25-2013 04:31 AM
Kindle and Physical buttons	ewandeep	Sony Reader Dev Corner	4	07-09-2012 10:12 AM
PRS-505 Some buttons don't work	karo02	Sony Reader	6	11-18-2011 10:10 AM

01-29-2023, 10:00 PM	#2
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	There should be workarounds in place for that in current KUAL versions, but I can't vouch for their efficacy as I don't have access to a Voyage. That they can be disabled in userland apps is a known "feature" though.

01-29-2023, 10:17 PM	#4
vurt Enthusiast Posts: 29 Karma: 28 Join Date: Apr 2016 Device: KV	I've been starting KOReader with (no framework) which kills KUAL and the Kindle front end I think? That kills the physical buttons. When I start KOReader normally (first option in KUAL menu "Start KOReader), the buttons work. Does starting KOReader with no framework help make KOReader run faster?

01-30-2023, 02:26 AM	#5
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Oh, forgot this was a thing. Yeah, no framework will most likely kill the buttons until someone with the device figures out how exactly they're neutered. The main purpose of the no framework mode is to lower memory pressure, which is otherwise fairly high on Kindle because said framework (i.e., the stock UI & backend) eats a humongous amount of RAM (hai, java). Should be mostly irrelevant unless you're reading PDFs, though.

03-31-2023, 01:33 PM	#8
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@kpopconnoisseur: That's cool, feel free to send a quick PR to expand https://github.com/koreader/koreader/pull/9419 so that it does so automatically on the Voyage .

Advert

Advert