Closed GoogleCodeExporter closed 8 years ago
It seems that your device/android version has very low memory available and
even Starting Launcher activity forces EBookDroid to be unloaded from memory.
Original comment by Andrei.K...@gmail.com
on 18 Apr 2012 at 7:01
Forget about the memory issues for a minute please, not all the issues i will
have from now to eternity will be related to memory issues.
I don't think it is a memory issue, you can see for yourself in this video:
http://youtu.be/gLCPZiwl0oU
In the video all that i'm doing is to show you that apparently it is not a
memory issue.
In time 2:05 you can see that ebookdroid is not unloaded from memory.
The exact procedure stated here in Issue 206 is between time frame 01:14 and
1:35
(Being in ebookdroid going to android home, and then returning to ebookdroid
with the expectation that the already loaded page remain there)
Are you saying that when YOU did the procedure stated here in Issue 206 (press
the home button then returning) you get the already loaded page?
Ps:The program used to show memory status are SystemPanel and CoolTool.
CootTool is the little box in upper right corner that shows CPU usage and RAM
memory available. CooLTool is a free app that shows real time information and
in this case it is configured to an update interval of 2 sec.(very handy)
Thanks
Original comment by lanos...@gmail.com
on 18 Apr 2012 at 7:24
I'd like to second this motion. Altough this behaviour has remained unchanged
for quite some time (I use the app for 7 months now). It would be nice to see
it changed to more normal (fixed would be a wrong word here).
Original comment by jiguromu...@gmail.com
on 24 Apr 2012 at 6:46
I checked, and this is also happening in this device:
Device: Rena3/Rena/Haipad M9 etc...
A 7 inch china Tablet with Android 2.2.1 and a capacitive two-point touch
screen with 800x480 screen resolution
CPU Renesas/nec Cortex A9 Dual-Core 512mhz+512hz
GPU PowerVX SGX530
Original comment by lanos...@gmail.com
on 25 Apr 2012 at 4:32
If I understand the original poster correctly, you can achieve what you want by
setting the option All Settings -> User Interface -> Load Recent
Original comment by norri...@gmail.com
on 2 May 2012 at 12:37
Actually no. That setting influences the app start behaviour, not the behaviour
exhibited when you have it running, press the home key to do something else,
and then you return to it. The problem described here occurs when you return to
the app and you find the recent documents screen instead of the document you
had open when you pressed home.
Original comment by jiguromu...@gmail.com
on 2 May 2012 at 12:41
Original issue fixed in trunk.
Original comment by Alexander.V.Kasatkin@gmail.com
on 3 Jul 2012 at 3:20
Issue 271 has been merged into this issue.
Original comment by Alexander.V.Kasatkin@gmail.com
on 7 Aug 2012 at 1:09
Original issue reported on code.google.com by
lanos...@gmail.com
on 17 Apr 2012 at 7:06Attachments: