Android get logs programmatically

Логирование в Android приложениях

Уверен, что всем разработчикам приложений на платформе Android знаком класс Log, позволяющий логировать различные события. По различным причинам, формат записи логов для каждого проекта может отличаться достаточно сильно — начиная от «AAA», «111111» и «I was here» до более-менее внятных — «Opening HTTP connection to habrahabr.ru». Под катом вы найдете пример функции, которая поможет навести порядок в логах.
Данный топик не претендует на оригинальность и универсальность. И поэтому, если в вашем проекте уже существует некий стандарт логирования событий, то смело проходите мимо — топик скорее ориентирован на начинающих разработчиков.

Как правило, ценность логов начинаешь понимать только когда заказчик матерясь отсылает лог на почту и просит засабмитить фикс через 5 минут. И если лог состоит из сообщений невнятного характера, то как минимум, разбр данного лога займет куда больше времени, чем хотелось бы.

Пытаемся навести порядок

Логи существуют для того, чтобы разработчик мог понять что, где и когда произошло. Найти ответ на вопрос «когда произошло» достаточно просто — в логах Андройд записывает время события. Нахождение ответа на вопрос «что произошло» так же не вызывает больших трудностей, если сообщение в лог было написано со смыслом, например: «Opening file. ». Вопрос «где произошло» оказывается наиболее сложным. Если проект большой, то придеться потратить время на нахождение нужного места кода, даже, если лог был написан со смыслом.

Если событие логируется с указанием Throwable (чаще Exception), например, метод public static int d (String tag, String msg, Throwable tr) , то в консоле сообщений будет выведен стек, который поможет быстро идентифицировать место логирования. Но использование данного метода без особой необходимости до безобразия перегрузит лог ненужной информацией.

Если же логируется просто текст, то при логировании можно явно указывать место вызова. Например:

Однако, писать такое каждый раз — дело утомительное и неблагодарное.

Ниже приведен пример класса Log , который делает это автоматически.

Использование класса очень простое:

Результатом логирования данным способом будут примерно следующие строки:

Примечание:
По понятным причинам, данный способ мало пригоден для приложений «пропущенных» через обфускатор.

В общем-то все.
Прошу прощения, если эта статья показалась слишком тривиальной для хабра.

Источник

Android Turn on GPS programmatically

Jan 2, 2019 · 3 min read

In our previous article, we have taught you how to get location using FusedLocationProviderClient and we also mentioned in that article that for using this feature, you need to turn on device GPS manually by redirecting to settings of your device.

Programmatically we can turn on GPS in two ways. First, redirect the user to location settings of a device (by code) or another way is to ask to turn on GPS by GPS dialog using LocationSettingsRequest and SettingsClient.

First method:
By usin g this, the user will be redirected to the Settings page of your device and user has to turn on GPS manually.

Second method:
In this method, we will show you code to turn on GPS using android gms location request and setting clients. Here we provide a custom class GpsUtils.java with a code written in it with method turnGPSOn(). The method has a callback listener to check the current status of GPS. If GPS is already turned on, no further code will be determined and callback revert true as GPS is on. Let’s look at the code below and we will show how to use GpsUtils.java.

SettingsClient class is the main key point for interacting with location-based API. This API makes it easy for an app to ensure that the device’s system settings are properly configured for the app’s location needs.

LocationSettingsRequest Specifies the types of location services the client is interested in using. Settings will be checked for optimal functionality of all requested services. Use LocationSettingsRequest.Builder to construct this object.

GPS Dialog will be shown for SettingsClient’s failure callback and it will result in an activity’s onActivityResult(). So basically if the user agrees for turn on GPS, we can enable GPS flag in our activity.

and now call GpsUtils class before getting a location.

We recommend you to put this code in onCreate() of your activity. So that, turn on GPS and getting a location works well one by one. And also GPS takes some minor delay to trace your device location.

We have provided code in the previous article to get a location. Thus, we made changes for GPS in that code and republish the same code.

Find code here. Code contains previous article example for getting the current location.

Источник

Android localization: Step-by-step

With Android’s expansive popularity among people from all over the world, getting Android localization done right has become a crucial step in app development.

You may be a novice developer building your very first Android app, or you may be an expert programmer getting yet another Android app under your belt among a dozen others. But, let me ask you a question. For whom are you creating this app? In other words, what’s your target audience?

Hopefully, you want your app to grow and be used beyond your local community; to reach across continents, and ultimately worldwide. Here’s the sticking point; most of the world does not speak English. Sooner or later, you will need to support multiple languages.

This warrants the need for your Android application to be localized.

In this article, we will explain how to get started with Android localization using step-by-step examples.

We will cover the following topics in this tutorial:

• Android i18n/l10n.
• Adding resources with the help of Android Studio l10n facilities.
• Programmatically switching Locale using proxied Context .
• Localization-related deprecations across different API levels.
• Noun pluralization with Android quantity strings.
• Date-time localization using java.text.DateFormat.getDateTimeInstance() .

The first version of this post was written by Arturs Ziborovs.

The source code is available on Github.

Localize Your Android App

First and foremost, let’s create an Android project with an empty Activity to be used for our localization purposes. We can use a template provided by Android Studio. For demonstration purposes, let’s make a project with the following configuration:

Note: You may choose any API version less than or equal to API 30 (latest version at the time of writing).

Add Some Elements

Now it’s time to put some content into this empty MainActivity . Open up the activity_main.xml file located the inside res/layout directory of our android-i18n project. Let’s put a simple TextView with the string «Hello world» in it:

Next, let’s run this app and see. It should look like this:

But, there’s an issue here; the «Hello world!» string value is embedded directly within the layout description of the test_text_view itself. As you may already know, it is an elementary level bad practice to hardcode string values within the code of an application. On top of that, you would need this text to dynamically change in case your Android localization app’s user decides to change the application’s language to another.

Add Language Resources

How about stocking up our Android app with some language resources holding localization-related values? These will act as static assets holding language content for multiple languages.

Android SDK provides a specific structure to hold Android app resources. Following this pattern, look inside the res/values directory and you’ll be able to find a strings.xml resource file holding the text strings used in our android-i18n application.

Let’s add a new string resource in strings.xml to hold the «Hello world!» string:

Note that we provided a my_string_name key to refer to our sample text string value «Hello World!» . It is acceptable to do so in simple contexts such as this, but please make it a habit to come up with self-explanatory names for your keys. For instance, try settings_language_title or settings_language_description .

Add More Resources

We can call upon the help of Android Studio l10n support to conveniently add another resource file.

Let’s create a new resource file for the Russian language using Android Studio’s resource file wizard.

Firstly, right-click on the res folder and choose “New -> Android resource file”:

The wizard will let you choose from a list of available Resource qualifiers for your new folder.

Qualifiers are used by the system to decide which resources to load based on the user’s device configuration, such as selected language, screen size, country code, etc. Keep in mind that these qualifiers can be used for other types of resources such as images or layouts as well. You can refer to this Android documentation to learn more about Android app resources.

Secondly, select Locale from the list of available qualifiers and add it to the chosen qualifiers. Now to add a Russian language resource file, choose ru: Russian from the language list. We can keep the Specific Region Only: setting at its default value Any Region since we will not be narrowing down our localization to particular regions for this example.

Thirdly, set the File name as «strings.xml» . You will notice that Android Studio has automatically set a Directory Name of values_ru .

Then lastly, click the OK button and a «strings.xml» file inside a res/values-ru/ directory should be opened.

Now, let’s add Russian language resources to this XML file. Be sure to add the same keys as previously when creating the «strings.xml» for the English US language:

Refer the Resources

Once we have our resources properly set up for two languages, let’s reference them on our TextView . Open up the TextView in the res/values/activity_main.xml layout. Refer the resource key my_string_name to the android:text attribute of the TextView :

Refer Resources Dynamically

If you need to dynamically change the strings used in a TextView , you can do it programmatically within MainActivity :

1. Set the title of this Activity’s ActionBar to the string resource app_name .
2. Set the text of test_text_view to string resource my_string_name .

Now our android-i18n application is successfully localized for two languages. Let’s run our app again and see what it looks like:

You might be thinking…

It looks the same as before, duh.

But as a matter of fact, we’re no longer showing a hardcoded «Hello world!» value on the TextView. Instead, in its place, we are now representing test_text_view resource localized according to our Android device’s System language.

We can test this out by running our android-i18n application on an Android device with its System language set to Russian.

Following the same pattern, we can now expose our application not just in the form of US English, but also in countless other languages.

However, how do we switch our app to another language without touching the device settings? We’ll explore this in the next section.

Change Application Locale Programmatically

By default, Android will try to load resources based on the System language that is set on the user’s phone. Therefore, if a Russian user, Ann, with her Android set to the Russian language opened our android-i18n application on her phone, she’d see an app localized to her own language.

But what if another user wants to use the Russian language for his android-i18n application on an Android that has its default language set to English?

To deal with this, we will have to programmatically update the locale of our android-i18n application to override the default locale set in the user’s system.

Let’s create a ContextUtils utility class to hold our locale updating methods. Place this within a utils package on the android-i18n application, as follows:

Extend the class with ContextWrapper to allow it to create ContextWrapper objects holding a proxy implementation of Context .

Let’s code an updateLocale method that returns a wrapper Context holding a modified locale of the current activity context, like so:

1. Create a new configuration object using the resource configuration in the given Context .
2. Create a locale list containing the locale to which we plan to switch.
3. Assign the default locale for this instance of the JVM to the locale at the first index on this list. Since there’s only one locale present in our example, this will inadvertently set the locale on localeToSwitchTo variable as the default locale.
4. Set the locale list we created in step #2 to the configuration object we created in step #1 using a setter.
5. Directly modify the locale field in the configuration object we created in step #1 with the localeToSwitchTo parameter on the method.
6. Set the current context variable to a new Context object whose resources are adjusted to match the given configuration.
7. Store the newly updated configuration in the resources field in the given context.
8. Return a new ContextUtils object created by passing the context variable as a parameter to ContextUtils constructor.

Deprecations Across Different Levels

If you skimmed through the code for the updateLocale method, you must have seen that the implementation faces changes based on the Android build version of the application. This is due to various deprecations that have occurred along the course of Android API levels.

Let’s reanalyze a few code snippets from the updateLocale method to get a general idea of these deprecations, and how they warranted the code changes that followed:

1. Configuration.locale field was deprecated in API level 24 (Nougat). This was put in place by Android API developers to make coders move to the use of getters and setters instead of directly accessing variables.
2. This was marked as the preferred way of setting up locales (instead of using the direct accessor or setLocale(java.util.Locale)) starting from API level 24.
3. Before API level 24, developers could directly access the configuration.locale field to change it as they pleased.

1. Resources.updateConfiguration method was deprecated from API 25 (Nougat++).
2. Context.createConfigurationContext has been around since API level 17 (Jelly Bean MR1). However, with the deprecation of the Resources.updateConfiguration method, this was the workaround approach to update the configuration of a context.
3. Before API level 25, developers could use the Resources.updateConfiguration method to update a context configuration.

With our ContextUtils sorted out, let’s see how to use it on our app to change locale. Let’s open up the MainActivity class on our android-i18n application and put in an overriding method like the below:

This code firstly creates a new ContextWrapper with its locale updated to the Russian language. Secondly, it passes this newly created ContextWrapper to be attached as the context used in MainActivity . Afterwards, when this activity loads on startup, it will work on a context that has its locale set to Russian.

That’s it! Simply run the application and voila, the text has successfully been localized without any manual changes to the Android’s System language on our end.

Some Android Localization Extras

Let’s take a look at a few other things you’ll surely run into on your Android app localization journey.

How to Pluralize Nouns

When dealing with nouns, we need them to be properly pluralized according to a particular language’s standards. For instance, we don’t want our Android application to say “I have 3 cat” instead of “3 cats“, right? This is where Android’s built-in support for quantity strings(plurals) comes in handy. Let’s try it out!

First off, add some TextViews to your activity_main.xml :

These will consecutively hold text for one, few, and many quantities of objects.

As you may know, pluralization rules usually differ from language to language. English only has two main forms such as:

While the Russian has three variations when counting whole numbers, like:

Therefore, we will have to create separate plurals elements for each of these languages.

Let’s add these pluralizations in our project’s respective language resource files:

• On res/values/strings.xml :

• In res/values-ru/strings.xml :

In case you’re interested, the syntax for plurals elements are documented in the syntax section of the Android documentation for quantity strings.

Now let’s set some plural text values in the TextViews we created earlier. Add these lines to the onCreate method of the MainActivity class:

Refer to the documentation on Resources.getQuantityString method to get an idea of its parameter usage.

The result should look like this for each localization:

What about Date and Time?

We can call upon the help of the getDateTimeInstance method provided in the DateFormat class to handle localization of date and time on Android projects.

Firstly, let’s add a simple TextView within our android-i18n application’s activity_main.xml :

Then, let’s fill this TextView with text showing a localized date and time upon launch of our app.

Open up the MainActivity class and put this code in its onCreate method:

1. Create a new Date object with a no-arguments constructor and allocate it to currentDateTime . Using this constructor makes the Date object represent the exact time (and date) at which it was allocated.
2. DateFormat.getDateTimeInstance static factory method is used to automatically format currentDateTime for the current locale.

Run the Android app with each localization. It should now show the current date and time successfully localized to the corresponding locales:

Lokalise saves the day

So my friend, if you’ve come this far in the article, you must be dead set on somehow getting your Android app internationalized. But let’s face it, do you — or your team — really have the time to learn all of these new classes and methods and deal with deprecated variables, just to localize your app?

Yeah, I heard you. You don’t.

As you add more features and expand to more markets, your app will grow to thousands of strings in dozens of languages. Surely you could use the help of a proper Translation Management System to carry out your Android app’s i18n while keeping yourself sane, am I right?

That’s where Lokalise comes in. Let’s see how it works.

First off, create an account or log in to Lokalise.

On the Lokalise dashboard, select Upload to upload the language resource files of the project you plan to localize. In the case of the Android application we created during the tutorial, you can choose the strings.xml files we created for the two languages.

Note: If the detected language is incorrect, feel free to select the correct language from the dropdown.

Click the Import the files button to complete the resource uploading process.

Head back to the project’s Lokalise Dashboard. You will see the resources neatly organized like so:

That was pretty fun and easy, wasn’t it? The Lokalise editor is a feature-rich and user-friendly interface that includes collaborative translation, translation quality assurance, automatic translation suggestions, professional translation services, and loads more to be used for your Android app’s localization.

How to Edit Your Translations

No need to change countless text files if you need to change some resource values. Let’s see how easy it is with Lokalise. Suppose you are a dog person, click on «cat» and replace it with «dog» in the popup:

Then click the Download button to download your new translations and perform the following steps:

1. Choose the «Android Resources» file format from the list.
2. Press the Build and download button to obtain a ZIP archive with your new translations.
3. Replace the old files in your project with the new ones.

Likewise, Lokalise automatically generates the requested translation files with all your project languages for the specified platform.

Conclusion

In this tutorial, we checked out how to localize an Android application to multiple locales. We explored various API deprecations that caused Android l10n to become not quite a walk in the park. We also delved into ways we could effectively tackle these deprecations. Next, saw how we can switch to different languages; either by changing the device’s language or forcefully switching the application to a modified Context .

In addition to this, we looked into how we can pluralize nouns using Android quantity strings, and how to perform date-time localization.

And with that, my watch is ended. Please don’t hesitate to leave a comment if you have any questions.

Источник