Posts tagged “mswl-ad

Using Hardware Devices while developing and Android Application

Many developers are using the emulator provided by Android SDK in order to test the application that they develop. There is although an other part of developers who wants to run the application in their device (android,tablet etc). So what happens in this case?The solution to the problem is very simple. By having a look on android developers documentation [1]  we can follow the steps given and emulate the application we develop in the device we wish.

“3) Set up your system to detect your device.

  • If you’re developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
  • If you’re developing on Mac OS X, it just works. Skip this step.
  • If you’re developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:
    1. Log in as root and create this file: /etc/udev/rules.d/51-android.rules.Use this format to add each vendor to the file:
      SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"

      In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.

      Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules.

    2. Now execute:
      chmod a+r /etc/udev/rules.d/51-android.rules

It is very important to find the Vendor ID of your device . In order to do that just have a look at the following part . This part provides a table with companies and vendor id’s

USB Vendor IDs

This table provides a reference to the vendor IDs needed in order to add USB device support on Linux. The USB Vendor ID is the value given to the ATTR{idVendor} property in the rules file, as described above.”


Company USB Vendor ID
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Fujitsu 04c5
Fujitsu Toshiba 04c5
Garmin-Asus 091e
Google 18d1
Haier 201E
Hisense 109b
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenovo 17ef
LG 1004
Motorola 22b8
MTK 0e8d
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10a9
Pegatron 1d4d
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony 054c
Sony Ericsson 0fce
Teleepoch 2340
Toshiba 0930
ZTE 19d2


Plug in your device, configure it and then  enjoy your application!!

Reference :


Goolge Summer of Code 2012 – Ambassador/Event plugin for openSUSE Connect – Event#1

Introduce my self

My name is Athanasios-Ilias Rousinopoulos. I am an openSUSE Ambassador and an active member of openSUSE Community. This year i participate in Google Summer of Code with openSUSE .[0]. My project is called “Ambassador/Event plugin for openSUSE Connect”.

Introduce my project

As an openSUSE  Ambassador  [1] i participate in conferences , make presentations and promote openSUSE to the people. openSUSE Connect is the social network of openSUSE Project (based on Elgg ). In my opinion openSUSE Connect  it is more than a useful tool. Ambassadors , members of openSUSE community do use it in order to communicate , form groups , follow other people, create events ,create polls  etc. Although it is a useful tool , it does suffer from some deficiencies. As an ambassador i found using the wiki in order to manage the community events not a good idea at all. As mentioned before openSUSE Connect is based on Elgg. Elgg is an  open source social networking engine that provides a robust framework on which to build all kinds of social environments. [2]. Elgg provides well-organized documentation [3] for developers. Furthermore Bug tracker is also available [4] . Besides Elgg has its own API Reference [5] which developers can use it. Finally he goal of my project is to create a plugin (developed in Elgg) which allows the users planning of events in openSUSE Connect , instead of using the wiki pages so as to create an event. Using this plugin by the community can be more beneficial


Event #1 (23/04-07/05) [Community Bonding period begins]

What did i do

Until  now i did made my “Contact first steps” [6] which means i talked with my mentor , informed him about my plan. Furthermore i started using Trello as a project management tool. Focusing more on the project i read openSUSE connect’s main features and Installed it as well [7] , [8] , [9]. openSUSE Connect allows create and develop new widgets , plugins and new themes by using the Elgg platform. During installing openSUSE Connect i did face some problems , so i edited the documentation [10] in order to make the installation process easier and more successful. After the installation process i read Elgg’s Wiki Main page [11] , how Elgg’s Engine works , and made my firsts steps with  Elgg Plugin Development. [12] ,[13], [14]. Elgg’s offers some introduction tutorials so as to begin developing your plugin. In addition Elgg offers about 1500 plugins which you can download them and  install them as well. Finally i installed PHP plugin for Eclipse and started using it.

What i am going to do

This week i will focus more on Elgg’s Plugin Development and try to implement the first tutorials [15] . Furthermore i am going to focus on Elgg Plugin Development and read upon the current used event plugin.

Problems &  Solutions

After the installation process i wasn’t able to access Elgg due to an Error message. Also while configuring “System settings” i had to add a folder which is not placed in Connect’s installation folder. These problems are already solved and descibed more detailed here [16]


These are my first 14 days in the project. I feel very happy about participating in Google Summer of Code with openSUSE Project. In my opinion this project would be beneficial for members of openSUSE Community and Open Source community as well. Finally my reports about my progress will be posted in weekly basis and will be called “Event # “.

How-to Install Eclipse 3.7 (Indigo SR1) in openSUSE 12.1 (GNOME 3) only within 9 Steps

This is my  blog post for  “How-to Install Eclipse 3.7 (Indigo SR1) in openSUSE 12.1 (GNOME 3) only within 9 Steps ”

In my case i installed Eclipse 3.7 (Indigo SR1) due to i have to use the Eclipse Marketplace. Eclipse Marketplace offers a thousand of plug-ins and extra features available for Eclipse platform. It is a truth that i searched a lot in order to find a package or a “one-click install” file  but the result was an installation of  3.6.2 version. As we all know in FLOSS always there is a way to overcome problems and also fix them. Furthermore as a developer  i have to use the “Eclipse IDE for Java EE Developers“.  Here are the instructions on how-to install (via terminal) this edition of Eclipse. (Some images are in greek language , due to the fact that i use the greek language as System language)

1st Step : You have to dowload the version you wish to install from Eclipse Official Website. In our case we choose Linux 32-bit.

2st Step : We download the .tar.gz file and  i suggest  saving it at  /home/your-user-name/Downloads.

3st Step : We open the terminal and then type

cd ~/Downloads/

tar -xvf eclipse-jee-indigo-SR1-linux-gtk.tar.gz

In order to un-compress the file which have been downloaded.

4st Step : We search the “Alacarte

5st Step : We click on  it , so as to open the application.

6th Step :  After the 5st Step we click at right so as to add a new ” Application launcher” .

7th Step : We fill the fields and add the Eclipse image (we have to search in ~/Downloads/eclipse/icon.xpm by using the “Browse” button).  Here is shown the “result of this process .

8th Step : Then we click on “Activities -> Applications” , and we see the  “Eclipse” so as to access it.

9th Step : Just enjoy  Eclipse!

This How-to is formed by 9 steps , 1 less than the KDE’s how to :).