DR800 trickd - fullscreen & pageflow with proper UI

yacoob · 07-09-2010, 07:16 PM

If you feel adventurous, or are annoyed by all this extra clicking you need to do when you're using flowmytears, here's a treat. I've written a slightly better version. It consists of a small program that runs in the background and adds menu options for page flow and/or fullscreen. Download, install, run, head over to PDF file, bring up the menu. It will still cause reader to drop back to main menu, but it'll bring the document back.

Standard disclaimer: if it breaks your DR800, you get to keep both pieces. It works for me, but I don't guarantee it will for you. Hopefully it will :) I've used it for few days now, and I haven't found it affecting battery life in a significant way. If you notice any unexpected behavior or find any bugs, tell me, and I'll do my best (which doesn't mean I'll be able to fix it, I'm not a proper C developer...)

Download it from here:
http://github.com/downloads/yacoob/irex/trickd.zip

Some documentation:
http://github.com/yacoob/irex/blob/m...ckd/README.rst

Feel free to look at the source, point and laugh, comment, then laugh some more. Send patches, too! And if you feel generous, here's my Amazon wishlist 8)

bokjeid · 07-09-2010, 10:10 PM

I'm sorry that an error message pops up which says that it can't be opened and possibly it is already opened. Is there anybody else?

yacoob · 07-10-2010, 05:38 AM

Say. My reader just refused to come back after a boot. I've temporarily removed the zip file from downloads, until I can verify what went wrong :/

yacoob · 07-10-2010, 06:44 AM

Just my luck. Bad blocks in the internal flash. Got it to boot few times, dmesg has shown i/o errors for NAND device. Looks like this is the culprit, but I'm going to debug it further

yacoob · 07-10-2010, 07:13 AM

As I understand it, certain amount of bad blocks is expected with NAND flash:

Code:

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xaa (Micron NAND 256MiB 1,8V 8-bit)
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: Bad block at 0x002e0000
nand_read_bbt: Bad block at 0x00640000
nand_read_bbt: Bad block at 0x010e0000
nand_read_bbt: Bad block at 0x01160000
nand_read_bbt: Bad block at 0x02140000
nand_read_bbt: Bad block at 0x02400000
nand_read_bbt: Bad block at 0x02540000
nand_read_bbt: Bad block at 0x02a80000
nand_read_bbt: Bad block at 0x02c40000
nand_read_bbt: Bad block at 0x05100000
nand_read_bbt: Bad block at 0x05480000
nand_read_bbt: Bad block at 0x05a60000
nand_read_bbt: Bad block at 0x05f00000
nand_read_bbt: Bad block at 0x06380000
nand_read_bbt: Bad block at 0x06ae0000
nand_read_bbt: Bad block at 0x070a0000
nand_read_bbt: Bad block at 0x07360000
nand_read_bbt: Bad block at 0x073a0000
nand_read_bbt: Bad block at 0x08560000
nand_read_bbt: Bad block at 0x08680000
nand_read_bbt: Bad block at 0x089c0000
nand_read_bbt: Bad block at 0x08a80000
nand_read_bbt: Bad block at 0x09540000
nand_read_bbt: Bad block at 0x0a040000
nand_read_bbt: Bad block at 0x0a1e0000
nand_read_bbt: Bad block at 0x0a4c0000
nand_read_bbt: Bad block at 0x0a7a0000
nand_read_bbt: Bad block at 0x0ab40000
nand_read_bbt: Bad block at 0x0b260000
nand_read_bbt: Bad block at 0x0cb20000
Searching for RedBoot partition table in NAND 256MiB 1,8V 8-bit at offset 0x100000
8 RedBoot partitions found on MTD device NAND 256MiB 1,8V 8-bit
Creating 8 MTD partitions on "NAND 256MiB 1,8V 8-bit":
0x00000000-0x00040000 : "RedBoot"
0x00100000-0x0011f000 : "FIS directory"
mtd: partition "FIS directory" doesn't end on an erase block
0x0011f000-0x00120000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't start on an erase block boundary
mtd: partition "RedBoot config" doesn't end on an erase block
0x00120000-0x00520000 : "kernel"
0x00520000-0x00920000 : "kernel_recovery"
0x00920000-0x0a320000 : "rootfs"
0x0a320000-0x0f120000 : "settings"
0x0f120000-0x0f520000 : "sysset"

That's a snippet from dmesg output of a successful boot. Not sure whether this is "expected" amount or not. At the same time the actual problem might be badblocks that are *not yet* in BBT. :(

The annoying part is that so far, device boots in 2 attempts out of 5, getting stuck at the loading screen otherwise. I don't know what it's getting stuck at (kernel? rootfs?) and there doesn't seem to be any logs available from those events. Any way of hooking up a serial console?

yacoob · 07-10-2010, 09:27 AM

I'm getting more and more convinced that the problem I saw was not related to trickd. I've also found and fixed an unrelated problem in trickd, and the zip is available once again.

akey · 07-10-2010, 03:49 PM

Awesome. It works wonderfully on most PDFs. Strangely, however, the menu options don't appear for all PDF files.

Also, if you get around to it, it would be nice to do the same for djvu files opened through luite's plugin.

Thanks!

yacoob · 07-10-2010, 05:43 PM

akey, I'm glad you like it

As for "some PDFs" - the only logic that program applies is whether extension matches ".pdf". If it matches ".epub", only fullscreen option is enabled. Can you send me an example file for which the program doesn't work?

As for djvu - enabling trickd for those would be simple, the question is whether djvu plugin actually respects those two fields (uds_page_flow and uds_full_screen) in its rendering

luite?

luite · 07-10-2010, 06:33 PM

Yes, the djvu plugin works with page flow and full screen. The plugin itself doesn't do anything with those fields, it just passes rendered pages (bitmaps) to uds, at the requested size. It's up to uds to determine the size and placement of those bitmaps on the screen.

yacoob · 07-10-2010, 08:15 PM

There you go. Please test that build, and tell me whether it works for djvu files (as I'm way too sleepy right now to look for those, install the plugin...). Please check both files ending in .djv and .djvu. If that build works fine, I'll submit that code in the morning.

yacoob · 07-11-2010, 11:58 AM

I've found and fixed a race condition that could have stopped trickd for working from time to time (and require a restart). New build available in usual place.

DeReader · 07-12-2010, 03:46 PM

Hi yacoob, cool hack, works fine on my DR800S. I like the fullscreen mode, in some PDFs it gives you that bit of space to have a more optimal zoom level for reading.

E.M · 07-15-2010, 03:00 PM

Works great, thanks!

ExtraSF · 07-16-2010, 11:06 AM

I've been using trickd and it works as advertised. The continous page mode in landscape makes the Dr800 a much more usefull reader..specially for .pdf's.

Thanks again.

yacoob · 07-16-2010, 02:22 PM

In the meantime my device decided to die permanently

Given Irex Technologies current state, I think I'm hosed. Luckily there are no new versions of the firmware, so there should be no changes needed :P

For anyone concerned about his reader: no, usage of trickd and death of my reader are *probably* not connected. It looks like flash memory storing kernel developed bad blocks, and it stopped booting. However, if you want to be 100% sure, don't use trickd.

07-09-2010, 07:16 PM	#1
yacoob Zealot Posts: 120 Karma: 1326 Join Date: Feb 2009 Device: none	trickd - fullscreen & pageflow with proper UI If you feel adventurous, or are annoyed by all this extra clicking you need to do when you're using flowmytears, here's a treat. I've written a slightly better version. It consists of a small program that runs in the background and adds menu options for page flow and/or fullscreen. Download, install, run, head over to PDF file, bring up the menu. It will still cause reader to drop back to main menu, but it'll bring the document back. Standard disclaimer: if it breaks your DR800, you get to keep both pieces. It works for me, but I don't guarantee it will for you. Hopefully it will :) I've used it for few days now, and I haven't found it affecting battery life in a significant way. If you notice any unexpected behavior or find any bugs, tell me, and I'll do my best (which doesn't mean I'll be able to fix it, I'm not a proper C developer...) Download it from here: http://github.com/downloads/yacoob/irex/trickd.zip Some documentation: http://github.com/yacoob/irex/blob/m...ckd/README.rst Feel free to look at the source, point and laugh, comment, then laugh some more. Send patches, too! And if you feel generous, here's my Amazon wishlist 8)

07-16-2010, 11:06 AM	#14
ExtraSF ExtraSolar Posts: 10 Karma: 10 Join Date: Aug 2009 Location: Portugal(Lisbon) Device: Kobo Glo	Continuos page mode. I've been using trickd and it works as advertised. The continous page mode in landscape makes the Dr800 a much more usefull reader..specially for .pdf's. Thanks again.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
FullScreen on Kindle Browser	SunLight	Amazon Kindle	7	10-11-2010 04:30 PM
DR800 Pageflow/fullscreen with UI	yacoob	iRex Developer's Corner	3	07-10-2010 03:51 AM
Output Iliad Fullscreen	Arnau	Calibre	4	04-17-2010 06:27 AM
Reset after Fullscreen with locked Buttons?	Floeee	iRex	2	09-16-2009 09:36 AM
iLiad fullscreen java awt frame	helch	iRex Developer's Corner	0	08-10-2007 03:30 AM

07-09-2010, 10:10 PM	#2
bokjeid Addict Posts: 217 Karma: 10 Join Date: May 2010 Device: DR1000S	I'm sorry that an error message pops up which says that it can't be opened and possibly it is already opened. Is there anybody else?

07-10-2010, 05:38 AM	#3
yacoob Zealot Posts: 120 Karma: 1326 Join Date: Feb 2009 Device: none	Say. My reader just refused to come back after a boot. I've temporarily removed the zip file from downloads, until I can verify what went wrong :/

07-10-2010, 06:44 AM	#4
yacoob Zealot Posts: 120 Karma: 1326 Join Date: Feb 2009 Device: none	Just my luck. Bad blocks in the internal flash. Got it to boot few times, dmesg has shown i/o errors for NAND device. Looks like this is the culprit, but I'm going to debug it further

07-10-2010, 09:27 AM	#6
yacoob Zealot Posts: 120 Karma: 1326 Join Date: Feb 2009 Device: none	I'm getting more and more convinced that the problem I saw was not related to trickd. I've also found and fixed an unrelated problem in trickd, and the zip is available once again.

07-10-2010, 03:49 PM	#7
akey Member Posts: 18 Karma: 10 Join Date: Feb 2010 Device: iRex ...	Awesome. It works wonderfully on most PDFs. Strangely, however, the menu options don't appear for all PDF files. Also, if you get around to it, it would be nice to do the same for djvu files opened through luite's plugin. Thanks!

07-10-2010, 05:43 PM	#8
yacoob Zealot Posts: 120 Karma: 1326 Join Date: Feb 2009 Device: none	akey, I'm glad you like it As for "some PDFs" - the only logic that program applies is whether extension matches ".pdf". If it matches ".epub", only fullscreen option is enabled. Can you send me an example file for which the program doesn't work? As for djvu - enabling trickd for those would be simple, the question is whether djvu plugin actually respects those two fields (uds_page_flow and uds_full_screen) in its rendering luite?

07-10-2010, 06:33 PM	#9
luite Connoisseur Posts: 82 Karma: 256 Join Date: Feb 2010 Location: Netherlands Device: dr1000	Yes, the djvu plugin works with page flow and full screen. The plugin itself doesn't do anything with those fields, it just passes rendered pages (bitmaps) to uds, at the requested size. It's up to uds to determine the size and placement of those bitmaps on the screen.

07-11-2010, 11:58 AM	#11
yacoob Zealot Posts: 120 Karma: 1326 Join Date: Feb 2009 Device: none	I've found and fixed a race condition that could have stopped trickd for working from time to time (and require a restart). New build available in usual place.

07-12-2010, 03:46 PM	#12
DeReader Connoisseur Posts: 69 Karma: 126 Join Date: Jan 2010 Location: Germany Device: Sony PRS-T1, iRex DR1000S, Kindle DXG, Jetbook Color	Hi yacoob, cool hack, works fine on my DR800S. I like the fullscreen mode, in some PDFs it gives you that bit of space to have a more optimal zoom level for reading.

07-15-2010, 03:00 PM	#13
E.M Junior Member Posts: 2 Karma: 10 Join Date: Jun 2010 Device: DR800	Works great, thanks!

Advert

Advert

07-16-2010, 02:22 PM	#15
yacoob Zealot Posts: 120 Karma: 1326 Join Date: Feb 2009 Device: none	In the meantime my device decided to die permanently Given Irex Technologies current state, I think I'm hosed. Luckily there are no new versions of the firmware, so there should be no changes needed :P For anyone concerned about his reader: no, usage of trickd and death of my reader are probably not connected. It looks like flash memory storing kernel developed bad blocks, and it stopped booting. However, if you want to be 100% sure, don't use trickd.