MobileRead Forums - View Single Post - Problem with KOReader 2019.06 "Sea Buckthorn"

pazos · 06-28-2019, 06:47 PM

The suspicious commit is https://github.com/koreader/koreader...fd33b5ec712ea6. Should affect may and june builds

ie. Instead of using the NativeContent surface of NativeActivity we implement our own surface based on a SurfaceView and take ownership of the Native window.

This didn't cause any trouble on most eink devices, with good reports on both rockchip and freescale. But it created a bug (Application Not Responding) on some Amazon firmware -> https://github.com/koreader/koreader/issues/5020.

Please check the build in https://github.com/koreader/koreader...ment-505658530 and see it that fixes your problems. It fixed some long term memory leaks too, so it might help.

I will investigate if we can call the superclass after taking ownership of the window on onCreate.

06-28-2019, 06:47 PM	#15
pazos cosiñeiro Posts: 1,406 Karma: 2451781 Join Date: Apr 2014 Device: BQ Cervantes 4	The suspicious commit is https://github.com/koreader/koreader...fd33b5ec712ea6. Should affect may and june builds ie. Instead of using the NativeContent surface of NativeActivity we implement our own surface based on a SurfaceView and take ownership of the Native window. This didn't cause any trouble on most eink devices, with good reports on both rockchip and freescale. But it created a bug (Application Not Responding) on some Amazon firmware -> https://github.com/koreader/koreader/issues/5020. Please check the build in https://github.com/koreader/koreader...ment-505658530 and see it that fixes your problems. It fixed some long term memory leaks too, so it might help. I will investigate if we can call the superclass after taking ownership of the window on onCreate.