dan5jr

Hmm, voice input... That's a really good idea, would be really nice if I could somehow make that work, but it doesn't seem possible since I really want to keep the phone I'm using for input hidden somewhere. That's really the last thing I'm trying to figure out is some way to control it - a simple joystick type input is all I need to switch through a couple apps. Probably just Torque and Music, can't really think of anything else too useful that I can use while driving.

I have a Nexus 7 and I really like it so when I first saw this install I really wanted to do it. But then the more I thought about it, the more I started to feel like the amount of extra work needed really wasn't worth it. Given all the possibilities for the OEM Nav input, I only really see two advantages - 1) obviously the much better looking/higher resolution screen and 2) native android touchscreen interface. But besides better navigation, anything else that android offers (video, music, games, apps, etc.) are things that you wouldn't (or at least definitely shouldn't) use while driving, so then why not just use the tab normally if you're stopped somewhere in your car and want to do something like that? Plus that way you're ~$200 tab isn't confined in your car and you can use it normally. Anyway, just my thoughts on that... I recently decided that I wanted to do a rearview cam install and after readying a lot of these threads I figured that I might as well run another video out cable while I have everything apart so I could easily add some type of carputer. After looking at all the options, I'm planning to use a friend's old Droid X which is fortunate enough to be one of the few phones made around then to have native hdmi out to connect to the navi screen. Since I only really want it for the app Torque, I'm planning to just mount it somewhere in my glovebox, hardwire the power, and then use tasker and have it turn on bluetooth/GPS, duplicate the screen, and then launch straight in to the torque dashboard (I think that's what they called it). Once it loses power I'll have it turn everything back off to save battery. I think if I run a lean ROM with a conservative kernel and strip out all the apps, including system, besides the few I need and charging it every time I'm driving should keep the battery from dying completely. Down the road I may look at adding some type of remote control so I can use it for music as well - I don't think it would be too much more work to run audio to the aux-in. Does anyone know if it's possible to have multiple Bluetooth devices connected at once (for a remote)? Since the USB port is already dedicated to power, I think bluetooth is really the only other option.