Apologies - I've now set up e-mail alerts. Sorry.
Mine is a MEMS 1.6 with a 3-pin connector so I used the instructions at
http://alum.wpi.edu/~colinb/mems_interface.html. I expect you have the later connector.
If yours is a 3-pin, I'll send you photos, otherwise Pawel, the developer of the app, is very good at replying to questions. Perhaps your Android device can't cope (see below)?
And yes, advancing the ignition to the 116 increments did improve drivability, all the more so when compared with the car retarded to 140! And there are graphs on Pawel's website showing torque and power curves for those 2 settings
http://memsdiag.blogspot.co.uk/ That timing tunable advances the timing map when the manifold absolute pressure (load) gets to around 65 kPa.
From the MEMSDiag site - some devices don't work:
"It has been reported recently that some devices doesn't support USB API correctly, despite having Android version > 3.1 (the first release with USB OTG host mode API available to application layer).
Basically, the non-functioning devices can be divided into two groups:
a) Hardware USB host mode not implemented.
A good example is LG Swift G (or related) mobile handheld, a rumour says that +5V DC supply voltage is not available, a result of hardware cost-cutting. Obviously there's nothing that could be done to enable USB host mode on those devices
b) Hardware USB compatible with host mode, Android version >=3.1, pendrive or mouse works fine, yet no USB devices are visible form the application layer.
This mostly is true when it comes to no-name devices (tablets), it looks as if manufacturers were in a big rush to release a product and forgot to properly configure Android OS.
Some devices can be fixed, a solution is to modify/copy a file in the /system/etc/permissions.
One must have root access to able to remount and modify those files.
See the thread:
http://stackoverflow.com/questions/11183792/android-usb-host-and-hidden-devices
Quotation from the above link:............"