Sumsung Galaxy Tab 7.7 P6800 supports only v.1 and v.1.1.4

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install separately each package with ARM Cortex A9 support.
2. Setup, launch and remove ebookdroid packages from higher to earlier 
versions...
3. Check, whether any version launches at Samsung GT.
4. If it launches (v.1 and v.1.1.4), it became evident, that error is caused at 
initial start by automatic directory screening and absence of small memory 
support...

What is the expected output?
I expect to have no directory screening and book finding at first start
(especially for my SDcard pathway: /sdcard/extStorages/SdCard/)
I expect to have small memory support at first start.

What do you see instead?
I see, that last versions of EBookDroid crash at start, from v.1.2.2 to 
ebookdroid-1.5.3-dev-r1682...
I have to use late version 1.1.4, but it also crashes at quick zoom sometimes...

What version of the product are you using?
ebookdroid-1.5.3-dev-r1682

On what operating system?
Android 3.2

What device are you using?
Samsung Galaxy Tab 7.7 P6800

Please provide any additional information below.

Original issue reported on code.google.com by skurydi...@gmail.com on 28 Sep 2012 at 10:07

[GoogleCodeExporter]

How can I provide detailed technical information on these startup crashes?

Original comment by skurydi...@gmail.com on 28 Sep 2012 at 10:09

[GoogleCodeExporter]

http://code.google.com/p/ebookdroid/wiki/FAQ

Original comment by Alexander.V.Kasatkin@gmail.com on 28 Sep 2012 at 11:06

• Changed state: Discussion

[GoogleCodeExporter]

Thank you for aLogCat link. I attach several logs for several builds of 
EBookDroid.

Original comment by skurydi...@gmail.com on 28 Sep 2012 at 12:04

Attachments:

• alogcat.2012-09-28-Crash-at-large-zoom-pdf-text-file-v114.txt
• alogcat.2012-09-28-normal-work-v114.txt
• alogcat.2012-09-28-several-crashes-at-startup-v153-r1682.txt

[GoogleCodeExporter]

Can you attach log that starts before startup of EBookDroid?

Original comment by Andrei.K...@gmail.com on 28 Sep 2012 at 12:33

[GoogleCodeExporter]

Thanks. System log of GT-P6800 clear boot without any user actions is attached. 
Please, review.

Original comment by skurydi...@gmail.com on 29 Sep 2012 at 11:04

Attachments:

• alogcat.2012-09-29-normal-clear-boot.txt

[GoogleCodeExporter]

To prevent crashes at ebookdroid start-up I need to open any document quickly, 
before scanning begins...
Thus, I want to turn off:
1) scanning my directory structure at start-up
2) an option of unknown background vpn-connection to web...

PayPal donation is appreciated :)

Original comment by skurydi...@gmail.com on 30 Sep 2012 at 9:42

[GoogleCodeExporter]

1) scanning my directory structure at start-up

You can use any file browser (File manager HD, ES explorer, etc) to open your 
files directly in EBookDroid. In that case no scanning will be performed. Just 
opening the book.

2) an option of unknown background vpn-connection to web

Sorry, I do not understand what do you mean. In EBookDroid there is no  
background vpn-connection to web.

Original comment by Andrei.K...@gmail.com on 30 Sep 2012 at 10:40

[GoogleCodeExporter]

Maybe I am wrong. But I saw unknown vpn lines in logs at EBookDroid startup 
(and I have no VPN connections at all).
Why not to turnoff folder scanning at startup? Do you really need it? Is it 
principal for EBookDroid functionality? I need this option to be tuned in 
options.

Original comment by skurydi...@gmail.com on 30 Sep 2012 at 11:12

[GoogleCodeExporter]

Original comment by Andrei.K...@gmail.com on 11 Dec 2012 at 7:43

• Changed state: Done