How can I get ADB to properly recognize an Alcatel One Touch 995 device on Windows/Ubuntu? The problem

I am trying to deploy a custom application to an Alcatel One Touch 995 running Android 2.3.6. I using Eclipse to compile the source code and push it onto the phone. The Android Device Chooser within Eclipse starts up and lists a device however it does not recognize the maker or model. The device shows up as question marks for the serial number (see screenshot).



I am able to install the application to a Samsung device. I tried the procedure on Windows 7 running Eclipse 3.7.2 and on Ubuntu 12.04. running Eclipse 4.2. The Android Development Kit is up-to-date on both systems.

I enabled "Unknown sources" and "USB debugging" in the application settings.



The USB driver attempt

I found a USB driver from Alcatel. The archive contains driver for different Windows versions. When I try to update the "Android USB Device" in the Windows device manager I am informed that the driver version is up-to-date. Here is a screenshot of the "ALCATEL Dream Composite ADB Interface" properties.



It seems as if this attempt was not helpful. I leave it anyways in case someone stumbles into the same situation.



The solutions

Windows:

Strange! I installed almost all available API Versions in the Android SDK Manager and now also selected the images for ARM, Intel and MIPS. The result is that the device is recognized on Windows.



I tried hard to undo the driver installation on Windows. To me, the most obvious is removing the "Google USB Driver". So I did and restarted Eclipse and the computer but still Windows remembers the maker and model. I further tried to remove other items without success. I will leave my experiments in this question for others to figure out the key installation module needed on Windows to recognize the device. I guess its "Google USB Driver" and the .inf file has been copy to the Windows system folder in the background.

Ubuntu:

Regarding Ubuntu, I like to grant the answer Flow (please put your comment as an answer). I configured a device rule as it has been explained by vsm and others. There is also an official guide entitled: Setting up a Device for Development.



Speculations

It could be that when I tried to update the Windows driver with the USB driver from Alcatel that it actually updated my system without telling me. All I received was the message "Driver version is up-to-date". I missed to check the version before I started. If anyone can verify this theory on a "clean" system I happy to hearing from you.
If that happens on Linux the reason is usually that the adb daemon is unable to write to the USB device in /dev. For more information see this answer on stackoverflow.