CBR reading broken on some device(s)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open a cbr file in ebookdroid
2.
3.

What is the expected output?
opening the file and being able to read it (seeing the images)

What do you see instead?
a black screen and an indicator (spinning wheel) that means ebookdroid is 
trying to load the file

What version of the product are you using?
1.5.1

On what operating system?
Android 2.3.4
kernel 2.6.36

What device are you using?
9.7 inches low cost chinese tablet with Cortex-A8
http://www.mediacomeurope.it/Prodotti/Scheda.aspx?XRI=1924

Please provide any additional information below.
Version 1.3.2 worked fine with cbr on this same device
PerfectViewer correctly opens cbr files on this same device
Tried two other tablets of the same maker and model, they are all unable to 
display cbr files.

Version 1.5.1 works fine with cbr on 8 inches device with Android 2.3.4

Tried the latest two developer versions (dev1581 and the one before that) and 
they won't even open on the 9.7 inches devices

Original issue reported on code.google.com by peltio on 4 Sep 2012 at 4:20

[GoogleCodeExporter]

Sorry the correct operating system for the 8 inches device on which CBR files 
open fine is
Android 2.3.1 with kernel 2.6.32.27.

Original comment by peltio on 4 Sep 2012 at 4:28

[GoogleCodeExporter]

What version are you tried? Generic or Cortex-A8 specific?

Original comment by Andrei.K...@gmail.com on 5 Sep 2012 at 8:22

• Changed state: Discussion

[GoogleCodeExporter]

I tried both.
The generic version simply shows a black screen. And I can recover by going 
back to the bookshelf view.
The Cortex A8 Neon specific version show a black screen with the wheel and the 
"loading... wait" message (in my language).
And it goes on this way indefinitely. I am not able to recover from this, 
though. I have to go to android home and terminate ebookdroid.

Original comment by peltio on 5 Sep 2012 at 2:08

[GoogleCodeExporter]

Further information:

CBZ files are opened normally, so it seems something that is specific to unrar 
or the rar format.
Bug still present in versions 1.5.2 and 1.5.3 dev 1647.

Original comment by peltio on 21 Sep 2012 at 11:57

[GoogleCodeExporter]

OK. Definetly it is caused by malfunctioning of the unrar executable. We will 
try to investigate further.

Original comment by Andrei.K...@gmail.com on 21 Sep 2012 at 12:39

[GoogleCodeExporter]

Did you tried latest build?

Original comment by Andrei.K...@gmail.com on 29 Oct 2012 at 6:29

[GoogleCodeExporter]

Original comment by Andrei.K...@gmail.com on 20 Dec 2012 at 9:33

• Changed state: Fixed