nexus-s

I hadn't seen this issue until after the 2.3.4 update for the Nexus S phone. I have a very simple application, with a main activity that loads on start of the application. This main activity has a LinearLayout consisting of some TextViews, and EditText, a couple Spinners, and a Button. I am now having an issue with the input to the EditText. It is supposed to come up with a soft keyboard with the phone input type. Instead it comes up with the standard alpha-numeric soft keyboard and once you start typing input, it passes this to the Google Search application, and does not fill in the EditText

I have tried to add a fairly simple extension on top of Android's example OpenGL 2.0 project in order to add texturing to basic shapes. This seems pretty straightforward, but on certain devices (Samsung Nexus S, LG Optimus 3D, Samsung Galaxy S) the texture just does not render. This is actually a problem that I am having on a much larger project, but I was able to reproduce the issue with the simple project below in the hope that someone here has an idea of where my code presents issues, or how to specifically architect GL textures for these devices (maybe there are issues with the devices).

OpenGL code that works on the Nexus One will not work properly on the Nexus S. Textures don't seem to render and I'm left with just black where textures should be. Anyone got any ideas? Daniel Smith The accepted answer given here addresses this issue in slightly more depth than I will, but while this black screen issue does arise from the Nexus S (and some other devices) being strict about power-of-two textures, it does not mean that textures need to have dimensions that are a Po2 . In the texture loading code, one may have the following lines: GLES20.glTexParameteri(GLES20.GL_TEXTURE_2D,

I want to create a google wallet like application in android. It is said that "all payment credentials are stored in a chip called the Secure Element contained within the phone". How can I access this secure element and store my card credentials into it. My aim is to use my phone (Nexus) at the checkout counter instead of my card. So what I want is to store some data to the Secure Element chip and access the data when I tap on an NFC reader. Thanks in advance. If you check the Google Wallet FAQ you can find the following : Your payment credentials are stored in a chip called the Secure Element

I'm trying to shoot picture and store it into internal storage by using the following code: Intent intent = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE); takenPhoto = new File(uploadsFolder, getNewPicFileName()); intent.putExtra(MediaStore.EXTRA_OUTPUT, Uri.fromFile(takenPhoto)); startActivityForResult(intent, SHOOT_MEDIA_REQUEST_CODE); The problem is that on Nexus S and Galaxy S devices default and the single orientation for ACTION_IMAGE_CAPTURE intent is landscape. If i shoot picture in portrait mode, that picture is stored into "takenPhoto" file rotated. That problem seems

i am able to disconnect the call programmatically for incoming unknown number call in android 2.2. But in android 4.1, its not working. Working Code to disconnect the call in android 2.2: private Class c; private Method m; private com.android.internal.telephony.ITelephony telephonyService; public void onReceive(Context context, Intent intent) { Bundle b = intent.getExtras(); String state = b.getString(TelephonyManager.EXTRA_STATE); if(state.equalsIgnoreCase(TelephonyManager.EXTRA_STATE_RINGING)) { TelephonyManager tm = (TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE); c =

I have to collect accelerometer data from my Android phone, so I have made a little program to do that. After some tests, I have found that my Nexus S accelerometer's rate is always 50 values per second when the phone is active, and 6 values per second when it is asleep (with a PARTIAL_WAKE_LOCK ), whatever the rate I ask for ( NORMAL , UI , GAME or FASTEST ). So I decided to install an application found on the Internet which tests the rate of the accelerometer : http://samoht.fr/tuto/accelerometers-frequency-on-android-with-code But I got the same "error" : whatever the rate I ask for, it is