galaxy

I am just starting to learn on Android development. I use Ubuntu 11.10 and Eclipse. I have installed the needed plugins from android development, and I have also write yet some examples that compiles and run fine on the emulator. But somethings as multitouch cannot be tested on the emulator, so I want to test them on my real Samsung Galaxy S2 device. The problem is that I have tried everything I have found on the web on this, but still have not been able to use it. When I run ./adb devices, it does show none, although the device IS attached. $ lsusb ... Bus 001 Device 012: ID 04e8:6860 Samsung

I am porting my iPhone app over to android and the client uses Samsung Galaxy Note III . I need to create an emulator to help with the debugging, but I am getting problems in starting the emulator with the settings I got from gsmarena . There are similar posts but they are of Samsung Galaxy Note II and also used old AVD. What should be selected in AVD ( Device and Target )? I also did some changes and my final settings came up to be: Emulator AVD- Device: 1080 x 1920:xhdpi Target: Google API's(Google Inc.) - API Level 17 RAM: 256 VM Heap: 48 Internal Storage: 1 GB SD Card Size: 1024 MB With

I'm developing an Android Widget and need to differentiate between Galaxy S and Galaxy S2 . I almost read everything about Screen sizes and densities articles. And I need, of course, to use the new qualifiers with the new qualifier Smallest Width . My problem is, that the sw320dp qualifier match for Galaxy S and also for Galaxy S2. But I need another layout for Galaxy S2, but cant find the right qualifier for it. Definition of Galaxy S, Density 233 Screen Size in Pixels: 480 Pixel x 800 Pixel Screen Size in dp: 329dp x 549dp (cause 1dp = 1pixel/(density/160) -> so the qualifier sw320dp must

Samsung Galaxy S4 have the " Floating Touch " functionality, in which the finger can be detected even if the screen is not touched. I would like to fire an event on a button ( btn1 ) when the finger is passing hover it. I tried using the OnHoverListener , but onHover never get called when the MotionEvent is MotionEvent.ACTION_HOVER_ENTER or MotionEvent.ACTION_HOVER_EXIT or MotionEvent.ACTION_HOVER_MOVE , which are the event that I need. This is my code: btn1.setOnHoverListener(new OnHoverListener() { @Override public boolean onHover(View v, MotionEvent event) { Log.d("FloatingTouch", "onHover:

How to open the Android ServiceMode menu programmatically on Samsung Phones ? Manually, I can do it by dialing the ussd code *#0011#. This was a challenge and I've been a few hours looking for a solution. But i am afraid i don't have good news. 1. First attemp, Intent.ACTION_DIAL Is true that in the beginning, it was possible to directly call USSD codes from an app (using the intent Intent.ACTION_DIAL), and even from a website, just using the "tel:" schema. That opens the dialer, an puts the desired number. As when you put the last #, the code get send automatically, it was almost transparent

i need to have the menu button shown for some activities on galaxy nexus . i can't find how to do that, since it hides it by default . i don't wish to create an action bar since it takes more space that i want to use to other things . when setting the "android:targetSdkVersion" value to lower than 14 , it seems to show the menu button , but otherwise, it hides it . btw, the activity needs to be full screen , with no title/action bars . it is very weird that this button is not shown by default for so many places (even the launcher) , and on some places it does exist . such a button is a very

Which Android (with Jelly Bean, 4.2) devices support Bluetooth low energy (BLE)? Does Samsung Galaxy S III support it? (This question came up after reading the blog post Bluetooth 4.0 on Galaxy S3 .) I believe that currently only the Motorola RAZR has BLE support (because Motorola provides their own BLE library to developers). The S3 does not support BLE (drivers / API not available). This letter from the COOKOO watch project describes Android's Bluetooth 4.0 disaster well. Additionally, this issue has become the unofficial venting / complaining forum for developers. There are occasionally