I stumbled across this nifty utility:

Android ScreenCast

It allows you to view and record your screen and explore your Android device on your computer. Rooted devices can also accept input controls (keyboard and mouse). The tool is java based so is cross platform.

Installation

The instructions on the link above are very simple and should be sufficient for a basic installation. Try that first. If you have any trouble, this guide will go into more detail and provide alternative methods of getting you up and running. Since my main OS is Windows, this guide will focus on the Windows based components of the SDK but very similar methods apply if you are running Linux or OSX.

- Download and install the latest Java Runtime Environment here
- Download the Android SDK here: here
- Run the SDK by launching SDK Setup.exe and install the latest version of “Android Platform Tools” via the updater.

If you are unable to download the components via the SDK interface (for example, if you are behind a proxy that requires authentication), then you can download the latest version via your browser using the following method.

 

Standalone SDK Component Download

You only need to do this if the updater in the SDK does not work.

View this XML file http://dl-ssl.google.com/android/repository/repository.xml containing the latest SDK file names. Locate the Android Platform Tools for your OS.

<sdk:archive os=”windows” arch=”any”>
<sdk:size>10075800</sdk:size>
<sdk:checksum type=”sha1″>ee7f70ed0c15286d6dbca85b57eb3d1950cc8ec4</sdk:checksum>
<sdk:url>platform-tools_r04-windows.zip</sdk:url>
</sdk:archive>

The archive file name is the information we are after; platform-tools_r04-windows.zip

The address to put in your browser is therefore

http://dl-ssl.google.com/android/repository/platform-tools_r04-windows.zip

The file should be downloaded, unpacked and the root folder placed in the platforms directory within the SDK to give a path similar to

android-sdk-windows\platforms\platform-tools_r04-windows

Connecting to your phone

Connect your phone by USB and make sure USB debugging is enabled.
Settings->Applications->Development->USB Debugging (Debug mode when USB is connected)

Check that it is detected as an ADB device. If you are unsure about this, you can check whether it is connected correctly using the command

adb devices

adb.exe can be found in the Platform Tools directory or the Tools directory of the SDK. If your phone is connected correctly, the command will return it’s specific ID will be displayed as a connected device.

In this case the device ID is 0123456789ABCDEF

You can now launch androidscreencast.jnlp which should successfully connect to your phone.

Running in Offline Mode

Since this is essentially a web based java application launcher, every time you run it, it connects to a webserver to download the appropriate (and latest) java runtime files. There are instances where this may be undesirable and this section explains how to run AndroidScreenCast in “Offline Mode”

Files required

androidscreencast.jnlp download
androidscreencast.jar download
ddmlib.jar download (note that this .jar file is different to the file of the same name found in the Platform Tools directory)

You must have the Android SDK and Platform Tools installed as described previously.

Place all three files in the same directory (in this guide I will use the directory C:\AndroidScreenCast)

Since all the application files are now local, the launcher (.jnlp file) needs to be edited to reference the local copies rather than the web based ones.

Codebase

<jnlp spec=”0.2 1.0″
codebase=”http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/” href=”androidscreencast.jnlp”>

<jnlp spec=”0.2 1.0″
codebase=”file://localhost/C:/AndroidScreenCast/” href=”androidscreencast.jnlp”>

Resources

<resources>
<j2se version=”1.5+” href=”http://java.sun.com/products/autodl/j2se”/>
<j2se version=”1.5+”/>
<jar href=”androidscreencast.jar” main=”true” download=”eager”/>
<jar href=”ddmlib.jar” main=”false” download=”eager”/>
</resources>

<resources>
<jar href=”androidscreencast.jar” main=”true” />
<jar href=”ddmlib.jar” main=”false” />
</resources>

Save the changes, ensure your device is connected and run the androidscreencast.jnlp

The application will now run without downloading the runtime files every time. The main disadvantage to doing this is that if there are any updates, you need to change the files manually. Otherwise, functionality is identical.

Any comments/questions/problems, post below

Have fun!

Note:

To stop the screen turning off when in use, enable the following

Settings->Applications->Development->Stay Awake (Screen will never sleep while charging)

To reduce the strain on the internal amplifier, an external, more powerful amp can be connected to the system, which in turn will provide much better sound quality. The speakers should also be changed when fitting an amp.

Generally speaking, audio can be divided into three frequency bands: highs (treble), mids, and lows (bass). To get the best sound reproduction, you need to have some form of output for all three ranges. The best way of doing this (imo) is by using a good set of components in the front of the car (handles mids and trebles), and a good quality sub in an enclosure of sorts (thats a different article altogether…) in the rear.

For those who aren’t familiar, component speakers come as a set containing a mid-range woofer and a tweeter to handle the mids and highs respectively. The set also contains a device known as a crossover which separates the incoming signal and routes it to the appropiate component. See image below – the mid woofers are mounted in the door, the tweeters up closer to head level to drag the sound stage upwards, and the crossovers are fixed inside the door itself:

Unless you really need or want speakers in the rear, my advice would be to avoid them (particularly 6x9s on a parcel shelf) as they will drag the sound-stage behind you (you dont go to a concert and stand with your back to the stage!). Additionally, having 6x9s and a sub in close proximity will undoubtedly cause some damage to the 6x9s and will have no worthwhile benefit.

Amplifiers:
You can get a variety of amplifiers for car audio purposes. The main differences are the number of channels and the output rating. In general, stick to good quality, well known makes. Cheap amps sound like garbage in comparison.

If we stick to the example above of using front components and a sub, there are two feasable options:

• Use a 4-channel amp. Use one channel per set of components in the front, and ‘bridge’ the remaining two for a higher output for the sub. This is the method I will go through.
• Use a 2-channel amp for the front components and a mono-block for the sub. This is the more powerful method but requires extra cabling and other considerations.

Cabling:
The amplifier is generally secured in the boot as it allows easy dissapation of heat (they can get quite warm) and is quite accesable. The problem is…it needs power from the battery…which unfortunately is in the front of the car…There are five items you need to deal with:

• Live cable from the battery positive terminal with an inline fuse to amplifier
• Earth cable from amplifier to unpainted section of car chassis
• Shielded RCA cables from headunit to amplifier. For sending audio signal from headunit to amp.
• Remote control cable. For allowing volume control, auto switch on/off etc from the headunit.
• Sheilded speaker cables from the amplifier to the front components and the sub.

The power cable you use is very important, more so in high power installations. If the cable you use is not capable of handling the current draw, it will melt and short on the car chassis potentially causing a fire. You can go through the calculations to determine the max current draw etc, but in general, choose the thickest cable you can. 4AWG is fine for most cases, but do your own research! You can buy amplifier wiring kits from many places and these are fine – just make sure you check the lengths and gauges.

Before beginning any electrical work, disconnect the negative terminal from the battery.

If you are lucky enough to have a pre drilled hole through the firewall then use that for routing the power cable into the car from the engine compartment. If not, you will have to do this youself (make sure you don’t drill into anything important!) and seal the hole using a rubber grommit or other method. When feeding the cable through, make sure the in-line fuse is at the end of the cable closest to the battery.

In the above image, the red cable is the power, and you can clearly see the fuse beside the battery. Ignore the other cables I have going through the hole…

Don’t connect the cable to the battery just yet.

You now need to route the cable down the side of the car – its fairly simple to prise away the trim and stick the cable underneath (see image below). Do this until the other end of the cable is in the boot. You may have to be inventive during this step – it depends on your cars design.

While you are at this stage, route the RCA and remote leads down the OTHER side of the car in the same way as you did with the power. Putting them down the opposite side will help eliminate inteference and alternator whine. Also, route the cable for your front speakers in the same manner.

You should now have a selection of cable ends in your boot: power, RCA x2, remote and speaker.

Before any of these are connected, secure the amp in place (I screwed mine into the rear of the back seat), and connect the GND terminal to an UNPAINTED point on the car chassis as close to the amp as possible. Remember, the ground cable should be the same gauge as the power cable.

Now you can connect the remaining cables to the appropiate tabs on the amp. The image below shows how I connected them up:

RCA’s in for channels 1,2,3 and 4.

From left to right:

• Channels 1 and 2 connected by the white cables to the front component speakers (double check you get the positive and negative the right way round)
• Channels 3 and 4 are ‘bridged’ and connected to the subwoofer. Again, check positive and negative.
• Thick red power cable (connect this last)
• Thin red remote lead connection
• Ground

There should be nothing left loose in the boot.

You can now connect the live end of the power cable to the battery positive terminal. It may be wise to use a distribution block for ease of use, but it is not essential.

Double check all connections and reconnect the negative terminal block to the battery. Test out the amp, make sure everything works correctly, and fine tune the settings using the crossovers, high pass and low pass filters etc on the amp to suit your music.

Final Words:
There are many different ways of connecting and configuring your system, this guide shows just one of them. Feel free to leave a comment here about anything contained in this guide, or if you have any specific questions or problems with your installation, post up in the forum and I can try to help.

Leonard.

Note that this is only intended to be a guide, and as such, I can’t be responsible for any problems you come across by following it. Use your common sense – if you aren’t sure, ask someone for advice or get someone who knows what they’re doing to help you or do it for you.