(PL2303 USB/TTL + 3 pin socket TE Connectivity / AMP 172201-1) questions/11183792/android- usb-host-and-hidden-devices One must have root access to able to remount and modify those files. Some devices can be fixed, a solution is to modify/copy a file in the /system/etc/permissions.
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. Obviously there's nothing that could be done to enable USB host mode on those devicesī) 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.
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).īasically, the non-functioning devices can be divided into two groups:Ī) Hardware USB host mode not implemented.Ī 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. Here is the result, torque & power as seen the the wheels (two runs, effect of min/max settings of the "unknown tunable", drivetrain losses not included) : There is no easy way to measure the effective ignition angle (map +/- offset), but knowing the vehicle weight, gear ratios (3rd gear, IRD, main diff.), cx + frontal area, rpm_over_time, we can create a rough estimation of engine torque/power delivered to the wheels. Apparently, there have been rumors a similar option is available with rover testbook. It could be a kind of ignition retard offset for markets with poor fuel quality (to avoid knocking). Try min/max values to see if there is any effect. The throttle response seems to be better. Somehow related to ignition advance offset or a kind of acceleration enrichment, if the value is DECREASED Perhaps with some other variants it might have a different effect.ĭ) Unknown (ignition advance offset ? / acceleration (pump) enrichment) ? - This is currently unknown, seems to be Idle fueling trim 2 - in case of MEMS 1.9 it's identical to "b". Set it a little bit on the rich side (FuelTrim <100 in the live data section) One should increment or decrement so that theįuelTrim value in the "live section" equals 100 (meaning no additionalįeedback is needed from the lambda sensor).
Idle fueling trim 1 - sets the base idle fueling trim, seems to be an offsetįrom the main idle map. Granularity seems to be 25 rpm ( +1 raw = +25 rpm). So far it has been only attempted against a MEMS 1.9 system, but in general both 1.6 and 1.9 ECUs are very similar.Ī) Idle target rpm - sets the desired idle engine speed (warm engine, but should also influence cold/fast-idle). The effect shouldīe seen in the mini "Live data" section below the inc/dec buttons.
Must be first established on the main connection tab). The drop-down list and then uses the increment or decrement button toĬhange the value of currently selected item (of course the connection "tuneview" tab should be self-explanatory, one selects the tunable from