Techniques To Avoid

The following points can be used as a technique that should be avoided in order to avoid any system failure in the development of free software. If you came to know that any of the following is used by any of your applications, then it must be patched immediately.

Avoid use of internal APIs

Although a strong message to the users against using this technique, but many developers still use the internal APIs. The most commonly used techniques are the folding Bluetooth API and the internal brightness control API that was there in 1.0 and 1.1 versions. There is a bug that gave free apps using the API, even without any prior authorization that was later fixed in Android 1.5. As a result, it was determined that the applications in Android 1.5, which is the use of the API is broken. It is therefore necessary to find out if your application using any of the API and if it is better to update the Android applications.

Avoid direct manipulation of settings

While using this technique is not prohibited for reasons that some changes made in the behavior of the Android software development, the main reason for bringing about such changes is to outsource certain activities because of the development of Android and the respective manufacturers. Even without notifying the user more than the application automatically changes the system settings. But now, the settings can not be manipulated by the application without prior approval. To open the configuration screen apps will now have to send intent, and then they can make the necessary changes manually. Under Android.provider.Settings.Secure class only those settings that are affected have moved to secure class settings.

Avoid water technique with Layouts

View rendering infrastructure has undergone changes as a result of which the display pattern of the hierarchy can lead to system crashes, but the development of Android 1.5 software was able to exhibit this problem long before Android 1.1. Appearance can be simplified by using the Frame Layout tables and layout.

Do not assume bad hardware

Soft keyboard support Android 1.5, will soon wipe the physical keyboard altogether. In the case of a physical keyboard prerequisites for the development of their Android apps then it becomes imperative to go down and take only a soft keyboard as soon as possible.

Avoid technical revolutions ashes are not careful

All who have come up with the Android 1.5 or later versions will have the ability to rotate the screen based on the user's orientation to the device. In certain devices to Android 1.5 will be done automatically by the system and many other users can enable the option. As a result, the development of Android applications will begin conducting business due to unexpected re-determination by their own. This happens under the assumption that the rotation of the screen is only possible if the physical keyboard is exposed. In the absence of a physical keyboard, a re-orientation will never take place.