Allows the app to create network sockets and use custom network protocols. The browser and other applications provide means to send data to the internet, so this permission is not required to send data to the internet. Allows the app to view information about network connections such as which networks exist and are connected. Allows the app to view information about Wi-Fi networking, such as whether Wi-Fi is enabled and name of connected Wi-Fi devices. Allows the app to receive packets sent to all devices on a Wi-Fi network using multicast addresses, not just your phone.
It uses more power than the non-multicast mode. Allows the app to connect to and disconnect from Wi-Fi access points and to make changes to device configuration for Wi-Fi networks. Allows the app to view the configuration of the Bluetooth on the phone, and to make and accept connections with paired devices.
Allows the app to configure the local Bluetooth phone, and to discover and pair with remote devices. Allows the app to have itself started as soon as the system has finished booting. See Selecting a device build for the build configurations of all existing devices. The userdebug build should behave the same as the user build, with the ability to enable additional debugging that normally violates the security model of the platform.
This makes the userdebug build good for user testing with greater diagnosis capabilities. When developing with the userdebug build, follow the userdebug guidelines. The eng build prioritizes engineering productivity for engineers who work on the platform. The eng build turns off various optimizations used to provide a good user experience.
Otherwise, the eng build has behavior similar to the user and userdebug builds so that device developers can see how the code behaves in those environments. For more information about building for and running on actual hardware, see Flashing Devices. The tapas command configures the build of unbundled apps.
It selects individual apps to be built by the Android build system. Unlike lunch , tapas does not request the building of images for a device. Build everything with m. If you don't provide a -j argument, the build system automatically selects a parallel task count that it thinks is optimal for your system. As explained above, you can build specific modules instead of the full device image by listing their names in your m command line.
In addition, m provides some pseudotargets for special purposes. Some examples are:. Run m help to see what other pseudotargets m provides. You can either run your build on an emulator or flash it on a device. Because you've already selected your build target with lunch , it's unlikely to run on a different target than it was built for.
To flash a device, use fastboot , which should be included in your path after a successful build. See Flashing a device for instructions. The emulator is added to your path automatically by the build process. More about the build tools. More about the profilers. Chrome OS For information on recommended devices and specifications, as well as Android Emulator support, visit chromeos. Thank you for downloading Android Studio! Download Android Studio Introduction 1. Accepting this License Agreement 2.
If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity. SDK License from Google 3. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose.
Google reserves all rights not expressly granted to you. Except to the extent required by applicable third party licenses, you may not copy except for backup purposes , modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK.
You agree that Google may stop permanently or temporarily providing the SDK or any features within the SDK to you or to users generally at Google's sole discretion, without prior notice to you. Use of the SDK by You 4. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users.
If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so. Your Developer Credentials 5. Privacy and Information 6. Before any of this information is collected, the SDK will notify you and seek your consent.
If you withhold consent, the information will not be collected. Third Party Applications 7. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources.
You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources either in whole or in part unless you have been specifically given permission to do so by the relevant owners.
0コメント