SkipStone browser for Kindle Touch

[baf]

Originally Posted by briant1234

UHOH! so i tried to load gmail, and everything froze up.

Do you use gnash browser plugin?

[baf]

Originally Posted by twobob

as you can see I need to fix the rotated layout for the mini.

Matchbox-keyboard layout is very easy to customize. Look into keyboard.xml file in the package.

[briant1234]

Yea, i used gnash, ill try it with it off for now. anyway after i got it working, all my books wouldnt open O.o im resyncing now to see if it is fixed

[twobob]

Originally Posted by baf

Matchbox-keyboard layout is very easy to customize. Look into keyboard.xml file in the package.

sorry mate. will do. I was still knee deep in ordered dither.

SDL tweaking. I will indeed have a look myself. just sharing what I was up to with the mini keyboard. : ) thanks baf

[briant1234]

ugh so i tried out the new version, turned gnash off, loaded up gdocs, and it froze and wouldnt do anything. i got it to restart, however, now, when i unlock it, it just shows a blank screen where the menu is supposed to be. It recognizes on the pc, but i dont seem to be able to hardware restart it. any advice?

atm- very scared of skipstone hehe havent managed to use it for more then 1 min bfore crashes

[twobob]

Originally Posted by briant1234

ugh so i tried out the new version, turned gnash off, loaded up gdocs, and it froze and wouldnt do anything. i got it to restart, however, now, when i unlock it, it just shows a blank screen where the menu is supposed to be. It recognizes on the pc, but i dont seem to be able to hardware restart it. any advice?

atm- very scared of skipstone hehe havent managed to use it for more then 1 min bfore crashes

hmm weird. it's been fairly solid on mine.

[briant1234]

generally what sort of sites are you loading? just loading anything more than a google page freezes it up

[thatworkshop]

Originally Posted by baf

The best way of fixing it would be adding some RAM to Kindle

Seriously, if it's possible, I'm willing to do it.

[baf]

Originally Posted by briant1234

atm- very scared of skipstone hehe havent managed to use it for more then 1 min bfore crashes

I might have spoiled it with my "improvements".
I will investigate when I have some time.

[geekmaster]

Originally Posted by baf

... The best way of fixing it would be adding some RAM to Kindle
...

Instead of RAM surgery inside your kindle, you can free up some RAM with a swap file, but the tradeoff is that it will cause extra write wear on the mmc while it is used. You can also use a swap file over a network (such as an nbd device) to save the mmc.

[twobob]

Originally Posted by geekmaster

Instead of RAM surgery inside your kindle, you can free up some RAM with a swap file, but the tradeoff is that it will cause extra write wear on the mmc while it is used. You can also use a swap file over a network (such as an nbd device) to save the mmc.

Would an external USB device be too slow to be a practical swap space?

[baf]

Originally Posted by briant1234

generally what sort of sites are you loading? just loading anything more than a google page freezes it up

I put new version on my site. Maybe massive debug output, that I forgot to remove, was freezing kindle.
I also corrected mime handling.
Please test.

[zerolucat]

there is a way to copy and paste some text?

[knc1]

Originally Posted by twobob

Would an external USB device be too slow to be a practical swap space?

No, it would not be "too slow", but it might be noticeable.

If the kernel supports NBD (Network Block Device), swap works over NBD.

It does not work over CIFS (Samba) nor NFS. In both cases trying to do that can lead to a kernel deadlock.

[twobob]

Originally Posted by knc1

No, it would not be "too slow", but it might be noticeable.

If the kernel supports NBD (Network Block Device), swap works over NBD.

It does not work over CIFS (Samba) nor NFS. In both cases trying to do that can lead to a kernel deadlock.

okay. I've built a few tools to give this a try. Don't want to Hi-jack the thread though so I've spoilered most of it...

Spoiler:

[root@kindle root]# nbd-server --help

This is nbd-server version 3.1
Usage: [ip:|ip6@]port file_to_export [size][kKmM] [-l authorize_file] [-r] [-m] [-c] [-C configuration file] [-p PID file name] [-o section name] [-M max connections]
-r|--read-only read only
-m|--multi-file multiple file
-c|--copy-on-write copy on write
-C|--config-file specify an alternate configuration file
-l|--authorize-file file with list of hosts that are allowed to
connect.
-p|--pid-file specify a filename to write our PID to
-o|--output-config output a config file section for what you
specified on the command line, with the
specified section name
-M|--max-connections specify the maximum number of opened connections

if port is set to 0, stdin is used (for running from inetd).
if file_to_export contains '%s', it is substituted with the IP
address of the machine trying to connect
if ip is set, it contains the local IP address on which we're listening.
if not, the server will listen on all local IP addresses
Using configuration file /etc/nbd-server/config

1st server test:

Kindle:

[root@kindle /dev]# nbd-server -C /dev/null 8080 /

** (process:4268): WARNING **: Specifying an export on the command line is deprecated.

** (process:4268): WARNING **: Please use a configuration file instead.

(These warnings are expected)

PC:

me@dev ~/GIT/k5ctng $ sudo nbd-client kt 8080 /dev/nbd0

Negotiation: ..size = 0MB
bs=1024, sz=8192 bytes

me@dev /dev $ sudo mount -a -o ro /dev/nbd0 /mnt/us

mount: /dev/nbd0: can't read superblock

(now kill all processes related)
[root@kindle /dev]#killer nbd-server
(you can use pidof and kill instead)

2nd test:

Kindle:

[root@kindle /dev]# nbd-server -C /dev/null 8080 /mnt/us

** (process:3918): WARNING **: Specifying an export on the command line is deprecated.

** (process:3918): WARNING **: Please use a configuration file instead.

PC:

me@dev /dev $ sudo nbd-client kt 8080 /dev/nbd0

Negotiation: ..size = 0MB
bs=1024, sz=0 bytes

me@dev /dev $ sudo mount -t vfat -o ro /dev/nbd0 /mnt/us

mount: /dev/nbd0: can't read superblock

so I obviously need to run more tests, do more reading as I am unsure of the expected output and the errors are quite unhelpful.

Can confirm there is no /dev/nbd0,1,2,3 in /dev on the touch... so it would probably be a custom kernel job to mount stuff with the client. but again I need to check that.

Have to read more about getting the swap space to run via nbd also. but essentially a nice quick set of tests that at least prove the arm bins run built via buildroot.

I used http://nbd.sourceforge.net/ http://www.thegeekstuff.com/2009/02/...mpstart-guide/ and http://www.microhowto.info/howto/exp...using_nbd.html as references.

Anyway, Hi-jack over. short answer: possibly.

: )