KOreader on Android

[karthikrr]

Originally Posted by Frenzie

Just to be sure, our build does work?

koreader-android-arm64-v2024.07.apk works without issues on both devices.

[pazos]

Originally Posted by karthikrr

koreader-android-arm64-v2024.07.apk works without issues on both devices.

Remember the android project is just a shell. Every single 3rd party dep needs to be built as well. Double check you got the prerrequisites right and start a clean build:

ANDROID_ARCH=arm64 ./kodev clean android
ANDROID_ARCH=arm64 ./kodev release android

Watch the output as it provides useful info in case something fails to build.

[pazos]

While debug builds are ok for debug are TOTALLY NOT OK to run them in a production environment. They're a lot of slower, a lot thicker and each transitition between the file manager and the reader will be, at least, 2x slower. Version updates will take about 4-5x time too.

Much better to build a release APK and sign it. The easiest option is to use https://github.com/patrickfav/uber-apk-signer

Something like

uber-apk-signer -a path/to/app.apk

should produce a path/to/app-aligned-debugsigned.apk that's installable.

[Rand Brittain]

I wound up getting an Onyx Tab Ultra C Pro after my Tab Ultra had an "accident", since the Tab Ultra isn't made any longer. Sadly, it looks like this one still has the "it takes several seconds to load a folder that has more than a hundred or so things in it" issue that I had with the Tab Ultra and the Nova Air 2 for a while.

I had hoped we were past this with a newer device, but I may just have to hope it gets fixed, since I think the only thing that helped with the other devices was "eventually a firmware update comes that makes the issue go away."

[Rand Brittain]

Originally Posted by Rand Brittain

I wound up getting an Onyx Tab Ultra C Pro after my Tab Ultra had an "accident", since the Tab Ultra isn't made any longer. Sadly, it looks like this one still has the "it takes several seconds to load a folder that has more than a hundred or so things in it" issue that I had with the Tab Ultra and the Nova Air 2 for a while.

I had hoped we were past this with a newer device, but I may just have to hope it gets fixed, since I think the only thing that helped with the other devices was "eventually a firmware update comes that makes the issue go away."

UPDATE: eventually a firmware update came, but it did not make the problem go away

Did anybody ever even figure out exactly what was causing this? It would be nice if I could at least send some kind of bug report to Onyx since they do seem to vaguely pay attending to posts in the Boox reddit.

[kandwo]

The Onyx Boox Go 10.3 was added to the list of new Android devices last month: https://github.com/koreader/koreader/issues/8482. But as of yesterday's nightly build the e-ink refresh still hasn't been implemented, even though the Onyx e-ink driver works with the device.

How long does it usually take before support for devices are added? Is there an easy way to make Koreader use the Onyx driver for e-ink to refresh the screen before it's added by the devs?

[Frenzie]

A few days to a few weeks probably. Tomorrow's nightly should support it.

[viceant]

Has been planned to implement zooming by gestures any time soon?

[Albertde]

--------- beginning of main
01-22 11:38:31.607 I/launcher.fdroid( 4950): Using CollectorTypeCMC GC.
01-22 11:38:31.616 E/launcher.fdroid( 4950): Not starting debugger since process cannot load the jdwp agent.
01-22 11:38:31.744 D/CompatibilityChangeReporter( 4950): Compat change id reported: 171979766; UID 10267; state: DISABLED
01-22 11:38:31.744 D/CompatibilityChangeReporter( 4950): Compat change id reported: 242716250; UID 10267; state: DISABLED
01-22 11:38:31.772 D/nativeloader( 4950): Configuring clns-6 for other apk /data/app/~~MhIibM_uTsQfR-RbOvtwLA==/org.koreader.launcher.fdroid-xotAkxyKA5ooilV4rgR7HQ==/base.apk. target_sdk_version=30, uses_libraries=, library_path=/data/app/~~MhIibM_uTsQfR-RbOvtwLA==/org.koreader.launcher.fdroid-xotAkxyKA5ooilV4rgR7HQ==/lib/arm64:/data/app/~~MhIibM_uTsQfR-RbOvtwLA==/org.koreader.launcher.fdroid-xotAkxyKA5ooilV4rgR7HQ==/base.apk!/lib/arm64-v8a, permitted_path=/data:/mnt/expand:/data/user/0/org.koreader.launcher.fdroid

[mkozlows]

Starting next year, Google apparently is going to need some developer verification for sideloaded apps: https://android-developers.googleblo...-security.html

KOReader is the main app I sideload -- is this something that's going to be a problem, or is this just a minor, easy hurdle for y'all to jump over and it'll be fine?

[Frenzie]

I can't say I want to give Google my address or my ID with a bunch of blacked out info for the intended purpose of not interacting with Google in any way whatsoever. There's no upside to this proposal.

[tetra]

Hi,
I see the latest Koreader version is available on F-Droid.
However, it seems it is made for very old android versions, as my Pixel phone complains about security risk when trying to install.
Is it possible to distribute a version made for recent Android versions?
Thanks

[Frenzie]

Compatible with, not made for. There are also features that require at least Android 11. I don't think there's anything that requires a higher version otoh.

Are you sure it's not merely complaining because it's not from the Play store? You just have to let it scan it.

[tetra]

Originally Posted by Frenzie

Compatible with, not made for. There are also features that require at least Android 11. I don't think there's anything that requires a higher version otoh.

Are you sure it's not merely complaining because it's not from the Play store? You just have to let it scan it.

No problem with other applications from F-Droid.
After downloading KOReader from F-Droid, when starting the installation, it is complaining that the application was made for an old android version that include no confidentiality security.

[Frenzie]

Just ignore it. That's meaningless planned obsolescence gibberish from Google. It has nothing to do with privacy.