In need of an icon that can be used indicate to the user when to use the Flatbed Scanner and when to use the ADF function of a scanner. The current scanner icon indicates a flatbed scanner so a different icon indicating an ADF scanner is required.

I'd like to be able to limit the retry count in Authenticator to 3. At the moment it appears to be 20. I don't see anything to do this and didn't get an answer in StackOverflow, so assuming it's not possible at the moment.

Since a good architecture serves to make it easy to swap implementations I think it would be nice to have one or more samples which demonstrate how a data source implementation using a combination of a remote api, and a local sqlite database can be replaced with a realtime database.

I am not sure yet how it would be possible to run the same espresso tests in such a sample since mocking the fire

When Retrofit2 returns okhttp3.ResponseBody then it has to be closed in order to avoid memory leaks, right? It's something what I have just noticed in our code and am not sure.

@GET("accountId")
@WorkerThread
Call<ResponseBody> getUserData(@Header(NetworkConstants.Header.AUTHORIZATION) String accessToken);

...
Response<ResponseBody> response = interface.getUserData();
// do something 

Your documentation for the description methods for a chart is outdated.

https://github.com/PhilJay/MPAndroidChart/wiki/General-Chart-Settings-&-Styling:

• setDescription(String desc): Set a description text that appears in the bottom right corner of the chart.
• setDescriptionColor(int color): Sets the color of the description text.
• setDescriptionPosition(float x, float y): Sets a cu

shadowsocks/shadowsocks-android#1328
I currently use Tasker to turn off Shadowsocks on standby to avoid this problem, but the TV client does not support the Tasker plugin.

Add Tasker plugin support to the TV client, just like the Android version.

Problem causes
CiNcH83/bravia_atv2#27

I am profiling memory on my app usage and was looking at the built-in tremMemory(int level) methods in LruResourceCache and LruBitmapPool to see what their behavior is when I invoke them from my application's onTrimMemory method. The trim memory levels are documented here.

Here is Glide's implementation

Question Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Question Subject

This is a question about documentatio

When Num Lock is off, the keys are supposed to function to left, right, up or down. But they aren't working.

Both of these pages discuss tools to debug network calls:
https://github.com/codepath/android_guides/wiki/Troubleshooting-Common-Issues
https://github.com/codepath/android_guides/wiki/Troubleshooting-API-calls

Android Studio 3.0 has a profiler that includes network information: https://developer.android.com/studio/profile/android-profiler.html

It would be good to include on the wiki pages.

Run following commands and enjoy the stream of warnings from Dokka:

rm -rf docs/api
./gradlew leakcanary-android-core:dokka leakcanary-android-instrumentation:dokka leakcanary-android-process:dokka leakcanary-object-watcher-android:dokka leakcanary-object-watcher:dokka shark-android:dokka shark-graph:dokka shark-hprof:dokka shark-log:dokka shark:dokka

Review errors and see if any of t

Hello everyone,

I would like to propose adding more documentation on this open source project as there is limited information for new contributors (especially English speaking ones). Here are the 2 additional documentation I think should be added to help new contributors to this project:

1. Add Authors / Main Contributors contact section
   In case new contributors have questions, it would

请问下，进入淘宝二楼之后，想回到一楼，目前只能从底部去上拉，期望全屏上拉都可以回到二楼，需要怎么去设置呢？谢谢，

Is your feature request related to a problem? Please describe.
When implementing a textField with next return key type, the keyboard is dismissed and focusing another textField brings it back BUT a flick is produced.

Describe the solution you'd like
I'd like to be able to prevent the textFieldShouldReturn implementation from always dimissing soft input.

**Describe alternatives yo

We've recently updated our github workflow to have 3 branches:

master - current version on npm that's live
next - upcoming features and changes
patch - bug fixes (usually released within a day)

We should update the contributing section on the website and maybe .github/CONTRIBUTING.md to let users know which branch they should base their changes on if they want to make a pull request.