Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android devices reported not working #673

Closed
Markismus opened this Issue Jun 29, 2014 · 44 comments

Comments

Projects
None yet
@Markismus
Copy link
Member

commented Jun 29, 2014

Ken Maltby started a thread on mobileread that has attracted some posts about non-compatible devices.

Please post non-working devices with android version number if at all possible!!

@chrox chrox changed the title Devices which are reported to be non-compatible for now. Android devices reported to be not working for now Jun 30, 2014

@chrox chrox added the Android label Jun 30, 2014

@chrox chrox referenced this issue Jun 30, 2014

Closed

frequent crashes #655

@chrox

This comment has been minimized.

Copy link
Member

commented Jun 30, 2014

Koreader also crashes on Galaxy Grand and Kindle Fire HDX 8.9. Reported in #655.

@hwhw

This comment has been minimized.

Copy link
Member

commented Jun 30, 2014

Crashes on unpacking bundle on each startup on Nexus 4, running Cyanogen M6, Android 4.4.2.

@hwhw

This comment has been minimized.

Copy link
Member

commented Jun 30, 2014

Crashes on unpacking bundle on each startup on the Android Emulator coming with the Android SDK.

@chrox

This comment has been minimized.

Copy link
Member

commented Jun 30, 2014

I can reliably reproduce crash or non-crash on my Android 4.2 phone now. The trick is how I boot the device. If the phone is fully shutdown or pulled out battery and then power up, the subsequent launching of Koreader will be fine without crash. If I reboot my phone with the command reboot in the terminal emulator, each launching of Koreader will end up with crash as described in #643 especially with a swipe gesture. This should not be coincidence because I have tried both conditions multiple times. And it predicts very well.

So is there any subtle environment difference between those two ways of reboot that may affect Koreader's behavior, especially the dynamic loading facility considering the back trace always directs to shared libraries loaded by Koreader?

@houqp

This comment has been minimized.

Copy link
Member

commented Jun 30, 2014

Also crashes very frequently on Nexus S 4.1.2 stock firmware. It works perfect on my HTC one X with stock 4.1.1 android.

@chrox , do you get the crash after rebooting your device using android's UI?

@chrox

This comment has been minimized.

Copy link
Member

commented Jul 1, 2014

Yes, normal reboot from power button also results crash in all subsequent launching of Koreader.

@th0mass

This comment has been minimized.

Copy link
Contributor

commented Jul 5, 2014

Crashes on Galaxy S3 Mini 4.1.2

@chrox

This comment has been minimized.

Copy link
Member

commented Jul 15, 2014

The latest nightly build won't crash on my Android phone 4.2.2 any more. And it also runs normally on Meizu MX3 4.4.4. Hopefully the #643 issue is solved.

@NiLuJe

This comment has been minimized.

Copy link
Member

commented Jul 15, 2014

@chrox: Whee, awesome :).

@H56

This comment has been minimized.

Copy link

commented Jul 15, 2014

@chrox
I am sorry to say that it also cannot run on my devices. On Meizu MX2 4.4.4 the error is "Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1), thread 6222 (reader.launcher)". And on boox c65ml the fault is "signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000068". I downloaded the version of koreader-nightly-20140715. Maybe the version is not it.

@H56

This comment has been minimized.

Copy link

commented Jul 15, 2014

Thanks for all your hard work. Even if these little flaws, it is also a very pretty and useful software!

@hwhw

This comment has been minimized.

Copy link
Member

commented Jul 15, 2014

My devices fail with the same fault address. It's also the address of the pc, so I guess the stack is mangled at some point. The stack trace points at fwrite, my wild guess is that we have wrong FFI definitions for something. It might be an alignment thing.

@Markismus

This comment has been minimized.

Copy link
Member Author

commented Sep 17, 2014

Update on the HTC Desire HD, android 2.35:
All builds after 577 generate a black screen only.

@Markismus

This comment has been minimized.

Copy link
Member Author

commented Sep 17, 2014

Doogee DG500C with preïnstalled Android 4.2 also generates this black screen.

@embryo10

This comment has been minimized.

Copy link

commented Sep 18, 2014

HTC Nexus One Android 2.3.7 CM7 and
Samsung Nexus S Android 4.4.4 CM11 M10
Both FC koreader when it starts.

@acalva

This comment has been minimized.

Copy link

commented Oct 2, 2014

I found out that if I uninstall lbe security master the program works ok, with lbe installed it crashes apparently when touching an empty space.

@chrox chrox changed the title Android devices reported to be not working for now Android devices reported not working Oct 5, 2014

@chrox

This comment has been minimized.

Copy link
Member

commented Oct 5, 2014

Probably we could open an issue for working Android device with koreader. LOL

@hwhw

This comment has been minimized.

Copy link
Member

commented Oct 6, 2014

Yep, I'm pretty sure there is a out-of-bounds memory access lingering around. It's just a matter of chance if it hits something vital.

@tastypear

This comment has been minimized.

Copy link

commented Oct 6, 2014

unfortunately FC on N9100 Panadroid 4.5 (Android 4.4.4)

@embryo10

This comment has been minimized.

Copy link

commented Nov 17, 2014

Version 2014.04-1118 is the first that runs on my Nexus S Kit-Kat 4.4.4 (CyanogenMod).
Seems usable but there is one question.
Where should I copy the dict, tessdata folders and the defaults.persistent.lua file?
I tried '\Android\data\org.koreader.launcher', '\Android\data\org.koreader.launcher\files' and '\Android\obb\org.koreader.launcher' with no Luck.

UPDATE: I found '\data\data\org.koreader.launcher\files' that's looked promising, but still no joy ..

@llb1979

This comment has been minimized.

Copy link

commented Jun 14, 2015

my mobile (nubia z7mini 4.4)works well.But i cant't use this software in Samsung note4(4.4) and levono k3 note(andriod 5.0),please help us! I need this program to read pdf!

@baqlias

This comment has been minimized.

Copy link

commented Jul 10, 2015

Let me add two Android E-Ink devices: the Boyue T62+ and the Onyx Boox C67ML Carta. Both of them run Android 4.2.2. I tried installing koreader on each one. On the T62+, I could never get past the list of folders. Constant crashing. On the Onyx, I was actually able to select a book, open it, look at the formatting options, and turn a couple of pages before it crashed. What I saw looked very promising.

@gerroon

This comment has been minimized.

Copy link

commented Sep 8, 2015

@baqlias
Are you able to use recent Koreader om Onyx Boox C67ML ? I am interested in this device but I am afraid Koreader wont run it.

thanks

@baqlias

This comment has been minimized.

Copy link

commented Sep 8, 2015

There has been a firmware update for the Onyx Boox C67ML since my last post. Yes, the latest nightly for Koreader works on the Onyx most of the time - but occasionally it may crash when I select an item in settings or open a book. I don't see a crash very often, but it does happen.

@KenMaltby

This comment has been minimized.

Copy link

commented Sep 8, 2015

@baqlias

This comment has been minimized.

Copy link

commented Sep 8, 2015

Thanks, Ken. I actually happen to know personally the one who made that post! Since gerroon was asking about a recent version of Koreader, I thought I'd try the latest nightly. It does work on my Onyx Boox C67ML - most of the time. But that older version referenced on that post works flawlessly all the time.

@gerroon

This comment has been minimized.

Copy link

commented Sep 8, 2015

Crap, it sounds nice except that I cant find the release that is mentioned in Ken`s post ;(

@KenMaltby

This comment has been minimized.

Copy link

commented Sep 8, 2015

It is a long ways back there : https://github.com/koreader/koreader/releases/tag/v2014.07.04-nightly
It would be lacking quite a bit, given all the development since then.

@baqlias

This comment has been minimized.

Copy link

commented Sep 8, 2015

Thanks. I was just about to post that link! It's possible that a more recent nightly will work fine, but this one, I know, works flawlessly.

@gerroon

This comment has been minimized.

Copy link

commented Sep 8, 2015

Hollllllllllyyyyy crappppppppppppppppppppppppppp. This works on my Boyue flawless. I do not know why they do not bring this stability back to Android ;( I bet it will work great on my Android tablet.

I bought this T62 to use Koreader on it and it never worked and I felt like I wasted $130 on it ;( Maybe I can use this version now.

The only issue is that the screen size patch does not work with it. #1180

@NiLuJe

This comment has been minimized.

Copy link
Member

commented Sep 8, 2015

Guess it's git bisect time for those who care about Android... ;p.

@irregularisnotrandom

This comment has been minimized.

Copy link

commented Sep 23, 2015

@NiLuJe

I wish that somone who knows coding did. :)

@KenMaltby

This comment has been minimized.

Copy link

commented Sep 24, 2015

I wonder how much might be issues related to Android and if any is really related to CyanogenMod? Might there be two different results?

@Frenzie

This comment has been minimized.

Copy link
Member

commented Sep 25, 2015

Like I said here, no issues here on cm-12.1. Doesn't mean there aren't any issues with e.g. cm-11, of course.

@danielrschmidt

This comment has been minimized.

Copy link

commented Sep 26, 2015

Another report for today's nightly (v2014.11-346-gf85da28):

I get mixed results on the Galaxy S4 running Android 5.0.1: Koreader takes a long time to load (showing a black screen) and it gets stuck at startup from time to time. Once it displays the directory list, however, it works smoothly and seems to be stable.

On the other hand: No issues on the Galaxy Note 8.0 (Android 4.4.2) so far. The directory list loads quickly, the black screen is there for just a second or so.

Only bug I found: If I set a home directory, it is not selected as the start directory on the next startup. Also, Koreader crashes if I click on the Home icon in the top screen toolbar. This happens on both devices.

@KenMaltby

This comment has been minimized.

Copy link

commented Sep 26, 2015

Does the Android version create a crash log?

@danielrschmidt

This comment has been minimized.

Copy link

commented Sep 26, 2015

If it does, I can't find it.Hum.

@chrox

This comment has been minimized.

Copy link
Member

commented Sep 26, 2015

Koreader on Android has no error log file (probably we need one), but if have adb access to your device, you can get the log by adb logcat | grep luajit when koreader is running.

@danielrschmidt

This comment has been minimized.

Copy link

commented Sep 27, 2015

Perfect, running adb is no problem, I'm attaching a few logs below. In the meantime, I figured out that the long black screens occur if the previous session has crashed. Apart from that, the app starts quickly.

I did the following to produce the logs:

  1. This is a successful start
  2. Open a book, open toolbar, tap on home -> crash.
  3. This is a relaunch after a crash, the black screen occurs after line 4 and before line 5 appears (just before "Application data directory...").
  4. Double tap on the back button to close the app -> crash.

Link to the logs: https://gist.github.com/danielrschmidt/00023fe97db9f9e57f35

@xorrox

This comment has been minimized.

Copy link

commented Nov 13, 2015

This is about a Sony Z1 (C6903) phone running an unofficial Android 5.1.1 ROM:

With the 2015-stable version, the screen just stays black. (logcat reports a problem about the filemanager module.)

With the 2014.04-309-g854b941 build linked by Ken, it basically works, but after selecting a book from file manager, after loading that book in the reader, the filemanager icon is missing. And exiting with the home icon doesn't actually kill the app. I also have a really hard time hitting the icons in the reader properly, could be related.

Adding logcats for both cases.
sony-z1-2015-stable.txt
sony-z1-2014-4.txt

////
EDIT:

I've narrowed it down: On that Xperia Z1, Android 5.1.1, Koreader build 415 still works, while build 421 doesn't.

@Frenzie

This comment has been minimized.

Copy link
Member

commented Nov 26, 2015

I acquired a Zenfone 2 (ZE551ML) to replace my aging SE Xperia Ray. Because it runs on an Intel processor, it doesn't work.

All the prerequisites are in place already in https://github.com/koreader/android-luajit-launcher/ to easily build APKs that contain binaries for both x86 and ARM, so I guess the main question is whether or not it's a good idea to. There aren't too many Intel-powered Android devices, so I suppose not.

@Markismus

This comment has been minimized.

Copy link
Member Author

commented Aug 14, 2016

Teclast x98 plus tablet with android 5.1 doesn't work. As others do work on android 5, it probably has to do with te screen resolution of 2k times 1.5k. Will investigate the logs with adb as soon as my girls are on vacation.

Reading the issue about android testing it seems more obvious the Intel atom cpu (Cherry Trail 8300) is the problem.

@Frenzie

This comment has been minimized.

Copy link
Member

commented Apr 2, 2017

I figured I'd try it again on my Zenfone 2 to see what happens.

04-02 14:34:29.270 20250 20266 I luajit-launcher: Waiting for app ready...
04-02 14:34:29.300 20250 20266 I luajit-launcher: App window ready.
04-02 14:34:29.300 20250 20266 I luajit-launcher: App gained focus.
04-02 14:34:29.300 20250 20266 I luajit-launcher: Launching LuaJIT assets...
04-02 14:34:29.620 20250 20266 I luajit-launcher: Application data directory /data/user/0/org.koreader.launcher/files
04-02 14:34:29.620 20250 20266 I luajit-launcher: Application library directory /data/app/org.koreader.launcher-1/lib/arm
04-02 14:34:29.620 20250 20266 I luajit-launcher: Screen size 1080x1920
04-02 14:34:29.630 20250 20266 I luajit-launcher: Screen brightness 12
04-02 14:34:29.640 20250 20266 I luajit-launcher: show progress dialog
04-02 14:34:29.660 20250 20266 I luajit-launcher: Check file in asset module: koreader-g1b700c0.7z
04-02 14:34:29.660 20250 20266 I luajit-launcher: Skip installation for revision g1b700c0
04-02 14:34:29.660 20250 20266 I luajit-launcher: dismiss progress dialog
04-02 14:34:29.660 20250 20266 I luajit-launcher: Change directory to /data/data/org.koreader.launcher/files
04-02 14:34:29.670 20250 20266 I KOReader: intent file path 
04-02 14:34:29.670 20250 20266 I KOReader: run command chmod 755 ./sdcv
04-02 14:34:29.700 20250 20266 I KOReader: command stdout:
04-02 14:34:29.700 20250 20266 I KOReader: command stderr:
04-02 14:34:29.700 20250 20266 I KOReader: command res:0
04-02 14:34:29.700 20250 20266 I KOReader: run command chmod 755 ./tar
04-02 14:34:29.720 20250 20266 I KOReader: command stdout:
04-02 14:34:29.720 20250 20266 I KOReader: command stderr:
04-02 14:34:29.720 20250 20266 I KOReader: command res:0
04-02 14:34:29.730 20250 20266 I KOReader: run command chmod 755 ./zsync
04-02 14:34:29.750 20250 20266 I KOReader: command stdout:
04-02 14:34:29.750 20250 20266 I KOReader: command stderr:
04-02 14:34:29.750 20250 20266 I KOReader: command res:0
04-02 14:34:29.780 20250 20266 I KOReader: try to load module libs/libkoreader-lfs.so
04-02 14:34:29.840 20250 20266 I KOReader: external storage /storage/emulated/0
04-02 14:34:29.870 20250 20266 I KOReader: ERROR cannot open translation file: l10n/en_US/koreader.po
04-02 14:34:29.910 20250 20266 I KOReader: ffi.load SDL2
04-02 14:34:29.910 20250 20266 I KOReader: ffi.load SDL

Note the three minute gap!

04-02 14:37:56.480 20250 20266 I KOReader: INFO  initializing for device Android
04-02 14:37:56.480 20250 20266 I KOReader: INFO  framebuffer resolution: {
04-02 14:37:56.480 20250 20266 I KOReader:     ["h"] = 1920,
04-02 14:37:56.480 20250 20266 I KOReader:     ["w"] = 1080
04-02 14:37:56.480 20250 20266 I KOReader: }
04-02 14:37:56.480 20250 20266 I KOReader: ffi.load libs/libfreetype.so.6
04-02 14:37:56.520 20250 20266 I KOReader: ffi.load libs/libmupdf.so
04-02 14:37:56.580 20250 20266 I KOReader: ffi.load libs/libwrap-mupdf.so
04-02 14:37:56.700 20250 20266 I KOReader: try to load module common/socket/score.so
04-02 14:37:56.720 20250 20266 I KOReader: try to load module common/mime/mcore.so
04-02 14:37:56.740 20250 20266 I KOReader: try to load module common/ssl.so
04-02 14:37:56.800 20250 20266 I KOReader: try to load module rocks/lib/lua/5.1/lpeg.so
04-02 14:37:56.810 20250 20266 E luajit-launcher: Failed to run script: error loading module 'lpeg' from file 'rocks/lib/lua/5.1/lpeg.so':
04-02 14:37:56.810 20250 20266 E luajit-launcher: 	dlopen failed: library "rocks/lib/lua/5.1/lpeg.so" not found

Then it just stays white.

I don't comprehend Android, so that's about all I can contribute. :-)

This was referenced Apr 2, 2017

@Frenzie

This comment has been minimized.

Copy link
Member

commented Feb 21, 2019

I'll close this as outdated.

@Frenzie Frenzie closed this Feb 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.