Pages are completely blank in case of SDK Launcher - Android

[kapilkmr8]

Hi all geeks,
I successfully built project on Windows (for Android). After following all instructions there on github, i run application(SDK Launcher-Android) on my Samsung galaxy tab 2 10.1 (gt-p5113 )(Android 4.2.2) and Samsung galaxy tab 750 (gt-p7500)(Android 4.0.4).
On both devices, it is showing complete blank pages without any error for every epub3.
I also made changes to 3 files as stated on github pull request.
But even after that it is showing complete blank pages.

Kindly guide and help as soon as possible as it is urgent for me.
@rkwright

[danielweck]

I have just successfully tested SDK-Launcher-Android. A clean build from the develop branches of all 3 repositories involved. I am able to read reflow and fixed layout EPUBs.

I'm on Mac OSX (Yosemite), latest version of Eclipse (standard/SDK), latest update from Android SDK manager, latest NDK r10c (make sure to configure path in Eclipse preferences), targeting API 19 / Android 4.4.x (default is API 11), and using NDK toolchain version 4.9 (default is 4.8).

I'll push my config files to the repository in a minute.

[kapilkmr8]

@danielweck
i will test it one more time by cloning again from repository. I am using Windows 7, latest update of SDK Manager, latest NDK r10c (path configured), targeting API 19.

1.Is there any issue with using default NDK toolchain?
2.After building through ./ndk-compile.sh build command, am i supposed to build Epub3-library again through eclipse?(eclipse stating this error- CreateProcess error=193, %1 is not a valid Win32 application(for ndk-compile.sh) )
3.Are you using EPUB test files under (Launcher-Android\readium-sdk\TestData) folder? I used these epubs, it is showing blank pages for them.

Thanks.

[danielweck]

Nowadays I do not build the epub3 native lib from the command line anymore, although I do check that it "cleans" properly:

cd SDKLauncher-Android/
cd readium-sdk/Platform/Android/
./ndk-compile.sh clean /Applications/android-ndk-r10c/

Then, I use Eclipse to build the lib, wait until it's done, then debug the launcher app.

I had libxml compiler issues with toolchain 4.8, so I switched to 4.9 and it worked.

My tablet is old and slow (Samsung Galaxy Tab 7" GT-P1000), but the Chromium WebView renders content correctly (CyanogenMod ROM 4.4.4 KitKat).

I pushed my config to the develop branch, see if it helps?

/Dan

[danielweck]

PS: yes, I use regular tests EPUBs under the normal SDCARD directory, in addition to some private (commercial) ebooks. Fixed layout and reflow. All works fine, including landscape / portrait rotation (viewport orientation to test-refresh the WebView).

[danielweck]

The config changes I pushed to develop (to be honest, not sure what Eclipse updated in .cproject ?):

256211b

readium/readium-sdk@a0eba52

[kapilkmr8]

Thanks @danielweck , Finally i am able to render epub3 books on my device's screen. I copy and pasted readium-shared-js folder under assests folder along with all its content, where code was trying to find it.

Just wanting to check another thing with you, in eclipse while launching sample launcher application, it crashes just after splash screen (showing this error in logcat - java.lang.java.lang.exceptionininitializererror due to line "System.loadLibrary(epub3);"). Well, it got solved on my system by some way(i cudn't figure it out yet). Please tell me if there is any information about it. Thanks Again.

[danielweck]

@kapilkmr8 Glad to hear you got it to work! I assume you are not using Readium's Eclipse project? (which automatically includes the readium-shared-js folder) ... or perhaps you did not initialise/update the readium-shared-js git submodule?

The epub3 library loader should work fine if you make sure to include the corresponding project inside your Eclipse workspace (SDK launcher app + epub lib).

[sushj]

hi @danielweck ,
After I clone project, I import it to my Eclipse then i rebuild it, i get this err from console
*** No rule to make target 'D:\Program/Workspaces/android/readium/Launcher-Android/readium-sdk/Platform/Android/build/core/build-local.mk'. Stop.,
can you help me, my mail is f.sushj@gmail.com (f.sushj is my nick skype too), thanks, sorry about my english

[danielweck]

Hello @sushj are you on Windows?
Either way, you need to make sure the readium-sdk and readium-shared-js Git submodules are initialized (git submodule update --init --recursive), and git checkout develop && git submodule foreach --recursive "git checkout develop" to ensure the desired branch.

Now, to make your life easier (and because Eclipse has been deprecated by Google for Android development, in favour of AndroidStudio), I would suggest using the Gradle "experimental" branch:
https://github.com/readium/SDKLauncher-Android/tree/feature/gradle-experimental
https://github.com/readium/readium-sdk/tree/feature/gradle-experimental
Make sure to download the latest version of AndroidStudio from the "canary" channel (you can set the option in the update preferences). It is now much simpler than Eclipse, and works great on Windows too.
Let us know how you get on.
Regards.

[sushj]

Hi @danielweck ,
Thank for your suggest about using readium-SDK in Android Studio, i'm try too using it android build successfully, but i'm get this err when app running

java.lang.UnsatisfiedLinkError: Cannot load library: soinfo_link_image(linker.cpp:1635): could not load library "libgnustl_shared.so"
please help me,
thanks,

[danielweck]

Hello, what is your installed NDK version, and is it picked-up correctly by AndroidStudio and the Graddle build?

[sushj]

Hi @danielweck,
I installed NDK android-ndk-r10e, but i wonder how to picked-up correctly, can you guide me correct step, my local.properties show correctly path
ndk.dir=D:\Program\plug-in\android-ndk-r10e
sdk.dir=D:\Program\plug-in\android-sdk-windows
Is due to x86 or 64bit does not ?