Problem with KOReader 2019.06 "Sea Buckthorn" - Page 3

Frenzie · 08-14-2019, 04:00 AM

The Android version by itself is unrelated, but updated/changed drivers shipped along could potentially alter behavior.

Did you try the prevent screen from turning off setting? It's under settings → screen → screen timeout.

Norbi24 · 08-14-2019, 06:52 AM

Yes, I checked settings->screen->screen timeout -> Keep screen On ...
but unfortunately no change

Frenzie · 08-14-2019, 09:03 AM

When you say you have the problem with the August build, do you mean it used to be different?

Norbi24 · 08-14-2019, 09:41 AM

Yes, previously I had 2019.04, it was working fine, but I was not using it as it was not supporting external dictonary apps, as this has been implemented now for 2019.07, I installed july build and since then it is occuring ... I even went back to 2019.06 just to isolate it, and there it is still fine ....

There must have occured something between june and july builds.

As I now am also able to build koreader on my Debian VM, I could checkout particular commits, build and test and thus isolate which commit may have caused this ...

If you or @pazos had any idea, where to start, I could do it next week and let you know

Thanks, Norbert

pazos · 08-14-2019, 10:19 AM

Quote:

Originally Posted by Norbi24

Yes, previously I had 2019.04, it was working fine, but I was not using it as it was not supporting external dictonary apps, as this has been implemented now for 2019.07, I installed july build and since then it is occuring ... I even went back to 2019.06 just to isolate it, and there it is still fine ....

There must have occured something between june and july builds.

As I now am also able to build koreader on my Debian VM, I could checkout particular commits, build and test and thus isolate which commit may have caused this ...

If you or @pazos had any idea, where to start, I could do it next week and let you know

Thanks, Norbert

You need to look at specific changes in https://github.com/koreader/android-...commits/master.

AFAICT there is no suspicious commit but:

https://github.com/koreader/android-...e3de5defec5075 introduces some overhead (screen helper hold a reference to the activity context from onCreate to onDestroy). It shouldn't hurt on a single activity - single instance application but anyways.

https://github.com/koreader/android-...44858b8827e681 migrates to androidX support libraries. It shouldn't add overhead at runtime (it does quite a bit at buildtime)

And the only commit I would find suspicious (but was present in 2019.06 too):

https://github.com/koreader/android-...821fd583907184. It uses a surfaceview to make java aware of the native window and have means to control it. It seems to setup a HW accel renderer even if we don't use it. On the logs you'll see a lot of GL spam on supported devices. Tolinos w FW11 are the ones that spam all those logs. Any modern android phone will spam them too. Legacy ereaders on 4.0.? don't seem to enable a hw accel surface, which is nice because we don't really need it.

pazos · 08-14-2019, 10:29 AM

And one last thing we might consider: google does not want ICS. It is deprecated for NDK libraries. It is deprecated everywhere. Google suggest a minimum target of api level 16-17. Google didn't fix the emulator for that build.

So, developing a non standard android app for ICS is a real pain. And it is worst if it is deployed on a first-locked-now-rooted device with just 512mb.

Norbi24 · 08-14-2019, 10:59 AM

Thanks, so the next logical step is to update for kitkat
(4.4.2) and try again, perhaps the problem would disappear

pazos · 08-15-2019, 07:07 PM

Quote:

Originally Posted by Norbi24

Thanks, so the next logical step is to update for kitkat
(4.4.2) and try again, perhaps the problem would disappear

Never had a tolino so I'm not sure if switching back to FW10 is possible. In any case do it at your own risk.

Norbi24 · 08-20-2019, 02:25 PM

Guys, wanted only report back - I upgraded my 2nd Tolino for FW 12.2 + open Android 4.4.2 and there it works fine (I mean no 4-5 sec. delays on opening the menus or TOC).

However, the problem on FW 10.1 (Android 4.0.4) occurs only sometimes - really sometimes as I reboot and start KOReader it runs reall smoothly (even a tick better than on later Android 4.4.2 - I have compared them having then side-by-side ...)

So for me the exremely long delays are perhaps really caused by the Android ICS ...
On 4.4.2 it works always fine, unfortunately only a tick showlier than on 4.0.4 - but this is due to the changes in E-Lnk screen refresh, right ?

Frenzie · 08-20-2019, 05:04 PM

There's a brand new build available which might resolve the problem. You can get it at http://build.koreader.rocks/download...78_2019-08-20/ (or just the regular on-device update).

It includes https://github.com/koreader/koreader/issues/5221.

Norbi24 · 08-24-2019, 08:56 AM

Hi Frenzie,
ONly wanted to give a feedback, the version you provided above didn't solve the issue (extremely slow menus + TOC on Tolino FW 10 (ICS).

But I had a discussion with @pazos here
https://www.mobileread.com/forums/sh...d.php?t=322117

and the problem is definitely solved by his PR:

https://github.com/koreader/android-...ncher/pull/172

Thanks a lot
Norbert

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
"Koreader" and "Coolreader" Prefixes	Ken Maltby	Feedback	3	05-21-2015 06:39 PM
I want to read books like "The Old Man and the Sea"	Mesutargie	Reading Recommendations	3	08-29-2014 01:40 PM
Problem "installing" "Kindle library extractor"	dhdurgee	Kindle Developer's Corner	7	11-24-2012 07:09 PM

08-14-2019, 04:00 AM	#31
Frenzie Wizard Posts: 1,617 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	The Android version by itself is unrelated, but updated/changed drivers shipped along could potentially alter behavior. Did you try the prevent screen from turning off setting? It's under settings → screen → screen timeout.

08-14-2019, 06:52 AM	#32
Norbi24 Connoisseur Posts: 64 Karma: 144 Join Date: Aug 2019 Device: Tolino Vision HD4, BOOX Poke2	Yes, I checked settings->screen->screen timeout -> Keep screen On ... but unfortunately no change

08-14-2019, 09:03 AM	#33
Frenzie Wizard Posts: 1,617 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	When you say you have the problem with the August build, do you mean it used to be different?

08-14-2019, 09:41 AM	#34
Norbi24 Connoisseur Posts: 64 Karma: 144 Join Date: Aug 2019 Device: Tolino Vision HD4, BOOX Poke2	Yes, previously I had 2019.04, it was working fine, but I was not using it as it was not supporting external dictonary apps, as this has been implemented now for 2019.07, I installed july build and since then it is occuring ... I even went back to 2019.06 just to isolate it, and there it is still fine .... There must have occured something between june and july builds. As I now am also able to build koreader on my Debian VM, I could checkout particular commits, build and test and thus isolate which commit may have caused this ... If you or @pazos had any idea, where to start, I could do it next week and let you know Thanks, Norbert

08-14-2019, 10:29 AM	#36
pazos cosiñeiro Posts: 1,271 Karma: 2200049 Join Date: Apr 2014 Device: BQ Cervantes 4	And one last thing we might consider: google does not want ICS. It is deprecated for NDK libraries. It is deprecated everywhere. Google suggest a minimum target of api level 16-17. Google didn't fix the emulator for that build. So, developing a non standard android app for ICS is a real pain. And it is worst if it is deployed on a first-locked-now-rooted device with just 512mb.

08-14-2019, 10:59 AM	#37
Norbi24 Connoisseur Posts: 64 Karma: 144 Join Date: Aug 2019 Device: Tolino Vision HD4, BOOX Poke2	Thanks, so the next logical step is to update for kitkat (4.4.2) and try again, perhaps the problem would disappear

08-20-2019, 02:25 PM	#39
Norbi24 Connoisseur Posts: 64 Karma: 144 Join Date: Aug 2019 Device: Tolino Vision HD4, BOOX Poke2	Guys, wanted only report back - I upgraded my 2nd Tolino for FW 12.2 + open Android 4.4.2 and there it works fine (I mean no 4-5 sec. delays on opening the menus or TOC). However, the problem on FW 10.1 (Android 4.0.4) occurs only sometimes - really sometimes as I reboot and start KOReader it runs reall smoothly (even a tick better than on later Android 4.4.2 - I have compared them having then side-by-side ...) So for me the exremely long delays are perhaps really caused by the Android ICS ... On 4.4.2 it works always fine, unfortunately only a tick showlier than on 4.0.4 - but this is due to the changes in E-Lnk screen refresh, right ?

08-20-2019, 05:04 PM	#40
Frenzie Wizard Posts: 1,617 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	There's a brand new build available which might resolve the problem. You can get it at http://build.koreader.rocks/download...78_2019-08-20/ (or just the regular on-device update). It includes https://github.com/koreader/koreader/issues/5221.

08-24-2019, 08:56 AM	#41
Norbi24 Connoisseur Posts: 64 Karma: 144 Join Date: Aug 2019 Device: Tolino Vision HD4, BOOX Poke2	Hi Frenzie, ONly wanted to give a feedback, the version you provided above didn't solve the issue (extremely slow menus + TOC on Tolino FW 10 (ICS). But I had a discussion with @pazos here https://www.mobileread.com/forums/sh...d.php?t=322117 and the problem is definitely solved by his PR: https://github.com/koreader/android-...ncher/pull/172 Thanks a lot Norbert

Advert

Advert