[Android Head-Units] donaldta:
This is the best way to address the issues below, yet also being the most involved. It would take the most effort and involve someone whom is comfortable at building ROM images and knows how to replace the bootloader.

I think this would take the second most highest effort. It would be easier if we had the actual java source code instead of trying to hack the decompiled dalvik executable through the smali files. If I get a big chunk of free time again, I might try to go over the code again but I'm not fluent in reading smali and the way the java classes get decompiled takes quite a bit of effort interpret.

This is probably the easiest and can probably be addressed for most programs by creating a symlink ("ln -s {/path/to/media/directory/on/sdcard} {/mnt/sdcard/symlink}"} or using the mount command to mount the physical sdcard onto an empty directory of the internal virtual one.

If you provide the output to "mount > /mnt/usb/mmcblk1p1/mount.txt", "ls -l > /mnt/usb/mmcblk1p1/lsr.txt", "ls -l /mnt/sdcard > /mnt/usb/mmcblk1p1/lsi.txt" and "ls -l /mnt/usb/mmcblk1p1 > /mnt/usb/mmcblk1p1/lsm.txt" then I can figure out a few ways to makeshift it.

I think this really should be the lowest priority. Especially, since the USB to ODB2 adapters are much cheaper, provide the best throughput, and use 0 watts when the head unit is powered off. (well, maybe not in omarko's case).

The Bluetooth module seems to exists on a low level board which appears to facilitate the actual pairing and communication. Sure there is an interface within the phone app, but this seems to be an Android facade that relays the directives to the low level board. We do know from [MENTION=5302494]Defender666[/MENTION] in Post #115 that the optional "Landu" ODB2 BT adapter provided from the seller will pair as an ODB in the phone app then can be read using the respective B-scan software. So, I suspect that the B-scan software has a special way of communicating with the BT module or maybe nobody has tried a different ODB adapter using the phone app.

I guess the question is whether the "Landu" adapter can work with other Android ODB2 software, like Torque Lite, Torque Pro or Dash Command on the AN 21-U? Or even if the other third-party ODB Adapters can pair as ODB in the phone app?

In addition to Market Helper, you can use AppBrain to find apps from the Android Market (Google Play) which are still hidden while spoofed. The issue with Google Play is that they place many filters and methods of disallowing certain software to be installed.

For example, Cobra iRadar even though it is a free app does not show in Google Play for unregistered devices. Even if you use Market Helper to spoof certain devices, it still might not show up. However, using both Market Helper and AppBrain in tandem will allow you find and install it from the Android Market.

But, downloading it from a sanctioned Android device and then copying it over to the AN 21-U is also another method.

I'm not sure why this is a problem? Which software keyboard are you using? Regardless if you have a physical USB keyboard connected or not, the soft keyboard should appear when you touch an text field which requires input. Although some software keyboards interact differently when having a hardware keyboard connected. Personally, I favor Hacker's Keyboard because of this and it also has the the available buttons of a standard PC keyboard.

---------- Post added at 01:29 PM ---------- Previous post was at 01:04 PM ----------

By your previous feedback, I personally believe that you have a malfunctioning unit. There's probably a short on the logic board which is causing the device to continuously drain more electricity than it needs.