Testing Android Build

[Markismus]

I installed the first nightly release of the first android build of koreader on my HTC Desire HD, android version 2.3.5. After starting koreader, I get a black screen without any change for more than 3 min.

Were can I look on my mobile for additional info about what's going on? A file search for reader.lua comes up empty. The device is not rooted.

[pazos]

It boots on my alcatel 4.0.4 phone, but crash when I scroll (up/down/left/right) the page in both reader and filemanager. Translations seems to be non-working right now.

One question, What is the Min SDK version for this app? Does it runs on android 2.1 (API 7)?

I would like to test this port in an old sony PRS-T1..

[thotypous]

It's API 9 (Android 2.3) according to AndroidManifest.xml

[chrox]

It seems that current build of Koreader for Android does not run on Android 2.3, it does work on Android 4.2 ( CM10.1 ) on my developing device.

And it turns out that the ANativeWindow_getWidth and ANativeWindow_getHeight here fail to get the right screen size. Actually on Android 2.3 they both return 1 and let fb make a framebuffer of 1 pixel size. And carefully enough when running Koreader on Android 2.3, you can notice a bright pixel at the upper-left corner of the screen, that would be the Koreader GUI.

I tested also to specify the screen size manually when opening the fb and it turned out fine without problem.

So what we should do to fix this issue is finding a way to get screen size on Android 2.3.

[hwhw]

I have a simple JNI interface in the pipeline that I will probably commit within 1-2 days. I think we could use it to get the Screen dimensions from the Java side via JNI. Or maybe we ask the system in a bad moment when the Window isn't fully initialized yet?

[hwhw]

As for the minimum required Android version: Yes, that is Android 2.3 (API 9), since only from that on there's the "NativeActivity" API. It gets a bit more complicated if we wouldn't use that - we would have to go and write a Java Activity and the input/output stuff gets a bit more messy. I'm not sure whether it would be worth it.

[Markismus]

Correct. Don't know how I could have missed that pixel! :)

[chrox]

Blank screen issue on Android 2.3 is fixed. So close this now.

[Markismus]

Yes! Build 154 works great on my android 2.35.