[Android Head-Units] Tuatara:
Hi! I missed your post, and I can't see that anyone else has answered you yet:

1). Those options were only available in a "language update" ROM which was released prior to 1.1.4, which (I believe) was based on 1.1.2. From the limited testing which was done by others in the thread, they didn't conclusively determine if those options were actually functional or merely cosmetic.

2). No. The android box is designed to be on when power is available or first applied. Therefore on reboot, the unit will always power up. As we know, there is a shutdown capability which happens after A 2 hour timeout, but I'm not (yet - i.e. I haven't looked!) certain where or how that functionality is called. This is VERY unlikely to be something within the Android box itself, as it only receives power from the Firewire cable, and therefore must receive a shutdown command from the MCU in order to effect a shutdown. Having the android box on USB power (or +12V supply), it will (obviously) never turn off. My bet is that this is controlled from the MCU (internal timer off a real-time clock in the STMicro arm chip, and comes in as a request on the serial port which is used for communications between the android box and the MCU.

3). I haven't had any time to keep playing with this (my android box is still on the bench and not in the car :() but from my hardware design understanding, ViPER should be available on the Android Audio, and Bluetooth Audio, but not on the Radio, or the Headset profile. If anyone has tested this, could they post their results?

REQUEST: If anyone can provide information about the "shutdown time options" available in the language update ROM, that would be great. If this feature is functional, I could add in that specific APK into the next 1.1.4 ROM I'm presently working on, which will correct the ViPER APK install location, and a few other minor issues I have found to date.

---------- Post added at 11:31 AM ---------- Previous post was at 11:26 AM ----------

Not yet. I'm also looking at the Logitech C270, since there have been a number of devices able to use this camera. I just need to go out and buy one ... soon.

---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------

Sorry to hear that it is not working. I'm using a Huawei E1552, and I'm having absolutely no issues with it. I don't know what to suggest, as my SIM card doesn't require a PIN to commence operations.

Ok ... I'll look into this and see if there is a way to force the playstore to use a different useragent.

Unfortunately, I don't know anything about this. Someone else or Google will need to be your friend. :)

Yes. The next update should not require a wipe, as the partition layout will be the same, and there should (functionally) be few changes. Since we have ClockworkMod though, this is no longer a real issue, but a nice to have.

---------- Post added at 11:42 AM ---------- Previous post was at 11:37 AM ----------

Android can only support a direct USB connection with a FTDI chipset as far as I know. For my OBD-style car communications I'm installing (yeah - it's even older than OBD) I had to ensure that the device version I purchased used a FTDI chipset, and everything worked out of the box. Check the unit on a Windows PC or Linux, and find out the chipset used for USB communications. That might help you find a driver you could use on android.

---------- Post added at 11:46 AM ---------- Previous post was at 11:42 AM ----------

AWESOME! Let me know when you've got something.

NOTE: Since I know you can do this/test this, can you flash the ClockworkMod recovery partition, and back up your current configuration - then upgrade the ROM, and see if the restore works for you?

P.S> What hardware are you having issues with? I might be able to help.

And the Lollipop theme was just a 'nod' to the people asking about getting Lollipop on the ROM.

Hey ... I can at least make it look a little bit like it's running on the headunit. :D