android-2.3-gingerbread

For some reason, using "GCMRegistrar.register(this, SENDER_ID);" works on 4.0 + devices. However, it stuck at the following message without getting anymore GCM notification from Google. " Registering app (my package) of senders (my api #) " 1) manifest and receiver should be correct since it's working on 4.2.1. 2) I have google play and linked with google account on 2.3.3 device I have searched for several day and couldn't find an answer. Anyone know what's wrong or have the same issue? Thanks Cookie Mon I found out it's just because I didn't set the receiver's category correctly. Since I was

Updated I have a problem with gradient bitmaps on android 2.3. I read this great article and decode my bitmaps using next options: BitmapFactory.Options options = new BitmapFactory.Options(); options.inPreferredConfig = Bitmap.Config.ARGB_8888; options.inDither = true; And on android 2.2 everything is great, but on android 2.3 gradient artifacts remain even after that decoding. I run application from article on 2.3 with my bitmaps and all variants are bad: 16/32 bit, (not) dither and RBG_565, ARGB_8888 and ARGB_4444 - gradient has artifacts. Also I tried to decode without options. Everything

I'm trying to show notifications in my app along with a progress bar in it. My app specs are that I'm targeting API 15 with minimum SDK set to 8. I'm using the following code to show notifications: NotificationManager mNotificationManager = (NotificationManager) getSystemService(Context.NOTIFICATION_SERVICE); NotificationCompat.Builder mBuilder = new NotificationCompat.Builder(this); mBuilder.setContentTitle("My Application") .setContentText("Downloading...") .setProgress(0, 0, true) .setSmallIcon(R.drawable.ic_launcher); PendingIntent in = PendingIntent.getActivity(getApplicationContext(), 0,

I've recently finished building a mobile site and discovered a bug that only seems to occur on Android Gingerbread. When a select input is placed on a slide within a JS slider (such as Flexslider or SwipeJS), you can no longer click it or give it focus and select the options. I'm wondering if it has to do with the use of display none/block which both these sliders use - perhaps Gingerbread cannot render the select properly under these circumstances? Interestingly, the first slide using SwipeJS is functional; the others not. I've popped a few tests online to demonstrate: http://playground

I am getting an OutOfMemoryError when I try to create a String larger than 4MB using StringBuilder.append() . As far as I know, StringBuilder doesn't have any limitations regarding size and so doesn't String . So I searched for "how to increase Android heap size" and as far as I could conclude from this answer and this answer , Gingerbread is the only version in which you have no way of dealing with the heap size, since for earlier versions you use the VMRuntime class and for newer versions android:largeHeap="true" on the Manifest. Is that assumption correct? What do you do when you're in

I created a simple application inspired by this example in order to test all the available options (ie extra). I read about the EXTRA_PARTIAL_RESULTS extra and if I enable this option I should receive from the server any partial results related to a speech recognition. However, when I add this extra to the ACTION_RECOGNIZE_SPEECH intent, the voice recognition does not work anymore: the list does not display any results. protected void onActivityResult(int requestCode, int resultCode, Intent data) { if (requestCode == VOICE_RECOGNITION_REQUEST_CODE) { switch(resultCode) { case RESULT_OK: Log.i

You can see my scrollview being displayed the same in jellybean, & kitkat, very awesome: But I am shocked to see the same thing in lower versions like 2.2, 2.3.3 It seems that it display some portion of text attached to upper & bottom portion of screen. BTW, The lines in middle are just the textviews with gray background . You can see my xml code, sorry its a little long code <ScrollView xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="wrap_content" android:background="@drawable/stars" android:padding="5dp" android:scrollbars

Added ActionBarCompat + NavDrawer to my project, running on 4.3 device is smooth, on 2.3 device I get the following exception: 09-08 15:09:15.229: E/AndroidRuntime(2964): FATAL EXCEPTION: main 09-08 15:09:15.229: E/AndroidRuntime(2964): android.view.InflateException: Binary XML file line #1: Error inflating class <unknown> 09-08 15:09:15.229: E/AndroidRuntime(2964): at android.view.LayoutInflater.createView(LayoutInflater.java:518) 09-08 15:09:15.229: E/AndroidRuntime(2964): at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56) 09-08 15:09:15.229: E

Seems like Samsung disabled their overscroll (probably due to an Apple suit). I have an implementation of a view that extends ScrollView and overrides protected boolean overScrollBy(int deltaX, int deltaY, int scrollX, int scrollY, int scrollRangeX, int scrollRangeY,int maxOverScrollX, int maxOverScrollY, boolean isTouchEvent) { ... return super.overScrollBy(deltaX, deltaY, scrollX, scrollY, scrollRangeX, scrollRangeY, 0, metrics.widthPixels,isTouchEvent); } On every other device (Gingerbread and up of course), overScrollBy is being called when the scroller reaches it's end, and the user can