热门标签 | HotTags
当前位置:  开发笔记 > 编程语言 > 正文

了解开发手机的各项参数之SystemProperties

SystemProperties这个涉及的东西比较多,我这里只讲点简单的概念和常用的属性.Android的系统属性,主要分为两种:1.用文件保存的持久属性mydroid

SystemProperties这个涉及的东西比较多,我这里只讲点简单的概念和常用的属性.


Android的系统属性,主要分为两种:

1. 用文件保存的持久属性

mydroid\bionic\libc\include\sys\_system_properties.h 这个文件中有定义:

/*
** Rules:
**
** - there is only one writer, but many readers
** - prop_area.count will never decrease in value
** - once allocated, a prop_info's name will not change
** - once allocated, a prop_info's offset will not change
** - reading a value requires the following steps
**   1. serial = pi->serial
**   2. if SERIAL_DIRTY(serial), wait*, then goto 1
**   3. memcpy(local, pi->value, SERIAL_VALUE_LEN(serial) + 1)
**   4. if pi->serial != serial, goto 2
**
** - writing a value requires the following steps
**   1. pi->serial = pi->serial | 1
**   2. memcpy(pi->value, local_value, value_len)
**   3. pi->serial = (value_len <<24) | ((pi->serial + 1) & 0xffffff)
*/

#define PROP_PATH_RAMDISK_DEFAULT  "/default.prop"
#define PROP_PATH_SYSTEM_BUILD     "/system/build.prop"
#define PROP_PATH_SYSTEM_DEFAULT   "/system/default.prop"
#define PROP_PATH_LOCAL_OVERRIDE   "/data/local.prop"
#define PROP_PATH_FACTORY          "/factory/factory.prop"

2.每次开机都会导入的Cache属性,Framework层通过:

frameworks\base\core\java\android\os\SystemProperties.java 这个类来操作.

Cache的存储方式为:

/*
 * Properties are stored in a hybrid trie/binary tree structure.
 * Each property's name is delimited at '.' characters, and the tokens are put
 * into a trie structure.  Siblings at each level of the trie are stored in a
 * binary tree.  For instance, "ro.secure"="1" could be stored as follows:
 *
 * +-----+   children    +----+   children    +--------+
 * |     |-------------->| ro |-------------->| secure |
 * +-----+               +----+               +--------+
 *                       /    \                /   |
 *                 left /      \ right   left /    |  prop   +===========+
 *                     v        v            v     +-------->| ro.secure |
 *                  +-----+   +-----+     +-----+            +-----------+
 *                  | net |   | sys |     | com |            |     1     |
 *                  +-----+   +-----+     +-----+            +===========+
 */


如何获取Android的系统属性

1.通过android.os.Build这个类,我们可以得到一些基本信息:

以下是Build类的源码:

/*
 * Copyright (C) 2007 The Android Open Source Project
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package android.os;

import com.android.internal.telephony.TelephonyProperties;

/**
 * Information about the current build, extracted from system properties.
 */
public class Build {
    /** Value used for when a build property is unknown. */
    public static final String UNKNOWN = "unknown";

    /** Either a changelist number, or a label like "M4-rc20". */
    public static final String ID = getString("ro.build.id");

    /** A build ID string meant for displaying to the user */
    public static final String DISPLAY = getString("ro.build.display.id");

    /** The name of the overall product. */
    public static final String PRODUCT = getString("ro.product.name");

    /** The name of the industrial design. */
    public static final String DEVICE = getString("ro.product.device");

    /** The name of the underlying board, like "goldfish". */
    public static final String BOARD = getString("ro.product.board");

    /** The name of the instruction set (CPU type + ABI convention) of native code. */
    public static final String CPU_ABI = getString("ro.product.cpu.abi");

    /** The name of the second instruction set (CPU type + ABI convention) of native code. */
    public static final String CPU_ABI2 = getString("ro.product.cpu.abi2");

    /** The manufacturer of the product/hardware. */
    public static final String MANUFACTURER = getString("ro.product.manufacturer");

    /** The brand (e.g., carrier) the software is customized for, if any. */
    public static final String BRAND = getString("ro.product.brand");

    /** The end-user-visible name for the end product. */
    public static final String MODEL = getString("ro.product.model");

    /** The system bootloader version number. */
    public static final String BOOTLOADER = getString("ro.bootloader");

    /**
     * The radio firmware version number.
     *
     * @deprecated The radio firmware version is frequently not
     * available when this class is initialized, leading to a blank or
     * "unknown" value for this string.  Use
     * {@link #getRadioVersion} instead.
     */
    @Deprecated
    public static final String RADIO = getString(TelephonyProperties.PROPERTY_BASEBAND_VERSION);

    /** The name of the hardware (from the kernel command line or /proc). */
    public static final String HARDWARE = getString("ro.hardware");

    /** A hardware serial number, if available.  Alphanumeric only, case-insensitive. */ 
    public static final String SERIAL = getString("ro.serialno");
  
    /** Various version strings. */
    public static class VERSION {
        /**
         * The internal value used by the underlying source control to
         * represent this build.  E.g., a perforce changelist number
         * or a git hash.
         */
        public static final String INCREMENTAL = getString("ro.build.version.incremental");

        /**
         * The user-visible version string.  E.g., "1.0" or "3.4b5".
         */
        public static final String RELEASE = getString("ro.build.version.release");

        /**
         * The user-visible SDK version of the framework in its raw String
         * representation; use {@link #SDK_INT} instead.
         * 
         * @deprecated Use {@link #SDK_INT} to easily get this as an integer.
         */
        @Deprecated
        public static final String SDK = getString("ro.build.version.sdk");

        /**
         * The user-visible SDK version of the framework; its possible
         * values are defined in {@link Build.VERSION_CODES}.
         */
        public static final int SDK_INT = SystemProperties.getInt(
                "ro.build.version.sdk", 0);

        /**
         * The current development codename, or the string "REL" if this is
         * a release build.
         */
        public static final String CODENAME = getString("ro.build.version.codename");

        /**
         * The SDK version to use when accessing resources.
         * Use the current SDK version code.  If we are a development build,
         * also allow the previous SDK version + 1.
         * @hide
         */
        public static final int RESOURCES_SDK_INT = SDK_INT
                + ("REL".equals(CODENAME) ? 0 : 1);
    }

    /**
     * Enumeration of the currently known SDK version codes.  These are the
     * values that can be found in {@link VERSION#SDK}.  Version numbers
     * increment monotonically with each official platform release.
     */
    public static class VERSION_CODES {
        /**
         * Magic version number for a current development build, which has
         * not yet turned into an official release.
         */
        public static final int CUR_DEVELOPMENT = 10000;
        
        /**
         * October 2008: The original, first, version of Android.  Yay!
         */
        public static final int BASE = 1;
        
        /**
         * February 2009: First Android update, officially called 1.1.
         */
        public static final int BASE_1_1 = 2;
        
        /**
         * May 2009: Android 1.5.
         */
        public static final int CUPCAKE = 3;
        
        /**
         * September 2009: Android 1.6.
         * 
         * 

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • They must explicitly request the * {@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE} permission to be * able to modify the contents of the SD card. (Apps targeting * earlier versions will always request the permission.) *
  • They must explicitly request the * {@link android.Manifest.permission#READ_PHONE_STATE} permission to be * able to be able to retrieve phone state info. (Apps targeting * earlier versions will always request the permission.) *
  • They are assumed to support different screen densities and * sizes. (Apps targeting earlier versions are assumed to only support * medium density normal size screens unless otherwise indicated). * They can still explicitly specify screen support either way with the * supports-screens manifest tag. *
  • {@link android.widget.TabHost} will use the new dark tab * background design. *
*/ public static final int DOnUT= 4; /** * November 2009: Android 2.0 * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • The {@link android.app.Service#onStartCommand * Service.onStartCommand} function will return the new * {@link android.app.Service#START_STICKY} behavior instead of the * old compatibility {@link android.app.Service#START_STICKY_COMPATIBILITY}. *
  • The {@link android.app.Activity} class will now execute back * key presses on the key up instead of key down, to be able to detect * canceled presses from virtual keys. *
  • The {@link android.widget.TabWidget} class will use a new color scheme * for tabs. In the new scheme, the foreground tab has a medium gray background * the background tabs have a dark gray background. *
*/ public static final int ECLAIR = 5; /** * December 2009: Android 2.0.1 */ public static final int ECLAIR_0_1 = 6; /** * January 2010: Android 2.1 */ public static final int ECLAIR_MR1 = 7; /** * June 2010: Android 2.2 */ public static final int FROYO = 8; /** * November 2010: Android 2.3 * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • The application's notification icons will be shown on the new * dark status bar background, so must be visible in this situation. *
*/ public static final int GINGERBREAD = 9; /** * February 2011: Android 2.3.3. */ public static final int GINGERBREAD_MR1 = 10; /** * February 2011: Android 3.0. * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • The default theme for applications is now dark holographic: * {@link android.R.style#Theme_Holo}. *
  • On large screen devices that do not have a physical menu * button, the soft (compatibility) menu is disabled. *
  • The activity lifecycle has changed slightly as per * {@link android.app.Activity}. *
  • An application will crash if it does not call through * to the super implementation of its * {@link android.app.Activity#onPause Activity.onPause()} method. *
  • When an application requires a permission to access one of * its components (activity, receiver, service, provider), this * permission is no longer enforced when the application wants to * access its own component. This means it can require a permission * on a component that it does not itself hold and still access that * component. *
  • {@link android.content.Context#getSharedPreferences * Context.getSharedPreferences()} will not automatically reload * the preferences if they have changed on storage, unless * {@link android.content.Context#MODE_MULTI_PROCESS} is used. *
  • {@link android.view.ViewGroup#setMotionEventSplittingEnabled} * will default to true. *
  • {@link android.view.WindowManager.LayoutParams#FLAG_SPLIT_TOUCH} * is enabled by default on windows. *
  • {@link android.widget.PopupWindow#isSplitTouchEnabled() * PopupWindow.isSplitTouchEnabled()} will return true by default. *
  • {@link android.widget.GridView} and {@link android.widget.ListView} * will use {@link android.view.View#setActivated View.setActivated} * for selected items if they do not implement {@link android.widget.Checkable}. *
  • {@link android.widget.Scroller} will be constructed with * "flywheel" behavior enabled by default. *
*/ public static final int HOnEYCOMB= 11; /** * May 2011: Android 3.1. */ public static final int HONEYCOMB_MR1 = 12; /** * June 2011: Android 3.2. * *

Update to Honeycomb MR1 to support 7 inch tablets, improve * screen compatibility mode, etc.

* *

As of this version, applications that don't say whether they * support XLARGE screens will be assumed to do so only if they target * {@link #HONEYCOMB} or later; it had been {@link #GINGERBREAD} or * later. Applications that don't support a screen size at least as * large as the current screen will provide the user with a UI to * switch them in to screen size compatibility mode.

* *

This version introduces new screen size resource qualifiers * based on the screen size in dp: see * {@link android.content.res.Configuration#screenWidthDp}, * {@link android.content.res.Configuration#screenHeightDp}, and * {@link android.content.res.Configuration#smallestScreenWidthDp}. * Supplying these in as per * {@link android.content.pm.ApplicationInfo#requiresSmallestWidthDp}, * {@link android.content.pm.ApplicationInfo#compatibleWidthLimitDp}, and * {@link android.content.pm.ApplicationInfo#largestWidthLimitDp} is * preferred over the older screen size buckets and for older devices * the appropriate buckets will be inferred from them.

* *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • New {@link android.content.pm.PackageManager#FEATURE_SCREEN_PORTRAIT} * and {@link android.content.pm.PackageManager#FEATURE_SCREEN_LANDSCAPE} * features were introduced in this release. Applications that target * previous platform versions are assumed to require both portrait and * landscape support in the device; when targeting Honeycomb MR1 or * greater the application is responsible for specifying any specific * orientation it requires.

    *
  • {@link android.os.AsyncTask} will use the serial executor * by default when calling {@link android.os.AsyncTask#execute}.

    *
  • {@link android.content.pm.ActivityInfo#configChanges * ActivityInfo.configChanges} will have the * {@link android.content.pm.ActivityInfo#CONFIG_SCREEN_SIZE} and * {@link android.content.pm.ActivityInfo#CONFIG_SMALLEST_SCREEN_SIZE} * bits set; these need to be cleared for older applications because * some developers have done absolute comparisons against this value * instead of correctly masking the bits they are interested in. *

*/ public static final int HONEYCOMB_MR2 = 13; /** * October 2011: Android 4.0. * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • For devices without a dedicated menu key, the software compatibility * menu key will not be shown even on phones. By targeting Ice Cream Sandwich * or later, your UI must always have its own menu UI affordance if needed, * on both tablets and phones. The ActionBar will take care of this for you. *
  • 2d drawing hardware acceleration is now turned on by default. * You can use * {@link android.R.attr#hardwareAccelerated android:hardwareAccelerated} * to turn it off if needed, although this is strongly discouraged since * it will result in poor performance on larger screen devices. *
  • The default theme for applications is now the "device default" theme: * {@link android.R.style#Theme_DeviceDefault}. This may be the * holo dark theme or a different dark theme defined by the specific device. * The {@link android.R.style#Theme_Holo} family must not be modified * for a device to be considered compatible. Applications that explicitly * request a theme from the Holo family will be guaranteed that these themes * will not change character within the same platform version. Applications * that wish to blend in with the device should use a theme from the * {@link android.R.style#Theme_DeviceDefault} family. *
  • Managed cursors can now throw an exception if you directly close * the cursor yourself without stopping the management of it; previously failures * would be silently ignored. *
  • The fadingEdge attribute on views will be ignored (fading edges is no * longer a standard part of the UI). A new requiresFadingEdge attribute allows * applications to still force fading edges on for special cases. *
  • {@link android.content.Context#bindService Context.bindService()} * will not automatically add in {@link android.content.Context#BIND_WAIVE_PRIORITY}. *
  • App Widgets will have standard padding automatically added around * them, rather than relying on the padding being baked into the widget itself. *
  • An exception will be thrown if you try to change the type of a * window after it has been added to the window manager. Previously this * would result in random incorrect behavior. *
  • {@link android.view.animation.AnimationSet} will parse out * the duration, fillBefore, fillAfter, repeatMode, and startOffset * XML attributes that are defined. *
  • {@link android.app.ActionBar#setHomeButtonEnabled * ActionBar.setHomeButtonEnabled()} is false by default. *
*/ public static final int ICE_CREAM_SANDWICH = 14; /** * December 2011: Android 4.0.3. */ public static final int ICE_CREAM_SANDWICH_MR1 = 15; /** * June 2012: Android 4.1. * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • You must explicitly request the {@link android.Manifest.permission#READ_CALL_LOG} * and/or {@link android.Manifest.permission#WRITE_CALL_LOG} permissions; * access to the call log is no longer implicitly provided through * {@link android.Manifest.permission#READ_CONTACTS} and * {@link android.Manifest.permission#WRITE_CONTACTS}. *
  • {@link android.widget.RemoteViews} will throw an exception if * setting an onClick handler for views being generated by a * {@link android.widget.RemoteViewsService} for a collection container; * previously this just resulted in a warning log message. *
  • New {@link android.app.ActionBar} policy for embedded tabs: * embedded tabs are now always stacked in the action bar when in portrait * mode, regardless of the size of the screen. *
  • {@link android.webkit.WebSettings#setAllowFileAccessFromFileURLs(boolean) * WebSettings.setAllowFileAccessFromFileURLs} and * {@link android.webkit.WebSettings#setAllowUniversalAccessFromFileURLs(boolean) * WebSettings.setAllowUniversalAccessFromFileURLs} default to false. *
  • Calls to {@link android.content.pm.PackageManager#setComponentEnabledSetting * PackageManager.setComponentEnabledSetting} will now throw an * IllegalArgumentException if the given component class name does not * exist in the application's manifest. *
  • {@link android.nfc.NfcAdapter#setNdefPushMessage * NfcAdapter.setNdefPushMessage}, * {@link android.nfc.NfcAdapter#setNdefPushMessageCallback * NfcAdapter.setNdefPushMessageCallback} and * {@link android.nfc.NfcAdapter#setOnNdefPushCompleteCallback * NfcAdapter.setOnNdefPushCompleteCallback} will throw * IllegalStateException if called after the Activity has been destroyed. *
  • Accessibility services must require the new * {@link android.Manifest.permission#BIND_ACCESSIBILITY_SERVICE} permission or * they will not be available for use. *
  • {@link android.accessibilityservice.AccessibilityServiceInfo#FLAG_INCLUDE_NOT_IMPORTANT_VIEWS * AccessibilityServiceInfo.FLAG_INCLUDE_NOT_IMPORTANT_VIEWS} must be set * for unimportant views to be included in queries. *
*/ public static final int JELLY_BEAN = 16; /** * Android 4.2: Moar jelly beans! * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • Content Providers: The default value of {@code android:exported} is now * {@code false}. See * * the android:exported section in the provider documentation for more details.
  • *
  • {@link android.view.View#getLayoutDirection() View.getLayoutDirection()} * can return different values than {@link android.view.View#LAYOUT_DIRECTION_LTR} * based on the locale etc. *
  • {@link android.webkit.WebView#addJavascriptInterface(Object, String) * WebView.addJavascriptInterface} requires explicit annotations on methods * for them to be accessible from Javascript. *
*/ public static final int JELLY_BEAN_MR1 = 17; } /** The type of build, like "user" or "eng". */ public static final String TYPE = getString("ro.build.type"); /** Comma-separated tags describing the build, like "unsigned,debug". */ public static final String TAGS = getString("ro.build.tags"); /** A string that uniquely identifies this build. Do not attempt to parse this value. */ public static final String FINGERPRINT = getString("ro.build.fingerprint"); // The following properties only make sense for internal engineering builds. public static final long TIME = getLong("ro.build.date.utc") * 1000; public static final String USER = getString("ro.build.user"); public static final String HOST = getString("ro.build.host"); /** * Returns true if we are running a debug build such as "user-debug" or "eng". * @hide */ public static final boolean IS_DEBUGGABLE = SystemProperties.getInt("ro.debuggable", 0) == 1; /** * Returns the version string for the radio firmware. May return * null (if, for instance, the radio is not currently on). */ public static String getRadioVersion() { return SystemProperties.get(TelephonyProperties.PROPERTY_BASEBAND_VERSION, null); } private static String getString(String property) { return SystemProperties.get(property, UNKNOWN); } private static long getLong(String property) { try { return Long.parseLong(SystemProperties.get(property)); } catch (NumberFormatException e) { return -1; } } }

那么就写一个例子,把Build中能查到的所有属性都打印出来吧,当然手机用的是我的花屏MX3.

public class MainActivity extends Activity {

	private TextView tv;

	@Override
	protected void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setContentView(R.layout.activity_main);
	
		StringBuffer sb = new StringBuffer();
		sb.append("ro.build.id"+" : "+Build.ID+"\n");
		sb.append("ro.build.display.id"+" : "+Build.DISPLAY+"\n");
		sb.append("ro.product.name"+" : "+Build.PRODUCT+"\n");
		sb.append("ro.product.device"+" : "+Build.DEVICE+"\n");
		sb.append("ro.product.board"+" : "+Build.BOARD+"\n");
		sb.append("ro.product.cpu.abi"+" : "+Build.CPU_ABI+"\n");
		sb.append("ro.product.cpu.abi2"+" : "+Build.CPU_ABI2+"\n");
		sb.append("ro.product.manufacturer"+" : "+Build.MANUFACTURER+"\n");
		sb.append("ro.product.brand"+" : "+Build.BRAND+"\n");
		sb.append("ro.product.model"+" : "+Build.MODEL+"\n");
		sb.append("ro.bootloader"+" : "+Build.BOOTLOADER+"\n");
		
		sb.append("ro.hardware"+" : "+Build.HARDWARE+"\n");
		sb.append("ro.serialno"+" : "+Build.SERIAL+"\n");
		sb.append("ro.build.type"+" : "+Build.TYPE+"\n");
		sb.append("ro.build.tags"+" : "+Build.TAGS+"\n");
		sb.append("ro.build.fingerprint"+" : "+Build.FINGERPRINT+"\n");
		sb.append("ro.build.date.utc"+" : "+Build.TIME+"\n");
		sb.append("ro.build.user"+" : "+Build.USER+"\n");
		sb.append("ro.build.host"+" : "+Build.HOST+"\n");
		sb.append("radioVersion"+" : "+Build.getRadioVersion()+"\n");
		
		sb.append("ro.build.version.incremental"+" : "+Build.VERSION.INCREMENTAL+"\n");
		sb.append("ro.build.version.release"+" : "+Build.VERSION.RELEASE+"\n");
		sb.append("ro.build.version.sdk"+" : "+Build.VERSION.SDK_INT+"\n");
		sb.append("ro.build.version.codename"+" : "+Build.VERSION.CODENAME+"\n");

		tv = (TextView) findViewById(R.id.show);
		tv.setText(sb.toString());

	}
}

运行截图:

2.通过反射,直接调用SystemProperties这个类的方法:

当手机通过adb连接电脑后,我们可以通过 adb shell getprop > d:\prop.txt 来获得系统的所有属性值.

而Build这个类获得的属性有限,所以通过反射,我们可以获得更多的信息.

我们发现,Build中有个用 hide标记的属性,让我们用反射把他们show出来

    /**
     * Returns true if we are running a debug build such as "user-debug" or "eng".
     * @hide
     */
    public static final boolean IS_DEBUGGABLE =
            SystemProperties.getInt("ro.debuggable", 0) == 1;

public class MainActivity extends Activity {

	private TextView tv;

	@Override
	protected void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setContentView(R.layout.activity_main);
	
		
		try {
			Class classT = Class.forName("android.os.SystemProperties");
			Method m = classT.getMethod("getInt", new Class[]{String.class,int.class});
			int isDebugable = (Integer) m.invoke(classT,new Object[]{"ro.debuggable",0});
			
			tv = (TextView) findViewById(R.id.show);
			tv.setText("       "+(isDebugable == 1));
		} catch (IllegalArgumentException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (ClassNotFoundException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (NoSuchMethodException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (IllegalAccessException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (InvocationTargetException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}

	}
}





推荐阅读
  • 本文介绍了设计师伊振华受邀参与沈阳市智慧城市运行管理中心项目的整体设计,并以数字赋能和创新驱动高质量发展的理念,建设了集成、智慧、高效的一体化城市综合管理平台,促进了城市的数字化转型。该中心被称为当代城市的智能心脏,为沈阳市的智慧城市建设做出了重要贡献。 ... [详细]
  • 自动轮播,反转播放的ViewPagerAdapter的使用方法和效果展示
    本文介绍了如何使用自动轮播、反转播放的ViewPagerAdapter,并展示了其效果。该ViewPagerAdapter支持无限循环、触摸暂停、切换缩放等功能。同时提供了使用GIF.gif的示例和github地址。通过LoopFragmentPagerAdapter类的getActualCount、getActualItem和getActualPagerTitle方法可以实现自定义的循环效果和标题展示。 ... [详细]
  • CF:3D City Model(小思维)问题解析和代码实现
    本文通过解析CF:3D City Model问题,介绍了问题的背景和要求,并给出了相应的代码实现。该问题涉及到在一个矩形的网格上建造城市的情景,每个网格单元可以作为建筑的基础,建筑由多个立方体叠加而成。文章详细讲解了问题的解决思路,并给出了相应的代码实现供读者参考。 ... [详细]
  • baresip android编译、运行教程1语音通话
    本文介绍了如何在安卓平台上编译和运行baresip android,包括下载相关的sdk和ndk,修改ndk路径和输出目录,以及创建一个c++的安卓工程并将目录考到cpp下。详细步骤可参考给出的链接和文档。 ... [详细]
  • 本文介绍了Android 7的学习笔记总结,包括最新的移动架构视频、大厂安卓面试真题和项目实战源码讲义。同时还分享了开源的完整内容,并提醒读者在使用FileProvider适配时要注意不同模块的AndroidManfiest.xml中配置的xml文件名必须不同,否则会出现问题。 ... [详细]
  • 本文讨论了clone的fork与pthread_create创建线程的不同之处。进程是一个指令执行流及其执行环境,其执行环境是一个系统资源的集合。在调用系统调用fork创建一个进程时,子进程只是完全复制父进程的资源,这样得到的子进程独立于父进程,具有良好的并发性。但是二者之间的通讯需要通过专门的通讯机制,另外通过fork创建子进程系统开销很大。因此,在某些情况下,使用clone或pthread_create创建线程可能更加高效。 ... [详细]
  • 在Android开发中,使用Picasso库可以实现对网络图片的等比例缩放。本文介绍了使用Picasso库进行图片缩放的方法,并提供了具体的代码实现。通过获取图片的宽高,计算目标宽度和高度,并创建新图实现等比例缩放。 ... [详细]
  • 云原生边缘计算之KubeEdge简介及功能特点
    本文介绍了云原生边缘计算中的KubeEdge系统,该系统是一个开源系统,用于将容器化应用程序编排功能扩展到Edge的主机。它基于Kubernetes构建,并为网络应用程序提供基础架构支持。同时,KubeEdge具有离线模式、基于Kubernetes的节点、群集、应用程序和设备管理、资源优化等特点。此外,KubeEdge还支持跨平台工作,在私有、公共和混合云中都可以运行。同时,KubeEdge还提供数据管理和数据分析管道引擎的支持。最后,本文还介绍了KubeEdge系统生成证书的方法。 ... [详细]
  • IhaveconfiguredanactionforaremotenotificationwhenitarrivestomyiOsapp.Iwanttwodiff ... [详细]
  • Linux重启网络命令实例及关机和重启示例教程
    本文介绍了Linux系统中重启网络命令的实例,以及使用不同方式关机和重启系统的示例教程。包括使用图形界面和控制台访问系统的方法,以及使用shutdown命令进行系统关机和重启的句法和用法。 ... [详细]
  • http:my.oschina.netleejun2005blog136820刚看到群里又有同学在说HTTP协议下的Get请求参数长度是有大小限制的,最大不能超过XX ... [详细]
  • Android系统移植与调试之如何修改Android设备状态条上音量加减键在横竖屏切换的时候的显示于隐藏
    本文介绍了如何修改Android设备状态条上音量加减键在横竖屏切换时的显示与隐藏。通过修改系统文件system_bar.xml实现了该功能,并分享了解决思路和经验。 ... [详细]
  • 本文记录了在vue cli 3.x中移除console的一些采坑经验,通过使用uglifyjs-webpack-plugin插件,在vue.config.js中进行相关配置,包括设置minimizer、UglifyJsPlugin和compress等参数,最终成功移除了console。同时,还包括了一些可能出现的报错情况和解决方法。 ... [详细]
  • VueCLI多页分目录打包的步骤记录
    本文介绍了使用VueCLI进行多页分目录打包的步骤,包括页面目录结构、安装依赖、获取Vue CLI需要的多页对象等内容。同时还提供了自定义不同模块页面标题的方法。 ... [详细]
  • 本文介绍了在CentOS 6.4系统中更新源地址的方法,包括备份现有源文件、下载163源、修改文件名、更新列表和系统,并提供了相应的命令。 ... [详细]
author-avatar
爱你真好958_358
这个家伙很懒,什么也没留下!
PHP1.CN | 中国最专业的PHP中文社区 | DevBox开发工具箱 | json解析格式化 |PHP资讯 | PHP教程 | 数据库技术 | 服务器技术 | 前端开发技术 | PHP框架 | 开发工具 | 在线工具
Copyright © 1998 - 2020 PHP1.CN. All Rights Reserved | 京公网安备 11010802041100号 | 京ICP备19059560号-4 | PHP1.CN 第一PHP社区 版权所有