Open GoogleCodeExporter opened 9 years ago
Original comment by mpietrzak
on 19 May 2010 at 1:33
I can't confirm it :)
I've displayed it with current version. It shows ugly white border around pages
- but
that's because APV shows media box instead of content only.
Could you please provide more information? Like phone model, resolution,
android
system version. Maybe you could provide more logs (before exception you've
pasted
happens).
Did you try to reproduce this bug in emulator?
Original comment by mpietrzak
on 19 May 2010 at 1:42
Wow, thanks for an extremely fast response time.
I use the latest stable cyanogen ROM on a plain old G1. I've attached the log;
some
relevant information that is also at its top:
Log Collector version: 1.1.0
Device model: T-Mobile G1
Firmware version: 1.6
Kernel version: 2.6.29.6-cyanogenmod
root@pershoot-ubuntu )
#1 PREEMPT Wed Mar 3 23:43:23 EST 2010
Build number: DRC83
The log is from a run with the "dusted donuts" dalvik JIT enabled, as you can
also
see from some messages. However I've also tested with the original dalvik, with
the
same result.
I'll have to put off experiments with the emulator until after working hours.
Original comment by thomasra...@gmail.com
on 19 May 2010 at 2:30
Attachments:
Very strange - I'm using adp1 with htc's android 1.6 and get rendering.
Are you sure pdf file on your sdcard is not broken?
Would you be willing to test with specially built apk with additional debugging
enabled? Debug version produces a LOT of logs and works very slowly, but it's
possible
to pin down bugs
Original comment by mpietrzak
on 19 May 2010 at 2:40
Damn, you're right. The PDF came out of K-9 mail damaged (saved it from an
email).
Getting a fresh copy worked. Sorry for taking your time over this.
I suppose a "your PDF is damaged" error message would have been nice though ;-)
Original comment by thomasra...@gmail.com
on 19 May 2010 at 2:49
PDF Viewer should never crash. I didn't bother with proper error reporting in
early
stages of coding, but now it's definitely the time to fix those loose ends, so
I'm
leaving this open; it should be fixed in 0.2.8.
Original comment by mpietrzak
on 19 May 2010 at 3:08
Original issue reported on code.google.com by
thomasra...@gmail.com
on 19 May 2010 at 12:39Attachments: