htc-android

I've released an IME (soft keyboard) app and I am getting crash reports from HTC phones only . Here is the stack trace: java.lang.NullPointerException at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:465) at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:697) at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:666) at com.comet.android.keyboard.util.Util.getBitmapDrawable(MyFile.java:416) ... Here is my call to Drawable.createFromResourceStream() drawable = Drawable.createFromResourceStream(context.getResources(),

I'm planning to calculate disparity map by taking two pictures from the two back cameras of Evo 3D. However, I'm able to use only one camera. I tried different index. index 0 gives me left camera (one of the back cameras) 1 gives me front camera -1 gives me left camera (one of the back cameras). I once got other camera using -1 index, but it's not working anymore. I'm using CameraBridgeViewBase . I have seen on Google group of android-opencv that people have successfully used both cameras of Evo 3D phone. I want to know how to do it? Is there some other index? or is there some other way using

The Problem: Certain Android devices (listed at the bottom of the question) exhibit unexpected behavior when utilizing the setOrientationHint(int degrees) function for videos taken with the front facing camera. The expected behavior is for the video to be rotated clockwise, but these devices rotate the video counterclockwise. My Goal: To identify a variable within either the camera settings or hardware orientations that allows me to predictably know when this will occur. Specifically, I would like to avoid special casing these phones in my code! Further Explanation: I am recording video using

When trying to push an app to my device using Android studio, I'm getting the below log readout in AS about 80% of the time. Any clues? Waiting for device. Target device: htc-htc_one_m8-FA43NWM07298 Uploading file local path: /Users/Pete/Development/github/myApp/app/build/outputs/apk/myApp_debug.apk remote path: /data/local/tmp/com.my.app Installing com.my.app DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.my.app" java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String android.os.SystemProperties.native_get(java.lang.String) (tried Java_android_os

I have gotten some reports from users of crashes when try use my application on Verizon's 4G/LTE. Looking at the stack trace, it looks like Android's HttpClient.execute() implementation is throwing an OOM. This happens only on 4G/LTE devices, specifically HTC Thunderbolt, and only when on 4G/LTE. WiFi, 3G, UMTS are OK. Also works fine on Sprint's WiMax 4G stuff works fine. Two questions: What's the best way to get the attention of Android devs about this? Any better options than reporting on http://code.google.com/p/android/issues ? Any ideas on how I can work around this? I don't have a 4G