Friday, July 1, 2011

iOS 3x speed increase for my instrument cluster app

But first another reason the crippled iOS is only magical in the sense it is something that makes me want to burn it at the stake.

I go running.  I send articles to my kindle and it reads them to me.  Easy - but it doesn't read the web page, so the upload is an extra step.

The iPodTouch has voicover, so I should just be able to use that.  No.  First it takes some setup.  A triple press  of the one button (I'm surprised they don't have a shift, option, control, and apple key) can bring it up.  OK, it is now almost impossible to navigate, but I can select a paragraph and two fingers down will start speaking.  Until I tilt it - then it speaks "landscape", and stops.  Then maybe "Portrait".  There is an orientation lock buried in the multiask menu.

Ok, so I've found a long article, press play, put it in my fanny pack... and after about 50 feet it starts back at the top.  I didn't do anything, I didn't touch the screen, but maybe "shake" does something.  Why can't I have a "just push play" that would read audio.  In the background.


Well, that is why this is an HTML5 webapp, not a native one.

But even that they can't do right.

The critical change was to rewrite the URL links to be the IP address.  I originally used the mDNS names, e.g. charley.local (for chumby-harley), so the motorcycle instrument cluster would be http://charley.local:2947/hogstat.html, the link itself being "hogstat.html".  I only got 2-3 updates per second.   I  modified webgpsd to prepend the IP address, so it would be "http://192.168.1.5:2947/hogstat.html".   I am getting 8-12 or maybe more updates per second!

Ordinary DNS seems a bit slower but does appear to be cached.  But why not mDNS?  It isn't as if the IP is likely to change in a fraction of a second.  Even a 30 second cache would help.

1 comments:

  1. just linked this article on my facebook account. it’s a very interesting article for all.


    Instrument Cluster

    ReplyDelete

Blog Archive