DevGex Search

This article provides a comprehensive guide on using putExtra() and getExtra() methods in Android Intents for transferring string data between activities. Through detailed code examples, it explains the complete process from creating Intents and adding string data in the sender activity to extracting and utilizing data in the receiver activity. The content covers dynamic user input handling, null value checking, Bundle usage, and best practice recommendations, offering a complete data transfer solution for Android developers.

This article provides a comprehensive guide on using Android Debug Bridge (adb) shell commands to launch specific Activities. It begins by explaining the fundamental architecture and working principles of the adb tool, including its three-tier client-server-daemon structure. The core focus is on the am start command syntax and usage, with concrete examples demonstrating how to specify package names and Activity class names to initiate target components. The coverage extends to various adb connection methods (USB and Wi-Fi), multi-device management, common issue troubleshooting, and other practical techniques, offering Android developers a complete reference for command-line operations.

This article addresses the common issue of ActivityNotFoundException when opening PDF files in Android apps by implementing Intent.createChooser. It includes step-by-step code examples, error handling techniques, and best practices for robust file handling.

This paper comprehensively analyzes three core approaches to prevent Activity reloading during screen orientation changes in Android applications: distinguishing between initial creation and state restoration via savedInstanceState, locking screen orientation in the Manifest, and handling configuration changes using the configChanges attribute. The article details the implementation principles, applicable scenarios, and considerations for each method, emphasizing the importance of handling both orientation and screenSize in API level 13 and above, with complete code examples and best practice recommendations.

This paper comprehensively examines the challenge of accessing string resources outside Activity or Context in Android development. By analyzing the limitations of Resources.getSystem() method, it distinguishes between system resources and local resources, and provides multiple practical solutions including passing Context parameters, using Application Context, and resource manager patterns. With detailed code examples, the article deeply explores the applicable scenarios and implementation details of various approaches, helping developers better manage string resources in Android applications.

This article provides an in-depth exploration of efficient Activity Context management in Android development. Focusing on the need to access Context in classes requiring numerous instances, it details the implementation of global Context management through custom Application classes. The analysis covers limitations of traditional parameter passing, complete code examples, Application class lifecycle considerations, memory management precautions, and alternative approaches. By comparing the pros and cons of different methods, it helps developers select the most suitable Context management strategy.

This technical article provides an in-depth analysis of the common 'This Activity already has an action bar supplied by the window decor' error encountered during Android development when migrating from ActionBar to Toolbar. It offers comprehensive solutions including theme configuration, style settings, and code implementation to help developers successfully transition to Material Design's Toolbar component.

This article explores how to simplify ViewModel initialization in Android development using the viewModels and activityViewModels extension functions from the Fragment-KTX library. By comparing the traditional ViewModelProviders.of() approach with the new Kotlin delegated properties method, it analyzes dependency configuration, JVM target version settings, and solutions to common issues. Based on high-scoring Stack Overflow answers, with code examples and best practices, it provides a comprehensive migration guide to enhance code conciseness and maintainability.

This paper comprehensively examines the automatic focus acquisition problem of EditText components during Activity startup in Android applications. By analyzing the focus management mechanism, it explains why single EditText elements default to receiving focus and provides multiple solution strategies. The article emphasizes the method of setting focus attributes on the root layout view, while comparing the applicability of different approaches including clearFocus() and getWindow().getDecorView().clearFocus(). Through code examples and principle analysis, it helps developers thoroughly understand focus control mechanisms and avoid common interface interaction issues.

This article explores methods to change the Android app icon programmatically, focusing on using shortcuts and activity aliases. It provides step-by-step code examples and discusses limitations, including permission configuration, code implementation, and compatibility issues.

This article provides an in-depth analysis of the common RuntimeException in Android development: Failure delivering result ResultInfo{who=null, request=1888, result=0, data=null} to activity. Through a typical camera photo capture scenario, it explains the root cause where resultCode returns RESULT_CANCELED (value 0) and data becomes null when users cancel camera operations, leading to NullPointerException. Based on the best practice answer, the article systematically explains the importance of validating both resultCode and data integrity in the onActivityResult method, provides complete solutions in both Java and Kotlin, and compares the advantages and disadvantages of different validation strategies. Finally, it discusses the underlying principles of result delivery in Android Intent mechanisms and best practices for defensive programming.

This paper provides an in-depth analysis of the soft keyboard auto-popup issue in Android EditText controls, identifying the root cause in the focus management mechanism during Activity initialization. Based on Q&A data, it systematically presents three main solutions: configuring windowSoftInputMode in AndroidManifest.xml, using transparent views to preempt focus, and invoking the setShowSoftInputOnFocus method. The paper focuses on explaining the working principle of the stateHidden parameter and its compatibility from API Level 3 onward, while comparing the applicability, advantages, and disadvantages of each approach, offering comprehensive implementation guidelines and best practices for developers.

This article provides an in-depth analysis of the common issue in Android development where onActivityResult() callback is not triggered after a Fragment starts a child Activity using startActivityForResult(). Through examination of code examples from the provided Q&A data, it identifies the root cause as calling getActivity().startActivityForResult() instead of the Fragment's own startActivityForResult(). The article explains the lifecycle coordination mechanism between Fragments and host Activities, presents complete solutions, and discusses relevant Android framework design principles.

This article provides an in-depth exploration of technical implementations for requesting focus on EditText controls and automatically displaying the soft keyboard in Android development. By analyzing both XML configuration and programmatic control methods, it explains the working principles of the requestFocus() method, the appropriate timing for using InputMethodManager, and practical guidelines for correctly invoking these methods within the Activity lifecycle. The article includes code examples to help developers address common focus management issues in scenarios such as login pages.

This paper addresses common lifecycle management issues when implementing periodic network tasks in Android applications. Using Handler's postDelayed method can lead to task duplication upon Activity restart. Based on best practices, we propose Service as a solution, detailing how its lifecycle characteristics ensure continuous background execution unaffected by Activity restarts. The discussion covers proper Handler usage, Activity-Service interaction mechanisms, with complete code examples and implementation recommendations.

This article addresses a common error in Android development where the app crashes with the message 'You need to use a Theme.AppCompat theme (or descendant) with this activity'. The error occurs when an AppCompatActivity is assigned a non-AppCompat theme. The solution involves defining a custom fullscreen theme based on AppCompat and applying it to the activity. Key concepts include theme inheritance, compatibility issues, and best practices for Android UI theming.

This article provides an in-depth exploration of the challenges and solutions for obtaining view dimensions at runtime in Android applications. Addressing the common issue of getWidth() and getHeight() returning zero values, it builds upon the best-practice answer to analyze the relationship between view lifecycle and layout processes. By implementing a custom ImageView subclass with overridden onLayout() method, combined with observer pattern and activity communication mechanisms, a stable and reliable dimension acquisition solution is presented. The article also compares alternative approaches such as ViewTreeObserver listeners and manual measurement, explaining their applicability and limitations in different scenarios, offering comprehensive technical reference for developers.

This article explores various methods for obtaining screen orientation in Android development, focusing on the proper usage of Activity.getResources().getConfiguration().orientation. By comparing with the onConfigurationChanged() method, it explains how to accurately retrieve device orientation in onCreate(), avoiding layout loading issues, and provides code examples and best practice recommendations.

This article provides an in-depth analysis of the common Android error where a Fragment is not attached to a Context, illustrated through a real-world case study that results in an IllegalStateException when calling Fragment methods directly from an Activity. Based on Fragment lifecycle principles, it explains the root cause: the Fragment instance is not properly attached to the Activity via FragmentTransaction. The core solution involves initializing and attaching the Fragment in the Activity's onCreate method, ensuring that Fragment lifecycle methods like onAttach and onCreateView are invoked to establish a valid Context reference. Additionally, the article supplements with practical tips, such as using getActivity().getString() instead of getString() to avoid Context dependencies and checking if getContext() is null before critical operations. By adopting systematic lifecycle management and transaction handling, developers can prevent such runtime errors and enhance application stability.

This article provides an in-depth exploration of techniques for detecting whether an application is installed on the Android platform. It begins by analyzing the traditional approach based on PackageManager.getPackageInfo() and its proper invocation timing within the Activity lifecycle, highlighting the ANR risks caused by while loops in the original problem. It then details the package visibility restrictions introduced in Android 11 (API 30), explaining the necessity and configuration of <queries> manifest declarations. By comparing behavioral differences across API levels, it offers a comprehensive solution that balances compatibility and security, along with best practices to avoid common runtime exceptions.