-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
Koreader also crashes on Galaxy Grand and Kindle Fire HDX 8.9. Reported in #655. |
Crashes on unpacking bundle on each startup on Nexus 4, running Cyanogen M6, Android 4.4.2. |
Crashes on unpacking bundle on each startup on the Android Emulator coming with the Android SDK. |
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 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? |
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? |
Yes, normal reboot from power button also results crash in all subsequent launching of Koreader. |
Crashes on Galaxy S3 Mini 4.1.2 |
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. |
@chrox: Whee, awesome :). |
@chrox |
Thanks for all your hard work. Even if these little flaws, it is also a very pretty and useful software! |
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. |
Update on the HTC Desire HD, android 2.35: |
Doogee DG500C with preïnstalled Android 4.2 also generates this black screen. |
HTC Nexus One Android 2.3.7 CM7 and |
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. |
Probably we could open an issue for working Android device with koreader. LOL |
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. |
unfortunately FC on N9100 Panadroid 4.5 (Android 4.4.4) |
Version 2014.04-1118 is the first that runs on my Nexus S Kit-Kat 4.4.4 (CyanogenMod). UPDATE: I found '\data\data\org.koreader.launcher\files' that's looked promising, but still no joy .. |
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! |
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. |
@baqlias thanks |
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. |
This might be of interest. http://www.mobileread.com/forums/showpost.php?p=3144545&postcount=35 Luck; |
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. |
Crap, it sounds nice except that I cant find the release that is mentioned in Ken`s post ;( |
It is a long ways back there : https://github.com/koreader/koreader/releases/tag/v2014.07.04-nightly |
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. |
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 |
Guess it's git bisect time for those who care about Android... ;p. |
I wish that somone who knows coding did. :) |
I wonder how much might be issues related to Android and if any is really related to CyanogenMod? Might there be two different results? |
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. |
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. |
Does the Android version create a crash log? |
If it does, I can't find it.Hum. |
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 |
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:
Link to the logs: https://gist.github.com/danielrschmidt/00023fe97db9f9e57f35 |
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. //// I've narrowed it down: On that Xperia Z1, Android 5.1.1, Koreader build 415 still works, while build 421 doesn't. |
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. |
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. |
I figured I'd try it again on my Zenfone 2 to see what happens.
Note the three minute gap!
Then it just stays white. I don't comprehend Android, so that's about all I can contribute. :-) |
I'll close this as outdated. |
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!!
The text was updated successfully, but these errors were encountered: