as promissed a while back..... here are the layout schematics for power, audio, and buttons. Please double check the schematics, it worked for me but it might not for you. Double check everything before you hook it up to the car (it is not going to be my fault if you brake something).
Here it goes:
and last the Button Layout
The next step is going to eliminate the Tone Control K100, the Carnetix Power Supply + Pololu PwS, and the ISL22511. Even though it was a good idea to use them at the begining (was a lot easier to get started) but now they are obsolete. The audio control is done via software in android 4.0 (don't need ISL22511 and K100 any more) and the Carnetix is just an overkill for the job. I am working on implementing the power circuitry from this SourceForge project. It has a battery option that would also put less stress on the car battery while the car is off and it would allow a setup with "instant on".
to answer your question regarding connecting external media. I had not played around with it, I either used the sdcard to play music or used streaming. So I tried to connect my ipod (an old shuffel) and after using adb to manually mount it I was able to play songs of it. Which means yes you can but it involves some manual intervention (using a terminal app or script it might work without adb, but I did not try that). I am also not able to go through the music player to play songs. Below is a screen capture on how I was able to play songs. I also attached a screenshot of the console output when the ipod gets pluged in. When I tried the same with an iPhone only the photos showed up, no access to the music folder since it does not show up as a storage device.
Hope that helped.
Right now I am playing around with ICS on my unit. It works quite good, managed to get it into tablet mode to make use of the onscreen buttons. It is not perfect though, the settings menu does not work in tablet mode. Hope to post a few more details about all that and my attempt to design my own pcb board for the hardware buttons and the power supply (want to remove the CarNetix). Volume up works through the hardware buttons, for some reason the volume down is not, even though the settings are in the kernel config file.
By the way, the chipsee pandaboard expansion board is now available with a capacitive multi-touch screen.
Last edited by nordman; 09-17-2012 at 03:31 AM.
i have been on a search far and wide for an actionable button press interface. i have gotten as far as being able to map the buttons as a keyboard in android, then set those buttons to the stock android media keys (vol up, down, play/pause, etc). what i have been unsuccessful so far in doing is being able to launch an app via a button press. there's a guy on xda that seemed to be successful in doing so via a shell script, but his post was a bit above my head.
needless to say, i'll be following your progress closely.
I have gotten my Pandaboard running JellyBean using Linaro. As of right now, everything seems to work except the following
1) The storage section in the settings crashes the settings
2) Google Talk doesnt run (Not really needed though)
3) Google Play wont allow me to install some apps like Google Maps. I think all I need is a build.prop change
I am not quite sure, are you using a usb keyboard module or are you talking about the chipsee expansion board? In the case with the expansion board the key layout is handled by the kernel (gpio). In my previous setup with Android 2.3 I had the volume control separate since it used 4 buttons. Now with ICS it is down to three and therefore leaves me with two unused buttons on the chipsee expansion board for volume up and down.
Regarding app launch via script, I have not done that but if you need a hand let me know.
nice to hear that JB runs on the Pandaboard.
"..... 3) Google Play wont allow me to install some apps like Google Maps. I think all I need is a build.prop change ...."
I changed the lcd_density in build.prop to get my setup in tablet mode. However, that still did not allow me to install apps from Google Play. The device restrictions are within the Google Play app.
I highly doubt the restriction is in the play store itself. Usually you just need to modify build.prop to spoof the correct things. I tried doing that (used a nexus build.prop) and it put the pandaboard into boot loop. I probably changed too many things in it.
Do you have any advice on going from a 3.5mm to a front, rear, sub RCA connections?
Last edited by dcplaya; 09-14-2012 at 11:02 AM.
thanks for your reply nordman.