HSG X5A and ADB Drivers

Similar to the previous posts about the Desire Z and Android devices in general, the lines you need to follow the following procedure to get a HSG X5A (which  is actually a decent device which can playback full HD with no problems):

1. Make sure you have updated the SDK and the USB driver to the latest version.
2. Open the android_winusb.inf file (located under the android-sdk-windows\usb_driver directory) using a text editor. I personally prefer Notepad++.
3. Add the following lines under the [Google.NTx86] and [Google.NTamd64] sections:

;
;HSG X5A
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_DEED&MI_01
;

4. Save the file
5. Try to install the driver again.

This might work with other HSG tablets (or their rebrands).

HTC Desire Z (AKA HTC Vision AKA T-Mobile G2) and ADB drivers

I just got myself a Desire Z and once again the ADB drivers fail to install in windows.

It is the same problem described and solved in this post.

To fix:
1. Make sure you have updated the SDK and the USB driver to the latest version.
2. Open the android_winusb.inf file (located under the android-sdk-windows\usb_driver directory) using a text editor. I personally prefer Notepad++.
3. Add the following lines under the [Google.NTx86] and [Google.NTamd64] sections:

 ;Desire Z  
 %SingleAdbInterface%    = USB_Install, USB\VID_0BB4&PID_0C91  
 %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01  
 ;  

4. Save the file
5. Try to install the driver again.

If it still fails to load, follow the instructions from this post to find the correct VID and PID of your phone.

AxVLCPlugin2, Visual Basic 2008 and Windows 7 64bit - clr20r3 and REGDB_E_CLASSNOTREG

I've been writing an application to monitor multiple streams in VB 2008 and I started using the AxVLCPlugin2 which comes with VLC.

It is a nice plugin and apart from a few problems (it will not go fullsceen in version 1.1.4 for example) works fine for any stream that VLC supports.

I do most of my work on a 32bit XP box at work, but sometimes I like to work on projects at home using my 64bit Win7 PC.

For most projects this works fine, but on this one every time I started the application it would crash telling me that an error with an "EvenType: clr20r3" has occurred. It also gives a lot of information about the crash but nothing useful to point to the source of the error.

Assuming that the problem was that the application could not find VLC or that the AxVLCPlugin2 was not recognised, I fired up Visual Studio, cleaned up the project and tried to recompile - at which point VS proclaimed that "Class not registered (Exception from HRESULT:0x80040154 (REGDB_E_CLASSNOTREG))".

No matter how many times I removed the reference an added it again, the error remained the same.

The solution was quite simple though.

Go to the "Project properties -> Compile" and set the platform to "x86" instead of "Any CPU". This allowed the application to successfully compile and run on the 64bit Win7 pc, without breaking it for the 32bit.

If "x86" does not appear in the combobox, open the configuration manager (Build -> Configuration Manager).

In the Configuration Manager dialogue, select "New" from the "Active Solution Platform" combobox.

In the new dialogue, select "x86" and "Copy Setting from Any CPU" and leave the checkbox ticked.

Keep in mind that this will create a new directory under the "<project>/bin/" folder of your project called "x86" which will contain new debug and release subdirectories. So make sure that if you have any shortcuts to your executables pointing to the old "<project>/bin/release" or "<project>/bin/debug" folders they are updated accordingly.

ADB driver installation fails after ROM update or change

Sometimes, after changing the ROM in an Android device, ADB will not detect the phone when you plug it in.
This can happen because:

1. The rom is a different OS version and there an updated driver version exists, so you will need to update your SDK.
2. The update changed your device's PID (Product ID) and/or VID (Vendor ID). These two values are used in USB devices to identify them and to select the correct drivers for them.

In the second case, you can modify the inf file which comes with the Android drivers to associate it with the new VID/PID.