Changing FloatingActionButton source:
 

    if (Build.VERSION.SDK_INT &gt;= Build.VERSION_CODES.LOLLIPOP) {
                floatingActionButton.setImageDrawable(getResources().getDrawable(R.drawable.ic_full_sad, context.getTheme()));
            } else {
                floatingActionButton.setImageDrawable(getResources().getDrawable(R.drawable.ic_full_sad));
        }

This can be replaced by following code from the support library instead:

    floatingActionButton.setImageDrawable(ContextCompat.getDrawable(getContext(), R.drawable.ic_full_sad));

If you are using the Support Library:

    floatingActionButton.setImageResource(R.drawable.icon_name)

Or you use the Support Library:

    floatingActionButton.setImageDrawable(ContextCompat.getDrawable(getContext(), R.drawable.ic_full_sad));


Assume that you will use the image `ic_arrow_forward.png` as your fab&#39;s background:

    fab.setImageResource(R.mipmap.ic_arrow_forward);

What I am using as follows,

    FloatingActionButton fab = (FloatingActionButton) findViewById(R.id.fab_btn);
    
    // State 1 -on
    
    fab.setImageDrawable(ContextCompat.getDrawable(getActivity(), R.drawable.fab_on));
    
    // State  2 - off
    
    fab.setImageDrawable(ContextCompat.getDrawable(getActivity(), R.drawable.fab_off));

I&#39;m having trouble creating a select in Angular2 that is backed by an array of Objects instead of strings. I knew how to do it in AngularJS using [ngOptions](https://docs.angularjs.org/api/ng/directive/ngOptions), but it doesn&#39;t seem to work in Angular2 (I&#39;m using alpha 42).

In the sample below, I have four selects, but only two of them work. 

 1. &#39;Select String&#39; is a simple string-based select, and it works fine. 
 2. &#39;Select Object via 2-way binding&#39; was my attempt to use 2-way binding. Unfortunately, it fails in two ways - when the page loads, the select shows the wrong value (foo instead of bar), and when I select an option in the list, the value &#39;[object Object]&#39; gets sent to the backing store instead of the correct value.
 3. &#39;Select Object via event&#39; was my attempt to get the selected value from $event. It fails in two ways, too - the initial load is incorrect in the same way as #2, and when I selection an option in the list, the value &#39;[object Object]&#39; is retrieved from the event, so I can&#39;t get the right value. The select gets cleared.
 4. &#39;Select Object via string&#39; is the only approach that uses an object that works. Unfortunately, it really works by using the string array from #1 and converting the value from string to object and back.

I can do #4 if that&#39;s the intended way, but it seems pretty clunky. Is there another approach? Am I just too early in the alpha? Did I do something silly?

    import {Component, FORM_DIRECTIVES, NgFor} from &#39;angular2/angular2&#39;;
    
    interface TestObject {
      name:string;
      value:number;
    }
    
    @Component({
      selector: &#39;app&#39;,
      template: `
        &lt;h4&gt;Select String&lt;/h4&gt;
        &lt;select [(ng-model)]=&quot;strValue&quot;&gt;
            &lt;option *ng-for=&quot;#o of strArray&quot; [value]=&quot;o&quot;&gt;{{o}}&lt;/option&gt;
        &lt;/select&gt;
    
        &lt;h4&gt;Select Object via 2-way binding&lt;/h4&gt;
        &lt;select [(ng-model)]=&quot;objValue1&quot;&gt;
            &lt;option *ng-for=&quot;#o of objArray&quot; [value]=&quot;o&quot;&gt;{{o.name}}&lt;/option&gt;
        &lt;/select&gt;
    
        &lt;h4&gt;Select Object via event&lt;/h4&gt;
        &lt;select [ng-model]=&quot;objValue2&quot; (change)=&quot;updateObjValue2($event)&quot;&gt;
            &lt;option *ng-for=&quot;#o of objArray&quot; [value]=&quot;o&quot;&gt;{{o.name}}&lt;/option&gt;
        &lt;/select&gt;
    
        &lt;h4&gt;Select Object via string&lt;/h4&gt;
        &lt;select [ng-model]=&quot;objValue3.name&quot; (change)=&quot;updateObjValue3($event)&quot;&gt;
            &lt;option *ng-for=&quot;#o of strArray&quot; [value]=&quot;o&quot;&gt;{{o}}&lt;/option&gt;
        &lt;/select&gt;
    
        &lt;div&gt;&lt;button (click)=&quot;printValues()&quot;&gt;Print Values&lt;/button&gt;&lt;/div&gt;
    
      `,
      directives: [FORM_DIRECTIVES, NgFor]
    })
    export class AppComponent {
      objArray:TestObject[] = [{name: &#39;foo&#39;, value: 1}, {name: &#39;bar&#39;, value: 1}];
      objValue1:TestObject = this.objArray[1];
      objValue2:TestObject = this.objArray[1];
      objValue3:TestObject = this.objArray[1];
    
      strArray:string[] = this.objArray.map((obj:TestObject) =&gt; obj.name);
      strValue:string = this.strArray[1];
    
      updateObjValue2(event:Event):void {
        const value:string = (&lt;HTMLSelectElement&gt;event.srcElement).value;
    
        this.objValue2 = this.objArray.find((obj:TestObject) =&gt; obj.name === value);
      }
    
      updateObjValue3(event:Event):void {
        const value:string = (&lt;HTMLSelectElement&gt;event.srcElement).value;
    
        this.objValue3 = this.objArray.find((obj:TestObject) =&gt; obj.name === value);
      }
    
      printValues():void {
        console.log(&#39;strValue&#39;, this.strValue);
        console.log(&#39;objValue1&#39;, this.objValue1);
        console.log(&#39;objValue2&#39;, this.objValue2);
        console.log(&#39;objValue3&#39;, this.objValue3);
      }
    }


How to use select/option/NgFor on an array of objects in Angular2

I have a large Ansible playbook where Docker images are built when running it. I am using an increasing number as the tag to version them. Currently, I have to specify this in every `hosts:` section.

I know there are global variables but from what I found by searching for &quot;ansible&quot; &quot;global variables&quot;, they have to defined outside of the playbook. Is it possible to define global variables which are global for the playbook?

Is it possible to define playbook-global variables in Ansible?

How to change FAB icon in an Activity during runtime. I have this code -&gt;

    FloatingActionButton fab = (FloatingActionButton) findViewById(R.id.fabMainActivity);

I know this is possible using `fab.setBackgroundDrawable();` but i am a newbie to android, don&#39;t understand how to do this.

Any help will be highly appreciated.

Thanks

android: dynamically change FAB(Floating Action Button) icon from code

How to change FAB icon in an Activity during runtime. I have this code ->
<pre><code class="hljs language-ini">FloatingActionButton fab = (FloatingActionButton) findViewById(R.id.fabMainActivity);
</code></pre>
I know this is possible using <code>fab.setBackgroundDrawable();</code> but i am a newbie to android, don't understand how to do this.
Any help will be highly appreciated.
Thanks

For my app I am using a `RecyclerView` inside a `ScrollView` where the `RecyclerView` has a height based on its content using [this library](https://github.com/serso/android-linear-layout-manager). Scrolling is working but it&#39;s not working smoothly when I scroll over the `RecyclerView`. When I scroll over the `ScrollView` itself it is scrolling smoothly.

The code I am using to define the `RecyclerView`:

    LinearLayoutManager friendsLayoutManager = new LinearLayoutManager(getActivity().getApplicationContext(), android.support.v7.widget.LinearLayoutManager.VERTICAL, false);
    mFriendsListView.setLayoutManager(friendsLayoutManager);
    mFriendsListView.addItemDecoration(new DividerItemDecoration(getActivity().getApplicationContext(), null));


The `RecyclerView` in the `ScrollView`:

    &lt;android.support.v7.widget.RecyclerView
        android:layout_marginTop=&quot;10dp&quot;
        android:layout_marginBottom=&quot;10dp&quot;
        android:id=&quot;@+id/friendsList&quot;
        android:layout_width=&quot;match_parent&quot;
        android:layout_height=&quot;wrap_content&quot; /&gt;


Recyclerview inside ScrollView not scrolling smoothly

While using RxJava and Retrofit 2 I am trying to create Unit Tests to cover when my app receives specific responses.

The issue I have is that with Retrofit 2 I cannot see a nice way of creating a retrofit.Response object without the use of reflection.

    @Test
    public void testLogin_throwsLoginBadRequestExceptionWhen403Error() {


        Request.Builder requestBuilder = new Request.Builder();
        requestBuilder.get();
        requestBuilder.url(&quot;http://localhost&quot;);

        Response.Builder responseBuilder = new Response.Builder();
        responseBuilder.code(403);
        responseBuilder.protocol(Protocol.HTTP_1_1);
        responseBuilder.body(ResponseBody.create(MediaType.parse(&quot;application/json&quot;), &quot;{\&quot;key\&quot;:[\&quot;somestuff\&quot;]}&quot;));
        responseBuilder.request(requestBuilder.build());

        retrofit.Response&lt;LoginResponse&gt; aResponse = null;

        try {
            Constructor&lt;retrofit.Response&gt; constructor= (Constructor&lt;retrofit.Response&gt;) retrofit.Response.class.getDeclaredConstructors()[0];
            constructor.setAccessible(true);
            aResponse = constructor.newInstance(responseBuilder.build(), null, null);
        } catch (Exception ex) {
            //reflection error
        }

        doReturn(Observable.just(aResponse)).when(mockLoginAPI).login(anyObject());

        TestSubscriber testSubscriber = new TestSubscriber();
        loginAPIService.login(loginRequest).subscribe(testSubscriber);

        Throwable resultError = (Throwable) testSubscriber.getOnErrorEvents().get(0);
        assertTrue(resultError instanceof LoginBadRequestException);
    }

I have tried using the following but this creates an OkHttp Response vs a Retrofit Response.

        Request.Builder requestBuilder = new Request.Builder();
        requestBuilder.get();
        requestBuilder.url(&quot;http://localhost&quot;);

        Response.Builder responseBuilder = new Response.Builder();
        responseBuilder.code(403);
        responseBuilder.protocol(Protocol.HTTP_1_1);

How to create a retrofit.Response object during Unit Testing with Retrofit 2

What causes following problem? Is my Android SDK Version not supported?

&lt;!-- language: none --&gt;

    Starting JS server...                                                                     
    Building and installing the app on the device (cd android &amp;&amp; gradlew.bat installDebug)...
                                                                                    
    FAILURE: Build failed with an exception.                                                  
                                                                                              
    * What went wrong:                                                                        
    A problem occurred configuring project &#39;:app&#39;.                                            
    &gt; failed to find Build Tools revision 23.0.1       

                                       
                                                                                          

React Native on Android failed to find Build Tools

In Lollipop, the download functionality works fine in my app, but when I upgraded to Marshmallow, my app crashes and gives this error when I try to download from the internet into the SD card: 

    Neither user  nor current process has android.permission.WRITE_EXTERNAL_STORAGE


It complains about this line of code: 

    DownloadManager manager = (DownloadManager) getSystemService(Context.DOWNLOAD_SERVICE);
    manager.enqueue(request);

I have the permissions in the manifest outside application:

    &lt;uses-permission android:name=&quot;android.permission.INTERNET&quot; /&gt;
    &lt;uses-permission android:name=&quot;android.permission.WRITE_EXTERNAL_STORAGE&quot; /&gt;
    &lt;uses-permission android:name=&quot;android.permission.WAKE_LOCK&quot; /&gt;

I cleaned and rebuilt the project, but it still crashes.

Storage permission error in Marshmallow

I am setting text using **setText()** by following way.

    prodNameView.setText(&quot;&quot; + name);

    prodOriginalPriceView.setText(&quot;&quot; + String.format(getString(R.string.string_product_rate_with_ruppe_sign), &quot;&quot; + new BigDecimal(price).setScale(2, RoundingMode.UP)));

In that **First** one is simple use and **Second** one is setting text with formatting text.

Android Studio is so much interesting, I used Menu **`Analyze -&gt; Code Cleanup`** and i got suggestion on above two lines like.

[![enter image description here][1]][1]

&gt; Do not concatenate text displayed with setText. Use resource string
&gt; with placeholders. less... (Ctrl+F1) 
&gt; 
&gt; When calling **TextView#setText:**
&gt; 
&gt; - Never call Number#toString() to format numbers; it will not handle fraction separators and locale-specific digits properly. Consider
&gt; using String#format with proper format specifications (%d or %f)
&gt; instead. 
&gt; - Do not pass a string literal (e.g. &quot;Hello&quot;) to display text. Hardcoded text can not be properly translated to other languages.
&gt; Consider using Android resource strings instead. 
&gt; - Do not build messages by concatenating text chunks. Such messages can not be properly translated.

What I can do for this? Anyone can help explain what the thing is and what should I do?

  [1]: http://i.stack.imgur.com/Yz5f2.png

Android TextView : &quot;Do not concatenate text displayed with setText&quot;

I want to set a ripple effect on textview and imageview in Android Studio. How can I do it?


How to set a ripple effect on textview or imageview on Android?

My applications UI is built using the Android Support Library, but there is currently no AppCompat version of the (intederminate) progressbar, which my app really needs.

I would prefer to not use any third party libraries to achieve material design progressbars, so I&#39;m wondering if anyone sits on information about why it&#39;s not included in the support library, and if there is any sign of it arriving (and when).

When is indeterminate progressbar coming to Android Support Library

Background
--
I try to add the same functionality as shown on many apps, where the upper area of the screen shrinks&amp;expands according to the scrolled content.

For this, I use Google&#39;s design library, as shown on [**the CheeseSquare sample**][1].

The problem
--
Thing is, no matter how much content there is in the NestedScrollView , it lets me scroll way below the last view of the content, just to let me see the final state of the actionbar, having the minimal size of itself.

In short, this is what I see when scrolling to the bottom (modified content of CheeseSquare sample):

[![enter image description here][2]][2]

while this is what I&#39;d like to have when scrolling to the bottom (taken from contacts app) :

[![enter image description here][3]][3]

I&#39;m also trying to fix a bug on [**ThreePhasesBottomSheet**][4] sample that scrolling in the bottom sheet content is possible even when it&#39;s in peek-state. To reproduce, start scrolling horizontally (which doesn&#39;t do anything, as there is nothing to scroll this way) and then vertically, which would somehow trigger scrolling of the content of the bottom-sheet.

Therefore, I need to disable there the scrolling in &quot;transformView()&quot; method, in the case that &quot;translation&lt;maxTranslation&quot; , and enable otherwise.

This is how it works using normal usage:

[![enter image description here][5]][5]

And this is how it behaves with the bug of not blocking the scrolling:

[![enter image description here][6]][6]


What I&#39;ve tried
--
I&#39;ve tried to play with the &quot;[**layout_scrollFlags**][7]&quot; flags, to change the height to wrap_content, and to remove the clipToPadding and fitsSystemWindows attributes.

Here&#39;s the sample XML file, which I&#39;ve modified to include only a single cardView instead of many:

    &lt;android.support.design.widget.CoordinatorLayout xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;
        xmlns:app=&quot;http://schemas.android.com/apk/res-auto&quot;
        android:id=&quot;@+id/main_content&quot;
        android:layout_width=&quot;match_parent&quot;
        android:layout_height=&quot;match_parent&quot;
        android:fitsSystemWindows=&quot;true&quot;&gt;
    
        &lt;android.support.design.widget.AppBarLayout
            android:id=&quot;@+id/appbar&quot;
            android:layout_width=&quot;match_parent&quot;
            android:layout_height=&quot;@dimen/detail_backdrop_height&quot;
            android:theme=&quot;@style/ThemeOverlay.AppCompat.Dark.ActionBar&quot;
            android:fitsSystemWindows=&quot;true&quot;&gt;
    
            &lt;android.support.design.widget.CollapsingToolbarLayout
                android:id=&quot;@+id/collapsing_toolbar&quot;
                android:layout_width=&quot;match_parent&quot;
                android:layout_height=&quot;match_parent&quot;
                app:layout_scrollFlags=&quot;scroll|exitUntilCollapsed&quot;
                android:fitsSystemWindows=&quot;true&quot;
                app:contentScrim=&quot;?attr/colorPrimary&quot;
                app:expandedTitleMarginStart=&quot;48dp&quot;
                app:expandedTitleMarginEnd=&quot;64dp&quot;&gt;
    
                &lt;ImageView
                    android:id=&quot;@+id/backdrop&quot;
                    android:layout_width=&quot;match_parent&quot;
                    android:layout_height=&quot;match_parent&quot;
                    android:scaleType=&quot;centerCrop&quot;
                    android:fitsSystemWindows=&quot;true&quot;
                    app:layout_collapseMode=&quot;parallax&quot; /&gt;
    
                &lt;android.support.v7.widget.Toolbar
                    android:id=&quot;@+id/toolbar&quot;
                    android:layout_width=&quot;match_parent&quot;
                    android:layout_height=&quot;?attr/actionBarSize&quot;
                    app:popupTheme=&quot;@style/ThemeOverlay.AppCompat.Light&quot;
                    app:layout_collapseMode=&quot;pin&quot; /&gt;
    
            &lt;/android.support.design.widget.CollapsingToolbarLayout&gt;
    
        &lt;/android.support.design.widget.AppBarLayout&gt;
    
        &lt;android.support.v4.widget.NestedScrollView
            android:layout_width=&quot;match_parent&quot;
            android:layout_height=&quot;match_parent&quot;
            app:layout_behavior=&quot;@string/appbar_scrolling_view_behavior&quot;&gt;
    
            &lt;LinearLayout
                android:layout_width=&quot;match_parent&quot;
                android:layout_height=&quot;match_parent&quot;
                android:orientation=&quot;vertical&quot;
                android:paddingTop=&quot;24dp&quot;&gt;
    
                &lt;android.support.v7.widget.CardView
                    android:layout_width=&quot;match_parent&quot;
                    android:layout_height=&quot;wrap_content&quot;
                    android:layout_margin=&quot;@dimen/card_margin&quot;&gt;
    
                    &lt;LinearLayout
                        style=&quot;@style/Widget.CardContent&quot;
                        android:layout_width=&quot;match_parent&quot;
                        android:layout_height=&quot;wrap_content&quot;&gt;
    
                        &lt;TextView
                            android:layout_width=&quot;match_parent&quot;
                            android:layout_height=&quot;wrap_content&quot;
                            android:text=&quot;Info&quot;
                            android:textAppearance=&quot;@style/TextAppearance.AppCompat.Title&quot; /&gt;
    
                        &lt;TextView
                            android:layout_width=&quot;match_parent&quot;
                            android:layout_height=&quot;wrap_content&quot;
                            android:text=&quot;@string/cheese_ipsum&quot; /&gt;
    
                    &lt;/LinearLayout&gt;
    
                &lt;/android.support.v7.widget.CardView&gt;
    
            &lt;/LinearLayout&gt;
    
        &lt;/android.support.v4.widget.NestedScrollView&gt;
    
        &lt;android.support.design.widget.FloatingActionButton
            android:layout_height=&quot;wrap_content&quot;
            android:layout_width=&quot;wrap_content&quot;
            app:layout_anchor=&quot;@id/appbar&quot;
            app:layout_anchorGravity=&quot;bottom|right|end&quot;
            android:src=&quot;@drawable/ic_discuss&quot;
            android:layout_margin=&quot;@dimen/fab_margin&quot;
            android:clickable=&quot;true&quot;/&gt;
    
    &lt;/android.support.design.widget.CoordinatorLayout&gt;

I&#39;ve tried the next code too :

    ((AppBarLayout.LayoutParams) collapsingToolbar.getLayoutParams()).setScrollFlags(0);

but this still allowed scrolling of the NestedScrollView itself in the [**CheeseSquare**][1] example, and also allowed flinging in the [**ThreePhasesBottomSheet**][4] sample . 


The questions
--
 1. What can I do in order to make the scrolling stop when there is no more content to show at the bottom?

 2. In addition, what can be done to disable scrolling of the NestedScrollView in any time I wish ( for the [**ThreePhasesBottomSheet**][4] sample) ? Something like &quot;setEnableScrolling(...)&quot; ? 

   I&#39;ve tried to extend NestedScrollView and also extend from ScrollingViewBehavior, but failed to find what can be done to disable the scrolling.

It&#39;s probably a very simple thing to change, but I can&#39;t find out what...


EDIT: if needed, this is what I currently use for the design&amp;support library

    compile &#39;com.android.support:appcompat-v7:23.1.0&#39;
    compile &#39;com.android.support:design:23.1.0&#39;

----

EDIT: for #2, I&#39;ve found a workaround from within the BottomSheetLayout.java file, to disable all that&#39;s related to the variable &quot;sheetViewOwnsTouch&quot;, as if it&#39;s always set to &quot;false&quot;. This will allow stealing touch events on the bottom sheet. However, this is just a workaround, and only for this case. It also causes some touch events that should have been handled by other views. I still wish to know how to block the scrolling programmatically, and also in the other case of enough-space-to-show-content.


  [1]: https://github.com/chrisbanes/cheesesquare
  [2]: http://i.stack.imgur.com/JYxsE.gif
  [3]: http://i.stack.imgur.com/t2qFA.gif
  [4]: https://github.com/AndroidDeveloperLB/ThreePhasesBottomSheet
  [5]: http://i.stack.imgur.com/fFVvm.gif
  [6]: http://i.stack.imgur.com/28tZR.gif
  [7]: http://developer.android.com/reference/android/support/design/widget/AppBarLayout.LayoutParams.html#setScrollFlags(int)

How to disable scrolling of NestedScrollView&amp;CollapsingToolbarLayout, for example when there is no more content below?

I&#39;m trying to figure out how can be modified FloatingActionButton from android support library. Can it be used with the text instead of image?

Something like this one:

[![enter image description here][1]][1]

I see it extends ImageButton so I think not. Am I right?

Is this correct in terms of Material Design in general?

  [1]: http://i.stack.imgur.com/5K8QI.png

FloatingActionButton with text instead of image

I&#39;m playing a little bit with [Material-UI][1]. Are there any options for creating a grid layout (like in [Bootstrap][2])? 

If not, what is the way to add this functionality?

There is a [GridList component][3] but I guess it has some different purpose.


  [1]: http://material-ui.com/#/home
  [2]: http://getbootstrap.com/css/#grid
  [3]: http://material-ui.com/#/components/grid-list

Material UI and Grid system

I want to hide/show `FloatingActionButton` on scroll of `RecyclerView`.

My `XML` layout :

&lt;!-- language: xml --&gt;

    &lt;android.support.design.widget.CoordinatorLayout
                android:layout_width=&quot;match_parent&quot;
                android:layout_height=&quot;match_parent&quot; &gt;

                &lt;android.support.v7.widget.RecyclerView
                    android:id=&quot;@+id/recyclerview_eventlist&quot;
                    android:layout_width=&quot;match_parent&quot;
                    android:layout_height=&quot;match_parent&quot; /&gt;

                &lt;android.support.design.widget.FloatingActionButton
                    android:id=&quot;@+id/fab_createevent&quot;
                    android:layout_width=&quot;wrap_content&quot;
                    android:layout_height=&quot;wrap_content&quot;
                    android:layout_margin=&quot;@dimen/fab_margin&quot;
                    app:layout_anchor=&quot;@id/recyclerview_eventlist&quot;
                    app:layout_anchorGravity=&quot;bottom|right|end&quot;
                    app:layout_behavior=&quot;com.eventizon.behavior.ScrollAwareFABBehavior&quot;
                    android:src=&quot;@drawable/ic_edit&quot;
                    app:backgroundTint=&quot;@color/custom_color_1&quot;
                    app:borderWidth=&quot;0dp&quot; /&gt;
            &lt;/android.support.design.widget.CoordinatorLayout&gt;

DrawerLayout is the parent layout of this layout.

    
    
        public class ScrollAwareFABBehavior extends FloatingActionButton.Behavior {
    
    
    	private static final String TAG = &quot;ScrollAwareFABBehavior&quot;;
    
    	public ScrollAwareFABBehavior(Context context, AttributeSet attrs) {
    		super();
    		Log.e(TAG,&quot;ScrollAwareFABBehavior&quot;);
    	}
    
    	@Override
    	public void onNestedScroll(CoordinatorLayout coordinatorLayout,
    			FloatingActionButton child, View target, int dxConsumed,
    			int dyConsumed, int dxUnconsumed, int dyUnconsumed) {
    		// TODO Auto-generated method stub
    		super.onNestedScroll(coordinatorLayout, child, target, dxConsumed, dyConsumed,
    				dxUnconsumed, dyUnconsumed);
    		Log.e(TAG,&quot;onNestedScroll called&quot;);
    		if (dyConsumed &gt; 0 &amp;&amp; child.getVisibility() == View.VISIBLE) {
    			Log.e(TAG,&quot;child.hide()&quot;);
    			child.hide();
    		} else if (dyConsumed &lt; 0 &amp;&amp; child.getVisibility() != View.VISIBLE) {
    			Log.e(TAG,&quot;child.show()&quot;);
    			child.show();
    		}
    	}
    }

Used this layout behaviour for `FloatingActionButton`. 

When I see `logcat` only constructor is getting called. `onNestedScroll()` doesn&#39;t get called when I scroll the list.

Hide FloatingActionButton on scroll of RecyclerView

Already asked [here][1] but without a proper answer.

I want the FAB to float on top of the keyboard. that&#39;s it.

For example

 1. Open a new `Blank Activity` template project with Android Studio
 2. Change the Hello World `TextView` to `EditText`
 3. See image below:


[![enter image description here][2]][2]


  [1]: https://stackoverflow.com/questions/32216564/move-floating-action-button-above-keyboard
  [2]: http://i.stack.imgur.com/rK58a.png

Set FAB (Floating Action Button) above keyboard

Where can I find the plus sign at the center of a Floating Action Button?

Is it made by Android or do I need to do it by my self?

Android FAB plus sign not present on android drawable

I&#39;m trying to create a floating button in my app. The button is there, but the image in the button is a bit upwards (see image). 

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/o38Rj.png

I can&#39;t figure out what&#39;s wrong with it. Below is part of the XML for floating button.

    &lt;android.support.design.widget.FloatingActionButton
            android:id=&quot;@+id/buttonUp&quot;
            android:layout_width=&quot;wrap_content&quot;
            android:layout_height=&quot;wrap_content&quot;
            android:layout_marginRight=&quot;16dp&quot;
            android:layout_marginTop=&quot;480dp&quot;
            android:clickable=&quot;true&quot;
            android:scaleType=&quot;center&quot;
            android:src=&quot;@drawable/btn_back_to_top_3x&quot;
            app:layout_anchor=&quot;@id/layout&quot;
            app:layout_anchorGravity=&quot;bottom|right|end&quot;
            app:backgroundTint=&quot;@android:color/background_light&quot;
            app:fabSize=&quot;normal&quot; /&gt;

The button is showing where I wanted it. The only problem seems to be the image inside isn&#39;t center. Why is this happening? 

**EDIT**:
After some more looking around I realized the image itself was having problem where the image isn&#39;t actually centered and there are space at the bottom side (which cause the image to being push upward).

Content Type	Original Author	Original Content on Stackoverflow
Question	Hirdesh Vishwdewa	View Question on Stackoverflow
Solution 1 - Android	Sunny	View Answer on Stackoverflow
Solution 2 - Android	PaulT	View Answer on Stackoverflow
Solution 3 - Android	Paul Spiesberger	View Answer on Stackoverflow
Solution 4 - Android	EckoTan	View Answer on Stackoverflow
Solution 5 - Android	Umanda	View Answer on Stackoverflow

android: dynamically change FAB(Floating Action Button) icon from code

Android Problem Overview

Android Solutions

Solution 1 - Android

Solution 2 - Android

Solution 3 - Android

Solution 4 - Android

Solution 5 - Android

Is it possible to define playbook-global variables in Ansible?

How to use select/option/NgFor on an array of objects in Angular2

Attributions