[Solved] Subaru Bluetooth Not Automatically Connecting To Phone

I have a 2014 Subaru Forester.
Previously, I was using an iPhone 4S on iOS 7 and every time I started the car, the phone would automatically connect to Bluetooth. Worked great.

I switched to an iPhone 5S on iOS 8 and that stopped working.

I tried deleting and re-pairing through the radio about a dozen times. Still didn’t work.

Finally, I remembered the audio pairing option available through the steering wheel control. Turns out, I think I had maxed out the number of connected devices there. Apparently, the radio and audio settings don’t interact with each other.

I talked through the BT setup options, deleted all the devices I had installed there and re-paired my iPhone.

Problem solved!

Nexus One Car Dock [Mini Review]

The Nexus One Car Dock is well constructed and sturdy. It communicates with your phone via Bluetooth.

It works ok, but there is one show-stopper in my book. NO LINE LEVEL AUDIO OUT port. If you want to connect it to your car stereo and listen to audio, you have two options:

  1. Bluetooth (which most cars don’t have yet… plus wouldn’t be able to pair with a headset for calls)
  2. The headphone jack (1/8″ Mini) on top of phone.

That means, when you get in your vehicle, you must cradle the phone then plug in your cable to the top of the phone, adjust the volume up (since it’s not line level). To get out of car, unplug the headphone cable, and uncradle the phone. I know, I know… this is not a “problem” experienced in developing countries. But COME ON Google… for $55 I should be able to drop the phone in the cradle, turn on my car stereo and drive.

Worth noting; when charging, the phone gets pretty warm. Not so hot you can’t hold it, but much warmer than my iPhone ever got.

More to come… these are just my initial thoughts.

Nexus One Desktop Dock [Mini Review]

The desktop dock is sturdy and attractive. Comes with an extra power cord (so you can use the one from the phone elsewhere) and an audio out cable (1/8 -> RCA).

When you cradle the Nexus One, it launches the “clock” app which shows time, date, weather, next alarm (if set) battery charge level and a row of icons at the bottom for Alarms, Gallery, Music and Home. After about 10 minutes, the screen goes black and the time, date and next alarm are shown in dull green (suitable for beside the bed).

Charge time from a completely drained battery takes about three hours when plugged into the wall.

My only complaint with the desktop cradle is the bottom lip that holds the phone from sliding out. It should be 1-2 millimeters taller. Sometimes if you press the screen near the top (like pulling down the info pane), it causes the phone to “pop” out of the cradle onto the desk.

Nexus One (Android) Gripes

Email Icons Don’t Show Unread Email Count
Unlike the iPhone, my Nexus One does not show the number of unread messages on the mailbox icon.

Screen Sensor Misalignment
About once a week, I have to restart my Nexus One because the screen sensor is misaligned. (Pressing an “R” yields a “D”, for example.)

Battery Life Sucks
The screen (which is very nice) sucks a ton of battery juice. With moderate use, I have to charge it twice a day.

Battery Gets Pretty Warm
When charging, the batter gets pretty warm. Not a huge deal, but I never experienced that with my iPhone.

No Hard Switch for Silent (on the N1)
Without a physical switch for “silent” (like the iPhone) you must set each app to “mute.” Example… say you’re bored silly during a presentation and whip out your phone to play a quick game. The ringer is set to mute, the media volume is set to mute, but the game you launch ignores all that… it happily starts singing all its startup sounds. BUSTED.

Elgato Turbo.264 HD – My Thoughts

I recently had the opportunity to try out the Elgato Turbo.264 HD encoder/accelerator.

The device does what it claims… it transcodes most any type of video file and produces an H.264 file formatted for your device (iPhone, iPod, AppleTV, BeyondTV, etc.). The processing time is (more or less) equal to the length of the video. e.g. A 60 minute video takes around 60 minutes to transcode.

My only complaint is that it uses 100% of my machine’s CPU while processing. I recall seeing a blurb about this somewhere in the documentation, but I thought it said it used “some” of the CPU. On my Macbook Pro 2.16Ghz, it spiked out the entire time. Obviously, that causes the internal fan to kick into overdrive, generating a good bit of noise.

The older non-HD version did NOT use the host CPU, so the transcode time was longer. But on a laptop I would gladly sacrifice the longer time in lieu of the fan noise. On a desktop, it would be a non-issue for me. A perfect solution would be to have a setting in the software that allowed you to choose how much of the CPU was used.

Some folks in various forums have complained about (and demonstrated) very dark videos from the device, but none of my tests were dark.

Overall, it’s a neat gadget. My only complaint is the CPU issue.

Install CentOS on ESXi from Netinstall ISO

It is SO easy to create a new virtual server from a Netinstall ISO. Downloading the DVD or CD ISOs can take a long time. Netinstall only pulls down the packages you need.

Step one, download the Netinstall ISO from the vendor. I prefer CentOS. (version 5 is only

Upload it to the datastore

Create new Virtual Machine

Choose custom

Name it

Pick your destination datastore

Pick the guest OS ( I use RHEL 5, 32bit)

# Procs, Ram, NICs, LSI Logic SCSI Adapter, HD size, etc.

Finish it out with the defaults.

Right click on the new VM and Edit Settings

Select the CD Drive, check “Connect at power on” change to Datastore ISO file and browse to the Netinstall ISO.

Click on options tab, select boot Options

Check the “Force BIOS Setup”

Click OK, boot the VM and go to console. BIOS will be waiting on you.

Go over to Boot option in Bios and move the CD-ROM Drive to the top of the list.

Exit, save.

CentOS installer will start.

On “Installation Method” screen, choose HTTP.

Web site name: mirror.centos.org
CentOS directory: /centos-5/5.3/os/i386/

Obviously, your version may be different.

It will start a download of “images/stage2.img” (it may take a while depending on your connection speed…typically around 5 mins on a DSL/Cable Modem).

From there, the process is like any other install.

Create Multipart Zip Files In Linux

Need to transfer a really large file but are worried that it will fail before completing?

Create a multi-part file using the split command, then join it on the remote server after it transfers. Example: Start with a zipped file (somefile.zip), then run…

split -b 10m somefile.zip someprefix-

That will take somefile.zip, chop it into 10MB pieces and name them “someprefix-aa, someprefix-ab, etc.” Run “man split” for all the options:

split -b number[ k|m ] [-a suffixlength] [filename [prefix] ]

If your file will be split into more than 52 pieces, you’ll need to change the number of suffix length. The default is 2 (a-z, twice).

After transferring the pieces to the remote server, re-assemble them with cat…

cat someprefix-aa someprefix-ab ... > somefile.zip

ESXi & MD3000i: No LUNs after adding VMkernel switch for iSCSI

Having problems getting iSCSI LUNs to appear in ESXi after enabling a second VMkernel switch on a separate subnet? Make sure you disable/re-enable the ESXi iSCSI Initiator AFTER adding the new vSwitch on the isolated network. I think iSCSI discovery only occurs on the Vswitches enabled at the time the initiator is enabled. Here is my scenario:

I recently setup an MD3000i SAN to connect to our VMware ESXi hosts via iSCSI on our internal LAN. My test server only has two NICs, but I only enabled eth0 with an IP of and left eth1 unused. I enabled iSCSI on the host, set send targets, config’d host access, created host-to-virt disk map, etc. and rescanned HBA. The test worked fine. After scan completed, I was able to see the LUNs in ESXi.

Next, I wanted to enable eth1 and move the iSCSI traffic off to dedicated, isolated, switches.

So I physically moved the MD iSCSI cables to 2 standalone switches, edited the MD Host Ports, setting them back to the defaults (192.168.130.x & 131.x). I left the two MD management ports in the LAN.

I enabled ESXi eth1 as VMkernel and set to IP in same range as one of the segments (

On ESXi, I removed the old send targets and entered the new IPs ( & 102).

Rebooted everything for good measure. Rescanned HBA, but the LUNS did NOT show up in ESXi.

The solution? After enabling the VMKernel switch on the different subnet, disable ESXi iSCSI Initiator and reboot (maybe not needed, but I find ESXi likes a reboot for many things). When it returns (5+ minutes for mine), ENABLE the ESXi iSCSI Initiator and rescan HBA. I think iSCSI discovery only occurs on the Vswitches enabled at the time the initiator is enabled.